From owner-freebsd-stable Sun Apr 8 0:15:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nero.transactionsite.com (nero.transactionsite.com [203.14.245.6]) by hub.freebsd.org (Postfix) with SMTP id 0E85437B422 for ; Sun, 8 Apr 2001 00:15:13 -0700 (PDT) (envelope-from janm@transactionware.com) Received: (qmail 88982 invoked by uid 0); 8 Apr 2001 07:11:00 -0000 Received: from janm.transactionsite.com (HELO janm) (192.168.1.8) by nero.transactionsite.com with SMTP; 8 Apr 2001 07:11:00 -0000 Message-ID: <00d901c0bffb$8042c590$0801a8c0@janm.transactionsite.com> From: "Jan Mikkelsen" To: Subject: Error dev/sound/pc/cmi.c during make buildkernel Date: Sun, 8 Apr 2001 17:14:07 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3612.1700 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm getting the following errors when doing a 'make buildkernel': /mnt/usr/src/sys/modules/sound/driver/cmi/../../../../dev/sound/pci/cmi. c: In function `cmi_init': /mnt/usr/src/sys/modules/sound/driver/cmi/../../../../dev/sound/pci/cmi. c:747: `CMPCI_REG_N4SPK3D' undeclared (first use in this function) /mnt/usr/src/sys/modules/sound/driver/cmi/../../../../dev/sound/pci/cmi. c:747: (Each undeclared identifier is reported only once /mnt/usr/src/sys/modules/sound/driver/cmi/../../../../dev/sound/pci/cmi. c:747: for each function it appears in.) I cvsup'd about four hours ago, and I just cvsup'd again, with the same problem. Have I missed something? Regards, Jan Mikkelsen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 0:30: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from montgomery.accessunited.com.au (montgomery.accessunited.com.au [203.46.135.133]) by hub.freebsd.org (Postfix) with ESMTP id DE43837B424 for ; Sun, 8 Apr 2001 00:30:02 -0700 (PDT) (envelope-from phillip@accessunited.com.au) Received: from willie.accessunited.com.au (ernally-@willie.accessunited.com.au [203.46.135.139]) by montgomery.accessunited.com.au (8.10.1/8.10.1) with SMTP id f387Tts13574 for ; Sun, 8 Apr 2001 17:29:55 +1000 (EST) Message-Id: <200104080729.f387Tts13574@montgomery.accessunited.com.au> From: "Phillip" To: "freebsd-stable@freebsd.org" Date: Sun, 08 Apr 2001 17:30:02 +1100 (EDT) Reply-To: "Phillip" X-Mailer: PMMail 2.00.1500 for OS/2 Warp 4.05 In-Reply-To: <00d901c0bffb$8042c590$0801a8c0@janm.transactionsite.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Error dev/sound/pc/cmi.c during make buildkernel Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ditto. I'm having exactly the same problem after cvsupping about 8 hours ago. I've got no solution yet :( On Sun, 8 Apr 2001 17:14:07 +1000, Jan Mikkelsen wrote: >Hi, > >I'm getting the following errors when doing a 'make buildkernel': > >/mnt/usr/src/sys/modules/sound/driver/cmi/../../../../dev/sound/pci/cmi. >c: In function `cmi_init': >/mnt/usr/src/sys/modules/sound/driver/cmi/../../../../dev/sound/pci/cmi. >c:747: `CMPCI_REG_N4SPK3D' undeclared (first use in this function) >/mnt/usr/src/sys/modules/sound/driver/cmi/../../../../dev/sound/pci/cmi. >c:747: (Each undeclared identifier is reported only once >/mnt/usr/src/sys/modules/sound/driver/cmi/../../../../dev/sound/pci/cmi. >c:747: for each function it appears in.) > >I cvsup'd about four hours ago, and I just cvsup'd again, with the same >problem. > >Have I missed something? > >Regards, > >Jan Mikkelsen > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 0:41:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost.auckland.ac.nz (mailhost.auckland.ac.nz [130.216.1.4]) by hub.freebsd.org (Postfix) with ESMTP id 19FB037B422 for ; Sun, 8 Apr 2001 00:41:14 -0700 (PDT) (envelope-from walker@gromit.ele.auckland.ac.nz) Received: from gromit.ele.auckland.ac.nz (IDENT:postfix@gromit.ele.auckland.ac.nz [130.216.216.23]) by mailhost.auckland.ac.nz (8.9.2/8.9.2/8.9.2-ua) with ESMTP id TAA10396; Sun, 8 Apr 2001 19:41:13 +1200 (NZST) Received: by gromit.ele.auckland.ac.nz (Postfix, from userid 501) id 974773F19; Sun, 8 Apr 2001 19:41:12 +1200 (NZST) Date: Sun, 8 Apr 2001 19:41:12 +1200 From: Jamie Walker To: Jan Mikkelsen Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Error dev/sound/pc/cmi.c during make buildkernel Message-ID: <20010408194112.A1732@auckland.ac.nz> References: <00d901c0bffb$8042c590$0801a8c0@janm.transactionsite.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <00d901c0bffb$8042c590$0801a8c0@janm.transactionsite.com>; from janm@transactionware.com on Sun, Apr 08, 2001 at 05:14:07PM +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 08, 2001 at 05:14:07PM +1000, Jan Mikkelsen wrote: > /mnt/usr/src/sys/modules/sound/driver/cmi/../../../../dev/sound/pci/cmi. > c: In function `cmi_init': > /mnt/usr/src/sys/modules/sound/driver/cmi/../../../../dev/sound/pci/cmi. > c:747: `CMPCI_REG_N4SPK3D' undeclared (first use in this function) > /mnt/usr/src/sys/modules/sound/driver/cmi/../../../../dev/sound/pci/cmi. > c:747: (Each undeclared identifier is reported only once > /mnt/usr/src/sys/modules/sound/driver/cmi/../../../../dev/sound/pci/cmi. > c:747: for each function it appears in.) > > I cvsup'd about four hours ago, and I just cvsup'd again, with the same > problem. I'm getting the same error. I removed "device pcm" from my kernel configuration to no avail. -- Fone: +64-9-373-7599 x4679 Room: 2.315, E&EE Dept, School of Engineering Work: jj.walker@auckland.ac.nz Home: jamiew@clear.net.nz ICQ: 5632563 or shout loudly To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 2:34:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pop3.psconsult.nl (ps226.psconsult.nl [193.67.147.226]) by hub.freebsd.org (Postfix) with ESMTP id 0357637B422 for ; Sun, 8 Apr 2001 02:34:12 -0700 (PDT) (envelope-from paul@pop3.psconsult.nl) Received: (from paul@localhost) by pop3.psconsult.nl (8.9.2/8.9.2) id LAA42755 for freebsd-stable@FreeBSD.ORG; Sun, 8 Apr 2001 11:34:10 +0200 (CEST) (envelope-from paul) Date: Sun, 8 Apr 2001 11:34:10 +0200 From: Paul Schenkeveld To: freebsd-stable@FreeBSD.ORG Subject: make relase stops at missing sysinstall Message-ID: <20010408113410.A42640@psconsult.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I've tried 'make release' several times over the last couple of weeks but all attempts end with: -------------------------------------------------------------- >>> elf make world completed on Fri Apr 6 09:17:11 GMT 2001 (started Fri Apr 6 08:12:02 GMT 2001) -------------------------------------------------------------- + touch /tmp/.world_done + cd /usr/src/release/sysinstall cd: can't cd to /usr/src/release/sysinstall *** Error code 1 (ignored) *** Error code 1 (ignored) *** Error code 1 (ignored) *** Error code 2 The machine is a dual PentiumIII with enough memory running 4.3RC as of march 31, I've got a complete CVS repository in /usr/cvs. My /usr/src and /usr/release are symlinks to a big disk, I'm root and then do: rm -rf /usr/src/* /usr/release/snap # don't touch my symlinks CVSROOT=/usr/src export CVSROOT cd /usr cvs co -r RELENG_4 src cd /usr/src make -j8 buildworld # dual processor PIII, so -j8 cd /usr/src/release env - \ PATH=/bin:/usr/bin:/sbin:/usr/sbin \ HOME=$HOME \ TERM=dumb \ CVSROOT=${CVSROOT:-/usr/cvs} \ make release \ BINFORMAT=elf \ NODOC=YES \ NOPORTS=YES \ BUILDNAME=4.3-SNAP-`date +%Y%m%d` \ CHROOTDIR=/usr/release/snap Looks pretty much like the recipe in the FAQ to me. I needed the 'env' trick because my standard .profile puts a lot of stuff in my environment that will break the make release for sure. What I understand about a make buildworld is that sysinstall is not automatically built so I even tried a 'cd /usr/src/release/sysinstall; make all' between the make buildworld and the make release. The same script used to work half a year ago (I'm only not sure whether I've done a release 4 build this way or only release 3 builds). So far no luck so before I spend a lot of time reading and understanding the Makefiles I hope someone can give me a hint whether I'm doing something wrong here or somethins fell out of one of the Makefiles unnoticed by the release gurus. Thans all for your time, Paul Schenkeveld, Consultant PSconsult ICT Services BV To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 3:59:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hugo10.ka.punkt.de (kagate.punkt.de [194.77.232.254]) by hub.freebsd.org (Postfix) with ESMTP id 86D4A37B423 for ; Sun, 8 Apr 2001 03:59:14 -0700 (PDT) (envelope-from hausen@punkt.de) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.9.3/8.9.3) id MAA03091 for freebsd-stable@freebsd.org; Sun, 8 Apr 2001 12:59:12 +0200 (CEST) (envelope-from ry93) From: "Patrick M. Hausen" Message-Id: <200104081059.MAA03091@hugo10.ka.punkt.de> Subject: 4-STABLE MFC of sys/dev/sound/pci/cmi.c doesn't compile To: freebsd-stable@freebsd.org Date: Sun, 8 Apr 2001 12:59:12 +0200 (CEST) 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all! Apparently sys/dev/sound/pci/cmi.c committed 20 hours ago doesn't compile on my stable system, because CMPCI_REG_N4SPK3D is undefined. cmireg.h wasn't updated when that change was made. Patrick -- --- WEB ISS GmbH - Scheffelstr. 17a - 76135 Karlsruhe - 0721/9109-0 --- ------ Patrick M. Hausen - Technical Director - hausen@punkt.de ------- "Two men say, they're Jesus - one of 'em must be wrong." (Dire Straits) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 3:59:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.urx.com (mail.urx.com [63.170.19.36]) by hub.freebsd.org (Postfix) with ESMTP id 06B6C37B42C for ; Sun, 8 Apr 2001 03:59:19 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com [206.159.132.160] by mail.urx.com with ESMTP (SMTPD32-6.06) id A47B58B701A6; Sun, 08 Apr 2001 03:59:07 -0700 Message-ID: <3AD0447B.204AFA1A@urx.com> Date: Sun, 08 Apr 2001 03:59:07 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Jamie Walker Cc: Jan Mikkelsen , freebsd-stable@FreeBSD.ORG Subject: Re: Error dev/sound/pc/cmi.c during make buildkernel References: <00d901c0bffb$8042c590$0801a8c0@janm.transactionsite.com> <20010408194112.A1732@auckland.ac.nz> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jamie Walker wrote: > > On Sun, Apr 08, 2001 at 05:14:07PM +1000, Jan Mikkelsen wrote: > > > /mnt/usr/src/sys/modules/sound/driver/cmi/../../../../dev/sound/pci/cmi. > > c: In function `cmi_init': > > /mnt/usr/src/sys/modules/sound/driver/cmi/../../../../dev/sound/pci/cmi. > > c:747: `CMPCI_REG_N4SPK3D' undeclared (first use in this function) > > /mnt/usr/src/sys/modules/sound/driver/cmi/../../../../dev/sound/pci/cmi. > > c:747: (Each undeclared identifier is reported only once > > /mnt/usr/src/sys/modules/sound/driver/cmi/../../../../dev/sound/pci/cmi. > > c:747: for each function it appears in.) > > > > I cvsup'd about four hours ago, and I just cvsup'd again, with the same > > problem. > > I'm getting the same error. I removed "device pcm" from my kernel > configuration to no avail. > > It is broken right now. If you want to fix it, look for an email from John Capo. He has a patch to add + # define CMPCI_REG_N4SPK3D 0x04000000 to cmireg.h. Kent -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 4:56: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nu.nu.cuk.nu (nu.nu.cuk.nu [212.30.95.50]) by hub.freebsd.org (Postfix) with ESMTP id 9753337B424 for ; Sun, 8 Apr 2001 04:55:54 -0700 (PDT) (envelope-from cuk@cuk.nu) Received: from localhost (localhost.nu.nu.cuk.nu [127.0.0.1]) by nu.nu.cuk.nu (Postfix) with ESMTP id 632A01ABAA for ; Sun, 8 Apr 2001 13:56:01 +0200 (CEST) Received: from cuk.nu (iris.localnet [192.168.6.12]) by nu.nu.cuk.nu (Postfix) with ESMTP id 943621ABA9 for ; Sun, 8 Apr 2001 13:55:57 +0200 (CEST) Message-ID: <3AD05197.BD21B88C@cuk.nu> Date: Sun, 08 Apr 2001 13:55:03 +0200 From: Marko Cuk X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: OpenSSH & 4.3RC Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello !! I have problems with installing OpenSSH on 4.3RC maschine even when I cvsup ports and make buildworld. Some libraries are not well. Cuk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 6:43:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailf.telia.com (mailf.telia.com [194.22.194.25]) by hub.freebsd.org (Postfix) with ESMTP id BC34737B422 for ; Sun, 8 Apr 2001 06:43:34 -0700 (PDT) (envelope-from watchman@ludd.luth.se) Received: from d1o907.telia.com (d1o907.telia.com [195.252.38.241]) by mailf.telia.com (8.11.2/8.11.0) with ESMTP id f38DhWM09105; Sun, 8 Apr 2001 15:43:32 +0200 (CEST) Received: from ludd.luth.se (h63n2fls21o907.telia.com [213.66.203.63]) by d1o907.telia.com (8.8.8/8.8.8) with ESMTP id PAA14104; Sun, 8 Apr 2001 15:43:31 +0200 (CEST) Message-ID: <3AD06AED.1C7B0B44@ludd.luth.se> Date: Sun, 08 Apr 2001 15:43:10 +0200 From: Joachim =?iso-8859-1?Q?Str=F6mbergson?= Organization: Acne X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-RC i386) X-Accept-Language: en-US MIME-Version: 1.0 To: kstewart@urx.com Cc: Jamie Walker , Jan Mikkelsen , freebsd-stable@FreeBSD.ORG Subject: "Solution" Re: Error dev/sound/pc/cmi.c during make buildkernel References: <00d901c0bffb$8042c590$0801a8c0@janm.transactionsite.com> <20010408194112.A1732@auckland.ac.nz> <3AD0447B.204AFA1A@urx.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Aloha! Had the same problem as anybody else with the cmi.c from the last update. A quick fix was to comment out the offending line cmi_set4(sc, CMPCI_REG_MISC, CMPCI_REG_N4SPK3D); The compile goes through. Dunno about the runnability of the kernel though... -- Cheers! Joachim - Alltid i harmonisk svängning --- FairLight ------ FairLight ------ FairLight ------ FairLight --- Joachim Strömbergson ASIC SoC designer, nice to CUTE animals Phone: +46(0)31 - 27 98 47 Web: http://www.ludd.luth.se/~watchman --------------- Spamfodder: regeringen@regeringen.se --------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 8:38:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id 04A1C37B422 for ; Sun, 8 Apr 2001 08:38:30 -0700 (PDT) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.3+3.4W/8.11.3) with ESMTP/inet id f38FcB829717; Mon, 9 Apr 2001 00:38:15 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Cc: stable@freebsd.org In-Reply-To: <20010408113410.A42640@psconsult.nl> References: <20010408113410.A42640@psconsult.nl> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Urania) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 12 From: Makoto MATSUSHITA To: paul@psconsult.nl Subject: Re: make relase stops at missing sysinstall Date: Mon, 09 Apr 2001 00:37:52 +0900 Message-Id: <20010409003752F.matusita@jp.FreeBSD.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG paul> make release \ paul> BINFORMAT=elf \ paul> NODOC=YES \ paul> NOPORTS=YES \ paul> BUILDNAME=4.3-SNAP-`date +%Y%m%d` \ paul> CHROOTDIR=/usr/release/snap You forget to add 'RELEASETAG'. See src/release/Makefile. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 10:19:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from klima.physik.uni-mainz.de (klima.Physik.Uni-Mainz.DE [134.93.180.162]) by hub.freebsd.org (Postfix) with ESMTP id C86F137B423 for ; Sun, 8 Apr 2001 10:19:50 -0700 (PDT) (envelope-from ohartman@klima.physik.uni-mainz.de) Received: from klima.Physik.Uni-Mainz.DE (klima.Physik.Uni-Mainz.DE [134.93.180.162]) by klima.physik.uni-mainz.de (8.11.3/8.11.3) with ESMTP id f38HJnQ02848 for ; Sun, 8 Apr 2001 19:19:49 +0200 (CEST) (envelope-from ohartman@klima.physik.uni-mainz.de) Date: Sun, 8 Apr 2001 19:19:49 +0200 (CEST) From: "Hartmann, O." To: Subject: ALPHA Multia and FreeBSD 4.3-RC Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. I have here a digital Multia (Alpha 21066 at 233 MHz) and I want to get this box work under FreeBSD 4.3. I installed successfuly FreeBSD 4.3-RC2 as I got this ISO-Image and booted the Multia with the apropriate disks. I have two problems: First: I have no access to the console! I just see all the output when booting, after activating 'console' in /etc/ttys I get only a login prompt, but the keyboard is dead - only the LEDs for CapsLock etc. are flashing when hiting the apropriate key. All in- output go through the serial console and that is crap. Can anybody tell me how to activate the Multia's console? I read about that the console is not supported, but, excuse this question, makes it any kind of sense installing an operating system on a Multia I can not gain access to? Second: I tried to make a world. Due the fact the machine is really slow it took a long time from starting the first make world up to the point it failed. My Multia reboots spontanously and shows me the console, awaiting the boot command. I saw this many times on Intel based systems when CPU reaches its limits due overheating, overclocking or bad hardware. What's up with the Alpha? The machine has 88MB memory, that seems to be enough for simple steps in making a world or similar. The system is attached to a 4GB IBM SCSI DCAS hdd... -- MfG O. Hartmann ohartman@klima.physik.uni-mainz.de ---------------------------------------------------------------- IT-Administration des Institut fuer Physik der Atmosphaere (IPA) ---------------------------------------------------------------- Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinensaal) Tel: +496131/3924144 FAX: +496131/3923532 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 10:51: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id 197D437B423 for ; Sun, 8 Apr 2001 10:50:57 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from morpheus.kfu.com (morpheus.kfu.com [205.178.90.226]) by quack.kfu.com (8.11.1/8.11.1) with ESMTP id f38Houh90014; Sun, 8 Apr 2001 10:50:56 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from quack.kfu.com (localhost [127.0.0.1]) by morpheus.kfu.com (8.11.3/8.11.3) with ESMTP id f38HouG23328; Sun, 8 Apr 2001 10:50:56 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Message-ID: <3AD0A500.10201@quack.kfu.com> Date: Sun, 08 Apr 2001 10:50:56 -0700 From: Nick Sayer User-Agent: Mozilla/5.0 (X11; U; FreeBSD 4.3-RC i386; en-US; 0.8) Gecko/20010313 X-Accept-Language: en-GB, en-US, en MIME-Version: 1.0 Cc: Jamie Walker , Jan Mikkelsen , freebsd-stable@freebsd.org Subject: Re: Error dev/sound/pc/cmi.c during make buildkernel References: <00d901c0bffb$8042c590$0801a8c0@janm.transactionsite.com> <20010408194112.A1732@auckland.ac.nz> <3AD0447B.204AFA1A@urx.com> Content-Type: multipart/mixed; boundary="------------030405000106050601040106" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------030405000106050601040106 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Kent Stewart wrote: > > Jamie Walker wrote: > >> On Sun, Apr 08, 2001 at 05:14:07PM +1000, Jan Mikkelsen wrote: >> >> >>> /mnt/usr/src/sys/modules/sound/driver/cmi/../../../../dev/sound/pci/cmi. >>> c: In function `cmi_init': >>> /mnt/usr/src/sys/modules/sound/driver/cmi/../../../../dev/sound/pci/cmi. >>> c:747: `CMPCI_REG_N4SPK3D' undeclared (first use in this function) >>> /mnt/usr/src/sys/modules/sound/driver/cmi/../../../../dev/sound/pci/cmi. >>> c:747: (Each undeclared identifier is reported only once >>> /mnt/usr/src/sys/modules/sound/driver/cmi/../../../../dev/sound/pci/cmi. >>> c:747: for each function it appears in.) >>> >>> I cvsup'd about four hours ago, and I just cvsup'd again, with the same >>> problem. >> >> I'm getting the same error. I removed "device pcm" from my kernel >> configuration to no avail. >> >> > > > It is broken right now. If you want to fix it, look for an email from John > Capo. He has a patch to add > > + # define CMPCI_REG_N4SPK3D 0x04000000 > > to cmireg.h. > > Kent Attached is the correct patch. --------------030405000106050601040106 Content-Type: text/plain; name="p" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="p" Index: src/sys/dev/sound/pci/cmireg.h =================================================================== RCS file: /home/ncvs/src/sys/dev/sound/pci/cmireg.h,v retrieving revision 1.1.2.1 diff -u -r1.1.2.1 cmireg.h --- src/sys/dev/sound/pci/cmireg.h 2001/02/27 03:42:28 1.1.2.1 +++ src/sys/dev/sound/pci/cmireg.h 2001/04/08 17:48:38 @@ -114,6 +114,7 @@ #define CMPCI_REG_MISC 0x18 # define CMPCI_REG_POWER_DOWN 0x80000000 # define CMPCI_REG_BUS_AND_DSP_RESET 0x40000000 +# define CMPCI_REG_N4SPK3D 0x04000000 # define CMPCI_REG_W_SPDIF_48L 0x01000000 # define CMPCI_REG_SPDIF_48K 0x00008000 # define CMPCI_REG_FM_ENABLE 0x00080000 --------------030405000106050601040106-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 11:54:53 2001 Delivered-To: freebsd-stable@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 22DD537B424 for ; Sun, 8 Apr 2001 11:54:50 -0700 (PDT) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.11.1/8.11.1) with ESMTP id f38J2pC96390; Sun, 8 Apr 2001 15:02:51 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Sun, 8 Apr 2001 15:02:51 -0400 (EDT) From: "Brandon D. Valentine" To: "Hartmann, O." Cc: Subject: Re: ALPHA Multia and FreeBSD 4.3-RC In-Reply-To: Message-ID: <20010408143436.L96072-100000@turtle.looksharp.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 8 Apr 2001, Hartmann, O. wrote: >First: I have no access to the console! I just see all the output >when booting, after activating 'console' in /etc/ttys I get only >a login prompt, but the keyboard is dead - only the LEDs for CapsLock etc. >are flashing when hiting the apropriate key. All in- output go through >the serial console and that is crap. >Can anybody tell me how to activate the Multia's console? >I read about that the console is not supported, but, excuse this question, >makes it any kind of sense installing an operating system on a Multia >I can not gain access to? This probably belonged on -questions or -alpha, but here goes: FreeBSD currently supports only serial consoles on the Multia. This is because it uses an unsupported TGA framebuffer. You can either run with a serial console, or try putting a PCI VGA card in the PCI slot. I'm not sure the level of success people have had with that, but you can ask on the -alpha list to check. The other option is to run NetBSD which does support the TGA framebuffer. >Second: I tried to make a world. Due the fact the machine is really slow >it took a long time from starting the first make world up to the >point it failed. My Multia reboots spontanously and shows me the console, >awaiting the boot command. >I saw this many times on Intel based systems when CPU reaches its limits due >overheating, overclocking or bad hardware. What's up with the Alpha? >The machine has 88MB memory, that seems to be enough for simple steps >in making a world or similar. The system is attached to a 4GB IBM >SCSI DCAS hdd... This phenomenon is known as Multia Heat Death and is well known to Multia owners. The thing is not cooled well at all. Make sure it is standing on end at all times or the air will not circulate at all. It is meant to stand on end with the DEC logo/power switch toward the top. Most Multia's came with a stand to hold them there originally, but most of those stands have disappeared over time. Be careful with it. For more information on Multia Heat Death see the NetBSD/alpha Multia FAQ @ http://www.netbsd.org/Ports/alpha/multiafaq.html -- Brandon D. Valentine This message is encrypted with ROT-26. Any attempt to circumvent this encryption is expressly prohibited under 17 USC 512. Violators may be prosecuted. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 13:18:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id B7AF337B422 for ; Sun, 8 Apr 2001 13:18:12 -0700 (PDT) (envelope-from oberman@ptavv.es.net) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id f38KHuc18607; Sun, 8 Apr 2001 13:17:57 -0700 (PDT) Message-Id: <200104082017.f38KHuc18607@ptavv.es.net> To: Marko Cuk Cc: freebsd-stable@FreeBSD.ORG Subject: Re: OpenSSH & 4.3RC In-reply-to: Your message of "Sun, 08 Apr 2001 13:55:03 +0200." <3AD05197.BD21B88C@cuk.nu> Date: Sun, 08 Apr 2001 13:17:56 -0700 From: "Kevin Oberman" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think you are a bit confused. OpenSSH has been part of the base system since at least 4.1 and probably 4,0. You don't need to install it and installing the port tends to cause conflicts with the installed software. The port is there to allow V2 and V3 systems to add OpenSSH. IT should not be installed on a V4 system. Worse, the port is currently only at 2.2.0 while the base system includes the newer 2.3.0. Just make sure that you have installed the crypto stuff with your installation. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 > Date: Sun, 08 Apr 2001 13:55:03 +0200 > From: Marko Cuk > Sender: owner-freebsd-stable@FreeBSD.ORG > > Hello !! > > I have problems with installing OpenSSH on 4.3RC maschine even when I > cvsup ports and make buildworld. > Some libraries are not well. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 13:25:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with SMTP id 1CF8F37B422 for ; Sun, 8 Apr 2001 13:25:57 -0700 (PDT) (envelope-from jim@nasby.net) Received: (qmail 68312 invoked from network); 8 Apr 2001 20:25:56 -0000 Received: from unknown (HELO nasby.net) ([64.81.115.128]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 8 Apr 2001 20:25:56 -0000 Message-ID: <3AD0C953.B31494A9@nasby.net> Date: Sun, 08 Apr 2001 15:25:55 -0500 From: "Jim C. Nasby" Organization: distributed.net X-Mailer: Mozilla 4.72 [en] (WinNT; U) X-Accept-Language: en-US,en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Errors in /usr/src/sys/sys/socket.h in current RELENG_4 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Apologies if this is old news. This is from a cvsup of RELENG_4 that's less than an hour old. cc -O2 -pipe -Wall -DLIBC_SCCS -I/usr/src/lib/libutil -I/usr/src/lib/libutil/../../sys -DINET6 -c /usr/src/lib/libutil/logwtmp.c -o l ogwtmp.o In file included from /usr/src/lib/libutil/logwtmp.c:44: /usr/src/lib/libutil/../../sys/sys/socket.h:312: syntax error before `socklen_t' /usr/src/lib/libutil/../../sys/sys/socket.h:316: syntax error before `socklen_t' /usr/src/lib/libutil/../../sys/sys/socket.h:338: syntax error before `socklen_t' /usr/src/lib/libutil/../../sys/sys/socket.h:433: syntax error before `socklen_t' /usr/src/lib/libutil/../../sys/sys/socket.h:434: syntax error before `socklen_t' /usr/src/lib/libutil/../../sys/sys/socket.h:435: syntax error before `socklen_t' /usr/src/lib/libutil/../../sys/sys/socket.h:436: syntax error before `socklen_t' /usr/src/lib/libutil/../../sys/sys/socket.h:437: syntax error before `socklen_t' /usr/src/lib/libutil/../../sys/sys/socket.h:438: syntax error before `socklen_t' /usr/src/lib/libutil/../../sys/sys/socket.h:441: syntax error before `socklen_t' /usr/src/lib/libutil/../../sys/sys/socket.h:445: syntax error before `socklen_t' /usr/src/lib/libutil/../../sys/sys/socket.h:448: syntax error before `socklen_t' *** Error code 1 -- Jim C. Nasby (aka Decibel!) /^\ jim@nasby.net /___\ Freelance lighting designer and database developer / | \ Member: Triangle Fraternity, Sports Car Club of America /___|___\ Give your computer some brain candy! www.distributed.net Team #1828 Get paid to surf!! http://www.enteract.com/~nasby/alladvantage.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 13:42:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from head.lvl.ru (head.lvl.ru [194.67.189.100]) by hub.freebsd.org (Postfix) with ESMTP id 86C9937B423 for ; Sun, 8 Apr 2001 13:42:44 -0700 (PDT) (envelope-from jadream@chat.ru) Received: from chat.ru (p26.gw.lvl.ru [194.67.189.26]) by head.lvl.ru (8.11.2/8.11.2) with ESMTP id f38Kgmc01532 for ; Mon, 9 Apr 2001 00:42:48 +0400 (MSD) Message-ID: <3AD0CF8D.F02AB836@chat.ru> Date: Mon, 09 Apr 2001 00:52:29 +0400 From: alex X-Mailer: Mozilla 4.72 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: SysV msg queue strange behaviour Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ppl ! I have FreeBSD 4.2 on a common i386 pc with SysV IPC configured and recompiled kernel. Everything goes well untill I create more than 128 processes sending messages (24bytes in size) to the same queue at a time with flags = 0 (Blocking mode) and 1 process getting them all with flags = 0 (Blocking mode too). After queue size rises up to 70 -180 all processes hangs - both the ones that sends (what's naturally) and the one that gets (that's strange to my mind). Hence I have dead lock. With all this I have in my kernel config file options like that MSGMNI=64 MSGMAX=256 MSGMNB=2048*24 MSGTQL=2048 I used semaphores to block sending messages processes until receiver cleares whole queue and it all works but total performance go down dramatically :0( Any idea how to handle that? Alexander Komratov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 14:25:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail5.nc.rr.com (fe5.southeast.rr.com [24.93.67.52]) by hub.freebsd.org (Postfix) with ESMTP id 3AFFB37B424 for ; Sun, 8 Apr 2001 14:25:53 -0700 (PDT) (envelope-from helix@subedei.chaotical.ly) Received: from subedei.chaotical.ly ([66.26.231.27]) by mail5.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Sun, 8 Apr 2001 15:13:06 -0400 Received: by subedei.chaotical.ly (Postfix, from userid 10001) id 6227FB050A; Sun, 8 Apr 2001 15:10:28 -0400 (EDT) Date: Sun, 8 Apr 2001 15:10:28 -0400 From: thomas r stromberg To: Gert-Jan Vons Cc: freebsd-stable@freebsd.org, ipfilter@coombs.anu.edu.au Subject: Broken rc.network for ipfilter w/ PR (was Re: How to install ipfilter..) Message-ID: <20010408151025.A34209@rtci.com> References: <5.1.0.12.2.20010407230631.00a688c0@mail.vons.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.16i In-Reply-To: <5.1.0.12.2.20010407230631.00a688c0@mail.vons.local>; from vons@iname.com on Sun, Apr 08, 2001 at 11:13:58AM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I added the four commands above to /etc/rc.network instead of using > FreeBSD's ipfilter support through rc.conf mechanism (it assumes that > ipfilter is built into the kernel) There is a PR with a patch sitting on this rc.network fuckup (oversight) that I'd really love to see committed for 4.3-RELEASE, but who knows if that's possible with the given timeline. http://www.freebsd.org/cgi/query-pr.cgi?pr=26275 I completely missed a previous PR on the same issue, but this one has a patch that will work no matter where $ipfilter_program is set to (hack), rather then hardcoding an ipfstat location. Patch also fixes it so that ipf.rules doesn't have to exist if your just setting up a NAT. This issue has been a pain in the ass when helping people setup ipnat.. so much so I actually recommend people to patch this on the bsdwiki entry: http://profile.sh/bsdwiki/index.php?Sharing%20your%20internet%20connection%20via%20ipnat -- : Thomas Stromberg work> tstromberg@rtci.com : : Research Triangle Commerce (ICC.net) home> thomas@stromberg.org : 'Every word is like an unnecessary stain on silence and nothingness' -- Beckett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 15: 9:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from johnson.mail.mindspring.net (johnson.mail.mindspring.net [207.69.200.177]) by hub.freebsd.org (Postfix) with ESMTP id 2E94237B422 for ; Sun, 8 Apr 2001 15:09:09 -0700 (PDT) (envelope-from mvh@ix.netcom.com) Received: from netcom1.netcom.com (lai-ca3c-113.ix.netcom.com [209.110.242.113]) by johnson.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id SAA29523; Sun, 8 Apr 2001 18:08:58 -0400 (EDT) Received: by netcom1.netcom.com (Postfix, from userid 1000) id A7023113B1E; Sun, 8 Apr 2001 15:08:41 -0700 (PDT) From: Mike Harding To: l.ipfilter@rtci.com Cc: vons@iname.com, freebsd-stable@freebsd.org, ipfilter@coombs.anu.edu.au In-reply-to: <20010408151025.A34209@rtci.com> (message from thomas r stromberg on Sun, 8 Apr 2001 15:10:28 -0400) Subject: Re: Broken rc.network for ipfilter w/ PR (was Re: How to install ipfilter..) References: <5.1.0.12.2.20010407230631.00a688c0@mail.vons.local> <20010408151025.A34209@rtci.com> Message-Id: <20010408220841.A7023113B1E@netcom1.netcom.com> Date: Sun, 8 Apr 2001 15:08:41 -0700 (PDT) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Also, if you use a dialup line, and dial-on-demand, as I do, 'ipf -y' is not called after the dynamic interfaces are set up, and you can have a filterless box, as the interface does not exist when the rules are set. Note that ppp is setup before ipfw and so ipfw and ipnat do not have this problem. - Mike H. Date: Sun, 8 Apr 2001 15:10:28 -0400 From: thomas r stromberg Cc: freebsd-stable@freebsd.org, ipfilter@coombs.anu.edu.au Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.16i Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.ORG Precedence: bulk > I added the four commands above to /etc/rc.network instead of using > FreeBSD's ipfilter support through rc.conf mechanism (it assumes that > ipfilter is built into the kernel) There is a PR with a patch sitting on this rc.network fuckup (oversight) that I'd really love to see committed for 4.3-RELEASE, but who knows if that's possible with the given timeline. http://www.freebsd.org/cgi/query-pr.cgi?pr=26275 I completely missed a previous PR on the same issue, but this one has a patch that will work no matter where $ipfilter_program is set to (hack), rather then hardcoding an ipfstat location. Patch also fixes it so that ipf.rules doesn't have to exist if your just setting up a NAT. This issue has been a pain in the ass when helping people setup ipnat.. so much so I actually recommend people to patch this on the bsdwiki entry: http://profile.sh/bsdwiki/index.php?Sharing%20your%20internet%20connection%20via%20ipnat -- : Thomas Stromberg work> tstromberg@rtci.com : : Research Triangle Commerce (ICC.net) home> thomas@stromberg.org : 'Every word is like an unnecessary stain on silence and nothingness' -- Beckett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 16:12:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nanguo.chalmers.com.au (gateway.chalmers.com.au [203.1.96.1]) by hub.freebsd.org (Postfix) with ESMTP id C2E7637B422 for ; Sun, 8 Apr 2001 16:12:29 -0700 (PDT) (envelope-from robert@chalmers.com.au) Received: from carbon (carbon.chalmers.com.au [203.1.96.26]) by nanguo.chalmers.com.au (8.11.0/8.11.0) with SMTP id f38NEBU08726 for ; Mon, 9 Apr 2001 09:14:12 +1000 (EST) From: "Robert" To: "FreeBSD" Subject: What are the current tags for 4 ? Date: Mon, 9 Apr 2001 09:15:45 +1000 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.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG www.polstra.com talks about doing this to match the lists porperly. what tags are current for 4.3-RC ? to achieve the same thing. tag=RELENG_4 for the "STABLE" branch, but what does one use now for the RELENG_xxxxxx_RELEASE Thanks Robert This is a little tricky and there are a couple of important details we haven't mentioned yet. So we'd better give you an example. Suppose you installed FreeBSD-2.2.5, including sources, from the CD-ROM. Now you decide you want to use CVSup to track the 2.2-stable sources. For your first update only, use a cvsupfile like this: *default host=cvsup2.freebsd.org *default base=/usr *default prefix=/usr *default release=cvs *default delete use-rel-suffix src-all tag=RELENG_2_2_5_RELEASE list=cvs:RELENG_2_2 For subsequent updates, change the last line to: src-all tag=RELENG_2_2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 16:18:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.cruzio.com (dsl3i239.cruzio.com [205.179.211.239]) by hub.freebsd.org (Postfix) with ESMTP id EEE3837B423 for ; Sun, 8 Apr 2001 16:18:14 -0700 (PDT) (envelope-from brucem@mail.cruzio.com) Received: (from brucem@localhost) by mail.cruzio.com (8.11.3/8.11.3) id f38N79Y00821 for stable@FreeBSD.ORG; Sun, 8 Apr 2001 16:07:09 -0700 (PDT) (envelope-from brucem) Date: Sun, 8 Apr 2001 16:07:09 -0700 (PDT) From: "Bruce R. MontagueBrucem" Message-Id: <200104082307.f38N79Y00821@mail.cruzio.com> To: stable@FreeBSD.ORG Subject: unsubscribe Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe freebsd-stable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 16:19:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nanguo.chalmers.com.au (gateway.chalmers.com.au [203.1.96.1]) by hub.freebsd.org (Postfix) with ESMTP id BAAAF37B423 for ; Sun, 8 Apr 2001 16:19:13 -0700 (PDT) (envelope-from robert@chalmers.com.au) Received: from carbon (carbon.chalmers.com.au [203.1.96.26]) by nanguo.chalmers.com.au (8.11.0/8.11.0) with SMTP id f38NKtU08789 for ; Mon, 9 Apr 2001 09:20:55 +1000 (EST) From: "Robert" To: "FreeBSD" Subject: Further to cvsup tags... actually need ports-audio for 4.3-RC . Date: Mon, 9 Apr 2001 09:22:30 +1000 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.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm actually trying to get the ports-audio collection ... The existing one tells me that the layout is wrong ? I'm running 4.3-RC currently. Thanks Robert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 16:51:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from c007.snv.cp.net (c007-h000.c007.snv.cp.net [209.228.33.206]) by hub.freebsd.org (Postfix) with SMTP id EF5D837B424 for ; Sun, 8 Apr 2001 16:51:01 -0700 (PDT) (envelope-from otterr@telocity.com) Received: (cpmta 26437 invoked from network); 8 Apr 2001 16:28:31 -0700 Received: from dsl-216-227-91-85.telocity.com (HELO zoso) (216.227.91.85) by smtp.telocity.com (209.228.33.206) with SMTP; 8 Apr 2001 16:28:31 -0700 X-Sent: 8 Apr 2001 23:28:31 GMT From: "Otter" To: "'Robert'" , "'FreeBSD'" Subject: RE: Further to cvsup tags... actually need ports-audio for 4.3-RC . Date: Sun, 8 Apr 2001 19:20:25 -0400 Message-ID: <000f01c0c082$7e8a53d0$1401a8c0@zoso> 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 CWS, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That's your ports tree. If it's wrong, just rm -rf /usr/ports/* (or whatever your ports dir is) and just cvsup again. This will restore the tree to what it should be. -Otter > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Robert > Sent: Sunday, April 08, 2001 7:23 PM > To: FreeBSD > Subject: Further to cvsup tags... actually need ports-audio > for 4.3-RC . > > > I'm actually trying to get the ports-audio collection ... The > existing one > tells me that the layout is wrong ? > > I'm running 4.3-RC currently. > > Thanks > Robert > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 18:12:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gw-us4.philips.com (gw-us4.philips.com [63.114.235.90]) by hub.freebsd.org (Postfix) with ESMTP id 5DBAE37B422 for ; Sun, 8 Apr 2001 18:12:16 -0700 (PDT) (envelope-from founder.fang@philips.com) Received: from smtprelay-hk1.philips.com (localhost.philips.com [127.0.0.1]) by gw-us4.philips.com with ESMTP id UAA05461; Sun, 8 Apr 2001 20:11:58 -0500 (CDT) (envelope-from founder.fang@philips.com) From: founder.fang@philips.com Received: from smtprelay-asp1.philips.com(130.147.65.5) by gw-us4.philips.com via mwrap (4.0a) id xma005458; Sun, 8 Apr 01 20:11:59 -0500 Received: from APLMS01.DIAMOND.PHILIPS.COM (aplms01sv1.diamond.philips.com [130.147.79.213]) by smtprelay-hk1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id JAA22817; Mon, 9 Apr 2001 09:11:56 +0800 (HKT) Received: by APLMS01.DIAMOND.PHILIPS.COM (Soft-Switch LMS 4.0) with snapi via APAC id 0056920010481429; Mon, 9 Apr 2001 09:11:56 +0800 To: , Subject: Re: my i810 card doesn't work Message-ID: <0056920010481429000002L292*@MHS> Date: Mon, 9 Apr 2001 09:11:56 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; name="MEMO 04/09/01 09:10:07" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i am using 4.2-release,the default installation is XFree86 3.3.x,how ca= n i install 4.0.1 in my box?the following is my dmesg.is it the version you specified? BTW,is there several version for 4.2 release?whether the release versio= n is a stable version?am i use a stable version? i have another box running 3.4,the dmesg in it was "FreeBSD 3.4-STABLE"= ,so i feel confused. what's the difference between STABLE and RELEASE?=20 my dmesg: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 199= 4 The Regents of the University of California. All rights reserved. FreeBSD 4.2-RELEASE #3: Thu Apr 5 00:37:17 CST 2001 >The i810 is a piece of trash... I know this because I use one. Since i= t >is supported in XFree86 4.x only on Linux at this time, you are >restricted to XFree86 4.0.1 on FreeBSD, since this version has >patchfiles which correct the AGP code. In 4.0.2, the driver was totall= y >restructured, and the port maintainer has removed the old patchfiles. >Consequently, while the i810 will work in 4.0.2-4.0.3, switching >consoles and then switching back will crash your X server, and it won'= t >work properly until you reboot. >If you want a fully-functional XFree86 install for your FreeBSD box, >find an old copy of the ports tree (the one in 4.2-RELEASE works fine)= >with XFree86 4.0.1, and build it from there. Downloading the source fr= om >xfree86.org will not work, unless you intend to fix the i810 driver. >One more thing... XF86Setup is 3.3.x-only. You need to either write th= e >config file by hand, or use xf86config to build a skeleton for you. >I imagine that the generic SVGA server will work for the i810, but >somehow, dual-head at 640x480x8bpp per screen seems a little pointless= . -- >Andrew Hesford >ajh3@chmod.ath.cx = To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 18:16:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id D84CC37B423 for ; Sun, 8 Apr 2001 18:16:44 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([fec0::2e0:7dff:fe81:749d]) by scientia.demon.co.uk with esmtp (Exim 3.22 #1) id 14mQIN-000GUQ-00; Mon, 09 Apr 2001 02:16:43 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.11.3/8.11.3) id f391Gg886086; Mon, 9 Apr 2001 02:16:42 +0100 (BST) (envelope-from ben) Date: Mon, 9 Apr 2001 02:16:42 +0100 From: Ben Smithurst To: Robert Cc: FreeBSD Subject: Re: What are the current tags for 4 ? Message-ID: <20010409021642.C78569@scientia.demon.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert wrote: > www.polstra.com talks about doing this to match the lists porperly. > > what tags are current for 4.3-RC ? to achieve the same thing. > > tag=RELENG_4 for the "STABLE" branch, but what does one use now for the > RELENG_xxxxxx_RELEASE 4.3-RC *is* the stable (RELENG_4) branch at the moment, it doesn't have a separate tag or branch tag. 4.3-RELEASE will of course be RELENG_4_3_0_RELEASE, when it is released. -- Ben Smithurst / ben@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 18:48:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [202.53.40.210]) by hub.freebsd.org (Postfix) with ESMTP id 1CE3737B423 for ; Sun, 8 Apr 2001 18:48:52 -0700 (PDT) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id LAA07752; Mon, 9 Apr 2001 11:48:49 +1000 (EST) (envelope-from gnb@itga.com.au) Received: from itga.com.au (lightning.itga.com.au [192.168.71.20]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id LAA02182; Mon, 9 Apr 2001 11:48:49 +1000 (EST) Message-Id: <200104090148.LAA02182@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: "Robert" Cc: "FreeBSD" Subject: Re: Sorry, but this 4.3 box has me totally stumped. It simply won't gateway the PPP link. FULL details of setups. In-reply-to: Your message of Sat, 07 Apr 2001 08:53:39 +1000. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Apr 2001 11:48:49 +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 1) enable proxy arp in the ppp config 2) make sure ip forwarding is on for the ppp server. (Hmm, is this needed for proxy arp? I think so!) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 18:55: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [202.53.40.210]) by hub.freebsd.org (Postfix) with ESMTP id ED39737B423 for ; Sun, 8 Apr 2001 18:55:01 -0700 (PDT) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id LAA07797; Mon, 9 Apr 2001 11:54:59 +1000 (EST) (envelope-from gnb@itga.com.au) Received: from itga.com.au (lightning.itga.com.au [192.168.71.20]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id LAA02651; Mon, 9 Apr 2001 11:54:57 +1000 (EST) Message-Id: <200104090154.LAA02651@lightning.itga.com.au> From: Gregory Bond To: Mike Meyer Cc: The Babbler , Rasputin , stable@FreeBSD.ORG, gnb@itga.com.au Subject: Re: Disklabel 101? In-reply-to: Your message of Sat, 07 Apr 2001 04:48:43 -0500. Date: Mon, 09 Apr 2001 11:54:57 +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If memory serves, partition table information used to be in the kernel > - wired into the driver for that disk - so all disks of the same type > had to have the same partition table. This was true upto and including V7, but not true in 4.2. I'm not sure where in the seqence from V7 -> Sys32 -> 4.1 -> 4.2 that pack-resident labels appeared. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 19:31:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nova.fnal.gov (nova.fnal.gov [131.225.121.207]) by hub.freebsd.org (Postfix) with ESMTP id B7DC437B42C for ; Sun, 8 Apr 2001 19:31:53 -0700 (PDT) (envelope-from zingelman@fnal.gov) Received: from localhost (tez@localhost) by nova.fnal.gov (8.9.3+Sun/8.9.3) with ESMTP id VAA01059 for ; Sun, 8 Apr 2001 21:31:47 -0500 (CDT) X-Authentication-Warning: nova.fnal.gov: tez owned process doing -bs Date: Sun, 8 Apr 2001 21:31:47 -0500 (CDT) From: Tim Zingelman X-Sender: To: Subject: make release broken with too many ports/distfiles... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On a system with all (or most of) the distfiles existing in /usr/ports/distfiles, line 680 of: $FreeBSD: src/release/Makefile,v 1.536.2.40 2000/03/27 16:49:58 @-rm -rf /usr/ports/distfiles/* fails to cleanup the duplicated distfiles directory, due to: "Argument list too long", and as a result the ports tarball includes the whole set of distfiles. (and that won't fit on a cdrom :) Just for reference... # cd /usr/ports/distfiles # ls * /bin/ls: Argument list too long. # echo * | wc -c 83575 # Here's a trivial patch: diff -w -u -b -r1.536.2.40 Makefile --- Makefile 2001/03/27 16:49:58 1.536.2.40 +++ Makefile 2001/04/09 02:21:47 @@ -677,7 +677,8 @@ @ln -f ${CD_DISC1}/kernel ${CD_DISC2}/kernel .endif .if !defined(NOPORTS) - @-rm -rf /usr/ports/distfiles/* + @-rm -rf /usr/ports/distfiles + @-mkdir /usr/ports/distfiles @mkdir -p ${CD_DISC1}/ports && \ tar --exclude CVS -czf ${CD_DISC1}/ports/ports.tgz -C /usr ports && \ cp ${.CURDIR}/scripts/ports-install.sh ${CD_DISC1}/ports/install.sh \ I just started a make release, with this patch in place. I'll reply to this email only if it does not solve the problem as I expect it to. Tim Zingelman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 19:50:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.unixathome.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id C001237B42C for ; Sun, 8 Apr 2001 19:50:38 -0700 (PDT) (envelope-from dan@langille.org) Received: from wocker (root@ns1.unixathome.org [192.168.0.20]) by ns1.unixathome.org (8.11.3/8.11.3) with ESMTP id f392oWe66294 for ; Mon, 9 Apr 2001 14:50:36 +1200 (NZST) (envelope-from dan@langille.org) Message-Id: <200104090250.f392oWe66294@ns1.unixathome.org> From: "Dan Langille" Organization: novice in training To: "'FreeBSD'" Date: Sun, 8 Apr 2001 22:50:30 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: RE: Further to cvsup tags... actually need ports-audio for 4.3-RC . Reply-To: dan@langille.org In-reply-to: <000f01c0c082$7e8a53d0$1401a8c0@zoso> References: X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is such a *huge* waste of bandwidth. I do wish we could solve this problem. It's occurring time after time. Ideally, we could come up with a simple script which cleans things up. On 8 Apr 2001, at 19:20, Otter wrote: > That's your ports tree. If it's wrong, just rm -rf /usr/ports/* (or > whatever your ports dir is) and just cvsup again. This will restore > the tree to what it should be. > -Otter > > > > -----Original Message----- > > From: owner-freebsd-stable@FreeBSD.ORG > > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Robert > > Sent: Sunday, April 08, 2001 7:23 PM > > To: FreeBSD > > Subject: Further to cvsup tags... actually need ports-audio > > for 4.3-RC . > > > > > > I'm actually trying to get the ports-audio collection ... The > > existing one > > tells me that the layout is wrong ? > > > > I'm running 4.3-RC currently. > > > > Thanks > > Robert > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- Dan Langille pgpkey - finger dan@unixathome.org | http://unixathome.org/finger.php got any work? I'm looking for some. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 20:23: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 0095637B422 for ; Sun, 8 Apr 2001 20:23:01 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f393N0x05916; Sun, 8 Apr 2001 20:23:00 -0700 (PDT) Date: Sun, 8 Apr 2001 20:23:00 -0700 From: Alfred Perlstein To: Tim Zingelman Cc: freebsd-stable@FreeBSD.ORG Subject: Re: make release broken with too many ports/distfiles... Message-ID: <20010408202300.J15938@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from zingelman@fnal.gov on Sun, Apr 08, 2001 at 09:31:47PM -0500 X-all-your-base: are belong to us. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Tim Zingelman [010408 19:32] wrote: > On a system with all (or most of) the distfiles existing in > /usr/ports/distfiles, line 680 of: > > $FreeBSD: src/release/Makefile,v 1.536.2.40 2000/03/27 16:49:58 > > @-rm -rf /usr/ports/distfiles/* > > fails to cleanup the duplicated distfiles directory, due to: "Argument > list too long", and as a result the ports tarball includes the whole set > of distfiles. (and that won't fit on a cdrom :) > > Just for reference... > # cd /usr/ports/distfiles > # ls * > /bin/ls: Argument list too long. > # echo * | wc -c > 83575 > # ha! :) > > Here's a trivial patch: Please provide more context, which makefile is this patch to be applied against? > > diff -w -u -b -r1.536.2.40 Makefile > --- Makefile 2001/03/27 16:49:58 1.536.2.40 > +++ Makefile 2001/04/09 02:21:47 > @@ -677,7 +677,8 @@ > @ln -f ${CD_DISC1}/kernel ${CD_DISC2}/kernel > .endif > .if !defined(NOPORTS) > - @-rm -rf /usr/ports/distfiles/* > + @-rm -rf /usr/ports/distfiles > + @-mkdir /usr/ports/distfiles > @mkdir -p ${CD_DISC1}/ports && \ > tar --exclude CVS -czf ${CD_DISC1}/ports/ports.tgz -C /usr ports && \ > cp ${.CURDIR}/scripts/ports-install.sh ${CD_DISC1}/ports/install.sh \ > > > I just started a make release, with this patch in place. I'll reply to > this email only if it does not solve the problem as I expect it to. What if ports/distfiles is a symlink? Or is this only done during make release? How about something like this: find /usr/ports/distfiles/ -mindepth 1 | xargs rm -rf ? -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Represent yourself, show up at BABUG http://www.babug.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 20:38:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nova.fnal.gov (nova.fnal.gov [131.225.121.207]) by hub.freebsd.org (Postfix) with ESMTP id BC65C37B424 for ; Sun, 8 Apr 2001 20:38:42 -0700 (PDT) (envelope-from zingelman@fnal.gov) Received: from localhost (tez@localhost) by nova.fnal.gov (8.9.3+Sun/8.9.3) with ESMTP id WAA01254 for ; Sun, 8 Apr 2001 22:38:37 -0500 (CDT) X-Authentication-Warning: nova.fnal.gov: tez owned process doing -bs Date: Sun, 8 Apr 2001 22:38:37 -0500 (CDT) From: Tim Zingelman X-Sender: To: Subject: Re: make release broken with too many ports/distfiles... In-Reply-To: <20010408202300.J15938@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 8 Apr 2001, Alfred Perlstein wrote: > > $FreeBSD: src/release/Makefile,v 1.536.2.40 2000/03/27 16:49:58 > Please provide more context, which makefile is this patch to be > applied against? See above... it is /usr/src/release/Makefile from 4.3-RC. > What if ports/distfiles is a symlink? Or is this only done during > make release? Yes, only during 'make release'. If I am reading things correctly, this is in a 'chroot ${CHROOTDIR}' environment. - Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 20:48:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id C835D37B423 for ; Sun, 8 Apr 2001 20:48:48 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f393mmm06531; Sun, 8 Apr 2001 20:48:48 -0700 (PDT) Date: Sun, 8 Apr 2001 20:48:48 -0700 From: Alfred Perlstein To: Tim Zingelman Cc: freebsd-stable@FreeBSD.ORG Subject: Re: make release broken with too many ports/distfiles... Message-ID: <20010408204848.L15938@fw.wintelcom.net> References: <20010408202300.J15938@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from zingelman@fnal.gov on Sun, Apr 08, 2001 at 10:38:37PM -0500 X-all-your-base: are belong to us. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Tim Zingelman [010408 20:39] wrote: > On Sun, 8 Apr 2001, Alfred Perlstein wrote: > > > > $FreeBSD: src/release/Makefile,v 1.536.2.40 2000/03/27 16:49:58 > > > Please provide more context, which makefile is this patch to be > > applied against? > > See above... it is /usr/src/release/Makefile from 4.3-RC. > > > What if ports/distfiles is a symlink? Or is this only done during > > make release? > > Yes, only during 'make release'. If I am reading things correctly, this > is in a 'chroot ${CHROOTDIR}' environment. You'll want to fling this at Jordan , he's the release engineer. :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 23:12: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pop3.psconsult.nl (ps226.psconsult.nl [193.67.147.226]) by hub.freebsd.org (Postfix) with ESMTP id B758037B423 for ; Sun, 8 Apr 2001 23:12:00 -0700 (PDT) (envelope-from paul@pop3.psconsult.nl) Received: (from paul@localhost) by pop3.psconsult.nl (8.9.2/8.9.2) id IAA58952; Mon, 9 Apr 2001 08:11:46 +0200 (CEST) (envelope-from paul) Date: Mon, 9 Apr 2001 08:11:46 +0200 From: Paul Schenkeveld To: Makoto MATSUSHITA Cc: paul@psconsult.nl, stable@FreeBSD.ORG Subject: Re: make relase stops at missing sysinstall Message-ID: <20010409081146.A58878@psconsult.nl> References: <20010408113410.A42640@psconsult.nl> <20010409003752F.matusita@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20010409003752F.matusita@jp.FreeBSD.org>; from matusita@jp.FreeBSD.org on Mon, Apr 09, 2001 at 12:37:52AM +0900 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks Makoto! That was it! I seem to have assumed that the CVS tag was sticky but forgot that the first thing make release does is remove the complete chroot tree, including the CVS/Tag files. Got my make release now working just in time for the coming 4.3 release (CD-roms usually arrive slowly here in The Netherlands) and make my customers happy again. Regards, Paul Schenkeveld On Mon, Apr 09, 2001 at 12:37:52AM +0900, Makoto MATSUSHITA wrote: > > paul> make release \ > paul> BINFORMAT=elf \ > paul> NODOC=YES \ > paul> NOPORTS=YES \ > paul> BUILDNAME=4.3-SNAP-`date +%Y%m%d` \ > paul> CHROOTDIR=/usr/release/snap > > You forget to add 'RELEASETAG'. See src/release/Makefile. > > -- - > Makoto `MAR' MATSUSHITA > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 8 23:27:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from montgomery.accessunited.com.au (montgomery.accessunited.com.au [203.46.135.133]) by hub.freebsd.org (Postfix) with ESMTP id 9470337B424 for ; Sun, 8 Apr 2001 23:27:47 -0700 (PDT) (envelope-from phillip@accessunited.com.au) Received: from willie.accessunited.com.au (ernally-@willie.accessunited.com.au [203.46.135.139]) by montgomery.accessunited.com.au (8.10.1/8.10.1) with SMTP id f396Ris29050 for ; Mon, 9 Apr 2001 16:27:44 +1000 (EST) Message-Id: <200104090627.f396Ris29050@montgomery.accessunited.com.au> From: "Phillip" To: "freebsd-stable@FreeBSD.ORG" Date: Mon, 09 Apr 2001 16:27:52 +1100 (EDT) Reply-To: "Phillip" X-Mailer: PMMail 2.00.1500 for OS/2 Warp 4.05 In-Reply-To: <3AD0A500.10201@quack.kfu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Error dev/sound/pc/cmi.c during make buildkernel Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hearty appreciation to Nick and Joachim for their help. I also note that with cvsupping afresh (about 6 ?? hours ago) that the problem is also fixed in the src. Many thanks to everyone for a very speedy and effective resolution. Cheers Phillip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 0:33:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nsl.nts.nnov.ru (nsl.nts.nnov.ru [194.84.212.22]) by hub.freebsd.org (Postfix) with ESMTP id A525137B42C for ; Mon, 9 Apr 2001 00:33:53 -0700 (PDT) (envelope-from shooter@zoctober.ru) Received: from shooter.mcc (cs3-a18.nts.nnov.ru [195.151.72.146]) by nsl.nts.nnov.ru (8.11.1/8.9.3) with ESMTP id f397Xjh18656 for ; Mon, 9 Apr 2001 11:33:46 +0400 Date: Mon, 9 Apr 2001 11:32:14 +0400 From: =?koi8-r?B?4czFy9PFyiD3LiD2yczYw8/X?= X-Mailer: The Bat! (v1.51) Personal Reply-To: =?koi8-r?B?4czFy9PFyiD3LiD2yczYw8/X?= Organization: =?koi8-r?B?7+HvICLuydbFx8/Sz8TTy8nKINrB18/EICLv6/Tx4vL4Ig==?= X-Priority: 3 (Normal) Message-ID: <1425031625.20010409113214@zoctober.ru> To: freebsd-stable@FreeBSD.org Subject: help MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 help -----BEGIN PGP SIGNATURE----- Version: PGP 6.5i iQA/AwUBOtE7WlS/zSSJZuf3EQKu3ACbBkjLXbpPOVzXa1U/HmvT6g01xo0AnRid BuTR+nnnUtMd/DZdnsT7eIgm =47tV -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 3: 0:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mfo01.iij.ad.jp (mfo01.iij.ad.jp [202.232.2.118]) by hub.freebsd.org (Postfix) with ESMTP id E6D4037B423 for ; Mon, 9 Apr 2001 03:00:11 -0700 (PDT) (envelope-from ok@pp.iij4u.or.jp) Received: from pp.iij4u.or.jp (pp.iij4u.or.jp [210.130.0.40]) by mfo01.iij.ad.jp (8.8.8/MFO1.3) with ESMTP id TAA10853 for ; Mon, 9 Apr 2001 19:00:10 +0900 (JST) Received: from [192.168.168.1] (h055.p487.iij4u.or.jp [210.149.231.55]) by pp.iij4u.or.jp (8.8.8+2.2IIJ/4U1.1) with SMTP id TAA01551 for ; Mon, 9 Apr 2001 19:00:10 +0900 (JST) Message-Id: <200104091000.TAA01551@pp.iij4u.or.jp> X-Mailer: Macintosh Eudora Pro Version 3.0.2J Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-2022-JP" Date: Mon, 9 Apr 2001 19:00:09 +0900 To: stable@FreeBSD.org From: Hirofumi Okuyama Subject: high maxusers value leads panic Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On FreeBSD 4.3-R2, a kernel configuration file with a line: maxusers 2500 generates a bad kernel, which says on boot: panic: swap_pager_swap_init: swap_zone == NULL syncing disks ... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up on 1 buffers On FreeBSD 4.2-RELEASE, specifying this high value makes no problem. Regards Hirofumi Okuyama To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 3:22:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dilbert.fcg.co.uk (dilbert.firstcallgroup.co.uk [194.203.69.166]) by hub.freebsd.org (Postfix) with ESMTP id 6D30A37B422 for ; Mon, 9 Apr 2001 03:22:39 -0700 (PDT) (envelope-from pfrench@firstcallgroup.co.uk) Received: from pfrench by dilbert.fcg.co.uk with local (Exim 3.22 #1) id 14mYoZ-0006LJ-00; Mon, 09 Apr 2001 11:22:31 +0100 To: mike@dad.state.vt.us, mwm@mired.org Subject: Re: Disklabel 101? Cc: stable@freebsd.org In-Reply-To: <15055.61547.661230.147704@guru.mired.org> Message-Id: From: Pete French Date: Mon, 09 Apr 2001 11:22:31 +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Barton types: > > Are there any issues with placing swap first on the hard drive? Unless you > > insist on filling the drive, it seems to me that this swap arrangement would > > result in less stack travel. > > Not that I know of. In fact, I'm pretty sure that one of my systems > has root on s2, with swap on s1, which is earlier on the hard disk. It doesnt work on the same disc however. Try and do an install of 4.2 creating a swap partition, then a root partition and it fails. Or always has in my expereince anyway. Its a bit of a nasty gotcha actually because it is not obvious what the problem is. I can see that it probably makes sense to have root frst then sawp (and they become a and b) so I dont do it that way anymore, but its still worth knowing about. The order of separate discs is not a problem. We have a Compaq server that insists on booting from da1 rather than da0, so I have / on da1, /usr on da0 and an interleved swap between them. Even in this case, however, I found it necessary to put the filesystems first on each disc, followed by the swap partitions. -pete. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 3:59:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id 1F99437B42C for ; Mon, 9 Apr 2001 03:59:17 -0700 (PDT) (envelope-from rasputin@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by probity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14mZO5-000FF2-00; Mon, 9 Apr 2001 11:59:13 +0100 Received: (from rasputin@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f39AxA220869; Mon, 9 Apr 2001 11:59:10 +0100 (BST) (envelope-from rasputin) Date: Mon, 9 Apr 2001 11:59:10 +0100 From: Rasputin To: The Babbler Cc: stable@freebsd.org Subject: Re: Disklabel 101? Message-ID: <20010409115910.B20710@dogma.freebsd-uk.eu.org> Reply-To: Rasputin References: <20010405111707.A35325@dogma.freebsd-uk.eu.org> <3ACE972D.A13CF44C@babbleon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3ACE972D.A13CF44C@babbleon.org>; from bts@babbleon.org on Sat, Apr 07, 2001 at 12:27:26AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * The Babbler [010407 05:32]: > Rasputin wrote: > > <-----EXTENDED-----><------PHYSICAL------------> > > ad0s1 ad0s5 ad0s6 ad0s3 > > <-winXX--><-msdos-><-------BSD----------------> > > | 2Gb | 1.5Gb | 2Gb | / | swap | /usr | /var | > > ^ > > | > > old FUBARed Slackware partition > > It's in the second logical partition in an extended DOS partition on > > my second physical partition (dev/ad0s6 in FreeBSD) > > There's a Gb of data in ad0s5 (which is fine). > > FreeBSD doesn't know extended partitions from what I can see. Does > your FreeBSD actually see ad0s5/ad0s6? 'Cause mine never seemed to > found; I used PartitionMagic to convert my DOS partition from logical to > primary largely to deal with this. I can read ad0s5 OK, except I get some wierd errors when lookng at files. I was trying to back up my w95 profile from ad0s5 to a zip drive, and ls seems to die in strange and wondorus ways e.g. (/extra is where /dev/ad0s5 is mounted) /extra/w96bak/netscape-profiles/rasputin/ holds my w95 netscape profile. trying to CD into it fails, 'not a directory' du -ksc /extra also falls over with read errors. I assumed it was because ad0s6 was screwed, so didn't think any more of it. Does anyone else have problems reading DOS extended partitions? I'd send a pr for this, but don't want to so close to a RELEASE unless it's seen by others. > Anyway, as far as *I* am aware what you've really got is: > > ad0s1 - first partition = winXx > ad0s2 - second partiion = extended > ad0s3 = third partition = BSD Check. Although the plan is to steal some space from ad0s2 for ad0s1 (half-life....drool....) and then reformat what's left into another BSD parttion for /usr/src (hence the stoopid disklabel question) > (And what release are you running, BTW?) 4.3-RC (The One With The B0rken PCM Header) -- Rasputin Jack of All Trades :: Master of Nuns To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 4:10:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebsd.org.ru (sweet.etrust.ru [194.84.67.5]) by hub.freebsd.org (Postfix) with ESMTP id 87B1A37B61A for ; Mon, 9 Apr 2001 04:10:21 -0700 (PDT) (envelope-from osa@freebsd.org.ru) Received: by freebsd.org.ru (Postfix, from userid 1000) id 3F2F9246; Mon, 9 Apr 2001 15:10:17 +0400 (MSD) Date: Mon, 9 Apr 2001 15:10:17 +0400 From: "Sergey A. Osokin" To: bjoern@loenneker.com Cc: stable@FreeBSD.ORG Subject: Re: HPT366 problems Message-ID: <20010409151016.A75461@freebsd.org.ru> References: <3ACFDF76.62E58A15@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3ACFDF76.62E58A15@acm.org>; from ktsin@acm.org on Sun, Apr 08, 2001 at 11:48:06AM +0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 08, 2001 at 11:48:06AM +0800, KT Sin wrote: > I have the same problem too. Let me guess, your disk is an IBM DTLA > (ATA100). I believe this is due to incompatibility between HPT366 and IBM's > ATA100 disks. > > HPT claims that the latest BIOS solved this problem but it didn't work for > me. I'm now avoiding HPT's controllers like plague. > > > Im running 4.2-RELEASE on an Abit BP6 with a 20G IBM connected to the > > onboard HPT366-UDMA66 controller. During heavy disk-io I get a > > read-command timed out error message and now Id like to know if this is > > due to a know driver bug in 4.2-R or maybe a hardware problem. > > > > Please let me know if you need further information like dmesg... I use HighPoint HPT370 ATA100 controller with ad4: 29314MB [59560/16/63] at ata2-master tagged UDMA100 under FreeBSD 4.3-RC #0: Mon Apr 2 22:47:25 GMT. AFAIK all works fine. -- Rgdz, /"\ Sergey Osokin aka oZZ, \ / ASCII RIBBON CAMPAIGN osa@freebsd.org.ru X AGAINST HTML MAIL http://freebsd.org.ru/~osa/ / \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 4:56:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id CA6D237B423 for ; Mon, 9 Apr 2001 04:56:01 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 94700 invoked by uid 100); 9 Apr 2001 11:55:50 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15057.41798.647179.240704@guru.mired.org> Date: Mon, 9 Apr 2001 06:55:50 -0500 To: Pete French Cc: mike@dad.state.vt.us, stable@freebsd.org Subject: Re: Disklabel 101? In-Reply-To: References: <15055.61547.661230.147704@guru.mired.org> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pete French types: > > Mike Barton types: > > > Are there any issues with placing swap first on the hard drive? Unless you > > > insist on filling the drive, it seems to me that this swap arrangement would > > > result in less stack travel. > > > > Not that I know of. In fact, I'm pretty sure that one of my systems > > has root on s2, with swap on s1, which is earlier on the hard disk. > It doesnt work on the same disc however. Try and do an install of 4.2 > creating a swap partition, then a root partition and it fails. Or always > has in my expereince anyway. Its a bit of a nasty gotcha actually because it > is not obvious what the problem is. I can see that it probably makes sense to > have root frst then sawp (and they become a and b) so I dont do it that way > anymore, but its still worth knowing about. I'm doing it on one disk. Here's pstat -s for swap: eve# pstat -s Device 1K-blocks Used Avail Capacity Type /dev/ad0s2b 135040 0 135040 0% Interleaved So I'm swapping on s2. Here's what mount has to say about things: eve# mount /dev/ad0s4a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad0s4e on /usr (ufs, local, soft-updates) /dev/ad0s1 on /msdos (msdos, local) procfs on /proc (procfs, local) So the Unix file systems are on s4. Here's the fdisk: The data for partition 1 is: sysid 11,(DOS or Windows 95 with 32 bit FAT) start 63, size 7197057 (3514 Meg), flag 0 beg: cyl 0/ head 1/ sector 1; end: cyl 447/ head 254/ sector 63 The data for partition 2 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 7197120, size 4192965 (2047 Meg), flag 0 beg: cyl 448/ head 0/ sector 1; end: cyl 708/ head 254/ sector 63 The data for partition 3 is: sysid 131,(Linux filesystem) start 11390085, size 4192965 (2047 Meg), flag 0 beg: cyl 709/ head 0/ sector 1; end: cyl 969/ head 254/ sector 63 The data for partition 4 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 15583050, size 4401810 (2149 Meg), flag 80 (active) beg: cyl 970/ head 0/ sector 1; end: cyl 1023/ head 254/ sector 63 So slice 4 starts well after slice 2 on this disk. In fact, there's a Linux file system in between them. I didn't use sysinstall, so that may refuse to do things like this. It may be that you tried to put root on something other than a, which causes the boot system to not work. I tried that on this system, then had to edit the disklabel to make the root partition a. Or it may be that -current does this but -stable doesn't, as this is a -current system. > The order of separate discs is not a problem. We have a Compaq server that > insists on booting from da1 rather than da0, so I have / on da1, /usr on da0 > and an interleved swap between them. Even in this case, however, I found it > necessary to put the filesystems first on each disc, followed by the swap > partitions. I take it you mean root file systems? The default system layout puts root first, swap second, /var and then /usr, and has followed that pattern on pretty much every Unix I've run into - even systems with logical volume managers which add another layer between the disk and the file systems. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 4:57: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from peloton.runet.edu (peloton.runet.edu [137.45.96.205]) by hub.freebsd.org (Postfix) with ESMTP id 253E037B422 for ; Mon, 9 Apr 2001 04:57:03 -0700 (PDT) (envelope-from brett@peloton.runet.edu) Received: from localhost (brett@localhost) by peloton.runet.edu (8.11.1/8.11.1) with ESMTP id f39BuHY23023; Mon, 9 Apr 2001 07:56:18 -0400 (EDT) (envelope-from brett@peloton.runet.edu) Date: Mon, 9 Apr 2001 07:56:17 -0400 (EDT) From: Brett Taylor To: Dan Langille Cc: "'FreeBSD'" Subject: RE: Further to cvsup tags... actually need ports-audio for 4.3-RC . In-Reply-To: <200104090250.f392oWe66294@ns1.unixathome.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Dan, On Sun, 8 Apr 2001, Dan Langille wrote: > This is such a *huge* waste of bandwidth. I do wish we could solve this > problem. It's occurring time after time. Ideally, we could come up with > a simple script which cleans things up. Dan, there's a lower bandwidth way to solve this, which I've posted many times when this problem first appeared (because it happened to me). The below technique is sort of like cutting off your finger because you have a hangnail. > On 8 Apr 2001, at 19:20, Otter wrote: > > > That's your ports tree. If it's wrong, just rm -rf /usr/ports/* Why do this???? The only thing wrong here is that he's got pkg/ and patches/ still hanging around, probably in a few ports. Instead: cd /usr/ports/ && rm -rf */*/work */*/patches Done. No need to regrab the ENTIRE ports ball. All you've done is type a few lines and CVSup will now work properly and keep things updated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 5: 0:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dilbert.fcg.co.uk (dilbert.firstcallgroup.co.uk [194.203.69.166]) by hub.freebsd.org (Postfix) with ESMTP id 4A2CA37B424 for ; Mon, 9 Apr 2001 05:00:44 -0700 (PDT) (envelope-from pfrench@firstcallgroup.co.uk) Received: from pfrench by dilbert.fcg.co.uk with local (Exim 3.22 #1) id 14maLX-0006QX-00; Mon, 09 Apr 2001 13:00:39 +0100 To: mwm@mired.org Subject: Re: Disklabel 101? Cc: mike@dad.state.vt.us, stable@freebsd.org In-Reply-To: <15057.41798.647179.240704@guru.mired.org> Message-Id: From: Pete French Date: Mon, 09 Apr 2001 13:00:39 +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm doing it on one disk. Here's pstat -s for swap: sorry, didnt make it very clear - I meant doing it within the same slice. nice to see that it works on two different slices though, I never tried that.... -pete. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 5: 5:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 20D9B37B422 for ; Mon, 9 Apr 2001 05:05:33 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 95163 invoked by uid 100); 9 Apr 2001 12:05:32 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15057.42380.369961.254638@guru.mired.org> Date: Mon, 9 Apr 2001 07:05:32 -0500 To: Pete French Cc: mike@dad.state.vt.us, stable@freebsd.org Subject: Re: Disklabel 101? In-Reply-To: References: <15057.41798.647179.240704@guru.mired.org> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pete French types: > > I'm doing it on one disk. Here's pstat -s for swap: > sorry, didnt make it very clear - I meant doing it within the same > slice. nice to see that it works on two different slices though, I > never tried that.... Just curious - did you try it with root still on the a partition? I can't think of any reason why things shouldn't work with b & a inverted. FWIW, the reason I'm using two slices is that the other FreeBSD installation clearly isn't going to use it's swap while that one is running, so why not? http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 5: 9:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailgate0.sover.net (mailgate0.sover.net [209.198.87.43]) by hub.freebsd.org (Postfix) with ESMTP id 6BB3737B422 for ; Mon, 9 Apr 2001 05:09:27 -0700 (PDT) (envelope-from mike@dad.state.vt.us) Received: from yoyo (arc5a301.bf.sover.net [209.198.117.111]) by mailgate0.sover.net (8.11.3/8.11.3) with SMTP id f39C9M622067; Mon, 9 Apr 2001 08:09:23 -0400 (EDT) Message-ID: <003101c0c0ed$a4c0ba10$1201a8c0@sanmik.com> From: "Mike Barton" To: , "Pete French" Cc: References: Subject: Re: Disklabel 101? Date: Mon, 9 Apr 2001 08:07:25 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Pete French" To: ; Cc: Sent: Monday, April 09, 2001 6:22 AM Subject: Re: Disklabel 101? > > Mike Barton types: > > > Are there any issues with placing swap first on the hard drive? Unless you > > > insist on filling the drive, it seems to me that this swap arrangement would > > > result in less stack travel. > > > > Not that I know of. In fact, I'm pretty sure that one of my systems > > has root on s2, with swap on s1, which is earlier on the hard disk. > > It doesnt work on the same disc however. Try and do an install of 4.2 > creating a swap partition, then a root partition and it fails. Or always > has in my expereince anyway. Its a bit of a nasty gotcha actually because it > is not obvious what the problem is. I can see that it probably makes sense to > have root frst then sawp (and they become a and b) so I dont do it that way > anymore, but its still worth knowing about. I've got a setup like that working now. I think the problem is that that you can't have the root partition past the 1024 logical cylinder due to BIOS issues - I surely would've liked to have been in on wrting that piece of code! Mind you, this machine hasn't swapped yet, which raises an OT question: what's the easiest way to get the machine to swap *hard*? Keep in mind that I'm still a bit leery of 'make world' ;) > The order of separate discs is not a problem. We have a Compaq server that > insists on booting from da1 rather than da0, so I have / on da1, /usr on da0 > and an interleved swap between them. Even in this case, however, I found it > necessary to put the filesystems first on each disc, followed by the swap > partitions. > > -pete. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 5:32:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dilbert.fcg.co.uk (dilbert.firstcallgroup.co.uk [194.203.69.166]) by hub.freebsd.org (Postfix) with ESMTP id 2CC8A37B423 for ; Mon, 9 Apr 2001 05:32:54 -0700 (PDT) (envelope-from pfrench@firstcallgroup.co.uk) Received: from pfrench by dilbert.fcg.co.uk with local (Exim 3.22 #1) id 14maqg-0006Rc-00; Mon, 09 Apr 2001 13:32:50 +0100 To: mwm@mired.org Subject: Re: Disklabel 101? Cc: mike@dad.state.vt.us, stable@freebsd.org In-Reply-To: <15057.42380.369961.254638@guru.mired.org> Message-Id: From: Pete French Date: Mon, 09 Apr 2001 13:32:50 +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just curious - did you try it with root still on the a partition? I > can't think of any reason why things shouldn't work with b & a > inverted. I cant remember if sysinstall gives you the option to decoide partition letters or not off the top of my head. I just assumed that the partition marked as UFS with mount point / would become 'a' and that the swap partition would become 'b'. Maybe thats what the problem is - in which case is this something that can be fixed in sysinstall ? I dont think its an uncommon idea for someone doing an install to think "oh, I'lll give it 256M of swap and use all the rest for the other bits" and thus put the 256M swap partition first. -pete. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 6:29: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mozart.patioenclosuresinc.com (mail.patioenclosuresinc.com [206.183.7.174]) by hub.freebsd.org (Postfix) with ESMTP id D0EFA37B422 for ; Mon, 9 Apr 2001 06:29:00 -0700 (PDT) (envelope-from SGHays@PatioEnclosuresInc.com) Received: by mozart.patioenclosuresinc.com with Internet Mail Service (5.5.2653.19) id ; Mon, 9 Apr 2001 09:33:11 -0400 Message-ID: From: "Hays, Sam" To: "'freebsd-stable@freebsd.org'" Subject: Releases Date: Mon, 9 Apr 2001 09:33:01 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, Is there a quick way to tell what the current tree is when I do a cvsup w/ RELENG_4? I thought that it was always 4.x-STABLE (not this release candidate stuff). -Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 6:45:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from harp.wrdp.com (harp.dublin.wrdp.net [212.147.130.131]) by hub.freebsd.org (Postfix) with ESMTP id A7BCF37B422 for ; Mon, 9 Apr 2001 06:45:08 -0700 (PDT) (envelope-from jraftery@wrdp.com) Received: from JRAFTERY (jrafte.dublin.wrdp.net [172.16.4.52]) by harp.wrdp.com (Postfix) with SMTP id 6B8EC10ACC for ; Mon, 9 Apr 2001 13:45:03 +0000 (GMT) Message-ID: <030e01c0c0fb$52b2fcc0$340410ac@JRAFTERY> From: "James Raftery" To: References: Subject: Re: Releases Date: Mon, 9 Apr 2001 14:45:22 +0100 Organization: Worldport Communications Inc 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.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Hays, Sam" To: Sent: Monday, April 09, 2001 2:33 PM Subject: Releases > Is there a quick way to tell what the current tree is when I do a cvsup w/ > RELENG_4? I thought that it was always 4.x-STABLE (not > this release candidate stuff). Argh! RELENG_4 is *always* 4-STABLE. An RC is a particularly "stable" phase of 4-STABLE development because it's subject to a code-freeze and is about to become a -RELEASE. This exact thread was played out *all* weekend. How could you not see it? Regards, james To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 6:58:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cisco.com (sword.cisco.com [161.44.208.100]) by hub.freebsd.org (Postfix) with ESMTP id 21CBB37B422 for ; Mon, 9 Apr 2001 06:58:19 -0700 (PDT) (envelope-from sjt@cisco.com) Received: from sjt-u10.cisco.com (sjt-u10.cisco.com [10.85.30.63]) by cisco.com (8.8.5-Cisco.1/8.8.8) with ESMTP id JAA19934 for ; Mon, 9 Apr 2001 09:58:18 -0400 (EDT) From: Steve Tremblett Received: (sjt@localhost) by sjt-u10.cisco.com (8.8.5-Cisco.1/CISCO.WS.1.2) id JAA13889 for freebsd-stable@freebsd.org; Mon, 9 Apr 2001 09:58:17 -0400 (EDT) Message-Id: <200104091358.JAA13889@sjt-u10.cisco.com> Subject: Re: Releases To: freebsd-stable@freebsd.org Date: Mon, 9 Apr 2001 09:58:17 -0400 (EDT) In-Reply-To: <030e01c0c0fb$52b2fcc0$340410ac@JRAFTERY> from "James Raftery" at Apr 09, 2001 02:45:22 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG +--- James Raftery wrote: | | ----- Original Message ----- | From: "Hays, Sam" | To: | Sent: Monday, April 09, 2001 2:33 PM | Subject: Releases | | | > Is there a quick way to tell what the current tree is when I do a | cvsup w/ | > RELENG_4? I thought that it was always 4.x-STABLE (not | > this release candidate stuff). | | Argh! RELENG_4 is *always* 4-STABLE. An RC is a particularly "stable" | phase of 4-STABLE development because it's subject to a code-freeze and | is about to become a -RELEASE. | | This exact thread was played out *all* weekend. How could you not see | it? | To be honest, FreeBSD's definition of BETA or RELEASE CANDIDATE is contrary to common understanding of the terms. BETA or RC implies new code that is currently in the testing phase (well RC implies that it is almost ready for release, but it still hasn't been proven as ready). Actually, maybe they should try it the other way around. There are commits to the STABLE stream, and when the STABLE stream is solid enough, it is released. STABLE sounds to me like it should be called BETA! my $0.02 (Canadian) -- Steve Tremblett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 7: 9:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from emma1.emma.line.org (p3EE3C88F.dip.t-dialin.net [62.227.200.143]) by hub.freebsd.org (Postfix) with ESMTP id 78F8437B423 for ; Mon, 9 Apr 2001 07:09:17 -0700 (PDT) (envelope-from ma@dt.e-technik.uni-dortmund.de) Received: by emma1.emma.line.org (Postfix, from userid 500) id A2DAEA2001; Mon, 9 Apr 2001 16:09:11 +0200 (CEST) To: freebsd-stable@freebsd.org Subject: BDECFLAGS break current 4.x-stable build From: Matthias Andree Date: 09 Apr 2001 16:09:11 +0200 Message-ID: Lines: 82 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 4.x-stable Checked out today (2001-04-09) at 13:00 UTC ***** NOTE: _ALL_ problems mentioned below disappear with BDECFLAGS removed from CFLAGS, thus a default build will not encounter these. ***** I caught some hard errors (build aborted) with CFLAGS+=${BDECFLAGS} in /etc/make.conf: /usr/src/secure/lib/libcrypt/crypt-des.c:196: syntax error before `int' (it doesn't understand "INLINE" here with BDECFLAGS enabled) Same problem for: (one problem shown as example) /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/comp_error.c:71: syntax error before `int' (it doesn't understand "inline" here with BDECFLAGS enabled) and various other places in libncurses libskey with BDECFLAGS: (one problem shown as example) /usr/src/lib/libskey/skey.h:43: warning: prototype declaration cc1: warnings being treated as errors /usr/src/lib/libskey/skeylogin.c: In function `skeylookup': /usr/src/lib/libskey/skeylogin.c:115: warning: passing arg 1 of `umask' with different width due to prototype /usr/src/lib/libskey/skeylogin.c:117: warning: passing arg 1 of `umask' with different width due to prototype *** Error code 1 libc/gen/arc4random.c: /usr/src/lib/libc/../libc/gen/arc4random.c: At top level: /usr/src/lib/libc/../libc/gen/arc4random.c:98: syntax error before `u_int8_t' /usr/src/lib/libc/../libc/gen/arc4random.c:100: warning: function declaration isn't a prototype /usr/src/lib/libc/../libc/gen/arc4random.c:113: syntax error before `u_int32_t' /usr/src/lib/libc/../libc/gen/arc4random.c:115: warning: function declaration isn't a prototype Removing the BDECFLAGS from CFLAGS in make.conf fixes the build (and gets me rid of tons of warnings). I'm not sure what causes this. I'm not investigating this further since I'm short on time and it might be worth fixing after 4.3 only. BDECFLAGS are from 4.3-RC's /etc/defaults/make.conf (see below) Context: ------------------------------------------------------------------------------ static u_char ascii64[] = "./0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz"; /* 0000000000111111111122222222223333333333444444444455555555556666 */ /* 0123456789012345678901234567890123456789012345678901234567890123 */ static INLINE int ascii_to_bin(char ch) { if (ch > 'z') return(0); if (ch >= 'a') return(ch - 'a' + 38); ------------------------------------------------------------------------------ My current BDECFLAGS: ------------------------------------------------------------------------------ BDECFLAGS= -W -Wall -ansi -pedantic -Wbad-function-cast -Wcast-align \ -Wcast-qual -Wchar-subscripts -Wconversion -Winline \ -Wmissing-prototypes -Wnested-externs -Wpointer-arith \ -Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings ------------------------------------------------------------------------------ -- Matthias Andree To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 7:37:11 2001 Delivered-To: freebsd-stable@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 4721437B423 for ; Mon, 9 Apr 2001 07:37:07 -0700 (PDT) (envelope-from andyf@speednet.com.au) Received: from backup.af.speednet.com.au (backup.af.speednet.com.au [172.22.2.4]) by backup.af.speednet.com.au (8.11.3/8.11.3) with ESMTP id f39Eb2T14048 for ; Tue, 10 Apr 2001 00:37:03 +1000 (EST) (envelope-from andyf@speednet.com.au) Date: Tue, 10 Apr 2001 00:37:02 +1000 (EST) From: Andy Farkas X-X-Sender: To: Subject: cvs commit: src/usr.sbin/cron/cron do_command.c (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Any chance of this being MFC'd before release?? >>> Modified files: usr.sbin/cron/cron do_command.c Log: Stop cron from shouting in the syslog. Use setproctitle() instead, since smashing argv[0] doesn't have the intended effect of changing the ps(1) output these days. PR: 25850 Revision Changes Path 1.20 +2 -7 src/usr.sbin/cron/cron/do_command.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 7:48: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id 0578337B423 for ; Mon, 9 Apr 2001 07:48:03 -0700 (PDT) (envelope-from rasputin@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14mcxV-000Bd8-00 for stable@freebsd.org; Mon, 9 Apr 2001 15:48:01 +0100 Received: (from rasputin@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f39Em0H24977 for stable@freebsd.org; Mon, 9 Apr 2001 15:48:00 +0100 (BST) (envelope-from rasputin) Date: Mon, 9 Apr 2001 15:48:00 +0100 From: Rasputin To: stable@freebsd.org Subject: Re: Releases Message-ID: <20010409154800.A24937@dogma.freebsd-uk.eu.org> Reply-To: Rasputin References: <030e01c0c0fb$52b2fcc0$340410ac@JRAFTERY> <200104091358.JAA13889@sjt-u10.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200104091358.JAA13889@sjt-u10.cisco.com>; from sjt@cisco.com on Mon, Apr 09, 2001 at 09:58:17AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Steve Tremblett [010409 14:59]: > +--- James Raftery wrote: > | > | > | Argh! RELENG_4 is *always* 4-STABLE. An RC is a particularly "stable" > | phase of 4-STABLE development because it's subject to a code-freeze and > | is about to become a -RELEASE. > To be honest, FreeBSD's definition of BETA or RELEASE CANDIDATE is > contrary to common understanding of the terms. BETA or RC implies new > code that is currently in the testing phase (well RC implies that it is > almost ready for release, but it still hasn't been proven as ready). How is that different for FreeBSD then? > Actually, maybe they should try it the other way around. There are > commits to the STABLE stream, and when the STABLE stream is solid > enough, it is released. STABLE sounds to me like it should be called > BETA! Hmm. Do you actually track STABLE? Been tracking it for over a year and I think it's broken twice in all that time. More importantly, it's been fixed within a day. -- Rasputin Jack of All Trades :: Master of Nuns To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 7:52:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from chmod.ath.cx (CC2-1242.charter-stl.com [24.217.116.226]) by hub.freebsd.org (Postfix) with ESMTP id C03C237B422 for ; Mon, 9 Apr 2001 07:52:41 -0700 (PDT) (envelope-from ajh3@chmod.ath.cx) Received: by chmod.ath.cx (Postfix, from userid 1001) id 3FACFA91E; Mon, 9 Apr 2001 09:52:09 -0500 (CDT) Date: Mon, 9 Apr 2001 09:52:09 -0500 From: Andrew Hesford To: Mike Barton Cc: mwm@mired.org, Pete French , stable@freebsd.org Subject: Re: Disklabel 101? Message-ID: <20010409095209.B2619@cec.wustl.edu> References: <003101c0c0ed$a4c0ba10$1201a8c0@sanmik.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <003101c0c0ed$a4c0ba10$1201a8c0@sanmik.com>; from mike@dad.state.vt.us on Mon, Apr 09, 2001 at 08:07:25AM -0400 X-Loop: Andrew Hesford Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 09, 2001 at 08:07:25AM -0400, Mike Barton wrote: > I've got a setup like that working now. I think the problem is that that you > can't have the root partition past the 1024 logical cylinder due to BIOS > issues - I surely would've liked to have been in on wrting that piece of > code! Mind you, this machine hasn't swapped yet, which raises an OT > question: what's the easiest way to get the machine to swap *hard*? Keep in > mind that I'm still a bit leery of 'make world' ;) No, the root partition can be anywhere. The trouble with the 1024th cylinder is that the boot sector might not be able to find the kernel. This is a non-issue, though, becaues the FreeBSD boot0 supports BIOS 0x13 extensions (see the manpage for boot0cfg, on the "packet" option), which will let the boot0 code find a kernel anywhere. Actually, when I first built my system, I didn't install boot0 because I was using LILO. When I tried to replace it, I couldn't get boot0 to boot, because I didn't specify the packet option. -- Andrew Hesford ajh3@chmod.ath.cx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 7:54:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id E279A37B423 for ; Mon, 9 Apr 2001 07:54:46 -0700 (PDT) (envelope-from oberman@ptavv.es.net) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id f39Eskc00975 for ; Mon, 9 Apr 2001 07:54:46 -0700 (PDT) Message-Id: <200104091454.f39Eskc00975@ptavv.es.net> To: stable@freebsd.org Subject: Enabling ata write cache in -Stable Date: Mon, 09 Apr 2001 07:54:46 -0700 From: "Kevin Oberman" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I see that the ATA_ENABLE_WC option has left the kernel. Is there any way to temporarily re-enable it at boot time? I see hw.ata.wc, but it is read-only. I only want to use the write cache when running stand-alone and using dd to copy my hard drive. I've checked the man pages and the release notes and I don't see anything. Thanks, R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 8: 5:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from matrix.dynamic-cast.com (r175-5-dsl.sea.lightrealm.net [216.122.5.175]) by hub.freebsd.org (Postfix) with ESMTP id 000B337B423 for ; Mon, 9 Apr 2001 08:05:28 -0700 (PDT) (envelope-from herveyw@dynamic-cast.com) Received: from chillipepper (chillipepper.dynamic-cast.com [192.168.1.1]) by matrix.dynamic-cast.com (8.11.3/8.11.3) with SMTP id f39F4vS55905; Mon, 9 Apr 2001 08:05:00 -0700 (PDT) (envelope-from herveyw@dynamic-cast.com) Message-ID: <007b01c0c106$792bebe0$0101a8c0@chillipepper> From: "Hervey Wilson" To: "Sergey A. Osokin" , Cc: References: <3ACFDF76.62E58A15@acm.org> <20010409151016.A75461@freebsd.org.ru> Subject: Re: HPT366 problems Date: Mon, 9 Apr 2001 08:05:07 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2462.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Sergey A. Osokin" > On Sun, Apr 08, 2001 at 11:48:06AM +0800, KT Sin wrote: > > I have the same problem too. Let me guess, your disk is an IBM DTLA > > (ATA100). I believe this is due to incompatibility between HPT366 and IBM's > > ATA100 disks. > > > > HPT claims that the latest BIOS solved this problem but it didn't work for > > me. I'm now avoiding HPT's controllers like plague. > > > > > Im running 4.2-RELEASE on an Abit BP6 with a 20G IBM connected to the > > > onboard HPT366-UDMA66 controller. During heavy disk-io I get a > > > read-command timed out error message and now Id like to know if this is > > > due to a know driver bug in 4.2-R or maybe a hardware problem. > > > > > > Please let me know if you need further information like dmesg... > > I use HighPoint HPT370 ATA100 controller with > ad4: 29314MB [59560/16/63] at ata2-master tagged UDMA100 > under FreeBSD 4.3-RC #0: Mon Apr 2 22:47:25 GMT. > AFAIK all works fine. > I had an IBM 30Gb (DTLA307030) ATA/100 attached to the HPT366 on my Abit BP6 and had no end of trouble with it. I gave up and moved it to the UDMA/33 controller. When the disk developed a bad sector, I exchanged it and got a Western Digital ATA/100 which works just fine on HPT366. So, I do this there's an issue with HPT366 and IBM ATA/100 drives. H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 8:11:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id 2D29437B424; Mon, 9 Apr 2001 08:11:33 -0700 (PDT) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.11.3) with SMTP id f39F9WR22849; Mon, 9 Apr 2001 11:09:32 -0400 (EDT) (envelope-from matt@gsicomp.on.ca) Message-ID: <001b01c0c106$a897f770$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Rasputin" , References: <030e01c0c0fb$52b2fcc0$340410ac@JRAFTERY> <200104091358.JAA13889@sjt-u10.cisco.com> <20010409154800.A24937@dogma.freebsd-uk.eu.org> Subject: Re: Releases Date: Mon, 9 Apr 2001 11:06:30 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > * Steve Tremblett [010409 14:59]: > > +--- James Raftery wrote: > > | Argh! RELENG_4 is *always* 4-STABLE. An RC is a particularly "stable" > > | phase of 4-STABLE development because it's subject to a code-freeze and > > | is about to become a -RELEASE. > > > To be honest, FreeBSD's definition of BETA or RELEASE CANDIDATE is > > contrary to common understanding of the terms. BETA or RC implies new > > code that is currently in the testing phase (well RC implies that it is > > almost ready for release, but it still hasn't been proven as ready). > > How is that different for FreeBSD then? The RC designation seems to be "normal". The BETA designation does not. Is there any reason why we really need a -BETA tag, or could we just go from -STABLE to -RC1? I think this would be less confusing to people who are new to FreeBSD's scheme of things. [ On a related note, -CURRENT seems to suggest the wrong thing. I've had the unlucky experience of recovering production boxes (!!) that previous admins had decided to update to -CURRENT because, hey, it must be the best code, right? IMHO, -CURRENT should be -DEV. That's a pretty clear indication that it shouldn't be run on production boxes. ] -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 8:15:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebsd.org.ru (sweet.etrust.ru [194.84.67.5]) by hub.freebsd.org (Postfix) with ESMTP id 2A8BF37B42C for ; Mon, 9 Apr 2001 08:15:32 -0700 (PDT) (envelope-from osa@freebsd.org.ru) Received: by freebsd.org.ru (Postfix, from userid 1000) id F290D243; Mon, 9 Apr 2001 19:15:26 +0400 (MSD) Date: Mon, 9 Apr 2001 19:15:26 +0400 From: "Sergey A. Osokin" To: Hervey Wilson Cc: bjoern@loenneker.com, stable@FreeBSD.ORG Subject: Re: HPT366 problems Message-ID: <20010409191526.A77548@freebsd.org.ru> References: <3ACFDF76.62E58A15@acm.org> <20010409151016.A75461@freebsd.org.ru> <007b01c0c106$792bebe0$0101a8c0@chillipepper> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <007b01c0c106$792bebe0$0101a8c0@chillipepper>; from herveyw@dynamic-cast.com on Mon, Apr 09, 2001 at 08:05:07AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 09, 2001 at 08:05:07AM -0700, Hervey Wilson wrote: > > ----- Original Message ----- > From: "Sergey A. Osokin" > > On Sun, Apr 08, 2001 at 11:48:06AM +0800, KT Sin wrote: > > > I have the same problem too. Let me guess, your disk is an IBM DTLA > > > (ATA100). I believe this is due to incompatibility between HPT366 and > IBM's > > > ATA100 disks. > > > > > > HPT claims that the latest BIOS solved this problem but it didn't work > for > > > me. I'm now avoiding HPT's controllers like plague. > > > > > > > Im running 4.2-RELEASE on an Abit BP6 with a 20G IBM connected to the > > > > onboard HPT366-UDMA66 controller. During heavy disk-io I get a > > > > read-command timed out error message and now Id like to know if this > is > > > > due to a know driver bug in 4.2-R or maybe a hardware problem. > > > > > > > > Please let me know if you need further information like dmesg... > > > > I use HighPoint HPT370 ATA100 controller with > > ad4: 29314MB [59560/16/63] at ata2-master tagged UDMA100 > > under FreeBSD 4.3-RC #0: Mon Apr 2 22:47:25 GMT. > > AFAIK all works fine. > > > > I had an IBM 30Gb (DTLA307030) ATA/100 attached to the HPT366 on my Abit BP6 > and had no end of trouble with it. I gave up and moved it to the UDMA/33 > controller. When the disk developed a bad sector, I exchanged it and got a > Western Digital ATA/100 which works just fine on HPT366. So, I do this > there's an issue with HPT366 and IBM ATA/100 drives. AFAIK some IBMs DTLA models have problems with some chipsets/controllers. Please see following URL: http://213.219.40.69/28030104.htm -- Rgdz, /"\ Sergey Osokin aka oZZ, \ / ASCII RIBBON CAMPAIGN osa@freebsd.org.ru X AGAINST HTML MAIL http://freebsd.org.ru/~osa/ / \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 8:27:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: from poontang.schulte.org (poontang.schulte.org [209.134.156.197]) by hub.freebsd.org (Postfix) with ESMTP id 6FC4737B422 for ; Mon, 9 Apr 2001 08:27:23 -0700 (PDT) (envelope-from christopher@schulte.org) Received: from schulte-laptop.schulte.org ([64.183.199.40]) by poontang.schulte.org (8.12.0.Beta5/8.12.0.Beta5) with ESMTP id f39FRGIr018495; Mon, 9 Apr 2001 10:27:17 -0500 (CDT) Message-Id: <5.0.2.1.0.20010409101533.00ace930@pop.schulte.org> X-Sender: schulte@pop.schulte.org X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Mon, 09 Apr 2001 10:26:50 -0500 To: "Matthew Emmerton" , "Rasputin" , From: Christopher Schulte Subject: Re: Releases In-Reply-To: <001b01c0c106$a897f770$1200a8c0@gsicomp.on.ca> References: <030e01c0c0fb$52b2fcc0$340410ac@JRAFTERY> <200104091358.JAA13889@sjt-u10.cisco.com> <20010409154800.A24937@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:06 AM 4/9/2001 -0400, Matthew Emmerton wrote: >[ On a related note, -CURRENT seems to suggest the wrong thing. I've had >the unlucky experience of recovering production boxes (!!) that previous >admins had decided to update to -CURRENT because, hey, it must be the best >code, right? IMHO, -CURRENT should be -DEV. That's a pretty clear >indication that it shouldn't be run on production boxes. ] Change the designation just because some admins don't know how to RTFM? I don't think so... They fu*ked up. Plain and simple. -CURRENT makes sense, and more importantly is documented for those who take the time to look. I'm not as hot about the BETA designation, but generally feel it should be left alone simply because it's documented, and thus should NOT be a problem. *sigh* My position may change on this topic. >-- >Matt Emmerton --chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 8:28: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id E5F3737B422 for ; Mon, 9 Apr 2001 08:27:58 -0700 (PDT) (envelope-from jose@we.lc.ehu.es) Received: from v-ger.we.lc.ehu.es (v-ger [158.227.6.51]) by polaris.we.lc.ehu.es (8.11.1/8.11.1) with ESMTP id f39FRvn05871; Mon, 9 Apr 2001 17:27:57 +0200 (MET DST) Received: from we.lc.ehu.es (localhost [127.0.0.1]) by v-ger.we.lc.ehu.es (8.11.3/8.11.3) with ESMTP id f39FRv500646; Mon, 9 Apr 2001 17:27:57 +0200 (CEST) (envelope-from jose@we.lc.ehu.es) Message-ID: <3AD1D4FD.504E92FA@we.lc.ehu.es> Date: Mon, 09 Apr 2001 17:27:57 +0200 From: "Jose M. Alcaide" Organization: Universidad del Pais Vasco - Dpto. de Electricidad y Electronica X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: Kevin Oberman Cc: stable@FreeBSD.ORG Subject: Re: Enabling ata write cache in -Stable References: <200104091454.f39Eskc00975@ptavv.es.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kevin Oberman wrote: > > I see that the ATA_ENABLE_WC option has left the kernel. Is there any > way to temporarily re-enable it at boot time? I see hw.ata.wc, but it > is read-only. I only want to use the write cache when running > stand-alone and using dd to copy my hard drive. > > I've checked the man pages and the release notes and I don't see > anything. > I bumped into this same problem and, after reading the ata(4) manpage several times, I noticed that it says: The following tunables are setable from the loader: ^^^^^^^^^^^^^^^ so you only need to add hw.ata.wc="1" to /boot/loader.conf. BTW, I think that these new ata kernel tunables should be added to /boot/defaults/loader.conf. Cheers, -- JMA ****** Jose M. Alcaide // jose@we.lc.ehu.es // jmas@FreeBSD.org ****** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 8:28:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id CC93037B423 for ; Mon, 9 Apr 2001 08:28:35 -0700 (PDT) (envelope-from rasputin@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by probity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14mdaj-000JMz-00; Mon, 9 Apr 2001 16:28:33 +0100 Received: (from rasputin@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f39FSVA25656; Mon, 9 Apr 2001 16:28:31 +0100 (BST) (envelope-from rasputin) Date: Mon, 9 Apr 2001 16:28:30 +0100 From: Rasputin To: Matthew Emmerton Cc: stable@freebsd.org Subject: Re: Releases Message-ID: <20010409162830.A25605@dogma.freebsd-uk.eu.org> Reply-To: Rasputin References: <030e01c0c0fb$52b2fcc0$340410ac@JRAFTERY> <200104091358.JAA13889@sjt-u10.cisco.com> <20010409154800.A24937@dogma.freebsd-uk.eu.org> <001b01c0c106$a897f770$1200a8c0@gsicomp.on.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <001b01c0c106$a897f770$1200a8c0@gsicomp.on.ca>; from matt@gsicomp.on.ca on Mon, Apr 09, 2001 at 11:06:30AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matthew Emmerton [010409 16:13]: > > * Steve Tremblett [010409 14:59]: > > > +--- James Raftery wrote: > The RC designation seems to be "normal". The BETA designation does not. Is > there any reason why we really need a -BETA tag, or could we just go > from -STABLE to -RC1? I think this would be less confusing to people who > are new to FreeBSD's scheme of things. Yeah, fair enough. Maybe UPDATING could be temporarily amended to reflect the state of the code. > [ On a related note, -CURRENT seems to suggest the wrong thing. I've had > the unlucky experience of recovering production boxes (!!) that previous > admins had decided to update to -CURRENT because, hey, it must be the best > code, right? > IMHO, -CURRENT should be -DEV. That's a pretty clear > indication that it shouldn't be run on production boxes. ] IMHO, anybody who can cvsup but not bother to read the 'what STABLE and CURRENT are' part of the cvsup section in the Handbook should be kept far away from production machines. And possibly sharp objects too. -- Rasputin Jack of All Trades :: Master of Nuns To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 8:46:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.unixathome.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 3400D37B424 for ; Mon, 9 Apr 2001 08:46:27 -0700 (PDT) (envelope-from dan@langille.org) Received: from xeon (xeon.int.nz.freebsd.org [192.168.0.18]) by ns1.unixathome.org (8.11.3/8.11.3) with ESMTP id f39Fjpe72483; Tue, 10 Apr 2001 03:45:52 +1200 (NZST) (envelope-from dan@langille.org) Date: Tue, 10 Apr 2001 03:45:51 +1200 (NZST) From: Dan Langille X-X-Sender: To: Christopher Schulte Cc: Matthew Emmerton , Rasputin , Subject: Re: Releases In-Reply-To: <5.0.2.1.0.20010409101533.00ace930@pop.schulte.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Apr 2001, Christopher Schulte wrote: > Change the designation just because some admins don't know how to RTFM? I > don't think so... They fu*ked up. Plain and simple. -CURRENT makes sense, > and more importantly is documented for those who take the time to look. This is beginning to sound like a human-computer interface issue. If you read comp.risks, you'll see that issues such as this arise time and time again. It's almost similar to POLA. If it looks like a duck and quacks like a duck.... Give meaningful and widely used names to things which people are familiar with. > I'm not as hot about the BETA designation, but generally feel it should > be left alone simply because it's documented, and thus should NOT be a > problem. By this designation, we could call a brake a clutch and get away with it because it's all documented. The problem is not with the documentation. It's with the name. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 9:17:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id D139837B423 for ; Mon, 9 Apr 2001 09:17:10 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id f39GH9I08011 for ; Mon, 9 Apr 2001 09:17:09 -0700 (PDT) Received: from pau-amma.whistle.com( 207.76.205.64) by whistle.com via smap (V2.0) id xma008002; Mon, 9 Apr 2001 09:16:51 -0700 Received: (from dhw@localhost) by pau-amma.whistle.com (8.11.1/8.11.1) id f39GGpb72064 for stable@FreeBSD.ORG; Mon, 9 Apr 2001 09:16:51 -0700 (PDT) Date: Mon, 9 Apr 2001 09:16:51 -0700 (PDT) From: David Wolfskill Message-Id: <200104091616.f39GGpb72064@pau-amma.whistle.com> To: stable@FreeBSD.ORG Subject: Re: Disklabel 101? In-Reply-To: <000001c0bfd9$3b96a230$1201a8c0@sanmik.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, since folks are comparing unusual disk layouts, here's one I've been using on my laptop for the last few weeks (since I got it). Now, this isn't something that you can tell sysinstall to do directly; more about that should be at http://www.catwhisker.org/~david/FreeBSD/laptop.html. It should also be understood that I'm tracking both -CURRENT and -STABLE on the machine; that I'm working (as time permits) on some code that will permit the space pointed to by the 4th MBR "partition table" entry to be used as a "suspend to disk partition". I just finished building -CURRENT for today, and did the multi-user boot, so that's what it's running at the moment. (I'll probably switch to today's -STABLE shortly after posting this.) m758712358[1] sudo boot0cfg -v ad0 # flag start chs type end chs offset size 1 0x00 0: 1: 1 0xa5 137:239:63 63 2086497 2 0x00 138: 0: 1 0xa5 275:239:63 2086560 2086560 3 0x80 346: 0: 1 0xa5 535:239:63 5231520 33838560 4 0x00 276: 0: 1 0xa0 345:239:63 4173120 1058400 version=1.1 drive=0x80 mask=0x7 ticks=182 options=packet,update,nosetdrv default_selection=F3 (Slice 3) m758712358[2] df -k; swapinfo Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s3a 95263 70203 17439 80% / devfs 1 1 0 100% /dev /dev/ad0s1a 95263 40768 46874 47% /S1 /dev/ad0s1e 915695 750190 92250 89% /S1/usr /dev/ad0s2a 95263 40767 46875 47% /S2 /dev/ad0s2e 915727 750172 92297 89% /S2/usr /dev/ad0s3e 915727 726821 115648 86% /usr /dev/ad0s3g 254063 73145 160593 31% /var /dev/ad0s3h 14116697 4354913 8632449 34% /common procfs 4 4 0 100% /proc /dev/md10c 520140 16 478516 0% /tmp Device 1K-blocks Used Avail Capacity Type /dev/ad0s3b 1048448 4168 1044280 0% Interleaved m758712358[3] ls -l /S?/kernel /boot/kernel/kernel -r-xr-xr-x 1 root wheel 2835013 Apr 9 06:51 /S1/kernel -r-xr-xr-x 1 root wheel 2834713 Apr 8 10:02 /S2/kernel -r-xr-xr-x 1 root wheel 3386431 Apr 9 08:43 /boot/kernel/kernel As in Mike's case, I share the swap space among the kernels; I also share /var and /common -- basically, everything on what the 3rd "partition tabel" entry points to. /common is where /usr/local points, as well as /home. And /usr/obj in each case is a symlink to /common/*/obj (where "*" is one of "C", "S1", or "S2"). /common/cvs is where I keep my CVS repository. It seems to be working OK for me so far. :-) Cheers, david -- David Wolfskill dhw@whistle.com UNIX System Administrator Desk: 650/577-7158 TIE: 8/499-7158 Cell: 650/759-0823 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 9:24: 2 2001 Delivered-To: freebsd-stable@freebsd.org Received: from poontang.schulte.org (poontang.schulte.org [209.134.156.197]) by hub.freebsd.org (Postfix) with ESMTP id B10A137B422 for ; Mon, 9 Apr 2001 09:23:59 -0700 (PDT) (envelope-from christopher@schulte.org) Received: from schulte-laptop.schulte.org ([64.183.199.40]) by poontang.schulte.org (8.12.0.Beta5/8.12.0.Beta5) with ESMTP id f39GNvIr020383; Mon, 9 Apr 2001 11:23:57 -0500 (CDT) Message-Id: <5.0.2.1.0.20010409111054.00b18008@pop.schulte.org> X-Sender: schulte@pop.schulte.org X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Mon, 09 Apr 2001 11:23:30 -0500 To: Dan Langille From: Christopher Schulte Subject: Re: Releases Cc: Matthew Emmerton , Rasputin , In-Reply-To: References: <5.0.2.1.0.20010409101533.00ace930@pop.schulte.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:45 AM 4/10/2001 +1200, Dan Langille wrote: >Give meaningful and widely used names to things which people are familiar >with. -CURRENT fits all those requirements. > > I'm not as hot about the BETA designation, but generally feel it should > > be left alone simply because it's documented, and thus should NOT be a > > problem. > >By this designation, we could call a brake a clutch and get away with it >because it's all documented. The problem is not with the documentation. >It's with the name. Documentation is not the only factor. The name was chosen for a *reason*, to convey a point. It's choice was not arbitrary. And it's since been accepted by the development and administrative community. Question being: Now, are we to a point where that accepted name needs to be reevaluated for the sake of general consensus, need or desire. That's the real question, IMHO. --chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 9:36:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-32.dsl.lsan03.pacbell.net [63.207.60.32]) by hub.freebsd.org (Postfix) with ESMTP id 34F6C37B423 for ; Mon, 9 Apr 2001 09:36:32 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D948366D3F; Mon, 9 Apr 2001 09:36:30 -0700 (PDT) Date: Mon, 9 Apr 2001 09:36:30 -0700 From: Kris Kennaway To: Matthias Andree Cc: freebsd-stable@FreeBSD.org Subject: Re: BDECFLAGS break current 4.x-stable build Message-ID: <20010409093630.B72961@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ma@dt.e-technik.uni-dortmund.de on Mon, Apr 09, 2001 at 04:09:11PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 09, 2001 at 04:09:11PM +0200, Matthias Andree wrote: > 4.x-stable Checked out today (2001-04-09) at 13:00 UTC > > ***** > NOTE: _ALL_ problems mentioned below disappear with BDECFLAGS removed > from CFLAGS, thus a default build will not encounter these. > ***** Submit patches to fix them, then. BDECFLAGS is there for developers to work on code correctness and possible bugs resulting from language misuse (or general gcc pickiness which doesn't actually involve code bugs). It doesn't change the code generated by gcc. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 9:38:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from thud.pcs.k12.mi.us (thud.pcs.k12.mi.us [204.39.58.108]) by hub.freebsd.org (Postfix) with ESMTP id 34E6537B424 for ; Mon, 9 Apr 2001 09:38:24 -0700 (PDT) (envelope-from mrr@thud.pcs.k12.mi.us) Received: by thud.pcs.k12.mi.us (Postfix, from userid 1000) id 4BE82B587; Mon, 9 Apr 2001 13:38:15 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by thud.pcs.k12.mi.us (Postfix) with ESMTP id 448D67910; Mon, 9 Apr 2001 13:38:15 -0400 (EDT) Date: Mon, 9 Apr 2001 13:38:15 -0400 (EDT) From: "Michael R. Rudel" To: Christopher Schulte Cc: Dan Langille , Matthew Emmerton , Rasputin , Subject: Re: Releases In-Reply-To: <5.0.2.1.0.20010409111054.00b18008@pop.schulte.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [... SNIP ...] Personally, I don't see a problem with the -CURRENT and -STABLE naming scheme. As someone said, anybody who can CVSup (not to mention get the sample CVSup files to work off of) yet not read the rest of the documentation has other issues. Renaming -CURRENT to -DEV or -DEVEL would be the equivlent of dulling all the knives in your house so that people don't cut themselves. As for -BETA, there isn't really a problem with this either, if you take it apart and look at it. From the Hacker's Dictionary, the definition of 'beta' is as follows: 1. Mostly working, but still under test; usu. used with `in': `in beta'. In the Real World, systems (hardware or software) software often go through two stages of release testing: Alpha (in-house) and Beta (out-house?). Beta releases are generally made to a group of lucky (or unlucky) trusted customers. 2. Anything that is new and experimental. "His girlfriend is in beta" means that he is still testing for compatibility and reserving judgment. 3. Flaky; dubious; suspect (since beta software is notoriously buggy). x.x-BETA is ... notoriously buggy. It has bugs, that's the point of the beta - to work the bugs out. If it didn't have bugs (that we knew about), it'd be -RELEASE. -STABLE is generally (with some execptions), more stable than -RELEASE, because it is a -RELEASE version with both ongoing bugfixes and (minor) new features. A release canidate is an almost ready release. Personally, I think these should be named GAMMA, DELTA, ... because that continues with the whole ALPHA or BETA trend. All these designitions do is indicate various stages of code freeze, and this is all documented places. Changing the whole release process of something that has worked for years isn't going to help anything, people are always going to be confused if you change it - if you suddenly change the way this shit is named, I'm going to be confused when 4.4 comes around or whatever. Just chill, and instruct people to Read The Fine Manual. -------------------------------------------------- Michael R. Rudel * 734.417.4859 * mrr@gotclue.org AOL AIM: ATSTheory * Cell e-mail: page@gotclue.org Network Engineer, Pinckney Community Schools Systems Engineer, NourDesign Corp Principal Engineer, Michael R. Rudel Consulting Authorized Representative, Charter Communications -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 10:26:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 7E68937B424 for ; Mon, 9 Apr 2001 10:26:23 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f39HPQ810973; Mon, 9 Apr 2001 10:25:26 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: dan@langille.org Cc: christopher@schulte.org, matt@gsicomp.on.ca, rara.rasputin@virgin.net, stable@FreeBSD.ORG Subject: Re: Releases In-Reply-To: References: <5.0.2.1.0.20010409101533.00ace930@pop.schulte.org> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010409102526S.jkh@osd.bsdi.com> Date: Mon, 09 Apr 2001 10:25:26 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 50 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > By this designation, we could call a brake a clutch and get away with it > because it's all documented. The problem is not with the documentation. > It's with the name. That's a nice pat answer, but the problem is that for every value of "name" we propose, somebody comes forward and says "But that confuses me." We can't call it BETA, we can't call it STABLE, we can't call it RC, we can't call it PRERELEASE, because each and every one of those have had push-back from people who said it would conflict with previous definitions they hold dear. Given that, chances are excellent that any other halfway logical names we come up with will suffer from the same problem. The real problem here is that we're trying to cater to the lowest common denominator, which is stupid people who leap before they look and then blame someone else for the injuries they sustain. It is for those very same people that legal liability forced McDonalds to write "Warning: This is called hot coffee. That means it is Hot. You should never, ever dump it into your crotch or on any other part of your body which is intended to remain unscalded. Did we mention that it's very hot?" If we were McDonalds (or Microsoft for that matter), we would also stop providing access to -stable and -current entirely because it had been statistically proven that the lower percentile out there was doing the equivalent of pouring coffee in their laps and we didn't want the liability. However, we're not them and I don't think we should try to twist ourselves into those kinds of shapes. Both -current and -stable are aimed at something other than "the masses" (for them, there are -releases in handy jewel-cased form) and are well documented as such in our handbook. The masses simply need to learn to stay out of those areas. To use another analogy, FreeBSD is not just a building, it's a building with a perpetual construction site next to it which is knocking up another building. As long as the office workers stay in their building, things are good. When they wander onto the construction site without hard-hats or an invitation for a guided tour, however, they should expect to get either squished or seriously yelled at and chased off the site by the first construction worker they run into. A construction site also generally has fences around it to stop the truly cerebrally challenged from crawling under the pile-driver, perhaps we need the same. I got it - unless you provide a special secret flag to it, cvsup always uses its GUI mode and presents the user with a disclaimer and release form which needs to be agreed to first. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 10:30:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.unixathome.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 6886237B618 for ; Mon, 9 Apr 2001 10:30:06 -0700 (PDT) (envelope-from dan@langille.org) Received: from xeon (xeon.int.nz.freebsd.org [192.168.0.18]) by ns1.unixathome.org (8.11.3/8.11.3) with ESMTP id f39HTie72987; Tue, 10 Apr 2001 05:29:44 +1200 (NZST) (envelope-from dan@langille.org) Date: Tue, 10 Apr 2001 05:29:43 +1200 (NZST) From: Dan Langille X-X-Sender: To: Christopher Schulte Cc: Matthew Emmerton , Rasputin , Subject: Re: Releases In-Reply-To: <5.0.2.1.0.20010409111054.00b18008@pop.schulte.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Apr 2001, Christopher Schulte wrote: > At 03:45 AM 4/10/2001 +1200, Dan Langille wrote: > >Give meaningful and widely used names to things which people are familiar > >with. > > -CURRENT fits all those requirements. In this case, the familiarity is reduced to those familiar with the project. Witness the frequency with which the confusion arises. > > > I'm not as hot about the BETA designation, but generally feel it should > > > be left alone simply because it's documented, and thus should NOT be a > > > problem. > > > >By this designation, we could call a brake a clutch and get away with it > >because it's all documented. The problem is not with the documentation. > >It's with the name. > > Documentation is not the only factor. The name was chosen for a *reason*, > to convey a point. It's choice was not arbitrary. Is this from experience or are you guessing? > And it's since been > accepted by the development and administrative community. The people already on the project understand. They have been "indoctrinated" for lack of a better term. It's the new people which have the trouble. Perhaps with a better name that trouble could be easily avoided. > Question being: Now, are we to a point where that accepted name needs > to be reevaluated for the sake of general consensus, need or desire. > That's the real question, IMHO. I think so. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 10:35:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from khan.acc.umu.se (khan.acc.umu.se [130.239.18.139]) by hub.freebsd.org (Postfix) with ESMTP id 4813737B42C for ; Mon, 9 Apr 2001 10:35:47 -0700 (PDT) (envelope-from markush@acc.umu.se) Received: from mao.acc.umu.se (root@mao.acc.umu.se [130.239.18.154]) by khan.acc.umu.se (8.11.2/8.11.2) with ESMTP id f39HZjc03717; Mon, 9 Apr 2001 19:35:45 +0200 (MEST) Received: (from markush@localhost) by mao.acc.umu.se (8.9.3/8.9.3/Debian 8.9.3-21) id TAA27063; Mon, 9 Apr 2001 19:35:44 +0200 Date: Mon, 9 Apr 2001 19:35:44 +0200 From: Markus Holmberg To: Christopher Schulte Cc: Matthew Emmerton , Rasputin , stable@FreeBSD.ORG Subject: Re: Releases Message-ID: <20010409193544.A25126@acc.umu.se> References: <030e01c0c0fb$52b2fcc0$340410ac@JRAFTERY> <200104091358.JAA13889@sjt-u10.cisco.com> <20010409154800.A24937@dogma.freebsd-uk.eu.org> <001b01c0c106$a897f770$1200a8c0@gsicomp.on.ca> <5.0.2.1.0.20010409101533.00ace930@pop.schulte.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3-current-20000511i In-Reply-To: <5.0.2.1.0.20010409101533.00ace930@pop.schulte.org>; from christopher@schulte.org on Mon, Apr 09, 2001 at 10:26:50AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 09, 2001 at 10:26:50AM -0500, Christopher Schulte wrote: > > Change the designation just because some admins don't know how to RTFM? I > don't think so... They fu*ked up. Plain and simple. -CURRENT makes sense, > and more importantly is documented for those who take the time to look. With self-documenting labels documentation becomes unnecessary. Markus -- Markus Holmberg | Give me Unix or give me a typewriter. markush@acc.umu.se | http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 10:39:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.unixathome.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 2DCF437B422 for ; Mon, 9 Apr 2001 10:39:14 -0700 (PDT) (envelope-from dan@langille.org) Received: from xeon (xeon.int.nz.freebsd.org [192.168.0.18]) by ns1.unixathome.org (8.11.3/8.11.3) with ESMTP id f39Hcje73052; Tue, 10 Apr 2001 05:38:45 +1200 (NZST) (envelope-from dan@langille.org) Date: Tue, 10 Apr 2001 05:38:45 +1200 (NZST) From: Dan Langille X-X-Sender: To: "Michael R. Rudel" Cc: Christopher Schulte , Matthew Emmerton , Rasputin , Subject: Re: Releases In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Apr 2001, Michael R. Rudel wrote: > [... SNIP ...] > > Personally, I don't see a problem with the -CURRENT and -STABLE naming > scheme. As someone said, anybody who can CVSup (not to mention get the > sample CVSup files to work off of) yet not read the rest of the > documentation has other issues. Renaming -CURRENT to -DEV or -DEVEL would > be the equivlent of dulling all the knives in your house so that people > don't cut themselves. A poor analogy. A better one would be labelling the knife drawer something other than knives. > Changing the whole > release process of something that has worked for years isn't going to help > anything Nothing has been suggested about change the *process*. AFAIK, we're talking about the name. Not the process >, people are always going to be confused if you change it - if you > suddenly change the way this shit is named, I'm going to be confused when > 4.4 comes around or whatever. Said confusion, if any, would be temporary and well announced. What is being proposed is a name which helps new people out and which will still make sense long after they've joined te project. > Just chill, and instruct people to Read The > Fine Manual. AFAIK, everyone is chilled. As for discarding the issue with a RTFM, that's avoiding the issue altogether and will not achieve anything. Reasoned discussion, whch is what I thought we were doing, will. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 10:39:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from chmod.ath.cx (CC2-1242.charter-stl.com [24.217.116.226]) by hub.freebsd.org (Postfix) with ESMTP id 2981437B422 for ; Mon, 9 Apr 2001 10:39:32 -0700 (PDT) (envelope-from ajh3@chmod.ath.cx) Received: by chmod.ath.cx (Postfix, from userid 1001) id 2F1B4A91F; Mon, 9 Apr 2001 12:38:49 -0500 (CDT) Date: Mon, 9 Apr 2001 12:38:49 -0500 From: Andrew Hesford To: David Wolfskill Cc: stable@FreeBSD.ORG Subject: Re: Disklabel 101? Message-ID: <20010409123849.A3315@cec.wustl.edu> References: <000001c0bfd9$3b96a230$1201a8c0@sanmik.com> <200104091616.f39GGpb72064@pau-amma.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <200104091616.f39GGpb72064@pau-amma.whistle.com>; from dhw@whistle.com on Mon, Apr 09, 2001 at 09:16:51AM -0700 X-Loop: Andrew Hesford Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 09, 2001 at 09:16:51AM -0700, David Wolfskill wrote: > OK, since folks are comparing unusual disk layouts, here's one I've been > using on my laptop for the last few weeks (since I got it). Now, this > isn't something that you can tell sysinstall to do directly; more about > that should be at http://www.catwhisker.org/~david/FreeBSD/laptop.html. > > It should also be understood that I'm tracking both -CURRENT and -STABLE > on the machine; that I'm working (as time permits) on some code that > will permit the space pointed to by the 4th MBR "partition table" entry > to be used as a "suspend to disk partition". I just finished building > -CURRENT for today, and did the multi-user boot, so that's what it's > running at the moment. (I'll probably switch to today's -STABLE shortly > after posting this.) > > As in Mike's case, I share the swap space among the kernels; I also share > /var and /common -- basically, everything on what the 3rd "partition tabel" > entry points to. /common is where /usr/local points, as well as /home. > And /usr/obj in each case is a symlink to /common/*/obj (where "*" is one > of "C", "S1", or "S2"). /common/cvs is where I keep my CVS repository. > > It seems to be working OK for me so far. :-) > Well, I'll throw my config in the ring too. My 20G drive is sliced in two, with s1 being 7.5G, and s2 being as large as the rest of the drive. On s2, I have a 250M /, 200M /var, 100M swap, and the remainder (about 10G) as /usr. s1 contains only one partition, /usr/home on ad0s1a. I never saw the need for a separate /tmp, especially since every partition has soft updates enabled. /usr/home is located elsewhere because I switched to FreeBSD from Linux, and I wanted to devote my entire disk to FreeBSD. When I had Linux across the entire drive, I packed it into the first 7.5G, made a BSD slice in the upper region of the drive, installed it, copied my data over from Linux, wiped out Linux, turned the free space into s1, and made that /usr/home. It needs to be 7G for my MP3s. :) I like this. Since /usr always has about 7-8G free, any time I need a new operating system, all I need to do is move /usr/home onto /usr¸ and I have 7G to play with. -- Andrew Hesford ajh3@chmod.ath.cx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 10:50: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.unixathome.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 958B937B422 for ; Mon, 9 Apr 2001 10:49:57 -0700 (PDT) (envelope-from dan@langille.org) Received: from xeon (xeon.int.nz.freebsd.org [192.168.0.18]) by ns1.unixathome.org (8.11.3/8.11.3) with ESMTP id f39Hnre73105; Tue, 10 Apr 2001 05:49:53 +1200 (NZST) (envelope-from dan@langille.org) Date: Tue, 10 Apr 2001 05:49:53 +1200 (NZST) From: Dan Langille X-X-Sender: To: Jordan Hubbard Cc: Subject: Re: Releases In-Reply-To: <20010409102526S.jkh@osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Apr 2001, Jordan Hubbard wrote: > > By this designation, we could call a brake a clutch and get away with it > > because it's all documented. The problem is not with the documentation. > > It's with the name. > > That's a nice pat answer, but the problem is that for every value of > "name" we propose, somebody comes forward and says "But that confuses > me." We can't call it BETA, we can't call it STABLE, we can't call it > RC, we can't call it PRERELEASE, because each and every one of those > have had push-back from people who said it would conflict with > previous definitions they hold dear. Given that, chances are > excellent that any other halfway logical names we come up with will > suffer from the same problem. Just because the problem is difficult to solve does not mean it can not be or should not be solved. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 10:52:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 3D2BE37B424 for ; Mon, 9 Apr 2001 10:52:31 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f39HqN811151; Mon, 9 Apr 2001 10:52:23 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: dan@langille.org Cc: stable@FreeBSD.ORG Subject: Re: Releases In-Reply-To: References: <20010409102526S.jkh@osd.bsdi.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010409105223C.jkh@osd.bsdi.com> Date: Mon, 09 Apr 2001 10:52:23 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 7 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just because the problem is difficult to solve does not mean it can not be > or should not be solved. Fine, how about you solve it and the rest of us will get back to all the other stuff we have on our plates. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 10:57:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.unixathome.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 8AA8A37B423 for ; Mon, 9 Apr 2001 10:57:07 -0700 (PDT) (envelope-from dan@langille.org) Received: from xeon (xeon.int.nz.freebsd.org [192.168.0.18]) by ns1.unixathome.org (8.11.3/8.11.3) with ESMTP id f39Hv4e73133; Tue, 10 Apr 2001 05:57:04 +1200 (NZST) (envelope-from dan@langille.org) Date: Tue, 10 Apr 2001 05:57:04 +1200 (NZST) From: Dan Langille X-X-Sender: To: Jordan Hubbard Cc: Subject: Re: Releases In-Reply-To: <20010409105223C.jkh@osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Apr 2001, Jordan Hubbard wrote: > > Just because the problem is difficult to solve does not mean it can not be > > or should not be solved. > > Fine, how about you solve it and the rest of us will get back to all > the other stuff we have on our plates. :) OK. But if you didn't want to be involved in the first place, you should have stayed out of it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 11:15:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 1DAAC37B422 for ; Mon, 9 Apr 2001 11:15:35 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f39IFR811298; Mon, 9 Apr 2001 11:15:27 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: dan@langille.org Cc: stable@FreeBSD.ORG Subject: Re: Releases In-Reply-To: References: <20010409105223C.jkh@osd.bsdi.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010409111527V.jkh@osd.bsdi.com> Date: Mon, 09 Apr 2001 11:15:27 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 14 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > OK. But if you didn't want to be involved in the first place, you > should have stayed out of it. [Best "cool hand Luke" voice] "Son, what we have here is a failure to communicate!" The fact that I think this is a waste of time and you're on a fool's errand is certainly something I'm free to communicate. The fact that I feel that way is also good reason for me to suggest that you do the work if you're hell-bent on proving me wrong - that's a time-honored and more than acceptable way of delivering your rebuttal. I have been as "involved" in this discussion as I needed to be, thanks. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 11:15:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dns3.solo.net (dns3.solo.net [64.23.2.19]) by hub.freebsd.org (Postfix) with ESMTP id A469037B422 for ; Mon, 9 Apr 2001 11:15:48 -0700 (PDT) (envelope-from dak@solo.net) Received: from solo.net (vip0 [64.23.2.19]) by dns3.solo.net (8.11.3/8.11.3) with SMTP id f39IFGm93151; Mon, 9 Apr 2001 14:15:18 -0400 (EDT) (envelope-from dak@solo.net) Received: from corp.namesafe.com ([209.141.226.130]) (proxying for 10.0.0.10) (SquirrelMail authenticated user dak) by www.solo.net with HTTP; Mon, 9 Apr 2001 14:15:22 -0400 (EDT) Message-ID: <1214.209.141.226.130.986840122.squirrel@www.solo.net> Date: Mon, 9 Apr 2001 14:15:22 -0400 (EDT) Subject: Re: Releases From: "David A. Koran" To: In-Reply-To: References: Cc: , Reply-To: dak@solo.net X-Mailer: SquirrelMail (version 1.1.0 [cvs]) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan (and all), Jordan does have a point though. I've noticed that there are a lot of people delving into CVSup'ed updates way before really understanding the consequences of what being "up to date" can cause. Jordan's point about the CVS tree and development always being in a state of flux holds very true and anybody willing to try to keep up should be aware of that fact. Now, obviously there is an argument for when CVS has major bug fixes and security patches, but at least for the security side of things, the SA's usually offer a patch diff file that can be applied to the source to fix the hole.If anybody plans on keeping on the "bleeding edge" (granted not following -CURRENT) they should know that depending on when they CVSup their tree, they get different snapshots. A solution, for those that seem to need their releases, is to truly do "snapshots" the way many ports get their sources (Postfix, Cyrus, etc.). I know the whole RC idea and BETA labelling gets people confused at times, but if you notice the build has those labels, you may want to think twice about typing the "make installworld" command. There are a lot of shops that will only run releases, and will only upgrade to their own "snapshots" after a load of internal testing. A possible offering, is to have some of those shops offer some of their own certification (via a TEXT document specifiying what works and what doesn't during a snapshot release) that a given release works and give back to community. Unless their is a formal QA process followed or FreeBSD sets up a testing lab, this is probably the best we can hope for. David A. Koran > On Mon, 9 Apr 2001, Jordan Hubbard wrote: > >> > Just because the problem is difficult to solve does not mean it can >> > not be or should not be solved. >> >> Fine, how about you solve it and the rest of us will get back to all >> the other stuff we have on our plates. :) > > OK. But if you didn't want to be involved in the first place, you > should have stayed out of it. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 11:21: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from flip.tenbit.pl (flip.tenbit.pl [195.205.163.234]) by hub.freebsd.org (Postfix) with ESMTP id 6708637B424 for ; Mon, 9 Apr 2001 11:20:59 -0700 (PDT) (envelope-from przemek@flip.tenbit.pl) Received: (from przemek@localhost) by flip.tenbit.pl (8.9.3/8.9.3) id UAA03404 for freebsd-stable@freebsd.org; Mon, 9 Apr 2001 20:16:17 +0200 From: Przemyslaw Brojewski Message-Id: <200104091816.UAA03404@flip.tenbit.pl> Subject: Re: Releases To: freebsd-stable@freebsd.org Date: Mon, 9 Apr 101 20:16:17 +0200 (CEST) In-Reply-To: <20010409193544.A25126@acc.umu.se> from "Markus Holmberg" at Apr 9, 1 07:35:44 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Change the designation just because some admins don't know how to RTFM? I > > don't think so... They fu*ked up. Plain and simple. -CURRENT makes sense, > > and more importantly is documented for those who take the time to look. > > With self-documenting labels documentation becomes unnecessary. > There's not such thing as self-documenting labels. I see no reason to changing the names. I'm new to FreeBSD, some three weeks, or so. I spent 5 minutes reading the handbook, to learn that -CURRENT is not for me. But for the masses, reading is a pain. They do not read. Period. For people who do not read, evrything is the problem, so why bother? So my solution would be to refer them to the docs, and if they don't follow -- filter them :-) Or else change the naming, and have the names duplicated, another source of confusion. brojek. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 11:22:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.altadena.net (ns.altadena.net [206.126.144.2]) by hub.freebsd.org (Postfix) with ESMTP id 3003737B42C for ; Mon, 9 Apr 2001 11:22:45 -0700 (PDT) (envelope-from pete@ns.altadena.net) Received: (from pete@localhost) by ns.altadena.net (8.11.3/8.8.8) id f39IJ7Z43613 for stable@freebsd.org; Mon, 9 Apr 2001 11:19:07 -0700 (PDT) (envelope-from pete) From: Pete Carah Message-Id: <200104091819.f39IJ7Z43613@ns.altadena.net> Subject: vinum breakage To: stable@freebsd.org Date: Mon, 9 Apr 2001 11:19:07 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=iso8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With a cvsup this morning, I get p_intr_nesting_level undefined compiling vinum in the kernel. This appears to not affect the compiling of the module, possibly because the module has VINUMDEBUG defined?. I got around it with #if __FreeBSD_version < 500000 but don't know what the right flag is for stability in 4-stable... -- Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 11:32:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.unixathome.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 2837037B422 for ; Mon, 9 Apr 2001 11:32:38 -0700 (PDT) (envelope-from dan@langille.org) Received: from xeon (xeon.int.nz.freebsd.org [192.168.0.18]) by ns1.unixathome.org (8.11.3/8.11.3) with ESMTP id f39IWFe73318; Tue, 10 Apr 2001 06:32:31 +1200 (NZST) (envelope-from dan@langille.org) Date: Tue, 10 Apr 2001 06:32:15 +1200 (NZST) From: Dan Langille X-X-Sender: To: Jordan Hubbard Cc: Subject: Re: Releases In-Reply-To: <20010409111527V.jkh@osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Apr 2001, Jordan Hubbard wrote: > > OK. But if you didn't want to be involved in the first place, you > > should have stayed out of it. > > [Best "cool hand Luke" voice] "Son, what we have here is a failure to > communicate!" > > The fact that I think this is a waste of time and you're on a fool's > errand is certainly something I'm free to communicate. I just wish you'd said that in the first place! Yeah, I know you did, but in far many more words. > The fact that > I feel that way is also good reason for me to suggest that you do the > work if you're hell-bent on proving me wrong - that's a time-honored > and more than acceptable way of delivering your rebuttal. I have > been as "involved" in this discussion as I needed to be, thanks. AFAIK, the thread to date has been about whether or not [something like] the label "-development" would cause less confusion than "-current". My objective is not to prove anyone wrong or right but to solve a problem which occurs again and again. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 11:37:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.unixathome.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id C8D4F37B423 for ; Mon, 9 Apr 2001 11:37:27 -0700 (PDT) (envelope-from dan@langille.org) Received: from xeon (xeon.int.nz.freebsd.org [192.168.0.18]) by ns1.unixathome.org (8.11.3/8.11.3) with ESMTP id f39Iaoe73335; Tue, 10 Apr 2001 06:36:50 +1200 (NZST) (envelope-from dan@langille.org) Date: Tue, 10 Apr 2001 06:36:50 +1200 (NZST) From: Dan Langille X-X-Sender: To: Przemyslaw Brojewski Cc: Subject: Re: Releases In-Reply-To: <200104091816.UAA03404@flip.tenbit.pl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Apr 101, Przemyslaw Brojewski wrote: > > > Change the designation just because some admins don't know how to RTFM? I > > > don't think so... They fu*ked up. Plain and simple. -CURRENT makes sense, > > > and more importantly is documented for those who take the time to look. > > > > With self-documenting labels documentation becomes unnecessary. > > > There's not such thing as self-documenting labels. Sure there are. You see them everyday. On example :push: on a door. > Or else change the naming, and have the names duplicated, > another source of confusion. What duplication? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 12: 4:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from flip.tenbit.pl (flip.tenbit.pl [195.205.163.234]) by hub.freebsd.org (Postfix) with ESMTP id BA02A37B422 for ; Mon, 9 Apr 2001 12:03:58 -0700 (PDT) (envelope-from przemek@flip.tenbit.pl) Received: (from przemek@localhost) by flip.tenbit.pl (8.9.3/8.9.3) id UAA06664 for freebsd-stable@freebsd.org; Mon, 9 Apr 2001 20:59:18 +0200 From: Przemyslaw Brojewski Message-Id: <200104091859.UAA06664@flip.tenbit.pl> Subject: Re: Releases To: freebsd-stable@freebsd.org Date: Mon, 9 Apr 101 20:59:18 +0200 (CEST) In-Reply-To: from "Dan Langille" at Apr 10, 1 06:36:50 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > With self-documenting labels documentation becomes unnecessary. > > > > > There's not such thing as self-documenting labels. > > Sure there are. You see them everyday. On example :push: on a door. But why running FreeBSD should be as simple task as pushing the door open? What usefull would you be able to do with such a system (aside from pushing the door open, of course) > > Or else change the naming, and have the names duplicated, > > another source of confusion. > > What duplication? Think a while: ---- begin of a dark forecast ----- Subject: Why my 3d-mouse-glove doesn't work in -DEVEL ? ::: Hi, I've just bought my new superb 3d-mouse-glove, and it doesn't ::: work!!!!!! I'm running 7.1-RELEASE-GAMMA-STABLE with all the fixes, ::: and it sais no such device or sumthing... So I get the ::: -DEVEL and no change.. still not working. So I tried -CURRENT, ::: and no better.. I even rebuilt the world!!!! Is there any other ::: version of FreeBSD, maybe -LATEST, where my 3d-mouse-glove will ::: work? I tried CVSup -LATEST, but got an error... Where can I download ::: -LATEST from? :: Hello. 3d-mose-glove is not supported yet. There is no such thing as :: -RELEASE-GAMMA-STABLE. its either -RELEASE or -GAMMA or -STABLE, :: or -DEVEL. -CURRENT has been dropped 3 years ago. There's no such :: thing as -LATEST either. Read the handbook. : What? But I have to use my 3d-mouse-glove with FreeBSD!!!, Where can : I gate -LATEST from?????????? ---- end of a dark forecast ---- And so on.... nothing is going to solve that kind of problems. You may invent new names, and have the situation go worse. brojek. PS. I think EOT. Nothing good is going to come out of this thread. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 12:11:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 1CC4337B424 for ; Mon, 9 Apr 2001 12:11:51 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id MAA32457; Mon, 9 Apr 2001 12:11:03 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200104091911.MAA32457@gndrsh.dnsmgr.net> Subject: Re: Releases In-Reply-To: from Dan Langille at "Apr 10, 2001 06:36:50 am" To: dan@langille.org (Dan Langille) Date: Mon, 9 Apr 2001 12:11:02 -0700 (PDT) Cc: przemek@my.tenbit.pl (Przemyslaw Brojewski), freebsd-stable@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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 9 Apr 101, Przemyslaw Brojewski wrote: > > > > > Change the designation just because some admins don't know how to RTFM? I > > > > don't think so... They fu*ked up. Plain and simple. -CURRENT makes sense, > > > > and more importantly is documented for those who take the time to look. > > > > > > With self-documenting labels documentation becomes unnecessary. > > > > > There's not such thing as self-documenting labels. > > Sure there are. You see them everyday. On example :push: on a door. And how many times have you mistakenly pulled on that door so labeled?? If you say zero, you sould probably think about it harder. If you go, hummm, yep, even with stuff that has ``self-docuemnting labels'' some people just don't read them and will :pull: when it clearly says :push:. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 12:13:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fremont.bolingbroke.com (adsl-216-102-90-210.dsl.snfc21.pacbell.net [216.102.90.210]) by hub.freebsd.org (Postfix) with ESMTP id D1E3F37B424 for ; Mon, 9 Apr 2001 12:13:28 -0700 (PDT) (envelope-from freebsd@bolingbroke.com) Received: from fremont.bolingbroke.com (fremont.bolingbroke.com [216.102.90.210]) by fremont.bolingbroke.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f39JDSU47292 for ; Mon, 9 Apr 2001 12:13:28 -0700 (PDT) Date: Mon, 9 Apr 2001 12:13:28 -0700 (PDT) From: Ken Bolingbroke To: freebsd-stable@FreeBSD.ORG Subject: Re: Releases In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Apr 2001, Dan Langille wrote: > On Mon, 9 Apr 101, Przemyslaw Brojewski wrote: > > > There's not such thing as self-documenting labels. > > Sure there are. You see them everyday. On example :push: on a door. I'd say that's more of an instruction than a label. But regardless of such nit-picking, even if we can think of a self-documenting label, it's going to be something simple enough to be contained within a small label. The nature of the various branches and the stages of those branches pretty much guarantee that you can't find a self-documenting label for those, because they're just too complex. (Feel free to prove me wrong, tho :-) There are different situations under which I would run -RELEASE instead of -STABLE, as well as other situations where I might run RELENG_3 instead of RELENG_4. But they're complex, requiring an understanding of each branch, their stages, and so forth. To understand which I need, it requires due process in reading the documentation and following the mailing lists. As has been said all too many times, if someone is NOT going to read the documentation, they're going to have trouble, period. Changing the labels just to delay their troubles a bit longer doesn't really help anyone. At best, if they _must_ change, I'd say change them to something totally unrelated. -STABLE becomes -MARS, -CURRENT becomes -JUPITER, etc. Having no inherent meaning would force (or am I too optimistic?) people to read the docs to find the meaning rather than making likely flawed assumptions as to what they mean. But I'd rather they not change at all. The current system _is_ logical, even if it takes a bit of time to grok it. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 12:16:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 1EBA537B424 for ; Mon, 9 Apr 2001 12:16:32 -0700 (PDT) (envelope-from Gerhard.Sittig@gmx.net) Received: (qmail 16021 invoked by uid 0); 9 Apr 2001 19:16:30 -0000 Received: from pd9508858.dip.t-dialin.net (HELO speedy.gsinet) (217.80.136.88) by mail.gmx.net (mp025-rz3) with SMTP; 9 Apr 2001 19:16:30 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id UAA20161; Mon, 9 Apr 2001 20:51:31 +0200 Date: Mon, 9 Apr 2001 20:51:31 +0200 From: Gerhard Sittig To: stable@freebsd.org Subject: Re: Disklabel 101? Message-ID: <20010409205131.V20830@speedy.gsinet> Mail-Followup-To: stable@freebsd.org References: <003101c0c0ed$a4c0ba10$1201a8c0@sanmik.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <003101c0c0ed$a4c0ba10$1201a8c0@sanmik.com>; from mike@dad.state.vt.us on Mon, Apr 09, 2001 at 08:07:25AM -0400 Organization: System Defenestrators Inc. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 09, 2001 at 08:07 -0400, Mike Barton wrote: > > I think the problem is that that you can't have the root > partition past the 1024 logical cylinder due to BIOS issues - I > surely would've liked to have been in on wrting that piece of > code! Which reminds me of my question I've been having for quite a few months now: Is it something essential in the mechanism or is it only sysinstall what prevents an arrangement like this: ad0s1a 64M / for the "normal" system ad0s2a 128M one "huge" fs (including /) for a rescue/maint. system ad0s3x rest "normal" swap, /usr, /var, /home, /tmp [ "small" sizes for really really really fitting into the first few cylinders under any mapping the BIOS might want to choose today, and swap ad0s[12] as you please -- it doesn't matter ] When I go and do an installation on ad0s1 and ad0s3 everything is fine. When I start the second round of installation for the rescue system I'm rejected when wanting to create the rescue's root in ad0s2. When starting with installing into ad0s2a and using ad0s3b for swap everything's fine, too -- which makes me sure about ad0s2a being a valid root partition wrt geometry and stuff. But then installing the actual system is impossible since sysinstall won't let me put its root into ad0s1. So who's the one telling me that I *cannot* create or mount a root (/) partition when there's already an "a" partition in _any_ slice of this disk? Putting the rescue system's root on another disk like ad1sNa works -- *if* one is lucky enough to have a second disk around. :> As well as installing in different order will cause the same problem and proves ad0s2 to not be the real problem. Since there's a boot manager to start one of the slices and every slice I would jump into would have a valid root partition in "a" I feel my wish to be not too silly. :) Unless I missed something important or obvious somebody can tell me and other subscribers who too want a rescue/maint. system next to the real system. Admittedly I'll have to go through it once more and provide a clear step by step instruction for those who want to reproduce it, combined with the real messages I get instead of writing from the top of my head (I only remember that the message popping up didn't tell me too much besides "you cannot do this"). But the inability to put a maintenance companion next to the regular system really is a pity. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 12:30:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 8445137B422 for ; Mon, 9 Apr 2001 12:30:51 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id wmvaaaaa for ; Tue, 10 Apr 2001 05:30:14 +1000 Message-ID: <3AD20ECC.5A895124@quake.com.au> Date: Tue, 10 Apr 2001 05:34:36 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Rodney W. Grimes" Cc: Dan Langille , Przemyslaw Brojewski , freebsd-stable@FreeBSD.ORG Subject: Re: Releases References: <200104091911.MAA32457@gndrsh.dnsmgr.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Rodney W. Grimes" wrote: > > > On Mon, 9 Apr 101, Przemyslaw Brojewski wrote: > > > > > > > Change the designation just because some admins don't know how to RTFM? I > > > > > don't think so... They fu*ked up. Plain and simple. -CURRENT makes sense, > > > > > and more importantly is documented for those who take the time to look. > > > > > > > > With self-documenting labels documentation becomes unnecessary. > > > > > > > There's not such thing as self-documenting labels. > > > > Sure there are. You see them everyday. On example :push: on a door. > > And how many times have you mistakenly pulled on that door so labeled?? > If you say zero, you sould probably think about it harder. If you go, > hummm, yep, even with stuff that has ``self-docuemnting labels'' some > people just don't read them and will :pull: when it clearly says :push:. Very very true! There is a door where I work, that will open both ways, but one way it doesnt close properly again and damages the wall... There is a clear sign near the handle saying PUSH and PULL on the correct sides, but people just cant help continually doing it the wrong way!!! The only solution would be to stop the door from going both ways... There is nothing wrong with the current label system... As it has been said RTFM!!! Its not a hard concept to grasp, there are thousands of people that understand it just fine, for those few that dont it wouldnt matter what labels you used they would still not understand... Since there is no problem to be solved here, lets kill this thread and get on with more important things... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 12:55:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id E81D237B422 for ; Mon, 9 Apr 2001 12:55:20 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id OAA29017; Mon, 9 Apr 2001 14:55:08 -0500 (CDT) (envelope-from jeff-ml@mountin.net) Received: from dial-42.tnt1.rac.cyberlynk.net(209.224.182.42) by peak.mountin.net via smap (V1.3) id sma029015; Mon Apr 9 14:55:05 2001 Message-Id: <4.3.2.20010409140550.0299a240@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Mon, 09 Apr 2001 14:54:39 -0500 To: Jordan Hubbard , dan@langille.org From: "Jeffrey J. Mountin" Subject: Re: Releases Cc: stable@FreeBSD.ORG In-Reply-To: <20010409111527V.jkh@osd.bsdi.com> References: <20010409105223C.jkh@osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:15 AM 4/9/01 -0700, Jordan Hubbard wrote: > > OK. But if you didn't want to be involved in the first place, you > > should have stayed out of it. > >[Best "cool hand Luke" voice] "Son, what we have here is a failure to >communicate!" > >The fact that I think this is a waste of time and you're on a fool's >errand is certainly something I'm free to communicate. The fact that >I feel that way is also good reason for me to suggest that you do the >work if you're hell-bent on proving me wrong - that's a time-honored >and more than acceptable way of delivering your rebuttal. I have >been as "involved" in this discussion as I needed to be, thanks. I'll agree and add that no matter the name, there will always be perception problem. Could say those that don't like the naming scheme that has been around for ages and having someone that comes in wanting to change it, which will (most likely) do nothing to enhance the perception of what it really is. If (l)users still don't read the docs before tracking stable... I'd suggest that this move to -chat or -docs, as it has nothing to do with tracking -stable and ask those on the list to refrain from discussing this every friggin week and learn the value of a *private* reply and avoid dragging everyone on the list into OT discussion. It's all fine and dandy to be helpful. Just wish more of the newer folks here would show a little restraint and drop -stable from the reply when dealing with issues that clearly don't have anything to do with tracking the -stable branch. And before anyone breaks out their flame throwers, consider how many questions in this past week had nothing to do with tracking -stable and should have been posted to other lists or even better, a private reply with a suggestion to check out the archives for commonly asked and answered questions on the appropriate list. As a matter of perception, those that complain they don't want to track "another" list more appropriate for their question, should then consider that tracking -stable involves a bit of work. And if reading is such a chore should consider that being someone that tracks -stable is like being part of the design/testing team and if you aren't willing to follow the developments. Rather tired of questions on -stable that first should be on -ports and almost anything with "I'm looking for" doesn't belong here. Perhaps it is the desire to have one list that covers everything. My perception is that this list is becoming that and -ports traffic has dropped or is mostly interportmeister traffic and PR's. FWIW - Had the thought of making a list the other day when I cleaned out a week's worth of mail. Figured there were better things to do with my time. A better S/N ratio here would benefit everyone, so do perceive this as a call for everyone on the list, active or not, to show a little restraint and consideration to what this list is supposed to be about and still help those that need it, privately if need be. One more thing that drove me nuts when cleaning out a zillion messages. If you post a question and follow-up, a suggestion would be to place the "sovled/solution/patch/etc." at the *end* of the subject. And if you don't get an answer within 5 minutes, don't post another with a different subject or keep changing it when the essence hasn't changed. Not to point any fingers, but some might call him "Bob" who will receive some bar-b-que sauce for when the flames go out as a consolation prize. Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 12:59:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id 8C8E137B422 for ; Mon, 9 Apr 2001 12:59:20 -0700 (PDT) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.11.3) with SMTP id f39JvVR23639 for ; Mon, 9 Apr 2001 15:57:31 -0400 (EDT) (envelope-from matt@gsicomp.on.ca) Message-ID: <014a01c0c12e$e5e76f20$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" Cc: References: Subject: Re: Releases Date: Mon, 9 Apr 2001 15:54:32 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's a good thing that I put my flame-retardant suit on this morning before I checked my e-mail. I hadn't expected this much debate about the naming. The basis consensus of the group has been that -CURRENT and -STABLE are well-established, mean the appropriate things to the appropriate people, and are self-documenting enough for those who need to know, but also that there exists a requirement for documentation to be improved in certain areas. In the case of people running -CURRENT on a production machine, that's just a plain and simple mistake. Ever wonder how someone who barely knows how to use cvsup and make world manages to obtain -CURRENT in the first place? Most of the time these people have only used cvsup to sync the ports tree - which uses "tag=.". They figure that getting the most recent source code would be the same, and do so. Unfortunately, they end up with -CURRENT instead of the latest -RELEASE. Here the problem isn't with cvsup, but rather a lack of knowledge about CVS and the concept of tags. RTFM is the solution (section 18 and appendix A in particular.) This said, I retract my suggestion that -DEV replace -CURRENT, since it wouldn't make a difference. Next, the case of -STABLE/-BETA/-RC/-RELEASE. I still maintain that -BETA is confusing to the newbie (since due to M$, betas of IE were more like pre-alphas and totally trashed most systems and rightly freak out most novice admins), while STABLE/RC/RELEASE just makes sense. However, this isn't in the handbook and should be, so that people on the list can say "go to handbook/release-process.html" and people unfamiliar with our release process will become enlightened. Next, the case of the bind and ntpd updates. Yes, these were fixed in -STABLE and -CURRENT very quickly, but were only documented in UPDATING. How many people who are running -RELEASE have this? That's right, none. If the "current release" box had an "Newsflash" or other such link to inform users of 1) critical bugs that exist in the current release, and 2) HOWTOs that show how to fix them, then a lot of the confusion surrounding these fixes would be resolved. Finally, almost every newbie I see asking a question asks "how can I do this on FreeBSD, and where is the HOWTO- to help me?" Most often these people are redirected to offsite repositories of information, rather than the documentation included with FreeBSD. IMHO, this contributes to the degradation of the existing documentation of FreeBSD, as more effort will go into updating third-party sources. The summary? If we can accurately answer newbie's questions with solid documentation (rather than everyone's pet solution in the lists), then we are "teaching a newbie to read", and will hopefully have to service fewer requests from that newbie in the future. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 13:18:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gsaix2.cc.GaSoU.EDU (gsaix2.cc.GaSoU.edu [141.165.1.57]) by hub.freebsd.org (Postfix) with ESMTP id 20C3F37B422 for ; Mon, 9 Apr 2001 13:18:38 -0700 (PDT) (envelope-from gsi22419@gsaix2.cc.GaSoU.EDU) Received: from localhost (gsi22419@localhost) by gsaix2.cc.GaSoU.EDU (8.9.2/8.9.2) with SMTP id QAA41272 for ; Mon, 9 Apr 2001 16:15:47 -0400 Date: Mon, 9 Apr 2001 16:15:45 -0400 (EDT) From: Scott Dodson To: stable@freebsd.org Subject: Re: Releases In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why not write some rather intuitive scripts to weed our this particular question which seems to be asked about once a day during code freeze times? Simply Autoreply with a nice note to read the docs, or repost if that didnt' answer their question. -- scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 13:27:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from web13203.mail.yahoo.com (web13203.mail.yahoo.com [216.136.174.188]) by hub.freebsd.org (Postfix) with SMTP id 81B6037B423 for ; Mon, 9 Apr 2001 13:27:41 -0700 (PDT) (envelope-from lipshitz909@yahoo.com) Message-ID: <20010409202741.62571.qmail@web13203.mail.yahoo.com> Received: from [169.139.124.27] by web13203.mail.yahoo.com; Mon, 09 Apr 2001 13:27:41 PDT Date: Mon, 9 Apr 2001 13:27:41 -0700 (PDT) From: Larry Librettez Subject: 100% CPU usage with xmms To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've run into an annoying problem with xmms. Occasionally when I start xmms, even before playing any mp3's, CPU use approaches 100%. top shows xmms as the offender, with xmms hogging up about 90% CPU, just sitting there even before I play an mp3. Even worse, to stop xmms I must issue kill -9 xmms or else it just keeps on going! I've updated my xmms port to the latest and still this occurs. This occurs on my 4.3-RC2 systems, both laptop and desktop. The laptop runs a maestro3 soundcard and the desktop has a plain SB 16. The sound itself is fine, it's just the 100% annoying excess CPU useage! Has anyone else noticed this, and can this be fixed? __________________________________________________ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 13:40:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from snoop.burghcom.com (burgcom.cust.stargate.net [209.166.166.21]) by hub.freebsd.org (Postfix) with SMTP id 8051237B423 for ; Mon, 9 Apr 2001 13:40:13 -0700 (PDT) (envelope-from jl@burghcom.com) Received: (qmail 76000 invoked from network); 9 Apr 2001 20:40:12 -0000 Received: from merlin.hq.sgi.net (HELO merlin) (jl@209.166.162.10) by snoop.burghcom.com with SMTP; 9 Apr 2001 20:40:12 -0000 From: Jeff Love To: freebsd-stable@freebsd.org Subject: Re: Releases Date: Mon, 9 Apr 2001 16:29:00 -0400 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <200104091859.UAA06664@flip.tenbit.pl> In-Reply-To: <200104091859.UAA06664@flip.tenbit.pl> MIME-Version: 1.0 Message-Id: <01040916401600.22539@merlin> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is my first post to this list. I've been running FreeBSD since 2.2.7, and have never had a problem understanding the difference between -STABLE, -RELEASE, etc. I have an older server that I cvsup first to see just how well the upgrade goes, and how the new system runs, before upgrading the production server. What surprises me is that the members of this list seem to like to quarrel over this subject (and others?). I did have a problem after a cvsup on 04/08/2001, as the 'cim' sound kernel module would not compile. I eliminated the subdirectory listing in the Makefile, and it simply did not attempt to compile the module. Why was the kernel make compiling modules for devices I did not set in my config? I suppose I'm either missing something, or I need to RTFM over again... -- Jeff Love jl@burghcom.com ----------------- Burgh-Com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 13:43:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from moek.pir.net (moek.pir.net [130.64.1.215]) by hub.freebsd.org (Postfix) with ESMTP id 91F8E37B43E for ; Mon, 9 Apr 2001 13:43:49 -0700 (PDT) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 14miVo-0005Ny-00 for freebsd-stable@freebsd.org; Mon, 09 Apr 2001 16:43:48 -0400 Date: Mon, 9 Apr 2001 16:43:48 -0400 From: Peter Radcliffe To: freebsd-stable@freebsd.org Subject: Re: Releases Message-ID: <20010409164348.H14079@pir.net> Reply-To: freebsd-stable@freebsd.org Mail-Followup-To: freebsd-stable@freebsd.org References: <200104091859.UAA06664@flip.tenbit.pl> <01040916401600.22539@merlin> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <01040916401600.22539@merlin>; from jl@burghcom.com on Mon, Apr 09, 2001 at 04:29:00PM -0400 X-fish: < X-Copy-On-Listmail: Please do NOT Cc: me on list mail. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeff Love probably said: > I did have a problem after a cvsup on 04/08/2001, as the 'cim' sound > kernel module would not compile. I eliminated the subdirectory listing in the > Makefile, and it simply did not attempt to compile the module. Why was the > kernel make compiling modules for devices I did not set in my config? I > suppose I'm either missing something, or I need to RTFM over again... Modules are, by definition, not included in the kernel. They are loaded and added to the monolithic kernel. You can load a module at any time and gain support for what that module does (assuming module form exists for that hardware) or you can compile it into the monolithic kernel. By default all modules are built, in case you want to use them. P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 13:44:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from grumpy.dyndns.org (user-24-214-76-236.knology.net [24.214.76.236]) by hub.freebsd.org (Postfix) with ESMTP id 4782337B42C for ; Mon, 9 Apr 2001 13:44:46 -0700 (PDT) (envelope-from dkelly@grumpy.dyndns.org) Received: (from dkelly@localhost) by grumpy.dyndns.org (8.11.3/8.11.3) id f39KhAR46064; Mon, 9 Apr 2001 15:43:10 -0500 (CDT) (envelope-from dkelly) Date: Mon, 9 Apr 2001 15:43:06 -0500 From: David Kelly To: Jordan Hubbard Cc: dan@langille.org, stable@FreeBSD.ORG Subject: Re: Releases Message-ID: <20010409154306.A46046@grumpy.dyndns.org> References: <20010409102526S.jkh@osd.bsdi.com> <20010409105223C.jkh@osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010409105223C.jkh@osd.bsdi.com>; from jkh@osd.bsdi.com on Mon, Apr 09, 2001 at 10:52:23AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 09, 2001 at 10:52:23AM -0700, Jordan Hubbard wrote: > > Just because the problem is difficult to solve does not mean it can not be > > or should not be solved. > > Fine, how about you solve it and the rest of us will get back to all > the other stuff we have on our plates. :) Clearly we could solve this issue by naming the tags after Jordan's cats. Then it would make sense to no one and everyone would have to RTFM. Or we could use a couple of my cat's names, GRUMPY and PATCHES. :-) Opus, Callie, and Reebok, don't seem as appropriate. Come to think of it, Stable and Current are not too bad of names for cats. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 14: 3:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from widomaker.widomaker.com (widomaker.widomaker.com [204.17.220.1]) by hub.freebsd.org (Postfix) with ESMTP id 4D28637B422 for ; Mon, 9 Apr 2001 14:03:41 -0700 (PDT) (envelope-from bloyall@loyall.org) Received: from ballista.widomaker.com (ballista.loyall.org [206.246.250.51]) by widomaker.widomaker.com (8.9.3/8.9.3) with ESMTP id RAA73336; Mon, 9 Apr 2001 17:03:36 -0400 (EDT) (envelope-from bloyall@loyall.org) Message-Id: <5.0.2.1.0.20010409170505.00a66598@irc.widomaker.com> X-Sender: bloyall@irc.widomaker.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Mon, 09 Apr 2001 17:08:12 -0400 To: Scott Dodson , stable@FreeBSD.ORG From: Ben Loyall Subject: Re: Releases In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why not add the definition of -RC, -BETA, -CURRENT to the confirmation message that majordomo sends out when one first joins this list? My reasoning is that most of these messages come from somebody who joined the list simply to post that question. ben At 04:15 PM 4/9/2001 -0400, Scott Dodson wrote: >Why not write some rather intuitive scripts to weed our this particular >question which seems to be asked about once a day during code freeze >times? Simply Autoreply with a nice note to read the docs, or repost if >that didnt' answer their question. > >-- >scott > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 14: 9:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.redlinenetworks.com (node-64-249-141-98.dslspeed.zyan.com [64.249.141.98]) by hub.freebsd.org (Postfix) with ESMTP id B78A937B43F for ; Mon, 9 Apr 2001 14:09:26 -0700 (PDT) (envelope-from james@redlinenetworks.com) Received: from vault (vault [192.168.0.2]) by mail.redlinenetworks.com (8.11.3/8.11.1) with ESMTP id f39L9Ao41369; Mon, 9 Apr 2001 14:09:11 -0700 (PDT) (envelope-from james@redlinenetworks.com) Date: Mon, 9 Apr 2001 14:09:10 -0700 (PDT) From: James Penick To: Ben Loyall Cc: Scott Dodson , Subject: Re: Releases In-Reply-To: <5.0.2.1.0.20010409170505.00a66598@irc.widomaker.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Might as well throw in the entire handbook. James R. Penick Redline Networks Inc On Mon, 9 Apr 2001, Ben Loyall wrote: > > Why not add the definition of -RC, -BETA, -CURRENT to the confirmation > message that majordomo sends out when one first joins this list? My > reasoning is that most of these messages come from somebody who joined the > list simply to post that question. > > ben > > > At 04:15 PM 4/9/2001 -0400, Scott Dodson wrote: > > >Why not write some rather intuitive scripts to weed our this particular > >question which seems to be asked about once a day during code freeze > >times? Simply Autoreply with a nice note to read the docs, or repost if > >that didnt' answer their question. > > > >-- > >scott > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-stable" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 14:21:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id BE59D37B423 for ; Mon, 9 Apr 2001 14:21:23 -0700 (PDT) (envelope-from juha@saarinen.org) Received: from dendennis.saarinen.org ([192.168.1.2] helo=dendennis) by vimfuego.saarinen.org with smtp (Exim 3.22 #1 (Red Hack)) id 14mj66-0000oX-04; Tue, 10 Apr 2001 09:21:18 +1200 From: "Juha Saarinen" To: "Jordan Hubbard" , Cc: Subject: RE: Releases Date: Tue, 10 Apr 2001 09:21:08 +1200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: <20010409102526S.jkh@osd.bsdi.com> Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :: That's a nice pat answer, but the problem is that for every value of :: "name" we propose, somebody comes forward and says "But that confuses :: me." We can't call it BETA, we can't call it STABLE, we can't call it :: RC, we can't call it PRERELEASE, because each and every one of those :: have had push-back from people who said it would conflict with :: previous definitions they hold dear. Given that, chances are :: excellent that any other halfway logical names we come up with will :: suffer from the same problem. Numbered releases instead, like the Linux kernel? Odd numbers == beta; even numbers == should work. ;-) :: If we were McDonalds (or Microsoft for that matter), we would also :: stop providing access to -stable and -current entirely because it had :: been statistically proven that the lower percentile out there was :: doing the equivalent of pouring coffee in their laps and we didn't :: want the liability. No... you would sell them Preview copies, so that they'd pay to have their laps scalded. Could fund the rest of the FreeBSD development programme, that. No, no, no need to thank me. I have these brilliant ideas all the time. -- Juha (Who also finds the naming convention baffling.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 14:44:41 2001 Delivered-To: freebsd-stable@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 3AD1B37B422 for ; Mon, 9 Apr 2001 14:44:36 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id HAA00786; Tue, 10 Apr 2001 07:44:29 +1000 (EST) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37645) with ESMTP id <01K286MA4QNKS4N064@cim.alcatel.com.au>; Tue, 10 Apr 2001 07:44:18 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f39LiND71725; Tue, 10 Apr 2001 07:44:24 +1000 (EST envelope-from jeremyp) Content-return: prohibited Date: Tue, 10 Apr 2001 07:44:23 +1000 From: Peter Jeremy Subject: Re: Disklabel 101? In-reply-to: <000001c0bfd9$3b96a230$1201a8c0@sanmik.com>; from mike@dad.state.vt.us on Sat, Apr 07, 2001 at 10:24:12AM -0400 To: Mike Barton Cc: stable@FreeBSD.ORG Mail-Followup-To: Mike Barton , stable@FreeBSD.ORG Message-id: <20010410074423.B71179@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <20010405111707.A35325@dogma.freebsd-uk.eu.org> <3ACE972D.A13CF44C@babbleon.org> <15054.57979.84674.462609@guru.mired.org> <000001c0bfd9$3b96a230$1201a8c0@sanmik.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-Apr-07 10:24:12 -0400, Mike Barton wrote: >Are there any issues with placing swap first on the hard drive? I think this is safe for FreeBSD, but some Unix variants will start writing at the beginning of the swap partition. This means that if the swap partition is at the start of a slice, you'll over-write the partition table and bootblocks. > Unless you >insist on filling the drive, it seems to me that this swap arrangement would >result in less stack travel. AFAIK, for most modern disks, latency is larger than the seek time. The major advantage is that the outer tracks provide a higher data rate than inner track. If you are really concerned about minimising seek/latency overheads, you need to study your disk access patterns and take them into account. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 15:44:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nanguo.chalmers.com.au (gateway.chalmers.com.au [203.1.96.1]) by hub.freebsd.org (Postfix) with ESMTP id 831F837B422 for ; Mon, 9 Apr 2001 15:44:47 -0700 (PDT) (envelope-from robert@chalmers.com.au) Received: from carbon (carbon.chalmers.com.au [203.1.96.26]) by nanguo.chalmers.com.au (8.11.0/8.11.0) with SMTP id f39MkYU12846 for ; Tue, 10 Apr 2001 08:46:35 +1000 (EST) From: "Robert" To: "FreeBSD" Subject: Can I stop BUILDWORLD from starting from scratch? Date: Tue, 10 Apr 2001 08:47:52 +1000 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.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it possible to stop 'make buildworld' from starting from scratch each time? Like it runs for 5 hours then breaks over something. I fix that 'something', and type 'make buildworld' - it starts from the beginning again. Can I make it start just from where it left off? thanks Robert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 15:55:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 83DDB37B424 for ; Mon, 9 Apr 2001 15:55:22 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 11404 invoked by uid 100); 9 Apr 2001 22:55:13 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15058.15825.422218.278218@guru.mired.org> Date: Mon, 9 Apr 2001 17:55:13 -0500 To: Przemyslaw Brojewski , Kal Torak , Christopher Schulte , "Matthew Emmerton" , Jordan Hubbard , stable@freebsd.org Subject: Re: Releases In-Reply-To: <200104091816.UAA03404@flip.tenbit.pl> References: <20010409102526S.jkh@osd.bsdi.com> <20010409105223C.jkh@osd.bsdi.com> <014a01c0c12e$e5e76f20$1200a8c0@gsicomp.on.ca> <5.0.2.1.0.20010409101533.00ace930@pop.schulte.org> <5.0.2.1.0.20010409111054.00b18008@pop.schulte.org> <200104091911.MAA32457@gndrsh.dnsmgr.net> <3AD20ECC.5A895124@quake.com.au> <20010409193544.A25126@acc.umu.se> <200104091816.UAA03404@flip.tenbit.pl> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kal Torak types: > There is nothing wrong with the current label system... As it has been > said RTFM!!! Its not a hard concept to grasp, there are thousands of > people that understand it just fine, for those few that dont it wouldnt > matter what labels you used they would still not understand... > > Since there is no problem to be solved here, lets kill this thread and > get on with more important things... Wrong. The problem is that the common perception of the meaning of "BETA" causes people to want to know how not to get a BETA when it shows up. Those of us who try to contribute via -questions have to put up with it there as well as here. If there's a simple solution to making the problem go away, I'd certainly like to have it happen. Matthew Emmerton types: > In the case of people running -CURRENT on a production machine, that's just > a plain and simple mistake. Ever wonder how someone who barely knows how to > use cvsup and make world manages to obtain -CURRENT in the first place? No, because it happens to everyone who uses the standard-supfile in the /usr/share/examples/cvsup. I think that stable-supfile should vanish from that directory, and standard-supfile should be right for the branch the system came from, no matter which branch that was. > Next, the case of -STABLE/-BETA/-RC/-RELEASE. I still maintain that -BETA > is confusing to the newbie (since due to M$, betas of IE were more like > pre-alphas and totally trashed most systems and rightly freak out most > novice admins), while STABLE/RC/RELEASE just makes sense. However, this > isn't in the handbook and should be, so that people on the list can say "go > to handbook/release-process.html" and people unfamiliar with our release > process will become enlightened. You can already say "go to FAQ/admin.html#RELEASE-CANDIDATE". That doesn't stop the questions. While all of them cause problems > Finally, almost every newbie I see asking a question asks "how can I do this > on FreeBSD, and where is the HOWTO- to help me?" Most often these people > are redirected to offsite repositories of information, rather than the > documentation included with FreeBSD. IMHO, this contributes to the > degradation of the existing documentation of FreeBSD, as more effort will go > into updating third-party sources. Note that the third-party repositories don't have a chance to be vetted by committers, who will presumably catch obsolete, inaccurate, or suboptimal information. Between these two problems, they are clearly bad for the community. If you maintain one of those things - I'd be interested in knowing why you aren't submitting them to the documentation project, instead of maintaining your own repository? Jordan Hubbard types: > > Just because the problem is difficult to solve does not mean it can not be > > or should not be solved. > Fine, how about you solve it and the rest of us will get back to all > the other stuff we have on our plates. :) I know, you're kidding. But if some group of people who have to deal with the questions propose a complete new naming scheme designed to deal with all the problems we see the current ones causing (though the only serious one is -BETA/-RC), is there any chance of it being adopted? How about just a new name for either -BETA (the major source of the problem), or simply calling -STABLE -ALPHA, thus making -BETA & -RC seem desirable? http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 16: 3:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id AB47F37B422 for ; Mon, 9 Apr 2001 16:03:16 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f39N3AW04167; Mon, 9 Apr 2001 16:03:10 -0700 (PDT) Date: Mon, 9 Apr 2001 16:03:10 -0700 From: Alfred Perlstein To: Robert Cc: FreeBSD Subject: Re: Can I stop BUILDWORLD from starting from scratch? Message-ID: <20010409160310.N15938@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from robert@chalmers.com.au on Tue, Apr 10, 2001 at 08:47:52AM +1000 X-all-your-base: are belong to us. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Robert [010409 15:46] wrote: > Is it possible to stop 'make buildworld' from starting from scratch each > time? > > Like it runs for 5 hours then breaks over something. I fix that 'something', > and type 'make buildworld' - it starts from the beginning again. Can I make > it start just from where it left off? Sorta, try: make buildworld -DNOCLEAN (you can do the same with kernels) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Represent yourself, show up at BABUG http://www.babug.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 16: 4:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mx.zrcalo.si (maribor.zrcalo.si [193.77.90.34]) by hub.freebsd.org (Postfix) with ESMTP id 9B0F837B422 for ; Mon, 9 Apr 2001 16:04:41 -0700 (PDT) (envelope-from mike@unix-systems.net) Received: from nexus.zrcalo.si (nexus.zrcalo.si [193.77.90.10]) by mx.zrcalo.si (Postfix) with ESMTP id 66CA99EE0C; Tue, 10 Apr 2001 01:05:53 +0200 (CEST) Received: by nexus.zrcalo.si (Postfix, from userid 1001) id 2A7FF7C203; Tue, 10 Apr 2001 01:05:43 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by nexus.zrcalo.si (Postfix) with ESMTP id 19DC97254B; Tue, 10 Apr 2001 01:05:43 +0200 (CEST) Date: Tue, 10 Apr 2001 01:05:42 +0200 (CEST) From: Miha Nedok X-X-Sender: To: Robert Cc: FreeBSD Subject: Re: Can I stop BUILDWORLD from starting from scratch? In-Reply-To: Message-ID: <20010410010501.I21331-100000@nexus.zrcalo.si> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Add NOCLEAN. So: make buildworld -DNOCLEAN Miha Nedok mike@unix-systems.net On Tue, 10 Apr 2001, Robert wrote: > Is it possible to stop 'make buildworld' from starting from scratch each > time? > > Like it runs for 5 hours then breaks over something. I fix that 'something', > and type 'make buildworld' - it starts from the beginning again. Can I make > it start just from where it left off? > > thanks > Robert > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 16: 5:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cage.simianscience.com (cage.simianscience.com [64.7.134.1]) by hub.freebsd.org (Postfix) with ESMTP id 2859F37B424 for ; Mon, 9 Apr 2001 16:05:47 -0700 (PDT) (envelope-from mike@sentex.net) Received: (from root@localhost) by cage.simianscience.com (8.11.3/8.11.2) id f39N5kH12396; Mon, 9 Apr 2001 19:05:46 -0400 (EDT) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.3/8.11.2av) with ESMTP id f39N5fC12388; Mon, 9 Apr 2001 19:05:41 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010409190439.027ccd08@192.168.0.12> X-Sender: mdtancsa@192.168.0.12 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 09 Apr 2001 19:05:40 -0400 To: "Robert" , "FreeBSD" From: Mike Tancsa Subject: Re: Can I stop BUILDWORLD from starting from scratch? In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:47 AM 4/10/2001 +1000, Robert wrote: >Is it possible to stop 'make buildworld' from starting from scratch each >time? > >Like it runs for 5 hours then breaks over something. I fix that 'something', >and type 'make buildworld' - it starts from the beginning again. Can I make >it start just from where it left off? make -DNOCLEAN buildworld But why is "something" breaking ? The build process should be clean. If not, something is messed in your source code repository. ---Mike -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Network Administration, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 16:17:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from snipe.mail.pas.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 53C0737B422 for ; Mon, 9 Apr 2001 16:17:17 -0700 (PDT) (envelope-from oistrakh@earthlink.net) Received: from pirastro.oistrakh.org (user-2ivfthd.dialup.mindspring.com [165.247.246.45]) by snipe.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id QAA02299; Mon, 9 Apr 2001 16:17:15 -0700 (PDT) Received: from localhost (oistrakh@localhost) by pirastro.oistrakh.org (8.11.3/8.11.1) with ESMTP id f39NGjs90487; Mon, 9 Apr 2001 16:16:46 -0700 (PDT) (envelope-from oistrakh@earthlink.net) X-Authentication-Warning: pirastro.oistrakh.org: oistrakh owned process doing -bs Date: Mon, 9 Apr 2001 16:16:45 -0700 (PDT) From: Christian Chen X-X-Sender: To: Mike Tancsa Cc: Robert , FreeBSD Subject: Re: Can I stop BUILDWORLD from starting from scratch? In-Reply-To: <4.2.2.20010409190439.027ccd08@192.168.0.12> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Apr 2001, Mike Tancsa wrote: > make -DNOCLEAN buildworld > > But why is "something" breaking ? The build process should be clean. If > not, something is messed in your source code repository. Well, I know that when I installed 4.2-RELEASE off of CD, make world in /usr/src did not work. I had to cvsup stable before I could make world. While it's entirely possible that I screwed something up during the install since it was only my second hour of running FreeBSD, I definitely didn't do anything besides running the install.sh script in the src directory of the CDROM to get the sources into the right place. I really wish it'd be possible to just make selective portions of the source tree, is that possible? Christian Chen > ---Mike > -------------------------------------------------------------------- > Mike Tancsa, tel +1 519 651 3400 > Network Administration, mike@sentex.net > Sentex Communications www.sentex.net > Cambridge, Ontario Canada www.sentex.net/mike > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 16:17:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from radix.cryptio.net (radix.cryptio.net [199.181.107.213]) by hub.freebsd.org (Postfix) with ESMTP id 19B6137B422 for ; Mon, 9 Apr 2001 16:17:48 -0700 (PDT) (envelope-from emechler@radix.cryptio.net) Received: (from emechler@localhost) by radix.cryptio.net (8.11.3/8.11.3) id f39NHlq33475 for stable@freebsd.org; Mon, 9 Apr 2001 16:17:47 -0700 (PDT) (envelope-from emechler) Date: Mon, 9 Apr 2001 16:17:46 -0700 From: Erick Mechler To: stable@freebsd.org Subject: Runt packets Message-ID: <20010409161746.B33217@techometer.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a dual-homed machine doing routing and firewalling on which hundreds of the following messages appear in my logs every 10 minutes or so: /kernel: icmp-response bandwidth limit 44069/200 pps /kernel: arp: runt packet last message repeated 14691 times At the same time these messages are occurring, I find the following while doing a tcpdump on the internal interface (it doesn't happen on the external interface at all): 19:05:34.247543 arp-#12469 for proto #208 (166) hardware #1 (183) 19:05:34.247588 arp-#12469 for proto #208 (166) hardware #1 (183) 19:05:34.247630 arp-#12469 for proto #208 (166) hardware #1 (183) 19:05:34.247674 arp-#12469 for proto #208 (166) hardware #1 (183) 19:05:34.247718 arp-#12469 for proto #208 (166) hardware #1 (183) 19:05:34.247762 arp-#12469 for proto #208 (166) hardware #1 (183) 19:05:34.247805 arp-#12469 for proto #208 (166) hardware #1 (183) ...except there are thousands of these. Has anybody seen this before? I'm running a slightly old version of 4.2 (Thu Dec 14 15:28:03 EST 2000), but I didn't see any relevant diffs to sys/netinet/if_ether.c which is where the "runt packet" errors are sent to syslog. Could this be a problem of bad hardware on the part of one of the internal hosts? Any and all help is much appreciated. Thanks! Erick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 16:22:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id 2F68437B423 for ; Mon, 9 Apr 2001 16:22:24 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from mail2.uniserve.com ([204.244.156.10]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 14mkzE-0005oM-00; Mon, 09 Apr 2001 16:22:20 -0700 Date: Mon, 9 Apr 2001 16:22:20 -0700 (PDT) From: Tom X-Sender: tom@athena.uniserve.ca To: Erick Mechler Cc: stable@freebsd.org Subject: Re: Runt packets In-Reply-To: <20010409161746.B33217@techometer.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Apr 2001, Erick Mechler wrote: > I have a dual-homed machine doing routing and firewalling on which hundreds > of the following messages appear in my logs every 10 minutes or so: > > /kernel: icmp-response bandwidth limit 44069/200 pps > /kernel: arp: runt packet > last message repeated 14691 times I think the ICMP problem is causing the runt problem. 44,069 packets per second is rather a lot, especialy if they are echo responses, meaning that your system is handling about 85,000 packets per second. That could very easily beyond the capabilities of the your CPU and network card. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 16:22:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pi.yip.org (yip.org [199.45.111.121]) by hub.freebsd.org (Postfix) with ESMTP id A197A37B423 for ; Mon, 9 Apr 2001 16:22:45 -0700 (PDT) (envelope-from melange@yip.org) Received: from localhost (melange@localhost) by pi.yip.org (8.11.1/8.11.1) with ESMTP id f39NMck17828 for ; Mon, 9 Apr 2001 19:22:43 -0400 (EDT) (envelope-from melange@yip.org) Date: Mon, 9 Apr 2001 19:22:38 -0400 (EDT) From: Bob K To: stable@FreeBSD.ORG Subject: Re: supfile idea (was Re: Releases) In-Reply-To: <15058.15825.422218.278218@guru.mired.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Apr 2001, Mike Meyer wrote: [snip] > Matthew Emmerton types: > > In the case of people running -CURRENT on a production machine, that's just > > a plain and simple mistake. Ever wonder how someone who barely knows how to > > use cvsup and make world manages to obtain -CURRENT in the first place? > > No, because it happens to everyone who uses the standard-supfile in > the /usr/share/examples/cvsup. I think that stable-supfile should > vanish from that directory, and standard-supfile should be right for > the branch the system came from, no matter which branch that was. [snip] I'm not going to touch on the rest of the thread, but that idea seems like an extremely good one. How 'bout putting this in once 4.3's gone out the door? -- Bob | "Villain, I have done thy mother" - Shakespeare, Titus Andronicus, act IV, scene II To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 16:22:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mx.zrcalo.si (maribor.zrcalo.si [193.77.90.34]) by hub.freebsd.org (Postfix) with ESMTP id E0D5B37B423 for ; Mon, 9 Apr 2001 16:22:55 -0700 (PDT) (envelope-from mike@unix-systems.net) Received: from nexus.zrcalo.si (nexus.zrcalo.si [193.77.90.10]) by mx.zrcalo.si (Postfix) with ESMTP id 472869EE0C; Tue, 10 Apr 2001 01:24:08 +0200 (CEST) Received: by nexus.zrcalo.si (Postfix, from userid 1001) id 808727C205; Tue, 10 Apr 2001 01:23:54 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by nexus.zrcalo.si (Postfix) with ESMTP id 574557254B; Tue, 10 Apr 2001 01:23:54 +0200 (CEST) Date: Tue, 10 Apr 2001 01:23:53 +0200 (CEST) From: Miha Nedok X-X-Sender: To: Christian Chen Cc: Mike Tancsa , Robert , FreeBSD Subject: Re: Can I stop BUILDWORLD from starting from scratch? In-Reply-To: Message-ID: <20010410012236.Q21441-100000@nexus.zrcalo.si> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Apr 2001, Christian Chen wrote: > > On Mon, 9 Apr 2001, Mike Tancsa wrote: > > > make -DNOCLEAN buildworld > > > > But why is "something" breaking ? The build process should be clean. If > > not, something is messed in your source code repository. > > Well, I know that when I installed 4.2-RELEASE off of CD, make world > in /usr/src did not work. I had to cvsup stable before I could make > world. While it's entirely possible that I screwed something up during > the install since it was only my second hour of running FreeBSD, I > definitely didn't do anything besides running the install.sh script in > the src directory of the CDROM to get the sources into the right place. > > I really wish it'd be possible to just make selective portions > of the source tree, is that possible? You might look at /etc/defaults/make.conf What you're looking for starts with this: # To avoid building various parts of the base system: #NO_CVS= true # do not build CVS Miha Nedok mike@unix-systems.net > > Christian Chen > > > ---Mike > > -------------------------------------------------------------------- > > Mike Tancsa, tel +1 519 651 3400 > > Network Administration, mike@sentex.net > > Sentex Communications www.sentex.net > > Cambridge, Ontario Canada www.sentex.net/mike > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 17:40:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cx344940-a.meta1.la.home.com (cx344940-a.meta1.la.home.com [24.6.21.74]) by hub.freebsd.org (Postfix) with ESMTP id B971637B424 for ; Mon, 9 Apr 2001 17:40:48 -0700 (PDT) (envelope-from conrads@cx344940-a.meta1.la.home.com) Received: (from conrads@localhost) by cx344940-a.meta1.la.home.com (8.11.3/8.11.3) id f3A0jxv01213; Mon, 9 Apr 2001 19:45:59 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.4.7 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010410012236.Q21441-100000@nexus.zrcalo.si> Date: Mon, 09 Apr 2001 19:45:59 -0500 (CDT) Organization: @Home Network From: Conrad Sabatier To: Miha Nedok Subject: Re: Can I stop BUILDWORLD from starting from scratch? Cc: FreeBSD , Robert , Mike Tancsa , Christian Chen Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 09-Apr-2001 Miha Nedok wrote: >> I really wish it'd be possible to just make selective portions >> of the source tree, is that possible? > > You might look at /etc/defaults/make.conf > > What you're looking for starts with this: > ># To avoid building various parts of the base system: >#NO_CVS= true # do not build CVS What does this do exactly? -- Conrad Sabatier conrads@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 17:44:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cx344940-a.meta1.la.home.com (cx344940-a.meta1.la.home.com [24.6.21.74]) by hub.freebsd.org (Postfix) with ESMTP id 6BEFE37B422 for ; Mon, 9 Apr 2001 17:44:54 -0700 (PDT) (envelope-from conrads@cx344940-a.meta1.la.home.com) Received: (from conrads@localhost) by cx344940-a.meta1.la.home.com (8.11.3/8.11.3) id f3A0oFr01253; Mon, 9 Apr 2001 19:50:15 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.4.7 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, 09 Apr 2001 19:50:15 -0500 (CDT) Organization: @Home Network From: Conrad Sabatier To: Bob K Subject: Re: supfile idea (was Re: Releases) Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 09-Apr-2001 Bob K wrote: > On Mon, 9 Apr 2001, Mike Meyer wrote: > > [snip] >> Matthew Emmerton types: >> > In the case of people running -CURRENT on a production machine, that's >> > just >> > a plain and simple mistake. Ever wonder how someone who barely knows how >> > to >> > use cvsup and make world manages to obtain -CURRENT in the first place? >> >> No, because it happens to everyone who uses the standard-supfile in >> the /usr/share/examples/cvsup. I think that stable-supfile should >> vanish from that directory, and standard-supfile should be right for >> the branch the system came from, no matter which branch that was. > [snip] > > I'm not going to touch on the rest of the thread, but that idea seems like > an extremely good one. How 'bout putting this in once 4.3's gone out the > door? I think it might be better, perhaps, to rename standard-supfile to something like unstable-supfile (unstable-supfile-use-at-your-own-risk? :-), and leave stable-supfile alone. That should be enough to ward off the wary. -- Conrad Sabatier conrads@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 17:46: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cage.simianscience.com (cage.simianscience.com [64.7.134.1]) by hub.freebsd.org (Postfix) with ESMTP id C341F37B422 for ; Mon, 9 Apr 2001 17:45:57 -0700 (PDT) (envelope-from mike@sentex.net) Received: (from root@localhost) by cage.simianscience.com (8.11.3/8.11.2) id f3A0jsZ13092; Mon, 9 Apr 2001 20:45:54 -0400 (EDT) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.3/8.11.2av) with ESMTP id f3A0jnC13084; Mon, 9 Apr 2001 20:45:49 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010409204301.027c1d88@192.168.0.12> X-Sender: mdtancsa@192.168.0.12 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 09 Apr 2001 20:45:48 -0400 To: Christian Chen From: Mike Tancsa Subject: Re: Can I stop BUILDWORLD from starting from scratch? Cc: freebsd-stable@freebsd.org In-Reply-To: References: <4.2.2.20010409190439.027ccd08@192.168.0.12> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:16 PM 4/9/2001 -0700, Christian Chen wrote: >On Mon, 9 Apr 2001, Mike Tancsa wrote: > > > make -DNOCLEAN buildworld > > > > But why is "something" breaking ? The build process should be clean. If > > not, something is messed in your source code repository. > > >I really wish it'd be possible to just make selective portions >of the source tree, is that possible? It depends what you want to build. There are some parts you can build on their own and not have to worry too much about dependencies. But it depends on what has changed since your last cvsup. If you want to update to the most recent snapshot of stable, you really should use cvsup to do so. Check the handbook for instructions on it as well as how to use cvsup and what needs to be done in order to track STABLE. Its a fairly easy process, but you must deal with the few caveats. Particularly the things in /etc that you must either manually merge, or use merge master. ---Mike -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Network Administration, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 18: 2:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.altadena.net (ns.altadena.net [206.126.144.2]) by hub.freebsd.org (Postfix) with ESMTP id 664E737B423 for ; Mon, 9 Apr 2001 18:02:50 -0700 (PDT) (envelope-from pete@ns.altadena.net) Received: (from pete@localhost) by ns.altadena.net (8.11.3/8.8.8) id f3A0xB873820 for stable@freebsd.org; Mon, 9 Apr 2001 17:59:11 -0700 (PDT) (envelope-from pete) From: Pete Carah Message-Id: <200104100059.f3A0xB873820@ns.altadena.net> Subject: Re: Answer found: TCP New Reno Algorithm To: stable@freebsd.org Date: Mon, 9 Apr 2001 17:59:11 -0700 (PDT) Action: X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=iso8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I seem to have the same problem that someone else noted here, but here is a big difference; it is an almost-unloaded 100-base-t switched network, with both systems running -stable cvsup-d on Sunday afternoon/evening. This appears to be a driver or stack problem, since New-reno on or off on either end has no effect. The (cheap) switch is entirely autoconfig'd (but used to work fine with these same two cards, switch, and cables), and both interfaces (both fxp) show full-duplex 100baseT. pelican# ifconfig fxp0 fxp0: flags=8843 mtu 1500 inet 192.168.167.2 netmask 0xffffff00 broadcast 192.168.167.255 inet6 fe80::202:b3ff:fe04:1ed1%fxp0 prefixlen 64 scopeid 0x1 ether 00:02:b3:04:1e:d1 media: 100baseTX status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP ----------------- portable% ifconfig fxp0 fxp0: flags=8843 mtu 1500 inet6 fe80::a00:46ff:fe06:2fdb%fxp0 prefixlen 64 scopeid 0x1 inet 192.168.167.22 netmask 0xffffff00 broadcast 192.168.167.255 ether 08:00:46:06:2f:db media: autoselect (100baseTX ) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP Apparently this isn't a new-reno problem. It *is* new with the latest -stable; things worked fine before. pelican has one of the newer fxp boards identifying as a 559. The portable is a Sony Z505HS; I don't know the intel chip rev. This is a transfer using rsync of a directory of 65 or so 1-meg jpgs, to an empty directory. Performance from the default case: ..... 010409/dscn1418.jpg 010409/dscn1419.jpg 010409/dscn1420.jpg 010409/dscn1421.jpg 010409/dscn1422.jpg 010409/info.txt ./ 010409/ wrote 65491864 bytes read 1076 bytes 8648.79 bytes/sec total size is 229631336 speedup is 3.51 ---------------------------------------------- (total size includes 4 other directories but "wrote" is the test move). ------------------------------- TCPdump on receiving end shows: (sender is dhcp22, receiver is pelican) 17:50:19.452868 dhcp22.home-lan.altadena.net.1219 > pelican.home-lan.altadena.net.ssh: . 14600:16060(1460) ack 1 win 17520 (DF) [tos 0x8] 17:50:19.452988 dhcp22.home-lan.altadena.net.1219 > pelican.home-lan.altadena.net.ssh: . 16060:17520(1460) ack 1 win 17520 (DF) [tos 0x8] 17:50:19.453023 pelican.home-lan.altadena.net.ssh > dhcp22.home-lan.altadena.net.1219: . ack 17520 win 11680 (DF) [tos 0x8] 17:50:19.453049 truncated-ip - 762 bytes missing!dhcp22.home-lan.altadena.net.1219 > pelican.home-lan.altadena.net.ssh: . 17520:18980(1460) ack 1 win 17520 (DF) [tos 0x8] 17:50:19.454499 pelican.home-lan.altadena.net.ssh > dhcp22.home-lan.altadena.net.1219: . ack 17520 win 17520 (DF) [tos 0x8] 17:50:19.454871 dhcp22.home-lan.altadena.net.1219 > pelican.home-lan.altadena.net.ssh: . 18980:20440(1460) ack 1 win 17520 (DF) [tos 0x8] 17:50:19.454946 pelican.home-lan.altadena.net.ssh > dhcp22.home-lan.altadena.net.1219: . ack 17520 win 17520 (DF) [tos 0x8] 17:50:19.454970 truncated-ip - 133 bytes missing!dhcp22.home-lan.altadena.net.1219 > pelican.home-lan.altadena.net.ssh: . 20440:21900(1460) ack 1 win 17520 (DF) [tos 0x8] This truncated-ip is something I've not seen before -- Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 18: 3:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 0D2FD37B424 for ; Mon, 9 Apr 2001 18:03:10 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id LAA24608; Tue, 10 Apr 2001 11:03:06 +1000 (EST) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37641) with ESMTP id <01K28DJCBJOWRX5IS6@cim.alcatel.com.au>; Tue, 10 Apr 2001 11:02:45 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f3A12vh73400; Tue, 10 Apr 2001 11:02:57 +1000 (EST envelope-from jeremyp) Content-return: prohibited Date: Tue, 10 Apr 2001 11:02:57 +1000 From: Peter Jeremy Subject: Re: ALPHA Multia and FreeBSD 4.3-RC In-reply-to: ; from ohartman@klima.physik.uni-mainz.de on Sun, Apr 08, 2001 at 07:19:49PM +0200 To: "Hartmann, O." Cc: freebsd-stable@FreeBSD.ORG Mail-Followup-To: "Hartmann, O." , freebsd-stable@FreeBSD.ORG Message-id: <20010410110257.Z66243@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-Apr-08 19:19:49 +0200, "Hartmann, O." wrote: >First: I have no access to the console! The builtin TGA is not supported yet. It is currently being worked on and you can find a work-in-progress tarball against 4.2-RELEASE in http://people.freebsd.org/~gallatin/TGA/tga.tar.gz Your current options are to either use a serial console or to install a VGA-compatible graphics card. >Second: I tried to make a world. Due the fact the machine is really slow >it took a long time from starting the first make world up to the >point it failed. My Multia reboots spontanously and shows me the console, >awaiting the boot command. Multia's are notorious for suffering heat-related problems. It is essential that it be run vertically, with the fan at the top. You might also like to replace the fan with one that actually moves air as well as replacing the 74F623 (see http://www.netbsd.org/Ports/alpha/multiafaq.html for more details). The power supply is also quite marginal and if your HDD is internal, you might like to consider mounting it externally (with an external power supply). I also found that one of my cache chips was a bit slow and I needed to change the L2 cache timings to make my Multia stable. Note that the SRM does not enable ECC on the L2 cache by default. > What's up with the Alpha? Basically DEC stuffed the design of the Multia. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 18: 5:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from kline-station.ckdhr.com (kline-station.ckdhr.com [209.58.172.141]) by hub.freebsd.org (Postfix) with SMTP id 4EF3A37B423 for ; Mon, 9 Apr 2001 18:05:29 -0700 (PDT) (envelope-from ckd@ckdhr.com) Received: (qmail 14712 invoked by uid 139); 10 Apr 2001 00:55:02 -0000 To: stable@freebsd.org Subject: Re: Releases References: <20010409102526S.jkh@osd.bsdi.com> <20010409105223C.jkh@osd.bsdi.com> <014a01c0c12e$e5e76f20$1200a8c0@gsicomp.on.ca> <5.0.2.1.0.20010409101533.00ace930@pop.schulte.org> <5.0.2.1.0.20010409111054.00b18008@pop.schulte.org> <200104091911.MAA32457@gndrsh.dnsmgr.net> <3AD20ECC.5A895124@quake.com.au> <20010409193544.A25126@acc.umu.se> <200104091816.UAA03404@flip.tenbit.pl> <15058.15825.422218.278218@guru.mired.org> X-Face: I8Alb*-ZdjN\/8k_QR,^l^m6GQB'S-B:}DVP].1HOw#tx:TX$k;Wl;4zqjWR|-jheM#? &beRf(!|0b0m=M~=%.Am>"QEY.(#Ys.%"s?z,hmwp&y0%p>9+T X-Attribution: ckd Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII From: Christopher K Davis Date: 09 Apr 2001 20:55:02 -0400 In-Reply-To: Mike Meyer's message of "Mon, 9 Apr 2001 17:55:13 -0500" Message-ID: Lines: 26 X-Mailer: Gnus v5.6.44/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike W Meyer writes: > I know, you're kidding. But if some group of people who have to deal > with the questions propose a complete new naming scheme designed to > deal with all the problems we see the current ones causing (though the > only serious one is -BETA/-RC), is there any chance of it being > adopted? How about just a new name for either -BETA (the major source > of the problem), or simply calling -STABLE -ALPHA, thus making -BETA & > -RC seem desirable? Off the top of my head: -STABLE, -FROZEN, -FROZENRC, -RELEASE. FROZEN has much better connotations than BETA (which should hopefully deconfuse people a bit), and continuing it into the release candidate phase gives us continuity there. The use of "FROZEN" also emphasizes the most critical change that happens in the currently-named BETA/RC phases, namely the freezing of changes other than critical ones. (I suppose it could be -SLUSHY and -FROZEN for -BETA and -RC if we wanted to be slightly cuter.) -- Christopher Davis * * Put location information in your DNS! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 18:18:28 2001 Delivered-To: freebsd-stable@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id F1EDC37B424 for ; Mon, 9 Apr 2001 18:18:21 -0700 (PDT) (envelope-from yann@yann.de) Received: from freiburger ([216.228.138.164]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id DAA12650 for ; Tue, 10 Apr 2001 03:18:14 +0200 (MET DST) From: "Yann Sommer" To: Subject: Why not stick with [STABLE] [Was: RE: Releases] Date: Mon, 9 Apr 2001 20:18:24 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Heya all, I've been following this thread with some extra attention, since I remember beeing new to FreeBSD and complaining about a dedicated Server I ordered, running BETA. It is just, as has been mentioned a few times before on this list, against what other programms use for version naming. But, in my humble opinion I think the easiest solution has not been mentioned here before. Why not just suffix the old version description to stable, like: 4.3-STABLE-BETA 4.3-STABLE-RC 4.3-STABLE-FINAL or something in that direction. The essential word "STABLE" which gives the newer users the trust in a system (allthough it's kind of stupid after knowing the exact naming, but heh, nobody gets born with all knowledge ;), and at the same time sticks with the naming BSD users are used to. Just my 2 cents, --Frei -----Original Message----- From: owner-freebsd-stable@FreeBSD.ORG [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Christopher K Davis Sent: Monday, April 09, 2001 5:55 PM To: stable@FreeBSD.ORG Subject: Re: Releases Mike W Meyer writes: > I know, you're kidding. But if some group of people who have to deal > with the questions propose a complete new naming scheme designed to > deal with all the problems we see the current ones causing (though the > only serious one is -BETA/-RC), is there any chance of it being > adopted? How about just a new name for either -BETA (the major source > of the problem), or simply calling -STABLE -ALPHA, thus making -BETA & > -RC seem desirable? Off the top of my head: -STABLE, -FROZEN, -FROZENRC, -RELEASE. FROZEN has much better connotations than BETA (which should hopefully deconfuse people a bit), and continuing it into the release candidate phase gives us continuity there. The use of "FROZEN" also emphasizes the most critical change that happens in the currently-named BETA/RC phases, namely the freezing of changes other than critical ones. (I suppose it could be -SLUSHY and -FROZEN for -BETA and -RC if we wanted to be slightly cuter.) -- Christopher Davis * * Put location information in your DNS! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 18:49:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id EC0AE37B422 for ; Mon, 9 Apr 2001 18:49:19 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id LAA29648; Tue, 10 Apr 2001 11:49:00 +1000 (EST) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37645) with ESMTP id <01K28F5FU78GS4N63W@cim.alcatel.com.au>; Tue, 10 Apr 2001 11:48:49 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f3A1msG73750; Tue, 10 Apr 2001 11:48:54 +1000 (EST envelope-from jeremyp) Content-return: prohibited Date: Tue, 10 Apr 2001 11:48:54 +1000 From: Peter Jeremy Subject: Re: Can I stop BUILDWORLD from starting from scratch? In-reply-to: ; from robert@chalmers.com.au on Tue, Apr 10, 2001 at 08:47:52AM +1000 To: Robert Cc: FreeBSD Mail-Followup-To: Robert , FreeBSD Message-id: <20010410114854.A66243@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-Apr-10 08:47:52 +1000, Robert wrote: >Is it possible to stop 'make buildworld' from starting from scratch each >time? How far into the buildworld are you? If you're beyond the ">>> stage 4: building everything.." prompt then you can use "make everything" instead of "make buildworld". Otherwise you have a choice of "make -DNOCLEAN buildworld" or editing /usr/src/Makefile.inc1 to restart from the stage it was in. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 18:58: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from never.tellme.com (never.tellme.com [209.157.156.27]) by hub.freebsd.org (Postfix) with ESMTP id 4677937B422 for ; Mon, 9 Apr 2001 18:58:01 -0700 (PDT) (envelope-from dannyman@tellme.com) Received: by never.tellme.com (Postfix, from userid 501) id 304D771658; Mon, 9 Apr 2001 18:58:00 -0700 (PDT) Date: Mon, 9 Apr 2001 18:58:00 -0700 From: Danny Howard To: freebsd-stable@freebsd.org Subject: fdisk & disklabel dont work! Message-ID: <20010409185759.N59290@tellme.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Loop: djhoward@uiuc.edu Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, so, I'm BTX booting diskless workstation on a 4.2-R system with two SCSI drives and an Adaptec controller. I can very very very easily install a systerm in dangerously dedicated mode as follows: disklabel -r -w da0 auto (Then write the disklabel the way I want, newfs everything, be done with it.) This is great, except the system will then refuse to boot. PXE boot crashes and SCSI boot hangs, and the explanation I can find is that the Adaptec controller is pissed off about the dangerously dedicated mode and ends up diving by zero. Okay, so let's do it the right way. Nearly two weeks later, I'M STILL STUCK. I've read about MBRs and why disklabel can't label an fdisk partition, but maybe now it can, but first you have to dd anywhere between one and 128 blocks on the disk before the magic incantations work properly ... Here's what I try to do: fdisk -I da0 disklabel -r -w da0s1 auto Okay. Any time after the very first fdisk when booting up, I get kernel messages about how da0 and da0s1 have no disk labels, and nothing works. I have tried zeroing out any number of sectors, various variations of fdisk, disklabel ... dd'ing the start of a working system on to the system in question ... nowhere! Nada! AUGHGHGHG!!!! Disklabel JUST WON'T FUNCTION!!! (I can always read fdisk with accuracy, even if the kernel is spitting out log messages about how there is no label. Why should fdisk da0 care if da0s1 has a label?) I have tried low-level SCSI format of disks, commands on the second disk ... not even disklabel -r -w da0 auto works any more ... always the same flavor of errors. For example: # disklabel -r -w da0s1 auto /kernel: da0: cannot find label (no disk label) /kernel: da0: cannot find label (no disk label) /kernel: da0s1: cannot find label (no disk label) /kernel: da0s1: cannot find label (no disk label) /kernel: da0: cannot find label (no disk label) /kernel: da0: cannot find label (no disk label) /kernel: da0s1: cannot find label (no disk label) /kernel: da0s1: cannot find label (no disk label) disklabel: ioctl DIOCGDINFO: Invalid argument disklabel: auto: unknown disk type Anyone has any idea? Maybe there's something really subtle that I am doing wrong? Thanks, -danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 19: 8:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id DB2A637B423; Mon, 9 Apr 2001 19:08:10 -0700 (PDT) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 9FFC46ACB7; Tue, 10 Apr 2001 11:38:08 +0930 (CST) Date: Tue, 10 Apr 2001 11:38:08 +0930 From: Greg Lehey To: Danny Howard Cc: FreeBSD Questions Subject: Re: fdisk & disklabel dont work! Message-ID: <20010410113808.K64481@wantadilla.lemis.com> References: <20010409185759.N59290@tellme.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010409185759.N59290@tellme.com>; from dannyman@tellme.com on Mon, Apr 09, 2001 at 06:58:00PM -0700 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 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 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [redirected to -questions] On Monday, 9 April 2001 at 18:58:00 -0700, Danny Howard wrote: > Okay, so, I'm BTX booting diskless workstation on a 4.2-R system with two SCSI > drives and an Adaptec controller. > > I can very very very easily install a systerm in dangerously dedicated mode as > follows: > disklabel -r -w da0 auto > (Then write the disklabel the way I want, newfs everything, be done with it.) > > This is great, except the system will then refuse to boot. PXE boot > crashes and SCSI boot hangs, and the explanation I can find is that > the Adaptec controller is pissed off about the dangerously dedicated > mode and ends up diving by zero. That's maybe the explanation you can find, but I doubt it's correct. I have lots of dedicated installations running with Adaptec host adaptors, and it works fine. > Okay, so let's do it the right way. > > Nearly two weeks later, I'M STILL STUCK. > > I've read about MBRs and why disklabel can't label an fdisk partition, but > maybe now it can, but first you have to dd anywhere between one and 128 blocks > on the disk before the magic incantations work properly ... > > Here's what I try to do: > > fdisk -I da0 > disklabel -r -w da0s1 auto > > Okay. Any time after the very first fdisk when booting up, I get kernel > messages about how da0 and da0s1 have no disk labels, and nothing works. I > have tried zeroing out any number of sectors, various variations of fdisk, > disklabel ... dd'ing the start of a working system on to the system in > question ... nowhere! Nada! AUGHGHGHG!!!! Disklabel JUST WON'T FUNCTION!!! > (I can always read fdisk with accuracy, even if the kernel is spitting out log > messages about how there is no label. Why should fdisk da0 care if da0s1 has > a label?) > > I have tried low-level SCSI format of disks, commands on the second disk ... > not even disklabel -r -w da0 auto works any more ... always the same flavor of > errors. For example: > > # disklabel -r -w da0s1 auto > /kernel: da0: cannot find label (no disk label) > /kernel: da0: cannot find label (no disk label) > /kernel: da0s1: cannot find label (no disk label) > /kernel: da0s1: cannot find label (no disk label) > /kernel: da0: cannot find label (no disk label) > /kernel: da0: cannot find label (no disk label) > /kernel: da0s1: cannot find label (no disk label) > /kernel: da0s1: cannot find label (no disk label) > disklabel: ioctl DIOCGDINFO: Invalid argument > disklabel: auto: unknown disk type > > Anyone has any idea? Maybe there's something really subtle that I am doing > wrong? Well, you're not showing much output. The output of disklabel and fdisk with no options would be interesting, as would the exact kernel error messages you're seeing. The *relevant* parts of dmesg output (i.e. relating to the disk probes) would also be interesting. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply. For more information, see http://www.lemis.com/questions.html 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-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 19: 9: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id 9DD4037B423 for ; Mon, 9 Apr 2001 19:09:02 -0700 (PDT) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.11.3) with SMTP id f3A276R24461; Mon, 9 Apr 2001 22:07:07 -0400 (EDT) (envelope-from matt@gsicomp.on.ca) Message-ID: <008901c0c162$8a684960$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Conrad Sabatier" , "Bob K" Cc: References: Subject: Re: supfile idea (was Re: Releases) Date: Mon, 9 Apr 2001 22:04:13 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 09-Apr-2001 Bob K wrote: > > On Mon, 9 Apr 2001, Mike Meyer wrote: > > > > [snip] > >> Matthew Emmerton types: > >> > In the case of people running -CURRENT on a production machine, that's > >> > just > >> > a plain and simple mistake. Ever wonder how someone who barely knows how > >> > to > >> > use cvsup and make world manages to obtain -CURRENT in the first place? > >> > >> No, because it happens to everyone who uses the standard-supfile in > >> the /usr/share/examples/cvsup. I think that stable-supfile should > >> vanish from that directory, and standard-supfile should be right for > >> the branch the system came from, no matter which branch that was. > > [snip] I like the idea of stable-supfile, so it should stay. standard-supfile should *definitely* refer to the -REL in which it is a part of. In that case, a novice user who doesn't change anything would end up cvsup'ing code that they already have on their system or on CD - no harm done. Further, they'd actually have to RTFM to figure out what tags to use to get what they really want. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 19:13:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from krycek.zoominternet.net (krycek.zoominternet.net [63.67.120.9]) by hub.freebsd.org (Postfix) with SMTP id 4490537B422 for ; Mon, 9 Apr 2001 19:13:08 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 7340 invoked from network); 10 Apr 2001 02:12:43 -0000 Received: from acs-24-154-35-235.zoominternet.net (HELO cvzoom.net) (24.154.35.235) by krycek.zoominternet.net with SMTP; 10 Apr 2001 02:12:43 -0000 Message-ID: <3AD26C2D.CD7049F0@cvzoom.net> Date: Mon, 09 Apr 2001 22:13:01 -0400 From: Donn Miller X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Emmerton Cc: Conrad Sabatier , Bob K , stable@FreeBSD.ORG Subject: Re: supfile idea (was Re: Releases) References: <008901c0c162$8a684960$1200a8c0@gsicomp.on.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Emmerton wrote: > I like the idea of stable-supfile, so it should stay. standard-supfile > should *definitely* refer to the -REL in which it is a part of. In that > case, a novice user who doesn't change anything would end up cvsup'ing code > that they already have on their system or on CD - no harm done. Personally, I think "standard-supfile" should be renamed "current-supfile", because it cvsups -current. Also, put some kind of warning in there that states you are about to cvsup an unstable, untested development version of FreeBSD. I think unstable-supfile is another good possibility. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 20:23:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nanguo.chalmers.com.au (gateway.chalmers.com.au [203.1.96.1]) by hub.freebsd.org (Postfix) with ESMTP id 1BD5937B422 for ; Mon, 9 Apr 2001 20:23:25 -0700 (PDT) (envelope-from robert@chalmers.com.au) Received: from carbon (carbon.chalmers.com.au [203.1.96.26]) by nanguo.chalmers.com.au (8.11.0/8.11.0) with SMTP id f3A3PHU13760 for ; Tue, 10 Apr 2001 13:25:19 +1000 (EST) From: "Robert" To: "FreeBSD" Subject: 4.3-RC sticking here after a cvsup? What's up doc? Date: Tue, 10 Apr 2001 13:26:32 +1000 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.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could some kind sould tell me what's wrong here please? Thansk Robert .......... after five hours plus, I get this. ===> ../secure/lib/libcrypt sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 bsd.README bsd.cpu.mk bs d.dep.mk bsd.doc.mk bsd.docb.mk bsd.info.mk bsd.kern.mk bsd.kmod.mk bsd.lib.mk b sd.libnames.mk bsd.man.mk bsd.obj.mk bsd.own.mk bsd.port.mk bsd.port.post.mk bs d.port.pre.mk bsd.port.subdir.mk bsd.prog.mk bsd.sgml.mk bsd.subdir.mk sys.mk / usr/obj/usr/src/i386/mk usage: install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-v] [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop in /usr/src/secure/lib/libcrypt. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 20:35: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from Mail6.nc.rr.com (fe6.southeast.rr.com [24.93.67.53]) by hub.freebsd.org (Postfix) with ESMTP id 3697037B423 for ; Mon, 9 Apr 2001 20:34:58 -0700 (PDT) (envelope-from bts@babbleon.org) Received: from babbleon.org ([66.26.250.181]) by Mail6.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Mon, 9 Apr 2001 23:34:52 -0400 Message-ID: <3AD27F41.42FCB6BC@babbleon.org> Date: Mon, 09 Apr 2001 23:34:25 -0400 From: The Babbler Organization: None to speak of X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Yann Sommer Cc: freebsd-stable@freebsd.org Subject: Re: Why not stick with [STABLE] [Was: RE: Releases] References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yann Sommer wrote: > > Heya all, > > I've been following this thread with some extra attention, since I remember > beeing new to FreeBSD and complaining about a dedicated Server I ordered, > running BETA. It is just, as has been mentioned a few times before on this > list, against what other programms use for version naming. > But, in my humble opinion I think the easiest solution has not been > mentioned here before. Why not just suffix the old version description to > stable, like: > > 4.3-STABLE-BETA > 4.3-STABLE-RC > 4.3-STABLE-FINAL > > or something in that direction. The essential word "STABLE" which gives the > newer users the trust in a system (allthough it's kind of stupid after > knowing the exact naming, but heh, nobody gets born with all knowledge ;), > and at the same time sticks with the naming BSD users are used to. > Something in that direction might be good, but the proposal in & of itself wouldn't work if BSD sticks with the current scheme whereby the number isn't incremented 'til the first Beta, becuase the entire sequence would then be: 4.3-STABLE-BETA 4.3-STABLE-RC 4.3-STABLE-FINAL 4.3-STABLE (huh??? Now we get questions later) 4.4-STABLE-BETA but maybe: 4.3-STABLE-ENCHANCED or 4.3-STABLE-POSTFINAL or something; or or 4.3-STABLE-BETA 4.3-STABLE-RC 4.3-STABLE-FINAL 4.4-STABLE-DEVEL (bump up the # at the beginning of "ordinary time" rather than the end) 4.4-STABLE-BETA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 20:48: 2 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nanguo.chalmers.com.au (gateway.chalmers.com.au [203.1.96.1]) by hub.freebsd.org (Postfix) with ESMTP id 2525A37B422 for ; Mon, 9 Apr 2001 20:47:54 -0700 (PDT) (envelope-from robert@chalmers.com.au) Received: from carbon (carbon.chalmers.com.au [203.1.96.26]) by nanguo.chalmers.com.au (8.11.0/8.11.0) with SMTP id f3A3npU14469 for ; Tue, 10 Apr 2001 13:49:51 +1000 (EST) From: "Robert" To: Subject: why not... RE: Why not stick with [STABLE] [Was: RE: Releases] Date: Tue, 10 Apr 2001 13:51:06 +1000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal In-Reply-To: <3AD27F41.42FCB6BC@babbleon.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why not use like; Release Build Date 4.3 Build 020501 4.3 Build 030501 4.3 Build 100601 ......... 4.3 Build 200601 ......... 5.0 Build 201201 > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of The Babbler > Sent: Tuesday, 10 April 2001 1:34 PM > To: Yann Sommer > Cc: freebsd-stable@FreeBSD.ORG > Subject: Re: Why not stick with [STABLE] [Was: RE: Releases] > > > Yann Sommer wrote: > > > > Heya all, > > > > I've been following this thread with some extra attention, > since I remember > > beeing new to FreeBSD and complaining about a dedicated Server > I ordered, > > running BETA. It is just, as has been mentioned a few times > before on this > > list, against what other programms use for version naming. > > But, in my humble opinion I think the easiest solution has not been > > mentioned here before. Why not just suffix the old version > description to > > stable, like: > > > > 4.3-STABLE-BETA > > 4.3-STABLE-RC > > 4.3-STABLE-FINAL > > > > or something in that direction. The essential word "STABLE" > which gives the > > newer users the trust in a system (allthough it's kind of stupid after > > knowing the exact naming, but heh, nobody gets born with all > knowledge ;), > > and at the same time sticks with the naming BSD users are used to. > > > > Something in that direction might be good, but the proposal in & of > itself wouldn't work if BSD sticks with the current scheme whereby the > number isn't incremented 'til the first Beta, becuase the entire > sequence would then be: > > 4.3-STABLE-BETA > 4.3-STABLE-RC > 4.3-STABLE-FINAL > 4.3-STABLE (huh??? Now we get questions later) > 4.4-STABLE-BETA > > but maybe: > > 4.3-STABLE-ENCHANCED or 4.3-STABLE-POSTFINAL or something; or > > or > > 4.3-STABLE-BETA > 4.3-STABLE-RC > 4.3-STABLE-FINAL > 4.4-STABLE-DEVEL (bump up the # at the beginning of "ordinary > time" rather than the end) > 4.4-STABLE-BETA > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 21: 6:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nanguo.chalmers.com.au (gateway.chalmers.com.au [203.1.96.1]) by hub.freebsd.org (Postfix) with ESMTP id 7D18437B422 for ; Mon, 9 Apr 2001 21:06:32 -0700 (PDT) (envelope-from robert@chalmers.com.au) Received: from carbon (carbon.chalmers.com.au [203.1.96.26]) by nanguo.chalmers.com.au (8.11.0/8.11.0) with SMTP id f3A48TU14949 for ; Tue, 10 Apr 2001 14:08:29 +1000 (EST) From: "Robert" To: "FreeBSD" Subject: Doesn't matter - incomplete cvsup run.. dam. RE: 4.3-RC sticking here after a cvsup? What's up doc? Date: Tue, 10 Apr 2001 14:09:44 +1000 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.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ===> ../secure/lib/libcrypt > sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 bsd.README > bsd.cpu.mk bs > d.dep.mk bsd.doc.mk bsd.docb.mk bsd.info.mk bsd.kern.mk bsd.kmod.mk > bsd.lib.mk b > sd.libnames.mk bsd.man.mk bsd.obj.mk bsd.own.mk bsd.port.mk > bsd.port.post.mk > bs > d.port.pre.mk bsd.port.subdir.mk bsd.prog.mk bsd.sgml.mk bsd.subdir.mk > sys.mk / > usr/obj/usr/src/i386/mk > usage: install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 > file2 > install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 > ... > fileN directory > install -d [-v] [-g group] [-m mode] [-o owner] directory ... > *** Error code 64 > > Stop in /usr/src/secure/lib/libcrypt. > *** Error code 1 > > Stop in /usr/src/lib. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 21:18:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from never.tellme.com (never.tellme.com [209.157.156.27]) by hub.freebsd.org (Postfix) with ESMTP id E712A37B422; Mon, 9 Apr 2001 21:18:12 -0700 (PDT) (envelope-from dannyman@tellme.com) Received: by never.tellme.com (Postfix, from userid 501) id 8F1ED71658; Mon, 9 Apr 2001 21:18:12 -0700 (PDT) Date: Mon, 9 Apr 2001 21:18:12 -0700 From: Danny Howard To: Greg Lehey Cc: FreeBSD Questions , freebsd-stable@freebsd.org Subject: Re: fdisk & disklabel dont work! Message-ID: <20010409211812.P59290@tellme.com> References: <20010409185759.N59290@tellme.com> <20010410113808.K64481@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010410113808.K64481@wantadilla.lemis.com>; from grog@lemis.com on Tue, Apr 10, 2001 at 11:38:08AM +0930 X-Loop: djhoward@uiuc.edu Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay. Well, FWIW, fdisk -I does *not* work successfully for me, under any circumstances I've tried so far. I have found a work-around, though: TERM=cons25 # If serial console, set this to vt100 export TERM /stand/sysinstall nonInteractive=YES partition=all bootManager=standard \ disk=${disk} diskPartitionEditor diskPartitionWrite Woohah! Interestingly enough, I see the same complaints about there not being a disklabel, but my subsequent disklabel commands work. To whit: disk=${disk}s1 disklabel -r -w $disk auto disksize=`disklabel $disk | awk -F : '$1 == "sectors/unit" {print $2}'` [...] disklabel $disk | grep -v ' c:' > /tmp/mylabel disklabel -R -B $disk /tmp/mylabel And then some MAKEDEV, newfs, distributions, packages, config files, etc. Okay, so I'll need to test this some more, but this is a pleasant break-through for the evening. One which I hope will hold. :) This is way screwed up, imho. I might investigate some day as to why sysinstall can do what fdisk -I can not, but I have some machines that are overdue for installs. :) -danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 22:12:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id A888A37B424 for ; Mon, 9 Apr 2001 22:12:52 -0700 (PDT) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.3+3.4W/8.11.3) with ESMTP/inet id f3A5Cm892330 for ; Tue, 10 Apr 2001 14:12:50 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Urania) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 77 From: Makoto MATSUSHITA To: stable@freebsd.org Subject: 4.3-RC2: broken crypto/CHECKSUM.MD5 Date: Tue, 10 Apr 2001 14:12:30 +0900 Message-Id: <20010410141230H.matusita@jp.FreeBSD.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG IIRC, I've sent a email before about this, but nobody doesn't pay attention nor fix src/release/Makefile... In our all distribution, including 4.3-RC2, have incorrect CHECKSUM.MD5 file in crypto/ distribution. Here is the current distribution: % ls 4.3-RC2 RELNOTES.TXT compat1x dict ports ABOUT.TXT TROUBLE.TXT compat20 doc proflibs ERRATA.TXT UPGRADE.TXT compat21 floppies src HARDWARE.TXT XF86336 compat22 games tools INSTALL.TXT bin compat3x info LAYOUT.TXT catpages compat4x manpages README.TXT cdrom.inf crypto packages % cd crypto % ls CHECKSUM.MD5 crypto.inf krb5.ad scrypto.aj scrypto.aw crypto.aa crypto.mtree krb5.ae scrypto.ak scrypto.ax crypto.ab install.sh krb5.inf scrypto.al scrypto.inf crypto.ac krb4.aa krb5.mtree scrypto.am skrb4.aa crypto.ad krb4.ab scrypto.aa scrypto.an skrb4.inf crypto.ae krb4.ac scrypto.ab scrypto.ao skrb5.aa crypto.af krb4.ad scrypto.ac scrypto.ap skrb5.inf crypto.ag krb4.ae scrypto.ad scrypto.aq ssecure.aa crypto.ah krb4.inf scrypto.ae scrypto.ar ssecure.inf crypto.ai krb4.mtree scrypto.af scrypto.as crypto.aj krb5.aa scrypto.ag scrypto.at crypto.ak krb5.ab scrypto.ah scrypto.au crypto.al krb5.ac scrypto.ai scrypto.av % cat CHECKSUM.MD5 MD5 (crypto.aa) = 21a7caed7fe026d89f27bc70f39326e5 MD5 (crypto.ab) = 262d9afa063c0bbb3707caf5b1a581f9 MD5 (crypto.ac) = 03bda022337686b15cfa6da0189a1e77 MD5 (crypto.ad) = 14ce9b4faa2e5770f2c68aedb7094ccc MD5 (crypto.ae) = b1bead2decc9e6da1930fc6a7d1528b3 MD5 (crypto.af) = 296176d36a620d744710fce74c776761 MD5 (crypto.ag) = c8d207f74bb4bcf91b0b81155e4d6740 MD5 (crypto.ah) = 6b327235f11f4979a4d80afa442191ba MD5 (crypto.ai) = 7c9a113aba4737c5aadd4443ffc2262a MD5 (crypto.aj) = b17b78ba8ff80155e2e471cfe68e88aa MD5 (crypto.ak) = 91e8a974469f818c0ec165b65c0056b7 MD5 (crypto.al) = e695f85d27217fa1d4a498de4599e991 MD5 (crypto.inf) = e2c02d036c392eadcfbf783621c9d7ad MD5 (crypto.mtree) = fd90e2e35d7a944e091dddf5a557498f MD5 (install.sh) = da31ec9cb344ce54d9873ecfc4d38821 MD5 (krb4.aa) = 02ed52bed52a2ff4e562ae8951586529 MD5 (krb4.ab) = 011b930316980c52ff75a6fa4802108f MD5 (krb4.ac) = 077e7342b59586d802cd026ad58304bd MD5 (krb4.ad) = 4ab31b7583ac3c7b995556060749df75 MD5 (krb4.ae) = 0ada03986b2daf11453bd7193acc113e MD5 (krb4.inf) = ba77a7b0442a1a20ac9ee525ef4e0305 MD5 (krb4.mtree) = 574a343a6a3008722fba688d036edc23 MD5 (krb5.aa) = d1d4c0d40644934e0506aeb452b45cb0 MD5 (krb5.ab) = 89b72bcce2c4f082a32687b0f4365399 MD5 (krb5.ac) = f6f1125efd6445266f83bebde6c60b86 MD5 (krb5.ad) = bfb6860a3c9f026bdb347160f0e28ee3 MD5 (krb5.ae) = b546b1be7cf373417e7b389e1c8ad42e MD5 (krb5.inf) = 19edbc53d1ecf11252496c78a4fdfcfa MD5 (krb5.mtree) = e9a0cb9c1f5cfcad4b7f2996e0cd7d43 You can easily find that "there are no MD5 checksum of scrypto.*, skrb4.*, skrb5.*, and ssecure.*"; src/CHECKSUM.MD5 knows about that, but it's strange that since all scrypto/skrb4/skrb5/ssecure are not in src/. It's easy to fix: 'release.7' target in src/release/Makefile does move all crypto-related source distributions to crypto/ directory. We should recreate src/CHECKSUM.MD5 and crypto/CHECKSUM.MD5 after moving all crypto-related source distributions. *** P.S.: Same story should be applied to 5-current. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 22:23:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from poontang.schulte.org (poontang.schulte.org [209.134.156.197]) by hub.freebsd.org (Postfix) with ESMTP id 1DD6637B422 for ; Mon, 9 Apr 2001 22:23:32 -0700 (PDT) (envelope-from christopher@schulte.org) Received: from TARMAP.schulte.org (tarmap.schulte.org [209.134.156.198]) by poontang.schulte.org (8.12.0.Beta5/8.12.0.Beta5) with ESMTP id f3A5NVIr048997 for ; Tue, 10 Apr 2001 00:23:31 -0500 (CDT) Message-Id: <5.1.0.12.0.20010410001159.00aac170@pop.schulte.org> X-Sender: schulte@pop.schulte.org X-Mailer: QUALCOMM Windows Eudora Version 5.1.0.12 (Beta) Date: Tue, 10 Apr 2001 00:22:28 -0500 To: freebsd-stable@freebsd.org From: Christopher Schulte Subject: 4.3 release schedule still on track for April 15? (for Jordan) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan, Is the 4.3 release date still on track for April 15, per your revised schedule as posted March 22 to this list? I'm planning a server maintenance window for later this month, and if possible I'd like to get some production boxes to 4.3-STABLE at the same time. Kill two or more birds. Thanks, -- Christopher Schulte Finger for PGP key, or for UNIX impaired: http://noc.schulte.org/cgi-bin/noc/finger.cgi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 9 22:56:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id F17B737B422 for ; Mon, 9 Apr 2001 22:55:59 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id AAA03087; Tue, 10 Apr 2001 00:55:53 -0500 (CDT) (envelope-from jeff-ml@mountin.net) Received: from dial-88.tnt1.rac.cyberlynk.net(209.224.182.88) by peak.mountin.net via smap (V1.3) id sma003042; Tue Apr 10 00:55:15 2001 Message-Id: <4.3.2.20010409225422.0271d820@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Tue, 10 Apr 2001 00:54:00 -0500 To: "Matthew Emmerton" , "Conrad Sabatier" , "Bob K" From: "Jeffrey J. Mountin" Subject: Re: supfile idea (was Re: Releases) Cc: In-Reply-To: <008901c0c162$8a684960$1200a8c0@gsicomp.on.ca> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=====================_605628960==_" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --=====================_605628960==_ Content-Type: text/plain; charset="us-ascii"; format=flowed At 10:04 PM 4/9/01 -0400, Matthew Emmerton wrote: >I like the idea of stable-supfile, so it should stay. standard-supfile >should *definitely* refer to the -REL in which it is a part of. In that >case, a novice user who doesn't change anything would end up cvsup'ing code >that they already have on their system or on CD - no harm done. Further, >they'd actually have to RTFM to figure out what tags to use to get what they >really want. Another issue that is common here and wonder if you are aware of this file: /usr/src/share/examples/cvsup/README Frankly I think there should be the readme and *ONE* example. There is a lot of duplication and since most use only one cvsupfile, possibly less confusion. I see there is a disclaimer for adding the ports collection in the "standard" version. Use that as a base and these: ports-supfile stable-supfile standard-supfile www-supfile Can be rolled into one, call it "new-supfile" for now, and now there are only: README cvs-supfile gnats-supfile new-supfile refuse refuse.README Less choices and changing "new" to "standard" should make it the obvious choice and not require building up a typical supfile. Not sure that the gnats could be folded in, as it uses "release=current" rather than "release=cvs" and does not use a "tag=" and having one might throw it off (John? anyone?). Also might not be a good idea to fold it in, since only those that work on PR's might want a local copy. Another common issue is when using individual collection vs src-all. Many time a person has src-crypto and no src-secure. Or worse, someone points out only one of them is missing and neglects to mention the other. It would be difficult to say what is optional, but if you consider /etc/defaults/make.conf *and* lose the comments before the crypto collections (outdated, but might be necessary in the future) then something like: # required by default #src-base #src-bin #src-contrib #src-etc #src-games #src-gnu #src-include #src-lib #src-libexec #src-sbin #src-share #src-sys #src-usrbin #src-usrsbin #src-crypto #src-secure #src-sys-crypto # optional #src-kerberos5 #src-kerberosIV #src-release #src-tools #src-eBones And perhaps a quick reference to make.conf and a suggestion to pull in src-release even if one doesn't wish to roll their own for the text files that everyone tracking stable *should* know about. Perhaps a quick reference to the handbook or FAQ to avoid cluttering the file like this. # comment the following if "NOGAMES=yes" in make.conf #src-games # un-comment the following if "MAKE_KERBEROS5=yes" in make.conf etc... The idea is to make it simple, central, and with simple comments that should avoid the common mistakes. And yes, I am aware that removing the supfiles for ports, doc, www, and stable would require a change to make.conf. They could remain and the standard might be updated to an all-in-one supfile rather than for -current. Perhaps all that is needed is a comment in the README to refer to the handbook for those new to fetching the source and what should be used when using individual collections. Minimal clutter and hopefully get more to RTFM before diving in. Mind right now I'm not sure where the docs are and how satisfactory they are (no insult to the docs people). Was going to update them, but find the docproj has bloated quite a bit in recent history. Might want to warn those fetching doc-all what it will take to build that beast. 8-) Can Kris or someone else say if src-sys-crypto is required or not. There was a discussion on this a long time back, but recall the answer was fuzzy and it *might* be required in the future for in-kernel crypto. I do list it when suggesting a trimmed down list rather than src-all. It's small and safer to do so. Rather than reply to another will agree with Donn that "standard" should be "current" to avoid confusion. Then making "standard" an all inclusive (or should I say "mostly") example might be a good idea along with pointing to documentation. Of course getting users to read things is always an issue. All the documentation in the world won't stop a (l)user from getting a bad case of LLMF. My question at this point is before changing a thing it would be best to find out how most get lost and then work out a remedy, which I could have stated in the first place and had less fun trying to cover a number of possibilities. It would be nice to force a new user to a certain minimum of RTFM, but might leave some cold and certainly won't stop them from not doing so, screwing up, and asking "why?" Attaching a copy of my idea of what standard-supfile should be like. --=====================_605628960==_ Content-Type: application/octet-stream; name="standard-supfile-new" Content-Transfer-Encoding: x-uuencode Content-Disposition: attachment; filename="standard-supfile-new" begin 600 standard-supfile-new M(R`D1G)E94)31#H@6]U7-T M96T@96%S:6QY"B,@86YD(&5F9FEC:65N=&QY("AF87(@;6]R92!S;R!T:&%N M('=I=&@@2!S97)V97(L M('EO=2!S:&]U;&0@2!W:7-H('1O(&-H86YG92!S;VUE(&]F('1H92!S971T:6YG M6]U(&%R92!#5E-U<'!I;F<@82!L87)G92!N=6UB97(@;V8* M(PD)8V]L;&5C=&EO;G,L('EO=2!W:6QL(&)E(&AA2!M=7-T(&5X:7-T(&EN(&]R9&5R('1O(')U;B!#5E-U<"X*(PHC(R,C M(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C M(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C"@HC($1E9F%U;'1S('1H M870@87!P;'D@=&\@86QL('1H92!C;VQL96-T:6]N'0@;&EN92!T;R!U#TO=7-R"B,@5&AE(&9O;&QO=VEN9R!L:6YE(&ES(&9O6]U('=A;G0@=&\@=')A8VL@+5-404),12P@;&5A=F4@=&AI7,* M(W-R8RUT;V]L7!T;PH*(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C M(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C M(PHC"B,@1$%.1T52(2`@5T%23DE.1R$@($Q/3TL@3U54(2`@5D]24TE#2%0A M"B,*(R!4:&4@9F]L;&]W:6YG(&-O;&QE8W1I;VYS(&%R92!C;VUM;VX@=&\@ M86QL(&)R86YC:&5S+@HC(`HC(%1H:7,@;&EN92!-55-4(&)E('5N8V]M;65N M=&5D('=H96X@=7-I;F<@86YY(&]F('1H90HC(&-O;&QE8W1I;VYS(&)E>6]N M9"!T:&ES('!O:6YT('5N;&5S6]U('5S92!A;GD@ M;V8@=&AE"B,@;W1H97(@:6YD:79I9'5A;"!C;VQL96-T:6]N6]U2!I9B!I=`HC(&ES(&YO="!K97!T('5P('1O(&1A=&4N M"B-P;W)T0HC M<&]R=',M8V%D"B-P;W)T7-U=&EL#$Q M"B-P;W)T#$Q+7=M"@HC(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C M(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C M(R,C"B,@"B,@3F]N+6-O9&4@8V]L;&5C=&EO;G,*(R`*(R,C(R,C(R,C(R,C M(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C M(R,C(R,C(R,C(R,C(R,C(R,C(R,C(PH*(R!4:&ES('=I;&P@0HC=W=W"@`` ` end --=====================_605628960==_ Content-Type: text/plain; charset="us-ascii"; format=flowed Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve --=====================_605628960==_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 0:39:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id 008F537B422 for ; Tue, 10 Apr 2001 00:39:42 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id CAA03740; Tue, 10 Apr 2001 02:39:39 -0500 (CDT) (envelope-from jeff-ml@mountin.net) Received: from dial-88.tnt1.rac.cyberlynk.net(209.224.182.88) by peak.mountin.net via smap (V1.3) id sma003737; Tue Apr 10 02:39:28 2001 Message-Id: <4.3.2.20010410012424.02b2f580@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Tue, 10 Apr 2001 02:38:54 -0500 To: "Yann Sommer" From: "Jeffrey J. Mountin" Subject: Re: Why not stick with [STABLE] [Was: RE: Releases] Cc: stable@FreeBSD.ORG In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:18 PM 4/9/01 -0700, Yann Sommer wrote: >Heya all, > >I've been following this thread with some extra attention, since I remember >beeing new to FreeBSD and complaining about a dedicated Server I ordered, >running BETA. It is just, as has been mentioned a few times before on this >list, against what other programms use for version naming. >But, in my humble opinion I think the easiest solution has not been >mentioned here before. Why not just suffix the old version description to >stable, like: > >4.3-STABLE-BETA >4.3-STABLE-RC >4.3-STABLE-FINAL The last is really 4.3-RELEASE or would it be 4.4-RELEASE, which opens up one more thing to confuse some. Mind I'm used to current naming. >or something in that direction. The essential word "STABLE" which gives the >newer users the trust in a system (allthough it's kind of stupid after >knowing the exact naming, but heh, nobody gets born with all knowledge ;), >and at the same time sticks with the naming BSD users are used to. Fact is what friggin difference does make what the build calls itself. Those that track the RELENG_4 branch should know that it doesn't matter what it calls itself when doing a uname, it is the same branch at different points or periods of time. The concept of how the naming is done is not an issue and cannot be solved by using a different or modified scheme. Rather the documentation should cover this. Just a matter of explaining what each period means in the handbook and/or/both the FAQ... When running -stable normally 'uname -r' will return a version such as 4.2-STABLE, which means the system is running code post 4.2-RELEASE. During the code freeze prior to the release of version 4.3 the name will change to 4.3-BETA, followed by 4.3-RC, and at a certain time a revision tag will be laid down and called 4.3-RELEASE. And a matter of minutes after that Jordan will change it over to 4.3-STABLE and the free-for-all will start anew. A chart might allow for a better visualization of the development cycle of a branch, noting the revision tags and what the system calls itself (found in src/sys/conf/newvers.sh for those that don't know). Would say cvsup.html is a good place for a quick note and somewhere else a chart explaining the development cycle that also show what the system will call itself at that point. Say an additional FAQ entry Then again if anyone perpetuating this thread had bothered to pay attention to the list (RYFM) and check out Nik's last message would know about: http://www.freebsd.org/FAQ/book.html#RELEASE-CANDIDATE and might find: http://www.freebsd.org/FAQ/book.html#STABLE Think that covers it... Don't forget to thank those working on the documentation for this solution and offer help if you are not happy with the way things are or praise if you are happy. There is a list for that hint-hint, so we need not do nothing more than point it out the next time this comes up and not bother to continue this discussion. Happy reading! Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 0:57:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fat.ti.ru (fat.ti.ru [212.1.224.35]) by hub.freebsd.org (Postfix) with ESMTP id 25F2D37B424 for ; Tue, 10 Apr 2001 00:57:20 -0700 (PDT) (envelope-from Martin@McFlySr.Kurgan.Ru) Received: from 127.0.0.1 (fat.ti.ru [212.1.224.35]) by fat.ti.ru (Postfix) with ESMTP id 3644DD923 for ; Tue, 10 Apr 2001 11:57:18 +0400 (MSD) Date: Tue, 10 Apr 2001 11:57:18 +0400 From: Martin McFlySr X-Mailer: The Bat! (v1.51) Business Reply-To: Martin McFlySr Organization: Back To The Future X-Priority: 3 (Normal) Message-ID: <120127513314.20010410115718@McFlySr.Kurgan.Ru> To: freebsd-stable@FreeBSD.ORG Subject: 4.3-RC, strange with ep0 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello freebsd-stable@FreeBSD.ORG, in machine was installed: fxp0, fxp1, fxp2, xl0, ep0. (ep0 record included in kernel file) After cvsup/make world/make-install kernel/reboot ( FreeBSD 4.3-RC #0: Tue Apr 10 01:02:55 MSD 2001 ) ep1 was appeared instead ep0. I hope, in 4.3-R|ELEASE this bug was fixed? -- Tuesday, 10 April 2001, 11:49 Best regards from future, Martin McFlySr, HillDale. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 1:46:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nbnotomail2.nesbittburns.ca (torfw1.nesbittburns.com [192.139.71.69]) by hub.freebsd.org (Postfix) with ESMTP id 24B3B37B422 for ; Tue, 10 Apr 2001 01:46:31 -0700 (PDT) (envelope-from Rodney.Lewis@bmonb.com) Received: by nbnotomail2.nesbittburns.ca with Internet Mail Service (5.5.2650.21) id <2T2TRJ9A>; Tue, 10 Apr 2001 04:46:40 -0400 Message-ID: <83773E236646D3118EAE00508B12C8FE7C7EB5@nbnelomail2.nesbittburns.ca> From: "Lewis, Rodney" To: "'freebsd-stable@freebsd.org'" Subject: installworld freezes in /usr/lib Date: Tue, 10 Apr 2001 04:46:06 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, =20 Last night I tried to upgrade to 4.3RC2 but have had problems. Here's = what I did. Sorry for the brief info but I am not at my machine. Any = insight would be appreciated. I cvsup'd to latest. Which was only about 4 files as I have been = keeping track but not installed since March 20th or there abouts. Performed buildworld, no problems Performed buildkernel, no problems Performed install kernel, no problems Rebooted into single user mode Performed installworld, when the install gets to anything in /usr/lib = the box freezes. When I reboot back into single usermode and try to run = more or man or run installworld it complains that libs are corrupt. I can = replace them from /usr/obj and the apps will start working. I did manage to boot up to multimode and copied by hand the new = /usr/libs into /usr/libs and tried to installworld again but it just barfed = somewhere else in /usr/lib. Libs it did fail on were libc.so.4, libmreadline.a, libma.a, libcurses = and more I think. I saw a post that was similar earlier and his cvs tree was corrupt does = this sound similar. Thanks Rodney Lewis=20 This message and any attachments are confidential to the ordinary user = of the e-mail address to which it was addressed and may also be = privileged. If you are not the addressee, you may not copy, forward, disclose or use = any part of the message or its attachments and should delete them from your system and kindly notify the sender immediately by return e-mail. Any opinions contained in this message are those of the author and are not = given or endorsed by the Bank of Montreal Group of Companies including BMO = Nesbitt Burns Group company or office through which this message is sent unless otherwise clearly indicated in this message. Internet communications = cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, arrive late or contain viruses. The = sender therefore does not accept liability for any errors or omissions in the content of this message which arise as a result of Internet = transmission. Unless otherwise stated, this transmission is neither an offer nor a solicitation of an offer to sell or purchase any security.=20 Ce message, ainsi que tout document pouvant y =EAtre joint, est = confidentiel et destin=E9 =E0 l'utilisateur habituel de l'adresse de courrier = =E9lectronique =E0 qui il s'adresse, et pourrait =EAtre privil=E9gi=E9. Si vous n'=EAtes = pas le destinataire, il vous est express=E9ment interdit de copier, = d'acheminer, de divulguer ou d'utiliser ce message et les documents joints, le cas = =E9ch=E9ant, en totalit=E9 ou en partie. Nous vous saurions gr=E9 de les supprimer = et d'avertir l'exp=E9diteur imm=E9diatement, par retour de courrier. Les = opinions que contient ce message sont celles de l'auteur et ne sont ni = donn=E9es, ni approuv=E9es par le Groupe de soci=E9t=E9s de la Banque de Montr=E9al, = BMO Nesbitt Burns ou la succursale ou le bureau d'o=F9 provient le message, =E0 = moins qu'une mention =E0 cette fin ne soit faite dans le message. Il n'est pas = possible de garantir que les communications par Internet sont s=FBres ou exemptes d'erreurs puisque les renseignements pourraient =EAtre intercept=E9s, = corrompus, =E9gar=E9s ou retard=E9s ou pourraient contenir des virus. = L'exp=E9diteur se d=E9gage donc de toute responsabilit=E9 =E0 l'=E9gard d'erreurs ou d'omissions = dans le contenu du message d=E9coulant d'une transmission par Internet. =C0 = moins d'une mention contraire, cette transmission ne constitue ni une offre ni une sollicitation d'une offre de vente ou d'achat de titres de quelque = nature que ce soit. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 3: 5: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tech.pcx.si (tech.pcx.si [212.18.46.56]) by hub.freebsd.org (Postfix) with ESMTP id 69D0E37B423; Tue, 10 Apr 2001 03:04:46 -0700 (PDT) (envelope-from cuk@cuk.nu) Received: from cuk.nu (bsd.pcx.si [192.168.1.4]) by tech.pcx.si (Postfix) with ESMTP id 31262F8A01; Tue, 10 Apr 2001 12:04:44 +0200 (CEST) Message-ID: <3AD2DB66.FA4A4F75@cuk.nu> Date: Tue, 10 Apr 2001 12:07:34 +0200 From: Marko Cuk Organization: Pcx computers d.o.o., Tehnika X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-ipfw@freebsd.org Subject: NATd & high internal load - help Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello !! I have problems with high load on FBSD box. First I had the 4.2 STABLE , then I cvsuped to 4.3-RC. Same thing. When high traffic occurs on 100mbit hub, to wich is fxp0 connected, load and processor usage on natd process is very high and after a while it won't pass packets anymore to outside world. The configuration: -Celeron 400 and BX motherboard, 512Mb RAM PC100. -fxp Intel 10/100 cards fxp0 - connected to hub and interface has routable IP, because it has a network behind fxp1 - connected to outside world Routing is working, everything was ok. Then I want to set an alias to fxp0 with 192.168.x.x unregistered class and make NATd working and to hide most of client computers and leave the routable IPs for servers, etc. It's very strange. I have NATd at home and it is working without any problems. The MAXUSERS variable is set to 196 and netstat -m: 261/944/14336 mbufs in use (current/peak/max): 236 mbufs allocated to data 25 mbufs allocated to packet headers 206/438/3584 mbuf clusters in use (current/peak/max) 1112 Kbytes allocated to network (10% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines Top: last pid: 9475; load averages: 0.97, 0.51, 0.35 up 8+09:49:40 11:47:42 48 processes: 4 running, 44 sleeping CPU states: 14.0% user, 0.0% nice, 71.3% system, 9.3% interrupt, 5.4% idle Mem: 170M Active, 246M Inact, 58M Wired, 20M Cache, 61M Buf, 6752K Free Swap: 2000M Total, 48K Used, 2000M Free PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 9475 root 36 0 448K 228K RUN 0:12 28.87% 24.56% ping /etc/rc.conf firewall_enable="YES" firewall_type="/etc/rc.pcx" firewall_script="/etc/rc.firewall" firewall_quiet="YES" natd_program="/sbin/natd" natd_enable="YES" natd_flags="-f /etc/natd.conf" /etc/natd.conf interface fxp1 <-----if I put an IP here, it's the same problem #log yes log_denied yes unregistered_only yes #use_sockets yes #same_ports yes #dynamic yes I also comment those things as Blaz Zupan told me. ipfw natd rule: add 80 divert natd ip from any to any via fxp1 Now I don't have any idea, what to do ? Did I miss something ? What did I do wrong ? I have also 84 ipfw rules for firewall ( most of them reset and deny and a few dummynet pipes ). Is the processor too slow for that ? Cuk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 3:12: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tech.pcx.si (tech.pcx.si [212.18.46.56]) by hub.freebsd.org (Postfix) with ESMTP id EEFCD37B422; Tue, 10 Apr 2001 03:11:30 -0700 (PDT) (envelope-from cuk@nu.cuk.nu) Received: from nu.cuk.nu (bsd.pcx.si [192.168.1.4]) by tech.pcx.si (Postfix) with ESMTP id 1EE79F8A04; Tue, 10 Apr 2001 12:11:28 +0200 (CEST) Message-ID: <3AD2DCFA.83888C38@nu.cuk.nu> Date: Tue, 10 Apr 2001 12:14:18 +0200 From: Marko Cuk Organization: Pcx computers d.o.o., Tehnika X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-ipfw@freebsd.org Subject: NATd & high internal load - help Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello !! I have problems with high load on FBSD box. First I had the 4.2 STABLE , then I cvsuped to 4.3-RC. Same thing. When high traffic occurs on 100mbit hub, to wich is fxp0 connected, load and processor usage on natd process is very high and after a while it won't pass packets anymore to outside world. The configuration: -Celeron 400 and BX motherboard, 512Mb RAM PC100. -fxp Intel 10/100 cards fxp0 - connected to hub and interface has routable IP, because it has a network behind fxp1 - connected to outside world Routing is working, everything was ok. Then I want to set an alias to fxp0 with 192.168.x.x unregistered class and make NATd working and to hide most of client computers and leave the routable IPs for servers, etc. It's very strange. I have NATd at home and it is working without any problems. The MAXUSERS variable is set to 196 and netstat -m: 261/944/14336 mbufs in use (current/peak/max): 236 mbufs allocated to data 25 mbufs allocated to packet headers 206/438/3584 mbuf clusters in use (current/peak/max) 1112 Kbytes allocated to network (10% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines Top: last pid: 9475; load averages: 0.97, 0.51, 0.35 up 8+09:49:40 11:47:42 48 processes: 4 running, 44 sleeping CPU states: 14.0% user, 0.0% nice, 71.3% system, 9.3% interrupt, 5.4% idle Mem: 170M Active, 246M Inact, 58M Wired, 20M Cache, 61M Buf, 6752K Free Swap: 2000M Total, 48K Used, 2000M Free PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 9475 root 36 0 448K 228K RUN 0:12 28.87% 24.56% ping /etc/rc.conf firewall_enable="YES" firewall_type="/etc/rc.pcx" firewall_script="/etc/rc.firewall" firewall_quiet="YES" natd_program="/sbin/natd" natd_enable="YES" natd_flags="-f /etc/natd.conf" /etc/natd.conf interface fxp1 <-----if I put an IP here, it's the same problem #log yes log_denied yes unregistered_only yes #use_sockets yes #same_ports yes #dynamic yes I also comment those things as Blaz Zupan told me. ipfw natd rule: add 80 divert natd ip from any to any via fxp1 Now I don't have any idea, what to do ? Did I miss something ? What did I do wrong ? I have also 84 ipfw rules for firewall ( most of them reset and deny and a few dummynet pipes ). Is the processor too slow for that ? Cuk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 4: 3: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 0A2A337B424 for ; Tue, 10 Apr 2001 04:03:04 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 10 Apr 2001 12:03:03 +0100 (BST) To: Greg Lehey Cc: Danny Howard , FreeBSD Questions , iedowse@maths.tcd.ie Subject: Re: fdisk & disklabel dont work! In-Reply-To: Your message of "Tue, 10 Apr 2001 11:38:08 +0930." <20010410113808.K64481@wantadilla.lemis.com> Date: Tue, 10 Apr 2001 12:03:03 +0100 (BST) From: iedowse@maths.tcd.ie Message-ID: <200104101203.aa96007@walton.maths.tcd.ie> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -------- In message <20010410113808.K64481@wantadilla.lemis.com>, Greg Lehey writes: >> # disklabel -r -w da0s1 auto >> /kernel: da0: cannot find label (no disk label) >> /kernel: da0: cannot find label (no disk label) >> /kernel: da0s1: cannot find label (no disk label) >> /kernel: da0s1: cannot find label (no disk label) >> /kernel: da0: cannot find label (no disk label) >> /kernel: da0: cannot find label (no disk label) >> /kernel: da0s1: cannot find label (no disk label) >> /kernel: da0s1: cannot find label (no disk label) >> disklabel: ioctl DIOCGDINFO: Invalid argument >> disklabel: auto: unknown disk type >> >> Anyone has any idea? Maybe there's something really subtle that I am doing >> wrong? > >Well, you're not showing much output. The output of disklabel and >fdisk with no options would be interesting, as would the exact kernel >error messages you're seeing. The *relevant* parts of dmesg output >(i.e. relating to the disk probes) would also be interesting. There was a major improvement to the disklabel code just after 4.2-RELEASE, and the above errors suggest that system does not include these changes. For 4.2-RELEASE and earlier, it is possible to use fdisk and disklabel to prepare a new disk in non-dedicated mode, but you must manually construct a text prototype and use the "-R" option. e.g. # cat > protofile type: SCSI # for ide disks use "ESDI" disk: da0s1 bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 522 sectors/unit: 8385930 rpm: 3600 interleave: 1 8 partitions: c: 8385930 0 unused 0 0 ^D # disklabel -R -r da0s1 protofile This is why most people use sysinstall :-) Since the end of November 2000, the version of disklabel in -stable will work correctly with "disklabel -r -w da0s1 auto". Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 4:21:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nothing-going-on.demon.co.uk (unknown [194.128.198.234]) by hub.freebsd.org (Postfix) with ESMTP id 136AE37B42C for ; Tue, 10 Apr 2001 04:21:51 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id f3ABCNC02502; Tue, 10 Apr 2001 12:12:23 +0100 (BST) (envelope-from nik) Date: Tue, 10 Apr 2001 12:12:23 +0100 From: Nik Clayton To: Matthew Emmerton Cc: stable@FreeBSD.ORG Subject: Re: Releases Message-ID: <20010410121223.B749@canyon.nothing-going-on.org> References: <014a01c0c12e$e5e76f20$1200a8c0@gsicomp.on.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="Bn2rw/3z4jIqBvZU" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <014a01c0c12e$e5e76f20$1200a8c0@gsicomp.on.ca>; from matt@gsicomp.on.ca on Mon, Apr 09, 2001 at 03:54:32PM -0400 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Bn2rw/3z4jIqBvZU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 09, 2001 at 03:54:32PM -0400, Matthew Emmerton wrote: > Next, the case of the bind and ntpd updates. Yes, these were fixed > in -STABLE and -CURRENT very quickly, but were only documented in UPDATIN= G. > How many people who are running -RELEASE have this? That's right, none. = If > the "current release" box had an "Newsflash" or other such link to inform > users of 1) critical bugs that exist in the current release, and 2) HOWTOs > that show how to fix them, then a lot of the confusion surrounding these > fixes would be resolved. That's the "Errata" link. Suggestions for alternative text welcome. Note that the NTP bug hasn't had an advisory released yet (presumably because the security are busy working on it at the moment). > Finally, almost every newbie I see asking a question asks "how can I do t= his > on FreeBSD, and where is the HOWTO- to help me?" Most often these people > are redirected to offsite repositories of information, rather than the > documentation included with FreeBSD. IMHO, this contributes to the > degradation of the existing documentation of FreeBSD, as more effort will= go > into updating third-party sources. Which sources. I am *very* interested in bringing more documentation in to the tree -- for example, I've been trying to get in touch with Dan who runs www.mostgraveconcern.com/freebsd/ to get them in to the tree, but so far, no response. Anyone that wants to submit documentation to the FreeBSD project is encouraged to do so. It's also a pretty fast track to becoming a committer. As ever, it's "rough consensus and working code" (or documentation, in this instance). Comments such as "The FAQ sucks" don't work. PRs that say "The FAQ sucks, because it doesn't answer this question, here's a patch ready to go" get looked at much more rapidly. N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- --Bn2rw/3z4jIqBvZU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjrS6pUACgkQk6gHZCw343WRzwCfbRZ9n/PtHs1M5NMWLmoKLEuh lHQAn36vyt0KXSG5E1xEDIizr0ybIIrc =eMqr -----END PGP SIGNATURE----- --Bn2rw/3z4jIqBvZU-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 4:22:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nothing-going-on.demon.co.uk (unknown [194.128.198.234]) by hub.freebsd.org (Postfix) with ESMTP id AFAC037B423 for ; Tue, 10 Apr 2001 04:22:30 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id f3AB71m02439; Tue, 10 Apr 2001 12:07:01 +0100 (BST) (envelope-from nik) Date: Tue, 10 Apr 2001 12:07:01 +0100 From: Nik Clayton To: Dan Langille Cc: Christopher Schulte , Matthew Emmerton , Rasputin , stable@FreeBSD.ORG Subject: Re: Releases Message-ID: <20010410120701.A749@canyon.nothing-going-on.org> References: <5.0.2.1.0.20010409111054.00b18008@pop.schulte.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="sm4nu43k4a2Rpi4c" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from dan@langille.org on Tue, Apr 10, 2001 at 05:29:43AM +1200 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 10, 2001 at 05:29:43AM +1200, Dan Langille wrote: > On Mon, 9 Apr 2001, Christopher Schulte wrote: > > At 03:45 AM 4/10/2001 +1200, Dan Langille wrote: > > >Give meaningful and widely used names to things which people are famil= iar > > >with. > > > > -CURRENT fits all those requirements. >=20 > In this case, the familiarity is reduced to those familiar with the > project. Witness the frequency with which the confusion > arises. It's question five in the FAQ. =20 http://www.freebsd.org/FAQ/preface.html#CURRENT The first para says "only of interest to developers working on the system and die-hard hobbyists". The second para says If you are not familiar with the operating system or are not capable of identifying the difference between a real problem and a temporary=20 problem, you should not use FreeBSD-CURRENT. This branch sometimes evolves quite quickly and can be un-buildable for a number of days at a time. People that use FreeBSD-CURRENT are expected to be able to analyz= e=20 any problems and only report them if they are deemed to be mistakes=20 rather than ``glitches''. Questions such as ``make world produces some= =20 error about groups'' on the -CURRENT mailing list are sometimes treated= =20 with contempt. I don't see any way in which someone could start running -current without seeing that warning, or the equivalent warnings in the Handbook. Short of making -current refuse to build without a magic cookie in /etc/make.conf, and a webpage that contains that cookie along with this dire warning, I don't see how we can make it more obvious to people that they shouldn't be running -current if they don't know what they're doing. N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- --sm4nu43k4a2Rpi4c Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjrS6VQACgkQk6gHZCw343WJsQCfQDdcdJiPSFStiCkokrtRV5Zq JdoAn3ltsJ2jmL/E0bx30Ny1BHHTpU7X =aM4c -----END PGP SIGNATURE----- --sm4nu43k4a2Rpi4c-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 4:25: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nothing-going-on.demon.co.uk (unknown [194.128.198.234]) by hub.freebsd.org (Postfix) with ESMTP id 6008937B423 for ; Tue, 10 Apr 2001 04:24:49 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id f3ABK0M02524; Tue, 10 Apr 2001 12:20:00 +0100 (BST) (envelope-from nik) Date: Tue, 10 Apr 2001 12:20:00 +0100 From: Nik Clayton To: Mike Meyer Cc: Przemyslaw Brojewski , Kal Torak , Christopher Schulte , Matthew Emmerton , Jordan Hubbard , stable@freebsd.org Subject: Re: Releases Message-ID: <20010410122000.C749@canyon.nothing-going-on.org> References: <20010409105223C.jkh@osd.bsdi.com> <014a01c0c12e$e5e76f20$1200a8c0@gsicomp.on.ca> <5.0.2.1.0.20010409101533.00ace930@pop.schulte.org> <5.0.2.1.0.20010409111054.00b18008@pop.schulte.org> <200104091911.MAA32457@gndrsh.dnsmgr.net> <3AD20ECC.5A895124@quake.com.au> <20010409193544.A25126@acc.umu.se> <200104091816.UAA03404@flip.tenbit.pl> <15058.15825.422218.278218@guru.mired.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="5G06lTa6Jq83wMTw" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15058.15825.422218.278218@guru.mired.org>; from mwm@mired.org on Mon, Apr 09, 2001 at 05:55:13PM -0500 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --5G06lTa6Jq83wMTw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 09, 2001 at 05:55:13PM -0500, Mike Meyer wrote: > Jordan Hubbard types: > > > Just because the problem is difficult to solve does not mean it can n= ot be > > > or should not be solved. > > Fine, how about you solve it and the rest of us will get back to all > > the other stuff we have on our plates. :) >=20 > I know, you're kidding.=20 He's almost certainly not. FreeBSD is a huge time sink, and people work on whatever interests them. If this topic interests you then you're the best person to work on it, and submit changes. > But if some group of people who have to deal > with the questions propose a complete new naming scheme designed to > deal with all the problems we see the current ones causing (though the > only serious one is -BETA/-RC), is there any chance of it being > adopted? =20 There's certainly a chance. > How about just a new name for either -BETA (the major source > of the problem), or simply calling -STABLE -ALPHA, thus making -BETA & > -RC seem desirable? Because -STABLE is not alpha code, by any definition of "Alpha" that I'm familiar with. -STABLE is designed to be exactly that, "Stable code that is probably suitable to run your production systems on, with as few surprises as possible". N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- --5G06lTa6Jq83wMTw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjrS7F8ACgkQk6gHZCw343VxbQCfWM3X51/GAu1DNk8tIP1gFFcl YA4An3xANyDgNR5ZOtoYcVHTpU0lFA3K =PQaN -----END PGP SIGNATURE----- --5G06lTa6Jq83wMTw-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 4:28:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cx344940-a.meta1.la.home.com (cx344940-a.meta1.la.home.com [24.6.21.74]) by hub.freebsd.org (Postfix) with ESMTP id 56C0737B423 for ; Tue, 10 Apr 2001 04:28:32 -0700 (PDT) (envelope-from conrads@cx344940-a.meta1.la.home.com) Received: (from conrads@localhost) by cx344940-a.meta1.la.home.com (8.11.3/8.11.3) id f3ABXvA96566; Tue, 10 Apr 2001 06:33:57 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.4.7 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <4.3.2.20010409221338.028a4a10@207.227.119.2> Date: Tue, 10 Apr 2001 06:33:57 -0500 (CDT) Organization: @Home Network From: Conrad Sabatier To: "Jeffrey J. Mountin" Subject: Re: Can I stop BUILDWORLD from starting from scratch? Cc: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-Apr-2001 Jeffrey J. Mountin wrote: > At 07:45 PM 4/9/01 -0500, Conrad Sabatier wrote: > >>On 09-Apr-2001 Miha Nedok wrote: >> >> I really wish it'd be possible to just make selective portions >> >> of the source tree, is that possible? >> > >> > You might look at /etc/defaults/make.conf >> > >> > What you're looking for starts with this: >> > >> ># To avoid building various parts of the base system: >> >#NO_CVS= true # do not build CVS >> >>What does this do exactly? > > Doesn't the first line preceding it explain things? Doh! I must have been braindead at the time. I was reading this, with some skepticism, as your suggestion for a solution for how to restart a buildworld without rebuilding everything. I realize now what you're referring to. :-) -- Conrad Sabatier conrads@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 4:31:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 2481737B422 for ; Tue, 10 Apr 2001 04:31:18 -0700 (PDT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 24458 invoked by uid 0); 10 Apr 2001 11:31:16 -0000 Received: from pd4b9eee8.dip.t-dialin.net (HELO lofizwei) (212.185.238.232) by mail.gmx.net (mp004-rz3) with SMTP; 10 Apr 2001 11:31:16 -0000 Message-ID: <02db01c0c1b1$c1a0ffe0$0508a8c0@lofi.dyndns.org> From: "Michael Nottebrock" To: Subject: ATA_ENABLE_ATAPI_DMA gone? Date: Tue, 10 Apr 2001 13:31:16 +0200 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.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am afraid this is a rather dumb question but where did option ATA_ENABLE_ATAPI_DMA go? I am in the process of upgrading a 4.2-Release box to the latest stable version and 'make buildkernel' complained about that option not being recognised - I have read /usr/src/UPDATING but couldn't find any information about this - is there some kind of CHANGES documentation for the kernel that I overlooked? Greetings, Michael Nottebrock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 4:33:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from bumper.jellybaby.net (bumper.jellybaby.net [194.159.247.1]) by hub.freebsd.org (Postfix) with ESMTP id BF56037B422 for ; Tue, 10 Apr 2001 04:33:13 -0700 (PDT) (envelope-from simond@bumper.jellybaby.net) Received: (from simond@localhost) by bumper.jellybaby.net (8.9.2/8.9.2) id MAA75365; Tue, 10 Apr 2001 12:33:18 +0100 (BST) (envelope-from simond) Date: Tue, 10 Apr 2001 12:33:17 +0100 From: simond@irrelevant.org To: Michael Nottebrock Cc: freebsd-stable@freebsd.org Subject: Re: ATA_ENABLE_ATAPI_DMA gone? Message-ID: <20010410123317.A73359@irrelevant.org> References: <02db01c0c1b1$c1a0ffe0$0508a8c0@lofi.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <02db01c0c1b1$c1a0ffe0$0508a8c0@lofi.dyndns.org>; from michaelnottebrock@gmx.net on Tue, Apr 10, 2001 at 01:31:16PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 10, 2001 at 01:31:16PM +0200, Michael Nottebrock wrote: > I am afraid this is a rather dumb question but where did option > ATA_ENABLE_ATAPI_DMA go? I am in the process of upgrading a > 4.2-Release box to the latest stable version and 'make buildkernel' > complained about that option not being recognised - I have read > /usr/src/UPDATING but couldn't find any information about this - is > there some kind of CHANGES documentation for the kernel that I > overlooked? It seems that they've been moved, the new ata(4) explains how to set them (ie from the loader) -- Simon Dick simond@irrelevant.org "Why do I get this urge to go bowling everytime I see Tux?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 4:50:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from alpha.kharkov.ukrpack.net (ns.ic.kharkov.ua [212.1.112.1]) by hub.freebsd.org (Postfix) with SMTP id 6BBCC37B422 for ; Tue, 10 Apr 2001 04:50:18 -0700 (PDT) (envelope-from alexovch@ic.kharkov.ua) Received: (qmail 27142 invoked by uid 518); 10 Apr 2001 11:48:51 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 10 Apr 2001 11:48:51 -0000 Date: Tue, 10 Apr 2001 14:48:51 +0300 (EEST) From: Aleksey Ovcharenko X-Sender: alexovch@alpha.kharkov.ukrpack.net To: freebsd-stable@freebsd.org Subject: Where can I get FreeBSD-STABLE iso images? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 5: 2:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dilbert.fcg.co.uk (dilbert.firstcallgroup.co.uk [194.203.69.166]) by hub.freebsd.org (Postfix) with ESMTP id BB89537B422 for ; Tue, 10 Apr 2001 05:02:16 -0700 (PDT) (envelope-from pfrench@firstcallgroup.co.uk) Received: from pfrench by dilbert.fcg.co.uk with local (Exim 3.22 #1) id 14mwqc-0009r3-00 for stable@freebsd.org; Tue, 10 Apr 2001 13:02:14 +0100 To: stable@freebsd.org Subject: 4.2 RC on Compaq Proliant 1600R Message-Id: From: Pete French Date: Tue, 10 Apr 2001 13:02:14 +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anybody out there had any success running 4.2-RC2 on the above mentioned system ? Particularly using either vinum or SMP support. I am finding that a GENRIC kernel with the two SMP options enabled refuses to boot, and that on a standard GENERIC kernel anything I try to do with vinum results in an immediate kernel panic. I realise that this is not the most useful posting in the world - I do not currently have physical access to the machine and thus cannot give any output messages yet (though I hope to go visit the box sometime next week). Its more of a request to see if anyone else has had problems. The SMP particularly concerns me - is there anything else that neeeds to be done other than enabling the kernel options that I missed in the documentation ? DOes anyone else have 4.3-RC2 running on an SMP machine ? cheers, -pete. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 5: 6:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp3.jaring.my (smtp3.jaring.my [192.228.128.46]) by hub.freebsd.org (Postfix) with ESMTP id 7D18537B424 for ; Tue, 10 Apr 2001 05:06:18 -0700 (PDT) (envelope-from mglory@po.jaring.my) Received: from svr.mgsb.domain ([202.187.194.33]) by smtp3.jaring.my (8.10.1/8.10.1) with SMTP id f3AC63410891; Tue, 10 Apr 2001 20:06:04 +0800 (MYT) Content-Type: text/plain; charset="iso-8859-1" From: K Karthik Reply-To: kar@mglorysb.com Organization: Multimedia Glory Sdn Bhd To: sos@freebsd.dk Subject: Re: bin/26151: burncd exists before fixating - 4.3 RC #0 Date: Tue, 10 Apr 2001 20:08:37 +0000 X-Mailer: KMail [version 1.2] Cc: freebsd-stable@freebsd.org X-Chameleon-Return-To: kar@mglorysb.com X-PRIORITY: 2 (High) MIME-Version: 1.0 Message-Id: <01041020083701.04855@svr.mgsb.domain> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is regarding the PR bin/26151. I have cvsup-ed just a few hours ago, but I still face the problem. It is better we have this rectified in 4.3-RELEASE. Thanks Karthik ---------- Forwarded Message ---------- Subject: Re: bin/26151: burncd exists before fixating - 4.3 RC #0 Date: Tue, 3 Apr 2001 20:59:02 +0000 From: K Karthik To: freebsd-gnats-submit@FreeBSD.org, kar@mglorysb.com Sorry, I missed one thing in my previous mail (below). I get a message "fixate returning early 0". Hope this is a debug message and will taken out later. Thanks Karthik ---------- Forwarded Message ---------- Subject: Re: bin/26151: burncd exists before fixating - 4.3 RC #0 Date: Tue, 3 Apr 2001 20:53:26 +0000 From: K Karthik To: freebsd-gnats-submit@FreeBSD.org, kar@mglorysb.com The patch works well. Now I don't get READ_CAPACITY and PREVENT_ALLOW messages, but burncd waits for too long even after the fixating process is completed. This I found out as the CD-RECORDER light goes off completely (not blinking) but the burncd still waits. Using CTRL+C while waiting does not terminate the burncd. Here is the duration of the process: Total wait after the message "fixating ..." displayed: 5 minutes (approx) Time taken for actual fixation: 2 minutes (approx.) Extra wait: rest. BTW, can you suppress the message "READ_TOC", if that does not take too much time. Thanks Karthik ---------- Forwarded Message ---------- Subject: Re: bin/26151: burncd exists before fixating - 4.3 RC #0 Date: Tue, 3 Apr 2001 18:05:23 +0000 From: K Karthik To: freebsd-gnats-submit@FreeBSD.org, kar@mglorysb.com Messages: 1. acd1: READ_TOC - ILLEGAL REQUEST asc=24 ascq=00 error=04 (old) 2. acd1: READ_CAPACITY - ILLEGAL REQUEST asc=24 ascq=00 error=04 (new) 3. acd1: PREVENT_ALLOW - ILLEGAL REQUEST asc=24 ascq=00 error=04 (old) Occurence: a. message 1 appeared after burncd exits when I use this command: burncd -f /dev/acd1c blank b. message 2 and 3 appeared after burncd exits when I use this command: burncd -f /dev/acd1c data cd.iso fixate After the data is written to disk, "fixating CD , please wait.." message appears, then burncd exits. After it exits (I get # prompt), then the message 2 and 3 appears. Thanks Karthik ---------- Forwarded Message ---------- Subject: Re: bin/26151: burncd exists before fixating - 4.3 RC #0 Date: Tue, 3 Apr 2001 11:42:40 +0000 From: K Karthik To: freebsd-gnats-submit@FreeBSD.org, kar@mglorysb.com I have applied the patch but the problem still persists. burncd exits before fixating is complete. I get a new message in bold. The following messages appear in bold: 1. acd1: READ_TOC - ILLEGAL REQUEST asc=24 ascq=00 error=04 (old) 2. acd1: READ_CAPACITY - ILLEGAL REQUEST asc=24 ascq=00 error=04 (new) 3. acd1: PREVENT_ALLOW - ILLEGAL REQUEST asc=24 ascq=00 error=04 (old) I am using Sony CD-RW (CRX100E). Thanks Karthik --- atapi-cd.c 2001/02/25 21:35:20 1.48.2.10 +++ atapi-cd.c 2001/04/02 19:36:45 @@ -1364,11 +1364,15 @@ static int acd_close_disk(struct acd_softc *cdp, int multisession) { - int8_t ccb[16] = { ATAPI_CLOSE_TRACK, 0x01, 0x02, 0, 0, 0, 0, 0, - 0, 0, 0, 0, 0, 0, 0, 0 }; + int8_t ccb1[16] = { ATAPI_CLOSE_TRACK, 0x01, 0x02, 0, 0, 0, 0, 0, + 0, 0, 0, 0, 0, 0, 0, 0 }; + int8_t ccb2[16] = { ATAPI_READ_CAPACITY, 0, 0, 0, 0, 0, 0, 0, + 0, 0, 0, 0, 0, 0, 0, 0 }; + struct write_param param; int timeout = 5*60*2; int error; - struct write_param param; + char tmp[8]; + if ((error = acd_mode_sense(cdp, ATAPI_CDROM_WRITE_PARAMETERS_PAGE, (caddr_t)¶m, sizeof(param)))) @@ -1382,12 +1386,15 @@ if ((error = acd_mode_select(cdp, (caddr_t)¶m, sizeof(param)))) return error; - error = atapi_queue_cmd(cdp->atp, ccb, NULL, 0, 0, 30, NULL, NULL); + error = atapi_queue_cmd(cdp->atp, ccb1, NULL, 0, 0, 30, NULL, NULL); if (error) return error; while (timeout-- > 0) { - if ((error = atapi_test_ready(cdp->atp)) != EBUSY) - return error; + if ((error = atapi_test_ready(cdp->atp)) != EBUSY) { + if (atapi_queue_cmd(cdp->atp, ccb2, tmp, sizeof(tmp), + ATPR_F_READ, 30, NULL, NULL) != EBUSY) + return error; + } tsleep(&error, PRIBIO, "acdcld", hz/2); } return EIO; ------------------------------------------------------- ------------------------------------------------------- ------------------------------------------------------- ------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 5:12:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mobile.hub.org (mobile.acadiau.ca [131.162.137.70]) by hub.freebsd.org (Postfix) with ESMTP id 916E937B423; Tue, 10 Apr 2001 05:12:34 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by mobile.hub.org (8.11.1/8.11.1) with ESMTP id f3AC2WH82779; Tue, 10 Apr 2001 09:02:32 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: mobile.hub.org: scrappy owned process doing -bs Date: Tue, 10 Apr 2001 09:02:32 -0300 (ADT) From: The Hermit Hacker To: Cc: Subject: Netfinity 7100 & 4.3- Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Morning ... I've been getting this for awhile, and until this morning, haven't had a moment to actually write down what is/was on the screen ... its a 4.3 system, on a Netfinity 7100 ... dmesg output included at the bottom. The system is running a concat vinum drive for a mirror drive ... Thoughts, based on the following? Periodically, more often then not when there is heavy disk activity, the thing will panic, as follows: Fatal Trap 12: page fault while in kernel mode fault virtual address = 0x8084 fault code = supervisor read, page at present instruction pointer = 0x8:0xc012341e stack pointer = 0x10:0xc0257b94 frame pointer = 0x10:0x0c257b98 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 interrupt mask = trap number = 12 I can break into DDB, and do a trace, which shows: Debugger scgetc sckbdevent atkbd_intr atkbd_isa_intr Xresume1 --- interrupt, ip = 0xc020e6d21, esp = 0xc0257878, ebp = 0xc02578bc --- vec1 bwrite vop_stdbwrite vop_defaultop ufs_vnoperate bwrite cluster_wbuild vfs_bio_awrite ffs_fscync ffs_sync boot panic trap_fatal trap_pfault trap calltrap --- trap 0xc, eip = 0xc012341e, esp = 0xc4257b94, ebp = 0xc257b98 --- xpt_setup_ccb camperiphdone camisr scsi_cambio splz_scsi Xresume9 --- interrupt, eip = 0xc0219016, eip = 0xc0257c94, ebp = 0 --- default_halt ==================== Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.3-RC #3: Mon Apr 2 11:54:44 ADT 2001 root@demeter.acadiau.ca:/usr/obj/usr/src/sys/demeter Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 699179279 Hz CPU: Pentium III/Pentium III Xeon/Celeron (699.18-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6a0 Stepping = 0 Features=0x383fbff real memory = 1073717248 (1048552K bytes) avail memory = 1042833408 (1018392K bytes) Preloaded elf kernel "kernel" at 0xc02d9000. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib1: on motherboard pci1: on pcib1 pcib0: on motherboard pci0: on pcib0 ahc0: port 0x2000-0x20ff mem 0xfebff000-0xfebfffff irq 9 at device 1.0 on pci0 aic7896/97: Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0x2100-0x21ff mem 0xfebfe000-0xfebfefff irq 9 at device 1.1 on pci0 aic7896/97: Wide Channel B, SCSI Id=7, 32/255 SCBs pci0: at 6.0 isab0: at device 15.0 on pci0 isa0: on isab0 pci0: at 15.2 irq 7 pcib2: on motherboard pci2: on pcib2 rl0: port 0x2200-0x22ff mem 0xf7fffc00-0xf7fffcff irq 11 at device 5.0 on pci2 rl0: Ethernet address: 00:e0:29:67:4e:d0 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl1: port 0x2300-0x23ff mem 0xf7fff800-0xf7fff8ff irq 15 at device 6.0 on pci2 rl1: Ethernet address: 00:e0:29:67:4a:eb miibus1: on rl1 rlphy1: on miibus1 rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcib3: on motherboard pci3: on pcib3 fdc0: at port 0x3f0-0x3f5,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 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model GlidePoint, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> Waiting 15 seconds for SCSI devices to settle pass7 at ahc1 bus 0 target 15 lun 0 pass7: Fixed Processor SCSI-2 device pass7: 3.300MB/s transfers da0 at ahc1 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 8678MB (17774160 512 byte sectors: 255H 63S/T 1106C) da4 at ahc1 bus 0 target 5 lun 0 da4: Fixed Direct Access SCSI-3 device da4: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da4: 17357MB (35548320 512 byte sectors: 255H 63S/T 2212C) da3 at ahc1 bus 0 target 4 lun 0 da3: Fixed Direct Access SCSI-3 device da3: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da3: 17357MB (35548320 512 byte sectors: 255H 63S/T 2212C) da2 at ahc1 bus 0 target 3 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da2: 17357MB (35548320 512 byte sectors: 255H 63S/T 2212C) da1 at ahc1 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 17357MB (35548320 512 byte sectors: 255H 63S/T 2212C) da6 at ahc1 bus 0 target 10 lun 0 da6: Fixed Direct Access SCSI-3 device da6: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da6: 34715MB (71096640 512 byte sectors: 255H 63S/T 4425C) da5 at ahc1 bus 0 target 9 lun 0 da5: Fixed Direct Access SCSI-3 device da5: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da5: 34715MB (71096640 512 byte sectors: 255H 63S/T 4425C) Mounting root from ufs:/dev/da0s1a WARNING: / was not properly dismounted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 5:33: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from head.lvl.ru (head.lvl.ru [194.67.189.100]) by hub.freebsd.org (Postfix) with ESMTP id 29B4E37B423; Tue, 10 Apr 2001 05:32:59 -0700 (PDT) (envelope-from jadream@chat.ru) Received: from chat.ru (p50.gw.lvl.ru [194.67.189.50]) by head.lvl.ru (8.11.2/8.11.2) with ESMTP id f3ACWsL20201; Tue, 10 Apr 2001 16:32:55 +0400 (MSD) Message-ID: <3AD2FFC5.71806BB9@chat.ru> Date: Tue, 10 Apr 2001 16:42:45 +0400 From: alex X-Mailer: Mozilla 4.72 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Subject: Urgent: SysV msg queue strange behaviour Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please help me! I'm in a real trouble with that. I have FreeBSD 4.2 on a common i386 pc with SysV IPC configured and recompiled kernel. Everything goes well untill I create more than 128 processes sending messages (24bytes in size) to the same queue at a time with flags = 0 (Blocking mode) and 1 process getting them all with flags = 0 (Blocking mode too). After queue size rises up to 70 -180 all processes hangs - both the ones that sends (what's naturally) and the one that gets (that's strange to my mind). Hence I have dead lock. With all this I have in my kernel config file options like that MSGMNI=64 MSGMAX=256 MSGMNB=2048*24 MSGTQL=2048 I used semaphores to block sending messages processes until receiver cleares whole queue and it all works but total performance go down dramatically :0( Any idea how to handle that? Alexander Komratov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 5:52:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 71C6E37B423 for ; Tue, 10 Apr 2001 05:52:07 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 30446 invoked by uid 100); 10 Apr 2001 12:52:06 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15059.502.493117.364068@guru.mired.org> Date: Tue, 10 Apr 2001 07:52:06 -0500 To: Nik Clayton Cc: stable@freebsd.org Subject: Re: Releases In-Reply-To: <20010410120701.A749@canyon.nothing-going-on.org> References: <5.0.2.1.0.20010409111054.00b18008@pop.schulte.org> <20010410120701.A749@canyon.nothing-going-on.org> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nik Clayton types: > I don't see any way in which someone could start running -current > without seeing that warning, or the equivalent warnings in the Handbook. More than once people have shown up on -questions running -current because they just grabbed the "standard" supfile. Which gets them -current :-(. Which was why I suggested that it standard-supfile get the branch being run. > Short of making -current refuse to build without a magic cookie in > /etc/make.conf, and a webpage that contains that cookie along with this > dire warning, I don't see how we can make it more obvious to people that > they shouldn't be running -current if they don't know what they're doing. It would help if they had to read those docs before having a supfile that could be used to grab -current without editing the supfile. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 6:20:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from snoop.burghcom.com (burgcom.cust.stargate.net [209.166.166.21]) by hub.freebsd.org (Postfix) with SMTP id 3B5CC37B423 for ; Tue, 10 Apr 2001 06:20:09 -0700 (PDT) (envelope-from jl@burghcom.com) Received: (qmail 88240 invoked from network); 10 Apr 2001 13:20:07 -0000 Received: from merlin.hq.sgi.net (HELO merlin) (jl@209.166.162.10) by snoop.burghcom.com with SMTP; 10 Apr 2001 13:20:07 -0000 From: Jeff Love To: stable@freebsd.org Subject: Re: 4.2 RC on Compaq Proliant 1600R Date: Tue, 10 Apr 2001 09:18:52 -0400 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: In-Reply-To: MIME-Version: 1.0 Message-Id: <01041009201200.23844@merlin> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > DOes anyone else have 4.3-RC2 running on an SMP machine ? > cheers, > -pete. Pete, Yes, I've got 4.3 -RC running on a dual Pentium machine. No problems compiling or booting/running. -- Jeff Love jl@burghcom.com ----------------- Burgh-Com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 6:36:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cisco.com (sword.cisco.com [161.44.208.100]) by hub.freebsd.org (Postfix) with ESMTP id 3BD5137B422 for ; Tue, 10 Apr 2001 06:36:42 -0700 (PDT) (envelope-from sjt@cisco.com) Received: from sjt-u10.cisco.com (sjt-u10.cisco.com [10.85.30.63]) by cisco.com (8.8.5-Cisco.1/8.8.8) with ESMTP id JAA01322 for ; Tue, 10 Apr 2001 09:36:41 -0400 (EDT) From: Steve Tremblett Received: (sjt@localhost) by sjt-u10.cisco.com (8.8.5-Cisco.1/CISCO.WS.1.2) id JAA16571 for freebsd-stable@freebsd.org; Tue, 10 Apr 2001 09:36:40 -0400 (EDT) Message-Id: <200104101336.JAA16571@sjt-u10.cisco.com> Subject: Re: Releases To: freebsd-stable@freebsd.org Date: Tue, 10 Apr 2001 09:36:40 -0400 (EDT) In-Reply-To: <20010409102526S.jkh@osd.bsdi.com> from "Jordan Hubbard" at Apr 09, 2001 10:25:26 AM 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG +--- Jordan Hubbard wrote: | | > By this designation, we could call a brake a clutch and get away with it | > because it's all documented. The problem is not with the documentation. | > It's with the name. | | That's a nice pat answer, but the problem is that for every value of | "name" we propose, somebody comes forward and says "But that confuses | me." We can't call it BETA, we can't call it STABLE, we can't call it | RC, we can't call it PRERELEASE, because each and every one of those | have had push-back from people who said it would conflict with | previous definitions they hold dear. Given that, chances are | excellent that any other halfway logical names we come up with will | suffer from the same problem. | | The real problem here is that we're trying to cater to the lowest | common denominator, which is stupid people who leap before they look | and then blame someone else for the injuries they sustain. It is for | those very same people that legal liability forced McDonalds to write | "Warning: This is called hot coffee. That means it is Hot. You | should never, ever dump it into your crotch or on any other part of | your body which is intended to remain unscalded. Did we mention that | it's very hot?" | Insulting those who misunderstand isn't a solution either. People say "read the handbook". If it is written in stone there, someone please re-edit this section: -------- 19.2.2.2. Who needs FreeBSD-STABLE? If you are a commercial user or someone who puts maximum stability of their FreeBSD system before all other concerns, you should consider tracking stable. This is especially true if you have installed the most recent release (4.2-RELEASE at the time of this writing) since the stable branch is effectively a bug-fix stream relative to the previous release. -------- please add "once every few months it will say BETA but don't worry, it isn't really a beta, because it is more stable than STABLE!" To be honest, I don't see the release process discussed in the handbook at all! There is a section explaining STABLE vs. CURRENT, but that's about it. I reiterate: the term BETA implies the testing phase of new code. The FBSD folks insist that it is just STABLE, and have to answer endless questions about it. If it is just STABLE, and more solid than STABLE, why have a BETA at all? Sorry for opening this can of worms - my apologies. my $0.02 (Canadian) -- Steve Tremblett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 6:43: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by hub.freebsd.org (Postfix) with ESMTP id 8566337B422 for ; Tue, 10 Apr 2001 06:42:57 -0700 (PDT) (envelope-from bmah@cisco.com) Received: from bmah-freebsd-0.cisco.com (bmah-freebsd-0.cisco.com [171.70.84.42]) by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id GAA27615; Tue, 10 Apr 2001 06:42:55 -0700 (PDT) Received: (from bmah@localhost) by bmah-freebsd-0.cisco.com (8.11.3/8.11.1) id f3ADgsn15019; Tue, 10 Apr 2001 06:42:54 -0700 (PDT) (envelope-from bmah) Message-Id: <200104101342.f3ADgsn15019@bmah-freebsd-0.cisco.com> X-Mailer: exmh version 2.3.1 01/19/2001 with nmh-1.0.4 To: simond@irrelevant.org Cc: Michael Nottebrock , freebsd-stable@FreeBSD.ORG Subject: Re: ATA_ENABLE_ATAPI_DMA gone? In-Reply-To: <20010410123317.A73359@irrelevant.org> References: <02db01c0c1b1$c1a0ffe0$0508a8c0@lofi.dyndns.org> <20010410123317.A73359@irrelevant.org> Comments: In-reply-to simond@irrelevant.org message dated "Tue, 10 Apr 2001 12:33:17 +0100." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-1242060858P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Tue, 10 Apr 2001 06:42:54 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_-1242060858P Content-Type: text/plain; charset=us-ascii If memory serves me right, simond@irrelevant.org wrote: > On Tue, Apr 10, 2001 at 01:31:16PM +0200, Michael Nottebrock wrote: > > I am afraid this is a rather dumb question but where did option > > ATA_ENABLE_ATAPI_DMA go? I am in the process of upgrading a > > 4.2-Release box to the latest stable version and 'make buildkernel' > > complained about that option not being recognised - I have read > > /usr/src/UPDATING but couldn't find any information about this - is > > there some kind of CHANGES documentation for the kernel that I > > overlooked? > > It seems that they've been moved, the new ata(4) explains how to set them > (ie from the loader) And it's also mentioned in RELNOTES.TXT: # To provide more flexible configuration, the various options for the # ata(4) driver are now boot loader tunables, rather than kernel # configure-time options. Bruce. --==_Exmh_-1242060858P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: Exmh version 2.2 06/23/2000 iD8DBQE60w3e2MoxcVugUsMRAkU5AKDGs1AJpIPIa2LfUVchov5ep1Ey5QCg84AY LC1wURB7onnKmmTACbT+dxk= =7Nie -----END PGP SIGNATURE----- --==_Exmh_-1242060858P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 6:53:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from krusty.e-technik.uni-dortmund.de (krusty.E-Technik.Uni-Dortmund.DE [129.217.163.1]) by hub.freebsd.org (Postfix) with ESMTP id 5704937B42C for ; Tue, 10 Apr 2001 06:53:21 -0700 (PDT) (envelope-from ma@dt.e-technik.uni-dortmund.de) Received: from burns.e-technik.uni-dortmund.de (burns.dt.e-technik.uni-dortmund.de [129.217.163.19]) by krusty.e-technik.uni-dortmund.de (Postfix) with ESMTP id 66A59A384A; Tue, 10 Apr 2001 15:53:20 +0200 (CEST) Received: by burns.e-technik.uni-dortmund.de (Postfix, from userid 537) id 4DD1E13388; Tue, 10 Apr 2001 15:53:18 +0200 (CEST) Date: Tue, 10 Apr 2001 15:53:18 +0200 From: Matthias Andree To: Kris Kennaway Cc: Matthias Andree , freebsd-stable@FreeBSD.org Subject: Re: BDECFLAGS break current 4.x-stable build Message-ID: <20010410155318.A2074@burns.dt.e-technik.uni-dortmund.de> References: <20010409093630.B72961@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010409093630.B72961@xor.obsecurity.org>; from kris@obsecurity.org on Mon, Apr 09, 2001 at 09:36:30 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 09 Apr 2001, Kris Kennaway wrote: > Submit patches to fix them, then. :-} Seriously, would these be relevant for 4.x-stable still or would these better be sent in for 5.x-current? > BDECFLAGS is there for developers to work on code correctness and > possible bugs resulting from language misuse (or general gcc pickiness > which doesn't actually involve code bugs). It doesn't change the code > generated by gcc. Yup, but now people looking through the archives have something to check if their build fails. That's been one reason for submitting this. :-) -- Matthias Andree To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 6:54: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from femail10.sdc1.sfba.home.com (femail10.sdc1.sfba.home.com [24.0.95.106]) by hub.freebsd.org (Postfix) with ESMTP id DD21737B422 for ; Tue, 10 Apr 2001 06:54:03 -0700 (PDT) (envelope-from graywane@home.com) Received: from cg392862-a.adubn1.nj.home.com ([65.2.79.221]) by femail10.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010410135402.VPRR7256.femail10.sdc1.sfba.home.com@cg392862-a.adubn1.nj.home.com> for ; Tue, 10 Apr 2001 06:54:02 -0700 Received: (from graywane@localhost) by cg392862-a.adubn1.nj.home.com (8.11.3/8.11.3) id f3ADs0F23952 for freebsd-stable@FreeBSD.ORG; Tue, 10 Apr 2001 09:54:00 -0400 (EDT) (envelope-from graywane) Date: Tue, 10 Apr 2001 09:54:00 -0400 From: Graywane To: freebsd-stable@FreeBSD.ORG Subject: Re: Releases Message-ID: <20010410095400.A23927@home.com> References: <20010409102526S.jkh@osd.bsdi.com> <200104101336.JAA16571@sjt-u10.cisco.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="VS++wcV0S1rZb1Fb" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104101336.JAA16571@sjt-u10.cisco.com>; from sjt@cisco.com on Tue, Apr 10, 2001 at 09:36:40AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --VS++wcV0S1rZb1Fb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 10, 2001 at 09:36:40AM -0400, Steve Tremblett wrote: > +--- Jordan Hubbard wrote: > | The real problem here is that we're trying to cater to the lowest > | common denominator, which is stupid people who leap before they look > | and then blame someone else for the injuries they sustain. >=20 > Insulting those who misunderstand isn't a solution either. Of course, given how long Jordan has been involved with the project, it isn't exactly wise to ignore his words of wisdom either now is it? Its just possible that he has participated in a discussion of this type one or twice before. --=20 Note: See http://www.members.home.net/graywane/ for PGP information. --VS++wcV0S1rZb1Fb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjrTEHgACgkQeHdFaBWUGN3u6wCfTyJhJwpCVL3Q31fvOFbRz3Zr YREAn3fsadEkk2j8Tjo2fZiIaHIib+pb =blpv -----END PGP SIGNATURE----- --VS++wcV0S1rZb1Fb-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 7: 1:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id B368637B424 for ; Tue, 10 Apr 2001 07:01:15 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 32318 invoked by uid 100); 10 Apr 2001 14:01:15 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15059.4651.149885.809111@guru.mired.org> Date: Tue, 10 Apr 2001 09:01:15 -0500 To: "Jeffrey J. Mountin" Cc: "Yann Sommer" , stable@FreeBSD.ORG Subject: Re: Why not stick with [STABLE] [Was: RE: Releases] In-Reply-To: <4.3.2.20010410012424.02b2f580@207.227.119.2> References: <4.3.2.20010410012424.02b2f580@207.227.119.2> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeffrey J. Mountin types: > The concept of how the naming is done is not an issue and cannot be solved > by using a different or modified scheme. Rather the documentation should > cover this. Quite right. The problem we're trying to solve is dealing with questions from people who don't know that > Just a matter of explaining what each period means in the > handbook and/or/both the FAQ... As you note, it's already there: > Then again if anyone perpetuating this thread had bothered to pay attention > to the list (RYFM) and check out Nik's last message would know about: > > http://www.freebsd.org/FAQ/book.html#RELEASE-CANDIDATE > > and might find: > > http://www.freebsd.org/FAQ/book.html#STABLE > > Think that covers it... http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 7:10:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nothing-going-on.demon.co.uk (unknown [194.128.198.234]) by hub.freebsd.org (Postfix) with ESMTP id 8AD6137B423 for ; Tue, 10 Apr 2001 07:10:14 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id f3ABNET11488; Tue, 10 Apr 2001 12:23:14 +0100 (BST) (envelope-from nik) Date: Tue, 10 Apr 2001 12:23:14 +0100 From: Nik Clayton To: Robert Cc: FreeBSD Subject: Re: Can I stop BUILDWORLD from starting from scratch? Message-ID: <20010410122313.D749@canyon.nothing-going-on.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="ZJcv+A0YCCLh2VIg" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from robert@chalmers.com.au on Tue, Apr 10, 2001 at 08:47:52AM +1000 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ZJcv+A0YCCLh2VIg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 10, 2001 at 08:47:52AM +1000, Robert wrote: > Is it possible to stop 'make buildworld' from starting from scratch each > time? http://www.freebsd.org/handbook/makeworld.html section 19.4.13.4 N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- --ZJcv+A0YCCLh2VIg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjrS7SAACgkQk6gHZCw343X1GwCaA9As+FDaVPS3SBqiKxvdVDz7 eJwAn1FNWJtQH6Mn7kqPf/FSm+DblUr6 =wA+W -----END PGP SIGNATURE----- --ZJcv+A0YCCLh2VIg-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 7:11:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freenix.no (atreides.freenix.no [217.68.117.6]) by hub.freebsd.org (Postfix) with ESMTP id 493F437B423 for ; Tue, 10 Apr 2001 07:11:24 -0700 (PDT) (envelope-from morten@freenix.no) Received: (from morten@localhost) by freenix.no (8.11.1/8.11.1) id f3AEBC321453 for freebsd-stable@freebsd.org; Tue, 10 Apr 2001 16:11:12 +0200 (CEST) (envelope-from morten) Date: Tue, 10 Apr 2001 16:11:12 +0200 From: "Morten A . Middelthon" To: freebsd-stable@freebsd.org Subject: arp: unknown hardware address format (0x4500) Message-ID: <20010410161112.A21375@freenix.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 4.2-STABLE X-Warning: So cunning you could brush your teeth with it. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Recently I've been getting tons of these in my syslog: arp: unknown hardware address format (0x4500) Iirc I haven't had these before, but now they keep appearing 10-20 times a day. The box is 4.2-STABLE built from sources from Feb 15. There are other FreeBSD boxes on the same network, but they're not showing any messages like this. It's running dhcpd, apache, named, NIS, nfsd, smbd and using an Intel NIC with the fxp driver, if that's interesting. -- Morten A. Middelthon Freenix Norge http://www.freenix.no/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 7:26: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from yertle.kciLink.com (yertle.kciLink.com [208.184.13.195]) by hub.freebsd.org (Postfix) with ESMTP id F06E437B424 for ; Tue, 10 Apr 2001 07:26:03 -0700 (PDT) (envelope-from khera@kciLink.com) Received: by yertle.kciLink.com (Postfix, from userid 100) id BEEE62E45E; Tue, 10 Apr 2001 10:26:01 -0400 (EDT) To: stable@freebsd.org Newsgroups: ml.freebsd.stable Subject: Re: ntpd root exploit - advisory? References: From: Vivek Khera Date: 10 Apr 2001 10:25:59 -0400 Message-ID: Organization: Khera Communications, Inc., Rockville, MD Lines: 14 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Posted-To: ml.freebsd.stable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following message is a courtesy copy of an article that has been posted to ml.freebsd.stable as well. >>>>> "l" == lamont writes: l> its fixed in the latest 4.2-stable, i'd not waste any time upgrading. Which is easy to do just cd /usr/src/usr.sbin/ntp and type "make" and then make install. shutdown and restart ntpd. no need to upgrade the whole system until it is convenient. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-240-453-8497 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 7:27:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail5.nc.rr.com (fe5.southeast.rr.com [24.93.67.52]) by hub.freebsd.org (Postfix) with ESMTP id 4651337B43E for ; Tue, 10 Apr 2001 07:27:27 -0700 (PDT) (envelope-from bts@babbleon.org) Received: from babbleon.org ([66.26.250.181]) by mail5.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Tue, 10 Apr 2001 08:27:02 -0400 Message-ID: <3AD2FBFA.ADDF188C@babbleon.org> Date: Tue, 10 Apr 2001 08:26:34 -0400 From: The Babbler Organization: None to speak of X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Jeffrey J. Mountin" Cc: Yann Sommer , stable@freebsd.org Subject: Re: Why not stick with [STABLE] [Was: RE: Releases] References: <4.3.2.20010410012424.02b2f580@207.227.119.2> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jeffrey J. Mountin" wrote: : : > Fact is what friggin difference does make what the build calls > itself. Those that track the RELENG_4 branch should know that it doesn't > matter what it calls itself when doing a uname, it is the same branch at > different points or periods of time. > > The concept of how the naming is done is not an issue and cannot be solved > by using a different or modified scheme. Rather the documentation should > cover this. Just a matter of explaining what each period means in the > handbook and/or/both the FAQ... On principle, yes. I am new to FreeBSD (well, "new again"; I used it in 1995ish but back then tracking stable was out of the question owing to my poor net connections; I upgraded when Walnut Creeek released the new CD), and I read the handbook and subscribed to the list and it never caused me a moments consternation when the name changed. BUT the endless questions in the list about the name have really gotten even on *my* nerves; it must be driving the long-time regulars bonkers. The idea of changing the label was to try to do something to forestall the number of dumb questions from those who apparently can't be bothered to read and pay attention. Of course, they don't "deserve" help, but the loyal readers of the lists *do* deserve reliefe from the repeated questions, and if changing the label can give it to us, it seems sensible to me to change the labels. As you said "what friggin difference does [it] make what the build calls itself?" -- so if the veterens don't care what the label is, why not make it into something that will forestall pointless questions from the clueless newbies? The recent update to UPDATING will hopefully forestall some of them, but a change to the label seems to me like a pretty useful proposal, if everybody can agree on what to chnage it *to*. After alll, it's the label that's causing the confusion & spurious traffic, so that's the place to tackle the problem if we want to address the problem at its source. -- "Brian, the man from babble-on" bts@babbleon.org Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 8:22: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 0211837B422 for ; Tue, 10 Apr 2001 08:22:04 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f3AFLf813510; Tue, 10 Apr 2001 08:21:42 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: matusita@jp.FreeBSD.org Cc: stable@FreeBSD.ORG Subject: Re: 4.3-RC2: broken crypto/CHECKSUM.MD5 In-Reply-To: <20010410141230H.matusita@jp.FreeBSD.org> References: <20010410141230H.matusita@jp.FreeBSD.org> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010410082141I.jkh@osd.bsdi.com> Date: Tue, 10 Apr 2001 08:21:41 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you submit a patch, I'll do my best to test and integrate it. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 8:24:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 004CF37B422 for ; Tue, 10 Apr 2001 08:24:09 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f3AFNv813528; Tue, 10 Apr 2001 08:23:58 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: christopher@schulte.org Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 4.3 release schedule still on track for April 15? (for Jordan) In-Reply-To: <5.1.0.12.0.20010410001159.00aac170@pop.schulte.org> References: <5.1.0.12.0.20010410001159.00aac170@pop.schulte.org> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010410082357Y.jkh@osd.bsdi.com> Date: Tue, 10 Apr 2001 08:23:57 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 9 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is the 4.3 release date still on track for April 15, per your revised > schedule as posted March 22 to this list? I'm not sure yet - we're juggling some last-minute stuff which might make a push-back to the 20th necessary, but I won't know for another day or two. If there's any need for a delay, I'll post words to that effect. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 8:28: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.infolibria.com (mail.infolibria.com [12.30.17.31]) by hub.freebsd.org (Postfix) with ESMTP id E2AD937B423 for ; Tue, 10 Apr 2001 08:28:00 -0700 (PDT) (envelope-from John@LoVerso.Southborough.MA.US) Received: from LoVerso.Southborough.MA.US (gw.infolibria.com [12.30.17.254]) by mail.infolibria.com (Postfix) with ESMTP id E890115CC04 for ; Tue, 10 Apr 2001 10:25:30 -0500 (EST) Message-ID: <3AD325FD.34DCA095@LoVerso.Southborough.MA.US> Date: Tue, 10 Apr 2001 11:25:49 -0400 From: John LoVerso Organization: InfoLibria, Inc. X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: stable@FreeBSD.ORG Subject: Re: Disklabel 101? References: <20010405111707.A35325@dogma.freebsd-uk.eu.org><3ACE972D.A13CF44C@babbleon.org> <15054.57979.84674.462609@guru.mired.org> <000001c0bfd9$3b96a230$1201a8c0@sanmik.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Are there any issues with placing swap first on the hard drive? Unless you > insist on filling the drive, it seems to me that this swap arrangement would > result in less stack travel. Except that the beginning of the hard disk is the fastest area of the drive. Normally, you would want to reserve that for your commonly read data and push the swap area to the end of the disk where I/O will be about half as fast. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 8:30:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.infolibria.com (mail.infolibria.com [12.30.17.31]) by hub.freebsd.org (Postfix) with ESMTP id DA39037B422 for ; Tue, 10 Apr 2001 08:30:43 -0700 (PDT) (envelope-from John@LoVerso.Southborough.MA.US) Received: from LoVerso.Southborough.MA.US (gw.infolibria.com [12.30.17.254]) by mail.infolibria.com (Postfix) with ESMTP id 0F1A515CC04; Tue, 10 Apr 2001 10:28:14 -0500 (EST) Message-ID: <3AD326A0.5CB0B17C@LoVerso.Southborough.MA.US> Date: Tue, 10 Apr 2001 11:28:32 -0400 From: John LoVerso Organization: InfoLibria, Inc. X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Gregory Bond Cc: stable@FreeBSD.ORG Subject: Re: Disklabel 101? References: <200104090154.LAA02651@lightning.itga.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This was true upto and including V7, but not true in 4.2. I'm not sure > where in the seqence from V7 -> Sys32 -> 4.1 -> 4.2 that pack-resident > labels appeared. 4.2 did not have pack-resident labels - I distinctly remember editing the partition table in the DEC RA81 driver in 4.3BSD, as the partition layout that Berkeley used (and distributed) didn't match the one we were already using. IIRK, Chris Torek (then at UMD) contributed the pack-resident label code around the time of 4.3 Tahoe. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 8:32:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id D106337B424 for ; Tue, 10 Apr 2001 08:32:45 -0700 (PDT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 6038 invoked by uid 0); 10 Apr 2001 15:32:44 -0000 Received: from pd950a1c0.dip.t-dialin.net (HELO lofizwei) (217.80.161.192) by mail.gmx.net (mp008-rz3) with SMTP; 10 Apr 2001 15:32:44 -0000 Message-ID: <003801c0c1d3$7d7edc20$0508a8c0@lofi.dyndns.org> From: "Michael Nottebrock" To: "Steve Tremblett" , References: <200104101336.JAA16571@sjt-u10.cisco.com> Subject: Re: Releases Date: Tue, 10 Apr 2001 17:32:30 +0200 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.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Steve Tremblett" To: Sent: Tuesday, April 10, 2001 3:36 PM Subject: Re: Releases > [...] > People say "read the handbook". If it is written in stone there, > someone please re-edit this section: > > -------- > 19.2.2.2. Who needs FreeBSD-STABLE? > > [...] > > To be honest, I don't see the release process discussed in the handbook > at all! There is a section explaining STABLE vs. CURRENT, but that's > about it. > > [...] I agree that it should be in the Handbook. But it _is_ actually in that other important FreeBSD document, the FAQ: "7.37. I tried to update by system to the latest -STABLE, but got -RC or -BETA! What's going on?" Btw, one other thing that appears in the FAQ but really should be mentioned in the handbook is "7.41. Why can't I unset the schg file flag?", preferably in Section 7.3 or 7.6. Greetings, Michael Nottebrock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 8:34:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 5E04637B423 for ; Tue, 10 Apr 2001 08:34:31 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id IAA35432; Tue, 10 Apr 2001 08:34:26 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200104101534.IAA35432@gndrsh.dnsmgr.net> Subject: Re: Releases In-Reply-To: <200104101336.JAA16571@sjt-u10.cisco.com> from Steve Tremblett at "Apr 10, 2001 09:36:40 am" To: sjt@cisco.com (Steve Tremblett) Date: Tue, 10 Apr 2001 08:34:25 -0700 (PDT) Cc: freebsd-stable@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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... > People say "read the handbook". If it is written in stone there, > someone please re-edit this section: > > -------- > 19.2.2.2. Who needs FreeBSD-STABLE? > > If you are a commercial user or someone who puts maximum stability of > their FreeBSD system before all other concerns, you should consider > tracking stable. This is especially true if you have installed the most > recent release (4.2-RELEASE at the time of this writing) since the > stable branch is effectively a bug-fix stream relative to the previous > release. > -------- > > please add "once every few months it will say BETA but don't worry, it > isn't really a beta, because it is more stable than STABLE!" Ahhh... well... in my 8 years of being around FreeBSD when we enter the -BETA phase on the -STABLE branch the tree goes to hell in a hand basket for about 2 weeks. So please don't make the handbook state the above. Perhaps more like: Every few months in preperation for the next -RELEASE from the -STABLE branch the system will call itself -BETA, this is to reflect the fact that lots of changes are occuring in the tree, mainly merges of well tested code from the developers branch (-CURRENT). The tag -BETA is used to denoate that these events are occuring and you may enconter minor problems. This is not like a -BETA product from most software companies, as the code being brought in has general had a rather extensive test period, but the project has no way to test all code in all situations and breakage is bound to happen. > To be honest, I don't see the release process discussed in the handbook > at all! There is a section explaining STABLE vs. CURRENT, but that's > about it. The release process is black magic passed down through the generations and just as the code is continuously evolving, so is the release process. Documenting black magic is really hard unless you get a technical writter doing the black magic, or one to spend a month sitting beside the practitioner taking really detailed notes. The tag sequences could be better documented, or err, the newvers.sh changes that occuring during the phases could be better documented. > > I reiterate: the term BETA implies the testing phase of new code. The > FBSD folks insist that it is just STABLE, and have to answer endless > questions about it. If it is just STABLE, and more solid than STABLE, > why have a BETA at all? Because those who claim it is ``just STABLE, and more solid than STABLE'' are making false claims. It is not really all that stable during this time period. BETA may be a bit on the strong side, but as already pointed out, the tree does de-stabalize during this time period. > Sorry for opening this can of worms - my apologies. Though many have called this a bikeshed, and at times I have agreed that a lot of what is being said is a bikeshed (names are names, people who attatch permanent fixed meaning to names are going to have problems understanding lots of things, the -STABLE, -RELEASE, -BETA, -CURRENT tags being one of them.) But I have seen 2 things come up in this last round of this 8 year old thread that could actually use some fixing: a) Rename the standard-supfile, that one in itself has caused a lot of grief and is a trivial change with minimal impact to the masses as it really should only be used by -developers, who know how to deal with all this. b) Correct everyone who says ``FreeBSD -BETA is really just as stable as the normal -STABLE. It is not! During this phase of a branch things get borked all over the place, from not being able to build the tree due to partial MFC's or botched commits, to kernels that crash and burn due to subtle bugs and corner cases that didn't get tested in -CURRENT due to the smaller user base and narrower scope of hardware being tested on. One way to correct this would be to actually branch for -BETA, then once the group of us -STABLE users who actually have a clue about how to build and test this stuff have had a fair chance (2 weeks?) to pound it a bit merge it back into -STABLE in one big sweep and call it -RC. This is a short lived branch, but may have a rather high impact on cvsup resources due to the tagging operations required to do this type of operation cleanly. The masses would never see -BETA, but it would be done by people who actually know how to be beta testers :-) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 8:42:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id D1B5437B423 for ; Tue, 10 Apr 2001 08:42:23 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f3AFgG813668; Tue, 10 Apr 2001 08:42:16 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: graywane@home.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Releases In-Reply-To: <20010410095400.A23927@home.com> References: <20010409102526S.jkh@osd.bsdi.com> <200104101336.JAA16571@sjt-u10.cisco.com> <20010410095400.A23927@home.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010410084216D.jkh@osd.bsdi.com> Date: Tue, 10 Apr 2001 08:42:16 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 6 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Its just possible that he has participated in a discussion of this type one > or twice before. I think the current count is 5, possibly 6. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 8:51:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id D189337B422 for ; Tue, 10 Apr 2001 08:51:36 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f3AFpOY46685; Tue, 10 Apr 2001 18:51:24 +0300 (EEST) (envelope-from ru) Date: Tue, 10 Apr 2001 18:51:24 +0300 From: Ruslan Ermilov To: "Morten A . Middelthon" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: arp: unknown hardware address format (0x4500) Message-ID: <20010410185124.B42234@sunbay.com> Mail-Followup-To: "Morten A . Middelthon" , freebsd-stable@FreeBSD.ORG References: <20010410161112.A21375@freenix.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010410161112.A21375@freenix.no>; from morten@freenix.no on Tue, Apr 10, 2001 at 04:11:12PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 10, 2001 at 04:11:12PM +0200, Morten A . Middelthon wrote: > > Recently I've been getting tons of these in my syslog: > arp: unknown hardware address format (0x4500) > > Iirc I haven't had these before, but now they keep appearing 10-20 times a > day. > > The box is 4.2-STABLE built from sources from Feb 15. There are other FreeBSD > boxes on the same network, but they're not showing any messages like this. > > It's running dhcpd, apache, named, NIS, nfsd, smbd and using an Intel NIC with > the fxp driver, if that's interesting. > This message indicates that some host of your LAN broadcasted ARP message with the wrong value of hardware address format type field. I have a Linux box on my LAN (Mandrake?) that for unknown reason _sometimes_ broadcasts broken ARP requests. These do not hurt anything, just annoying. There is no mechanism to turn these messages off. I ran tcpdump(1) for a while to see the hardware address of the host that broadcasted these wrong ARP messages. You might also want to take a look at the header file for the format of the ARP message, and to take an idea on what fields to look in the tcpdump(1) output. I think, something like this might work for you: # tcpdump -exn "arp[0]=0x45 and arp[1]=0" Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 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-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 10:22:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id 894FF37B422 for ; Tue, 10 Apr 2001 10:22:34 -0700 (PDT) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.3+3.4W/8.11.3) with ESMTP/inet id f3AHMC855476; Wed, 11 Apr 2001 02:22:13 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Cc: stable@FreeBSD.ORG In-Reply-To: <20010410082141I.jkh@osd.bsdi.com> References: <20010410141230H.matusita@jp.FreeBSD.org> <20010410082141I.jkh@osd.bsdi.com> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Urania) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 9 From: Makoto MATSUSHITA To: jkh@osd.bsdi.com Subject: Re: 4.3-RC2: broken crypto/CHECKSUM.MD5 Date: Wed, 11 Apr 2001 02:21:57 +0900 Message-Id: <20010411022157P.matusita@jp.FreeBSD.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jkh> If you submit a patch, I'll do my best to test and integrate it. Already submitted to FreeBSD PR database. Please fetch a patch from: -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 10:55:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 4D10E37B423 for ; Tue, 10 Apr 2001 10:55:47 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f3AHtiL00452; Tue, 10 Apr 2001 10:55:44 -0700 (PDT) Date: Tue, 10 Apr 2001 10:55:44 -0700 From: Alfred Perlstein To: alex Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Urgent: SysV msg queue strange behaviour Message-ID: <20010410105544.S15938@fw.wintelcom.net> References: <3AD2FFC5.71806BB9@chat.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AD2FFC5.71806BB9@chat.ru>; from jadream@chat.ru on Tue, Apr 10, 2001 at 04:42:45PM +0400 X-all-your-base: are belong to us. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * alex [010410 05:33] wrote: > Please help me! > I'm in a real trouble with that. > > > I have FreeBSD 4.2 on a common i386 pc with SysV IPC configured and > recompiled kernel. 1) don't cc both -stable and -questions! 2) Please provide the source code to a program that will reproduce the problem you're having and I'll be glad to check it out. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 12:16:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 8843137B424 for ; Tue, 10 Apr 2001 12:16:50 -0700 (PDT) (envelope-from Gerhard.Sittig@gmx.net) Received: (qmail 31880 invoked by uid 0); 10 Apr 2001 19:16:45 -0000 Received: from p3ee20a9e.dip.t-dialin.net (HELO speedy.gsinet) (62.226.10.158) by mail.gmx.net (mp026-rz3) with SMTP; 10 Apr 2001 19:16:45 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id SAA22614 for freebsd-stable@freebsd.org; Tue, 10 Apr 2001 18:51:52 +0200 Date: Tue, 10 Apr 2001 18:51:52 +0200 From: Gerhard Sittig To: freebsd-stable@freebsd.org Subject: Re: Building code for non configured features (was: Releases) Message-ID: <20010410185152.X20830@speedy.gsinet> Mail-Followup-To: freebsd-stable@freebsd.org References: <200104091859.UAA06664@flip.tenbit.pl> <01040916401600.22539@merlin> <20010409164348.H14079@pir.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20010409164348.H14079@pir.net>; from pir@pir.net on Mon, Apr 09, 2001 at 04:43:48PM -0400 Organization: System Defenestrators Inc. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 09, 2001 at 16:43 -0400, Peter Radcliffe wrote: > > Jeff Love probably said: > > > > Why was the kernel make compiling modules for devices I did > > not set in my config? > > Modules are, by definition, not included in the kernel. They > are loaded and added to the monolithic kernel. > > [ ... ] By default all modules are built, in case you want to > use them. That's where I love the Linux notion of configuring a feature as either enabled, disabled, or modularized. Did I miss some obvious reason for not completely disabling functionality? Is the current choice of making features and drivers either builtin or a module to not confuse users by the possibility to disable too many of them? Is it since compiling is cheap these days and opinions about "I don't need these" might change over time? Looking at the low end machines I have around here I sometimes would like to completely disable some features and exclude them from compilation and installation. And I'm absolutely positive about some of them to never become necessary for this setup. :) virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 12:33:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.unixathome.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id DE01A37B422 for ; Tue, 10 Apr 2001 12:33:42 -0700 (PDT) (envelope-from dan@langille.org) Received: from wocker (root@ns1.unixathome.org [192.168.0.20]) by ns1.unixathome.org (8.11.3/8.11.3) with ESMTP id f3AJXYe81872; Wed, 11 Apr 2001 07:33:35 +1200 (NZST) (envelope-from dan@langille.org) Message-Id: <200104101933.f3AJXYe81872@ns1.unixathome.org> From: "Dan Langille" Organization: novice in training To: "Rodney W. Grimes" Date: Tue, 10 Apr 2001 15:33:23 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Releases Reply-To: dan@langille.org Cc: freebsd-stable@FreeBSD.ORG In-reply-to: <200104101534.IAA35432@gndrsh.dnsmgr.net> References: <200104101336.JAA16571@sjt-u10.cisco.com> from Steve Tremblett at "Apr 10, 2001 09:36:40 am" X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10 Apr 2001, at 8:34, Rodney W. Grimes wrote some very fine stuff: > Ahhh... well... in my 8 years of being around FreeBSD when we enter > the -BETA phase on the -STABLE branch the tree goes to hell in a > hand basket for about 2 weeks. So please don't make the handbook > state the above. Perhaps more like: > > Every few months in preperation for the next -RELEASE from the > -STABLE branch the system will call itself -BETA, this is to reflect > the fact that lots of changes are occuring in the tree, mainly merges > of well tested code from the developers branch (-CURRENT). The tag > -BETA is used to denoate that these events are occuring and you may > enconter minor problems. This is not like a -BETA product from most > software companies, as the code being brought in has general had a > rather extensive test period, but the project has no way to test all > code in all situations and breakage is bound to happen. This would go a long way to both reducing -questions traffic and increasing understanding. > Though many have called this a bikeshed, and at times I have agreed > that a lot of what is being said is a bikeshed (names are names, people who > attatch permanent fixed meaning to names are going to have problems > understanding lots of things, the -STABLE, -RELEASE, -BETA, -CURRENT tags > being one of them.) But I have seen 2 things come up in this last round of > this 8 year old thread that could actually use some fixing: > > a) Rename the standard-supfile, that one in itself has caused a lot > of grief and is a trivial change with minimal impact to the masses as > it really should only be used by -developers, who know how to deal with > all this. Renaming is a fine idea. What about one more step. Remove it altogether. The people that need it already know how to create it. How does that sound? > b) Correct everyone who says ``FreeBSD -BETA is really just as stable > as the normal -STABLE. It is not! During this phase of a branch > things get borked all over the place, from not being able to build the > tree due to partial MFC's or botched commits, to kernels that crash and > burn due to subtle bugs and corner cases that didn't get tested in > -CURRENT due to the smaller user base and narrower scope of hardware > being tested on. > > One way to correct this would be to actually branch for -BETA, then > once the group of us -STABLE users who actually have a clue about how > to build and test this stuff have had a fair chance (2 weeks?) to pound > it a bit merge it back into -STABLE in one big sweep and call it -RC. > This is a short lived branch, but may have a rather high impact on > cvsup resources due to the tagging operations required to do this type > of operation cleanly. > > The masses would never see -BETA, but it would be done by people > who actually know how to be beta testers :-) Well, the branch makes a good deal of sense. It stops beta from getting out to the people who track -stable and allows changes to be even more isolated. This will also eliminate the inevitable posts to - stable and -questions reagarding "how come I got BETA code?". Do others think this is a good idea? -- Dan Langille pgpkey - finger dan@unixathome.org | http://unixathome.org/finger.php got any work? I'm looking for some. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 12:44:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from light.imasy.or.jp (light.imasy.or.jp [202.227.24.4]) by hub.freebsd.org (Postfix) with ESMTP id 93DDD37B422 for ; Tue, 10 Apr 2001 12:44:14 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: (from uucp@localhost) by light.imasy.or.jp (8.11.3+3.4W/8.11.3/light) with UUCP id f3AJhum08299; Wed, 11 Apr 2001 04:43:56 +0900 (JST) (envelope-from ume@mahoroba.org) Received: from peace.mahoroba.org (IDENT:y14pzqFgVaCJxg2He46zKu4uCZHPYWy+QastNbPjUrdnjqRzrTAWaq95swA7XNFU@peace.mahoroba.org [2001:200:301:0:200:f8ff:fe05:3eae]) (authenticated as ume with CRAM-MD5) by mail.mahoroba.org (8.11.3/8.11.3/chaos) with ESMTP/inet6 id f3AJh9c12650; Wed, 11 Apr 2001 04:43:09 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Wed, 11 Apr 2001 04:43:05 +0900 (JST) Message-Id: <20010411.044305.111162972.ume@mahoroba.org> To: jim@nasby.net Cc: freebsd-stable@freebsd.org Subject: Re: Errors in /usr/src/sys/sys/socket.h in current RELENG_4 From: Hajimu UMEMOTO In-Reply-To: <3AD0C953.B31494A9@nasby.net> References: <3AD0C953.B31494A9@nasby.net> X-Mailer: xcite1.38> Mew version 1.95b119 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Sun, 08 Apr 2001 15:25:55 -0500 >>>>> "Jim C. Nasby" said: jim> Apologies if this is old news. This is from a cvsup of RELENG_4 that's jim> less than an hour old. jim> cc -O2 -pipe -Wall -DLIBC_SCCS -I/usr/src/lib/libutil jim> -I/usr/src/lib/libutil/../../sys -DINET6 -c jim> /usr/src/lib/libutil/logwtmp.c -o l jim> ogwtmp.o jim> In file included from /usr/src/lib/libutil/logwtmp.c:44: jim> /usr/src/lib/libutil/../../sys/sys/socket.h:312: syntax error before jim> `socklen_t' Did you sure do make buildworld / installworld? Recently, socklen_t was introduced due to confirm to the specification of getnameinfo(3). -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 13:34:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fluffy.adriel.net (fluffy.adriel.net [216.141.4.150]) by hub.freebsd.org (Postfix) with ESMTP id A08C637B422 for ; Tue, 10 Apr 2001 13:34:32 -0700 (PDT) (envelope-from adriel@fluffy.adriel.net) Received: (from adriel@localhost) by fluffy.adriel.net (8.11.2/8.11.2) id f3AKYQo91056 for freebsd-stable@freebsd.org; Tue, 10 Apr 2001 15:34:26 -0500 (CDT) (envelope-from adriel) Date: Tue, 10 Apr 2001 15:34:26 -0500 From: adriel To: freebsd-stable@freebsd.org Subject: Re: ATA_ENABLE_ATAPI_DMA gone? Message-ID: <20010410153425.I5028@adriel.net> References: <02db01c0c1b1$c1a0ffe0$0508a8c0@lofi.dyndns.org> <20010410123317.A73359@irrelevant.org> <200104101342.f3ADgsn15019@bmah-freebsd-0.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104101342.f3ADgsn15019@bmah-freebsd-0.cisco.com>; from bmah@FreeBSD.ORG on Tue, Apr 10, 2001 at 06:42:54AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hw.ata.atapi_dma set to 1 for DMA access 0 for PIO (default is PIO). root@misty:~# sysctl -w hw.ata.atapi_dma=1 sysctl: oid 'hw.ata.atapi_dma' is read only what the hell? I need this, my drive takes forever to mount without it it scrolls tons of errors before finally timing out and using pio. Quoting Bruce A. Mah (bmah@FreeBSD.ORG): > If memory serves me right, simond@irrelevant.org wrote: > > On Tue, Apr 10, 2001 at 01:31:16PM +0200, Michael Nottebrock wrote: > > > I am afraid this is a rather dumb question but where did option > > > ATA_ENABLE_ATAPI_DMA go? I am in the process of upgrading a > > > 4.2-Release box to the latest stable version and 'make buildkernel' > > > complained about that option not being recognised - I have read > > > /usr/src/UPDATING but couldn't find any information about this - is > > > there some kind of CHANGES documentation for the kernel that I > > > overlooked? > > > > It seems that they've been moved, the new ata(4) explains how to set them > > (ie from the loader) > > And it's also mentioned in RELNOTES.TXT: > > # To provide more flexible configuration, the various options for the > # ata(4) driver are now boot loader tunables, rather than kernel > # configure-time options. > > Bruce. > > -- ---------------------------------------------------- Adriel Ickler Network Administrator - adriel@jlms.com Self Trading Securities - Voice: 512-263-2769 www.selftrading.com - Fax: 512-263-2141 ---------------------------------------------------- Remember: Silly is a state of Mind, Stupid is a way of Life. -- Dave Butler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 13:49:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 923DE37B423 for ; Tue, 10 Apr 2001 13:49:36 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f3AKnZw05443; Tue, 10 Apr 2001 13:49:35 -0700 (PDT) Date: Tue, 10 Apr 2001 13:49:35 -0700 From: Alfred Perlstein To: adriel Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ATA_ENABLE_ATAPI_DMA gone? Message-ID: <20010410134934.Z15938@fw.wintelcom.net> References: <02db01c0c1b1$c1a0ffe0$0508a8c0@lofi.dyndns.org> <20010410123317.A73359@irrelevant.org> <200104101342.f3ADgsn15019@bmah-freebsd-0.cisco.com> <20010410153425.I5028@adriel.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010410153425.I5028@adriel.net>; from adriel@adriel.net on Tue, Apr 10, 2001 at 03:34:26PM -0500 X-all-your-base: are belong to us. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * adriel [010410 13:34] wrote: > hw.ata.atapi_dma > set to 1 for DMA access 0 for PIO (default is PIO). > > root@misty:~# sysctl -w hw.ata.atapi_dma=1 > sysctl: oid 'hw.ata.atapi_dma' is read only > > what the hell? I need this, my drive takes forever to mount without it > it scrolls tons of errors before finally timing out and using pio. "what the hell?" ? didn't you read that Bruce told you? > Quoting Bruce A. Mah (bmah@FreeBSD.ORG): > > > > And it's also mentioned in RELNOTES.TXT: > > > > # To provide more flexible configuration, the various options for the > > # ata(4) driver are now boot loader tunables, rather than kernel > > # configure-time options. You must set it from the loader. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 13:53:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 6B4A837B423 for ; Tue, 10 Apr 2001 13:53:13 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id NAA36777; Tue, 10 Apr 2001 13:53:08 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200104102053.NAA36777@gndrsh.dnsmgr.net> Subject: Re: Releases In-Reply-To: <200104101933.f3AJXYe81872@ns1.unixathome.org> from Dan Langille at "Apr 10, 2001 03:33:23 pm" To: dan@langille.org Date: Tue, 10 Apr 2001 13:53:08 -0700 (PDT) Cc: freebsd-stable@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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... > > > Though many have called this a bikeshed, and at times I have agreed > > that a lot of what is being said is a bikeshed (names are names, people who > > attatch permanent fixed meaning to names are going to have problems > > understanding lots of things, the -STABLE, -RELEASE, -BETA, -CURRENT tags > > being one of them.) But I have seen 2 things come up in this last round of > > this 8 year old thread that could actually use some fixing: > > > > a) Rename the standard-supfile, that one in itself has caused a lot > > of grief and is a trivial change with minimal impact to the masses as > > it really should only be used by -developers, who know how to deal with > > all this. > > Renaming is a fine idea. What about one more step. Remove it > altogether. The people that need it already know how to create it. How > does that sound? I could go along with removing it from the -STABLE branch, after all those are the people that keep blowing there toes off because we have left a loaded gun laying in front of them and they don't seem to be able to read the instructions we have placed on it... (actually having gone and looked at it, this file could surely use a big fat Warning in the top of it (and probably one in the README too!)!). ... -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 13:59:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 7E7EE37B422 for ; Tue, 10 Apr 2001 13:59:25 -0700 (PDT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 4186 invoked by uid 0); 10 Apr 2001 20:59:23 -0000 Received: from pd950a1c0.dip.t-dialin.net (HELO lofizwei) (217.80.161.192) by mail.gmx.net (mp005-rz3) with SMTP; 10 Apr 2001 20:59:23 -0000 Message-ID: <00a401c0c201$1f3fbac0$0508a8c0@lofi.dyndns.org> From: "Michael Nottebrock" To: "adriel" , References: <02db01c0c1b1$c1a0ffe0$0508a8c0@lofi.dyndns.org> <20010410123317.A73359@irrelevant.org> <200104101342.f3ADgsn15019@bmah-freebsd-0.cisco.com> <20010410153425.I5028@adriel.net> Subject: Re: ATA_ENABLE_ATAPI_DMA gone? Date: Tue, 10 Apr 2001 22:59:22 +0200 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.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "adriel" To: Sent: Tuesday, April 10, 2001 10:34 PM Subject: Re: ATA_ENABLE_ATAPI_DMA gone? > hw.ata.atapi_dma > set to 1 for DMA access 0 for PIO (default is PIO). > > root@misty:~# sysctl -w hw.ata.atapi_dma=1 > sysctl: oid 'hw.ata.atapi_dma' is read only > > what the hell? I need this, my drive takes forever to mount without it > it scrolls tons of errors before finally timing out and using pio. > > [...] I think hw.ata.atapi_dma can only be set in /boot/loader.conf. From the commandline, you can set the mode of each ide/atapi device via hw.atamodes. See 'man 4 ata' for the details. Greetings, Michael Nottebrock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 14:29:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from buddha.automagic.org (buddha-nexxia.automagic.org [207.61.141.34]) by hub.freebsd.org (Postfix) with SMTP id 69C6837B422 for ; Tue, 10 Apr 2001 14:29:27 -0700 (PDT) (envelope-from jabley@buddha.automagic.org) Received: (qmail 15152 invoked by uid 100); 10 Apr 2001 21:29:21 -0000 Date: Tue, 10 Apr 2001 17:29:21 -0400 From: Joe Abley To: Steve Tremblett Cc: freebsd-stable@freebsd.org Subject: Re: Releases Message-ID: <20010410172920.N7423@buddha.home.automagic.org> References: <20010409102526S.jkh@osd.bsdi.com> <200104101336.JAA16571@sjt-u10.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104101336.JAA16571@sjt-u10.cisco.com>; from sjt@cisco.com on Tue, Apr 10, 2001 at 09:36:40AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 10, 2001 at 09:36:40AM -0400, Steve Tremblett wrote: > People say "read the handbook". If it is written in stone there, > someone please re-edit this section: > > -------- > 19.2.2.2. Who needs FreeBSD-STABLE? > > If you are a commercial user or someone who puts maximum stability of > their FreeBSD system before all other concerns, you should consider > tracking stable. This is especially true if you have installed the most > recent release (4.2-RELEASE at the time of this writing) since the > stable branch is effectively a bug-fix stream relative to the previous > release. > -------- > > please add "once every few months it will say BETA but don't worry, it > isn't really a beta, because it is more stable than STABLE!" > > To be honest, I don't see the release process discussed in the handbook > at all! There is a section explaining STABLE vs. CURRENT, but that's > about it. Seems to me that if the lowest-common-denominator had some way to stay stable that didn't involve using cvsup or a compiler, this would be a non-issue. Numbered binary patches, anyone? Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 14:34:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mohegan.mohawk.net (mohegan.mohawk.net [63.66.68.21]) by hub.freebsd.org (Postfix) with ESMTP id 1E11737B422 for ; Tue, 10 Apr 2001 14:34:47 -0700 (PDT) (envelope-from fbsd@mohawk.net) Received: from localhost (fbsd@localhost) by mohegan.mohawk.net (8.9.3/8.9.3) with ESMTP id RAA85144 for ; Tue, 10 Apr 2001 17:36:20 -0400 (EDT) (envelope-from fbsd@mohawk.net) Date: Tue, 10 Apr 2001 17:36:20 -0400 (EDT) From: FreeBSD Admin To: freebsd-stable@FreeBSD.ORG Subject: how to track stable Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For years now I have been running FreeBSD machines (since 2.0.5) but I never bothered tracking stable. I would watch for security advisories and decide if I needed to upgrade some executable. Eventually, I would backup the user content and reload from scratch to get a new release (generally by x.2). That worked for me okay, but now, with many many machines to deal with, I thought I should probably learn to track stable. Please bear with me. I have tried to understand this process, but still it is not clear to me. I have read http://www.freebsd.org/handbook/current-stable.html http://www.freebsd.org/handbook/synching.html http://www.freebsd.org/handbook/makeworld.html http://www.freebsd.org/handbook/anoncvs.html http://www.freebsd.org/handbook/cvsup.html and other docs, but I find it confusing for some reason. Maybe I'm slightly out to lunch or something, but it seems more complicated than I imagine it really is. Can someone point me to a clear step-by-step explanation of how to do this? I have cvsup'd the stable sources and the ports, but now what? Do I have to rebuild everything? There's a lot of stuff we never use. Does everything have to be done? Perhaps this is right under my nose. If so, I apologize and thank you for setting me right. Thanks in advance for any pointers about tracking stable. Thanks again. - Ralph To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 14:42:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id 4AF2537B423; Tue, 10 Apr 2001 14:42:28 -0700 (PDT) Date: Tue, 10 Apr 2001 14:42:28 -0700 From: David O'Brien To: Tim Zingelman Cc: freebsd-stable@FreeBSD.ORG Subject: Re: make release broken with too many ports/distfiles... Message-ID: <20010410144228.A20548@hub.freebsd.org> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from zingelman@fnal.gov on Sun, Apr 08, 2001 at 09:31:47PM -0500 X-Operating-System: FreeBSD 4.2-STABLE Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 08, 2001 at 09:31:47PM -0500, Tim Zingelman wrote: > On a system with all (or most of) the distfiles existing in > /usr/ports/distfiles, line 680 of: How did you even get all (or most of) the distfiles in the chroot'ed /usr/ports/distfiles? -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 14:47:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 2F56737B423 for ; Tue, 10 Apr 2001 14:47:15 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 42996 invoked by uid 100); 10 Apr 2001 21:47:14 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15059.32610.648363.284781@guru.mired.org> Date: Tue, 10 Apr 2001 16:47:14 -0500 To: "Rodney W. Grimes" Cc: stable@freebsd.org Subject: standard-supfile (Was: Releases) In-Reply-To: <200104102053.NAA36777@gndrsh.dnsmgr.net> References: <200104101933.f3AJXYe81872@ns1.unixathome.org> <200104102053.NAA36777@gndrsh.dnsmgr.net> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rodney W. Grimes types: > ... > > > > > Though many have called this a bikeshed, and at times I have agreed > > > that a lot of what is being said is a bikeshed (names are names, people who > > > attatch permanent fixed meaning to names are going to have problems > > > understanding lots of things, the -STABLE, -RELEASE, -BETA, -CURRENT tags > > > being one of them.) But I have seen 2 things come up in this last round of > > > this 8 year old thread that could actually use some fixing: > > > > > > a) Rename the standard-supfile, that one in itself has caused a lot > > > of grief and is a trivial change with minimal impact to the masses as > > > it really should only be used by -developers, who know how to deal with > > > all this. > > > > Renaming is a fine idea. What about one more step. Remove it > > altogether. The people that need it already know how to create it. How > > does that sound? > > I could go along with removing it from the -STABLE branch, after all > those are the people that keep blowing there toes off because we have > left a loaded gun laying in front of them and they don't seem to be > able to read the instructions we have placed on it... (actually having > gone and looked at it, this file could surely use a big fat Warning > in the top of it (and probably one in the README too!)!). My original suggestion was that standard-supfile should be the supfile for the branch it was on. In other words, remove it from every branch but -current, then rename stable-supfile for each of those branches to standard-supfile. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 14:48: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (Postfix) with ESMTP id AA2E537B424; Tue, 10 Apr 2001 14:47:54 -0700 (PDT) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (localhost.xtalwind.net [127.0.0.1]) by germanium.xtalwind.net (8.11.3/8.11.3) with ESMTP id f3ALlrY45219; Tue, 10 Apr 2001 17:47:53 -0400 (EDT) (envelope-from jack@germanium.xtalwind.net) Date: Tue, 10 Apr 2001 17:47:53 -0400 (EDT) From: jack To: "David O'Brien" Cc: Tim Zingelman , freebsd-stable@FreeBSD.ORG Subject: Re: make release broken with too many ports/distfiles... In-Reply-To: <20010410144228.A20548@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Today David O'Brien wrote: > On Sun, Apr 08, 2001 at 09:31:47PM -0500, Tim Zingelman wrote: > > On a system with all (or most of) the distfiles existing in > > /usr/ports/distfiles, line 680 of: > > How did you even get all (or most of) the distfiles in the chroot'ed > /usr/ports/distfiles? If you don't figure out what distfiles are needed for docproj-{whatever}, relocate them, and set this: DOCDISTFILES?= ${.CURDIR}/../../ports/distfiles cp -rp ${DOCDISTFILES} ${CHROOTDIR}/usr/ports/distfiles will copy _every_ file, and subdirectory, you have in /usr/ports/distfiles. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- A Microsoft Certified Systems Engineer is to computing what a McDonalds Certified Food Specialist is to fine cuisine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 14:48: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id 7134537B424; Tue, 10 Apr 2001 14:48:04 -0700 (PDT) Date: Tue, 10 Apr 2001 14:48:04 -0700 From: David O'Brien To: Dan Langille Cc: stable@FreeBSD.ORG Subject: Re: Releases Message-ID: <20010410144804.B20548@hub.freebsd.org> Reply-To: stable@freebsd.org References: <20010409111527V.jkh@osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from dan@langille.org on Tue, Apr 10, 2001 at 06:32:15AM +1200 X-Operating-System: FreeBSD 4.2-STABLE Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 10, 2001 at 06:32:15AM +1200, Dan Langille wrote: > AFAIK, the thread to date has been about whether or not [something like] > the label "-development" would cause less confusion than "-current". My And then we'd have people who CVSup'ed -development because they wanted to develop an application on FreeBSD. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 14:54:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id 9E35937B422; Tue, 10 Apr 2001 14:54:33 -0700 (PDT) Date: Tue, 10 Apr 2001 14:54:33 -0700 From: David O'Brien To: Matthew Emmerton Cc: stable@FreeBSD.ORG Subject: Re: Releases Message-ID: <20010410145433.C20548@hub.freebsd.org> Reply-To: stable@freebsd.org References: <014a01c0c12e$e5e76f20$1200a8c0@gsicomp.on.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <014a01c0c12e$e5e76f20$1200a8c0@gsicomp.on.ca>; from matt@gsicomp.on.ca on Mon, Apr 09, 2001 at 03:54:32PM -0400 X-Operating-System: FreeBSD 4.2-STABLE Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 09, 2001 at 03:54:32PM -0400, Matthew Emmerton wrote: > pre-alphas and totally trashed most systems and rightly freak out most > novice admins), while STABLE/RC/RELEASE just makes sense. However, this You obviously haven't been reading all the threads on this same topic over the past month. We need the "BETA" stage for ports. Plain and simple. Some seem to prefer -PRERELEASE. I don't care what it is called -- 4.3-I_AM_A_MORNON_BECAUSE_I_DO_NOT_RTFM would be fine too. Read the archives to see why it is needed for ports right before a release. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 14:54:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.unixathome.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id EEF3337B422 for ; Tue, 10 Apr 2001 14:54:41 -0700 (PDT) (envelope-from dan@langille.org) Received: from wocker (root@ns1.unixathome.org [192.168.0.20]) by ns1.unixathome.org (8.11.3/8.11.3) with ESMTP id f3ALsce84245; Wed, 11 Apr 2001 09:54:39 +1200 (NZST) (envelope-from dan@langille.org) Message-Id: <200104102154.f3ALsce84245@ns1.unixathome.org> From: "Dan Langille" Organization: novice in training To: "David O'Brien" Date: Tue, 10 Apr 2001 17:54:24 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Releases Reply-To: dan@langille.org Cc: stable@FreeBSD.ORG In-reply-to: <20010410144804.B20548@hub.freebsd.org> References: ; from dan@langille.org on Tue, Apr 10, 2001 at 06:32:15AM +1200 X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10 Apr 2001, at 14:48, David O'Brien wrote: > On Tue, Apr 10, 2001 at 06:32:15AM +1200, Dan Langille wrote: > > AFAIK, the thread to date has been about whether or not [something like] > > the label "-development" would cause less confusion than "-current". My > > And then we'd have people who CVSup'ed -development because they wanted to > develop an application on FreeBSD. Thanks. I like that one. Then -unstable is a better name then - development. But we've moved on from this I think. -- Dan Langille pgpkey - finger dan@unixathome.org | http://unixathome.org/finger.php got any work? I'm looking for some. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 14:56: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 8729C37B422 for ; Tue, 10 Apr 2001 14:55:53 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 43485 invoked by uid 100); 10 Apr 2001 21:55:49 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15059.33125.707948.129365@guru.mired.org> Date: Tue, 10 Apr 2001 16:55:49 -0500 To: stable@freebsd.org Subject: Re: Releases In-Reply-To: <20010410144804.B20548@hub.freebsd.org> References: <20010409111527V.jkh@osd.bsdi.com> <20010410144804.B20548@hub.freebsd.org> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien types: > On Tue, Apr 10, 2001 at 06:32:15AM +1200, Dan Langille wrote: > > AFAIK, the thread to date has been about whether or not [something like] > > the label "-development" would cause less confusion than "-current". My > And then we'd have people who CVSup'ed -development because they wanted > to develop an application on FreeBSD. Clearly, the solution is rename -CURRENT to be -BETA. That should keep the clueless from grabbing it by accident. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 14:56: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id C5D1237B43E for ; Tue, 10 Apr 2001 14:55:54 -0700 (PDT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 18566 invoked by uid 0); 10 Apr 2001 21:55:53 -0000 Received: from pd950a1c0.dip.t-dialin.net (HELO lofizwei) (217.80.161.192) by mail.gmx.net (mail04) with SMTP; 10 Apr 2001 21:55:53 -0000 Message-ID: <016b01c0c209$03b8a2a0$0508a8c0@lofi.dyndns.org> From: "Michael Nottebrock" To: "FreeBSD Admin" , References: Subject: Re: how to track stable Date: Tue, 10 Apr 2001 23:55:52 +0200 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.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "FreeBSD Admin" To: Sent: Tuesday, April 10, 2001 11:36 PM Subject: how to track stable > [...] > Can someone point me to a clear step-by-step explanation of how to do > this? I have cvsup'd the stable sources and the ports, but now what? Do I > have to rebuild everything? There's a lot of stuff we never use. Does > everything have to be done? > [...] If you have already cvsup'd everything, read /usr/src/UPDATING, which provides step-by-step instructions for upgrading 3.x to 4.x stable and 4.0-Release or later to 4.x stable. I have succeeded in upgrading my vanilla 4.2-Release to 4.3-RC by following those instructions. Greetings, Michael Nottebrock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 14:56:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id EEB1837B422; Tue, 10 Apr 2001 14:56:24 -0700 (PDT) Date: Tue, 10 Apr 2001 14:56:24 -0700 From: David O'Brien To: "Michael R. Rudel" Cc: Christopher Schulte , Dan Langille , Matthew Emmerton , Rasputin , stable@FreeBSD.ORG Subject: Re: Releases Message-ID: <20010410145624.D20548@hub.freebsd.org> Reply-To: stable@freebsd.org References: <5.0.2.1.0.20010409111054.00b18008@pop.schulte.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mrr@thud.pcs.k12.mi.us on Mon, Apr 09, 2001 at 01:38:15PM -0400 X-Operating-System: FreeBSD 4.2-STABLE Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 09, 2001 at 01:38:15PM -0400, Michael R. Rudel wrote: > x.x-BETA is ... notoriously buggy. It has bugs, that's the point of the x.y-GAMMA rather than x.y-BETA might would be a good move. Then we'd have 1/2 the world asking what "GAMMA" means. We could then hit over the head them with the cluebat and maybe it would stick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 15: 1: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id F1F5B37B424 for ; Tue, 10 Apr 2001 15:00:51 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([fec0::2e0:7dff:fe81:749d]) by scientia.demon.co.uk with esmtp (Exim 3.22 #1) id 14n6Bu-000O3l-00; Tue, 10 Apr 2001 23:00:50 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.11.3/8.11.3) id f3AM0oW16722; Tue, 10 Apr 2001 23:00:50 +0100 (BST) (envelope-from ben) Date: Tue, 10 Apr 2001 23:00:50 +0100 From: Ben Smithurst To: FreeBSD Admin Cc: freebsd-stable@FreeBSD.ORG Subject: Re: how to track stable Message-ID: <20010410230049.G8173@scientia.demon.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSD Admin wrote: > Can someone point me to a clear step-by-step explanation of how to do > this? I have cvsup'd the stable sources and the ports, but now what? 1. Set KERNCONF=FOO in /etc/make.conf, where FOO is the name of your kernel. 2. cvsup, you say you've done that bit. 3. # cd /usr/src # make buildworld buildkernel # mergemaster (may as well do that while build is running) # shutdown now (go to single user mode) # make installworld installkernel # reboot That should be all you need to do, it normally just works though things can go wrong. Probably best to wait a bit to see if anyone points out something blatantly obvious that I've missed. Anything important you need to do when updating should be listed in /usr/src/UPDATING, so read that. As for ports, most of them should just keep working but you can recompile your installed ports if you want. Things like lsof, if you have it installed, *will* need recompiling because it deals with the kernel very closely (same reason ps, top, etc, need to be recompiled for a new kernel). Good luck! -- Ben Smithurst / ben@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 15:19:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id 5F23337B424; Tue, 10 Apr 2001 15:19:07 -0700 (PDT) Date: Tue, 10 Apr 2001 15:19:07 -0700 From: David O'Brien To: Christian Chen Cc: Mike Tancsa , Robert , FreeBSD Subject: Re: Can I stop BUILDWORLD from starting from scratch? Message-ID: <20010410151907.E20548@hub.freebsd.org> Reply-To: stable@freebsd.org References: <4.2.2.20010409190439.027ccd08@192.168.0.12> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from oistrakh@earthlink.net on Mon, Apr 09, 2001 at 04:16:45PM -0700 X-Operating-System: FreeBSD 4.2-STABLE Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 09, 2001 at 04:16:45PM -0700, Christian Chen wrote: > > But why is "something" breaking ? The build process should be clean. If > > not, something is messed in your source code repository. > > Well, I know that when I installed 4.2-RELEASE off of CD, make world > in /usr/src did not work. You've got big problems then. It would be worth your time to figure out *why* it broke. As other things are liable to be broken for you. If the source from the 4.2-RELEASE CD did not build, there would be no 4.2-RELEASE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 15:23:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id 2553937B422; Tue, 10 Apr 2001 15:23:32 -0700 (PDT) Date: Tue, 10 Apr 2001 15:23:32 -0700 From: David O'Brien To: FreeBSD Admin Cc: freebsd-stable@FreeBSD.ORG Subject: Re: how to track stable Message-ID: <20010410152332.F20548@hub.freebsd.org> Reply-To: freebsd-stable@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from fbsd@mohawk.net on Tue, Apr 10, 2001 at 05:36:20PM -0400 X-Operating-System: FreeBSD 4.2-STABLE Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 10, 2001 at 05:36:20PM -0400, FreeBSD Admin wrote: > Please bear with me. I have tried to understand this process, but still it > is not clear to me. I have read > > http://www.freebsd.org/handbook/current-stable.html > http://www.freebsd.org/handbook/synching.html > http://www.freebsd.org/handbook/makeworld.html > http://www.freebsd.org/handbook/anoncvs.html > http://www.freebsd.org/handbook/cvsup.html ... > Can someone point me to a clear step-by-step explanation of how to do We do think these are clear explanations. Perhaps you should tell us _WHY_ you do not think they are, so we'd know how to phrase our responses such that they aren't verbatim from the above docs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 15:29:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id B3EC837B422 for ; Tue, 10 Apr 2001 15:29:09 -0700 (PDT) (envelope-from juha@saarinen.org) Received: from dendennis.saarinen.org ([192.168.1.2] helo=dendennis) by vimfuego.saarinen.org with smtp (Exim 3.22 #1 (Red Hack)) id 14n6dF-0002Va-00; Wed, 11 Apr 2001 10:29:05 +1200 From: "Juha Saarinen" To: "Joe Abley" Cc: Subject: RE: Releases Date: Wed, 11 Apr 2001 10:28:54 +1200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: <20010410172920.N7423@buddha.home.automagic.org> Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :: Seems to me that if the lowest-common-denominator had some way to :: stay stable that didn't involve using cvsup or a compiler, this would :: be a non-issue. :: :: Numbered binary patches, anyone? Troll! ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 15:33:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mohegan.mohawk.net (mohegan.mohawk.net [63.66.68.21]) by hub.freebsd.org (Postfix) with ESMTP id 65D6937B422 for ; Tue, 10 Apr 2001 15:33:11 -0700 (PDT) (envelope-from fbsd@mohawk.net) Received: from localhost (fbsd@localhost) by mohegan.mohawk.net (8.9.3/8.9.3) with ESMTP id SAA86642 for ; Tue, 10 Apr 2001 18:34:50 -0400 (EDT) (envelope-from fbsd@mohawk.net) Date: Tue, 10 Apr 2001 18:34:50 -0400 (EDT) From: Ralph Huntington To: freebsd-stable@FreeBSD.ORG Subject: Re: how to track stable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kind regards and grateful appreciateion to those who responded. I thyink I get it now. Thanks again. - Ralph To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 15:34:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 034E837B422 for ; Tue, 10 Apr 2001 15:34:44 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f3AMYS893727; Tue, 10 Apr 2001 15:34:28 -0700 (PDT) (envelope-from dillon) Date: Tue, 10 Apr 2001 15:34:28 -0700 (PDT) From: Matt Dillon Message-Id: <200104102234.f3AMYS893727@earth.backplane.com> To: Erick Mechler Cc: stable@FreeBSD.ORG Subject: Re: Runt packets References: <20010409161746.B33217@techometer.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I have a dual-homed machine doing routing and firewalling on which hundreds :of the following messages appear in my logs every 10 minutes or so: : : /kernel: icmp-response bandwidth limit 44069/200 pps : /kernel: arp: runt packet : last message repeated 14691 times : :At the same time these messages are occurring, I find the following while :doing a tcpdump on the internal interface (it doesn't happen on the :external interface at all): : : 19:05:34.247543 arp-#12469 for proto #208 (166) hardware #1 (183) : 19:05:34.247588 arp-#12469 for proto #208 (166) hardware #1 (183) : 19:05:34.247630 arp-#12469 for proto #208 (166) hardware #1 (183) : 19:05:34.247674 arp-#12469 for proto #208 (166) hardware #1 (183) : 19:05:34.247718 arp-#12469 for proto #208 (166) hardware #1 (183) : 19:05:34.247762 arp-#12469 for proto #208 (166) hardware #1 (183) : 19:05:34.247805 arp-#12469 for proto #208 (166) hardware #1 (183) : :...except there are thousands of these. Has anybody seen this before? :I'm running a slightly old version of 4.2 (Thu Dec 14 15:28:03 EST 2000), :but I didn't see any relevant diffs to sys/netinet/if_ether.c which is :where the "runt packet" errors are sent to syslog. Could this be a problem :of bad hardware on the part of one of the internal hosts? : :Any and all help is much appreciated. : :Thanks! :Erick A runt packet is typically caused by a collision on an ethernet segment. There are lots of possibilities, but the jist is that if your network is misconfigured you can wind up with a 'packet storm' of activity due to competing machines constantly tripping over each other trying to retransmit (usually large) packets. Runt packets typically cannot pass through routers, but they can pass throug hubs and can also often pass through switches (depending on the method the switch uses to switch packets). Here are some possibilities: * You have a bad switch in your network somewhere nearby that is allowing runt packets to be passed through and someone on some other nearby LAN (connected to you through the switch) is broken. * You have too many hubs and/or too-long ethernet segments in your network somewhere nearby. * There is a misconfigured host on the network. For example, a host that is configured for full duplex in a half duplex network will happily blast packets down the wire and cause everyone else to retry continuously ('packet storm') while it is doing it. Your problem kinda sounds like #3, but I don't your topology. The easiest solution is take a small store-and-forward switch and insert inline with segments of your network until you can isolate the problem source. Any modern cheap 10/100 switch should do the job. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 15:40:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hawk.mail.pas.earthlink.net (hawk.mail.pas.earthlink.net [207.217.120.22]) by hub.freebsd.org (Postfix) with ESMTP id 4E34037B424 for ; Tue, 10 Apr 2001 15:40:13 -0700 (PDT) (envelope-from zer0byte@linuxfreemail.com) Received: from linuxfreemail.com (pool0546.cvx4-bradley.dialup.earthlink.net [209.178.148.36]) by hawk.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id PAA25907 for ; Tue, 10 Apr 2001 15:40:12 -0700 (PDT) Message-ID: <3AD38A53.52242319@linuxfreemail.com> Date: Tue, 10 Apr 2001 15:33:56 -0700 From: zer0byte X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: freebsd-stable@freebsd.org subscribe freebsd-stable Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 15:53:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from greenbox.dhs.org (host51.south.iit.edu [216.47.130.51]) by hub.freebsd.org (Postfix) with ESMTP id 5642337B424 for ; Tue, 10 Apr 2001 15:53:22 -0700 (PDT) (envelope-from spigot@greenbox.dhs.org) Received: (from spigot@localhost) by greenbox.dhs.org (8.11.1/8.11.1) id f3AMqK215202 for freebsd-stable@freebsd.org; Tue, 10 Apr 2001 17:52:20 -0500 (CDT) (envelope-from spigot) Date: Tue, 10 Apr 2001 17:52:20 -0500 (CDT) From: Greggory Gruen Message-Id: <200104102252.f3AMqK215202@greenbox.dhs.org> To: freebsd-stable@freebsd.org Subject: problem with stable installworld Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, You'll have to excuse me, I'm quite the new user. I sychronized my source with the stable branch using cvsup. Everything went ok with buildworld but now installworld is giving me errors. I get something along the lines of: ln: /usr/share/man/man3/mvaddnstr.3.gz no such file rm -f /usr/include/ncurses.h Error code 1 And that's pretty much it. It stops from there. I may have missed some documentation somewhere, like I said, I'm very new. Thanks for the help To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 16:23:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from greenbox.dhs.org (host51.south.iit.edu [216.47.130.51]) by hub.freebsd.org (Postfix) with ESMTP id 2420437B424 for ; Tue, 10 Apr 2001 16:23:18 -0700 (PDT) (envelope-from spigot@greenbox.dhs.org) Received: (from spigot@localhost) by greenbox.dhs.org (8.11.1/8.11.1) id f3ANMJS15254 for freebsd-stable@freebsd.org; Tue, 10 Apr 2001 18:22:19 -0500 (CDT) (envelope-from spigot) Date: Tue, 10 Apr 2001 18:22:19 -0500 (CDT) From: Greggory Gruen Message-Id: <200104102322.f3ANMJS15254@greenbox.dhs.org> To: freebsd-stable@freebsd.org Subject: fixed problem with installworld Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG problem fixed. I misread the handbook and thought I could use the -j during make for the installworld. I got rid of it and all was well. thanks Gregg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 16:31:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 2936937B422; Tue, 10 Apr 2001 16:31:55 -0700 (PDT) (envelope-from billf@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1098) id D1F9281D01; Tue, 10 Apr 2001 18:31:54 -0500 (CDT) Date: Tue, 10 Apr 2001 18:31:54 -0500 From: Bill Fumerola To: Marko Cuk Cc: freebsd-stable@freebsd.org, freebsd-ipfw@freebsd.org Subject: Re: NATd & high internal load - help Message-ID: <20010410183154.H75584@elvis.mu.org> References: <3AD2DB66.FA4A4F75@cuk.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AD2DB66.FA4A4F75@cuk.nu>; from cuk@cuk.nu on Tue, Apr 10, 2001 at 12:07:34PM +0200 X-Operating-System: FreeBSD 4.3-FEARSOME-20010328 i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 10, 2001 at 12:07:34PM +0200, Marko Cuk wrote: > > I have also 84 ipfw rules for firewall ( most of them reset and deny and > a few dummynet pipes ). > Is the processor too slow for that ? Depending on the order of these rules: possibly. -- Bill Fumerola - security yahoo / Yahoo! inc. - fumerola@yahoo-inc.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 16:56:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.noos.fr (verlaine.noos.net [212.198.2.73]) by hub.freebsd.org (Postfix) with ESMTP id 6D16037B424 for ; Tue, 10 Apr 2001 16:56:38 -0700 (PDT) (envelope-from clefevre@poboxes.com) Received: (qmail 5459284 invoked by uid 0); 10 Apr 2001 23:56:36 -0000 Received: from d165.dhcp212-198-231.noos.fr (HELO gits.dyndns.org) ([212.198.231.165]) (envelope-sender ) by verlaine.noos.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 10 Apr 2001 23:56:36 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.3/8.11.3) id f3ANuZw43187; Wed, 11 Apr 2001 01:56:35 +0200 (CEST) (envelope-from clefevre@poboxes.com) To: bmah@FreeBSD.ORG Cc: simond@irrelevant.org, Michael Nottebrock , freebsd-stable@FreeBSD.ORG Subject: Re: ATA_ENABLE_ATAPI_DMA gone? References: <02db01c0c1b1$c1a0ffe0$0508a8c0@lofi.dyndns.org> <20010410123317.A73359@irrelevant.org> <200104101342.f3ADgsn15019@bmah-freebsd-0.cisco.com> X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C Reply-To: Cyrille Lefevre In-Reply-To: <200104101342.f3ADgsn15019@bmah-freebsd-0.cisco.com> Mail-Copies-To: never From: Cyrille Lefevre Date: 11 Apr 2001 01:56:34 +0200 Message-ID: Lines: 25 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Bruce A. Mah" writes: > > It seems that they've been moved, the new ata(4) explains how to set them > > (ie from the loader) > > And it's also mentioned in RELNOTES.TXT: > > # To provide more flexible configuration, the various options for the > # ata(4) driver are now boot loader tunables, rather than kernel > # configure-time options. the ata(4) manual page isn't clear about the difference between hw.ata.ata_dma (where ata-disk.c says ATA disk DMA mode control) and hw.ata.atapi_dma (where atapi-all.c says ATAPI device DMA mode control) ? well, humm! also, what is the purpose of the (last) descr field in SYSCTL_* macros. is there any way to obtain the description of such sysctl from the user land ? Cyrille. -- home: mailto:clefevre@poboxes.com UNIX is user-friendly; it's just particular work: mailto:Cyrille.Lefevre@edf.fr about who it chooses to be friends with. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 17:11:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from spare.westbend.net (spare.westbend.net [216.106.246.5]) by hub.freebsd.org (Postfix) with ESMTP id 1ED4337B422 for ; Tue, 10 Apr 2001 17:11:10 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: (from root@localhost) by spare.westbend.net (8.11.3/8.11.3) id f3B0Ejx27571 for freebsd-stable@freebsd.org; Tue, 10 Apr 2001 19:14:45 -0500 (CDT) (envelope-from hetzels@westbend.net) Date: Tue, 10 Apr 2001 19:14:45 -0500 (CDT) Message-Id: <200104110014.f3B0Ejx27571@spare.westbend.net> From: Scot.W.Hetel@spare.westbend.net To: FreeBSD-Stable@freebsd.org Subject: Release (patch included) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since, noone supplied a patch that will help users to find the information when the tag changes from -STABLE/-CURRENT to -BETA or -RC. I created a patch to newvers.sh that will display an informitive message. This patch changes the version string to include a message that can be used to inform the admin on where to get more information on the meaning of RC, BETA, & CURRENT. Scot W. Hetzel --- newvers.sh.orig Wed Mar 21 15:06:19 2001 +++ newvers.sh Tue Apr 10 19:11:54 2001 @@ -84,13 +84,27 @@ echo 0 > version fi +if [ "${BRANCH}" = "RC" -o "${BRANCH}" = "BETA" ] ; then + WARNING="\\n See the ${TYPE} Handbook for the meaning of \`${BRANCH}'" + WARNING="${WARNING}\\n [place url to handbook/faq explaining the meaning of ${BRANCH} here]" + #WARNING="${WARNING}\\n http://www.freebsd.org/handbook/current-stable.html#${BRANCH}" + WARNING="${WARNING}\\n http://www.freebsd.org/FAQ/preface.html#STABLE" +fi + +if [ "${BRANCH}" = "CURRENT" ]; then + WARNING="\\n ${BRANCH} is a development version of ${TYPE}." + WARNING="${WARNING}\\n ${BRANCH} is not recommened for use on production systems." + WARNING="${WARNING}\\n http://www.freebsd.org/handbook/current-stable.html#AEN12985" + WARNING="${WARNING}\\n http://www.freebsd.org/FAQ/preface.html#CURRENT" +fi + touch version v=`cat version` u=${USER-root} d=`pwd` h=`hostname` t=`date` cat << EOF > vers.c $COPYRIGHT char sccspad[32 - 4 /* sizeof(sccs) */] = { '\\0' }; char sccs[4] = { '@', '(', '#', ')' }; -char version[] = "${VERSION} #${v}: ${t}\\n ${u}@${h}:${d}\\n"; +char version[] = "${VERSION} #${v}: ${t}\\n ${u}@${h}:${d}${WARNING}\\n"; char ostype[] = "${TYPE}"; char osrelease[] = "${RELEASE}"; int osreldate = ${RELDATE}; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 17:18:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 82D3637B422 for ; Tue, 10 Apr 2001 17:18:44 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f3B0Iit11922; Tue, 10 Apr 2001 17:18:44 -0700 (PDT) Date: Tue, 10 Apr 2001 17:18:44 -0700 From: Alfred Perlstein To: Scot.W.Hetel@spare.westbend.net Cc: FreeBSD-Stable@FreeBSD.ORG Subject: Re: Release (patch included) Message-ID: <20010410171844.I15938@fw.wintelcom.net> References: <200104110014.f3B0Ejx27571@spare.westbend.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104110014.f3B0Ejx27571@spare.westbend.net>; from Scot.W.Hetel@spare.westbend.net on Tue, Apr 10, 2001 at 07:14:45PM -0500 X-all-your-base: are belong to us. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Scot.W.Hetel@spare.westbend.net [010410 17:11] wrote: > Since, noone supplied a patch that will help users to find the > information when the tag changes from -STABLE/-CURRENT to -BETA > or -RC. I created a patch to newvers.sh that will display an > informitive message. > > This patch changes the version string to include a message > that can be used to inform the admin on where to get more > information on the meaning of RC, BETA, & CURRENT. Unfortunetly patches like this don't address the problem of a user accidentally upgrading to a version he doesn't want. For a patch to address that see: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=28213+0+archive/2001/freebsd-arch/20010325.freebsd-arch -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 17:24:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from c000.sfo.cp.net (c004-h009.c004.snv.cp.net [209.228.33.73]) by hub.freebsd.org (Postfix) with SMTP id B77D537B42C for ; Tue, 10 Apr 2001 17:24:40 -0700 (PDT) (envelope-from psglenn@uswestmail.net) Received: (cpmta 17952 invoked from network); 10 Apr 2001 17:24:40 -0700 Date: 10 Apr 2001 17:24:39 -0700 Message-ID: <20010411002439.17951.cpmta@c000.sfo.cp.net> X-Sent: 11 Apr 2001 00:24:39 GMT Received: from [64.40.47.245] by mail.uswestmail.net with HTTP; 10 Apr 2001 17:24:39 PDT Content-Type: multipart/mixed; boundary="----------=_986948679-12375-0" Mime-Version: 1.0 To: richw@webcom.com From: psglenn@uswestmail.net Cc: freebsd-stable@FreeBSD.org X-Mailer: Web Mail 3.7.1.9 Subject: Re: Silo overflows Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format... ------------=_986948679-12375-0 Content-Type: text/plain Content-Disposition: inline Hi. Back on March 13 I recieved a response from Gerd Knops [gerti@bitart.com] {thank you by the way} where he said ; >>Usually a sign that flow control was not enabled try >> stty -f /dev/cuaia1 crtscts >> stty -f /dev/cuala1 crtscts >>before using the modem that might help. I am using a US Robotics 56k sportster on /dev/cuaa1. I am running user ppp. I am running XFree86-4.0.3 because I have a 32meg 128 Rage pro card that needed 4.x for support. I was using ncftp3 to download but now I prefer lftp from a console terminal. I've been getting only a few silo overflows (about six) since I last posted about this problem. The flow control may have been the issue as I've downloaded 1.98TB since then. Three iso images. I'd like to change to kernel ppp with ipnat and ipfilter to see if that makes a difference. This has been an intermittant problem and I've just benn watching to see if I can make it repeat but so far I've not had any strings of hundreds of silo overflows wether I set flow control or not. Anyway thank you, and I'll report more as I discover said. Perry S Glenn. X-Received: 9 Apr 2001 04:49:00 GMT Date: Sun, 8 Apr 2001 21:48:56 -0700 (PDT) From: Rich Wales X-Sender: richw@wyattearp.stanford.edu To: psglenn@uswestmail.net Subject: Re: Silo overflows In-Reply-To: <20010313083251.21417.cpmta@c000.sfo.cp.net> >Hi. A few weeks ago, you said on the "freebsd-stable" list: > > I have been seeing many silo overflows lately. I'm running > > yesterday's 4.3 BETA and tracking stable. I've seen some > > mail about this problem so I send this info. . . . >If I may ask, are you using XFree86? And if so, what version? >The reason I'm asking is that someone suggested (on USENET) that the >silo overflow problem could be caused by version 4 of XFree86 -- as >opposed to the default version 3.3.6 which comes standard in FreeBSD. >Rich Wales richw@webcom.com http://www.webcom.com/richw/ Signup for your free USWEST.mail Email account http://www.uswestmail.net ------------=_986948679-12375-0 Content-Type: application/octet-stream; name="messa" Content-Disposition: attachment; filename="messa" Content-Transfer-Encoding: base64 WC1SZWNlaXZlZDogOSBBcHIgMjAwMSAwNDo0OTowMCBHTVQKRGF0ZTogU3Vu LCA4IEFwciAyMDAxIDIxOjQ4OjU2IC0wNzAwIChQRFQpCkZyb206IFJpY2gg V2FsZXMgPHJpY2h3QHdlYmNvbS5jb20+ClgtU2VuZGVyOiByaWNod0B3eWF0 dGVhcnAuc3RhbmZvcmQuZWR1ClRvOiBwc2dsZW5uQHVzd2VzdG1haWwubmV0 ClN1YmplY3Q6IFJlOiBTaWxvIG92ZXJmbG93cwpJbi1SZXBseS1UbzogPDIw MDEwMzEzMDgzMjUxLjIxNDE3LmNwbXRhQGMwMDAuc2ZvLmNwLm5ldD4KCkhp LiAgQSBmZXcgd2Vla3MgYWdvLCB5b3Ugc2FpZCBvbiB0aGUgImZyZWVic2Qt c3RhYmxlIiBsaXN0OgoKICAgID4gSSBoYXZlIGJlZW4gc2VlaW5nIG1hbnkg c2lsbyBvdmVyZmxvd3MgbGF0ZWx5LiAgSSdtIHJ1bm5pbmcKICAgID4geWVz dGVyZGF5J3MgNC4zIEJFVEEgYW5kIHRyYWNraW5nIHN0YWJsZS4gIEkndmUg c2VlbiBzb21lCiAgICA+IG1haWwgYWJvdXQgdGhpcyBwcm9ibGVtIHNvIEkg c2VuZCB0aGlzIGluZm8uIC4gLiAuCgpJZiBJIG1heSBhc2ssIGFyZSB5b3Ug dXNpbmcgWEZyZWU4Nj8gIEFuZCBpZiBzbywgd2hhdCB2ZXJzaW9uPwoKVGhl IHJlYXNvbiBJJ20gYXNraW5nIGlzIHRoYXQgc29tZW9uZSBzdWdnZXN0ZWQg KG9uIFVTRU5FVCkgdGhhdCB0aGUKc2lsbyBvdmVyZmxvdyBwcm9ibGVtIGNv dWxkIGJlIGNhdXNlZCBieSB2ZXJzaW9uIDQgb2YgWEZyZWU4NiAtLSBhcwpv cHBvc2VkIHRvIHRoZSBkZWZhdWx0IHZlcnNpb24gMy4zLjYgd2hpY2ggY29t ZXMgc3RhbmRhcmQgaW4gRnJlZUJTRC4KClJpY2ggV2FsZXMgICAgICAgICBy aWNod0B3ZWJjb20uY29tICAgICAgICAgaHR0cDovL3d3dy53ZWJjb20uY29t L3JpY2h3LwoKLS0tLS0gRW5kIGZvcndhcmRlZCBtZXNzYWdlIC0tLS0tCgo= ------------=_986948679-12375-0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 17:24:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id 847BB37B423 for ; Tue, 10 Apr 2001 17:24:46 -0700 (PDT) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.11.3) with SMTP id f3B0MlR27549; Tue, 10 Apr 2001 20:22:47 -0400 (EDT) (envelope-from matt@gsicomp.on.ca) Message-ID: <003301c0c21d$2c4b0cd0$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Cyrille Lefevre" Cc: References: <02db01c0c1b1$c1a0ffe0$0508a8c0@lofi.dyndns.org><20010410123317.A73359@irrelevant.org><200104101342.f3ADgsn15019@bmah-freebsd-0.cisco.com> Subject: Re: ATA_ENABLE_ATAPI_DMA gone? Date: Tue, 10 Apr 2001 20:20:10 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > the ata(4) manual page isn't clear about the difference between > hw.ata.ata_dma (where ata-disk.c says ATA disk DMA mode control) and > hw.ata.atapi_dma (where atapi-all.c says ATAPI device DMA mode control) ? ATA devices are hard disks. ATAPI devices are everything else (tape drives, floppy drives - including ZIP drives, and CD-ROM and DVD drives). ATA was originally developed as a standard for hard drives, and was later extended to support other devices. Hence, ATAPI, where PI stands for "Peripheral Interconnect" or something like that. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 17:28:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ece.cmu.edu (ECE.CMU.EDU [128.2.236.200]) by hub.freebsd.org (Postfix) with ESMTP id 1DEF037B423 for ; Tue, 10 Apr 2001 17:28:28 -0700 (PDT) (envelope-from allbery@ece.cmu.edu) Received: from rushlight.rem.cmu.edu (ANNEX-5.ECE.CMU.EDU [128.2.136.5]) (authenticated) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id f3B0Rgr12078; Tue, 10 Apr 2001 20:27:42 -0400 (EDT) Date: Tue, 10 Apr 2001 20:27:40 -0400 From: "Brandon S. Allbery KF8NH" To: Cyrille Lefevre Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ATA_ENABLE_ATAPI_DMA gone? Message-ID: <236930000.986948860@rushlight.rem.cmu.edu> In-Reply-To: X-Mailer: Mulberry/2.0.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, April 11, 2001 01:56:34 +0200, clefevre-lists@noos.fr wrote: +---- | "Bruce A. Mah" writes: | | > > It seems that they've been moved, the new ata(4) explains how to set | them > > (ie from the loader) | > | > And it's also mentioned in RELNOTES.TXT: | > | > # To provide more flexible configuration, the various options for the | > # ata(4) driver are now boot loader tunables, rather than kernel | > # configure-time options. | | the ata(4) manual page isn't clear about the difference between | hw.ata.ata_dma (where ata-disk.c says ATA disk DMA mode control) and | hw.ata.atapi_dma (where atapi-all.c says ATAPI device DMA mode control) ? +--->8 As I understand it, ATA disks generally support DMA, and ATAPI devices (floppies, tapes, CDROM/CDRW, etc.) generally don't; but some (many?) ATAPI devices claim to support it due to buggy firmware. So you have to enable DMA for ATAPI devices manually, if you want it and you know that you have ATAPI devices which don't falsely report DMA capability. -- brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering KF8NH carnegie mellon university ["better check the oblivious first" -ke6sls] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 17:31:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id E7C8B37B422 for ; Tue, 10 Apr 2001 17:31:17 -0700 (PDT) (envelope-from juha@saarinen.org) Received: from dendennis.saarinen.org ([192.168.1.2] helo=dendennis) by vimfuego.saarinen.org with smtp (Exim 3.22 #1 (Red Hack)) id 14n8XJ-0002fu-00; Wed, 11 Apr 2001 12:31:05 +1200 From: "Juha Saarinen" To: "Matthew Emmerton" , "Cyrille Lefevre" Cc: Subject: RE: ATA_ENABLE_ATAPI_DMA gone? Date: Wed, 11 Apr 2001 12:30:55 +1200 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.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: <003301c0c21d$2c4b0cd0$1200a8c0@gsicomp.on.ca> Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :: ATA devices are hard disks. :: ATAPI devices are everything else (tape drives, floppy drives - including :: ZIP drives, and CD-ROM and DVD drives). :: :: ATA was originally developed as a standard for hard drives, and was later :: extended to support other devices. Hence, ATAPI, where PI stands for :: "Peripheral Interconnect" or something like that. Well, not quite. The AT Attachment Packet Interface is part of the ATA-2 spec. -- Juha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 17:33: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id 994C737B422 for ; Tue, 10 Apr 2001 17:33:03 -0700 (PDT) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.11.3) with SMTP id f3B0VFR27586 for ; Tue, 10 Apr 2001 20:31:15 -0400 (EDT) (envelope-from matt@gsicomp.on.ca) Message-ID: <00b801c0c21e$5a1532c0$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: References: <014a01c0c12e$e5e76f20$1200a8c0@gsicomp.on.ca> <20010410145433.C20548@hub.freebsd.org> Subject: Re: Releases Date: Tue, 10 Apr 2001 20:28:37 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, Apr 09, 2001 at 03:54:32PM -0400, Matthew Emmerton wrote: > > pre-alphas and totally trashed most systems and rightly freak out most > > novice admins), while STABLE/RC/RELEASE just makes sense. However, this > > You obviously haven't been reading all the threads on this same topic > over the past month. We need the "BETA" stage for ports. Plain and > simple. Some seem to prefer -PRERELEASE. I don't care what it is called > -- 4.3-I_AM_A_MORNON_BECAUSE_I_DO_NOT_RTFM would be fine too. Read the > archives to see why it is needed for ports right before a release. Do you read every thread on every topic? While reading through some of the other messages in this thread I figured out what the -BETA stage is used for, and in many cases, the name is appropriate, although it's confusing to people unfamiliar with the release process. As was previously mentioned, documenting this "black magic" release process is a tough thing to do. However, I'd be willing to solicit explanations of the release process from people who are familiar with it so that it can be documented, with appropriate references made to it where -STABLE is mentioned in the handbook. This is a first step into providing better documentation which we can arm ourselves with to point people at, in order to avoid discussions like this one from recurring. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 17:40:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id B396537B422 for ; Tue, 10 Apr 2001 17:40:31 -0700 (PDT) (envelope-from juha@saarinen.org) Received: from dendennis.saarinen.org ([192.168.1.2] helo=dendennis) by vimfuego.saarinen.org with smtp (Exim 3.22 #1 (Red Hack)) id 14n8gF-0002gn-00; Wed, 11 Apr 2001 12:40:19 +1200 From: "Juha Saarinen" To: "Brandon S. Allbery KF8NH" , "Cyrille Lefevre" Cc: Subject: RE: ATA_ENABLE_ATAPI_DMA gone? Date: Wed, 11 Apr 2001 12:40:09 +1200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: <236930000.986948860@rushlight.rem.cmu.edu> Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :: As I understand it, ATA disks generally support DMA, and ATAPI devices :: (floppies, tapes, CDROM/CDRW, etc.) generally don't; My understanding is that DMA is more efficient than PIO, so you'll find that newer CD ROM drives (ditto DVD drives) support it, because of the higher transfer rates provided. Slower floppy and tape drives on the other hand can get by with PIO. Don't think it's a device-specific issue, but I could be wrong. -- Juha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 17:43:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from femail8.sdc1.sfba.home.com (femail8.sdc1.sfba.home.com [24.0.95.88]) by hub.freebsd.org (Postfix) with ESMTP id 1ADF037B422 for ; Tue, 10 Apr 2001 17:43:29 -0700 (PDT) (envelope-from graywane@home.com) Received: from cg392862-a.adubn1.nj.home.com ([65.2.79.221]) by femail8.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010411004326.SEDR26721.femail8.sdc1.sfba.home.com@cg392862-a.adubn1.nj.home.com> for ; Tue, 10 Apr 2001 17:43:26 -0700 Received: (from graywane@localhost) by cg392862-a.adubn1.nj.home.com (8.11.3/8.11.3) id f3B0hMv01035 for freebsd-stable@FreeBSD.ORG; Tue, 10 Apr 2001 20:43:22 -0400 (EDT) (envelope-from graywane) Date: Tue, 10 Apr 2001 20:43:20 -0400 From: Graywane To: freebsd-stable@FreeBSD.ORG Subject: Re: ATA_ENABLE_ATAPI_DMA gone? Message-ID: <20010410204319.A995@home.com> References: <236930000.986948860@rushlight.rem.cmu.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="82I3+IH0IqGh5yIs" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <236930000.986948860@rushlight.rem.cmu.edu>; from allbery@ece.cmu.edu on Tue, Apr 10, 2001 at 08:27:40PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --82I3+IH0IqGh5yIs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 10, 2001 at 08:27:40PM -0400, Brandon S. Allbery KF8NH wrote: > As I understand it, ATA disks generally support DMA, and ATAPI devices=20 > (floppies, tapes, CDROM/CDRW, etc.) generally don't; but some (many?) ATA= PI=20 > devices claim to support it due to buggy firmware. So you have to enable= =20 > DMA for ATAPI devices manually, if you want it and you know that you have= =20 > ATAPI devices which don't falsely report DMA capability. While everyone is on the topic... I have an old CDROM that barfs if you have DMA or PIO enabled. Both FreeBSD and OpenBSD on two different motherboards reboot if you access the drive while PIO or DMA is enabled. In OpenBSD I can set the "flags" option in the kernel config file to disable PIO and DMA on the drive and then the drive works fine. In FreeBSD I can't seem to find an option to do the same thing. Anyone have any ideas. --=20 Note: See http://www.members.home.net/graywane/ for PGP information. --82I3+IH0IqGh5yIs Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjrTqKcACgkQeHdFaBWUGN0uPgCdEKs4nJRNNftiEAOk22N29CVV zCUAnis+m07eFNPXcIDKIugse0+n31ot =xw5w -----END PGP SIGNATURE----- --82I3+IH0IqGh5yIs-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 17:45:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.noos.fr (lafontaine.noos.net [212.198.2.72]) by hub.freebsd.org (Postfix) with ESMTP id 4A2CC37B422 for ; Tue, 10 Apr 2001 17:45:26 -0700 (PDT) (envelope-from root@gits.dyndns.org) Received: (qmail 311299 invoked by uid 0); 11 Apr 2001 00:45:18 -0000 Received: from d165.dhcp212-198-231.noos.fr (HELO gits.dyndns.org) ([212.198.231.165]) (envelope-sender ) by lafontaine.noos.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 11 Apr 2001 00:45:18 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.3/8.11.3) id f3B0jHA45737; Wed, 11 Apr 2001 02:45:17 +0200 (CEST) (envelope-from root) From: Cyrille Lefevre Message-Id: <200104110045.f3B0jHA45737@gits.dyndns.org> Subject: Re: ATA_ENABLE_ATAPI_DMA gone? In-Reply-To: <003301c0c21d$2c4b0cd0$1200a8c0@gsicomp.on.ca> "from Matthew Emmerton at Apr 10, 2001 08:20:10 pm" To: Matthew Emmerton Date: Wed, 11 Apr 2001 02:45:16 +0200 (CEST) Cc: freebsd-stable@FreeBSD.ORG, freebsd-doc@FreeBSD.ORG Reply-To: clefevre@poboxes.com Organization: ACME X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Emmerton wrote: > > the ata(4) manual page isn't clear about the difference between > > hw.ata.ata_dma (where ata-disk.c says ATA disk DMA mode control) and > > hw.ata.atapi_dma (where atapi-all.c says ATAPI device DMA mode control) ? > > ATA devices are hard disks. > ATAPI devices are everything else (tape drives, floppy drives - including > ZIP drives, and CD-ROM and DVD drives). I was just saying that the documentation isn't clear about that and I suppose that everybody don't have to look into the code to make the difference between them. do you understand what I mean. currently, the manual page entry says : hw.ata.ata_dma set to 1 for DMA access 0 for PIO (default is DMA). hw.ata.atapi_dma set to 1 for DMA access 0 for PIO (default is PIO). as you can see, neither the denomination nor the description say that hw.ata.ata_dma is about disks and hw.ata.atapi_dma for all other things. also, why ata_dma and just wc or tags ? to be homogeneous, the laters would have be named ata_wc and ata_tags. about tags, is there a software way to know if some drive is DPTA or DTLA compliant ? what's happen if someone enable this w/ uncompliant drives ? CC: -doc Cyrille. -- home: mailto:clefevre@poboxes.com UNIX is user-friendly; it's just particular work: mailto:Cyrille.Lefevre@edf.fr about who it chooses to be friends with. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 17:48:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.westbend.net (ns1.westbend.net [216.106.246.3]) by hub.freebsd.org (Postfix) with ESMTP id 6EA8737B424 for ; Tue, 10 Apr 2001 17:48:31 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin0.westbend.net [216.106.246.17]) by mail.westbend.net (8.11.2/8.11.2) with ESMTP id f3B0mTU76985; Tue, 10 Apr 2001 19:48:29 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <002f01c0c220$f01628e0$11f66ad8@westbend.net> From: "Scot W. Hetzel" To: Cc: "\"Alfred Perlstein\"" References: <200104110014.f3B0Ejx27571@spare.westbend.net> <20010410171844.I15938@fw.wintelcom.net> Subject: Re: Release (patch included) Date: Tue, 10 Apr 2001 19:47:07 -0500 Organization: West Bend Interent 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.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "Alfred Perlstein" > Unfortunetly patches like this don't address the problem of a user > accidentally upgrading to a version he doesn't want. > > For a patch to address that see: > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=28213+0+archive/2001/freebsd-ar ch/20010325.freebsd-arch > Your patch is much better, as the user is informed before install[kernel|world] that they are upgrading to a newer release. But it doesn't address the RC, BETA tag naming issue. What you could do is check $newvers for the RC, BETA, and CURRENT tags, and then provide URL links to the appropriate Handbook/FAQ entries for RC, BETA, and CURRENT. That way we can get theses "I cvsuped STABLE and now I have BETA/RC" questions off the list. Scot PS: I didn't mean to start a new thread on this subject. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 17:49:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ece.cmu.edu (ECE.CMU.EDU [128.2.236.200]) by hub.freebsd.org (Postfix) with ESMTP id 2534E37B422 for ; Tue, 10 Apr 2001 17:49:38 -0700 (PDT) (envelope-from allbery@ece.cmu.edu) Received: from rushlight.rem.cmu.edu (ANNEX-5.ECE.CMU.EDU [128.2.136.5]) (authenticated) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id f3B0mgr13301; Tue, 10 Apr 2001 20:48:42 -0400 (EDT) Date: Tue, 10 Apr 2001 20:48:41 -0400 From: "Brandon S. Allbery KF8NH" To: Juha Saarinen , "Brandon S. Allbery KF8NH" , Cyrille Lefevre Cc: freebsd-stable@FreeBSD.ORG Subject: RE: ATA_ENABLE_ATAPI_DMA gone? Message-ID: <250770000.986950121@rushlight.rem.cmu.edu> In-Reply-To: X-Mailer: Mulberry/2.0.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, April 11, 2001 12:40:09 +1200, juha@saarinen.org wrote: +---- | :: As I understand it, ATA disks generally support DMA, and ATAPI devices | :: (floppies, tapes, CDROM/CDRW, etc.) generally don't; | | My understanding is that DMA is more efficient than PIO, so you'll find | that newer CD ROM drives (ditto DVD drives) support it, because of the | higher transfer rates provided. | | Slower floppy and tape drives on the other hand can get by with PIO. | | Don't think it's a device-specific issue, but I could be wrong. +--->8 Certainly early CDROMs falsely claiming DMA support caused pain in the Linux community until they split off ATAPI DMA support into a separate config option. One can hope that modern hardware doesn't have that problem, but I have little faith in PC hardware :) -- brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering KF8NH carnegie mellon university ["better check the oblivious first" -ke6sls] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 17:56:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id 4E4B037B422 for ; Tue, 10 Apr 2001 17:56:09 -0700 (PDT) (envelope-from juha@saarinen.org) Received: from dendennis.saarinen.org ([192.168.1.2] helo=dendennis) by vimfuego.saarinen.org with smtp (Exim 3.22 #1 (Red Hack)) id 14n8vW-0002hE-00; Wed, 11 Apr 2001 12:56:06 +1200 From: "Juha Saarinen" To: "Graywane" , Subject: RE: ATA_ENABLE_ATAPI_DMA gone? Date: Wed, 11 Apr 2001 12:55:55 +1200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: <20010410204319.A995@home.com> Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :: I have an old CDROM that barfs if you have DMA or PIO enabled. :: Both FreeBSD :: and OpenBSD on two different motherboards reboot if you access the drive :: while PIO or DMA is enabled. In OpenBSD I can set the "flags" :: option in the :: kernel config file to disable PIO and DMA on the drive and then the drive :: works fine. In FreeBSD I can't seem to find an option to do the :: same thing. :: Anyone have any ideas. What is it using if you disable both PIO and DMA? It sounds like you have the wrong PIO mode enabled (if it's older drive, it'll likely only support PIO modes 0, 1 and 2). -- Juha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 17:56:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id C044D37B422 for ; Tue, 10 Apr 2001 17:56:18 -0700 (PDT) (envelope-from juha@saarinen.org) Received: from dendennis.saarinen.org ([192.168.1.2] helo=dendennis) by vimfuego.saarinen.org with smtp (Exim 3.22 #1 (Red Hack)) id 14n8vW-0002hE-01; Wed, 11 Apr 2001 12:56:06 +1200 From: "Juha Saarinen" To: "Brandon S. Allbery KF8NH" , "Cyrille Lefevre" Cc: Subject: RE: ATA_ENABLE_ATAPI_DMA gone? Date: Wed, 11 Apr 2001 12:55:56 +1200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: <250770000.986950121@rushlight.rem.cmu.edu> Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :: Certainly early CDROMs falsely claiming DMA support caused pain in the :: Linux community until they split off ATAPI DMA support into a separate :: config option. One can hope that modern hardware doesn't have that :: problem, but I have little faith in PC hardware :) Yes, seen that a lot on various platforms... think lot of it was caused by "non-standard" AT implementations that differed from vendor to vendor. Anyway, looked it up. ATA-1 specified these modes: PIO 0, 1 and 2 DMA 0, 1 and 2 plus multi-word DMA 0. ATA-2 added the Packet Interface stuff, so that you hang non-hd devices off the IDE interface, plus block-mode transfers, LBA, more DMA modes etc. PIO is in fact deprecated, if I read things right. Cheers, -- Juha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 21:30:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 2879A37B423 for ; Tue, 10 Apr 2001 21:30:45 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from spike.unixfreak.org (spike [63.198.170.139]) by bazooka.unixfreak.org (Postfix) with ESMTP id 07F373E09; Tue, 10 Apr 2001 21:30:41 -0700 (PDT) To: "Rodney W. Grimes" Cc: sjt@cisco.com (Steve Tremblett), freebsd-stable@FreeBSD.ORG Subject: Re: Releases In-Reply-To: <200104101534.IAA35432@gndrsh.dnsmgr.net>; from freebsd@gndrsh.dnsmgr.net on "Tue, 10 Apr 2001 08:34:25 -0700 (PDT)" Date: Tue, 10 Apr 2001 21:30:40 -0700 From: Dima Dorfman Message-Id: <20010411043041.07F373E09@bazooka.unixfreak.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Rodney W. Grimes" writes: > The tag sequences could be better documented, or err, the newvers.sh > changes that occuring during the phases could be better documented. Attached is something that resembles a first attempt at this. Essentially, it's the admin.html#RELEASE-CANDIDATE FAQ question but with more detail. It's not meant as an extensive guide, but rather a summary of what happens and some appropriate rationale. The FAQ entry is great, but I think something with more detail is in order. I'm not quite sure where this should go. It seems redundant and too long for the FAQ, but it's not quite an article, although I guess I could add some more to it to make an article about "The FreeBSD Release Cycle". At the very least it's a summary of the majority of the anti-BETA threads. Comments and suggestions welcome. Thanks, Dima Dorfman dima@unixfreak.org How -STABLE becomes -RELEASE Minor releases, i.e. releases where the minor version number is greater than zero, are tags, or points, on the RELENG_X branch corresponding to their major version number. Before a release is made, the branch its being cut from goes through a ``code freeze''. A code freeze is the state in which all changes to the respective branch must be approved by the release engineer before being committed {XXX footnote explain 'commit'}. During the code freeze, the branch is renamed from ``-STABLE'' to ``-BETA''. There are two reasons for this seemingly unreasonable change: 1. Right before the code freeze (a few days), a lot of changes--fixes and others--are merged from -CURRENT (``MFC'd''). This isn't an intentional part of the release cycle; it just so happens that developers wait until the day before the freeze to merge the changes they want in the release (and since this is a volunteer project, we shouldn't ask them to do otherwise). Thus, the quality of the code right before the code freeze is slightly impaired. 2. Some ports break in mysterious ways when the version of the system changes (e.g., 3.1 becomes 3.2). It is desireable that the ports as shipped with the release work properly, so they must be tested on a system as similar to the one being release as possible; bumping the version number is just another way to catch some rather silly and easy-to-correct errors. Also, since the ports collection is collectively maintained by over 500 {XXX is this right?} people, it would be unfair to ask them to manually change the version number themselves simply for testing the ports. The branch remains in the code freeze anywhere from a few weeks to a month. As the code freeze draws to a close, and the release to its due date, the branch is renamed from ``-BETA'' to ``-RC''. RC stands for release candidate. Anything marked as a release candidate may eventually become the release without any changes (modulo the branch name). Depending on how many changes do occur in this state, there may be multiple release candidates. These are represented as ``-RCx'' where x is the number of the release candidate. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 21:57:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ureach.com (mail.ureach.com [63.150.151.36]) by hub.freebsd.org (Postfix) with ESMTP id 199E537B424 for ; Tue, 10 Apr 2001 21:57:53 -0700 (PDT) (envelope-from pechter@ureach.com) Received: from www21.ureach.com (IDENT:root@www21.ureach.com [172.16.2.49]) by ureach.com (8.9.1/8.8.5) with ESMTP id AAA11473 for ; Wed, 11 Apr 2001 00:57:52 -0400 Received: (from nobody@localhost) by www21.ureach.com (8.9.3/8.9.1) id AAA02595; Wed, 11 Apr 2001 00:57:52 -0400 Date: Wed, 11 Apr 2001 00:57:52 -0400 Message-Id: <200104110457.AAA02595@www21.ureach.com> To: freebsd-stable@freebsd.org From: Bill Pechter Reply-To: Subject: SSH -- "No RSA support in lib ssl and libcrypto" on 4.3-RC upgraded from 4.2-STABLE Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-vsuite-type: e Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm sure the following is something obvious, but it appears to be eluding me tonight. I installed 4.2-RELEASE at work and cvsupped to get 4.3-RC sources and did a make kernel and world. When generating ssh keys as myself and not root I get the following. ssh-keygen ssh-keygen: no RSA support in libssl and libcrypto. See ssl(8). My home machine running 4.3-RC (4.2-STABLE as of Saturday does not show the same message...) Any obvious idea what I'm missing here. -- Bill Pechter Systems Administrator To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 22:23:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from astral.isec.com.br (astral.isec.com.br [200.254.79.62]) by hub.freebsd.org (Postfix) with SMTP id AA74F37B422 for ; Tue, 10 Apr 2001 22:23:39 -0700 (PDT) (envelope-from duwde@duwde.com.br) Received: (qmail 821 invoked from network); 11 Apr 2001 05:20:54 -0000 Received: from localhost.isec.com.br (HELO duwde.com.br) (127.0.0.1) by localhost.isec.com.br with SMTP; 11 Apr 2001 05:20:54 -0000 Message-ID: <3AD3E8E7.AB85B459@duwde.com.br> Date: Wed, 11 Apr 2001 02:17:27 -0300 From: "Duwde (Fabio V. Dias)" X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Little fix needed in /usr/src/etc/security (4.x-stable) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. The /usr/src/etc/security in the 4.x-stable needs a little fix. As we can see in /usr/src/contrib/bind/CHANGES line 495 there was a little change in the logging method since BIND 8.2.3-T1A, thus affecting all new versions. (8.2.3-REL is the 4.x-stable version) -- line 495 /usr/src/contrib/bind/CHANGES 940. [clarity] unapproved -> denied in log messages. -- /etc/security greps for "unapproved AXFR from" and the new bind logging method is "denied AXFR from", no big deal. Just to clarify, patch follows. Someone with access to the branch, please commit it or fix things up on your own way. ---------------------------------------------------------------------------- *** security.old Wed Apr 11 02:00:06 2001 --- security Wed Apr 11 02:00:26 2001 *************** *** 201,207 **** # separator echo "$host checking for denied secondary zone transfers:" ! n=$(catmsgs | grep -i "unapproved AXFR from" | tee /dev/stderr | wc -l) [ $n -gt 0 -a $rc -lt 1 ] && rc=1 rm -f ${TMP} --- 201,207 ---- # separator echo "$host checking for denied secondary zone transfers:" ! n=$(catmsgs | grep -i "denied AXFR from" | tee /dev/stderr | wc -l) [ $n -gt 0 -a $rc -lt 1 ] && rc=1 rm -f ${TMP} ---------------------------------------------------------------------------- My $0.01 contribution to the upcoming 4.3-release. PS: Reply, if needed (don't think so) to my email, as I'm not subscribed to the list. -- Fabio Vilan Dias / Duwde PGP key @ http://www.duwde.com.br/duwdepgp.asc FP = BB35 50F2 7F83 655D 6B11 F0A2 F8E2 FF3D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 22:31:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 138F437B422 for ; Tue, 10 Apr 2001 22:31:18 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id PAA23743; Wed, 11 Apr 2001 15:31:15 +1000 (EST) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37640) with ESMTP id <01K2A17JY6LSRW2IAP@cim.alcatel.com.au>; Wed, 11 Apr 2001 15:31:14 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f3B5VCi93011; Wed, 11 Apr 2001 15:31:12 +1000 (EST envelope-from jeremyp) Content-return: prohibited Date: Wed, 11 Apr 2001 15:31:12 +1000 From: Peter Jeremy Subject: Re: Releases In-reply-to: <20010411043041.07F373E09@bazooka.unixfreak.org>; from dima@unixfreak.org on Tue, Apr 10, 2001 at 09:30:40PM -0700 To: Dima Dorfman Cc: freebsd-stable@FreeBSD.ORG Mail-Followup-To: Dima Dorfman , freebsd-stable@FreeBSD.ORG Message-id: <20010411153112.T66243@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <200104101534.IAA35432@gndrsh.dnsmgr.net> <20010411043041.07F373E09@bazooka.unixfreak.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-Apr-10 21:30:40 -0700, Dima Dorfman wrote: >Attached is something that resembles a first attempt at this. >Essentially, it's the admin.html#RELEASE-CANDIDATE FAQ question but >with more detail. Looks quite good. The only minor nit is that -BETA and -RC don't exist as CVS tags, they are just changes to the REVISION and BRANCH variables in /sys/conf/newvers.sh Once the release engineer is satisfied that a release candidate is suitable for release, he will change the BRANCH name in /sys/conf/newvers.sh to "RELEASE" and apply the appropriate CVS tag. I don't know if you want to document the way ports freezes work for completeness. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 22:48:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id E7C6137B423 for ; Tue, 10 Apr 2001 22:48:51 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id WAA38089; Tue, 10 Apr 2001 22:48:29 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200104110548.WAA38089@gndrsh.dnsmgr.net> Subject: Re: Releases In-Reply-To: <20010411043041.07F373E09@bazooka.unixfreak.org> from Dima Dorfman at "Apr 10, 2001 09:30:40 pm" To: dima@unixfreak.org (Dima Dorfman) Date: Tue, 10 Apr 2001 22:48:29 -0700 (PDT) Cc: sjt@cisco.com (Steve Tremblett), freebsd-stable@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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... > > Comments and suggestions welcome. > > Thanks, > > Dima Dorfman > dima@unixfreak.org > > > > How -STABLE becomes -RELEASE > > Minor releases, i.e. releases where the minor version number is > greater than zero, are tags, or points, on the RELENG_X branch > corresponding to their major version number. Before a release is > made, the branch its being cut from goes through a ``code freeze''. > > A code freeze is the state in which all changes to the respective > branch must be approved by the release engineer before being committed > {XXX footnote explain 'commit'}. During the code freeze, the branch > is renamed from ``-STABLE'' to ``-BETA''. There are two reasons for > this seemingly unreasonable change: > > 1. Right before the code freeze (a few days), a lot of > changes--fixes and others--are merged from -CURRENT (``MFC'd''). This > isn't an intentional part of the release cycle; it just so happens > that developers wait until the day before the freeze to merge the > changes they want in the release (and since this is a volunteer > project, we shouldn't ask them to do otherwise). Thus, the quality of > the code right before the code freeze is slightly impaired. The only comment I have is perhaps we should slightly change the actual procedure such that the -BETA goes on when the Release engineer announces the impending release, as that is when the flury of MFC commits start, and when the tree start to go down hill as far as stability. IMHO, the -BETA phase is usually marked to late in the time line... This would also give a clear marker to the commiters as to when the have to start asking the release engineer for MFC/commit permission. During -BETA it is open house, at -RC you have to ask for permission. Also some minor rewording may help, the code isn't really frozen until the release engineers says okay, stop doing all that nasty MFC stuff guys, it's time to re-stabalize this tree and get a release out the door. [If it was me still doing releases the commiters wouldn't even know it was about to happen, I'd just come along and go, yep, this is building pretty good, it's March 15th and time to cut a release... boom boom.. tag down.. beta build and pushed out... okay folks find the critical bugs and point me at MFS's to pull over, and I don't want to here what feature you'd like to see, it can wait for another 90 days, trust me.] [Jordan, put down that AK-47 I feel drawing a nice cross hair on the back of my head and calm down.... Also IMHO your doing just a fine job as things are, we just have different MO's :-) :-)] -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 10 23: 1:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.wanadoo.nl (smtp.wanadoo.nl [194.134.193.6]) by hub.freebsd.org (Postfix) with ESMTP id BBE8937B422 for ; Tue, 10 Apr 2001 23:01:40 -0700 (PDT) (envelope-from steveo@eircom.net) Received: from ams-gw.sohara.org (p223.vcu.wanadoo.nl [194.134.200.151]) by smtp.wanadoo.nl (8.11.2/8.11.2) with SMTP id f3B61Sq14985; Wed, 11 Apr 2001 08:01:29 +0200 (MET DST) Date: Wed, 11 Apr 2001 08:00:58 +0200 From: "Steve O'Hara-Smith" To: dan@langille.org Cc: freebsd@gndrsh.dnsmgr.net, freebsd-stable@FreeBSD.ORG Subject: Re: Releases Message-Id: <20010411080058.1f9ca01a.steveo@eircom.net> In-Reply-To: <200104101933.f3AJXYe81872@ns1.unixathome.org> References: <200104101336.JAA16571@sjt-u10.cisco.com> <200104101933.f3AJXYe81872@ns1.unixathome.org> X-Mailer: Sylpheed version 0.4.63cvs15 (GTK+ 1.2.8; i386-unknown-freebsdelf4.3) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=.UTa2ffq5nckG'+" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --=.UTa2ffq5nckG'+ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Tue, 10 Apr 2001 15:33:23 -0400 "Dan Langille" wrote: DL> Well, the branch makes a good deal of sense. It stops beta from DL> getting out to the people who track -stable and allows changes to be As a regular -stable tracker who does understand what the tags mean I *want* the BETA and RC stages in -stable. The current setup is fine IMHO. If I were a commiter I would *not* want the extra branch to deal with. Some people seem to have run off with the idea the -STABLE sits almost unchanged until -BETA and then all the MFCs happen. Nothing could be further from the truth, the -BETA and -RC names are symptoms of a code *freeze* and the rate of change *drops* a *lot*, just after -RELEASE is the potentially dodgy time when a bunch of stuff backed up against the code freeze gets put through - I have always been amazed that this causes so little disruption, a real credit to the commiters that. -- Optimal hardware acceleration for Windows PC (Mac). 9.81 m/s/s applied for (at least) 2s followed by impact with solid object. Optimal software upgrade FreeBSD (OS-X). --=.UTa2ffq5nckG'+ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4g (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE60/MkBT76Ak1D8yARAqjEAKCashwBwSSl6bS8JRrwKK+BXRNvOgCggHqo ut9IC0vU8Om1q0q7sTl8qXk= =1Jnt -----END PGP SIGNATURE----- --=.UTa2ffq5nckG'+-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 0:16:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 8710737B424 for ; Wed, 11 Apr 2001 00:16:42 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f3B7GX885566; Wed, 11 Apr 2001 00:16:34 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: Scot.W.Hetel@spare.westbend.net Cc: FreeBSD-Stable@FreeBSD.ORG Subject: Re: Release (patch included) In-Reply-To: <200104110014.f3B0Ejx27571@spare.westbend.net> References: <200104110014.f3B0Ejx27571@spare.westbend.net> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010411001633D.jkh@osd.bsdi.com> Date: Wed, 11 Apr 2001 00:16:33 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 6 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've retired the BETA tag since the last spate of contraversy over it; now we just go straight from -STABLE to -RC to -STABLE again (post-release). If we're going to confuse users, we might as well just confuse them once. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 0:40:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from camelot.bitart.com (BITart-45.BITart.com [206.103.221.45]) by hub.freebsd.org (Postfix) with SMTP id A11E837B422 for ; Wed, 11 Apr 2001 00:40:39 -0700 (PDT) (envelope-from gerti@bitart.com) Received: (qmail 264 invoked by uid 101); 11 Apr 2001 07:40:32 -0000 Message-ID: <20010411074032.263.qmail@camelot.bitart.com> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach v148) X-Nextstep-Mailer: Mail 4.2mach (Enhance 2.2p1) Received: by NeXT.Mailer (1.148) From: Gerd Knops Date: Wed, 11 Apr 2001 02:40:31 -0500 To: freebsd-stable@freebsd.org Subject: 4.3 PS2 drivers, mouse, KVM: Arrrgghhh Reply-To: gerti-freebsds@BITart.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Since I upgraded to 4.3-RC, the middle mouse button and the wheel on my IntelliMouse (connected through a Belkin OmniView SE) quit working. The exact same combination worked fine with an early 4.2 stable. Dmesg shows psm0: failed to get data. psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 The 'failed to get data' message seems to be new with 4.3-RC. If I connect the mouse directly (without KVM) it works fine (again: note that the combination WITH the KVM worked fine in early 4.2S). Any sugestions? Was the PS/2 driver modified recently in a way that could cause this? Thanks Gerd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 0:45:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hawk.mail.pas.earthlink.net (hawk.mail.pas.earthlink.net [207.217.120.22]) by hub.freebsd.org (Postfix) with ESMTP id E1E2137B42C for ; Wed, 11 Apr 2001 00:45:14 -0700 (PDT) (envelope-from oistrakh@earthlink.net) Received: from pirastro.oistrakh.org (user-2ivftss.dialup.mindspring.com [165.247.247.156]) by hawk.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id AAA04775; Wed, 11 Apr 2001 00:45:14 -0700 (PDT) Received: from localhost (oistrakh@localhost) by pirastro.oistrakh.org (8.11.3/8.11.1) with ESMTP id f3B7ifZ00474; Wed, 11 Apr 2001 00:44:42 -0700 (PDT) (envelope-from oistrakh@earthlink.net) X-Authentication-Warning: pirastro.oistrakh.org: oistrakh owned process doing -bs Date: Wed, 11 Apr 2001 00:44:41 -0700 (PDT) From: Christian Chen X-X-Sender: To: Cc: Subject: Re: 4.3 PS2 drivers, mouse, KVM: Arrrgghhh In-Reply-To: <20010411074032.263.qmail@camelot.bitart.com> Message-ID: <20010411004306.Q389-100000@pirastro.oistrakh.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Apr 2001, Gerd Knops wrote: > Since I upgraded to 4.3-RC, the middle mouse button and the wheel on > my IntelliMouse (connected through a Belkin OmniView SE) quit working. > The exact same combination worked fine with an early 4.2 stable. Dmesg > shows > > psm0: failed to get data. > psm0: irq 12 on atkbdc0 > psm0: model Generic PS/2 mouse, device ID 0 > > The 'failed to get data' message seems to be new with 4.3-RC. For what it's worth, I'm also using a KVM, and I've gotten that message in both 4.2-RELEASE and 4.3-RC. I'm still in the process of getting X up and running in a satisfactory fashion, so I can't comment on whether my Intellimouse works correctly despite that warning. Christian Chen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 1:32: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailjayb.creighton.edu (MailjayB.creighton.edu [147.134.2.193]) by hub.freebsd.org (Postfix) with ESMTP id 94ACD37B423 for ; Wed, 11 Apr 2001 01:32:00 -0700 (PDT) (envelope-from cwilmes@creighton.edu) Received: from bluejay.creighton.edu (bluejay.creighton.edu [147.134.2.20]) by mailjayb.creighton.edu (8.9.3 (PHNE_18546)/8.9.3) with ESMTP id DAA15933; Wed, 11 Apr 2001 03:31:55 -0500 (CDT) Date: Wed, 11 Apr 2001 03:31:55 -0500 (CDT) From: To: Christian Chen Cc: gerti-freebsds@bitart.com, freebsd-stable@FreeBSD.ORG Subject: Re: 4.3 PS2 drivers, mouse, KVM: Arrrgghhh In-Reply-To: <20010411004306.Q389-100000@pirastro.oistrakh.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Apr 2001, Christian Chen wrote: > > On Wed, 11 Apr 2001, Gerd Knops wrote: > > > Since I upgraded to 4.3-RC, the middle mouse button and the wheel on > > my IntelliMouse (connected through a Belkin OmniView SE) quit working. > > The exact same combination worked fine with an early 4.2 stable. Dmesg > > shows > > > > psm0: failed to get data. > > psm0: irq 12 on atkbdc0 > > psm0: model Generic PS/2 mouse, device ID 0 > > > > The 'failed to get data' message seems to be new with 4.3-RC. > > For what it's worth, I'm also using a KVM, and I've gotten that message > in both 4.2-RELEASE and 4.3-RC. I'm still in the process of getting > X up and running in a satisfactory fashion, so I can't comment on whether > my Intellimouse works correctly despite that warning. > > Christian Chen > We've got several Belkin KVM's at my office, and it seems like scrollwheel functionality is a matter of luck. I once tried to find some configuration that would reliably work or reliably not work, and I failed. I just keep switching round mice until I find one that works. I do have a few non-FreeBSD suggestions, though. You have probably tried several of these already: 1. Reset the KVM 2. Change the KVM port that the computer is connected to. 3. Change mice (even if it's with another of the same model) 4. Plug the mouse directly into the computer, get the scrollwheel working, then start using the KVM again. You should be able to work OK with the keyboard and monitor plugged into the switch, and the mouse into the computer, at least temporarily. Hopefully you can benefit from my toil. :-) You would think that, since it worked before, it must be a problem with 4.3-RC. I'm afraid the problem might not be that straightforward. Just be glad you didn't get a Linksys KVM. I hear that scrollwheels almost never work on them. Good luck. Chris Wilmes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 2:21:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from spmler1.mail.eds.com (spmler1.mail.eds.com [194.128.225.190]) by hub.freebsd.org (Postfix) with ESMTP id AB39337B422 for ; Wed, 11 Apr 2001 02:21:13 -0700 (PDT) (envelope-from christer.moller@eds.com) Received: from nnse.eds.com ([192.168.1.1]) by spmler1.mail.eds.com (8.11.1/8.11.1) with ESMTP id f3B9LCg05201 for ; Wed, 11 Apr 2001 10:21:12 +0100 (BST) Received: from nnse.eds.com (localhost [127.0.0.1]) by nnse.eds.com (8.11.3/8.11.1) with ESMTP id f3B9LB623381 for ; Wed, 11 Apr 2001 10:21:11 +0100 (BST) Received: from pceweb.thn.se.eds.com (root@pceweb.thn.se.eds.com [139.96.4.10]) by nnse.eds.com (8.11.3/8.11.1) with ESMTP id f3B9LAv23353 for ; Wed, 11 Apr 2001 10:21:10 +0100 (BST) Received: from pce275 (pce275.thn.se.eds.com [139.96.16.22]) by pceweb.thn.se.eds.com (8.9.3/8.9.3) with SMTP id MAA29007 for ; Wed, 11 Apr 2001 12:23:04 +0200 From: "B. Christer Moller" To: Subject: CTM not updated since Mar 13 Date: Wed, 11 Apr 2001 11:21:00 +0200 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 CWS, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All, I know you are all very busy with the upcoming FreeBSD-4.3 RELEASE, but for us who uses CTM to update our sources there hasn't been any updates since 13 Mar. Is this meant to be like this or just a problem? Good luck with the 4.3-RELEASE, it looks great from my testing's at home! B. Christer Moller EDS Sweden AB Core Infrastructure EMEA Network Services, Nordic Tel: +46 520 787 33 Mobile: +46 705 325481 Fax: +46 520 787 04 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 2:42:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 69D3B37B422 for ; Wed, 11 Apr 2001 02:42:14 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id myvaaaaa for ; Wed, 11 Apr 2001 19:41:40 +1000 Message-ID: <3AD427DC.CFC52BAE@quake.com.au> Date: Wed, 11 Apr 2001 19:46:04 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-stable Subject: nVidia Cards /w FreeBSD (3D Acceleration) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hiyas, I have been looking into the situation with 3D Acceleration (eg. OpenGL) with FreeBSD, the current state of things is pretty poor compared with what linux now offers! We currently have Mesa and Glide 2 to support 3dfx cards (voodoo etc.) which are no longer being produced since 3dfx has been bought out by nVidia... There is Utah-GLX for the Rage cards... That leaves us with nothing for nVidia cards, the current market leader in the 3D Acceleration game!!! (nVidia are pretty much the only player right now) I know there was *some* work to port DRI to FreeBSD, but that seems to have been stopped or something? There are also the nVidia drivers for linux, which involve a kernel module and a good deal of it is binary only :( Then I look at www.lokigames.com and see all these great games that work under FreeBSD (with linux compat), and I think OMG! We NEED some support for these nVidia cards!!! Software rendering is not even an option for a lot of these games, and as I said 3dfx is no longer making cards, so if you want 3D Acceleration you goto nVidia... I am hoping to spark some interest in getting DRI ported to FreeBSD and even better, to get the nVidia linux drivers ported... I am going to mail nVidia linux team and see if I can get them to ether release all the source or to work with some FreeBSD developers to make a port, but we need some developers to take an interest in making it happen! (I unfortunately dont have the needed skills) Anyway, let me know of anything in this area, anyone get DRI to work? any thought on the issue etc? Lets take away the need for windows to play games!!! Viva la revaluation! ;) Thanks heaps guys! Kal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 2:53: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from clueless.redbus.aaisp.net (clueless.redbus.aaisp.net [213.161.73.195]) by hub.freebsd.org (Postfix) with SMTP id AB8BC37B422 for ; Wed, 11 Apr 2001 02:52:51 -0700 (PDT) (envelope-from jon@witchspace.com) Received: from zebedee.innovision-group.com (HELO:garfield.innovisiongroup.com) by clueless.redbus.aaisp.net for freebsd-stable@freebsd.org; Wed, 11 Apr 2001 10:52:46 +0100 Message-ID: <004c01c0c26e$21b6e7c0$650e850a@innovisiongroup.com> From: "Jonathan Belson" To: "Kal Torak" , "FreeBSD-stable" References: <3AD427DC.CFC52BAE@quake.com.au> Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) Date: Wed, 11 Apr 2001 10:59:40 +0100 Organization: Jon's Place 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.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hiya > I have been looking into the situation with 3D Acceleration (eg. OpenGL) > with FreeBSD, the current state of things is pretty poor compared with > what linux now offers! I agree - maybe it's not that important if you're running a web server, but accelerated OpenGL is pretty useful. > We currently have Mesa and Glide 2 to support 3dfx cards (voodoo etc.) > which are no longer being produced since 3dfx has been bought out by > nVidia... There is Utah-GLX for the Rage cards... That leaves us with > nothing for nVidia cards, the current market leader in the 3D Acceleration > game!!! (nVidia are pretty much the only player right now) The TNT2 cards are supported, at least under X3. The Radeon should have support too AIR. > I am hoping to spark some interest in getting DRI ported to FreeBSD and even > better, to get the nVidia linux drivers ported... I am going to mail nVidia > linux team and see if I can get them to ether release all the source or to nVidia won't release source 8^( -- C-YA Jon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 2:53:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from blake.arcadia.spb.ru (ns.arcadia.spb.ru [212.119.177.2]) by hub.freebsd.org (Postfix) with ESMTP id 610F337B422 for ; Wed, 11 Apr 2001 02:53:52 -0700 (PDT) (envelope-from Lev.Serebryakov@arcadia.spb.ru) Received: from anti.arcadia.spb.ru (anti.arcadia.spb.ru [212.119.177.3] (may be forged)) by blake.arcadia.spb.ru (8.9.2/8.8.6) with SMTP id OAA84131 for ; Wed, 11 Apr 2001 14:15:36 +0400 (MSD) Received: from LEV ([172.16.16.85]:3030) (HELO dhcp85.arcadia.intranet) by anti.arcadia.spb.ru ([212.119.177.3]:25) (F-Secure Anti-Virus for Internet Mail 5.0.53 Release) with SMTP; Wed, 11 Apr 2001 09:43:10 -0000 Date: Wed, 11 Apr 2001 13:52:11 +0400 From: Lev Serebryakov X-Mailer: The Bat! (v1.46d) Personal Reply-To: Lev Serebryakov Organization: Arcadia, Inc. X-Priority: 3 (Normal) Message-ID: <190174694797.20010411135211@arcadia.spb.ru> To: All Subject: gcc-2.95.3 and sjlj patches Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello All, Where could I get sjlj patches for gcc-2.95.3 to put in my port, based on gcc-2.95.3? I know, FreeBSD's cvs contains these patches, but I need patches to apply to unpacked gcc-{core|g++|objc}-2.95.3.tar.bz2 -- Best regards, Lev mailto:Lev.Serebryakov@arcadia.spb.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 6:14:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailout02.sul.t-online.com (mailout02.sul.t-online.com [194.25.134.17]) by hub.freebsd.org (Postfix) with ESMTP id 8C89137B422 for ; Wed, 11 Apr 2001 06:14:10 -0700 (PDT) (envelope-from sven.huster@mailsurf.com) Received: from fwd05.aul.t-online.de by mailout02.sul.t-online.com with smtp id 14nKRl-0005Hu-05; Wed, 11 Apr 2001 15:14:09 +0200 Received: from venus.mailsurf.com (320051988339-0001@[62.158.243.45]) by fmrl05.sul.t-online.com with esmtp id 14nKRZ-04MJ4iC; Wed, 11 Apr 2001 15:13:57 +0200 Message-Id: <5.0.2.1.0.20010411150941.0358c138@mx01.mailsurf.com> X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Wed, 11 Apr 2001 15:14:30 +0200 To: freebsd-stable@freebsd.org From: Sven Huster Subject: diskless operation Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Sender: 320051988339-0001@t-dialin.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, i check the rc.diskless* scripts and found that diskless2 uses chown/chgrp which are in /usr/bin also this system does not seem to support pxe boot operation. is there a fix out there? or someone who did this already? regards Sven Huster Senior IT Systems Administrator *BSD, Linux, Solaris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 6:43:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id 86CBF37B422 for ; Wed, 11 Apr 2001 06:43:14 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by probity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14nKto-0008Ee-00 for freebsd-stable@freebsd.org; Wed, 11 Apr 2001 14:43:08 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f3BDh7f67974 for freebsd-stable@freebsd.org; Wed, 11 Apr 2001 14:43:07 +0100 (BST) (envelope-from jcm) Date: Wed, 11 Apr 2001 14:43:07 +0100 From: j mckitrick To: freebsd-stable@freebsd.org Subject: bug in tar exclude file handling? Message-ID: <20010411144307.A67926@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Perhaps I have overlooked something, but in writing a recent backup script, I ran across what might be a bug. In the 'exclude' file you may use with tar, if there is ANY whitespace on the lines after the file names, tar will not match them. This caused me untold grief when 2 apparently identical exclude files produced entirely different results. One worked, the other didn't. At the least, maybe a note could be added to the man page. Or would this be considered a bug? Or is it a 'feature' designed to protect backward compatibility or interaction with other progs? Jonathon -- "One World, One Web, One Program." - Microsoft Promotional Ad. "Ein Volk, Ein Reich, Ein Fuhrer." - Adolf Hitler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 6:45:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id 1231B37B422 for ; Wed, 11 Apr 2001 06:45:43 -0700 (PDT) (envelope-from olli@lurza.secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.9.3/8.9.3) id PAA67262; Wed, 11 Apr 2001 15:45:41 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Date: Wed, 11 Apr 2001 15:45:41 +0200 (CEST) Message-Id: <200104111345.PAA67262@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG Reply-To: freebsd-stable@FreeBSD.ORG Subject: Re: Releases In-Reply-To: <200104102154.f3ALsce84245@ns1.unixathome.org> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.1-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Langille wrote: > On 10 Apr 2001, at 14:48, David O'Brien wrote: > > On Tue, Apr 10, 2001 at 06:32:15AM +1200, Dan Langille wrote: > > > AFAIK, the thread to date has been about whether or not [something like] > > > the label "-development" would cause less confusion than "-current". My > > > > And then we'd have people who CVSup'ed -development because they wanted to > > develop an application on FreeBSD. > > Thanks. I like that one. Then -unstable is a better name then - > development. But we've moved on from this I think. So far, I like -experimental best. However, I'd actually vote for keeping it -current. It's explained in the FAQ and in the Handbook, so if anyone needs a clue, we can drag his nose into that direction. It seems that there is some confusion about the names of branches, release tags and actual system names (those taken from newvers.sh). These three are all different things, and this should be very carefully explained in the documentation -- in particular for those who are not familiar with CVS. Oh by the way, there's an error in the FAQ. In section 7.37 it says: ``Once the release, 4.1-RELEASE in this example, has been made, the branch will be renamed to 4.1-STABLE'' That's nonsense, of course. There is no renaming of branches. The name of the branch is 4-stable (a.k.a. RELENG_4), both before and after the release. The release is just a point in time on the ongoing 4-stable branch. Maybe it would reduce confusion somewhat if people would just stop saying ``4.1-stable'' etc. Those simply do not exist. I would also vote for ``uname -r'' saying ``4-STABLE'' and appending the date (similar to the snapshot naming), like ``4-STABLE-20010509''. This is much more useful than ``4.3-STABLE'', IMO. Just my 2 Euro cents ... Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 6:47:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 137A637B422 for ; Wed, 11 Apr 2001 06:47:56 -0700 (PDT) (envelope-from danny@cs.huji.ac.il) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.22 #1) id 14nKyQ-0005dL-00; Wed, 11 Apr 2001 16:47:54 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 14nKyP-00029Y-00; Wed, 11 Apr 2001 16:47:53 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Sven Huster Cc: freebsd-stable@freebsd.org Subject: Re: diskless operation In-reply-to: Your message of Wed, 11 Apr 2001 15:14:30 +0200 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Apr 2001 16:47:53 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <5.0.2.1.0.20010411150941.0358c138@mx01.mailsurf.com>you write: }Hi there, } }i check the rc.diskless* scripts and found that diskless2 }uses chown/chgrp which are in /usr/bin so you better have /usr/bin :-) some of us have changed this. }also this system does not seem to support pxe boot operation. }is there a fix out there? or someone who did this already? the pxe stuff is 'controlled' via dhcp, it handles the boot/loader stuff, rc.diskless? is executed after by the kernel, after it got loaded. danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 7:15:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id C975837B422 for ; Wed, 11 Apr 2001 07:15:44 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by probity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14nLPL-00092n-00 for freebsd-stable@freebsd.org; Wed, 11 Apr 2001 15:15:43 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f3BEFh668489 for freebsd-stable@freebsd.org; Wed, 11 Apr 2001 15:15:43 +0100 (BST) (envelope-from jcm) Date: Wed, 11 Apr 2001 15:15:43 +0100 From: j mckitrick To: freebsd-stable@freebsd.org Subject: new kernel book this summer? Message-ID: <20010411151543.A68310@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I posted a week or so ago on -hackers asking about a rumor that a revised 'design and implementation of freebsd os' would be out this summer. No one replied. Since then, a number of people have emailed me privately expressing interest in this. So, does anyone know anything about this? Jonathon -- "One World, One Web, One Program." - Microsoft Promotional Ad. "Ein Volk, Ein Reich, Ein Fuhrer." - Adolf Hitler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 7:33:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 6A02837B424 for ; Wed, 11 Apr 2001 07:33:19 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id nzvaaaaa for ; Thu, 12 Apr 2001 00:32:48 +1000 Message-ID: <3AD46C19.FC1AFB93@quake.com.au> Date: Thu, 12 Apr 2001 00:37:13 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jonathan Belson Cc: FreeBSD-stable Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: <3AD427DC.CFC52BAE@quake.com.au> <004c01c0c26e$21b6e7c0$650e850a@innovisiongroup.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have been looking into the situation with 3D Acceleration (eg. OpenGL) > > with FreeBSD, the current state of things is pretty poor compared with > > what linux now offers! > > I agree - maybe it's not that important if you're running a web server, but > accelerated OpenGL is pretty useful. > > I am going to mail nVidia linux team and see if I can get them to ether > release all the source or to make a port to FreeBSD... > > nVidia won't release source 8^( Yeah I wouldnt expect them to really, one can always dream :) So in that case we need to mail nVidia and request that they make a port for there drivers to FreeBSD! If enough of us mail them about it, surly they will take notice? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 7:44:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailout00.sul.t-online.com (mailout00.sul.t-online.com [194.25.134.16]) by hub.freebsd.org (Postfix) with ESMTP id 0C7FF37B423 for ; Wed, 11 Apr 2001 07:44:16 -0700 (PDT) (envelope-from sven.huster@mailsurf.com) Received: from fwd05.aul.t-online.de by mailout00.sul.t-online.com with smtp id 14nLqt-0007oQ-01; Wed, 11 Apr 2001 16:44:11 +0200 Received: from venus.mailsurf.com (320051988339-0001@[62.158.243.45]) by fmrl05.sul.t-online.com with esmtp id 14nLqp-07rolEC; Wed, 11 Apr 2001 16:44:07 +0200 Message-Id: <5.0.2.1.0.20010411164359.00a63880@mx01.mailsurf.com> X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Wed, 11 Apr 2001 16:44:40 +0200 To: Danny Braniss From: Sven Huster Subject: Re: diskless operation Cc: freebsd-stable@freebsd.org In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Sender: 320051988339-0001@t-dialin.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 15:47 11.04.2001, Danny Braniss wrote: >*This message was transferred with a trial version of CommuniGate(tm) Pro* >In message <5.0.2.1.0.20010411150941.0358c138@mx01.mailsurf.com>you write: >}Hi there, >} >}i check the rc.diskless* scripts and found that diskless2 >}uses chown/chgrp which are in /usr/bin >so you better have /usr/bin :-) >some of us have changed this. > >}also this system does not seem to support pxe boot operation. >}is there a fix out there? or someone who did this already? > >the pxe stuff is 'controlled' via dhcp, it handles the boot/loader stuff, >rc.diskless? is executed after by the kernel, after it got loaded. > >danny > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message But my interface has no ip after boot! So dhclient needs to be invoked. regards Sven Huster Senior IT Systems Administrator *BSD, Linux, Solaris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 7:48:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mobile.hub.org (mobile.acadiau.ca [131.162.137.70]) by hub.freebsd.org (Postfix) with ESMTP id 389BC37B422 for ; Wed, 11 Apr 2001 07:48:30 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by mobile.hub.org (8.11.1/8.11.1) with ESMTP id f3BEm5r68019; Wed, 11 Apr 2001 11:48:06 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: mobile.hub.org: scrappy owned process doing -bs Date: Wed, 11 Apr 2001 11:48:05 -0300 (ADT) From: The Hermit Hacker To: Kal Torak Cc: Jonathan Belson , FreeBSD-stable Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) In-Reply-To: <3AD46C19.FC1AFB93@quake.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG NVidia cards are all I buy now, have 3 or 4 right now ... don't the cards have some sort of serial number? is there any way of using that to provide a pseudo-petition list ... maybe our new benefactors could talk to NVidia themselves, get nVidia to setup a nonline 'registration form' that we could all connect to and submit our serial numbers, to give them a feel for number of FreeBSD'rs out here? On Thu, 12 Apr 2001, Kal Torak wrote: > > > I have been looking into the situation with 3D Acceleration (eg. OpenGL) > > > with FreeBSD, the current state of things is pretty poor compared with > > > what linux now offers! > > > > I agree - maybe it's not that important if you're running a web server, but > > accelerated OpenGL is pretty useful. > > > > I am going to mail nVidia linux team and see if I can get them to ether > > release all the source or to make a port to FreeBSD... > > > > nVidia won't release source 8^( > > Yeah I wouldnt expect them to really, one can always dream :) > > So in that case we need to mail nVidia and request that they make > a port for there drivers to FreeBSD! > If enough of us mail them about it, surly they will take notice? > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > 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-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 8: 2:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id BB2BF37B422 for ; Wed, 11 Apr 2001 08:02:48 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by probity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14nM8t-0009qh-00; Wed, 11 Apr 2001 16:02:47 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f3BF2lt69280; Wed, 11 Apr 2001 16:02:47 +0100 (BST) (envelope-from jcm) Date: Wed, 11 Apr 2001 16:02:47 +0100 From: j mckitrick To: Cy Schubert - ITSD Open Systems Group Cc: freebsd-stable@freebsd.org Subject: Re: new kernel book this summer? Message-ID: <20010411160247.A69250@dogma.freebsd-uk.eu.org> References: <20010411151543.A68310@dogma.freebsd-uk.eu.org> <200104111456.f3BEuSi02953@cwsys.cwsent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200104111456.f3BEuSi02953@cwsys.cwsent.com>; from Cy.Schubert@uumail.gov.bc.ca on Wed, Apr 11, 2001 at 07:55:38AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | that a new book, a follow on to The Design and Implementation of the | 4.4BSD Operating System, entitled The Design and Implementation of the | FreeBSD Operating System would be published after the next release of | FreeBSD. Thanks, Cy, just what I was hoping for! Jonathon -- "One World, One Web, One Program." - Microsoft Promotional Ad. "Ein Volk, Ein Reich, Ein Fuhrer." - Adolf Hitler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 8:47:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 7E86B37B424 for ; Wed, 11 Apr 2001 08:47:21 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id IAA39265; Wed, 11 Apr 2001 08:45:57 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200104111545.IAA39265@gndrsh.dnsmgr.net> Subject: Re: bug in tar exclude file handling? In-Reply-To: <20010411144307.A67926@dogma.freebsd-uk.eu.org> from j mckitrick at "Apr 11, 2001 02:43:07 pm" To: jcm@FreeBSD-uk.eu.org (j mckitrick) Date: Wed, 11 Apr 2001 08:45:57 -0700 (PDT) Cc: freebsd-stable@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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a feature, and a needed one. Understand that a space is a legal filename character in a file under Unix: br1.chatusa.com:root{119}# touch "X " br1.chatusa.com:root{120}# touch "X " br1.chatusa.com:root{122}# ls -lag X* -rw-r--r-- 1 root wheel 0 Apr 11 15:42 X -rw-r--r-- 1 root wheel 0 Apr 11 15:43 X If tar was to strip off spaces, even trailing or leading spaces from an exclude file list it would not allow full functionality and then we would have a bug. > > Perhaps I have overlooked something, but in writing a recent backup script, > I ran across what might be a bug. In the 'exclude' file you may use with > tar, if there is ANY whitespace on the lines after the file names, tar will > not match them. This caused me untold grief when 2 apparently identical > exclude files produced entirely different results. One worked, the other > didn't. At the least, maybe a note could be added to the man page. Or > would this be considered a bug? Or is it a 'feature' designed to protect > backward compatibility or interaction with other progs? > > Jonathon > -- > "One World, One Web, One Program." - Microsoft Promotional Ad. > "Ein Volk, Ein Reich, Ein Fuhrer." - Adolf Hitler > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 8:55:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id 5384937B424 for ; Wed, 11 Apr 2001 08:55:21 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by probity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14nMxk-000AjW-00; Wed, 11 Apr 2001 16:55:20 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f3BFtJL70448; Wed, 11 Apr 2001 16:55:19 +0100 (BST) (envelope-from jcm) Date: Wed, 11 Apr 2001 16:55:19 +0100 From: j mckitrick To: "Rodney W. Grimes" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: bug in tar exclude file handling? Message-ID: <20010411165519.A70415@dogma.freebsd-uk.eu.org> References: <20010411144307.A67926@dogma.freebsd-uk.eu.org> <200104111545.IAA39265@gndrsh.dnsmgr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200104111545.IAA39265@gndrsh.dnsmgr.net>; from freebsd@gndrsh.dnsmgr.net on Wed, Apr 11, 2001 at 08:45:57AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | If tar was to strip off spaces, even trailing or leading spaces from | an exclude file list it would not allow full functionality and then | we would have a bug. Understood. Thanks! Jonathon -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 9:15:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ureach.com (mail.ureach.com [63.150.151.36]) by hub.freebsd.org (Postfix) with ESMTP id 945CC37B63E for ; Wed, 11 Apr 2001 09:15:26 -0700 (PDT) (envelope-from pechter@ureach.com) Received: from www20.ureach.com (IDENT:root@www20.ureach.com [172.16.2.48]) by ureach.com (8.9.1/8.8.5) with ESMTP id MAA30071; Wed, 11 Apr 2001 12:15:23 -0400 Received: (from nobody@localhost) by www20.ureach.com (8.9.3/8.9.1) id MAA16812; Wed, 11 Apr 2001 12:15:25 -0400 Date: Wed, 11 Apr 2001 12:15:25 -0400 Message-Id: <200104111615.MAA16812@www20.ureach.com> To: "SpectreGadget" From: Bill Pechter Reply-To: Subject: Re: Re: SSH -- "No RSA support in lib ssl and libcrypto" on 4.3-RC upgraded from 4.2-STABLE Cc: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-vsuite-type: e Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ---- On Wed, 11 Apr 2001, SpectreGadget (gadget@greenhauz.com) wrote: > Unless somebody already pointed it out... It's a permission on > something. probably a config file. Did you run mergemaster with a > Nazi umask ? :-) (077?) Sorry i can't tell you for sure, the other > day i ran into this on a friends box and re-ran mergemaster watching > the umask carefully and it cleared up. > > sorry, not alot of info but might get you in the right direction. > > later > gadget > > Well, the ssh-keygen now works after a MAKEDEV std... bet the permissions on /dev/random or /dev/null were screwed. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 9:18:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 18EE337B422 for ; Wed, 11 Apr 2001 09:18:27 -0700 (PDT) (envelope-from danny@cs.huji.ac.il) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.22 #1) id 14nNK1-0000i2-00; Wed, 11 Apr 2001 19:18:21 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 14nNK0-0002G5-00; Wed, 11 Apr 2001 19:18:20 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Sven Huster Subject: Re: diskless operation Cc: freebsd-stable@freebsd.org In-reply-to: Your message of Wed, 11 Apr 2001 16:44:40 +0200 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Apr 2001 19:18:20 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <5.0.2.1.0.20010411164359.00a63880@mx01.mailsurf.com>you write: }But my interface has no ip after boot! }So dhclient needs to be invoked. if you are booting via bootp/pxe then the loader will have placed in the environment some info. see kenv(1), or before loading, type show. look in /etc/rc.diskless1, it will try and figure out the interface and set some variables so that rc.network can do the rest. do you get a message, like Interface exp0 IP-Address 10.0.0.1 Broadcast ... ? as far as i know, you dont't need dhclient if you are booting diskless, unless there is other info you need, such as gateway, dns server, etc. danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 9:19:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gekko.i-clue.de (server.ms-agentur.de [62.153.134.194]) by hub.freebsd.org (Postfix) with ESMTP id F31EF37B422 for ; Wed, 11 Apr 2001 09:19:19 -0700 (PDT) (envelope-from so@server.i-clue.de) Received: from i-clue.de (automatix.i-clue.de [192.168.0.112]) by gekko.i-clue.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id TAA10371; Wed, 11 Apr 2001 19:25:54 +0200 Message-ID: <3AD48414.CE5E4386@i-clue.de> Date: Wed, 11 Apr 2001 18:19:32 +0200 From: Christoph Sold Reply-To: so@server.i-clue.de X-Mailer: Mozilla 4.75 [de] (WinNT; U) X-Accept-Language: de MIME-Version: 1.0 To: Aleksey Ovcharenko Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Where can I get FreeBSD-STABLE iso images? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [It would be nice to include at least a copy of your subject in the message body. Helps stupid users like me who have to re-type your question.] Aleksey Ovcharenko schrieb: > > Where can I get FreeBSD-STABLE iso images? You can't. You may get FreeBSD-4.3RC ISO images until FreeBSD4.3-Release is out. ISO images are usually built for Release only. Stable is a dynamic target, thus CD-ROMs (even in image form) would be outdated pretty soon. Read the FreeBSD Handbook, Chapter "The Cutting Edge" (http://www.freebsd.org/handbook/cutting-edge.html), to learn how to stay stable. HTH -Christoph Sold To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 9:29:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from grizzly.carrier.kiev.ua (grizzly.carrier.kiev.ua [193.193.193.138]) by hub.freebsd.org (Postfix) with ESMTP id 5FC5037B422 for ; Wed, 11 Apr 2001 09:29:01 -0700 (PDT) (envelope-from netch@grizzly.carrier.kiev.ua) Received: (from netch@localhost) by grizzly.carrier.kiev.ua (8.11.3/8.11.0) id f3BGSt200720 for freebsd-stable@freebsd.org; Wed, 11 Apr 2001 19:28:55 +0300 (EEST) (envelope-from netch) Date: Wed, 11 Apr 2001 19:28:55 +0300 From: Valentin Nechayev To: freebsd-stable@freebsd.org Subject: fresh 4.3-RC: "microuptime went backwards", console lockup Message-ID: <20010411192854.A570@netch.kiev.ua> Reply-To: netch@netch.kiev.ua Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-42: On Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Today, 4.3-RC (RELENG_4, date=2001.04.11.00.00.00) was built and, when new system started: 1) during boot and even before /sbin/init started, "microuptime went backwards" occured too many times. 2) after startx, syscons switched to ttyv0 and stayed here; after mutual swithing to ttyvb, console locked up totally. No problems with previous system (RELENG_4, date=2001.03.05.00.00.00) were seen. Xwindow is 3.3.6 from latest port. Messages, messages diff and kernel config attached. What another information should I provide? /var/log/messages during bad kernel: ==={{{ Apr 11 18:41:38 grizzly /kernel: Copyright (c) 1992-2001 The FreeBSD Project. Apr 11 18:41:38 grizzly /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Apr 11 18:41:38 grizzly /kernel: The Regents of the University of California. All rights reserved. Apr 11 18:41:38 grizzly /kernel: FreeBSD 4.3-RC #0: Wed Apr 11 18:29:42 EEST 2001 Apr 11 18:41:38 grizzly /kernel: root@grizzly.carrier.kiev.ua:/var/obj/var/src/sys/compile/griz Apr 11 18:41:38 grizzly /kernel: Timecounter "i8254" frequency 1193182 Hz Apr 11 18:41:38 grizzly /kernel: CPU: Pentium II/Pentium II Xeon/Celeron (300.68-MHz 686-class CPU) Apr 11 18:41:38 grizzly /kernel: Origin = "GenuineIntel" Id = 0x660 Stepping = 0 Apr 11 18:41:38 grizzly /kernel: Features=0x183f9ff Apr 11 18:41:38 grizzly /kernel: real memory = 134217728 (131072K bytes) Apr 11 18:41:38 grizzly /kernel: avail memory = 127016960 (124040K bytes) Apr 11 18:41:38 grizzly /kernel: Preloaded elf kernel "kernel" at 0xc0357000. Apr 11 18:41:38 grizzly /kernel: VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc02f81a2 (1000022) Apr 11 18:41:38 grizzly /kernel: VESA: ATI MACH64 Apr 11 18:41:38 grizzly /kernel: Pentium Pro MTRR support enabled Apr 11 18:41:38 grizzly /kernel: apm0: on motherboard Apr 11 18:41:38 grizzly /kernel: apm: found APM BIOS v1.2, connected at v1.2 Apr 11 18:41:38 grizzly /kernel: npx0: on motherboard Apr 11 18:41:38 grizzly /kernel: npx0: INT 16 interface Apr 11 18:41:38 grizzly /kernel: pcib0: on motherboard Apr 11 18:41:38 grizzly /kernel: pci0: on pcib0 Apr 11 18:41:38 grizzly /kernel: pcib1: at device 1.0 on pci0 Apr 11 18:41:38 grizzly /kernel: pci1: on pcib1 Apr 11 18:41:38 grizzly /kernel: pci1: at 0.0 irq 15 Apr 11 18:41:38 grizzly /kernel: isab0: at device 7.0 on pci0 Apr 11 18:41:38 grizzly /kernel: isa0: on isab0 Apr 11 18:41:38 grizzly /kernel: pci0: at 7.1 Apr 11 18:41:38 grizzly /kernel: pci0: at 7.2 Apr 11 18:41:38 grizzly /kernel: chip1: port 0x5000-0x500f at device 7.3 on pci0 Apr 11 18:41:38 grizzly /kernel: fxp0: port 0xe400-0xe41f mem 0xea000000-0xea0fffff,0xea101000-0xea101fff irq 11 at device 18.0 on pci0 Apr 11 18:41:38 grizzly /kernel: fxp0: Ethernet address 00:90:27:2d:41:d0 Apr 11 18:41:38 grizzly /kernel: ahc0: port 0xe800-0xe8ff mem 0xea100000-0xea100fff irq 10 at device 19.0 on pci0 Apr 11 18:41:38 grizzly /kernel: aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs Apr 11 18:41:38 grizzly /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Apr 11 18:41:38 grizzly /kernel: fdc0: FIFO enabled, 8 bytes threshold Apr 11 18:41:38 grizzly /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Apr 11 18:41:38 grizzly /kernel: atkbdc0: at port 0x60,0x64 on isa0 Apr 11 18:41:38 grizzly /kernel: atkbd0: flags 0x1 irq 1 on atkbdc0 Apr 11 18:41:38 grizzly /kernel: kbd0 at atkbd0 Apr 11 18:41:38 grizzly /kernel: psm0: irq 12 on atkbdc0 Apr 11 18:41:38 grizzly /kernel: psm0: model Generic PS/2 mouse, device ID 0 Apr 11 18:41:38 grizzly /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Apr 11 18:41:38 grizzly /kernel: sc0: at flags 0x100 on isa0 Apr 11 18:41:38 grizzly /kernel: sc0: VGA <16 virtual consoles, flags=0x300> Apr 11 18:41:38 grizzly /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Apr 11 18:41:38 grizzly /kernel: sio0: type 16550A Apr 11 18:41:38 grizzly /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Apr 11 18:41:38 grizzly /kernel: sio1: type 16550A Apr 11 18:41:38 grizzly /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 Apr 11 18:41:38 grizzly /kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Apr 11 18:41:38 grizzly /kernel: ppc0: FIFO with 16/16/16 bytes threshold Apr 11 18:41:38 grizzly /kernel: plip0: on ppbus0 Apr 11 18:41:38 grizzly /kernel: lpt0: on ppbus0 Apr 11 18:41:38 grizzly /kernel: lpt0: Interrupt-driven port Apr 11 18:41:38 grizzly /kernel: ppi0: on ppbus0 Apr 11 18:41:38 grizzly /kernel: sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,3 on isa0 Apr 11 18:41:38 grizzly /kernel: pcm0: on sbc0 Apr 11 18:41:38 grizzly /kernel: IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to accept, unlimited logging Apr 11 18:41:38 grizzly /kernel: Waiting 3 seconds for SCSI devices to settle Apr 11 18:41:38 grizzly /kernel: Mounting root from ufs:/dev/da0s1a Apr 11 18:41:38 grizzly /kernel: da1 at ahc0 bus 0 target 2 lun 0 Apr 11 18:41:38 grizzly /kernel: da1: Fixed Direct Access SCSI-2 device Apr 11 18:41:38 grizzly /kernel: da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) Apr 11 18:41:38 grizzly /kernel: da1: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) Apr 11 18:41:38 grizzly /kernel: da0 at ahc0 bus 0 target 0 lun 0 Apr 11 18:41:38 grizzly /kernel: da0: Fixed Direct Access SCSI-2 device Apr 11 18:41:38 grizzly /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled Apr 11 18:41:38 grizzly /kernel: da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843816 -> 7.734809) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843816 -> 7.737171) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843573 -> 7.734732) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843573 -> 7.735340) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843573 -> 7.736912) Apr 11 18:41:38 grizzly /kernel: cd0 at ahc0 bus 0 target 1 lun 0 Apr 11 18:41:38 grizzly /kernel: cd0: Removable CD-ROM SCSI-2 device Apr 11 18:41:38 grizzly /kernel: cd0: 10.000MB/s transfers (10.000MHz, offset 8) Apr 11 18:41:38 grizzly /kernel: cd0: cd present [327338 x 2048 byte records] Apr 11 18:41:38 grizzly named[177]: starting (/etc/namedb/named.conf). named 8.2.3-REL Wed Apr 11 16:59:40 EEST 2001 root@grizzly.carrier.kiev.ua:/var/obj/var/src/usr.sbin/named Apr 11 18:41:38 grizzly named[177]: limit files set to fdlimit (1024) Apr 11 18:41:38 grizzly named[178]: Ready to answer queries. Apr 11 18:41:38 grizzly ntpd[180]: ntpd 4.0.99b Wed Apr 11 16:58:45 EEST 2001 (1) Apr 11 18:41:38 grizzly ntpd[180]: using kernel phase-lock loop 2040 Apr 11 18:41:38 grizzly ntpd[180]: getnetnum: "news.demos.su" invalid host number, line ignored Apr 11 18:41:38 grizzly ntpd[180]: getnetnum: "news1.demos.su" invalid host number, line ignored Apr 11 18:41:38 grizzly ntpd[180]: getnetnum: "news.gamma.ru" invalid host number, line ignored Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.834984 -> 7.737884) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842559 -> 7.735504) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843816 -> 7.738378) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839712 -> 7.734986) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839748 -> 7.743734) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.736175) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.739450) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.750258) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.751613) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.764301) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.764883) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.775410) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.776000) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.780731) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.787880) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.788925) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.791228) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.792100) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.742846) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.745269) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.746962) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.748818) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.749914) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.751635) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.753202) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.756961) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.739800) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.740682) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.751453) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.752134) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.753513) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.754646) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.755632) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.757180) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.761039) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.765178) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.766163) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843178 -> 7.734621) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843178 -> 7.735361) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843178 -> 7.737016) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843178 -> 7.737564) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.830187 -> 7.734668) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.830187 -> 7.749899) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.838573 -> 7.734923) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843469 -> 7.734611) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.838522 -> 7.738094) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.838522 -> 7.745038) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.844055 -> 7.734420) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.735466) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.740883) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.755061) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.766780) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.783736) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.795306) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.810152) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.826392) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843630 -> 7.735223) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.831660 -> 7.737727) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.831660 -> 7.759594) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842772 -> 7.734324) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.805040 -> 7.735190) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.805040 -> 7.735336) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.805040 -> 7.771539) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843616 -> 7.734416) Apr 11 18:41:38 grizzly login: ROOT LOGIN (root) ON ttyv1 Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.774619 -> 7.740860) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839139 -> 7.735976) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839139 -> 7.736433) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839139 -> 7.736580) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839139 -> 7.736791) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839139 -> 7.736964) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.820332 -> 7.744583) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.820332 -> 7.744793) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.820332 -> 7.750961) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842030 -> 7.734805) Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.831764 -> 7.737653) ===}}} Different lines between bad kernel messages('-') and good old kernel messages('+'): -avail memory = 127016960 (124040K bytes) +avail memory = 127021056 (124044K bytes) -VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc02f81a2 (1000022) +VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc02f7362 (1000022) Kernel config (did not changed): ==={{{ machine i386 #cpu I386_CPU #cpu I486_CPU #cpu I586_CPU cpu I686_CPU ident griz maxusers 64 options MSGBUF_SIZE=81920 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about options IPFIREWALL_DEFAULT_TO_ACCEPT options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=3000 #Delay (in ms) before probing SCSI options INCLUDE_CONFIG_FILE options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev options VESA options EXT2FS options USER_LDT device isa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 # SCSI peripherals device ahc # AHA2940 and onboard AIC7xxx devices device scbus # SCSI bus (required) device da # Direct Access (disks) device cd # CD device pass # Passthrough device (direct SCSI access) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0 at atkbdc? irq 12 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 options SC_HISTORY_SIZE=1200 options SC_MOUSE_CHAR=0x03 # 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? flags 0x20 # Advanced Power Management # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # PCI Ethernet NICs. device fxp # Intel EtherExpress PRO/100B (82557, 82558) ## sound device pcm device sbc # 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 64 # Pseudo-ttys (telnet etc) pseudo-device vn 3 pseudo-device bpf 3 pseudo-device speaker options NETGRAPH #netgraph(4) system options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN options TCP_RESTRICT_RST #restrict emission of TCP RST options ICMP_BANDLIM options QUOTA #enable disk quotas options NTIMECOUNTER=20 options VESA ===}}} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 9:30:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id C6E0737B423 for ; Wed, 11 Apr 2001 09:30:16 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id fawaaaaa for ; Thu, 12 Apr 2001 02:29:45 +1000 Message-ID: <3AD48782.2CEAE87B@quake.com.au> Date: Thu, 12 Apr 2001 02:34:10 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: The Hermit Hacker Cc: Jonathan Belson , FreeBSD-stable Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Hermit Hacker wrote: > > NVidia cards are all I buy now, have 3 or 4 right now ... don't the cards > have some sort of serial number? is there any way of using that to > provide a pseudo-petition list ... maybe our new benefactors could talk to > NVidia themselves, get nVidia to setup a nonline 'registration form' that > we could all connect to and submit our serial numbers, to give them a feel > for number of FreeBSD'rs out here? nVidia cards are really the ONLY choice to buy now... Not that Im complaining, they are good cards, we just need some support for the more recent ones! Since I cant find anything for the GeForce line... Let alone GeForce2, and the GeForce3 series (are they going to call it that?) will be on sale soon... If there is enough interest from us they should be willing to make ports to FreeBSD.. I mean they support BeOS, how many people even use that, let alone have nVidia cards? Surly we could match them in numbers! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 9:37:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from farc.ikami.com (farc.ikami.com [204.29.203.67]) by hub.freebsd.org (Postfix) with ESMTP id 54A3937B422 for ; Wed, 11 Apr 2001 09:37:36 -0700 (PDT) (envelope-from nrh@ikami.com) Received: by farc.ikami.com (Postfix, from userid 1000) id A3D6A300E5; Wed, 11 Apr 2001 11:37:35 -0500 (CDT) Date: Wed, 11 Apr 2001 11:37:35 -0500 From: nicholas harteau To: Valentin Nechayev Cc: freebsd-stable@freebsd.org Subject: Re: fresh 4.3-RC: "microuptime went backwards", console lockup Message-ID: <20010411113735.J23469@voyager.net> References: <20010411192854.A570@netch.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010411192854.A570@netch.kiev.ua>; from netch@netch.kiev.ua on Wed, Apr 11, 2001 at 07:28:55PM +0300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This happened to me; a couple things you might try: kern.timecounter.method=1 or, possibly adding: device apm0 at nexus? disable flags 0x20 to your kernel. Valentin Nechayev wrote: > Today, 4.3-RC (RELENG_4, date=2001.04.11.00.00.00) was built and, when > new system started: > 1) during boot and even before /sbin/init started, "microuptime went backwards" > occured too many times. > 2) after startx, syscons switched to ttyv0 and stayed here; after > mutual swithing to ttyvb, console locked up totally. > No problems with previous system (RELENG_4, date=2001.03.05.00.00.00) > were seen. Xwindow is 3.3.6 from latest port. > > Messages, messages diff and kernel config attached. What another information > should I provide? > > /var/log/messages during bad kernel: > > ==={{{ > Apr 11 18:41:38 grizzly /kernel: Copyright (c) 1992-2001 The FreeBSD Project. > Apr 11 18:41:38 grizzly /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > Apr 11 18:41:38 grizzly /kernel: The Regents of the University of California. All rights reserved. > Apr 11 18:41:38 grizzly /kernel: FreeBSD 4.3-RC #0: Wed Apr 11 18:29:42 EEST 2001 > Apr 11 18:41:38 grizzly /kernel: root@grizzly.carrier.kiev.ua:/var/obj/var/src/sys/compile/griz > Apr 11 18:41:38 grizzly /kernel: Timecounter "i8254" frequency 1193182 Hz > Apr 11 18:41:38 grizzly /kernel: CPU: Pentium II/Pentium II Xeon/Celeron (300.68-MHz 686-class CPU) > Apr 11 18:41:38 grizzly /kernel: Origin = "GenuineIntel" Id = 0x660 Stepping = 0 > Apr 11 18:41:38 grizzly /kernel: Features=0x183f9ff > Apr 11 18:41:38 grizzly /kernel: real memory = 134217728 (131072K bytes) > Apr 11 18:41:38 grizzly /kernel: avail memory = 127016960 (124040K bytes) > Apr 11 18:41:38 grizzly /kernel: Preloaded elf kernel "kernel" at 0xc0357000. > Apr 11 18:41:38 grizzly /kernel: VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc02f81a2 (1000022) > Apr 11 18:41:38 grizzly /kernel: VESA: ATI MACH64 > Apr 11 18:41:38 grizzly /kernel: Pentium Pro MTRR support enabled > Apr 11 18:41:38 grizzly /kernel: apm0: on motherboard > Apr 11 18:41:38 grizzly /kernel: apm: found APM BIOS v1.2, connected at v1.2 > Apr 11 18:41:38 grizzly /kernel: npx0: on motherboard > Apr 11 18:41:38 grizzly /kernel: npx0: INT 16 interface > Apr 11 18:41:38 grizzly /kernel: pcib0: on motherboard > Apr 11 18:41:38 grizzly /kernel: pci0: on pcib0 > Apr 11 18:41:38 grizzly /kernel: pcib1: at device 1.0 on pci0 > Apr 11 18:41:38 grizzly /kernel: pci1: on pcib1 > Apr 11 18:41:38 grizzly /kernel: pci1: at 0.0 irq 15 > Apr 11 18:41:38 grizzly /kernel: isab0: at device 7.0 on pci0 > Apr 11 18:41:38 grizzly /kernel: isa0: on isab0 > Apr 11 18:41:38 grizzly /kernel: pci0: at 7.1 > Apr 11 18:41:38 grizzly /kernel: pci0: at 7.2 > Apr 11 18:41:38 grizzly /kernel: chip1: port 0x5000-0x500f at device 7.3 on pci0 > Apr 11 18:41:38 grizzly /kernel: fxp0: port 0xe400-0xe41f mem 0xea000000-0xea0fffff,0xea101000-0xea101fff irq 11 at device 18.0 on pci0 > Apr 11 18:41:38 grizzly /kernel: fxp0: Ethernet address 00:90:27:2d:41:d0 > Apr 11 18:41:38 grizzly /kernel: ahc0: port 0xe800-0xe8ff mem 0xea100000-0xea100fff irq 10 at device 19.0 on pci0 > Apr 11 18:41:38 grizzly /kernel: aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs > Apr 11 18:41:38 grizzly /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > Apr 11 18:41:38 grizzly /kernel: fdc0: FIFO enabled, 8 bytes threshold > Apr 11 18:41:38 grizzly /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > Apr 11 18:41:38 grizzly /kernel: atkbdc0: at port 0x60,0x64 on isa0 > Apr 11 18:41:38 grizzly /kernel: atkbd0: flags 0x1 irq 1 on atkbdc0 > Apr 11 18:41:38 grizzly /kernel: kbd0 at atkbd0 > Apr 11 18:41:38 grizzly /kernel: psm0: irq 12 on atkbdc0 > Apr 11 18:41:38 grizzly /kernel: psm0: model Generic PS/2 mouse, device ID 0 > Apr 11 18:41:38 grizzly /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Apr 11 18:41:38 grizzly /kernel: sc0: at flags 0x100 on isa0 > Apr 11 18:41:38 grizzly /kernel: sc0: VGA <16 virtual consoles, flags=0x300> > Apr 11 18:41:38 grizzly /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > Apr 11 18:41:38 grizzly /kernel: sio0: type 16550A > Apr 11 18:41:38 grizzly /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 > Apr 11 18:41:38 grizzly /kernel: sio1: type 16550A > Apr 11 18:41:38 grizzly /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 > Apr 11 18:41:38 grizzly /kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > Apr 11 18:41:38 grizzly /kernel: ppc0: FIFO with 16/16/16 bytes threshold > Apr 11 18:41:38 grizzly /kernel: plip0: on ppbus0 > Apr 11 18:41:38 grizzly /kernel: lpt0: on ppbus0 > Apr 11 18:41:38 grizzly /kernel: lpt0: Interrupt-driven port > Apr 11 18:41:38 grizzly /kernel: ppi0: on ppbus0 > Apr 11 18:41:38 grizzly /kernel: sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,3 on isa0 > Apr 11 18:41:38 grizzly /kernel: pcm0: on sbc0 > Apr 11 18:41:38 grizzly /kernel: IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to accept, unlimited logging > Apr 11 18:41:38 grizzly /kernel: Waiting 3 seconds for SCSI devices to settle > Apr 11 18:41:38 grizzly /kernel: Mounting root from ufs:/dev/da0s1a > Apr 11 18:41:38 grizzly /kernel: da1 at ahc0 bus 0 target 2 lun 0 > Apr 11 18:41:38 grizzly /kernel: da1: Fixed Direct Access SCSI-2 device > Apr 11 18:41:38 grizzly /kernel: da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) > Apr 11 18:41:38 grizzly /kernel: da1: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) > Apr 11 18:41:38 grizzly /kernel: da0 at ahc0 bus 0 target 0 lun 0 > Apr 11 18:41:38 grizzly /kernel: da0: Fixed Direct Access SCSI-2 device > Apr 11 18:41:38 grizzly /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled > Apr 11 18:41:38 grizzly /kernel: da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843816 -> 7.734809) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843816 -> 7.737171) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843573 -> 7.734732) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843573 -> 7.735340) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843573 -> 7.736912) > Apr 11 18:41:38 grizzly /kernel: cd0 at ahc0 bus 0 target 1 lun 0 > Apr 11 18:41:38 grizzly /kernel: cd0: Removable CD-ROM SCSI-2 device > Apr 11 18:41:38 grizzly /kernel: cd0: 10.000MB/s transfers (10.000MHz, offset 8) > Apr 11 18:41:38 grizzly /kernel: cd0: cd present [327338 x 2048 byte records] > Apr 11 18:41:38 grizzly named[177]: starting (/etc/namedb/named.conf). named 8.2.3-REL Wed Apr 11 16:59:40 EEST 2001 root@grizzly.carrier.kiev.ua:/var/obj/var/src/usr.sbin/named > Apr 11 18:41:38 grizzly named[177]: limit files set to fdlimit (1024) > Apr 11 18:41:38 grizzly named[178]: Ready to answer queries. > Apr 11 18:41:38 grizzly ntpd[180]: ntpd 4.0.99b Wed Apr 11 16:58:45 EEST 2001 (1) > Apr 11 18:41:38 grizzly ntpd[180]: using kernel phase-lock loop 2040 > Apr 11 18:41:38 grizzly ntpd[180]: getnetnum: "news.demos.su" invalid host number, line ignored > Apr 11 18:41:38 grizzly ntpd[180]: getnetnum: "news1.demos.su" invalid host number, line ignored > Apr 11 18:41:38 grizzly ntpd[180]: getnetnum: "news.gamma.ru" invalid host number, line ignored > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.834984 -> 7.737884) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842559 -> 7.735504) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843816 -> 7.738378) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839712 -> 7.734986) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839748 -> 7.743734) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.736175) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.739450) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.750258) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.751613) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.764301) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.764883) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.775410) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.776000) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.780731) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.787880) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.788925) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.791228) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.792100) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.742846) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.745269) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.746962) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.748818) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.749914) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.751635) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.753202) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.756961) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.739800) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.740682) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.751453) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.752134) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.753513) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.754646) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.755632) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.757180) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.761039) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.765178) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.766163) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843178 -> 7.734621) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843178 -> 7.735361) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843178 -> 7.737016) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843178 -> 7.737564) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.830187 -> 7.734668) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.830187 -> 7.749899) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.838573 -> 7.734923) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843469 -> 7.734611) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.838522 -> 7.738094) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.838522 -> 7.745038) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.844055 -> 7.734420) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.735466) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.740883) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.755061) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.766780) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.783736) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.795306) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.810152) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.826392) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843630 -> 7.735223) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.831660 -> 7.737727) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.831660 -> 7.759594) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842772 -> 7.734324) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.805040 -> 7.735190) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.805040 -> 7.735336) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.805040 -> 7.771539) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843616 -> 7.734416) > Apr 11 18:41:38 grizzly login: ROOT LOGIN (root) ON ttyv1 > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.774619 -> 7.740860) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839139 -> 7.735976) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839139 -> 7.736433) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839139 -> 7.736580) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839139 -> 7.736791) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839139 -> 7.736964) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.820332 -> 7.744583) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.820332 -> 7.744793) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.820332 -> 7.750961) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842030 -> 7.734805) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.831764 -> 7.737653) > ===}}} > > Different lines between bad kernel messages('-') and good old kernel > messages('+'): > > -avail memory = 127016960 (124040K bytes) > +avail memory = 127021056 (124044K bytes) > > -VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc02f81a2 (1000022) > +VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc02f7362 (1000022) > > Kernel config (did not changed): > > ==={{{ > machine i386 > #cpu I386_CPU > #cpu I486_CPU > #cpu I586_CPU > cpu I686_CPU > ident griz > maxusers 64 > options MSGBUF_SIZE=81920 > #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols > #options MATH_EMULATE #Support for x87 emulation > options INET #InterNETworking > options IPFIREWALL #firewall > options IPFIREWALL_VERBOSE #print information about > options IPFIREWALL_DEFAULT_TO_ACCEPT > options FFS #Berkeley Fast Filesystem > options FFS_ROOT #FFS usable as root device [keep this!] > options SOFTUPDATES #Enable FFS soft updates support > options NFS #Network Filesystem > options MSDOSFS #MSDOS Filesystem > options CD9660 #ISO 9660 Filesystem > options PROCFS #Process filesystem > options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] > options SCSI_DELAY=3000 #Delay (in ms) before probing SCSI > options INCLUDE_CONFIG_FILE > options USERCONFIG #boot -c editor > options VISUAL_USERCONFIG #visual boot -c editor > options KTRACE #ktrace(1) support > options SYSVSHM #SYSV-style shared memory > options SYSVMSG #SYSV-style message queues > options SYSVSEM #SYSV-style semaphores > options P1003_1B #Posix P1003_1B real-time extensions > options _KPOSIX_PRIORITY_SCHEDULING > options ICMP_BANDLIM #Rate limit bad replies > options KBD_INSTALL_CDEV # install a CDEV entry in /dev > options VESA > options EXT2FS > options USER_LDT > device isa > device pci > # Floppy drives > device fdc0 at isa? port IO_FD1 irq 6 drq 2 > device fd0 at fdc0 drive 0 > # SCSI peripherals > device ahc # AHA2940 and onboard AIC7xxx devices > device scbus # SCSI bus (required) > device da # Direct Access (disks) > device cd # CD > device pass # Passthrough device (direct SCSI access) > # atkbdc0 controls both the keyboard and the PS/2 mouse > device atkbdc0 at isa? port IO_KBD > device atkbd0 at atkbdc? irq 1 flags 0x1 > device psm0 at atkbdc? irq 12 > device vga0 at isa? > # splash screen/screen saver > pseudo-device splash > # syscons is the default console driver, resembling an SCO console > device sc0 at isa? flags 0x100 > options SC_HISTORY_SIZE=1200 > options SC_MOUSE_CHAR=0x03 > # 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? flags 0x20 # Advanced Power Management > # Serial (COM) ports > device sio0 at isa? port IO_COM1 flags 0x10 irq 4 > device sio1 at isa? port IO_COM2 irq 3 > # Parallel port > device ppc0 at isa? irq 7 > device ppbus # Parallel port bus (required) > device lpt # Printer > device plip # TCP/IP over parallel > device ppi # Parallel port interface device > #device vpo # Requires scbus and da > # PCI Ethernet NICs. > device fxp # Intel EtherExpress PRO/100B (82557, 82558) > ## sound > device pcm > device sbc > # 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 64 # Pseudo-ttys (telnet etc) > pseudo-device vn 3 > pseudo-device bpf 3 > pseudo-device speaker > > options NETGRAPH #netgraph(4) system > options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN > options TCP_RESTRICT_RST #restrict emission of TCP RST > options ICMP_BANDLIM > options QUOTA #enable disk quotas > options NTIMECOUNTER=20 > options VESA > ===}}} > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- nicholas harteau nrh@ikami.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 10:14:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id 1045337B424; Wed, 11 Apr 2001 10:14:34 -0700 (PDT) Date: Wed, 11 Apr 2001 10:14:34 -0700 From: David O'Brien To: Matthew Emmerton Cc: stable@FreeBSD.ORG Subject: Re: Releases Message-ID: <20010411101433.A42670@hub.freebsd.org> Reply-To: stable@freebsd.org References: <014a01c0c12e$e5e76f20$1200a8c0@gsicomp.on.ca> <20010410145433.C20548@hub.freebsd.org> <00b801c0c21e$5a1532c0$1200a8c0@gsicomp.on.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <00b801c0c21e$5a1532c0$1200a8c0@gsicomp.on.ca>; from matt@gsicomp.on.ca on Tue, Apr 10, 2001 at 08:28:37PM -0400 X-Operating-System: FreeBSD 4.2-STABLE Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 10, 2001 at 08:28:37PM -0400, Matthew Emmerton wrote: > Do you read every thread on every topic? Just about. Which is why many of us have had it with the same question comming up over, and over, and over, and over. I couldn't take it anymore and now only read -stable during freezes and when I've made a big commit there. I know other committers who have been run out of here also. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 10:21:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 8E9C837B624 for ; Wed, 11 Apr 2001 10:21:21 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f3BHIL887421; Wed, 11 Apr 2001 10:18:21 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: jcm@FreeBSD-uk.eu.org Cc: freebsd-stable@FreeBSD.ORG Subject: Re: new kernel book this summer? In-Reply-To: <20010411151543.A68310@dogma.freebsd-uk.eu.org> References: <20010411151543.A68310@dogma.freebsd-uk.eu.org> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010411101821Z.jkh@osd.bsdi.com> Date: Wed, 11 Apr 2001 10:18:21 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 12 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I posted a week or so ago on -hackers asking about a rumor that a revised > 'design and implementation of freebsd os' would be out this summer. No one > replied. Since then, a number of people have emailed me privately expressing > interest in this. > > So, does anyone know anything about this? It's not a rumor, both Kirk McKusick and David Greenman (two of the authors) announced it at BSDCon, but it's been delayed. It's not sure at this stage just how long the book will take to get published. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 10:27:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id 31FB637B422; Wed, 11 Apr 2001 10:27:32 -0700 (PDT) Date: Wed, 11 Apr 2001 10:27:32 -0700 From: David O'Brien To: Lev Serebryakov Cc: All Subject: Re: gcc-2.95.3 and sjlj patches Message-ID: <20010411102732.C42670@hub.freebsd.org> Reply-To: stable@freebsd.org References: <190174694797.20010411135211@arcadia.spb.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <190174694797.20010411135211@arcadia.spb.ru>; from Lev.Serebryakov@arcadia.spb.ru on Wed, Apr 11, 2001 at 01:52:11PM +0400 X-Operating-System: FreeBSD 4.2-STABLE Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 11, 2001 at 01:52:11PM +0400, Lev Serebryakov wrote: > Where could I get sjlj patches for gcc-2.95.3 to put in my port, > based on gcc-2.95.3? One way is to get the gcc-2.95.3.tar.* tarball and the gcc-2.95.3.test3.tar.* tarball, extract the two and diff gcc-2.95.3 to gcc-2.95.3.test3. Edit the resulting patch to remove the obivious bits like the version number and docs differences. I sent a set of patches to -hackers (these should be the right ones, but I cannot remember how I produced them): Date: Wed, 21 Mar 2001 09:46:38 -0800 From: David O'Brien Subject: Re: GCC Upgrade? Message-ID: <20010321094638.E92274@dragon.nuxi.com> References: Index: except.c =================================================================== RCS file: /cvs/gcc/egcs/gcc/except.c,v retrieving revision 1.82.4.3 retrieving revision 1.82.4.2 diff -u -r1.82.4.3 -r1.82.4.2 --- except.c 2001/02/19 14:01:59 1.82.4.3 +++ except.c 2000/12/29 16:18:54 1.82.4.2 @@ -723,21 +723,41 @@ receive_exception_label (handler_label) rtx handler_label; { + rtx around_label = NULL_RTX; + + if (! flag_new_exceptions || exceptions_via_longjmp) + { + around_label = gen_label_rtx (); + emit_jump (around_label); + emit_barrier (); + } + emit_label (handler_label); -#ifdef HAVE_exception_receiver if (! exceptions_via_longjmp) - if (HAVE_exception_receiver) - emit_insn (gen_exception_receiver ()); + { +#ifdef HAVE_exception_receiver + if (HAVE_exception_receiver) + emit_insn (gen_exception_receiver ()); + else #endif - #ifdef HAVE_nonlocal_goto_receiver - if (! exceptions_via_longjmp) - if (HAVE_nonlocal_goto_receiver) - emit_insn (gen_nonlocal_goto_receiver ()); + if (HAVE_nonlocal_goto_receiver) + emit_insn (gen_nonlocal_goto_receiver ()); + else #endif -} + { /* Nothing */ } + } + else + { +#ifndef DONT_USE_BUILTIN_SETJMP + expand_builtin_setjmp_receiver (handler_label); +#endif + } + if (around_label) + emit_label (around_label); +} struct func_eh_entry { @@ -1320,7 +1340,7 @@ start_dynamic_handler () { rtx dhc, dcc; - rtx x, arg, buf; + rtx arg, buf; int size; #ifndef DONT_USE_BUILTIN_SETJMP @@ -1362,18 +1382,17 @@ buf = plus_constant (XEXP (arg, 0), GET_MODE_SIZE (Pmode)*2); #ifdef DONT_USE_BUILTIN_SETJMP - x = emit_library_call_value (setjmp_libfunc, NULL_RTX, 1, SImode, 1, - buf, Pmode); - /* If we come back here for a catch, transfer control to the handler. */ - jumpif_rtx (x, ehstack.top->entry->exception_handler_label); -#else { - /* A label to continue execution for the no exception case. */ - rtx noex = gen_label_rtx(); - x = expand_builtin_setjmp (buf, NULL_RTX, noex, - ehstack.top->entry->exception_handler_label); - emit_label (noex); + rtx x; + x = emit_library_call_value (setjmp_libfunc, NULL_RTX, LCT_CONST, + TYPE_MODE (integer_type_node), 1, + buf, Pmode); + /* If we come back here for a catch, transfer control to the handler. */ + jumpif_rtx (x, ehstack.top->entry->exception_handler_label); } +#else + expand_builtin_setjmp_setup (buf, + ehstack.top->entry->exception_handler_label); #endif /* We are committed to this, so update the handler chain. */ Index: expr.c =================================================================== RCS file: /cvs/gcc/egcs/gcc/expr.c,v retrieving revision 1.144.4.9 retrieving revision 1.144.4.8 diff -u -r1.144.4.9 -r1.144.4.8 --- expr.c 2001/02/19 14:02:00 1.144.4.9 +++ expr.c 2001/01/25 14:03:06 1.144.4.8 @@ -192,6 +192,7 @@ static int apply_args_size PROTO((void)); static int apply_result_size PROTO((void)); static rtx result_vector PROTO((int, rtx)); +static rtx expand_builtin_setjmp PROTO((tree, rtx)); static rtx expand_builtin_apply_args PROTO((void)); static rtx expand_builtin_apply PROTO((rtx, rtx, rtx)); static void expand_builtin_return PROTO((rtx)); @@ -8544,44 +8545,29 @@ return tem; } -/* __builtin_setjmp is passed a pointer to an array of five words (not - all will be used on all machines). It operates similarly to the C - library function of the same name, but is more efficient. Much of - the code below (and for longjmp) is copied from the handling of - non-local gotos. - - NOTE: This is intended for use by GNAT and the exception handling - scheme in the compiler and will only work in the method used by - them. */ +/* Construct the leading half of a __builtin_setjmp call. Control will + return to RECEIVER_LABEL. This is used directly by sjlj exception + handling code. */ -rtx -expand_builtin_setjmp (buf_addr, target, first_label, next_label) +void +expand_builtin_setjmp_setup (buf_addr, receiver_label) rtx buf_addr; - rtx target; - rtx first_label, next_label; + rtx receiver_label; { - rtx lab1 = gen_label_rtx (); enum machine_mode sa_mode = STACK_SAVEAREA_MODE (SAVE_NONLOCAL); - enum machine_mode value_mode; rtx stack_save; - value_mode = TYPE_MODE (integer_type_node); - #ifdef POINTERS_EXTEND_UNSIGNED buf_addr = convert_memory_address (Pmode, buf_addr); #endif buf_addr = force_reg (Pmode, buf_addr); - if (target == 0 || GET_CODE (target) != REG - || REGNO (target) < FIRST_PSEUDO_REGISTER) - target = gen_reg_rtx (value_mode); - emit_queue (); - /* We store the frame pointer and the address of lab1 in the buffer - and use the rest of it for the stack save area, which is - machine-dependent. */ + /* We store the frame pointer and the address of receiver_label in + the buffer and use the rest of it for the stack save area, which + is machine-dependent. */ #ifndef BUILTIN_SETJMP_FRAME_VALUE #define BUILTIN_SETJMP_FRAME_VALUE virtual_stack_vars_rtx @@ -8593,7 +8579,7 @@ (gen_rtx_MEM (Pmode, plus_constant (buf_addr, GET_MODE_SIZE (Pmode)))), - force_reg (Pmode, gen_rtx_LABEL_REF (Pmode, lab1))); + force_reg (Pmode, gen_rtx_LABEL_REF (Pmode, receiver_label))); stack_save = gen_rtx_MEM (sa_mode, plus_constant (buf_addr, @@ -8606,20 +8592,22 @@ emit_insn (gen_builtin_setjmp_setup (buf_addr)); #endif - /* Set TARGET to zero and branch to the first-time-through label. */ - emit_move_insn (target, const0_rtx); - emit_jump_insn (gen_jump (first_label)); - emit_barrier (); - emit_label (lab1); + /* Tell optimize_save_area_alloca that extra work is going to + need to go on during alloca. */ + current_function_calls_setjmp = 1; - /* Tell flow about the strange goings on. Putting `lab1' on - `nonlocal_goto_handler_labels' to indicates that function - calls may traverse the arc back to this label. */ - + /* Set this so all the registers get saved in our frame; we need to be + able to copy the saved values for any registers from frames we unwind. */ current_function_has_nonlocal_label = 1; - nonlocal_goto_handler_labels = - gen_rtx_EXPR_LIST (VOIDmode, lab1, nonlocal_goto_handler_labels); +} +/* Construct the trailing part of a __builtin_setjmp call. + This is used directly by sjlj exception handling code. */ + +void +expand_builtin_setjmp_receiver (receiver_label) + rtx receiver_label ATTRIBUTE_UNUSED; +{ /* Clobber the FP when we get here, so we have to make sure it's marked as used by this function. */ emit_insn (gen_rtx_USE (VOIDmode, hard_frame_pointer_rtx)); @@ -8666,7 +8654,7 @@ #ifdef HAVE_builtin_setjmp_receiver if (HAVE_builtin_setjmp_receiver) - emit_insn (gen_builtin_setjmp_receiver (lab1)); + emit_insn (gen_builtin_setjmp_receiver (receiver_label)); else #endif #ifdef HAVE_nonlocal_goto_receiver @@ -8678,11 +8666,67 @@ ; /* Nothing */ } - /* Set TARGET, and branch to the next-time-through label. */ - emit_move_insn (target, const1_rtx); - emit_jump_insn (gen_jump (next_label)); + /* @@@ This is a kludge. Not all machine descriptions define a blockage + insn, but we must not allow the code we just generated to be reordered + by scheduling. Specifically, the update of the frame pointer must + happen immediately, not later. So emit an ASM_INPUT to act as blockage + insn. */ + emit_insn (gen_rtx_ASM_INPUT (VOIDmode, "")); +} + + +/* __builtin_setjmp is passed a pointer to an array of five words (not + all will be used on all machines). It operates similarly to the C + library function of the same name, but is more efficient. Much of + the code below (and for longjmp) is copied from the handling of + non-local gotos. + + NOTE: This is intended for use by GNAT and the exception handling + scheme in the compiler and will only work in the method used by + them. */ + +static rtx +expand_builtin_setjmp (arglist, target) + tree arglist; + rtx target; +{ + rtx buf_addr, next_lab, cont_lab; + + if (arglist == 0 + || TREE_CODE (TREE_TYPE (TREE_VALUE (arglist))) != POINTER_TYPE) + return NULL_RTX; + + if (target == 0 || GET_CODE (target) != REG + || REGNO (target) < FIRST_PSEUDO_REGISTER) + target = gen_reg_rtx (TYPE_MODE (integer_type_node)); + + buf_addr = expand_expr (TREE_VALUE (arglist), NULL_RTX, VOIDmode, 0); + + next_lab = gen_label_rtx (); + cont_lab = gen_label_rtx (); + + expand_builtin_setjmp_setup (buf_addr, next_lab); + + /* Set TARGET to zero and branch to the continue label. */ + emit_move_insn (target, const0_rtx); + emit_jump_insn (gen_jump (cont_lab)); emit_barrier (); + emit_label (next_lab); + expand_builtin_setjmp_receiver (next_lab); + + /* Set TARGET to one. */ + emit_move_insn (target, const1_rtx); + emit_label (cont_lab); + + /* Tell flow about the strange goings on. Putting `next_lab' on + `nonlocal_goto_handler_labels' to indicates that function + calls may traverse the arc back to this label. */ + + current_function_has_nonlocal_label = 1; + nonlocal_goto_handler_labels + = gen_rtx_EXPR_LIST (VOIDmode, next_lab, nonlocal_goto_handler_labels); + return target; } @@ -9703,18 +9747,10 @@ #endif case BUILT_IN_SETJMP: - if (arglist == 0 - || TREE_CODE (TREE_TYPE (TREE_VALUE (arglist))) != POINTER_TYPE) - break; - else - { - rtx buf_addr = expand_expr (TREE_VALUE (arglist), subtarget, - VOIDmode, 0); - rtx lab = gen_label_rtx (); - rtx ret = expand_builtin_setjmp (buf_addr, target, lab, lab); - emit_label (lab); - return ret; - } + target = expand_builtin_setjmp (arglist, target); + if (target) + return target; + break; /* __builtin_longjmp is passed a pointer to an array of five words. It's similar to the C library longjmp function but works with Index: expr.h =================================================================== RCS file: /cvs/gcc/egcs/gcc/expr.h,v retrieving revision 1.34.4.4 retrieving revision 1.34.4.3 diff -u -r1.34.4.4 -r1.34.4.3 --- expr.h 2001/02/19 14:02:02 1.34.4.4 +++ expr.h 2000/12/29 16:18:54 1.34.4.3 @@ -831,7 +831,8 @@ Useful after calling expand_expr with 1 as sum_ok. */ extern rtx force_operand PROTO((rtx, rtx)); -extern rtx expand_builtin_setjmp PROTO((rtx, rtx, rtx, rtx)); +extern void expand_builtin_setjmp_setup PARAMS ((rtx, rtx)); +extern void expand_builtin_setjmp_receiver PARAMS ((rtx)); #ifdef TREE_CODE /* Generate code for computing expression EXP. Index: varasm.c =================================================================== RCS file: /cvs/gcc/egcs/gcc/varasm.c,v retrieving revision 1.59.4.7 retrieving revision 1.59.4.6 diff -u -r1.59.4.7 -r1.59.4.6 --- varasm.c 2001/02/19 14:02:02 1.59.4.7 +++ varasm.c 2001/01/25 14:03:24 1.59.4.6 @@ -3494,6 +3494,18 @@ pop_obstacks (); } + if (GET_CODE (x) == LABEL_REF) + { + extern rtx forced_labels; + + push_obstacks_nochange (); + rtl_in_saveable_obstack (); + + forced_labels = gen_rtx_EXPR_LIST (VOIDmode, + XEXP (x, 0), + forced_labels); + pop_obstacks (); + } /* Allocate a pool constant descriptor, fill it in, and chain it in. */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 10:28:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gatekeeper.orem.verio.net (gatekeeper.orem.verio.net [192.41.0.8]) by hub.freebsd.org (Postfix) with ESMTP id 94B3E37B424 for ; Wed, 11 Apr 2001 10:28:36 -0700 (PDT) (envelope-from aaronm@orem.verio.net) Received: from mx.dmz.orem.verio.net (mx.dmz.orem.verio.net [10.1.1.10]) by gatekeeper.orem.verio.net (Postfix) with ESMTP id C69F43BF160 for ; Wed, 11 Apr 2001 11:28:35 -0600 (MDT) Received: from localhost (aaronm@localhost) by mx.dmz.orem.verio.net (8.11.1/8.11.1) with ESMTP id f3BHSWd79964; Wed, 11 Apr 2001 11:28:32 -0600 (MDT) (envelope-from aaronm@mx.dmz.orem.verio.net) Date: Wed, 11 Apr 2001 11:28:32 -0600 (MDT) From: Aaron Mildenstein To: Kal Torak Cc: The Hermit Hacker , Jonathan Belson , FreeBSD-stable Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) In-Reply-To: <3AD48782.2CEAE87B@quake.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I believe that the nVidia for BeOS drivers were written by a 3rd party individual and not by nVidia themselves. buh On Thu, 12 Apr 2001, Kal Torak wrote: > The Hermit Hacker wrote: > > > > NVidia cards are all I buy now, have 3 or 4 right now ... don't the cards > > have some sort of serial number? is there any way of using that to > > provide a pseudo-petition list ... maybe our new benefactors could talk to > > NVidia themselves, get nVidia to setup a nonline 'registration form' that > > we could all connect to and submit our serial numbers, to give them a feel > > for number of FreeBSD'rs out here? > > nVidia cards are really the ONLY choice to buy now... Not that Im complaining, > they are good cards, we just need some support for the more recent ones! > Since I cant find anything for the GeForce line... Let alone GeForce2, and the > GeForce3 series (are they going to call it that?) will be on sale soon... > > If there is enough interest from us they should be willing to make ports to > FreeBSD.. I mean they support BeOS, how many people even use that, let alone > have nVidia cards? Surly we could match them in numbers! > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 10:35:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 3690637B422 for ; Wed, 11 Apr 2001 10:35:41 -0700 (PDT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 1234 invoked by uid 0); 11 Apr 2001 17:35:39 -0000 Received: from pd950a3a5.dip.t-dialin.net (HELO lofizwei) (217.80.163.165) by mail.gmx.net (mp027-rz3) with SMTP; 11 Apr 2001 17:35:39 -0000 Message-ID: <012401c0c2ad$d3d29d20$0508a8c0@lofi.dyndns.org> From: "Michael Nottebrock" To: "Kal Torak" , "The Hermit Hacker" Cc: "Jonathan Belson" , "FreeBSD-stable" References: <3AD48782.2CEAE87B@quake.com.au> Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) Date: Wed, 11 Apr 2001 19:35:38 +0200 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.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Kal Torak" To: "The Hermit Hacker" Cc: "Jonathan Belson" ; "FreeBSD-stable" Sent: Wednesday, April 11, 2001 6:34 PM Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) > [...] > nVidia cards are really the ONLY choice to buy now... Not that Im complaining, > they are good cards, we just need some support for the more recent ones! nVidia won't release the source code nor let people outside nVidia work freely on hardware accelerated OpenGL drivers, so the cards of choice for FreeBSD systems probably are ATi Rage 128, ATi Radeon, Matrox G4x0 or Intel based cards since those manufacturers have laid the development of non-windows accelerated drives completely into the hands of the DRI team (by contracting VA Linux systems, formerly known as Precision Insight). Ofcourse, the DRI team is developing the kernel modules for Linux, but at least, the modules are open source, which makes them portable. Greetings, Michael Nottebrock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 11: 8:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id 9952137B422 for ; Wed, 11 Apr 2001 11:08:52 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by probity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14nP2w-000Dfn-00; Wed, 11 Apr 2001 19:08:50 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f3BI8oP72726; Wed, 11 Apr 2001 19:08:50 +0100 (BST) (envelope-from jcm) Date: Wed, 11 Apr 2001 19:08:50 +0100 From: j mckitrick To: Jordan Hubbard Cc: freebsd-stable@FreeBSD.ORG Subject: Re: new kernel book this summer? Message-ID: <20010411190849.A72702@dogma.freebsd-uk.eu.org> References: <20010411151543.A68310@dogma.freebsd-uk.eu.org> <20010411101821Z.jkh@osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010411101821Z.jkh@osd.bsdi.com>; from jkh@osd.bsdi.com on Wed, Apr 11, 2001 at 10:18:21AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 11, 2001 at 10:18:21AM -0700, Jordan Hubbard wrote: | It's not a rumor, both Kirk McKusick and David Greenman (two of the | authors) announced it at BSDCon, but it's been delayed. It's not sure | at this stage just how long the book will take to get published. Ah, thanks. Best guess: before or after summer (June) ? jm -- ------------------------------------------- Jonathon McKitrick -- jcm@freebsd-uk.eu.org Do not mistake lack of talent for genius ------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 11:15:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id B378D37B422 for ; Wed, 11 Apr 2001 11:15:07 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f3BICD887688; Wed, 11 Apr 2001 11:12:15 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: jcm@FreeBSD-uk.eu.org Cc: freebsd-stable@FreeBSD.ORG Subject: Re: new kernel book this summer? In-Reply-To: <20010411190849.A72702@dogma.freebsd-uk.eu.org> References: <20010411151543.A68310@dogma.freebsd-uk.eu.org> <20010411101821Z.jkh@osd.bsdi.com> <20010411190849.A72702@dogma.freebsd-uk.eu.org> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010411111213M.jkh@osd.bsdi.com> Date: Wed, 11 Apr 2001 11:12:13 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 1 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wouldn't even venture a guess at this point. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 11:23:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailout06.sul.t-online.com (mailout06.sul.t-online.com [194.25.134.19]) by hub.freebsd.org (Postfix) with ESMTP id 5D96337B422 for ; Wed, 11 Apr 2001 11:23:28 -0700 (PDT) (envelope-from sven.huster@mailsurf.com) Received: from fwd05.aul.t-online.de by mailout06.sul.t-online.com with smtp id 14nPGz-0004Av-06; Wed, 11 Apr 2001 20:23:21 +0200 Received: from venus.mailsurf.com (320051988339-0001@[62.158.243.45]) by fmrl05.sul.t-online.com with esmtp id 14nPGj-0uk7iiC; Wed, 11 Apr 2001 20:23:05 +0200 Message-Id: <5.0.2.1.0.20010411202315.028defe0@mx01.mailsurf.com> X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Wed, 11 Apr 2001 20:23:38 +0200 To: Danny Braniss From: Sven Huster Subject: Re: diskless operation Cc: freebsd-stable@freebsd.org In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Sender: 320051988339-0001@t-dialin.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 18:18 11.04.2001, Danny Braniss wrote: >*This message was transferred with a trial version of CommuniGate(tm) Pro* >In message <5.0.2.1.0.20010411164359.00a63880@mx01.mailsurf.com>you write: > >}But my interface has no ip after boot! >}So dhclient needs to be invoked. > >if you are booting via bootp/pxe then the loader will have placed in the >environment some info. see kenv(1), or before loading, type show. > >look in /etc/rc.diskless1, it will try and figure out the interface and set >some variables so that rc.network can do the rest. do you get a message, like > Interface exp0 IP-Address 10.0.0.1 Broadcast ... ? > >as far as i know, you dont't need dhclient if you are booting diskless, unless >there is other info you need, such as gateway, dns server, etc. Got the message but no ip in there. regards Sven Huster Senior IT Systems Administrator *BSD, Linux, Solaris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 11:36:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from globalrelay.com (h216-18-71-77.gtcust.grouptelecom.net [216.18.71.77]) by hub.freebsd.org (Postfix) with ESMTP id 42A6637B422 for ; Wed, 11 Apr 2001 11:36:40 -0700 (PDT) (envelope-from lists@globalrelay.net) Received: from [10.2.0.6] (HELO hpvl4002) by globalrelay.com (CommuniGate Pro SMTP 3.4b7) with SMTP id 446274 for freebsd-stable@FreeBSD.ORG; Wed, 11 Apr 2001 11:36:39 -0700 Message-ID: <040801c0c2b6$59cce310$0600020a@frontend> Reply-To: "Eric Parusel" From: "Eric Parusel" To: Subject: subscribe Date: Wed, 11 Apr 2001 11:36:41 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0405_01C0C27B.AD67F090" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0405_01C0C27B.AD67F090 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable subscribe ------=_NextPart_000_0405_01C0C27B.AD67F090 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
subscribe
------=_NextPart_000_0405_01C0C27B.AD67F090-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 12: 2:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id DB15237B423 for ; Wed, 11 Apr 2001 12:02:27 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id vawaaaaa for ; Thu, 12 Apr 2001 05:01:51 +1000 Message-ID: <3AD4AB28.EA342EC0@quake.com.au> Date: Thu, 12 Apr 2001 05:06:16 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Michael Nottebrock Cc: The Hermit Hacker , Jonathan Belson , FreeBSD-stable Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: <3AD48782.2CEAE87B@quake.com.au> <012401c0c2ad$d3d29d20$0508a8c0@lofi.dyndns.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Nottebrock wrote: > > ----- Original Message ----- > From: "Kal Torak" > To: "The Hermit Hacker" > Cc: "Jonathan Belson" ; "FreeBSD-stable" > > Sent: Wednesday, April 11, 2001 6:34 PM > Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) > > > [...] > > nVidia cards are really the ONLY choice to buy now... Not that Im > complaining, > > they are good cards, we just need some support for the more recent > ones! > > nVidia won't release the source code nor let people outside nVidia > work freely on hardware accelerated OpenGL drivers, so the cards of > choice for FreeBSD systems probably are ATi Rage 128, ATi Radeon, > Matrox G4x0 or Intel based cards since those manufacturers have laid > the development of non-windows accelerated drives completely into the > hands of the DRI team (by contracting VA Linux systems, formerly known > as Precision Insight). Ofcourse, the DRI team is developing the kernel > modules for Linux, but at least, the modules are open source, which > makes them portable. And yet DRI isnt yet fully working under FreeBSD... Not last I looked anyway! nVidia cards are currently the best... We need to have support for them! Apparently the BeOS drivers were made by a 3rd party, I dont know that for sure, but if they were... Why cant we make some for FreeBSD? Or if nVidia made them surly there would be enough people using FreeBSD that have nVidia based cards that they would make a port? I dont see why they wont make there drivers open source... They must provide the win32 source to the card manufacturers, since nVidia based cards often come with drivers supplied by the company... Anyway, whatever the case we need those drivers for FreeBSD :) We must not rest until we have them! Why should only linux be able to play all those great games in OpenGL? Why should we be stuck with having to use low end accelerator cards? We shouldnt! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 12: 3: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 2FBA137B422 for ; Wed, 11 Apr 2001 12:03:04 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id xawaaaaa for ; Thu, 12 Apr 2001 05:02:32 +1000 Message-ID: <3AD4AB51.B2402FE2@quake.com.au> Date: Thu, 12 Apr 2001 05:06:57 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Aaron Mildenstein Cc: The Hermit Hacker , Jonathan Belson , FreeBSD-stable Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Aaron Mildenstein wrote: > > I believe that the nVidia for BeOS drivers were written by a 3rd party > individual and not by nVidia themselves. If thats true, then we need to develop some for FreeBSD!!! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 12:15:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mobile.hub.org (mobile.acadiau.ca [131.162.137.70]) by hub.freebsd.org (Postfix) with ESMTP id C131D37B422 for ; Wed, 11 Apr 2001 12:15:48 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by mobile.hub.org (8.11.1/8.11.1) with ESMTP id f3BJFT070170; Wed, 11 Apr 2001 16:15:29 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: mobile.hub.org: scrappy owned process doing -bs Date: Wed, 11 Apr 2001 16:15:29 -0300 (ADT) From: The Hermit Hacker To: Kal Torak Cc: Michael Nottebrock , Jonathan Belson , FreeBSD-stable Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) In-Reply-To: <3AD4AB28.EA342EC0@quake.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Apr 2001, Kal Torak wrote: > Michael Nottebrock wrote: > > > > ----- Original Message ----- > > From: "Kal Torak" > > To: "The Hermit Hacker" > > Cc: "Jonathan Belson" ; "FreeBSD-stable" > > > > Sent: Wednesday, April 11, 2001 6:34 PM > > Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) > > > > > [...] > > > nVidia cards are really the ONLY choice to buy now... Not that Im > > complaining, > > > they are good cards, we just need some support for the more recent > > ones! > > > > nVidia won't release the source code nor let people outside nVidia > > work freely on hardware accelerated OpenGL drivers, so the cards of > > choice for FreeBSD systems probably are ATi Rage 128, ATi Radeon, > > Matrox G4x0 or Intel based cards since those manufacturers have laid > > the development of non-windows accelerated drives completely into the > > hands of the DRI team (by contracting VA Linux systems, formerly known > > as Precision Insight). Ofcourse, the DRI team is developing the kernel > > modules for Linux, but at least, the modules are open source, which > > makes them portable. > > And yet DRI isnt yet fully working under FreeBSD... Not last I looked > anyway! > > nVidia cards are currently the best... We need to have support for them! > Apparently the BeOS drivers were made by a 3rd party, I dont know that > for sure, but if they were... Why cant we make some for FreeBSD? > > Or if nVidia made them surly there would be enough people using FreeBSD > that have nVidia based cards that they would make a port? I dont see why > they wont make there drivers open source... > > They must provide the win32 source to the card manufacturers, since nVidia > based cards often come with drivers supplied by the company... Anyway, > whatever the case we need those drivers for FreeBSD :) Ya, but, the nVidia drivers supplied by the manufacturers are most likely under a very heavy NDA ... just look at the headaches that (god, I forget his name, sorry *sigh*) is going through with the whole Sun/JDK isue, and that is supposed to be "Open Source Software", no? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 12:30:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from seaholm.caamora.com.au (seaholm.caamora.com.au [203.7.226.5]) by hub.freebsd.org (Postfix) with ESMTP id 815B737B424 for ; Wed, 11 Apr 2001 12:30:05 -0700 (PDT) (envelope-from jon@seaholm.caamora.com.au) Received: (from jon@localhost) by seaholm.caamora.com.au (8.11.1/8.11.1) id f3BJRIt09704; Thu, 12 Apr 2001 05:27:18 +1000 (EST) Message-ID: <20010412052718.44835@caamora.com.au> Date: Thu, 12 Apr 2001 05:27:18 +1000 From: jonathan michaels To: Oliver Fromme Cc: freebsd-stable@freebsd.org Subject: Re: Releases References: <200104102154.f3ALsce84245@ns1.unixathome.org> <200104111345.PAA67262@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <200104111345.PAA67262@lurza.secnetix.de>; from Oliver Fromme on Wed, Apr 11, 2001 at 03:45:41PM +0200 Organisation: Caamora, PO Box 144, Rosebery NSW 1445 Australia Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG oliver, On Wed, Apr 11, 2001 at 03:45:41PM +0200, Oliver Fromme wrote: > Dan Langille wrote: > > On 10 Apr 2001, at 14:48, David O'Brien wrote: > > > On Tue, Apr 10, 2001 at 06:32:15AM +1200, Dan Langille wrote: > > > > AFAIK, the thread to date has been about whether or not [something like] > > > > the label "-development" would cause less confusion than "-current". My snipped for compactness > Maybe it would reduce confusion somewhat if people would > just stop saying ``4.1-stable'' etc. Those simply do not > exist. > > I would also vote for ``uname -r'' saying ``4-STABLE'' and > appending the date (similar to the snapshot naming), like > ``4-STABLE-20010509''. This is much more useful than > ``4.3-STABLE'', IMO. actually, given teh granularity of teh cvs system it might be worthwhile to add hh:mm .. on second thoughts your sugestion is teh sanest i've seen and personally wonder why it wasn't done like this fron teh begining. this is how cvs functions, and give we use cvs why not make it ease fro people to actually use the resources that are provide by cvs, i.e. the very system that we use. with regard and thanks. jonathan > Just my 2 Euro cents ... and my two pacific peso centimes .. heading for 1 us cent and falling -- ================================================================ Jonathan Michaels http://www.caamora.com.au PO Box 144, Rosebery, NSW 1445 suffering construction anxiety ============================================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 12:49: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id 94A1037B423 for ; Wed, 11 Apr 2001 12:48:58 -0700 (PDT) (envelope-from olli@lurza.secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.9.3/8.9.3) id VAA85126; Wed, 11 Apr 2001 21:48:57 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Date: Wed, 11 Apr 2001 21:48:57 +0200 (CEST) Message-Id: <200104111948.VAA85126@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG Reply-To: freebsd-stable@FreeBSD.ORG Subject: Re: Releases In-Reply-To: <20010412052718.44835@caamora.com.au> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.1-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jonathan michaels wrote: > On Wed, Apr 11, 2001 at 03:45:41PM +0200, Oliver Fromme wrote: > > Maybe it would reduce confusion somewhat if people would > > just stop saying ``4.1-stable'' etc. Those simply do not > > exist. > > > > I would also vote for ``uname -r'' saying ``4-STABLE'' and > > appending the date (similar to the snapshot naming), like > > ``4-STABLE-20010509''. This is much more useful than > > ``4.3-STABLE'', IMO. > > actually, given teh granularity of teh cvs system it might be > worthwhile to add hh:mm .. That would be rather difficult. As far as I know, there is no automatic mechanism to store the current date and time somewhere upon a cvs checkout or update. Anyway, just the day should be sufficient in most cases. Think of someone posting a well-known problem to -questions or -stable, and giving his uname output which says, for example, ``4-STABLE-20010509''. Now we can tell him to upgrade because it was fixed on 2001-05-20 or whatever. If he just said ``4.3-STABLE'', it wouldn't help much. Storing the date (without time of day) in that string would require some cron script somewhere (probably on the master CVS server) that updates the newvers.sh file daily. This might sound like a gross hack, but so far I haven't seen a better idea. > on second thoughts your sugestion is teh > sanest i've seen and personally wonder why it wasn't done like this > fron teh begining. Probably because of the gross hack that I described above. :-) But maybe someone else has a better idea how to achieve that. Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 12:58:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id DB3B437B422 for ; Wed, 11 Apr 2001 12:58:52 -0700 (PDT) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id PAA21457; Wed, 11 Apr 2001 15:57:11 -0400 (EDT) (envelope-from mwlucas) Date: Wed, 11 Apr 2001 15:57:11 -0400 From: Michael Lucas To: j mckitrick Cc: Jordan Hubbard , freebsd-stable@FreeBSD.ORG Subject: Re: new kernel book this summer? Message-ID: <20010411155711.A21410@blackhelicopters.org> References: <20010411151543.A68310@dogma.freebsd-uk.eu.org> <20010411101821Z.jkh@osd.bsdi.com> <20010411190849.A72702@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010411190849.A72702@dogma.freebsd-uk.eu.org>; from jcm@FreeBSD-uk.eu.org on Wed, Apr 11, 2001 at 07:08:50PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Best guess answers: The publisher doesn't know. The authors don't know. We don't know. Most publishers sit on manuscripts for an indefinite length of time. Publication date varies with perceived interest, the time of the publisher's current fiscal year, the printer schedules, and (God help us all) the cost of paper this month. Some technical books become obsolete before they actually get printed, and hence are never published. My publisher seems to have more of a clue than most in these regards, but I'm quite lucky. On Wed, Apr 11, 2001 at 07:08:50PM +0100, j mckitrick wrote: > On Wed, Apr 11, 2001 at 10:18:21AM -0700, Jordan Hubbard wrote: > | It's not a rumor, both Kirk McKusick and David Greenman (two of the > | authors) announced it at BSDCon, but it's been delayed. It's not sure > | at this stage just how long the book will take to get published. > > Ah, thanks. Best guess: before or after summer (June) ? > > > jm > -- > ------------------------------------------- > Jonathon McKitrick -- jcm@freebsd-uk.eu.org > Do not mistake lack of talent for genius > ------------------------------------------- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Michael Lucas mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 12:59:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dilbert.fcg.co.uk (dilbert.firstcallgroup.co.uk [194.203.69.166]) by hub.freebsd.org (Postfix) with ESMTP id A796237B42C for ; Wed, 11 Apr 2001 12:59:14 -0700 (PDT) (envelope-from pfrench@firstcallgroup.co.uk) Received: from pfrench by dilbert.fcg.co.uk with local (Exim 3.22 #1) id 14nQlg-000OcG-00 for freebsd-stable@FreeBSD.ORG; Wed, 11 Apr 2001 20:59:08 +0100 To: freebsd-stable@FreeBSD.ORG Subject: Re: Releases In-Reply-To: <200104111345.PAA67262@lurza.secnetix.de> Message-Id: From: Pete French Date: Wed, 11 Apr 2001 20:59:08 +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Maybe it would reduce confusion somewhat if people would > just stop saying ``4.1-stable'' etc. Those simply do not > exist. Best idea so far, and consequently change the bit in the handbook that implies that -STABLE is a bug fix to the last release, independent of the changes to making the next release. Tthats one of the major causes of confusions as it leads to people having an odd expectation of what the -STABLE actually is. -pete. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 12:59:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nova.fnal.gov (nova.fnal.gov [131.225.121.207]) by hub.freebsd.org (Postfix) with ESMTP id 1F39937B422 for ; Wed, 11 Apr 2001 12:59:43 -0700 (PDT) (envelope-from zingelman@fnal.gov) Received: from localhost (tez@localhost) by nova.fnal.gov (8.9.3+Sun/8.9.3) with ESMTP id OAA23991 for ; Wed, 11 Apr 2001 14:59:36 -0500 (CDT) X-Authentication-Warning: nova.fnal.gov: tez owned process doing -bs Date: Wed, 11 Apr 2001 14:59:36 -0500 (CDT) From: Tim Zingelman X-Sender: To: Subject: Re: make release broken with too many ports/distfiles... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Apr 2001, jack wrote: > Today David O'Brien wrote: > > How did you even get all (or most of) the distfiles in the chroot'ed > > /usr/ports/distfiles? > > If you don't figure out what distfiles are needed for > docproj-{whatever}, relocate them, and set this: > DOCDISTFILES?= ${.CURDIR}/../../ports/distfiles > > cp -rp ${DOCDISTFILES} ${CHROOTDIR}/usr/ports/distfiles > > will copy _every_ file, and subdirectory, you have in > /usr/ports/distfiles. Just to be sure this is clear, the above referenced 'cp -rp ...' is in /usr/src/release/Makefile. So the quick answer is figure out what subset of distfiles I need, put them someplace other than /usr/ports/distfiles & set DOCDISTFILES. Has anyone made this list of needed distfiles for a release build? Thanks, - Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 13:13:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from exosecure-exo-sc.exodus.net (exosecure.exodus.net [209.1.10.206]) by hub.freebsd.org (Postfix) with SMTP id 01E4037B424 for ; Wed, 11 Apr 2001 13:13:50 -0700 (PDT) (envelope-from Michael.Butler@exodus.net) Received: from exoserv.exodus.net by exosecure-exo-sc.exodus.net via smtpd (for hub.freebsd.org [216.136.204.18]) with SMTP; 11 Apr 2001 20:13:50 UT Received: from scl4mlims02.exodus.net ([10.255.39.51]) by exoserv.exodus.net (8.9.3/8.9.3) with ESMTP id NAA04850 for ; Wed, 11 Apr 2001 13:13:49 -0700 Received: by SCL4MLIMS02 with Internet Mail Service (5.5.2654.52) id <2T62MKTT>; Wed, 11 Apr 2001 13:13:48 -0700 Message-ID: From: Michael Butler To: "'freebsd-stable@FreeBSD.ORG'" Subject: RE: Releases Date: Wed, 11 Apr 2001 13:13:48 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2654.52) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Oliver Fromme [mailto:olli@secnetix.de] > Sent: Wednesday, 11 April 2001 15:49 > To: freebsd-stable@FreeBSD.ORG > Subject: Re: Releases > > > I would also vote for ``uname -r'' saying ``4-STABLE'' and > > > appending the date (similar to the snapshot naming), like > > > ``4-STABLE-20010509''. This is much more useful than > > > ``4.3-STABLE'', IMO. > That would be rather difficult. > Storing the date (without time of day) in that string would > require some cron script somewhere (probably on the master > CVS server) that updates the newvers.sh file daily. This > might sound like a gross hack, but so far I haven't seen a > better idea. Perhaps we could add something to either: i) snoop through the cvsup tags on the client to identify the most recently modified file and use it's datestamp as the '-stable-yymmdd' seed or ii) modify cvsup client to record most recently modified file in a more convenient place from which 'make buildworld' can retrieve the same, Michael Butler Managed Security Services Exodus Communications US Cell: +1-408-896-6689 Australian Cell: +61-413-571-819 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 13:23:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from seaholm.caamora.com.au (seaholm.caamora.com.au [203.7.226.5]) by hub.freebsd.org (Postfix) with ESMTP id 1A12237B423 for ; Wed, 11 Apr 2001 13:23:50 -0700 (PDT) (envelope-from jon@seaholm.caamora.com.au) Received: (from jon@localhost) by seaholm.caamora.com.au (8.11.1/8.11.1) id f3BKLHn09841; Thu, 12 Apr 2001 06:21:17 +1000 (EST) Message-ID: <20010412062117.11022@caamora.com.au> Date: Thu, 12 Apr 2001 06:21:17 +1000 From: jonathan michaels To: Oliver Fromme Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Releases References: <20010412052718.44835@caamora.com.au> <200104111948.VAA85126@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <200104111948.VAA85126@lurza.secnetix.de>; from Oliver Fromme on Wed, Apr 11, 2001 at 09:48:57PM +0200 Organisation: Caamora, PO Box 144, Rosebery NSW 1445 Australia Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 11, 2001 at 09:48:57PM +0200, Oliver Fromme wrote: > jonathan michaels wrote: > > On Wed, Apr 11, 2001 at 03:45:41PM +0200, Oliver Fromme wrote: > > > Maybe it would reduce confusion somewhat if people would > > > just stop saying ``4.1-stable'' etc. Those simply do not > > > exist. > > > > > > I would also vote for ``uname -r'' saying ``4-STABLE'' and > > > appending the date (similar to the snapshot naming), like > > > ``4-STABLE-20010509''. This is much more useful than > > > ``4.3-STABLE'', IMO. > > > > actually, given teh granularity of teh cvs system it might be > > worthwhile to add hh:mm .. > > That would be rather difficult. > > As far as I know, there is no automatic mechanism to store > the current date and time somewhere upon a cvs checkout or > update. i wasn't sure, i am sort of fiddling with setting up some sort of source code management system (html, freebsd system sources, tcp/ip network maintenance et al) and i'm starting to get a handle on how cvs/rcs/perforce sort of work. > Anyway, just the day should be sufficient in most cases. > Think of someone posting a well-known problem to -questions > or -stable, and giving his uname output which says, for > example, ``4-STABLE-20010509''. Now we can tell him to > upgrade because it was fixed on 2001-05-20 or whatever. yup, this is what i thought would be the best and given that i couldn't see how to get the granularity required to extract teh exactly required version and given that clocks are out and given that .. a whole lot of other things i endup with (as you rightly pointed out) settling on the date of the day of teh er, um whatever that part of teh 4-stable contium would be called. > If he just said ``4.3-STABLE'', it wouldn't help much. yes, this has always been my problem since i started with freebsd back at 2.0.5-release, i could never reconcile who cvs and its mechanisms for getting and making on call 'images' so to speak of either a file, a subsystem or even teh whole of freebsd at a given point in time (usually a given day, being identified by its date). > Storing the date (without time of day) in that string would > require some cron script somewhere (probably on the master > CVS server) that updates the newvers.sh file daily. This > might sound like a gross hack, but so far I haven't seen a > better idea. "gross hack", not advocating, most people have enough on thier plates already, i can see that getting what one needs from cvs for say releng_4 for say march 23rd 2001 ... then we all can call it freebsd 4-stable-23042001. instead of freebsd 4.?-stable as of sometime early this year and teh other time frame hack normally used. > > on second thoughts your sugestion is teh > > sanest i've seen and personally wonder why it wasn't done like this > > fron teh begining. > > Probably because of the gross hack that I described above. > :-) maybe for teh hours:minutes part but for teh stable-23042001 that (from what i've managed to gather so far, ok) should be ok. just a bit of a discription reorganising because it is muchly what we are using right now, ummm i think. > But maybe someone else has a better idea how to achieve > that. given the tools we use, i think this sounds like teh most likely cource of action to take (from my perspective) but, ok, your probably right. with regards and thanks jonathan -- ================================================================ Jonathan Michaels http://www.caamora.com.au PO Box 144, Rosebery, NSW 1445 suffering construction anxiety ============================================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 13:33:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from news.IAEhv.nl (news.iae.nl [212.61.26.37]) by hub.freebsd.org (Postfix) with ESMTP id 3C7D537B42C for ; Wed, 11 Apr 2001 13:33:50 -0700 (PDT) (envelope-from Arjan.deVet@adv.iae.nl) Received: (from uucp@localhost) by news.IAEhv.nl (8.9.1/8.9.1) with IAEhv.nl id WAA14621; Wed, 11 Apr 2001 22:33:49 +0200 (MET DST) Received: by adv.devet.org (Postfix, from userid 100) id DD1283E1D; Wed, 11 Apr 2001 22:33:35 +0200 (CEST) Date: Wed, 11 Apr 2001 22:33:35 +0200 To: l.ipfilter@rtci.com Cc: stable@freebsd.org Subject: Re: Broken rc.network for ipfilter w/ PR (was Re: How to install ipfilter..) Message-ID: <20010411223335.A1195@adv.devet.org> References: <5.1.0.12.2.20010407230631.00a688c0@mail.vons.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Newsgroups: list.freebsd.stable In-Reply-To: <20010408151025.A34209@rtci.com> Organization: Eindhoven, the Netherlands From: Arjan.deVet@adv.iae.nl (Arjan de Vet) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20010408151025.A34209@rtci.com> you write: >> I added the four commands above to /etc/rc.network instead of using >> FreeBSD's ipfilter support through rc.conf mechanism (it assumes that >> ipfilter is built into the kernel) > > There is a PR with a patch sitting on this rc.network fuckup > (oversight) that I'd really love to see committed for 4.3-RELEASE, > but who knows if that's possible with the given timeline. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=26275 > > I completely missed a previous PR on the same issue, but this one > has a patch that will work no matter where $ipfilter_program is set > to (hack), rather then hardcoding an ipfstat location. > > Patch also fixes it so that ipf.rules doesn't have to exist if your > just setting up a NAT. There's another issue that needs fixing: ipmon should be started before ipf. Arjan -- Arjan de Vet, Eindhoven, The Netherlands URL: http://www.iae.nl/users/devet/ for PGP key: finger devet@iae.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 13:53:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 705C737B423; Wed, 11 Apr 2001 13:53:40 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f3BKrV888277; Wed, 11 Apr 2001 13:53:31 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: stable@freebsd.org Cc: developers@freebsd.org Subject: 4.3RC3 is now available for FTP X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010411135331V.jkh@osd.bsdi.com> Date: Wed, 11 Apr 2001 13:53:31 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 22 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now available from: ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/4.3-RC3/ ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/4.3rc3-install.iso Please test this as seriously as you can. This has the compiler fixes rolled up as well as a number of recently reported -stable issues fixed and it will also be the last RC image until -release, which is currently scheduled for April 15th, barring any unforseen delays. That said, I will say right now that if the situation does not look very close to perfect by April 15th, I will consider extending the release date by another week or so (but no longer than that). This is an important release for FreeBSD and we can take a little extra time to do it right. Thanks are also due to everyone who's worked so much overtime to get needed fixes and enhancements into -stable during this code freeze. I think this release will represent a good balance of necessary new features and very conservative incremental progress! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 14:12: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 2F7F837B422 for ; Wed, 11 Apr 2001 14:12:03 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id HAA23571; Thu, 12 Apr 2001 07:11:52 +1000 (EST) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37640) with ESMTP id <01K2AY2PH1HSRW1DZI@cim.alcatel.com.au>; Thu, 12 Apr 2001 07:11:50 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f3BLBmK04712; Thu, 12 Apr 2001 07:11:48 +1000 (EST envelope-from jeremyp) Content-return: prohibited Date: Thu, 12 Apr 2001 07:11:48 +1000 From: Peter Jeremy Subject: Re: CTM not updated since Mar 13 In-reply-to: ; from christer.moller@eds.com on Wed, Apr 11, 2001 at 11:21:00AM +0200 To: "B. Christer Moller" Cc: freebsd-stable@FreeBSD.ORG Mail-Followup-To: "B. Christer Moller" , freebsd-stable@FreeBSD.ORG Message-id: <20010412071147.W66243@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-Apr-11 11:21:00 +0200, "B. Christer Moller" wrote: >I know you are all very busy with the upcoming FreeBSD-4.3 RELEASE, but for >us who uses CTM to update our sources there hasn't been any updates since 13 >Mar. Is this meant to be like this or just a problem? If you're relying on CTM, you should really be reading ctm-announce. The machine hosting the CTM generation lost net connectivity without notice. A new host has been found and CTM generation was re-enabled a couple of days ago. I don't see the stable sources, but a cvs-cur delta was posted on 9th April and I thought it was the last to be generated. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 14:14: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mta07-svc.ntlworld.com (mta07-svc.ntlworld.com [62.253.162.47]) by hub.freebsd.org (Postfix) with ESMTP id 962EC37B422 for ; Wed, 11 Apr 2001 14:13:59 -0700 (PDT) (envelope-from jon@witchspace.com) Received: from witchspace.com ([213.105.80.222]) by mta07-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20010411211354.SCJL285.mta07-svc.ntlworld.com@witchspace.com>; Wed, 11 Apr 2001 22:13:54 +0100 Message-ID: <3AD4C91B.FEC4C498@witchspace.com> Date: Wed, 11 Apr 2001 22:14:03 +0100 From: Jonathan Belson Organization: Jon's Place X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Kal Torak Cc: FreeBSD-stable Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: <3AD48782.2CEAE87B@quake.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kal Torak wrote: > nVidia cards are really the ONLY choice to buy now... Not that Im complaining, > they are good cards, we just need some support for the more recent ones! > Since I cant find anything for the GeForce line... Let alone GeForce2, and the > GeForce3 series (are they going to call it that?) will be on sale soon... > > If there is enough interest from us they should be willing to make ports to > FreeBSD.. I mean they support BeOS, how many people even use that, let alone > have nVidia cards? Surly we could match them in numbers! (There were over one million recorded downloads of BeOS free edition when it was made available.) The nVidia drivers were written by a Be employee and they support 2d only. -- C-YA Jon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 14:25:28 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp-relay.rtci.com (calamari-ex.arch.rtci.com [208.11.246.4]) by hub.freebsd.org (Postfix) with ESMTP id 885D137B422 for ; Wed, 11 Apr 2001 14:25:24 -0700 (PDT) (envelope-from jhopkins@rtci.com) Received: from rtci.com (hoodlum [208.11.244.8]) by smtp-relay.rtci.com (Postfix) with ESMTP id BF0CE1C99D for ; Wed, 11 Apr 2001 17:25:23 -0400 (EDT) Message-ID: <3AD4CBC3.F3E79AFC@rtci.com> Date: Wed, 11 Apr 2001 17:25:23 -0400 From: Jeremy Hopkins Organization: Internet Commerce Corp. (RTCI division) X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-BETA i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Problems with 3c905B and 4.3-RC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have just installed a FreeBSD 4.1.1-RELEASE box. I had to start there as my 3c905B card did not show in an ifconfig -a using newer floppies so I reverted to 4.1.1 I got the box up and running and did a cvsup to 4.3-RC, made/installed world and kernel just fine. However I notice I have no network interface at xl0 like I did before the reboot into 4.3-RC. xl0 shows up in dmesg but I get error messages along with it. xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 10 at device 15.0 on pci0 xl0: couldn't map ports/memory device_probe_and_attach: xl0 attach returned 6 I had also had the same error messages about my sound card pcm0. I have removed the sound card to eliminate the possibility these are conflicting, and the dmesg below is without the sound card in the system. It appears there was some talk about this back in Sept. 2000 in the -current list, but I can't seem to find a resolution on it. Thanks in advance, Jeremy -- Jeremy Hopkins Systems Administrator www.icc.net www.rtci.com For those who like this sort of thing, this is the sort of thing they like. -- Abraham Lincoln below is copy of full dmesg output- ------------------------------ Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.3-RC #0: Wed Apr 11 18:50:15 GMT 2001 root@shadow.ghettoweb.net:/usr/obj/usr/src/sys/GUNSHOT Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (497.84-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383f9ff real memory = 134217728 (131072K bytes) avail memory = 126545920 (123580K bytes) Preloaded elf kernel "kernel" at 0xc03e1000. 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 pci1: at 0.0 irq 11 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1000-0x100f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0x1020-0x103f irq 9 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered chip1: port 0x7000-0x700f at device 7.3 on pci0 xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 10 at device 15.0 on pci0 xl0: couldn't map ports/memory device_probe_and_attach: xl0 attach returned 6 fdc0: at port 0x3f0-0x3f5,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,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 IPsec: Initialized Security Association Processing. ad0: 9787MB [19885/16/63] at ata0-master UDMA33 ad1: 9787MB [19885/16/63] at ata0-slave UDMA33 acd0: CDROM at ata1-master using PIO4 afd0: 96MB [96/64/32] at ata1-slave using PIO3 Mounting root from ufs:/dev/ad0s1a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 14:28:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from flounder.jimking.net (flounder.jimking.net [209.205.176.18]) by hub.freebsd.org (Postfix) with ESMTP id D174237B422 for ; Wed, 11 Apr 2001 14:28:36 -0700 (PDT) (envelope-from jim@jimking.net) Received: from jking (jking.lgc.com [134.132.76.82]) (authenticated) by flounder.jimking.net (8.11.3/8.11.2) with ESMTP id f3BLSVD01141 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO); Wed, 11 Apr 2001 16:28:32 -0500 (CDT) (envelope-from jim@jimking.net) Message-ID: <01f901c0c2ce$5bb4a1f0$524c8486@jking> From: "Jim King" To: "Jeremy Hopkins" , References: <3AD4CBC3.F3E79AFC@rtci.com> Subject: Re: Problems with 3c905B and 4.3-RC Date: Wed, 11 Apr 2001 16:28:31 -0500 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.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jeremy Hopkins" wrote: > I have just installed a FreeBSD 4.1.1-RELEASE box. I had to start there > as my 3c905B card did not show in an ifconfig -a using newer floppies so > I reverted to 4.1.1 I got the box up and running and did a cvsup to > 4.3-RC, made/installed world and kernel just fine. However I notice I > have no network interface at xl0 like I did before the reboot into > 4.3-RC. > > xl0 shows up in dmesg but I get error messages along with it. > > xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 10 at device 15.0 on pci0 > xl0: couldn't map ports/memory > device_probe_and_attach: xl0 attach returned 6 > > I had also had the same error messages about my sound card pcm0. I have > removed the sound card to eliminate the possibility these are > conflicting, and the dmesg below is without the sound card in the > system. It appears there was some talk about this back in Sept. 2000 in > the -current list, but I can't seem to find a resolution on it. I get this when I have the BIOS option "PnP OS" set to "yes". Try setting that option to "no". Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 14:44: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp-relay.rtci.com (calamari-ex.arch.rtci.com [208.11.246.4]) by hub.freebsd.org (Postfix) with ESMTP id 269C837B423 for ; Wed, 11 Apr 2001 14:43:57 -0700 (PDT) (envelope-from jhopkins@rtci.com) Received: from rtci.com (hoodlum [208.11.244.8]) by smtp-relay.rtci.com (Postfix) with ESMTP id 9E7F81C99A; Wed, 11 Apr 2001 17:43:56 -0400 (EDT) Message-ID: <3AD4D01C.E96027A4@rtci.com> Date: Wed, 11 Apr 2001 17:43:56 -0400 From: Jeremy Hopkins Organization: Internet Commerce Corp. (RTCI division) X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-BETA i386) X-Accept-Language: en MIME-Version: 1.0 To: Jim King Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Problems with 3c905B and 4.3-RC References: <3AD4CBC3.F3E79AFC@rtci.com> <01f901c0c2ce$5bb4a1f0$524c8486@jking> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I usually make sure that pnp OS is off, but in this case it was on. This fixed it. Thanks a great deal. Jeremy Jim King wrote: > > "Jeremy Hopkins" wrote: > > > I have just installed a FreeBSD 4.1.1-RELEASE box. I had to start there > > as my 3c905B card did not show in an ifconfig -a using newer floppies so > > I reverted to 4.1.1 I got the box up and running and did a cvsup to > > 4.3-RC, made/installed world and kernel just fine. However I notice I > > have no network interface at xl0 like I did before the reboot into > > 4.3-RC. > > > > xl0 shows up in dmesg but I get error messages along with it. > > > > xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 10 at device 15.0 on pci0 > > xl0: couldn't map ports/memory > > device_probe_and_attach: xl0 attach returned 6 > > > > I had also had the same error messages about my sound card pcm0. I have > > removed the sound card to eliminate the possibility these are > > conflicting, and the dmesg below is without the sound card in the > > system. It appears there was some talk about this back in Sept. 2000 in > > the -current list, but I can't seem to find a resolution on it. > > I get this when I have the BIOS option "PnP OS" set to "yes". Try setting > that option to "no". > > Jim > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Jeremy Hopkins Systems Administrator www.icc.net www.rtci.com For those who like this sort of thing, this is the sort of thing they like. -- Abraham Lincoln To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 14:44:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id 083EC37B422 for ; Wed, 11 Apr 2001 14:44:57 -0700 (PDT) (envelope-from juha@saarinen.org) Received: from dendennis.saarinen.org ([192.168.1.2] helo=dendennis) by vimfuego.saarinen.org with smtp (Exim 3.22 #1 (Red Hack)) id 14nSPq-0003gP-01; Thu, 12 Apr 2001 09:44:42 +1200 From: "Juha Saarinen" To: "Kal Torak" , "The Hermit Hacker" Cc: "Jonathan Belson" , "FreeBSD-stable" Subject: RE: nVidia Cards /w FreeBSD (3D Acceleration) Date: Thu, 12 Apr 2001 09:44:20 +1200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal In-Reply-To: <3AD48782.2CEAE87B@quake.com.au> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :: If there is enough interest from us they should be willing to :: make ports to :: FreeBSD.. I mean they support BeOS, how many people even use :: that, let alone :: have nVidia cards? Surly we could match them in numbers! Check the Utah-GLX and other mailing lists on this issue. It might be possible to get Nvidia to port the binary kernel driver for Linux to FreeBSD (provided that it's possible to use such drivers under FreeBSD, I don't know), but they ain't gonna release the full specs. If I understand it right, Nvidia's reasoning for this is that if they give out the full specs to Open Source developers without an NDA, the clone makers would copy their the specs in an instant and they might as well shut up shop and go home. Before you lambast Nvidia for wanting to keep its IP under wraps, it appears that none of the other video card makers (ATI, Matrox) have handed over their "crown jewels" to Open Source developers. Nvidia is at least providing an optimised driver for its cards -- Matrox and ATI haven't, but they seem to be supporting Red Hat's Precision Insight offshoot, which is providing the DRI for XFree86. -- Juha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 14:54:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from rhymer.cogsci.ed.ac.uk (rhymer.cogsci.ed.ac.uk [129.215.144.8]) by hub.freebsd.org (Postfix) with ESMTP id 7ED2237B424 for ; Wed, 11 Apr 2001 14:54:10 -0700 (PDT) (envelope-from richard@cogsci.ed.ac.uk) Received: from banks.cogsci.ed.ac.uk (banks [129.215.144.55]) by rhymer.cogsci.ed.ac.uk (8.9.3/8.9.3) with ESMTP id WAA00194; Wed, 11 Apr 2001 22:53:54 +0100 (BST) Received: (from richard@localhost) by banks.cogsci.ed.ac.uk (8.9.3+Sun/8.9.3) id WAA00825; Wed, 11 Apr 2001 22:53:45 +0100 (BST) Date: Wed, 11 Apr 2001 22:53:45 +0100 (BST) Message-Id: <200104112153.WAA00825@banks.cogsci.ed.ac.uk> From: Richard Tobin Subject: RE: nVidia Cards /w FreeBSD (3D Acceleration) To: "Juha Saarinen" , "Kal Torak" , "The Hermit Hacker" In-Reply-To: Juha Saarinen's message of Thu, 12 Apr 2001 09:44:20 +1200 Organization: just say no Cc: "Jonathan Belson" , "FreeBSD-stable" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Before you lambast Nvidia for wanting to keep its IP > under wraps, it appears that none of the other video card makers (ATI, > Matrox) have handed over their "crown jewels" to Open Source developers. > Nvidia is at least providing an optimised driver for its cards -- Matrox and > ATI haven't So how come we haven't even got the XVideo extension available on GeForce cards, unlike ATI and Matrox? Sounds fair to lambast NVidia to me. -- Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 14:58:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailout06.sul.t-online.com (mailout06.sul.t-online.com [194.25.134.19]) by hub.freebsd.org (Postfix) with ESMTP id D870637B423 for ; Wed, 11 Apr 2001 14:58:14 -0700 (PDT) (envelope-from sven.huster@mailsurf.com) Received: from fwd05.aul.t-online.de by mailout06.sul.t-online.com with smtp id 14nScw-0001bk-01; Wed, 11 Apr 2001 23:58:14 +0200 Received: from venus.mailsurf.com (320051988339-0001@[62.158.242.102]) by fmrl05.sul.t-online.com with esmtp id 14nScg-0jAh7YC; Wed, 11 Apr 2001 23:57:58 +0200 Message-Id: <5.0.2.1.0.20010411234537.037a9c70@mx01.mailsurf.com> X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Wed, 11 Apr 2001 23:58:32 +0200 To: freebsd-stable@freebsd.org From: Sven Huster Subject: error with mfs Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Sender: 320051988339-0001@t-dialin.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, i installed a diskless machine just after reboot i did: login: root Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. test# top -bS last pid: 355; load averages: 0.12, 0.03, 0.01 up 0+00:00:52 22:55:07 22 processes: 1 running, 21 sleeping Mem: 6392K Active, 5032K Inact, 7564K Wired, 160K Cache, 6448K Buf, 195M Free Swap: PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 318 root 2 0 2152K 1364K select 0:00 0.00% 0.00% sshd 350 root 18 0 1304K 904K pause 0:00 0.00% 0.00% csh 274 root 2 0 916K 552K select 0:00 0.00% 0.00% syslogd 196 root 10 0 33448K 1364K mfsidl 0:00 0.00% 0.00% mount_mfs 174 root 10 0 1668K 1128K mfsidl 0:00 0.00% 0.00% mount_mfs 313 root 2 0 1044K 724K select 0:00 0.00% 0.00% inetd 355 root 28 0 1856K 884K RUN 0:00 0.00% 0.00% top 1 root 10 0 528K 316K wait 0:00 0.00% 0.00% init 278 root 2 -12 1244K 776K select 0:00 0.00% 0.00% ntpd 315 root 10 0 968K 684K nanslp 0:00 0.00% 0.00% cron 282 root 2 0 908K 588K select 0:00 0.00% 0.00% ypbind 280 daemon 2 0 936K 624K select 0:00 0.00% 0.00% portmap 288 root 10 0 208K 76K nfsidl 0:00 0.00% 0.00% nfsiod 75 root 2 0 516K 348K select 0:00 0.00% 0.00% dhclient 5 root 18 0 0K 0K syncer 0:00 0.00% 0.00% syncer 2 root -18 0 0K 0K psleep 0:00 0.00% 0.00% pagedaemon 0 root -18 0 0K 0K sched 0:00 0.00% 0.00% swapper 4 root -18 0 0K 0K psleep 0:00 0.00% 0.00% bufdaemon test# mount /dev/md0c on / (ufs, local) mfs:174 on /conf/etc (mfs, asynchronous, local) /conf/etc on /etc (null, local) procfs on /proc (procfs, local) mfs:196 on /var (mfs, asynchronous, local) /var/tmp on /tmp (null, local) 10.254.0.3:/vol/vol0/pxeroot/usr on /usr (nfs, read-only) 10.254.0.3:/vol/vol0/home on /home (nfs) test# df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/md0c 34687 23109 11578 67% / mfs:174 959 816 67 92% /conf/etc /conf/etc 959 816 67 92% /etc procfs 4 4 0 100% /proc mfs:196 31743 58 29146 0% /var /var/tmp 31743 58 29146 0% /tmp 10.254.0.3:/vol/vol0/pxeroot/usr 127105232 50518528 76586704 40% /usr 10.254.0.3:/vol/vol0/home 127105232 50518528 76586704 40% /home test# uname -a FreeBSD test.mailsurf.com 4.3-BETA FreeBSD 4.3-BETA #1: Fri Mar 9 00:03:34 GMT 2001 root@mnt01.mailsurf.com:/usr/obj/usr/src/sys/MAILSURF i386 test# dd if=/dev/zero of=/tmp/test bs=1m count=10 Fatal trap 12: page fault while in kernel mode fault virtual address = 0xc4 fault code = supervisor read, page not present instruction pointer = 0x8:0xc4 stack pointer = 0x10:0xd15e2c64 frame pointer = 0x10:0xd15e2cf4 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 = 196 (mount_mfs) interrupt mask = none kernel: type 12 trap, code=0 Stopped at 0xc4: Fatal trap 12: page fault while in kernel mode fault virtual address = 0xc4 fault code = supervisor read, page not present instruction pointer = 0x8:0xc024c370 stack pointer = 0x10:0xd15e2acc frame pointer = 0x10:0xd15e2ad0 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 = 196 (mount_mfs) interrupt mask = none kernel: type 12 trap, code=0 db> error is reproduceable. root fs is a mfs root loaded via nfs, machine boot via pxe machine config according to rc.diskless* no swap configure, but should be not a problem here. any suggestions? regards Sven Huster Senior IT Systems Administrator *BSD, Linux, Solaris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 15: 4: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 3C88737B423 for ; Wed, 11 Apr 2001 15:04:04 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id ecwaaaaa for ; Thu, 12 Apr 2001 08:03:29 +1000 Message-ID: <3AD4D5B9.28531597@quake.com.au> Date: Thu, 12 Apr 2001 08:07:53 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Richard Tobin Cc: Juha Saarinen , The Hermit Hacker , Jonathan Belson , FreeBSD-stable Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: <200104112153.WAA00825@banks.cogsci.ed.ac.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Tobin wrote: > > > Before you lambast Nvidia for wanting to keep its IP > > under wraps, it appears that none of the other video card makers (ATI, > > Matrox) have handed over their "crown jewels" to Open Source developers. > > Nvidia is at least providing an optimised driver for its cards -- Matrox and > > ATI haven't > > So how come we haven't even got the XVideo extension available on > GeForce cards, unlike ATI and Matrox? Sounds fair to lambast NVidia > to me. If nVidia wont provide enough info for developers to make drivers, then they will just have to make ports for ever system! Ok, so they wont do that, but we only need to convince them to make a port to FreeBSD :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 15: 4:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id 96EB937B422 for ; Wed, 11 Apr 2001 15:04:11 -0700 (PDT) (envelope-from juha@saarinen.org) Received: from dendennis.saarinen.org ([192.168.1.2] helo=dendennis) by vimfuego.saarinen.org with smtp (Exim 3.22 #1 (Red Hack)) id 14nSiU-0003k5-00; Thu, 12 Apr 2001 10:03:58 +1200 From: "Juha Saarinen" To: "Kal Torak" , "Michael Nottebrock" Cc: "The Hermit Hacker" , "Jonathan Belson" , "FreeBSD-stable" Subject: RE: nVidia Cards /w FreeBSD (3D Acceleration) Date: Thu, 12 Apr 2001 10:03:37 +1200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal In-Reply-To: <3AD4AB28.EA342EC0@quake.com.au> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :: They must provide the win32 source to the card manufacturers, :: since nVidia :: based cards often come with drivers supplied by the company... Anyway, :: whatever the case we need those drivers for FreeBSD :) Sign an NDA, and you might get the specs as well.... -- Juha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 15: 4:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from c001.snv.cp.net (c001-h014.c001.snv.cp.net [209.228.32.128]) by hub.freebsd.org (Postfix) with SMTP id 68E5B37B422 for ; Wed, 11 Apr 2001 15:04:25 -0700 (PDT) (envelope-from scott@sawilson.org) Received: (cpmta 22582 invoked from network); 11 Apr 2001 15:04:25 -0700 Date: 11 Apr 2001 15:04:25 -0700 Message-ID: <20010411220425.22581.cpmta@c001.snv.cp.net> X-Sent: 11 Apr 2001 22:04:25 GMT Received: from [208.165.47.219] by mail.sawilson.org with HTTP; 11 Apr 2001 15:04:25 PDT Content-Type: text/plain Content-Disposition: inline Mime-Version: 1.0 To: freebsd-stable@freebsd.org From: scott@sawilson.org X-Mailer: Web Mail 3.7.1.9 Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 April 2001, Kal Torak wrote: > > Michael Nottebrock wrote: > > > > ----- Original Message ----- > > From: "Kal Torak" > > To: "The Hermit Hacker" > > Cc: "Jonathan Belson" ; "FreeBSD-stable" > > > > Sent: Wednesday, April 11, 2001 6:34 PM > > Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) > > > > > [...] > > > nVidia cards are really the ONLY choice to buy now... Not that Im > > complaining, > > > they are good cards, we just need some support for the more recent > > ones! --snip-- Hello, I feel your pain, as I'm sure others do on the list. You aren't going to be satisfied with a "there is nothing we can do about this because" type answer. To you it sounds defeatist and like an excuse to do nothing. I agree. I have an idea I wanted to run by the list. What if someone were to set up a simple email cgi with a form letter in the nature of: Dear nVidia, My name is _______. I am sending you this email because I use an operating system called FreeBSD(http://www.freebsd.org) and there does not appear to be driver support for your product because of a business decision you have made. Currently I, Select One: *Own one of your _______ cards *Own a _______ which is a compeditors card and would like to use one of your ________ cards instead *Would like to use one of your _____ cards when it is supported Please consider developing your own drivers for FreeBSD, opening the source code to your drivers, or releasing the hardware specifications to your hardware so eager FreeBSD coders can make drivers for our operating system. You'd be making a rapidly growing culture of computer users that like playing games and doing high end graphics work very happy. Very many of us would be very happy to use your superior products with our operating system of choice. Thank you. Joe FreeBSD User Have them numbered in the subject so nVidia has an instant idea how many people are effected. It would be important that we don't sound like depraved zealots like some other operating system fans have in the past when doing a letter writing campaign. Any thoughts? I know that I'm worried I won't be able to play Doom3 when it finally comes out. I'm a big fan of the ID software series. Speed with tribes2 would be nice also. Please let me know what you think. I know I'd gladly do my best to set something like this up, or visit the URL and take the time to fill in the blanks if someone else posts it. I'm sure someone is going to say it won't do any good, but I don't think it could hurt. Doing nothing always seems to have this way of looking a lot like doing nothing. Best Regards, Scott Alan Wilson http://sawilson.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 15:13:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nothing-going-on.demon.co.uk (pc-62-31-42-141-hy.blueyonder.co.uk [62.31.42.141]) by hub.freebsd.org (Postfix) with ESMTP id 08F4F37B424; Wed, 11 Apr 2001 15:13:42 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id f3BLpvb72910; Wed, 11 Apr 2001 22:51:57 +0100 (BST) (envelope-from nik) Date: Wed, 11 Apr 2001 22:51:57 +0100 From: Nik Clayton To: Mike Meyer Cc: Nik Clayton , stable@freebsd.org Subject: Re: Releases Message-ID: <20010411225157.A72900@canyon.nothing-going-on.org> References: <5.0.2.1.0.20010409111054.00b18008@pop.schulte.org> <20010410120701.A749@canyon.nothing-going-on.org> <15059.502.493117.364068@guru.mired.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="VS++wcV0S1rZb1Fb" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15059.502.493117.364068@guru.mired.org>; from mwm@mired.org on Tue, Apr 10, 2001 at 07:52:06AM -0500 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --VS++wcV0S1rZb1Fb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 10, 2001 at 07:52:06AM -0500, Mike Meyer wrote: > Nik Clayton types: > > I don't see any way in which someone could start running -current > > without seeing that warning, or the equivalent warnings in the Handbook. >=20 > More than once people have shown up on -questions running -current > because they just grabbed the "standard" supfile. Which gets them > -current :-(. Which was why I suggested that it standard-supfile get > the branch being run. Done. 'standard-supfile' on RELENG_4 will now pull down RELENG_4 by default. When 4.3 is released, 'standard-supfile' for that release will point=20 to the 4.3-bugfix branch. N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- --VS++wcV0S1rZb1Fb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjrU0fkACgkQk6gHZCw343VUhgCfSX//6U+EareRIPyCXIZpIF1H OFMAnRPctjmGFxPFZfXe2JDpAS1BXkRd =wjBW -----END PGP SIGNATURE----- --VS++wcV0S1rZb1Fb-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 15:17:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id BB66C37B422 for ; Wed, 11 Apr 2001 15:17:19 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id kcwaaaaa for ; Thu, 12 Apr 2001 08:16:49 +1000 Message-ID: <3AD4D8DA.77E28CB6@quake.com.au> Date: Thu, 12 Apr 2001 08:21:14 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: scott@sawilson.org Cc: freebsd-stable@freebsd.org Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: <20010411220425.22581.cpmta@c001.snv.cp.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well Im all for it! Its a lot better than sitting back and saying, oh they wont give us the source, they wont give us the technical specs, they are nasty people etc, etc, etc. :) Now... We just need someone with experiance to run this thing... > I feel your pain, as I'm sure others do on the list. You aren't going to be satisfied with a "there is nothing we can do about this because" type answer. To you it sounds defeatist and like an excuse to do nothing. I agree. I have an idea I wanted to run by the list. > > What if someone were to set up a simple email cgi with a form letter in the nature of: > > Dear nVidia, > > My name is _______. I am sending you this email because I use an operating system called FreeBSD(http://www.freebsd.org) and there does not appear to be driver support for your product because of a business decision you have made. > > Currently I, > > Select One: > > *Own one of your _______ cards > > *Own a _______ which is a compeditors card and would like to use one of your ________ cards instead > > *Would like to use one of your _____ cards when it is supported > > Please consider developing your own drivers for FreeBSD, opening the source code to your drivers, or releasing the hardware specifications to your hardware so eager FreeBSD coders can make drivers for our operating system. You'd be making a rapidly growing culture of computer users that like playing games and doing high end graphics work very happy. Very many of us would be very happy to use your superior products with our operating system of choice. > > Thank you. > > Joe FreeBSD User > > Have them numbered in the subject so nVidia has an instant idea how many people are effected. It would be important that we don't sound like depraved zealots like some other operating system fans have in the past when doing a letter writing campaign. > > Any thoughts? I know that I'm worried I won't be able to play Doom3 when it finally comes out. I'm a big fan of the ID software series. Speed with tribes2 would be nice also. Please let me know what you think. I know I'd gladly do my best to set something like this up, or visit the URL and take the time to fill in the blanks if someone else posts it. I'm sure someone is going to say it won't do any good, but I don't think it could hurt. Doing nothing always seems to have this way of looking a lot like doing nothing. > > Best Regards, > > Scott Alan Wilson > http://sawilson.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 15:18:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from c000.sfo.cp.net (c004-h017.c004.snv.cp.net [209.228.33.81]) by hub.freebsd.org (Postfix) with SMTP id 4324637B42C for ; Wed, 11 Apr 2001 15:18:13 -0700 (PDT) (envelope-from psglenn@uswestmail.net) Received: (cpmta 25747 invoked from network); 11 Apr 2001 15:18:12 -0700 Date: 11 Apr 2001 15:18:12 -0700 Message-ID: <20010411221812.25746.cpmta@c000.sfo.cp.net> X-Sent: 11 Apr 2001 22:18:12 GMT Received: from [64.40.43.76] by mail.uswestmail.net with HTTP; 11 Apr 2001 15:18:12 PDT Content-Type: text/plain Content-Disposition: inline Mime-Version: 1.0 To: bruce@zuhause.org From: psglenn@uswestmail.net Cc: freebsd-stable@FreeBSD.org X-Mailer: Web Mail 3.7.1.9 Subject: Re: silo overflows Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >psglenn@uswestmail.net writes: > > I've been getting only a few silo overflows (about six) since I last posted > > about this problem. > > The flow control may have been the issue as I've downloaded 1.98TB since then. > > Three iso images. > > I'd like to change to kernel ppp with ipnat and ipfilter to see if that makes > > a difference. >I don't think the USR 56k sportster has been in production long enough to for you to transmit 2 terabytes on one! Sorry that would be 1.98GB. at my download rates 1.98TB would get me 5 to 15 years. P S Glenn That's all for now. Signup for your free USWEST.mail Email account http://www.uswestmail.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 15:20:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.unixathome.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id C2C4637B422; Wed, 11 Apr 2001 15:20:28 -0700 (PDT) (envelope-from dan@langille.org) Received: from wocker (root@ns1.unixathome.org [192.168.0.20]) by ns1.unixathome.org (8.11.3/8.11.3) with ESMTP id f3BMKPe96220; Thu, 12 Apr 2001 10:20:26 +1200 (NZST) (envelope-from dan@langille.org) Message-Id: <200104112220.f3BMKPe96220@ns1.unixathome.org> From: "Dan Langille" Organization: novice in training To: Nik Clayton Date: Wed, 11 Apr 2001 18:20:18 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Releases Reply-To: dan@langille.org Cc: stable@FreeBSD.ORG In-reply-to: <20010411225157.A72900@canyon.nothing-going-on.org> References: <15059.502.493117.364068@guru.mired.org>; from mwm@mired.org on Tue, Apr 10, 2001 at 07:52:06AM -0500 X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11 Apr 2001, at 22:51, Nik Clayton wrote: > Done. Did I miss the commit? When was this done? > 'standard-supfile' on RELENG_4 will now pull down RELENG_4 by default. When > 4.3 is released, 'standard-supfile' for that release will point to the > 4.3-bugfix branch. Thank you. -- Dan Langille pgpkey - finger dan@unixathome.org | http://unixathome.org/finger.php got any work? I'm looking for some. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 15:30:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id 3A04537B43E for ; Wed, 11 Apr 2001 15:30:08 -0700 (PDT) (envelope-from juha@saarinen.org) Received: from dendennis.saarinen.org ([192.168.1.2] helo=dendennis) by vimfuego.saarinen.org with smtp (Exim 3.22 #1 (Red Hack)) id 14nT7b-0003o8-00; Thu, 12 Apr 2001 10:29:55 +1200 From: "Juha Saarinen" To: "Richard Tobin" , "Kal Torak" , "The Hermit Hacker" Cc: "Jonathan Belson" , "FreeBSD-stable" Subject: RE: nVidia Cards /w FreeBSD (3D Acceleration) Date: Thu, 12 Apr 2001 10:29:33 +1200 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.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal In-Reply-To: <200104112153.WAA00825@banks.cogsci.ed.ac.uk> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :: So how come we haven't even got the XVideo extension available on :: GeForce cards, unlike ATI and Matrox? Sounds fair to lambast NVidia :: to me. Is it missing? -- Juha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 15:37:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from moya.lambermont.dyndns.org (e165253.upc-e.chello.nl [213.93.165.253]) by hub.freebsd.org (Postfix) with ESMTP id 87A4B37B424 for ; Wed, 11 Apr 2001 15:37:50 -0700 (PDT) (envelope-from hans@lambermont.dyndns.org) Received: by moya.lambermont.dyndns.org (Postfix, from userid 1001) id 10E533640A; Thu, 12 Apr 2001 00:37:47 +0200 (CEST) Date: Thu, 12 Apr 2001 00:37:47 +0200 To: freebsd-stable@freebsd.org Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) Message-ID: <20010412003746.A51230@moya.lambermont.dyndns.org> References: <20010411220425.22581.cpmta@c001.snv.cp.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010411220425.22581.cpmta@c001.snv.cp.net>; from scott@sawilson.org on Wed, Apr 11, 2001 at 03:04:25PM -0700 From: hans@lambermont.dyndns.org (H) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG scott@sawilson.org wrote: > What if someone were to set up a simple email cgi with a form > letter in the nature of: > Dear nVidia, snip -good letter proto deleted- > Have them numbered in the subject so nVidia has an instant idea how > many people are effected. It would be important that we don't sound > like depraved zealots like some other operating system fans have in > the past when doing a letter writing campaign. Interesting, has a letter writing campaign like this worked before for graphics driver issues ? Is so we should go for it ! regards, Hans Lambermont -- http://hans.mypage.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 16: 5:28 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ghostwheel.tribble.net (ghostwheel.tribble.net [206.124.26.66]) by hub.freebsd.org (Postfix) with ESMTP id 3112837B423 for ; Wed, 11 Apr 2001 16:05:22 -0700 (PDT) (envelope-from tribble@ghostwheel.tribble.net) Received: (from tribble@localhost) by ghostwheel.tribble.net (8.11.1/8.11.1) id f3BN5JB28912; Wed, 11 Apr 2001 17:05:19 -0600 (MDT) (envelope-from tribble) Date: Wed, 11 Apr 2001 17:05:19 -0600 From: Paul To: The Hermit Hacker Cc: FreeBSD-stable Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) Message-ID: <20010411170519.B28596@tribble.net> References: <3AD46C19.FC1AFB93@quake.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from scrappy@hub.org on Wed, Apr 11, 2001 at 11:48:05AM -0300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 11, 2001 at 11:48:05AM -0300, The Hermit Hacker wrote: > NVidia cards are all I buy now, have 3 or 4 right now ... don't the cards > have some sort of serial number? is there any way of using that to > provide a pseudo-petition list ... maybe our new benefactors could talk to > NVidia themselves, get nVidia to setup a nonline 'registration form' that > we could all connect to and submit our serial numbers, to give them a feel > for number of FreeBSD'rs out here? If nvidia is unwilling, then we could designate someone the "keeper of the petition", and have everyone submit their serials to their server through a (lynx-friendly, perhaps?) web form of some sort. Once we've collected what we feel is a good amount, we could mail the whole damn list to nVidia... and see if they respond favorably. Regards, Paul http://www.tribble.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 16:12:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id AFE8037B423 for ; Wed, 11 Apr 2001 16:12:29 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14nTmm-000OVs-00 for freebsd-stable@freebsd.org; Thu, 12 Apr 2001 00:12:28 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f3BNCSi79607 for freebsd-stable@freebsd.org; Thu, 12 Apr 2001 00:12:28 +0100 (BST) (envelope-from jcm) Date: Thu, 12 Apr 2001 00:12:27 +0100 From: j mckitrick To: freebsd-stable@freebsd.org Subject: www supfile Message-ID: <20010412001227.A79583@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've noticed that 'www/en' no longer works as a valid tag for cvsup files. But the 'www/en' directory still exists. I must have missed something somewhere. Is there revised documentation somewhere? jm -- ------------------------------------------- Jonathon McKitrick -- jcm@freebsd-uk.eu.org Do not mistake lack of talent for genius ------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 16:18:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from salmiak.hemmet.chalmers.se (salmiak.hemmet.chalmers.se [193.11.248.165]) by hub.freebsd.org (Postfix) with ESMTP id 7F25437B422 for ; Wed, 11 Apr 2001 16:18:41 -0700 (PDT) (envelope-from smurf@salmiak.hemmet.chalmers.se) Received: from localhost (smurf@localhost) by salmiak.hemmet.chalmers.se (8.11.1/8.11.1) with ESMTP id f3BNZvJ03239; Thu, 12 Apr 2001 01:35:58 +0200 (CEST) (envelope-from smurf@salmiak.hemmet.chalmers.se) Date: Thu, 12 Apr 2001 01:35:57 +0200 (CEST) From: =?ISO-8859-1?Q?Thorbj=F6rn_Axelsson?= To: Kal Torak Cc: , Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) In-Reply-To: <3AD4D8DA.77E28CB6@quake.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Apr 2001, Kal Torak wrote: > Well Im all for it! > > Its a lot better than sitting back and saying, oh they wont give > us the source, they wont give us the technical specs, they are nasty > people etc, etc, etc. :) FYI, I'm pretty sure that there is some kind of petition you can sign on some webpage on the internet. I know I signed something. You might want to look for it (no idea where it is). I would be very happy about any support for nVidia cards on FreeBSD, as it is now I run my desktop-machine with Linux to be able to get the full hardware acceleration (both 2d and 3d works really smooth). Of course I run FreeBSD on my servers still :) And the reason that NVidia does not release the full source is that they have licenced some of the code and they can not legally open source it since they do not own it. [disclaimer: I haven't reviewed this to closely] There shouldn't really be a problem here since the [linux] kernel-module is opensourced but not the real driver. I believe that the kernel-module could be rewritten and use linux emulation provided by FreeBSD for the rest. Maybe :) /Thorbj=F6rn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 16:30:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from boromir.vpop.net (dns1.vpop.net [206.117.147.2]) by hub.freebsd.org (Postfix) with ESMTP id 7E4AB37B423 for ; Wed, 11 Apr 2001 16:30:48 -0700 (PDT) (envelope-from mreimer@vpop.net) Received: from vpop.net ([209.102.16.48]) by boromir.vpop.net (8.11.2/8.11.2) with ESMTP id f3BNUbn37010; Wed, 11 Apr 2001 16:30:37 -0700 (PDT) (envelope-from mreimer@vpop.net) Message-ID: <3AD4E929.99C40DC5@vpop.net> Date: Wed, 11 Apr 2001 16:30:49 -0700 From: Matthew Reimer Organization: VPOP Technologies, Inc. X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Richard Tobin , stable@freebsd.org Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Xvideo support for GeForce2 and better was added into the XFree86 nv driver (not Nvidia's driver) just after XFree86 4.0.3. You'll have to build XFree from CVS to get these bits. Matt Richard Tobin wrote: > > > Before you lambast Nvidia for wanting to keep its IP > > under wraps, it appears that none of the other video card makers (ATI, > > Matrox) have handed over their "crown jewels" to Open Source developers. > > Nvidia is at least providing an optimised driver for its cards -- Matrox and > > ATI haven't > > So how come we haven't even got the XVideo extension available on > GeForce cards, unlike ATI and Matrox? Sounds fair to lambast NVidia > to me. > > -- Richard > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 16:40:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from boromir.vpop.net (dns1.vpop.net [206.117.147.2]) by hub.freebsd.org (Postfix) with ESMTP id 3103937B422 for ; Wed, 11 Apr 2001 16:40:47 -0700 (PDT) (envelope-from mreimer@vpop.net) Received: from vpop.net ([209.102.16.48]) by boromir.vpop.net (8.11.2/8.11.2) with ESMTP id f3BNehn37580 for ; Wed, 11 Apr 2001 16:40:43 -0700 (PDT) (envelope-from mreimer@vpop.net) Message-ID: <3AD4EB86.84643B81@vpop.net> Date: Wed, 11 Apr 2001 16:40:54 -0700 From: Matthew Reimer Organization: VPOP Technologies, Inc. X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It shouldn't be that hard, and I think most of what we need is already available. Read this thread: http://www.FreeBSD.org/cgi/search.cgi?words=triantos&max=100&sort=date&index=all&source=freebsd-hackers I quote: > We'll be happy to work with people to get our code up and running, but it's > important to note that our drivers do not use DRI, we use our own direct > rendering mechanism. There are exactly 3 source files which need to be > ported from linux to freebsd, then after that, it should be fairly simple to > get all of our drivers running on FreeBSD. Again, we do intend to do this, > we've just been swamped and haven't yet had bandwidth to do this work. So presumably all one needs to do is download the Linux kernel module and start porting. http://www.nvidia.com/Pages.nsf/Lookup/linux_03/$file/NVIDIA_kernel-0.9-769.tar.gz ls -l total 1425 -r--r--r-- 1 mreimer mreimer 2501 Mar 14 15:20 Makefile -rw-r--r-- 1 mreimer mreimer 647446 Mar 14 15:20 Module-nvkernel -r--r--r-- 1 mreimer mreimer 1064 Mar 14 15:20 README -r-xr-xr-x 1 mreimer mreimer 818 Mar 14 15:20 makedevices.sh* -r--r--r-- 1 mreimer mreimer 68534 Mar 14 15:20 nv.c -r--r--r-- 1 mreimer mreimer 12071 Mar 14 15:20 nv.h -rw-r--r-- 1 mreimer mreimer 400 Mar 14 15:20 nv_ref.h -r--r--r-- 1 mreimer mreimer 48735 Mar 14 15:20 nvrm.h -rw-r--r-- 1 mreimer mreimer 280169 Mar 14 15:20 nvrmapi.lib -r--r--r-- 1 mreimer mreimer 6722 Mar 14 15:20 nvtypes.h -r--r--r-- 1 mreimer mreimer 3448 Mar 14 15:20 os-agpconfig.h -r--r--r-- 1 mreimer mreimer 52293 Mar 14 15:20 os-interface.c -r--r--r-- 1 mreimer mreimer 12037 Mar 14 15:20 os-interface.h -r--r--r-- 1 mreimer mreimer 8108 Mar 14 15:20 os-registry.c -rw-r--r-- 1 mreimer mreimer 265912 Mar 14 15:20 xf86nvrmapi.lib I think they hide their secret sauce in the files Module-nvkernel, nvrmapi.lib and xf86nvrmapi.lib. Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 16:48: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from boromir.vpop.net (dns1.vpop.net [206.117.147.2]) by hub.freebsd.org (Postfix) with ESMTP id B324337B42C for ; Wed, 11 Apr 2001 16:47:59 -0700 (PDT) (envelope-from mreimer@vpop.net) Received: from vpop.net ([209.102.16.48]) by boromir.vpop.net (8.11.2/8.11.2) with ESMTP id f3BNlun37996 for ; Wed, 11 Apr 2001 16:47:56 -0700 (PDT) (envelope-from mreimer@vpop.net) Message-ID: <3AD4ED37.F1A1B948@vpop.net> Date: Wed, 11 Apr 2001 16:48:07 -0700 From: Matthew Reimer Organization: VPOP Technologies, Inc. X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Correction: GeForce256 and better. See: http://www.xfree86.org/pipermail/cvs-commit/2001-March/001888.html Matt Matthew Reimer wrote: > > Xvideo support for GeForce2 and better was added into the XFree86 nv > driver (not Nvidia's driver) just after XFree86 4.0.3. You'll have to > build XFree from CVS to get these bits. > > Matt > > Richard Tobin wrote: > > > > > Before you lambast Nvidia for wanting to keep its IP > > > under wraps, it appears that none of the other video card makers (ATI, > > > Matrox) have handed over their "crown jewels" to Open Source developers. > > > Nvidia is at least providing an optimised driver for its cards -- Matrox and > > > ATI haven't > > > > So how come we haven't even got the XVideo extension available on > > GeForce cards, unlike ATI and Matrox? Sounds fair to lambast NVidia > > to me. > > > > -- Richard > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 16:51:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mobile.hub.org (SHW39-29.accesscable.net [24.138.39.29]) by hub.freebsd.org (Postfix) with ESMTP id B8F9637B43F for ; Wed, 11 Apr 2001 16:51:07 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by mobile.hub.org (8.11.1/8.11.1) with ESMTP id f3BNlgL71870; Wed, 11 Apr 2001 20:47:42 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: mobile.hub.org: scrappy owned process doing -bs Date: Wed, 11 Apr 2001 20:47:42 -0300 (ADT) From: The Hermit Hacker To: Kal Torak Cc: , Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) In-Reply-To: <3AD4D8DA.77E28CB6@quake.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG have some instructions on the form that allow those of us *with* their cards can put in a serial number as some sort of 'proof of purchase'? On Thu, 12 Apr 2001, Kal Torak wrote: > Well Im all for it! > > Its a lot better than sitting back and saying, oh they wont give > us the source, they wont give us the technical specs, they are nasty > people etc, etc, etc. :) > > Now... We just need someone with experiance to run this thing... > > > I feel your pain, as I'm sure others do on the list. You aren't going to be satisfied with a "there is nothing we can do about this because" type answer. To you it sounds defeatist and like an excuse to do nothing. I agree. I have an idea I wanted to run by the list. > > > > What if someone were to set up a simple email cgi with a form letter in the nature of: > > > > Dear nVidia, > > > > My name is _______. I am sending you this email because I use an operating system called FreeBSD(http://www.freebsd.org) and there does not appear to be driver support for your product because of a business decision you have made. > > > > Currently I, > > > > Select One: > > > > *Own one of your _______ cards > > > > *Own a _______ which is a compeditors card and would like to use one of your ________ cards instead > > > > *Would like to use one of your _____ cards when it is supported > > > > Please consider developing your own drivers for FreeBSD, opening the source code to your drivers, or releasing the hardware specifications to your hardware so eager FreeBSD coders can make drivers for our operating system. You'd be making a rapidly growing culture of computer users that like playing games and doing high end graphics work very happy. Very many of us would be very happy to use your superior products with our operating system of choice. > > > > Thank you. > > > > Joe FreeBSD User > > > > Have them numbered in the subject so nVidia has an instant idea how many people are effected. It would be important that we don't sound like depraved zealots like some other operating system fans have in the past when doing a letter writing campaign. > > > > Any thoughts? I know that I'm worried I won't be able to play Doom3 when it finally comes out. I'm a big fan of the ID software series. Speed with tribes2 would be nice also. Please let me know what you think. I know I'd gladly do my best to set something like this up, or visit the URL and take the time to fill in the blanks if someone else posts it. I'm sure someone is going to say it won't do any good, but I don't think it could hurt. Doing nothing always seems to have this way of looking a lot like doing nothing. > > > > Best Regards, > > > > Scott Alan Wilson > > http://sawilson.org > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > 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-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 16:57:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.noos.fr (lafontaine.noos.net [212.198.2.72]) by hub.freebsd.org (Postfix) with ESMTP id EAD9037B424 for ; Wed, 11 Apr 2001 16:57:17 -0700 (PDT) (envelope-from clefevre@poboxes.com) Received: (qmail 1209187 invoked by uid 0); 11 Apr 2001 23:57:16 -0000 Received: from d165.dhcp212-198-231.noos.fr (HELO gits.dyndns.org) ([212.198.231.165]) (envelope-sender ) by lafontaine.noos.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 11 Apr 2001 23:57:16 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.3/8.11.3) id f3BNvEm94030; Thu, 12 Apr 2001 01:57:14 +0200 (CEST) (envelope-from clefevre@poboxes.com) To: "Jonathan Belson" Cc: "Kal Torak" , "FreeBSD-stable" Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: <3AD427DC.CFC52BAE@quake.com.au> <004c01c0c26e$21b6e7c0$650e850a@innovisiongroup.com> X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C Reply-To: Cyrille Lefevre In-Reply-To: <004c01c0c26e$21b6e7c0$650e850a@innovisiongroup.com> Mail-Copies-To: never From: Cyrille Lefevre Date: 12 Apr 2001 01:57:13 +0200 Message-ID: Lines: 15 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jonathan Belson" writes: > The TNT2 cards are supported, at least under X3. The Radeon should have > support too AIR. TNT2 are almost obsolete, no ? and the Radeon cost almost 2x a GeForce2... also, is the Radeon really 3D accelated ? does someone has a working OpenGL for Radeon ? not sure. Cyrille. -- home: mailto:clefevre@poboxes.com UNIX is user-friendly; it's just particular work: mailto:Cyrille.Lefevre@edf.fr about who it chooses to be friends with. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 18:12:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from xyzzy.intranet.snsonline.net (dhcp.looksmart.com.au [202.53.47.178]) by hub.freebsd.org (Postfix) with ESMTP id E3FAB37B43E for ; Wed, 11 Apr 2001 18:12:03 -0700 (PDT) (envelope-from msergeant@snsonline.net) Received: from xyzzy.intranet.snsonline.net (localhost [127.0.0.1]) by xyzzy.intranet.snsonline.net (8.11.1/8.11.1) with SMTP id f3C1BEm31177; Thu, 12 Apr 2001 11:11:17 +1000 (EST) (envelope-from msergeant@snsonline.net) Message-Id: <200104120111.f3C1BEm31177@xyzzy.intranet.snsonline.net> Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 From: "Mark Sergeant" To: Kal Torak , Jonathan Belson Cc: FreeBSD-stable Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) X-Mailer: Pronto v2.2.3 On freebsd/mysql Date: 11 Apr 2001 20:11:13 EST Reply-To: "Mark Sergeant" In-Reply-To: <3AD46C19.FC1AFB93@quake.com.au> References: <3AD427DC.CFC52BAE@quake.com.au> <004c01c0c26e$21b6e7c0$650e850a@innovisiongroup.com> <3AD46C19.FC1AFB93@quake.com.au> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nvidia won't realease the source for one reason & one reason only. They license part of the technology off other vendors & are under NDI's with these vendors. Opening the source would be illegal for them to do. I as much as everyone else would love to get my nvidia card's working under FreeBSD. The only reason I run windows @ home is to play games & because my gf is yet to see the light. Cheers, Mark On Thu, 12 Apr 2001 00:37:13 +1000, Kal Torak said: > > > I have been looking into the situation with 3D Acceleration (eg. OpenGL) > > > with FreeBSD, the current state of things is pretty poor compared with > > > what linux now offers! > > > > I agree - maybe it's not that important if you're running a web server, but > > accelerated OpenGL is pretty useful. > > > > I am going to mail nVidia linux team and see if I can get them to ether > > release all the source or to make a port to FreeBSD... > > > > nVidia won't release source 8^( > > Yeah I wouldnt expect them to really, one can always dream :) > > So in that case we need to mail nVidia and request that they make > a port for there drivers to FreeBSD! > If enough of us mail them about it, surly they will take notice? > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > -- Why not have an old-fashioned Christmas for your family this year? Just picture the scene in your living room on Christmas morning as your children open their old-fashioned presents. Your 11-year-old son: "What the heck is this?" You: "A spinning top! You spin it around, and then eventually it falls down. What fun! Ha, ha!" Son: "Is this a joke? Jason Thompson's parents got him a computer with two disk drives and 128 kilobytes of random-access memory, and I get this cretin TOP?" Your 8-year-old daughter: "You think that's bad? Look at this." You: "It's figgy pudding! What a treat!" Daughter: "It looks like goat barf." -- Dave Barry, "Simple, Homespun Gifts" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 18:27:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ece.cmu.edu (ECE.CMU.EDU [128.2.236.200]) by hub.freebsd.org (Postfix) with ESMTP id 7045737B43E for ; Wed, 11 Apr 2001 18:27:12 -0700 (PDT) (envelope-from allbery@ece.cmu.edu) Received: from rushlight.rem.cmu.edu (ANNEX-4.ECE.CMU.EDU [128.2.136.4]) (authenticated) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id f3C1Qbr27956; Wed, 11 Apr 2001 21:26:38 -0400 (EDT) Date: Wed, 11 Apr 2001 21:26:36 -0400 From: "Brandon S. Allbery KF8NH" To: scott@sawilson.org, freebsd-stable@FreeBSD.ORG Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) Message-ID: <105060000.987038796@rushlight.rem.cmu.edu> In-Reply-To: <20010411220425.22581.cpmta@c001.snv.cp.net> X-Mailer: Mulberry/2.0.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, April 11, 2001 15:04:25 -0700, scott@sawilson.org wrote: +---- | On Wed, 11 April 2001, Kal Torak wrote: | | > | > Michael Nottebrock wrote: | > > | > > ----- Original Message ----- | > > From: "Kal Torak" | > > To: "The Hermit Hacker" | > > Cc: "Jonathan Belson" ; "FreeBSD-stable" | > > | > > Sent: Wednesday, April 11, 2001 6:34 PM | > > Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) | > > | > > > [...] | > > > nVidia cards are really the ONLY choice to buy now... Not that Im | > > complaining, | > > > they are good cards, we just need some support for the more recent | > > ones! | --snip-- | | Hello, | | I feel your pain, as I'm sure others do on the list. You aren't | going to be satisfied with a "there is nothing we can do about | this because" type answer. To you it sounds defeatist and like an | excuse to do nothing. I agree. I have an idea I wanted to run by | the list. | | What if someone were to set up a simple email cgi with a form | letter in the nature of: +--->8 My gut feeling is that form letters --- and especially form *email* --- aren't perceived as being worth much; people sending in their own letters with their own choice of wording, and preferably *paper* letters, will make more of an impact. -- brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering KF8NH carnegie mellon university ["better check the oblivious first" -ke6sls] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 18:32:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id 5652C37B422 for ; Wed, 11 Apr 2001 18:32:03 -0700 (PDT) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.3+3.4W/8.11.3) with ESMTP/inet id f3C1Vg899191; Thu, 12 Apr 2001 10:31:56 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: <20010411022157P.matusita@jp.FreeBSD.org> References: <20010410141230H.matusita@jp.FreeBSD.org> <20010410082141I.jkh@osd.bsdi.com> <20010411022157P.matusita@jp.FreeBSD.org> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Urania) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 59 From: Makoto MATSUSHITA To: jkh@osd.bsdi.com, stable@FreeBSD.ORG Subject: Re: 4.3-RC2: broken crypto/CHECKSUM.MD5 Date: Thu, 12 Apr 2001 10:31:24 +0900 Message-Id: <20010412103124U.matusita@jp.FreeBSD.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jkh> If you submit a patch, I'll do my best to test and integrate it. matusita> Already submitted to FreeBSD PR database. Please fetch a patch from: matusita> For anybody cannot access webpages nor the PR database itself, here is a patch. This patch fixes: - rebuild crypto/CHECKSUM.MD5, if crypto-related source distributions are moved from src/ to crypto/. - rebuild src/CHECKSUM.MD5 unconditionally after all src/ distribution fixes are finished. Note that this is not related to crypto-related source distributions, since yet another sources described in EXTRA_SRC are also added to src/ distribution. Maybe we can check strictly whether src/CHECKSUM.MD5 needs updating or not, but this works in all cases. I've confirmed that this patch should work, but more checking and checking will be desired. Note: crypto/CHECKSUM.MD5 in 4.3-RC3 needs rebuilding :-) -- - Makoto `MAR' MATSUSHITA Index: Makefile =================================================================== RCS file: /lab/FreeBSD/FreeBSD.cvs/src/release/Makefile,v retrieving revision 1.586 diff -c -r1.586 Makefile *** Makefile 2000/11/21 04:37:30 1.586 --- Makefile 2000/12/05 05:43:41 *************** *** 503,509 **** if [ -f ssecure.aa ] ; then mv ssecure.* ../crypto ; fi && \ if [ -f scrypto.aa ] ; then mv scrypto.* ../crypto ; fi && \ if [ -f skrb4.aa ] ; then mv skrb4.* ../crypto ; fi && \ ! if [ -f skrb5.aa ] ; then mv skrb5.* ../crypto ; fi ; ) ; fi @echo "src distribution is finished." .endif touch release.7 --- 503,512 ---- if [ -f ssecure.aa ] ; then mv ssecure.* ../crypto ; fi && \ if [ -f scrypto.aa ] ; then mv scrypto.* ../crypto ; fi && \ if [ -f skrb4.aa ] ; then mv skrb4.* ../crypto ; fi && \ ! if [ -f skrb5.aa ] ; then mv skrb5.* ../crypto ; fi ; \ ! cd ${RD}/dists/crypto; rm -f CHECKSUM.MD5; \ ! md5 * > CHECKSUM.MD5 ) ; fi ! (cd ${RD}/dists/src; rm -f CHECKSUM.MD5; md5 * > CHECKSUM.MD5) @echo "src distribution is finished." .endif touch release.7 But if creating CHECKSUM.MD5 files are already totally broken feature, we can simply remove all CHECKSUM.MD5 files. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 18:35:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebsd.netcom.com (freebsd.netcom.com [198.211.79.3]) by hub.freebsd.org (Postfix) with ESMTP id DEF5D37B43E for ; Wed, 11 Apr 2001 18:34:58 -0700 (PDT) (envelope-from bugs@freebsd.netcom.com) Received: (from bugs@localhost) by freebsd.netcom.com (8.8.8+Sun/8.8.8) id UAA20957 for freebsd-stable@freebsd.org; Wed, 11 Apr 2001 20:34:57 -0500 (CDT) From: Mark Hittinger Message-Id: <200104120134.UAA20957@freebsd.netcom.com> Subject: re: nVidia Cards /w FreeBSD (3D Acceleration) To: freebsd-stable@freebsd.org Date: Wed, 11 Apr 2001 20:34:57 -0500 (CDT) 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >msergeant wrote: >Nvidia won't realease the source for one reason & one reason only. They license >part of the technology off other vendors & are under NDI's with these vendors. >Opening the source would be illegal for them to do. I as much as everyone else >would love to get my nvidia card's working under FreeBSD. The only reason I run >windows @ home is to play games & because my gf is yet to see the light. This is something we need to consider seriously, as the Linux camps will. My son recently began fiddling with Tribes2. He has what I thought was a reasonably good game platform (p3-500/vodoo3500) but I see lots of slowdown and other problem areas when I look over his shoulder. I went shopping for a geforce2 card but went ahead and preordered a geforce3. After people address their graphics cards, they will probably have to address their cpu. I'm suspicious that a 1.x gz cpu may not be enough to do the job right. It appears to me that the game manufacturers of these high end games may have to begin (if they aren't already) considering using dual cpu motherboards and some sort of OS with threads. I am saying that Win98/2k may be at that point where the high end game developers are forced to leave Win* behind. We ought to make sure that we can go along with that move. It strikes me that in such a resource intensive and performance intensive environment we would be able to provide a more stable situation than our competition :-) Later Mark Hittinger Earthlink bugs@freebsd.netcom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 18:54:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns5.sony.co.jp (ns5.Sony.CO.JP [202.238.80.5]) by hub.freebsd.org (Postfix) with ESMTP id 55F5637B43F for ; Wed, 11 Apr 2001 18:54:03 -0700 (PDT) (envelope-from mistral@imasy.or.jp) Received: from mail2.sony.co.jp (gatekeeper8.Sony.CO.JP [202.238.80.22]) by ns5.sony.co.jp (R8) with ESMTP id f3C1ru300248; Thu, 12 Apr 2001 10:53:56 +0900 (JST) Received: from mail2.sony.co.jp (localhost [127.0.0.1]) by mail2.sony.co.jp (R8) with ESMTP id f3C1ruY14055; Thu, 12 Apr 2001 10:53:56 +0900 (JST) Received: from mistral.imasy.or.jp ([43.1.172.41]) by mail2.sony.co.jp (R8) with ESMTP id f3C1ruv14050; Thu, 12 Apr 2001 10:53:56 +0900 (JST) Received: (from yohta@localhost) by mistral.imasy.or.jp (8.11.3/3.7Wpl2-010215) id f3C1rtL13001; Thu, 12 Apr 2001 10:53:55 +0900 (JST) From: mistral@imasy.or.jp (Yoshihiko SARUMARU) To: jkh@osd.bsdi.com Cc: stable@FreeBSD.ORG Subject: Re: desktop selection on sysinstall and available packages in CD-ROM In-Reply-To: Your message of "Mon, 2 Apr 2001 20:28:52 +0900". <010402202852.M0300970@mistral.imasy.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Mailer: mnews [version 1.22PL5] 2001-02/07(Wed) Date: Thu, 12 Apr 2001 10:53:54 +0900 Message-ID: <010412105354.M0112914@mistral.imasy.or.jp> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > We usually go to some trouble to make sure that all the packages > > referenced by sysinstall are there on the disc #1 image. Can you > > verify that these items are still missing in the 4.3-rc2 ISO? If you > > can tell us precisely what's missing, we can make sure that this > > doesn't happen for the next one or, certainly, for 4.3-RELEASE. > > OK. I tested again with 4.3rc2-install.iso. > The result is the same as rc1. I tested again with 4.3rc3-install.iso The result is the same as rc1 and rc2. Date stamp of all packages are still March 27 :( Jordan, Can I expect that this problem is fixed in 4.3-RELEASE ? If there is no time for the release engineer to fix this, I request him to add some notes for the menu in this time. -- Yoshihiko SARUMARU mail: mistral@imasy.or.jp web: http://www.imasy.or.jp/~mistral/ I love the magic number `4.3' more than `4.4' :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 18:54:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from awww.jeah.net (awww.jeah.net [216.111.239.130]) by hub.freebsd.org (Postfix) with ESMTP id BFB7437B424 for ; Wed, 11 Apr 2001 18:54:48 -0700 (PDT) (envelope-from chris@awww.jeah.net) Received: (from chris@localhost) by awww.jeah.net (8.11.3/8.11.0) id f3C1sim15540 for stable@FREEBSD.ORG; Wed, 11 Apr 2001 20:54:44 -0500 (CDT) (envelope-from chris) Date: Wed, 11 Apr 2001 20:54:44 -0500 (CDT) From: Chris Byrnes Message-Id: <200104120154.f3C1sim15540@awww.jeah.net> To: stable@FREEBSD.ORG Subject: "ELF Interpreter not Found..", New 4.3 Box. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Upon booting a newly CVSup'd and built 4.3 box, I get: ELF interpreter /usr/libexec/ld-elf.so.1 not found I've gotten that error before in a shell, but never preventing me from booting.. -cb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 19: 0:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tulip.okilab.oki.co.jp (okigate.oki.co.jp [202.226.91.194]) by hub.freebsd.org (Postfix) with ESMTP id 6BEEC37B43F for ; Wed, 11 Apr 2001 19:00:22 -0700 (PDT) (envelope-from hyama@okilab.oki.co.jp) Received: from localhost (tulip.okilab.oki.co.jp [172.24.23.187]) by tulip.okilab.oki.co.jp (8.9.3/8.9.3) with ESMTP id LAA88658 for ; Thu, 12 Apr 2001 11:00:21 +0900 (JST) (envelope-from hyama@okilab.oki.co.jp) To: stable@FreeBSD.ORG Subject: userland ppp for IPv6 From: Hideki Yamamoto X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010412110020W.hyama@okilab.oki.co.jp> Date: Thu, 12 Apr 2001 11:00:20 +0900 X-Dispatcher: imput version 990905(IM130) Lines: 19 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am searching for an implementation of a userland PPP for IPv6. IPv6 address cannot be assigned to tunnel devices in FreeBSD now. Are there any pointers to the extension for tunnel device code in kernel to support IPv6 address or to mailing lists to discuss this matter? Thanks in advance. ----------------------------------------------------------------- Hideki YAMAMOTO | E-mail: yamamoto436@oki.co.jp Research and Development group | Tel: +81-3-3455-0870 Oki Electric Industry Co., Ltd. | FAX: +81-3-3798-7670 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 19:19:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from front004.cluster1.charter.net (outbound.charter.net [24.216.159.200]) by hub.freebsd.org (Postfix) with ESMTP id C3AB737B424 for ; Wed, 11 Apr 2001 19:19:50 -0700 (PDT) (envelope-from duhring@charter.net) Received: from [24.217.148.158] (HELO dave.uhring.com) by front004.cluster1.charter.net (CommuniGate Pro SMTP 3.4.3) with SMTP id 11169148; Wed, 11 Apr 2001 22:19:49 -0400 Content-Type: text/plain; charset="iso-8859-1" From: Dave Uhring To: mistral@imasy.or.jp (Yoshihiko SARUMARU), jkh@osd.bsdi.com Subject: Re: desktop selection on sysinstall and available packages in CD-ROM Date: Wed, 11 Apr 2001 21:19:47 -0500 X-Mailer: KMail [version 1.2] Cc: stable@FreeBSD.ORG References: <010412105354.M0112914@mistral.imasy.or.jp> In-Reply-To: <010412105354.M0112914@mistral.imasy.or.jp> MIME-Version: 1.0 Message-Id: <01041121194700.28924@dave.uhring.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday 11 April 2001 20:53, Yoshihiko SARUMARU wrote: > > > We usually go to some trouble to make sure that all the packages > > > referenced by sysinstall are there on the disc #1 image. Can you > > > verify that these items are still missing in the 4.3-rc2 ISO? If you > > > can tell us precisely what's missing, we can make sure that this > > > doesn't happen for the next one or, certainly, for 4.3-RELEASE. > > > > OK. I tested again with 4.3rc2-install.iso. > > The result is the same as rc1. > > I tested again with 4.3rc3-install.iso > The result is the same as rc1 and rc2. > Date stamp of all packages are still March 27 :( > > Jordan, Can I expect that this problem is fixed in 4.3-RELEASE ? > If there is no time for the release engineer to fix this, I > request him to add some notes for the menu in this time. > > -- > Yoshihiko SARUMARU > mail: mistral@imasy.or.jp web: http://www.imasy.or.jp/~mistral/ > I love the magic number `4.3' more than `4.4' :) > When I attempted to install KDE2 from the 4.3-rc2 ISO CD, sysinstall attempted to install kdesupport without having first installed qt. Subsequently, I added qt2 with pkg_add, then added the rest of KDE2. Some of the utilities were "broken", like kmail. As soon as it started up, it seg-faulted. Had to build everything in KDE2 from ports. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 19:37:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id CCCD537B42C for ; Wed, 11 Apr 2001 19:37:25 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id TAA12099; Wed, 11 Apr 2001 19:35:28 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200104120235.TAA12099@freeway.dcfinc.com> Subject: Re: new kernel book this summer? In-Reply-To: <20010411101821Z.jkh@osd.bsdi.com> from Jordan Hubbard at "Apr 11, 1 10:18:21 am" To: jkh@osd.bsdi.com (Jordan Hubbard) Date: Wed, 11 Apr 2001 19:35:27 -0700 (MST) Cc: jcm@FreeBSD-uk.eu.org, freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com Organization: DCF, Inc. X-O/S: FreeBSD 2.2.8-STABLE X-Unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Jordan Hubbard wrote: >> I posted a week or so ago on -hackers asking about a rumor that a >> revised 'design and implementation of freebsd os' would be out this >> summer. No one replied. Since then, a number of people have emailed >> me privately expressing interest in this. So, does anyone know >> anything about this? > > It's not a rumor, both Kirk McKusick and David Greenman (two of the > authors) announced it at BSDCon, but it's been delayed. It's not sure > at this stage just how long the book will take to get published. So, has an ISBN been assigned? Can we get on the queue at Amazon or BSDI? > - Jordan -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 19:51:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebsd.netcom.com (freebsd.netcom.com [198.211.79.3]) by hub.freebsd.org (Postfix) with ESMTP id 3116D37B50B for ; Wed, 11 Apr 2001 19:51:20 -0700 (PDT) (envelope-from bugs@freebsd.netcom.com) Received: (from bugs@localhost) by freebsd.netcom.com (8.8.8+Sun/8.8.8) id VAA21412 for freebsd-stable@freebsd.org; Wed, 11 Apr 2001 21:51:19 -0500 (CDT) From: Mark Hittinger Message-Id: <200104120251.VAA21412@freebsd.netcom.com> Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) To: freebsd-stable@freebsd.org Date: Wed, 11 Apr 2001 21:51:19 -0500 (CDT) 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Daryl Chance wrote: > Just so you know, there have been a LOT of people griping and > complaiining about how Tribes 2 runs on thier systems. Mainly, > nearly all, are people with a VooDoo of sorts. V 2/3/4/5. I know that people are unhappy but on the other hand it looks like this is a kind of "obsoleting" release of software. 3dfx has their own financial issues which cast doubt on the long term viability of their stuff. The level of improvement that people need to make in their systems appears to me to be a substantial one - one that will cause people to have to address several portions of their game box. We could be seeing the beginning of some good times for PC manufacturers. People will have to do something substantial about their graphics, yes, but after having done that they will have to do something substantial about their cpu, motherboard, etc. My speculation is that having done all that, there will still be a problem! The game developers may have to face the prospect that there is only one piece of the puzzle that hasn't received a performance facelift and it is the OS ! :-) I know the Linux people will be in there trying to be the natural migration path. It would be nice if we could at least maintain parity with Linux on this nvdia issue. They are working on Tribes 3 already :-) Later Mark Hittinger Earthlink bugs@freebsd.netcom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 19:53:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id 6649137B440 for ; Wed, 11 Apr 2001 19:53:40 -0700 (PDT) (envelope-from juha@saarinen.org) Received: from dendennis.saarinen.org ([192.168.1.2] helo=dendennis) by vimfuego.saarinen.org with smtp (Exim 3.22 #1 (Red Hack)) id 14nXEj-0004Q3-00; Thu, 12 Apr 2001 14:53:33 +1200 From: "Juha Saarinen" To: "Mark Hittinger" , Subject: RE: nVidia Cards /w FreeBSD (3D Acceleration) Date: Thu, 12 Apr 2001 14:53:11 +1200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal In-Reply-To: <200104120251.VAA21412@freebsd.netcom.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :: I know that people are unhappy but on the other hand it looks like this :: is a kind of "obsoleting" release of software. 3dfx has their own :: financial issues which cast doubt on the long term viability of their :: stuff. Wasn't 3DFx bought by nVidia? -- Juha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 20: 1: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.bmi.net (smtp.bmi.net [204.57.191.31]) by hub.freebsd.org (Postfix) with ESMTP id 8D54B37B440 for ; Wed, 11 Apr 2001 20:01:00 -0700 (PDT) (envelope-from jmcoopr@webmail.bmi.net) Received: from webmail.bmi.net (dsl-154.bmi.net [207.173.60.230]) by smtp.bmi.net (Pro-8.9.3/Pro-8.9.3) with ESMTP id UAA24511; Wed, 11 Apr 2001 20:00:57 -0700 Message-ID: <3AD51A6D.68C4DFEC@webmail.bmi.net> Date: Wed, 11 Apr 2001 20:01:01 -0700 From: John Merryweather Cooper X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Juha Saarinen Cc: FreeBSD-STABLE Mailing List Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: base64 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG SnVoYSBTYWFyaW5lbiB3cm90ZToNCg0KPiA6OiBObywgYnkgU1RCIC4gLiAuDQo+DQo+IE5v IGJ5IG5WaWRpYSA7LSkNCj4NCj4gd3d3LjNkZnguY29tDQoNCkxvb2tzIGxpa2UgblZpZGlh IElTIHRoZSBtb3N0IHJlY2VudCAiYnV5ZXIiLS1hbHRob3VnaCwgYnkgdGhlIGltcGxpZWQN CnRlcm1zIG9mIHRoZSBhbm5vdW5jZW1lbnQgYXQgaHR0cDovL3d3dy4zZGZ4LmNvbSwgaXQg YXBwZWFycyB0byBiZSBtb3JlDQppbiB0aGUgbW9kZSBvZiBhIGxpcXVpZGF0aW9uLiAgSSdk IHNheSAzZGZ4IGlzIGhpc3RvcnkuIC4gLg0KDQpqbWMNCg== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 20:33:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100]) by hub.freebsd.org (Postfix) with SMTP id 6F42337B496 for ; Wed, 11 Apr 2001 20:33:36 -0700 (PDT) (envelope-from Harald.Schmalzbauer@gmx.de) Received: (qmail 18025 invoked by uid 0); 12 Apr 2001 03:33:35 -0000 Date: Thu, 12 Apr 2001 05:33:34 +0200 (MEST) From: Harald Schmalzbauer To: stable@freebsd.org MIME-Version: 1.0 Subject: IP-Filter in release? X-Priority: 3 (Normal) X-Authenticated-Sender: #0000301138@gmx.net X-Authenticated-IP: [212.63.129.190] Message-ID: <26505.987046414@www51.gmx.net> X-Mailer: WWW-Mail 1.5 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, since IP-Filter 3.4.16 has a serious security hole in it's fragment state cache, I'd love to see 3.4.17 in 4.3-release. Today there was an article in a very popular german newsticker (http://www.heise.de/newsticker/data/ju-11.04.01-000/) that somebody wrote a downloadable peace of code which generates that fragmented packets, so attacking is made easy to everybody. Right now I'm testing 3.4.17 on RC from today. I had to replace some osreldate.h to param.h but it compiled fine and is running so far without problems. I upgraded my 4.2-stable boxes earlier and it's also running fine. Perhaps Darren can commit it to 4.3? Greetings, -Harry -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 20:45:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id E40F437B42C for ; Wed, 11 Apr 2001 20:45:39 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f3C3jN892664; Wed, 11 Apr 2001 20:45:25 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: mistral@imasy.or.jp Cc: stable@FreeBSD.ORG Subject: Re: desktop selection on sysinstall and available packages in CD-ROM In-Reply-To: <010412105354.M0112914@mistral.imasy.or.jp> References: <010402202852.M0300970@mistral.imasy.or.jp> <010412105354.M0112914@mistral.imasy.or.jp> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010411204523H.jkh@osd.bsdi.com> Date: Wed, 11 Apr 2001 20:45:23 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > OK. I tested again with 4.3rc2-install.iso. > > The result is the same as rc1. > > I tested again with 4.3rc3-install.iso > The result is the same as rc1 and rc2. I guess Steve Price hasn't updated the package set yet, since he's the one who provides them all to me for inclusion on the ISOs. I've asked Steve directly about this. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 20:49:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id DF93F37B446 for ; Wed, 11 Apr 2001 20:49:19 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f3C3kT892682; Wed, 11 Apr 2001 20:46:30 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: chad@DCFinc.com Cc: jcm@FreeBSD-uk.eu.org, freebsd-stable@FreeBSD.ORG Subject: Re: new kernel book this summer? In-Reply-To: <200104120235.TAA12099@freeway.dcfinc.com> References: <20010411101821Z.jkh@osd.bsdi.com> <200104120235.TAA12099@freeway.dcfinc.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010411204629L.jkh@osd.bsdi.com> Date: Wed, 11 Apr 2001 20:46:29 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 1 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 20:51:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 11A4537B505 for ; Wed, 11 Apr 2001 20:51:48 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id lewaaaaa for ; Thu, 12 Apr 2001 13:51:18 +1000 Message-ID: <3AD5273F.D91B3A05@quake.com.au> Date: Thu, 12 Apr 2001 13:55:43 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, so far we have 3 possible paths to take :) 1) Group mail thing, with your cards serials etc send to nVidia asking them to please pretty please port there drivers to FreeBSD (Since they cant give us the source for legal reasons) 2) Individual mails to nVidia asking the same thing... 3) Port the kernel module and use linux compat for the rest... Well lets do all 3 :) Who has a decent connected web server we can host this mail thingy on? And who is willing to co-ordinate it? Looking on the nVidia site, they dont really give a mail address we should post to for this sort of thing... So unless someone knows a better address mail should goto info@nvidia.com (Corporate Office). The only other addresses I could find were for investors (we buy there cards are we *investing* in them ;), the press and jobs... Can we simply port the kernel module? I dont have the skills in that area, so if it can be done hopefully someone is willing to do the tech stuff... Anyone? Allright, anyone have any other ideas or things to add? Lets get the ball rolling on this asap :))) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 20:57:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from xyzzy.intranet.snsonline.net (dhcp.looksmart.com.au [202.53.47.178]) by hub.freebsd.org (Postfix) with ESMTP id CBA2737B505 for ; Wed, 11 Apr 2001 20:57:31 -0700 (PDT) (envelope-from msergeant@snsonline.net) Received: from xyzzy.intranet.snsonline.net (localhost [127.0.0.1]) by xyzzy.intranet.snsonline.net (8.11.1/8.11.1) with SMTP id f3C3vAm31610; Thu, 12 Apr 2001 13:57:10 +1000 (EST) (envelope-from msergeant@snsonline.net) Message-Id: <200104120357.f3C3vAm31610@xyzzy.intranet.snsonline.net> Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 From: "Mark Sergeant" To: Kal Torak Cc: freebsd-stable@freebsd.org Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) X-Mailer: Pronto v2.2.3 On freebsd/mysql Date: 11 Apr 2001 22:57:08 EST Reply-To: "Mark Sergeant" In-Reply-To: <3AD5273F.D91B3A05@quake.com.au> References: <3AD5273F.D91B3A05@quake.com.au> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm happy to help out web server wise. Co-ordination wise I believe you just volunteered ;) On Thu, 12 Apr 2001 13:55:43 +1000, Kal Torak said: > Ok, so far we have 3 possible paths to take :) > > 1) Group mail thing, with your cards serials etc send to nVidia > asking them to please pretty please port there drivers to FreeBSD > (Since they cant give us the source for legal reasons) > > 2) Individual mails to nVidia asking the same thing... > > 3) Port the kernel module and use linux compat for the rest... > > Well lets do all 3 :) > > Who has a decent connected web server we can host this mail thingy > on? And who is willing to co-ordinate it? > > Looking on the nVidia site, they dont really give a mail address we > should post to for this sort of thing... So unless someone knows a > better address mail should goto info@nvidia.com (Corporate Office). > The only other addresses I could find were for investors (we buy there > cards are we *investing* in them ;), the press and jobs... > > Can we simply port the kernel module? I dont have the skills in that > area, so if it can be done hopefully someone is willing to do the tech > stuff... Anyone? > > Allright, anyone have any other ideas or things to add? Lets get the > ball rolling on this asap :))) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > -- Give me a Plumber's friend the size of the Pittsburgh dome, and a place to stand, and I will drain the world. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 21: 3:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id C7DF737B42C for ; Wed, 11 Apr 2001 21:03:54 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id pewaaaaa for ; Thu, 12 Apr 2001 14:03:22 +1000 Message-ID: <3AD52A10.7997F8EA@quake.com.au> Date: Thu, 12 Apr 2001 14:07:44 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mark Hittinger Cc: freebsd-stable@freebsd.org Subject: Games on FreeBSD (was:Re: nVidia Cards /w FreeBSD (3D Acceleration)) References: <200104120134.UAA20957@freebsd.netcom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > After people address their graphics cards, they will probably have to address > their cpu. I'm suspicious that a 1.x gz cpu may not be enough to do the job > right. It appears to me that the game manufacturers of these high end > games may have to begin (if they aren't already) considering using dual > cpu motherboards and some sort of OS with threads. > > I am saying that Win98/2k may be at that point where the high end game > developers are forced to leave Win* behind. We ought to make sure that > we can go along with that move. It strikes me that in such a resource > intensive and performance intensive environment we would be able to provide > a more stable situation than our competition :-) Very true, games like tribes2 really need a more powerfull O/S... I am currently having to play it under winblows, and its bad! I have a 1.1ghz t-bird and geforce256 ddr.. Yet still are a lot of performance problems mainly to do with windows handeling of memory (or not handeling)... Forget playing more than 3 games in a row without restarting... They might move to a more stable and better preforming O/S in the future, it will be a slowish proccess though, and the way things are currently linux will be what they move to... Thats still good for us, but it would be better if they moved totaly to FreeBSD :)) Ahh yes... I would love never to boot windows again... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 21: 5: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by hub.freebsd.org (Postfix) with ESMTP id 5C37837B423 for ; Wed, 11 Apr 2001 21:05:03 -0700 (PDT) (envelope-from mvh@ix.netcom.com) Received: from netcom1.netcom.com (lai-ca4d-93.ix.netcom.com [209.110.247.93]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id AAA22822; Thu, 12 Apr 2001 00:05:01 -0400 (EDT) Received: by netcom1.netcom.com (Postfix, from userid 1000) id 94248113ADA; Wed, 11 Apr 2001 21:04:53 -0700 (PDT) From: Mike Harding To: Harald.Schmalzbauer@gmx.de Cc: stable@freebsd.org In-reply-to: <26505.987046414@www51.gmx.net> (message from Harald Schmalzbauer on Thu, 12 Apr 2001 05:33:34 +0200 (MEST)) Subject: Re: IP-Filter in release? References: <26505.987046414@www51.gmx.net> Message-Id: <20010412040453.94248113ADA@netcom1.netcom.com> Date: Wed, 11 Apr 2001 21:04:53 -0700 (PDT) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I believe that Darren already fixed this in the -Stable tree - check http://www.FreeBSD.org/cgi/cvsweb.cgi/src/sys/netinet/ip_frag.c and see a fix commited 5 days ago. - Mike H. Date: Thu, 12 Apr 2001 05:33:34 +0200 (MEST) From: Harald Schmalzbauer X-Priority: 3 (Normal) X-Authenticated-Sender: #0000301138@gmx.net X-Authenticated-IP: [212.63.129.190] X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.ORG Precedence: bulk Hello all, since IP-Filter 3.4.16 has a serious security hole in it's fragment state cache, I'd love to see 3.4.17 in 4.3-release. Today there was an article in a very popular german newsticker (http://www.heise.de/newsticker/data/ju-11.04.01-000/) that somebody wrote a downloadable peace of code which generates that fragmented packets, so attacking is made easy to everybody. Right now I'm testing 3.4.17 on RC from today. I had to replace some osreldate.h to param.h but it compiled fine and is running so far without problems. I upgraded my 4.2-stable boxes earlier and it's also running fine. Perhaps Darren can commit it to 4.3? Greetings, -Harry -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 21: 6:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lerami.lerctr.org (lerami.lerctr.org [207.158.72.11]) by hub.freebsd.org (Postfix) with ESMTP id 7F8BE37B496 for ; Wed, 11 Apr 2001 21:06:18 -0700 (PDT) (envelope-from ler@lerctr.org) Received: (from ler@localhost) by lerami.lerctr.org (8.12.0.Beta7/8.12.0.Beta7/20010318/$Revision: 1.21 $) id f3C46D4I009742 for stable@FreeBSD.ORG; Wed, 11 Apr 2001 23:06:13 -0500 (CDT) (envelope-from ler) Date: Wed, 11 Apr 2001 23:06:12 -0500 From: Larry Rosenman To: stable@FreeBSD.ORG Subject: Re: IP-Filter in release? Message-ID: <20010411230612.A9722@lerami.lerctr.org> References: <26505.987046414@www51.gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.16i In-Reply-To: <26505.987046414@www51.gmx.net>; from Harald.Schmalzbauer@gmx.de on Thu, Apr 12, 2001 at 05:33:34AM +0200 X-Mailer: Mutt http://www.mutt.org/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Harald Schmalzbauer [010411 22:34]: > Hello all, > > since IP-Filter 3.4.16 has a serious security hole in it's fragment state > cache, I'd love to see 3.4.17 in 4.3-release. Today there was an article in a > very popular german newsticker > (http://www.heise.de/newsticker/data/ju-11.04.01-000/) that somebody wrote a downloadable peace of code which generates that > fragmented packets, so attacking is made easy to everybody. > > Right now I'm testing 3.4.17 on RC from today. I had to replace some > osreldate.h to param.h but it compiled fine and is running so far without problems. > > I upgraded my 4.2-stable boxes earlier and it's also running fine. > Perhaps Darren can commit it to 4.3? > > Greetings, Darren put a patch in for the frag-cache problem. I doubt he will do another MFC before the -RELEASE... LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 21: 9: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id EF7A337B628 for ; Wed, 11 Apr 2001 21:08:51 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id uewaaaaa for ; Thu, 12 Apr 2001 14:08:23 +1000 Message-ID: <3AD52B3E.305BA9D3@quake.com.au> Date: Thu, 12 Apr 2001 14:12:46 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mark Sergeant Cc: freebsd-stable@freebsd.org Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: <3AD5273F.D91B3A05@quake.com.au> <200104120357.f3C3vAm31610@xyzzy.intranet.snsonline.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Sergeant wrote: > > I'm happy to help out web server wise. Co-ordination wise I believe you just > volunteered ;) Well I would be happy to co-ordinate it, I just dont know how good a job I would do... Im not experienced in large scale operations to get big companies to do what I want :P If no one else with experience in this sort of thing is willing, then I will try my best to do the job! Damn, I was hopping to just throw the first stone, then let the avalanche take over ;) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 21:33:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from chmod.ath.cx (CC2-861.charter-stl.com [24.217.115.99]) by hub.freebsd.org (Postfix) with ESMTP id 7FD0C37B509 for ; Wed, 11 Apr 2001 21:33:44 -0700 (PDT) (envelope-from ajh3@chmod.ath.cx) Received: by chmod.ath.cx (Postfix, from userid 1001) id A1A29A91E; Wed, 11 Apr 2001 23:33:02 -0500 (CDT) Date: Wed, 11 Apr 2001 23:33:02 -0500 From: Andrew Hesford To: Kal Torak Cc: Mark Hittinger , freebsd-stable@freebsd.org Subject: Re: Games on FreeBSD (was:Re: nVidia Cards /w FreeBSD (3D Acceleration)) Message-ID: <20010411233302.A8789@cec.wustl.edu> References: <200104120134.UAA20957@freebsd.netcom.com> <3AD52A10.7997F8EA@quake.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AD52A10.7997F8EA@quake.com.au>; from kaltorak@quake.com.au on Thu, Apr 12, 2001 at 02:07:44PM +1000 X-Loop: Andrew Hesford Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 12, 2001 at 02:07:44PM +1000, Kal Torak wrote: > > After people address their graphics cards, they will probably have to address > > their cpu. I'm suspicious that a 1.x gz cpu may not be enough to do the job > > right. It appears to me that the game manufacturers of these high end > > games may have to begin (if they aren't already) considering using dual > > cpu motherboards and some sort of OS with threads. > > > > I am saying that Win98/2k may be at that point where the high end game > > developers are forced to leave Win* behind. We ought to make sure that > > we can go along with that move. It strikes me that in such a resource > > intensive and performance intensive environment we would be able to provide > > a more stable situation than our competition :-) > > Very true, games like tribes2 really need a more powerfull O/S... > I am currently having to play it under winblows, and its bad! > > I have a 1.1ghz t-bird and geforce256 ddr.. Yet still are a lot > of performance problems mainly to do with windows handeling of > memory (or not handeling)... Forget playing more than 3 games in > a row without restarting... > > They might move to a more stable and better preforming O/S in the > future, it will be a slowish proccess though, and the way things > are currently linux will be what they move to... Thats still good > for us, but it would be better if they moved totaly to FreeBSD :)) > > Ahh yes... I would love never to boot windows again... > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message I don't know... I've never been much of a gamer. Prboom and quakeforge do me just fine, and they both work fine on a PIII-733 with any video card you can imagine. Remember, DOOM was designed in the 386/486 days, and quake, well, I think the shareware CD folder says system requirements are a 100MHz pentium. Personally, I buy ATI. I've heard that 3D support is lousy, but I'm not using 3D. All my life, simple, cheap ATI cards based on the Mach chipset have worked with XFree86 on Linux and FreeBSD, and I venture to say the other BSDs also. When I went dual head, what do you think I bought? A $50 PCI Xpert 98, because I knew it would work with XFree86 4.0.1. My previous PC had an Xpert 98D, which worked beautifully. Don't ask what I have for a primary card, though. I hate to admit it, but it's an i810 soldered-in. Terrible, I know, but the PC was cheap and I was short on cash. Support in Linux was mildly acceptable, and it works in FreeBSD, but only with XFree86 4.0.1. So far, greater versions crash when I switch consoles. Well, that's my solution to the UNIX gaming problem: don't play games. I wonder if WINE will run Flight Simulatory or Fury^3? Those games weren't so bad, and they bring back memories. I thought I heard WINE was getting DirectX support... -- Andrew Hesford ajh3@chmod.ath.cx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 22: 0:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 20ED837B422 for ; Wed, 11 Apr 2001 22:00:41 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id efwaaaaa for ; Thu, 12 Apr 2001 15:00:11 +1000 Message-ID: <3AD53763.B2B2B38A@quake.com.au> Date: Thu, 12 Apr 2001 15:04:35 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Hesford Cc: Mark Hittinger , freebsd-stable@freebsd.org Subject: Re: Games on FreeBSD References: <200104120134.UAA20957@freebsd.netcom.com> <3AD52A10.7997F8EA@quake.com.au> <20010411233302.A8789@cec.wustl.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't know... I've never been much of a gamer. Prboom and quakeforge > do me just fine, and they both work fine on a PIII-733 with any video > card you can imagine. Remember, DOOM was designed in the 386/486 days, > and quake, well, I think the shareware CD folder says system > requirements are a 100MHz pentium. GlQuakeWorld... thats where its at... any game without OpenGL support is just crap :) > Well, that's my solution to the UNIX gaming problem: don't play games. I > wonder if WINE will run Flight Simulatory or Fury^3? Those games weren't > so bad, and they bring back memories. I thought I heard WINE was getting > DirectX support... Thats fine if you dont enjoy having fun, or you dont do any graphics work... But there are many uses for OpenGL and hardware acceleration in general, there are also lots of great games :) WINE has DirectX support now I think, its quite possible to play Half-Life under WINE on FreeBSD... But that dosent exactly the slove our card problem, which there are plenty of people wanting sloved over in the other thread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 22:10:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from chmod.ath.cx (CC2-861.charter-stl.com [24.217.115.99]) by hub.freebsd.org (Postfix) with ESMTP id D315537B506 for ; Wed, 11 Apr 2001 22:10:29 -0700 (PDT) (envelope-from ajh3@chmod.ath.cx) Received: by chmod.ath.cx (Postfix, from userid 1001) id A5C43A91E; Thu, 12 Apr 2001 00:09:48 -0500 (CDT) Date: Thu, 12 Apr 2001 00:09:48 -0500 From: Andrew Hesford To: Kal Torak Cc: Andrew Hesford , Mark Hittinger , freebsd-stable@freebsd.org Subject: Re: Games on FreeBSD Message-ID: <20010412000948.C8789@cec.wustl.edu> References: <200104120134.UAA20957@freebsd.netcom.com> <3AD52A10.7997F8EA@quake.com.au> <20010411233302.A8789@cec.wustl.edu> <3AD53763.B2B2B38A@quake.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AD53763.B2B2B38A@quake.com.au>; from kaltorak@quake.com.au on Thu, Apr 12, 2001 at 03:04:35PM +1000 X-Loop: Andrew Hesford Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 12, 2001 at 03:04:35PM +1000, Kal Torak wrote: > > I don't know... I've never been much of a gamer. Prboom and quakeforge > > do me just fine, and they both work fine on a PIII-733 with any video > > card you can imagine. Remember, DOOM was designed in the 386/486 days, > > and quake, well, I think the shareware CD folder says system > > requirements are a 100MHz pentium. > > GlQuakeWorld... thats where its at... any game without OpenGL support is > just crap :) > > > Well, that's my solution to the UNIX gaming problem: don't play games. I > > wonder if WINE will run Flight Simulatory or Fury^3? Those games weren't > > so bad, and they bring back memories. I thought I heard WINE was getting > > DirectX support... > > Thats fine if you dont enjoy having fun, or you dont do any graphics work... > But there are many uses for OpenGL and hardware acceleration in general, > there are also lots of great games :) > > WINE has DirectX support now I think, its quite possible to play Half-Life > under WINE on FreeBSD... But that dosent exactly the slove our card problem, > which there are plenty of people wanting sloved over in the other thread! > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message Who said I don't have any fun? I just said I don't play PC games. I understand the card problem... I was doing a classic "nyah nyah" post to tell all of you that I don't have the problem. :) Has anybody offered to sign an NDA with nVidia to write a binary-only driver for FreeBSD? Everybody should ask around amongst all the good FreeBSD hackers, to see if one of them would be willing to do so. After all, this isn't Linux, and we aren't governed by RMS. I wouldn't expect this to be a religious concern about binary-only code, as long as it works, and it works well. Then you all can be happy with your big fancy 3D cards... not like the phosphor on a CRT is thick enough to be an effect 3D display though. :p I'd offer to write the driver, but I am limited by two things: 1) I don't have a card, so I have no incentive to write the driver and no means to test it. 2) My biggest C programs are ~1000 lines long, dedicated to solving mathematical problems, and DEFINITELY not stable enough to be part of any OS kernel except Windows. -- Andrew Hesford ajh3@chmod.ath.cx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 22:11: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from web11804.mail.yahoo.com (web11804.mail.yahoo.com [216.136.172.158]) by hub.freebsd.org (Postfix) with SMTP id 0D74237B50C for ; Wed, 11 Apr 2001 22:10:53 -0700 (PDT) (envelope-from wyldephyre2@yahoo.com) Message-ID: <20010412051052.85230.qmail@web11804.mail.yahoo.com> Received: from [131.181.127.39] by web11804.mail.yahoo.com; Wed, 11 Apr 2001 22:10:52 PDT Date: Wed, 11 Apr 2001 22:10:52 -0700 (PDT) From: Haikal Saadh Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) To: Cyrille Lefevre , Jonathan Belson Cc: Kal Torak , FreeBSD-stable In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- Cyrille Lefevre wrote: > "Jonathan Belson" writes: > > > The TNT2 cards are supported, at least under X3. > The Radeon should have > > support too AIR. > > TNT2 are almost obsolete, no ? and the Radeon cost > almost 2x a > GeForce2... > FWIW, under windows, nVidia has only one driver for )all there cards, ranging from the TNTs to the geForce2s. And while I'm at it, i've got an oem TNT2 M64, but I doubt i'd be bothered to pull it out to get a serial number, assuming it even has one. __________________________________________________ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 22:19:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id EC27437B50C for ; Wed, 11 Apr 2001 22:19:19 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id WAA40922; Wed, 11 Apr 2001 22:19:14 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200104120519.WAA40922@gndrsh.dnsmgr.net> Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) In-Reply-To: <20010412003746.A51230@moya.lambermont.dyndns.org> from H at "Apr 12, 2001 00:37:47 am" To: hans@lambermont.dyndns.org (H) Date: Wed, 11 Apr 2001 22:19:13 -0700 (PDT) Cc: freebsd-stable@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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > scott@sawilson.org wrote: > > > What if someone were to set up a simple email cgi with a form > > letter in the nature of: > > Dear nVidia, > > snip -good letter proto deleted- Agreed, it was a good prototype, no negatives or bashes that I noticed, save those for latter. > > > Have them numbered in the subject so nVidia has an instant idea how > > many people are effected. It would be important that we don't sound > > like depraved zealots like some other operating system fans have in > > the past when doing a letter writing campaign. > > Interesting, has a letter writing campaign like this worked before for > graphics driver issues ? Is so we should go for it ! I am not quite sure of the details, but it was quite a pain for the XFree86 folks to ever get Matrox to work with them on drivers for thier cards. You might search thier archives, or ask them... And IIRC some form of consumer pressure was applied to Diamond to get them to release the details of certian special stuff that they had done on some of their cards having to do with special dot clock circuits... (After someone else did some reverse engineering IIRC again.) I do know that any manufacture can be made to bend or even totaly reverse a company policy if enough of the right type of pressure is applied. That leaves the question, are there enough of us that own nVida products to get them to listen. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 11 22:27: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fat.ti.ru (fat.ti.ru [212.1.224.35]) by hub.freebsd.org (Postfix) with ESMTP id 2707C37B422 for ; Wed, 11 Apr 2001 22:27:01 -0700 (PDT) (envelope-from Martin@McFlySr.Kurgan.Ru) Received: from 127.0.0.1 (fat.ti.ru [212.1.224.35]) by fat.ti.ru (Postfix) with ESMTP id 85C3BD923 for ; Thu, 12 Apr 2001 09:26:59 +0400 (MSD) Date: Thu, 12 Apr 2001 09:26:59 +0400 From: Martin McFlySr X-Mailer: The Bat! (v1.51) Business Reply-To: Martin McFlySr Organization: Back To The Future X-Priority: 3 (Normal) Message-ID: <14455976690.20010412092659@McFlySr.Kurgan.Ru> Disposition-Notification-To: Martin@McFlySr.Kurgan.Ru To: freebsd-stable@FreeBSD.ORG Subject: dmesg troubles in 4.3-RC MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello freebsd-stable@FreeBSD.ORG, FreeBSD 4.3-RC. Anybody have a properly working dmesg? $dmesg :369 in via fxp1 Therefore, report from /etc/security have a problem too... Of course, line if dmesg 2>/dev/null > ${TMP}; then may change to if dmesg -a>/dev/null > ${TMP}; then but this incorrectly, i think.... -- Thursday, 12 April 2001, 09:05 Best regards from future, Martin McFlySr, HillDale. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 0: 9:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from scaup.mail.pas.earthlink.net (scaup.mail.pas.earthlink.net [207.217.121.49]) by hub.freebsd.org (Postfix) with ESMTP id 08F5037B422 for ; Thu, 12 Apr 2001 00:09:16 -0700 (PDT) (envelope-from oistrakh@earthlink.net) Received: from pirastro.oistrakh.org (user-2ivftra.dialup.mindspring.com [165.247.247.106]) by scaup.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id AAA15707; Thu, 12 Apr 2001 00:09:14 -0700 (PDT) Received: from localhost (oistrakh@localhost) by pirastro.oistrakh.org (8.11.3/8.11.1) with ESMTP id f3C78iX87019; Thu, 12 Apr 2001 00:08:45 -0700 (PDT) (envelope-from oistrakh@earthlink.net) X-Authentication-Warning: pirastro.oistrakh.org: oistrakh owned process doing -bs Date: Thu, 12 Apr 2001 00:08:44 -0700 (PDT) From: Christian Chen X-X-Sender: To: Kal Torak Cc: FreeBSD-stable Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) In-Reply-To: <3AD48782.2CEAE87B@quake.com.au> Message-ID: <20010412000523.I86970-100000@pirastro.oistrakh.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Apr 2001, Kal Torak wrote: > nVidia cards are really the ONLY choice to buy now... Not that Im complaining, Maybe this is just *my* personal quirkiness, but does anyone else out there feel as though ATI's 2D performance is higher quality? And by higher quality, I don't mean _faster_, I mean _looks better_. When I replaced my nVidia card with an ATI Rage Fury Pro, and after that a Rage Fury Maxx, the text looked crisper, and images were sharper. Granted, these things are irrevelant to 3D gamers, but for all those sysadmins out there, it sure is nice having crisper console screens and xterms. But maybe it's just me. Lots of people don't notice 60Hz scan rate flicker, but I do ... Christian Chen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 0:21:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from firebat.bushong.net (c128625-a.frmt1.sfba.home.com [24.176.225.90]) by hub.freebsd.org (Postfix) with ESMTP id AB43637B50C for ; Thu, 12 Apr 2001 00:21:08 -0700 (PDT) (envelope-from dbushong@firebat.bushong.net) Received: (from dbushong@localhost) by firebat.bushong.net (8.11.0/8.11.0) id f3C7L6M30741; Thu, 12 Apr 2001 00:21:06 -0700 (PDT) (envelope-from dbushong) Date: Thu, 12 Apr 2001 00:19:51 -0700 From: David Bushong To: Kal Torak Cc: freebsd-stable@FreeBSD.ORG Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) Message-ID: <20010412001951.C12643@bushong.net> References: <3AD5273F.D91B3A05@quake.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AD5273F.D91B3A05@quake.com.au>; from kaltorak@quake.com.au on Thu, Apr 12, 2001 at 01:55:43PM +1000 X-Floating-Sheep-Port: 0xbaa Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 12, 2001 at 01:55:43PM +1000, Kal Torak wrote: > Ok, so far we have 3 possible paths to take :) > > 1) Group mail thing, with your cards serials etc send to nVidia > asking them to please pretty please port there drivers to FreeBSD > (Since they cant give us the source for legal reasons) > > 2) Individual mails to nVidia asking the same thing... > > 3) Port the kernel module and use linux compat for the rest... > Regarding #3, little note: I don't believe any linux compat would be involved at all. The "module" for XFree86 4 should be architecture-specific, but OS neutral (i.e. you have to be running i386, but it doesn't care if you're using linux, freebsd, darwin, etc) The kernel module, if ported, would have to be FreeBSD-native. The only linux-compat usage would come in if you wanted to play all of those binary-only games that probably started this whole discussion, in which case you'd have to build a linux libGL.so to talk via DRI to your FreeBSD XFree86, which I believe /usr/ports/graphics/linux_glx does for you. Just some tidbits. --David Bushong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 0:58:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebsd.org.ru (sweet.etrust.ru [194.84.67.5]) by hub.freebsd.org (Postfix) with ESMTP id BB22037B5AF for ; Thu, 12 Apr 2001 00:58:43 -0700 (PDT) (envelope-from osa@freebsd.org.ru) Received: by freebsd.org.ru (Postfix, from userid 1000) id 4C242233; Thu, 12 Apr 2001 11:58:41 +0400 (MSD) Date: Thu, 12 Apr 2001 11:58:41 +0400 From: "Sergey A. Osokin" To: freebsd-stable@FreeBSD.ORG Subject: HP PC Lan+ cards (27247B) unsupported? Message-ID: <20010412115841.A49908@freebsd.org.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. Yesterday I tried to install 4.2-RELEASE on 486 with HP PC Lan+ ISA card (27247B). FreeBSD (kern.flp and mfsroot.flp) boot successfully from floppies, but card not defined. I looked at the GENERIC kernel and set defined vars for network card (like IRQ/IO etc.) with hplanset tool from HP. Card still not recognise. Any idea? Does this card still supported hardware for FreeBSD? -- Rgdz, /"\ Sergey Osokin aka oZZ, \ / ASCII RIBBON CAMPAIGN osa@freebsd.org.ru X AGAINST HTML MAIL http://freebsd.org.ru/~osa/ / \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 1:42:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id D51E837B446 for ; Thu, 12 Apr 2001 01:42:38 -0700 (PDT) (envelope-from rasputin@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14ncgX-000ALZ-00; Thu, 12 Apr 2001 09:42:37 +0100 Received: (from rasputin@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f3C8gat87427; Thu, 12 Apr 2001 09:42:36 +0100 (BST) (envelope-from rasputin) Date: Thu, 12 Apr 2001 09:42:35 +0100 From: Rasputin To: Kal Torak Cc: stable@freebsd.org Subject: Re: Games on FreeBSD Message-ID: <20010412094235.A87336@dogma.freebsd-uk.eu.org> Reply-To: Rasputin References: <200104120134.UAA20957@freebsd.netcom.com> <3AD52A10.7997F8EA@quake.com.au> <20010411233302.A8789@cec.wustl.edu> <3AD53763.B2B2B38A@quake.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3AD53763.B2B2B38A@quake.com.au>; from kaltorak@quake.com.au on Thu, Apr 12, 2001 at 03:04:35PM +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Kal Torak [010412 06:02]: > WINE has DirectX support now I think, its quite possible to play Half-Life > under WINE on FreeBSD... /me prick up ears as though some just mentioned free beer You don't have a working ~/.wine/config for that, by any chance? -- Rasputin Jack of All Trades :: Master of Nuns To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 1:56:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by hub.freebsd.org (Postfix) with ESMTP id C290A37B424 for ; Thu, 12 Apr 2001 01:56:19 -0700 (PDT) (envelope-from netch@segfault.kiev.ua) Received: (from netch@localhost) by segfault.kiev.ua (8) id LUZ85658; Thu, 12 Apr 2001 11:54:33 +0300 (EEST) (envelope-from netch) Date: Thu, 12 Apr 2001 11:54:33 +0300 From: Valentin Nechayev To: nicholas harteau Cc: freebsd-stable@freebsd.org Subject: Re: fresh 4.3-RC: "microuptime went backwards", console lockup Message-ID: <20010412115433.D42860@netch.kiev.ua> Reply-To: netch@netch.kiev.ua References: <20010411192854.A570@netch.kiev.ua> <20010411113735.J23469@voyager.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010411113735.J23469@voyager.net>; from nrh@ikami.com on Wed, Apr 11, 2001 at 11:37:35AM -0500 X-42: On Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wed, Apr 11, 2001 at 11:37:35, nrh wrote about "Re: fresh 4.3-RC: "microuptime went backwards", console lockup": > This happened to me; a couple things you might try: > kern.timecounter.method=1 This is set already (in sysctl.conf), but does not help. > or, possibly adding: > device apm0 at nexus? disable flags 0x20 See my config - it exists there already. Also does not help. > to your kernel. P.S. There is no need for overquote. P.P.S. I ask again: can anybody send me text or URL for PHK's description of his timecounter scheme, especially for tco_forward() concept? > Valentin Nechayev wrote: > > Today, 4.3-RC (RELENG_4, date=2001.04.11.00.00.00) was built and, when > > new system started: > > 1) during boot and even before /sbin/init started, "microuptime went backwards" > > occured too many times. > > 2) after startx, syscons switched to ttyv0 and stayed here; after > > mutual swithing to ttyvb, console locked up totally. > > No problems with previous system (RELENG_4, date=2001.03.05.00.00.00) > > were seen. Xwindow is 3.3.6 from latest port. /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 2:11:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from clueless.redbus.aaisp.net (clueless.redbus.aaisp.net [213.161.73.195]) by hub.freebsd.org (Postfix) with SMTP id B27D737B423 for ; Thu, 12 Apr 2001 02:11:32 -0700 (PDT) (envelope-from jon@witchspace.com) Received: from zebedee.innovision-group.com (HELO:witchspace.com) by clueless.redbus.aaisp.net for freebsd-stable@FreeBSD.ORG; Thu, 12 Apr 2001 09:19:24 +0100 Message-ID: <3AD566AD.68D9FC2E@witchspace.com> Date: Thu, 12 Apr 2001 09:26:21 +0100 From: Jonathan Belson X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Cyrille Lefevre Cc: FreeBSD-stable Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: <3AD427DC.CFC52BAE@quake.com.au> <004c01c0c26e$21b6e7c0$650e850a@innovisiongroup.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cyrille Lefevre wrote: > > "Jonathan Belson" writes: > > > The TNT2 cards are supported, at least under X3. The Radeon should have > > support too AIR. > > TNT2 are almost obsolete, no ? and the Radeon cost almost 2x a Well, mine still works ;^) > GeForce2... Depends which GeForce and which Radeon. In the UK a GeForce Ultra costs about 340GBP compared with 170GBP for the Radeon VIVO. > also, is the Radeon really 3D accelated ? does someone has a working > OpenGL for Radeon ? not sure. I remember reading an email by one of the contracted glx/dri (?) developers that he was trying to write the drivers in such a way that it would work with *BSD too - I can't remember any details sadly, I'll see if I can find the email. -- C-YA Jon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 3: 8: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hvv.svzserv.kemerovo.su (hvv.svzserv.kemerovo.su [213.184.65.67]) by hub.freebsd.org (Postfix) with ESMTP id B30E137B423; Thu, 12 Apr 2001 03:07:55 -0700 (PDT) (envelope-from vk@hvv.svzserv.kemerovo.su) Received: (from vk@localhost) by hvv.svzserv.kemerovo.su (8.9.3/8.9.3) id SAA48207; Thu, 12 Apr 2001 18:07:45 +0800 (NKZS) (envelope-from vk) Message-Id: Date: Thu, 12 Apr 2001 18:03:28 +0800 From: Vladimir Kurtukov X-Mailer: MEd Version 1.1 (i386--freebsd3.5) References: <200103140624.f2E6Om137753@prism.flugsvamp.com> In-Reply-To: <200103140624.f2E6Om137753@prism.flugsvamp.com>; from Jonathan Lemon To: jlemon@flugsvamp.com Cc: eugen@svzserv.kemerovo.su, stable@freebsd.org, jlemon@freebsd.org, jkh@freebsd.org Subject: Re: New 4.3 BETA (BETA2) release available MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="---=_460442.0691D2D6" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multipart message in MIME format. -----=_460442.0691D2D6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello ! Wed Mar 14 13:24, Jonathan Lemon wrote: > >> Anyway, please test the heck even more out of this one since we're > >> only 12 days away from the final release candidate! :) > > > >le nic driver is broken in all 4.x versions. Any chance that > >kern/25650 will be commited before 4.3-RELEASE? > > > >http://www.FreeBSD.org/cgi/query-pr.cgi?pr=25650 > > If someone who has a le card will confirm that the following patch > fixes the problem, (I don't have one here), then we should probably > be able to get it into 4.3. this patch (see attach) work fine for about a 4 weeks (it's yours patch + my one line) --- Best regards, { Vladimir Kurtukov, ICQ 2929697 } Vladimir { vk@hvv.svzserv.kemerovo.su } { 2:5006/9@fidonet } -----=_460442.0691D2D6 Content-Type: application/octet-stream; name="if_le.patch2" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="if_le.patch2" Content-Description: patch for le driver LS0tIGlmX2xlLmMub3JpZwlUdWUgSnVsIDE4IDA1OjI0OjMwIDIwMDAKKysrIGlmX2xlLmMJ VGh1IEFwciAxMiAxODowMDo1NSAyMDAxCkBAIC03Myw4ICs3Myw2IEBACiB0eXBlZGVmIHVf c2hvcnQgbGVfbWNiaXRzX3Q7CiAjZGVmaW5lCUxFX01DX05CUFdfTE9HMgkJNAogI2RlZmlu ZSBMRV9NQ19OQlBXCQkoMSA8PCBMRV9NQ19OQlBXX0xPRzIpCi0jZGVmaW5lCUlGX1JFU0VU X0FSR1MJaW50IHVuaXQKLSNkZWZpbmUJTEVfUkVTRVQoaWZwKQkoKChzYyktPmlmX3Jlc2V0 KSgoc2MpLT5sZV9pZi5pZl91bml0KSkKIAwKICNpZiAhZGVmaW5lZChMRV9OT0xFTUFDKQog LyoKQEAgLTE5Myw4ICsxOTEsOCBAQAogICovCiBzdHJ1Y3QgbGVfc29mdGMgewogICAgIHN0 cnVjdCBhcnBjb20gbGVfYWM7CQkvKiBDb21tb24gRXRoZXJuZXQvQVJQIFN0cnVjdHVyZSAq LwotICAgIHZvaWQgKCppZl9pbml0KSBfX1AoKGludCkpOwkJLyogSW50ZXJmYWNlIGluaXQg cm91dGluZSAqLwotICAgIHZvaWQgKCppZl9yZXNldCkgX19QKChpbnQpKTsJLyogSW50ZXJm YWNlIHJlc2V0IHJvdXRpbmUgKi8KKyAgICB2b2lkICgqaWZfaW5pdCkgX19QKChsZV9zb2Z0 Y190ICopKTsvKiBJbnRlcmZhY2UgaW5pdCByb3V0aW5lICovCisgICAgdm9pZCAoKmlmX3Jl c2V0KSBfX1AoKGxlX3NvZnRjX3QgKikpOy8qIEludGVyZmFjZSByZXNldCByb3V0aW5lICov CiAgICAgY2FkZHJfdCBsZV9tZW1iYXNlOwkJCS8qIFN0YXJ0aW5nIG1lbW9yeSBhZGRyZXNz ICh2aXJ0dWFsKSAqLwogICAgIHVuc2lnbmVkIGxlX2lvYmFzZTsJCQkvKiBTdGFydGluZyBJ L08gYmFzZSBhZGRyZXNzICovCiAgICAgdW5zaWduZWQgbGVfaXJxOwkJCS8qIEludGVycnVw dCBSZXF1ZXN0IFZhbHVlICovCkBAIC0zNDgsNiArMzQ2LDcgQEAKICAgICBpZnAtPmlmX2Zs YWdzID0gSUZGX0JST0FEQ0FTVCB8IElGRl9TSU1QTEVYIHwgSUZGX01VTFRJQ0FTVDsKICAg ICBpZnAtPmlmX291dHB1dCA9IGV0aGVyX291dHB1dDsKICAgICBpZnAtPmlmX2lvY3RsID0g bGVfaW9jdGw7CisgICAgaWZwLT5pZl9pbml0ID0gc2MtPmlmX2luaXQ7CiAgICAgaWZwLT5p Zl90eXBlID0gSUZUX0VUSEVSOwogICAgIGlmcC0+aWZfYWRkcmxlbiA9IDY7CiAgICAgaWZw LT5pZl9oZHJsZW4gPSAxNDsKQEAgLTQ0OCw3ICs0NDcsNyBAQAogICAgICAgICAgICAgICAg IGJyZWFrOwogCiAJY2FzZSBTSU9DU0lGRkxBR1M6IHsKLQkgICAgKCpzYy0+aWZfaW5pdCko aWZwLT5pZl91bml0KTsKKwkgICAgc2MtPmlmX2luaXQoc2MpOwogCSAgICBicmVhazsKIAl9 CiAKQEAgLTQ1Nyw3ICs0NTYsNyBAQAogCSAgICAvKgogCSAgICAgKiBVcGRhdGUgbXVsdGlj YXN0IGxpc3RlbmVycwogCSAgICAgKi8KLQkJKCpzYy0+aWZfaW5pdCkoaWZwLT5pZl91bml0 KTsKKwkJc2MtPmlmX2luaXQoc2MpOwogCQllcnJvciA9IDA7CiAJCWJyZWFrOwogCkBAIC02 MTUsOSArNjE0LDkgQEAKICNkZWZpbmUgTEVNQUNfMzJLX01PREUobWJhc2UpCSgoKG1iYXNl KSA+PSAweDE0KSAmJiAoKG1iYXNlKSA8PSAweDFGKSkKICNkZWZpbmUgTEVNQUNfMktfTU9E RShtYmFzZSkJKCAobWJhc2UpID49IDB4NDApCiAKLXN0YXRpYyB2b2lkIGxlbWFjX2luaXQo aW50IHVuaXQpOworc3RhdGljIHZvaWQgbGVtYWNfaW5pdChsZV9zb2Z0Y190ICpzYyk7CiBz dGF0aWMgdm9pZCBsZW1hY19zdGFydChzdHJ1Y3QgaWZuZXQgKmlmcCk7Ci1zdGF0aWMgdm9p ZCBsZW1hY19yZXNldChJRl9SRVNFVF9BUkdTKTsKK3N0YXRpYyB2b2lkIGxlbWFjX3Jlc2V0 KGxlX3NvZnRjX3QgKnNjKTsKIHN0YXRpYyB2b2lkIGxlbWFjX2ludHIobGVfc29mdGNfdCAq c2MpOwogc3RhdGljIHZvaWQgbGVtYWNfcm5lX2ludHIobGVfc29mdGNfdCAqc2MpOwogc3Rh dGljIHZvaWQgbGVtYWNfdG5lX2ludHIobGVfc29mdGNfdCAqc2MpOwpAQCAtNjk0LDcgKzY5 Myw3IEBACiAgICAgc2MtPmxlX2lmLmlmX3N0YXJ0ID0gbGVtYWNfc3RhcnQ7CiAgICAgc2Mt PmlmX3Jlc2V0ID0gbGVtYWNfcmVzZXQ7CiAgICAgc2MtPmxlbWFjX21lbW1vZGUgPSAyOwot ICAgIExFX1JFU0VUKHNjKTsKKyAgICBzYy0+aWZfcmVzZXQoc2MpOwogICAgIGlmICgoc2Mt PmxlX2ZsYWdzICYgSUZGX1VQKSA9PSAwKQogCXJldHVybiAwOwogCkBAIC03MjMsOSArNzIy LDggQEAKICAqLwogc3RhdGljIHZvaWQKIGxlbWFjX3Jlc2V0KAotICAgIElGX1JFU0VUX0FS R1MpCisgICAgbGVfc29mdGNfdCAqc2MpCiB7Ci0gICAgbGVfc29mdGNfdCAqc2MgPSAmbGVf c29mdGNbdW5pdF07CiAgICAgaW50IHBvcnR2YWwsIGNrc3VtOwogCiAgICAgLyoKQEAgLTc4 MSw5ICs3NzksOCBAQAogDAogc3RhdGljIHZvaWQKIGxlbWFjX2luaXQoCi0gICAgaW50IHVu aXQpCisgICAgbGVfc29mdGNfdCAqc2MpCiB7Ci0gICAgbGVfc29mdGNfdCAqc2MgPSAmbGVf c29mdGNbdW5pdF07CiAgICAgaW50IHM7CiAKICAgICBpZiAoKHNjLT5sZV9mbGFncyAmIElG Rl9VUCkgPT0gMCkKQEAgLTk0OCw5ICs5NDUsOSBAQAogICAgIHByaW50ZigiJXMlZDogZmF0 YWwgUlhEIGVycm9yLCBhdHRlbXB0aW5nIHJlY292ZXJ5XG4iLAogCSAgIHNjLT5sZV9pZi5p Zl9uYW1lLCBzYy0+bGVfaWYuaWZfdW5pdCk7CiAKLSAgICBMRV9SRVNFVChzYyk7CisgICAg c2MtPmlmX3Jlc2V0KHNjKTsKICAgICBpZiAoc2MtPmxlX2ZsYWdzICYgSUZGX1VQKSB7Ci0J bGVtYWNfaW5pdChzYy0+bGVfaWYuaWZfdW5pdCk7CisJbGVtYWNfaW5pdChzYyk7CiAJcmV0 dXJuOwogICAgIH0KIApAQCAtMTE0Miw4ICsxMTM5LDggQEAKIHN0YXRpYyBpbnQgIGxhbmNl X2luaXRfcmluZyhsZV9zb2Z0Y190ICpzYywgbG5fcmluZ190ICpycCwgbGFuY2VfcmluZ190 ICpyaSwKIAkJCSAgICB1bnNpZ25lZCBuZGVzY3MsIHVuc2lnbmVkIGJ1Zm9mZnNldCwKIAkJ CSAgICB1bnNpZ25lZCBkZXNjb2Zmc2V0KTsKLXN0YXRpYyB2b2lkIGxhbmNlX2luaXQoaW50 IHVuaXQpOwotc3RhdGljIHZvaWQgbGFuY2VfcmVzZXQoSUZfUkVTRVRfQVJHUyk7CitzdGF0 aWMgdm9pZCBsYW5jZV9pbml0KGxlX3NvZnRjX3QgKnNjKTsKK3N0YXRpYyB2b2lkIGxhbmNl X3Jlc2V0KGxlX3NvZnRjX3QgKnNjKTsKIHN0YXRpYyB2b2lkIGxhbmNlX2ludHIobGVfc29m dGNfdCAqc2MpOwogc3RhdGljIGludCAgbGFuY2VfcnhfaW50cihsZV9zb2Z0Y190ICpzYyk7 CiBzdGF0aWMgdm9pZCBsYW5jZV9zdGFydChzdHJ1Y3QgaWZuZXQgKmlmcCk7CkBAIC0xMzY3 LDcgKzEzNjQsNyBAQAogICAgIHNjLT5pZl9pbml0ID0gbGFuY2VfaW5pdDsKICAgICBzYy0+ bGVfaWYuaWZfc3RhcnQgPSBsYW5jZV9zdGFydDsKICAgICBERVBDQV9XUk5JQ1NSKHNjLCBE RVBDQV9OSUNTUl9TSEUgfCBERVBDQV9OSUNTUl9FTkFCSU5UUik7Ci0gICAgTEVfUkVTRVQo c2MpOworICAgIHNjLT5pZl9yZXNldChzYyk7CiAKICAgICBMTl9TVEFUKGxvd190eGZyZWUg PSBzYy0+bGFuY2VfdHhpbmZvLnJpX21heCk7CiAgICAgTE5fU1RBVChsb3dfdHhoZWFwc2l6 ZSA9IDB4RkZGRkZGRkYpOwpAQCAtMTUyMCw5ICsxNTE3LDggQEAKIAogc3RhdGljIHZvaWQK IGxhbmNlX3Jlc2V0KAotICAgIElGX1JFU0VUX0FSR1MpCisgICAgbGVfc29mdGNfdCAqc2Mp CiB7Ci0gICAgbGVfc29mdGNfdCAqc2MgPSAmbGVfc29mdGNbdW5pdF07CiAgICAgcmVnaXN0 ZXIgaW50IGNudCwgY3NyOwogCiAgICAgLyogbGFuY2VfZHVtcGNzcnMoc2MsICJsYW5jZV9y ZXNldDogc3RhcnQiKTsgKi8KQEAgLTE1ODUsMTYgKzE1ODEsMTUgQEAKIAwKIHN0YXRpYyB2 b2lkCiBsYW5jZV9pbml0KAotICAgIGludCB1bml0KQorICAgIGxlX3NvZnRjX3QgKnNjKQog ewotICAgIGxlX3NvZnRjX3QgKnNjID0gJmxlX3NvZnRjW3VuaXRdOwogICAgIGxhbmNlX3Jp bmdfdCAqcmk7CiAgICAgbGFuY2VfZGVzY2luZm9fdCAqZGk7CiAgICAgbG5fZGVzY190IGRl c2M7CiAKICAgICBMTl9TVEFUKGluaXRzKyspOwogICAgIGlmIChzYy0+bGVfaWYuaWZfZmxh Z3MgJiBJRkZfUlVOTklORykgewotCUxFX1JFU0VUKHNjKTsKKyAgICAgICAgc2MtPmlmX3Jl c2V0KHNjKTsKIAlsYW5jZV90eF9pbnRyKHNjKTsKIAkvKgogCSAqIElmIHdlIHdlcmUgcnVu bmluZywgcmVxdWV1ZSBhbnkgcGVuZGluZyB0cmFuc21pdHMuCkBAIC0xNjExLDcgKzE2MDYs NyBAQAogCSAgICByaS0+cmlfZnJlZSsrOwogCX0KICAgICB9IGVsc2UgewotCUxFX1JFU0VU KHNjKTsKKyAgICAgICAgc2MtPmlmX3Jlc2V0KHNjKTsKICAgICB9CiAKICAgICAvKgpAQCAt MTY4NSwxNCArMTY4MCwxNCBAQAogCWlmIChvbGRjc3IgJiBMTl9DU1IwX01FTUVSUk9SKSB7 CiAJICAgIExOX1NUQVQobWVtb3J5X2Vycm9ycysrKTsKIAkgICAgaWYgKG9sZGNzciAmIChM Tl9DU1IwX1JYT058TE5fQ1NSMF9UWE9OKSkgewotCQlsYW5jZV9pbml0KHNjLT5sZV9pZi5p Zl91bml0KTsKKwkJbGFuY2VfaW5pdChzYyk7CiAJCXJldHVybjsKIAkgICAgfQogCX0KICAg ICB9CiAKICAgICBpZiAoKG9sZGNzciAmIExOX0NTUjBfUlhJTlQpICYmIGxhbmNlX3J4X2lu dHIoc2MpKSB7Ci0JbGFuY2VfaW5pdChzYy0+bGVfaWYuaWZfdW5pdCk7CisJbGFuY2VfaW5p dChzYyk7CiAJcmV0dXJuOwogICAgIH0KIApAQCAtMTk2MSw3ICsxOTU2LDcgQEAKIAkJICAg IExOX1NUQVQodHhfYnVmZXJyb3IrKyk7CiAJCXNjLT5sZV9pZi5pZl9vZXJyb3JzKys7CiAJ CWlmICgoZGVzYy5kX3N0YXR1cyAmIExOX0RTVFNfVHhMQVRFQ09MTCkgPT0gMCkgewotCQkg ICAgbGFuY2VfaW5pdChzYy0+bGVfaWYuaWZfdW5pdCk7CisJCSAgICBsYW5jZV9pbml0KHNj KTsKIAkJICAgIHJldHVybiAwOwogCQl9IGVsc2UgewogCQkgICAgTE5fU1RBVCh0eF9sYXRl X2NvbGxpc2lvbnMrKyk7Cg== -----=_460442.0691D2D6-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 4: 1: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nothing-going-on.demon.co.uk (unknown [194.128.198.234]) by hub.freebsd.org (Postfix) with ESMTP id 7858C37B440 for ; Thu, 12 Apr 2001 04:01:02 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id f3C7xU680584; Thu, 12 Apr 2001 08:59:30 +0100 (BST) (envelope-from nik) Date: Thu, 12 Apr 2001 08:59:30 +0100 From: Nik Clayton To: j mckitrick Cc: freebsd-stable@freebsd.org Subject: Re: www supfile Message-ID: <20010412085930.B80546@canyon.nothing-going-on.org> References: <20010412001227.A79583@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="8GpibOaaTibBMecb" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010412001227.A79583@dogma.freebsd-uk.eu.org>; from jcm@FreeBSD-uk.eu.org on Thu, Apr 12, 2001 at 12:12:27AM +0100 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --8GpibOaaTibBMecb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 12, 2001 at 12:12:27AM +0100, j mckitrick wrote: > I've noticed that 'www/en' no longer works as a valid tag for cvsup files. > But the 'www/en' directory still exists. I must have missed something > somewhere. Is there revised documentation somewhere? What do you mean by 'tag'? On a '*default tag=3D' line? N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- --8GpibOaaTibBMecb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjrVYGAACgkQk6gHZCw343UHmgCeOygRJaJjuCwhOQ5DaJHzdtSz 5PYAnRaMmFq5UFmjTQ6KJKywtQfOQKUf =zY3K -----END PGP SIGNATURE----- --8GpibOaaTibBMecb-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 4: 1:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nothing-going-on.demon.co.uk (unknown [194.128.198.234]) by hub.freebsd.org (Postfix) with ESMTP id 5A27D37B443; Thu, 12 Apr 2001 04:01:18 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id f3C7vMg80573; Thu, 12 Apr 2001 08:57:22 +0100 (BST) (envelope-from nik) Date: Thu, 12 Apr 2001 08:57:22 +0100 From: Nik Clayton To: Dan Langille Cc: Nik Clayton , stable@FreeBSD.ORG Subject: Re: Releases Message-ID: <20010412085722.A80546@canyon.nothing-going-on.org> References: <15059.502.493117.364068@guru.mired.org>; <20010411225157.A72900@canyon.nothing-going-on.org> <200104112220.f3BMKPe96220@ns1.unixathome.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="nFreZHaLTZJo0R7j" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104112220.f3BMKPe96220@ns1.unixathome.org>; from dan@langille.org on Wed, Apr 11, 2001 at 06:20:18PM -0400 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --nFreZHaLTZJo0R7j Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 11, 2001 at 06:20:18PM -0400, Dan Langille wrote: > On 11 Apr 2001, at 22:51, Nik Clayton wrote: >=20 > > Done. >=20 > Did I miss the commit? When was this done? 21:50 last night, to src/share/examples/cvsup/standard-supfile, on the RELENG_4 branch. ID 1.17.2.2. N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- --nFreZHaLTZJo0R7j Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjrVX+EACgkQk6gHZCw343UJKQCffIYMYPFSeL0UOTkaH2hUX2GO m/oAnir/O+UAq3+voqcwg/iyMiJo897y =5F04 -----END PGP SIGNATURE----- --nFreZHaLTZJo0R7j-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 4: 9:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id 9983837B42C; Thu, 12 Apr 2001 04:09:21 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by probity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14neyV-000OMa-00; Thu, 12 Apr 2001 12:09:19 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f3CB9Ib89374; Thu, 12 Apr 2001 12:09:18 +0100 (BST) (envelope-from jcm) Date: Thu, 12 Apr 2001 12:09:18 +0100 From: j mckitrick To: Nik Clayton Cc: freebsd-stable@freebsd.org Subject: Re: www supfile Message-ID: <20010412120918.A89288@dogma.freebsd-uk.eu.org> References: <20010412001227.A79583@dogma.freebsd-uk.eu.org> <20010412085930.B80546@canyon.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010412085930.B80546@canyon.nothing-going-on.org>; from nik@freebsd.org on Thu, Apr 12, 2001 at 08:59:30AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 12, 2001 at 08:59:30AM +0100, Nik Clayton wrote: | On Thu, Apr 12, 2001 at 12:12:27AM +0100, j mckitrick wrote: | > I've noticed that 'www/en' no longer works as a valid tag for cvsup files. | > But the 'www/en' directory still exists. I must have missed something | > somewhere. Is there revised documentation somewhere? | | What do you mean by 'tag'? On a '*default tag=' line? I guess that was the wrong word. local:~> cat .admin/www-supfile # $Id: www-supfile,v 1.1 2001/02/21 13:06:54 jcm Exp jcm $ #*default host=216.94.113.4 #*default host=cvsup3.freebsd.org *default host=cvsup5.freebsd.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix *default compress # This collection retrieves the www/ tree of the FreeBSD repository www/en/ jm -- ------------------------------------------- Jonathon McKitrick -- jcm@freebsd-uk.eu.org Do not mistake lack of talent for genius ------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 4:13:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id 26EEA37B423 for ; Thu, 12 Apr 2001 04:13:09 -0700 (PDT) (envelope-from olli@lurza.secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.9.3/8.9.3) id NAA23060; Thu, 12 Apr 2001 13:13:08 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Date: Thu, 12 Apr 2001 13:13:08 +0200 (CEST) Message-Id: <200104121113.NAA23060@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG Reply-To: freebsd-stable@FreeBSD.ORG Subject: Re: make release broken with too many ports/distfiles... In-Reply-To: X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.1-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tim Zingelman wrote: > So the quick answer is figure out what subset of distfiles I need, put > them someplace other than /usr/ports/distfiles & set DOCDISTFILES. You could, of course, set up a simple FTP server on localhost, and let ``make release'' fetch the distfiles that it needs itself. That's what I do, kind of. ;-) So I never have to think about what distfiles it needs. (Requires a small hack to the release Makefile so that there's an appropriate setting for the MASTER_SITE in the chroot's make.conf.) Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 4:30:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id 7E93537B423 for ; Thu, 12 Apr 2001 04:30:08 -0700 (PDT) (envelope-from rasputin@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14nfId-000Hs0-00 for stable@freebsd.org; Thu, 12 Apr 2001 12:30:07 +0100 Received: (from rasputin@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f3CBU7v89769 for stable@freebsd.org; Thu, 12 Apr 2001 12:30:07 +0100 (BST) (envelope-from rasputin) Date: Thu, 12 Apr 2001 12:30:07 +0100 From: Rasputin To: stable@freebsd.org Subject: PicoBSD Message-ID: <20010412123007.A89724@dogma.freebsd-uk.eu.org> Reply-To: Rasputin Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone got any up to date docs on it? (They're in /usr/src/release somewhere but they're hiding) The website mentions running a build shell script, but it doesn't seem to exist. Thanks -- Rasputin Jack of All Trades :: Master of Nuns To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 5:13:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from snoop.burghcom.com (burgcom.cust.stargate.net [209.166.166.21]) by hub.freebsd.org (Postfix) with SMTP id B79D437B440 for ; Thu, 12 Apr 2001 05:13:13 -0700 (PDT) (envelope-from jl@burghcom.com) Received: (qmail 25766 invoked from network); 12 Apr 2001 12:13:12 -0000 Received: from merlin.hq.sgi.net (HELO merlin) (jl@209.166.162.10) by snoop.burghcom.com with SMTP; 12 Apr 2001 12:13:12 -0000 From: Jeff Love To: freebsd-stable@freebsd.org Subject: Re: Problems with 3c905B and 4.3-RC Date: Thu, 12 Apr 2001 08:11:27 -0400 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <3AD4CBC3.F3E79AFC@rtci.com> In-Reply-To: <3AD4CBC3.F3E79AFC@rtci.com> MIME-Version: 1.0 Message-Id: <01041208131800.29806@merlin> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not sure if this is the problem in your case, but did you include 'device miibus' to your kernel config? This was a fairly recent addition needed for 3com nics. -- Jeff Love jl@burghcom.com ----------------- Burgh-Com On Wed, 11 Apr 2001, Jeremy Hopkins wrote: > I have just installed a FreeBSD 4.1.1-RELEASE box. I had to start there > as my 3c905B card did not show in an ifconfig -a using newer floppies so > I reverted to 4.1.1 I got the box up and running and did a cvsup to > 4.3-RC, made/installed world and kernel just fine. However I notice I > have no network interface at xl0 like I did before the reboot into > 4.3-RC. > > xl0 shows up in dmesg but I get error messages along with it. > > xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 10 at device 15.0 on pci0 > xl0: couldn't map ports/memory > device_probe_and_attach: xl0 attach returned 6 > > I had also had the same error messages about my sound card pcm0. I have > removed the sound card to eliminate the possibility these are > conflicting, and the dmesg below is without the sound card in the > system. It appears there was some talk about this back in Sept. 2000 in > the -current list, but I can't seem to find a resolution on it. > > Thanks in advance, > > Jeremy > -- > Jeremy Hopkins > Systems Administrator > www.icc.net www.rtci.com > For those who like this sort of thing, this is the sort of thing they > like. -- Abraham Lincoln > > > > below is copy of full dmesg output- > ------------------------------ > Copyright (c) 1992-2001 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights > reserved. > FreeBSD 4.3-RC #0: Wed Apr 11 18:50:15 GMT 2001 > root@shadow.ghettoweb.net:/usr/obj/usr/src/sys/GUNSHOT > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium III/Pentium III Xeon/Celeron (497.84-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x673 Stepping = 3 > > Features=0x383f9ff > real memory = 134217728 (131072K bytes) > avail memory = 126545920 (123580K bytes) > Preloaded elf kernel "kernel" at 0xc03e1000. > 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 > pci1: at 0.0 irq 11 > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port 0x1000-0x100f at device 7.1 > on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > uhci0: port 0x1020-0x103f irq > 9 at device 7.2 on pci0 > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > chip1: port 0x7000-0x700f at > device 7.3 on pci0 > xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 10 at device 15.0 on pci0 > xl0: couldn't map ports/memory > device_probe_and_attach: xl0 attach returned 6 > fdc0: at port 0x3f0-0x3f5,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,0x64 on isa0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > psm0: irq 12 on atkbdc0 > psm0: model IntelliMouse, device ID 3 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on > isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1: configured irq 3 not in bitmap of probed irqs 0 > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/8 bytes threshold > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > IPsec: Initialized Security Association Processing. > ad0: 9787MB [19885/16/63] at ata0-master UDMA33 > ad1: 9787MB [19885/16/63] at ata0-slave UDMA33 > acd0: CDROM at ata1-master using PIO4 > afd0: 96MB [96/64/32] at ata1-slave using PIO3 > Mounting root from ufs:/dev/ad0s1a > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Jeff Love jl@burghcom.com ----------------- Burgh-Com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 5:21:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gactr.uga.edu (mail.gactr.uga.edu [128.192.37.21]) by hub.freebsd.org (Postfix) with SMTP id E321537B42C for ; Thu, 12 Apr 2001 05:21:46 -0700 (PDT) (envelope-from Robin_Blanchard@gactr.uga.edu) Received: (qmail 20585 invoked from network); 12 Apr 2001 12:21:42 -0000 Received: from qat.noc.nat (HELO gactr.uga.edu) ([10.10.100.125]) (envelope-sender ) by mail.servers.nat (qmail-ldap-1.03) with SMTP for ; 12 Apr 2001 12:21:42 -0000 Message-ID: <3AD59DA9.74D41EED@gactr.uga.edu> Date: Thu, 12 Apr 2001 08:20:57 -0400 From: "Robin P. Blanchard" X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: soundcard woes... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i'm trying to setup icecast + liveice and all seemed well until it came time to actually capture audio. i'm using 4.3-RC (latest cvs) with an tried and true ensoniq 1370. playback is fine. line-in is fine (as i can hook up a line-in source and hear everything, adjust the mixer settings for the line-device, etc). however, if i try to capture anything, i end with silence. nothing. liveice was transmitting dead silence to icecast, so i stopped everything and began to test if i could in fact capture audio at all (using wavplay/wavrec). i get nothing but silence when i attempt to capture. don't even have any useful errors or logs here. must be something silly i'm overlooking. please advise. -- ------------------------------------ Robin P. Blanchard IT Program Specialist Georgia Center for Continuing Ed. fon: 706.542.2404 fax: 706.542.6546 email: Robin_Blanchard@gactr.uga.edu ------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 5:23:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id F260837B423 for ; Thu, 12 Apr 2001 05:23:06 -0700 (PDT) (envelope-from dwcjr@inethouston.net) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id 07EDF10F400; Thu, 12 Apr 2001 07:23:08 -0500 (CDT) Message-ID: <045c01c0c34b$588d6980$931576d8@inethouston.net> From: "David W. Chapman Jr." To: "Jeff Love" , References: <3AD4CBC3.F3E79AFC@rtci.com> <01041208131800.29806@merlin> Subject: Re: Problems with 3c905B and 4.3-RC Date: Thu, 12 Apr 2001 07:23:14 -0500 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.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No, he solved the problem already by setting pnp OS to off I believe. ----- Original Message ----- From: "Jeff Love" To: Sent: Thursday, April 12, 2001 7:11 AM Subject: Re: Problems with 3c905B and 4.3-RC > Not sure if this is the problem in your case, but did you include 'device > miibus' to your kernel config? This was a fairly recent addition needed for > 3com nics. > -- > Jeff Love > jl@burghcom.com > ----------------- > Burgh-Com > > On Wed, 11 Apr 2001, Jeremy Hopkins wrote: > > I have just installed a FreeBSD 4.1.1-RELEASE box. I had to start there > > as my 3c905B card did not show in an ifconfig -a using newer floppies so > > I reverted to 4.1.1 I got the box up and running and did a cvsup to > > 4.3-RC, made/installed world and kernel just fine. However I notice I > > have no network interface at xl0 like I did before the reboot into > > 4.3-RC. > > > > xl0 shows up in dmesg but I get error messages along with it. > > > > xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 10 at device 15.0 on pci0 > > xl0: couldn't map ports/memory > > device_probe_and_attach: xl0 attach returned 6 > > > > I had also had the same error messages about my sound card pcm0. I have > > removed the sound card to eliminate the possibility these are > > conflicting, and the dmesg below is without the sound card in the > > system. It appears there was some talk about this back in Sept. 2000 in > > the -current list, but I can't seem to find a resolution on it. > > > > Thanks in advance, > > > > Jeremy > > -- > > Jeremy Hopkins > > Systems Administrator > > www.icc.net www.rtci.com > > For those who like this sort of thing, this is the sort of thing they > > like. -- Abraham Lincoln > > > > > > > > below is copy of full dmesg output- > > ------------------------------ > > Copyright (c) 1992-2001 The FreeBSD Project. > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > > The Regents of the University of California. All rights > > reserved. > > FreeBSD 4.3-RC #0: Wed Apr 11 18:50:15 GMT 2001 > > root@shadow.ghettoweb.net:/usr/obj/usr/src/sys/GUNSHOT > > Timecounter "i8254" frequency 1193182 Hz > > CPU: Pentium III/Pentium III Xeon/Celeron (497.84-MHz 686-class CPU) > > Origin = "GenuineIntel" Id = 0x673 Stepping = 3 > > > > Features=0x383f9ff > > real memory = 134217728 (131072K bytes) > > avail memory = 126545920 (123580K bytes) > > Preloaded elf kernel "kernel" at 0xc03e1000. > > 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 > > pci1: at 0.0 irq 11 > > isab0: at device 7.0 on pci0 > > isa0: on isab0 > > atapci0: port 0x1000-0x100f at device 7.1 > > on pci0 > > ata0: at 0x1f0 irq 14 on atapci0 > > ata1: at 0x170 irq 15 on atapci0 > > uhci0: port 0x1020-0x103f irq > > 9 at device 7.2 on pci0 > > usb0: on uhci0 > > usb0: USB revision 1.0 > > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > > uhub0: 2 ports with 2 removable, self powered > > chip1: port 0x7000-0x700f at > > device 7.3 on pci0 > > xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 10 at device 15.0 on pci0 > > xl0: couldn't map ports/memory > > device_probe_and_attach: xl0 attach returned 6 > > fdc0: at port 0x3f0-0x3f5,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,0x64 on isa0 > > atkbd0: flags 0x1 irq 1 on atkbdc0 > > kbd0 at atkbd0 > > psm0: irq 12 on atkbdc0 > > psm0: model IntelliMouse, device ID 3 > > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on > > isa0 > > sc0: at flags 0x100 on isa0 > > sc0: VGA <16 virtual consoles, flags=0x300> > > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > > sio0: type 16550A > > sio1: configured irq 3 not in bitmap of probed irqs 0 > > ppc0: at port 0x378-0x37f irq 7 on isa0 > > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > > ppc0: FIFO with 16/16/8 bytes threshold > > lpt0: on ppbus0 > > lpt0: Interrupt-driven port > > ppi0: on ppbus0 > > IPsec: Initialized Security Association Processing. > > ad0: 9787MB [19885/16/63] at ata0-master UDMA33 > > ad1: 9787MB [19885/16/63] at ata0-slave UDMA33 > > acd0: CDROM at ata1-master using PIO4 > > afd0: 96MB [96/64/32] at ata1-slave using PIO3 > > Mounting root from ufs:/dev/ad0s1a > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > -- > Jeff Love > jl@burghcom.com > ----------------- > Burgh-Com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 5:31:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from slackerbsd.org (cn434050-d.wall1.pa.home.com [24.40.72.54]) by hub.freebsd.org (Postfix) with SMTP id 35FD037B43F for ; Thu, 12 Apr 2001 05:31:22 -0700 (PDT) (envelope-from lists@slackerbsd.org) Received: (qmail 39727 invoked by uid 1029); 12 Apr 2001 12:31:20 -0000 Date: Thu, 12 Apr 2001 08:31:20 -0400 From: Carl Schmidt To: freebsd-stable@freebsd.org Subject: Re: soundcard woes... Message-ID: <20010412083120.A67001@slackerbsd.org> References: <3AD59DA9.74D41EED@gactr.uga.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Mutt/1.2.5i In-Reply-To: <3AD59DA9.74D41EED@gactr.uga.edu>; from Robin_Blanchard@gactr.uga.edu on Thu, Apr 12, 2001 at 08:20:57AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Funny, I have an ensoniq 1371 card and have the same problem. All the mixer controls work fine but the input isn't doing anything. No sound, nothing. As you said, there are no errors anywhere or anything of the sort, just silence on the input. =3D( Carl Schmidt http://slackerbsd.org/ On Thu, Apr 12, 2001 at 08:20:57AM -0400, Robin P. Blanchard wrote: > Delivered-To: lists@slackerbsd.org > Delivered-To: freebsd-stable@freebsd.org > Date: Thu, 12 Apr 2001 08:20:57 -0400 > From: "Robin P. Blanchard" > X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) > X-Accept-Language: en > To: stable@freebsd.org > Subject: soundcard woes... > X-Loop: FreeBSD.ORG > Precedence: bulk >=20 > i'm trying to setup icecast + liveice and all seemed well until > it came time to actually capture audio. >=20 > i'm using 4.3-RC (latest cvs) with an tried and true ensoniq 1370. > playback is fine. line-in is fine (as i can hook up a line-in source > and hear everything, adjust the mixer settings for the line-device, etc). > however, if i try to capture anything, i end with silence. nothing. > liveice was transmitting dead silence to icecast, so i stopped everything > and began to test if i could in fact capture audio at all (using > wavplay/wavrec). > i get nothing but silence when i attempt to capture. >=20 > don't even have any useful errors or logs here. must be something silly i= 'm > overlooking. please advise. >=20 >=20 > --=20 > ------------------------------------ > Robin P. Blanchard > IT Program Specialist > Georgia Center for Continuing Ed. > fon: 706.542.2404 fax: 706.542.6546 > email: Robin_Blanchard@gactr.uga.edu > ------------------------------------ >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 5:36:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from clueless.redbus.aaisp.net (clueless.redbus.aaisp.net [213.161.73.195]) by hub.freebsd.org (Postfix) with SMTP id 005CA37B43F for ; Thu, 12 Apr 2001 05:36:45 -0700 (PDT) (envelope-from jon@witchspace.com) Received: from zebedee.innovision-group.com (HELO:garfield.innovisiongroup.com) by clueless.redbus.aaisp.net for freebsd-stable@FreeBSD.ORG; Thu, 12 Apr 2001 12:26:43 +0100 Message-ID: <00ab01c0c344$6c819d00$650e850a@innovisiongroup.com> From: "Jonathan Belson" To: "Cyrille Lefevre" Cc: "FreeBSD-stable" References: <3AD427DC.CFC52BAE@quake.com.au> <004c01c0c26e$21b6e7c0$650e850a@innovisiongroup.com> <3AD566AD.68D9FC2E@witchspace.com> Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) Date: Thu, 12 Apr 2001 12:33:37 +0100 Organization: Jon's Place 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.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hiya > > also, is the Radeon really 3D accelated ? does someone has a working > > OpenGL for Radeon ? not sure. > > I remember reading an email by one of the contracted glx/dri (?) > developers that he was trying to write the drivers in such a way > that it would work with *BSD too - I can't remember any details sadly, > I'll see if I can find the email. Couldn't find the mail I was thinking of, but take a look at: http://www.geocrawler.com/archives/3/680/2000/2/0/3282410/ From reading through the dri-devel archives, it looks like Doug Rabson has done some work on the FreeBSD port, but apparently doesn't have much time to work on it due to other commitments. Any volunteers? 8^) -- C-YA Jon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 5:37:28 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gactr.uga.edu (mail.gactr.uga.edu [128.192.37.21]) by hub.freebsd.org (Postfix) with SMTP id E4F9737B422 for ; Thu, 12 Apr 2001 05:37:24 -0700 (PDT) (envelope-from Robin_Blanchard@gactr.uga.edu) Received: (qmail 21905 invoked from network); 12 Apr 2001 12:37:24 -0000 Received: from qat.noc.nat (HELO gactr.uga.edu) ([10.10.100.125]) (envelope-sender ) by mail.servers.nat (qmail-ldap-1.03) with SMTP for ; 12 Apr 2001 12:37:24 -0000 Message-ID: <3AD5A157.E6BD49CF@gactr.uga.edu> Date: Thu, 12 Apr 2001 08:36:39 -0400 From: "Robin P. Blanchard" X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 Cc: freebsd-stable@freebsd.org Subject: Re: soundcard woes... References: <3AD59DA9.74D41EED@gactr.uga.edu> <20010412083120.A67001@slackerbsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG my "input isn't doing anything" do you mean you have no line-in audio whatsoever? i am able to use my line-in (and adjust its volume via the mixer), i am only unable to capture it using any common tool. > Funny, I have an ensoniq 1371 card and have the same problem. All the mixer > controls work fine but the input isn't doing anything. No sound, nothing. > As you said, there are no errors anywhere or anything of the sort, just > silence on the input. =( > > Carl Schmidt > http://slackerbsd.org/ > > On Thu, Apr 12, 2001 at 08:20:57AM -0400, Robin P. Blanchard wrote: > > Delivered-To: lists@slackerbsd.org > > Delivered-To: freebsd-stable@freebsd.org > > Date: Thu, 12 Apr 2001 08:20:57 -0400 > > From: "Robin P. Blanchard" > > X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) > > X-Accept-Language: en > > To: stable@freebsd.org > > Subject: soundcard woes... > > X-Loop: FreeBSD.ORG > > Precedence: bulk > > > > i'm trying to setup icecast + liveice and all seemed well until > > it came time to actually capture audio. > > > > i'm using 4.3-RC (latest cvs) with an tried and true ensoniq 1370. > > playback is fine. line-in is fine (as i can hook up a line-in source > > and hear everything, adjust the mixer settings for the line-device, etc). > > however, if i try to capture anything, i end with silence. nothing. > > liveice was transmitting dead silence to icecast, so i stopped everything > > and began to test if i could in fact capture audio at all (using > > wavplay/wavrec). > > i get nothing but silence when i attempt to capture. > > > > don't even have any useful errors or logs here. must be something silly i'm > > overlooking. please advise. -- ------------------------------------ Robin P. Blanchard IT Program Specialist Georgia Center for Continuing Ed. fon: 706.542.2404 fax: 706.542.6546 email: Robin_Blanchard@gactr.uga.edu ------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 5:40:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gactr.uga.edu (mail.gactr.uga.edu [128.192.37.21]) by hub.freebsd.org (Postfix) with SMTP id B809337B440 for ; Thu, 12 Apr 2001 05:40:06 -0700 (PDT) (envelope-from Robin_Blanchard@gactr.uga.edu) Received: (qmail 22182 invoked from network); 12 Apr 2001 12:40:06 -0000 Received: from qat.noc.nat (HELO gactr.uga.edu) ([10.10.100.125]) (envelope-sender ) by mail.servers.nat (qmail-ldap-1.03) with SMTP for ; 12 Apr 2001 12:40:06 -0000 Message-ID: <3AD5A1F9.7133FC74@gactr.uga.edu> Date: Thu, 12 Apr 2001 08:39:21 -0400 From: "Robin P. Blanchard" X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: [Fwd: install world on 486] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i cvs'd (src-all tag=RELENG_4) this morning and rebuilt on a i686 with the following make.conf: FETCH_BEFORE_ARGS=-p USA_RESIDENT=yes MAKE_IDEA=YES #CPUTYPE=i486 CFLAGS=-O -pipe COPTFLAGS=-O -pipe CXXFLAGS+= -fmemoize-lookups -fsave-memoized i did the make as such: make MAKEOBJDIRPREFIX=/usr/obj-486 clean buildworld and mounted /usr/obj-486 (and /usr/src) appropriately on the 486 that this build was destined for. the make.conf on the 486 is as follows: FETCH_BEFORE_ARGS=-p USA_RESIDENT=yes MAKE_IDEA=YES #CPUTYPE=i486 CFLAGS=-O -pipe COPTFLAGS=-O -pipe CXXFLAGS+= -fmemoize-lookups -fsave-memoized installworld on the 486 dies with: pid 2645 (strip), uid 0: exited on signal 4 (core dumped) *** Error code 70 Stop in /usr/src/lib/libcom_err i commented out the CPUTYPE from each make.conf as i seem to recall someone claiming they had this similar problem when setting the CPUTYPE. i've attached the core file as well. any ideas as to how to get my poor old 486 working? :) i've been attempting to post this for over a week now; but realised that the strip.core attachment seemed to be causing my message to never get delivered. ideas on how to post the core file would also be appreciated. thanks in advance. -- ------------------------------------ Robin P. Blanchard IT Program Specialist Georgia Center for Continuing Ed. fon: 706.542.2404 fax: 706.542.6546 email: Robin_Blanchard@gactr.uga.edu ------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 5:57:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from slackerbsd.org (cn434050-d.wall1.pa.home.com [24.40.72.54]) by hub.freebsd.org (Postfix) with SMTP id EC1D837B423 for ; Thu, 12 Apr 2001 05:57:06 -0700 (PDT) (envelope-from lists@slackerbsd.org) Received: (qmail 39907 invoked by uid 1029); 12 Apr 2001 12:57:05 -0000 Date: Thu, 12 Apr 2001 08:57:05 -0400 From: List handler To: "Robin P. Blanchard" Cc: freebsd-stable@freebsd.org Subject: Re: soundcard woes... Message-ID: <20010412085705.A39894@slackerbsd.org> References: <3AD59DA9.74D41EED@gactr.uga.edu> <20010412083120.A67001@slackerbsd.org> <3AD5A157.E6BD49CF@gactr.uga.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="LQksG6bCIzRHxTLp" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AD5A157.E6BD49CF@gactr.uga.edu>; from Robin_Blanchard@gactr.uga.edu on Thu, Apr 12, 2001 at 08:36:39AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --LQksG6bCIzRHxTLp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Yeah I can control that part of the mixer and all but like you, I can't rec= ord anything from it. -- Carl Schmidt http://slackerbsd.org/ On Thu, Apr 12, 2001 at 08:36:39AM -0400, Robin P. Blanchard wrote: >=20 > my "input isn't doing anything" do you mean you have no line-in > audio whatsoever? i am able to use my line-in (and adjust its volume > via the mixer), i am only unable to capture it using any common tool. >=20 >=20 >=20 >=20 > > Funny, I have an ensoniq 1371 card and have the same problem. All the m= ixer > > controls work fine but the input isn't doing anything. No sound, nothin= g. > > As you said, there are no errors anywhere or anything of the sort, just > > silence on the input. =3D( > >=20 > > Carl Schmidt > > http://slackerbsd.org/ > >=20 > > On Thu, Apr 12, 2001 at 08:20:57AM -0400, Robin P. Blanchard wrote: > > > Delivered-To: lists@slackerbsd.org > > > Delivered-To: freebsd-stable@freebsd.org > > > Date: Thu, 12 Apr 2001 08:20:57 -0400 > > > From: "Robin P. Blanchard" > > > X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) > > > X-Accept-Language: en > > > To: stable@freebsd.org > > > Subject: soundcard woes... > > > X-Loop: FreeBSD.ORG > > > Precedence: bulk > > > > > > i'm trying to setup icecast + liveice and all seemed well until > > > it came time to actually capture audio. > > > > > > i'm using 4.3-RC (latest cvs) with an tried and true ensoniq 1370. > > > playback is fine. line-in is fine (as i can hook up a line-in source > > > and hear everything, adjust the mixer settings for the line-device, e= tc). > > > however, if i try to capture anything, i end with silence. nothing. > > > liveice was transmitting dead silence to icecast, so i stopped everyt= hing > > > and began to test if i could in fact capture audio at all (using > > > wavplay/wavrec). > > > i get nothing but silence when i attempt to capture. > > > > > > don't even have any useful errors or logs here. must be something sil= ly i'm > > > overlooking. please advise. >=20 > --=20 > ------------------------------------ > Robin P. Blanchard > IT Program Specialist > Georgia Center for Continuing Ed. > fon: 706.542.2404 fax: 706.542.6546 > email: Robin_Blanchard@gactr.uga.edu > ------------------------------------ >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message --LQksG6bCIzRHxTLp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: VMgNxiUeQhCwaMlrJgpT1IppZvq/AbeK iQA/AwUBOtWmHsnZAPSvxuenEQLrnwCfRlriyEpUMjWoZR9sGLxQKy/XG9IAoORe hABe9fjrR5yUKblkrL3HrZQ8 =RyvP -----END PGP SIGNATURE----- --LQksG6bCIzRHxTLp-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 6:41:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from junkun.vblab.tsukuba.ac.jp (junkun.vbl.tsukuba.ac.jp [130.158.94.147]) by hub.freebsd.org (Postfix) with ESMTP id 043DF37B42C for ; Thu, 12 Apr 2001 06:41:08 -0700 (PDT) (envelope-from junkun@esys.tsukuba.ac.jp) Received: from localhost (junkun [192.168.2.147]) by junkun.vblab.tsukuba.ac.jp (8.11.3/8.11.3) with ESMTP id f3CDfGW16767 for ; Thu, 12 Apr 2001 22:41:16 +0900 (JST) (envelope-from junkun@esys.tsukuba.ac.jp) To: freebsd-stable@FreeBSD.ORG Subject: USB mouse with FreeBSD 4.3 RC3 From: Jun YAMASHITA X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010412224115R.junkun@esys.tsukuba.ac.jp> Date: Thu, 12 Apr 2001 22:41:15 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 84 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I'm using SONY PCG-SR1/BP notebook computer and I've installed FreeBSD 4.3RC3 just now(All sources were CVSuped several hours ago). In order to use USB mouse, I turn off PnP-OS support at the BIOS menu but when booting the system it seems to be frozen while probing ATA disks. It seems to be passed to boot sequence if I turn on PnP-OS support but usbd does not work with following message:No USB host controllers found. When I had used FreeBSD 4.2R, I could use USB mouce and had no problems. Are there anyone who can give advices to me? Jun Yamashita junkun@debug.gr.jp % dmesg Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.3-RC #3: Thu Apr 12 21:11:36 JST 2001 junkun@pcg-sr1.vbl.tsukuba.ac.jp:/usr/src/sys/compile/SR1 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (444.85-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x681 Stepping = 1 Features=0x383f9ff real memory = 67043328 (65472K bytes) avail memory = 62119936 (60664K bytes) Preloaded elf kernel "kernel" at 0xc0320000. Pentium Pro MTRR support enabled 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 pci1: at 0.0 irq 9 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xfcf0-0xfcff at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xfcc0-0xfcdf at device 7.2 on pci0 uhci0: Invalid irq 255 uhci0: Please switch on USB support and switch PNP-OS to 'No' in BIOS device_probe_and_attach: uhci0 attach returned 6 chip1: port 0x1040-0x104f at device 7.3 on pci0 pci0: (vendor=0x104d, dev=0x8039) at 8.0 pcm0: mem 0xfedf0000-0xfedf7fff irq 9 at device 9.0 on pci0 pci0: (vendor=0x14f1, dev=0x2443) at 10.0 pcic-pci0: at device 12.0 on pci0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model GlidePoint, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> pcic0: at port 0x3e0-0x3e1 on isa0 pcic0: Polling mode pccard0: on pcic0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 sio1: configured irq 3 not in bitmap of probed irqs 0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources ad0: 19077MB [38760/16/63] at ata0-master UDMA33 Mounting root from ufs:/dev/ad0s3a pccard: card inserted, slot 0 ed0 at port 0x240-0x25f irq 3 slot 0 on pccard0 ed0: address 00:00:f4:5e:25:4c, type Linksys (16 bit) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 6:44:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtpproxy1.mitre.org (mb-20-100.mitre.org [129.83.20.100]) by hub.freebsd.org (Postfix) with ESMTP id 7043F37B440 for ; Thu, 12 Apr 2001 06:44:47 -0700 (PDT) (envelope-from jandrese@mitre.org) Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58]) by smtpproxy1.mitre.org (8.9.3/8.9.3) with ESMTP id JAA27610 for ; Thu, 12 Apr 2001 09:44:39 -0400 (EDT) Received: from mailsrv2.mitre.org (mailsrv2.mitre.org [129.83.221.17]) by smtpsrv1.mitre.org (8.9.3/8.9.3) with ESMTP id JAA21801 for ; Thu, 12 Apr 2001 09:44:38 -0400 (EDT) Received: from mitre.org ([128.29.145.140]) by mailsrv2.mitre.org (Netscape Messaging Server 4.15) with ESMTP id GBOM6D00.7I4; Thu, 12 Apr 2001 09:44:37 -0400 Message-ID: <3AD5B145.EF09CEA4@mitre.org> Date: Thu, 12 Apr 2001 09:44:37 -0400 From: "Andresen,Jason R." X-Mailer: Mozilla 4.75 [en]C-20000818M (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Christian Chen Cc: Kal Torak , FreeBSD-stable Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: <20010412000523.I86970-100000@pirastro.oistrakh.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christian Chen wrote: > > On Thu, 12 Apr 2001, Kal Torak wrote: > > nVidia cards are really the ONLY choice to buy now... Not that Im complaining, > > Maybe this is just *my* personal quirkiness, but does anyone else out there > feel as though ATI's 2D performance is higher quality? And by higher quality, > I don't mean _faster_, I mean _looks better_. When I replaced my nVidia > card with an ATI Rage Fury Pro, and after that a Rage Fury Maxx, the text > looked crisper, and images were sharper. Granted, these things are > irrevelant to 3D gamers, but for all those sysadmins out there, it sure > is nice having crisper console screens and xterms. > > But maybe it's just me. Lots of people don't notice 60Hz scan rate > flicker, but I do ... 2D performance, coupled with the Windows drivers has always kept me with Matrox personally. XFree-4 supports Xv with my G200 (hardware scaling rules on full motion video, especally when you have a fixed frequency 1280x1024 monitor). XFree will do Xv with newer ATI cards too IIRC, however in Windows (still have to reboot to play games and run the occasional Window-only application, like VirtualDub) the ATI drivers crash constantly and produce wierd side effects when they aren't crashing. Most notably, the backing store on the mouse pointer tends to break a lot, leaving me with an invisible mouse in Windows, and will leave blocks of garbage over any window that is updating while the cursor passes over. Matrox on the other hand as wonderful Windows drivers (Unlike ATI, I've never seen a Windows crash inside MGADRAB.DLL). 3D performance wise, the G series Matrox cards seem pretty comperable to the equivelent ATI Rage chip. The ATI cards tend to work better at lower resolutions than the Matrox cards, but the Matrox cards tend to work better at 1024x768+ resolutions in my (albiet limited) experience. You are right about the raster quality of the NVidia cards (Geforce especially). As you probably know, NVidia liceneses out their chipset (and a "reference board") to companies, and these companies do the final board design and manufacture your card. Apparently even the reference board from NVidia had rather bad raster issues, and most manufacturers weren't really set up to fix them, so they basically reproduced the reference board as is, leaving the problems in place. Also, GeForce cards are pretty expensive if all you want to do with them is sysadmin or do other 2D tasks. Warning: This paragraph is third hand information, your accuracy may vary. Finally, one really big downside for buying either card (if you are a gamer) is that they are merely tested for "compatability" by most game companies. This means it is all too common to find games tickling bugs in your card (that NEVER get fixed, because they only really care about the NVidia and 3dfx folks). I still have to downgrade my video drivers to play some games (Star Trek Armada) and then upgrade them again to play different games (Heavy Gear II), which is annoying to say the least. -- _ _ _ ___ ____ ___ ______________________________________ / \/ \ | ||_ _|| _ \|___| | Jason Andresen -- jandrese@mitre.org / /\/\ \ | | | | | |/ /|_|_ | Views expressed may not reflect those /_/ \_\|_| |_| |_|\_\|___| | of the Mitre Corporation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 6:50:28 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtpproxy1.mitre.org (mb-20-100.mitre.org [129.83.20.100]) by hub.freebsd.org (Postfix) with ESMTP id EE40E37B43F for ; Thu, 12 Apr 2001 06:50:25 -0700 (PDT) (envelope-from jandrese@mitre.org) Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58]) by smtpproxy1.mitre.org (8.9.3/8.9.3) with ESMTP id JAA28969 for ; Thu, 12 Apr 2001 09:50:25 -0400 (EDT) Received: from mailsrv2.mitre.org (mailsrv2.mitre.org [129.83.221.17]) by smtpsrv1.mitre.org (8.9.3/8.9.3) with ESMTP id JAA23322 for ; Thu, 12 Apr 2001 09:50:24 -0400 (EDT) Received: from mitre.org ([128.29.145.140]) by mailsrv2.mitre.org (Netscape Messaging Server 4.15) with ESMTP id GBOMFZ00.NKZ; Thu, 12 Apr 2001 09:50:23 -0400 Message-ID: <3AD5B29E.8A3C312A@mitre.org> Date: Thu, 12 Apr 2001 09:50:23 -0400 From: "Andresen,Jason R." X-Mailer: Mozilla 4.75 [en]C-20000818M (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Rasputin , freebsd-stable@freebsd.org Subject: Re: PicoBSD References: <20010412123007.A89724@dogma.freebsd-uk.eu.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rasputin wrote: > > Has anyone got any up to date docs on it? > (They're in /usr/src/release somewhere but they're hiding) > > The website mentions running a build shell script, but it doesn't > seem to exist. I think the "build" script has been replaced by "picobsd" The docs are in /usr/src/release/picobsd/docs/src/, of particular interest to you would be how2build.html. A word of caution, I don't know if it was fixed or not, but as of 4.2-BETA I was unable to get a picobsd floppy to actually boot, although that may have been an error on my part. I didn't have time at that point to actually track down the source of the error unfortunatly. -- _ _ _ ___ ____ ___ ______________________________________ / \/ \ | ||_ _|| _ \|___| | Jason Andresen -- jandrese@mitre.org / /\/\ \ | | | | | |/ /|_|_ | Views expressed may not reflect those /_/ \_\|_| |_| |_|\_\|___| | of the Mitre Corporation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 7:17:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209]) by hub.freebsd.org (Postfix) with SMTP id C287937B440 for ; Thu, 12 Apr 2001 07:17:54 -0700 (PDT) (envelope-from karsten@rohrbach.de) Received: (qmail 98706 invoked by uid 1000); 12 Apr 2001 14:18:15 -0000 Date: Thu, 12 Apr 2001 16:18:15 +0200 From: "Karsten W. Rohrbach" To: "Andresen,Jason R." Cc: Christian Chen , Kal Torak , FreeBSD-stable Subject: OT: nVidia Cards picture/driver quality Message-ID: <20010412161815.A95253@mail.webmonster.de> References: <20010412000523.I86970-100000@pirastro.oistrakh.org> <3AD5B145.EF09CEA4@mitre.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AD5B145.EF09CEA4@mitre.org>; from jandrese@mitre.org on Thu, Apr 12, 2001 at 09:44:37AM -0400 X-Arbitrary-Number-Of-The-Day: 42 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andresen,Jason R.(jandrese@mitre.org)@2001.04.12 09:44:37 +0000: > You are right about the raster quality of the NVidia cards (Geforce > especially). As you probably know, NVidia liceneses out their chipset > (and a "reference board") to companies, and these companies do the > final board design and manufacture your card. Apparently even the > reference board from NVidia had rather bad raster issues, and most > manufacturers weren't really set up to fix them, so they basically > reproduced the reference board as is, leaving the problems in place. > Also, GeForce cards are pretty expensive if all you want to do with > them is sysadmin or do other 2D tasks. Warning: This paragraph > is third hand information, your accuracy may vary. you might also check out http://www.geocities.com/porotuner/imagequality.html wich conatins a not-so-nice (speak: ugly) mod involving handling of soldering irons but seems to work. /k > Finally, one really big downside for buying either card (if you are > a gamer) is that they are merely tested for "compatability" by most > game companies. This means it is all too common to find games tickling > bugs in your card (that NEVER get fixed, because they only really care > about the NVidia and 3dfx folks). I still have to downgrade my video > drivers to play some games (Star Trek Armada) and then upgrade them > again to play different games (Heavy Gear II), which is annoying to > say the least. the drivers that ocassoinally "leak" from invidia and show up on http://www.reactorcritical.com/ appear to work very reliable for me (10.80/11.01 for win2k) and they also fix the ugly 60hz default of the older reference drivers when switching to directx fullscreen to somewhat higher refresh rates (72..85Hz) /k -- > Sex is one of the nine reasons for reincarnation ... the other eight > are unimportant. -- Henry Miller KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 7:27:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id BB6E137B423 for ; Thu, 12 Apr 2001 07:27:05 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 12 Apr 2001 15:27:04 +0100 (BST) To: Jun YAMASHITA Cc: freebsd-stable@FreeBSD.ORG, iedowse@maths.tcd.ie Subject: Re: USB mouse with FreeBSD 4.3 RC3 In-Reply-To: Your message of "Thu, 12 Apr 2001 22:41:15 +0900." <20010412224115R.junkun@esys.tsukuba.ac.jp> Date: Thu, 12 Apr 2001 15:27:04 +0100 From: Ian Dowse Message-ID: <200104121527.aa93629@salmon.maths.tcd.ie> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010412224115R.junkun@esys.tsukuba.ac.jp>, Jun YAMASHITA writes: > >In order to use USB mouse, I turn off PnP-OS support at the BIOS menu >but when booting the system it seems to be frozen while probing ATA >disks. It seems to be passed to boot sequence if I turn on PnP-OS >support but usbd does not work with following message:No USB host >controllers found. > >When I had used FreeBSD 4.2R, I could use USB mouce and had no >problems. This is becoming quite a common complaint with Sony hardware since the "pcic" device was changed to use polling mode by default. The problem is that the pccard controller seems to generate interrupts even when it has been told not to (but only when PnP OS is "no"). When an interrupt is generated, the machine gets stuck in a loop because none of the interrupt handlers for that interrupt line know how to disable source of the signal. The workaround is to specify a non-zero IRQ for the pcic device in your kernel config. e.g. device pcic0 at isa? irq 5 port 0x3e0 iomem 0xd0000 (you can do this also via /boot/kernel.conf or the UserConfig prompt with the command "irq pcic0 5"). Then change the BIOS PnP OS setting to "no", and both USB and pccard should work together. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 8: 5:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.stomped.com (stomped.com [216.17.56.5]) by hub.freebsd.org (Postfix) with SMTP id 2148237B424 for ; Thu, 12 Apr 2001 08:05:10 -0700 (PDT) (envelope-from malhavoc@www.stomped.com) Received: (qmail 48763 invoked by uid 1041); 12 Apr 2001 15:05:09 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 12 Apr 2001 15:05:09 -0000 Date: Thu, 12 Apr 2001 10:05:09 -0500 (CDT) From: Jason Nugent To: Subject: a word of appreciation Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, I'm not sure how much you get of this, but I just wanted to say thanks to all of you working on the freebsd project. You do fine work. I'm not sure how often you get to hear that, so I'm going to say it now. I just finished a routine upgrade of my FreeBSD 4.1.1-RELEASE machine to 4.3-RC, in order to make sure that the circulated ftp glob() vulnerability wouldn't affect my system. I'm curious, though, if the lib-paranoia library in the ports collection would have prevented the exploit from happening in the first place. Has anyone experimented with this? Jason ---------------------- Jason Nugent Aka MalHavoc Server Programmer and Administrator S T O M P E D . C O M For PGP public key: http://malhavoc.stomped.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 8:13:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id D936437B43F for ; Thu, 12 Apr 2001 08:13:35 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from medusa.kfu.com (medusa.kfu.com [205.178.90.222]) by quack.kfu.com (8.11.1/8.11.1) with ESMTP id f3CFDYh64238; Thu, 12 Apr 2001 08:13:34 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) From: Nick Sayer Received: from kfu.com (localhost [127.0.0.1]) by medusa.kfu.com (8.11.3/8.11.3) with SMTP id f3CFDYY89287; Thu, 12 Apr 2001 08:13:34 -0700 (PDT) (envelope-from nsayer@kfu.com) Received: from 207.5.33.65 (SquirrelMail authenticated user nsayer) by medusa.kfu.com with HTTP; Thu, 12 Apr 2001 08:13:34 -0700 (PDT) Message-ID: <4783.207.5.33.65.987088414.squirrel@medusa.kfu.com> Date: Thu, 12 Apr 2001 08:13:34 -0700 (PDT) Subject: Re: USB mouse with FreeBSD 4.3 RC3 To: junkun@debug.gr.jp In-Reply-To: <20010412224115R.junkun@esys.tsukuba.ac.jp> References: <20010412224115R.junkun@esys.tsukuba.ac.jp> Cc: freebsd-stable@FreeBSD.ORG X-Mailer: SquirrelMail (version 1.0.4) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_?hOe4ym7uCUUmuF/Ihy2ac+g'JRBhu6Lcs6I93'8k6_1+.9Kt((9d7+PLMc6" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------=_?hOe4ym7uCUUmuF/Ihy2ac+g'JRBhu6Lcs6I93'8k6_1+.9Kt((9d7+PLMc6 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Give your pccard controller a real interrupt rather than use polled mode. Sony laptops seem to fail when in polled mode and non-pnp-os mode, even when booting Windows. > Hi folks, > > I'm using SONY PCG-SR1/BP notebook computer and I've installed FreeBSD [...] > pcic0: at port 0x3e0-0x3e1 on isa0 > pcic0: Polling mode ------=_?hOe4ym7uCUUmuF/Ihy2ac+g'JRBhu6Lcs6I93'8k6_1+.9Kt((9d7+PLMc6 Content-Type: application/octet-stream;name="" Content-Disposition: attachment; filename="" Content-Transfer-Encoding: base64 DQo= ------=_?hOe4ym7uCUUmuF/Ihy2ac+g'JRBhu6Lcs6I93'8k6_1+.9Kt((9d7+PLMc6-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 8:24:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ursa.calvin.edu (ursa.calvin.edu [153.106.4.1]) by hub.freebsd.org (Postfix) with ESMTP id 77E7E37B424 for ; Thu, 12 Apr 2001 08:24:16 -0700 (PDT) (envelope-from diephouse@eastnode.com) Received: from eastnode.com (resnet179-234.resnet.calvin.edu [153.106.179.234]) by ursa.calvin.edu (8.10.1/8.10.1) with ESMTP id f3CFOEk13873 for ; Thu, 12 Apr 2001 11:24:14 -0400 (EDT) Message-ID: <3AD5C7B8.6538274F@eastnode.com> Date: Thu, 12 Apr 2001 11:20:24 -0400 From: Dan Diephouse X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Tunneling with PPP Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello - I am in the midst of trying to set up a FreeBSD server through a PPP tunnel. I work for a non-profit organization and they are beginning a for-profit side of their organization. As the for-profit side gets started they are running it out of a house. So as the systems admin for the non-profit side I set up a server for them. But, we can not keep the server on the grounds of the non-profit organization for some legal reasons. So what I did was set up a PPP tunnel from the server in the house the non-profit's server. Let's call the for-profit server "shorty" and the non-profit server "amnesiac." Shorty is behind a router that connects to a cable modem. It tunnels out and connects to Amnesiac using user-ppp. That all works fine, but what I want to do is have an IP address that is on the public Internet tunnel back to Shorty behind the cable modem. Amnesiac has an IP address and domain name on the internet. What I want it to do is listen for an additional ip address and directy back to shorty. Is this possible? I tried various combinations of natd/ipfw setups but I couldn't make it work. I can give specific tried setups, but I figure that'd probably be a waste of everyone's time because some could lay out what to do in a few seconds. Also, I am open to any other suggestions on how to make this work not using ppp.... Thanks, Dan Diephouse To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 8:38:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pump3.york.ac.uk (pump3.york.ac.uk [144.32.128.131]) by hub.freebsd.org (Postfix) with ESMTP id C18C537B42C for ; Thu, 12 Apr 2001 08:38:42 -0700 (PDT) (envelope-from gavin@ury.york.ac.uk) Received: from ury.york.ac.uk (ury.york.ac.uk [144.32.108.81]) by pump3.york.ac.uk (8.10.2/8.10.2) with ESMTP id f3CFcet25735 for ; Thu, 12 Apr 2001 16:38:41 +0100 (BST) Received: from localhost (gavin@localhost) by ury.york.ac.uk (8.9.3/8.9.3) with ESMTP id QAA55746 for ; Thu, 12 Apr 2001 16:38:40 +0100 (BST) (envelope-from gavin@ury.york.ac.uk) Date: Thu, 12 Apr 2001 16:38:40 +0100 (BST) From: Gavin Atkinson To: freebsd-stable@freebsd.org Subject: 4.3-RC3 install fails from ISO on laptop Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My experience is on a Pentium 166 unbranded laptop which currently has Linux installed. The machine cannot boot from CD so I have wrote the floppies from the images in the 4.3RC3 iso. Upon booting the install disks, FreeBSD recognises the CD rom drive as a Toshiba CD-ROM XM-1602B at ata1-master using BIOSPIO. After selecting everything i want installing, the installer runs newfs on all my slices, then comes to install the distributions. This is where I run into problems. I have attempted exactly the same process several times, and each time I get different results. I've tried to section them below to make it less ugly and more readeable, hope it makes sense. ------------- Sometimes I get the following messagebox: | The CD looks more like an audio CD than a FreeBSD CD. (at which point the install terminates) ------------- Other times I get: | A signal 11 was caught... etc (the alt-f2 log shows success in mounting the CD here) ------------------ However, if a PCMCIA network card is installed (A D-Link DE660), the following always occurs, can sometimes also occur without the net card: (again, the alt-f2 log shows success in mounting the CD) | Warning: The CD currently in the drive is either not a FreeBSD | CD or it is an older (pre 2.1.5) FreeBSD CD which does not | have a version number on it. Do you wish to use this CD anyway? Selecting 'yes' results in (for each distribution): | Write failure on transfer! (wrote -1 bytes of 240640 bytes) and then eventually | Cannot parse information file for the info distribution: I/O error | Please verify that your media is valid and try again. The debug log (alt-f2) reads: /stand/cpio: premature end of archive /stand/gunzip: failed gzclose /stand/cpio: premature end of archive /stand/gunzip: failed gzclose RRIP without PX field? /stand/cpio: premature end of archive /stand/gunzip: failed gzclose ----------- Anyone can help? I'm going to re-download the ISO (if I can find it - it seems to have disappeared from some FTP sites) and write a different CD soon, but it reads fine under Windows, the current install Linux on the same laptop (suggesting the CD rom drive is fine), and in other freeBSD boxes. Note that in all cases, enabling extra debugging gives no further information. Tomorrow I should be able to attempt to install via ftp (assuming I can get my 3com PCMCIA net card working...) Thanks in advance, Gavin Atkinson -- Life makes more sense when you realise that most other things don't. - - Gavin Atkinson - Head Of Computing - University Radio York - - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 10:13:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mighty.grot.org (mighty.grot.org [216.15.97.5]) by hub.freebsd.org (Postfix) with ESMTP id 002F937B424 for ; Thu, 12 Apr 2001 10:13:29 -0700 (PDT) (envelope-from lists@grot.org) Received: by mighty.grot.org (Postfix, from userid 998) id B8F9B5D12; Thu, 12 Apr 2001 10:13:29 -0700 (PDT) Date: Thu, 12 Apr 2001 10:13:29 -0700 From: "R.P. Aditya" To: freebsd-stable@freebsd.org Subject: uninstalling a distribution (xfree86) Message-ID: <20010412101329.A99058@mighty.grot.org> Reply-To: lists@lists.grot.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Is there a way, akin to installing the xfree86 distribution during install or using /stand/sysinstall, to uninstall it. If it matters, this is on a 4.2-RELEASE machine that has XFree86 3.3.6 on it. I'm turning it into a remote server and want to recover some room in /usr. It would be nice if there was some sort of "pkg" info kept for the xfree86 distribution so it could be removed by pkg_delete -- I figured I'd check before I just ran rm -r /usr/X11R6 Thanks, Adi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 11:42:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from darkstar.umd.edu (darkstar.umd.edu [128.8.215.163]) by hub.freebsd.org (Postfix) with ESMTP id C9FF937B440 for ; Thu, 12 Apr 2001 11:42:55 -0700 (PDT) (envelope-from bfoz@glue.umd.edu) Received: from glue.umd.edu (localhost [127.0.0.1]) by darkstar.umd.edu (8.11.2/8.11.2) with ESMTP id f3CIf2b03714; Thu, 12 Apr 2001 14:41:02 -0400 (EDT) (envelope-from bfoz@glue.umd.edu) Message-ID: <3AD5F6BE.622E96FF@glue.umd.edu> Date: Thu, 12 Apr 2001 14:41:02 -0400 From: Brandon Fosdick X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: scott@sawilson.org Cc: freebsd-stable@FreeBSD.ORG Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: <20010411220425.22581.cpmta@c001.snv.cp.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG scott@sawilson.org wrote: > Hello, > > I feel your pain, as I'm sure others do on the list. You aren't going to be satisfied with a "there is nothing we can do about this because" type answer. To you it sounds defeatist and like an excuse to do nothing. I agree. I have an idea I wanted to run by the list. > > What if someone were to set up a simple email cgi with a form letter in the nature of: I seem to remember that the last time this came up on -hackers somebody mentioned that nVidia already had someone working on FreeBSD drivers, but work was going slowly. I think they were also already coordinating with somebody on the FreeBSD team, don't remember who. It would probably be better to find out the status of the effort already underway, if there really is such an effort. -Brandon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 11:53:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp-relay.rtci.com (calamari-ex.arch.rtci.com [208.11.246.4]) by hub.freebsd.org (Postfix) with ESMTP id 105FA37B423 for ; Thu, 12 Apr 2001 11:53:28 -0700 (PDT) (envelope-from jhopkins@rtci.com) Received: from rtci.com (hoodlum [208.11.244.8]) by smtp-relay.rtci.com (Postfix) with ESMTP id 707891C9A0; Thu, 12 Apr 2001 14:53:27 -0400 (EDT) Message-ID: <3AD5F9A7.2B305998@rtci.com> Date: Thu, 12 Apr 2001 14:53:27 -0400 From: Jeremy Hopkins Organization: Internet Commerce Corp. (RTCI division) X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-BETA i386) X-Accept-Language: en MIME-Version: 1.0 To: jl@burghcom.com, freebsd-stable@freebsd.org Subject: Re: Problems with 3c905B and 4.3-RC References: <3AD4CBC3.F3E79AFC@rtci.com> <01041208131800.29806@merlin> <045c01c0c34b$588d6980$931576d8@inethouston.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Correct. the pnp OS setting solved my issue. But to answer the question. Yes, miibus was in my kernel. "David W. Chapman Jr." wrote: > > No, he solved the problem already by setting pnp OS to off I believe. > > ----- Original Message ----- > From: "Jeff Love" > > Not sure if this is the problem in your case, but did you include 'device > > miibus' to your kernel config? This was a fairly recent addition needed > for > > 3com nics. > > > > > > xl0 shows up in dmesg but I get error messages along with it. > > > > > > xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 10 at device 15.0 on pci0 > > > xl0: couldn't map ports/memory > > > device_probe_and_attach: xl0 attach returned 6 > > > below is copy of full dmesg output- > > > ------------------------------ > > > Copyright (c) 1992-2001 The FreeBSD Project. > > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > > > The Regents of the University of California. All rights > > > reserved. > > > FreeBSD 4.3-RC #0: Wed Apr 11 18:50:15 GMT 2001 > > > root@shadow.ghettoweb.net:/usr/obj/usr/src/sys/GUNSHOT > > > Timecounter "i8254" frequency 1193182 Hz > > > CPU: Pentium III/Pentium III Xeon/Celeron (497.84-MHz 686-class CPU) > > > Origin = "GenuineIntel" Id = 0x673 Stepping = 3 > > > > > > > Features=0x383f9ff PAT,PSE36,MMX,FXSR,SSE> > > > real memory = 134217728 (131072K bytes) > > > avail memory = 126545920 (123580K bytes) > > > Preloaded elf kernel "kernel" at 0xc03e1000. > > > 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 > > > pci1: at 0.0 irq 11 > > > isab0: at device 7.0 on pci0 > > > isa0: on isab0 > > > atapci0: port 0x1000-0x100f at device 7.1 > > > on pci0 > > > ata0: at 0x1f0 irq 14 on atapci0 > > > ata1: at 0x170 irq 15 on atapci0 > > > uhci0: port 0x1020-0x103f irq > > > 9 at device 7.2 on pci0 > > > usb0: on uhci0 > > > usb0: USB revision 1.0 > > > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > > > uhub0: 2 ports with 2 removable, self powered > > > chip1: port 0x7000-0x700f at > > > device 7.3 on pci0 > > > xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 10 at device 15.0 on pci0 > > > xl0: couldn't map ports/memory > > > device_probe_and_attach: xl0 attach returned 6 > > > fdc0: at port 0x3f0-0x3f5,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,0x64 on isa0 > > > atkbd0: flags 0x1 irq 1 on atkbdc0 > > > kbd0 at atkbd0 > > > psm0: irq 12 on atkbdc0 > > > psm0: model IntelliMouse, device ID 3 > > > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on > > > isa0 > > > sc0: at flags 0x100 on isa0 > > > sc0: VGA <16 virtual consoles, flags=0x300> > > > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > > > sio0: type 16550A > > > sio1: configured irq 3 not in bitmap of probed irqs 0 > > > ppc0: at port 0x378-0x37f irq 7 on isa0 > > > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > > > ppc0: FIFO with 16/16/8 bytes threshold > > > lpt0: on ppbus0 > > > lpt0: Interrupt-driven port > > > ppi0: on ppbus0 > > > IPsec: Initialized Security Association Processing. > > > ad0: 9787MB [19885/16/63] at ata0-master UDMA33 > > > ad1: 9787MB [19885/16/63] at ata0-slave UDMA33 > > > acd0: CDROM at ata1-master using PIO4 > > > afd0: 96MB [96/64/32] at ata1-slave using PIO3 > > > Mounting root from ufs:/dev/ad0s1a > > > -- Jeremy Hopkins Systems Administrator www.icc.net www.rtci.com For those who like this sort of thing, this is the sort of thing they like. -- Abraham Lincoln To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 12: 7:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 97E3137B424 for ; Thu, 12 Apr 2001 12:07:38 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id ijwaaaaa for ; Fri, 13 Apr 2001 05:07:10 +1000 Message-ID: <3AD5FDE6.3B2866A9@quake.com.au> Date: Fri, 13 Apr 2001 05:11:34 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Christian Chen Cc: FreeBSD-stable Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: <20010412000523.I86970-100000@pirastro.oistrakh.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christian Chen wrote: > > On Thu, 12 Apr 2001, Kal Torak wrote: > > nVidia cards are really the ONLY choice to buy now... Not that Im complaining, > > Maybe this is just *my* personal quirkiness, but does anyone else out there > feel as though ATI's 2D performance is higher quality? And by higher quality, > I don't mean _faster_, I mean _looks better_. When I replaced my nVidia > card with an ATI Rage Fury Pro, and after that a Rage Fury Maxx, the text > looked crisper, and images were sharper. Granted, these things are > irrevelant to 3D gamers, but for all those sysadmins out there, it sure > is nice having crisper console screens and xterms. > > But maybe it's just me. Lots of people don't notice 60Hz scan rate > flicker, but I do ... Well personaly I found the GeForce to have much better 2D quality than other cards, as you said things look crisper and sharper... But thats just my experance... Maybe ATI cards work better with your system/monitor or something? I also notice 60Hz scan rate... 85Hz is the minimum I will accept :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 12:14:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 5889837B446 for ; Thu, 12 Apr 2001 12:14:14 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id kjwaaaaa for ; Fri, 13 Apr 2001 05:13:44 +1000 Message-ID: <3AD5FF70.5AF56038@quake.com.au> Date: Fri, 13 Apr 2001 05:18:08 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Rasputin Cc: stable@freebsd.org Subject: Re: Games on FreeBSD References: <200104120134.UAA20957@freebsd.netcom.com> <3AD52A10.7997F8EA@quake.com.au> <20010411233302.A8789@cec.wustl.edu> <3AD53763.B2B2B38A@quake.com.au> <20010412094235.A87336@dogma.freebsd-uk.eu.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rasputin wrote: > > * Kal Torak [010412 06:02]: > > > WINE has DirectX support now I think, its quite possible to play Half-Life > > under WINE on FreeBSD... > > /me prick up ears as though some just mentioned free beer > > You don't have a working ~/.wine/config for that, by any chance? Well so long as your 3D accelerator is supported under FreeBSD, all you need to do is run the install.exe program on the half-life cd with wine, and it should do all the configuring for you... Its just a matter of making the wine config file point to the right places on your system, make like a /usr/win or something.. then under that you just have to make a tree like: /usr/wine/ /usr/wine/windows /usr/wine/windows/system /usr/wine/games then in the wine config, make C: point to /usr/wine I also find making D: point to /usr/half-life-cd and copy all of the cd into that... thats pritty much all you need to do, then run the install program and any update patchs using wine and it will create the needed registery for you! I havent been able to play single player, but it works fine for network play :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 12:23:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 5CFD037B443 for ; Thu, 12 Apr 2001 12:23:51 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id mjwaaaaa for ; Fri, 13 Apr 2001 05:23:22 +1000 Message-ID: <3AD601B2.8DBE138B@quake.com.au> Date: Fri, 13 Apr 2001 05:27:46 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Karsten W. Rohrbach" Cc: "Andresen,Jason R." , Christian Chen , FreeBSD-stable Subject: Re: OT: nVidia Cards picture/driver quality References: <20010412000523.I86970-100000@pirastro.oistrakh.org> <3AD5B145.EF09CEA4@mitre.org> <20010412161815.A95253@mail.webmonster.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Karsten W. Rohrbach" wrote: > > Andresen,Jason R.(jandrese@mitre.org)@2001.04.12 09:44:37 +0000: > > You are right about the raster quality of the NVidia cards (Geforce > > especially). As you probably know, NVidia liceneses out their chipset > > (and a "reference board") to companies, and these companies do the > > final board design and manufacture your card. Apparently even the > > reference board from NVidia had rather bad raster issues, and most > > manufacturers weren't really set up to fix them, so they basically > > reproduced the reference board as is, leaving the problems in place. > > Also, GeForce cards are pretty expensive if all you want to do with > > them is sysadmin or do other 2D tasks. Warning: This paragraph > > is third hand information, your accuracy may vary. > you might also check out > http://www.geocities.com/porotuner/imagequality.html > wich conatins a not-so-nice (speak: ugly) mod involving handling of > soldering irons but seems to work. You would have to be really worried about the quality to do that!!! Do you know how small those parts are? The quality on my GeForce256 is fine... I dont see any bluriness at all... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 12:25:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 1608F37B443 for ; Thu, 12 Apr 2001 12:25:38 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id ojwaaaaa for ; Fri, 13 Apr 2001 05:25:07 +1000 Message-ID: <3AD6021B.40F8601F@quake.com.au> Date: Fri, 13 Apr 2001 05:29:31 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Brandon Fosdick Cc: scott@sawilson.org, freebsd-stable@FreeBSD.ORG Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: <20010411220425.22581.cpmta@c001.snv.cp.net> <3AD5F6BE.622E96FF@glue.umd.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I seem to remember that the last time this came up on -hackers somebody > mentioned that nVidia already had someone working on FreeBSD drivers, > but work was going slowly. I think they were also already coordinating > with somebody on the FreeBSD team, don't remember who. It would probably > be better to find out the status of the effort already underway, if > there really is such an effort. Hmmm.. Anyone got any varification on this??? I will contact nVidia and see what they have to say... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 13: 5:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fluffy.adriel.net (fluffy.adriel.net [216.141.4.150]) by hub.freebsd.org (Postfix) with ESMTP id ABB9337B424 for ; Thu, 12 Apr 2001 13:05:43 -0700 (PDT) (envelope-from adriel@fluffy.adriel.net) Received: (from adriel@localhost) by fluffy.adriel.net (8.11.2/8.11.2) id f3CK5gP72703 for freebsd-stable@FreeBSD.ORG; Thu, 12 Apr 2001 15:05:42 -0500 (CDT) (envelope-from adriel) Date: Thu, 12 Apr 2001 15:05:42 -0500 From: adriel To: freebsd-stable@FreeBSD.ORG Subject: Re: ATA_ENABLE_ATAPI_DMA gone? Message-ID: <20010412150542.M5028@adriel.net> References: <02db01c0c1b1$c1a0ffe0$0508a8c0@lofi.dyndns.org> <20010410123317.A73359@irrelevant.org> <200104101342.f3ADgsn15019@bmah-freebsd-0.cisco.com> <20010410153425.I5028@adriel.net> <20010410134934.Z15938@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010410134934.Z15938@fw.wintelcom.net>; from bright@wintelcom.net on Tue, Apr 10, 2001 at 01:49:35PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I suppose my frustration comes from changing something that worked perfectly for no good reason, what exactly was wrong with compiling that flag in the kernel, and why was it deemed "obsolete". I understand how to do it now, but my point remains, why was I forced to change, what advantage did I receive from this? I am not running -CURRENT. the main problem in my situation is that I have a DMA hd sharing an IDE cdrom, if you dont enable the ATAPI_DMA then it wont allow dma on the hard drive either. Maybe there is a good reason for this, but I still do not understand why something that was not breaking the system would be arbitrarily removed without any warning. The only POSSIBLE advantage I could have seen with moving this to be sysctl only is that you could change it without rebooting, and even that is not the case. Quoting Alfred Perlstein (bright@wintelcom.net): > * adriel [010410 13:34] wrote: > > hw.ata.atapi_dma > > set to 1 for DMA access 0 for PIO (default is PIO). > > > > root@misty:~# sysctl -w hw.ata.atapi_dma=1 > > sysctl: oid 'hw.ata.atapi_dma' is read only > > > > what the hell? I need this, my drive takes forever to mount without it > > it scrolls tons of errors before finally timing out and using pio. > > "what the hell?" ? > > didn't you read that Bruce told you? > > > Quoting Bruce A. Mah (bmah@FreeBSD.ORG): > > > > > > And it's also mentioned in RELNOTES.TXT: > > > > > > # To provide more flexible configuration, the various options for the > > > # ata(4) driver are now boot loader tunables, rather than kernel > > > # configure-time options. > > You must set it from the loader. > > -- > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > Instead of asking why a piece of software is using "1970s technology," > start asking why software is ignoring 30 years of accumulated wisdom. -- ---------------------------------------------------- Adriel Ickler Network Administrator - adriel@jlms.com Self Trading Securities - Voice: 512-263-2769 www.selftrading.com - Fax: 512-263-2141 ---------------------------------------------------- Avoid Quiet and Placid persons unless you are in Need of Sleep. -- National Lampoon, "Deteriorata" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 13:35: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hbmadv.com (hbmadv.com [206.5.9.100]) by hub.freebsd.org (Postfix) with ESMTP id 8DAC937B42C for ; Thu, 12 Apr 2001 13:34:58 -0700 (PDT) (envelope-from arodriguez@hbmadv.com) Received: from [206.5.9.82] (206.5.9.82) by hbmadv.com with ESMTP (Eudora Internet Mail Server 3.0.2) for ; Thu, 12 Apr 2001 16:34:59 -0400 Mime-Version: 1.0 X-Sender: arodriguez@hbmadv.com (Unverified) Message-Id: Date: Thu, 12 Apr 2001 16:34:54 -0400 To: stable@FreeBSD.org From: Alex Rodriguez Subject: subscribe Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 14: 8: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by hub.freebsd.org (Postfix) with ESMTP id 6BA8237B43E for ; Thu, 12 Apr 2001 14:08:04 -0700 (PDT) (envelope-from gehicks@cisco.com) Received: from mira1.cisco.com (mira1.cisco.com [171.71.208.193]) by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id OAA20620 for ; Thu, 12 Apr 2001 14:08:08 -0700 (PDT) Received: from cisco.com (ptlm1-dhcp-101.cisco.com [171.71.210.101]) by mira1.cisco.com (Mirapoint) with ESMTP id AAR08005; Thu, 12 Apr 2001 14:08:02 -0700 (PDT) Message-ID: <3AD618E9.E3C5890E@cisco.com> Date: Thu, 12 Apr 2001 14:06:49 -0700 From: W Gerald Hicks Organization: Cisco Systems, Inc. X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-stable Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: <3AD427DC.CFC52BAE@quake.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Uhm, Can we please move this thread away from the stable list? Cheers, Jerry Hicks gehicks@cisco.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 14:42:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hercules.icarz.com (ns1.icarz.com [207.99.22.7]) by hub.freebsd.org (Postfix) with ESMTP id 2C2D237B43E for ; Thu, 12 Apr 2001 14:42:07 -0700 (PDT) (envelope-from kenm@icarz.com) Received: from newken (dhcp113.icarz.com [207.99.22.113]) by hercules.icarz.com (8.10.1/8.10.1) with SMTP id f3CLg6229815 for ; Thu, 12 Apr 2001 17:42:06 -0400 (EDT) Message-ID: <000901c0c399$13f7e680$711663cf@icarz.com> From: "Ken Menzel" To: Subject: Tail of file larger than 2 gig fails (patch) Date: Thu, 12 Apr 2001 17:39:39 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had a problem today with a very large log file (3.6 gig) I wanted to see the last few lines but 'tail' wanted to show me the last gig or so. Anyway I made it work, I don't know if this is the right list, because I have never submitted a patch before. Could someone committer either advise me where to send this patch or take a look at it and commit it if it looks OK? It should not affect the way tail works for files smaller that 2Gig (1/2 of SIZE_T_MAX). It also fixes the comparison of SIZE_T_MAX which never worked anyway and does print a warning at the top of the tail if the file is larger that 2 gig. Thanks Ken --- ./kentail/forward.c Thu Apr 12 17:18:48 2001 +++ ./tail/forward.c Wed Feb 28 11:18:13 2001 @@ -268,30 +268,20 @@ struct stat *sbp; { off_t size; - off_t max_size; - off_t big_off; - size_t orig_size; - char *p; char *start; if (!(size = sbp->st_size)) return; - max_size=SIZE_T_MAX/2; - big_off=0; - if (size > max_size) { + if (size > SIZE_T_MAX) { errno = EFBIG; ierr(); - // Just look at back of file - big_off=size-max_size; - size=max_size; - // return; + return; } - orig_size=size; if ((start = mmap(NULL, (size_t)size, - PROT_READ, MAP_SHARED, fileno(fp), (off_t)big_off)) == MAP_FAILED) { + PROT_READ, MAP_SHARED, fileno(fp), (off_t)0)) == MAP_FAILED) { ierr(); return; } @@ -304,13 +294,13 @@ } /* Set the file pointer to reflect the length displayed. */ - size = orig_size - size; + size = sbp->st_size - size; WR(p, size); - if (fseeko(fp, sbp->st_size, SEEK_SET) == -1) { + if (fseek(fp, (long)sbp->st_size, SEEK_SET) == -1) { ierr(); return; } - if (munmap(start, orig_size)) { + if (munmap(start, (size_t)sbp->st_size)) { ierr(); return; } ----------------------------------------------------- Ken Menzel ICQ# 9325188 www.icarz.com kenm@icarz.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 15: 1:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88]) by hub.freebsd.org (Postfix) with ESMTP id B723F37B42C for ; Thu, 12 Apr 2001 15:01:10 -0700 (PDT) (envelope-from bmah@cisco.com) Received: from bmah-freebsd-0.cisco.com (bmah-freebsd-0.cisco.com [171.70.84.42]) by sj-msg-core-2.cisco.com (8.9.3/8.9.1) with ESMTP id PAA17030; Thu, 12 Apr 2001 15:01:34 -0700 (PDT) Received: (from bmah@localhost) by bmah-freebsd-0.cisco.com (8.11.3/8.11.1) id f3CM1Ad17532; Thu, 12 Apr 2001 15:01:10 -0700 (PDT) (envelope-from bmah) Message-Id: <200104122201.f3CM1Ad17532@bmah-freebsd-0.cisco.com> X-Mailer: exmh version 2.3.1 01/19/2001 with nmh-1.0.4 To: "Ken Menzel" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Tail of file larger than 2 gig fails (patch) In-Reply-To: <000901c0c399$13f7e680$711663cf@icarz.com> References: <000901c0c399$13f7e680$711663cf@icarz.com> Comments: In-reply-to "Ken Menzel" message dated "Thu, 12 Apr 2001 17:39:39 -0400." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_250520767P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Thu, 12 Apr 2001 15:01:09 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_250520767P Content-Type: text/plain; charset=us-ascii If memory serves me right, "Ken Menzel" wrote: > I had a problem today with a very large log file (3.6 gig) I wanted to > see the last few lines but 'tail' wanted to show me the last gig or > so. Anyway I made it work, I don't know if this is the right list, > because I have never submitted a patch before. Could someone > committer either advise me where to send this patch or take a look at > it and commit it if it looks OK? FYI: tail(1) in 5-CURRENT was modified to handle large files a few weeks ago, in response to PR bin/14786. These changes haven't been MFC-ed yet. Maybe you should drop a note to dwmalone. Cheers, Bruce. --==_Exmh_250520767P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: Exmh version 2.2 06/23/2000 iD8DBQE61iWl2MoxcVugUsMRAu5+AKCX2nhcWp+OEGHSJRv+9GpIeOG2jwCg78dg Rh1qpE8jvu/W7MAIsTMfuTg= =/bgr -----END PGP SIGNATURE----- --==_Exmh_250520767P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 15:33:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nova.fnal.gov (nova.fnal.gov [131.225.121.207]) by hub.freebsd.org (Postfix) with ESMTP id F104337B443 for ; Thu, 12 Apr 2001 15:33:13 -0700 (PDT) (envelope-from zingelman@fnal.gov) Received: from localhost (tez@localhost) by nova.fnal.gov (8.9.3+Sun/8.9.3) with ESMTP id RAA27889 for ; Thu, 12 Apr 2001 17:33:10 -0500 (CDT) X-Authentication-Warning: nova.fnal.gov: tez owned process doing -bs Date: Thu, 12 Apr 2001 17:33:10 -0500 (CDT) From: Tim Zingelman X-Sender: To: Subject: Re: make release broken with too many ports/distfiles... In-Reply-To: <200104121113.NAA23060@lurza.secnetix.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Apr 2001, Oliver Fromme wrote: > > So the quick answer is figure out what subset of distfiles I need, put > > them someplace other than /usr/ports/distfiles & set DOCDISTFILES. > > You could, of course, set up a simple FTP server on > localhost, and let ``make release'' fetch the distfiles > that it needs itself. That's what I do, kind of. ;-) > So I never have to think about what distfiles it needs. > > (Requires a small hack to the release Makefile so that > there's an appropriate setting for the MASTER_SITE in > the chroot's make.conf.) I set MASTER_SITE=file:/path_to_all_distfiles/, so I didn't even need to setup ftp... thanks for the idea. - Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 16:57:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from landak.altek.com.my (landak.altek.com.my [202.186.13.26]) by hub.freebsd.org (Postfix) with SMTP id C4D4737B424 for ; Thu, 12 Apr 2001 16:57:45 -0700 (PDT) (envelope-from rosli@skali.com) Received: by landak.altek.com.my; (5.65v3.2/1.3/10May95) id AA24126; Fri, 13 Apr 2001 07:57:42 +0800 Message-Id: <00bb01c0c3ac$85773ff0$de01a8c0@altek.com.my> From: "Rosli Sukri" To: Subject: Date: Fri, 13 Apr 2001 07:58:50 +0800 Organization: Alam Teknokrat Sdn Bhd Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B8_01C0C3EF.9381EEE0" X-Priority: 3 X-Msmail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-Mimeole: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_00B8_01C0C3EF.9381EEE0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable auth 5366cb3c unsubscribe freebsd-stable=20 ------=_NextPart_000_00B8_01C0C3EF.9381EEE0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
auth 5366cb3c unsubscribe freebsd-stable =
------=_NextPart_000_00B8_01C0C3EF.9381EEE0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 17: 1:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from chmod.ath.cx (CC2-861.charter-stl.com [24.217.115.99]) by hub.freebsd.org (Postfix) with ESMTP id 6EEE637B43F for ; Thu, 12 Apr 2001 17:01:28 -0700 (PDT) (envelope-from ajh3@chmod.ath.cx) Received: by chmod.ath.cx (Postfix, from userid 1001) id 7E305A920; Thu, 12 Apr 2001 19:00:42 -0500 (CDT) Date: Thu, 12 Apr 2001 19:00:42 -0500 From: Andrew Hesford To: adriel Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ATA_ENABLE_ATAPI_DMA gone? Message-ID: <20010412190042.A11761@cec.wustl.edu> References: <02db01c0c1b1$c1a0ffe0$0508a8c0@lofi.dyndns.org> <20010410123317.A73359@irrelevant.org> <200104101342.f3ADgsn15019@bmah-freebsd-0.cisco.com> <20010410153425.I5028@adriel.net> <20010410134934.Z15938@fw.wintelcom.net> <20010412150542.M5028@adriel.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010412150542.M5028@adriel.net>; from adriel@adriel.net on Thu, Apr 12, 2001 at 03:05:42PM -0500 X-Loop: Andrew Hesford Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 12, 2001 at 03:05:42PM -0500, adriel wrote: > I suppose my frustration comes from changing something that worked > perfectly for no good reason, what exactly was wrong with compiling that > flag in the kernel, and why was it deemed "obsolete". I understand how > to do it now, but my point remains, why was I forced to change, what > advantage did I receive from this? I am not running -CURRENT. > > the main problem in my situation is that I have a DMA hd sharing an IDE > cdrom, if you dont enable the ATAPI_DMA then it wont allow dma on the > hard drive either. Maybe there is a good reason for this, but I still > do not understand why something that was not breaking the system would > be arbitrarily removed without any warning. The only POSSIBLE advantage > I could have seen with moving this to be sysctl only is that you could > change it without rebooting, and even that is not the case. Just because you don't run -CURRENT doesn't mean things aren't subject to change. Nobody is forcing you to cvsup; you don't have to change things if you don't want to. To keep a static system, run -RELEASE. -- Andrew Hesford ajh3@chmod.ath.cx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 17: 8:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id BAFDF37B446 for ; Thu, 12 Apr 2001 17:08:27 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id alwaaaaa for ; Fri, 13 Apr 2001 10:07:57 +1000 Message-ID: <3AD64466.441A6A21@quake.com.au> Date: Fri, 13 Apr 2001 10:12:22 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: <20010411220425.22581.cpmta@c001.snv.cp.net> <3AD5F6BE.622E96FF@glue.umd.edu> <3AD6021B.40F8601F@quake.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am waiting for nVidia to confirm if there is any work currently happening on a FreeBSD driver... But when I talked to loki (www.lokigames.com) about drivers for FreeBSD, they sure didnt know anything about it... So we may as well get started on the group letter! Who said they could provide fast web access? And anyone interested in making the page? We just need a simple page saying what where trying to do and some sort of submition type thing setup... I could do a simple perl script to handel that if no one has any better ideas! Could someone subscribed to some of the development lists ask around and see if there is anyone willing to sign an NDI with nVidia and try to make some binary drivers for FreeBSD? We also need someone to take on the job of continuing to port DRI to FreeBSD since the original porter has stoped... Even if nVidia will make a port, its probably worth trying to make some binary drivers since nVidia could well take there sweet time and we need these drivers yesterday :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 17:16:41 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns3.cswnet.com (ns3.cswnet.com [209.136.205.10]) by hub.freebsd.org (Postfix) with ESMTP id 2EB5137B496 for ; Thu, 12 Apr 2001 17:16:39 -0700 (PDT) (envelope-from lambert@os2warp.org) Received: from laptop.os2warp.org (laptop.os2warp.org [209.136.194.228]) by ns3.cswnet.com (Postfix) with ESMTP id 5375C68A1C for ; Thu, 12 Apr 2001 19:16:32 -0500 (CDT) Received: by laptop.os2warp.org (Postfix, from userid 1000) id 4BA8128B26; Thu, 12 Apr 2001 19:16:29 -0500 (CDT) Date: Thu, 12 Apr 2001 19:16:29 -0500 From: Scott Lambert To: FreeBSD-STABLE@FreeBSD.org Subject: Re: Games on FreeBSD Message-ID: <20010412191629.C1312@laptop.os2warp.org> Reply-To: FreeBSD-STABLE@FreeBSD.org Mail-Followup-To: Scott Lambert , FreeBSD-STABLE@FreeBSD.org References: <200104120134.UAA20957@freebsd.netcom.com> <3AD52A10.7997F8EA@quake.com.au> <20010411233302.A8789@cec.wustl.edu> <3AD53763.B2B2B38A@quake.com.au> <20010412000948.C8789@cec.wustl.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010412000948.C8789@cec.wustl.edu>; from ajh3@chmod.ath.cx on Thu, Apr 12, 2001 at 12:09:48AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 12, 2001 at 12:09:48AM -0500, Andrew Hesford wrote: > > Has anybody offered to sign an NDA with nVidia to write a binary-only > driver for FreeBSD? Everybody should ask around amongst all the good > FreeBSD hackers, to see if one of them would be willing to do so. Or go talk to SciTech Software. They are in the business of writing video drivers for other people's hardware. They work really well on OS/2. They have a project to build drivers for XF86 for Linux. It is pay-ware but worth it. I have four copies for my OS/2 boxes. Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 17:20:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.bmi.net (smtp.bmi.net [204.57.191.31]) by hub.freebsd.org (Postfix) with ESMTP id 4970D37B446 for ; Thu, 12 Apr 2001 17:20:35 -0700 (PDT) (envelope-from jmcoopr@webmail.bmi.net) Received: from webmail.bmi.net (dsl-154.bmi.net [207.173.60.230]) by smtp.bmi.net (Pro-8.9.3/Pro-8.9.3) with ESMTP id RAA16883 for ; Thu, 12 Apr 2001 17:20:34 -0700 Message-ID: <3AD6465B.61BAAF49@webmail.bmi.net> Date: Thu, 12 Apr 2001 17:20:43 -0700 From: John Merryweather Cooper X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en-US, en, en-GB MIME-Version: 1.0 To: FreeBSD-STABLE@FreeBSD.ORG Subject: Re: Games on FreeBSD References: <200104120134.UAA20957@freebsd.netcom.com> <3AD52A10.7997F8EA@quake.com.au> <20010411233302.A8789@cec.wustl.edu> <3AD53763.B2B2B38A@quake.com.au> <20010412000948.C8789@cec.wustl.edu> <20010412191629.C1312@laptop.os2warp.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Scott Lambert wrote: > > On Thu, Apr 12, 2001 at 12:09:48AM -0500, Andrew Hesford wrote: > > > > Has anybody offered to sign an NDA with nVidia to write a binary-only > > driver for FreeBSD? Everybody should ask around amongst all the good > > FreeBSD hackers, to see if one of them would be willing to do so. > > Or go talk to SciTech Software. They are in the business of writing video > drivers for other people's hardware. They work really well on OS/2. > > They have a project to build drivers for XF86 for Linux. It is pay-ware > but worth it. I have four copies for my OS/2 boxes. > > Scott > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message Yes, they'd be willing to do it (I almost sure), but they have the same problem--nVidia won't release the tech specs for the chips for love, money, or an ND. jmc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 17:22: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.jetnet.co.uk (www.jetnet.co.uk [62.172.71.4]) by hub.freebsd.org (Postfix) with ESMTP id EBF0637B496 for ; Thu, 12 Apr 2001 17:22:01 -0700 (PDT) (envelope-from dreid@jetnet.co.uk) Received: from godzilla (host217-32-142-4.hg.mdip.bt.net [217.32.142.4]) (authenticated) by www.jetnet.co.uk (8.11.1/8.11.1) with ESMTP id f3D0LpK15531 for ; Fri, 13 Apr 2001 01:21:51 +0100 (GMT/BST) Message-ID: <014b01c0c3af$8024c380$6400a8c0@godzilla> From: "David Reid" To: References: <200104120134.UAA20957@freebsd.netcom.com> <3AD52A10.7997F8EA@quake.com.au> <20010411233302.A8789@cec.wustl.edu> <3AD53763.B2B2B38A@quake.com.au> <20010412000948.C8789@cec.wustl.edu> <20010412191629.C1312@laptop.os2warp.org> Subject: Re: Games on FreeBSD Date: Fri, 13 Apr 2001 01:20:06 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No, no, what we should be doing is refusing to play the game in the first place. I'm going to aadopt the policy of NOT buying any hardware unless it has open access to enough information that drivers for any operating system that has the desire can be written. I'm sick and tired of having drivers for only one of the 3 OS's I run! The only thing they recognise is $$$ and £££ (or those daft euro things), so if enough people did it then the consumer will win. A lone voice... david > > > > Has anybody offered to sign an NDA with nVidia to write a binary-only > > driver for FreeBSD? Everybody should ask around amongst all the good > > FreeBSD hackers, to see if one of them would be willing to do so. > > Or go talk to SciTech Software. They are in the business of writing video > drivers for other people's hardware. They work really well on OS/2. > > They have a project to build drivers for XF86 for Linux. It is pay-ware > but worth it. I have four copies for my OS/2 boxes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 17:43:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from junkun.vblab.tsukuba.ac.jp (junkun.vbl.tsukuba.ac.jp [130.158.94.147]) by hub.freebsd.org (Postfix) with ESMTP id C276537B422 for ; Thu, 12 Apr 2001 17:43:48 -0700 (PDT) (envelope-from junkun@esys.tsukuba.ac.jp) Received: from localhost (junkun [192.168.2.147]) by junkun.vblab.tsukuba.ac.jp (8.11.3/8.11.3) with ESMTP id f3D0hmb00647 for ; Fri, 13 Apr 2001 09:43:48 +0900 (JST) (envelope-from junkun@esys.tsukuba.ac.jp) To: freebsd-stable@FreeBSD.ORG Subject: Re: USB mouse with FreeBSD 4.3 RC3 From: Jun YAMASHITA / =?iso-2022-jp?B?GyRCOzMyPD1fGyhC?= In-Reply-To: <200104121527.aa93629@salmon.maths.tcd.ie> References: <20010412224115R.junkun@esys.tsukuba.ac.jp> <200104121527.aa93629@salmon.maths.tcd.ie> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010413094348J.junkun@esys.tsukuba.ac.jp> Date: Fri, 13 Apr 2001 09:43:48 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 30 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Ian Dowse Subject: Re: USB mouse with FreeBSD 4.3 RC3 Date: Thu, 12 Apr 2001 15:27:04 +0100 Message-ID: <200104121527.aa93629@salmon.maths.tcd.ie> > (you can do this also via /boot/kernel.conf or the UserConfig > prompt with the command "irq pcic0 5"). I could use USB mouse and internal Memory Stick Slot. Thank you very much. What I did are: I add the following line to /boot/loader.conf. machdep.pccard.pcic_irq="5" # Assigns PCCARD controller IRQ (0=polled) Then I change the BIOS PnP OS seting to "NO". By the way, I have another question. A change was committed to the 5.0-current. The change is the code that enables to attach Sony Vaio's internal Memory Stick Slot(in /sys/cam/scsi/scsi_da.c, http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/cam/scsi/scsi_da.c.diff?r1=1.59&r2=1.60). Memory Stick is very popular storage and this code may make many FreeBSD users happy, and the code is just a one line. So I wish this change is MFCed to 4.3-stable, but I don't know how to claim. How should I do? send-pr? or any other way? Jun junkun@debug.gr.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 17:44: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from firebat.bushong.net (c128625-a.frmt1.sfba.home.com [24.176.225.90]) by hub.freebsd.org (Postfix) with ESMTP id 0093137B43F for ; Thu, 12 Apr 2001 17:44:01 -0700 (PDT) (envelope-from dbushong@firebat.bushong.net) Received: (from dbushong@localhost) by firebat.bushong.net (8.11.0/8.11.0) id f3D0i0x41202 for freebsd-stable@freebsd.org; Thu, 12 Apr 2001 17:44:00 -0700 (PDT) (envelope-from dbushong) Date: Thu, 12 Apr 2001 17:42:45 -0700 From: David Bushong To: freebsd-stable@freebsd.org Subject: Re: ATA_ENABLE_ATAPI_DMA gone? Message-ID: <20010412174245.D12643@bushong.net> References: <02db01c0c1b1$c1a0ffe0$0508a8c0@lofi.dyndns.org> <20010410123317.A73359@irrelevant.org> <200104101342.f3ADgsn15019@bmah-freebsd-0.cisco.com> <20010410153425.I5028@adriel.net> <20010410134934.Z15938@fw.wintelcom.net> <20010412150542.M5028@adriel.net> <20010412190042.A11761@cec.wustl.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010412190042.A11761@cec.wustl.edu>; from ajh3@chmod.ath.cx on Thu, Apr 12, 2001 at 07:00:42PM -0500 X-Floating-Sheep-Port: 0xbaa Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is the right place to put this? /boot/loader.conf? What's the command? Why isn't this in /usr/src/UPDATING? --David Bushong On Thu, Apr 12, 2001 at 07:00:42PM -0500, Andrew Hesford wrote: > On Thu, Apr 12, 2001 at 03:05:42PM -0500, adriel wrote: > > I suppose my frustration comes from changing something that worked > > perfectly for no good reason, what exactly was wrong with compiling that > > flag in the kernel, and why was it deemed "obsolete". I understand how > > to do it now, but my point remains, why was I forced to change, what > > advantage did I receive from this? I am not running -CURRENT. > > > > the main problem in my situation is that I have a DMA hd sharing an IDE > > cdrom, if you dont enable the ATAPI_DMA then it wont allow dma on the > > hard drive either. Maybe there is a good reason for this, but I still > > do not understand why something that was not breaking the system would > > be arbitrarily removed without any warning. The only POSSIBLE advantage > > I could have seen with moving this to be sysctl only is that you could > > change it without rebooting, and even that is not the case. > > Just because you don't run -CURRENT doesn't mean things aren't subject > to change. Nobody is forcing you to cvsup; you don't have to change > things if you don't want to. > > To keep a static system, run -RELEASE. > > -- > Andrew Hesford > ajh3@chmod.ath.cx > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 17:47: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cage.simianscience.com (cage.simianscience.com [64.7.134.1]) by hub.freebsd.org (Postfix) with ESMTP id 87BEA37B446 for ; Thu, 12 Apr 2001 17:47:04 -0700 (PDT) (envelope-from mike@sentex.net) Received: (from root@localhost) by cage.simianscience.com (8.11.3/8.11.2) id f3D0kwI44760; Thu, 12 Apr 2001 20:46:58 -0400 (EDT) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.3/8.11.2av) with ESMTP id f3D0krC44752; Thu, 12 Apr 2001 20:46:54 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010412204547.03077cf0@192.168.0.12> X-Sender: mdtancsa@192.168.0.12 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 12 Apr 2001 20:46:52 -0400 To: David Bushong , freebsd-stable@freebsd.org From: Mike Tancsa Subject: Re: ATA_ENABLE_ATAPI_DMA gone? In-Reply-To: <20010412174245.D12643@bushong.net> References: <20010412190042.A11761@cec.wustl.edu> <02db01c0c1b1$c1a0ffe0$0508a8c0@lofi.dyndns.org> <20010410123317.A73359@irrelevant.org> <200104101342.f3ADgsn15019@bmah-freebsd-0.cisco.com> <20010410153425.I5028@adriel.net> <20010410134934.Z15938@fw.wintelcom.net> <20010412150542.M5028@adriel.net> <20010412190042.A11761@cec.wustl.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05:42 PM 4/12/2001 -0700, David Bushong wrote: >What is the right place to put this? > >/boot/loader.conf? What's the command? Why isn't this in /usr/src/UPDATING? man ata will tell you. Yes, in /boot/loader.conf e.g. smtp2% cat /boot/loader.conf # -- sysinstall generated deltas -- # userconfig_script_load="YES" hw.ata.wc="1" smtp2% sysctl -a | grep ata kern.ipc.max_datalen: 136 hw.ata.ata_dma: 1 hw.ata.wc: 1 hw.ata.tags: 0 hw.ata.atapi_dma: 0 hw.atamodes: dma,---,---,---, smtp2% -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Network Administration, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 17:48:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id A2CE237B440 for ; Thu, 12 Apr 2001 17:48:34 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id RAA15929; Thu, 12 Apr 2001 17:48:31 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200104130048.RAA15929@freeway.dcfinc.com> Subject: Re: Games on FreeBSD In-Reply-To: <014b01c0c3af$8024c380$6400a8c0@godzilla> from David Reid at "Apr 13, 1 01:20:06 am" To: dreid@jetnet.co.uk (David Reid) Date: Thu, 12 Apr 2001 17:48:31 -0700 (MST) Cc: FreeBSD-STABLE@FreeBSD.ORG Reply-To: chad@DCFinc.com Organization: DCF, Inc. X-O/S: FreeBSD 2.2.8-STABLE X-Unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, David Reid wrote: > No, no, what we should be doing is refusing to play the game in the > first place. I'm going to aadopt the policy of NOT buying any > hardware unless it has open access to enough information that drivers > for any operating system that has the desire can be written. Here! Here! > A lone voice... Not so lone... -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 17:50:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id 20D4737B496 for ; Thu, 12 Apr 2001 17:50:27 -0700 (PDT) (envelope-from juha@saarinen.org) Received: from dendennis.saarinen.org ([192.168.1.2] helo=dendennis) by vimfuego.saarinen.org with smtp (Exim 3.22 #1 (Red Hack)) id 14nrmz-000602-00; Fri, 13 Apr 2001 12:50:17 +1200 From: "Juha Saarinen" To: "David Reid" , Subject: RE: Games on FreeBSD Date: Fri, 13 Apr 2001 12:50:26 +1200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <014b01c0c3af$8024c380$6400a8c0@godzilla> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :: I'm sick and tired of having drivers :: for only one of the 3 OS's I run! The only thing they recognise :: is $$$ and :: £££ (or those daft euro things), so if enough people did it then the :: consumer will win. It's a Catch-22 though. More users means better vendor support but to attract more users, you need better vendor support. -- Juha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 18:31:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from scully.zoominternet.net (scully.zoominternet.net [63.67.120.3]) by hub.freebsd.org (Postfix) with SMTP id 836A737B449 for ; Thu, 12 Apr 2001 18:31:52 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 30047 invoked from network); 13 Apr 2001 01:31:49 -0000 Received: from acs-24-154-53-183.zoominternet.net (HELO cvzoom.net) (24.154.53.183) by scully.zoominternet.net with SMTP; 13 Apr 2001 01:31:49 -0000 Message-ID: <3AD65706.E9ABB2B6@cvzoom.net> Date: Thu, 12 Apr 2001 21:31:50 -0400 From: Donn Miller X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: W Gerald Hicks Cc: FreeBSD-stable Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: <3AD427DC.CFC52BAE@quake.com.au> <3AD618E9.E3C5890E@cisco.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG W Gerald Hicks wrote: > > Uhm, Can we please move this thread away from the stable list? Exactly! Correct me if I'm wrong, but perhaps that's why we have a freebsd-hardware list. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 20:13:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from snoop.burghcom.com (burgcom.cust.stargate.net [209.166.166.21]) by hub.freebsd.org (Postfix) with SMTP id 36BA937B443 for ; Thu, 12 Apr 2001 20:13:32 -0700 (PDT) (envelope-from jl@burghcom.com) Received: (qmail 37308 invoked from network); 13 Apr 2001 03:13:30 -0000 Received: from host111.64-31-14.bignet.net (HELO celery) (64.31.14.111) by snoop.burghcom.com with SMTP; 13 Apr 2001 03:13:30 -0000 Message-ID: <001701c0c3c7$1a905a30$060aa8c0@celery> From: "JL" To: References: <200104130048.RAA15929@freeway.dcfinc.com> Subject: Re: Games on FreeBSD Date: Thu, 12 Apr 2001 23:09:07 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I know you want to kill this thread, but may I simply state that FreeBSD runs linux game servers in emulation better than they run in native linux, in my humble opinion. I have run quake3, and currently run half-life counter-strike daemons. We may not be able to play them, but we can serve them better than anything else. Jeff Love ----- Original Message ----- From: "Chad R. Larson" To: "David Reid" Cc: Sent: Thursday, April 12, 2001 8:48 PM Subject: Re: Games on FreeBSD > As I recall, David Reid wrote: > > No, no, what we should be doing is refusing to play the game in the > > first place. I'm going to aadopt the policy of NOT buying any > > hardware unless it has open access to enough information that drivers > > for any operating system that has the desire can be written. > > Here! Here! > > > A lone voice... > > Not so lone... > > -crl > -- > Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? > chad@dcfinc.com chad@larsons.org larson1@home.com > DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 20:33:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id A2B6737B422 for ; Thu, 12 Apr 2001 20:33:45 -0700 (PDT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 28959 invoked by uid 0); 13 Apr 2001 03:33:43 -0000 Received: from pd4b9eee4.dip.t-dialin.net (HELO lofizwei) (212.185.238.228) by mail.gmx.net (mp013-rz3) with SMTP; 13 Apr 2001 03:33:43 -0000 Message-ID: <008b01c0c3ca$ef31c3c0$0508a8c0@lofi.dyndns.org> From: "Michael Nottebrock" To: "adriel" , References: <02db01c0c1b1$c1a0ffe0$0508a8c0@lofi.dyndns.org> <20010410123317.A73359@irrelevant.org> <200104101342.f3ADgsn15019@bmah-freebsd-0.cisco.com> <20010410153425.I5028@adriel.net> <20010410134934.Z15938@fw.wintelcom.net> <20010412150542.M5028@adriel.net> Subject: Re: ATA_ENABLE_ATAPI_DMA gone? Date: Fri, 13 Apr 2001 05:36:31 +0200 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.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "adriel" To: Sent: Thursday, April 12, 2001 10:05 PM Subject: Re: ATA_ENABLE_ATAPI_DMA gone? > I suppose my frustration comes from changing something that worked > perfectly for no good reason, what exactly was wrong with compiling that > flag in the kernel, and why was it deemed "obsolete". I understand how > to do it now, but my point remains, why was I forced to change, what > advantage did I receive from this? I am not running -CURRENT. > > the main problem in my situation is that I have a DMA hd sharing an IDE > cdrom, if you dont enable the ATAPI_DMA then it wont allow dma on the > hard drive either. Maybe there is a good reason for this, but I still > do not understand why something that was not breaking the system would > be arbitrarily removed without any warning. The only POSSIBLE advantage > I could have seen with moving this to be sysctl only is that you could > change it without rebooting, and even that is not the case. > [...] As far as I understand it, it was moved because it is a driver setting, and a driver setting does not belong into the kernel-configuration (we are not running Linux here, are we?). With the old way, if the ENABLE setting would break your system, you would have to recompile the kernel, now it's just a matter of changing a configuration file. And, it _is_ possible to change the settings (of each individual device on the ide-bus) afterwards, without rebooting, by writing the sysctl-variable hw.atamodes (see 'man ata'). What I don't understand is that this change didn't make it's way into /usr/src/UPDATING. Someone should bother and add it, for all the updates that can be expected when 4.3 becomes a release. Greetings, Michael Nottebrock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 21:19:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id BC74937B424 for ; Thu, 12 Apr 2001 21:19:16 -0700 (PDT) (envelope-from mvh@ix.netcom.com) Received: from netcom1.netcom.com (lai-ca3b-205.ix.netcom.com [209.110.241.205]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id AAA21882 for ; Fri, 13 Apr 2001 00:19:15 -0400 (EDT) Received: by netcom1.netcom.com (Postfix, from userid 1000) id E9F0B113EDC; Thu, 12 Apr 2001 21:19:02 -0700 (PDT) From: Mike Harding To: freebsd-stable@freebsd.org Subject: Amanda dumps failing - glob change? Message-Id: <20010413041902.E9F0B113EDC@netcom1.netcom.com> Date: Thu, 12 Apr 2001 21:19:02 -0700 (PDT) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We have been using Amanda to do all of our backups, and recently we have been getting failures for a remote drive with lots of files. An examination of the /tmp/amanda directory shows 3 core files: sed.core sh.core sendbackup.core Could this be caused by the recent 'glob' changes? This system is a SMP system built April 6... FreeBSD dev1.xxxxx 4.3-RC FreeBSD 4.3-RC #0: Fri Apr 6 06:49:33 PDT 2001 root@dxxxxx:/usr/obj/usr/src/sys/SMP-4.3 i386 and we have been seeing failures since about Mar. 16. This has been killing our mail backups - anyone have any ideas? I will rebuild on Monday and see if this fixes anything but it's certainly worrisome - this system had been working without problems for several months. - Mike H. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 21:45:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 7706B37B449 for ; Thu, 12 Apr 2001 21:45:14 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f3D4j8009983; Thu, 12 Apr 2001 21:45:08 -0700 Date: Thu, 12 Apr 2001 21:45:08 -0700 From: Brooks Davis To: Mike Harding Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Amanda dumps failing - glob change? Message-ID: <20010412214508.A8902@Odin.AC.HMC.Edu> References: <20010413041902.E9F0B113EDC@netcom1.netcom.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="jRHKVT23PllUwdXP" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010413041902.E9F0B113EDC@netcom1.netcom.com>; from mvh@ix.netcom.com on Thu, Apr 12, 2001 at 09:19:02PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --jRHKVT23PllUwdXP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 12, 2001 at 09:19:02PM -0700, Mike Harding wrote: >=20 > We have been using Amanda to do all of our backups, and recently we > have been getting failures for a remote drive with lots of files. An > examination of the /tmp/amanda directory shows 3 core files:=20 >=20 > sed.core > sh.core > sendbackup.core >=20 > Could this be caused by the recent 'glob' changes? This system is a > SMP system built April 6... I don't think it's the glob changes. I've had problems with amanda dumps (in -current) of large volumes since the nodump changes went in. I've has success with backing the source off to before the change. I'm trying some patches recently posted somewhere that are supposed to correct some bugs, hopefully they will fix the problem I'm having. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --jRHKVT23PllUwdXP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE61oRUXY6L6fI4GtQRAltMAKCjhH6x9jGxbAhyPBo2kCpPbpI8lgCgq16V oNuPdqo13+LPaZh7XRqRs/c= =qieK -----END PGP SIGNATURE----- --jRHKVT23PllUwdXP-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 22:20:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 78CBA37B449 for ; Thu, 12 Apr 2001 22:20:25 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id wlwaaaaa for ; Fri, 13 Apr 2001 15:19:59 +1000 Message-ID: <3AD68D88.471BF306@quake.com.au> Date: Fri, 13 Apr 2001 15:24:24 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Donn Miller Cc: W Gerald Hicks , FreeBSD-stable Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: <3AD427DC.CFC52BAE@quake.com.au> <3AD618E9.E3C5890E@cisco.com> <3AD65706.E9ABB2B6@cvzoom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Donn Miller wrote: > > W Gerald Hicks wrote: > > > > Uhm, Can we please move this thread away from the stable list? > > Exactly! Correct me if I'm wrong, but perhaps that's why we have a > freebsd-hardware list. No, we have a hardware list for developers to talk about hardware and such things, not for topics to goto when certain people dont want to see them anymore! Dont read the thread if it annoys you so much, its not going to take us long to get this sorted out... I tired to start this topic in several other lists but got no joy, stable responded favourably, so we will finish it up here... It will die soon, we are close to working out the details! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 23:42:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from 1stwebs.com (1stwebs.com [216.122.237.185]) by hub.freebsd.org (Postfix) with ESMTP id 6E4BF37B440 for ; Thu, 12 Apr 2001 23:42:56 -0700 (PDT) (envelope-from deven@netexplorer.org) Received: from netexplorer.org (pilot.netexplorer.org [209.203.248.115]) by 1stwebs.com (8.11.0/8.11.0) with ESMTP id f3D6hOs36067; Thu, 12 Apr 2001 23:43:24 -0700 (PDT) (envelope-from deven@netexplorer.org) Message-ID: <3AD6A0C1.7040106@netexplorer.org> Date: Thu, 12 Apr 2001 23:46:25 -0700 From: Deven Kampenhout User-Agent: Mozilla/5.0 (X11; U; FreeBSD 4.3-BETA i386; en-US; 0.8) Gecko/20010321 X-Accept-Language: en MIME-Version: 1.0 To: Kal Torak Cc: freebsd-stable@FreeBSD.ORG Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: <20010411220425.22581.cpmta@c001.snv.cp.net> <3AD5F6BE.622E96FF@glue.umd.edu> <3AD6021B.40F8601F@quake.com.au> <3AD64466.441A6A21@quake.com.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kal Torak wrote: > I am waiting for nVidia to confirm if there is any work > currently happening on a FreeBSD driver... > > But when I talked to loki (www.lokigames.com) about drivers > for FreeBSD, they sure didnt know anything about it... So we > may as well get started on the group letter! > > Who said they could provide fast web access? And anyone interested > in making the page? We just need a simple page saying what where > trying to do and some sort of submition type thing setup... I could > do a simple perl script to handel that if no one has any better ideas! I can provide web server space. I can't say I have all the time in the world to create a web page, but I can give whoever wants to head that up access to my system. - Deven Kampenhout deven@netexplorer.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 12 23:55:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 180F037B423; Thu, 12 Apr 2001 23:55:43 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f3D6tkM02814; Thu, 12 Apr 2001 23:55:47 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: stable@freebsd.org Cc: developers@freebsd.org Subject: 4.3-RELEASE: One final delay X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010412235546U.jkh@osd.bsdi.com> Date: Thu, 12 Apr 2001 23:55:46 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 15 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry folks, we need just a little more time to pat everything into place, including the package testing. The release date is now scheduled for April 20th, 2001. I've also updated the 4.3-RC3 ISO image to contain Steve Price's absolute most up-to-date package set, hopefully fixing the reported issues with sysinstall's in-built package requirements and the KDE2 packages. There will be one more -RC release for both the x86 and Alpha platforms before the final release on the 20th. Thanks, - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 0: 2:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.viasoft.com.cn (unknown [61.153.1.177]) by hub.freebsd.org (Postfix) with ESMTP id 2F0D137B505; Fri, 13 Apr 2001 00:02:27 -0700 (PDT) (envelope-from bsddiy@21cn.com) Received: from xyf ([192.168.1.204]) by mail.viasoft.com.cn (8.9.3/8.9.3) with SMTP id OAA31940; Fri, 13 Apr 2001 14:58:46 +0800 Message-ID: <010d01c0c3e7$d0c7f180$cc01a8c0@xyf> From: "bsddiy" To: , "Jordan Hubbard" Cc: References: <20010412235546U.jkh@osd.bsdi.com> Subject: Re: 4.3-RELEASE: One final delay Date: Fri, 13 Apr 2001 15:03:02 +0800 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Delay is good. We are very pleasant with your wonderful work. Thanks, David Xu ----- Original Message ----- From: Jordan Hubbard To: Cc: Sent: Friday, April 13, 2001 2:55 PM Subject: 4.3-RELEASE: One final delay > Sorry folks, we need just a little more time to pat everything into > place, including the package testing. The release date is now > scheduled for April 20th, 2001. > > I've also updated the 4.3-RC3 ISO image to contain Steve Price's > absolute most up-to-date package set, hopefully fixing the reported > issues with sysinstall's in-built package requirements and the KDE2 > packages. > > There will be one more -RC release for both the x86 and Alpha > platforms before the final release on the 20th. > > Thanks, > > - Jordan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 0: 4:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 7037937B43F; Fri, 13 Apr 2001 00:04:42 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f3D74kM02908; Fri, 13 Apr 2001 00:04:46 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: stable@FreeBSD.ORG Cc: developers@FreeBSD.ORG Subject: Re: 4.3-RELEASE: One final delay In-Reply-To: <20010412235546U.jkh@osd.bsdi.com> References: <20010412235546U.jkh@osd.bsdi.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010413000446C.jkh@osd.bsdi.com> Date: Fri, 13 Apr 2001 00:04:46 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 6 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry, I forgot to include this in my previous email. The MD5 signature for the new 4.3-RC3 ISO image is: MD5 (4.3rc3-install.iso) = 4c0b43db6889edec3e40e7e441d2c5a6 - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 0: 6:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from 1stwebs.com (1stwebs.com [216.122.237.185]) by hub.freebsd.org (Postfix) with ESMTP id 481A437B446 for ; Fri, 13 Apr 2001 00:06:45 -0700 (PDT) (envelope-from deven@netexplorer.org) Received: from netexplorer.org (pilot.netexplorer.org [209.203.248.115]) by 1stwebs.com (8.11.0/8.11.0) with ESMTP id f3D77Hs36828; Fri, 13 Apr 2001 00:07:17 -0700 (PDT) (envelope-from deven@netexplorer.org) Message-ID: <3AD6A65A.5020504@netexplorer.org> Date: Fri, 13 Apr 2001 00:10:18 -0700 From: Deven Kampenhout User-Agent: Mozilla/5.0 (X11; U; FreeBSD 4.3-BETA i386; en-US; 0.8) Gecko/20010321 X-Accept-Language: en MIME-Version: 1.0 Cc: Kal Torak , freebsd-stable@FreeBSD.ORG Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: <20010411220425.22581.cpmta@c001.snv.cp.net> <3AD5F6BE.622E96FF@glue.umd.edu> <3AD6021B.40F8601F@quake.com.au> <3AD64466.441A6A21@quake.com.au> <3AD6A0C1.7040106@netexplorer.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Deven Kampenhout wrote: > Kal Torak wrote: > >> I am waiting for nVidia to confirm if there is any work >> currently happening on a FreeBSD driver... >> >> But when I talked to loki (www.lokigames.com) about drivers >> for FreeBSD, they sure didnt know anything about it... So we >> may as well get started on the group letter! >> >> Who said they could provide fast web access? And anyone interested >> in making the page? We just need a simple page saying what where >> trying to do and some sort of submition type thing setup... I could >> do a simple perl script to handel that if no one has any better ideas! > > > I can provide web server space. I can't say I have all the time in > the world to create a web page, but I can give whoever wants to head > that up access to my system. Ok. The site is up, along with a main page that I was able to spend about 1 minute in creating. If we have any web developers who wish to enhance the site, feel free to mail me to help get the page started. If not, then I will get to it eventually, but I warn that it will not be in the near future as I'm extremely busy at the moment. The site is at http://nvidia.netexplorer.org/ - Deven Kampenhout deven@netexplorer.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 0:17: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from jacinto.yi.org (dsl-64-34-174-133.telocity.com [64.34.174.133]) by hub.freebsd.org (Postfix) with ESMTP id 86AEE37B423 for ; Fri, 13 Apr 2001 00:17:01 -0700 (PDT) (envelope-from erich@jacinto.yi.org) Received: from jacinto.yi.org (palomar [192.168.42.22]) by jacinto.yi.org (8.9.3/8.9.3) with ESMTP id AAA60018 for ; Fri, 13 Apr 2001 00:13:43 -0700 (PDT) (envelope-from erich@jacinto.yi.org) Message-ID: <3AD6A7A3.4060002@jacinto.yi.org> Date: Fri, 13 Apr 2001 00:15:47 -0700 From: unsafe at any speed User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; 0.8.1) Gecko/20010412 X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: multiple CPUTYPEs? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings folks, Is it possible to have multiple /usr/obj directories compiled with different CPUTYPEs? A month or so ago I remember someone was having trouble installing onto a 486 from a system whose userland was compiled with i686 but whose /usr/obj was compiled with i486. Installworld was picking up a library from /usr/lib instead of /usr/obj/..../lib. Anyway, I didn't see if that ever got resolved. I guess I could just try it, but I figured I'd ask first. thanks, Eric Hedstrom erich@ucsd.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 0:20:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 085B937B43E for ; Fri, 13 Apr 2001 00:20:29 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id lmwaaaaa for ; Fri, 13 Apr 2001 17:19:59 +1000 Message-ID: <3AD6A9A7.65CCFF3D@quake.com.au> Date: Fri, 13 Apr 2001 17:24:24 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Deven Kampenhout Cc: freebsd-stable@FreeBSD.ORG Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: <20010411220425.22581.cpmta@c001.snv.cp.net> <3AD5F6BE.622E96FF@glue.umd.edu> <3AD6021B.40F8601F@quake.com.au> <3AD64466.441A6A21@quake.com.au> <3AD6A0C1.7040106@netexplorer.org> <3AD6A65A.5020504@netexplorer.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ok. The site is up, along with a main page that I was able to spend > about 1 minute in creating. If we have any web developers who wish to > enhance the site, feel free to mail me to help get the page started. If > not, then I will get to it eventually, but I warn that it will not be in > the near future as I'm extremely busy at the moment. > > The site is at http://nvidia.netexplorer.org/ Great! If I have time later I will do the site, unless someone else offers before I get a chance :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 1: 2:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nanguo.chalmers.com.au (gateway.chalmers.com.au [203.1.96.1]) by hub.freebsd.org (Postfix) with ESMTP id 5E9E437B424; Fri, 13 Apr 2001 01:02:21 -0700 (PDT) (envelope-from robert@chalmers.com.au) Received: from carbon (carbon.chalmers.com.au [203.1.96.26]) by nanguo.chalmers.com.au (8.11.0/8.11.0) with SMTP id f3D82pw09687; Fri, 13 Apr 2001 18:02:51 +1000 (EST) From: "Robert" To: "bsddiy" , , "Jordan Hubbard" Cc: Subject: RE: 4.3-RELEASE: One final delay Date: Fri, 13 Apr 2001 18:05:28 +1000 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.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: <010d01c0c3e7$d0c7f180$cc01a8c0@xyf> Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I agree entirely. Better to be certain than rush something out the door. Robert > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of bsddiy > Sent: Friday, 13 April 2001 5:03 PM > To: stable@FreeBSD.ORG; Jordan Hubbard > Cc: developers@FreeBSD.ORG > Subject: Re: 4.3-RELEASE: One final delay > > > Delay is good. > We are very pleasant with your wonderful work. > > Thanks, > David Xu > > ----- Original Message ----- > From: Jordan Hubbard > To: > Cc: > Sent: Friday, April 13, 2001 2:55 PM > Subject: 4.3-RELEASE: One final delay > > > > Sorry folks, we need just a little more time to pat everything into > > place, including the package testing. The release date is now > > scheduled for April 20th, 2001. > > > > I've also updated the 4.3-RC3 ISO image to contain Steve Price's > > absolute most up-to-date package set, hopefully fixing the reported > > issues with sysinstall's in-built package requirements and the KDE2 > > packages. > > > > There will be one more -RC release for both the x86 and Alpha > > platforms before the final release on the 20th. > > > > Thanks, > > > > - Jordan > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 1:16:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from chmod.ath.cx (CC2-861.charter-stl.com [24.217.115.99]) by hub.freebsd.org (Postfix) with ESMTP id B2C0637B446; Fri, 13 Apr 2001 01:16:27 -0700 (PDT) (envelope-from ajh3@chmod.ath.cx) Received: by chmod.ath.cx (Postfix, from userid 1001) id 8A0DEA91E; Fri, 13 Apr 2001 03:15:40 -0500 (CDT) Date: Fri, 13 Apr 2001 03:15:40 -0500 From: Andrew Hesford To: Robert Cc: bsddiy , stable@FreeBSD.ORG, Jordan Hubbard , developers@FreeBSD.ORG Subject: Re: 4.3-RELEASE: One final delay Message-ID: <20010413031540.C12819@cec.wustl.edu> References: <010d01c0c3e7$d0c7f180$cc01a8c0@xyf> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from robert@chalmers.com.au on Fri, Apr 13, 2001 at 06:05:28PM +1000 X-Loop: Andrew Hesford Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 13, 2001 at 06:05:28PM +1000, Robert wrote: > I agree entirely. Better to be certain than rush something out the door. > > Robert > > > -----Original Message----- > > From: owner-freebsd-stable@FreeBSD.ORG > > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of bsddiy > > Sent: Friday, 13 April 2001 5:03 PM > > To: stable@FreeBSD.ORG; Jordan Hubbard > > Cc: developers@FreeBSD.ORG > > Subject: Re: 4.3-RELEASE: One final delay > > > > > > Delay is good. > > We are very pleasant with your wonderful work. > > > > Thanks, > > David Xu As long as my supfile says RELENG_4, I don't really care if it's called -RELEASE, -STABLE, -RC or -BETA. Hell, you could call if -SHITPILE, if you really wanted to. Just keep providing a stable BSD platform, and I'll keep contributing in any way possible. -- Andrew Hesford ajh3@chmod.ath.cx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 7: 5:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tomts13-srv.bellnexxia.net (tomts13.bellnexxia.net [209.226.175.34]) by hub.freebsd.org (Postfix) with ESMTP id B850037B449 for ; Fri, 13 Apr 2001 07:05:55 -0700 (PDT) (envelope-from blaue@sympatico.ca) Received: from sympatico.ca ([64.228.82.35]) by tomts13-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010413140554.ITDF12101.tomts13-srv.bellnexxia.net@sympatico.ca> for ; Fri, 13 Apr 2001 10:05:54 -0400 Message-ID: <3AD707D9.9F2CD909@sympatico.ca> Date: Fri, 13 Apr 2001 10:06:17 -0400 From: Brad Laue X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: FreeBSD 4.3RC out of buffer space in network operations Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sendto in send_tcp_raw: sendto(3, packet, 40, 0, 64.228.82.35, 16) => No buffer space available Sleeping 15 seconds then retrying This occurs mainly when nmap -sS is called, and has just started occuring within the last few cvsups. I have adjusted NMBCLUSTERS as well as MAXUSERS and several things using sysctl, with no success. The one peculiarity is that the interface in question is tunneling PPPoE. It seems generally incapable of communicating with nmap normally, manifesting many odd behaviours (such as nmap not knowing which interface on which to route a scan, even though it is the default route). PPPoE is set up exactly as pointed out in the FreeBSD handbook. nmap might not be a serious utility for most, but it has pointed out to me that something to do with networking is very broken. Any suggestions you may have are more than welcome! FreeBSD TMA-1.brad-x.com 4.3-RC FreeBSD 4.3-RC #0: Thu Apr 12 03:02:34 EDT 2001 root@TMA-1.brad-x.com:/usr/src/sys/compile/DISCOVERY-IPF i386 Cheers, Brad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 7:21:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mta2.snfc21.pbi.net (mta2.snfc21.pbi.net [206.13.28.123]) by hub.freebsd.org (Postfix) with ESMTP id 4676237B42C for ; Fri, 13 Apr 2001 07:21:46 -0700 (PDT) (envelope-from freep@postoffice.pacbell.net) Received: from terra ([64.166.224.36]) by mta2.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with SMTP id <0GBQ00CH1IK1DA@mta2.snfc21.pbi.net> for freebsd-stable@FreeBSD.ORG; Fri, 13 Apr 2001 07:21:38 -0700 (PDT) Date: Fri, 13 Apr 2001 07:21:38 -0700 From: Sam Subject: fetchmail broke To: freebsd-stable@FreeBSD.ORG Message-id: MIME-version: 1.0 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Content-type: multipart/mixed; boundary="----=_NextPart_000_000C_01C0C3EA.6108BCA0" Importance: Normal X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-MS-TNEF-Correlator: X-Priority: 3 (Normal) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_000C_01C0C3EA.6108BCA0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit I'm a relative newbie and I'm not sure this is the right place for this question. I recently cvsupped and then recompiled my kernel which broke my fetchmail. I recompiled from ports both fetchmail and sendmail. the relevant message in the fetchmail log is: fetchmail: 5.5.6 querying thecity.sfsu.edu (protocol POP3) at Tue Apr 10 00:57:19 2001 fetchmail: fetchmail: getaddrinfo(thecity.sfsu.edu.pop3) fetchmail: Query status=2 (SOCKET) i ran fetchmail with verbose logging and found this error message: fetchmail: 5.7.6 querying pop.mail.yahoo.com (protocol POP3) at Thu Apr 12 07:57:11 2001 fetchmail: POP3< +OK hello from popgate fetchmail: POP3> USER * fetchmail: POP3< +OK password required. fetchmail: POP3> PASS * fetchmail: POP3< +OK maildrop ready, 1 message (6720 octets) (7677 6291456) fetchmail: POP3> STAT fetchmail: POP3< +OK 1 6720 fetchmail: 1 message for * at pop.vip.sc5.yahoo.com (6720 octets). fetchmail: POP3> LIST fetchmail: POP3< +OK 1 message (6720 octets) fetchmail: POP3< 1 6720 fetchmail: POP3< . fetchmail: POP3> RETR 1 fetchmail: POP3< +OK 6720 octets fetchmail: reading message 1 of 1 (6720 octets) fetchmail: SMTP< 220 sol.A ESMTP Sendmail 8.11.1/8.11.1; Thu, 12 Apr 2001 07:57:14 -0700 (PDT) fetchmail: SMTP> EHLO localhost fetchmail: SMTP< 250-sol.A Hello localhost [127.0.0.1], pleased to meet you fetchmail: SMTP< 250-ENHANCEDSTATUSCODES fetchmail: SMTP< 250-8BITMIME fetchmail: SMTP< 250-SIZE fetchmail: SMTP< 250-DSN fetchmail: SMTP< 250-ONEX fetchmail: SMTP< 250-ETRN fetchmail: SMTP< 250-XUSR fetchmail: SMTP< 250 HELP fetchmail: SMTP> MAIL FROM: SIZE=6720 fetchmail: SMTP< 451 4.1.8 ... Domain of sender address opirpet@mai ltimeonline.com does not resolve fetchmail: SMTP> RSET fetchmail: SMTP< 250 2.0.0 Reset state fetchmail: SMTP error: 250 2.0.0 Reset state fetchmail: not flushed fetchmail: POP3> QUIT fetchmail: POP3< +OK server signing off. fetchmail: 5.7.6 querying postoffice.pacbell.net (protocol POP3) at Thu Apr 12 07:57:15 2001 fetchmail: fetchmail: getaddrinfo(postoffice.pacbell.net.pop3) fetchmail: Query status=2 (SOCKET) fetchmail: SMTP> QUIT anyone know what is going on? is getaddrinfo() broken? thanks in advance for all your help, Sam ------=_NextPart_000_000C_01C0C3EA.6108BCA0 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="winmail.dat" eJ8+IiYOAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEGgAMADgAAANEHBAANAAcAFQAAAAUACgEB A5AGAEQJAAAmAAAACwACAAEAAAALACMAAAAAAAMAJgAAAAAACwApAAAAAAADADYAAAAAAB4AcAAB AAAAEAAAAGZldGNobWFpbCBicm9rZQACAXEAAQAAABYAAAABwMQlDRWnEVllL9ER1Z9KAJAnJqnF AAACAR0MAQAAACIAAABTTVRQOkZSRUVQQFBPU1RPRkZJQ0UuUEFDQkVMTC5ORVQAAAALAAEOAAAA AEAABg4AroL2JMTAAQIBCg4BAAAAGAAAAAAAAAAZO2vwMZrSEZ87ABB6oAZ2woAAAAsAHw4BAAAA AgEJEAEAAAADBQAA/wQAAEkKAABMWkZ1rmpbagMACgByY3BnMTI1FjIA+Atgbg4QMDMzTwH3AqQD 4wIAY2gKwHOwZXQwIAcTAoB9CoGSdgiQd2sLgGQ0DGAOYwBQCwMLtSBJJ20YIGEgCXALYHRpduhl IG4H0GIIkBQAEoBpE8NubwVAcwhwFKB0emgEACAWYRZAFKAFEGf2aAVAC1FjFKACEAXAFkPacQpQ cxRwAiAuE8AUIYMXkAIwbHkgY3YV8PxwcAmAFSMWwQOgGREDcNZwAxAaAW0ZgGsEkRRAzCB3FlAQ 4CBiA2AboP0bYmYRMBDgAMADEBjVGvb/A1IXUAkRBCAG4BZAHPgVI58RIBKAHVQWwxRAZXYAcOMF QAeBc2FnFKALgBaz6x+ICQBnFoE6CqIKhAqAoR0HOiA1LiVANhhCHHJ5C4AjgBbBY2l0SHkucwPQ dS4JgHVIIChwA2B0bwjhIGBQT1AzKRQABUBUFwpQEWAnUCAPQCAwMIA6NTc6MTkgAdA+MBLjJHsk mSIgAZBkZFUFEG4CECgmPi4e0HA7KBAp/1ElshXgAZB0dQhzPTInMFNPQ0vsRVQtxSPUaRQgA5Ef iHcD8B9RFJByBuARICNSZ/cl8hUyAhB1GkMWYQSQA2BvBcAh1SPPJNc3JXotgS6BHVN5YWhvby4a 4bsnPyhCaCcgKLMvsDApYB0pUjEpryTzJ+I8ICvoT0sgFtBsCQAedg4ADRRgZTt/J+I+IFVT8EVS ICo+TzyICrAEEF53BbAVUAlwGFBpCXEu40AfP1RQQVMF8EAPPHmfHVIsAC2QFCEr4HksKODpIcco NgHBICeQPiAfAAkoICg3SBA3IDYyYDkxNDU2Lc8/RVP4VEFUSc88iDsQSBJLf/tHaBfCKigyN5IS IDewBPCfJUA4KUgaQt8/RUxJSzD/Ug9MikePSJJTvzyETS88KvtR/z9FUjAgP+A7bzx5SBmfW/9G 8iXyIdY7EG9mVVFDVg8ke1NNVFA8wDKFE6FzBvAuQSBFYrJjBlEghCA4LjsAZLAv/WSkOzniR0Ev sCiyOzI6ljg0IC06oCkgOLBQRIcwNmINP5BFSExPI1E+YwdAOEAYgGfvYrU1MJotY1RIPTNppyBb DiDlNsAwbYExXUdAC1BHAJ8RIBpRPWAHgBEwIHkIYANqP2tIRU5IQU5DjEVESzI/sENPRGOwA29P a0g4QklUTUmMTUVyL2tIU0ladE8bazlxYE52T2tIT05Fvlh4L3BZW7B4H2s5WD+wjlJ8D2tHbDBF TFB9/wFo9E1BSUwgRlJwT006PC2QQpAZ8HReQB1SFHAHgAIgbAuAZfc4cksRdhE9WG9ieEmAOxBi NGSwLjgggf+DCS75iCAgRANxIlFggSBiBJB/FAAr8SHhSFCGiDU0gr0g/GRvB5EVsomhBvAUkIRf 3Wj0Uj/AU69++TJtggfw/weQbuEvQoz/YqM0RCUgkC//kT8lAhWjDvAvgBbQCzFcH3k/clFVc/CW bzyIESByvzJhFeAXEAMAJgFggGZaHz82n2oBmrEN4INQCrBjYn09MS4UwAVAOM853ylhNf87Lyq/ K8mc/54DLX8ujy+f/41fl8k1NABwbxAUwBuQFbBPB+AcEChBFmFnb5pzbv4/q0MrySggHHOr8DU6 FkD9AHBrFnEDoCvgIYEXlQdAbwMgbxEFwD0hcEdABhBtCzU0EeEAsYAAAwAAfAUAAAALAAGACCAG AAAAAADAAAAAAAAARgAAAAADhQAAAAAAAAMABYAIIAYAAAAAAMAAAAAAAABGAAAAAFKFAAAnagEA HgAGgAggBgAAAAAAwAAAAAAAAEYAAAAAVIUAAAEAAAAEAAAAOS4wAAMAB4AIIAYAAAAAAMAAAAAA AABGAAAAAAGFAAAAAAAACwAQgAggBgAAAAAAwAAAAAAAAEYAAAAADoUAAAAAAAADABGACCAGAAAA AADAAAAAAAAARgAAAAAQhQAAAAAAAAMAEoAIIAYAAAAAAMAAAAAAAABGAAAAABGFAAAAAAAAAwAV gAggBgAAAAAAwAAAAAAAAEYAAAAAGIUAAAAAAAAeACWACCAGAAAAAADAAAAAAAAARgAAAAA2hQAA AQAAAAEAAAAAAAAAHgAmgAggBgAAAAAAwAAAAAAAAEYAAAAAN4UAAAEAAAABAAAAAAAAAB4AJ4AI IAYAAAAAAMAAAAAAAABGAAAAADiFAAABAAAAAQAAAAAAAAALAAyBCCAGAAAAAADAAAAAAAAARgAA AACChQAAAQAAAAsAKoEIIAYAAAAAAMAAAAAAAABGAAAAAAaFAAAAAAAAAgH4DwEAAAAQAAAAGTtr 8DGa0hGfOwAQeqAGdgIB+g8BAAAAEAAAABk7a/AxmtIRnzsAEHqgBnYCAfsPAQAAAGAAAAAAAAAA OKG7EAXlEBqhuwgAKypWwgAAUFNUUFJYLkRMTAAAAAAAAAAATklUQfm/uAEAqgA32W4AAABcXFNP TFxGSUxFU1xVc2Vyc1xzYW1cTUFJTFxNYWlsYm94LnBzdAADAP4PBQAAAAMADTT9NwAAAgF/AAEA AAA8AAAAPE5DQkJKUERMQkpDTEJCRkFESE9NS0VMQ0RQQUEuZnJlZXBAcG9zdG9mZmljZS5wYWNi ZWxsLm5ldD4AAwAGEKeSHFMDAAcQWAcAAAMAEBAAAAAAAwAREAAAAAAeAAgQAQAAAGUAAABJTUFS RUxBVElWRU5FV0JJRUFORElNTk9UU1VSRVRISVNJU1RIRVJJR0hUUExBQ0VGT1JUSElTUVVFU1RJ T05JUkVDRU5UTFlDVlNVUFBFREFORFRIRU5SRUNPTVBJTEVETVlLAAAAAGhP ------=_NextPart_000_000C_01C0C3EA.6108BCA0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 7:31:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id 50AF237B423 for ; Fri, 13 Apr 2001 07:31:51 -0700 (PDT) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.11.3) with SMTP id f3DETap01498; Fri, 13 Apr 2001 10:29:37 -0400 (EDT) (envelope-from matt@gsicomp.on.ca) Message-ID: <017001c0c425$b60c3020$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Robin P. Blanchard" , References: <3AD5A1F9.7133FC74@gactr.uga.edu> Subject: Re: install world on 486] Date: Fri, 13 Apr 2001 10:26:20 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > i cvs'd (src-all tag=RELENG_4) this morning and rebuilt on a i686 > with the following make.conf: > > FETCH_BEFORE_ARGS=-p > USA_RESIDENT=yes > MAKE_IDEA=YES > #CPUTYPE=i486 This will 'buildworld' everything using the current processor type. Since you're building on an i686, it's going to create code for the i686, which won't run properly on your i486. > installworld on the 486 dies with: > > pid 2645 (strip), uid 0: exited on signal 4 (core dumped) > *** Error code 70 Signal 4 is "Illegal Instruction", which is quite reasonable, since your 'buildworld' was run on an i686 machine. Early in the 'installworld' process, new copies of many compilation tools (such as strip) are installed on the target machine. Since these tools were compiled for i686, they're failing miserably on your i486. You need to re-enable the CPUTYPE lines in /etc/make.conf and re-run your 'make buildworld' again. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 7:46:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id 837C837B446 for ; Fri, 13 Apr 2001 07:46:38 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id f3DEkbV19907 for ; Fri, 13 Apr 2001 07:46:37 -0700 (PDT) Received: from pau-amma.whistle.com( 207.76.205.64) by whistle.com via smap (V2.0) id xma019902; Fri, 13 Apr 2001 07:46:21 -0700 Received: (from dhw@localhost) by pau-amma.whistle.com (8.11.1/8.11.1) id f3DEkKj89412 for freebsd-stable@FreeBSD.ORG; Fri, 13 Apr 2001 07:46:20 -0700 (PDT) Date: Fri, 13 Apr 2001 07:46:20 -0700 (PDT) From: David Wolfskill Message-Id: <200104131446.f3DEkKj89412@pau-amma.whistle.com> To: freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD 4.3RC out of buffer space in network operations In-Reply-To: <3AD707D9.9F2CD909@sympatico.ca> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Fri, 13 Apr 2001 10:06:17 -0400 >From: Brad Laue >sendto in send_tcp_raw: sendto(3, packet, 40, 0, 64.228.82.35, 16) => No >buffer space available >Sleeping 15 seconds then retrying >This occurs mainly when nmap -sS is called, and has just started >occuring within the last few cvsups. I have adjusted NMBCLUSTERS >as well as MAXUSERS and several things using sysctl, with no >success. I saw this yesterday (also using nmap, but -sP) on my laptop: FreeBSD m133.whistle.com 4.3-RC FreeBSD 4.3-RC #16: Thu Apr 12 11:29:44 PDT 2001 root@m138.whistle.com:/common/S2/obj/usr/src/sys/LAPTOP_30W i386 I had a couple of local modifications affecting the interface in use (an0), so it wasn't apparent to me that this might be something that others would (necessarily or likely) see (which is one reason I didn't mention it then). >The one peculiarity is that the interface in question is tunneling >PPPoE. It seems generally incapable of communicating with nmap normally, >manifesting many odd behaviours (such as nmap not knowing which >interface on which to route a scan, even though it is the default >route). In my case, there's no PPPoE involved, so I suspect that it's not likely an issue. Also, the machine has 256 MB RAM; maxusers is set to 128. I have ready access to a local repository, and can try things out reasonably quickly. Here's a diff of GENERIC vs. LAPTOP_30W (my kernel config file): --- GENERIC Fri Apr 6 05:10:12 2001 +++ LAPTOP_30W Mon Apr 9 13:59:17 2001 @@ -15,19 +15,15 @@ # 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.246.2.23 2001/03/07 08:08:42 imp Exp $ +# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.20 2000/10/31 23:16:07 n_hibma Exp $ machine i386 -cpu I386_CPU -cpu I486_CPU -cpu I586_CPU cpu I686_CPU -ident GENERIC -maxusers 32 +ident "LAPTOP_30W" +maxusers 128 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols -options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem @@ -75,53 +72,26 @@ device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives -device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering +#options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # SCSI Controllers -device ahb # EISA AHA1742 family -device ahc # AHA2940 and onboard AIC7xxx devices -device amd # AMD 53C974 (Tekram DC-390(T)) -device isp # Qlogic family -device ncr # NCR/Symbios Logic -device sym # NCR/Symbios Logic (newer chipsets) -options SYM_SETUP_LP_PROBE_MAP=0x40 - # Allow ncr to attach legacy NCR devices when - # both sym and ncr are configured - -device adv0 at isa? -device adw -device bt0 at isa? -device aha0 at isa? -device aic0 at isa? - -device ncv # NCR 53C500 -device nsp # Workbit Ninja SCSI-3 -device stg # TMC 18C30/18C50 # SCSI peripherals -device scbus # SCSI bus (required) -device da # Direct Access (disks) -device sa # Sequential Access (tape etc) -device cd # CD -device pass # Passthrough device (direct SCSI access) # RAID controllers interfaced to the SCSI subsystem -device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID -device dpt # DPT Smartcache - See LINT for options! -device mly # Mylex AcceleRAID/eXtremeRAID # RAID controllers -device aac # Adaptec FSA RAID, Dell PERC2/PERC3 -device ida # Compaq Smart RAID -device amr # AMI MegaRAID -device mlx # Mylex DAC960 family -device twe # 3ware Escalade # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0 at atkbdc? irq 12 +# Options for psm: +options PSM_DEBUG=0 # 1 for debugging +options PSM_HOOKRESUME #hook the system resume event, useful + #for some laptops +options PSM_RESETAFTERSUSPEND #reset the device at the resume event device vga0 at isa? @@ -142,12 +112,14 @@ 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 +device apm0 at nexus? flags 0x20 # Advanced Power Management # PCCARD (PCMCIA) support device card device pcic0 at isa? irq 0 port 0x3e0 iomem 0xd0000 device pcic1 at isa? irq 0 port 0x3e2 iomem 0xd4000 disable +# You may need to reset all pccards after resuming +options PCIC_RESUME_RESET # reset after resume # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 @@ -187,31 +159,22 @@ # ISA Ethernet NICs. device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 -device ex -device ep -device fe0 at isa? port 0x300 -# Xircom Ethernet -device xe -# PRISM I IEEE 802.11b wireless NIC. -device awi # WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really # exists only as a PCMCIA device, so there is no ISA attachment needed # and resources will always be dynamically assigned by the pccard code. device wi # Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will # work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP # mode (the factory default). If you set the switches on your ISA # card for a manually chosen I/O address and IRQ, you must specify # those parameters here. device an +# Xircom Ethernet +device xe # 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 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 -device sn0 at isa? port 0x300 irq 10 # Pseudo devices - the number indicates how many units to allocate. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device sl 1 # Kernel SLIP @@ -224,7 +187,7 @@ # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! -pseudo-device bpf #Berkeley packet filter +pseudo-device bpf 3 #Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface @@ -234,10 +197,25 @@ device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer -device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device uscanner # Scanners # USB Ethernet, requires mii device aue # ADMtek USB ethernet device cue # CATC USB ethernet device kue # Kawasaki LSI USB ethernet + +# For non-pnp sound cards with no bridge drivers only: +# device pcm0 at isa? irq 10 drq 1 flags 0x0 +# +# For PnP/PCI sound cards +device pcm + +# Not controlled by `snd' +device pca0 at isa? port IO_TIMER1 + +# +# Allow user-mode programs to manipulate their local descriptor tables. +# This option is required for the WINE Windows(tm) emulator, and is +# not used by anything else (that we know of). +# +options USER_LDT #allow user-level control of i386 ldt Cheers, david -- David Wolfskill dhw@whistle.com UNIX System Administrator Desk: 650/577-7158 TIE: 8/499-7158 Cell: 650/759-0823 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 7:52: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gactr.uga.edu (mail.gactr.uga.edu [128.192.37.21]) by hub.freebsd.org (Postfix) with SMTP id 5B0DF37B422 for ; Fri, 13 Apr 2001 07:52:05 -0700 (PDT) (envelope-from Robin_Blanchard@gactr.uga.edu) Received: (qmail 26986 invoked from network); 13 Apr 2001 14:52:04 -0000 Received: from qat.noc.nat (HELO gactr.uga.edu) ([10.10.100.125]) (envelope-sender ) by mail.servers.nat (qmail-ldap-1.03) with SMTP for ; 13 Apr 2001 14:52:04 -0000 Message-ID: <3AD71263.6E420055@gactr.uga.edu> Date: Fri, 13 Apr 2001 10:51:15 -0400 From: "Robin P. Blanchard" X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Emmerton Cc: stable@FreeBSD.ORG Subject: Re: install world on 486] References: <3AD5A1F9.7133FC74@gactr.uga.edu> <017001c0c425$b60c3020$1200a8c0@gsicomp.on.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG the reason CPUTYPE was commented out was because i'd gotten the same error while having CPUTYPE set and seemed to remember someone on the list saying something about CPUTYPE=i486 giving him the same errors for 'strip'. so CPUTYPE or not CPUTYPE, i get the same error. > > i cvs'd (src-all tag=RELENG_4) this morning and rebuilt on a i686 > > with the following make.conf: > > > > FETCH_BEFORE_ARGS=-p > > USA_RESIDENT=yes > > MAKE_IDEA=YES > > #CPUTYPE=i486 > > This will 'buildworld' everything using the current processor type. Since > you're building on an i686, it's going to create code for the i686, which > won't run properly on your i486. > > > installworld on the 486 dies with: > > > > pid 2645 (strip), uid 0: exited on signal 4 (core dumped) > > *** Error code 70 > > Signal 4 is "Illegal Instruction", which is quite reasonable, since your > 'buildworld' was run on an i686 machine. Early in the 'installworld' > process, new copies of many compilation tools (such as strip) are installed > on the target machine. Since these tools were compiled for i686, they're > failing miserably on your i486. > > You need to re-enable the CPUTYPE lines in /etc/make.conf and re-run your > 'make buildworld' again. > > -- > Matt Emmerton -- ------------------------------------ Robin P. Blanchard IT Program Specialist Georgia Center for Continuing Ed. fon: 706.542.2404 fax: 706.542.6546 email: Robin_Blanchard@gactr.uga.edu ------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 8: 1:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id F33B737B449 for ; Fri, 13 Apr 2001 08:01:18 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14o54W-0001B1-00 for freebsd-stable@freebsd.org; Fri, 13 Apr 2001 16:01:16 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f3DF1Fg18356 for freebsd-stable@freebsd.org; Fri, 13 Apr 2001 16:01:15 +0100 (BST) (envelope-from jcm) Date: Fri, 13 Apr 2001 16:01:15 +0100 From: j mckitrick To: freebsd-stable@freebsd.org Subject: module documentation? Message-ID: <20010413160114.A18212@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has there been any documentation on how to compile modules into or outside the kernel? I must have missed the transition, and I'd like to move sound into a module. I'd also like to see what else could be moved. jm -- ----------------------------------------------------------- Jonathon McKitrick -- jcm@freebsd-uk.eu.org Bill's Law - "The speed of Windows halves every 18 months." ----------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 8: 8:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from icon.bg (icon.bg [62.176.80.58]) by hub.freebsd.org (Postfix) with SMTP id 1D4C937B446 for ; Fri, 13 Apr 2001 08:08:27 -0700 (PDT) (envelope-from v0rbiz@icon.bg) Received: (qmail 33481 invoked by uid 1144); 13 Apr 2001 15:12:39 -0000 Date: Fri, 13 Apr 2001 18:12:39 +0300 From: Victor Ivanov To: "Robin P. Blanchard" Cc: freebsd-stable@freebsd.org Subject: Re: install world on 486] Message-ID: <20010413181239.A33404@icon.icon.bg> References: <3AD5A1F9.7133FC74@gactr.uga.edu> <017001c0c425$b60c3020$1200a8c0@gsicomp.on.ca> <3AD71263.6E420055@gactr.uga.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="NzB8fVQJ5HfG6fxh" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AD71263.6E420055@gactr.uga.edu>; from Robin_Blanchard@gactr.uga.edu on Fri, Apr 13, 2001 at 10:51:15AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 13, 2001 at 10:51:15AM -0400, Robin P. Blanchard wrote: > the reason CPUTYPE was commented out was because i'd gotten the > same error while having CPUTYPE set and seemed to remember someone > on the list saying something about CPUTYPE=3Di486 giving him the > same errors for 'strip'. >=20 > so CPUTYPE or not CPUTYPE, i get the same error. Without CPUTYPE it's i386 isn't it? I have /usr/obj on a CD, it was built on a i686 machine (actualy a buggy Cyrix) without the CPUTYPE option in make.conf. Later I have installed this on a i586 and on old Compaq with i486 processor -- didn't have any problems... The failing i486 could have hardware problems (bad memory?) > > > i cvs'd (src-all tag=3DRELENG_4) this morning and rebuilt on a i686 > > > with the following make.conf: > > > > > > FETCH_BEFORE_ARGS=3D-p > > > USA_RESIDENT=3Dyes > > > MAKE_IDEA=3DYES > > > #CPUTYPE=3Di486 > >=20 > > This will 'buildworld' everything using the current processor type. Si= nce > > you're building on an i686, it's going to create code for the i686, whi= ch > > won't run properly on your i486. > >=20 > > > installworld on the 486 dies with: > > > > > > pid 2645 (strip), uid 0: exited on signal 4 (core dumped) > > > *** Error code 70 > >=20 > > Signal 4 is "Illegal Instruction", which is quite reasonable, since your > > 'buildworld' was run on an i686 machine. Early in the 'installworld' > > process, new copies of many compilation tools (such as strip) are insta= lled > > on the target machine. Since these tools were compiled for i686, they'= re > > failing miserably on your i486. > >=20 > > You need to re-enable the CPUTYPE lines in /etc/make.conf and re-run yo= ur > > 'make buildworld' again. --=20 Players win and winners play Have a lucky day --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.1i iQCVAwUBOtcXZfD9M5lef5W3AQHjzAP/Qy0+hzrNm9dyIqbN//M0zrOn3FclKGQd B5J64+qlozUbK971sX4vgj0/3mlKxcHdH48pcFWeo2p44PNlUw8a+UhxVRTQQ4Go 2+zXvkxcElOuvWuFWcgRqfUhqBU2dHzoYcEcoZs6qsDybrIvRshUS/gn0O3CXAUO 6/qncCbbflM= =ZPN+ -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 9: 0:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from internal.mail.telinco.net (internal.mail.telinco.net [212.1.128.4]) by hub.freebsd.org (Postfix) with ESMTP id 9FE7437B506 for ; Fri, 13 Apr 2001 09:00:44 -0700 (PDT) (envelope-from b.candler@pobox.com) Received: from ppp-dp1-mk-66.access.uk.worldonline.com ([212.74.113.66] helo=bloodhound.uk.worldonline.com) by internal.mail.telinco.net with esmtp (Exim 3.02 #1) id 14o603-000AjF-00; Fri, 13 Apr 2001 17:00:43 +0100 Received: from brian by bloodhound.uk.worldonline.com with local (Exim 3.22 #1) id 14o602-00022F-00; Fri, 13 Apr 2001 17:00:42 +0100 Date: Fri, 13 Apr 2001 17:00:42 +0100 From: Brian Candler To: Sam Cc: freebsd-stable@freebsd.org Subject: Re: fetchmail broke Message-ID: <20010413170042.A7785@linnet.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > fetchmail: SMTP> MAIL FROM: SIZE=6720 > fetchmail: SMTP< 451 4.1.8 ... Domain of sender address opirpet@mailtimeonline.com does not resolve There is your error. Try this to confirm it: # nslookup -q=mx mailtimeonline.com. # nslookup -q=a mailtimeonline.com. It doesn't resolve for me either. Looks like both their authoritative nameservers are broken. Tell them to fix their servers, and also read RFC2182 (since they have them both on the same network). You can configure sendmail to accept mail from broken domains if you wish; I can't remember how to do so off-hand, since I stopped using sendmail a long time ago. Regards, Brian. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 9: 1:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lerami.lerctr.org (lerami.lerctr.org [207.158.72.11]) by hub.freebsd.org (Postfix) with ESMTP id BD45937B424 for ; Fri, 13 Apr 2001 09:01:22 -0700 (PDT) (envelope-from ler@lerctr.org) Received: from ler-freebie.iadfw.net (ler-freebie.iadfw.net [206.66.13.221]) by lerami.lerctr.org (8.12.0.Beta7/8.12.0.Beta7/20010318/$Revision: 1.21 $) with SMTP id f3DG1BHh006157; Fri, 13 Apr 2001 11:01:12 -0500 (CDT) (envelope-from ler@lerctr.org) From: Larry Rosenman Date: Fri, 13 Apr 2001 16:01:12 GMT Message-ID: <20010413.16011200@ler-freebie.iadfw.net> Subject: Re: multiple CPUTYPEs? To: unsafe at any speed Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <3AD6A7A3.4060002@jacinto.yi.org> References: <3AD6A7A3.4060002@jacinto.yi.org> X-Mailer: Mozilla/3.0 (compatible; StarOffice/5.2; Linux) X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was that perpetrator. The consensus was that the FreeBSD team needs t= o=20 build some infrastructure, and that wouldn't happen for 4.3.=20 It was promised to be done post-4.3.=20 For now, compile the host world with the lowest processor when you need = to do this.=20 Larry Rosenman --=20 Larry Rosenman http://www.lerctr.org/~ler/ Phone: +1 972 414 9812 E-Mail: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 US >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 4/13/01, 2:15:47 AM, unsafe at any speed wrote= =20 regarding multiple CPUTYPEs?: > Greetings folks, > Is it possible to have multiple /usr/obj directories compiled with > different CPUTYPEs? A month or so ago I remember someone was having > trouble installing onto a 486 from a system whose userland was compile= d > with i686 but whose /usr/obj was compiled with i486. Installworld was > picking up a library from /usr/lib instead of /usr/obj/..../lib. > Anyway, I didn't see if that ever got resolved. I guess I could just t= ry > it, but I figured I'd ask first. > thanks, > Eric Hedstrom > erich@ucsd.edu > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 9: 7:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tsing.ita.tip.net (tsing.ita.tip.net [194.20.0.21]) by hub.freebsd.org (Postfix) with ESMTP id 8696337B496 for ; Fri, 13 Apr 2001 09:07:10 -0700 (PDT) (envelope-from olgeni@uli.it) Received: from dev1.localdomain.net ([194.244.229.102]) by tsing.ita.tip.net (AurorA/BorealE) with ESMTP id RAA07377; Fri, 13 Apr 2001 17:54:24 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by dev1.localdomain.net (8.11.3/8.11.3) with ESMTP id f3DG6ve47911; Fri, 13 Apr 2001 18:06:57 +0200 (CEST) (envelope-from olgeni@uli.it) Date: Fri, 13 Apr 2001 18:06:57 +0200 (CEST) From: Jimmy Olgeni X-X-Sender: To: Brian Candler Cc: Sam , Subject: Re: fetchmail broke In-Reply-To: <20010413170042.A7785@linnet.org> Message-ID: <20010413180536.K47902-100000@dev1.localdomain.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 13 Apr 2001, Brian Candler wrote: > You can configure sendmail to accept mail from broken domains if you wish; I > can't remember how to do so off-hand, since I stopped using sendmail a long > time ago. I added "FEATURE(accept_unresolvable_domains)dnl" to my .mc file and sendmail stopped complaining - if I remember correctly :) -- jimmy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 9:28:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from internal.mail.telinco.net (internal.mail.telinco.net [212.1.128.4]) by hub.freebsd.org (Postfix) with ESMTP id 2FD9237B422 for ; Fri, 13 Apr 2001 09:28:53 -0700 (PDT) (envelope-from b.candler@pobox.com) Received: from ppp-dp1-mk-66.access.uk.worldonline.com ([212.74.113.66] helo=bloodhound.uk.worldonline.com) by internal.mail.telinco.net with esmtp (Exim 3.02 #1) id 14o6RI-000BKE-00; Fri, 13 Apr 2001 17:28:52 +0100 Received: from brian by bloodhound.uk.worldonline.com with local (Exim 3.22 #1) id 14o6RH-00023C-00; Fri, 13 Apr 2001 17:28:51 +0100 Date: Fri, 13 Apr 2001 17:28:51 +0100 From: Brian Candler To: Brad Laue Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 4.3RC out of buffer space in network operations Message-ID: <20010413172851.B7785@linnet.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > sendto in send_tcp_raw: sendto(3, packet, 40, 0, 64.228.82.35, 16) => No > buffer space available > Sleeping 15 seconds then retrying > > This occurs mainly when nmap -sS is called I get that too with FreeBSD 4.2-STABLE, when trying to run nmap over a wi0 (wavelan) interface. I presume it just means that nmap is sending so many packets that the driver can't get them out onto the air quickly enough... my solution has been to plug into fxp0 instead when using nmap :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 9:36: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from grizzly.carrier.kiev.ua (grizzly.carrier.kiev.ua [193.193.193.138]) by hub.freebsd.org (Postfix) with ESMTP id 19D5237B422; Fri, 13 Apr 2001 09:35:49 -0700 (PDT) (envelope-from netch@grizzly.carrier.kiev.ua) Received: (from netch@localhost) by grizzly.carrier.kiev.ua (8.11.3/8.11.0) id f3DGZdP00629; Fri, 13 Apr 2001 19:35:39 +0300 (EEST) (envelope-from netch) Date: Fri, 13 Apr 2001 19:35:39 +0300 From: Valentin Nechayev To: freebsd-stable@freebsd.org, obrien@freebsd.org, phk@freebsd.org Cc: nicholas harteau Subject: fresh 4.3-RC: "microuptime went backwards", console lockup Message-ID: <20010413193539.A428@netch.kiev.ua> Reply-To: netch@netch.kiev.ua References: <20010411192854.A570@netch.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010411192854.A570@netch.kiev.ua>; from netch@netch.kiev.ua on Wed, Apr 11, 2001 at 07:28:54PM +0300 X-42: On Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (CC to obrien as author of commit in question, phk as timecounters author) Below is quote of my original letter with problem description. I found source of the problem; it is following commit: === cut === Revision 1.149.2.2 / (download) - annotate - [select for diffs], Mon Mar 5 13:09:01 2001 UTC (5 weeks, 4 days ago) by obrien Branch: RELENG_4 Changes since 1.149.2.1: +2 -2 lines Diff to previous 1.149.2.1 (colored) to branchpoint 1.149 (colored) next main 1.150 (colored) MFC: Convert all users of fldoff() to offsetof(). fldoff() is bad because it only takes a struct tag which makes it impossible to use unions, typedefs etc. Define __offsetof() in Define offsetof() in terms of __offsetof() in and === end cut === which contains such change (which is not described in commit description!) === cut === --- src/sys/i386/isa/clock.c 2000/08/03 00:09:29 1.149.2.1 +++ src/sys/i386/isa/clock.c 2001/03/05 13:09:01 1.149.2.2 [...skipped by netch...] @@ -191,7 +191,7 @@ SYSCTL_OPAQUE(_debug, OID_AUTO, tsc_time static struct timecounter i8254_timecounter = { i8254_get_timecount, /* get_timecount */ 0, /* no poll_pps */ - ~0u, /* counter_mask */ + 0x1ffff, /* counter_mask */ 0, /* frequency */ "i8254" /* name */ }; === end cut === and contains no more, hence commit description is _totally bogus_. When I revert only this change with all another source newer than previous working version (date=2001.03.05.00.00.00), system begins to work correctly. 2obrien@: can you please revert invalid patch? (And commit really what you wanted) My previous letter is fully quoted here to provide context for considering. Additional info: with this problem, system timer stops _totally_. Wed, Apr 11, 2001 at 19:28:54, netch wrote about "fresh 4.3-RC: "microuptime went backwards", console lockup": > Date: Wed, 11 Apr 2001 19:28:54 +0300 > From: Valentin Nechayev > To: freebsd-stable@freebsd.org > Subject: fresh 4.3-RC: "microuptime went backwards", console lockup > > Today, 4.3-RC (RELENG_4, date=2001.04.11.00.00.00) was built and, when > new system started: > 1) during boot and even before /sbin/init started, "microuptime went backwards" > occured too many times. > 2) after startx, syscons switched to ttyv0 and stayed here; after > mutual swithing to ttyvb, console locked up totally. > No problems with previous system (RELENG_4, date=2001.03.05.00.00.00) > were seen. Xwindow is 3.3.6 from latest port. > > Messages, messages diff and kernel config attached. What another information > should I provide? > > /var/log/messages during bad kernel: > > ==={{{ > Apr 11 18:41:38 grizzly /kernel: Copyright (c) 1992-2001 The FreeBSD Project. > Apr 11 18:41:38 grizzly /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > Apr 11 18:41:38 grizzly /kernel: The Regents of the University of California. All rights reserved. > Apr 11 18:41:38 grizzly /kernel: FreeBSD 4.3-RC #0: Wed Apr 11 18:29:42 EEST 2001 > Apr 11 18:41:38 grizzly /kernel: root@grizzly.carrier.kiev.ua:/var/obj/var/src/sys/compile/griz > Apr 11 18:41:38 grizzly /kernel: Timecounter "i8254" frequency 1193182 Hz > Apr 11 18:41:38 grizzly /kernel: CPU: Pentium II/Pentium II Xeon/Celeron (300.68-MHz 686-class CPU) > Apr 11 18:41:38 grizzly /kernel: Origin = "GenuineIntel" Id = 0x660 Stepping = 0 > Apr 11 18:41:38 grizzly /kernel: Features=0x183f9ff > Apr 11 18:41:38 grizzly /kernel: real memory = 134217728 (131072K bytes) > Apr 11 18:41:38 grizzly /kernel: avail memory = 127016960 (124040K bytes) > Apr 11 18:41:38 grizzly /kernel: Preloaded elf kernel "kernel" at 0xc0357000. > Apr 11 18:41:38 grizzly /kernel: VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc02f81a2 (1000022) > Apr 11 18:41:38 grizzly /kernel: VESA: ATI MACH64 > Apr 11 18:41:38 grizzly /kernel: Pentium Pro MTRR support enabled > Apr 11 18:41:38 grizzly /kernel: apm0: on motherboard > Apr 11 18:41:38 grizzly /kernel: apm: found APM BIOS v1.2, connected at v1.2 > Apr 11 18:41:38 grizzly /kernel: npx0: on motherboard > Apr 11 18:41:38 grizzly /kernel: npx0: INT 16 interface > Apr 11 18:41:38 grizzly /kernel: pcib0: on motherboard > Apr 11 18:41:38 grizzly /kernel: pci0: on pcib0 > Apr 11 18:41:38 grizzly /kernel: pcib1: at device 1.0 on pci0 > Apr 11 18:41:38 grizzly /kernel: pci1: on pcib1 > Apr 11 18:41:38 grizzly /kernel: pci1: at 0.0 irq 15 > Apr 11 18:41:38 grizzly /kernel: isab0: at device 7.0 on pci0 > Apr 11 18:41:38 grizzly /kernel: isa0: on isab0 > Apr 11 18:41:38 grizzly /kernel: pci0: at 7.1 > Apr 11 18:41:38 grizzly /kernel: pci0: at 7.2 > Apr 11 18:41:38 grizzly /kernel: chip1: port 0x5000-0x500f at device 7.3 on pci0 > Apr 11 18:41:38 grizzly /kernel: fxp0: port 0xe400-0xe41f mem 0xea000000-0xea0fffff,0xea101000-0xea101fff irq 11 at device 18.0 on pci0 > Apr 11 18:41:38 grizzly /kernel: fxp0: Ethernet address 00:90:27:2d:41:d0 > Apr 11 18:41:38 grizzly /kernel: ahc0: port 0xe800-0xe8ff mem 0xea100000-0xea100fff irq 10 at device 19.0 on pci0 > Apr 11 18:41:38 grizzly /kernel: aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs > Apr 11 18:41:38 grizzly /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > Apr 11 18:41:38 grizzly /kernel: fdc0: FIFO enabled, 8 bytes threshold > Apr 11 18:41:38 grizzly /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > Apr 11 18:41:38 grizzly /kernel: atkbdc0: at port 0x60,0x64 on isa0 > Apr 11 18:41:38 grizzly /kernel: atkbd0: flags 0x1 irq 1 on atkbdc0 > Apr 11 18:41:38 grizzly /kernel: kbd0 at atkbd0 > Apr 11 18:41:38 grizzly /kernel: psm0: irq 12 on atkbdc0 > Apr 11 18:41:38 grizzly /kernel: psm0: model Generic PS/2 mouse, device ID 0 > Apr 11 18:41:38 grizzly /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Apr 11 18:41:38 grizzly /kernel: sc0: at flags 0x100 on isa0 > Apr 11 18:41:38 grizzly /kernel: sc0: VGA <16 virtual consoles, flags=0x300> > Apr 11 18:41:38 grizzly /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > Apr 11 18:41:38 grizzly /kernel: sio0: type 16550A > Apr 11 18:41:38 grizzly /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 > Apr 11 18:41:38 grizzly /kernel: sio1: type 16550A > Apr 11 18:41:38 grizzly /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 > Apr 11 18:41:38 grizzly /kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > Apr 11 18:41:38 grizzly /kernel: ppc0: FIFO with 16/16/16 bytes threshold > Apr 11 18:41:38 grizzly /kernel: plip0: on ppbus0 > Apr 11 18:41:38 grizzly /kernel: lpt0: on ppbus0 > Apr 11 18:41:38 grizzly /kernel: lpt0: Interrupt-driven port > Apr 11 18:41:38 grizzly /kernel: ppi0: on ppbus0 > Apr 11 18:41:38 grizzly /kernel: sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,3 on isa0 > Apr 11 18:41:38 grizzly /kernel: pcm0: on sbc0 > Apr 11 18:41:38 grizzly /kernel: IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to accept, unlimited logging > Apr 11 18:41:38 grizzly /kernel: Waiting 3 seconds for SCSI devices to settle > Apr 11 18:41:38 grizzly /kernel: Mounting root from ufs:/dev/da0s1a > Apr 11 18:41:38 grizzly /kernel: da1 at ahc0 bus 0 target 2 lun 0 > Apr 11 18:41:38 grizzly /kernel: da1: Fixed Direct Access SCSI-2 device > Apr 11 18:41:38 grizzly /kernel: da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) > Apr 11 18:41:38 grizzly /kernel: da1: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) > Apr 11 18:41:38 grizzly /kernel: da0 at ahc0 bus 0 target 0 lun 0 > Apr 11 18:41:38 grizzly /kernel: da0: Fixed Direct Access SCSI-2 device > Apr 11 18:41:38 grizzly /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled > Apr 11 18:41:38 grizzly /kernel: da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843816 -> 7.734809) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843816 -> 7.737171) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843573 -> 7.734732) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843573 -> 7.735340) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843573 -> 7.736912) > Apr 11 18:41:38 grizzly /kernel: cd0 at ahc0 bus 0 target 1 lun 0 > Apr 11 18:41:38 grizzly /kernel: cd0: Removable CD-ROM SCSI-2 device > Apr 11 18:41:38 grizzly /kernel: cd0: 10.000MB/s transfers (10.000MHz, offset 8) > Apr 11 18:41:38 grizzly /kernel: cd0: cd present [327338 x 2048 byte records] > Apr 11 18:41:38 grizzly named[177]: starting (/etc/namedb/named.conf). named 8.2.3-REL Wed Apr 11 16:59:40 EEST 2001 root@grizzly.carrier.kiev.ua:/var/obj/var/src/usr.sbin/named > Apr 11 18:41:38 grizzly named[177]: limit files set to fdlimit (1024) > Apr 11 18:41:38 grizzly named[178]: Ready to answer queries. > Apr 11 18:41:38 grizzly ntpd[180]: ntpd 4.0.99b Wed Apr 11 16:58:45 EEST 2001 (1) > Apr 11 18:41:38 grizzly ntpd[180]: using kernel phase-lock loop 2040 > Apr 11 18:41:38 grizzly ntpd[180]: getnetnum: "news.demos.su" invalid host number, line ignored > Apr 11 18:41:38 grizzly ntpd[180]: getnetnum: "news1.demos.su" invalid host number, line ignored > Apr 11 18:41:38 grizzly ntpd[180]: getnetnum: "news.gamma.ru" invalid host number, line ignored > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.834984 -> 7.737884) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842559 -> 7.735504) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843816 -> 7.738378) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839712 -> 7.734986) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839748 -> 7.743734) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.736175) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.739450) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.750258) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.751613) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.764301) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.764883) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.775410) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.776000) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.780731) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.787880) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.788925) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.791228) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.811999 -> 7.792100) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.742846) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.745269) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.746962) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.748818) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.749914) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.751635) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.753202) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839740 -> 7.756961) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.739800) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.740682) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.751453) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.752134) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.753513) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.754646) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.755632) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.757180) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.761039) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.765178) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.837073 -> 7.766163) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843178 -> 7.734621) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843178 -> 7.735361) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843178 -> 7.737016) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843178 -> 7.737564) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.830187 -> 7.734668) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.830187 -> 7.749899) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.838573 -> 7.734923) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843469 -> 7.734611) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.838522 -> 7.738094) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.838522 -> 7.745038) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.844055 -> 7.734420) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.735466) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.740883) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.755061) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.766780) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.783736) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.795306) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.810152) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842481 -> 7.826392) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843630 -> 7.735223) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.831660 -> 7.737727) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.831660 -> 7.759594) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842772 -> 7.734324) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.805040 -> 7.735190) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.805040 -> 7.735336) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.805040 -> 7.771539) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.843616 -> 7.734416) > Apr 11 18:41:38 grizzly login: ROOT LOGIN (root) ON ttyv1 > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.774619 -> 7.740860) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839139 -> 7.735976) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839139 -> 7.736433) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839139 -> 7.736580) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839139 -> 7.736791) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.839139 -> 7.736964) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.820332 -> 7.744583) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.820332 -> 7.744793) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.820332 -> 7.750961) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.842030 -> 7.734805) > Apr 11 18:41:38 grizzly /kernel: microuptime() went backwards (7.831764 -> 7.737653) > ===}}} > > Different lines between bad kernel messages('-') and good old kernel > messages('+'): > > -avail memory = 127016960 (124040K bytes) > +avail memory = 127021056 (124044K bytes) > > -VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc02f81a2 (1000022) > +VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc02f7362 (1000022) > > Kernel config (did not changed): > > ==={{{ > machine i386 > #cpu I386_CPU > #cpu I486_CPU > #cpu I586_CPU > cpu I686_CPU > ident griz > maxusers 64 > options MSGBUF_SIZE=81920 > #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols > #options MATH_EMULATE #Support for x87 emulation > options INET #InterNETworking > options IPFIREWALL #firewall > options IPFIREWALL_VERBOSE #print information about > options IPFIREWALL_DEFAULT_TO_ACCEPT > options FFS #Berkeley Fast Filesystem > options FFS_ROOT #FFS usable as root device [keep this!] > options SOFTUPDATES #Enable FFS soft updates support > options NFS #Network Filesystem > options MSDOSFS #MSDOS Filesystem > options CD9660 #ISO 9660 Filesystem > options PROCFS #Process filesystem > options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] > options SCSI_DELAY=3000 #Delay (in ms) before probing SCSI > options INCLUDE_CONFIG_FILE > options USERCONFIG #boot -c editor > options VISUAL_USERCONFIG #visual boot -c editor > options KTRACE #ktrace(1) support > options SYSVSHM #SYSV-style shared memory > options SYSVMSG #SYSV-style message queues > options SYSVSEM #SYSV-style semaphores > options P1003_1B #Posix P1003_1B real-time extensions > options _KPOSIX_PRIORITY_SCHEDULING > options ICMP_BANDLIM #Rate limit bad replies > options KBD_INSTALL_CDEV # install a CDEV entry in /dev > options VESA > options EXT2FS > options USER_LDT > device isa > device pci > # Floppy drives > device fdc0 at isa? port IO_FD1 irq 6 drq 2 > device fd0 at fdc0 drive 0 > # SCSI peripherals > device ahc # AHA2940 and onboard AIC7xxx devices > device scbus # SCSI bus (required) > device da # Direct Access (disks) > device cd # CD > device pass # Passthrough device (direct SCSI access) > # atkbdc0 controls both the keyboard and the PS/2 mouse > device atkbdc0 at isa? port IO_KBD > device atkbd0 at atkbdc? irq 1 flags 0x1 > device psm0 at atkbdc? irq 12 > device vga0 at isa? > # splash screen/screen saver > pseudo-device splash > # syscons is the default console driver, resembling an SCO console > device sc0 at isa? flags 0x100 > options SC_HISTORY_SIZE=1200 > options SC_MOUSE_CHAR=0x03 > # 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? flags 0x20 # Advanced Power Management > # Serial (COM) ports > device sio0 at isa? port IO_COM1 flags 0x10 irq 4 > device sio1 at isa? port IO_COM2 irq 3 > # Parallel port > device ppc0 at isa? irq 7 > device ppbus # Parallel port bus (required) > device lpt # Printer > device plip # TCP/IP over parallel > device ppi # Parallel port interface device > #device vpo # Requires scbus and da > # PCI Ethernet NICs. > device fxp # Intel EtherExpress PRO/100B (82557, 82558) > ## sound > device pcm > device sbc > # 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 64 # Pseudo-ttys (telnet etc) > pseudo-device vn 3 > pseudo-device bpf 3 > pseudo-device speaker > > options NETGRAPH #netgraph(4) system > options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN > options TCP_RESTRICT_RST #restrict emission of TCP RST > options ICMP_BANDLIM > options QUOTA #enable disk quotas > options NTIMECOUNTER=20 > options VESA > ===}}} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 9:37:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 5B75837B43E for ; Fri, 13 Apr 2001 09:37:22 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) Received: (from jkh@localhost) by winston.osd.bsdi.com (8.11.3/8.11.2) id f3DGbPt04946 for stable@freebsd.org; Fri, 13 Apr 2001 09:37:25 -0700 (PDT) (envelope-from jkh) Date: Fri, 13 Apr 2001 09:37:25 -0700 (PDT) From: Jordan Hubbard Message-Id: <200104131637.f3DGbPt04946@winston.osd.bsdi.com> To: stable@freebsd.org Subject: Anyone interested in the SVR4 compat module anymore? Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm just now noticing (I so rarely turn it on) that the svr4 ABI module is broken - you get "link_elf: symbol svr4_stream_get undefined" when you try to load it. Unless someone wants to fix it before the 19th or so, I'll remove it as a sysinstall option at the last minute so people new to 4.3 don't go "Huh?" - they'll have to work a little harder to confuse themselves. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 9:42:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ece.cmu.edu (ECE.CMU.EDU [128.2.236.200]) by hub.freebsd.org (Postfix) with ESMTP id 6E55337B50C for ; Fri, 13 Apr 2001 09:42:22 -0700 (PDT) (envelope-from allbery@ece.cmu.edu) Received: from tully (allbery@TULLY.ECE.CMU.EDU [128.2.136.132]) (authenticated) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id f3DGfkr12950; Fri, 13 Apr 2001 12:41:46 -0400 (EDT) Date: Fri, 13 Apr 2001 12:41:45 -0400 From: "Brandon S. Allbery KF8NH" To: Jordan Hubbard , stable@FreeBSD.ORG Subject: Re: Anyone interested in the SVR4 compat module anymore? Message-ID: <32600000.987180105@tully> In-Reply-To: <200104131637.f3DGbPt04946@winston.osd.bsdi.com> X-Mailer: Mulberry/2.0.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, April 13, 2001 09:37:25 AM -0700, Jordan Hubbard wrote: +----- | I'm just now noticing (I so rarely turn it on) that the svr4 ABI | module is broken - you get "link_elf: symbol svr4_stream_get undefined" | when you try to load it. +--->8 I believe you have to load streams.ko first, and then it works. -- brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering KF8NH carnegie mellon university ["better check the oblivious first" -ke6sls] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 9:49:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tomts5-srv.bellnexxia.net (tomts5.bellnexxia.net [209.226.175.25]) by hub.freebsd.org (Postfix) with ESMTP id 673D137B422 for ; Fri, 13 Apr 2001 09:49:55 -0700 (PDT) (envelope-from blaue@sympatico.ca) Received: from sympatico.ca ([64.228.82.35]) by tomts5-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010413164954.KISW17644.tomts5-srv.bellnexxia.net@sympatico.ca>; Fri, 13 Apr 2001 12:49:54 -0400 Message-ID: <3AD72E49.1741E6D0@sympatico.ca> Date: Fri, 13 Apr 2001 12:50:17 -0400 From: Brad Laue X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: Brian Candler Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 4.3RC out of buffer space in network operations References: <20010413172851.B7785@linnet.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Candler wrote: > > sendto in send_tcp_raw: sendto(3, packet, 40, 0, 64.228.82.35, 16) => No > > buffer space available > > Sleeping 15 seconds then retrying > > > > This occurs mainly when nmap -sS is called > > I get that too with FreeBSD 4.2-STABLE, when trying to run nmap over a wi0 > (wavelan) interface. > > I presume it just means that nmap is sending so many packets that the driver > can't get them out onto the air quickly enough... my solution has been to > plug into fxp0 instead when using nmap :-) Good thing you have a way out of it - unfortunately my PPPoE connection tunnels through ed0, so it's my only public route to the internet :( Hoping this gets noticed before -RELEASE Brad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 9:54:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from veldy.net (w028.z064001117.msp-mn.dsl.cnc.net [64.1.117.28]) by hub.freebsd.org (Postfix) with ESMTP id C427F37B50C for ; Fri, 13 Apr 2001 09:54:42 -0700 (PDT) (envelope-from veldy@veldy.net) Received: from HP2500B (fuggle.veldy.net [64.1.117.28]) by veldy.net (Postfix) with SMTP id 61D1FBA4E for ; Fri, 13 Apr 2001 10:52:05 -0500 (CDT) Message-ID: <000701c0c431$09a2ce00$3028680a@tgt.com> From: "Thomas T. Veldhouse" To: Subject: natd[232]: failed to write packet back (Permission denied) Date: Fri, 13 Apr 2001 10:47:25 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 1 X-MSMail-Priority: High X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Apr 13 10:47:37 fuggle natd[232]: failed to write packet back (Permission denied) Apr 13 10:47:46 fuggle last message repeated 4 times Apr 13 10:47:47 fuggle su: veldy to root on /dev/ttyp0 Apr 13 10:47:58 fuggle natd[232]: failed to write packet back (Permission denied) Apr 13 10:48:31 fuggle last message repeated 3 times Can anybody explain what causes this? I have look through archive after archive and have found many many reports of this problem, but no solution. The closest I have come is a message that says to check the firewall rules to see what is blocking packets passed back from natd. This cannot be it because I have added rules after the natd divert to open everything and this still occurs. Please help -- this fills logs and is a nuisance -- it has been a problem ever since at least 4.1.1. Tom Veldhouse veldy@veldy.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 9:57:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id B500E37B423 for ; Fri, 13 Apr 2001 09:57:46 -0700 (PDT) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.11.3) with SMTP id f3DGtbp01862; Fri, 13 Apr 2001 12:55:37 -0400 (EDT) (envelope-from matt@gsicomp.on.ca) Message-ID: <003f01c0c43a$1cf242c0$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Robin P. Blanchard" Cc: References: <3AD5A1F9.7133FC74@gactr.uga.edu> <017001c0c425$b60c3020$1200a8c0@gsicomp.on.ca> <3AD71263.6E420055@gactr.uga.edu> <20010413181239.A33404@icon.icon.bg> Subject: Re: install world on 486] Date: Fri, 13 Apr 2001 12:52:23 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 13, 2001 at 10:51:15AM -0400, Robin P. Blanchard wrote: >> the reason CPUTYPE was commented out was because i'd gotten the >> same error while having CPUTYPE set and seemed to remember someone >> on the list saying something about CPUTYPE=i486 giving him the >> same errors for 'strip'. >> >> so CPUTYPE or not CPUTYPE, i get the same error. >Without CPUTYPE it's i386 isn't it? I have /usr/obj on a CD, it was built >on a i686 machine (actualy a buggy Cyrix) without the CPUTYPE option in >make.conf. Later I have installed this on a i586 and on old Compaq with i486 >processor -- didn't have any problems... My mistake, yes, with no CPUTYPE it's i386. However, if hardware was the problem, I doubt you'd get signal 4 - you'd be getting signal 10 or 11 (bus error or segmentation fault), commonly triggered by bad memory. Between builds are you removing /usr/obj? If not, some stuff won't get rebuilt and thus you will end up with some binaries that are compiled for i386 (no CPUTYPE) and some for i686 (if you did a build with CPUTYPE=i686 at some point.) -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 9:59:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id 76D1A37B50C for ; Fri, 13 Apr 2001 09:59:39 -0700 (PDT) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.11.3) with SMTP id f3DGvPp01871; Fri, 13 Apr 2001 12:57:26 -0400 (EDT) (envelope-from matt@gsicomp.on.ca) Message-ID: <004401c0c43a$5d634cf0$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Jordan Hubbard" , References: <200104131637.f3DGbPt04946@winston.osd.bsdi.com> Subject: Re: Anyone interested in the SVR4 compat module anymore? Date: Fri, 13 Apr 2001 12:54:11 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm just now noticing (I so rarely turn it on) that the svr4 ABI > module is broken - you get "link_elf: symbol svr4_stream_get undefined" > when you try to load it. The SVR4 module isn't the best at ensuring that the dependent streams.ko module is loaded first. If you use the svr4.sh script to enable it, then all shoudl be well. If you're just doing a 'kldload svr4' then you need to make sure you do a 'kldload streams' first, to prevent the error that you are reporting. I'm cvsup'ing as we speak, but I won't be able to look at it until Monday, being Easter weekend and all. Mark Newton (the author of the svr4 modules) might beat me to this. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 10: 8:28 2001 Delivered-To: freebsd-stable@freebsd.org Received: from veldy.net (w028.z064001117.msp-mn.dsl.cnc.net [64.1.117.28]) by hub.freebsd.org (Postfix) with ESMTP id 86ED437B440 for ; Fri, 13 Apr 2001 10:08:25 -0700 (PDT) (envelope-from veldy@veldy.net) Received: from HP2500B (fuggle.veldy.net [64.1.117.28]) by veldy.net (Postfix) with SMTP id 4AFBDBA4E for ; Fri, 13 Apr 2001 12:07:35 -0500 (CDT) Message-ID: <002b01c0c43b$95b2ee20$3028680a@tgt.com> From: "Thomas T. Veldhouse" To: References: <000701c0c431$09a2ce00$3028680a@tgt.com> Subject: Re: natd[232]: failed to write packet back (Permission denied) Date: Fri, 13 Apr 2001 12:02:47 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 1 X-MSMail-Priority: High X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As an addendum -- I get these messages even when there is NO activity on the LAN -- so natd is not even being used by any client. Tom Veldhouse veldy@veldy.net ----- Original Message ----- From: "Thomas T. Veldhouse" To: Sent: Friday, April 13, 2001 10:47 AM Subject: natd[232]: failed to write packet back (Permission denied) > Apr 13 10:47:37 fuggle natd[232]: failed to write packet back (Permission > denied) > Apr 13 10:47:46 fuggle last message repeated 4 times > Apr 13 10:47:47 fuggle su: veldy to root on /dev/ttyp0 > Apr 13 10:47:58 fuggle natd[232]: failed to write packet back (Permission > denied) > Apr 13 10:48:31 fuggle last message repeated 3 times > > > Can anybody explain what causes this? I have look through archive after > archive and have found many many reports of this problem, but no solution. > The closest I have come is a message that says to check the firewall rules > to see what is blocking packets passed back from natd. This cannot be it > because I have added rules after the natd divert to open everything and this > still occurs. > > Please help -- this fills logs and is a nuisance -- it has been a problem > ever since at least 4.1.1. > > Tom Veldhouse > veldy@veldy.net > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 10:33:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dns3.solo.net (dns3.solo.net [64.23.2.19]) by hub.freebsd.org (Postfix) with ESMTP id AC8BD37B509 for ; Fri, 13 Apr 2001 10:33:34 -0700 (PDT) (envelope-from dak@solo.net) Received: from solo.net (vip0 [64.23.2.19]) by dns3.solo.net (8.11.3/8.11.3) with SMTP id f3DHXZj18207; Fri, 13 Apr 2001 13:33:36 -0400 (EDT) (envelope-from dak@solo.net) Received: from corp.namesafe.com ([209.141.226.130]) (proxying for 10.0.0.10) (SquirrelMail authenticated user dak) by www.solo.net with HTTP; Fri, 13 Apr 2001 13:33:36 -0400 (EDT) Message-ID: <4383.209.141.226.130.987183216.squirrel@www.solo.net> Date: Fri, 13 Apr 2001 13:33:36 -0400 (EDT) Subject: ports "make index" fails From: "David A. Koran" To: In-Reply-To: <003f01c0c43a$1cf242c0$1200a8c0@gsicomp.on.ca> References: <003f01c0c43a$1cf242c0$1200a8c0@gsicomp.on.ca> Cc: Reply-To: dak@solo.net X-Mailer: SquirrelMail (version 1.1.0 [cvs]) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I always like to do a fresh "make index" after cvsupping the ports tree, and came across this issue this morning. Dunno how many other rely on the INDEX for tracking port revs easily, but if this woudl get fixed, that woudl be grand. ERROR MESSAGES: machine# make index Generating INDEX - please wait.."/usr/ports/Mk/bsd.sites.mk", line 63: Unassociated shell command "ftp://ftp.sunet.se/pub/X11/GNOME/%SUBDIR%/ ftp://ftp.dit.upm.es/linux/gnome/%SUBDIR%/ ftp://ftp.tr.gnome.org/pub/GNOME/%SUBDIR%/ ftp://ftp.no.gnome.org/pub/GNOME/%SUBDIR%/ ftp://ftp.dataplus.se/pub/linux/gnome/%SUBDIR%/ ftp://ftp.mirror.ac.uk/sites/ftp.gnome.org/pub/GNOME/%SUBDIR%/ ${MASTER_SITE_RINGSERVER:S,%SUBDIR%,X/gnome/&,}" make: fatal errors encountered -- cannot continue Done. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 10:35:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gactr.uga.edu (mail.gactr.uga.edu [128.192.37.21]) by hub.freebsd.org (Postfix) with SMTP id 88AF537B496 for ; Fri, 13 Apr 2001 10:35:06 -0700 (PDT) (envelope-from Robin_Blanchard@gactr.uga.edu) Received: (qmail 4350 invoked from network); 13 Apr 2001 17:35:06 -0000 Received: from qat.noc.nat (HELO gactr.uga.edu) ([10.10.100.125]) (envelope-sender ) by mail.servers.nat (qmail-ldap-1.03) with SMTP for ; 13 Apr 2001 17:35:06 -0000 Message-ID: <3AD73898.3AC838@gactr.uga.edu> Date: Fri, 13 Apr 2001 13:34:16 -0400 From: "Robin P. Blanchard" X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Emmerton Cc: freebsd-stable@FreeBSD.ORG Subject: Re: install world on 486] References: <3AD5A1F9.7133FC74@gactr.uga.edu> <017001c0c425$b60c3020$1200a8c0@gsicomp.on.ca> <3AD71263.6E420055@gactr.uga.edu> <20010413181239.A33404@icon.icon.bg> <003f01c0c43a$1cf242c0$1200a8c0@gsicomp.on.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ok. here's what i've done: cvs'd (src-all tag=RELENG_4) a few hours ago on my 686 box. did a "make MAKEOBJDIRPREFIX=/usr/obj-486 clean buildworld" on that box with this make.conf: FETCH_BEFORE_ARGS=-p USA_RESIDENT=yes MAKE_IDEA=YES CPUTYPE=i486 CFLAGS=-O -pipe COPTFLAGS=-O -pipe CXXFLAGS+= -fmemoize-lookups -fsave-memoized on my 486 i did: mount 686:/usr/src /usr/src mount 686:/usr/obj-486 /usr/obj i then did a "make installworld" on the 486 with this (identical) make.conf: FETCH_BEFORE_ARGS=-p USA_RESIDENT=yes MAKE_IDEA=YES CPUTYPE=i486 CFLAGS=-O -pipe COPTFLAGS=-O -pipe CXXFLAGS+= -fmemoize-lookups -fsave-memoized and i get the same error at the same point: pid 28217 (strip), uid 0: exited on signal 4 (core dumped) *** Error code 70 Stop in /usr/src/lib/libcom_err > >> so CPUTYPE or not CPUTYPE, i get the same error. > > >Without CPUTYPE it's i386 isn't it? I have /usr/obj on a CD, it was built > >on a i686 machine (actualy a buggy Cyrix) without the CPUTYPE option in > >make.conf. Later I have installed this on a i586 and on old Compaq with > i486 > >processor -- didn't have any problems... > > My mistake, yes, with no CPUTYPE it's i386. However, if hardware was the > problem, I doubt you'd get signal 4 - you'd be getting signal 10 or 11 (bus > error or segmentation fault), commonly triggered by bad memory. > > Between builds are you removing /usr/obj? If not, some stuff won't get > rebuilt and thus you will end up with some binaries that are compiled for > i386 (no CPUTYPE) and some for i686 (if you did a build with CPUTYPE=i686 at > some point.) > > -- > Matt Emmerton -- ------------------------------------ Robin P. Blanchard IT Program Specialist Georgia Center for Continuing Ed. fon: 706.542.2404 fax: 706.542.6546 email: Robin_Blanchard@gactr.uga.edu ------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 10:48:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lerami.lerctr.org (lerami.lerctr.org [207.158.72.11]) by hub.freebsd.org (Postfix) with ESMTP id C321837B505 for ; Fri, 13 Apr 2001 10:48:46 -0700 (PDT) (envelope-from ler@lerctr.org) Received: from ler-freebie.iadfw.net (ler-freebie.iadfw.net [206.66.13.221]) by lerami.lerctr.org (8.12.0.Beta7/8.12.0.Beta7/20010318/$Revision: 1.21 $) with SMTP id f3DHmiHh011663; Fri, 13 Apr 2001 12:48:45 -0500 (CDT) (envelope-from ler@lerctr.org) From: Larry Rosenman Date: Fri, 13 Apr 2001 17:48:44 GMT Message-ID: <20010413.17484400@ler-freebie.iadfw.net> Subject: Re: install world on 486] To: Robin "P. Blanchard" Cc: Matthew Emmerton , freebsd-stable@FreeBSD.ORG In-Reply-To: <3AD73898.3AC838@gactr.uga.edu> References: <3AD5A1F9.7133FC74@gactr.uga.edu> <017001c0c425$b60c3020$1200a8c0@gsicomp.on.ca> <3AD71263.6E420055@gactr.uga.edu> <20010413181239.A33404@icon.icon.bg> <003f01c0c43a$1cf242c0$1200a8c0@gsicomp.on.ca> <3AD73898.3AC838@gactr.uga.edu> X-Mailer: Mozilla/3.0 (compatible; StarOffice/5.2; Linux) X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You *MUST* for 4.3 use a HOST SYSTEM compiled for the LOWEST processor=20 you want to installworld to.=20 There is a few places (strip for one) that link in /usr/lib/libc.a and=20 NOT the one from /usr/obj/...=20 This is on the list of things to be fixed POST-4.3, but will be true in = 4.3-RELEASE.=20 This was discussed right after Kris Kennaway added the CPUTYPE support=20 for RELENG_4, and I ran into it. See the archives with a title of=20 CPUTYPE=3Di486 .=20 Larry Rosenman --=20 Larry Rosenman http://www.lerctr.org/~ler/ Phone: +1 972 414 9812 E-Mail: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 US >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 4/13/01, 12:34:16 PM, Robin "P." Blanchard=20 wrote regarding Re: install world on 486= ]: > ok. here's what i've done: > cvs'd (src-all tag=3DRELENG_4) a few hours ago on my 686 box. > did a "make MAKEOBJDIRPREFIX=3D/usr/obj-486 clean buildworld" > on that box with this make.conf: > FETCH_BEFORE_ARGS=3D-p > USA_RESIDENT=3Dyes > MAKE_IDEA=3DYES > CPUTYPE=3Di486 > CFLAGS=3D-O -pipe > COPTFLAGS=3D-O -pipe > CXXFLAGS+=3D -fmemoize-lookups -fsave-memoized > on my 486 i did: > mount 686:/usr/src /usr/src > mount 686:/usr/obj-486 /usr/obj > i then did a "make installworld" on the 486 with this (identical)=20 make.conf: > FETCH_BEFORE_ARGS=3D-p > USA_RESIDENT=3Dyes > MAKE_IDEA=3DYES > CPUTYPE=3Di486 > CFLAGS=3D-O -pipe > COPTFLAGS=3D-O -pipe > CXXFLAGS+=3D -fmemoize-lookups -fsave-memoized > and i get the same error at the same point: > pid 28217 (strip), uid 0: exited on signal 4 (core dumped) > *** Error code 70 > Stop in /usr/src/lib/libcom_err > > >> so CPUTYPE or not CPUTYPE, i get the same error. > > > > >Without CPUTYPE it's i386 isn't it? I have /usr/obj on a CD, it was= =20 built > > >on a i686 machine (actualy a buggy Cyrix) without the CPUTYPE optio= n in > > >make.conf. Later I have installed this on a i586 and on old Compaq = with > > i486 > > >processor -- didn't have any problems... > > > > My mistake, yes, with no CPUTYPE it's i386. However, if hardware wa= s the > > problem, I doubt you'd get signal 4 - you'd be getting signal 10 or = 11=20 (bus > > error or segmentation fault), commonly triggered by bad memory. > > > > Between builds are you removing /usr/obj? If not, some stuff won't = get > > rebuilt and thus you will end up with some binaries that are compile= d for > > i386 (no CPUTYPE) and some for i686 (if you did a build with CPUTYPE= =3Di686=20 at > > some point.) > > > > -- > > Matt Emmerton > -- > ------------------------------------ > Robin P. Blanchard > IT Program Specialist > Georgia Center for Continuing Ed. > fon: 706.542.2404 fax: 706.542.6546 > email: Robin_Blanchard@gactr.uga.edu > ------------------------------------ > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 11: 4:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sdmail0.sd.bmarts.com (sdmail0.sd.bmarts.com [209.247.77.155]) by hub.freebsd.org (Postfix) with ESMTP id 97EA337B424 for ; Fri, 13 Apr 2001 11:04:52 -0700 (PDT) (envelope-from gordont@bluemtn.net) Received: from localhost (gordont@localhost) by sdmail0.sd.bmarts.com (8.11.3/8.11.2/BMA1.1) with ESMTP id f3DI3n268655; Fri, 13 Apr 2001 11:03:49 -0700 (PDT) Date: Fri, 13 Apr 2001 11:03:49 -0700 (PDT) From: Gordon Tetlow X-X-Sender: To: "Thomas T. Veldhouse" Cc: Subject: Re: natd[232]: failed to write packet back (Permission denied) In-Reply-To: <002b01c0c43b$95b2ee20$3028680a@tgt.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG But, if you use the default firewall rules, *all* packets get put through natd, not just lan traffic, but incoming, and loopback traffic as well. I used to have this problem, but when I rewrote my firewall rules to use stateful firewalling, it disappeared. -gordon On Fri, 13 Apr 2001, Thomas T. Veldhouse wrote: > As an addendum -- I get these messages even when there is NO activity on the > LAN -- so natd is not even being used by any client. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 11:10:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from veldy.net (w028.z064001117.msp-mn.dsl.cnc.net [64.1.117.28]) by hub.freebsd.org (Postfix) with ESMTP id C44F237B507 for ; Fri, 13 Apr 2001 11:10:52 -0700 (PDT) (envelope-from veldy@veldy.net) Received: from HP2500B (fuggle.veldy.net [64.1.117.28]) by veldy.net (Postfix) with SMTP id CC40EBA4E; Fri, 13 Apr 2001 13:10:01 -0500 (CDT) Message-ID: <00a601c0c444$4ef9fc40$3028680a@tgt.com> From: "Thomas T. Veldhouse" To: "Gordon Tetlow" Cc: References: Subject: Re: natd[232]: failed to write packet back (Permission denied) Date: Fri, 13 Apr 2001 13:05:22 -0500 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.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was using stateful firewalling. I get even more errors. Oddly, whatever is causing it now happens in bursts of two every 12 minutes. I have not figured it out -- really annoying. The default "SIMPLE" firewall also causes it. That should not be -- so I would call that a bug in the /etc/rc.firewall script at the very least. Tom Veldhouse veldy@veldy.net ----- Original Message ----- From: "Gordon Tetlow" To: "Thomas T. Veldhouse" Cc: Sent: Friday, April 13, 2001 1:03 PM Subject: Re: natd[232]: failed to write packet back (Permission denied) > But, if you use the default firewall rules, *all* packets get put through > natd, not just lan traffic, but incoming, and loopback traffic as well. > > I used to have this problem, but when I rewrote my firewall rules to use > stateful firewalling, it disappeared. > > -gordon > > On Fri, 13 Apr 2001, Thomas T. Veldhouse wrote: > > > As an addendum -- I get these messages even when there is NO activity on the > > LAN -- so natd is not even being used by any client. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 11:14:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gactr.uga.edu (mail.gactr.uga.edu [128.192.37.21]) by hub.freebsd.org (Postfix) with SMTP id 984AA37B424 for ; Fri, 13 Apr 2001 11:14:30 -0700 (PDT) (envelope-from Robin_Blanchard@gactr.uga.edu) Received: (qmail 7866 invoked from network); 13 Apr 2001 18:14:30 -0000 Received: from qat.noc.nat (HELO gactr.uga.edu) ([10.10.100.125]) (envelope-sender ) by mail.servers.nat (qmail-ldap-1.03) with SMTP for ; 13 Apr 2001 18:14:30 -0000 Message-ID: <3AD741D4.A0B9F77A@gactr.uga.edu> Date: Fri, 13 Apr 2001 14:13:40 -0400 From: "Robin P. Blanchard" X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Larry Rosenman Cc: Matthew Emmerton , freebsd-stable@FreeBSD.ORG Subject: Re: install world on 486] References: <3AD5A1F9.7133FC74@gactr.uga.edu> <017001c0c425$b60c3020$1200a8c0@gsicomp.on.ca> <3AD71263.6E420055@gactr.uga.edu> <20010413181239.A33404@icon.icon.bg> <003f01c0c43a$1cf242c0$1200a8c0@gsicomp.on.ca> <3AD73898.3AC838@gactr.uga.edu> <20010413.17484400@ler-freebie.iadfw.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ok. so if i understand this correctly, the ideal setup for a collection of FreeBSD boxes would be to have an nfs server that itself is built without CPUTYPE, which has /usr/obj (for itself, without CPUTYPE) /usr/obj-486 /usr/obj-586 /usr/obj-686 (etc) all built separately via "make MAKEOBJDIRPREFIX=/usr/obj-[456]86" with the appropriate CPUTYPE set. then on the client boxes, simply mount the appropriate obj dir and do make installworld. is this the correct (and optimal) solution ? thanks in advance. > You *MUST* for 4.3 use a HOST SYSTEM compiled for the LOWEST processor > you want to installworld to. > > There is a few places (strip for one) that link in /usr/lib/libc.a and > NOT the one from /usr/obj/... > > This is on the list of things to be fixed POST-4.3, but will be true in > 4.3-RELEASE. > > This was discussed right after Kris Kennaway added the CPUTYPE support > for RELENG_4, and I ran into it. See the archives with a title of > CPUTYPE=i486 . > > Larry Rosenman > -- ------------------------------------ Robin P. Blanchard IT Program Specialist Georgia Center for Continuing Ed. fon: 706.542.2404 fax: 706.542.6546 email: Robin_Blanchard@gactr.uga.edu ------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 11:14:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 840D837B43E for ; Fri, 13 Apr 2001 11:14:43 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([fec0::2e0:7dff:fe81:749d] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.22 #1) id 14o85i-000Dwa-00; Fri, 13 Apr 2001 19:14:42 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.11.3/8.11.3) id f3DIEfs88711; Fri, 13 Apr 2001 19:14:42 +0100 (BST) (envelope-from ben) Date: Fri, 13 Apr 2001 19:14:41 +0100 From: Ben Smithurst To: j mckitrick Cc: freebsd-stable@freebsd.org Subject: Re: module documentation? Message-ID: <20010413191441.J75296@scientia.demon.co.uk> References: <20010413160114.A18212@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010413160114.A18212@dogma.freebsd-uk.eu.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG j mckitrick wrote: > Has there been any documentation on how to compile modules into or outside > the kernel? I must have missed the transition, and I'd like to move sound > into a module. I'd also like to see what else could be moved. Not sure, but for sound, I wouldn't waste your time. ;-) ben@platinum:/modules$ uname -rs FreeBSD 4.3-RC ben@platinum:/modules$ ls snd_* snd_ad1816.ko* snd_ds1.ko* snd_fm801.ko* snd_neomagic.ko* snd_sbc.ko* snd_cmi.ko* snd_emu10k1.ko* snd_maestro.ko* snd_pcm.ko* snd_solo.ko* snd_cs4281.ko* snd_es137x.ko* snd_maestro3.ko* snd_sb16.ko* snd_t4dwave.ko* snd_csa.ko* snd_ess.ko* snd_mss.ko* snd_sb8.ko* snd_via82c686.ko* It already is a module. Well, 20 modules anyway. Though if you want to make the snoop (snp) device a module, that would be nice, there have been a couple of times when I wanted it. -- Ben Smithurst / ben@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 12:15:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lerami.lerctr.org (lerami.lerctr.org [207.158.72.11]) by hub.freebsd.org (Postfix) with ESMTP id 6FD2437B506 for ; Fri, 13 Apr 2001 12:15:20 -0700 (PDT) (envelope-from ler@lerctr.org) Received: from ler-freebie.iadfw.net (ler-freebie.iadfw.net [206.66.13.221]) by lerami.lerctr.org (8.12.0.Beta7/8.12.0.Beta7/20010318/$Revision: 1.21 $) with SMTP id f3DJFIHh016136; Fri, 13 Apr 2001 14:15:18 -0500 (CDT) (envelope-from ler@lerctr.org) From: Larry Rosenman Date: Fri, 13 Apr 2001 19:15:18 GMT Message-ID: <20010413.19151800@ler-freebie.iadfw.net> Subject: Re: install world on 486] To: Robin "P. Blanchard" Cc: Larry Rosenman , Matthew Emmerton , freebsd-stable@FreeBSD.ORG In-Reply-To: <3AD741D4.A0B9F77A@gactr.uga.edu> References: <3AD5A1F9.7133FC74@gactr.uga.edu> <017001c0c425$b60c3020$1200a8c0@gsicomp.on.ca> <3AD71263.6E420055@gactr.uga.edu> <20010413181239.A33404@icon.icon.bg> <003f01c0c43a$1cf242c0$1200a8c0@gsicomp.on.ca> <3AD73898.3AC838@gactr.uga.edu> <20010413.17484400@ler-freebie.iadfw.net> <3AD741D4.A0B9F77A@gactr.uga.edu> X-Mailer: Mozilla/3.0 (compatible; StarOffice/5.2; Linux) X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I believe that will work, but will defer to the Committers in attendance= . LER --=20 Larry Rosenman http://www.lerctr.org/~ler/ Phone: +1 972 414 9812 E-Mail: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 US >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 4/13/01, 1:13:40 PM, Robin "P." Blanchard=20 wrote regarding Re: install world on 486= ]: > ok. so if i understand this correctly, the ideal setup for a collectio= n=20 of > FreeBSD boxes would be to have an nfs server that itself is built with= out > CPUTYPE, which has /usr/obj (for itself, without CPUTYPE) /usr/obj-486= > /usr/obj-586 /usr/obj-686 (etc) all built separately via > "make MAKEOBJDIRPREFIX=3D/usr/obj-[456]86" with the appropriate CPUTYP= E=20 set. > then on the client boxes, simply mount the appropriate obj dir and do = make > installworld. > is this the correct (and optimal) solution ? > thanks in advance. > > You *MUST* for 4.3 use a HOST SYSTEM compiled for the LOWEST process= or > > you want to installworld to. > > > > There is a few places (strip for one) that link in /usr/lib/libc.a a= nd > > NOT the one from /usr/obj/... > > > > This is on the list of things to be fixed POST-4.3, but will be true= in > > 4.3-RELEASE. > > > > This was discussed right after Kris Kennaway added the CPUTYPE suppo= rt > > for RELENG_4, and I ran into it. See the archives with a title of > > CPUTYPE=3Di486 . > > > > Larry Rosenman > > > -- > ------------------------------------ > Robin P. Blanchard > IT Program Specialist > Georgia Center for Continuing Ed. > fon: 706.542.2404 fax: 706.542.6546 > email: Robin_Blanchard@gactr.uga.edu > ------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 12:52:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88]) by hub.freebsd.org (Postfix) with ESMTP id 080F537B449 for ; Fri, 13 Apr 2001 12:52:54 -0700 (PDT) (envelope-from gehicks@cisco.com) Received: from mira1.cisco.com (mira1.cisco.com [171.71.208.193]) by sj-msg-core-2.cisco.com (8.9.3/8.9.1) with ESMTP id MAA24202 for ; Fri, 13 Apr 2001 12:53:16 -0700 (PDT) Received: from cisco.com (ptlm1-dhcp-102.cisco.com [171.71.210.102]) by mira1.cisco.com (Mirapoint) with ESMTP id AAW05538; Fri, 13 Apr 2001 12:52:50 -0700 (PDT) Message-ID: <3AD75930.E759E95B@cisco.com> Date: Fri, 13 Apr 2001 12:53:20 -0700 From: W Gerald Hicks Organization: Cisco Systems X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-BETA i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-stable@freebsd.org Subject: Re: nVidia Cards /w FreeBSD (3D Acceleration) References: <3AD427DC.CFC52BAE@quake.com.au> <3AD618E9.E3C5890E@cisco.com> <3AD65706.E9ABB2B6@cvzoom.net> <3AD68D88.471BF306@quake.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kal Torak wrote: > > Donn Miller wrote: > > > > W Gerald Hicks wrote: > > > > > > Uhm, Can we please move this thread away from the stable list? > > > > Exactly! Correct me if I'm wrong, but perhaps that's why we have a > > freebsd-hardware list. > > No, we have a hardware list for developers to talk about hardware and > such things, not for topics to goto when certain people dont want to > see them anymore! > > Dont read the thread if it annoys you so much, its not going to take us > long to get this sorted out... I tired to start this topic in several other > lists but got no joy, stable responded favourably, so we will finish it up > here... > > It will die soon, we are close to working out the details! Ok, pardon me for wanting to use the appropriate lists for their chartered purposes; especially in the thick of a release cycle when a lot of people are upgrading gobs of computers and stuff. -- Jerry Hicks gehicks@cisco.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 12:55:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.unixathome.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id A549837B446 for ; Fri, 13 Apr 2001 12:55:17 -0700 (PDT) (envelope-from dan@langille.org) Received: from wocker (root@ns1.unixathome.org [192.168.0.20]) by ns1.unixathome.org (8.11.3/8.11.3) with ESMTP id f3DJtEe11914 for ; Sat, 14 Apr 2001 07:55:15 +1200 (NZST) (envelope-from dan@langille.org) Message-Id: <200104131955.f3DJtEe11914@ns1.unixathome.org> From: "Dan Langille" Organization: novice in training To: stable@FreeBSD.ORG Date: Fri, 13 Apr 2001 15:55:12 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Just an observation - MUA's seen in the lists Reply-To: dan@langille.org In-reply-to: <20010413074206.A35752@lunatic.oneinsane.net> References: ; from kris@catonic.net on Fri, Apr 13, 2001 at 01:10:51PM +0000 X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13 Apr 2001, at 7:42, Ron 'The InSaNe One' Rosson wrote: > I would like to see a Windows based Email program try to open a mailbox > with 500 messages (threaded). ;-) Let's see, perhaps I misunderstand the point, but Pegasus here on NT has 1 folder with 30367 messages, two folders with about 4500 msgs, and several with > 2000. -- Dan Langille pgpkey - finger dan@unixathome.org | http://unixathome.org/finger.php got any work? I'm looking for some. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 13:15:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 010C837B446 for ; Fri, 13 Apr 2001 13:15:37 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id wowaaaaa for ; Sat, 14 Apr 2001 06:15:10 +1000 Message-ID: <3AD75F56.72F47E6D@quake.com.au> Date: Sat, 14 Apr 2001 06:19:34 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: W Gerald Hicks Cc: FreeBSD-stable@freebsd.org Subject: Kill This Thread (was-> Re: nVidia Cards /w FreeBSD (3D Acceleration)) References: <3AD427DC.CFC52BAE@quake.com.au> <3AD618E9.E3C5890E@cisco.com> <3AD65706.E9ABB2B6@cvzoom.net> <3AD68D88.471BF306@quake.com.au> <3AD75930.E759E95B@cisco.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG W Gerald Hicks wrote: > > Kal Torak wrote: > > > > Donn Miller wrote: > > > > > > W Gerald Hicks wrote: > > > > > > > > Uhm, Can we please move this thread away from the stable list? > > > > > > Exactly! Correct me if I'm wrong, but perhaps that's why we have a > > > freebsd-hardware list. > > > > No, we have a hardware list for developers to talk about hardware and > > such things, not for topics to goto when certain people dont want to > > see them anymore! > > > > Dont read the thread if it annoys you so much, its not going to take us > > long to get this sorted out... I tired to start this topic in several other > > lists but got no joy, stable responded favourably, so we will finish it up > > here... > > > > It will die soon, we are close to working out the details! > > Ok, pardon me for wanting to use the appropriate lists for their chartered purposes; especially in the thick of a release cycle > when a lot of people are upgrading gobs of computers and stuff. Thats ok I forgive you! hardware is not really the location for this sort of thing anyway! a better list would be -people_that_want_companys_to_do_stuff_so_there_ product_works_with_freebsd... unfortunately we dont have such a list... anyway, when you made your post about killing the thread it was already pretty much over, since we had worked out what could and needed to be done... Im sorry to have been short tempered with you, but it really annoys me when people say "take this to another list"... Especially when there is not really an appropriate list in existence! Try to be more tolerant of threads you feel are in the wrong list... I never complain about such things... Unless someone starts asking windows questions on the FreeBSD lists of cause ;) If its roughly in line with the list (which this topic is, since its getting support of hardware into stable) then just let it ride... Thats my feelings anyway! Have fun! Kal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 13:37:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from chmod.ath.cx (CC2-861.charter-stl.com [24.217.115.99]) by hub.freebsd.org (Postfix) with ESMTP id C064437B449 for ; Fri, 13 Apr 2001 13:37:21 -0700 (PDT) (envelope-from ajh3@chmod.ath.cx) Received: by chmod.ath.cx (Postfix, from userid 1001) id 805EDA921; Fri, 13 Apr 2001 15:36:31 -0500 (CDT) Date: Fri, 13 Apr 2001 15:36:31 -0500 From: Andrew Hesford To: Jordan Hubbard Cc: stable@freebsd.org Subject: Re: Anyone interested in the SVR4 compat module anymore? Message-ID: <20010413153631.A14679@cec.wustl.edu> References: <200104131637.f3DGbPt04946@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104131637.f3DGbPt04946@winston.osd.bsdi.com>; from jkh@winston.osd.bsdi.com on Fri, Apr 13, 2001 at 09:37:25AM -0700 X-Loop: Andrew Hesford Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 13, 2001 at 09:37:25AM -0700, Jordan Hubbard wrote: > I'm just now noticing (I so rarely turn it on) that the svr4 ABI > module is broken - you get "link_elf: symbol svr4_stream_get undefined" > when you try to load it. > > Unless someone wants to fix it before the 19th or so, I'll remove > it as a sysinstall option at the last minute so people new to 4.3 > don't go "Huh?" - they'll have to work a little harder to confuse > themselves. :) I once tried to get Matlab for Solaris running with the svr4 ABI module. I got some "invalid binary file" message--it was so long ago, I can't remember what exactly it was. Anyway, I never investigated it, I just scrapped the task after the first failure. Since then, I have had no interest in the SVR4 binary. -- Andrew Hesford ajh3@chmod.ath.cx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 13:40:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from chmod.ath.cx (CC2-861.charter-stl.com [24.217.115.99]) by hub.freebsd.org (Postfix) with ESMTP id D28A537B506 for ; Fri, 13 Apr 2001 13:40:51 -0700 (PDT) (envelope-from ajh3@chmod.ath.cx) Received: by chmod.ath.cx (Postfix, from userid 1001) id EF4E8A921; Fri, 13 Apr 2001 15:40:01 -0500 (CDT) Date: Fri, 13 Apr 2001 15:40:01 -0500 From: Andrew Hesford To: Kal Torak Cc: W Gerald Hicks , FreeBSD-stable@freebsd.org Subject: Re: Kill This Thread (was-> Re: nVidia Cards /w FreeBSD (3D Acceleration)) Message-ID: <20010413154001.B14679@cec.wustl.edu> References: <3AD427DC.CFC52BAE@quake.com.au> <3AD618E9.E3C5890E@cisco.com> <3AD65706.E9ABB2B6@cvzoom.net> <3AD68D88.471BF306@quake.com.au> <3AD75930.E759E95B@cisco.com> <3AD75F56.72F47E6D@quake.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AD75F56.72F47E6D@quake.com.au>; from kaltorak@quake.com.au on Sat, Apr 14, 2001 at 06:19:34AM +1000 X-Loop: Andrew Hesford Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 14, 2001 at 06:19:34AM +1000, Kal Torak wrote: > Im sorry to have been short tempered with you, but it really annoys me when > people say "take this to another list"... Especially when there is not really > an appropriate list in existence! > > Try to be more tolerant of threads you feel are in the wrong list... I never > complain about such things... Unless someone starts asking windows questions > on the FreeBSD lists of cause ;) > If its roughly in line with the list (which this topic is, since its getting > support of hardware into stable) then just let it ride... Thats my feelings > anyway! I don't really care much what topics are spawned, I just delete things en masse according to subjects. What DOES piss me off are cross-posts. People say, "Don't read them if you don't want," but I'm not reading them. The problem is now I have to go through and delete multiple copies of the same message. I'm of the firm belief (as are many others on this list) that threads should be confined to one list, and moved to another only after they have gotten no original response. -- Andrew Hesford ajh3@chmod.ath.cx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 13:46:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ece.cmu.edu (ECE.CMU.EDU [128.2.236.200]) by hub.freebsd.org (Postfix) with ESMTP id 9B10C37B50C for ; Fri, 13 Apr 2001 13:46:33 -0700 (PDT) (envelope-from allbery@ece.cmu.edu) Received: from rushlight.rem.cmu.edu (ANNEX-3.ECE.CMU.EDU [128.2.136.3]) (authenticated) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id f3DKjcr00545; Fri, 13 Apr 2001 16:45:38 -0400 (EDT) Date: Fri, 13 Apr 2001 16:45:36 -0400 From: "Brandon S. Allbery KF8NH" To: Andrew Hesford , Jordan Hubbard Cc: stable@FreeBSD.ORG Subject: Re: Anyone interested in the SVR4 compat module anymore? Message-ID: <232850000.987194736@rushlight.rem.cmu.edu> In-Reply-To: <20010413153631.A14679@cec.wustl.edu> X-Mailer: Mulberry/2.0.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, April 13, 2001 15:36:31 -0500, ajh3@chmod.ath.cx wrote: +---- | On Fri, Apr 13, 2001 at 09:37:25AM -0700, Jordan Hubbard wrote: | > I'm just now noticing (I so rarely turn it on) that the svr4 ABI | > module is broken - you get "link_elf: symbol svr4_stream_get undefined" | > when you try to load it. | > | > Unless someone wants to fix it before the 19th or so, I'll remove | > it as a sysinstall option at the last minute so people new to 4.3 | > don't go "Huh?" - they'll have to work a little harder to confuse | > themselves. :) | | I once tried to get Matlab for Solaris running with the svr4 ABI module. +--->8 Solaris x86 isn't quite svr4 ABI (x86 version); Solaris x86 stuff tends not to work as expected. Specifically, IIRC the shared object support is different, so static binaries tend to work but dynamic ones are unreliable. -- brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering KF8NH carnegie mellon university ["better check the oblivious first" -ke6sls] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 14:37:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 859E837B43F for ; Fri, 13 Apr 2001 14:37:37 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f3DLbZM05888; Fri, 13 Apr 2001 14:37:36 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: kaltorak@quake.com.au Cc: gehicks@cisco.com, FreeBSD-stable@FreeBSD.ORG Subject: Re: Kill This Thread (was-> Re: nVidia Cards /w FreeBSD (3D Acceleration)) In-Reply-To: <3AD75F56.72F47E6D@quake.com.au> References: <3AD68D88.471BF306@quake.com.au> <3AD75930.E759E95B@cisco.com> <3AD75F56.72F47E6D@quake.com.au> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010413143735M.jkh@osd.bsdi.com> Date: Fri, 13 Apr 2001 14:37:35 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, the correct list for the discussion of nVidia cards is freebsd-multimedia - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 14:56:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hecky.it.northwestern.edu (hecky.acns.nwu.edu [129.105.16.51]) by hub.freebsd.org (Postfix) with ESMTP id CD47237B443 for ; Fri, 13 Apr 2001 14:56:39 -0700 (PDT) (envelope-from stuyman@confusion.net) Received: (from mailnull@localhost) by hecky.it.northwestern.edu (8.8.7/8.8.7) id QAA18553; Fri, 13 Apr 2001 16:56:37 -0500 (CDT) Received: from confusion.net (dhcp089069.res-hall.nwu.edu [199.74.89.69]) by hecky.acns.nwu.edu via smap (V2.0) id xma018326; Fri, 13 Apr 01 16:56:04 -0500 Message-ID: <3AD775BF.F686B70A@confusion.net> Date: Fri, 13 Apr 2001 16:55:11 -0500 From: Laurence Berland X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: dan@langille.org Cc: stable@FreeBSD.ORG Subject: Re: Just an observation - MUA's seen in the lists References: ; from kris@catonic.net on Fri, Apr 13, 2001 at 01:10:51PM +0000 <200104131955.f3DJtEe11914@ns1.unixathome.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As much as I love bashing windows, I do actually use it for my email machine (because I don't think there's a version of Meeting Maker for any UNIX, and I need it to sync to my Palm...) and the folder I'm reading this message in has 7605 messages in it, threaded. My questions folder is bigger. I just don't delete stuff until it annoys me too much... this is on Netscape btw... L: Dan Langille wrote: > > On 13 Apr 2001, at 7:42, Ron 'The InSaNe One' Rosson wrote: > > > I would like to see a Windows based Email program try to open a mailbox > > with 500 messages (threaded). ;-) > > Let's see, perhaps I misunderstand the point, but Pegasus here on NT > has 1 folder with 30367 messages, two folders with about 4500 msgs, > and several with > 2000. > > -- > Dan Langille > pgpkey - finger dan@unixathome.org | http://unixathome.org/finger.php > got any work? I'm looking for some. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Laurence Berland Intern, Flooz.com Northwestern '04 stuyman@confusion.net http://www.isp.northwestern.edu/~laurence "The world has turned and left me here" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 14:58: 2 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id E640F37B422 for ; Fri, 13 Apr 2001 14:57:59 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id opwaaaaa for ; Sat, 14 Apr 2001 07:57:30 +1000 Message-ID: <3AD77732.E634871B@quake.com.au> Date: Sat, 14 Apr 2001 08:01:22 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Hesford Cc: W Gerald Hicks , FreeBSD-stable@freebsd.org Subject: Re: Kill This Thread (was-> Re: nVidia Cards /w FreeBSD (3D Acceleration)) References: <3AD427DC.CFC52BAE@quake.com.au> <3AD618E9.E3C5890E@cisco.com> <3AD65706.E9ABB2B6@cvzoom.net> <3AD68D88.471BF306@quake.com.au> <3AD75930.E759E95B@cisco.com> <3AD75F56.72F47E6D@quake.com.au> <20010413154001.B14679@cec.wustl.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't really care much what topics are spawned, I just delete things > en masse according to subjects. What DOES piss me off are cross-posts. > People say, "Don't read them if you don't want," but I'm not reading > them. The problem is now I have to go through and delete multiple copies > of the same message. > > I'm of the firm belief (as are many others on this list) that threads > should be confined to one list, and moved to another only after they > have gotten no original response. Well I started this on the hardware list... after a few days of no response I tried questions, then thought I would give ports a go... Then finally figured I would try my luck on stable... Stable was the only place there seemed to be an interest, which is why am annoyed with people telling me to change lists... Its a moot point now anyway since we have finished the public discussion of it! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 15:29:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 771FE37B42C for ; Fri, 13 Apr 2001 15:29:27 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f3DMT2M06093; Fri, 13 Apr 2001 15:29:02 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: kaltorak@quake.com.au Cc: ajh3@chmod.ath.cx, gehicks@cisco.com, FreeBSD-stable@FreeBSD.ORG Subject: Re: Kill This Thread (was-> Re: nVidia Cards /w FreeBSD (3D Acceleration)) In-Reply-To: <3AD77732.E634871B@quake.com.au> References: <3AD75F56.72F47E6D@quake.com.au> <20010413154001.B14679@cec.wustl.edu> <3AD77732.E634871B@quake.com.au> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010413152902Q.jkh@osd.bsdi.com> Date: Fri, 13 Apr 2001 15:29:02 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 8 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well I started this on the hardware list... after a few days of no response > I tried questions, then thought I would give ports a go... Then finally > figured I would try my luck on stable... Don't do that. That approach will simply get you blacklisted and I honestly don't care if that offends you or not. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 15:35:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from finch-post-12.mail.demon.net (finch-post-12.mail.demon.net [194.217.242.41]) by hub.freebsd.org (Postfix) with ESMTP id B5E0B37B446 for ; Fri, 13 Apr 2001 15:35:24 -0700 (PDT) (envelope-from goddard@acm.org) Received: from shootthemlater.demon.co.uk ([194.222.93.84] helo=cerebus.parse.net) by finch-post-12.mail.demon.net with esmtp (Exim 2.12 #1) id 14oC9z-000MPN-0C for freebsd-stable@freebsd.org; Fri, 13 Apr 2001 22:35:24 +0000 Received: from wbra0013.cognos.com ([10.0.0.3] helo=acm.org) by cerebus.parse.net with esmtp (Exim 3.16 #1) id 14oBMl-0003jN-00 for freebsd-stable@freebsd.org; Fri, 13 Apr 2001 22:44:31 +0100 Message-ID: <3AD77374.1F876BDA@acm.org> Date: Fri, 13 Apr 2001 22:45:24 +0100 From: David Goddard X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: Problems with 3c905B and 4.3-RC References: <3AD4CBC3.F3E79AFC@rtci.com> <01041208131800.29806@merlin> <045c01c0c34b$588d6980$931576d8@inethouston.net> <3AD5F9A7.2B305998@rtci.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm a bit worried about this one... I have a remote server that I was planning to upgrade after 4.3 comes out and this has a 3C905C NIC. I don't believe PnP OS is set on in the BIOS but I can't guarantee this totally. Am I going to have to visit the co-lo place? Is there any way I can query BOIS settings remotely? Thanks, Dave Jeremy Hopkins wrote: > > Correct. the pnp OS setting solved my issue. > But to answer the question. Yes, miibus was in my kernel. > > "David W. Chapman Jr." wrote: > > > > No, he solved the problem already by setting pnp OS to off I believe. > > > > ----- Original Message ----- > > From: "Jeff Love" > > > > Not sure if this is the problem in your case, but did you include 'device > > > miibus' to your kernel config? This was a fairly recent addition needed > > for > > > 3com nics. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 15:48:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 76F8137B43E for ; Fri, 13 Apr 2001 15:48:14 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id vpwaaaaa for ; Sat, 14 Apr 2001 08:47:51 +1000 Message-ID: <3AD7831F.28B9D953@quake.com.au> Date: Sat, 14 Apr 2001 08:52:15 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jordan Hubbard Cc: ajh3@chmod.ath.cx, gehicks@cisco.com, FreeBSD-stable@FreeBSD.ORG Subject: Re: Kill This Thread (was-> Re: nVidia Cards /w FreeBSD (3D Acceleration)) References: <3AD75F56.72F47E6D@quake.com.au> <20010413154001.B14679@cec.wustl.edu> <3AD77732.E634871B@quake.com.au> <20010413152902Q.jkh@osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan Hubbard wrote: > > > Well I started this on the hardware list... after a few days of no response > > I tried questions, then thought I would give ports a go... Then finally > > figured I would try my luck on stable... > > Don't do that. That approach will simply get you blacklisted and I > honestly don't care if that offends you or not. Right, so instead you just give up? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 15:57:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cmailg3.svr.pol.co.uk (cmailg3.svr.pol.co.uk [195.92.195.173]) by hub.freebsd.org (Postfix) with ESMTP id 4A8F237B507 for ; Fri, 13 Apr 2001 15:57:29 -0700 (PDT) (envelope-from admin@unix-security.co.uk) Received: from modem-188.helium.dialup.pol.co.uk ([62.136.1.188] helo=thunder) by cmailg3.svr.pol.co.uk with smtp (Exim 3.13 #0) id 14oCVF-0007Jg-00 for freebsd-stable@freebsd.org; Fri, 13 Apr 2001 23:57:24 +0100 Message-ID: <001001c0c46d$9665b0a0$03000004@thunder> From: "Jon" To: Subject: trouble mounting atapi cd drvie in 4.1 Date: Sat, 14 Apr 2001 00:00:31 +0100 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0005_01C0C475.EBF39200" 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C0C475.EBF39200 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0006_01C0C475.EBF39200" ------=_NextPart_001_0006_01C0C475.EBF39200 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I recently tried mounting my cd drive using different commands but it = gave =3D=20 the following error (or something similar )=20 acd0c: READ_BIG illegal request=20 cd9660: input/output error=20 it mounted fine before using the command =3D93mount_cd9660 /dev/acd0c = /cdrom=3D=20 =3D93=20 I tried unmounting the cd drive but it said =3D93not currently = mounted=3D93=3D20=20 There was no physical problem with the cd-drive because it could install = pa=3D=20 ckages when I booted from floppy, I tried using =3D93sysctl -w = hw.atamodes=3D3D=3D=20 pio=3D93 to set it to pio mode, no luck. I tried kldload cd9660.ko but = it sai=3D=20 d the module was already loaded. The /cdrom directory was there as = before. =3D=20 I then thought that I may have altered something wrongly in the kernel, = so =3D=20 I compiled the generic, still no luck. In the end I reinstalled and it = was =3D=20 working fine. any ideas what could have caused this and how it could = have b=3D=20 een fixed?=20 I have inluded my dmesg as an attachment=20 ------=_NextPart_001_0006_01C0C475.EBF39200 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I recently tried mounting my cd drive = using=20 different commands but it gave =3D
the following error (or something = similar )=20

acd0c: READ_BIG illegal request
cd9660: input/output error=20

it mounted fine before using the command =3D93mount_cd9660 = /dev/acd0c=20 /cdrom=3D
=3D93
I tried unmounting the cd drive but it said = =3D93not currently=20 mounted=3D93=3D20
There was no physical problem with the cd-drive = because it=20 could install pa=3D
ckages when I booted from floppy, I tried using = =3D93sysctl=20 -w hw.atamodes=3D3D=3D
pio=3D93 to set it to pio mode, no luck. I = tried kldload=20 cd9660.ko but it sai=3D
d the module was already loaded. The /cdrom = directory=20 was there as before. =3D
I then thought that I may have altered = something=20 wrongly in the kernel, so =3D
I compiled the generic, still no luck. = In the=20 end I reinstalled and it was =3D
working fine. any ideas what could = have=20 caused this and how it could have b=3D
een fixed?

I have = inluded my=20 dmesg as an attachment

------=_NextPart_001_0006_01C0C475.EBF39200-- ------=_NextPart_000_0005_01C0C475.EBF39200 Content-Type: text/plain; name="Dmesg.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Dmesg.txt" Copyright (c) 1992-2000 The FreeBSD Project.=0A= Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994=0A= The Regents of the University of California. All rights reserved.=0A= FreeBSD 4.1-RELEASE #0: Fri Jul 28 14:30:31 GMT 2000=0A= jkh@ref4.freebsd.org:/usr/src/sys/compile/GENERIC=0A= Timecounter "i8254" frequency 1193182 Hz=0A= CPU: Pentium/P5 (57.00-MHz 586-class CPU)=0A= Origin =3D "GenuineIntel" Id =3D 0x517 Stepping =3D 7=0A= Features=3D0x1bf=0A= real memory =3D 33554432 (32768K bytes)=0A= avail memory =3D 28659712 (27988K bytes)=0A= Preloaded elf kernel "kernel" at 0xc040d000.=0A= Intel Pentium detected, installing workaround for F00F bug=0A= md0: Malloc disk=0A= npx0: on motherboard=0A= npx0: INT 16 interface=0A= pcib0: on motherboard=0A= pci0: on pcib0=0A= isab0: at device 2.0 on pci0=0A= isa0: on isab0=0A= pci0: (vendor=3D0x1813, dev=3D0x4000) at 6.0 irq 9=0A= pci0: at 12.0 irq 9=0A= fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0=0A= fdc0: FIFO enabled, 8 bytes threshold=0A= fd0: <1440-KB 3.5" drive> on fdc0 drive 0=0A= ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0=0A= atkbdc0: at port 0x60,0x64 on isa0=0A= atkbd0: flags 0x1 irq 1 on atkbdc0=0A= kbd0 at atkbd0=0A= psm0: irq 12 on atkbdc0=0A= psm0: model Generic PS/2 mouse, device ID 0=0A= vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0=0A= sc0: at flags 0x100 on isa0=0A= sc0: VGA <16 virtual consoles, flags=3D0x300>=0A= sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0=0A= sio0: type 16550A=0A= sio1 at port 0x2f8-0x2ff irq 3 on isa0=0A= sio1: type 16550A=0A= ppc0: at port 0x378-0x37f irq 7 on isa0=0A= ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode=0A= ppi0: on ppbus0=0A= lpt0: on ppbus0=0A= lpt0: Interrupt-driven port=0A= plip0: on ppbus0=0A= ad0: 2014MB [4092/16/63] at ata0-master using BIOSPIO=0A= acd0: CDROM at ata0-slave using BIOSPIO=0A= Mounting root from ufs:/dev/ad0s1a=0A= WARNING: / was not properly dismounted=0A= IP packet filtering initialized, divert disabled, rule-based forwarding = disabled, default to deny, logging disabled=0A= ------=_NextPart_000_0005_01C0C475.EBF39200-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 15:58:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 961A337B43E for ; Fri, 13 Apr 2001 15:58:55 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id f3DMwqS38465; Fri, 13 Apr 2001 15:58:52 -0700 (PDT) Date: Fri, 13 Apr 2001 15:58:52 -0700 (PDT) From: Doug White To: "R.P. Aditya" Cc: Subject: Re: uninstalling a distribution (xfree86) In-Reply-To: <20010412101329.A99058@mighty.grot.org> Message-ID: X-All-Your-Base: are belong to us MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Apr 2001, R.P. Aditya wrote: > Hi, > > Is there a way, akin to installing the xfree86 distribution during install or > using /stand/sysinstall, to uninstall it. If it matters, this is on a > 4.2-RELEASE machine that has XFree86 3.3.6 on it. I'm turning it into a remote > server and want to recover some room in /usr. It would be nice if there was > some sort of "pkg" info kept for the xfree86 distribution so it could be > removed by pkg_delete -- I figured I'd check before I just ran rm -r > /usr/X11R6 That's where X lives, so trashing /usr/X11R6 is pretty safe (modulo /etc/XF86Config). 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-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 17: 9:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (Postfix) with ESMTP id 996DB37B43F for ; Fri, 13 Apr 2001 17:09:09 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.3/8.9.1) with ESMTP id RAA86859 for ; Fri, 13 Apr 2001 17:09:09 -0700 (PDT) Date: Fri, 13 Apr 2001 17:09:08 -0700 (PDT) From: Chris Timmons To: freebsd-stable@freebsd.org Subject: telnet(1): No default realm defined for Kerberos! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've done everything I can to expunge Kerberos from my -stable machine (I never was running it in the first place, but I must have installed it via sysinstall when I built the system). I'm up-to-date with today's -RC3 and mergemaster, have the kerberos nobs turned off in /etc/defaults/make.conf, and am not seeing any kerberos utilities built or installed. I removed the /etc/kerberos* directory that I had prior to the last build/installworld, and all of the the other kerberos stuff that was originally installed. After all that, whenever I open a telnet session from this host to another (eg. a cisco switch), I have the following text splattered in my session: Kerberos: No default realm defined for Kerberos! I saw another report of this on -questions, but no answer Does anyone have any ideas of where else to look? I ktraced my telnet session and could see telnet looking up the kerberos ports in /etc/services, but I haven't yet found what configuration file it is looking in to tell it to do that. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 17:58: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id B526F37B42C for ; Fri, 13 Apr 2001 17:58:02 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id RAA19541; Fri, 13 Apr 2001 17:57:56 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200104140057.RAA19541@freeway.dcfinc.com> Subject: Re: ports "make index" fails In-Reply-To: <4383.209.141.226.130.987183216.squirrel@www.solo.net> from "David A. Koran" at "Apr 13, 1 01:33:36 pm" To: dak@solo.net Date: Fri, 13 Apr 2001 17:57:55 -0700 (MST) Cc: dak@solo.net, freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com Organization: DCF, Inc. X-O/S: FreeBSD 2.2.8-STABLE X-Unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, David A. Koran wrote: > I always like to do a fresh "make index" after cvsupping the ports > tree, and came across this issue this morning. Dunno how many other > rely on the INDEX for tracking port revs easily, but if this woudl get > fixed, that woudl be grand. When I use CVSup to update my repository, and then use cvs to update my ports tree, an INDEX file seems to propogate. Someone is building them on the server end, it seems. Now, if someone has a tidy way of dealing with the "README.html" files, I'd be interested. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 18:12:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id AC85337B422 for ; Fri, 13 Apr 2001 18:12:25 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id SAA19658; Fri, 13 Apr 2001 18:11:52 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200104140111.SAA19658@freeway.dcfinc.com> Subject: Re: Anyone interested in the SVR4 compat module anymore? In-Reply-To: <20010413153631.A14679@cec.wustl.edu> from Andrew Hesford at "Apr 13, 1 03:36:31 pm" To: ajh3@chmod.ath.cx (Andrew Hesford) Date: Fri, 13 Apr 2001 18:11:51 -0700 (MST) Cc: jkh@winston.osd.bsdi.com, stable@FreeBSD.ORG Reply-To: chad@DCFinc.com Organization: DCF, Inc. X-O/S: FreeBSD 2.2.8-STABLE X-Unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Andrew Hesford wrote: > Anyway, I never investigated it, I just scrapped the task after the > first failure. Since then, I have had no interest in the SVR4 binary. I'm interested in it working, as we have a mix of Solaris x86 boxes and FreeBSD. And, we used to use the iBSC2 module to run Interactive UNIX binaries. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 18:20:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.urx.com (mail.urx.com [63.170.19.36]) by hub.freebsd.org (Postfix) with ESMTP id 6F7E737B61A for ; Fri, 13 Apr 2001 18:20:09 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com [206.159.132.160] by mail.urx.com with ESMTP (SMTPD32-6.06) id A5C5252025C; Fri, 13 Apr 2001 18:20:05 -0700 Message-ID: <3AD7A5C4.85C1FB95@urx.com> Date: Fri, 13 Apr 2001 18:20:04 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: chad@DCFinc.com Cc: dak@solo.net, freebsd-stable@FreeBSD.ORG Subject: Re: ports "make index" fails References: <200104140057.RAA19541@freeway.dcfinc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Chad R. Larson" wrote: > > As I recall, David A. Koran wrote: > > I always like to do a fresh "make index" after cvsupping the ports > > tree, and came across this issue this morning. Dunno how many other > > rely on the INDEX for tracking port revs easily, but if this woudl get > > fixed, that woudl be grand. > > When I use CVSup to update my repository, and then use cvs to update > my ports tree, an INDEX file seems to propogate. Someone is > building them on the server end, it seems. But not as often as changes are made to it. If you want the equivilent current INDEX, you need to do a make index. > > Now, if someone has a tidy way of dealing with the "README.html" > files, I'd be interested. The readme's are usually built by doing a "make readmes". Kent > > -crl > -- > Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? > chad@dcfinc.com chad@larsons.org larson1@home.com > DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 18:21:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ece.cmu.edu (ECE.CMU.EDU [128.2.236.200]) by hub.freebsd.org (Postfix) with ESMTP id 9FCB437B43F for ; Fri, 13 Apr 2001 18:21:30 -0700 (PDT) (envelope-from allbery@ece.cmu.edu) Received: from rushlight.rem.cmu.edu (ANNEX-3.ECE.CMU.EDU [128.2.136.3]) (authenticated) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id f3E1H7r18317; Fri, 13 Apr 2001 21:17:07 -0400 (EDT) Date: Fri, 13 Apr 2001 21:17:04 -0400 From: "Brandon S. Allbery KF8NH" To: Chris Timmons , freebsd-stable@FreeBSD.ORG Subject: Re: telnet(1): No default realm defined for Kerberos! Message-ID: <124030000.987211024@rushlight.rem.cmu.edu> In-Reply-To: X-Mailer: Mulberry/2.0.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, April 13, 2001 17:09:08 -0700, skynyrd@opus.cts.cwu.edu wrote: +---- | After all that, whenever I open a telnet session from this host to another | (eg. a cisco switch), I have the following text splattered in my session: | | Kerberos: No default realm defined for Kerberos! +--->8 That message is printed by a Cisco router. You need to use the telnet from /usr/src/usr.bin/telnet; it's no longer the default one installed, apparently, and if you use the default one from the kerberos distribution then any remote machine which is kerberos-aware will attempt (and fail) to negotiate kerberos authentication. -- brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering KF8NH carnegie mellon university ["better check the oblivious first" -ke6sls] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 18:41:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 227DC37B440 for ; Fri, 13 Apr 2001 18:41:20 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id SAA19851; Fri, 13 Apr 2001 18:41:11 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200104140141.SAA19851@freeway.dcfinc.com> Subject: Re: ports "make index" fails In-Reply-To: <3AD7A5C4.85C1FB95@urx.com> from Kent Stewart at "Apr 13, 1 06:20:04 pm" To: kstewart@urx.com Date: Fri, 13 Apr 2001 18:41:10 -0700 (MST) Cc: dak@solo.net, freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com Organization: DCF, Inc. X-O/S: FreeBSD 2.2.8-STABLE X-Unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Kent Stewart wrote: >> Now, if someone has a tidy way of dealing with the "README.html" >> files, I'd be interested. > > The readme's are usually built by doing a "make readmes". Yes, but then the cvs update complains about those files it knows nothing about. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 13 19: 6:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.urx.com (mail.urx.com [63.170.19.36]) by hub.freebsd.org (Postfix) with ESMTP id 3BE9337B446 for ; Fri, 13 Apr 2001 19:06:29 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com [206.159.132.160] by mail.urx.com with ESMTP (SMTPD32-6.06) id A0A0C4020E; Fri, 13 Apr 2001 19:06:24 -0700 Message-ID: <3AD7B0A0.58F03378@urx.com> Date: Fri, 13 Apr 2001 19:06:24 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: chad@DCFinc.com Cc: dak@solo.net, freebsd-stable@FreeBSD.ORG Subject: Re: ports "make index" fails References: <200104140141.SAA19851@freeway.dcfinc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Chad R. Larson" wrote: > > As I recall, Kent Stewart wrote: > >> Now, if someone has a tidy way of dealing with the "README.html" > >> files, I'd be interested. > > > > The readme's are usually built by doing a "make readmes". > > Yes, but then the cvs update complains about those files it knows > nothing about. I do a cvsup ports-all and then cd /usr/ports to do the make index. It usually works. Kent > > -crl > -- > Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? > chad@dcfinc.com chad@larsons.org larson1@home.com > DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 1: 2:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from easystreet01.easystreet.com (easystreet.com [206.26.36.40]) by hub.freebsd.org (Postfix) with ESMTP id DB53037B496 for ; Sat, 14 Apr 2001 01:02:54 -0700 (PDT) (envelope-from tashchuk@easystreet.com) Received: from easystreet.com (dsl-209-162-218-66.easystreet.com [209.162.218.66]) by easystreet01.easystreet.com (8.11.2/8.11.2) with ESMTP id f3E82lL13274; Sat, 14 Apr 2001 01:02:48 -0700 (PDT) Message-ID: <3AD80427.36871745@easystreet.com> Date: Sat, 14 Apr 2001 01:02:47 -0700 From: Bohdan Tashchuk X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "Thomas T. Veldhouse" Cc: Gordon Tetlow , freebsd-stable@FreeBSD.ORG Subject: Re: natd[232]: failed to write packet back (Permission denied) References: <00a601c0c444$4ef9fc40$3028680a@tgt.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running 3.5, so everything may have changed since. But I also had this problem. Somehow the 'rwho' packets cause this. (Man rwho). A simple change to /etc/rc.firewall is all it takes to get rid of this. Here is a snippet of my change: if [ "X${natd_enable}" = X"YES" -a "X${natd_interface}" != X"" ]; then $fwcmd add 10 deny udp from any who to any who via ${natd_interface} $fwcmd add 20 divert natd all from any to any via ${natd_interface} fi "Thomas T. Veldhouse" wrote: > > I was using stateful firewalling. I get even more errors. Oddly, whatever > is causing it now happens in bursts of two every 12 minutes. I have not > figured it out -- really annoying. The default "SIMPLE" firewall also > causes it. That should not be -- so I would call that a bug in the > /etc/rc.firewall script at the very least. > > Tom Veldhouse > veldy@veldy.net > > ----- Original Message ----- > From: "Gordon Tetlow" > To: "Thomas T. Veldhouse" > Cc: > Sent: Friday, April 13, 2001 1:03 PM > Subject: Re: natd[232]: failed to write packet back (Permission denied) > > > But, if you use the default firewall rules, *all* packets get put through > > natd, not just lan traffic, but incoming, and loopback traffic as well. > > > > I used to have this problem, but when I rewrote my firewall rules to use > > stateful firewalling, it disappeared. > > > > -gordon > > > > On Fri, 13 Apr 2001, Thomas T. Veldhouse wrote: > > > > > As an addendum -- I get these messages even when there is NO activity on > the > > > LAN -- so natd is not even being used by any client. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 2:31: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from emma1.emma.line.org (p3EE3CC9E.dip.t-dialin.net [62.227.204.158]) by hub.freebsd.org (Postfix) with ESMTP id E96DA37B50D for ; Sat, 14 Apr 2001 02:31:05 -0700 (PDT) (envelope-from ma@dt.e-technik.uni-dortmund.de) Received: by emma1.emma.line.org (Postfix, from userid 500) id 26C0CA2001; Sat, 14 Apr 2001 11:30:59 +0200 (CEST) To: freebsd-stable@freebsd.org Subject: FreeBSD 4.x refuses to use DMA on WDC31200F? From: Matthias Andree Date: 14 Apr 2001 11:30:59 +0200 Message-ID: Lines: 25 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I recently noticed that FreeBSD 4.x (4.0-RELEASE, 4.2-RELEASE, 4.2-STABLE, currently 4.3-RC) refuses to use DMA to transfer data to/from my Western Digital Caviar AC31200F. This drive is able to do DMA1 or PIO3, for a reason I cannot see and that is neither mentioned in ata(4) or in syslog, even sysctl -w hd.atamodes=dma,---,---,---, does not change FreeBSD's mind. A WDCAC420400D is used in DMA mode (UDMA/33). My system is boots and mounts /, /usr and /var from a SCSI disk attached to a Tekram DC-390 (AMD PCscsiII/53C974). That very same drive can be successfully used in DMA mode with NetBSD 1.5 (same machine) and Linux 2.2.19 (same board type/chipset), I've never seen corruption on that drive with DMA. The drive is attached to a VIA VT82C586B (Apollo MVP3) on a Tyan Trinity 100AT (S1590). What causes FreeBSD's refusal to use DMA? Can I fix that? Can somebody else fix that? -- Matthias Andree To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 2:44: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-21.dsl.lsan03.pacbell.net [63.207.60.21]) by hub.freebsd.org (Postfix) with ESMTP id F306837B449 for ; Sat, 14 Apr 2001 02:43:59 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id CC97466B84; Sat, 14 Apr 2001 14:43:29 -0700 (PDT) Date: Sat, 14 Apr 2001 14:43:29 -0700 From: Kris Kennaway To: Matthias Andree Cc: freebsd-stable@FreeBSD.org Subject: Re: BDECFLAGS break current 4.x-stable build Message-ID: <20010414144328.A792@xor.obsecurity.org> References: <20010409093630.B72961@xor.obsecurity.org> <20010410155318.A2074@burns.dt.e-technik.uni-dortmund.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="T4sUOijqQbZv57TR" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010410155318.A2074@burns.dt.e-technik.uni-dortmund.de>; from matthias.andree@gmx.de on Tue, Apr 10, 2001 at 03:53:18PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 10, 2001 at 03:53:18PM +0200, Matthias Andree wrote: > On Mon, 09 Apr 2001, Kris Kennaway wrote: >=20 > > Submit patches to fix them, then. >=20 > :-} >=20 > Seriously, would these be relevant for 4.x-stable still or would these > better be sent in for 5.x-current? Best do it for 5.0-current, though the majority of userland code is identical between 4.x and 5.x Kris --T4sUOijqQbZv57TR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE62MSAWry0BWjoQKURAqLoAJ4rats7Gi2YWgFjhpbTWFNQL0Ce2wCdG0UM wPeFyVCoFHyxb79VyA/kPQg= =BnhK -----END PGP SIGNATURE----- --T4sUOijqQbZv57TR-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 3:13:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailout02.sul.t-online.com (mailout02.sul.t-online.com [194.25.134.17]) by hub.freebsd.org (Postfix) with ESMTP id A89D137B422; Sat, 14 Apr 2001 03:13:21 -0700 (PDT) (envelope-from sven.huster@mailsurf.com) Received: from fwdtmp0.sul.t-online.com by mailout02.sul.t-online.com with smtp id 14oN3Q-0001Xt-00; Sat, 14 Apr 2001 12:13:20 +0200 Received: from venus.mailsurf.com (320051988339-0001@[62.158.240.16]) by fmrl00.sul.t-online.com with esmtp id 14oN3O-01wiTAC; Sat, 14 Apr 2001 12:13:18 +0200 Message-Id: <5.0.2.1.0.20010414121126.00a64130@mx01.mailsurf.com> X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Sat, 14 Apr 2001 12:13:48 +0200 To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org From: Sven Huster Subject: file cache (on nfs) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Sender: 320051988339-0001@t-dialin.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, can someone tell me how/if file caching is done on freebsd over nfs? are the parameters to modify the behaviour (e.g. memory usage)? are there parameters for "normal" local disk cache also? thanks regards Sven Huster Senior IT Systems Administrator *BSD, Linux, Solaris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 9:29:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id EC61837B422; Sat, 14 Apr 2001 09:28:49 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (chowder.dons.net.au [203.31.81.11]) by midget.dons.net.au (8.11.3/8.9.3) with ESMTP id f3EGSkJ40888; Sun, 15 Apr 2001 01:58:46 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.7 on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=XFMail.1.4.7.FreeBSD:20010415015844:358=_" Date: Sun, 15 Apr 2001 01:58:44 +0930 (CST) From: "Daniel O'Connor" To: freebsd-mobile@freebsd.org Subject: Dell Inspiron 8000 and FreeBSD 4.3 Cc: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.4.7.FreeBSD:20010415015844:358=_ Content-Type: text/plain; charset=us-ascii Hi, I recently got a i8000 for work and so far I am fairly pleased with the success I am having. Currently the internal modem and ethernet work, USB works and X is running. I can't get the sound to work which seems quite odd to me since I can see an ID for a supported soundcard when I do pciconf -l (ie a Maestro 3 - 0x1998125d). I haven't investigated further than boot -v. Inserting a PCMCIA card locks the machine solid (I have only tried a CF adapter card so far). I haven't played with configuring it either (tips gratefully received :) Also, I can't suspend/resume which I am told is because of a BIOS bug which sucks but there's not much to be done about that :) (I can induce a suspend/resume OK but when the laptop comes back the fxp card spits millions of 'SCB timeout' and 'DMA timeout', and it seems the ata controller wedges, or doesn't reinit the controller). Attached is the output of the boot process and my kernel config. --- 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 --_=XFMail.1.4.7.FreeBSD:20010415015844:358=_ Content-Disposition: attachment; filename="dmesg" Content-Transfer-Encoding: 7bit Content-Description: dmesg Content-Type: text/plain; charset=us-ascii; name=dmesg; SizeOnDisk=19348 Apr 15 01:42:24 chowder /kernel: Copyright (c) 1992-2001 The FreeBSD Project. Apr 15 01:42:24 chowder /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 198 9, 1991, 1992, 1993, 1994 Apr 15 01:42:24 chowder /kernel: The Regents of the University of California. Al l rights reserved. Apr 15 01:42:24 chowder /kernel: FreeBSD 4.3-RC #3: Fri Apr 13 23:42:31 CST 2001 Apr 15 01:42:24 chowder /kernel: root@chowder.dons.net.au:/usr/src/sys/compile/C HOWDER Apr 15 01:42:24 chowder /kernel: Calibrating clock(s) ... TSC clock: 698451239 H z, i8254 clock: 1193150 Hz Apr 15 01:42:24 chowder /kernel: CLK_USE_I8254_CALIBRATION not specified - using default frequency Apr 15 01:42:24 chowder /kernel: Timecounter "i8254" frequency 1193182 Hz Apr 15 01:42:24 chowder /kernel: CLK_USE_TSC_CALIBRATION not specified - using o ld calibration method Apr 15 01:42:24 chowder /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (698. 47-MHz 686-class CPU) Apr 15 01:42:24 chowder /kernel: Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Apr 15 01:42:24 chowder /kernel: Features=0x383f9ff Apr 15 01:42:25 chowder /kernel: real memory = 134135808 (130992K bytes) Apr 15 01:42:25 chowder /kernel: Physical memory chunk(s): Apr 15 01:42:25 chowder /kernel: 0x00001000 - 0x0009efff, 647168 bytes (158 page s) Apr 15 01:42:25 chowder /kernel: 0x0030b000 - 0x07fe3fff, 130912256 bytes (31961 pages) Apr 15 01:42:25 chowder /kernel: avail memory = 127627264 (124636K bytes) Apr 15 01:42:25 chowder /kernel: bios32: Found BIOS32 Service Directory header a t 0xc00ffe80 Apr 15 01:42:25 chowder /kernel: bios32: Entry = 0xffe90 (c00ffe90) Rev = 0 Le n = 1 Apr 15 01:42:25 chowder /kernel: pcibios: PCI BIOS entry at 0xc06e Apr 15 01:42:25 chowder /kernel: pnpbios: Found PnP BIOS data at 0xc00fe2d0 Apr 15 01:42:25 chowder /kernel: pnpbios: Entry = f0000:e2f4 Rev = 1.0 Apr 15 01:42:25 chowder /kernel: pnpbios: Event flag at 4b4 Apr 15 01:42:25 chowder /kernel: Other BIOS signatures found: Apr 15 01:42:25 chowder /kernel: ACPI: 000fde50 Apr 15 01:42:25 chowder /kernel: Preloaded elf kernel "kernel" at 0xc02e5000. Apr 15 01:42:25 chowder /kernel: Pentium Pro MTRR support enabled Apr 15 01:42:25 chowder /kernel: pci_open(1): mode 1 addr port (0x0cf8) is 0x800 0fac4 Apr 15 01:42:25 chowder /kernel: pci_open(1a): mode1res=0x80000000 (0x80000000) Apr 15 01:42:25 chowder /kernel: pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=11308086) Apr 15 01:42:25 chowder /kernel: apm0: on motherboard Apr 15 01:42:25 chowder /kernel: apm: found APM BIOS v1.2, connected at v1.2 Apr 15 01:42:26 chowder /kernel: npx0: on motherboard Apr 15 01:42:26 chowder /kernel: npx0: INT 16 interface Apr 15 01:42:26 chowder /kernel: pci_open(1): mode 1 addr port (0x0cf8) is 0x000 00000 Apr 15 01:42:26 chowder /kernel: pci_open(1a): mode1res=0x80000000 (0x80000000) Apr 15 01:42:26 chowder /kernel: pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=11308086) Apr 15 01:42:26 chowder /kernel: pcib0: on motherboard Apr 15 01:42:26 chowder /kernel: found-> vendor=0x8086, dev=0x1130, revid=0x02 Apr 15 01:42:26 chowder /kernel: class=06-00-00, hdrtype=0x00, mfdev=0 Apr 15 01:42:26 chowder /kernel: subordinatebus=0 secondarybus=0 Apr 15 01:42:26 chowder /kernel: map[10]: type 1, range 32, base e4000000, size 26 Apr 15 01:42:26 chowder /kernel: found-> vendor=0x8086, dev=0x1131, revid=0x02 Apr 15 01:42:26 chowder /kernel: class=06-04-00, hdrtype=0x01, mfdev=0 Apr 15 01:42:26 chowder /kernel: subordinatebus=1 secondarybus=1 Apr 15 01:42:26 chowder /kernel: found-> vendor=0x8086, dev=0x2448, revid=0x02 Apr 15 01:42:26 chowder /kernel: class=06-04-00, hdrtype=0x01, mfdev=0 Apr 15 01:42:26 chowder /kernel: subordinatebus=8 secondarybus=2 Apr 15 01:42:27 chowder /kernel: found-> vendor=0x8086, dev=0x244c, revid=0x02 Apr 15 01:42:27 chowder /kernel: class=06-01-00, hdrtype=0x00, mfdev=1 Apr 15 01:42:27 chowder /kernel: subordinatebus=0 secondarybus=0 Apr 15 01:42:27 chowder /kernel: found-> vendor=0x8086, dev=0x244a, revid=0x02 Apr 15 01:42:27 chowder /kernel: class=01-01-80, hdrtype=0x00, mfdev=0 Apr 15 01:42:27 chowder /kernel: subordinatebus=0 secondarybus=0 Apr 15 01:42:27 chowder /kernel: map[20]: type 1, range 32, base 0000bfa0, size 4 Apr 15 01:42:27 chowder /kernel: found-> vendor=0x8086, dev=0x2442, revid=0x02 Apr 15 01:42:27 chowder /kernel: class=0c-03-00, hdrtype=0x00, mfdev=0 Apr 15 01:42:27 chowder /kernel: subordinatebus=0 secondarybus=0 Apr 15 01:42:27 chowder /kernel: intpin=d, irq=11 Apr 15 01:42:27 chowder /kernel: map[20]: type 1, range 32, base 0000bce0, size 5 Apr 15 01:42:27 chowder /kernel: pci0: on pcib0 Apr 15 01:42:27 chowder /kernel: pcib1: at device 1.0 on pci0 Apr 15 01:42:27 chowder /kernel: found-> vendor=0x1002, dev=0x4d46, revid=0x00 Apr 15 01:42:27 chowder /kernel: class=03-00-00, hdrtype=0x00, mfdev=0 Apr 15 01:42:27 chowder /kernel: subordinatebus=0 secondarybus=0 Apr 15 01:42:27 chowder /kernel: intpin=a, irq=11 Apr 15 01:42:27 chowder /kernel: map[10]: type 1, range 32, base e8000000, size 26 Apr 15 01:42:28 chowder /kernel: map[14]: type 1, range 32, base 0000cc00, size 8 Apr 15 01:42:28 chowder /kernel: map[18]: type 1, range 32, base fcffc000, size 14 Apr 15 01:42:28 chowder /kernel: pci1: on pcib1 Apr 15 01:42:28 chowder /kernel: pci1: (ve ndor=0x1002, dev=0x4d46) at 0.0 irq 11 Apr 15 01:42:28 chowder /kernel: pcib2: at device 30.0 on pci0 Apr 15 01:42:28 chowder /kernel: found-> vendor=0x125d, dev=0x1998, revid=0x10 Apr 15 01:42:28 chowder /kernel: class=04-01-00, hdrtype=0x00, mfdev=0 Apr 15 01:42:28 chowder /kernel: subordinatebus=0 secondarybus=0 Apr 15 01:42:28 chowder /kernel: intpin=a, irq=5 Apr 15 01:42:28 chowder /kernel: map[10]: type 1, range 32, base 0000dc00, size 8 Apr 15 01:42:28 chowder /kernel: map[14]: type 1, range 32, base f6ffe000, size 13 Apr 15 01:42:28 chowder /kernel: found-> vendor=0x1668, dev=0x0100, revid=0x11 Apr 15 01:42:28 chowder /kernel: class=06-04-00, hdrtype=0x01, mfdev=0 Apr 15 01:42:28 chowder /kernel: subordinatebus=8 secondarybus=8 Apr 15 01:42:28 chowder /kernel: found-> vendor=0x104c, dev=0xac42, revid=0x00 Apr 15 01:42:28 chowder /kernel: class=06-07-00, hdrtype=0x02, mfdev=1 Apr 15 01:42:28 chowder /kernel: subordinatebus=0 secondarybus=0 Apr 15 01:42:28 chowder /kernel: intpin=a, irq=11 Apr 15 01:42:28 chowder /kernel: found-> vendor=0x104c, dev=0xac42, revid=0x00 Apr 15 01:42:28 chowder /kernel: class=06-07-00, hdrtype=0x02, mfdev=1 Apr 15 01:42:28 chowder /kernel: subordinatebus=0 secondarybus=0 Apr 15 01:42:28 chowder /kernel: intpin=a, irq=11 Apr 15 01:42:29 chowder /kernel: found-> vendor=0x104c, dev=0x8027, revid=0x00 Apr 15 01:42:29 chowder /kernel: class=0c-00-10, hdrtype=0x00, mfdev=1 Apr 15 01:42:29 chowder /kernel: subordinatebus=0 secondarybus=0 Apr 15 01:42:29 chowder /kernel: intpin=a, irq=11 Apr 15 01:42:29 chowder /kernel: map[10]: type 1, range 32, base f6ffd800, size 11 Apr 15 01:42:29 chowder /kernel: map[14]: type 1, range 32, base f6ff8000, size 14 Apr 15 01:42:29 chowder /kernel: pci2: on pcib2 Apr 15 01:42:29 chowder /kernel: pci2: (vendor=0x125d, dev=0x1998 ) at 3.0 irq 5 Apr 15 01:42:29 chowder /kernel: pcib3: at device 6.0 on pci2 Apr 15 01:42:29 chowder /kernel: found-> vendor=0x8086, dev=0x1229, revid=0x08 Apr 15 01:42:29 chowder /kernel: class=02-00-00, hdrtype=0x00, mfdev=0 Apr 15 01:42:29 chowder /kernel: subordinatebus=0 secondarybus=0 Apr 15 01:42:29 chowder /kernel: intpin=a, irq=11 Apr 15 01:42:29 chowder /kernel: map[10]: type 1, range 32, base f8fff000, size 12 Apr 15 01:42:29 chowder /kernel: map[14]: type 1, range 32, base 0000ecc0, size 6 Apr 15 01:42:29 chowder /kernel: map[18]: type 1, range 32, base f8e00000, size 20 Apr 15 01:42:29 chowder /kernel: found-> vendor=0x11c1, dev=0x0448, revid=0x01 Apr 15 01:42:29 chowder /kernel: class=07-80-00, hdrtype=0x00, mfdev=0 Apr 15 01:42:29 chowder /kernel: subordinatebus=0 secondarybus=0 Apr 15 01:42:29 chowder /kernel: intpin=a, irq=11 Apr 15 01:42:29 chowder /kernel: map[10]: type 1, range 32, base f8ffec00, size 8 Apr 15 01:42:29 chowder /kernel: map[14]: type 3, range 32, base 0000ecb8, size 3 Apr 15 01:42:29 chowder /kernel: map[18]: type 1, range 32, base 0000e800, size 8 Apr 15 01:42:29 chowder /kernel: pci8: on pcib3 Apr 15 01:42:29 chowder /kernel: fxp0: port 0x ecc0-0xecff mem 0xf8e00000-0xf8efffff,0xf8fff000-0xf8ffffff irq 11 at device 4.0 on pci8 Apr 15 01:42:29 chowder /kernel: fxp0: Ethernet address 00:20:e0:65:13:1d Apr 15 01:42:30 chowder /kernel: bpf: fxp0 attached Apr 15 01:42:30 chowder /kernel: pci8: (vendor=0x11c1, dev=0x0448 ) at 8.0 irq 11 Apr 15 01:42:30 chowder /kernel: chip1: irq 11 at device 15.0 on pci2 Apr 15 01:42:30 chowder /kernel: chip2: irq 11 at device 15.1 on pci2 Apr 15 01:42:30 chowder /kernel: pci2: (vendor=0x104c, dev=0x8027 ) at 15.2 irq 11 Apr 15 01:42:30 chowder /kernel: isab0: at device 31.0 on pci0 Apr 15 01:42:30 chowder /kernel: isa0: on isab0 Apr 15 01:42:30 chowder /kernel: atapci0: port 0xbf a0-0xbfaf at device 31.1 on pci0 Apr 15 01:42:30 chowder /kernel: ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xb fa0 Apr 15 01:42:30 chowder /kernel: ata0: mask=03 status0=50 status1=50 Apr 15 01:42:30 chowder /kernel: ata0: mask=03 ostat0=50 ostat2=50 Apr 15 01:42:30 chowder /kernel: ata0-slave: ATAPI probe a=14 b=eb Apr 15 01:42:30 chowder /kernel: ata0-master: ATAPI probe a=00 b=00 Apr 15 01:42:30 chowder /kernel: ata0: mask=03 status0=50 status1=00 Apr 15 01:42:30 chowder /kernel: ata0-master: ATA probe a=01 b=a5 Apr 15 01:42:30 chowder /kernel: ata0: devices=09 Apr 15 01:42:30 chowder /kernel: ata0: at 0x1f0 irq 14 on atapci0 Apr 15 01:42:30 chowder /kernel: ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xb fa8 Apr 15 01:42:30 chowder /kernel: ata1: mask=00 status0=ff status1=ff Apr 15 01:42:30 chowder /kernel: ata1: probe allocation failed Apr 15 01:42:30 chowder /kernel: pci0: (vendor=0x8086, dev =0x2442) at 31.2 irq 11 Apr 15 01:42:30 chowder /kernel: ata-: ata0 exists, using next available unit nu mber Apr 15 01:42:30 chowder /kernel: ata-: ata1 exists, using next available unit nu mber Apr 15 01:42:31 chowder /kernel: Trying Read_Port at 203 Apr 15 01:42:31 chowder /kernel: Trying Read_Port at 243 Apr 15 01:42:31 chowder /kernel: Trying Read_Port at 283 Apr 15 01:42:31 chowder /kernel: Trying Read_Port at 2c3 Apr 15 01:42:31 chowder /kernel: Trying Read_Port at 303 Apr 15 01:42:31 chowder /kernel: Trying Read_Port at 343 Apr 15 01:42:31 chowder /kernel: Trying Read_Port at 383 Apr 15 01:42:31 chowder /kernel: Trying Read_Port at 3c3 Apr 15 01:42:31 chowder /kernel: isa_probe_children: disabling PnP devices Apr 15 01:42:31 chowder /kernel: isa_probe_children: probing non-PnP devices Apr 15 01:42:31 chowder /kernel: fdc0: at port 0x3f0-0x3f5 ,0x3f7 irq 6 drq 2 on isa0 Apr 15 01:42:31 chowder /kernel: fdc0: FIFO enabled, 8 bytes threshold Apr 15 01:42:31 chowder /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Apr 15 01:42:31 chowder /kernel: ata2 failed to probe at port 0x1f0 irq 14 on is a0 Apr 15 01:42:31 chowder /kernel: ata3: iobase=0x0170 altiobase=0x0376 bmaddr=0x0 000 Apr 15 01:42:31 chowder /kernel: ata3: mask=00 status0=ff status1=ff Apr 15 01:42:31 chowder /kernel: ata3: probe allocation failed Apr 15 01:42:31 chowder /kernel: ata3 failed to probe at port 0x170-0x177,0x376 irq 15 on isa0 Apr 15 01:42:31 chowder /kernel: atkbdc0: at port 0x60,0x64 on isa0 Apr 15 01:42:31 chowder /kernel: atkbd0: flags 0x1 irq 1 on atkbdc 0 Apr 15 01:42:31 chowder /kernel: atkbd: the current kbd controller command byte 0065 Apr 15 01:42:31 chowder /kernel: atkbd: keyboard ID 0x41ab (2) Apr 15 01:42:32 chowder /kernel: kbd0: atkbd0, AT 101/102 (2), config:0x1, flags :0x3d0000 Apr 15 01:42:32 chowder /kernel: psm0: current command byte:0065 Apr 15 01:42:32 chowder /kernel: psm0: irq 12 on atkbdc0 Apr 15 01:42:32 chowder /kernel: psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons Apr 15 01:42:32 chowder /kernel: psm0: config:00000000, flags:00000000, packet s ize:3 Apr 15 01:42:32 chowder /kernel: psm0: syncmask:c0, syncbits:00 Apr 15 01:42:32 chowder /kernel: vga0: at port 0x3c0-0x3df iom em 0xa0000-0xbffff on isa0 Apr 15 01:42:32 chowder /kernel: fb0: vga0, vga, type:VGA (5), flags:0x7007f Apr 15 01:42:32 chowder /kernel: fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 Apr 15 01:42:32 chowder /kernel: fb0: init mode:24, bios mode:3, current mode:24 Apr 15 01:42:32 chowder /kernel: fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k Apr 15 01:42:32 chowder /kernel: vga0: vga: WARNING: video mode switching is not fully supported on this adapter Apr 15 01:42:32 chowder /kernel: VGA parameters upon power-up Apr 15 01:42:32 chowder /kernel: 50 18 10 00 00 00 03 00 02 67 6f 4f 4f 93 55 c3 Apr 15 01:42:32 chowder /kernel: 9e 1f 00 4f 0d 0e 00 00 07 80 8f 82 8f 28 1f 8f Apr 15 01:42:32 chowder /kernel: 9f a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Apr 15 01:42:32 chowder /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff Apr 15 01:42:32 chowder /kernel: VGA parameters in BIOS for mode 24 Apr 15 01:42:32 chowder /kernel: 50 18 0e 00 10 01 03 00 02 a3 5f 4f 50 82 55 81 Apr 15 01:42:32 chowder /kernel: bf 1f 00 4d 0b 0c 00 00 00 00 83 85 5d 28 1f 63 Apr 15 01:42:32 chowder /kernel: ba a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Apr 15 01:42:33 chowder /kernel: 3d 3e 3f 08 00 0f 00 00 00 00 00 00 10 0e 00 ff Apr 15 01:42:33 chowder /kernel: EGA/VGA parameters to be used for mode 24 Apr 15 01:42:33 chowder /kernel: 50 18 10 00 00 00 03 00 02 67 6f 4f 4f 93 55 c3 Apr 15 01:42:33 chowder /kernel: 9e 1f 00 4f 0d 0e 00 00 07 80 8f 82 8f 28 1f 8f Apr 15 01:42:33 chowder /kernel: 9f a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Apr 15 01:42:33 chowder /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff Apr 15 01:42:33 chowder /kernel: sc0: at flags 0x100 on isa0 Apr 15 01:42:33 chowder /kernel: sc0: VGA <16 virtual consoles, flags=0x300> Apr 15 01:42:33 chowder /kernel: sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) Apr 15 01:42:33 chowder /kernel: pcic0: at port 0x3e0 iomem 0xd000 0 on isa0 Apr 15 01:42:33 chowder /kernel: pcic0: Polling mode Apr 15 01:42:33 chowder /kernel: stat is 0 Apr 15 01:42:33 chowder /kernel: stat is 0 Apr 15 01:42:33 chowder /kernel: pccard0: on pci c0 Apr 15 01:42:33 chowder /kernel: pccard1: on pci c0 Apr 15 01:42:33 chowder /kernel: pcic1: not probed (disabled) Apr 15 01:42:33 chowder /kernel: sio0: configured irq 4 not in bitmap of probed irqs 0 Apr 15 01:42:33 chowder /kernel: sio0: irq maps: 0x200 0x200 0x200 0x200 Apr 15 01:42:33 chowder /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on is a0 Apr 15 01:42:33 chowder /kernel: sio0: type 16550A Apr 15 01:42:33 chowder /kernel: sio1: configured irq 3 not in bitmap of probed irqs 0 Apr 15 01:42:33 chowder /kernel: sio1: irq maps: 0x200 0x200 0x200 0x200 Apr 15 01:42:33 chowder /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Apr 15 01:42:34 chowder /kernel: sio1: type 16550A Apr 15 01:42:34 chowder /kernel: ppc0: parallel port found at 0x378 Apr 15 01:42:34 chowder /kernel: ppc0: using extended I/O port range Apr 15 01:42:34 chowder /kernel: ppc0: ECP SPP ECP+EPP SPP Apr 15 01:42:34 chowder /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 Apr 15 01:42:34 chowder /kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Apr 15 01:42:34 chowder /kernel: ppc0: FIFO with 16/16/8 bytes threshold Apr 15 01:42:34 chowder /kernel: lpt0: on ppbus0 Apr 15 01:42:34 chowder /kernel: lpt0: Interrupt-driven port Apr 15 01:42:34 chowder /kernel: ppi0: on ppbus0 Apr 15 01:42:34 chowder /kernel: isa_probe_children: probing PnP devices Apr 15 01:42:34 chowder /kernel: BIOS Geometries: Apr 15 01:42:34 chowder /kernel: 0:03fefe3f 0..1022=1023 cylinders, 0..254=255 h eads, 1..63=63 sectors Apr 15 01:42:34 chowder /kernel: 0 accounted for Apr 15 01:42:34 chowder /kernel: Device configuration finished. Apr 15 01:42:34 chowder /kernel: bpf: lo0 attached Apr 15 01:42:34 chowder /kernel: ata0-master: DMA limited to UDMA33, non-ATA66 c ompliant cable Apr 15 01:42:34 chowder /kernel: Creating DISK ad0 Apr 15 01:42:34 chowder /kernel: Creating DISK wd0 Apr 15 01:42:34 chowder /kernel: ad0: ATA-5 disk at ata0 -master Apr 15 01:42:34 chowder /kernel: ad0: 9590MB (19640880 sectors), 19485 cyls, 16 heads, 63 S/T, 512 B/S Apr 15 01:42:34 chowder /kernel: ad0: 16 secs/int, 1 depth queue, BIOSDMA Apr 15 01:42:34 chowder /kernel: ad0: piomode=4 dmamode=2 udmamode=4 cblid=0 Apr 15 01:42:34 chowder /kernel: ad0: 9590MB [19485/16/63] at ata 0-master BIOSDMA Apr 15 01:42:34 chowder /kernel: ata0-slave: piomode=4 dmamode=2 udmamode=2 dmaf lag=1 Apr 15 01:42:34 chowder /kernel: ata0-slave: success setting PIO4 on generic chi p Apr 15 01:42:34 chowder /kernel: acd0: CDROM drive at ata0 as slave Apr 15 01:42:34 chowder /kernel: acd0: read 4134KB/s (4134KB/s), 128KB buffer, P IO4 Apr 15 01:42:34 chowder /kernel: acd0: Reads: CD-R, CD-RW, CD-DA stream, packet Apr 15 01:42:34 chowder /kernel: acd0: Audio: play, 256 volume levels Apr 15 01:42:35 chowder /kernel: acd0: Mechanism: ejectable tray Apr 15 01:42:35 chowder /kernel: acd0: Medium: no/blank disc inside, unlocked Apr 15 01:42:35 chowder /kernel: Mounting root from ufs:/dev/ad0s2a Apr 15 01:42:35 chowder /kernel: ad0s1: type 0xb, start 289170, end = 8675099, s ize 8385930 : OK Apr 15 01:42:35 chowder /kernel: ad0s2: type 0xa5, start 8675100, end = 19631429 , size 10956330 : OK Apr 15 01:42:35 chowder /kernel: start_init: trying /sbin/init Apr 15 01:42:38 chowder /kernel: uhci0: port 0xb ce0-0xbcff irq 11 at device 31.2 on pci0 Apr 15 01:42:38 chowder /kernel: uhci0: (New UHCI DeviceId=0x24428086) Apr 15 01:42:38 chowder /kernel: using shared irq11. Apr 15 01:42:38 chowder /kernel: usb0: on uhci0 Apr 15 01:42:38 chowder /kernel: usb0: USB revision 1.0 Apr 15 01:42:38 chowder /kernel: uhub0: (0x24428086) UHCI root hub, class 9/0, r ev 1.00/1.00, addr 1 Apr 15 01:42:38 chowder /kernel: uhub0: 2 ports with 2 removable, self powered Apr 15 01:42:55 chowder /kernel: Linux-ELF exec handler installed Apr 15 01:42:55 chowder /kernel: ltmdm0: port 0xe800-0xe8ff,0 xecb8-0xecbf mem 0xf8ffec00-0xf8ffecff irq 11 at device 8.0 on pci8 Apr 15 01:42:55 chowder /kernel: ltmdm0: using SHARED IRQ. Apr 15 01:42:55 chowder /kernel: ltmdm0: type Virtual 16550A --_=XFMail.1.4.7.FreeBSD:20010415015844:358=_ Content-Disposition: attachment; filename="CHOWDER" Content-Transfer-Encoding: 7bit Content-Description: CHOWDER Content-Type: text/plain; charset=us-ascii; name=CHOWDER; SizeOnDisk=2794 machine i386 cpu I686_CPU ident CHOWDER maxusers 64 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options INCLUDE_CONFIG_FILE options USER_LDT options DDB options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING device isa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0 at atkbdc? irq 12 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 # 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? flags 0x20 # Advanced Power Management # PCCARD (PCMCIA) support device card device pcic0 at isa? irq 0 port 0x3e0 iomem 0xd0000 device pcic1 at isa? irq 0 port 0x3e2 iomem 0xd4000 disable # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer device ppi # Parallel port interface device device fxp # Intel EtherExpress PRO/100B (82557, 82558) device pcm # Pseudo devices - the number indicates how many units to allocate. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device bpf # Berkeley packet filter pseudo-device snp # Snoop device device smbus # Bus support, required for smb below. device intpm device ichsmb device smb device iicbus # Bus support, required for ic/iic/iicsmb below. device iicbb device ic device iic device iicsmb # smb over i2c bridge --_=XFMail.1.4.7.FreeBSD:20010415015844:358=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 10:44: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from klima.physik.uni-mainz.de (klima.Physik.Uni-Mainz.DE [134.93.180.162]) by hub.freebsd.org (Postfix) with ESMTP id B805C37B449; Sat, 14 Apr 2001 10:43:53 -0700 (PDT) (envelope-from ohartman@klima.physik.uni-mainz.de) Received: from mail.Physik.Uni-Mainz.DE (Linux@mail.Physik.Uni-Mainz.DE [134.93.180.161]) by klima.physik.uni-mainz.de (8.11.3/8.11.3) with ESMTP id f3EHhqT01279; Sat, 14 Apr 2001 19:43:53 +0200 (CEST) (envelope-from ohartman@klima.physik.uni-mainz.de) Date: Sat, 14 Apr 2001 19:43:52 +0200 (CEST) From: "Hartmann, O." X-X-Sender: To: Cc: Subject: CPU type settings problems, suggestion Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Sirs. Again, I run into light problems with setting CPUTYPE in /etc/make.conf. The history: We use several machines with DUAL CPUs, some Intel chip based servers and several machines with AMD Duron (our X terminals) and AMD TBird CPUs. On each 'architecture' I compile the appropriate kernel and base system with CPUTYPE set to the right architecture. And for each package out of the port's tree I use this option, too. All boxes running FreeBSD 4.3-RC as cvsupdated these days, the last update was done today. Mk-base has been updated also, the ports-collection was deleted and reinstalled twice this day! Fact: On Intel based systems I can compile _each_ packet with CPUTYPE set to 'pentiumpro', that means for us for the appropriate architecture. On AMD based system this is not working today! I had to disable the CPUTYPE tag in /etc/make.conf to compile packages (I did so with XFree86-4, gimp1 (?), Mesa3). I come alongside with this problem and switch between nothing and k7/k6 for packages that will not compile with CPUTYPE set on AMD machines. If it is disabled, all things run all right! My suggestion: FreeBSD now has two switches for kernel compilation and other stuff, base system of the UNIX included. We should migrate to three switches: one for kernel compilation, a second for the OS as we do it recently, and a third for stuff out of the ports collection. I can compile both kernel and the base UNIX with the appropriate CPU switch set, but not serveral ports. Each machine does not share its kernel! Each machine should not share its basic System, butwithin our system's architecture and organisation we share several filesystems with packages to keep all system 'on the same status' (means up to date). I think many others do so, too. For the time FreeBSD will really take profits from real optimisations by setting CPUTYPE, kernel and base OS should be tuned up to its limits by that way (or as the Gurus want us to be tuned). But the ports should also be 'tuned' or 'not tuned' by an individual switch. Sorry about my english, hope you can understand what I'm trying to explain. Thanks, Oliver -- MfG O. Hartmann ohartman@klima.physik.uni-mainz.de ---------------------------------------------------------------- IT-Administration des Institut fuer Physik der Atmosphaere (IPA) ---------------------------------------------------------------- Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinensaal) Tel: +496131/3924144 FAX: +496131/3923532 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 13:23:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id C87FD37B50B; Sat, 14 Apr 2001 13:23:30 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f3EKLQG12995; Sat, 14 Apr 2001 13:22:31 -0700 (PDT) (envelope-from jhb@FreeBSD.org) 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: Sat, 14 Apr 2001 13:20:54 -0700 (PDT) From: John Baldwin To: "Daniel O'Connor" Subject: RE: Dell Inspiron 8000 and FreeBSD 4.3 Cc: freebsd-stable@FreeBSD.org, freebsd-mobile@FreeBSD.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Apr-01 Daniel O'Connor wrote: > Hi, > I recently got a i8000 for work and so far I am fairly pleased with the > success > I am having. Currently the internal modem and ethernet work, USB works and X > is > running. > > I can't get the sound to work which seems quite odd to me since I can see an > ID > for a supported soundcard when I do pciconf -l (ie a Maestro 3 - 0x1998125d). > I > haven't investigated further than boot -v. The maestro3 requires a GPL'd header so you have to kldload it's module separately I think or some such. > Inserting a PCMCIA card locks the machine solid (I have only tried a CF > adapter > card so far). I haven't played with configuring it either (tips gratefully > received :) Hrm, pccard works fine on my 5000e. > Also, I can't suspend/resume which I am told is because of a BIOS bug which > sucks but there's not much to be done about that :) > (I can induce a suspend/resume OK but when the laptop comes back the fxp card > spits millions of 'SCB timeout' and 'DMA timeout', and it seems the ata > controller wedges, or doesn't reinit the controller). This doesn't sound like the 5000e kernel bug, which panics the kernel as soon as you try to do anything with apm. The problems do seem to indicate a problem where the hardware isn't being rewoken properly. Not sure if that is a BIOS bug or a software bug though. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 14:20:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id AFD9F37B509; Sat, 14 Apr 2001 14:20:33 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id RAA29258; Sat, 14 Apr 2001 17:19:54 -0400 (EDT) Date: Sat, 14 Apr 2001 17:19:53 -0400 (EDT) From: Daniel Eischen To: John Baldwin Cc: "Daniel O'Connor" , freebsd-stable@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: RE: Dell Inspiron 8000 and FreeBSD 4.3 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 14 Apr 2001, John Baldwin wrote: > > On 14-Apr-01 Daniel O'Connor wrote: > > Inserting a PCMCIA card locks the machine solid (I have only tried a CF > > adapter > > card so far). I haven't played with configuring it either (tips gratefully > > received :) > > Hrm, pccard works fine on my 5000e. Locks up the Dell Latitude C800 also unless you give the pcic devices an irq instead of using polling. This is under 4.3-stable; I haven't tried -current. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 14:40:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from be-well.ilk.org (lowellg.ne.mediaone.net [24.147.184.128]) by hub.freebsd.org (Postfix) with ESMTP id CF27A37B505; Sat, 14 Apr 2001 14:40:12 -0700 (PDT) (envelope-from lowell@be-well.ilk.org) Received: (from lowell@localhost) by be-well.ilk.org (8.11.3/8.11.3) id f3ELeCW08303; Sat, 14 Apr 2001 17:40:12 -0400 (EDT) (envelope-from lowell) To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Reply-To: freebsd-questions@freebsd.org Subject: Re: natd[232]: failed to write packet back (Permission denied) References: <9b7b3i$2kli$1@FreeBSD.csie.NCTU.edu.tw> From: Lowell Gilbert Date: 14 Apr 2001 17:40:12 -0400 In-Reply-To: veldy@veldy.net's message of "14 Apr 2001 00:56:18 +0800" Message-ID: <44eluvqhxf.fsf@lowellg.ne.mediaone.net> Lines: 38 X-Mailer: Gnus v5.7/Emacs 20.7 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG veldy@veldy.net ("Thomas T. Veldhouse") writes: > Apr 13 10:47:37 fuggle natd[232]: failed to write packet back (Permission > denied) > Apr 13 10:47:46 fuggle last message repeated 4 times > Apr 13 10:47:47 fuggle su: veldy to root on /dev/ttyp0 > Apr 13 10:47:58 fuggle natd[232]: failed to write packet back (Permission > denied) > Apr 13 10:48:31 fuggle last message repeated 3 times > > > Can anybody explain what causes this? I have look through archive after > archive and have found many many reports of this problem, but no solution. > The closest I have come is a message that says to check the firewall rules > to see what is blocking packets passed back from natd. This cannot be it > because I have added rules after the natd divert to open everything and this > still occurs. That is *exactly* what causes this message. Check your rules again -- and do it with 'ipfw l', not just by looking at your your firewall configuration script, because the auto-incrementing numbering may not have done quite what you expected. [I've made this mistake a number of times.] Also, make sure that the "open everything" rule is numbered higher than the divert rule. It won't work at all if they're at the same number. If the machines behind the NAT are sharing the same public address as the NAT machine itself, and you don't need them to accept connections initiated from the outside Internet, then it should be perfectly possible to set up your ipfw rules to avoid this. > Please help -- this fills logs and is a nuisance -- it has been a problem > ever since at least 4.1.1. Sounds like it's not a -stable problem, then. Let's move this over to -questions instead... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 15:11:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mta6.srv.hcvlny.cv.net (mta6.srv.hcvlny.cv.net [167.206.5.17]) by hub.freebsd.org (Postfix) with ESMTP id 0C12637B43E for ; Sat, 14 Apr 2001 15:11:22 -0700 (PDT) (envelope-from trini0@optonline.net) Received: from optonline.net (ool-18be012f.dyn.optonline.net [24.190.1.47]) by mta6.srv.hcvlny.cv.net (iPlanet Messaging Server 5.0 Patch 2 (built Dec 14 2000)) with ESMTP id <0GBS0049AYYZH5@mta6.srv.hcvlny.cv.net> for stable@freebsd.org; Sat, 14 Apr 2001 18:11:24 -0400 (EDT) Date: Sat, 14 Apr 2001 18:11:20 -0400 From: trini0 Subject: What do you think? To: Stable Message-id: <3AD8CB08.2030209@optonline.net> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_FcRxxPFw4ei3y9KFlbjtUQ)" X-Accept-Language: en User-Agent: Mozilla/5.0 (X11; U; FreeBSD 4.2-RELEASE i386; en-US; 0.8.1) Gecko/20010411 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --Boundary_(ID_FcRxxPFw4ei3y9KFlbjtUQ) Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT Hey all. This message popped up on the console today. Never had a problem with this box before. Im running 4.3RC (as of Monday) on a PPro200 with an Intel VS440FX chipset. I rebuilt the kernel without DMA support on Thursday, and this came up on Friday. I didnt provide support for dma via sysctl (Im still looking at what needs to be done...its a newbie thing). Just wanted to make you aware, just in case its a 'bug' before 4.3 gets clamped down. Thanks trini0 --Boundary_(ID_FcRxxPFw4ei3y9KFlbjtUQ) Content-type: text/plain; name=error-1.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=error-1.txt Apr 13 16:15:58 hivemind /kernel: ata0-master: timeout waiting to give command=ca s=80 e=04 Apr 13 16:15:58 hivemind /kernel: ad0: error executing command - resetting Apr 13 16:15:58 hivemind /kernel: ata0: resetting devices .. done --Boundary_(ID_FcRxxPFw4ei3y9KFlbjtUQ)-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 15:14:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209]) by hub.freebsd.org (Postfix) with SMTP id E87A537B446 for ; Sat, 14 Apr 2001 15:14:29 -0700 (PDT) (envelope-from karsten@rohrbach.de) Received: (qmail 29507 invoked by uid 1000); 14 Apr 2001 22:14:49 -0000 Date: Sun, 15 Apr 2001 00:14:49 +0200 From: "Karsten W. Rohrbach" To: freebsd-stable@freebsd.org Subject: 4.3-RC2 install freezes on sony vaio c1xd Message-ID: <20010415001449.B27762@mail.webmonster.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Arbitrary-Number-Of-The-Day: 42 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i have strange things happening when trying to run a freebsd install from boot floppies on my vaio c1xd. the kern.flp will find a loader and load the kernel, then ask me for the mfsroot.flp which also gets read in without a problem (the floppy on the vaio is a y-e flashbuster usb device which has boot support in the system bios for real mode). then the kernel would start, but all that happens is, that the box locks up. it is not dependent on the pcmcia card inserted and i disabled the pnp os setting in bios. the lockup is hard, so i got to switch it off an on again, keyboard is not resonding as a matter of fact, too. the 4.2-RELEASE boot floppies work, btw. any ideas how i can track this one down or if this happens with other vaios as well? i will try to boot the install cd when i got my burner at work so i can create a boot cd later next week. /k -- > Parts that don't exist can't break. -- Russell Nelson KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de [Key] [KeyID---] [Created-] [Fingerprint-------------------------------------] GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 BF46 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 15:24:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-21.dsl.lsan03.pacbell.net [63.207.60.21]) by hub.freebsd.org (Postfix) with ESMTP id D2F3237B509 for ; Sat, 14 Apr 2001 15:24:20 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5B0FB66DA4; Sat, 14 Apr 2001 15:24:20 -0700 (PDT) Date: Sat, 14 Apr 2001 15:24:20 -0700 From: Kris Kennaway To: trini0 Cc: Stable Subject: Re: What do you think? Message-ID: <20010414152420.A16838@xor.obsecurity.org> References: <3AD8CB08.2030209@optonline.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="J/dobhs11T7y2rNN" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AD8CB08.2030209@optonline.net>; from trini0@optonline.net on Sat, Apr 14, 2001 at 06:11:20PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --J/dobhs11T7y2rNN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 14, 2001 at 06:11:20PM -0400, trini0 wrote: > Hey all. This message popped up on the console today. Never had a > problem with this box before. Im running 4.3RC (as of Monday) on a > PPro200 with an Intel VS440FX chipset. I rebuilt the kernel without DMA > support on Thursday, and this came up on Friday. I didnt provide > support for dma via sysctl (Im still looking at what needs to be > done...its a newbie thing). Just wanted to make you aware, just in case > its a 'bug' before 4.3 gets clamped down. Thanks > trini0 >=20 >=20 > Apr 13 16:15:58 hivemind /kernel: ata0-master: timeout waiting to give co= mmand=3Dca s=3D80 e=3D04 > Apr 13 16:15:58 hivemind /kernel: ad0: error executing command - resetting > Apr 13 16:15:58 hivemind /kernel: ata0: resetting devices .. done Your IDE controller needed to be reset because it wasn't responding properly to commands. IDE hardware is often pretty marginal. Kris --J/dobhs11T7y2rNN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE62M4TWry0BWjoQKURAuEyAKDD2IoNzZ+m9IGtF2axkQreoPnKJwCg5ygw HdspH8vr560DZqaE9Z0xPuY= =cQGr -----END PGP SIGNATURE----- --J/dobhs11T7y2rNN-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 15:49:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 7933A37B59E for ; Sat, 14 Apr 2001 15:49:40 -0700 (PDT) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id PAA23095; Sat, 14 Apr 2001 15:49:05 -0700 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda23093; Sat Apr 14 15:49:00 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.2/8.9.1) id f3EMmtB46520; Sat, 14 Apr 2001 15:48:55 -0700 (PDT) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdR46518; Sat Apr 14 15:48:17 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.3/8.9.1) id f3EMmFK63219; Sat, 14 Apr 2001 15:48:15 -0700 (PDT) Message-Id: <200104142248.f3EMmFK63219@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdq63114; Sat Apr 14 15:48:10 2001 X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: schubert To: Jason Nugent Cc: freebsd-stable@FreeBSD.ORG Subject: Re: a word of appreciation In-reply-to: Your message of "Thu, 12 Apr 2001 10:05:09 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Apr 2001 15:48:10 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Jason Nu gent writes: > > Folks, > > I'm not sure how much you get of this, but I just wanted to say thanks to > all of you working on the freebsd project. You do fine work. I'm not > sure how often you get to hear that, so I'm going to say it now. > > I just finished a routine upgrade of my FreeBSD 4.1.1-RELEASE machine to > 4.3-RC, in order to make sure that the circulated ftp glob() vulnerability > wouldn't affect my system. > > I'm curious, though, if the lib-paranoia library in the ports collection > would have prevented the exploit from happening in the first place. Has > anyone experimented with this? I've been using FreeBSD since 2.0.5. I've been very pleased with the quality of the O/S. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 15:54:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from krycek.zoominternet.net (krycek.zoominternet.net [63.67.120.9]) by hub.freebsd.org (Postfix) with SMTP id 4F5E337B449 for ; Sat, 14 Apr 2001 15:54:26 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 1755 invoked from network); 14 Apr 2001 22:54:10 -0000 Received: from acs-24-154-35-93.zoominternet.net (HELO cvzoom.net) (24.154.35.93) by krycek.zoominternet.net with SMTP; 14 Apr 2001 22:54:10 -0000 Message-ID: <3AD8D520.F39A45D5@cvzoom.net> Date: Sat, 14 Apr 2001 18:54:24 -0400 From: Donn Miller X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Cy Schubert - ITSD Open Systems Group Cc: Jason Nugent , freebsd-stable@FreeBSD.ORG Subject: Re: a word of appreciation References: <200104142248.f3EMmFK63219@cwsys.cwsent.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cy Schubert - ITSD Open Systems Group wrote: > I've been using FreeBSD since 2.0.5. I've been very pleased with the > quality of the O/S. Yep, same here. Wasn't 2.0.5 from around May '95? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 16: 3:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail8.nc.rr.com (fe8.southeast.rr.com [24.93.67.55]) by hub.freebsd.org (Postfix) with ESMTP id 988DB37B423 for ; Sat, 14 Apr 2001 16:03:20 -0700 (PDT) (envelope-from aa8vb@nc.rr.com) Received: from stealth.dummynet ([24.25.3.190]) by mail8.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Sat, 14 Apr 2001 19:00:08 -0400 Received: (from rhh@localhost) by stealth.dummynet (8.11.1/8.11.1) id f3EN4cB07031 for stable@freebsd.org; Sat, 14 Apr 2001 19:04:38 -0400 (EDT) (envelope-from aa8vb@nc.rr.com) X-Authentication-Warning: stealth.dummynet: rhh set sender to aa8vb@nc.rr.com using -f Date: Sat, 14 Apr 2001 19:04:38 -0400 From: Randall Hopper To: stable@freebsd.org Subject: Multi-CD Backup Utility (?) Message-ID: <20010414190437.A6932@nc.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone have a multi-CD backup utility you use on FreeBSD? I'm looking for something to make the process of backing up partitions larger than 650MB/700MB to CDR/CDRW as painless from possible. Thanks, Randall -- Randall Hopper aa8vb@nc.rr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 18:40:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 081CB37B506; Sat, 14 Apr 2001 18:40:53 -0700 (PDT) (envelope-from DougB@DougBarton.net) Received: from DougBarton.net (master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id SAA33602; Sat, 14 Apr 2001 18:40:49 -0700 (PDT) (envelope-from DougB@DougBarton.net) Message-ID: <3AD8FC21.D96E72C0@DougBarton.net> Date: Sat, 14 Apr 2001 18:40:49 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Jordan Hubbard Cc: stable@FreeBSD.ORG, newton@FreeBSD.ORG Subject: Re: Anyone interested in the SVR4 compat module anymore? References: <200104131637.f3DGbPt04946@winston.osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan Hubbard wrote: > > I'm just now noticing (I so rarely turn it on) that the svr4 ABI > module is broken - you get "link_elf: symbol svr4_stream_get undefined" > when you try to load it. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=26215 -- Perhaps the greatest damage the American system of education has done to its children is to teach them that their opinions are relevant simply because they are their opinions. Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 18:49:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id 6872E37B505 for ; Sat, 14 Apr 2001 18:49:17 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by probity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14obfA-000DlU-00 for freebsd-stable@freebsd.org; Sun, 15 Apr 2001 02:49:16 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f3F1nFB48550 for freebsd-stable@freebsd.org; Sun, 15 Apr 2001 02:49:15 +0100 (BST) (envelope-from jcm) Date: Sun, 15 Apr 2001 02:49:15 +0100 From: j mckitrick To: freebsd-stable@freebsd.org Subject: major lockup from pccard Message-ID: <20010415024915.A48446@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maybe this is just me. I am running a world cvsupped Mar 31. I have a Toshiba 4010CDT with the usual Noteworthy PCcard modem. The following sequence causes a complete lockup right in the middle of the message onscreen that the kernel is setting up sio2. shutdown now [return] ctrl-d it skips disk checks, goes to start the network, and hangs while checking the sio serial port. Could someone else check this with another laptop? -- ----------------------------------------------------------- Jonathon McKitrick -- jcm@freebsd-uk.eu.org Bill's Law - "The speed of Windows halves every 18 months." ----------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 19:42:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hobbits.brel.com (hobbits.brel.com [203.127.231.61]) by hub.freebsd.org (Postfix) with ESMTP id BACE437B422; Sat, 14 Apr 2001 19:42:05 -0700 (PDT) (envelope-from calvinng@hobbits.brel.com) Received: by hobbits.brel.com (Postfix, from userid 1001) id 37C793435; Sun, 15 Apr 2001 10:41:47 +0800 (SGT) Date: Sun, 15 Apr 2001 10:41:47 +0800 From: Calvin NG To: freebsd-mobile@FreeBSD.ORG Cc: Daniel O'Connor , freebsd-stable@FreeBSD.ORG Subject: Re: Dell Inspiron 8000 and FreeBSD 4.3 Message-ID: <20010415104147.C2823@brel.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.ORG on Sat, Apr 14, 2001 at 01:20:54PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, I have a Dell 8000, and I just figured the module part out too and got sound working. My Way: ------ in /boot/loader.conf, I have a line that says, snd_pcm_load="YES" This loads the pcm module way in advance, (before kernel, I think), then , I have to edit a file /etc/rc.local (create it if not there), and add the following line, /sbin/kldload snd_maestro3 Which loads the sound driver towards the end of system startup. BTW, I also have the lines, /usr/sbin/mixer vol 45:45 /usr/sbin/mixer speaker 45:45 to adjust the volume, so it isn't too loud. The default is about 75:75 which is way too loud for me. I didn't compile "device pcm" into the kernel. Correct Way: ----------- Okay, supposedly, you only need to edit /boot/locder.conf, and add the line snd_maestro3_load="YES" It will load the dependency, which is "pcm" correctly. It loaded the modules okay, but then I get terrible screeching sounds, or static, when I play sound, so it didn't seem quite like. I figure out after a while that it probably has to do with the order of the modules loading (I tried and error by hand), and that I need to load the pcm module way in advance, then after that load the maestro3 module. Tried but didn't work --------------------- tried this already, in /booot/loader.conf, snd_pcm_load="YES" snd_maestro3_load="YES" tried editing /usr/src/sys/conf/files, and added one line as follows, dev/sound/pci/maestro.c optional pcm pci ++ dev/sound/pci/maestro.c optional pcm pci dev/sound/pci/neomagic.c optional pcm pci That compiles the maestro3 driver, and detected correctly, but get the static too. Anyway, the above is what I have tried. Good luck to you, Daniel. Hope this helps. ps: Haven't tried any PCMCIA though. also, resume is not working for me too, I think someone reported it very recently. Regards, /calvin lines with :> are quotes from John Baldwin's email :> :> On 14-Apr-01 Daniel O'Connor wrote: :> > Hi, :> > I recently got a i8000 for work and so far I am fairly pleased with the :> > success :> > I am having. Currently the internal modem and ethernet work, USB works and X :> > is :> > running. :> > :> > I can't get the sound to work which seems quite odd to me since I can see an :> > ID :> > for a supported soundcard when I do pciconf -l (ie a Maestro 3 - 0x1998125d). :> > I :> > haven't investigated further than boot -v. :> :> The maestro3 requires a GPL'd header so you have to kldload it's module :> separately I think or some such. :> :> > Inserting a PCMCIA card locks the machine solid (I have only tried a CF :> > adapter :> > card so far). I haven't played with configuring it either (tips gratefully :> > received :) :> :> Hrm, pccard works fine on my 5000e. :> :> > Also, I can't suspend/resume which I am told is because of a BIOS bug which :> > sucks but there's not much to be done about that :) :> > (I can induce a suspend/resume OK but when the laptop comes back the fxp card :> > spits millions of 'SCB timeout' and 'DMA timeout', and it seems the ata :> > controller wedges, or doesn't reinit the controller). :> :> This doesn't sound like the 5000e kernel bug, which panics the kernel as soon :> as you try to do anything with apm. The problems do seem to indicate a problem :> where the hardware isn't being rewoken properly. Not sure if that is a BIOS :> bug or a software bug though. :> :> -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 20:22:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from c000.sfo.cp.net (c004-h007.c004.snv.cp.net [209.228.33.71]) by hub.freebsd.org (Postfix) with SMTP id 7114537B443 for ; Sat, 14 Apr 2001 20:22:53 -0700 (PDT) (envelope-from psglenn@uswestmail.net) Received: (cpmta 20513 invoked from network); 14 Apr 2001 20:22:52 -0700 Date: 14 Apr 2001 20:22:52 -0700 Message-ID: <20010415032252.20512.cpmta@c000.sfo.cp.net> X-Sent: 15 Apr 2001 03:22:52 GMT Received: from [64.40.57.177] by mail.uswestmail.net with HTTP; 14 Apr 2001 20:22:52 PDT Content-Type: text/plain Content-Disposition: inline Mime-Version: 1.0 To: freebsd-stable@FreeBSD.org From: psglenn@uswestmail.net X-Mailer: Web Mail 3.7.1.9 Subject: /weekly/310locate truncates db Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, my weekly 310.locate script using defaults in /etc/locate.rc produces a database which contains only a few file systems output I'm not yet sure when this stopped working but I wonder if anyone else is seeing this ? Now after reading man locate I know that if directories are not readable by user `nobody' find will skip them but the 'ls / ' below shows world readability, and I'm actually not sure that makes perfect sense let paranoia tell it. But this system is not permanently connected. P S Glenn uname -a FreeBSD big.psf.his.org 4.3-RC FreeBSD 4.3-RC #3: Tue Apr 3 01:10:08 PDT 2001 root@big.psf.his.org:/usr/src/sys/compile/BIG i386 < the truncated database > (after sh /etc/periodic/weekly/310.locate) ls /var/db/locate.database -r--r--r-- 1 nobody wheel 342 Apr 14 17:56 /var/db/locate.database locate -s Database: /var/db/locate.database Compression: Front: 61.95%, Bigram: 84.21%, Total: 38.05% Filenames: 16, Characters: 226, Database size: 342 Bigram characters: 54, Integers: 2, 8-Bit characters: 0 using find / -print | /usr/libexec/locate.mklocatedb > locate.database gives me everything. With no pruning . ls /root/locate.datbase -r--r--r-- 1 root wheel 946136 Apr 14 17:56 locate.database locate -s -d /root/locate.database Database: locate.database Compression: Front: 18.35%, Bigram: 63.21%, Total: 13.41% Filenames: 164591, Characters: 7051714, Database size: 946136 Bigram characters: 348087, Integers: 2154, 8-Bit characters: 0 df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad4s1a 297663 60230 213620 22% / /dev/ad4s2g 5356477 2538747 2389212 52% /back /dev/ad4s1g 5485853 875935 4171050 17% /usr /dev/ad4s2e 2032623 175324 1694690 9% /usr/ports /dev/ad4s2f 2032623 244018 1625996 13% /usr/ports/distfiles /dev/ad4s1e 297663 3334 270516 1% /var /dev/ad6s1g 5830989 302753 5061757 6% /backup procfs 4 4 0 100% /proc /dev/ad6s1e 1016303 296786 638213 32% /usr/obj /dev/ad4s1f 3048942 29160 2775867 1% /home /dev/ad6s1f 1016303 10 934989 0% /tmp ls / total 8482 drwxr-xr-x 22 root wheel 512 Apr 14 02:30 ./ drwxr-xr-x 22 root wheel 512 Apr 14 02:30 ../ -rw-r--r-- 2 root wheel 802 Mar 26 22:58 .cshrc -rw-r--r-- 2 root wheel 251 Nov 20 04:03 .profile -r--r--r-- 1 root wheel 4735 Nov 20 04:03 COPYRIGHT drwxr-xr-x 3 root wheel 512 Apr 7 12:40 back/ drwxr-xr-x 2 root wheel 512 Apr 14 18:13 backup/ drwxr-xr-x 2 root wheel 1024 Apr 14 02:31 bin/ drwxr-xr-x 3 root wheel 512 Apr 14 02:37 boot/ drwxr-xr-x 2 root wheel 512 Mar 26 17:06 cdrom/ drwxr-xr-x 2 root wheel 512 Mar 26 17:06 cdrom1/ lrwxr-xr-x 1 root wheel 11 Mar 26 17:12 compat@ -> /usr/compat drwxr-xr-x 4 root wheel 15360 Apr 14 18:04 dev/ drwxr-xr-x 2 root wheel 512 Mar 26 17:07 dist/ drwxr-xr-x 18 root wheel 2560 Apr 14 18:30 etc/ drwxr-xr-x 4 root wheel 512 Apr 14 18:28 home/ -r-xr-xr-x 1 root wheel 2721956 Apr 9 23:11 kernel* -r-xr-xr-x 1 root wheel 3258128 Nov 20 05:02 kernel.GENERIC* -r-xr-xr-x 1 root wheel 2613771 Apr 5 02:21 kernel.old* drwxr-xr-x 2 root wheel 512 Nov 20 03:56 mnt/ drwxr-xr-x 2 root wheel 3072 Apr 9 23:11 modules/ drwxr-xr-x 2 root wheel 3072 Mar 31 18:46 modules.old/ lrwxr-xr-x 1 root wheel 10 Mar 27 09:50 ports@ -> /usr/ports dr-xr-xr-x 1 root wheel 512 Apr 14 19:55 proc/ drwxr-xr-x 17 root wheel 1024 Apr 14 19:52 root/ drwxr-xr-x 2 root wheel 2048 Apr 14 02:35 sbin/ drwxr-xr-x 4 root wheel 1024 Apr 8 21:01 stand/ lrwxr-xr-x 1 root wheel 11 Apr 14 02:29 sys@ -> usr/src/sys drwxrwxrwt 2 root wheel 512 Apr 14 19:53 tmp/ drwxr-xr-x 18 root wheel 512 Mar 26 17:57 usr/ drwxr-xr-x 18 root wheel 512 Nov 20 05:13 var/ That's all for now. Signup for your free USWEST.mail Email account http://www.uswestmail.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 20:30:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id 8327E37B42C; Sat, 14 Apr 2001 20:30:27 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (chowder.dons.net.au [203.31.81.11]) by midget.dons.net.au (8.11.3/8.9.3) with ESMTP id f3F3UKJ48506; Sun, 15 Apr 2001 13:00:20 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.7 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010415104147.C2823@brel.com> Date: Sun, 15 Apr 2001 13:00:16 +0930 (CST) From: "Daniel O'Connor" To: Calvin NG Subject: Re: Dell Inspiron 8000 and FreeBSD 4.3 Cc: freebsd-stable@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15-Apr-2001 Calvin NG wrote: > My Way: > ------ > in /boot/loader.conf, I have a line that says, > snd_pcm_load="YES" > This loads the pcm module way in advance, (before kernel, I think), Yes. > then , I have to edit a file /etc/rc.local (create it if not there), > and add the following line, > /sbin/kldload snd_maestro3 > Which loads the sound driver towards the end of system startup. Hmm OK. > I figure out after a while that it probably has to do with > the order of the modules loading (I tried and error by hand), > and that I need to load the pcm module way in advance, then > after that load the maestro3 module. Hmm.. that shouldn't be the case.. Maybe you have a slightly out of date system? > Good luck to you, Daniel. Hope this helps. Yep, I loaded the module and sounds works great now :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 20:39:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id C9EAF37B446; Sat, 14 Apr 2001 20:39:16 -0700 (PDT) (envelope-from darius@dons.net.au) Received: from cain.gsoft.com.au (chowder.dons.net.au [203.31.81.11]) by midget.dons.net.au (8.11.3/8.9.3) with ESMTP id f3F3dFJ48590; Sun, 15 Apr 2001 13:09:15 +0930 (CST) (envelope-from darius@dons.net.au) Message-ID: X-Mailer: XFMail 1.4.7 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: Sun, 15 Apr 2001 13:09:10 +0930 (CST) From: "Daniel O'Connor" To: John Baldwin Subject: RE: Dell Inspiron 8000 and FreeBSD 4.3 Cc: freebsd-mobile@FreeBSD.org, freebsd-stable@FreeBSD.org, "Daniel O'Connor" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Apr-2001 John Baldwin wrote: > The maestro3 requires a GPL'd header so you have to kldload it's module > separately I think or some such. Yep.. Forgot the PCM module loading stuff was MFC'd, thanks. > > card so far). I haven't played with configuring it either (tips gratefully > > received :) > Hrm, pccard works fine on my 5000e. Yeah, I found out mine works when you give it an IRQ :) > > spits millions of 'SCB timeout' and 'DMA timeout', and it seems the ata > > controller wedges, or doesn't reinit the controller). > This doesn't sound like the 5000e kernel bug, which panics the kernel as > soon > as you try to do anything with apm. The problems do seem to indicate a > problem > where the hardware isn't being rewoken properly. Not sure if that is a BIOS > bug or a software bug though. Yeah, any idea how I find out which one it is, and how I can fix it? :) I pine for suspend to disk 8-) --- 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-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 20:45:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tomts7-srv.bellnexxia.net (tomts7.bellnexxia.net [209.226.175.40]) by hub.freebsd.org (Postfix) with ESMTP id 2322737B509 for ; Sat, 14 Apr 2001 20:45:57 -0700 (PDT) (envelope-from blaue@sympatico.ca) Received: from sympatico.ca ([64.228.94.144]) by tomts7-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010415034551.VYDB8469.tomts7-srv.bellnexxia.net@sympatico.ca>; Sat, 14 Apr 2001 23:45:51 -0400 Message-ID: <3AD91987.F4533EF8@sympatico.ca> Date: Sat, 14 Apr 2001 23:46:15 -0400 From: Brad Laue X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: Lowell Gilbert , freebsd-stable@freebsd.org Subject: Re: [freebsd-stable] FreeBSD 4.3RC out of buffer space in network operations References: <9b7aqs$2khu$1@FreeBSD.csie.NCTU.edu.tw> <44hezrqigm.fsf@lowellg.ne.mediaone.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lowell Gilbert wrote: > blaue@sympatico.ca (Brad Laue) writes: > > > Good thing you have a way out of it - unfortunately my PPPoE connection tunnels > > through ed0, so it's my only public route to the internet :( Hoping this gets > > noticed before -RELEASE > > Are you sure it's a serious problem? From what you guys are saying, > it sounds like you just need more mbufs... Yes, it's very serious - netstat -m shows no overrun of any buffers, nor does it demonstrate the need for additional space - everything is under 10% capacity. As I mentioned, I have already maximized my buffer settings to a point where this server would be able to handle a midsized network, rather than a mere DSL modem. MAXUSERS= 256 options NMBCLUSTERS="16384" Further, this problem didn't occur before the last two cvsups. Any further input is welcome. Brad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 20:59: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from h24-69-46-74.gv.shawcable.net (h24-69-46-74.gv.shawcable.net [24.69.46.74]) by hub.freebsd.org (Postfix) with ESMTP id C536B37B42C for ; Sat, 14 Apr 2001 20:59:00 -0700 (PDT) (envelope-from michael@tenzo.com) Received: from h24-69-46-74.gv.shawcable.net (localhost.gv.shawcable.net [127.0.0.1]) by h24-69-46-74.gv.shawcable.net (8.11.1/8.11.1) with SMTP id f3F41W200742 for ; Sat, 14 Apr 2001 21:01:32 -0700 (PDT) (envelope-from michael@tenzo.com) Content-Type: text/plain; charset="iso-8859-1" From: "Michael O'Henly" Reply-To: michael@tenzo.com Organization: TENZO Design To: freebsd-stable@FreeBSD.ORG Subject: Problem setting up printer... Date: Sat, 14 Apr 2001 21:01:32 -0700 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <01041421013201.00431@h24-69-46-74.gv.shawcable.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to troubleshoot the difficulty I'm having setting up printing under FreeBSD 4.2. An answer to this question would save me a lot of grief. ;-) I have a native Postscript printer (HP 4050) and I've created a simple Postscript test file using an example from the Handbook. The question is: if I'm able to print successfully this way... cat printerTest.ps > /dev/lpt0 ...does this rule out misconfiguration of the kernel? If so, then I'll concentrate on my config files. Thanks. M. -- Michael O'Henly TENZO Design To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 20:59:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from h24-69-46-74.gv.shawcable.net (h24-69-46-74.gv.shawcable.net [24.69.46.74]) by hub.freebsd.org (Postfix) with ESMTP id 24E9637B449 for ; Sat, 14 Apr 2001 20:59:39 -0700 (PDT) (envelope-from michael@tenzo.com) Received: from h24-69-46-74.gv.shawcable.net (localhost.gv.shawcable.net [127.0.0.1]) by h24-69-46-74.gv.shawcable.net (8.11.1/8.11.1) with SMTP id f3F42B200746 for ; Sat, 14 Apr 2001 21:02:11 -0700 (PDT) (envelope-from michael@tenzo.com) Content-Type: text/plain; charset="iso-8859-1" From: "Michael O'Henly" Reply-To: michael@tenzo.com Organization: TENZO Design To: freebsd-stable@FreeBSD.ORG Subject: Printer madness... Date: Sat, 14 Apr 2001 21:02:11 -0700 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <01041421021102.00431@h24-69-46-74.gv.shawcable.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi... I'm trying to set up printing with FreeBSD 4.2 and an HP LaserJet 4050 connected to the parallel port. I've been following the procedure in the Handbook -- but I'm having some trouble... Here's what I've done so far: 1. Compiled a new kernel with these options: # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt0 # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device device vpo # Requires scbus and da (As you can see, there are options enabled that I don't need. My approach so far has been to get the basic services running, then go back and turn off the things I don't need.) 2. When I do 'dmesg | grep lpt' I get this: lpt0: on ppbus0 lpt0: Interrupt-driven port 3. I've done '/dev/MAKEDEV lpt0' and checked to make sure it worked: # ls -asl /dev/lpt* 0 crw------- 1 root wheel 16, 0 Apr 14 19:23 /dev/lpt0 0 crw------- 1 root wheel 16, 1 Apr 12 15:05 /dev/lpt1 0 crw------- 1 root wheel 16, 2 Apr 12 15:05 /dev/lpt2 4. Tested communication to printer by printing a test Postscript file: # cat testPrinter.ps > /dev/lpt0 No problems with this. 5. Created the following /etc/printcap entry: lp|hp4050|HP LaserJet 4050:\ :sh:\ :lp=/dev/lpt0:\ :sd=/var/spool/lpd/lp:\ :lf=/var/log/lp-errs:\ :if=/usr/local/libexec/psif:\ :df=/usr/local/libexec/psdf:\ :tf=/usr/local/libexec/pstf: FWIW, I've tested the following pared-down version as well (with identical results): lp:\ :sh:\ :lp=/dev/lpt0:\ sd=/var/spool/lpd/lp: 6. Made a spooling directory and made it private to the print daemon: # mkdir /var/spool/lpd/lp # chmod 770 /var/spool/lpd/lp 7. Installed and made executable some print filters. (Note that I've tested without filter entries in /etc/printcap and had identical resutls.) 8. Added to /etc/rc.conf: lpd_enable="YES" 9. Rebooted. 10. At this point, tests like "lptest 20 5 | lpr -Plp" and even just 'lpr' result in 'lpr: lp: unknown printer '. I'm stumped. Any advice? Thanks. M. -- Michael O'Henly TENZO Design To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 21:18:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from web1106.mail.yahoo.com (web1106.mail.yahoo.com [128.11.23.126]) by hub.freebsd.org (Postfix) with SMTP id 1395337B440 for ; Sat, 14 Apr 2001 21:18:16 -0700 (PDT) (envelope-from galen_sampson@yahoo.com) Received: (qmail 837 invoked by uid 60001); 15 Apr 2001 04:18:15 -0000 Message-ID: <20010415041815.836.qmail@web1106.mail.yahoo.com> Received: from [209.247.139.200] by web1106.mail.yahoo.com; Sat, 14 Apr 2001 21:18:15 PDT Date: Sat, 14 Apr 2001 21:18:15 -0700 (PDT) From: Galen Sampson Subject: Re: natd[232]: failed to write packet back (Permission denied) To: freebsd-questions@freebsd.org Cc: lowell@world.std.com, freebsd-stable@freebsd.org In-Reply-To: <44eluvqhxf.fsf@lowellg.ne.mediaone.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I had this problem after installing a make buildworld from 4/12. With "open" firewall rules in rc.conf. I realized that I had changed my rc.conf to only load specific interfaces instead of "auto". This meant that the loopback wasn't up. As soon as I brought the loopback up messages dissapeared. Hope this helps. Regards, Galen --- Lowell Gilbert wrote: > veldy@veldy.net ("Thomas T. Veldhouse") writes: > > > Apr 13 10:47:37 fuggle natd[232]: failed to write packet back (Permission > > denied) > > Apr 13 10:47:46 fuggle last message repeated 4 times > > Apr 13 10:47:47 fuggle su: veldy to root on /dev/ttyp0 > > Apr 13 10:47:58 fuggle natd[232]: failed to write packet back (Permission > > denied) > > Apr 13 10:48:31 fuggle last message repeated 3 times > > > > > > Can anybody explain what causes this? I have look through archive after > > archive and have found many many reports of this problem, but no solution. > > The closest I have come is a message that says to check the firewall rules > > to see what is blocking packets passed back from natd. This cannot be it > > because I have added rules after the natd divert to open everything and > this > > still occurs. > > That is *exactly* what causes this message. Check your rules again -- > and do it with 'ipfw l', not just by looking at your your firewall > configuration script, because the auto-incrementing numbering may not > have done quite what you expected. [I've made this mistake a number > of times.] > > Also, make sure that the "open everything" rule is numbered higher > than the divert rule. It won't work at all if they're at the same > number. > > If the machines behind the NAT are sharing the same public address as > the NAT machine itself, and you don't need them to accept connections > initiated from the outside Internet, then it should be perfectly > possible to set up your ipfw rules to avoid this. > > > Please help -- this fills logs and is a nuisance -- it has been a problem > > ever since at least 4.1.1. > > Sounds like it's not a -stable problem, then. Let's move this over to > -questions instead... > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message __________________________________________________ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 21:57: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cx587235-a.chnd1.az.home.com (cx587235-a.chnd1.az.home.com [24.1.255.253]) by hub.freebsd.org (Postfix) with ESMTP id 335D637B42C for ; Sat, 14 Apr 2001 21:57:01 -0700 (PDT) (envelope-from jjreynold@home.com) Received: from home.com (whale [192.168.1.2]) by cx587235-a.chnd1.az.home.com (8.11.3/8.11.3) with ESMTP id f3F4uv410222; Sat, 14 Apr 2001 21:56:58 -0700 (MST) (envelope-from jjreynold@home.com) Message-ID: <3AD92A1B.421B8051@home.com> Date: Sat, 14 Apr 2001 21:56:59 -0700 From: John Reynolds X-Mailer: Mozilla 4.76 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Randall Hopper Cc: stable@freebsd.org Subject: Re: Multi-CD Backup Utility (?) References: <20010414190437.A6932@nc.rr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Randall Hopper wrote: > > Does anyone have a multi-CD backup utility you use on FreeBSD? > > I'm looking for something to make the process of backing up partitions > larger than 650MB/700MB to CDR/CDRW as painless from possible. I have a script that recursively decends down a given tree and then "partitions" all the files it finds (using whole directories of files if possible) into CD-sized chunks--it then uses this information to create files that mkisofs could use. You basically do things one "partition" at a time with mkisofs | cdrecord. I routinely "backup" all my Gigs of MP3 files onto N CD-RW discs. I've never actually backed up /usr in this manner, but I've run the script on /usr just to see "what it would do" and it did pretty well (in terms of memory and runtime). The script is in REALLY poor shape as far as user friendliness. I have been meaning to clean it up and integrate it into the flexbackup port that I maintain, but just haven't had time (for a long time ... :( ). If you'd like to grab it from me, just sent private e-mail. -Jr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 22: 4:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gloria.cord.edu (gloria.cord.edu [138.129.254.6]) by hub.freebsd.org (Postfix) with ESMTP id 3CB8337B50D; Sat, 14 Apr 2001 22:04:15 -0700 (PDT) (envelope-from twschulz@gloria.cord.edu) Received: from localhost (twschulz@localhost) by gloria.cord.edu (8.10.1/8.10.1) with ESMTP id f3F53pa14901; Sun, 15 Apr 2001 00:03:55 -0500 (CDT) Date: Sun, 15 Apr 2001 00:03:50 -0500 (CDT) From: Trenton Schulz To: "Daniel O'Connor" Cc: , Subject: Re: Dell Inspiron 8000 and FreeBSD 4.3 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 15 Apr 2001, Daniel O'Connor wrote: > Hi, > I recently got a i8000 for work and so far I am fairly pleased with the success > I am having. Currently the internal modem and ethernet work, USB works and X is > running. Just wondering? But does your Inspiron 8000 use the ATI Mobility and have a builtin DVD drive? I had a couple problems that I can't seem to figure out, and haven't annoyed me enough to do something about it... With X, sometimes, when I'm leaving the graphics mode(switching consoles or ending my X session) the screen does a fade to a nice bright white and locks up the machine, causing me to swear and hard reboot the notebook. This is with XFree86 4.0.2 on up (I couldn't get a configuration to work with XFree86-3). I'm wondering if it's my hardware or XFree86-4 not as ready for primetime status. My DVD drive isn't detected unless I wait for about a minute to boot the kernel (by setting the autoboot to 60). If I don't wait that long then I get "ad0 identity retires exceeded" or something along those lines (don't have the dmesg handy :( It didn't happen when I installed from a 4.0 disk I had hanging around, nor if you use the old wd drivers From the archives it sounds like it is a bug that crept in around the end of August 2000 and has stuck around. The annoying part was that I was gonna try and see what happened in the offending part of code, but since it took me longer that an minute to get there the probe succeeds and I couldn't figure out what happened (I'm not a seasoned kernel debugger). Anyway just wondering if anyone else is having a problem. Other than that, everything I use it for works peachy (never had a problem w/sound, I used the old maestro3 driver and the current one). > > Also, I can't suspend/resume which I am told is because of a BIOS bug which > sucks but there's not much to be done about that :) > (I can induce a suspend/resume OK but when the laptop comes back the fxp card > spits millions of 'SCB timeout' and 'DMA timeout', and it seems the ata > controller wedges, or doesn't reinit the controller). > > Attached is the output of the boot process and my kernel config. > > --- > 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 > -- Trenton Schulz twschulz@cord.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 22:21:41 2001 Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 6343D37B42C; Sat, 14 Apr 2001 22:21:35 -0700 (PDT) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 276EA6ACB8; Sun, 15 Apr 2001 14:51:24 +0930 (CST) Date: Sun, 15 Apr 2001 14:51:24 +0930 From: Greg Lehey To: Daniel O'Connor Cc: freebsd-mobile@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Dell Inspiron 8000 and FreeBSD 4.3 Message-ID: <20010415145124.A12250@wantadilla.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from doconnor@gsoft.com.au on Sun, Apr 15, 2001 at 01:58:44AM +0930 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 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 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 15 April 2001 at 1:58:44 +0930, Daniel O'Connor wrote: > Hi, > I recently got a i8000 for work and so far I am fairly pleased with the success > I am having. Currently the internal modem and ethernet work, USB works and X is > running. > > I can't get the sound to work which seems quite odd to me since I can see an ID > for a supported soundcard when I do pciconf -l (ie a Maestro 3 - 0x1998125d). I > haven't investigated further than boot -v. > > Inserting a PCMCIA card locks the machine solid (I have only tried a CF adapter > card so far). I haven't played with configuring it either (tips gratefully > received :) I've just finished some unsuccessful playing around with my CF adaptor in my I7500. It worked fine with -STABLE and -CURRENT up to the last build (end of December), but I upgraded to a recent -CURRENT with NEWCARD a couple of days ago, and now inserting the CF adaptor freezes the machine and causes it to reboot. Booting with the adaptor installed causes a panic during the probes. I'm still investigating, but I'll keep you posted. If you want, bring the equipment out here and we'll play around with it :-) 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-stable" in the body of the message From owner-freebsd-stable Sat Apr 14 22:43:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 545C637B506 for ; Sat, 14 Apr 2001 22:43:09 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 94252 invoked by uid 100); 15 Apr 2001 05:43:08 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15065.13548.269098.225788@guru.mired.org> Date: Sun, 15 Apr 2001 00:43:08 -0500 To: michael@tenzo.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Printer madness... In-Reply-To: <01041421021102.00431@h24-69-46-74.gv.shawcable.net> References: <01041421021102.00431@h24-69-46-74.gv.shawcable.net> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael O'Henly types: > Hi... > 4. Tested communication to printer by printing a test Postscript file: > > # cat testPrinter.ps > /dev/lpt0 > > No problems with this. Which means that everything up to that point is right. > 5. Created the following /etc/printcap entry: > > lp|hp4050|HP LaserJet 4050:\ > :sh:\ > :lp=/dev/lpt0:\ > :sd=/var/spool/lpd/lp:\ > :lf=/var/log/lp-errs:\ > :if=/usr/local/libexec/psif:\ > :df=/usr/local/libexec/psdf:\ > :tf=/usr/local/libexec/pstf: > > FWIW, I've tested the following pared-down version as well (with identical > results): The filters are a bit odd. Do you really expect to do a lot of troff & tex, as compared to everything else? If not, I'd recommend using magifilter from the ports tree. Just use one of the hp postscript printer drivers - 4m, probably. I don't know if the 4050 is 600 or 1200dpi, but that should be the only thing you have to change.n > lp:\ > :sh:\ > :lp=/dev/lpt0:\ > sd=/var/spool/lpd/lp: > > 6. Made a spooling directory and made it private to the print daemon: > > # mkdir /var/spool/lpd/lp > # chmod 770 /var/spool/lpd/lp group and owner? > 7. Installed and made executable some print filters. (Note that I've tested > without filter entries in /etc/printcap and had identical resutls.) Unless the 4050 lost the ability to print flat ascii, it shouldn't matter much. Any reasonable filter will just forward the ascii, possibly with Unix->MSDOS EOL translation. If you're missing that, you should get stairsteps. > 8. Added to /etc/rc.conf: > > lpd_enable="YES" > > 9. Rebooted. Ugh. Overkill.... > 10. At this point, tests like "lptest 20 5 | lpr -Plp" and even just 'lpr' > result in 'lpr: lp: unknown printer '. > > I'm stumped. Any advice? Check the system log files to see if it says anything else. Check "lpc status all" to see what it can see. Make sure that your printcap doesn't have anything in it that might be screwing things up. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message