From owner-freebsd-stable Sun Mar 19 0:11:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from moek.pir.net (moek.pir.net [209.192.237.190]) by hub.freebsd.org (Postfix) with ESMTP id 3DF9237B60F for ; Sun, 19 Mar 2000 00:11:37 -0800 (PST) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 12WaoB-0005Ys-00 for FreeBSD-STABLE@FreeBSD.ORG; Sun, 19 Mar 2000 03:11:35 -0500 Date: Sun, 19 Mar 2000 03:11:35 -0500 From: Peter Radcliffe To: FreeBSD-STABLE@FreeBSD.ORG Subject: Re: SMP oddity Message-ID: <20000319031135.A20988@pir.net> Reply-To: freebsd-stable@freebsd.org Mail-Followup-To: FreeBSD-STABLE@FreeBSD.ORG References: <200003191700.LAA15601@aurora.sol.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003191700.LAA15601@aurora.sol.net>; from jgreco@ns.sol.net on Sun, Mar 19, 2000 at 11:00:47AM -0600 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 Joe Greco probably said: > Sun FE nearly hysterical once... got called in to replace a disk and he > just HAD to open up the machine to find out why the banner reported _3_ > CPU's (I don't think there's a blessed configuration with 3, maybe there > is)... No, there isn't. Sun have always said that the processor modules in a 10 or 20 must be identical. Some other configurations work (when the MBUS speed is the same), but are not supported. Since you can only put two modules in, blessed configurations have 1, 2 or 4 CPUs, all processors identical. > found a dual CPU card plus one rather faster single CPU, and swore > that the disk problem ("the disk is DEAD, Jim") might be caused by my > creative CPU engineering. Heard the one about the DEC Field Circus engineer with a flat tire ? He's the one changing the tires one by one to see which one is flat. Heard the one about the DEC Field Circus engineer with a dead battery ? He's the one changing the tires one by one to see which one is flat. > Note that Solaris didn't have any idea how to deal with the CPU's from a > scheduling point of view: it scheduled them all fairly equally, which > wasn't exactly ideal, but better than it would have been with only two > CPU's. If all your CPUs are identical, which sun say they must be, then this is fine. Not ideal, but they have an excuse. Both of my home sparc 20s are (suprisingly for me) running in supported processor configurations (4x50MHz and 2x75MHz). gmake -j4 is my friend. 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 Sun Mar 19 0:18:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 06C9337B5E6; Sun, 19 Mar 2000 00:18:08 -0800 (PST) (envelope-from jim@nasby.net) Received: from nasby.net (sysnasby@2.nasby.dsl.enteract.com [216.80.51.18]) by mail.enteract.com (8.9.3/8.9.3) with ESMTP id CAA82960; Sun, 19 Mar 2000 02:18:06 -0600 (CST) (envelope-from jim@nasby.net) Message-ID: <38D48D3D.1DBA8F5D@nasby.net> Date: Sun, 19 Mar 2000 02:18:05 -0600 From: "Jim C. Nasby" Organization: distributed.net X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en-US,en MIME-Version: 1.0 To: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Subject: 3.4-4.0 and vinum Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For those of you who are running vinum, make damn sure you keep an old kernel around while upgrading... it seems that you can't load vinum after booting with the new kernel... I'm hoping that a make install in the vinum directory will remedy this situation... I'll post an update once I know what's going on, but in the meantime, this is a heads-up for everyone running vinum. -- 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 Mar 19 0:27:14 2000 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 143C737B528 for ; Sun, 19 Mar 2000 00:27:09 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 19 Mar 2000 08:27:06 +0000 (GMT) Date: Sun, 19 Mar 2000 08:27:06 +0000 From: David Malone To: "Art Neilson, WH7N" Cc: stable@freebsd.org Subject: Re: net.inet.tcp.always_keepalive: 1 Message-ID: <20000319082706.A67837@walton.maths.tcd.ie> References: <3.0.6.32.20000318074032.00916500@pilikia.hi.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3.0.6.32.20000318074032.00916500@pilikia.hi.net>; from art@pilikia.hi.net on Sat, Mar 18, 2000 at 07:40:32AM -1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 18, 2000 at 07:40:32AM -1000, Art Neilson, WH7N wrote: > I've been running 3.4-Stable for a while now and finally updated my > /etc/defaults/rc.conf from /usr/src/etc/defaults/rc.conf. I noticed > the new sysctl toggles in the conf file, and was wondering what this one > in particular did? I thought keepalive packets were for systems connected > up to providers who whould time them out if they had no activity for x > length of time. The comment here seems to indicate it is for cleanup > of dead connections. Can someone enlighten me or point me to relevant doc? If you have tcp keepalives on, the tcp stack will periodically check that the machine at the other end of an idle tcp connection is still there. If it has gone away it will shut down the connection. There are other sysctl settings which control how long a tcp connection must be idle before it is checked, and how many checks are done before the connection is shut down. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 0:36:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 769F437B612 for ; Sun, 19 Mar 2000 00:36:44 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id DAA220300 for ; Sun, 19 Mar 2000 03:36:39 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: Date: Sun, 19 Mar 2000 03:37:04 -0500 To: stable@freebsd.org From: Garance A Drosihn Subject: 4.0-release vs ftp5.freebsd.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I (finally) got the new HD I've been waiting for, and wanted to do a fresh install of freebsd-4 on it. I got the floppies from the 4.0-release directory (probably off ftp.freebsd.org), and used them to boot up. Initially I thought I'd use ftp5.freebsd.org, thinking that was "closer" to me. The install was not able to find most of the things it was trying to install (like "Can't find /bin, do you want to try again?"). Interestingly enough, it WAS able to find XFree86, so it installed that. It may have also installed ports, but in any case the result certainly wasn't going to go anywhere. I just changed my options back to use ftp.freebsd.org, and the install seems to be going along fine. Doing a quick comparison of the two sites, I don't see why 4.0-RELEASE would work coming from one and not the other. This is not an urgent problem or anything, but I thought it was odd enough that I'd mention it. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 0:49:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 0ACC737BC52 for ; Sun, 19 Mar 2000 00:49:46 -0800 (PST) (envelope-from jim@nasby.net) Received: from nasby.net (sysnasby@2.nasby.dsl.enteract.com [216.80.51.18]) by mail.enteract.com (8.9.3/8.9.3) with ESMTP id CAA84328 for ; Sun, 19 Mar 2000 02:49:41 -0600 (CST) (envelope-from jim@nasby.net) Message-ID: <38D494A5.FE9796CD@nasby.net> Date: Sun, 19 Mar 2000 02:49:41 -0600 From: "Jim C. Nasby" Organization: distributed.net X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en-US,en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: 3.4-4.0 and vinum References: <38D48D3D.1DBA8F5D@nasby.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, I got vinum to start by doing a 'cd /usr/src/sys/modules/vinum && make install' (after booting back to a 3.4 GENERIC kernel). I can now get vinum to load, but it won't mount anything... the error it gives is 'Cannot get device list: cannot allocate memory'... I'm guessing that some library needs to be installed as well. I'm way to tired to try trouble-shooting this anymore tonight (last thing I want to do is destroy my volumes :) ), but if anyone has any ideas I'd love to hear them. FWIW, I'd followed all the steps in /usr/src/UPDATING up to and including ''... the only variations were that for building/installing the kernel, I used make buildkernel from /usr/src (as well as make installkernel), and I just did a MAKEDEV all (I don't have any IDE drives on this box; though dmesg is now saying something about an IDE device... guess I still have one of the controllers enabled in the BIOS). Also, sorry for cross-posting my previous message to -questions as well as -stable, but I wanted to warn anyone who might be running vinum about this... would be a major pain if this happened on a production box. Thanks, Jim "Jim C. Nasby" wrote: > > For those of you who are running vinum, make damn sure you keep an old > kernel around while upgrading... it seems that you can't load vinum > after booting with the new kernel... I'm hoping that a make install in > the vinum directory will remedy this situation... I'll post an update > once I know what's going on, but in the meantime, this is a heads-up for > everyone running vinum. > -- > 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-questions" in the body of the message -- 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 Mar 19 1:15:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 5F40E37BC67 for ; Sun, 19 Mar 2000 01:15:36 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA21467; Sun, 19 Mar 2000 01:16:00 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Laurence Berland Cc: Thomas David Rivers , freebsd-stable@FreeBSD.ORG Subject: Re: Is 4.0 the next `to ship' from Walnut Creek? In-reply-to: Your message of "Sat, 18 Mar 2000 22:18:41 EST." <38D44711.14BEAA08@confusion.net> Date: Sun, 19 Mar 2000 01:15:55 -0800 Message-ID: <21461.953457355@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If you've subscribed to the snapshots though, there's some exception, or > so I heard. Care to shed some light on this? (my reading of the web > page is that snap subscribers WILL get 4.0 by default, am I screwed up > in the head?) I'd rather not answer that last question. :) Suffice it to say that snapshot customers are NOT getting 4.0. It's a mainstream release and those don't count as snapshots. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 1:19:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id A656D37BCAB for ; Sun, 19 Mar 2000 01:19:46 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.225.101]) by smtp04.wxs.nl (Netscape Messaging Server 4.05) with ESMTP id FRNWKX02.564; Sun, 19 Mar 2000 10:19:45 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id JAA61402; Sun, 19 Mar 2000 09:54:54 +0100 (CET) (envelope-from asmodai) Date: Sun, 19 Mar 2000 09:54:54 +0100 From: Jeroen Ruigrok/Asmodai To: Jim Weeks Cc: FreeBSD-STABLE@FreeBSD.ORG Subject: Re: Desperate help upgrading from 3.2-R > 3.4-S Message-ID: <20000319095454.A61398@daemon.ninth-circle.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from jim@siteplus.net on Sat, Mar 18, 2000 at 07:03:47PM -0500 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000319 04:00], Jim Weeks (jim@siteplus.net) wrote: >It may not be broken, and I would love to do the make world, but I can not >get past this error during make install of groff. > >cd >/usr/src/gnu/usr.bin/groff/tmac/../../../../contrib/groff/tmac; install >-c -o root -g wheel -m 444 tmac.andoc tmac.pic tmac.ps tmac.psnew >tmac.psold tmac.pspic tmac.psatk tmac.dvi tmac.safer tmac.tty >tmac.tty-char tmac.X tmac.Xps tmac.latin1 tmac.lj4 eqnrc troffrc >tmac.arkup tmac.html /usr/share/tmac >cd >/usr/src/gnu/usr.bin/groff/tmac/../../../../contrib/groff/tmac/locale; install >-c -o root -g wheel -m 444 locale-list koi8-r /usr/share/tmac/mdoc/locale >usage: install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 >file2 > install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 Hmmmm. Slight guess, you don't have a /usr/share/tmac/mdoc/locale directory? I added a few new directories to the mtree files in /usr/src/etc/mtree. Because if you compare the two snippets you sent me, you will see that the install usage is identical, albeit not as much files get installed, and yet you get an error. And since the other one errors in locale, which is a new directory, I am betting that you don't have that dir. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Any fool can make a rule. And every fool will mind it... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 2:58: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from postfix2.free.fr (postfix2.free.fr [212.27.32.74]) by hub.freebsd.org (Postfix) with ESMTP id 52D6637B6D3 for ; Sun, 19 Mar 2000 02:57:56 -0800 (PST) (envelope-from jaco@titine.fr.eu.org) Received: from titine.fr.eu.org (unknown [213.228.46.124]) by postfix2.free.fr (Postfix) with ESMTP id 33A637408D for ; Sun, 19 Mar 2000 11:57:54 +0100 (MET) Received: by titine.fr.eu.org (Postfix, from userid 1000) id C726114A05; Sun, 19 Mar 2000 11:57:11 +0100 (CET) To: freebsd-stable@FreeBSD.ORG Subject: Still pbs with ata driver From: Eric Jacoboni Date: 19 Mar 2000 11:57:11 +0100 Message-ID: <87u2i32po8.fsf@titine.fr.eu.org> Lines: 54 User-Agent: Gnus/5.0803 (Gnus v5.8.3) XEmacs/21.1 (Bryce Canyon) 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'm still testing the new ata driver in order to replace the wd : From a today's cvsup : % grep ,v /sys/dev/ata/*.c /sys/dev/ata/ata-all.c: * $FreeBSD: src/sys/dev/ata/ata-all.c,v 1.50.2.2 2000/03/18 22:26:28 sos Exp $ /sys/dev/ata/ata-disk.c: * $FreeBSD: src/sys/dev/ata/ata-disk.c,v 1.60.2.2 2000/03/14 20:25:07 sos Exp $ /sys/dev/ata/ata-dma.c: * $FreeBSD: src/sys/dev/ata/ata-dma.c,v 1.35 2000/03/05 16:52:24 sos Exp $ /sys/dev/ata/atapi-all.c: * $FreeBSD: src/sys/dev/ata/atapi-all.c,v 1.46.2.2 2000/03/18 22:26:28 sos Exp $ /sys/dev/ata/atapi-cd.c: * $FreeBSD: src/sys/dev/ata/atapi-cd.c,v 1.48.2.1 2000/03/14 20:25:11 sos Exp $ /sys/dev/ata/atapi-fd.c: * $FreeBSD: src/sys/dev/ata/atapi-fd.c,v 1.44.2.1 2000/03/14 20:25:12 sos Exp $ /sys/dev/ata/atapi-tape.c: * $FreeBSD: src/sys/dev/ata/atapi-tape.c,v 1.36.2.2 2000/03/18 22:26:29 sos Exp $ % /sbin/dmesg |grep ata atapci0: port 0xe800-0xe80f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 1222MB [2484/16/63] at ata0-master using WDMA2 ad1: 2445MB [4969/16/63] at ata0-slave using WDMA2 acd0: CDROM at ata1-master using PIO4 % grep ata /sys/i386/conf/TITINE device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk device atapicd device atapifd Looking for /var/log/message, a 'tail -f' gives : Mar 19 11:41:34 titine /kernel: ad0: WRITE command timeout - resetting Mar 19 11:42:12 titine /kernel: ata0: resetting devices .. done Mar 19 11:42:12 titine /kernel: ad0: WRITE command timeout - resetting Mar 19 11:42:12 titine /kernel: ata0: resetting devices .. ata0-master: timeout waiting for command=c6 s=90 e=00 Mar 19 11:42:12 titine /kernel: ata0-master: timeout waiting for command=ef s=01 e=02 Mar 19 11:42:12 titine /kernel: ata0-master: timeout waiting for command=ef s=01 e=02 Mar 19 11:42:12 titine /kernel: done Mar 19 11:42:12 titine /kernel: ad0: timeout waiting for DRQad0: HARD WRITE ERROR blk# 1774352 status=01 error=02 Mar 19 11:42:12 titine /kernel: ad0: timeout waiting for DRQad0: HARD WRITE ERROR blk# 1774512 status=01 error=02 Mar 19 11:42:12 titine /kernel: ad0: timeout waiting for DRQad0: HARD WRITE ERROR blk# 1774768 status=01 error=02 Mar 19 11:42:12 titine /kernel: ad0: timeout waiting for DRQad0: HARD WRITE ERROR blk# 1774832 status=01 error=02 Mar 19 11:42:12 titine /kernel: ad0: timeout waiting for DRQad0: HARD WRITE ERROR blk# 1840032 status=01 error=02 Mar 19 11:42:12 titine /kernel: ad1: WRITE command timeout - resetting Mar 19 11:42:12 titine /kernel: ata0: resetting devices .. done Seems that better than before, as no death freeze happens, yet. -- --------------------------------------------------------- Éric Jacoboni « No sport, cigars! » (W. Churchill) --------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 4:51:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.bna.bellsouth.net (mail2.bna.bellsouth.net [205.152.150.14]) by hub.freebsd.org (Postfix) with ESMTP id DB03037B757; Sun, 19 Mar 2000 04:51:11 -0800 (PST) (envelope-from jim@siteplus.net) Received: from discover.siteplus.net (host-216-78-82-12.cha.bellsouth.net [216.78.82.12]) by mail2.bna.bellsouth.net (3.3.5alt/0.75.2) with ESMTP id HAA02320; Sun, 19 Mar 2000 07:42:51 -0500 (EST) Date: Sun, 19 Mar 2000 07:51:11 -0500 (EST) From: Jim Weeks To: Jeroen Ruigrok/Asmodai Cc: FreeBSD-STABLE@FreeBSD.ORG Subject: Re: Desperate help upgrading from 3.2-R > 3.4-S In-Reply-To: <20000319095454.A61398@daemon.ninth-circle.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 Exactly, I don't have them on my 3.2 or 3.4 machines. I am confused though, I have made the world on at least one 3.4 machine within the last couple of weeks. I suppose you added them since? On Sun, 19 Mar 2000, Jeroen Ruigrok/Asmodai wrote: > > Hmmmm. > > Slight guess, you don't have a /usr/share/tmac/mdoc/locale directory? > I added a few new directories to the mtree files in /usr/src/etc/mtree. Thanks, Jim A little knowledge is a DANGEROUS thing James W. Weeks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 8: 5:13 2000 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 5E8B137B53B; Sun, 19 Mar 2000 08:05:08 -0800 (PST) (envelope-from conrads@cx344940-a.meta1.la.home.com) Received: (from conrads@localhost) by cx344940-a.meta1.la.home.com (8.9.3/8.9.3) id KAA00579; Sun, 19 Mar 2000 10:04:41 -0600 (CST) (envelope-from conrads) 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: <20000317215327.A40008@ipass.net> Date: Sun, 19 Mar 2000 10:04:41 -0600 (CST) Organization: @Home Network From: Conrad Sabatier To: Randall Hopper Subject: Re: AWE32 Cc: multimedia@FreeBSD.ORG, Andy Sparrow , stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Mar-00 Randall Hopper wrote: > Andy Sparrow: > > |Yup, I think so. That's what my AWE32 daughterboard used to probe as > |before I put memory in it... > ... > |Unfortunately, I can't use VoxWare (and thus the AWE driver) anymore > |with -CURRENT. > > Why is that? > > Randall Because, once again, they've gone and deprecated the Voxware drivers . Frankly, this is very disappointing to me. If you recall, we went through exactly the same thing a good while back with -current (just prior to 2.2.8 or 3.0, I think), and there was such a hew and cry that they put it back in very quickly. Something tells me that's not going to be the case this time. I'm running 4.0-STABLE now, and frankly, I'm not too happy with the newpcm driver(s). I'm getting a lot more chop now playing MP3s on my 166 MHz P5 than I did with Voxware. Bummer. Not to mention *NO MIDI*. I'm sorry, but timidity just plain *sucks* compared to awemidi with a nice wavetable loaded. I may end up just going back to 3.4-STABLE and staying there. I *liked* my awemidi. I *liked* smooth MP3s. I *don't* like this. Oh, they've also removed the "pnp" (boottime) kernel config command. While the new PnP detection seems to work pretty well, I'd still like to be able to disable my motherboard audio like I've been doing for a long time. Haven't figured out a way to do this yet. Why must they do this? We went through the whole thing about not removing older functionality until there was a suitable replacement before. This is just nuts, if you ask me. Sign me, Mystified (and a little pissed) -- Conrad Sabatier http://members.home.net/conrads/ ICQ# 1147270 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 8:10:44 2000 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 5BA4C37B759; Sun, 19 Mar 2000 08:10:40 -0800 (PST) (envelope-from conrads@cx344940-a.meta1.la.home.com) Received: (from conrads@localhost) by cx344940-a.meta1.la.home.com (8.9.3/8.9.3) id KAA00611; Sun, 19 Mar 2000 10:10:38 -0600 (CST) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 19 Mar 2000 10:10:38 -0600 (CST) Organization: @Home Network From: Conrad Sabatier To: stable@freebsd.org Subject: Suggestions for improving newpcm performance? Cc: multimedia@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I mentioned in another post, since upgrading to 4.0 and converting from Voxware to newpcm, I've noticed quite a significant degradation in audio performance. Whereas my MP3s used to play smoothly until the system load reached a really high level, now I'm getting breakup even with minimal system loads (on a 166MHz P5). Any ideas on how I might improve performance? I've already disabled ATAPI DMA (my system is pure IDE), thinking there may have been a conflict, and am using softupdates as well, but still, anytime the system load increases even slightly, I notice some chop. Thanks for any ideas. -- Conrad Sabatier http://members.home.net/conrads/ ICQ# 1147270 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 8:19: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id DD72837B621 for ; Sun, 19 Mar 2000 08:18:58 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.225.74]) by smtp05.wxs.nl (Netscape Messaging Server 4.05) with ESMTP id FROFZJ02.324; Sun, 19 Mar 2000 17:18:55 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id QAA73400; Sun, 19 Mar 2000 16:30:52 +0100 (CET) (envelope-from asmodai) Date: Sun, 19 Mar 2000 16:30:51 +0100 From: Jeroen Ruigrok/Asmodai To: Jim Weeks Cc: FreeBSD-STABLE@FreeBSD.ORG Subject: Re: Desperate help upgrading from 3.2-R > 3.4-S Message-ID: <20000319163051.A471@daemon.ninth-circle.org> References: <20000319095454.A61398@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from jim@siteplus.net on Sun, Mar 19, 2000 at 07:51:11AM -0500 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000319 16:00], Jim Weeks (jim@siteplus.net) wrote: >Exactly, > >I don't have them on my 3.2 or 3.4 machines. I am confused though, I have >made the world on at least one 3.4 machine within the last couple of >weeks. I suppose you added them since? I added the mtree changes one or two days before the groff MFC. Because if people would make world in the meantime would already create the directories for them. A non-intrusive commit. After that I tested the MFC and the install a few times, including make world and that all worked correctly. So either I missed something which stepped over the problems you guys are encountering or there's something else acting up. Alternatively you could do a: mtree -deU -f /usr/src/etc/mtree/BSD.usr.dist -p /usr as root to force the directories to be created. Then you can install groff and make world again. I won't be able to get completely on the install case until tomorrow. Only have CURRENT boxes at home. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Any fool can make a rule. And every fool will mind it... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 8:21:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from charon.ipass.net (charon.ipass.net [198.79.53.8]) by hub.freebsd.org (Postfix) with ESMTP id 1F6B037B51E; Sun, 19 Mar 2000 08:21:22 -0800 (PST) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-1-72.dialup.rdu.ipass.net [209.170.132.72]) by charon.ipass.net (8.9.3/8.9.3) with ESMTP id LAA16197; Sun, 19 Mar 2000 11:21:03 -0500 (EST) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id LAA05877; Sun, 19 Mar 2000 11:23:32 -0500 (EST) (envelope-from rhh) Date: Sun, 19 Mar 2000 11:23:32 -0500 From: Randall Hopper To: Conrad Sabatier Cc: multimedia@FreeBSD.ORG, Andy Sparrow , stable@FreeBSD.ORG Subject: Re: AWE32 Message-ID: <20000319112332.A5517@ipass.net> References: <20000317215327.A40008@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from conrads@home.com on Sun, Mar 19, 2000 at 10:04:41AM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Conrad Sabatier: |Randall Hopper: |> Andy Sparrow: |> | |> |Unfortunately, I can't use VoxWare (and thus the AWE driver) anymore |> |with -CURRENT. |> |> Why is that? | |Because, once again, they've gone and deprecated the Voxware drivers |. Frankly, this is very disappointing to me. If you recall, we |went through exactly the same thing a good while back with -current (just |prior to 2.2.8 or 3.0, I think), and there was such a hew and cry that |they put it back in very quickly. Sure do. I was among the folks protesting. |I'm running 4.0-STABLE now, and frankly, I'm not too happy with the newpcm |driver(s). I'm getting a lot more chop now playing MP3s on my 166 MHz P5 |than I did with Voxware. Bummer. Not to mention *NO MIDI*. I'm sorry, |but timidity just plain *sucks* compared to awemidi with a nice wavetable |loaded. | |I may end up just going back to 3.4-STABLE and staying there. I *liked* |my awemidi. I *liked* smooth MP3s. I *don't* like this. Thanks for the heads-up. I will certainly fortify my 3.4-RELEASE installation, grab all the packages out there, burn them onto CDs, do a full backup, and plan do stick with 3.4 for a while. Unless the sound driver situation changes, a _long_ while. |Why must they do this? We went through the whole thing about not removing |older functionality until there was a suitable replacement before. This |is just nuts, if you ask me. I see what you mean. If we were close to the same level of functionality (soundcard support, pcm, midi, etc.), from your results it sounds like we still need more testing before we pull the rug out from under folks like that. But, we're not at that level yet (AFAICT). So I'm scratching my head too. Are we trying to alienenate FreeBSD desktop users or what? Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 8:38: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id 4949537B754; Sun, 19 Mar 2000 08:37:56 -0800 (PST) (envelope-from gandalf@vilnya.demon.co.uk) Received: from vilnya.demon.co.uk ([158.152.19.238]) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 12Wii7-000Hhi-0A; Sun, 19 Mar 2000 16:37:54 +0000 Received: from NENYA (nenya.rings [10.2.4.3]) by vilnya.demon.co.uk (Postfix) with SMTP id 07DBDD9AD; Sun, 19 Mar 2000 16:37:49 +0000 (GMT) Message-ID: <001a01bf91c1$7f62a4b0$0304020a@NENYA> From: "Cameron Grant" To: "Conrad Sabatier" , Cc: References: Subject: Re: Suggestions for improving newpcm performance? Date: Sun, 19 Mar 2000 16:38:04 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As I mentioned in another post, since upgrading to 4.0 and converting from > Voxware to newpcm, I've noticed quite a significant degradation in audio > performance. Whereas my MP3s used to play smoothly until the system load > reached a really high level, now I'm getting breakup even with minimal > system loads (on a 166MHz P5). define breakup? noise, or pausing? > Any ideas on how I might improve performance? I've already disabled ATAPI > DMA (my system is pure IDE), thinking there may have been a conflict, and > am using softupdates as well, but still, anytime the system load increases > even slightly, I notice some chop. what you are seeing is probably spl-related. spls are going away in -current, which will improve concurrency greatly. the situation with voxware is that it will remain in 4.x, but unless a maintainer comes forward who will convert it to newbus, in -current it will soon be toast. - cg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 9:18:12 2000 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 B97C837B545 for ; Sun, 19 Mar 2000 09:18:08 -0800 (PST) (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 JAA08246; Sun, 19 Mar 2000 09:17:18 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda08244; Sun Mar 19 09:17:16 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id JAA91181; Sun, 19 Mar 2000 09:17:16 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdX91179; Sun Mar 19 09:17:02 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id JAA01199; Sun, 19 Mar 2000 09:17:01 -0800 (PST) Message-Id: <200003191717.JAA01199@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdAK1195; Sun Mar 19 09:16:34 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: Randall Hopper Cc: stable@FreeBSD.ORG Subject: Re: Netscape pegs CPU on XServer kill In-reply-to: Your message of "Sat, 18 Mar 2000 11:08:31 EST." <20000318110831.A34338@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 19 Mar 2000 09:16:32 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000318110831.A34338@ipass.net>, Randall Hopper writes: > I've got Netscape Navigator 4.72 built from ports. > > In the past, killing the X server (e.g Ctrl-Alt-Bksp) killed Netscape. > Now, Netscape lives on and just hammers the CPU. > > Anybody else seen this problem? What's the best fix/workaround? Netscape 4.0+ will do this frequently even when shutting down the app [at times]. Switching to the Linux version of NS running under Linux compatibility fixed the problem for me. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC "COBOL IS A WASTE OF CARDS." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 9:26:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from poseidon.student.umd.edu (poseidon.student.umd.edu [129.2.220.99]) by hub.freebsd.org (Postfix) with ESMTP id 59CA437B55C; Sun, 19 Mar 2000 09:26:29 -0800 (PST) (envelope-from bfoz@glue.umd.edu) Received: from glue.umd.edu (localhost [127.0.0.1]) by poseidon.student.umd.edu (8.9.3/8.9.3) with ESMTP id MAA01492; Sun, 19 Mar 2000 12:26:20 -0500 (EST) (envelope-from bfoz@glue.umd.edu) Message-ID: <38D50DBC.88FA8E4D@glue.umd.edu> Date: Sun, 19 Mar 2000 12:26:20 -0500 From: Brandon Fosdick Reply-To: bfoz@glue.umd.edu X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Doug Barton , Josef Karthauser , Ruslan Ermilov , stable@FreeBSD.ORG Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions References: <38D3AB72.366D851D@glue.umd.edu> <200003152159.OAA89926@harmony.village.org> <38D03E64.3D17FC34@glue.umd.edu> <200003190433.VAA04863@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <38D3AB72.366D851D@glue.umd.edu> Brandon Fosdick writes: > : When I did the MAKEDEV stuff I forgot to put the 'a' on the end of the device > : names. I did ad0s3 instead of ad0s3a. Doh! So when I rebooted (after changing > > One can always do > mount /dev/ad0a /mnt > cd /mnt/dev > sh MAKEDEV ad0s3a > cd / > umount /mnt > reboot > > if one finds one's self in that situation. > > Warner I thought of that, but I didn't know what the devices w/o slice numbers did. Guess I should have just tried it. Thanks, Brandon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 9:46: 1 2000 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 DDA8637B781 for ; Sun, 19 Mar 2000 09:45:56 -0800 (PST) (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 JAA08292; Sun, 19 Mar 2000 09:45:18 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda08290; Sun Mar 19 09:45:16 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id JAA91260; Sun, 19 Mar 2000 09:45:16 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdQ91258; Sun Mar 19 09:45:03 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id JAA09610; Sun, 19 Mar 2000 09:45:02 -0800 (PST) Message-Id: <200003191745.JAA09610@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdKx9602; Sun Mar 19 09:44:12 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: Laurence Berland Cc: stable@FreeBSD.ORG Subject: Re: Small spaces In-reply-to: Your message of "Sat, 18 Mar 2000 21:40:14 EST." <38D43E0E.1DDECC10@confusion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 19 Mar 2000 09:44:10 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38D43E0E.1DDECC10@confusion.net>, Laurence Berland writes: > I'm trying to install FreeBSD 3.4 on an old 486 I've got lying around to > use as a NATing firewall for my home network, but I've only got a 200 > Meg HD around. I'm gonna go get another HD later, but right now I'd > like to get running with just that. So far I've been trying with 16 to > swap and various other combinations, but it always seems to run out of > /usr space. I figure / should be at least 32MB, and the rest (~152MB) > goes to /usr. I'm trying to install the binaries, the docs, and the > kernel source (but not the rest of the source). Any idea if it's even > possible? Should I shrink down the root partition more? I've done > loads of installs at this point, but all on HDs with at least a gig for > FreeBSD. Any ideas where I can get a bigger HD that's still under the > limit for old BIOSen? Thanks in advance for any help. My 486/33 looks like this. X, games, /compat, and /usr/share are served off my P120 server. Swap on this machine is 43 MB backing 20 MB RAM. The root disk, which contains /var and /usr, is a 200 MB slice which is 43% full. For a pure firewall machine, don't install X, games, info files, so you should be able to run it stand-alone. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC "COBOL IS A WASTE OF CARDS." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 9:51: 0 2000 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 B71D037B70B for ; Sun, 19 Mar 2000 09:50:52 -0800 (PST) (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 JAA08306; Sun, 19 Mar 2000 09:50:18 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda08304; Sun Mar 19 09:50:16 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id JAA91290; Sun, 19 Mar 2000 09:50:16 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdH91288; Sun Mar 19 09:50:03 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id JAA09645; Sun, 19 Mar 2000 09:50:02 -0800 (PST) Message-Id: <200003191750.JAA09645@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdVL9625; Sun Mar 19 09:49:17 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: Vova Golubkov Cc: "stable@FreeBSD.ORG" Subject: Re: 4.0: EtherExpress16 disappeared? In-reply-to: Your message of "Sun, 19 Mar 2000 05:16:03 +0100." <38D45483.110F6A78@cern.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 19 Mar 2000 09:49:17 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38D45483.110F6A78@cern.ch>, Vova Golubkov writes: > Hi > > I have upgraded to 4.0-RELEASE and found that my Intel EtherExpress16 > NIC is not detected anymore. I know that this driver is not perfect > (as well as the card itself), but I prefer it to nothing :-) > Should it be added to sys/i386/isa/isa_compat.h? Had the same problem with my 3C509B (ep0). Disabled all unneeded drivers (boot -c) and it now works. A comment in the -current archives by Warner (IIRC) stated that other drivers may trash the card's registers while probing for their supported hardware, causing your card to become unresponsive. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC "COBOL IS A WASTE OF CARDS." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 9:57:34 2000 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 1C50D37B663; Sun, 19 Mar 2000 09:57:30 -0800 (PST) (envelope-from conrads@cx344940-a.meta1.la.home.com) Received: (from conrads@localhost) by cx344940-a.meta1.la.home.com (8.9.3/8.9.3) id LAA01098; Sun, 19 Mar 2000 11:57:25 -0600 (CST) (envelope-from conrads) 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: <001a01bf91c1$7f62a4b0$0304020a@NENYA> Date: Sun, 19 Mar 2000 11:57:25 -0600 (CST) Organization: @Home Network From: Conrad Sabatier To: Cameron Grant Subject: Re: Suggestions for improving newpcm performance? Cc: multimedia@freebsd.org, stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Mar-00 Cameron Grant wrote: >> As I mentioned in another post, since upgrading to 4.0 and converting >> from Voxware to newpcm, I've noticed quite a significant degradation >> in audio performance. Whereas my MP3s used to play smoothly until the >> system load reached a really high level, now I'm getting breakup even >> with minimal system loads (on a 166MHz P5). > > define breakup? noise, or pausing? Pausing, choppiness. > what you are seeing is probably spl-related. spls are going away > in -current, which will improve concurrency greatly. I'm sure I have no idea what you're talking about. :-) > the situation with voxware is that it will remain in 4.x, but unless a > maintainer comes forward who will convert it to newbus, in -current it > will soon be toast. I tried building a kernel with the old Voxware stuff, and config warned me that the drivers had been deprecated and to use pcm/sbc/etc instead. So it *is* possible to still use the old stuff? Hmmm. -- Conrad Sabatier http://members.home.net/conrads/ ICQ# 1147270 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 10: 2:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from server.hmm.za.net (admin.bsdonline.org [196.28.82.142]) by hub.freebsd.org (Postfix) with ESMTP id 0D5CF37B57A for ; Sun, 19 Mar 2000 10:02:06 -0800 (PST) (envelope-from david@campsbay.za.net) Received: from DAVID (david [192.168.1.2]) by server.hmm.za.net (8.9.3/8.9.3) with SMTP id UAA01069 for ; Sun, 19 Mar 2000 20:03:14 +0200 (SAST) (envelope-from david@campsbay.za.net) Message-ID: <004501bf91cd$5bfc0730$0201a8c0@DAVID> From: "David" To: Subject: problem with boot Date: Sun, 19 Mar 2000 20:02:57 +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.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsuped from 3.4-release to 4.0-stable now and i followed instructions 100% when i reboot finally in single user mode to do the final step (make installworld) i get this error. Please could you give me information as to amend this.. ad0: 4211MB [8912/15/63] Mounting root from ufs:wd0sa ad0: Read command timeout - resetting ata0: resetting devices... device dissapeared ata0-master: timeout waiting to give command=c6 s=d0 e=00 And then nothing happens thanks bye _________________________ David van Rensburg - david@van.web.za aka Van 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 Sun Mar 19 10:17: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from atlas.pathcom.com (pathway1.pathcom.com [209.250.128.4]) by hub.freebsd.org (Postfix) with ESMTP id 1386437B550 for ; Sun, 19 Mar 2000 10:16:59 -0800 (PST) (envelope-from lwh@pathcom.com) Received: from dial-0112.tor.pathcom.com (dial-0112.tor.pathcom.com [216.249.0.112]) by atlas.pathcom.com (8.9.3/8.9.3) with ESMTP id NAA02511 for ; Sun, 19 Mar 2000 13:16:04 -0500 (EST) Date: Sun, 19 Mar 2000 13:15:55 -0500 (EST) From: Luke Hollins Reply-To: lwh@pathcom.com To: freebsd-stable@freebsd.org Subject: Serial problem Message-ID: Confirm-Reading-To: "Me" Disposition-Notification-To: "luke" MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just started using RELENG_4 and started experiencing an odd serial problem... with my mb sio ports, and a number of sio cards, half a dozen different cables, 3 different external modems, they all act as if they work , they even flash when you type at them, but they really cant do anything. I am using an internal one right now that is working but really need to solve this, I have no idea what is wrong and wondered if anyone else has experienced any oddities I have tried many AT commands to fix it, like turning on echo, turning on verbal result codes etc, I am being led to believe it is some setting with the port, I tried "sh /etc/rc.serial modem " Thanks Luke To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 10:20:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2221337B628 for ; Sun, 19 Mar 2000 10:20:33 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA14432; Sun, 19 Mar 2000 11:20:30 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA08229; Sun, 19 Mar 2000 11:20:23 -0700 (MST) Message-Id: <200003191820.LAA08229@harmony.village.org> To: bfoz@glue.umd.edu Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions Cc: stable@FreeBSD.ORG In-reply-to: Your message of "Sun, 19 Mar 2000 12:26:20 EST." <38D50DBC.88FA8E4D@glue.umd.edu> References: <38D50DBC.88FA8E4D@glue.umd.edu> <38D3AB72.366D851D@glue.umd.edu> <200003152159.OAA89926@harmony.village.org> <38D03E64.3D17FC34@glue.umd.edu> <200003190433.VAA04863@harmony.village.org> Date: Sun, 19 Mar 2000 11:20:23 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38D50DBC.88FA8E4D@glue.umd.edu> Brandon Fosdick writes: : I thought of that, but I didn't know what the devices w/o slice numbers : did. Guess I should have just tried it. Devices w/o slice numbers are the "compatibility" devices. These map to the first BSD partition on the disk. For most people, this is the only partition on the disk. It is a shame that you can't use them to mount / on / in an emergency. The consistancy checks won't let you. Mounting one file system read only and the other read/write is asking for trouble. But the trouble tends to manifest itself as the r/o file system not seeing the changes in the r/w file system. In olden days, this could cause a panic, but I've not seen such panics in a while. I don't know if this means that I'm lucky, or if the underlying problems have been corrected. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 10:39:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 1C06A37B743; Sun, 19 Mar 2000 10:39:37 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id KAA40955; Sun, 19 Mar 2000 10:38:01 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200003191838.KAA40955@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Cameron Grant" Cc: "Conrad Sabatier" , stable@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Suggestions for improving newpcm performance? In-reply-to: Your message of "Sun, 19 Mar 2000 16:38:04 GMT." <001a01bf91c1$7f62a4b0$0304020a@NENYA> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 19 Mar 2000 10:38:01 -0800 From: Amancio Hasty Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > the situation with voxware is that it will remain in 4.x, but unless a > maintainer comes forward who will convert it to newbus, in -current it will > soon be toast. I can't promise anything specially since I have a new job;nevertheless, before you decide to toast the voxware from current send me mail . If -core decides to toast voxware I will probably pick up the maintainence of voxware from right here were maintainence of voxware used to be. The latter is not a bad idea since it will avoid conflicts between -core and I. -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 10:40:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.sfba.home.com (ha1.rdc1.sfba.home.com [24.0.0.66]) by hub.freebsd.org (Postfix) with ESMTP id E73CA37B5BC for ; Sun, 19 Mar 2000 10:40:36 -0800 (PST) (envelope-from boshea@ricochet.net) Received: from beastie.localdomain ([24.19.158.41]) by mail.rdc1.sfba.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <20000319184036.OJOK14939.mail.rdc1.sfba.home.com@beastie.localdomain>; Sun, 19 Mar 2000 10:40:36 -0800 Received: (from brian@localhost) by beastie.localdomain (8.9.3/8.8.7) id KAA33086; Sun, 19 Mar 2000 10:50:19 -0800 (PST) (envelope-from brian) Date: Sun, 19 Mar 2000 10:50:19 -0800 From: "Brian O'Shea" To: Randall Hopper Cc: Tom , stable@FreeBSD.ORG Subject: Re: Dynamic linker bug in 3.4-RELEASE (I think) Message-ID: <20000319105019.D78517@beastie.localdomain> Mail-Followup-To: Randall Hopper , Tom , stable@FreeBSD.ORG References: <20000317195156.A24243@ipass.net> <20000318110118.A34149@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20000318110118.A34149@ipass.net>; from Randall Hopper on Sat, Mar 18, 2000 at 11:01:18AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 18, 2000 at 11:01:18AM -0500, Randall Hopper wrote: > Tom: > |On Fri, 17 Mar 2000, Randall Hopper wrote: > |> I have a small program I wrote that uses sigwait and takes about 1 second > |> to complete. > |> > |> If I run it over-and-over many times repeatedly, occasionally the dynamic > |> linker will fail to resolve the "sigwait" symbol. > ... > |> Done > |> Done > |> /usr/libexec/ld-elf.so.1: hw4-1: Undefined symbol "sigwait" > |> Done > |> Done > ... > | > | I think it is more likely you are exceeding your limit on number of file > |descriptors, so the dynamic linker isn't able to open the libraries. > > How could that be? The program opens one file and one pipe. So that's > 5 file descriptors. I think that Tom is referring to the fact that the shell opens /dev/null a bunch of times (with the redirection operator in a while-loop), and each child process of the shell inherits the open file descriptors of its parent. He is suggesting that, once this gets close enough to the maximum number of open files, the next child process that is created will exceed the limit of open files, and will then have trouble opening shared libraries. However, I don't think that this is what's going on here since in each iteration of the while-loop, the shell waits for its child to exit before starting the next iteration (and it should be closing /dev/null in the parent process after each fork() system call). It could be a shell bug (if the shell isn't closing the open files from the redirection after the fork). To test this, you could try running fstat on the shell process while the script is running to see how many times it has /dev/null open. The fstat program doesn't show file names, it will only tell you that there are open files in / (/dev/null is in the / filesystem), so it might be useful to run this command before and during the while-loop and compare the output from both times). To get the PID of your shell process, run the following command in the terminal where you will be running your program. You will be passing this PID to fstat later: $ echo $$ (run your program in a while-loop from this terminal, as you described before) Now in another terminal, run the following command, replacing with your shell's PID (which you got above). $ fstat -p -brian -- Brian O'Shea boshea@ricochet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 10:53: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lafontaine.cybercable.fr (lafontaine.cybercable.fr [212.198.0.202]) by hub.freebsd.org (Postfix) with SMTP id 906AB37B798 for ; Sun, 19 Mar 2000 10:53:01 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 5710799 invoked from network); 19 Mar 2000 18:52:59 -0000 Received: from d016.paris-30.cybercable.fr (HELO cybercable.fr) ([212.198.30.16]) (envelope-sender ) by lafontaine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 19 Mar 2000 18:52:59 -0000 Message-ID: <38D52113.5F3B4EB@cybercable.fr> Date: Sun, 19 Mar 2000 19:48:51 +0100 From: "Thierry.herbelot" X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Amancio Hasty Cc: Cameron Grant , Conrad Sabatier , stable@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Suggestions for improving newpcm performance? References: <200003191838.KAA40955@rah.star-gate.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote: > > > the situation with voxware is that it will remain in 4.x, but unless a > > maintainer comes forward who will convert it to newbus, in -current it will > > soon be toast. > > I can't promise anything specially since I have a new job;nevertheless, before > you decide to toast the voxware from current send me mail . If -core decides > to toast voxware I will probably pick up the maintainence of voxware from > right here were maintainence of voxware used to be. The latter is not a bad > idea since it will avoid conflicts between -core and I. Wouldn't it be better to list the apps which **need** some voxware functionalities (I have just discovered that Spaek_Freely is one such beast) and try get them running with pcm ? TfH -- Thierry Herbelot ASCII RIBBON CAMPAIGN /"\ mailto:herbelot@cybercable.fr AGAINST HTML MAIL & NEWS \ / http://perso.cybercable.fr/herbelot PAS DE HTML DANS X Hiroshima 45, Tchernobyl 86, Windows 95... LES COURRIELS / \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 10:59:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by hub.freebsd.org (Postfix) with ESMTP id 80BBD37BF6E; Sun, 19 Mar 2000 10:59:39 -0800 (PST) (envelope-from gandalf@vilnya.demon.co.uk) Received: from vilnya.demon.co.uk ([158.152.19.238]) by anchor-post-34.mail.demon.net with esmtp (Exim 2.12 #1) id 12WkvF-0003Gd-0Y; Sun, 19 Mar 2000 18:59:34 +0000 Received: from NENYA (nenya.rings [10.2.4.3]) by vilnya.demon.co.uk (Postfix) with SMTP id 212B0D9AD; Sun, 19 Mar 2000 18:59:30 +0000 (GMT) Message-ID: <000701bf91d5$4aebeb60$0304020a@NENYA> From: "Cameron Grant" To: "Amancio Hasty" Cc: "Conrad Sabatier" , , References: <200003191838.KAA40955@rah.star-gate.com> Subject: Re: Suggestions for improving newpcm performance? Date: Sun, 19 Mar 2000 18:59:45 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > the situation with voxware is that it will remain in 4.x, but unless a > > maintainer comes forward who will convert it to newbus, in -current it will > > soon be toast. > I can't promise anything specially since I have a new job;nevertheless, before > you decide to toast the voxware from current send me mail . If -core decides > to toast voxware I will probably pick up the maintainence of voxware from > right here were maintainence of voxware used to be. The latter is not a bad > idea since it will avoid conflicts between -core and I. you should be aware that the voxware code will need extensive renovation and conversion to newbus. already it will not cope with pnp devices, and the compatibility shims it relies on will shortly be gone. in my opinion it would be far better to divert any effort you would be willing to put in towards newpcm. -cg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 11:32:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id B536437B798; Sun, 19 Mar 2000 11:32:16 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id LAA41341; Sun, 19 Mar 2000 11:30:55 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200003191930.LAA41341@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Cameron Grant" Cc: "Conrad Sabatier" , stable@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Suggestions for improving newpcm performance? In-reply-to: Your message of "Sun, 19 Mar 2000 18:59:45 GMT." <000701bf91d5$4aebeb60$0304020a@NENYA> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 19 Mar 2000 11:30:55 -0800 From: Amancio Hasty Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Don't forget that before there was any PNP support on FreeBSD there was the guspnp and I know the voxware driver very well. Take Care and Have Fun! -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 11:40:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bigphred.greycat.com (bigphred.greycat.com [207.173.133.2]) by hub.freebsd.org (Postfix) with ESMTP id 267A137B7D3 for ; Sun, 19 Mar 2000 11:40:48 -0800 (PST) (envelope-from dann@bigphred.greycat.com) Received: (from dann@localhost) by bigphred.greycat.com (8.9.3/8.9.3) id LAA09257 for stable@freebsd.org; Sun, 19 Mar 2000 11:40:44 -0800 (PST) (envelope-from dann) Date: Sun, 19 Mar 2000 11:40:44 -0800 From: Dann Lunsford To: stable@freebsd.org Subject: RELENG_4 and sound on a Toshiba laptop Message-ID: <20000319114021.A9089@greycat.com> 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 did a cold install from the March 7 snap .iso on my Toshiba 2595XDVD laptop and I am pleased to report that most everything went very well. X is running, most of the devices are working, network is up on my DE-660 pc-card. Just did my first RELENG_4 cvsup, and did a make world with apparently complete success. Way to go, Core Team! The only thing that isn't working is the audio. This thing has a ESS Maestro 2E based pci sound system; one of the reasons I wanted 4.0 on the machine was my (mistaken?) understanding that it supported this chipset. The kernel spots the thing. as can be seen from this dmesg: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-STABLE #0: Sun Mar 19 10:35:46 PST 2000 root@mach.greycat.com:/usr/src/sys/compile/SATELLITE Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (399.06-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x66a Stepping = 10 Features=0x183f9ff real memory = 201195520 (196480K bytes) avail memory = 191913984 (187416K bytes) Preloaded elf kernel "kernel" at 0xc0303000. VESA: v2.0, 2560k memory, flags:0x0, mode table:0xc00c806c (c000806c) VESA: Copyright 1997 TRIDENT MICROSYSTEMS INC. 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 5.0 on pci0 isa0: on isab0 atapci0: port 0xfe60-0xfe6f at device 5.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 5.2 irq 11 chip1: port 0xfe70-0xfe7f at device 5.3 on pci0 chip2: port 0xff80-0xff9f irq 11 at device 10.0 on pci0 chip3: port 0xfc00-0xfcff irq 11 at device 12.0 on pci0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model GlidePoint, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> pcic0: at port 0x3e0 iomem 0xd0000 irq 10 on isa0 pcic0: management irq 10 pccard0: on pcic0 pccard1: on pcic0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A ncp_load: [210-213] pccard: card inserted, slot 0 pccard: card inserted, slot 1 ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: 6194MB [13424/15/63] at ata0-master using UDMA33 acd0: DVD-ROM at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s1a sio1 at port 0x2f8-0x2ff irq 3 slot 0 on pccard0 sio1: type 16550A ed0 at port 0x240-0x25f irq 7 slot 1 on pccard1 ed0: address 00:80:c8:ba:8c:96, type NE2000 (16 bit) but nothing I've come up with has worked to get sound. I've tried device pcm and device pcm0 and using the "bridge" driver device pcm device sbc and quite a few other things. No go. Is it me or is it this Toshiba? Hellllllpppp!!!! -- Dann Lunsford The only thing necessary for the triumph of evil dann@greycat.com is that men of good will do nothing. -- Cicero To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 12:42:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail0.bna.bellsouth.net (mail0.bna.bellsouth.net [205.152.150.12]) by hub.freebsd.org (Postfix) with ESMTP id 8562737B798; Sun, 19 Mar 2000 12:42:28 -0800 (PST) (envelope-from jim@siteplus.net) Received: from discover.siteplus.net (host-216-78-82-12.cha.bellsouth.net [216.78.82.12]) by mail0.bna.bellsouth.net (3.3.5alt/0.75.2) with ESMTP id PAA25069; Sun, 19 Mar 2000 15:41:37 -0500 (EST) Date: Sun, 19 Mar 2000 15:42:39 -0500 (EST) From: Jim Weeks To: Jeroen Ruigrok/Asmodai Cc: FreeBSD-STABLE@FreeBSD.ORG Subject: Re: Desperate help upgrading from 3.2-R > 3.4-S In-Reply-To: <20000319163051.A471@daemon.ninth-circle.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 I ran the groff install a couple, or maybe three times this morning making the directories by hand as I received the errors. This seemed to work fine, and the make buildworld went without a hitch. I won't do the install world and build the kernel untill the wee hours of Monday morning since this a fairly busy web server. I have to answer enough email as it is. I don't want to "T" anyone off for no good reason. Thanks again, Jim A little knowledge is a DANGEROUS thing James W. Weeks On Sun, 19 Mar 2000, Jeroen Ruigrok/Asmodai wrote: > > Alternatively you could do a: > > mtree -deU -f /usr/src/etc/mtree/BSD.usr.dist -p /usr > > as root to force the directories to be created. > > Then you can install groff and make world again. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 12:59:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from nol.co.za (nol.co.za [196.33.45.2]) by hub.freebsd.org (Postfix) with ESMTP id 7910937BC57 for ; Sun, 19 Mar 2000 12:59:33 -0800 (PST) (envelope-from tim@nol.co.za) Received: from sz.nol.co.za ([196.33.45.130] helo=eclipse) by nol.co.za with esmtp (Exim 3.13 #1) id 12Wmms-0009pe-00 for freebsd-stable@freebsd.org; Sun, 19 Mar 2000 22:59:03 +0200 Message-Id: <4.2.0.58.20000319225834.00a51570@nol.co.za> X-Sender: tim@nol.co.za X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Sun, 19 Mar 2000 23:03:16 +0200 To: freebsd-stable@freebsd.org From: "Timothy S. Bowers" Subject: freebsd 3.4 stable 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 Hi all. I think I found some sort of bug in freebsd 3.4 stable. I was playing with ipfw pipes. I added pipes limiting bandwidth to 128Kbps and 64Kbps to/from the server etc.. then after a few days when I took the firewall rules off of the server but the bandwidth stayed the same.. I only get 128Kbps to the server from my personal pc and all other pc's. The server is on the same 10/100Mb switch as me and the other pc's. Also when I upload to the server.. if I'm lucky I can upload fast again... but then downloading freezes after 4096 bytes of data... Any suggestions.. What info do you need? Later, Timothy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 14: 7:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from vivaldi.pn.npi.msu.ru (gw.pn.npi.msu.ru [193.232.127.202]) by hub.freebsd.org (Postfix) with ESMTP id 5399337B7F9 for ; Sun, 19 Mar 2000 14:07:43 -0800 (PST) (envelope-from svysh@pn.sinp.msu.ru) Received: from handel (handel [195.208.223.24]) by vivaldi.pn.npi.msu.ru (8.10.0/8.10.0) with SMTP id e2JM7bD73754 for ; Mon, 20 Mar 2000 01:07:38 +0300 (MSK) Message-Id: <3.0.5.32.20000320010755.007b6500@vivaldi> X-Sender: svysh@vivaldi (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 20 Mar 2000 01:07:55 +0300 To: freebsd-stable@freebsd.org From: Sergei Vyshenski Subject: tun0 lost in 4.0 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can not revive tun0 interface after moving to 4.0 from 3.4 in a way that src/UPDATING teaches. Kernel file has "pseudo-device tun 1", kernel builds ok; ./MAKEDEV tun0 in /dev does not complain; but ifconfig says: "interface tun0 does not exist" Actually, I need tun0 to accept incoming user-ppp, and would be happy to hear of workaround at least. Thank you in advance. Sergei To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 14:40:31 2000 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 B766C37B5B4; Sun, 19 Mar 2000 14:40:24 -0800 (PST) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id RAA72392; Sun, 19 Mar 2000 17:36:44 -0500 (EST) (envelope-from bandix@looksharp.net) Date: Sun, 19 Mar 2000 17:36:44 -0500 (EST) From: "Brandon D. Valentine" To: Amancio Hasty Cc: Cameron Grant , Conrad Sabatier , stable@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Suggestions for improving newpcm performance? In-Reply-To: <200003191838.KAA40955@rah.star-gate.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 Sun, 19 Mar 2000, Amancio Hasty wrote: >I can't promise anything specially since I have a new job;nevertheless, before >you decide to toast the voxware from current send me mail . If -core decides >to toast voxware I will probably pick up the maintainence of voxware from >right here were maintainence of voxware used to be. The latter is not a bad >idea since it will avoid conflicts between -core and I. > >-- > Amancio Hasty > hasty@rah.star-gate.com I too would be rather remiss to see voxware axed from current. I have a plethora of real creative cards in use that I just love voxware for. I've never quite had the same luck under pcm with them. I don't know an awful lot about sound drivers, or voxware in particular, but if you are willing to pick this up I don't mind testing code. ------------------------------------------------------------- | -Brandon D. Valentine bandix at looksharp.net | bandix on EFnet IRC BVRiker on AIM ------------------------------------------------------------- | "...and as for hackers, we note that all of those known to | The Register are so strapped financially that seizing their | property would be tantamount to squeezing blood from a | stone." -- The Register, 02/17/2000 ------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 14:49:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from charon.ipass.net (charon.ipass.net [198.79.53.8]) by hub.freebsd.org (Postfix) with ESMTP id 7704F37B744 for ; Sun, 19 Mar 2000 14:49:47 -0800 (PST) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-1-177.dialup.rdu.ipass.net [209.170.132.177]) by charon.ipass.net (8.9.3/8.9.3) with ESMTP id RAA10912; Sun, 19 Mar 2000 17:49:41 -0500 (EST) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id RAA53292; Sun, 19 Mar 2000 17:52:10 -0500 (EST) (envelope-from rhh) Date: Sun, 19 Mar 2000 17:52:10 -0500 From: Randall Hopper To: Tom , stable@FreeBSD.ORG Subject: Re: Dynamic linker bug in 3.4-RELEASE (I think) Message-ID: <20000319175210.A52827@ipass.net> References: <20000317195156.A24243@ipass.net> <20000318110118.A34149@ipass.net> <20000319105019.D78517@beastie.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000319105019.D78517@beastie.localdomain>; from boshea@ricochet.net on Sun, Mar 19, 2000 at 10:50:19AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian O'Shea: |>| Randall Hopper: |>| > I have a small program I wrote that uses sigwait and takes about 1 |>| > second to complete. |>| > |>| > If I run it over-and-over many times repeatedly, occasionally the |>| > dynamic linker will fail to resolve the "sigwait" symbol. |> ... |>| > /usr/libexec/ld-elf.so.1: hw4-1: Undefined symbol "sigwait" | |However, I don't think that this is what's going on here since in each |iteration of the while-loop, the shell waits for its child to exit |before starting the next iteration (and it should be closing /dev/null |in the parent process after each fork() system call). It could be a |shell bug (if the shell isn't closing the open files from the |redirection after the fork). To test this, you could try running fstat |on the shell process while the script is running to see how many times |it has /dev/null open. The fstat program doesn't show file names, it |will only tell you that there are open files in / (/dev/null is in the |/ filesystem), so it might be useful to run this command before and |during the while-loop and compare the output from both times). I tried this. I never caught tcsh (6.09.00) with /dev/null open. I did see hw4-1 with it open one or twice (it forks one child process and terminates after the child exits, so the second /dev/null is the child). But nothing besides that with either process. Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 16:17:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from field.videotron.net (field.videotron.net [205.151.222.108]) by hub.freebsd.org (Postfix) with ESMTP id DB16537B6EB for ; Sun, 19 Mar 2000 16:17:27 -0800 (PST) (envelope-from luc_m@videotron.ca) Received: from videotron.ca ([24.200.211.63]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FRP00HBU1O859@field.videotron.net> for stable@freebsd.org; Sun, 19 Mar 2000 19:07:25 -0500 (EST) Date: Sun, 19 Mar 2000 19:06:57 -0500 From: Luc Morin Subject: CD problems after upgrade to 4.0 To: stable@freebsd.org Message-id: <38D56BA0.79A31C82@videotron.ca> MIME-version: 1.0 X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-STABLE i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, After upgrading my system to 4.0 with sources (cvsup), I'm experiencing problems with my CD player. I can't mount any CD, nor can I listen to any music CD. When I try to mount, I get: cd9660: Device not configured and when I try to access using wmcdplay I get: wmcdplay : Unable to open cdrom device '/dev/cdrom'. I have the following in my kernel config file: options CD9660 ... device ata device atadisk device atapicd options ATA_STATIC_ID I also have the following entries in /dev: bash-2.03# cd /dev/ bash-2.03# ls acd* acd0a acd0c acd1a acd1c bash-2.03# ls -l cdrom lrwxr-xr-x 1 root wheel 5 Mar 19 15:58 cdrom -> acd0a And the following entry in /etc/fstab: /dev/acd0c /cdrom cd9660 ro,noauto 0 0 As I write this, I notice the different references to acd0a and acd0c... what should I be using ? Have I overlooked anything else? Thanks Luc Morin Electrical Engineering Technologist To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 16:28:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zipcode.corp.home.net (zipcode.corp.home.net [24.0.26.58]) by hub.freebsd.org (Postfix) with ESMTP id E7AED37B828 for ; Sun, 19 Mar 2000 16:28:26 -0800 (PST) (envelope-from manek@ecst.csuchico.edu) Received: from after (shiva-user28.corp.home.net [24.0.8.158]) by zipcode.corp.home.net (8.9.3/8.9.3) with SMTP id QAA04546 for ; Sun, 19 Mar 2000 16:28:19 -0800 (PST) From: "Sameer R. Manek" To: Subject: unusual cvsup message Date: Sun, 19 Mar 2000 16:28:36 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got this message on a cvsup performed today, at about Sun Mar 19 15:07:18 PST 2000, anyone else get a similar message? and should i be concerned about it? Sameer Connected to cvsup.freebsd.org Updating collection src-all/cvs Edit src/release/sysinstall/menus.c Edit src/share/man/man9/VOP_ATTRIB.9 Edit src/sys/boot/pc98/libpc98/biosdisk.c Edit src/sys/contrib/dev/oltr/if_oltr.c Edit src/sys/contrib/dev/oltr/trlld.h src/sys/contrib/dev/oltr/trlld.h: Cannot get edited text: "d" edit command specifies line past end of base delta -- will transfer entire file Edit src/sys/contrib/dev/oltr/trlldbm.c Edit src/sys/contrib/dev/oltr/trlldhm.c Edit src/sys/contrib/dev/oltr/trlldmac.c Edit src/sys/dev/kbd/kbdtables.h Edit src/sys/i386/i386/k6_mem.c Edit src/sys/i386/i386/pmap.c Edit src/sys/pc98/i386/machdep.c Edit src/sys/pc98/pc98/olpt.c Edit src/sys/pc98/pc98/pc98_machdep.c Edit src/sys/pc98/pc98/pc98_machdep.h Applying fixups for collection src-all/cvs Fixup src/sys/contrib/dev/oltr/trlld.h Finished successfully To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 16:47:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.twave.net (twave.net [206.100.228.5]) by hub.freebsd.org (Postfix) with SMTP id 9DCD337B5D8 for ; Sun, 19 Mar 2000 16:47:16 -0800 (PST) (envelope-from brameld@twave.net) Received: from [208.47.188.83] by mail.twave.net (NTMail 3.03.0018/1.abwg) with ESMTP id ta331103 for ; Sun, 19 Mar 2000 19:47:04 -0500 From: Walter Brameld To: Sergei Vyshenski , freebsd-stable@freebsd.org Subject: Re: tun0 lost in 4.0 Date: Sun, 19 Mar 2000 19:45:59 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <3.0.5.32.20000320010755.007b6500@vivaldi> In-Reply-To: <3.0.5.32.20000320010755.007b6500@vivaldi> MIME-Version: 1.0 Message-Id: <00031919470101.01387@Bozo_3.BozoLand.domain> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 19 Mar 2000, in a never-ending search for enlightenment, Sergei Vyshenski wrote: > Can not revive tun0 interface after moving to 4.0 from 3.4 > in a way that src/UPDATING teaches. > > Kernel file has "pseudo-device tun 1", kernel builds ok; > ./MAKEDEV tun0 in /dev does not complain; > bbut ifconfig says: "interface tun0 does not exist" > > Actually, I need tun0 to accept incoming user-ppp, > and would be happy to hear of workaround at least. > > Thank you in advance. > Sergei Believe it should only be "pseudo-device tun" with no "1". -- Walter Brameld Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? Walter: Where the hell am I? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 17: 1:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from awfulhak.org (dynamic-118.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.246]) by hub.freebsd.org (Postfix) with ESMTP id 0084037B820 for ; Sun, 19 Mar 2000 17:01:38 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA16922; Mon, 20 Mar 2000 00:57:04 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA22832; Mon, 20 Mar 2000 00:56:52 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200003200056.AAA22832@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Sergei Vyshenski Cc: freebsd-stable@FreeBSD.ORG, brian@hak.lan.awfulhak.org Subject: Re: tun0 lost in 4.0 In-Reply-To: Message from Sergei Vyshenski of "Mon, 20 Mar 2000 01:07:55 +0300." <3.0.5.32.20000320010755.007b6500@vivaldi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 20 Mar 2000 00:56:52 +0000 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can not revive tun0 interface after moving to 4.0 from 3.4 > in a way that src/UPDATING teaches. > > Kernel file has "pseudo-device tun 1", kernel builds ok; > ./MAKEDEV tun0 in /dev does not complain; > but ifconfig says: "interface tun0 does not exist" > > Actually, I need tun0 to accept incoming user-ppp, > and would be happy to hear of workaround at least. Just start ppp. The open() of the tun device creates the interface. > Thank you in advance. > Sergei -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 17: 6:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id AEE8E37B6FE for ; Sun, 19 Mar 2000 17:06:41 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p51-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.52]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id KAA18848; Mon, 20 Mar 2000 10:06:25 +0900 (JST) Message-ID: <38D57225.9039963@newsguy.com> Date: Mon, 20 Mar 2000 09:34:45 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Warner Losh Cc: Richard Wackerbarth , stable@FreeBSD.ORG Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions References: <00031811062100.03963@nomad.dataplex.net> <200003190442.VAA04896@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > These old days must predate my involvement in unix.... > > I have a system with 3 bsd partitions. The first one is 4.0, the > second 3.4 stable and the third is unused. I've not been able to get > the boot0 boot loader to boot off the second partition. I've been > able to get /boot/loader to do it w/o much of a problem: > set currdev=disk1s2: > unload > boot /kernel > although I suppose that I could also say boot disk1s2:/kernel You can have a menu come up and offer the choice between the partitions, and then boot one of them if timed out. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 17: 8:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7053337B805 for ; Sun, 19 Mar 2000 17:08:14 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA15691; Sun, 19 Mar 2000 18:08:12 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA10951; Sun, 19 Mar 2000 18:08:05 -0700 (MST) Message-Id: <200003200108.SAA10951@harmony.village.org> To: "Daniel C. Sobral" Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions Cc: Richard Wackerbarth , stable@FreeBSD.ORG In-reply-to: Your message of "Mon, 20 Mar 2000 09:34:45 +0900." <38D57225.9039963@newsguy.com> References: <38D57225.9039963@newsguy.com> <00031811062100.03963@nomad.dataplex.net> <200003190442.VAA04896@harmony.village.org> Date: Sun, 19 Mar 2000 18:08:05 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38D57225.9039963@newsguy.com> "Daniel C. Sobral" writes: : You can have a menu come up and offer the choice between the partitions, : and then boot one of them if timed out. How? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 17:21:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 56B9D37B805 for ; Sun, 19 Mar 2000 17:21:50 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p20-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.149]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id KAA20808; Mon, 20 Mar 2000 10:21:38 +0900 (JST) Message-ID: <38D57CAD.B7B06F3@newsguy.com> Date: Mon, 20 Mar 2000 10:19:41 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Warner Losh Cc: Richard Wackerbarth , stable@FreeBSD.ORG Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions References: <38D57225.9039963@newsguy.com> <00031811062100.03963@nomad.dataplex.net> <200003190442.VAA04896@harmony.village.org> <200003200108.SAA10951@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <38D57225.9039963@newsguy.com> "Daniel C. Sobral" writes: > : You can have a menu come up and offer the choice between the partitions, > : and then boot one of them if timed out. > > How? There is an example of that on /usr/share/examples/bootforth. There are two examples there, and they share a couple of files. If you have any trouble, just ask. I have this precise setup running on my computer. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 17:26:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from weeble.dyndns.org (ubppp248-206.dialin.buffalo.edu [128.205.248.206]) by hub.freebsd.org (Postfix) with ESMTP id 8C02037B6FE for ; Sun, 19 Mar 2000 17:26:24 -0800 (PST) (envelope-from cjm2@earthling.net) Received: from shithead (shithead.weeble.dyndns.org [10.0.0.2]) by weeble.dyndns.org (8.9.3/8.9.3) with SMTP id UAA02193; Sun, 19 Mar 2000 20:26:24 -0500 (EST) (envelope-from cjm2@earthling.net) From: "C J Michaels" To: "Luc Morin" Cc: "FreeBSD Stable" Subject: RE: CD problems after upgrade to 4.0 Date: Sun, 19 Mar 2000 20:26:30 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <38D56BA0.79A31C82@videotron.ca> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Take a look at dmesg output, is the CD-ROM being detected? and if so, make sure the /dev/cdrom link is pointing to the right device. -Chris -----Original Message----- From: owner-freebsd-stable@FreeBSD.ORG [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Luc Morin Sent: Sunday, March 19, 2000 7:07 PM To: stable@FreeBSD.ORG Subject: CD problems after upgrade to 4.0 Hi all, After upgrading my system to 4.0 with sources (cvsup), I'm experiencing problems with my CD player. I can't mount any CD, nor can I listen to any music CD. When I try to mount, I get: cd9660: Device not configured and when I try to access using wmcdplay I get: wmcdplay: Unable to open cdrom device '/dev/cdrom'. I have the following in my kernel config file: options CD9660 ... device ata device atadisk device atapicd options ATA_STATIC_ID I also have the following entries in /dev: bash-2.03# cd /dev/ bash-2.03# ls acd* acd0a acd0c acd1a acd1c bash-2.03# ls -l cdrom lrwxr-xr-x 1 root wheel 5 Mar 19 15:58 cdrom -> acd0a And the following entry in /etc/fstab: /dev/acd0c /cdrom cd9660 ro,noauto 0 0 As I write this, I notice the different references to acd0a and acd0c... what should I be using ? Have I overlooked anything else? Thanks Luc Morin Electrical Engineering Technologist 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 Mar 19 17:42:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cr759667-a.nvcr1.bc.wave.home.com (cr759667-a.nvcr1.bc.wave.home.com [24.113.130.83]) by hub.freebsd.org (Postfix) with ESMTP id 2CEED37B702 for ; Sun, 19 Mar 2000 17:42:57 -0800 (PST) (envelope-from freebsdstable@cr759667-a.nvcr1.bc.wave.home.com) Received: from localhost (freebsdstable@localhost) by cr759667-a.nvcr1.bc.wave.home.com (8.9.3/8.9.3) with ESMTP id RAA24649 for ; Sun, 19 Mar 2000 17:45:35 -0800 (PST) (envelope-from freebsdstable@cr759667-a.nvcr1.bc.wave.home.com) Date: Sun, 19 Mar 2000 17:45:35 -0800 (PST) From: freebsd stable To: freebsd-stable@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 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 Sun Mar 19 18:20:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 6652B37B73C; Sun, 19 Mar 2000 18:20:03 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id SAA43512; Sun, 19 Mar 2000 18:18:30 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200003200218.SAA43512@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Brandon D. Valentine" Cc: Cameron Grant , Conrad Sabatier , stable@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Suggestions for improving newpcm performance? In-reply-to: Your message of "Sun, 19 Mar 2000 17:36:44 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 19 Mar 2000 18:18:30 -0800 From: Amancio Hasty Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Tnks for you support before I can contemplate the work on voxware there is one device driver which I must write ahead of the queue. Best Regards > On Sun, 19 Mar 2000, Amancio Hasty wrote: > > >I can't promise anything specially since I have a new job;nevertheless, before > >you decide to toast the voxware from current send me mail . If -core decides > >to toast voxware I will probably pick up the maintainence of voxware from > >right here were maintainence of voxware used to be. The latter is not a bad > >idea since it will avoid conflicts between -core and I. > > > >-- > > Amancio Hasty > > hasty@rah.star-gate.com > > I too would be rather remiss to see voxware axed from current. I have a > plethora of real creative cards in use that I just love voxware for. > I've never quite had the same luck under pcm with them. I don't know an > awful lot about sound drivers, or voxware in particular, but if you are > willing to pick this up I don't mind testing code. > > ------------------------------------------------------------- > | -Brandon D. Valentine bandix at looksharp.net > | bandix on EFnet IRC BVRiker on AIM > ------------------------------------------------------------- > | "...and as for hackers, we note that all of those known to > | The Register are so strapped financially that seizing their > | property would be tantamount to squeezing blood from a > | stone." -- The Register, 02/17/2000 > ------------------------------------------------------------- > -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 18:25:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp10.nwnexus.com (smtp10.nwnexus.com [206.63.63.53]) by hub.freebsd.org (Postfix) with ESMTP id 92CFD37B873; Sun, 19 Mar 2000 18:25:21 -0800 (PST) (envelope-from wrsomsky@halcyon.com) Received: from gramarye (evt-lx102-ip8.nwnexus.net [204.57.235.108]) by smtp10.nwnexus.com (8.8.8/8.8.8) with ESMTP id SAA13284; Sun, 19 Mar 2000 18:25:17 -0800 (PST) Received: (from wrsomsky@localhost) by gramarye (8.9.3/8.9.3) id SAA00288; Sun, 19 Mar 2000 18:20:24 -0800 (PST) (envelope-from wrsomsky) Date: Sun, 19 Mar 2000 18:20:24 -0800 From: "William R. Somsky" To: Brandon Fosdick Cc: Warner Losh , Doug Barton , Josef Karthauser , Ruslan Ermilov , stable@FreeBSD.ORG Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions Message-ID: <20000319182024.A249@gramarye.halcyon.com> References: <200003152159.OAA89926@harmony.village.org> <38D03E64.3D17FC34@glue.umd.edu> <38D3AB72.366D851D@glue.umd.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <38D3AB72.366D851D@glue.umd.edu>; from bfoz@glue.umd.edu on Sat, Mar 18, 2000 at 11:14:42AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm... I ran into this problem/difficulty that you may want to warn people about. I had partitions w/ bad144 bad-sector mapping in them. And the new ata drivers don't do that any more, so I couldn't boot the new kernel. I had to boot the old, backup, repartition, relabel, reinstall and then continue w/ the ->4.0 update. ________________________________________________________________________ William R. Somsky wrsomsky@halcyon.com Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 18:40:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from field.videotron.net (field.videotron.net [205.151.222.108]) by hub.freebsd.org (Postfix) with ESMTP id C54EE37B879 for ; Sun, 19 Mar 2000 18:40:51 -0800 (PST) (envelope-from luc_m@videotron.ca) Received: from videotron.ca ([24.200.211.63]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FRP0071G8MZUO@field.videotron.net> for stable@freebsd.org; Sun, 19 Mar 2000 21:37:48 -0500 (EST) Date: Sun, 19 Mar 2000 21:37:24 -0500 From: Luc Morin Subject: Re: CD problems after upgrade to 4.0 To: stable@freebsd.org Message-id: <38D58EE4.49360A86@videotron.ca> MIME-version: 1.0 X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-STABLE i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en References: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG C J Michaels wrote: > Take a look at dmesg output, is the CD-ROM being detected? and if so, make > sure the /dev/cdrom link is pointing to the right device. > > -Chris > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Luc Morin > Sent: Sunday, March 19, 2000 7:07 PM > To: stable@FreeBSD.ORG > Subject: CD problems after upgrade to 4.0 > > Hi all, > > After upgrading my system to 4.0 with sources (cvsup), I'm experiencing > problems with my CD player. > > I can't mount any CD, nor can I listen to any music CD. When I try to > mount, I get: > > cd9660: Device not configured > > and when I try to access using wmcdplay I get: > > wmcdplay: Unable to open cdrom device '/dev/cdrom'. > > I have the following in my kernel config file: > > options CD9660 > > ... > > device ata > device atadisk > device atapicd > options ATA_STATIC_ID > > I also have the following entries in /dev: > > bash-2.03# cd /dev/ > bash-2.03# ls acd* > acd0a acd0c acd1a acd1c > bash-2.03# ls -l cdrom > lrwxr-xr-x 1 root wheel 5 Mar 19 15:58 cdrom -> acd0a > > And the following entry in /etc/fstab: > > /dev/acd0c /cdrom cd9660 ro,noauto 0 > 0 > > As I write this, I notice the different references to acd0a and acd0c... > what should I be using ? > > Have I overlooked anything else? > > Thanks > > Luc Morin > Electrical Engineering Technologist > > 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 bash-2.03# dmesg | grep acd acd0: CDROM at ata0-slave using PIO4 bash-2.03# cd /dev bash-2.03# rm acd* bash-2.03# ./MAKEDEV acd0 bash-2.03# ls acd0* acd0a acd0c bash-2.03# rm cdrom bash-2.03# ln -s acd0a cdrom bash-2.03# mount /cdrom cd9660: Device not configured bash-2.03# rm cdrom bash-2.03# ln -s acd0c cdrom bash-2.03# mount /cdrom cd9660: Device not configured Now, why does it say the device cd9660 is not configured ? bash-2.03# uname -a FreeBSD southpark.videotron.ca 4.0-STABLE FreeBSD 4.0-STABLE #0: Sun Mar 19 15:42:13 EST 2000 root@southpark.videotron.ca:/usr/src/sys/compile/MYKERN4 i386 bash-2.03# grep CD9660 /usr/src/sys/i386/conf/MYKERN4 options CD9660 #ISO 9660 Filesystem #options CD9660_ROOT #CD-ROM usable as root, CD9660 required As far as I'm concerned, I don't need the CD9660_ROOT option, so that shouldn't be causing any problems, right ? Here's the complete dmesg output: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-STABLE #0: Sun Mar 19 15:42:13 EST 2000 root@southpark.videotron.ca:/usr/src/sys/compile/MYKERN4 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383f9ff real memory = 67092480 (65520K bytes) avail memory = 62148608 (60692K bytes) Preloaded elf kernel "kernel" at 0xc02d4000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02d409c. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 11 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xb800-0xb80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 4.2 irq 12 chip1: port 0xe800-0xe80f at device 4.3 on pci0 pcm0: port 0xb000-0xb03f irq 10 at device 10.0 on pci0 ed0: port 0xa800-0xa81f irq 12 at device 13.0 on pci0 ed0: supplying EUI64: 00:e0:29:ff:fe:40:c0:4f ed0: address 00:e0:29:40:c0:4f, type NE2000 (16 bit) 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-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: IEEE1284 device found /NIBBLE/ECP Probing for PnP devices on ppbus0: ppbus0: PRINTER MLC,PCL,PJL lpt0: on ppbus0 lpt0: Interrupt-driven port IP Filter: initialized. Default = pass all, Logging = disabled IP Filter: v3.3.8 ad0: 13216MB [26853/16/63] at ata0-master using UDMA33 ad2: 8063MB [16383/16/63] at ata1-master using UDMA33 ad3: 3079MB [6256/16/63] at ata1-slave using UDMA33 acd0: CDROM at ata0-slave using PIO4 Mounting root from ufs:/dev/ad0s2a ed0: starting DAD for fe80:0001::02e0:29ff:fe40:c04f ed0: DAD complete for fe80:0001::02e0:29ff:fe40:c04f - no duplicates found Thanks for any additional hint. Luc Morin Electrical Engineering Technologist To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 19: 2:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from charon.ipass.net (charon.ipass.net [198.79.53.8]) by hub.freebsd.org (Postfix) with ESMTP id C012F37B83C; Sun, 19 Mar 2000 19:02:26 -0800 (PST) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-1-177.dialup.rdu.ipass.net [209.170.132.177]) by charon.ipass.net (8.9.3/8.9.3) with ESMTP id WAA00115; Sun, 19 Mar 2000 22:02:23 -0500 (EST) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id WAA66588; Sun, 19 Mar 2000 22:04:53 -0500 (EST) (envelope-from rhh) Date: Sun, 19 Mar 2000 22:04:53 -0500 From: Randall Hopper To: Amancio Hasty , Cameron Grant Cc: Conrad Sabatier , stable@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Suggestions for improving newpcm performance? Message-ID: <20000319220453.A65973@ipass.net> References: <200003191838.KAA40955@rah.star-gate.com> <000701bf91d5$4aebeb60$0304020a@NENYA> <001a01bf91c1$7f62a4b0$0304020a@NENYA> <200003191838.KAA40955@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003191838.KAA40955@rah.star-gate.com>; from hasty@rah.star-gate.com on Sun, Mar 19, 2000 at 10:38:01AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty: |> the situation with voxware is that it will remain in 4.x, but unless a |> maintainer comes forward who will convert it to newbus, in -current it will |> soon be toast. | |I can't promise anything specially since I have a new job; nevertheless, |before you decide to toast the voxware from current send me mail . If |-core decides to toast voxware I will probably pick up the maintainence |of voxware from right here were maintainence of voxware used to be. The |latter is not a bad idea since it will avoid conflicts between -core and I. Thanks for volunteering Amancio. Glad someone with driver-writing knowledge is going to pitch in. Along with Brandon, I too will volunteer to help you test and aid in keeping Voxware in shape, until such time as sufficient volunteering brings the new development driver up to Voxware's level of capability. Cameron Grant: |you should be aware that the voxware code will need extensive renovation and |conversion to newbus. already it will not cope with pnp devices, and the |compatibility shims it relies on will shortly be gone. | |in my opinion it would be far better to divert any effort you would be |willing to put in towards newpcm. That sounds fine in the abstract. But we should be concrete about the details before we go nixing code. - Have we identified exactly what functionality is missing in the new sound driver but supported by Voxware? - Have we got volunteers with time on their hands signed up to provide each piece of this functionality with estimated completion dates? IMO, the cut-over to PCM should be tied to the last of these completion dates, revised forward or backward as actual completion dates slip. Why would we transition any other way? Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 19:12:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3F8DF37B7AE for ; Sun, 19 Mar 2000 19:12:30 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id UAA16134; Sun, 19 Mar 2000 20:12:12 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id UAA11835; Sun, 19 Mar 2000 20:12:04 -0700 (MST) Message-Id: <200003200312.UAA11835@harmony.village.org> To: Cy Schubert - ITSD Open Systems Group Subject: Re: 4.0: EtherExpress16 disappeared? Cc: Vova Golubkov , "stable@FreeBSD.ORG" In-reply-to: Your message of "Sun, 19 Mar 2000 09:49:17 PST." <200003191750.JAA09645@cwsys.cwsent.com> References: <200003191750.JAA09645@cwsys.cwsent.com> Date: Sun, 19 Mar 2000 20:12:04 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003191750.JAA09645@cwsys.cwsent.com> Cy Schubert - ITSD Open Systems Group writes: : Had the same problem with my 3C509B (ep0). Disabled all unneeded : drivers (boot -c) and it now works. A comment in the -current archives : by Warner (IIRC) stated that other drivers may trash the card's : registers while probing for their supported hardware, causing your card : to become unresponsive. It was the ex driver that was causing my problem, but it seems to be fixed. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 19:15:49 2000 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 5FC6737BC82 for ; Sun, 19 Mar 2000 19:15:34 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.12 #1) id 12Wq9b-000OlW-00; Mon, 20 Mar 2000 00:34:43 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7) id 12Wq9b-0001EN-00; Mon, 20 Mar 2000 00:34:43 +0000 Date: Mon, 20 Mar 2000 00:34:43 +0000 From: Ben Smithurst To: Luc Morin Cc: stable@freebsd.org Subject: Re: CD problems after upgrade to 4.0 Message-ID: <20000320003443.B87822@strontium.scientia.demon.co.uk> References: <38D56BA0.79A31C82@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38D56BA0.79A31C82@videotron.ca> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luc Morin wrote: > I also have the following entries in /dev: > > bash-2.03# cd /dev/ > bash-2.03# ls acd* > acd0a acd0c acd1a acd1c > bash-2.03# ls -l cdrom > lrwxr-xr-x 1 root wheel 5 Mar 19 15:58 cdrom -> acd0a > > And the following entry in /etc/fstab: > > /dev/acd0c /cdrom cd9660 ro,noauto 0 > 0 > > > As I write this, I notice the different references to acd0a and acd0c... > what should I be using ? I've always used the 'c' partition on CDs. I don't know whether that's your problem with audio CDs, but that shouldn't affect "mount /cdrom" operation. > Have I overlooked anything else? I assume the CD is detected at boot time? 'dmesg | grep acd' -- Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 19:16: 3 2000 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 264E537BDEF for ; Sun, 19 Mar 2000 19:15:54 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.12 #1) id 12Wq7Z-000OlP-00; Mon, 20 Mar 2000 00:32:37 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7) id 12Wq7Z-0000h4-00; Mon, 20 Mar 2000 00:32:37 +0000 Date: Mon, 20 Mar 2000 00:32:37 +0000 From: Ben Smithurst To: Sergei Vyshenski Cc: freebsd-stable@freebsd.org Subject: Re: tun0 lost in 4.0 Message-ID: <20000320003237.A87822@strontium.scientia.demon.co.uk> References: <3.0.5.32.20000320010755.007b6500@vivaldi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3.0.5.32.20000320010755.007b6500@vivaldi> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sergei Vyshenski wrote: > Can not revive tun0 interface after moving to 4.0 from 3.4 > in a way that src/UPDATING teaches. > > Kernel file has "pseudo-device tun 1", kernel builds ok; > ./MAKEDEV tun0 in /dev does not complain; > but ifconfig says: "interface tun0 does not exist" > > Actually, I need tun0 to accept incoming user-ppp, > and would be happy to hear of workaround at least. I have a feeling there's something funny about tun devices now, IIRC hearing they're created on demand or something... What error is ppp(8) giving you? -- Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 19:22:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from charon.ipass.net (charon.ipass.net [198.79.53.8]) by hub.freebsd.org (Postfix) with ESMTP id CF23E37BCAB for ; Sun, 19 Mar 2000 19:22:37 -0800 (PST) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-1-177.dialup.rdu.ipass.net [209.170.132.177]) by charon.ipass.net (8.9.3/8.9.3) with ESMTP id WAA01937; Sun, 19 Mar 2000 22:22:31 -0500 (EST) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id WAA67226; Sun, 19 Mar 2000 22:25:01 -0500 (EST) (envelope-from rhh) Date: Sun, 19 Mar 2000 22:25:01 -0500 From: Randall Hopper To: David Kelly Cc: stable@FreeBSD.ORG Subject: Re: Netscape pegs CPU on XServer kill Message-ID: <20000319222501.A66999@ipass.net> References: <200003190148.TAA45044@nospam.hiwaay.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003190148.TAA45044@nospam.hiwaay.net>; from dkelly@hiwaay.net on Sat, Mar 18, 2000 at 07:48:24PM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Kelly: |Speaking of which, am I the only one seeing: | |pid 4106 (communicator-4.7), uid 928: exited on signal 10 (core dumped) |pid 4113 (communicator-4.7), uid 928: exited on signal 10 (core dumped) |pid 4211 (communicator-4.7), uid 928: exited on signal 10 (core dumped) |pid 4215 (communicator-4.7), uid 928: exited on signal 10 (core dumped) |pid 4219 (communicator-4.7), uid 928: exited on signal 10 (core dumped) | |on *every* exit of the FreeBSD native U.S. Communicator? Same thing |with 4.7 and 4.72. Think this started when I upgraded XFree86 from |3.3.1 to 3.3.6, built from the port. Hmm. I've not even seen this. Just as a data point, most recently, I'm running 3.4-R, XFree86 3.3.5 depth 16, Netscape Navigator 4.72 from ports. Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 19:28: 4 2000 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 7C0BB37BA34 for ; Sun, 19 Mar 2000 19:28:00 -0800 (PST) (envelope-from jcm@dogma.freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3) for freebsd-stable@freebsd.org id 12WsrH-000A5j-00; Mon, 20 Mar 2000 03:27:59 +0000 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id DAA52093 for freebsd-stable@freebsd.org; Mon, 20 Mar 2000 03:27:58 GMT (envelope-from jcm) Date: Mon, 20 Mar 2000 03:27:58 +0000 From: J McKitrick To: freebsd-stable@freebsd.org Subject: Re: serial probs in 4.0 Message-ID: <20000320032758.A48883@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 don't know if this will help anyone, but i did 2 things that *might have solved the serial problem on my machine. I just deleted the cuaa devices and remade them. My serial port modem ended up on cuaa4, which was strange, but at least it worked. Then, when i removed everything after sio0 from the kernel config, the modem showed up at cuaa1, where it used to be under 3.4. I don't know if this is what solved my problem, but it's worth a shot if you are still having problems. I had the *exact* same thing... it opened under term, and accepted keystrokes, but didn't answer to AT commands. jm -- -------------------------------------------- Jonathon McKitrick -- jcm@freebsd-uk.eu.org "Doors to the pleasures of heaven or hell, and i didn't care which." -------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 20: 3:51 2000 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 8D2DC37B7EB; Sun, 19 Mar 2000 20:03:42 -0800 (PST) (envelope-from gandalf@vilnya.demon.co.uk) Received: from vilnya.demon.co.uk ([158.152.19.238]) by finch-post-12.mail.demon.net with esmtp (Exim 2.12 #1) id 12WtPm-000CCN-0C; Mon, 20 Mar 2000 04:03:39 +0000 Received: from NENYA (nenya.rings [10.2.4.3]) by vilnya.demon.co.uk (Postfix) with SMTP id 336A6D9AD; Mon, 20 Mar 2000 04:03:22 +0000 (GMT) Message-ID: <005d01bf9221$4660ac60$0304020a@NENYA> From: "Cameron Grant" To: "Randall Hopper" , "Amancio Hasty" Cc: "Conrad Sabatier" , , References: <200003191838.KAA40955@rah.star-gate.com> <000701bf91d5$4aebeb60$0304020a@NENYA> <001a01bf91c1$7f62a4b0$0304020a@NENYA> <200003191838.KAA40955@rah.star-gate.com> <20000319220453.A65973@ipass.net> Subject: Re: Suggestions for improving newpcm performance? Date: Mon, 20 Mar 2000 04:03:39 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Cameron Grant: > |you should be aware that the voxware code will need extensive renovation and > |conversion to newbus. already it will not cope with pnp devices, and the > |compatibility shims it relies on will shortly be gone. > | > |in my opinion it would be far better to divert any effort you would be > |willing to put in towards newpcm. > > That sounds fine in the abstract. But we should be concrete about the > details before we go nixing code. > > - Have we identified exactly what functionality is missing in the new > sound driver but supported by Voxware? to my knowledge, midi is the only functionality missing. also, multiple opens of /dev/dsp are not yet implemented. both will be soon. > - Have we got volunteers with time on their hands signed up to provide > each piece of this functionality with estimated completion dates? > > IMO, the cut-over to PCM should be tied to the last of these completion > dates, revised forward or backward as actual completion dates slip. > > Why would we transition any other way? because various functionality voxware uses is now optional and will be gone in the coming weeks. the kernel does not revolve around sound, and voxware is an acceptable loss. once the isa shims are gone, voxware will not compile without being newbusified which is a task of great magnitude. at this time, the point is moot. unless someone comes forward with a newbusified voxware, it will be removed soon. i, and others, will want to see code, not promises. -cg, not meaning to sound harsh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 20:19:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.ufl.edu (sp28fe.nerdc.ufl.edu [128.227.128.108]) by hub.freebsd.org (Postfix) with ESMTP id BA75C37B53A for ; Sun, 19 Mar 2000 20:19:47 -0800 (PST) (envelope-from saxonww@ufl.edu) Received: from n44-230.dhnet.ufl.edu (gremlin@[128.227.44.230]) by smtp.ufl.edu (8.9.3/8.9.3/2.2.1) with ESMTP id XAA130510; Sun, 19 Mar 2000 23:19:38 -0500 Date: Sun, 19 Mar 2000 23:19:38 -0500 (EST) From: Will Saxon X-Sender: gremlin@localhost To: Randall Hopper Cc: David Kelly , stable@FreeBSD.ORG Subject: Re: Netscape pegs CPU on XServer kill In-Reply-To: <20000319222501.A66999@ipass.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 It seems that it doesnt happen to all people, I for one have Netscape coredump 90% of the time when I exit it. Maybe there is an issue with the way window managers close programs when you close the window (instead of exiting the program) ? -Will On Sun, 19 Mar 2000, Randall Hopper wrote: > David Kelly: > |Speaking of which, am I the only one seeing: > | > |pid 4106 (communicator-4.7), uid 928: exited on signal 10 (core dumped) > |pid 4113 (communicator-4.7), uid 928: exited on signal 10 (core dumped) > |pid 4211 (communicator-4.7), uid 928: exited on signal 10 (core dumped) > |pid 4215 (communicator-4.7), uid 928: exited on signal 10 (core dumped) > |pid 4219 (communicator-4.7), uid 928: exited on signal 10 (core dumped) > | > |on *every* exit of the FreeBSD native U.S. Communicator? Same thing > |with 4.7 and 4.72. Think this started when I upgraded XFree86 from > |3.3.1 to 3.3.6, built from the port. > > Hmm. I've not even seen this. Just as a data point, most recently, I'm > running 3.4-R, XFree86 3.3.5 depth 16, Netscape Navigator 4.72 from ports. > > > Randall > > > 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 Mar 19 20:21:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by hub.freebsd.org (Postfix) with ESMTP id 5F21C37B8C0 for ; Sun, 19 Mar 2000 20:21:29 -0800 (PST) (envelope-from stuyman@confusion.net) Received: from confusion.net (user-2ive6e6.dialup.mindspring.com [165.247.25.198]) by tisch.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id XAA18347; Sun, 19 Mar 2000 23:21:13 -0500 (EST) Message-ID: <38D5A662.F6230787@confusion.net> Date: Sun, 19 Mar 2000 23:17:38 -0500 From: Laurence Berland Organization: B.R.A.T.T. X-Mailer: Mozilla 4.5 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: Thomas David Rivers , freebsd-stable@FreeBSD.ORG Subject: Re: Is 4.0 the next `to ship' from Walnut Creek? References: <21461.953457355@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Silly follow-up, to try and figure out why I'm so screwed up in the head (you don't need to tell me, I already know it's true :). What does this paragraph from http://www.cdrom.com/titles/freebsd/bsd40offer.phtml mean? "If you are a current FreeBSD Snapshot subscriber you will be getting 4.0 at YOUR special discount rate and it WILL be sent to you automatically as a thank you for being on the front-lines of bug-checking etc. This offer however is only good for Current Snapshot Subscribers and New Snapshot Subscribers who sign up before 4.0 is released. After that you'll have to pay full price. If you are interested in subscribing to the FreeBSD Snapshot, check out this page. " Probably being dumb and missing the point, {I blame my immaturity} Laurence "Jordan K. Hubbard" wrote: > > > If you've subscribed to the snapshots though, there's some exception, or > > so I heard. Care to shed some light on this? (my reading of the web > > page is that snap subscribers WILL get 4.0 by default, am I screwed up > > in the head?) > > I'd rather not answer that last question. :) Suffice it to say that > snapshot customers are NOT getting 4.0. It's a mainstream release and > those don't count as snapshots. > > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Laurence Berland, Stuyvesant HS Debate <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. http://stuy.debate.net icq #7434346 aol imer E1101 The above email Copyright (C) 2000 Laurence Berland All rights reserved To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 20:27:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.nerv.nu (cx639627-c.irvn1.occa.home.com [24.0.209.134]) by hub.freebsd.org (Postfix) with ESMTP id 826FE37B79A; Sun, 19 Mar 2000 20:27:41 -0800 (PST) (envelope-from nugundam@nerv.nu) Received: from localhost (nugundam@localhost) by mail.nerv.nu (8.9.3/8.9.3) with ESMTP id UAA00541; Sun, 19 Mar 2000 20:33:32 -0800 (PST) (envelope-from nugundam@greenwood3.nerv.nu) Date: Sun, 19 Mar 2000 20:33:32 -0800 (PST) From: Joseph Lee To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Cc: msmith@freebsd.org Subject: netgear fa410TX and 4.x problems 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 read from the archives that a few people (such as Mike Smith) has had success using the Netgear 410TX pcmcia card in -current (or 4.x). I've just made a successful transition from 3.4-release+PAO to 4.x, but my 410tx card is not working anymore. Specifically, it's being detected as some NE1000 8-bit card. Is there any special settings I should be aware of to get the card to work? I've done the device card, device pcic0 additions into the kernel. Thanks, Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ # Anime Expo 2000 >> www.anime-expo.org/ > # FreeBSD: The Power to Serve >> www.freebsd.org > # The Ultimate Online Speed-Shop >> www.racesearch.com / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 20:45:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id 870CE37B8B2 for ; Sun, 19 Mar 2000 20:45:33 -0800 (PST) (envelope-from stuyman@confusion.net) Received: from confusion.net (user-2ive6e6.dialup.mindspring.com [165.247.25.198]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id XAA03334; Sun, 19 Mar 2000 23:45:25 -0500 (EST) Message-ID: <38D5AC0E.D2906589@confusion.net> Date: Sun, 19 Mar 2000 23:41:50 -0500 From: Laurence Berland Organization: B.R.A.T.T. X-Mailer: Mozilla 4.5 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Clifton Royston Cc: stable@freebsd.org Subject: Re: Small spaces References: <38D43E0E.1DDECC10@confusion.net> <20000318215028.C15998@lava.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What's worked for me now is: No X or games, no ports tree, only kernel source. Right now I don't have a network because we were using dialups, but at last DSL is here, so I'll compile my kernel locally, and then once I have everything set, i'll delete the sources and nfs mount them, and i'll install the ports tree (could those be mounted too? or will that cause issues?). Alternatively, I could just add a big hd to this and have the other machines NFS mount off this (but the other machines are so much faster...). Perhaps i'll find some money (yea right, I need to go to school [but I need a summer internship, if you're readin:)]) and build a system around the PPro I just grabbed on eBay...ah to dream. Let's get Bell Atlantic here with DSL first though. Thanks everyone for your help Grateful as ever, and always learning something new, Laurence PS: If I do enough crunchgen(1)ing, how small can bin and sbin get? Clifton Royston wrote: > > On Sat, Mar 18, 2000 at 09:40:14PM -0500, Laurence Berland wrote: > > I'm trying to install FreeBSD 3.4 on an old 486 I've got lying around to > > use as a NATing firewall for my home network, but I've only got a 200 > > Meg HD around. I'm gonna go get another HD later, but right now I'd > > like to get running with just that. So far I've been trying with 16 to > > swap and various other combinations, but it always seems to run out of > > /usr space. I figure / should be at least 32MB, and the rest (~152MB) > > goes to /usr. I'm trying to install the binaries, the docs, and the > > kernel source (but not the rest of the source). Any idea if it's even > > possible? Should I shrink down the root partition more? > > 32 is pretty minimal, I think; / will use nearly all of that. You > should try to see if you can trim what's in /usr a bit. Have you made > sure to ditch the games, as well as X? If you skip your kernel source > and do your compiles on another box (which I think you'd want to do > anyway!) you could ditch the kernel source, and then all the essential > binaries should be sure to fit into the remaining space of /usr. > > It should be doable; I had a very similar config (486-120, 16MB RAM, > 240MB HD) running just a few months ago on OpenBSD 2.5, which is pretty > similar in size of essential binaries & data space. Similar > application, too - home network firewall, in my case with IP filtering > for a DSL connection. (After a bit it got to be too much of a pain, so > last month I bought the smallest new hard drive I could find; this > turned out to be about 4GB, and space is no longer an issue.) > > -- Clifton > > -- > Clifton Royston -- LavaNet Systems Architect -- cliftonr@lava.net > The named which can be named is not the Eternal named. -- Laurence Berland, Stuyvesant HS Debate (In NYC) <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. http://stuy.debate.net icq #7434346 aol imer E1101 The above email Copyright (C) 2000 Laurence Berland All rights reserved To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 20:49:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.bankinter.es (dns.bankinter.es [195.235.30.34]) by hub.freebsd.org (Postfix) with ESMTP id 8C2AE37B7AE for ; Sun, 19 Mar 2000 20:49:17 -0800 (PST) (envelope-from feria@mac21.com) Received: from default (h027139.nexo.es [195.235.27.139]) by smtp.bankinter.es (8.8.8+Sun/8.8.8) with SMTP id FAA26688 for ; Mon, 20 Mar 2000 05:45:49 +0100 (MET) From: feria@mac21.com To: Subject: MAC21 Art Fair 2000 Date: Mon, 20 Mar 2000 05:44:56 +0100 Message-Id: <36605.239538657408000.2294@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG M A C 2 1 - 2000 International Contemporary Art Fair Feria Internacional de Arte Contemporáneo =============================================== Contenido: 1 ................. ENGLISH TEXT 2 ................. TEXTO EN ESPAŃOL **************** ENGLISH TEXT **************** You can visit actualized: www.mac21.com with complete information of 3 Edition of MAC21 - International Contemporary Art Fair, that will take place in the Fairs and Congresses Center of Marbella (Spain), from 19 to 23 July, 2000. Galleries, conditions, application, prices,... Moreover, information of the 2 Edition of Art-e-mail, International Exhibition of E-mails of Artists. MAC21 feria@mac21.com art-e-mail@mac21.com =============================================== We adhere to responsible e-mail ethics if you wish to be "removed" from future mailings, please click on this link mailto: publicidad@mac21.com?subject=REMOVE:stable@freebsd.org and hit send. =============================================== **************** TEXTO ESPAŃOL **************** Ya puedes visitar actualizada: www.mac21.com con toda la información de la 3 edicion de MAC21-Feria Internacional de Arte Contemporaneo, que se celebrara en el Palacio de Ferias y Congresos de Marbella (Espańa), del 19 al 23 de julio del 2000. Galerías, condiciones, inscripcion, precios,... Además, información de la 2 Edición de Art-e-mail, Exposición Internacional de E-mails de Artistas. MAC21 feria@mac21.com art-e-mail@mac21.com =============================================== Acogiendonos a la etica de la comunicacion por e-mail, si desea ser "borrado" de futuros envios, por favor pulse el siguiente link mailto: publicidad@mac21.com?subject=BORRAR:stable@freebsd.org y envie. =============================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 21: 8: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail0.bna.bellsouth.net (mail0.bna.bellsouth.net [205.152.150.12]) by hub.freebsd.org (Postfix) with ESMTP id EE4C537B6C5 for ; Sun, 19 Mar 2000 21:08:05 -0800 (PST) (envelope-from jim@siteplus.net) Received: from discover.siteplus.net (host-209-214-40-68.cha.bellsouth.net [209.214.40.68]) by mail0.bna.bellsouth.net (3.3.5alt/0.75.2) with ESMTP id AAA19812 for ; Mon, 20 Mar 2000 00:07:13 -0500 (EST) Date: Mon, 20 Mar 2000 00:08:00 -0500 (EST) From: Jim Weeks To: freebsd-stable@FreeBSD.ORG Subject: 4.0 make install problem 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 Ok, I finally got around to updating this machine from 3.4s to 4.0s. I followed the instructions and many of the tips from this list. Everything went well untill "make -DNOINFO installworld". Here is where things choked. chown -R root:wheel /usr/share/zoneinfo/* ===> sys ===> sys/boot ===> sys/boot/ficl ===> sys/boot/i386 ===> sys/boot/i386/mbr install -c -o root -g wheel -m 444 mbr /boot ===> sys/boot/i386/boot0 install -c -o root -g wheel -m 444 boot0 /boot ===> sys/boot/i386/kgzldr install -c -o root -g wheel -m 444 kgzldr.o /usr/lib ===> sys/boot/i386/btx ===> sys/boot/i386/btx/btx ===> sys/boot/i386/btx/btxldr ===> sys/boot/i386/btx/lib ===> sys/boot/i386/boot2 install -c -o root -g wheel -m 444 boot1 /boot/boot1 install -c -o root -g wheel -m 444 boot2 /boot/boot2 *** Error code 71 I checked the dates on /boot/boot1 and /boot/boot2. boot1 installed boot2 didn't I was in single user mode, I have made the changes to fstab, I have no trouble mounting the file systems, but I am confused as to why / mounted on wd0 as you can see from this df. /dev/wd0s1a 49583 23437 22180 51% / /dev/ad0s1g 1519667 266163 1131931 19% /bak /dev/ad0s1f 3125790 2447215 428512 85% /usr /dev/ad0s1e 19815 2932 15298 16% /var procfs 4 4 0 100% /proc By the way. I have rebooted again but didn't catch it in time to get to single user mode. I am presently in X and as you can see have most of my functionality. I notice that top doesn't work. Any ideas would be helpful. I will drop back to single user and finish the Install. Thanks, Jim A little knowledge is a DANGEROUS thing James W. Weeks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 21:12:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from server1.huntsvilleal.com (server1.huntsvilleal.com [207.13.224.7]) by hub.freebsd.org (Postfix) with ESMTP id B3FBC37B8C7; Sun, 19 Mar 2000 21:12:31 -0800 (PST) (envelope-from kris@hiwaay.net) Received: from barricuda.bsd.nws.net (kris.huntsvilleal.com [207.13.224.46]) by server1.huntsvilleal.com (8.9.3/8.9.3) with ESMTP id XAA30852; Sun, 19 Mar 2000 23:53:34 -0500 Received: from localhost (localhost [127.0.0.1]) by barricuda.bsd.nws.net (8.9.3/8.9.3) with ESMTP id XAA14087; Sun, 19 Mar 2000 23:11:45 -0600 (CST) (envelope-from kris@hiwaay.net) Date: Sun, 19 Mar 2000 23:11:05 -0600 (CST) From: Kris Kirby To: Amancio Hasty Cc: Cameron Grant , Conrad Sabatier , stable@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Suggestions for improving newpcm performance? In-Reply-To: <200003191930.LAA41341@rah.star-gate.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 > Don't forget that before there was any PNP support on FreeBSD there was > the guspnp and I know the voxware driver very well. Hmmm... I wish I had working MPU401 and OPL3 support.... If I had some documentation as to how OPL3 and MPU401 work, I could try some coding.... ----- Kris Kirby, KE4AHR | TGIFreeBSD... 'Nuff said. | ------------------------------------------------------- "God gave them the ability to reproduce... ... Science gave us the hope they won't." -KBK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 22:48:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id A1BEC37B8D0; Sun, 19 Mar 2000 22:44:34 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id WAA17338; Sun, 19 Mar 2000 22:44:35 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 19 Mar 2000 22:44:35 -0800 (PST) From: Kris Kennaway To: Dann Lunsford Cc: stable@freebsd.org Subject: Re: RELENG_4 and sound on a Toshiba laptop In-Reply-To: <20000319114021.A9089@greycat.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 Sun, 19 Mar 2000, Dann Lunsford wrote: > complete success. Way to go, Core Team! Just a note that the people you really should be thanking are the FreeBSD committers, not the core team who don't have any involvement in the day-to-day development of FreeBSD and just act as a management oversight body. But thanks anyway! :) Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 23:29:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ramstind.gtf.ol.no (ramstind.gtf.ol.no [128.39.174.16]) by hub.freebsd.org (Postfix) with ESMTP id 6886437B7C6 for ; Sun, 19 Mar 2000 23:29:13 -0800 (PST) (envelope-from trond@ramstind.gtf.ol.no) Received: from localhost (trond@localhost) by ramstind.gtf.ol.no (8.9.3/8.9.3) with ESMTP id IAA79453; Mon, 20 Mar 2000 08:29:03 +0100 (CET) (envelope-from trond@ramstind.gtf.ol.no) Date: Mon, 20 Mar 2000 08:29:03 +0100 (CET) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= To: Luc Morin Cc: stable@FreeBSD.ORG Subject: Re: CD problems after upgrade to 4.0 In-Reply-To: <38D56BA0.79A31C82@videotron.ca> Message-ID: 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 On Sun, 19 Mar 2000, Luc Morin wrote: > bash-2.03# ls acd* > acd0a acd0c acd1a acd1c > bash-2.03# ls -l cdrom > lrwxr-xr-x 1 root wheel 5 Mar 19 15:58 cdrom -> acd0a > > And the following entry in /etc/fstab: > > /dev/acd0c /cdrom cd9660 ro,noauto 0 > 0 > > > As I write this, I notice the different references to acd0a and acd0c... > what should I be using ? > > Have I overlooked anything else? I would just point out: No matter what you do with /dev/cdrom, /etc/fstab will use /dev/acd0c for /cdrom and not /dev/cdrom. I suggest you use /dev/acd0c since it refers to the entire cd-rom when loaded. ---------------------------------------------------------------------- Trond Endrestřl | trond@gtf.ol.no Merkantilvegen 59HB7, | trond@ramstind.gtf.ol.no N-2815 GJŘVIK, NORWAY |+47 61139424 || +47 63874242 Patron of The Art of Computer Programming| FreeBSD 3.4 & Pine 4.21 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 23:48: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id A439037B89B for ; Sun, 19 Mar 2000 23:48:00 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA24915; Sun, 19 Mar 2000 23:48:23 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Laurence Berland Cc: Thomas David Rivers , freebsd-stable@FreeBSD.ORG Subject: Re: Is 4.0 the next `to ship' from Walnut Creek? In-reply-to: Your message of "Sun, 19 Mar 2000 23:17:38 EST." <38D5A662.F6230787@confusion.net> Date: Sun, 19 Mar 2000 23:48:23 -0800 Message-ID: <24912.953538503@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry, I guess I was wrong! I hate to be wrong about my own product line, but it looks like WC decided to send 4.0 out to the SNAP subscribers as a kind of stop-gap measure since they're only shipping the usual subscribers 3.5 and 4.1, when they come out. Hmmm. OK, seems reasonable to me. :-) - Jordan > Silly follow-up, to try and figure out why I'm so screwed up in the head > (you don't need to tell me, I already know it's true :). What does this > paragraph from http://www.cdrom.com/titles/freebsd/bsd40offer.phtml > mean? > > "If you are a current FreeBSD Snapshot subscriber you will be getting > 4.0 at YOUR special discount rate and it WILL be sent to you > automatically as a thank you for being on the front-lines of > bug-checking etc. This offer however is only good for Current Snapshot > Subscribers and New Snapshot Subscribers who sign up before 4.0 is > released. After that you'll have to pay full price. If you are > interested in subscribing to the FreeBSD Snapshot, check out this page. > " > > > Probably being dumb and missing the point, > {I blame my immaturity} > Laurence > > "Jordan K. Hubbard" wrote: > > > > > If you've subscribed to the snapshots though, there's some exception, or > > > so I heard. Care to shed some light on this? (my reading of the web > > > page is that snap subscribers WILL get 4.0 by default, am I screwed up > > in the head?) > > > > I'd rather not answer that last question. :) Suffice it to say that > > snapshot customers are NOT getting 4.0. It's a mainstream release and > > those don't count as snapshots. > > > > - Jordan > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > -- > Laurence Berland, Stuyvesant HS Debate > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Windows 98: n. > useless extension to a minor patch release for > 32-bit extensions and a graphical shell for a > 16-bit patch to an 8-bit operating system > originally coded for a 4-bit microprocessor, > written by a 2-bit company that can't stand for > 1 bit of competition. > http://stuy.debate.net > icq #7434346 aol imer E1101 > The above email Copyright (C) 2000 Laurence Berland > All rights reserved To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 23:48:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id DCCDC37B803; Sun, 19 Mar 2000 23:48:15 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA16830; Mon, 20 Mar 2000 00:48:14 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA13449; Mon, 20 Mar 2000 00:48:06 -0700 (MST) Message-Id: <200003200748.AAA13449@harmony.village.org> To: Joseph Lee Subject: Re: netgear fa410TX and 4.x problems Cc: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, msmith@FreeBSD.ORG In-reply-to: Your message of "Sun, 19 Mar 2000 20:33:32 PST." References: Date: Mon, 20 Mar 2000 00:48:06 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Joseph Lee writes: : I've read from the archives that a few people (such as Mike Smith) has : had success using the Netgear 410TX pcmcia card in -current (or 4.x). : : I've just made a successful transition from 3.4-release+PAO to 4.x, but : my 410tx card is not working anymore. : : Specifically, it's being detected as some NE1000 8-bit card. : : Is there any special settings I should be aware of to get the card to : work? I've done the device card, device pcic0 additions into the kernel. What's the ethernet address printed on the card? I just made a fix to if_ed.c that might fix your problem. I've not MFC'd it yet, but will shortly. Are you in a position to try it? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 19 23:51:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from server.hmm.za.net (admin.bsdonline.org [196.28.82.142]) by hub.freebsd.org (Postfix) with ESMTP id AB97937B6C5 for ; Sun, 19 Mar 2000 23:51:31 -0800 (PST) (envelope-from david@campsbay.za.net) Received: from DAVID (david [192.168.1.2]) by server.hmm.za.net (8.9.3/8.9.3) with SMTP id JAA00439 for ; Mon, 20 Mar 2000 09:52:49 +0200 (SAST) (envelope-from david@campsbay.za.net) Message-ID: <002e01bf9241$44f91f90$0201a8c0@DAVID> From: "David" To: Subject: Date: Mon, 20 Mar 2000 09:52:41 +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.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsuped from 3.4-release to 4.0-stable now and i followed instructions 100% when i reboot finally in single user mode to do the final step (make installworld) i get this error. Please could you give me information as to amend this.. this happens when i reboot normally! ad0: 4211MB [8912/15/63] Mounting root from ufs:wd0sa ad0: Read command timeout - resetting ata0: resetting devices... device dissapeared ata0-master: timeout waiting to give command=c6 s=d0 e=00 this line keeps being repeated any comments or solutions please mail me and cc the mail to me thanks very much Cheers From David! _________________________ David van Rensburg - david@van.web.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 0: 0: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from nol.co.za (nol.co.za [196.33.45.2]) by hub.freebsd.org (Postfix) with ESMTP id 3D58437B514 for ; Sun, 19 Mar 2000 23:59:58 -0800 (PST) (envelope-from tim@nol.co.za) Received: from sz.nol.co.za ([196.33.45.130] helo=eclipse) by nol.co.za with esmtp (Exim 3.13 #1) id 12Wx6Q-00005j-00 for freebsd-stable@freebsd.org; Mon, 20 Mar 2000 09:59:54 +0200 Message-Id: <4.2.0.58.20000320094249.00a51750@nol.co.za> X-Sender: tim@nol.co.za X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Mon, 20 Mar 2000 10:03:14 +0200 To: freebsd-stable@freebsd.org From: "Timothy S. Bowers" Subject: dummynet problems 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 Some usefull output I get: # ipfw show 65535 9262877 2782094306 allow ip from any to any #ipfw pipe show # #uname -a FreeBSD nol.co.za 3.4-STABLE FreeBSD 3.4-STABLE #2: Sun Feb 27 12:49:43 SAST 2000 root@nol.co.za:/usr/src/sys/compile/NEXUS i386 #dmesg Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.4-STABLE #2: Sun Feb 27 12:49:43 SAST 2000 root@nol.co.za:/usr/src/sys/compile/NEXUS Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 467729508 Hz CPU: Celeron (467.73-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183f9ff real memory = 167772160 (163840K bytes) avail memory = 159358976 (155624K bytes) Preloaded elf kernel "kernel" at 0xc02b6000. Pentium Pro MTRR support enabled Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x02 on pci0.4.0 ide_pci0: rev 0x01 on pci0.4.1 chip3: rev 0x02 on pci0.4.3 xl0: <3Com 3c905B-TX Fast Etherlink XL> rev 0x64 int a irq 10 on pci0.10.0 xl0: Ethernet address: 00:50:da:39:4e:81 xl0: autoneg complete, link status good (half-duplex, 10Mbps) xl1: <3Com 3c905B-TX Fast Etherlink XL> rev 0x64 int a irq 11 on pci0.11.0 xl1: Ethernet address: 00:50:da:39:4d:9d xl1: autoneg complete, link status good (half-duplex, 10Mbps) Probing for devices on PCI bus 1: vga0: rev 0x02 on pci1.0.0 Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model IntelliMouse, device ID 3 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 8250 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 24405MB (49981680 sectors), 49585 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (atapi): , removable, dma, iordis acd0: drive speed 6890KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked wdc1 not found at 0x170 ppc0 at 0x278 irq 7 flags 0x40 on isa ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 plip0: on ppbus 0 vga0 at 0x3c0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry by default BRIDGE 990810, have 8 interfaces -- index 1 type 6 phy 0 addrl 6 addr 00.50.da.39.4e.81 -- index 2 type 6 phy 0 addrl 6 addr 00.50.da.39.4d.9d DUMMYNET initialized (000212) IP Filter: initialized. Default = pass all, Logging = enabled changing root device to wd0s1a --- Timothy >I think I found some sort of bug in freebsd 3.4 stable. >I was playing with ipfw pipes. I added pipes limiting bandwidth to 128Kbps and 64Kbps to/from the server etc.. then after a few days when I took the >firewall rules off of the server but the bandwidth stayed the same.. I only get 128Kbps to the server from my personal pc and all other pc's. >The server is on the same 10/100Mb switch as me and the other pc's. > >Also when I upload to the server.. if I'm lucky I can upload fast again... but then downloading freezes after 4096 bytes of data... > >Any suggestions.. What info do you need? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 0:55:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 3D78137B639; Mon, 20 Mar 2000 00:55:37 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id AAA50671; Mon, 20 Mar 2000 00:55:26 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38D5E77D.8F903DFE@gorean.org> Date: Mon, 20 Mar 2000 00:55:25 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0316 i386) X-Accept-Language: en MIME-Version: 1.0 To: Cameron Grant Cc: Randall Hopper , Amancio Hasty , Conrad Sabatier , stable@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Suggestions for improving newpcm performance? References: <200003191838.KAA40955@rah.star-gate.com> <000701bf91d5$4aebeb60$0304020a@NENYA> <001a01bf91c1$7f62a4b0$0304020a@NENYA> <200003191838.KAA40955@rah.star-gate.com> <20000319220453.A65973@ipass.net> <005d01bf9221$4660ac60$0304020a@NENYA> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [snipping] Cameron Grant wrote: > to my knowledge, midi is the only functionality missing. also, multiple > opens of /dev/dsp are not yet implemented. both will be soon. I think someone else already responded to this point. You can check the archives for more discussion. > i, and others, will want to > see code, not promises. Which, I think, is exactly what the current voxware users are saying. The promises about the additions/improvements to (new)pcm have been going on for a year or more. This is the second round of removing the voxware drivers before the new stuff is ready. I would think that the PTB would have learned from the last round of hue'ing and cry'ing that the transition would have been much easier if the new functionality had been added first. Far be it from me to stand in the way of progress, but it would be nice to _see_ some progress first. Don't get me wrong, I know the new stuff is going to be cool, I know that that people working on it are working hard, and I appreciate their efforts. But it seems that some involved in the project are hell bent on getting rid of voxware, for better or worse. It would be nice if there were more of a spirit of cooperation. (Yes, I know all the arguments for removing the "stale" code, but I don't buy them, not yet. See archives for more.) Doug PS, can we stop naming things "_new_foo"? There are two problems with that. First, in 6 months it won't be new anymore. Second, what do you call the next step in evolution? newnewpcm? :) -- "While the future's there for anyone to change, still you know it seems, it would be easier sometimes to change the past" - Jackson Browne, "Fountain of Sorrow" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 1:49:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from infos1.casaccia.enea.it (INFOS1.casaccia.enea.it [192.107.71.175]) by hub.freebsd.org (Postfix) with ESMTP id 62BE737B5A2 for ; Mon, 20 Mar 2000 01:49:22 -0800 (PST) (envelope-from poggif@casaccia.enea.it) Received: from studi7106 (STUDI7106.casaccia.enea.it [192.107.77.106]) by infos1.casaccia.enea.it (8.9.1/8.9.1) with SMTP id KAA27483 for ; Mon, 20 Mar 2000 10:50:07 +0100 (MET) Message-Id: <3.0.5.32.20000320104909.00943730@infos1.casaccia.enea.it> X-Sender: poggif@infos1.casaccia.enea.it X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 20 Mar 2000 10:49:09 +0100 To: freebsd-stable@FreeBSD.ORG From: Fabrizio Poggi Subject: Sis6326 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I've found a courios problem. I have a graphic adapter model Daytona with a SiS6326 chip, 4mb, perfect working. With the last Xfree86 (3.3.5 version) it gives a rubick-cube problem. During X sessions this adapter don't show any charachter (name of icons, menu, xterm, pop-up messages, and so on be desplayed as a undefined dark blocks), often (when click on desktop) the arrow of mouse become a flat, black square. For having a correct vision must launch startx at 24 bpp of depht (the mouse becomes ever a square): in this case the chars are perfect. I've changed all xf86config setting & frequency of refresh (poor my monitor), every window manager (kde, gnome..), buy a new serial-standard mouse, mounted a RedHat 6.1 (the same, a little more slow). Nothing of done. Anyone more expert has the same problem or found a trick of configuration? Or maybe is a particular hardware bug in the adapter? In console all works good ;) ! thanX in advance; bye bye To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 2: 1:52 2000 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 1ABB837B63A for ; Mon, 20 Mar 2000 02:01:48 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e2KANWk19022; Mon, 20 Mar 2000 02:23:32 -0800 (PST) Date: Mon, 20 Mar 2000 02:23:32 -0800 From: Alfred Perlstein To: Fabrizio Poggi Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Sis6326 Message-ID: <20000320022332.Y14789@fw.wintelcom.net> References: <3.0.5.32.20000320104909.00943730@infos1.casaccia.enea.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3.0.5.32.20000320104909.00943730@infos1.casaccia.enea.it>; from poggif@casaccia.enea.it on Mon, Mar 20, 2000 at 10:49:09AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Fabrizio Poggi [000320 02:13] wrote: > Hi all, > > I've found a courios problem. I have a graphic adapter model Daytona with a > SiS6326 chip, 4mb, perfect working. With the last Xfree86 (3.3.5 version) > it gives a rubick-cube problem. During X sessions this adapter don't show > any charachter (name of icons, menu, xterm, pop-up messages, and so on be > desplayed as a undefined dark blocks), often (when click on desktop) the > arrow of mouse become a flat, black square. For having a correct vision > must launch startx at 24 bpp of depht (the mouse becomes ever a square): in > this case the chars are perfect. > > I've changed all xf86config setting & frequency of refresh (poor my > monitor), every window manager (kde, gnome..), buy a new serial-standard > mouse, mounted a RedHat 6.1 (the same, a little more slow). Nothing of > done. Anyone more expert has the same problem or found a trick of > configuration? Or maybe is a particular hardware bug in the adapter? > In console all works good ;) ! > > thanX in advance; bye bye The Xfree86 system is maintained by the Xfree86 project, you can find information about them at http://www.xfree86.org/ since this card doesn't seem to work on both FreeBSD and Linux it seems to be an Xfree issue and you ought to take it up with them. However, Xfree 4.0 was just released, I would try installing that and see what happens. It's available in the ports tree afaik and as binary downloads from the mirrors listed on the Xfree86 site. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@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 Mar 20 3:58: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from field.videotron.net (field.videotron.net [205.151.222.108]) by hub.freebsd.org (Postfix) with ESMTP id 5475A37B8BB for ; Mon, 20 Mar 2000 03:58:01 -0800 (PST) (envelope-from luc_m@videotron.ca) Received: from videotron.ca ([24.200.211.63]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FRP002ALYKND3@field.videotron.net> for stable@freebsd.org; Mon, 20 Mar 2000 06:57:59 -0500 (EST) Date: Mon, 20 Mar 2000 06:57:35 -0500 From: Luc Morin Subject: [Fwd: CD problems after upgrade to 4.0 (solved)] To: stable@freebsd.org Message-id: <38D6122F.5FAAE102@videotron.ca> MIME-version: 1.0 X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-STABLE i386) Content-type: MULTIPART/MIXED; BOUNDARY="Boundary_(ID_Rc395fTwogTx+yeNLMhQnA)" X-Accept-Language: en Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --Boundary_(ID_Rc395fTwogTx+yeNLMhQnA) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Luc Morin wrote: > Sean O'Connell wrote: > > > > > Luc- > > > > Did you rebuild your acd* devices and all of /dev for that matter? > > What are the major/minor numbers? > > > > crw-r----- 1 root operator 117, 0 Mar 1 10:30 /dev/acd0a > > crw-r----- 1 root operator 117, 2 Mar 1 10:30 /dev/acd0c > > > > cd /dev > > sh MAKEDEV acd0 > > > > S > > ----------------------------------------------------------------------- > > Sean O'Connell Email: sean@stat.Duke.EDU > > Institute of Statistics and Decision Sciences Phone: (919) 684-5419 > > Duke University Fax: (919) 684-8594 > > Well I'll be damned.... > > I was sure I ran mergemaster after the upgrade to 4.0 and thus that MAKEDEV > was up-to-date. It was not. Now I'm not so sure I ran mergemaster.... > > I looked at the major/minor of those node files and sure enough they were not > good. > > I had some glitches during the install process and it's quite possible I > overlooked this importnat step... oh well, thanks for the shove in the right > direction 8-) > > Problem solved. Ain't this list wonderful ? > > Luc Morin > Electrical Engineering Technologist --Boundary_(ID_Rc395fTwogTx+yeNLMhQnA) Content-type: MESSAGE/RFC822 Date: Mon, 20 Mar 2000 06:56:16 -0500 From: Luc Morin Subject: Re: CD problems after upgrade to 4.0 (solved) To: Sean O'Connell Message-id: <38D611E0.D7A84B3@videotron.ca> MIME-version: 1.0 X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-STABLE i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Mozilla-Status2: 00000000 X-Accept-Language: en References: <38D56BA0.79A31C82@videotron.ca> <20000319232605.A8631@stat.Duke.EDU> Sean O'Connell wrote: > > Luc- > > Did you rebuild your acd* devices and all of /dev for that matter? > What are the major/minor numbers? > > crw-r----- 1 root operator 117, 0 Mar 1 10:30 /dev/acd0a > crw-r----- 1 root operator 117, 2 Mar 1 10:30 /dev/acd0c > > cd /dev > sh MAKEDEV acd0 > > S > ----------------------------------------------------------------------- > Sean O'Connell Email: sean@stat.Duke.EDU > Institute of Statistics and Decision Sciences Phone: (919) 684-5419 > Duke University Fax: (919) 684-8594 Well I'll be damned.... I was sure I ran mergemaster after the upgrade to 4.0 and thus that MAKEDEV was up-to-date. It was not. Now I'm not so sure I ran mergemaster.... I looked at the major/minor of those node files and sure enough they were not good. I had some glitches during the install process and it's quite possible I overlooked this importnat step... oh well, thanks for the shove in the right direction 8-) Problem solved. Ain't this list wonderful ? Luc Morin Electrical Engineering Technologist --Boundary_(ID_Rc395fTwogTx+yeNLMhQnA)-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 4:17:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ns2.x-link.za.net (ns2.x-link.za.net [163.195.1.237]) by hub.freebsd.org (Postfix) with ESMTP id 962DE37B923 for ; Mon, 20 Mar 2000 04:17:40 -0800 (PST) (envelope-from swhite@gov.za) Received: from localhost (swhite@localhost) by ns2.x-link.za.net (8.8.8/8.8.7) with SMTP id OAA03613; Mon, 20 Mar 2000 14:16:34 +0200 (SAST) (envelope-from swhite@gov.za) Date: Mon, 20 Mar 2000 14:16:33 +0200 (SAST) From: X-Sender: swhite@ns2.x-link.za.net To: Fabrizio Poggi Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Sis6326 In-Reply-To: <3.0.5.32.20000320104909.00943730@infos1.casaccia.enea.it> 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, 20 Mar 2000, Fabrizio Poggi wrote: > I've found a courios problem. I have a graphic adapter model Daytona with a > SiS6326 chip, 4mb, perfect working. With the last Xfree86 (3.3.5 version) I had no joy at all with 3.3.5 so installed 3.3.6 from source. I'm currently running at 1280x1024x16bpp, no problems. Sorry if this is OT... Regards, - Sean. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 4:45:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 1A5C437B968 for ; Mon, 20 Mar 2000 04:45:29 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12X1YN-00049y-00; Mon, 20 Mar 2000 14:45:03 +0200 From: Sheldon Hearn To: Randall Hopper Cc: stable@FreeBSD.ORG Subject: Re: Missing man pages: ld.so, sigwait() In-reply-to: Your message of "Fri, 17 Mar 2000 19:55:26 EST." <20000317195526.A24340@ipass.net> Date: Mon, 20 Mar 2000 14:45:03 +0200 Message-ID: <15993.953556303@axl.ops.uunet.co.za> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 17 Mar 2000 19:55:26 EST, Randall Hopper wrote: > sigwait is available but there's no man page. Also I don't find one > for ld.so, though it's mentioned in the ldd man page. > > Worth a PR? Well, it's certainly worth some work. I don't know whether a PR without contributions is going to get much done, though. Hmmm, let's see... OpenBSD has a sigwait(3) manual page and both NetBSD and OpenBSD have ld.so pages. Perhaps you could start with those and come up with something to add as follow-up for your own PR's? :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 5:18:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 9D09A37B8D6 for ; Mon, 20 Mar 2000 05:18:28 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12X24Y-0005GW-00; Mon, 20 Mar 2000 15:18:18 +0200 From: Sheldon Hearn To: Randall Hopper Cc: stable@FreeBSD.ORG Subject: Re: Missing man pages: ld.so, sigwait() In-reply-to: Your message of "Mon, 20 Mar 2000 14:45:03 +0200." <15993.953556303@axl.ops.uunet.co.za> Date: Mon, 20 Mar 2000 15:18:18 +0200 Message-ID: <20243.953558298@axl.ops.uunet.co.za> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 20 Mar 2000 14:45:03 +0200, Sheldon Hearn wrote: > Hmmm, let's see... OpenBSD has a sigwait(3) manual page and both NetBSD > and OpenBSD have ld.so pages. Hmmm, my comments about sigwait(3) still apply, but I've had a look and it looks like we have something _very_ similar to {Net,Open}BSD's ld.so(1) in our own rtld(1). The question is now simply whether we create an MLINK for rtld.1 or or fix the Xrefs in other manual pages to point to it. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 5:23:36 2000 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 6A2CF37B8F9 for ; Mon, 20 Mar 2000 05:23:30 -0800 (PST) (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 FAA10938; Mon, 20 Mar 2000 05:23:29 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda10936; Mon Mar 20 05:23:12 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id FAA95493; Mon, 20 Mar 2000 05:23:11 -0800 (PST) Message-Id: <200003201323.FAA95493@passer.osg.gov.bc.ca> Received: from localhost.osg.gov.bc.ca(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost.osg.gov.bc.ca, id smtpdQ95485; Mon Mar 20 05:22:55 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cschuber To: Vova Golubkov Cc: freebsd-stable@freebsd.org Subject: Re: 4.0: EtherExpress16 disappeared? In-reply-to: Your message of "Mon, 20 Mar 2000 10:52:42 +0100." <38D5F4EA.FA6F919@cern.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 20 Mar 2000 05:22:55 -0800 From: Cy Schubert Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38D5F4EA.FA6F919@cern.ch>, Vova Golubkov writes: > This is a multi-part message in MIME format. > --------------C36FB26629C82B7589A35043 > Content-Type: text/plain; charset=koi8-r > Content-Transfer-Encoding: 7bit > > Cy Schubert - ITSD Open Systems Group wrote: > > > > In message <38D45483.110F6A78@cern.ch>, Vova Golubkov writes: > > > Hi > > > > > > I have upgraded to 4.0-RELEASE and found that my Intel EtherExpress16 > > > NIC is not detected anymore. I know that this driver is not perfect > > > (as well as the card itself), but I prefer it to nothing :-) > > > Should it be added to sys/i386/isa/isa_compat.h? > > > > Had the same problem with my 3C509B (ep0). Disabled all unneeded > > drivers (boot -c) and it now works. A comment in the -current archives > > by Warner (IIRC) stated that other drivers may trash the card's > > registers while probing for their supported hardware, causing your card > > to become unresponsive. > > Yes, but in my case the card (ie0) has been just brougt out of the > detection process! I spent several hours changing parameters of the > card, > playing with the settings at the "boot -c prompt", but then found that > the driver is just not enabled, although it is compiled into the kernel. This is a different problem than I had. Can anyone else offer assistance? Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC 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 Mon Mar 20 5:40:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from green.wl.vg (green.wl.vg [204.203.49.94]) by hub.freebsd.org (Postfix) with ESMTP id 6E72937B63A for ; Mon, 20 Mar 2000 05:40:11 -0800 (PST) (envelope-from patrick@whetstonelogic.com) Received: from whetstonelogic.com (patrick [205.252.46.171]) by green.wl.vg (8.9.3/8.9.3) with ESMTP id FAA16980; Mon, 20 Mar 2000 05:39:52 -0800 (PST) (envelope-from patrick@whetstonelogic.com) Message-ID: <38D62A46.5884B7D7@whetstonelogic.com> Date: Mon, 20 Mar 2000 08:40:22 -0500 From: Patrick Gardella Organization: Whetstone Logic, Inc. X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Brandon D. Valentine" Cc: Matt Heckaman , "Brian O'Shea" , FreeBSD-STABLE Subject: Re: SMP oddity References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does this patch work for anyone else? More importantly, does it break anything for anyone? Note: The below patch is for 3.4-RELEASE. If you are using something else, you'll have to patch the file by hand, but it's not difficult :) Patrick "Brandon D. Valentine" wrote: > > Well, the diff didn't work on my 3.4-RELEASE system via patch. However, > I found the 4 lines the diff wanted to remove and did it myself and it > works beautifully. I imagine it is just a change in the file under > RELENG_3 since 3.4-RELEASE came out that altered the line numbers patch > was looking for. Anyway, here are my results followed by a diff from my > 3.4-RELEASE system to prove that the changes are identical to the one > yours suggested: *** identcpu.c.orig Sat Mar 18 17:02:14 2000 --- identcpu.c Sat Mar 18 17:03:53 2000 *************** *** 504,524 **** #endif #if defined(I586_CPU) case CPUCLASS_586: - #ifndef SMP printf("%d.%02d-MHz ", (tsc_freq + 4999) / 1000000, ((tsc_freq + 4999) / 10000) % 100); - #endif printf("586"); break; #endif #if defined(I686_CPU) case CPUCLASS_686: - #ifndef SMP printf("%d.%02d-MHz ", (tsc_freq + 4999) / 1000000, ((tsc_freq + 4999) / 10000) % 100); - #endif printf("686"); break; #endif --- 504,520 ---- Patrick ---------- Patrick Gardella patrick@whetstonelogic.com VP-Technology patrick@freebsd.org Whetstone Logic, Inc. This space intentionally left blank. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 5:41: 5 2000 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 DF43537B971 for ; Mon, 20 Mar 2000 05:41:01 -0800 (PST) (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 FAA10976; Mon, 20 Mar 2000 05:40:29 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda10974; Mon Mar 20 05:40:13 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id FAA95592; Mon, 20 Mar 2000 05:40:12 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdH95580; Mon Mar 20 05:39:32 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id FAA13963; Mon, 20 Mar 2000 05:39:27 -0800 (PST) Message-Id: <200003201339.FAA13963@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdB13959; Mon Mar 20 05:39:19 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: Randall Hopper Cc: stable@FreeBSD.ORG Subject: Re: Missing man pages: ld.so, sigwait() In-reply-to: Your message of "Fri, 17 Mar 2000 19:55:26 EST." <20000317195526.A24340@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 20 Mar 2000 05:39:18 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000317195526.A24340@ipass.net>, Randall Hopper writes: > sigwait is available but there's no man page. Also I don't find one > for ld.so, though it's mentioned in the ldd man page. Agreeed, there is no man page for sigwait, however on my 3.4R systems: cwsys$ man -k ld.so ld.so(1) - run-time link-editor cwsys$ man ld.so RTLD(1) FreeBSD General Commands Manual RTLD(1) NAME ld.so - run-time link-editor DESCRIPTION ld.so is a self-contained, position independent program image providing And on my 4.0R slice: cwsys$ zcat /opt3/usr/share/man/man1/ld.so.1.gz | nroff -man | l RTLD(1) FreeBSD General Commands Manual RTLD(1) NAME ld.so - run-time link-editor DESCRIPTION ld.so is a self-contained, position independent program image providing Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC 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 Mon Mar 20 5:42:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gallions-reach.inpharmatica.co.uk (gallions-reach.inpharmatica.co.uk [193.115.214.5]) by hub.freebsd.org (Postfix) with ESMTP id D870D37B525 for ; Mon, 20 Mar 2000 05:42:31 -0800 (PST) (envelope-from m.seaman@inpharmatica.co.uk) Received: from mailhost.inpharmatica.co.uk (euston.inpharmatica.co.uk [193.115.214.6]) by gallions-reach.inpharmatica.co.uk (8.9.3/8.9.3) with ESMTP id NAA46118; Mon, 20 Mar 2000 13:40:57 GMT (envelope-from m.seaman@inpharmatica.co.uk) Received: from paddington.inpharmatica.co.uk (IDENT:root@paddington.inpharmatica.co.uk [192.168.122.1]) by mailhost.inpharmatica.co.uk (8.9.3/8.9.3) with ESMTP id NAA43929; Mon, 20 Mar 2000 13:40:52 GMT (envelope-from m.seaman@inpharmatica.co.uk) Received: from inpharmatica.co.uk (IDENT:matthew@localhost.inpharmatica.co.uk [127.0.0.1]) by paddington.inpharmatica.co.uk (8.9.3/8.9.3) with ESMTP id NAA15788; Mon, 20 Mar 2000 13:40:52 GMT Message-ID: <38D62A63.21483F49@inpharmatica.co.uk> Date: Mon, 20 Mar 2000 13:40:51 +0000 From: Matthew Seaman X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.4 i586) X-Accept-Language: en-GB, en MIME-Version: 1.0 To: J McKitrick Cc: freebsd-stable@FreeBSD.ORG Subject: Re: serial probs in 4.0 References: <20000320032758.A48883@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 J McKitrick wrote: > > I don't know if this will help anyone, but i did 2 things that *might > have solved the serial problem on my machine. I just deleted the cuaa > devices and remade them. My serial port modem ended up on cuaa4, > which was strange, but at least it worked. Then, when i removed > everything after sio0 from the kernel config, the modem showed up at > cuaa1, where it used to be under 3.4. I don't know if this is what > solved my problem, but it's worth a shot if you are still having > problems. I had the *exact* same thing... it opened under term, and > accepted keystrokes, but didn't answer to AT commands. I saw pretty much the same thing: under 4.0 my PnP modem card ended up as /dev/sio4, whereas under 3.4 it had always appeared as /dev/sio2. The problem seems to be that userconfig (ie. boot -c) no-longer understands the 'pnp ...' command, so you can't override the PnP configuration of the card any more. My solution was to delete the lines: device sio2 at isa? disable port IO_COM3 irq 5 device sio3 at isa? disable port IO_COM4 irq 9 from the kernel config, after which the PnP autoconfiguration did the right thing. Examine your dmesg output: it will make it clear if you've got a dysfunctional /boot/kernel.conf script. Matthew -- Certe, Toto, sentio nos in Kansate non iam adesse. Dr. Matthew Seaman, Inpharmatica Ltd, 60 Charlotte St, London, W1P 2AX Tel: +44 171 631 4644 x229 Fax: +44 171 631 4844 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 6:10:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id DD5C237B77C for ; Mon, 20 Mar 2000 06:10:33 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12X2sl-0005jA-00; Mon, 20 Mar 2000 16:10:11 +0200 From: Sheldon Hearn To: Cy Schubert - ITSD Open Systems Group Cc: Randall Hopper , stable@FreeBSD.ORG Subject: Re: Missing man pages: ld.so, sigwait() In-reply-to: Your message of "Mon, 20 Mar 2000 05:39:18 PST." <200003201339.FAA13963@cwsys.cwsent.com> Date: Mon, 20 Mar 2000 16:10:11 +0200 Message-ID: <22019.953561411@axl.ops.uunet.co.za> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 20 Mar 2000 05:39:18 PST, Cy Schubert - ITSD Open Systems Group wrote: > Agreeed, there is no man page for sigwait, however on my 3.4R systems: > > cwsys$ man -k ld.so > ld.so(1) - run-time link-editor Check the date on /opt3/usr/share/man/man1/ld.so.1.gz, I'm pretty sure it's stale. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 6:11:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bigphred.greycat.com (bigphred.greycat.com [207.173.133.2]) by hub.freebsd.org (Postfix) with ESMTP id 2F0E437B63A for ; Mon, 20 Mar 2000 06:11:44 -0800 (PST) (envelope-from dann@bigphred.greycat.com) Received: (from dann@localhost) by bigphred.greycat.com (8.9.3/8.9.3) id GAA01406 for stable@freebsd.org; Mon, 20 Mar 2000 06:11:36 -0800 (PST) (envelope-from dann) Date: Mon, 20 Mar 2000 06:11:36 -0800 From: Dann Lunsford To: stable@freebsd.org Subject: Re: RELENG_4 and sound on a Toshiba laptop Message-ID: <20000320061136.A1360@greycat.com> References: <20000319114021.A9089@greycat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from kris@FreeBSD.org on Sun, Mar 19, 2000 at 10:44:35PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 19, 2000 at 10:44:35PM -0800, Kris Kennaway wrote: > On Sun, 19 Mar 2000, Dann Lunsford wrote: > > > complete success. Way to go, Core Team! > > Just a note that the people you really should be thanking are the FreeBSD > committers, not the core team who don't have any involvement in the > day-to-day development of FreeBSD and just act as a management oversight > body. But thanks anyway! :) Whoops! Didn't mean to slight anyone :-). I just have a (perhaps unfortunate) tendency to think of the gods and demigods as part of the same pantheon. Would you believe "Way to go, Core/Committers!"? -- Dann Lunsford The only thing necessary for the triumph of evil dann@greycat.com is that men of good will do nothing. -- Cicero To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 6:24:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from atlas.pathcom.com (pathway1.pathcom.com [209.250.128.4]) by hub.freebsd.org (Postfix) with ESMTP id 5CF0937B776 for ; Mon, 20 Mar 2000 06:24:20 -0800 (PST) (envelope-from lwh@pathcom.com) Received: from dial-0711.tor.pathcom.com (dial-0711.tor.pathcom.com [216.249.2.203]) by atlas.pathcom.com (8.9.3/8.9.3) with ESMTP id JAA23693; Mon, 20 Mar 2000 09:20:51 -0500 (EST) Date: Mon, 20 Mar 2000 09:20:46 -0500 (EST) From: Luke Hollins Reply-To: lwh@pathcom.com To: Matthew Seaman Cc: J McKitrick , freebsd-stable@FreeBSD.ORG Subject: Re: serial probs in 4.0 In-Reply-To: <38D62A63.21483F49@inpharmatica.co.uk> Message-ID: Confirm-Reading-To: "Me" Disposition-Notification-To: "luke" 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, 20 Mar 2000, Matthew Seaman wrote: > > I don't know if this will help anyone, but i did 2 things that *might > > have solved the serial problem on my machine. I just deleted the cuaa > > devices and remade them. My serial port modem ended up on cuaa4, > > which was strange, but at least it worked. Then, when i removed > > everything after sio0 from the kernel config, the modem showed up at > > cuaa1, where it used to be under 3.4. I don't know if this is what > > solved my problem, but it's worth a shot if you are still having > > problems. I had the *exact* same thing... it opened under term, and > > accepted keystrokes, but didn't answer to AT commands. > > I saw pretty much the same thing: under 4.0 my PnP modem card ended up as > /dev/sio4, whereas under 3.4 it had always appeared as /dev/sio2. The problem > seems to be that userconfig (ie. boot -c) no-longer understands the 'pnp ...' > command, so you can't override the PnP configuration of the card any more. My > solution was to delete the lines: I've tried everyones ideas they've sent me so far (thanks alot) , but to no avail. I am only using external modems so I have ruled out a couple of things, I tried a modem that I know works, and it had the same problem. I tried serial cards, so I dont think it is my onboard serial ports problem. It looks alot like not a FreeBSD issue right now, I had been using 4.0 for a few days when the ports stopped working, and I booted RELENG_3 and they still didn't work. If someone could send me the output of stty -a on a working serial port used with a modem I would greatly appreciate it (14400 is becoming painful :)....... Thanks Luke To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 6:54:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (Postfix) with ESMTP id 7A5A337B77C; Mon, 20 Mar 2000 06:54:01 -0800 (PST) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id PAA06728; Mon, 20 Mar 2000 15:54:20 +0100 (CET) Message-ID: <20000320155420.B6058@foobar.franken.de> Date: Mon, 20 Mar 2000 15:54:20 +0100 From: Harold Gutch To: Mike Smith Cc: stable@FreeBSD.ORG Subject: Re: booting 3.x from CD? References: <20000105191920.D11588@foobar.franken.de> <200001060829.AAA01025@mass.cdrom.com> <20000106144633.A13911@foobar.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <20000106144633.A13911@foobar.franken.de>; from Harold Gutch on Thu, Jan 06, 2000 at 02:46:33PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 02:46:33PM +0100, Harold Gutch wrote: > On Thu, Jan 06, 2000 at 12:29:18AM -0800, Mike Smith wrote: > > > On a (semi-)related topic - I tried to install FreeBSD > > > 3.3-RELEASE on my "Gericom" notebook last week and _always_ > > > failed when booting from either the CD or from the 3.3 bootdisks > > > I had created. > > > The booting process would halt at either the point where it says > > > > > > Timecounter "i8254" frequency 1193182 Hz > > > > > > or it would pass exactly this point and then halt at the next > > > screen (the one where you select wether you want to config your > > > kernel in visual mode etc.). At one of these points it would > > > simply freeze, no panic, no dump, nothing. > > > > More details (eg. the output when you use 'boot -v' on the install > > floppies) would be helpful. > > Whoops, yes, I forgot to attach it to my last mail. > This is the output when booting from the CD. I doubt that the > verbose output from a bootdisk will look different, but I could > give it a try... > > > > It'd be interesting to know if you have the same problem with the boot > > floppies for a recent 4.0 snapshot. > > It halts at exactly the same point. I tried upgrading my notebook to 4.0-RELEASE last night and it froze at exactly the same point again. Two things to note: a) When booting with boot_ddb set, the kernel drops to DDB, but that's it - I can't do/type anything in DDB b) A GENERIC kernel from 4.0-CURRENT as of January 23rd 1999 (just a few days after 4.0 got split off) boots just fine. I just started a "binary search" trying to nail down the last day it worked (and perhaps even the commit that broke it). bye, Harold -- Someone should do a study to find out how many human life spans have been lost waiting for NT to reboot. Ken Deboy on Dec 24 1999 in comp.unix.bsd.freebsd.misc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 7:29:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id F1CDE37B7FD for ; Mon, 20 Mar 2000 07:29:10 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id C6F5DE89A for ; Mon, 20 Mar 2000 10:29:05 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id KAA30343; Mon, 20 Mar 2000 10:29:05 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14550.17345.705573.306696@onceler.kcilink.com> Date: Mon, 20 Mar 2000 10:29:05 -0500 (EST) To: stable@FreeBSD.ORG Subject: Re: Error: "Maximum file descriptors exceeded"... In-Reply-To: References: <200003181539.PAA21176@pancake.earlsfort.iol.ie> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "BK" == Brad Knowles writes: BK> At 3:39 PM +0000 2000/3/18, Nick Hilliard wrote: >> You've run "cap_mkdb /etc/login.conf", haven't you? I know this is pretty >> basic, and am embarrassed to even suggest it, but I've been inattentive >> enough to be caught by this once or twice... :-( BK> No, I hadn't. I wasn't even aware that this sort of thing was BK> necessary, especially when you don't make any changes at all to BK> /etc/login.conf from the default that gets installed. I hadn't known this either. Reading the login.conf man page doesn't reveal this on a 3.4-STABLE system, and that same system does not have a /etc/login.conf.db file. What are the rules for seaching a DB cap file rather than a flat cap file? -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 PGP & MIME spoken here http://www.kciLink.com/home/khera/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 7:32: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id 3BCDC37B7FE for ; Mon, 20 Mar 2000 07:32:02 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 15A12E881; Mon, 20 Mar 2000 10:32:01 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id KAA30366; Mon, 20 Mar 2000 10:32:01 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14550.17520.977561.161166@onceler.kcilink.com> Date: Mon, 20 Mar 2000 10:32:00 -0500 (EST) To: Randall Hopper Cc: stable@freebsd.org Subject: Re: Netscape pegs CPU on XServer kill In-Reply-To: <20000318110831.A34338@ipass.net> References: <20000318110831.A34338@ipass.net> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "RH" == Randall Hopper writes: RH> I've got Netscape Navigator 4.72 built from ports. RH> In the past, killing the X server (e.g Ctrl-Alt-Bksp) killed Netscape. RH> Now, Netscape lives on and just hammers the CPU. RH> Anybody else seen this problem? What's the best fix/workaround? Make sure you kill Netscape first. This problem plagues me on BSD/OS and FreeBSD. I think Netscape doesn't notice the X connection is severed, which is a bug clearly in that application. I guess a workaround is to use a CPU time limit when running Netscape so that if it does go into a sprial of death, it will ultimately self-destruct when the CPU time limit is reached. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 PGP & MIME spoken here http://www.kciLink.com/home/khera/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 7:33:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id AF47C37B7D2 for ; Mon, 20 Mar 2000 07:33:31 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id D3BF2E897; Mon, 20 Mar 2000 10:33:30 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id KAA30378; Mon, 20 Mar 2000 10:33:30 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14550.17610.683653.914874@onceler.kcilink.com> Date: Mon, 20 Mar 2000 10:33:30 -0500 (EST) To: Jim Weeks Cc: stable@FreeBSD.ORG Subject: Re: Netscape pegs CPU on XServer kill In-Reply-To: References: <20000318110831.A34338@ipass.net> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "JW" == Jim Weeks writes: JW> I have seen this on 3.4 and have also noticed that the process ignores JW> kill from the command line. It does respond to kill -9 however. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 PGP & MIME spoken here http://www.kciLink.com/home/khera/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 7:46: 5 2000 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 9ABEC37B819 for ; Mon, 20 Mar 2000 07:45:59 -0800 (PST) (envelope-from jcm@dogma.freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 1.92 #3) for freebsd-stable@freebsd.org id 12X4NP-0005PW-00; Mon, 20 Mar 2000 15:45:55 +0000 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id PAA54489 for freebsd-stable@freebsd.org; Mon, 20 Mar 2000 15:45:55 GMT (envelope-from jcm) Date: Mon, 20 Mar 2000 15:45:54 +0000 From: J McKitrick To: freebsd-stable@freebsd.org Subject: how to make world under 4.0 stable Message-ID: <20000320154554.D48883@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 The instructions for upgrading to 4.0-R were more complex than the usual makeworld. When i cvsupp from now on under 4.0, do i need to repeat all those steps, or just make buildworld and make install world and compile kernel like i usually do? jm -- -------------------------------------------- Jonathon McKitrick -- jcm@freebsd-uk.eu.org "Doors to the pleasures of heaven or hell, and i didn't care which." -------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 7:55:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id AD1A737B8E9 for ; Mon, 20 Mar 2000 07:55:04 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id BDB08E881; Mon, 20 Mar 2000 10:55:03 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id KAA82007; Mon, 20 Mar 2000 10:55:03 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14550.18902.797775.916259@onceler.kcilink.com> Date: Mon, 20 Mar 2000 10:55:02 -0500 (EST) To: David Kelly Cc: "Sean O'Connell" , stable@FreeBSD.ORG Subject: Re: Netscape pegs CPU on XServer kill In-Reply-To: <200003190148.TAA45044@nospam.hiwaay.net> References: <20000318145829.D8194@stat.Duke.EDU> <200003190148.TAA45044@nospam.hiwaay.net> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "DK" == David Kelly writes: DK> Speaking of which, am I the only one seeing: DK> pid 4106 (communicator-4.7), uid 928: exited on signal 10 (core dumped) It does not happen to me, except when doing Java. When Java is on, it dumps any time it feels like, even when viewing non-java enabled pages. With Java off, it is at least somewhat stable and rarely crashes. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 PGP & MIME spoken here http://www.kciLink.com/home/khera/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 8:40:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 2B4B137B8A5 for ; Mon, 20 Mar 2000 08:40:33 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id D13B1123D1; Mon, 20 Mar 2000 17:40:16 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <38D494A5.FE9796CD@nasby.net> References: <38D48D3D.1DBA8F5D@nasby.net> <38D494A5.FE9796CD@nasby.net> Date: Mon, 20 Mar 2000 16:24:18 +0100 To: "Jim C. Nasby" , freebsd-stable@FreeBSD.ORG From: Brad Knowles Subject: Re: 3.4-4.0 and vinum Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:49 AM -0600 2000/3/19, Jim C. Nasby wrote: > Also, sorry for cross-posting my previous message to -questions as well > as -stable, but I wanted to warn anyone who might be running vinum about > this... would be a major pain if this happened on a production box. Of course, you shouldn't be trying to use 4.0 on a production box. ;-) It's at the "Hey guys, take a look at this thing that is hot out of alpha test" stage right now, and there's going to be a lot of teething problems before things settle down. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 8:43:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from vivaldi.pn.npi.msu.ru (gw.pn.npi.msu.ru [193.232.127.202]) by hub.freebsd.org (Postfix) with ESMTP id 9F1AE37B5E0 for ; Mon, 20 Mar 2000 08:43:13 -0800 (PST) (envelope-from svysh@pn.sinp.msu.ru) Received: from scarlatti (scarlatti [195.208.223.16]) by vivaldi.pn.npi.msu.ru (8.10.0/8.10.0) with SMTP id e2KGglW79446 for ; Mon, 20 Mar 2000 19:42:57 +0300 (MSK) Message-Id: <3.0.5.32.20000320194415.007c18a0@vivaldi> X-Sender: svysh@vivaldi X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 20 Mar 2000 19:44:15 +0300 To: freebsd-stable@FreeBSD.ORG From: Sergei Vyshenski Subject: perl not built in 4.0 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In 4.0-stable cvsupped today, "make buildworld" runs ok only with "NOPERL=true" in /etc/make.conf. If I want perl ("#NOPERL=true"), then "make buildworld" dies as below. Thank you ahead of time for any comment. Sergei ***************** cc -O -pipe -I/usr/obj/usr/src/gnu/usr.bin/perl/libperl -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/perl.c -o perl.o /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/perl.c: In function `perl_parse': /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/perl.c:690: warning: passing arg 1 of `time' from incompatible pointer type cc -O -pipe -I/usr/obj/usr/src/gnu/usr.bin/perl/libperl -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/gv.c -o gv.o cc -O -pipe -I/usr/obj/usr/src/gnu/usr.bin/perl/libperl -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/toke.c -o toke.o cc -O -pipe -I/usr/obj/usr/src/gnu/usr.bin/perl/libperl -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/perly.c -o perly.o cc -O -pipe -I/usr/obj/usr/src/gnu/usr.bin/perl/libperl -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/op.c -o op.o cc -O -pipe -I/usr/obj/usr/src/gnu/usr.bin/perl/libperl -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/regcomp.c -o regcomp.o cc -O -pipe -I/usr/obj/usr/src/gnu/usr.bin/perl/libperl -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/dump.c -o dump.o cc -O -pipe -I/usr/obj/usr/src/gnu/usr.bin/perl/libperl -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/util.c -o util.o /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/util.c: In function `vsprintf': /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/util.c:1634: structure has no member named `_ptr' /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/util.c:1635: structure has no member named `_cnt' /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/util.c:1639: structure has no member named `_flag' /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/util.c:1639: `_IOWRT' undeclared (first use in this function) /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/util.c:1639: (Each undeclared identifier is reported only once /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/util.c:1639: for each function it appears in.) *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl/libperl. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 8:54:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hurricane.columbus.rr.com (m5.columbus.rr.com [204.210.252.249]) by hub.freebsd.org (Postfix) with ESMTP id D2B8337B829; Mon, 20 Mar 2000 08:54:30 -0800 (PST) (envelope-from caa@columbus.rr.com) Received: from columbus.rr.com ([204.210.243.142]) by hurricane.columbus.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-53939U80000L80000S0V35) with ESMTP id com; Mon, 20 Mar 2000 11:54:35 -0500 Received: (from caa@localhost) by columbus.rr.com (8.9.3/8.9.3) id LAA82706; Mon, 20 Mar 2000 11:54:29 -0500 (EST) (envelope-from caa) Date: Mon, 20 Mar 2000 11:54:23 -0500 From: "Charles Anderson" To: Cameron Grant Cc: Randall Hopper , Amancio Hasty , Conrad Sabatier , stable@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Suggestions for improving newpcm performance? Message-ID: <20000320115423.A7946@midgard.dhs.org> References: <200003191838.KAA40955@rah.star-gate.com> <000701bf91d5$4aebeb60$0304020a@NENYA> <001a01bf91c1$7f62a4b0$0304020a@NENYA> <200003191838.KAA40955@rah.star-gate.com> <20000319220453.A65973@ipass.net> <005d01bf9221$4660ac60$0304020a@NENYA> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <005d01bf9221$4660ac60$0304020a@NENYA>; from gandalf@vilnya.demon.co.uk on Mon, Mar 20, 2000 at 04:03:39AM -0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 20, 2000 at 04:03:39AM -0000, Cameron Grant wrote: > > Cameron Grant: > > > > - Have we identified exactly what functionality is missing in the new > > sound driver but supported by Voxware? > > to my knowledge, midi is the only functionality missing. also, multiple > opens of /dev/dsp are not yet implemented. both will be soon. Last time I tried memmapped output, it was not working. I thought I had read a comment a while back that it was being worked on...(Or am I imagining things) (I guess I really couldn't call it missing, though) -Charlie -- Charles Anderson caa@columbus.rr.com No quote, no nothin' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 8:57:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from www.menzor.dk (menzor.org [195.249.147.160]) by hub.freebsd.org (Postfix) with ESMTP id A9C4537B8D4 for ; Mon, 20 Mar 2000 08:57:33 -0800 (PST) (envelope-from ml@seeberg.dk) Received: from sos (userhost.cma.dk [130.228.127.200]) by www.menzor.dk (8.8.8/8.8.8) with SMTP id SAA10291 for ; Mon, 20 Mar 2000 18:04:26 +0100 (CET) (envelope-from ml@seeberg.dk) Message-ID: <030401bf928d$e6e6c270$deff58c1@sos> Reply-To: "Morten Seeberg" From: "Morten Seeberg" To: Subject: psm mouse = psmintr errors on 4.0R Date: Mon, 20 Mar 2000 18:01:13 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, my 4.0-RELEASE finds the PS/2 mouse just fine, but when I try to configure the mouse daemon in sysinstall, i get the error below on my console and in my logs (se the end of dmesg). All the info I could find searching the archives and the website relate to older versions of FreeBSD. I running 4.0R on an IBM PC300PL (P200-MMX) with an IBM Intellimouse (the one with the little clitoris :) ). Any ideas? DMESG: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-RELEASE #1: Sun Mar 19 22:09:39 CET 2000 root@sos-wks.cma.dk:/usr/src/sys/compile/SOS-WKS Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P55C (199.43-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Features=0x8001bf real memory = 100663296 (98304K bytes) avail memory = 93745152 (91548K bytes) Preloaded elf kernel "kernel" at 0xc039f000. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: on motherboard pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port 0xfff0-0xffff at device 1.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 1.2 irq 11 pci0: at 5.0 irq 9 fxp0: port 0x5000-0x501f mem 0x6000000 0-0x600fffff,0x60100000-0x60100fff irq 10 at device 6.0 on pci0 fxp0: Ethernet address 00:60:94:8f:5e:8f fxp0: supplying EUI64: 00:60:94:ff:fe:8f:5e:8f 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-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: cannot reserve I/O port range pcm0: at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 unknown0: on isa0 unknown1: at port 0x120-0x127 on isa0 ad0: 4028MB [8184/16/63] at ata0-master using WDMA2 acd0: CDROM at ata1-master using PIO3 Mounting root from ufs:/dev/ad0s1a fxp0: starting DAD for fe80:0001::0260:94ff:fe8f:5e8f fxp0: DAD complete for fe80:0001::0260:94ff:fe8f:5e8f - no duplicates found psmintr: out of sync (0008 != 0000). psmintr: out of sync (0008 != 0000). psmintr: out of sync (00c8 != 0000). psmintr: out of sync (00c8 != 0000). psmintr: out of sync (0008 != 0000). psmintr: out of sync (00c8 != 0000). psmintr: out of sync (00c8 != 0000). psmintr: out of sync (0008 != 0000). psmintr: out of sync (0008 != 0000). psmintr: out of sync (00c8 != 0000). psmintr: out of sync (00c8 != 0000). psmintr: out of sync (0008 != 0000). psmintr: out of sync (00c8 != 0000). psmintr: out of sync (00c8 != 0000). psmintr: out of sync (0008 != 0000). psmintr: out of sync (00c8 != 0000). psmintr: out of sync (00c8 != 0000). psmintr: out of sync (0008 != 0000). psmintr: out of sync (00c8 != 0000). psmintr: out of sync (00c8 != 0000). ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /\/\orten $eeberg, Systems Consultant @ Merkantildata - Enterprise Solutions #echo 'System Administrators suck :)' > /dev/console To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 9:16: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uunet.ca (mail2.uunet.ca [142.77.1.15]) by hub.freebsd.org (Postfix) with ESMTP id 7832B37B8E9 for ; Mon, 20 Mar 2000 09:15:57 -0800 (PST) (envelope-from matt@ARPA.MAIL.NET) Received: from epsilon.lucida.qc.ca ([216.95.146.6]) by mail2.uunet.ca with ESMTP id <601259-2244>; Mon, 20 Mar 2000 12:04:44 -0500 Date: Mon, 20 Mar 2000 12:09:17 -0500 From: Matt Heckaman X-Sender: matt@epsilon.lucida.qc.ca To: FreeBSD-STABLE Subject: Some observations on 4.0-release and 4.0-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 First of all, I'd like to say that I'm finding FreeBSD 4.0 quite nice indeed, some very nice advancements over 3.x. Here are some things I've noticed so far though; * make world bombs if MAKE_KERBEROS4=NO, but I suppose I should be making that nonetheless, yes? =) * ad driver giving me some problems, I think. I had originally two disks under 3.4 which ere wd0 and wd1, (wd0s1,wd1s1) The first disk was handle perfectly under ad0, the second however blows up hard, and I'm not sure why. Here's the dmesg relative and the error; ad0: 8063MB [16383/16/63] at ata0-master using UDMA33 ad1: 1549MB [3148/16/63] at ata0-slave using WDMA2 ad1: HARD READ ERROR blk# 0ata0-slave: WARNING: WAIT_READY active=ATA_ACTIVE_ATA ad1: HARD READ ERROR blk# 0 status=59 error=04 ad1: DMA problem fallback to PIO mode ad1: reading primary partition table: error reading fsbn 0 (that happens on fdisk, fsck, mount, sysinstall, just about anything that hits that drive. Perhaps it is because it is older?) * xmms screwed up the entire audio until I removed my ~/.xmms and let it create a new one on it's own, no biggie and probably not freebsd related at all. * asmon doesn't work on 4.0 =/ Beyond that though, it's quite nice. I re-wrote my kernel configuration mostly for this event as recommended due to the changes, I found that the GENERIC kernel file is much easier to follow and make good sense out of now than the 3.x one was. LINT is also very well documented and quickly set aside and questions I came across while making the kernel. This is not meant to be a detailed bug report, just a synopsis of my upgrade (read; format and start over) expierence. If anyone has any idea about the hard disk problem above, please do contact me, I'll provide with any information required, thanks =) Keep up the good work, Matt [PS: If this was not the right list, my apologies, the issue of which list to post to is getting quite confusing.] -- Matt Heckaman [matt@arpa.mail.net|matt@relic.net] [Please do not send me] !Powered by FreeBSD/x86! [http://www.freebsd.org] [any SPAM (UCE) e-mail] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 9:35: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.surf1.de (mail.Surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id EC5D437B81D for ; Mon, 20 Mar 2000 09:34:51 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.com (postfix@pC19F5488.dip0.t-ipconnect.de [193.159.84.136]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id RAA23596; Mon, 20 Mar 2000 17:21:25 +0100 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 1356DAC2F; Mon, 20 Mar 2000 18:22:08 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id SAA09093; Mon, 20 Mar 2000 18:20:54 +0100 (CET) (envelope-from alex) Date: Mon, 20 Mar 2000 18:20:54 +0100 From: Alexander Langer To: J McKitrick Cc: freebsd-stable@FreeBSD.ORG Subject: Re: how to make world under 4.0 stable Message-ID: <20000320182054.I2721@cichlids.cichlids.com> Mail-Followup-To: J McKitrick , freebsd-stable@FreeBSD.ORG References: <20000320154554.D48883@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000320154554.D48883@dogma.freebsd-uk.eu.org>; from jcm@freebsd-uk.eu.org on Mon, Mar 20, 2000 at 03:45:54PM +0000 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake J McKitrick (jcm@freebsd-uk.eu.org): > usual makeworld. When i cvsupp from now on under 4.0, do i need to > repeat all those steps, or just make buildworld and make install world > and compile kernel like i usually do? Nope, please read /usr/src/UPDATING (at the end of the file) Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 9:43: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from scrooge.parallelconsulting.com (www.parallelconsulting.com [195.242.42.108]) by hub.freebsd.org (Postfix) with ESMTP id 2FFCA37B893 for ; Mon, 20 Mar 2000 09:42:52 -0800 (PST) (envelope-from jonas.bulow@parallelconsulting.com) Received: from parallelconsulting.com ([193.150.232.120]) by scrooge.parallelconsulting.com (Netscape Messaging Server 3.6) with ESMTP id AAA1933; Mon, 20 Mar 2000 18:43:10 +0100 Message-ID: <38D662E3.48216032@parallelconsulting.com> Date: Mon, 20 Mar 2000 18:41:56 +0100 From: Jonas =?iso-8859-1?Q?B=FClow?= Organization: Parallel Consulting Group X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Sergei Vyshenski Cc: freebsd-stable@FreeBSD.ORG Subject: Re: perl not built in 4.0 References: <3.0.5.32.20000320194415.007c18a0@vivaldi> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, looks like a major upgrade to me! :-) Sergei Vyshenski wrote: > > In 4.0-stable cvsupped today, "make buildworld" > runs ok only with "NOPERL=true" in /etc/make.conf. If I want > perl ("#NOPERL=true"), then "make buildworld" dies as below. > > Thank you ahead of time for any comment. > Sergei > > ***************** > cc -O -pipe -I/usr/obj/usr/src/gnu/usr.bin/perl/libperl > -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 > -I/usr/obj/usr/src/i386/usr/include -c > /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/perl.c -o perl.o > /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/perl.c: In > function `perl_parse': > /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/perl.c:690: > warning: passing arg 1 of `time' from incompatible pointer type > cc -O -pipe -I/usr/obj/usr/src/gnu/usr.bin/perl/libperl > -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 > -I/usr/obj/usr/src/i386/usr/include -c > /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/gv.c -o gv.o > cc -O -pipe -I/usr/obj/usr/src/gnu/usr.bin/perl/libperl > -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 > -I/usr/obj/usr/src/i386/usr/include -c > /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/toke.c -o toke.o > cc -O -pipe -I/usr/obj/usr/src/gnu/usr.bin/perl/libperl > -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 > -I/usr/obj/usr/src/i386/usr/include -c > /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/perly.c -o perly.o > cc -O -pipe -I/usr/obj/usr/src/gnu/usr.bin/perl/libperl > -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 > -I/usr/obj/usr/src/i386/usr/include -c > /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/op.c -o op.o > cc -O -pipe -I/usr/obj/usr/src/gnu/usr.bin/perl/libperl > -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 > -I/usr/obj/usr/src/i386/usr/include -c > /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/regcomp.c -o > regcomp.o > cc -O -pipe -I/usr/obj/usr/src/gnu/usr.bin/perl/libperl > -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 > -I/usr/obj/usr/src/i386/usr/include -c > /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/dump.c -o dump.o > cc -O -pipe -I/usr/obj/usr/src/gnu/usr.bin/perl/libperl > -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 > -I/usr/obj/usr/src/i386/usr/include -c > /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/util.c -o util.o > /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/util.c: In > function `vsprintf': > /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/util.c:1634: > structure has no member named `_ptr' > /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/util.c:1635: > structure has no member named `_cnt' > /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/util.c:1639: > structure has no member named `_flag' > /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/util.c:1639: > `_IOWRT' undeclared (first use in this function) > /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/util.c:1639: > (Each undeclared identifier is reported only once > /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/util.c:1639: > for each function it appears in.) > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/perl/libperl. > *** Error code 1 > > 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 Mar 20 9:53:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from csmd2.cs.uni-magdeburg.de (csmd2.CS.Uni-Magdeburg.De [141.44.22.2]) by hub.freebsd.org (Postfix) with ESMTP id 6041237B8B8 for ; Mon, 20 Mar 2000 09:53:44 -0800 (PST) (envelope-from jesse@mail.CS.Uni-Magdeburg.De) Received: from knecht.cs.uni-magdeburg.de (jesse@knecht [141.44.21.3]) by csmd2.cs.uni-magdeburg.de (8.9.3/8.9.3) with ESMTP id SAA12321 for ; Mon, 20 Mar 2000 18:53:42 +0100 (MET) Received: (from jesse@localhost) by knecht.cs.uni-magdeburg.de (8.8.8+Sun/8.8.8) id SAA29086; Mon, 20 Mar 2000 18:52:40 +0100 (MET) X-Authentication-Warning: knecht.cs.uni-magdeburg.de: jesse set sender to jesse@cs.uni-magdeburg.de using -f To: freebsd-stable@FreeBSD.ORG Subject: Re: how to make world under 4.0 stable References: <20000320154554.D48883@dogma.freebsd-uk.eu.org> <20000320182054.I2721@cichlids.cichlids.com> From: Roland Jesse In-Reply-To: Alexander Langer's message of "Mon, 20 Mar 2000 18:20:54 +0100" Date: 20 Mar 2000 18:52:40 +0100 Message-ID: <0vsnxlh6l3.fsf@cs.uni-magdeburg.de> Lines: 13 User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Langer writes: > > usual makeworld. When i cvsupp from now on under 4.0, do i need to > > repeat all those steps, or just make buildworld and make install world > > and compile kernel like i usually do? > > Nope, please read /usr/src/UPDATING (at the end of the file) He is not asking for the steps needed to update a 3.x system to 4.0 but for staying -stable on a box already running 4.0. The usual buildworld / installworld and a new kernel should do that job. Roland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 10:44:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 417B337B961 for ; Mon, 20 Mar 2000 10:44:16 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA27216; Mon, 20 Mar 2000 10:44:31 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Matt Heckaman Cc: FreeBSD-STABLE Subject: Re: Some observations on 4.0-release and 4.0-stable In-reply-to: Your message of "Mon, 20 Mar 2000 12:09:17 EST." Date: Mon, 20 Mar 2000 10:44:31 -0800 Message-ID: <27213.953577871@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > * ad driver giving me some problems, I think. I had originally two disks > under 3.4 which ere wd0 and wd1, (wd0s1,wd1s1) The first disk was > handle perfectly under ad0, the second however blows up hard, and I'm > not sure why. Here's the dmesg relative and the error; This is a known bug and something I'm actually re-rolling the 4.0 RELEASE over now. Soren just fixed it, and I consider this bug bad enough to merit a re-roll. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 10:52:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uunet.ca (mail2.uunet.ca [142.77.1.15]) by hub.freebsd.org (Postfix) with ESMTP id E20A537BC01 for ; Mon, 20 Mar 2000 10:52:28 -0800 (PST) (envelope-from matt@ARPA.MAIL.NET) Received: from epsilon.lucida.qc.ca ([216.95.146.6]) by mail2.uunet.ca with ESMTP id <599410-16752>; Mon, 20 Mar 2000 13:44:03 -0500 Date: Mon, 20 Mar 2000 13:48:36 -0500 From: Matt Heckaman X-Sender: matt@epsilon.lucida.qc.ca To: "Jordan K. Hubbard" Cc: FreeBSD-STABLE Subject: Re: Some observations on 4.0-release and 4.0-stable In-Reply-To: <27213.953577871@zippy.cdrom.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 Thanks for letting me know, I must also note that you guys have done a wonderful job at making the process of a make world much easier in that it does not blow as much local configuration as it used to, the options to not override crypt links was a nice touch, as was mailer.conf, finally I don't have to think any longer at 4 am why qmail is not working because I forgot to link 'sendmail' =) Matt -- Matt Heckaman [matt@arpa.mail.net|matt@relic.net] [Please do not send me] !Powered by FreeBSD/x86! [http://www.freebsd.org] [any SPAM (UCE) e-mail] On Mon, 20 Mar 2000, Jordan K. Hubbard wrote: : Date: Mon, 20 Mar 2000 13:44:31 -0500 : From: Jordan K. Hubbard : To: Matt Heckaman : Cc: FreeBSD-STABLE : Subject: Re: Some observations on 4.0-release and 4.0-stable : : > * ad driver giving me some problems, I think. I had originally two disks : > under 3.4 which ere wd0 and wd1, (wd0s1,wd1s1) The first disk was : > handle perfectly under ad0, the second however blows up hard, and I'm : > not sure why. Here's the dmesg relative and the error; : : This is a known bug and something I'm actually re-rolling the 4.0 : RELEASE over now. Soren just fixed it, and I consider this bug bad : enough to merit a re-roll. : : - Jordan : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 11:46:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.on.home.com (ha1.rdc1.on.wave.home.com [24.2.9.66]) by hub.freebsd.org (Postfix) with ESMTP id B73B537BDEC for ; Mon, 20 Mar 2000 11:46:24 -0800 (PST) (envelope-from genew@mail.rdc1.on.wave.home.com) Received: from CR121722-a ([24.114.8.161]) by mail.rdc1.on.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <20000320194621.UFT1324.mail.rdc1.on.home.com@CR121722-a> for ; Mon, 20 Mar 2000 11:46:21 -0800 From: genew@home.com To: FreeBSD-STABLE Date: Mon, 20 Mar 2000 14:51:11 -0500 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: 3.4->4.0 ld-elf.so.1 error? X-mailer: Pegasus Mail for Win32 (v3.12b) Message-Id: <20000320194621.UFT1324.mail.rdc1.on.home.com@CR121722-a> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am upgrading from 3.4-s to 4.0 and have been following the instructions in the UPGRADING doc. I am receiving an error that I have not seen mentioned in this list. I am at the step of 'config YOUR-KERNAL-HERE' but when I run the config I get an error saying... "/usr/libexec/ld-elf.so.1: Shared object 'libc.so.4' not found" and it stops. while doing make buildworld I noticed a few other references to the same error but the build kept going so I didn't pay not attention to them. I know I have am missing something somewhere but I have no idea where. and suggestions ( or answers ) would be appreciated Gene Wright To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 11:48: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from science-guy.npt.nuwc.navy.mil (SCIENCE-GUY.NPT.NUWC.NAVY.MIL [129.190.139.47]) by hub.freebsd.org (Postfix) with ESMTP id 196B437B9A9 for ; Mon, 20 Mar 2000 11:47:56 -0800 (PST) (envelope-from tod@science-guy.npt.nuwc.navy.mil) Received: from science-guy.npt.nuwc.navy.mil (localhost [127.0.0.1]) by science-guy.npt.nuwc.navy.mil (8.9.3/8.9.3) with ESMTP id OAA00583; Mon, 20 Mar 2000 14:48:38 -0500 (EST) (envelope-from tod@science-guy.npt.nuwc.navy.mil) Message-ID: <38D68096.6F2F8575@science-guy.npt.nuwc.navy.mil> Date: Mon, 20 Mar 2000 14:48:38 -0500 From: Tod Luginbuhl Reply-To: t.e.luginbuhl@ieee.org Organization: Code 2121, Naval Undersea Warfare Center X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Patrick Gardella , FreeBSD-STABLE Subject: Re: SMP oddity References: <38D62A46.5884B7D7@whetstonelogic.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Patrick Gardella wrote: > > Does this patch work for anyone else? More importantly, does it break > anything for anyone? > > Note: The below patch is for 3.4-RELEASE. If you are using something > else, you'll have to patch the file by hand, but it's not difficult :) > I am running 3.4-RELEASE on a dual Pentium-III 450mHz ASUS P2BDS system. I install the patch this afternoon by hand, rebuilt and install the new kernel. The information cpu clock speed information comes up correctly now when booting the new kernel. I haven't done extensive system testing yet, but the kernel seems to be stable. -- Tod Luginbuhl email: t.e.luginbuhl@ieee.org Code 2121 Naval Undersea Warfare Center 1176 Howell Street Telephone: (401) 832-8241 Newport, Rhode Island FAX: (401) 832-7453 02841-1708 USA "Don't argue with drunks and fanatics!" -- Sun Wolf (Barbara Hambly) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 12: 8:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from limerick.tchden.org (limerick.tchden.org [207.174.34.128]) by hub.freebsd.org (Postfix) with ESMTP id 2B9AC37C067 for ; Mon, 20 Mar 2000 12:08:12 -0800 (PST) (envelope-from groman.jeff@tchden.org) Received: from tchden.org (localhost [127.0.0.1]) by limerick.tchden.org (8.9.3/8.9.3) with ESMTP id NAA01907 for ; Mon, 20 Mar 2000 13:08:10 GMT (envelope-from groman.jeff@tchden.org) Message-ID: <38D622BA.DF7AB73B@tchden.org> Date: Mon, 20 Mar 2000 13:08:10 +0000 From: Jeff Groman X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Subject: (no subject) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 12:18:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lex.balt.net (lex.balt.net [195.14.162.1]) by hub.freebsd.org (Postfix) with ESMTP id EBCB337C565 for ; Mon, 20 Mar 2000 12:18:30 -0800 (PST) (envelope-from dt@mail.balt.net) Received: from mambo ([195.14.166.42]) by lex.balt.net (8.9.3/8.9.0) with SMTP id WAA18470 for ; Mon, 20 Mar 2000 22:16:37 -0200 X-Authentication-Warning: lex.balt.net: Host [195.14.166.42] claimed to be mambo Message-ID: <011201bf92b1$b9fb8b00$7a0d12ac@mambo.da.ru> From: "DT" To: Subject: 4.0 stable. 2 observation/qestions Date: Mon, 20 Mar 2000 22:17:40 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_010F_01BF92BA.1B3B32A0" 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 This is a multi-part message in MIME format. ------=_NextPart_000_010F_01BF92BA.1B3B32A0 Content-Type: text/plain; charset="iso-8859-4" Content-Transfer-Encoding: quoted-printable Hi there, Recently I sucesfuly upgraded from my 3.4-STABLE to 4.0-STABLE and = noticed two strange things. 1. when I compile kernel, say w/o my network card, and then compiling it = with it I need to do make clean, but config process don't say to do = this. I'm not remeber such things with my 3.4 2. There are two network cards in my system. Bouth are PCI realteck = baset NE2000 clones. detected as ed0 and ad1. The qestion is why i shold = include in kernel ISA device ed0 to forse my PCI card to work ? Dalius Tarvydas P.S. sorry for my Eanglish. there were hard day.. and I'm not shure = anyone understand my Eanglish. ------=_NextPart_000_010F_01BF92BA.1B3B32A0 Content-Type: text/html; charset="iso-8859-4" Content-Transfer-Encoding: quoted-printable
Hi there,
 
Recently I sucesfuly upgraded from my = 3.4-STABLE to=20 4.0-STABLE and noticed two strange things.
 
1. when I compile kernel, say w/o my = network card,=20 and then compiling it with it I need to do make clean, but config = process don't=20 say to do this. I'm not remeber such things with my 3.4
 
2. There are two network cards in my = system. Bouth=20 are PCI realteck baset NE2000 clones. detected as ed0 and ad1. The = qestion is=20 why i shold include in kernel ISA device ed0 to forse my PCI card to = work=20 ?
 
Dalius Tarvydas
 
P.S. sorry for my Eanglish. there were = hard day..=20 and I'm not shure anyone understand my = Eanglish.
------=_NextPart_000_010F_01BF92BA.1B3B32A0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 12:45:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 10CF637C7C4; Mon, 20 Mar 2000 12:21:33 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id MAA90253; Mon, 20 Mar 2000 12:21:33 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 20 Mar 2000 12:21:32 -0800 (PST) From: Kris Kennaway To: Matt Heckaman Cc: FreeBSD-STABLE Subject: Re: Some observations on 4.0-release and 4.0-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 On Mon, 20 Mar 2000, Matt Heckaman wrote: > First of all, I'd like to say that I'm finding FreeBSD 4.0 quite nice > indeed, some very nice advancements over 3.x. Here are some things I've > noticed so far though; > > * make world bombs if MAKE_KERBEROS4=NO, but I suppose I should be making > that nonetheless, yes? =) The contents of MAKE_KERBEROS[45] don't matter, it only looks whether or not the variable is set. Similarly, doing NOCRYPT=NO won't cause the build to compile with crypto support (two wrongs make a right), it will compile withOUT crypto. I think sheldonh was looking at documenting this better in make.conf. However, world builds with MAKE_KERBEROS4 set _should_ work, if you have up-to-date sources. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 12:47: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 4F1CF37C8EE for ; Mon, 20 Mar 2000 12:28:27 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id MAA14118; Mon, 20 Mar 2000 12:28:01 -0800 (PST) Date: Mon, 20 Mar 2000 12:28:01 -0800 From: Brooks Davis To: DT Cc: stable@FreeBSD.ORG Subject: Re: 4.0 stable. 2 observation/qestions Message-ID: <20000320122801.A9060@orion.ac.hmc.edu> References: <011201bf92b1$b9fb8b00$7a0d12ac@mambo.da.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <011201bf92b1$b9fb8b00$7a0d12ac@mambo.da.ru>; from dt@mail.balt.net on Mon, Mar 20, 2000 at 10:17:40PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [HTML mail is evil, don't use it. This probably belonged on -questions not -stable.] On Mon, Mar 20, 2000 at 10:17:40PM +0100, DT wrote: > Recently I sucesfuly upgraded from my 3.4-STABLE to 4.0-STABLE and > noticed two strange things. > > 1. when I compile kernel, say w/o my network card, and then compiling > it with it I need to do make clean, but config process don't say to do > this. I'm not remeber such things with my 3.4 This should not be the case. Are you running "make depend" before make every time? > 2. There are two network cards in my system. Bouth are PCI realteck > baset NE2000 clones. detected as ed0 and ad1. The qestion is why i > shold include in kernel ISA device ed0 to forse my PCI card to work ? I think you should be able to get away with: device ed but you'll need to try it to be sure as I haven't tested it. It certainly should work. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 12:47:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from charon.ipass.net (charon.ipass.net [198.79.53.8]) by hub.freebsd.org (Postfix) with ESMTP id A467837C6EF; Mon, 20 Mar 2000 12:32:54 -0800 (PST) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-2-55.dialup.rdu.ipass.net [209.170.133.55]) by charon.ipass.net (8.9.3/8.9.3) with ESMTP id PAA00466; Mon, 20 Mar 2000 15:32:20 -0500 (EST) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id PAA01872; Mon, 20 Mar 2000 15:34:32 -0500 (EST) (envelope-from rhh) Date: Mon, 20 Mar 2000 15:34:29 -0500 From: Randall Hopper To: Cameron Grant Cc: Amancio Hasty , Conrad Sabatier , stable@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Message-ID: <20000320153429.A1373@ipass.net> References: <200003191838.KAA40955@rah.star-gate.com> <000701bf91d5$4aebeb60$0304020a@NENYA> <001a01bf91c1$7f62a4b0$0304020a@NENYA> <200003191838.KAA40955@rah.star-gate.com> <20000319220453.A65973@ipass.net> <005d01bf9221$4660ac60$0304020a@NENYA> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <005d01bf9221$4660ac60$0304020a@NENYA>; from gandalf@vilnya.demon.co.uk on Mon, Mar 20, 2000 at 04:03:39AM -0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cameron Grant: |Randall Hopper: |> - Have we identified exactly what functionality is missing in the new |> sound driver but supported by Voxware? | |to my knowledge, midi is the only functionality missing. also, multiple |opens of /dev/dsp are not yet implemented. both will be soon. From what I hear, it sounds like we need some more testing time too. |> - Have we got volunteers with time on their hands signed up to provide |> each piece of this functionality with estimated completion dates? |> |> IMO, the cut-over to PCM should be tied to the last of these completion |> dates, revised forward or backward as actual completion dates slip. |> |> Why would we transition any other way? | |because various functionality voxware uses is now optional What does this mean? |and will be gone in the coming weeks. the kernel does not revolve around |sound, Exactly. The kernel revolves around applications. And applications revolve around users and their needs. |and voxware is an acceptable loss. once the isa shims are gone, voxware |will not compile without being newbusified which is a task of great |magnitude. at this time, the point is moot. Is it? You own a 400 room apartment building. You've built a brand-spankin new 200 room apartment building with a pool. Cool. Now you say to the residents, "Everybody over to the new building with the pool. We're gonna blow the other one up!" Do you really think the residents in the other 200 rooms are going to sleep on the the street while you expand? There are other apartments.... |unless someone comes forward with a newbusified voxware, it will be |removed soon. i, and others, will want to see code, not promises. Sorry Fred. That line don't fly with me. I don't have to stand ready with coding time to fix anything you want to break or rip out. Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 12:47:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hq.inar.ru (hq.inar.ru [212.14.161.10]) by hub.freebsd.org (Postfix) with ESMTP id 4CAE637C360 for ; Mon, 20 Mar 2000 12:42:19 -0800 (PST) (envelope-from bashkin@inar.ru) Received: (from bashkin@localhost) by hq.inar.ru (8.9.3/8.9.3/AT.EK.160699.01) id XAA22736 for freebsd-stable@freebsd.org; Mon, 20 Mar 2000 23:42:09 +0300 (MSK) Message-Id: <200003202042.XAA22736@hq.inar.ru> Subject: To: freebsd-stable@freebsd.org Date: Mon, 20 Mar 2000 23:42:08 +0300 (MSK) From: Evgeny Bashkin X-NCC-RegID: ru.inar X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsabscribe freebsd-stable -- Bye. Evgeny Bashkin bashkin@inar.ru Internet Arkhangelsk Tel/Fax: +7 (8182) 650002 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 12:47:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 0E7C537C715; Mon, 20 Mar 2000 12:33:54 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id MAA94172; Mon, 20 Mar 2000 12:33:54 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 20 Mar 2000 12:33:54 -0800 (PST) From: Kris Kennaway To: "Art Neilson, WH7N" Cc: stable@freebsd.org Subject: Re: net.inet.tcp.always_keepalive: 1 In-Reply-To: <3.0.6.32.20000318074032.00916500@pilikia.hi.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 Sat, 18 Mar 2000, Art Neilson, WH7N wrote: > I've been running 3.4-Stable for a while now and finally updated my > /etc/defaults/rc.conf from /usr/src/etc/defaults/rc.conf. I noticed > the new sysctl toggles in the conf file, and was wondering what this one > in particular did? I thought keepalive packets were for systems connected > up to providers who whould time them out if they had no activity for x > length of time. The comment here seems to indicate it is for cleanup > of dead connections. Can someone enlighten me or point me to relevant doc? > > tcp_keepalive="YES" # Kill dead TCP connections (or NO). TCP keepalives and PPP keepalives are different things. The former is for detecting and killing dead connections where the other end silently rebooted or dropped off the network, the latter is to defeat the idle timeout of an ISP (a 'PPP keepalive' can usually be any traffic sent over the modem, like a ping once a minute to an outside address). Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 13:20:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from anchor-post-31.mail.demon.net (anchor-post-31.mail.demon.net [194.217.242.89]) by hub.freebsd.org (Postfix) with ESMTP id A2D0337BF63; Mon, 20 Mar 2000 12:59:12 -0800 (PST) (envelope-from gandalf@vilnya.demon.co.uk) Received: from vilnya.demon.co.uk ([158.152.19.238]) by anchor-post-31.mail.demon.net with esmtp (Exim 2.12 #1) id 12X9G1-000CaF-0V; Mon, 20 Mar 2000 20:58:43 +0000 Received: from NENYA (nenya.rings [10.2.4.3]) by vilnya.demon.co.uk (Postfix) with SMTP id 94D39D9AD; Mon, 20 Mar 2000 20:58:20 +0000 (GMT) Message-ID: <000c01bf92af$144ac600$0304020a@NENYA> From: "Cameron Grant" To: "Randall Hopper" Cc: "Amancio Hasty" , "Conrad Sabatier" , , References: <200003191838.KAA40955@rah.star-gate.com> <000701bf91d5$4aebeb60$0304020a@NENYA> <001a01bf91c1$7f62a4b0$0304020a@NENYA> <200003191838.KAA40955@rah.star-gate.com> <20000319220453.A65973@ipass.net> <005d01bf9221$4660ac60$0304020a@NENYA> <20000320153429.A1373@ipass.net> Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Date: Mon, 20 Mar 2000 20:58:44 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > |to my knowledge, midi is the only functionality missing. also, multiple > |opens of /dev/dsp are not yet implemented. both will be soon. >From what I hear, it sounds like we need some more testing time too. exactly *what* do you think -current is? > |> Why would we transition any other way? > |because various functionality voxware uses is now optional > What does this mean? unless you define 'options COMPAT_OLDISA' voxware will not compile. > |and will be gone in the coming weeks. the kernel does not revolve around > |sound, > Exactly. The kernel revolves around applications. And applications > revolve around users and their needs. -current revolves around developers. 5.0-release will be at least a year in the making. > |and voxware is an acceptable loss. once the isa shims are gone, voxware > |will not compile without being newbusified which is a task of great > |magnitude. at this time, the point is moot. > Is it? You own a 400 room apartment building. You've built a > brand-spankin new 200 room apartment building with a pool. Cool. Now you > say to the residents, "Everybody over to the new building with the pool. > We're gonna blow the other one up!" Do you really think the residents in > the other 200 rooms are going to sleep on the the street while you expand? > There are other apartments.... this similie is not appropriate to -current, which is the subject of this discussion. > |unless someone comes forward with a newbusified voxware, it will be > |removed soon. i, and others, will want to see code, not promises. > Sorry Fred. That line don't fly with me. I don't have to stand ready with > coding time to fix anything you want to break or rip out. then suffer the loss gracefully. -cg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 13:21: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gadolinium.btinternet.com (gadolinium.btinternet.com [194.73.73.111]) by hub.freebsd.org (Postfix) with ESMTP id DD83E37C2B1 for ; Mon, 20 Mar 2000 13:14:21 -0800 (PST) (envelope-from mark@ukug.uk.freebsd.org) Received: from [213.1.70.218] (helo=parish.my.domain) by gadolinium.btinternet.com with esmtp (Exim 2.05 #1) id 12X9Va-0000QR-00; Mon, 20 Mar 2000 21:14:42 +0000 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id VAA01674; Mon, 20 Mar 2000 21:14:17 GMT (envelope-from mark) Date: Mon, 20 Mar 2000 21:14:16 +0000 From: Mark Ovens To: genew@home.com Cc: FreeBSD-STABLE Subject: Re: 3.4->4.0 ld-elf.so.1 error? Message-ID: <20000320211416.F236@parish> References: <20000320194621.UFT1324.mail.rdc1.on.home.com@CR121722-a> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000320194621.UFT1324.mail.rdc1.on.home.com@CR121722-a>; from genew@home.com on Mon, Mar 20, 2000 at 02:51:11PM -0500 Organization: Total lack of Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 20, 2000 at 02:51:11PM -0500, genew@home.com wrote: > I am upgrading from 3.4-s to 4.0 and have been following the > instructions in the UPGRADING doc. > I am receiving an error that I have not seen mentioned in this list. > I am at the step of 'config YOUR-KERNAL-HERE' but when I run > the config I get an error saying... > "/usr/libexec/ld-elf.so.1: Shared object 'libc.so.4' not found" > and it stops. > while doing make buildworld I noticed a few other references to the > same error but the build kept going so I didn't pay not attention to > them. > > I know I have am missing something somewhere but I have no idea > where. > I don't think you're missing anything. I got the same thing (and another 166 instances of the same message during ``make buildworld''). # ldconfig -R /usr/obj/usr/src/lib/libc # config YOUR-KERNEL-HERE will fix it. > and suggestions ( or answers ) would be appreciated > > Gene Wright > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Seminars, n.: From "semi" and "arse", hence, any half-assed discussion. ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:mark@ukug.uk.freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 13:49: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay.ultimanet.com (relay.ultimanet.com [205.179.129.1]) by hub.freebsd.org (Postfix) with ESMTP id 3947E37C6C2 for ; Mon, 20 Mar 2000 13:48:59 -0800 (PST) (envelope-from randy@Cloudfactory.ORG) Received: from Cloudfactory.ORG (cloudfactory.org [205.179.129.18]) by relay.ultimanet.com (8.9.3/8.9.3) with ESMTP id OAA23489; Mon, 20 Mar 2000 14:06:13 -0800 Message-Id: <200003202206.OAA23489@relay.ultimanet.com> To: "Morten Seeberg" Cc: freebsd-stable@freebsd.org Subject: Re: psm mouse = psmintr errors on 4.0R In-Reply-To: Your message of "Mon, 20 Mar 2000 18:01:13 +0100." <030401bf928d$e6e6c270$deff58c1@sos> Date: Mon, 20 Mar 2000 13:48:47 -0800 From: Randy Primeaux Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try: http://www.FreeBSD.org/FAQ/x.html#AEN2536 man psm For my specific issue, I turned on NOCHECKSYNC for my trackball. These are my kernel config entries: # psm 0x100 NOCHECKSYNC # man psm - bit 8 NOCHECKSYNC for ThinkingMouse on KVM. device psm0 at isa? tty flags 0x100 irq 12 Good luck with your trackpoint mouse. Your mileage may vary. "Morten Seeberg" writes: > Hi, my 4.0-RELEASE finds the PS/2 mouse just fine, but when I try to > configure the mouse daemon in sysinstall, i get the error below on my > console and in my logs (se the end of dmesg). > > All the info I could find searching the archives and the website relate to > older versions of FreeBSD. I running 4.0R on an IBM PC300PL (P200-MMX) with > an IBM Intellimouse (the one with the little clitoris :) ). > > Any ideas? [=snip=] > psm0: irq 12 on atkbdc0 > psm0: model IntelliMouse, device ID 3 [=snip=] > psmintr: out of sync (0008 != 0000). > psmintr: out of sync (0008 != 0000). > psmintr: out of sync (00c8 != 0000). > psmintr: out of sync (00c8 != 0000). -- Randy Primeaux randy@cloudfactory.org http://cloudfactory.org/~randy/ tranze@hyperreal.org http://hyperreal.org/~tranze/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 14:18: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id F1E4237BAAB; Mon, 20 Mar 2000 14:17:46 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: from mojave.worldwide.lemis.com ([216.88.157.130]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id IAA13101; Tue, 21 Mar 2000 08:47:35 +1030 (CST) (envelope-from grog@mojave.worldwide.lemis.com) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id OAA04104; Mon, 20 Mar 2000 14:17:16 -0800 (PST) (envelope-from grog) Date: Mon, 20 Mar 2000 14:17:15 -0800 From: Greg Lehey To: "Jim C. Nasby" Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: 3.4-4.0 and vinum Message-ID: <20000320141715.C3675@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <38D48D3D.1DBA8F5D@nasby.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38D48D3D.1DBA8F5D@nasby.net>; from jim@nasby.net on Sun, Mar 19, 2000 at 02:18:05AM -0600 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 19 March 2000 at 2:18:05 -0600, Jim C. Nasby wrote: > For those of you who are running vinum, make damn sure you keep an old > kernel around while upgrading... it seems that you can't load vinum > after booting with the new kernel... I'm hoping that a make install in > the vinum directory will remedy this situation... I'll post an update > once I know what's going on, but in the meantime, this is a heads-up for > everyone running vinum. This appears to be a problem that the upgrade doesn't install the klds for the new kernel. If you install them, you should be OK. Greg -- When replying to this message, please copy the original recipients. 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 Mar 20 14:40: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from veldy.net (veldy-host201.dsl.visi.com [208.42.48.201]) by hub.freebsd.org (Postfix) with ESMTP id C8EBA37B75B; Mon, 20 Mar 2000 14:39:50 -0800 (PST) (envelope-from veldy@fuggle.veldy.net) Received: by veldy.net (Postfix, from userid 1000) id 1719F1923; Mon, 20 Mar 2000 16:42:56 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by veldy.net (Postfix) with ESMTP id 09E6D1921; Mon, 20 Mar 2000 16:42:56 -0600 (CST) Date: Mon, 20 Mar 2000 16:42:55 -0600 (CST) From: "Thomas T. Veldhouse" To: freebsd-stable , freebsd-current Subject: compat3x in 4.0-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 Where did the compat3x install files go in the latest 4.0-STABLE snapshot? They seem to be missing. 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 Mon Mar 20 15: 4:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 205ED37B9B4; Mon, 20 Mar 2000 15:04:29 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id PAA50301; Mon, 20 Mar 2000 15:03:03 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200003202303.PAA50301@rah.star-gate.com> To: Randall Hopper Cc: Cameron Grant , Amancio Hasty , Conrad Sabatier , stable@FreeBSD.ORG, multimedia@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) In-reply-to: Your message of "Mon, 20 Mar 2000 15:34:29 EST." <20000320153429.A1373@ipass.net> Date: Mon, 20 Mar 2000 15:03:03 -0800 From: Amancio Hasty Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG don't worry guys I am stepping in however not today I have work related priorities dictating my time . Fortunately, I am coming out of my crunch. For years, I have supported you guys so please keep the flames down for starters thats not really who we are -- Remember we are friendly and cool 8) Best Regards To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 15:36: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from carlton.innotts.co.uk (carlton.innotts.co.uk [212.56.32.2]) by hub.freebsd.org (Postfix) with ESMTP id B592F37C230 for ; Mon, 20 Mar 2000 15:36:02 -0800 (PST) (envelope-from robmel@nadt.org.uk) Received: from muffin.highwire.local (pool-1-p15.innotts.co.uk [212.56.33.15]) by carlton.innotts.co.uk (8.9.3/8.9.3) with ESMTP id XAA14832 for ; Mon, 20 Mar 2000 23:36:00 GMT Received: from [172.16.17.20] (robsmac.highwire.local [172.16.17.20]) by muffin.highwire.local (8.9.3/8.9.3) with ESMTP id XAA10879 for ; Mon, 20 Mar 2000 23:33:59 GMT (envelope-from robmel@nadt.org.uk) Mime-Version: 1.0 X-Sender: robmel@mailhost Message-Id: Date: Tue, 21 Mar 2000 00:33:32 +0100 To: freebsd-stable@freebsd.org From: Robin Melville Subject: A very tiny issue Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a small issue, the man page for popen/pclose has a small inconsistency about the return value from pclose -- man 3 pclose: > The pclose() function waits for the associated process to terminate and > returns the exit status of the command as returned by wait4(). and then... > The pclose() function returns -1 if stream is not associated with a > ``popened'' command, if stream already ``pclosed'', or if wait4 returns > an error. Actually. I believe neither to be true, it returns (-1) if not opened by popen OR exited with a signal other than EINTR, otherwise the exit status as returned by wait4(). Very best wishes Robin. ---------------------------------------------------------------------- Robin Melville, Addiction Information Services Nottingham Alcohol & Drug Team Tel: +44 (0)115 952 9478 Fax: +44 (0)115 952 9421 work: robmel@nadt.org.uk home: robmel@innotts.co.uk Pages: http://www.innotts.co.uk/~robmel (home page) http://www.nadt.org.uk/ (substance misuse pages) ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 15:36:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (Postfix) with ESMTP id 03EA337BA52; Mon, 20 Mar 2000 15:36:42 -0800 (PST) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id AAA07689; Tue, 21 Mar 2000 00:36:18 +0100 (CET) Message-ID: <20000321003618.A7626@foobar.franken.de> Date: Tue, 21 Mar 2000 00:36:18 +0100 From: Harold Gutch To: Mike Smith Cc: stable@FreeBSD.ORG, jlemon@flugsvamp.com Subject: Re: booting 3.x from CD? References: <20000105191920.D11588@foobar.franken.de> <200001060829.AAA01025@mass.cdrom.com> <20000106144633.A13911@foobar.franken.de> <20000320155420.B6058@foobar.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <20000320155420.B6058@foobar.franken.de>; from Harold Gutch on Mon, Mar 20, 2000 at 03:54:20PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 20, 2000 at 03:54:20PM +0100, Harold Gutch wrote: > On Thu, Jan 06, 2000 at 02:46:33PM +0100, Harold Gutch wrote: > > On Thu, Jan 06, 2000 at 12:29:18AM -0800, Mike Smith wrote: > > > > On a (semi-)related topic - I tried to install FreeBSD > > > > 3.3-RELEASE on my "Gericom" notebook last week and _always_ > > > > failed when booting from either the CD or from the 3.3 bootdisks > > > > I had created. > > > > The booting process would halt at either the point where it says > > > > > > > > Timecounter "i8254" frequency 1193182 Hz > > > > > > > > or it would pass exactly this point and then halt at the next > > > > screen (the one where you select wether you want to config your > > > > kernel in visual mode etc.). At one of these points it would > > > > simply freeze, no panic, no dump, nothing. > > > > > > More details (eg. the output when you use 'boot -v' on the install > > > floppies) would be helpful. > > > > Whoops, yes, I forgot to attach it to my last mail. > > This is the output when booting from the CD. I doubt that the > > verbose output from a bootdisk will look different, but I could > > give it a try... > > > > > > > It'd be interesting to know if you have the same problem with the boot > > > floppies for a recent 4.0 snapshot. > > > > It halts at exactly the same point. > > I tried upgrading my notebook to 4.0-RELEASE last night and > it froze at exactly the same point again. > > Two things to note: > a) When booting with boot_ddb set, the kernel drops to DDB, but > that's it - I can't do/type anything in DDB > b) A GENERIC kernel from 4.0-CURRENT as of January 23rd 1999 > (just a few days after 4.0 got split off) boots just fine. > I just started a "binary search" trying to nail down the last > day it worked (and perhaps even the commit that broke it). This is the commit that broke things for me. A kernel built from the sources just before it boots, a kernel built from the sources right after it "freezes" at the point above. jlemon 1999/06/01 11:20:37 PDT Modified files: sys/dev/syscons scvesactl.c syscons.c sys/i386/apm apm.c Log: Unifdef VM86 Reviewed by: silence on on -current Revision Changes Path 1.10 +3 -4 src/sys/dev/syscons/scvesactl.c 1.306 +4 -5 src/sys/dev/syscons/syscons.c 1.88 +1 -8 src/sys/i386/apm/apm.c Modified files: sys/i386/conf LINT files.i386 options.i386 Log: Make vm86 a standard component Reviewed by: silence on on -current Revision Changes Path 1.605 +2 -9 src/sys/i386/conf/LINT 1.246 +2 -2 src/sys/i386/conf/files.i386 1.115 +1 -2 src/sys/i386/conf/options.i386 Modified files: sys/i386/i386 exception.s genassym.c globals.s locore.s machdep.c mp_machdep.c mpboot.s pmap.c swtch.s sys_machdep.c trap.c vm86.c vm86bios.s vm_machdep.c sys/i386/include globaldata.h globals.h pcb.h vm86.h sys/i386/isa apic_vector.s ipl.s vesa.c sys/i386/svr4 svr4_locore.s svr4_machdep.c sys/kern subr_prf.c sys/modules/vesa Makefile Log: Unifdef VM86. Reviewed by: silence on on -current Revision Changes Path 1.61 +1 -4 src/sys/i386/i386/exception.s 1.70 +1 -10 src/sys/i386/i386/genassym.c 1.12 +1 -6 src/sys/i386/i386/globals.s 1.123 +1 -17 src/sys/i386/i386/locore.s 1.337 +363 -285 src/sys/i386/i386/machdep.c 1.102 +1 -4 src/sys/i386/i386/mp_machdep.c 1.11 +1 -5 src/sys/i386/i386/mpboot.s 1.237 +1 -2 src/sys/i386/i386/pmap.c 1.82 +1 -14 src/sys/i386/i386/swtch.s 1.42 +1 -8 src/sys/i386/i386/sys_machdep.c 1.138 +1 -10 src/sys/i386/i386/trap.c 1.26 +18 -97 src/sys/i386/i386/vm86.c 1.14 +1 -3 src/sys/i386/i386/vm86bios.s 1.122 +1 -14 src/sys/i386/i386/vm_machdep.c 1.10 +1 -3 src/sys/i386/include/globaldata.h 1.3 +1 -5 src/sys/i386/include/globals.h 1.28 +1 -5 src/sys/i386/include/pcb.h 1.11 +3 -2 src/sys/i386/include/vm86.h 1.39 +1 -3 src/sys/i386/isa/apic_vector.s 1.28 +1 -7 src/sys/i386/isa/ipl.s 1.24 +3 -4 src/sys/i386/isa/vesa.c 1.4 +0 -2 src/sys/i386/svr4/svr4_locore.s 1.5 +0 -4 src/sys/i386/svr4/svr4_machdep.c 1.52 +18 -1 src/sys/kern/subr_prf.c 1.6 +3 -7 src/sys/modules/vesa/Makefile I noticed that when booting with older sources, the kernel reports: [...] sio0: system console [...] which looks pretty wrong to me, as the console are the keyboard and the screen attached to it (I didn't even connect anything to the serial ports). I have absolutely no idea how to debug the problem I described above, as not even setting "boot_ddb" managed to break into a debugger where I would be able to at least try to have a closer look at this problem. Does somebody have any ideas what I could try out? bye, Harold -- Someone should do a study to find out how many human life spans have been lost waiting for NT to reboot. Ken Deboy on Dec 24 1999 in comp.unix.bsd.freebsd.misc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 17: 3:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id A0E5A37BC71; Mon, 20 Mar 2000 17:03:41 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA04298; Mon, 20 Mar 2000 17:05:31 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003210105.RAA04298@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Harold Gutch Cc: Mike Smith , stable@FreeBSD.ORG, jlemon@flugsvamp.com Subject: Re: booting 3.x from CD? In-reply-to: Your message of "Tue, 21 Mar 2000 00:36:18 +0100." <20000321003618.A7626@foobar.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 20 Mar 2000 17:05:31 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > The booting process would halt at either the point where it says > > > > > > > > > > Timecounter "i8254" frequency 1193182 Hz > > > > > > > > > > or it would pass exactly this point and then halt at the next > > > > > screen (the one where you select wether you want to config your > > > > > kernel in visual mode etc.). At one of these points it would > > > > > simply freeze, no panic, no dump, nothing. ... > This is the commit that broke things for me. A kernel built from > the sources just before it boots, a kernel built from the sources > right after it "freezes" at the point above. Which one of the points above? > I have absolutely no idea how to debug the problem I described > above, as not even setting "boot_ddb" managed to break into a > debugger where I would be able to at least try to have a closer > look at this problem. > Does somebody have any ideas what I could try out? Sounds like you've got BIOS problems. Look for an upgrade from your vendor, and then start breaking down the kernel boot process to see if you can find where exactly it's hanging up. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 17:49:23 2000 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 68A2037BEF8 for ; Mon, 20 Mar 2000 17:49:20 -0800 (PST) (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 RAA13132; Mon, 20 Mar 2000 17:48:08 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda13130; Mon Mar 20 17:48:07 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id RAA99788; Mon, 20 Mar 2000 17:48:07 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdt99786; Mon Mar 20 17:47:38 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id RAA15848; Mon, 20 Mar 2000 17:47:37 -0800 (PST) Message-Id: <200003210147.RAA15848@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdZ15843; Mon Mar 20 17:47:16 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: Sheldon Hearn Cc: Cy Schubert - ITSD Open Systems Group , Randall Hopper , stable@FreeBSD.ORG Subject: Re: Missing man pages: ld.so, sigwait() In-reply-to: Your message of "Mon, 20 Mar 2000 16:10:11 +0200." <22019.953561411@axl.ops.uunet.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 20 Mar 2000 17:47:16 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <22019.953561411@axl.ops.uunet.co.za>, Sheldon Hearn writes: > > > On Mon, 20 Mar 2000 05:39:18 PST, Cy Schubert - ITSD Open Systems Group wrote > : > > > Agreeed, there is no man page for sigwait, however on my 3.4R systems: > > > > cwsys$ man -k ld.so > > ld.so(1) - run-time link-editor > > Check the date on /opt3/usr/share/man/man1/ld.so.1.gz, I'm pretty sure > it's stale. Your are indeed correct. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC 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 Mon Mar 20 18:32:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 31C2037B999 for ; Mon, 20 Mar 2000 18:32:51 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt6-216-180-5-65.dialup.HiWAAY.net [216.180.5.65]) by mail.HiWAAY.net (8.9.3/8.9.0) with ESMTP id UAA30536; Mon, 20 Mar 2000 20:32:45 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id TAA54503; Mon, 20 Mar 2000 19:47:46 -0600 (CST) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <200003210147.TAA54503@nospam.hiwaay.net> X-Mailer: exmh version 2.1.1 10/15/1999 To: Vivek Khera Cc: stable@FreeBSD.ORG From: David Kelly Subject: Re: Netscape pegs CPU on XServer kill In-reply-to: Message from Vivek Khera of "Mon, 20 Mar 2000 10:55:02 EST." <14550.18902.797775.916259@onceler.kcilink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 20 Mar 2000 19:47:46 -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vivek Khera writes: > >>>>> "DK" == David Kelly writes: > > DK> Speaking of which, am I the only one seeing: > > DK> pid 4106 (communicator-4.7), uid 928: exited on signal 10 (core dumped) > > It does not happen to me, except when doing Java. When Java is on, it > dumps any time it feels like, even when viewing non-java enabled > pages. With Java off, it is at least somewhat stable and rarely > crashes. What doesn't appear to be clear is that the native FreeBSD Communicator is not *crashing*. When I select "Exit" it disappears just as I expect it to but dmesg, the console, and /var/log/messages, are filled with the above note. And it *says* it "core dumped" but I haven't found any netscape.core's laying around lately. -- 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 Mar 20 18:32:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 6D24F37BA6E for ; Mon, 20 Mar 2000 18:32:51 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt6-216-180-5-65.dialup.HiWAAY.net [216.180.5.65]) by mail.HiWAAY.net (8.9.3/8.9.0) with ESMTP id UAA09743; Mon, 20 Mar 2000 20:32:47 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id TAA54389; Mon, 20 Mar 2000 19:42:51 -0600 (CST) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <200003210142.TAA54389@nospam.hiwaay.net> X-Mailer: exmh version 2.1.1 10/15/1999 To: Randall Hopper Cc: stable@FreeBSD.ORG From: David Kelly Subject: Re: Netscape pegs CPU on XServer kill In-reply-to: Message from Randall Hopper of "Sun, 19 Mar 2000 22:25:01 EST." <20000319222501.A66999@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 20 Mar 2000 19:42:49 -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Randall Hopper writes: > David Kelly: > |Speaking of which, am I the only one seeing: > | > |pid 4106 (communicator-4.7), uid 928: exited on signal 10 (core dumped) > |pid 4113 (communicator-4.7), uid 928: exited on signal 10 (core dumped) > |pid 4211 (communicator-4.7), uid 928: exited on signal 10 (core dumped) > |pid 4215 (communicator-4.7), uid 928: exited on signal 10 (core dumped) > |pid 4219 (communicator-4.7), uid 928: exited on signal 10 (core dumped) > | > |on *every* exit of the FreeBSD native U.S. Communicator? Same thing > |with 4.7 and 4.72. Think this started when I upgraded XFree86 from > |3.3.1 to 3.3.6, built from the port. > > Hmm. I've not even seen this. Just as a data point, most recently, I'm > running 3.4-R, XFree86 3.3.5 depth 16, Netscape Navigator 4.72 from ports. Maybe its a screw up on my part. I *think* I'm running 16bpp but have completely forgotten where/how to check. When the X server is started I don't see mention of pixel depth, only a complaint about inability to probe the Mill II's RAM size. Have updated /etc/XF86Config, will see what it says next time. Also with the 3.3.6 upgrade I believe scrolling has gotten jerky, leading me to suspect that I don't have the accelerated SVGA driver operating my Matrox Millenium II 4MB. Maybe the above edits to /etc/XF86Config will help. -- 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 Mar 20 18:35:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 28EE137B8F2; Mon, 20 Mar 2000 18:35:45 -0800 (PST) (envelope-from jim@nasby.net) Received: from nasby.net (sysnasby@2.nasby.dsl.enteract.com [216.80.51.18]) by mail.enteract.com (8.9.3/8.9.3) with ESMTP id UAA56872; Mon, 20 Mar 2000 20:35:30 -0600 (CST) (envelope-from jim@nasby.net) Message-ID: <38D6DFF3.2142EFAA@nasby.net> Date: Mon, 20 Mar 2000 20:35:31 -0600 From: "Jim C. Nasby" Organization: distributed.net X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en-US,en MIME-Version: 1.0 To: Greg Lehey Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: How to upgrade to 4.0 with vinum [was: Re: 3.4-4.0 and vinum] References: <38D48D3D.1DBA8F5D@nasby.net> <20000320141715.C3675@mojave.worldwide.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yup, absolutely correct Greg. For everyone else, here's the steps that you need to take to upgrade to 4.0 if your /usr is on a vinum volume. (If you're running vinum but /usr is on a 'normal' device then I think you'll be ok). 1) Follow the instructions in /usr/src/UPDATING up to the reboot (don't reboot yet), but make sure that you keep an backup copy of your 3.4 kernel 2) You need to install the new vinum kernel module and userland, but before you do this, I very, very strongly recommend you back up the old files. If something goes wrong and you have to go back, you're in big trouble without them. To back them up: cp /modules/vinum.ko /modules/vinum.3; cp /sbin/vinum /sbin/vinum.3 3) Install the new vinum software. cd /usr/src/sys/modules/vinum && make install && cd /usr/src/sbin/vinum && make install 4) You should now be able to reboot to single-user and continue on. I don't know if this is normal for a non-vinum machine or not, but my machine doesn't do any mounting of devices when booted to single-user. In order to get your filesystems up and running, do this as soon as you have a shell: vinum start fsck -p mount -a You should now be good to go. Greg/anyone else: I did this over 3 days and finished very late last night, so if I screwed anything up here, please correct me. Good luck! :) Greg Lehey wrote: > > On Sunday, 19 March 2000 at 2:18:05 -0600, Jim C. Nasby wrote: > > For those of you who are running vinum, make damn sure you keep an old > > kernel around while upgrading... it seems that you can't load vinum > > after booting with the new kernel... I'm hoping that a make install in > > the vinum directory will remedy this situation... I'll post an update > > once I know what's going on, but in the meantime, this is a heads-up for > > everyone running vinum. > > This appears to be a problem that the upgrade doesn't install the klds > for the new kernel. If you install them, you should be OK. > > Greg > -- > When replying to this message, please copy the original recipients. > 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 -- 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 Mon Mar 20 18:49:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from charon.ipass.net (charon.ipass.net [198.79.53.8]) by hub.freebsd.org (Postfix) with ESMTP id 2A16C37BC77 for ; Mon, 20 Mar 2000 18:49:41 -0800 (PST) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-2-223.dialup.rdu.ipass.net [209.170.133.223]) by charon.ipass.net (8.9.3/8.9.3) with ESMTP id VAA18382; Mon, 20 Mar 2000 21:49:39 -0500 (EST) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id VAA12297; Mon, 20 Mar 2000 21:52:09 -0500 (EST) (envelope-from rhh) Date: Mon, 20 Mar 2000 21:52:09 -0500 From: Randall Hopper To: David Kelly Cc: stable@FreeBSD.ORG Subject: Re: Netscape pegs CPU on XServer kill Message-ID: <20000320215209.C11239@ipass.net> References: <200003210142.TAA54389@nospam.hiwaay.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003210142.TAA54389@nospam.hiwaay.net>; from dkelly@hiwaay.net on Mon, Mar 20, 2000 at 07:42:49PM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Kelly: |Randall Hopper writes: |> David Kelly: |> |Speaking of which, am I the only one seeing: |> | |> |pid 4106 (communicator-4.7), uid 928: exited on signal 10 (core dumped) |> |pid 4113 (communicator-4.7), uid 928: exited on signal 10 (core dumped) |> |pid 4211 (communicator-4.7), uid 928: exited on signal 10 (core dumped) |> |pid 4215 (communicator-4.7), uid 928: exited on signal 10 (core dumped) |> |pid 4219 (communicator-4.7), uid 928: exited on signal 10 (core dumped) |> | |> |on *every* exit of the FreeBSD native U.S. Communicator? Same thing |> |with 4.7 and 4.72. Think this started when I upgraded XFree86 from |> |3.3.1 to 3.3.6, built from the port. |> |> Hmm. I've not even seen this. Just as a data point, most recently, I'm |> running 3.4-R, XFree86 3.3.5 depth 16, Netscape Navigator 4.72 from ports. | |Maybe its a screw up on my part. I *think* I'm running 16bpp but have |completely forgotten where/how to check. When the X server is started I |don't see mention of pixel depth, only a complaint about inability to |probe the Mill II's RAM size. Have updated /etc/XF86Config, will see |what it says next time. Easiest way is to run: xwininfo and click on the Netscape window. You can also look at the default visual (which is what apps come up in unless they override and pick their own visual): xdpyinfo | grep 'default visual id' That'll give you a visual ID for the default visual. Then: xdpyinfo | more and look at the visual section with that ID. For example, here: default visual id: 0x22 visual: visual id: 0x22 class: TrueColor depth: 16 planes available colormap entries: 64 per subfield red, green, blue masks: 0xf800, 0x7e0, 0x1f significant bits in color specification: 6 bits Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 20: 6:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 8236A37BA42 for ; Mon, 20 Mar 2000 20:05:54 -0800 (PST) (envelope-from mmercer@ipass.net) Received: from ipass.net (dsl-2-196.dsl.rdu.ipass.net [209.170.144.196] (may be forged)) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id XAA22393 for ; Mon, 20 Mar 2000 23:05:39 -0500 (EST) Message-ID: <38D6F515.D0536435@ipass.net> Date: Mon, 20 Mar 2000 23:05:42 -0500 From: "Michael E. Mercer" Reply-To: mmercer@ipass.net X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: ep0 eeprom failed to come ready... 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 have a 3com 3C509-TPO Etherlink III card... I have just upgraded my pentium 200 MMX machine to 4.0-Stable. Everything seems to be going well except that it fails with ep0: <3Com 3C509-TPO Etherlink III> at port 0x300-0x30f irq 10 on isa0 ep0: eeprom failed to come ready. last line repeated 4 more times... then later during the boot process it finds the same card on a different port and everything is fine... except now I can not get to the outside world... ep0: <3Com 3C509-TPO Etherlink III> at port 0x210-0x21f irq 10 on isa0 What is the problem here.... normally with me it is user error so let me know... Thanks Michael Mercer mmercer@ipass.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 20:44:20 2000 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 BAB0537BCC3 for ; Mon, 20 Mar 2000 20:44:12 -0800 (PST) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id XAA84551; Mon, 20 Mar 2000 23:44:35 -0500 (EST) (envelope-from bandix@looksharp.net) Date: Mon, 20 Mar 2000 23:44:35 -0500 (EST) From: "Brandon D. Valentine" To: FreeBSD-STABLE Cc: Patrick Gardella Subject: Re: SMP oddity In-Reply-To: <38D68096.6F2F8575@science-guy.npt.nuwc.navy.mil> 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, 20 Mar 2000, Tod Luginbuhl wrote: >I am running 3.4-RELEASE on a dual Pentium-III 450mHz ASUS P2BDS >system. I install the patch this afternoon by hand, rebuilt and install >the new kernel. The information cpu clock speed information comes up >correctly now when booting the new kernel. I haven't done extensive >system testing yet, but the kernel seems to be stable. On that note, since I booted with the patched kernel the other day I started up RC5 and gave the machine a good burn-in and it's running with no problems whatsoever. In fact, I've had an ssh session open to it for the past 72 hours that hasn't so much as hiccuped. Considering the relative triviality of the patch and the fact that Mr. Luginbuhl echoes my success I'd say it's a safe commit. ------------------------------------------------------------- | -Brandon D. Valentine bandix at looksharp.net | bandix on EFnet IRC BVRiker on AIM ------------------------------------------------------------- | "...and as for hackers, we note that all of those known to | The Register are so strapped financially that seizing their | property would be tantamount to squeezing blood from a | stone." -- The Register, 02/17/2000 ------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 21: 1:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by hub.freebsd.org (Postfix) with ESMTP id A9B0737B96C; Mon, 20 Mar 2000 21:01:46 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca6-109.ix.netcom.com [205.186.213.109]) by tisch.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id AAA26453; Tue, 21 Mar 2000 00:01:25 -0500 (EST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id VAA96598; Mon, 20 Mar 2000 21:00:59 -0800 (PST) To: "Thomas T. Veldhouse" Cc: freebsd-stable , freebsd-current Subject: Re: compat3x in 4.0-STABLE? References: From: asami@freebsd.org (Satoshi - Ports Wraith - Asami) Date: 20 Mar 2000 20:59:46 -0800 In-Reply-To: "Thomas T. Veldhouse"'s message of "Mon, 20 Mar 2000 16:42:55 -0600 (CST)" Message-ID: Lines: 10 X-Mailer: Gnus v5.7/Emacs 20.6 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: "Thomas T. Veldhouse" * Where did the compat3x install files go in the latest 4.0-STABLE * snapshot? They seem to be missing. That was actually a 3.4-STABLE snapshot that ended up in a directory with a wrong name. Jordan fixed it (and deleted the offending snapshot) so new ones, when they get built, should be fine. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 21: 5:50 2000 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 CF9CF37BAC8 for ; Mon, 20 Mar 2000 21:05:45 -0800 (PST) (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 VAA13459; Mon, 20 Mar 2000 21:05:13 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda13457; Mon Mar 20 21:05:13 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id VAA00547; Mon, 20 Mar 2000 21:05:13 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdgJE539; Mon Mar 20 21:05:01 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id UAA41566; Mon, 20 Mar 2000 20:26:45 -0800 (PST) Message-Id: <200003210426.UAA41566@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdC41561; Mon Mar 20 20:26:18 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: mmercer@ipass.net Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ep0 eeprom failed to come ready... In-reply-to: Your message of "Mon, 20 Mar 2000 23:05:42 EST." <38D6F515.D0536435@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 20 Mar 2000 20:26:17 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38D6F515.D0536435@ipass.net>, "Michael E. Mercer" writes: > hello, > > I have a 3com 3C509-TPO Etherlink III card... > I have just upgraded my pentium 200 MMX machine to 4.0-Stable. > Everything seems to be going well except that it fails with > ep0: <3Com 3C509-TPO Etherlink III> at port 0x300-0x30f irq 10 on isa0 > ep0: eeprom failed to come ready. > last line repeated 4 more times... > > then later during the boot process it finds the same card on a different port > and everything is fine... except now I can not get to the outside world... > > ep0: <3Com 3C509-TPO Etherlink III> at port 0x210-0x21f irq 10 on isa0 > > What is the problem here.... normally with me it is user error so let me know > ... I had the same problem. You have two solutions to choose from: 1. Build a custom kernel w/o unnecessary network devices. 2. boot -c and delete all unnecessary network devices. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC 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 Mon Mar 20 22:20:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from proxy.outblaze.com (proxy.outblaze.com [202.77.223.120]) by hub.freebsd.org (Postfix) with SMTP id 4D7BB37BC0A for ; Mon, 20 Mar 2000 22:20:06 -0800 (PST) (envelope-from yusufg@outblaze.com) Received: (qmail 2901 invoked from network); 21 Mar 2000 06:19:48 -0000 Received: from unknown (HELO yusufg.portal2.com) (202.77.181.217) by proxy.outblaze.com with SMTP; 21 Mar 2000 06:19:48 -0000 Received: (qmail 8727 invoked by uid 500); 21 Mar 2000 06:19:51 -0000 Date: 21 Mar 2000 06:19:51 -0000 Message-ID: <20000321061951.8726.qmail@yusufg.portal2.com> From: Yusuf Goolamabbas To: freebsd-stable@freebsd.org Subject: Reason for sshd[238]: fatal: rsa_private_decrypt() failed 4.0-stable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I installed 4.0 and then cvsup'ped via 4.x-secure-stable-supfile I then said USA_RESIDENT=NO in /etc/make.conf and did the usual kernel build and build world I setup an acnt to ssh into from another box and when I tried to do so, I get the following message in /var/log/messages sshd[238]: fatal: rsa_private_decrypt() failed. Did I goof up some place ? Thanks, Yusuf -- Yusuf Goolamabbas yusufg@outblaze.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 20 23:44:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (Postfix) with ESMTP id BD1E737B976; Mon, 20 Mar 2000 23:44:28 -0800 (PST) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id IAA08784; Tue, 21 Mar 2000 08:44:56 +0100 (CET) Message-ID: <20000321084455.A8694@foobar.franken.de> Date: Tue, 21 Mar 2000 08:44:55 +0100 From: Harold Gutch To: Mike Smith Cc: stable@FreeBSD.ORG, jlemon@flugsvamp.com Subject: Re: booting 3.x from CD? References: <20000321003618.A7626@foobar.franken.de> <200003210105.RAA04298@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <200003210105.RAA04298@mass.cdrom.com>; from Mike Smith on Mon, Mar 20, 2000 at 05:05:31PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 20, 2000 at 05:05:31PM -0800, Mike Smith wrote: > > > > > > The booting process would halt at either the point where it says > > > > > > > > > > > > Timecounter "i8254" frequency 1193182 Hz > > > > > > > > > > > > or it would pass exactly this point and then halt at the next > > > > > > screen (the one where you select wether you want to config your > > > > > > kernel in visual mode etc.). At one of these points it would > > > > > > simply freeze, no panic, no dump, nothing. > ... > > This is the commit that broke things for me. A kernel built from > > the sources just before it boots, a kernel built from the sources > > right after it "freezes" at the point above. > > Which one of the points above? Sorry for being unclear. A 4.0 GENERIC-kernel built from the sourcetree as of June 1st (after the commit I mentioned in my last mail) freezes just after printing out the "Timecounter"-message I quoted above. Note that I have _not_ tried a non-GENERIC kernel, but since GENERIC failed repeatedly on me after the commit and since it worked flawlessly before the commit I guessed that this would be sufficient. I'll try compiling an own kernel with only the mostly needed options compiled in later on today. I'll try connecting a serial console to the notebook later on today when I have the time, perhaps that will help me somehow... Since the problem somehow seems related to VM86, I'll build a few test-kernels from long before June 1st with and without VM86 enabled and see if they both work. > > I have absolutely no idea how to debug the problem I described > > above, as not even setting "boot_ddb" managed to break into a > > debugger where I would be able to at least try to have a closer > > look at this problem. > > Does somebody have any ideas what I could try out? > > Sounds like you've got BIOS problems. Look for an upgrade from your > vendor, and then start breaking down the kernel boot process to see if > you can find where exactly it's hanging up. If I get you right, you're saying that these two things (the freeze and the unability to boot directly into DDB) are unrelated? OK, I'll check for BIOS updates and see if that at least fixes that one problem. bye, Harold -- Someone should do a study to find out how many human life spans have been lost waiting for NT to reboot. Ken Deboy on Dec 24 1999 in comp.unix.bsd.freebsd.misc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 0:20:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from spirit.jaded.net (liv3-3.hamilton.idirect.com [209.161.208.3]) by hub.freebsd.org (Postfix) with ESMTP id 0545537B976 for ; Tue, 21 Mar 2000 00:20:43 -0800 (PST) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id DAA04698; Tue, 21 Mar 2000 03:19:27 -0500 (EST) Date: Tue, 21 Mar 2000 03:19:27 -0500 From: Dan Moschuk To: Yusuf Goolamabbas Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Reason for sshd[238]: fatal: rsa_private_decrypt() failed 4.0-stable Message-ID: <20000321031927.A4669@spirit.jaded.net> References: <20000321061951.8726.qmail@yusufg.portal2.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000321061951.8726.qmail@yusufg.portal2.com>; from yusufg@outblaze.com on Tue, Mar 21, 2000 at 06:19:51AM -0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | Hi, I installed 4.0 and then cvsup'ped via 4.x-secure-stable-supfile | I then said USA_RESIDENT=NO in /etc/make.conf and did the usual kernel | build and build world | | I setup an acnt to ssh into from another box and when I tried to do | so, I get the following message in /var/log/messages | | sshd[238]: fatal: rsa_private_decrypt() failed. | | Did I goof up some place ? | | Thanks, Yusuf You need to install the rsaref library. See /usr/ports/security/rsaref -- Dan Moschuk (TFreak!dan@freebsd.org) "Waste not fresh tears on old griefs." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 0:27:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from proxy.outblaze.com (proxy.outblaze.com [202.77.223.120]) by hub.freebsd.org (Postfix) with SMTP id E0BF937B774 for ; Tue, 21 Mar 2000 00:27:13 -0800 (PST) (envelope-from yusufg@outblaze.com) Received: (qmail 1847 invoked from network); 21 Mar 2000 08:27:03 -0000 Received: from unknown (HELO yusufg.portal2.com) (202.77.181.217) by proxy.outblaze.com with SMTP; 21 Mar 2000 08:27:03 -0000 Received: (qmail 9150 invoked by uid 500); 21 Mar 2000 08:27:06 -0000 Date: Tue, 21 Mar 2000 16:27:06 +0800 From: Yusuf Goolamabbas To: Dan Moschuk Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Reason for sshd[238]: fatal: rsa_private_decrypt() failed 4.0-stable Message-ID: <20000321162706.B9095@outblaze.com> References: <20000321061951.8726.qmail@yusufg.portal2.com> <20000321031927.A4669@spirit.jaded.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000321031927.A4669@spirit.jaded.net>; from dan@FreeBSD.ORG on Tue, Mar 21, 2000 at 03:19:27AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Isn't that illegal (inappropiate) for somebody outside the US ? On 3-4 stable machines, I used to do make install in /usr/ports/security/openssh and it used to do the right thing Shouldn't USA_RESIDENT=NO and make world do this > | Thanks, Yusuf > > You need to install the rsaref library. > > See /usr/ports/security/rsaref > > -- > Dan Moschuk (TFreak!dan@freebsd.org) > "Waste not fresh tears on old griefs." -- Yusuf Goolamabbas yusufg@outblaze.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 0:30:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ns2.infologigruppen.se (ns2.infologigruppen.se [212.214.163.69]) by hub.freebsd.org (Postfix) with ESMTP id 9833837B7C1 for ; Tue, 21 Mar 2000 00:30:07 -0800 (PST) (envelope-from Goran.Lowkrantz@infologigruppen.se) Received: (from uucp@localhost) by ns2.infologigruppen.se (8.9.3/8.9.3) id JAA44950 for ; Tue, 21 Mar 2000 09:30:04 +0100 (CET) (envelope-from Goran.Lowkrantz@infologigruppen.se) Received: from valhall.ign.se(192.168.3.1) via SMTP by bifrost-net.ign.se, id smtpdY44945; Tue Mar 21 09:29:57 2000 Received: by valhall.ign.se with Internet Mail Service (5.5.2448.0) id ; Tue, 21 Mar 2000 09:30:40 +0100 Message-ID: From: "Lowkrantz, Goran" To: "'stable@FreeBSD.ORG'" Subject: Amanda ond Vinum Date: Tue, 21 Mar 2000 09:30:40 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01BF930F.BDA5F599" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01BF930F.BDA5F599 Content-Type: text/plain; charset="iso-8859-1" On the first backup of a new Vinum system, somthing odd happened. It seems liek Vinum reset the ownership of the devices. Description: We configured four RAID-5 disks to a fileserver following vinum(8). All working well. Then added the four new volumes to Amanda disklist and did an amcheck. This risulted in warnings that Amanda couldn't access the devised due to permission denied. So I changed the group ownership to operator, reran amcheck and this them no errors. During the night, the backup failed and when I checked the permissions they had changed back to group wheel. I have reset the permissions and enabled more debugging on amanada for this nights backup but if there are any suggestions I'd appreciate them. Appended: uname -a ls -l /dev/vinum vinum list vinum_history Amanda Tape Server Host Check Amanda report Cheers, GLZ --- Goran Lowkrantz Email : goran.lowkrantz@infologigruppen.se Infologigruppen Alfa AB Telephone: Nat 070-587 8782 Fax: Nat 070-615 8782 Box 202 Int +46 70-587 8782 Int +46 70-615 8782 941 25 Pitea, Sweden ------_=_NextPart_000_01BF930F.BDA5F599 Content-Type: text/plain; name="amanda-vinum.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="amanda-vinum.txt" =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > uname -a FreeBSD glansheim.ign.se 4.0-STABLE FreeBSD 4.0-STABLE #0: Sun Mar 19 = 17:25:11 CET 2000 root@:/usr/src/sys/compile/GLANSHEIM i386 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > ls -l /dev/vinum total 4 crw------- 1 root wheel 91, 0x40000001 Mar 20 04:33 Control crw-r----- 1 root wheel 91, 2 Mar 20 04:33 commonsw crw-r----- 1 root wheel 91, 0 Mar 20 04:33 company crw------- 1 root wheel 91, 0x40000002 Mar 20 04:33 control crw------- 1 root wheel 91, 0x40000000 Mar 20 04:33 controld drwxr-xr-x 2 root wheel 512 Mar 20 04:33 drive crw-r----- 1 root wheel 91, 3 Mar 20 04:33 home drwxr-xr-x 2 root wheel 512 Mar 20 04:33 plex crw-r----- 1 root wheel 91, 1 Mar 20 04:33 projects drwxr-xr-x 2 root wheel 512 Mar 20 04:33 sd drwxr-xr-x 6 root wheel 512 Mar 20 04:33 vol =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D # vinum list 4 drives: D disk1 State: up Device /dev/da2s1h Avail: = 0/4353 MB (0%) D disk2 State: up Device /dev/da3s1h Avail: = 0/4353 MB (0%) D disk3 State: up Device /dev/da4s1h Avail: = 0/4353 MB (0%) D disk4 State: up Device /dev/da5s1h Avail: = 0/4353 MB (0%) 4 volumes: V company State: up Plexes: 1 Size: = 1536 MB V projects State: up Plexes: 1 Size: = 3072 MB V commonsw State: up Plexes: 1 Size: = 1536 MB V home State: up Plexes: 1 Size: = 6915 MB 4 plexes: P company.p0 R5 State: up Subdisks: 4 Size: = 1536 MB P projects.p0 R5 State: up Subdisks: 4 Size: = 3072 MB P commonsw.p0 R5 State: up Subdisks: 4 Size: = 1536 MB P home.p0 R5 State: up Subdisks: 4 Size: = 6915 MB 16 subdisks: S company.p0.s0 State: up PO: 0 B Size: = 512 MB S company.p0.s1 State: up PO: 512 kB Size: = 512 MB S company.p0.s2 State: up PO: 1024 kB Size: = 512 MB S company.p0.s3 State: up PO: 1536 kB Size: = 512 MB S projects.p0.s0 State: up PO: 0 B Size: = 1024 MB S projects.p0.s1 State: up PO: 512 kB Size: = 1024 MB S projects.p0.s2 State: up PO: 1024 kB Size: = 1024 MB S projects.p0.s3 State: up PO: 1536 kB Size: = 1024 MB S commonsw.p0.s0 State: up PO: 0 B Size: = 512 MB S commonsw.p0.s1 State: up PO: 512 kB Size: = 512 MB S commonsw.p0.s2 State: up PO: 1024 kB Size: = 512 MB S commonsw.p0.s3 State: up PO: 1536 kB Size: = 512 MB S home.p0.s0 State: up PO: 0 B Size: = 2305 MB S home.p0.s1 State: up PO: 512 kB Size: = 2305 MB S home.p0.s2 State: up PO: 1024 kB Size: = 2305 MB S home.p0.s3 State: up PO: 1536 kB Size: = 2305 MB =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Amanda Tape Server Host Check ----------------------------- /dump/amanda/1: 2278628 KB disk space available, that's plenty. amcheck-server: slot 1: date 20000208 label 4mdds1000012 (exact label = match) NOTE: skipping tape-writable test. Tape 4mdds1000012 label ok. Server check took 16.842 seconds. Amanda Backup Client Hosts Check -------------------------------- ERROR: glansheim.ign.se: [can not access /dev/vinum/projects = (/dev/vinum/projects): Permission denied] ERROR: glansheim.ign.se: [can not access /dev/vinum/home = (/dev/vinum/home): Permission denied] ERROR: glansheim.ign.se: [can not access /dev/vinum/company = (/dev/vinum/company): Permission denied] ERROR: glansheim.ign.se: [can not access /dev/vinum/commonsw = (/dev/vinum/commonsw): Permission denied] Client check: 7 hosts checked in 1.637 seconds, 4 problems found. (brought to you by Amanda 2.4.1p1) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Amanda report: These dumps were to tape 4mdds1000012. Tonight's dumps should go onto 1 tape: 4mdds1000025. FAILURE AND STRANGE DUMP SUMMARY: glansheim. /dev/vinum/projects lev 0 FAILED [disk /dev/vinum/projects = offline on glansheim.ign.se?] glansheim. /dev/vinum/home lev 0 FAILED [disk /dev/vinum/home offline = on glansheim.ign.se?] glansheim. /dev/vinum/company lev 0 FAILED [disk /dev/vinum/company = offline on glansheim.ign.se?] glansheim. /dev/vinum/commonsw lev 0 FAILED [disk /dev/vinum/commonsw = offline on glansheim.ign.se?] STATISTICS: Total Full Daily -------- -------- -------- Dump Time (hrs:min) 0:54 0:15 0:12 (0:05 start, = 0:22 idle) Output Size (meg) 592.5 347.8 244.7 Original Size (meg) 1754.8 998.3 756.5 Avg Compressed Size (%) 33.8 34.8 32.3 Tape Used (%) 31.2 18.3 12.9 (level:#disks = ...) Filesystems Dumped 29 2 27 (1:25 2:1 3:1) Avg Dump Rate (k/s) 159.2 143.5 188.6 Avg Tp Write Rate (k/s) 371.8 391.5 347.1 NOTES: planner: Forcing full dump of glansheim.ign.se:da0s1f as directed. planner: Adding new disk glansheim.ign.se:/dev/vinum/commonsw. planner: Adding new disk glansheim.ign.se:/dev/vinum/company. planner: Adding new disk glansheim.ign.se:/dev/vinum/home. planner: Adding new disk glansheim.ign.se:/dev/vinum/projects. planner: Incremental of glansheim.ign.se:da1s1f bumped to level 2. taper: tape 4mdds1000012 kb 607648 fm 29 [OK] DUMP SUMMARY: DUMPER STATS = TAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s = MMM:SS KB/s -------------------------- -------------------------------------- = -------------- balder.in da0s1a 1 61 32 52.5 0:02 16.6 = 0:00 1330.5 balder.in da0s1e 1 35 32 91.4 0:01 33.7 = 0:00 1586.8 balder.in da0s1f 1 192 64 33.3 0:56 1.1 = 0:00 1110.5 balder.in da1s1e 1 107531 9056 8.4 3:55 38.6 = 0:29 317.7 bifrost-n wd0s1a 1 60 32 53.3 0:01 22.2 = 0:00 1465.8 bifrost-n wd0s1e 1 43 32 74.4 0:01 24.7 = 0:00 1470.6 bifrost-n wd0s1f 1 42472 3680 8.7 0:23 162.8 = 1:06 56.1 bifrost-n wd0s1g 3 220769 100512 45.5 4:32 370.1 = 4:19 388.6 brock.ign wd0s1a 1 611 160 26.2 0:06 26.0 = 0:00 1351.4 brock.ign wd0s1e 1 440 128 29.1 0:05 28.0 = 0:00 1196.0 brock.ign wd0s1f 1 4177 1312 31.4 0:44 29.5 = 0:06 238.8 glansheim -inum/commonsw 0 FAILED = -------------------------------------------- glansheim -vinum/company 0 FAILED = -------------------------------------------- glansheim -ev/vinum/home 0 FAILED = -------------------------------------------- glansheim -inum/projects 0 FAILED = -------------------------------------------- glansheim da0s1a 1 23995 10784 44.9 0:27 393.3 = 0:27 397.2 glansheim da0s1e 1 27927 4832 17.3 0:20 242.8 = 0:12 399.2 glansheim da0s1f 0 420731 160064 38.0 8:01 332.8 = 6:46 394.1 glansheim da1s1e 1 467 96 20.6 0:37 2.6 = 0:00 534.0 glansheim da1s1f 2 11229 3904 34.8 0:31 125.1 = 0:10 396.2 glansheim da1s1g 1 304110 104800 34.5 6:36 264.5 = 4:32 386.0 glansheim da1s1h 1 173 32 18.5 0:13 2.5 = 0:13 4.8 heimdal.i ad0s1a 1 72 32 44.4 0:05 6.7 = 0:00 1454.4 heimdal.i ad0s1e 1 8419 704 8.4 0:11 62.6 = 0:02 401.8 heimdal.i ad0s1f 1 221 32 14.5 0:04 7.7 = 0:00 1146.9 heimdal.i ad0s1g 1 4222 864 20.5 0:25 34.4 = 0:02 435.0 modgunn.i da0s1a 1 110 32 29.1 0:02 13.5 = 0:00 399.7 modgunn.i da0s1e 1 41 32 78.0 0:04 9.0 = 0:00 614.7 modgunn.i da0s1f 1 12097 7680 63.5 0:34 227.7 = 0:20 392.3 modgunn.i da0s1g 1 3991 1440 36.1 1:07 21.5 = 0:04 402.3 sindre.ig wd0s1a 1 106 32 30.2 0:03 12.3 = 0:00 1126.2 sindre.ig wd0s1e 1 1079 256 23.7 0:04 58.6 = 0:00 922.9 sindre.ig wd0s1f 0 601505 196064 32.6 33:21 98.0 = 8:23 389.5 (brought to you by Amanda version 2.4.1p1) ------_=_NextPart_000_01BF930F.BDA5F599-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 3: 3:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from thomas.clark.net (thomas.clark.net [168.143.2.191]) by hub.freebsd.org (Postfix) with ESMTP id 8A35637B53C for ; Tue, 21 Mar 2000 03:03:06 -0800 (PST) (envelope-from thomas@clark.net) Received: from minotaur (minotaur [192.168.99.100]) by thomas.clark.net (8.9.3/8.9.3) with SMTP id GAA98052; Tue, 21 Mar 2000 06:02:20 -0500 (EST) (envelope-from thomas@clark.net) Message-Id: <3.0.6.32.20000321060357.00889550@mail.clark.net> X-Sender: thomas@mail.clark.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Tue, 21 Mar 2000 06:03:57 -0500 To: "Lester A. Mesa" , From: Mark Thomas Subject: Re: *** Error code 1 on make buildworld In-Reply-To: <004601bf8d48$9b0019a0$38040a0a@prontel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Was there a solution found to the problem below? I supped 3/20 about 9 PM EST, and still encounter this error on a build world. At 07:02 PM 3/13/00 -0500, Lester A. Mesa wrote: >I'm currently running a server with 3.2-RELEASE and I'm trying to update my >server to 3.4-STABLE. These are the steps I took to make this upgrade: > >1: I updated the source, cvsup -g -L 2 stable-supfile >2: Drop to single user-mode, shutdown now >3: fsck -p, mout -u /, mount -a -t -ufs and swapon -a >4: I had nothing on the /usr/obj so I left it alone. >5: cd /usr/src and make buildworld > >this are my settings in /etc/make.conf >NOPROFILE= true >COPTFLAGS= -O -pipe >USA_RESIDENT= YES >FORCE_PKG_REGISTER= YES > >for some reason this is how make buildworld is exiting.. Any ideas? > > >===> share/doc/usd/12.vi/viapwh >touch _stamp.extraobjs >(cd >/usr/src/share/doc/usd/12.vi/viapwh/../../../../../contrib/nvi/docs/USD.doc/ >vitut; groff -mtty-char -Tascii -t -ms -o1- / >usr/src/share/doc/usd/12.vi/viapwh/../../../../../contrib/nvi/docs/USD.doc/v >itut/vi.apwh.ms) | gzip -cn > viapwh.ascii.gz >troff: fatal error: can't find macro file safer >===> share/doc/usd/12.vi/summary >touch _stamp.extraobjs >(cd >/usr/src/share/doc/usd/12.vi/summary/../../../../../contrib/nvi/docs/USD.doc >/vitut; groff -mtty-char -Tascii -t -ms -o1- >/usr/src/share/doc/usd/12.vi/summary/../../../../../contrib/nvi/docs/USD.doc >/vitut/vi.summary) | gzip -cn > summary.ascii.gz > >troff: fatal error: can't find macro file safer >===> share/doc/usd/13.viref >sed -e\ 's:\(\.so[\ \ ][\ > ]*\)\(vi.ref\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contrib/nvi/ >docs/USD.doc/vi.ref >/\2:' -e\ 's:\(\.so[\ \ ][\ > ]*\)\(ex.cmd.roff\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contrib >/nvi/docs/USD.doc/v >i.ref/\2:' -e\ 's:\(\.so[\ \ ][\ > ]*\)\(ref.so\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contrib/nvi/ >docs/USD.do >c/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ > ]*\)\(set.opt.roff\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contri >b/nvi/docs/ >USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ > ]*\)\(vi.cmd.roff\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contrib >/nv >i/docs/USD.doc/vi.ref/\2:' -e 's:^\.so index.so$::' >/usr/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.r >ef/vi.ref | groff -mtty-char -Tascii -t -s -me -o1- > /dev/null >troff: fatal error: can't find macro file safer >*** Error code 1 > >Stop. >*** Error code 1 > >Stop. >*** Error code 1 > >Stop. >*** Error code 1 > >Stop. >*** Error code 1 > >Stop. >*** Error code 1 > >Stop. >*** Error code 1 > >Stop. >*** Error code 1 > >Stop. ># exit > > >Thank you all in advanced.. > > >Lester A. Mesa >lmesa@prontel.com >Prontel Corporation >Internet Division >http://www.prontel.com >Toll Free: 1-800-920-0920 Ext 206 >Outside US: 1+ (305) 406-9055 Ext 206 >Fax Number: 1+ (305) 406-9056 >" Prontel Complete Internet Solutions " > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > Mark --- thomas@clark.net ---> http://www.clark.net/pub/thomas PBEM Eldritch --------> http://www.pbegames.com [TM4463-ORG] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 3:48: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 5E1B137B839; Tue, 21 Mar 2000 03:47:56 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id CB7F018055; Tue, 21 Mar 2000 12:47:38 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <20000320153429.A1373@ipass.net> References: <200003191838.KAA40955@rah.star-gate.com> <000701bf91d5$4aebeb60$0304020a@NENYA> <001a01bf91c1$7f62a4b0$0304020a@NENYA> <200003191838.KAA40955@rah.star-gate.com> <20000319220453.A65973@ipass.net> <005d01bf9221$4660ac60$0304020a@NENYA> <20000320153429.A1373@ipass.net> Date: Tue, 21 Mar 2000 10:41:07 +0100 To: Randall Hopper , Cameron Grant From: Brad Knowles Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Cc: Amancio Hasty , Conrad Sabatier , stable@FreeBSD.ORG, multimedia@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 3:34 PM -0500 2000/3/20, Randall Hopper wrote: > From what I hear, it sounds like we need some more testing time too. Yeah, we do. This is what an x.0-RELEASE is all about. The people seriously hacking on -CURRENT are largely done with this chunk of their work, and things have been mostly cleaned up to the point where it's semi-useable. Now, it's time to get this code out to a wider audience, and see what else is missing and needs to be fixed. However, IMO anyone using an x.0-RELEASE on a production box basically gets what they deserve. This is more appropriate for development/test/play boxes, so that you can get a feel for what is coming, and you'll feel comfortable enough with it that by the time x.3-RELEASE comes around, you will feel confident that you can safely put it into production. > Exactly. The kernel revolves around applications. And applications > revolve around users and their needs. True enough. But the guys who've been doing some serious hacking on -CURRENT don't have all the various bits of more unusual hardware and applications that the wider community has, so they can't see these problems, and if they can't see them then they can't fix them. This is *why* they're getting an x.0-RELEASE out now, so that a wider community of people with more unusual hardware and applications *can* see it, and report the bugs back so that these problems can be fixed. > Sorry Fred. That line don't fly with me. I don't have to stand ready with > coding time to fix anything you want to break or rip out. If you want to play with -CURRENT, yes you do. It has been stated many times over that -CURRENT isn't guaranteed to do anything (including compile or run), except have a higher probability of toasting your machine and your application. This is the true bleeding edge, and if you want to play, you have to be prepared to get cut pretty often. If you want to play with x.0-RELEASE, you have to realize that there are some rough spots and some sharp edges that have not yet been detected, or if they have been detected they haven't yet been dealt with. So again, you have to be prepared for the possibility of being cut. If you prefer not to get cut, then you had better stick with the -STABLE tree, which right now means 3.x-STABLE. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 3:48:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 43D7037BB3C; Tue, 21 Mar 2000 03:48:06 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id 4AF78180B3; Tue, 21 Mar 2000 12:47:45 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <20000321162706.B9095@outblaze.com> References: <20000321061951.8726.qmail@yusufg.portal2.com> <20000321031927.A4669@spirit.jaded.net> <20000321162706.B9095@outblaze.com> Date: Tue, 21 Mar 2000 10:50:36 +0100 To: Yusuf Goolamabbas , Dan Moschuk From: Brad Knowles Subject: Re: Reason for sshd[238]: fatal: rsa_private_decrypt() failed 4.0-stable Cc: freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:27 PM +0800 2000/3/21, Yusuf Goolamabbas wrote: > Isn't that illegal (inappropiate) for somebody outside the US ? Yes, I believe so. In fact, if USA_RESIDENT is NO, I would expect this port to bomb out. > On 3-4 stable machines, I used to do make install in > /usr/ports/security/openssh and it used to do the right thing > Shouldn't USA_RESIDENT=NO and make world do this I just installed a fresh 4.0-RELEASE a couple of days ago, and although USA_RESIDENT was set to "NO", and I made a point of grabbing both the sources and the crypto from ftp.uk.freebsd.org, it still seemed to get the RSAREF stuff which choked and puked on keys larger than 1024 bits. In order to fix it, I installed cvsup (like an idiot, I did the port and not the package -- Do you have any idea how long it takes to build XFree86, especially when you don't want X on the machine, and you have no way to specify -NOX on the command line to "make install" for cvsup? ;-). After that, I set up the appropriate cvsup files for RELENG_4, did a make update (which took many hours, since I was still running on a GENERIC kernel and couldn't make use of either SMP or softupdates), then a "make buildworld" and finally a "make installworld". Afterwards, sshd seems to work okay now. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 3:54:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.uned.es (mail.uned.es [193.146.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 0E93837B7BE for ; Tue, 21 Mar 2000 03:53:59 -0800 (PST) (envelope-from vjori@csi.uned.es) Received: from maki (makidos.csi.uned.es [10.194.1.159]) by mail.uned.es (8.9.3/8.9.3) with SMTP id MAA21996 for ; Tue, 21 Mar 2000 12:51:13 +0100 Message-ID: <005001bf932c$1c853800$9f01c20a@maki> From: "Victor Jori" To: Subject: Date: Tue, 21 Mar 2000 12:53:45 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_004D_01BF9334.7E313600" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_004D_01BF9334.7E313600 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable unsubscribe stable ------=_NextPart_000_004D_01BF9334.7E313600 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
unsubscribe stable
------=_NextPart_000_004D_01BF9334.7E313600-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 3:57:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.uned.es (mail.uned.es [193.146.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 90A6C37B632 for ; Tue, 21 Mar 2000 03:57:05 -0800 (PST) (envelope-from vjori@csi.uned.es) Received: from maki (makidos.csi.uned.es [10.194.1.159]) by mail.uned.es (8.9.3/8.9.3) with SMTP id IAA12149; Tue, 21 Mar 2000 08:02:59 +0100 Message-ID: <003801bf9303$e3e23160$9f01c20a@maki> From: "Victor Jori" To: Cc: Subject: Date: Tue, 21 Mar 2000 08:05:50 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0035_01BF930C.458E2F60" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0035_01BF930C.458E2F60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable unsubscribe freebsd-stable ------=_NextPart_000_0035_01BF930C.458E2F60 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
unsubscribe=20 freebsd-stable
------=_NextPart_000_0035_01BF930C.458E2F60-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 4:11: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from student-mailhub.dcu.ie (ns.dcu.ie [136.206.1.3]) by hub.freebsd.org (Postfix) with ESMTP id 2DBA337B6B1 for ; Tue, 21 Mar 2000 04:10:57 -0800 (PST) (envelope-from drjolt@redbrick.dcu.ie) Received: from enigma.redbrick.dcu.ie (postfix@enigma.redbrick.dcu.ie [136.206.15.5]) by student-mailhub.dcu.ie (8.9.3/8.9.3/893-FD) with ESMTP id MAA12994 for ; Tue, 21 Mar 2000 12:10:48 GMT Received: by enigma.redbrick.dcu.ie (Postfix, from userid 2034) id 48BE17C94; Tue, 21 Mar 2000 12:10:48 +0000 (GMT) Date: Tue, 21 Mar 2000 12:10:48 +0000 From: David Murphy To: stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Message-ID: <20000321121048.E49550@enigma.redbrick.dcu.ie> References: <200003191838.KAA40955@rah.star-gate.com> <000701bf91d5$4aebeb60$0304020a@NENYA> <001a01bf91c1$7f62a4b0$0304020a@NENYA> <200003191838.KAA40955@rah.star-gate.com> <20000319220453.A65973@ipass.net> <005d01bf9221$4660ac60$0304020a@NENYA> <20000320153429.A1373@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from blk@skynet.be on Tue, Mar 21, 2000 at 10:41:07AM +0100 X-no-archive: yes Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting by Brad Knowles : > However, IMO anyone using an x.0-RELEASE on a production box > basically gets what they deserve. This is more appropriate for > development/test/play boxes, so that you can get a feel for what is > coming, and you'll feel comfortable enough with it that by the time > x.3-RELEASE comes around, you will feel confident that you can > safely put it into production. The problem is, -RELEASE is pushed out like a new release of a commercial OS, with big announcements, etc. etc., so people expect it to have been subject to a similar level of prerelease beta testing. Clearly this is not and cannot be the case, and IMHO therefore it should not be labeled -RELEASE, but -EARLYACCESS or similar. -- When asked if it is true that he uses his wheelchair as a weapon he will reply: "That's a malicious rumour. I'll run over anyone who repeats it." Stephen Hawking - [http://www.smh.com.au/news/0001/07/features/features1.html] David Murphy - For PGP public key, send mail with Subject: send-pgp-key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 4:34:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.13.27]) by hub.freebsd.org (Postfix) with ESMTP id EBE0C37B630 for ; Tue, 21 Mar 2000 04:34:07 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id MAA00476; Tue, 21 Mar 2000 12:38:49 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000321121048.E49550@enigma.redbrick.dcu.ie> Date: Tue, 21 Mar 2000 12:38:49 -0000 (GMT) From: "Steve O'Hara-Smith" To: David Murphy Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for imp Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Simple question which of 3.x, 4.x and 5.x is Voxware toast in ? IMHO, 5.x is a good place to toast it 4.x is a good place to keep it as long as possible 3.x is a place where it should be kept (POLA) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 4:52:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 96FC537B515 for ; Tue, 21 Mar 2000 04:52:44 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id 8DDCDD98F; Tue, 21 Mar 2000 13:52:37 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <20000321121048.E49550@enigma.redbrick.dcu.ie> References: <200003191838.KAA40955@rah.star-gate.com> <000701bf91d5$4aebeb60$0304020a@NENYA> <001a01bf91c1$7f62a4b0$0304020a@NENYA> <200003191838.KAA40955@rah.star-gate.com> <20000319220453.A65973@ipass.net> <005d01bf9221$4660ac60$0304020a@NENYA> <20000320153429.A1373@ipass.net> <20000321121048.E49550@enigma.redbrick.dcu.ie> Date: Tue, 21 Mar 2000 13:38:47 +0100 To: David Murphy , stable@FreeBSD.ORG From: Brad Knowles Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:10 PM +0000 2000/3/21, David Murphy wrote: > The problem is, -RELEASE is pushed out like a new release of a > commercial OS, with big announcements, etc. etc., so people expect it > to have been subject to a similar level of prerelease beta testing. It has gotten *way* more testing than any Microsoft x.0 release, but it's still not ready for prime-time. The difference is that Microsoft will tell you to switch everything over ASAP (since it "fixes" all those old bugs you've been having to live with), and then they'll take in *huge* amounts of money as you pay to upgrade all your other software, and as they get more licenses shipped because you have to buy all new hardware to run all their new bloatware that runs on their new 63,000+ bug-ridden OS. > Clearly this is not and cannot be the case, and IMHO therefore it > should not be labeled -RELEASE, but -EARLYACCESS or similar. This has been debated before. The problem is that so long as it is called -BETA, -EARLYACCESS, or whatever, people will stay away from it in droves, and we'll never run across most of the problems that remain to be debugged. At some point, you *MUST* declare that this has gone on long enough, and that it is time to cut a -RELEASE version. At which point, everybody and their brother jumps on it and stupidly tries to install it on all their production systems. I think the folks who bring you FreeBSD are being much more intelligent about this -- they name it -RELEASE, they encourage you to take a look at it on non-production hardware, but they *DISCOURAGE* you from running it on production hardware, because there haven't been enough people testing it yet. What is so hard to understand about that? -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 5: 5:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 2F74137B707 for ; Tue, 21 Mar 2000 05:05:40 -0800 (PST) (envelope-from mmercer@ipass.net) Received: from ipass.net (dsl-2-196.dsl.rdu.ipass.net [209.170.144.196] (may be forged)) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id IAA28949; Tue, 21 Mar 2000 08:05:35 -0500 (EST) Message-ID: <38D773A0.27B46245@ipass.net> Date: Tue, 21 Mar 2000 08:05:37 -0500 From: "Michael E. Mercer" Reply-To: mmercer@ipass.net, mmercer@nortelnetworks.com X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Sean O'Connell" , freebsd-stable@freebsd.org Subject: Re: ep0 eeprom failed to come ready... References: <38D6F515.D0536435@ipass.net> <20000320234144.B9150@stat.Duke.EDU> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, this did not work either... the pnp stuff is complaining it can not assign resources... eeprom failed to come ready -> still on the ep0 device... finds it again with ep1 except this time it is using irq 11 which irq 11 was already assigned to a PCI device (video card) nothing else from what I saw was using irq 10.... I booted with -c , went to visual, and NOTHING was in the NETWORK selection... I could not find ep0 or ep1 in any selection... I can not send my kernel config, since I have no connection and I do not feel like retyping it here... any other suggestions please? later Michael Mercer mmercer@ipass.net Sean O'Connell wrote: > Michael E. Mercer stated: > > hello, > > > > I have a 3com 3C509-TPO Etherlink III card... > > I have just upgraded my pentium 200 MMX machine to 4.0-Stable. > > Everything seems to be going well except that it fails with > > ep0: <3Com 3C509-TPO Etherlink III> at port 0x300-0x30f irq 10 on isa0 > > ep0: eeprom failed to come ready. > > last line repeated 4 more times... > > > > then later during the boot process it finds the same card on a different port > > and everything is fine... except now I can not get to the outside world... > > > > ep0: <3Com 3C509-TPO Etherlink III> at port 0x210-0x21f irq 10 on isa0 > > > > What is the problem here.... normally with me it is user error so let me know... > > > > Thanks > Michael Mercer- > > What do have in your kernel config? Try adding > > options PNPBIOS > device ep > > Also, make sure that nothing else is using irq 10 on your box. Was > it using these settings in its previous incarnation? > > ----------------------------------------------------------------------- > Sean O'Connell Email: sean@stat.Duke.EDU > Institute of Statistics and Decision Sciences Phone: (919) 684-5419 > Duke University Fax: (919) 684-8594 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 5:39: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from interslcr.kada.lt (mail.kada.lt [195.22.170.131]) by hub.freebsd.org (Postfix) with ESMTP id AED3A37B6B1 for ; Tue, 21 Mar 2000 05:38:57 -0800 (PST) (envelope-from dara@kada.lt) Received: from intrantk.kada.lan (mail.kada.lan [10.254.254.2]) by interslcr.kada.lt with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id G0BVRXMH; Tue, 21 Mar 2000 15:38:52 +0200 Received: from dara.kada.lan (darau.kada.lan [10.254.254.40]) by intrantk.kada.lan with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id G8LYVAZ7; Tue, 21 Mar 2000 15:38:51 +0200 From: Darius Ramanauskas Date: Tue, 21 Mar 2000 13:38:59 GMT Message-ID: <20000321.13385900@dara.kada.lan> Subject: newpcm and CS423X To: freebsd-stable@freebsd.org X-Mailer: Mozilla/3.0 (compatible; StarOffice/5.1; Linux) X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------=_4D4800EAC52C08436D30" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --------------=_4D4800EAC52C08436D30 Content-Description: filename="text1.txt" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi All, I just upgraded my system from 3.4-STABLE to 4.0-STABLE=20 and have some questions related to newpcm driver. Then kernel starts it reports this: pcm0: at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0= =20 on isa0 unknown0: at port 0x3a0-0x3a7 on isa0 unknown1: at port 0xf00-0xf07 on isa0 unknown2: at port 0x330-0x331 on isa0 So what this "unknownX" is ? I feel that something is missing in my kernel config or in /dev but I could not find what :(( In kernel config contains just this: device pcm from sndstat: dara:/home/dara> cat /dev/sndstat FreeBSD Audio Driver (newpcm) Mar 21 2000 13:56:43 Installed devices: pcm0: at io 0x534 irq 5 drq 1:0 (1p/1r channels duplex)=20 Thank You, Darius PS If it easy, please don't beat me, just point to right answer .... --------------=_4D4800EAC52C08436D30 Content-Description: filename="text1.rtf" Content-Type: application/rtf Content-Transfer-Encoding: base64 e1xydGYxXGFuc2lcZGVmZjAKe1xmb250dGJse1xmMFxmcm9tYW5cZnBycTIgdGltZXM7fXtc ZjFcZnJvbWFuXGZwcnEyXGZjaGFyc2V0MCBUaW1lcyBOZXcgUm9tYW47fXtcZjJcZnJvbWFu XGZwcnExIGNvdXJpZXI7fX0Ke1xjb2xvcnRibFxyZWQwXGdyZWVuMFxibHVlMDtccmVkMFxn cmVlbjBcYmx1ZTEyODtccmVkMTI4XGdyZWVuMFxibHVlMDtccmVkMjU1XGdyZWVuMjU1XGJs dWUyNTU7XHJlZDEyOFxncmVlbjEyOFxibHVlMTI4O30Ke1xzdHlsZXNoZWV0e1xzMVxzbmV4 dDEgU3RhbmRhcmQ7fQp7XHMye1wqXHRsc3dnODIzNn1cdHFjXHR4NDgxOXtcKlx0bHN3Zzgy MzZ9XHRxclx0eDk2Mzlcc2Jhc2Vkb24xXHNuZXh0MiBGb290ZXI7fQp7XHMze1wqXHRsc3dn ODIzNn1cdHFjXHR4NDgxOXtcKlx0bHN3ZzgyMzZ9XHRxclx0eDk2Mzlcc2Jhc2Vkb24xXHNu ZXh0MyBIZWFkZXI7fQp7XHM0XHNiMjQwXHNhMjgzXGtlZXBuXGYxXGZzNDhcYlxzYmFzZWRv bjE1XHNuZXh0MTR7XCpcc291dGx2bDB9IEhlYWRpbmcgMTt9CntcczVcc2EyODNcYnJkcmJc YnJkcmRiXGJyZHJ3MTVcYnJkcmNmNFxicnNwMHtcKlxicmRib3gwXGJyZHJiXGJyZGxuY29s NFxicmRsbmluMVxicmRsbm91dDFcYnJkbG5kaXN0MjB9XGZzMTJcc2Jhc2Vkb24xXHNuZXh0 MTQgSG9yaXpvbnRhbCBMaW5lO30Ke1xzNlxzYTI4M1xiXHFjXHNiYXNlZG9uN1xzbmV4dDYg VGFibGUgSGVhZGluZzt9Cntcczdcc2EyODNcc2Jhc2Vkb24xNFxzbmV4dDcgVGFibGUgQ29u dGVudHM7fQp7XHM4XGlcc2Jhc2Vkb24xXHNuZXh0OCBTZW5kZXI7fQp7XHM5XHNiMjQwXHNh MjgzXGtlZXBuXGYxXGZzMzZcYlxzYmFzZWRvbjE1XHNuZXh0MTR7XCpcc291dGx2bDF9IEhl YWRpbmcgMjt9CntcczEwXHNiMjQwXHNhMjgzXGtlZXBuXGYxXGZzMjhcYlxzYmFzZWRvbjE1 XHNuZXh0MTR7XCpcc291dGx2bDJ9IEhlYWRpbmcgMzt9CntcczExXHNiMjQwXHNhMjgzXGtl ZXBuXGYxXGJcc2Jhc2Vkb24xNVxzbmV4dDE0e1wqXHNvdXRsdmwzfSBIZWFkaW5nIDQ7fQp7 XHMxMlxzYjI0MFxzYTI4M1xrZWVwblxmMVxmczIwXGJcc2Jhc2Vkb24xNVxzbmV4dDE0e1wq XHNvdXRsdmw0fSBIZWFkaW5nIDU7fQp7XHMxM1xzYjI0MFxzYTI4M1xrZWVwblxmMVxmczE0 XGJcc2Jhc2Vkb24xNVxzbmV4dDE0IEhlYWRpbmcgNjt9CntcczE0XHNhMjgzXHNiYXNlZG9u MVxzbmV4dDE0IFRleHQgYm9keTt9CntcczE1XHNiMjQwXHNhMjgzXGtlZXBuXGYxXGZzMjhc c2Jhc2Vkb24xXHNuZXh0MTQgSGVhZGluZzt9CntcczE2XGYyXGZzMjBcc2Jhc2Vkb24xXHNu ZXh0MTYgUHJlZm9ybWF0dGVkIFRleHQ7fQp7XHMxN1xsaTU2NlxyaTBcZmkwXHNiYXNlZG9u MVxzbmV4dDE3IExpc3QgQ29udGVudHM7fQp7XCpcY3MxOSBGb290bm90ZSBTeW1ib2w7fQp7 XCpcY3MyMFxjZjFcdWwgSW50ZXJuZXQgbGluazt9CntcKlxjczIxXGNmMlx1bCBWaXNpdGVk IEludGVybmV0IExpbms7fQp7XCpcY3MyMiBFbmRub3RlIFN5bWJvbDt9Cn0Ke1xpbmZve1xj cmVhdGltXHlyMjAwMFxtbzNcZHkyMVxocjE1XG1pbjMwfXtcb3BlcmF0b3IgRGFyaXVzIFJh bWFuYXVza2FzfXtccmV2dGltXHlyMjAwMFxtbzNcZHkyMVxocjE1XG1pbjM4fXtccHJpbnRp bVx5cjE2MDFcbW8xXGR5MVxocjBcbWluMH17XGNvbW1lbnQgU3RhcldyaXRlcn17XHZlcm41 MTcwfX1cZGVmdGFiNzIwCntcKlxwZ2RzY3RibAp7XHBnZHNjMFxwZ2RzY3VzZTE5NVxwZ3dz eG4xMTkwNVxwZ2hzeG4xNjgzN1xtYXJnbHN4bjExMzRcbWFyZ3JzeG4xMTM0XG1hcmd0c3hu MTEzNFxtYXJnYnN4bjExMzRccGdkc2NueHQwIFN0YW5kYXJkO30Ke1xwZ2RzYzFccGdkc2N1 c2UxOTVccGd3c3huMTE5MDVccGdoc3huMTY4MzdcbWFyZ2xzeG4xMTM0XG1hcmdyc3huNTY3 XG1hcmd0c3huNTY3XG1hcmdic3huNTY3XGhlYWRlcnkwe1wqXGhlYWRlcnliMjgzXGhlYWRl cnhsMFxoZWFkZXJ4cjB9e1xoZWFkZXIgXHRyb3dkXHRycWxcdHJoZHJcY2VsbHg5Mjg1XGNl bGx4MTA5MDMKXHBhcmRcaW50YmxccGFyZFxwbGFpbiBcaW50YmxcczdcbWFyZ3RzeG4wXG1h cmdic3huMjgzXGZzMjAgVGl0bGU6IApcY2VsbFxwYXJkXHBsYWluIFxpbnRibFxzN1xtYXJn dHN4bjBcbWFyZ2JzeG4yODNcZnMyMFxxciBEYXRlOiAzLzIxLzAwClxjZWxsXHJvd1xwYXJk IFx0cm93ZFx0cnFsXGNlbGx4OTI4NVxjZWxseDEwOTAzClxwYXJkXGludGJsXHBhcmRccGxh aW4gXGludGJsXHM3XG1hcmd0c3huMFxtYXJnYnN4bjI4M1xmczIwIFVSTDoge1xmaWVsZHtc KlxmbGRpbnN0IFxcZmlsZW5hbWUgfXtcZmxkcnNsdCAvdG1wL3NvZmZpY2UudG1wL3N2NTE0 Ni50bXAvc2RtYWk1MTQ5LnRtcC9tYWlsNTE1MC5odG19fQpcY2VsbFxwYXJkXHBsYWluIFxp bnRibFxzN1xtYXJndHN4bjBcbWFyZ2JzeG4yODNcZnMyMFxxciBUaW1lOiAxNTozMDo0Mgpc Y2VsbFxyb3dccGFyZCBccGFyZFxwbGFpbiBcczEgClxwYXIgfQpcZm9vdGVyeTB7XCpcZm9v dGVyeXQyODNcZm9vdGVyeGwwXGZvb3RlcnhyMH17XGZvb3RlciBccGFyZFxwbGFpbiBcczFc ZnMyMFxxYyBQYWdlIHtcZmllbGR7XCpcZmxkaW5zdCBcXHBhZ2V9e1xmbGRyc2x0IH19IG9m IDEKXHBhciB9ClxwZ2RzY254dDEgSFRNTDt9fQpccGFwZXJoMTY4MzdccGFwZXJ3MTE5MDVc bWFyZ2wxMTM0XG1hcmdyNTY3XG1hcmd0NTY3XG1hcmdiNTY3XHNlY3RkXHNia25vbmVccGd3 c3huMTE5MDVccGdoc3huMTY4MzdcbWFyZ2xzeG4xMTM0XG1hcmdyc3huNTY3XG1hcmd0c3hu MTEzM1xtYXJnYnN4bjExMzNcaGVhZGVyeTU2N3tcaGVhZGVyIFx0cm93ZFx0cnFsXHRyaGRy XGNlbGx4OTI4NVxjZWxseDEwOTAzClxwYXJkXGludGJsXHBhcmRccGxhaW4gXGludGJsXHM3 XG1hcmd0c3huNTY2XG1hcmdic3huODQ5XGZzMjAgVGl0bGU6IApcY2VsbFxwYXJkXHBsYWlu IFxpbnRibFxzN1xtYXJndHN4bjU2NlxtYXJnYnN4bjg0OVxmczIwXHFyIERhdGU6IDMvMjEv MDAKXGNlbGxccm93XHBhcmQgXHRyb3dkXHRycWxcY2VsbHg5Mjg1XGNlbGx4MTA5MDMKXHBh cmRcaW50YmxccGFyZFxwbGFpbiBcaW50YmxcczdcbWFyZ3RzeG41NjZcbWFyZ2JzeG44NDlc ZnMyMCBVUkw6IHtcZmllbGR7XCpcZmxkaW5zdCBcXGZpbGVuYW1lIH17XGZsZHJzbHQgL3Rt cC9zb2ZmaWNlLnRtcC9zdjUxNDYudG1wL3NkbWFpNTE0OS50bXAvbWFpbDUxNTAuaHRtfX0K XGNlbGxccGFyZFxwbGFpbiBcaW50YmxcczdcbWFyZ3RzeG41NjZcbWFyZ2JzeG44NDlcZnMy MFxxciBUaW1lOiAxNTozMDo0MgpcY2VsbFxyb3dccGFyZCBccGFyZFxwbGFpbiBcczEgClxw YXIgfQpcZm9vdGVyeTU2N3tcZm9vdGVyIFxwYXJkXHBsYWluIFxzMVxmczIwXHFjIFBhZ2Ug e1xmaWVsZHtcKlxmbGRpbnN0IFxccGFnZX17XGZsZHJzbHQgfX0gb2YgMQpccGFyIH0KXGZ0 bmJqXGZ0bnN0YXJ0MVxmdG5yc3Rjb250XGZ0bm5hclxhZW5kZG9jXGFmdG5yc3Rjb250XGFm dG5zdGFydDFcYWZ0bm5ybGMKXHBhcmRccGxhaW4gXHMxNlxmMlxmczIwIEhpIEFsbCwKXHBh ciBccGFyZFxwbGFpbiBcczE2XGYyXGZzMjAgClxwYXIgSSBqdXN0IHVwZ3JhZGVkIG15IHN5 c3RlbSBmcm9tIDMuNC1TVEFCTEUgdG8gNC4wLVNUQUJMRSAKXHBhciBhbmQgaGF2ZSBzb21l IHF1ZXN0aW9ucyByZWxhdGVkIHRvIG5ld3BjbSBkcml2ZXIuClxwYXIgXHBhcmRccGxhaW4g XHMxNlxmMlxmczIwXGJyZHJiXGJyZHJzXGJyZHJ3MVxicmRyY2YwXGJyc3A0MntcKlxicmRi b3g0MlxicmRyYlxicmRsbmNvbDBcYnJkbG5pbjBcYnJkbG5vdXQxXGJyZGxuZGlzdDB9VGhl biBrZXJuZWwgc3RhcnRzIGl0IHJlcG9ydHMgdGhpczoKXHBhciBccGFyZFxwbGFpbiBcczE2 XGYyXGZzMjAgcGNtMDogPENTNDIzeD4gYXQgcG9ydCAweDUzNC0weDUzNywweDM4OC0weDM4 YiwweDIyMC0weDIyZiBpcnEgNSBkcnEgMSwwIG9uIGlzYTAKXHBhciB1bmtub3duMDogPEdh bWU+IGF0IHBvcnQgMHgzYTAtMHgzYTcgb24gaXNhMApccGFyIHVua25vd24xOiA8Q3RybD4g YXQgcG9ydCAweGYwMC0weGYwNyBvbiBpc2EwClxwYXIgXHBhcmRccGxhaW4gXHMxNlxmMlxm czIwXGJyZHJiXGJyZHJzXGJyZHJ3MVxicmRyY2YwXGJyc3A0MntcKlxicmRib3g0MlxicmRy YlxicmRsbmNvbDBcYnJkbG5pbjBcYnJkbG5vdXQxXGJyZGxuZGlzdDB9dW5rbm93bjI6IDxN UFU+IGF0IHBvcnQgMHgzMzAtMHgzMzEgb24gaXNhMApccGFyIFxwYXJkXHBsYWluIFxzMTZc ZjJcZnMyMCAKXHBhciBTbyB3aGF0IHRoaXMgInVua25vd25YIiBpcyA/IEkgZmVlbCB0aGF0 IHNvbWV0aGluZyBpcyBtaXNzaW5nClxwYXIgaW4gbXkga2VybmVsIGNvbmZpZyBvciBpbiAv ZGV2IGJ1dCBJIGNvdWxkIG5vdCBmaW5kIHdoYXQgOigoClxwYXIgSW4ga2VybmVsIGNvbmZp ZyBjb250YWlucyBqdXN0IHRoaXM6ClxwYXIgClxwYXIgZGV2aWNlXHRhYiBcdGFiIHBjbQpc cGFyIApccGFyIGZyb20gc25kc3RhdDoKXHBhciBkYXJhOi9ob21lL2RhcmE+IGNhdCAvZGV2 L3NuZHN0YXQKXHBhciBGcmVlQlNEIEF1ZGlvIERyaXZlciAobmV3cGNtKSBNYXIgMjEgMjAw MCAxMzo1Njo0MwpccGFyIEluc3RhbGxlZCBkZXZpY2VzOgpccGFyIHBjbTA6IDxDUzQyM3g+ IGF0IGlvIDB4NTM0IGlycSA1IGRycSAxOjAgKDFwLzFyIGNoYW5uZWxzIGR1cGxleCkgClxw YXIgClxwYXIgVGhhbmsgWW91LApccGFyIApccGFyIERhcml1cwpccGFyIApccGFyIFBTIElm IGl0IGVhc3ksIHBsZWFzZSBkb24ndCBiZWF0IG1lLCBqdXN0IHBvaW50IHRvIHJpZ2h0IGFu c3dlciAuLi4uClxwYXIgfW== --------------=_4D4800EAC52C08436D30-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 6:11:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from student-mailhub.dcu.ie (ns.dcu.ie [136.206.1.3]) by hub.freebsd.org (Postfix) with ESMTP id F2C8B37B909 for ; Tue, 21 Mar 2000 06:10:59 -0800 (PST) (envelope-from drjolt@redbrick.dcu.ie) Received: from enigma.redbrick.dcu.ie (postfix@enigma.redbrick.dcu.ie [136.206.15.5]) by student-mailhub.dcu.ie (8.9.3/8.9.3/893-FD) with ESMTP id OAA21035 for ; Tue, 21 Mar 2000 14:10:56 GMT Received: by enigma.redbrick.dcu.ie (Postfix, from userid 2034) id 364BD7C94; Tue, 21 Mar 2000 14:10:55 +0000 (GMT) Date: Tue, 21 Mar 2000 14:10:55 +0000 From: David Murphy To: stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Message-ID: <20000321141055.E5367@enigma.redbrick.dcu.ie> References: <200003191838.KAA40955@rah.star-gate.com> <000701bf91d5$4aebeb60$0304020a@NENYA> <001a01bf91c1$7f62a4b0$0304020a@NENYA> <200003191838.KAA40955@rah.star-gate.com> <20000319220453.A65973@ipass.net> <005d01bf9221$4660ac60$0304020a@NENYA> <20000320153429.A1373@ipass.net> <20000321121048.E49550@enigma.redbrick.dcu.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from blk@skynet.be on Tue, Mar 21, 2000 at 01:38:47PM +0100 X-no-archive: yes Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting by Brad Knowles : > > The problem is, -RELEASE is pushed out like a new release of a > > commercial OS, with big announcements, etc. etc., so people expect it > > to have been subject to a similar level of prerelease beta testing. > The difference is that Microsoft will tell you to switch > everything over ASAP (since it "fixes" all those old bugs you've been > having to live with), and then they'll take in *huge* amounts of > money as you pay to upgrade all your other software, and as they get > more licenses shipped because you have to buy all new hardware to run > all their new bloatware that runs on their new 63,000+ bug-ridden OS. Actually, I was thinking more along the lines of commercial unix OSes, Sun for example, and I use this example because I'm familiar with them, put out an Early Access version of Solaris 8 some months before formally releasing Solaris 8. Effectively, this is the same timescale FreeBSD is going to run on, but the early access version is labelled -RELEASE. > This has been debated before. The problem is that so long as it > is called -BETA, -EARLYACCESS, or whatever, people will stay away > from it in droves, and we'll never run across most of the problems > that remain to be debugged. As opposed to what? People staying away from x.0-RELEASE in droves, because they find out it's a beta, AFTER they've been confused by the naming policy? > I think the folks who bring you FreeBSD are being much more > intelligent about this -- they name it -RELEASE, they encourage you > to take a look at it on non-production hardware, but they > *DISCOURAGE* you from running it on production hardware, because > there haven't been enough people testing it yet. > What is so hard to understand about that? The fact that the above statement does not appear in the release announcement[1], or the release notes[2]. How is a new FreeBSD user supposed to discover the weird and wonderful naming policy in use by the FreeBSD project? [1] http://www.FreeBSD.org/releases/4.0R/announce.html [2] http://www.FreeBSD.org/releases/4.0R/notes.html -- When asked if it is true that he uses his wheelchair as a weapon he will reply: "That's a malicious rumour. I'll run over anyone who repeats it." Stephen Hawking - [http://www.smh.com.au/news/0001/07/features/features1.html] David Murphy - For PGP public key, send mail with Subject: send-pgp-key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 7: 4: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from primex.prontel.net (primex.prontel.net [216.242.25.10]) by hub.freebsd.org (Postfix) with ESMTP id 9E54B37B8BA for ; Tue, 21 Mar 2000 07:04:03 -0800 (PST) (envelope-from netadmin@primex.prontel.net) Received: from sysop1 (matrix.prontel.net [216.242.25.4]) by primex.prontel.net (8.9.3/8.9.3) with SMTP id KAA13393; Tue, 21 Mar 2000 10:04:06 -0500 (EST) (envelope-from netadmin@primex.prontel.net) From: "Lester A. Mesa" To: "'Dave Runkle'" Cc: , "'Mark Thomas'" Subject: RE: Desperate help upgrading from 3.2-R > 3.4-S Date: Tue, 21 Mar 2000 15:03:59 -0500 Message-ID: <001c01bf9370$991b8100$38040a0a@prontel.com> 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.00.2919.6600 In-Reply-To: Importance: Normal Disposition-Notification-To: "Lester A. Mesa" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes I sure did found a way.. Try this steps to upgrade from 3.2-RELEASE to 3.4-STABLE 1: move the /usr/src (mv /usr/src /usr/src.old) 2: clear the /usr/obj (cd /usr/obj ; rm -rf *) 3: do a fresh cvsup (cvsup -g -L 2 stable-supfile) 4: manually make groff (cd /usr/src/gnu/usr.bin/groff ; make install) 5: make buildworld (cd /usr/src ; make buildworld) 6: make install (make installworld) and just do the rest update /etc /dev and kernel This should work without a problem.. Let me know if it works ok? -----Original Message----- From: Dave Runkle [mailto:drunkle@home.com] Sent: Monday, March 20, 2000 9:53 PM To: Lester A. Mesa Subject: Re: Desperate help upgrading from 3.2-R > 3.4-S Hello, did you ever get built/installed? I'm stopped at exactly the same point... I did some looking at the repository at the BSD site and can't find some of the directories that are stopping it. I'd sure be interested if you have a solution. I'll probably write the stable mailing list soon if I can't figure it out. I am doing exactly like you did, can't make ports, system too old, need to to 3.4-STABLE to build ports. I'd like to get to -STABLE or -CURRENT or anything beyond 3.2. Yesterday I did a fresh /stand/sysinstall from the 3.2 cd, installed src and ports, then cvsup the STABLE. I can't get out of buildworld Thanks, Dave On Fri, 17 Mar 2000, Lester A. Mesa wrote: > For the last week I have been trying to upgrade 2 already configure and > running 3.2-RELEASE servers to 3.4-STABLE since when I try to install > something from the ports I get the following error: > ===> apache-1.3.12 : Your system is too old to use this bsd.port.mk. You > need a fresh make world or an upgrade kit. Please go to > http://www.FreeBSD.org/ports/ or a mirror site and follow the instructions. > > I already try cvsuping the ports-supfile and that did not work. That's why > I'm trying to go with 3.4-STABLE or the most stable freebsd version. > > I'm following all the directions on the > http://www.freebsd.org/handbook/stable.html web page and everything on the > http://www.freebsd.org/handbook/makeworld.html This are exactly the steps > I'm taking to upgrade the machine (in case I'm misunderstanding something > after reading the instruction. > > 1): cd /usr/share/examples/cvsup ; cvsup -g -L 2 stable-supfile > (stable-supfile file) > *default host=cvsup5.FreeBSD.org > *default base=/usr > *default prefix=/usr > *default release=cvs tag=RELENG_3 > *default delete use-rel-suffix > src-all > src-crypto > src-eBones > src-secure > > 2): cd /usr/obj ; chflags -R noschg * ; rm -rf * > > 3): cd /usr/src ; make buildworld > (/etc/make.conf file) > NOPROFILE= true > COPTFLAGS= -O -pipe > USA_RESIDENT= YES > FORCE_PKG_REGISTER= YES > > and while running the make buildworld is where I get the following error: > > ===> share/doc/usd/13.viref > sed -e\ 's:\(\.so[\ \ ][\ > ]*\)\(vi.ref\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contrib/nv i/ > docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ > ]*\)\(ex.cmd.roff\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contr ib > /nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ > ]*\)\(ref.so\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contrib/nv i/ > docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ > ]*\)\(set.opt.roff\)$:\1/usr/src/share/doc/usd/13.viref/../../../../cont ri > b/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ > ]*\)\(vi.cmd.roff\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contr ib > /nvi/docs/USD.doc/vi.ref/\2:' -e 's:^\.so index.so$::' > /usr/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/ > vi.ref | groff -mtty-char -Tascii -t -s -me -o1- > /dev/null > troff: fatal error: can't find macro file safer > *** Error code 1 > > Stop. > > ANY body knows why? or what do I have to do to make this work? > > I did notice that the " troff: fatal error: can't find macro file safer " > error started here: > > ===> share/doc/psd/title > touch _stamp.extraobjs > (cd /usr/src/share/doc/psd/title; groff -mtty-char -Tascii -ms -o1- > /usr/src/share/doc/psd/title/Title) | gzip -cn > Title.ascii.gz > troff: fatal error: can't find macro file safer > > PLEASE if any can give me any input on the problem I will appreciate it so > much, I need to get this 2 servers up and running ASAP. > > Thank you all in advanced for the input. > > > > > > > Lester A. Mesa > Internet Information Manager > lmesa@prontel.com > Prontel Corporation > Internet Division > http://www.prontel.com > Toll Free: 1-800-920-0920 Ext 206 > Outside US: 1+ (305) 406-9055 Ext 206 > Fax Number: 1+ (305) 406-9056 > " Prontel Complete Internet Solutions " > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 7:16:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ckmso1.proxy.att.com (ckmso1.att.com [12.20.58.69]) by hub.freebsd.org (Postfix) with ESMTP id 59FAD37B6F0 for ; Tue, 21 Mar 2000 07:16:26 -0800 (PST) (envelope-from jwb@homer.att.com) Received: from ulysses.homer.att.com ([135.205.193.4]) by ckmso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id KAA07489 for ; Tue, 21 Mar 2000 10:15:55 -0500 (EST) Received: from akiva.homer.att.com (akiva.homer.att.com [135.205.198.103]) by ulysses.homer.att.com (8.9.3/8.9.3) with ESMTP id KAA16740 for ; Tue, 21 Mar 2000 10:15:55 -0500 (EST) Received: from akiva.homer.att.com (localhost [127.0.0.1]) by akiva.homer.att.com (8.8.8+Sun/8.8.8) with ESMTP id KAA08957 for ; Tue, 21 Mar 2000 10:15:54 -0500 (EST) Message-Id: <200003211515.KAA08957@akiva.homer.att.com> X-Mailer: exmh version 2.0.3 3/22/1999 To: freebsd-stable@freebsd.org Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions Date: Tue, 21 Mar 2000 10:15:54 -0500 From: "J. W. Ballantine" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: >Let me know if the following doesn't work: > To update from 3.x to 4.0 stable > -------------------------------- > cd /usr/src > make buildworld > cd sbin/mknod > make install > > [*] > reboot > > cd /usr/src > make -DNOINFO installworld > make installworld > > [*] You may need to switch from wd to ad ala 19991210 > > To build a kernel > ----------------- > Update config, genassym and go: > cd src/usr.bin/genassym > make depend all install > cd ../../usr.sbin/config > make depend all install > > To rebuild disk /dev entries > ---------------------------- > > MAKEDEV should be copied from src/etc/MAKEDEV to /dev before > starting the following: > > For N in the list of disks > MAKEDEV N # eg ad0 > for M in the list of slices > MAKEDEV NsMa # eg ad0s1a > > Ok, I cvs'ed the releng_4, edited /etc/make.conf for ``USA_RESIDENT'', then did a ``make buildworld''. When that ended, did the make install in sbin/mknod, genassym and config, and then tried to build GENERIC kernel, set LD_LIBRARY_PATH to point to the uninstalled libc.so.4, the then built and install GENERIC kernel. So far so good, since my disks are da9x9x, is skipped the disk rebuild step, and rebooted in single user mode, and did a ``make -DNOINFO installworld''. during this set, the kernel crashed in the bin/test install. When I try to reboot, I get the message that / was not dismounted cleanly and to fsck the disk. I go to single user mode and did a full fsck, a fsck -p and an fsck /dev/wd0s1 (/ mount point), and just for the heck of it a few sync's after the fsck's. Since I installed the R4 kernel, that is the one booting, when I try to boot with kernel.old (3.x-STABLE), it will not boot. Anyone have any ideas on (a) why the NOINFO install failed, (b) other than reload the 3.4-RELEASE binaries get back to a fixable system??? Thanks for any and all responses Jim Ballantine Selected portions of log file: # cd /usr/src # make buildworld -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- rm -rf /usr/obj/usr/src/i386 mkdir -p /usr/obj/usr/src/i386/usr/bin mkdir -p /usr/obj/usr/src/i386/usr/lib/compat/aout mkdir -p /usr/obj/usr/src/i386/usr/games mkdir -p /usr/obj/usr/src/i386/usr/libdata/ldscripts mkdir -p /usr/obj/usr/src/i386/usr/libexec/elf mkdir -p /usr/obj/usr/src/i386/usr/sbin mkdir -p /usr/obj/usr/src/i386/usr/share/misc mkdir -p /usr/obj/usr/src/i386/usr/include/arpa mkdir -p /usr/obj/usr/src/i386/usr/include/g++/std mkdir -p /usr/obj/usr/src/i386/usr/include/objc mkdir -p /usr/obj/usr/src/i386/usr/include/protocols mkdir -p /usr/obj/usr/src/i386/usr/include/readline mkdir -p /usr/obj/usr/src/i386/usr/include/rpc mkdir -p /usr/obj/usr/src/i386/usr/include/rpcsvc mkdir -p /usr/obj/usr/src/i386/usr/include/openssl mkdir -p /usr/obj/usr/src/i386/usr/include/security mkdir -p /usr/obj/usr/src/i386/usr/include/ss ln -sf /usr/src/sys /usr/obj/usr/src/i386/sys -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- Remainder of build to end deleted...... ===> etc ===> etc/sendmail rm -f freebsd.cf (cd /usr/src/etc/sendmail && m4 -D_CF_DIR_=/usr/src/etc/sendmail/../../contrib /sendmail/cf/ /usr/src/etc/sendmail/../../contrib/sendmail/cf/m4/cf.m4 freebsd.mc) > freebsd.cf chmod 444 freebsd.cf you have mail in /var/mail/root # cd sbin/mknod # make install install -c -s -o root -g wheel -m 555 mknod /sbin install -c -o root -g wheel -m 444 mknod.8.gz /usr/share/man/man8 # cd ls Makefile mknod.8 mknod.c # cd /usr/src/usr.bin/genassym # make depend all install install -c -s -o root -g wheel -m 555 genassym /usr/bin install -c -o root -g wheel -m 444 genassym.8.gz /usr/share/man/man8 # cd ../../usr/sbin .sbin/config # make depend all install install -c -s -o root -g wheel -m 555 config /usr/sbin install -c -o root -g wheel -m 444 config.8.gz /usr/share/man/man8 # cd ../../sys/i386/conf # config GENERIG /usr/libexec/ld-elf.so.1: Shared object "libc.so.4" not found Restart after setting LD_LIBRARY_PATH # cd /usr/src/sys/i386/conf # config GENERIC Don't forget to do a ``make depend'' Kernel build directory is ../../compile/GENERIC # cd ../../compile/GENERIC # make depend && make cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf ../../i386/i386/genassym.c genassym genassym.o >assym.s Kernel srcs compiles deleted cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf vers.c linking kernel text data bss dec hex filename 2174751 142284 123136 2440171 253beb kernel # make install chflags noschg /kernel mv /kernel /kernel.old install -c -m 555 -o root -g wheel -fschg kernel /kernel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 8:22: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 2ADEA37B63E for ; Tue, 21 Mar 2000 08:22:05 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id 6F89CDA0A; Tue, 21 Mar 2000 17:21:54 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <20000321141055.E5367@enigma.redbrick.dcu.ie> References: <200003191838.KAA40955@rah.star-gate.com> <000701bf91d5$4aebeb60$0304020a@NENYA> <001a01bf91c1$7f62a4b0$0304020a@NENYA> <200003191838.KAA40955@rah.star-gate.com> <20000319220453.A65973@ipass.net> <005d01bf9221$4660ac60$0304020a@NENYA> <20000320153429.A1373@ipass.net> <20000321121048.E49550@enigma.redbrick.dcu.ie> <20000321141055.E5367@enigma.redbrick.dcu.ie> Date: Tue, 21 Mar 2000 17:16:21 +0100 To: David Murphy , stable@FreeBSD.ORG From: Brad Knowles Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:10 PM +0000 2000/3/21, David Murphy wrote: > Actually, I was thinking more along the lines of commercial unix > OSes, Sun for example, and I use this example because I'm familiar > with them, put out an Early Access version of Solaris 8 some months > before formally releasing Solaris 8. Effectively, this is the same > timescale FreeBSD is going to run on, but the early access version is > labelled -RELEASE. We just got our official shrink-wrapped versions of Solaris 8 from Sun. Do you think we're actually going to be stupid enough to try to put this into production any time within the next few months? It's an x.0 release from Sun, and we're going to treat it just like we do with x.0 releases from *any* vendor. We may play with it on our desktops, we may do some prototyping with it, etc.... But we're not going to put it up in any kind of production until we're pretty convinced that it will work well and we have sufficiently tested it on internal non-production machines, and we feel reasonably confident that it will be reasonably reliable. > As opposed to what? People staying away from x.0-RELEASE in droves, > because they find out it's a beta, AFTER they've been confused by > the naming policy? Thing is, it's *not* a beta anymore. It's more like a gamma version. It's been through the beta (the period during feature freeze and then code freeze when we try to wrap up outstanding bugs without introducing any new ones), and it's been tested about as much during that period of time as it could be. The *only* way to proceed from here is to actually release the thing, let people start trying to use it, and then report bugs back. But we wouldn't be acting in good faith if we didn't at least warn people that it's not quite ready for use on production servers. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 8:37:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from student-mailhub.dcu.ie (ns.dcu.ie [136.206.1.3]) by hub.freebsd.org (Postfix) with ESMTP id 5C88937BA4E for ; Tue, 21 Mar 2000 08:37:09 -0800 (PST) (envelope-from drjolt@redbrick.dcu.ie) Received: from enigma.redbrick.dcu.ie (postfix@enigma.redbrick.dcu.ie [136.206.15.5]) by student-mailhub.dcu.ie (8.9.3/8.9.3/893-FD) with ESMTP id QAA26270; Tue, 21 Mar 2000 16:37:07 GMT Received: by enigma.redbrick.dcu.ie (Postfix, from userid 2034) id 92CC37C94; Tue, 21 Mar 2000 16:37:07 +0000 (GMT) Date: Tue, 21 Mar 2000 16:37:07 +0000 From: David Murphy To: Brad Knowles Cc: stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Message-ID: <20000321163707.L5367@enigma.redbrick.dcu.ie> References: <001a01bf91c1$7f62a4b0$0304020a@NENYA> <200003191838.KAA40955@rah.star-gate.com> <20000319220453.A65973@ipass.net> <005d01bf9221$4660ac60$0304020a@NENYA> <20000320153429.A1373@ipass.net> <20000321121048.E49550@enigma.redbrick.dcu.ie> <20000321141055.E5367@enigma.redbrick.dcu.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from blk@skynet.be on Tue, Mar 21, 2000 at 05:16:21PM +0100 X-no-archive: yes Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting by Brad Knowles : > We just got our official shrink-wrapped versions of Solaris 8 from > Sun. Do you think we're actually going to be stupid enough to try > to put this into production any time within the next few months? > It's an x.0 release from Sun, and we're going to treat it just like > we do with x.0 releases from *any* vendor. We may play with it on > our desktops, we may do some prototyping with it, etc.... Right, and if you try to upgrade your Solaris 7 desktop, which, while not a production server, is a machine you personally need to do your job, to Solaris 8, and it fails, and you call Sun about it, and they tell you "Hey, what do you think you're doing? That's not ready for real use yet!". You wouldn't be too impressed, would you? That's basically the scenario I'm seeing with FreeBSD. > Thing is, it's *not* a beta anymore. It's more like a gamma > version. Call it -GAMMA then. Bascially, I'm saying I think it should be called something other than -RELEASE until the average user can install it, and upgrade to it from the prior version. > The *only* way to proceed from here is to actually release the > thing, let people start trying to use it, and then report bugs back. > But we wouldn't be acting in good faith if we didn't at least warn > people that it's not quite ready for use on production servers. IMHO the place for that warning is the release announcement and the release notes, and it wasn't in either last I looked. -- When asked if it is true that he uses his wheelchair as a weapon he will reply: "That's a malicious rumour. I'll run over anyone who repeats it." Stephen Hawking - [http://www.smh.com.au/news/0001/07/features/features1.html] David Murphy - For PGP public key, send mail with Subject: send-pgp-key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 8:45: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 2AEFD37BA7C for ; Tue, 21 Mar 2000 08:44:56 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id IAA13390; Tue, 21 Mar 2000 08:43:49 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: David Murphy Cc: stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) In-reply-to: Your message of "Tue, 21 Mar 2000 12:10:48 GMT." <20000321121048.E49550@enigma.redbrick.dcu.ie> Date: Tue, 21 Mar 2000 08:43:49 -0800 Message-ID: <13387.953657029@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The problem is, -RELEASE is pushed out like a new release of a > commercial OS, with big announcements, etc. etc., so people expect it > to have been subject to a similar level of prerelease beta testing. > Clearly this is not and cannot be the case, and IMHO therefore it > should not be labeled -RELEASE, but -EARLYACCESS or similar. Actually, the problem is that we ARE now doing good quality "dot-zero" releases and all our old quotes about how bleeding edge they are now comes back to haunt us. I challenge you to find anything about 4.0 which is inherently less stable or usable than, say, 3.4. We've come a long way and probably need to stop scaring people off from our releases. We didn't do a 30 day code freeze this time for nothing you know! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 8:48:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from servo.ccr.org (servo.ccr.org [198.3.0.2]) by hub.freebsd.org (Postfix) with ESMTP id 14E9337BA7C for ; Tue, 21 Mar 2000 08:48:49 -0800 (PST) (envelope-from mo@servo.ccr.org) Received: from servo.ccr.org (localhost [127.0.0.1]) by servo.ccr.org (8.9.2/8.9.2) with ESMTP id LAA01778; Tue, 21 Mar 2000 11:47:39 -0500 (EST) (envelope-from mo@servo.ccr.org) Message-Id: <200003211647.LAA01778@servo.ccr.org> To: Brad Knowles Cc: David Murphy , stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) In-reply-to: Your message of "Tue, 21 Mar 2000 17:16:21 +0100." Date: Tue, 21 Mar 2000 11:47:39 -0500 From: "Mike O'Dell" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i see. the justification is that it's ok for it to suck as much as anything else one claims to be better than. my, my, what a glowing endorsement. "When all else fails, lower your standards." -mo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 8:53:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (Postfix) with SMTP id 8DFAD37B944 for ; Tue, 21 Mar 2000 08:53:37 -0800 (PST) (envelope-from vev@michvhf.com) Received: (qmail 5767 invoked by uid 1001); 21 Mar 2000 16:53:39 -0000 Date: Tue, 21 Mar 2000 11:53:38 -0500 (EST) From: Vince Vielhaber To: "Jordan K. Hubbard" Cc: David Murphy , stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) In-Reply-To: <13387.953657029@zippy.cdrom.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 Tue, 21 Mar 2000, Jordan K. Hubbard wrote: > > The problem is, -RELEASE is pushed out like a new release of a > > commercial OS, with big announcements, etc. etc., so people expect it > > to have been subject to a similar level of prerelease beta testing. > > Clearly this is not and cannot be the case, and IMHO therefore it > > should not be labeled -RELEASE, but -EARLYACCESS or similar. > > Actually, the problem is that we ARE now doing good quality "dot-zero" > releases and all our old quotes about how bleeding edge they are now > comes back to haunt us. I challenge you to find anything about 4.0 > which is inherently less stable or usable than, say, 3.4. We've > come a long way and probably need to stop scaring people off from > our releases. We didn't do a 30 day code freeze this time for nothing > you know! If the regular subscribers won't get 4.x until it's 4.1 and 4.0 is as stable as 3.4, then why weren't we even offered the same choice we had with the 2.2.8->3.0 transition (get them all - and 3.0 wasn't all that stable). Is there a reason that 4.0 isn't being shipped as part of the regular stable sub? Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com http://www.pop4.net 128K ISDN: $24.95/mo or less - 56K Dialup: $17.95/mo or less at Pop4 Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 8:54:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id E028A37B62A for ; Tue, 21 Mar 2000 08:54:12 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id IAA13454; Tue, 21 Mar 2000 08:53:13 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Brad Knowles Cc: David Murphy , stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) In-reply-to: Your message of "Tue, 21 Mar 2000 13:38:47 +0100." Date: Tue, 21 Mar 2000 08:53:13 -0800 Message-ID: <13451.953657593@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It has gotten *way* more testing than any Microsoft x.0 release, > but it's still not ready for prime-time. Actually, it's my understanding that Yahoo already has 4.0 in production. Again, 4.0 is not your typical dot-zero release and I doubt we'll ever release anything like 3.0 again. To make an analogy of sorts, in the early days of aviation it was all about cloth and wood and a lot of pilots who were probably marginally suicidal at best. Then the industry grew up and pilots became more like accountants in nature than barnstorming daredevils. So it is with us, and (with a few regrettable exceptions) each release is just that much better tested and put together than the ones which preceded it. We need to stop knocking our efforts; that's the user's job. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 9: 2:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from student-mailhub.dcu.ie (ns.dcu.ie [136.206.1.3]) by hub.freebsd.org (Postfix) with ESMTP id 0206137BA07 for ; Tue, 21 Mar 2000 09:02:37 -0800 (PST) (envelope-from drjolt@redbrick.dcu.ie) Received: from enigma.redbrick.dcu.ie (postfix@enigma.redbrick.dcu.ie [136.206.15.5]) by student-mailhub.dcu.ie (8.9.3/8.9.3/893-FD) with ESMTP id RAA30934; Tue, 21 Mar 2000 17:01:17 GMT Received: by enigma.redbrick.dcu.ie (Postfix, from userid 2034) id 18D817C94; Tue, 21 Mar 2000 17:01:18 +0000 (GMT) Date: Tue, 21 Mar 2000 17:01:18 +0000 From: David Murphy To: "Jordan K. Hubbard" Cc: stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Message-ID: <20000321170118.M5367@enigma.redbrick.dcu.ie> References: <20000321121048.E49550@enigma.redbrick.dcu.ie> <13387.953657029@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <13387.953657029@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Tue, Mar 21, 2000 at 08:43:49AM -0800 X-no-archive: yes Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting <13387.953657029@zippy.cdrom.com> by "Jordan K. Hubbard" : > I challenge you to find anything about 4.0 which is inherently less > stable or usable than, say, 3.4. Well, to be perfectly honest, I don't know what the 2.X->3.X upgrade procedure was like, but upgrading from 3.4 to 4.0 is fiddly, and it doesn't help that the instructions are counterintuitively at the bottom of /usr/src/UPDATING which, to the untrained eye, looks like a changelog, and lusers like me don't read changelogs to see if someone happened to put vital instructions at the bottom of it. > We've come a long way and probably need to stop scaring people off > from our releases. We didn't do a 30 day code freeze this time for > nothing you know! Well, don't take this personally (anyone), but I wish you (plural) would make up your (plural) minds. If it's a not-ready-for-real-use release, it'd be nice if people didn't start flaming other people (Who, I might add, read the release notes carefully, looking for warnings) for trying to use it for real work with "Fool! Don't you know that 4.0 means it's not ready for real use?!". -- When asked if it is true that he uses his wheelchair as a weapon he will reply: "That's a malicious rumour. I'll run over anyone who repeats it." Stephen Hawking - [http://www.smh.com.au/news/0001/07/features/features1.html] David Murphy - For PGP public key, send mail with Subject: send-pgp-key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 9: 7:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from melete.ch.intel.com (melete.ch.intel.com [143.182.246.25]) by hub.freebsd.org (Postfix) with ESMTP id A60EC37BABA for ; Tue, 21 Mar 2000 09:07:48 -0800 (PST) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by melete.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.19 2000/01/29 00:15:43 dmccart Exp $) with ESMTP id RAA20645 for ; Tue, 21 Mar 2000 17:09:04 GMT Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id KAA04866 for ; Tue, 21 Mar 2000 10:06:41 -0700 (MST) X-Envelope-To: X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id MAA17622; Tue, 21 Mar 2000 12:07:46 -0500 (EST) X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14551.44129.972535.210497@hip186.ch.intel.com> Date: Tue, 21 Mar 2000 10:07:45 -0700 (MST) To: stable@freebsd.org Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) In-Reply-To: <13387.953657029@zippy.cdrom.com> References: <20000321121048.E49550@enigma.redbrick.dcu.ie> <13387.953657029@zippy.cdrom.com> X-Mailer: VM 6.75 under Emacs 20.3.11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Tuesday, March 21, Jordan K. Hubbard wrote: ] > > Actually, the problem is that we ARE now doing good quality "dot-zero" > releases and all our old quotes about how bleeding edge they are now > comes back to haunt us. I challenge you to find anything about 4.0 > which is inherently less stable or usable than, say, 3.4. We've > come a long way and probably need to stop scaring people off from > our releases. We didn't do a 30 day code freeze this time for nothing > you know! > > - Jordan I would have to agree with Jordan here. Of course with the plethora of PC hardware combinations out there (with some of the marginally designed components people pick up) it is impossible for the developers to make sure 100% of everything "works as expected (TM)." I went through the 2.2.8->3.0 transition and now I've installed 4.0-RC, RC2, and RC3 on the same hardware that I did the 2.2.8->3.0 transition on and I can say without a doubt that 4.0 is a *much* better ".0" release than 3.0 was. This "crypto" thing is tripping people up, but it's just a matter of RTFM, not instability of the software. As with everything, YMMV .... -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 9:24: 4 2000 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 AEE5F37BAAE for ; Tue, 21 Mar 2000 09:23:58 -0800 (PST) (envelope-from jcm@dogma.freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 1.92 #3) for freebsd-stable@freebsd.org id 12XSNo-0005cn-00; Tue, 21 Mar 2000 17:23:56 +0000 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id RAA63268 for freebsd-stable@freebsd.org; Tue, 21 Mar 2000 17:23:55 GMT (envelope-from jcm) Date: Tue, 21 Mar 2000 17:23:55 +0000 From: J McKitrick To: freebsd-stable@freebsd.org Subject: zip driver Message-ID: <20000321172355.B63148@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 heard there is a PR for the parallel port zip drive problem. Does anyone know if work is being done on this yet, or if there is a workaround to get the drive to function? As of now, vpo times out during the boot sequence and is inaccessible. I've tinkered with the glags for ppc, but nothing works so far. jm -- ----------------------- j_mckitrick@bigfoot.com Ski Utah ! ----------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 9:40:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 0441037BBA1 for ; Tue, 21 Mar 2000 09:36:47 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: from kilt.nothing-going-on.org (kilt.nothing-going-on.org [192.168.1.18]) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) with ESMTP id QAA97004; Tue, 21 Mar 2000 16:47:14 GMT (envelope-from nik@catkin.nothing-going-on.org) Received: (from nik@localhost) by kilt.nothing-going-on.org (8.9.3/8.9.3) id MAA26744; Tue, 21 Mar 2000 12:29:24 GMT (envelope-from nik@catkin.nothing-going-on.org) Date: Tue, 21 Mar 2000 12:29:24 +0000 From: Nik Clayton To: Alexandr Listopad Cc: stable@freebsd.org Subject: Re: defaults/make.conf patch. Message-ID: <20000321122924.A26706@kilt.nothing-going-on.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Alexandr Listopad on Fri, Mar 17, 2000 at 09:03:09AM +0200 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 17, 2000 at 09:03:09AM +0200, Alexandr Listopad wrote: > --- src/etc/defaults/make.conf~ Fri Mar 17 08:56:45 2000 > +++ src/etc/defaults/make.conf Fri Mar 17 09:00:10 2000 > @@ -225,3 +225,8 @@ > # /etc/passwd. The default number is 20011. > # > #TOP_TABLE_SIZE= 101 > +# > +# DOC_LANG - select your default list of languages to build and install > +# docs. > +# > +#DOC_LANG= ru_RU.KOI8-R en_US.ISO_8859-1 Good idea. I'll commit later. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 9:44:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zogbe.tasam.com (jogleaso.campus.vt.edu [198.82.107.209]) by hub.freebsd.org (Postfix) with ESMTP id 634E037BA71 for ; Tue, 21 Mar 2000 09:44:08 -0800 (PST) (envelope-from clash@zogbe.tasam.com) Received: from localhost (clash@localhost) by zogbe.tasam.com (8.9.3/8.9.3) with ESMTP id MAA85696; Tue, 21 Mar 2000 12:42:54 -0500 (EST) (envelope-from clash@zogbe.tasam.com) Date: Tue, 21 Mar 2000 12:42:54 -0500 (EST) From: Joe Gleason To: bod@tasam.com Cc: freebsd-stable@freebsd.org Subject: Re: 4.0 Install World problems on all systems In-Reply-To: <200003211307.IAA65790@sneeze.tasam.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 cp /usr/obj/usr/src/i386/usr/bin/install-info /usr/bin If this is done after make buildworld and before installworld, it should be groovy. The old version of install-info does not work correctly when doing the installworld. Joe Gleason Tasam On Tue, 21 Mar 2000, digital wrote: > ===> lib/libcom_err > cd /usr/src/lib/libcom_err && install -C -o root -g wheel -m 444 /usr/src/lib/libcom_err/../../contrib/com_err/com_err.h /usr/include > cd /usr/src/lib/libcom_err && install -C -o root -g wheel -m 444 /usr/src/lib/libcom_err/../../contrib/com_err/com_right.h /usr/include > install -c -o root -g wheel -m 444 libcom_err.a /usr/lib > install -c -o root -g wheel -m 444 libcom_err_p.a /usr/lib > install -c -s -o root -g wheel -m 444 libcom_err.so.2 /usr/lib > ln -sf libcom_err.so.2 /usr/lib/libcom_err.so > install -c -o root -g wheel -m 444 com_err.3.gz /usr/share/man/man3 > ===> lib/libcom_err/doc > install-info --quiet --defsection="Programming & development tools." --defentry="* libcom_err: (com_err). A Common Error Description Library for UNIX." com_err.info /usr/share/info/dir > install-info: unrecognized option `--defsection=Programming & development tools.' > Try `install-info --help' for a complete list of options. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 10:25:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from correo.tamnet.com.mx (correo.tamnet.com.mx [200.34.205.20]) by hub.freebsd.org (Postfix) with ESMTP id 7C2AD37BA2F for ; Tue, 21 Mar 2000 10:25:22 -0800 (PST) (envelope-from adepoo@tamnet.com.mx) Received: from correo.tamnet.com.mx (correo.tamnet.com.mx [200.34.205.20]) by correo.tamnet.com.mx (8.9.1a/8.9.1a) with SMTP id MAA25934 for ; Tue, 21 Mar 2000 12:25:18 -0600 (CST) Date: Tue, 21 Mar 2000 12:25:18 -0600 (CST) From: To: freebsd-stable@FreeBSD.ORG Subject: can't make openssh fix (is this ok?) 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 cvsup the security ports and find that patch-ac changed on openssh, so I tried to make again the port with this failure: /usr/include/sys/socket.h:47: warning: `sa_family_t' previously declared here /usr/ports/security/openssh/work/ssh/lib/../includes.h:73: conflicting types for `socklen_t' /usr/include/sys/socket.h:48: previous declaration of `socklen_t' *** Error code 1 Stop. so I checked the patch-ac file and found: @@ -65,5 +64,30 @@ * client program. Socketpairs do not seem to work on all systems. */ #define USE_PIPES 1 + +#if defined(__FreeBSD__) && __FreeBSD__ <= 3 +/* + * Data types. + */ +typedef u_char sa_family_t; +typedef int socklen_t; + changed to: @@ -65,5 +64,28 @@ * client program. Socketpairs do not seem to work on all systems. */ #define USE_PIPES 1 + +#if defined(__FreeBSD__) && __FreeBSD__ <= 3 +/* + * Data types. + */ + and the make went well. Is this patch to the patch-ac correct? The data types are already declared in an included file. Thanks in advance. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 10:31:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id CD36137BC79; Tue, 21 Mar 2000 10:31:15 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id KAA30359; Tue, 21 Mar 2000 10:30:39 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 21 Mar 2000 10:30:39 -0800 (PST) From: Kris Kennaway To: Yusuf Goolamabbas Cc: Dan Moschuk , freebsd-stable@FreeBSD.ORG Subject: Re: Reason for sshd[238]: fatal: rsa_private_decrypt() failed 4.0-stable In-Reply-To: <20000321162706.B9095@outblaze.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 Tue, 21 Mar 2000, Yusuf Goolamabbas wrote: > Isn't that illegal (inappropiate) for somebody outside the US ? It's not illegal, but it is inappropriate - the RSAREF code is inferior to the openssl native implementation of RSA which isn't carried in the US. Since you used the 4.x-secure-stable-supfile you should be correctly getting your crypto from internat, so thats not the problem. Can you run sshd in debug mode (sshd -d) and report the more verbose error you get when you connect to it with the client? Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 10:35:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 5908637BCE3; Tue, 21 Mar 2000 10:35:28 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id KAA30820; Tue, 21 Mar 2000 10:35:28 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 21 Mar 2000 10:35:27 -0800 (PST) From: Kris Kennaway To: Brad Knowles Cc: Yusuf Goolamabbas , Dan Moschuk , freebsd-stable@FreeBSD.ORG Subject: Re: Reason for sshd[238]: fatal: rsa_private_decrypt() failed 4.0-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 On Tue, 21 Mar 2000, Brad Knowles wrote: > Yes, I believe so. In fact, if USA_RESIDENT is NO, I would > expect this port to bomb out. It will work outside the US - but perhaps I should add a warning to the port/package that if you're outside the US you probably don't want to use it. > I just installed a fresh 4.0-RELEASE a couple of days ago, and > although USA_RESIDENT was set to "NO", and I made a point of grabbing > both the sources and the crypto from ftp.uk.freebsd.org, it still > seemed to get the RSAREF stuff which choked and puked on keys larger > than 1024 bits. Unless ftp.uk.freebsd.org rolled their own release, they've got the US 4.0 one, which doesn't contain the international crypto (although I believe it should give you the option of fetching it from internat during the install - which still won't work because Mark Murray still hasn't rebuilt the librsaintl package yet like I've been asking him for the past week). This is unfortunate because it means a lot of international folks are going to be installing the inferior US implementation :-( > In order to fix it, I installed cvsup This fixed it because most international cvsup mirrors (although not all, I think there's a cvsup operator in germany who hasn't been reading my emails on the topic) pick up their crypto from internat, so you compiled the correct version. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 10:35:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id D77CF37B9FC for ; Tue, 21 Mar 2000 10:35:38 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA13946; Tue, 21 Mar 2000 10:35:04 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Vince Vielhaber Cc: David Murphy , stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) In-reply-to: Your message of "Tue, 21 Mar 2000 11:53:38 EST." Date: Tue, 21 Mar 2000 10:34:59 -0800 Message-ID: <13940.953663699@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If the regular subscribers won't get 4.x until it's 4.1 and 4.0 is > as stable as 3.4, then why weren't we even offered the same choice > we had with the 2.2.8->3.0 transition (get them all - and 3.0 wasn't > all that stable). Is there a reason that 4.0 isn't being shipped as > part of the regular stable sub? You are offered the same choice; all you need to do is call Walnut Creek CDROM (or email orders@cdrom.com) and indicate your preference. Their current plan is based purely on what we expected the *perception* out there to be, not reality. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 10:44:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 1FA7E37BC4E for ; Tue, 21 Mar 2000 10:44:43 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id 05AFFDC28; Tue, 21 Mar 2000 19:43:55 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <20000321163707.L5367@enigma.redbrick.dcu.ie> References: <001a01bf91c1$7f62a4b0$0304020a@NENYA> <200003191838.KAA40955@rah.star-gate.com> <20000319220453.A65973@ipass.net> <005d01bf9221$4660ac60$0304020a@NENYA> <20000320153429.A1373@ipass.net> <20000321121048.E49550@enigma.redbrick.dcu.ie> <20000321141055.E5367@enigma.redbrick.dcu.ie> <20000321163707.L5367@enigma.redbrick.dcu.ie> Date: Tue, 21 Mar 2000 19:00:16 +0100 To: David Murphy From: Brad Knowles Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Cc: stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:37 PM +0000 2000/3/21, David Murphy wrote: > Right, and if you try to upgrade your Solaris 7 desktop, which, while > not a production server, is a machine you personally need to do your > job, to Solaris 8, and it fails, and you call Sun about it, and they > tell you "Hey, what do you think you're doing? That's not ready for > real use yet!". You wouldn't be too impressed, would you? That's > basically the scenario I'm seeing with FreeBSD. If that is the impression you have gotten, then I apologize. I am not saying that 4.0 is not yet ready for installation on your desktops and other non-production servers, in fact that is precisely where it should be installed, and by a broader audience than it has gotten so far. I *am* saying that I do not think that it is ready yet for installation on production servers, just like Solaris 8 is not yet ready for installation on production servers. FreeBSD 4.0 is a commercial-quality OS that doesn't cost you anything to download and install (other than your time and whatever the cost might be to transfer the bits), and in fact I believe that it is of higher quality than anything else out there in the mid-range non-HA server environment -- with the possible exception of the most recent releases of the previous version of FreeBSD. Frankly, I think that speaks very highly of FreeBSD. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 10:46:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 9B19537BC4F for ; Tue, 21 Mar 2000 10:46:36 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id 99123DE20; Tue, 21 Mar 2000 19:44:03 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <13451.953657593@zippy.cdrom.com> References: <13451.953657593@zippy.cdrom.com> Date: Tue, 21 Mar 2000 19:35:38 +0100 To: "Jordan K. Hubbard" From: Brad Knowles Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Cc: David Murphy , stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 8:53 AM -0800 2000/3/21, Jordan K. Hubbard wrote: > Actually, it's my understanding that Yahoo already has 4.0 in > production. Guys like you and Mike are so busy that when you step in on an issue, it's got to be pretty important -- especially when you step in multiple times. So, I'll sit down and shut up. However, that doesn't mean that I believe that 4.0 is ready for general use in a production environment. IMO, the guys at Yahoo! know enough about systems like this (and probably helped write goodly portions of them) that they can take OS versions that are not quite ready for general use in a production environment, and they can make them ready. However, that's precisely the kind of additional work that needs to get folded into 4.0, so that 4.1 or 4.2 *is* ready for general use in a production environment. > Again, 4.0 is not your typical dot-zero release and I > doubt we'll ever release anything like 3.0 again. I don't doubt that it is light-years ahead of 3.0. However, with 3.4-STABLE, you have set a very high bar for yourself, and I think there are still a few niggling details that need to be dealt with before 4.x is ready to clear that hurdle and go on to conquer new territory. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 10:46:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 7477837BC24 for ; Tue, 21 Mar 2000 10:46:39 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id 9524AE05F; Tue, 21 Mar 2000 19:43:57 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <13387.953657029@zippy.cdrom.com> References: <13387.953657029@zippy.cdrom.com> Date: Tue, 21 Mar 2000 19:04:23 +0100 To: "Jordan K. Hubbard" , David Murphy From: Brad Knowles Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Cc: stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 8:43 AM -0800 2000/3/21, Jordan K. Hubbard wrote: > I challenge you to find anything about 4.0 > which is inherently less stable or usable than, say, 3.4. I can't speak for the relative quality of 4.0 versus 3.0, but I'll take your word for it. However, if you're going to compare 4.0 to 3.4, then I think a perfect counter-example is the message that got this whole thread started -- voxware. I do continue to monitor the -current mailing list, and I continue to see a few too many things cropping up there that lead me to believe that, while 4.0 may be much better than 3.0, it's still got a little ways to go before it can compare favourably to 3.4 in all respects. 4.0 is already better than 3.4 in many areas, but there are still a few areas where 3.4 is superior, and IMO overall 3.4 is still the smarter choice -- for now. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 10:46:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 4530A37BB85 for ; Tue, 21 Mar 2000 10:46:19 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id 47CB0E083; Tue, 21 Mar 2000 19:44:02 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <200003211647.LAA01778@servo.ccr.org> References: <200003211647.LAA01778@servo.ccr.org> Date: Tue, 21 Mar 2000 19:19:28 +0100 To: "Mike O'Dell" From: Brad Knowles Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Cc: David Murphy , stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:47 AM -0500 2000/3/21, Mike O'Dell wrote: > i see. > > the justification is that it's ok for it to suck as > much as anything else one claims to be better than. I'm not sure I follow your logic. Our worst is far better than the best Microsoft has ever produced, so surely you can't be using that as the basis of this comment. The best that Sun has ever produced is probably better than the worst that we've ever produced, so that might be the basis of your comment. But I'm not sure. > my, my, what a glowing endorsement. > > "When all else fails, lower your standards." I don't think we're lowering our standards at all. My personal opinion is that FreeBSD is better than just about everything else out there on the market, freely available or not. IMO, the only places where FreeBSD is not yet superior to the other solutions available are on the ultra high end, where you're up against things like the Compaq/Tandem Himalaya non-stop systems that can truly claim to be fault-tolerant and not just fault-resilient or "highly available". We're producing a commercial-quality OS and letting people download and install it at no charge (or we'll sell them CDs at minimal prices), and we don't charge anything for the support that we provide today. I think that speaks very highly for us, very highly indeed when you consider that the largest and most heavily trafficked sites on the 'net depend on FreeBSD. However, relative to that extremely high standard, I believe that there are still a few rough edges in FreeBSD 4.0, and it is not yet quite ready to be considered suitable for use in production environments. There are people who can take it and turn it into a platform that is imminently suitable for production environments, but those are the same sorts of people who helped build 4.0 from 3.x, so they know enough about what they are doing that they don't have to worry about those rough edges. For everyone else, it's not quite yet at the "./configure; make; make install" no-brainer stage, where it would be suitable for use on production systems for those people who are new to FreeBSD and don't have the knowledge, skills, or talent necessary to take 4.0 and turn it into that kind of a production platform. In other words, you know enough that you can probably install FreeBSD 6.0-FUTURE on your production systems and do quite well. Places like Yahoo! and hotmail can install 5.0-CURRENT on their production systems, and be just fine. People like me can install RELENG_4 on a server that is not yet in production, and play around with it, do some benchmarking, and get some idea of what it's going to be able to do for us when we do finally put a release of 4.x-STABLE in production. Others will still be better off starting with 3.x-STABLE and learning with it, until such time as it nears its end-of-life and we're getting closer to releasing 5.0-STABLE. Personally, I think the sweet spot for 4.0-STABLE is somewhere in the middle of that curve, but we're not yet quite there. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 10:49:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id BE3FB37BBC2; Tue, 21 Mar 2000 10:49:45 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id KAA32237; Tue, 21 Mar 2000 10:49:45 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 21 Mar 2000 10:49:45 -0800 (PST) From: Kris Kennaway To: David Murphy Cc: stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) In-Reply-To: <20000321141055.E5367@enigma.redbrick.dcu.ie> 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, 21 Mar 2000, David Murphy wrote: > Actually, I was thinking more along the lines of commercial unix > OSes, Sun for example, and I use this example because I'm familiar > with them, put out an Early Access version of Solaris 8 some months > before formally releasing Solaris 8. Effectively, this is the same > timescale FreeBSD is going to run on, but the early access version is > labelled -RELEASE. No, the early-access version is labelled 4.0-RC1. If you're not willing to jump on board during the testing phase when we say "okay, we think this is pretty much ready unless anyone finds bugs in the next 30 days (which turned into over 2 months in the end)", then don't complain when 4.0 is released and you find a bug that could have been fixed earlier. It's as simple as that - if there are bugs we don't get alerted about during the publicized "prerelease" cycle (and thanks to all those who *did* jump on board and help us improve the quality of 4.0!), then they'll have to be fixed post-release. > As opposed to what? People staying away from x.0-RELEASE in droves, > because they find out it's a beta, AFTER they've been confused by > the naming policy? As others have pointed out, it's not a "beta" - but it *is* new technology which must be expected to have some bugs. This is the case *all over the computer industry* - every dot-zero release has some level of bugginess, because by definition the dot-zero means it's got a lot of new code in it, and humans are bad programmers. Cisco x.0 releases are buggy. Solaris 2.0 was extremely buggy. Windows NT 4.0 was extremely buggy (they're still fixing serious bugs in it after 5 years in the field) Windows 2000 is extremely buggy, and Microsoft rolled out one of the most extensive beta testing programs ever - Windows 2000 was in beta for over a year! If you don't understand this reality, then you've either been conned by the marketing apparati of big companies into thinking that dot-zero releases only contain wonderful new features that you really need, or you don't understand this game we're in all that well. Perhaps if we ran multimedia ads across the world and charged people exorbitant license fees for the upgrade then they'd be happier. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 10:51:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ring.vpop.net (ring.vpop.net [206.117.147.5]) by hub.freebsd.org (Postfix) with ESMTP id 517B037BC4E for ; Tue, 21 Mar 2000 10:51:54 -0800 (PST) (envelope-from mreimer@vpop.net) Received: from vpop.net (bilbo.vpop.net [216.160.82.65]) by ring.vpop.net (8.9.3/8.9.3) with ESMTP id KAA48475; Tue, 21 Mar 2000 10:51:45 -0800 (PST) (envelope-from mreimer@vpop.net) Message-ID: <38D7C4C7.ABC430C0@vpop.net> Date: Tue, 21 Mar 2000 10:51:51 -0800 From: Matthew Reimer Organization: VPOP Technologies, Inc. X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Darius Ramanauskas Cc: stable@freebsd.org Subject: Re: newpcm and CS423X References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To get the game port attached, add device joy0 I don't think the other two are currently used by any driver. Matt Darius Ramanauskas wrote: > > Hi All, > > I just upgraded my system from 3.4-STABLE to 4.0-STABLE > and have some questions related to newpcm driver. > Then kernel starts it reports this: > pcm0: at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 > on isa0 > unknown0: at port 0x3a0-0x3a7 on isa0 > unknown1: at port 0xf00-0xf07 on isa0 > unknown2: at port 0x330-0x331 on isa0 > > So what this "unknownX" is ? I feel that something is missing > in my kernel config or in /dev but I could not find what :(( > In kernel config contains just this: > > device pcm > > from sndstat: > dara:/home/dara> cat /dev/sndstat > FreeBSD Audio Driver (newpcm) Mar 21 2000 13:56:43 > Installed devices: > pcm0: at io 0x534 irq 5 drq 1:0 (1p/1r channels duplex) > > Thank You, > > Darius > > PS If it easy, please don't beat me, just point to right answer .... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 10:55:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id DAD6E37C038; Tue, 21 Mar 2000 10:55:29 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id KAA32940; Tue, 21 Mar 2000 10:55:30 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 21 Mar 2000 10:55:29 -0800 (PST) From: Kris Kennaway To: Brad Knowles Cc: "Jordan K. Hubbard" , David Murphy , stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) 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, 21 Mar 2000, Brad Knowles wrote: > I can't speak for the relative quality of 4.0 versus 3.0, but > I'll take your word for it. However, if you're going to compare 4.0 > to 3.4, then I think a perfect counter-example is the message that > got this whole thread started -- voxware. Voxware is still supported in 4.0 and won't be removed. This thread started with speculation about what might happen during the course of development of 5.0-CURRENT over the next year or more. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 10:55:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 9214337C03B; Tue, 21 Mar 2000 10:55:30 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id UAA58856; Tue, 21 Mar 2000 20:55:24 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200003211855.UAA58856@zibbi.mikom.csir.co.za> Subject: Re: Reason for sshd[238]: fatal: rsa_private_decrypt() failed 4.0-stable In-Reply-To: from Kris Kennaway at "Mar 21, 2000 10:35:27 am" To: kris@FreeBSD.ORG (Kris Kennaway) Date: Tue, 21 Mar 2000 20:55:24 +0200 (SAT) Cc: blk@skynet.be (Brad Knowles), yusufg@outblaze.com (Yusuf Goolamabbas), dan@FreeBSD.ORG (Dan Moschuk), 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 > > Unless ftp.uk.freebsd.org rolled their own release, they've got the US 4.0 > one, which doesn't contain the international crypto (although I believe it > should give you the option of fetching it from internat during the install > - which still won't work because Mark Murray still hasn't rebuilt the > librsaintl package yet like I've been asking him for the past week). > Uhm, I think it is there. Maybe Mark just forgot to tell you or isn't this it? internat:~ > ls -l /home/ftp/pub/FreeBSD/packages-4.0/All/librsaintl-1.0.tgz -rw-r--r-- 1 markm ftpmaint 7461 Mar 18 11:36 /home/ftp/pub/FreeBSD/packages-4.0/All/librsaintl-1.0.tgz John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 11: 4:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 99EF037BDB6 for ; Tue, 21 Mar 2000 11:04:24 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA14081; Tue, 21 Mar 2000 11:03:49 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: David Murphy Cc: stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) In-reply-to: Your message of "Tue, 21 Mar 2000 17:01:18 GMT." <20000321170118.M5367@enigma.redbrick.dcu.ie> Date: Tue, 21 Mar 2000 11:03:49 -0800 Message-ID: <14078.953665429@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, to be perfectly honest, I don't know what the 2.X->3.X upgrade > procedure was like, but upgrading from 3.4 to 4.0 is fiddly, and it Upgrading is a different kettle of fish. I'm asking what it is about 4.0 that you find more unstable *once it is installed*. > Well, don't take this personally (anyone), but I wish you (plural) > would make up your (plural) minds. If it's a not-ready-for-real-use > release, it'd be nice if people didn't start flaming other people > (Who, I might add, read the release notes carefully, looking for > warnings) for trying to use it for real work with "Fool! Don't you > know that 4.0 means it's not ready for real use?!". People are still working from old information, some of which was resurrected without my go-ahead (I'm thinking of a certain announcement from Nik). - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 11: 9:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from thehousleys.net (frenchknot.ne.mediaone.net [24.147.224.201]) by hub.freebsd.org (Postfix) with ESMTP id D52F137BBC2; Tue, 21 Mar 2000 11:09:42 -0800 (PST) (envelope-from jim@thehousleys.net) Received: from thehousleys.net (housley@baby.int.thehousleys.net [192.168.0.24]) by thehousleys.net (8.9.3/8.9.3) with ESMTP id OAA75905; Tue, 21 Mar 2000 14:09:38 -0500 (EST) Message-ID: <38D7C8F1.E982FC55@thehousleys.net> Date: Tue, 21 Mar 2000 14:09:37 -0500 From: James Housley Organization: The Housleys dot Net X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: David Murphy , stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improvingnewpcm performance?) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > snip > No, the early-access version is labelled 4.0-RC1. If you're not willing to > jump on board during the testing phase when we say "okay, we think this is > pretty much ready unless anyone finds bugs in the next 30 days (which > snip > > Perhaps if we ran multimedia ads across the world and charged people > exorbitant license fees for the upgrade then they'd be happier. > > That would actually be easier to deal with. Society, at least in the USA, have gotten used to not accepting any responsibility for ourselves. Having a large multi-national to blame is both easier and socially acceptable. Personally I did NOT participate in 4.0-RCx nor have I moved from 3.x-STABLE to 4.x-STABLE because I haven't had time and more importantly I use these machines to make my living. When 3-STABLE is about to be designated as "INACTIVE except for security issues" as 2-STABLE did about 3.2, I will then start to migrate to 4-STABLE. Jim -- Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 11:23:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id ECCDA37BAAE; Tue, 21 Mar 2000 11:23:37 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id LAA35714; Tue, 21 Mar 2000 11:23:38 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 21 Mar 2000 11:23:38 -0800 (PST) From: Kris Kennaway To: James Housley Cc: David Murphy , stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improvingnewpcm performance?) In-Reply-To: <38D7C8F1.E982FC55@thehousleys.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 Tue, 21 Mar 2000, James Housley wrote: > That would actually be easier to deal with. Society, at least in the > USA, have gotten used to not accepting any responsibility for > ourselves. Having a large multi-national to blame is both easier and > socially acceptable. :) I could almost handle being cursed impotently by customers if they were paying me thousands of dollars for the privilege :-) > Personally I did NOT participate in 4.0-RCx nor have I moved from > 3.x-STABLE to 4.x-STABLE because I haven't had time and more importantly > I use these machines to make my living. When 3-STABLE is about to be > designated as "INACTIVE except for security issues" as 2-STABLE did > about 3.2, I will then start to migrate to 4-STABLE. That's perfectly fine..this is the "conservative upgrade path" intended for people who don't want to (or can't afford to) face shakedown bugs on their machines. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 11:27:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id A022937B881 for ; Tue, 21 Mar 2000 11:27:10 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA14320; Tue, 21 Mar 2000 11:25:45 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Brad Knowles Cc: David Murphy , stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) In-reply-to: Your message of "Tue, 21 Mar 2000 19:04:23 +0100." Date: Tue, 21 Mar 2000 11:25:45 -0800 Message-ID: <14317.953666745@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I can't speak for the relative quality of 4.0 versus 3.0, but > I'll take your word for it. However, if you're going to compare 4.0 > to 3.4, then I think a perfect counter-example is the message that > got this whole thread started -- voxware. I don't understand where voxware comes into this. As many people have already noted (repeatedly), voxware was NOT removed from 4.0, it's purely a 5.0 issue. > I do continue to monitor the -current mailing list, and I > continue to see a few too many things cropping up there that lead me > to believe that, while 4.0 may be much better than 3.0, it's still > got a little ways to go before it can compare favourably to 3.4 in > all respects. Again, I wouldn't mind some details. I believe we've fixed all the outstanding issues which have been reported. Please don't just go on mailing list traffic since half of those reports operator error. As they say on ``Dragnet'', "Just the facts, sir." > 4.0 is already better than 3.4 in many areas, but there are still > a few areas where 3.4 is superior, and IMO overall 3.4 is still the > smarter choice -- for now. Which areas are these? Again, please be specific so that I can actually respond to this rather than going "What the hell is this man even talking about?" :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 11:27:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id A037437BC12 for ; Tue, 21 Mar 2000 11:27:41 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA14332; Tue, 21 Mar 2000 11:26:35 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Brad Knowles Cc: David Murphy , stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) In-reply-to: Your message of "Tue, 21 Mar 2000 19:35:38 +0100." Date: Tue, 21 Mar 2000 11:26:35 -0800 Message-ID: <14329.953666795@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 3.4-STABLE, you have set a very high bar for yourself, and I think > there are still a few niggling details that need to be dealt with > before 4.x is ready to clear that hurdle and go on to conquer new > territory. Ahem ahem. I see niggling, I don't see details. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 11:32:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from noc.uoa.gr (olympus.noc.uoa.gr [195.134.100.100]) by hub.freebsd.org (Postfix) with ESMTP id EC61537B881 for ; Tue, 21 Mar 2000 11:32:49 -0800 (PST) (envelope-from isach@noc.uoa.gr) Received: from localhost (isach@localhost) by noc.uoa.gr (8.8.8/8.8.8) with SMTP id VAA11511 for ; Tue, 21 Mar 2000 21:32:37 +0200 (EET) Date: Tue, 21 Mar 2000 21:32:37 +0200 (EET) From: Ilias Sachpazidis To: stable@FreeBSD.ORG Subject: Problem with XFree86-aoutlibs-3.3.3 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-7 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, I am trying to install XFree86-aoutlibs-3.3.3 but ... I have got FreeBSD 4.0-20000320-STABLE(?) . palamas:/usr/ports/www/netscape47-communicator # make install >> communicator-v472-export.x86-unknown-freebsd.tar.gz doesn't seem to exist on this system. >> Attempting to fetch from ftp://gaia.cs.uoi.gr/pub/FreeBSD/ports/distfiles/. Receiving communicator-v472-export.x86-unknown-freebsd.tar.gz (11927015 bytes): 100% 11927015 bytes transferred in 89.9 seconds (129.50 Kbytes/s) =3D=3D=3D> Extracting for netscape-communicator-4.72 >> Checksum OK for communicator-v472-export.x86-unknown-freebsd.tar.gz. =3D=3D=3D> netscape-communicator-4.72 depends on shared library: X11.6 - = found You can make Netscape use 128-bit encryption by defining USE_128BIT =3D=3D=3D> Patching for netscape-communicator-4.72 =3D=3D=3D> Configuring for netscape-communicator-4.72 =3D=3D=3D> Installing for netscape-communicator-4.72 =3D=3D=3D> netscape-communicator-4.72 depends on file: /usr/X11R6/lib/aout/libX11.so.6.1 - not found =3D=3D=3D> Verifying install for /usr/X11R6/lib/aout/libX11.so.6.1 in /usr/ports/x11/XFree 86-aoutlibs >> Xbin.tgz doesn't seem to exist on this system. >> Attempting to fetch from ftp://gaia.cs.uoi.gr/pub/FreeBSD/ports/distfiles/. Receiving Xbin.tgz (2646694 bytes): 100% 2646694 bytes transferred in 21.1 seconds (122.64 Kbytes/s) =3D=3D=3D> Extracting for XFree86-aoutlibs-3.3.3 >> Checksum OK for Xbin.tgz. =3D=3D=3D> XFree86-aoutlibs-3.3.3 depends on shared library: X11.6 - foun= d =3D=3D=3D> Patching for XFree86-aoutlibs-3.3.3 =3D=3D=3D> Configuring for XFree86-aoutlibs-3.3.3 =3D=3D=3D> Installing for XFree86-aoutlibs-3.3.3 =3D=3D=3D> XFree86-aoutlibs-3.3.3 depends on shared library: X11.6 - foun= d cd /usr/ports/x11/XFree86-aoutlibs/work/lib; for l in $(ls lib*); do /usr/bin/env OBJ FORMAT=3Daout install -c -s -o root -g wheel -m 555 $l /usr/X11R6/lib/aout; done /usr/bin/env OBJFORMAT=3Daout /sbin/ldconfig -m /usr/X11R6/lib/aout ldconfig: =CC: trailing characters ignored ldconfig: =CC: No such file or directory ldconfig: =8BU=A0=83=C2=F6t+=8Bu=9Cf=8B>fz=F6=8Bu=A0f=89>f=8Bq=FEfr=F8f=89r=FEf=8B9f= =81=E7=FE=FFf=89:=EB=90=90=8Bu=9C=8B=8B}=A0=89f=8Bf=89=83=C2=83E=A0f=8Bf=83= =E0=83=C1=83E=9Cf=85 =C0t=C7E=B8: trailing characters ignored ldconfig: =8BU=A0=83=C2=F6t+=8Bu=9Cf=8B>fz=F6=8Bu=A0f=89>f=8Bq=FEfr=F8f=89r=FEf=8B9f= =81=E7=FE=FFf=89:=EB=90=90=8Bu=9C=8B=8B}=A0=89f=8Bf=89=83=C2=83E=A0f=8Bf=83= =E0=83=C1=83E=9Cf=85 =C0t=C7E=B8: No such file or directory ldconfig: =8Bu=C4f=89>f=8B}=E4f=89~f=8B}=D8f=81=E7=FB=FFf=89~=83=C6=89u=C4= =83E=A8=FFE=C0=8Bu=C09=B3P: trailing characters ignored ldconfig: =8Bu=C4f=89>f=8B}=E4f=89~f=8B}=D8f=81=E7=FB=FFf=89~=83=C6=89u=C4= =83E=A8=FFE=C0=8Bu=C09=B3P: No such file or directory ldconfig: 9=D1t/=90=8BA: trailing characters ignored ldconfig: 9=D1t/=90=8BA: No such file or directory ldconfig: =E8=DA=FF=FF=FF: trailing characters ignored ldconfig: =E8=DA=FF=FF=FF: No such file or directory *** Error code 255 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Any suggestion ? +-----------------------------------------------------------------------+ |Ilias Sachpazidis | | | |Network Operations Center University of Athens | | | |Department of Informatics, phone : +30 1 727 ??? | |University of Athens. fax : +30 1 727 ??? | |Panepistimioupoli, Ilissia, email : isach@noc.uoa.gr | |157 84 Athens, Greece http://www.noc.uoa.gr/~isach/ | +-----------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 11:58:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from moran.grauel.com (usr1-17.mintel.net [63.81.123.32]) by hub.freebsd.org (Postfix) with ESMTP id EDB8637B723 for ; Tue, 21 Mar 2000 11:58:27 -0800 (PST) (envelope-from rjk@moran.grauel.com) Received: (from rjk@localhost) by moran.grauel.com (8.9.3/8.9.3) id OAA05217; Tue, 21 Mar 2000 14:55:55 -0500 (EST) (envelope-from rjk) From: Richard J Kuhns MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14551.54219.482583.719000@localhost.grauel.com> Date: Tue, 21 Mar 2000 14:55:55 -0500 (EST) To: J McKitrick Cc: freebsd-stable@FreeBSD.ORG Subject: Re: zip driver In-Reply-To: <20000321172355.B63148@dogma.freebsd-uk.eu.org> References: <20000321172355.B63148@dogma.freebsd-uk.eu.org> X-Mailer: VM 6.75 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG J McKitrick writes: > I've heard there is a PR for the parallel port zip drive problem. > Does anyone know if work is being done on this yet, or if there is a > workaround to get the drive to function? As of now, vpo times out > during the boot sequence and is inaccessible. I've tinkered with the > glags for ppc, but nothing works so far. > > jm I've no idea what PR you're talking about, but I've found that my parallel port zip drive times out when the parallel port is set to `bidirectional' in the BIOS, but works without a hitch when it's set to `EPP'. I've never tried any other settings. - Rich -- Richard Kuhns rjk@grauel.com PO Box 6249 Tel: (765)477-6000 \ 100 Sawmill Road x319 Lafayette, IN 47903 (800)489-4891 / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 12: 0:24 2000 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 22B9637C08D for ; Tue, 21 Mar 2000 12:00:19 -0800 (PST) (envelope-from jcm@dogma.freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 1.92 #3) id 12XUp0-000Aw3-00; Tue, 21 Mar 2000 20:00:10 +0000 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id UAA64154; Tue, 21 Mar 2000 20:00:09 GMT (envelope-from jcm) Date: Tue, 21 Mar 2000 20:00:09 +0000 From: J McKitrick To: Richard J Kuhns Cc: freebsd-stable@FreeBSD.ORG Subject: Re: zip driver Message-ID: <20000321200009.B63620@dogma.freebsd-uk.eu.org> References: <20000321172355.B63148@dogma.freebsd-uk.eu.org> <14551.54219.482583.719000@localhost.grauel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <14551.54219.482583.719000@localhost.grauel.com>; from rjk@grauel.com on Tue, Mar 21, 2000 at 02:55:55PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 21, 2000 at 02:55:55PM -0500, Richard J Kuhns wrote: > > I've no idea what PR you're talking about, but I've found that my parallel > port zip drive times out when the parallel port is set to `bidirectional' > in the BIOS, but works without a hitch when it's set to `EPP'. We are talking about 4.0 release, correct? But i don't have EPP mode anyway, just ECP jm -- -------------------------------------------- Jonathon McKitrick -- jcm@freebsd-uk.eu.org "Doors to the pleasures of heaven or hell, and i didn't care which." -------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 12: 6: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.desktop.com (mail.desktop.com [166.90.128.242]) by hub.freebsd.org (Postfix) with ESMTP id 977BC37BE54 for ; Tue, 21 Mar 2000 12:05:59 -0800 (PST) (envelope-from clark@desktop.com) Received: (from clark@localhost) by mail.desktop.com (8.9.2/8.9.2) id MAA79378; Tue, 21 Mar 2000 12:05:44 -0800 (PST) (envelope-from clark) Date: Tue, 21 Mar 2000 12:05:44 -0800 From: Clark Shishido To: Ilias Sachpazidis Cc: freebsd-stable@freebsd.org Subject: Re: Problem with XFree86-aoutlibs-3.3.3 Message-ID: <20000321120544.B77964@desktop.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Ilias Sachpazidis on Tue, Mar 21, 2000 at 09:32:37PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 21, 2000 at 09:32:37PM +0200, Ilias Sachpazidis emailed: > > hi, I am trying to install XFree86-aoutlibs-3.3.3 but ... > I have got FreeBSD 4.0-20000320-STABLE(?) . > ... > ===> XFree86-aoutlibs-3.3.3 depends on shared library: X11.6 - found > ===> Patching for XFree86-aoutlibs-3.3.3 > ===> Configuring for XFree86-aoutlibs-3.3.3 > ===> Installing for XFree86-aoutlibs-3.3.3 > ===> XFree86-aoutlibs-3.3.3 depends on shared library: X11.6 - found > cd /usr/ports/x11/XFree86-aoutlibs/work/lib; for l in $(ls lib*); do > /usr/bin/env OBJ FORMAT=aout install -c -s -o root -g wheel -m > 555 $l /usr/X11R6/lib/aout; done > /usr/bin/env OBJFORMAT=aout /sbin/ldconfig -m /usr/X11R6/lib/aout > ldconfig: ?: trailing characters ignored > ldconfig: ?: No such file or directory > ldconfig: > ‹U ??t+‹uśf‹>fz?‹u f‰>f‹q?fr?f‰r?f‹9f???f‰:?‹uś‹‹} ‰f‹f‰?E f‹f??Eśf… > ?t?E?: trailing characters ignored > ldconfig: > ‹U ??t+‹uśf‹>fz?‹u f‰>f‹q?fr?f‰r?f‹9f???f‰:?‹uś‹‹} ‰f‹f‰?E f‹f??Eśf… > ?t?E?: No such file or directory > ldconfig: ‹u?f‰>f‹}?f‰~f‹}?f???f‰~?‰u?E¨?E?‹u?9łP: trailing characters > ignored > ldconfig: ‹u?f‰>f‹}?f‰~f‹}?f???f‰~?‰u?E¨?E?‹u?9łP: No such file or > directory > ldconfig: 9?t/‹A: trailing characters ignored > ldconfig: 9?t/‹A: No such file or directory > ldconfig: ?????: trailing characters ignored > ldconfig: ?????: No such file or directory > *** Error code 255 > > Stop. > *** Error code 1 ... I did an ftp install of 4.0-RELEASE a few days ago and ran into the same thing. move /usr/X11R6/lib/aout out of the way and create a /usr/X11R6/lib/aout directory so that the XFree86-aout port knows where to put the aout-lib files. I haven't tried it a second time on another 4.0-RELEASE installation with X from the CD yet so I don't know which part of the installation process isn't creating the directory properly. --clark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 12: 7: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (Postfix) with SMTP id F26B937B881 for ; Tue, 21 Mar 2000 12:06:58 -0800 (PST) (envelope-from vev@paprika.michvhf.com) Received: (qmail 6478 invoked by uid 1001); 21 Mar 2000 20:07:02 -0000 From: Vince Vielhaber MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14551.54886.490752.344885@paprika.michvhf.com> Date: Tue, 21 Mar 2000 15:07:02 -0500 (EST) X-Face: *0^4Iw) Cc: David Murphy , stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) In-Reply-To: <13940.953663699@zippy.cdrom.com> References: <13940.953663699@zippy.cdrom.com> X-Mailer: VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> If the regular subscribers won't get 4.x until it's 4.1 and 4.0 is >> as stable as 3.4, then why weren't we even offered the same choice >> we had with the 2.2.8->3.0 transition (get them all - and 3.0 wasn't >> all that stable). Is there a reason that 4.0 isn't being shipped as >> part of the regular stable sub? > >You are offered the same choice; all you need to do is call Walnut >Creek CDROM (or email orders@cdrom.com) and indicate your preference. >Their current plan is based purely on what we expected the >*perception* out there to be, not reality. > >- Jordan Oh, ok. I had expected mail sent out like last time. Email going to orders as soon as this one goes out. Thanks! Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com http://www.pop4.net 128K ISDN from $22.00/mo and 56K Dialup from $16.00/mo at Pop4 Networking Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 12:46:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 3AE1D37BA5D; Tue, 21 Mar 2000 12:46:39 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id MAA45020; Tue, 21 Mar 2000 12:46:39 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 21 Mar 2000 12:46:38 -0800 (PST) From: Kris Kennaway To: Mark Ovens Cc: genew@home.com, FreeBSD-STABLE Subject: Re: 3.4->4.0 ld-elf.so.1 error? In-Reply-To: <20000320211416.F236@parish> 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, 20 Mar 2000, Mark Ovens wrote: > # ldconfig -R /usr/obj/usr/src/lib/libc or something like setenv LD_LIBRARY_PATH /usr/obj/usr/src/lib/libc > # config YOUR-KERNEL-HERE Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 12:47: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 57CA737BD70 for ; Tue, 21 Mar 2000 12:47:00 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id 443DDF251; Tue, 21 Mar 2000 21:08:37 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <14317.953666745@zippy.cdrom.com> References: <14317.953666745@zippy.cdrom.com> Date: Tue, 21 Mar 2000 21:01:32 +0100 To: "Jordan K. Hubbard" From: Brad Knowles Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Cc: David Murphy , stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:25 AM -0800 2000/3/21, Jordan K. Hubbard wrote: > Which areas are these? Again, please be specific so that I can > actually respond to this rather than going "What the hell is this man > even talking about?" :-) Alright, as I get first-hand details of problems that I am personally experiencing with 4.0-STABLE, I will post them here or in -current, as I feel more appropriate. In fact, you may want to look at a message I just posted on -current with regards to vinum and rawio, although at this stage I'm at the "what the hell did I do wrong?" stage, and can't do much more than identify that there is some sort of problem. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 12:56:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from neodymium.btinternet.com (neodymium.btinternet.com [194.73.73.83]) by hub.freebsd.org (Postfix) with ESMTP id 42E9837BCFC; Tue, 21 Mar 2000 12:56:24 -0800 (PST) (envelope-from mark@ukug.uk.freebsd.org) Received: from [213.1.141.242] (helo=parish.my.domain) by neodymium.btinternet.com with esmtp (Exim 2.05 #1) id 12XVgl-0003Dz-00; Tue, 21 Mar 2000 20:55:44 +0000 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id UAA06938; Tue, 21 Mar 2000 20:55:51 GMT (envelope-from mark) Date: Tue, 21 Mar 2000 20:55:50 +0000 From: Mark Ovens To: Kris Kennaway Cc: genew@home.com, FreeBSD-STABLE Subject: Re: 3.4->4.0 ld-elf.so.1 error? Message-ID: <20000321205550.B6493@parish> References: <20000320211416.F236@parish> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from kris@freebsd.org on Tue, Mar 21, 2000 at 12:46:38PM -0800 Organization: Total lack of Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 21, 2000 at 12:46:38PM -0800, Kris Kennaway wrote: > On Mon, 20 Mar 2000, Mark Ovens wrote: > > > # ldconfig -R /usr/obj/usr/src/lib/libc > > or something like setenv LD_LIBRARY_PATH /usr/obj/usr/src/lib/libc > Why would you set LD_LIBRARY_PATH? ``ldconfig -R ....'' worked fine for me, I only needed it to build the kernel. After installworld libc.so.4 wasn't a problem. > > # config YOUR-KERNEL-HERE > > Kris > > ---- > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Seminars, n.: From "semi" and "arse", hence, any half-assed discussion. ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:mark@ukug.uk.freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 13:25:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from newton.physics.uiowa.edu (newton.physics.uiowa.edu [128.255.34.132]) by hub.freebsd.org (Postfix) with ESMTP id AE8A237B881 for ; Tue, 21 Mar 2000 13:25:31 -0800 (PST) (envelope-from sca@newton.physics.uiowa.edu) Received: (from sca@localhost) by newton.physics.uiowa.edu (8.8.8+Sun/8.8.8) id PAA08912 for stable@freebsd.org; Tue, 21 Mar 2000 15:25:29 -0600 (CST) Date: Tue, 21 Mar 2000 15:25:29 -0600 (CST) From: Scott Allendorf Message-Id: <200003212125.PAA08912@newton.physics.uiowa.edu> To: stable@freebsd.org Subject: 3.4S->4.0S upgrade: make buildworld failing Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am attempting to upgrade from 3.4-STABLE (cvsupped/built late last week) to 4.0-STABLE cvsupped this morning into a clean /usr/src. The supfile was /usr/src/share/examples/cvsup/stable-supfile with cvs-crypto uncommented and RELENG_3 changed to RELENG_4. Whenever MAKE_KERBEROS4 is uncommented in /etc/make.conf, "make buildworld" fails with the error shown below. Adding "RSAREF= YES" to /etc/make.conf does not change anything. Commenting out the MAKE_KERBEROS4 definition allows the build to complete. Is anyone else seeing this? Is it pilot error or have I stumbled onto a problem or an omission in the instructions in /usr/src/UPDATING? Cheers, Scott Script started on Tue Mar 21 13:03:32 2000 host# grep -v ^\# /etc/make.conf CFLAGS= -O -pipe COPTFLAGS= -O -pipe COMPAT1X= yes COMPAT20= yes COMPAT21= yes COMPAT22= yes HAVE_MOTIF= yes USA_RESIDENT= YES MAKE_KERBEROS4= yes SUP_UPDATE= yes SUP= /usr/local/bin/cvsup SUPFLAGS= -g -L 2 SUPFILE= /usr/local/etc/cvsup/stable-supfile SUPFILE2= /usr/local/etc/cvsup/ports-supfile TOP_TABLE_SIZE= 101 host# cd /usr/src host# ls /usr/obj host# make buildworld -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- ... All was well until ... ===> libkadm ln -sf /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/include/protos.H protos.h rm -f .depend mkdep -f .depend -a -I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/include -I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../include -I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/krb -I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kdb -I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm -I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/roken -I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb -I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm -I/usr/obj/usr/src/kerberosIV/lib/libkadm -I/usr/src/kerberosIV/lib/libkadm/../../include -DHAVE_CONFIG_H -I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -I/usr/obj/usr/src/i386/usr/include /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_cli_wrap.c /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_stream.c /usr/src/kerberosIV/lib/libkadm/..! /../../crypto/kerberosIV/lib/kadm/kadm_supp.c /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.c /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/check_password.c In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:75, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_cli_wrap.c:30: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: invalid macro name In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:78, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_cli_wrap.c:30: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: warning: `ERROR_TABLE_BASE_' redefined /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: warning: this is the location of the previous definition /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: invalid macro name In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:75, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_stream.c:38: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: invalid macro name In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:78, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_stream.c:38: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: warning: `ERROR_TABLE_BASE_' redefined /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: warning: this is the location of the previous definition /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: invalid macro name In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:75, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_supp.c:36: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: invalid macro name In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:78, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_supp.c:36: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: warning: `ERROR_TABLE_BASE_' redefined /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: warning: this is the location of the previous definition /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: invalid macro name In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:75, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/check_password.c:34: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: invalid macro name In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:78, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/check_password.c:34: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: warning: `ERROR_TABLE_BASE_' redefined /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: warning: this is the location of the previous definition /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: invalid macro name mkdep: compile failed *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. host# exit Script done on Tue Mar 21 13:19:42 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 13:55:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from atcjet.net (atcjet.net [205.139.53.1]) by hub.freebsd.org (Postfix) with ESMTP id 66CA037BCA9 for ; Tue, 21 Mar 2000 13:55:53 -0800 (PST) (envelope-from rwhipple@atcjet.net) Received: from atcjet.net ([205.139.53.70]) by atcjet.net (8.9.0/8.8.5) with ESMTP id PAA20605 for ; Tue, 21 Mar 2000 15:48:02 -0600 (CST) Message-ID: <38D7F260.BA1F7C63@atcjet.net> Date: Tue, 21 Mar 2000 16:06:24 -0600 From: Rodney Whipple Organization: ATC Communications X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Subject: bru2000 15.1 elf 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 am currently trying to get Bru2000 15.1 which is the elf version. I keep getting an error upon ./install that tells me try bru -h ...elf binary type not known use brandelf try bru.static -h ...elf binary type not know I have tried the brandelf to the file bru still the same error. Has any ran into the same thing and how do I get around it. I have tried installing the port elftoaout and still the same error. Bru still has an a.out 15.1 solution but am trying to go with the elf version since it seems the right direction. -- Thank You Rodney Whipple ATCjet.net Internet Services rwhipple@atcjet.net 1-888-565-5422 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 14:18:47 2000 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 D8E3B37BAF4 for ; Tue, 21 Mar 2000 14:18:44 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id QAA23097; Tue, 21 Mar 2000 16:18:23 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-98.max1.wa.cyberlynk.net(207.227.118.98) by peak.mountin.net via smap (V1.3) id sma023094; Tue Mar 21 16:18:10 2000 Message-Id: <4.3.2.20000321160347.00ad9b20@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Tue, 21 Mar 2000 16:17:58 -0600 To: Warner Losh From: "Jeffrey J. Mountin" Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions Cc: stable@FreeBSD.ORG In-Reply-To: <200003191820.LAA08229@harmony.village.org> References: <38D50DBC.88FA8E4D@glue.umd.edu> <38D3AB72.366D851D@glue.umd.edu> <200003152159.OAA89926@harmony.village.org> <38D03E64.3D17FC34@glue.umd.edu> <200003190433.VAA04863@harmony.village.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:20 AM 3/19/00 -0700, Warner Losh wrote: >In message <38D50DBC.88FA8E4D@glue.umd.edu> Brandon Fosdick writes: >: I thought of that, but I didn't know what the devices w/o slice numbers >: did. Guess I should have just tried it. > >Devices w/o slice numbers are the "compatibility" devices. These map >to the first BSD partition on the disk. For most people, this is the >only partition on the disk. Are you saying that da0a is (almost) functionally equivalent to da0s3a if slice 3 is the first FBSD slice. Thought they were for "dangerously dedicated" partitions. Sounds similar to da0 being the same as da0s1 for disklabel. Hmmm... Changed an fstab entry from ad1s1e to ad1e and it works. >It is a shame that you can't use them to mount / on / in an >emergency. The consistancy checks won't let you. Agreed. The few times I've needed to use a fixit floppy or CD... Let's just say it isn't fun. 8-/ --snip-- 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 Mar 21 14:19:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from student-mailhub.dcu.ie (ns.dcu.ie [136.206.1.3]) by hub.freebsd.org (Postfix) with ESMTP id EF64537BAF4 for ; Tue, 21 Mar 2000 14:19:19 -0800 (PST) (envelope-from drjolt@redbrick.dcu.ie) Received: from enigma.redbrick.dcu.ie (postfix@enigma.redbrick.dcu.ie [136.206.15.5]) by student-mailhub.dcu.ie (8.9.3/8.9.3/893-FD) with ESMTP id WAA04622 for ; Tue, 21 Mar 2000 22:19:18 GMT Received: by enigma.redbrick.dcu.ie (Postfix, from userid 2034) id B5BAF7C94; Tue, 21 Mar 2000 22:19:18 +0000 (GMT) Date: Tue, 21 Mar 2000 22:19:18 +0000 From: David Murphy To: stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Message-ID: <20000321221918.B46913@enigma.redbrick.dcu.ie> References: <20000321170118.M5367@enigma.redbrick.dcu.ie> <14078.953665429@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <14078.953665429@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Tue, Mar 21, 2000 at 11:03:49AM -0800 X-no-archive: yes Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting <14078.953665429@zippy.cdrom.com> by "Jordan K. Hubbard" : > > Well, to be perfectly honest, I don't know what the 2.X->3.X > > upgrade procedure was like, but upgrading from 3.4 to 4.0 is > > fiddly, and it > Upgrading is a different kettle of fish. I'm asking what it is > about 4.0 that you find more unstable *once it is installed*. Nothing. Having just barely escaped being completely scared off 4.0, I installed a minimal 3.4 from CD, successfully jumped through the upgrade hoops, and now have 4.0 up and running, and it seems just fine. My complaint/problem, and this may have got lost somewhere along the way, was about the upgrade process/documentation. -- When asked if it is true that he uses his wheelchair as a weapon he will reply: "That's a malicious rumour. I'll run over anyone who repeats it." Stephen Hawking - [http://www.smh.com.au/news/0001/07/features/features1.html] David Murphy - For PGP public key, send mail with Subject: send-pgp-key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 14:27:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dragonfire.penguinpowered.com (dragonfire.reno.nv.us [207.228.2.94]) by hub.freebsd.org (Postfix) with SMTP id E576037BCB8 for ; Tue, 21 Mar 2000 14:27:19 -0800 (PST) (envelope-from gibbons@dragonfire.penguinpowered.com) Received: (qmail 47646 invoked by uid 0); 21 Mar 2000 22:08:43 -0000 Received: from localhost (127.0.0.1) by localhost with SMTP; 21 Mar 2000 22:08:43 -0000 To: sca@newton.physics.uiowa.edu Cc: stable@FreeBSD.ORG Subject: Re: 3.4S->4.0S upgrade: make buildworld failing In-Reply-To: <200003212125.PAA08912@newton.physics.uiowa.edu> References: <200003212125.PAA08912@newton.physics.uiowa.edu> X-Mailer: Mew version 1.94.1 on XEmacs 21.1 (Canyonlands) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000321140843Q.gibbons@dragonfire.penguinpowered.com> Date: Tue, 21 Mar 2000 14:08:43 -0800 From: Christopher J.Gibbons X-Dispatcher: imput version 20000228(IM140) Lines: 127 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I ran into the exact same situation when I upgraded from 3.4, commenting out the KERBEROS line in make.conf does indeed cause the build to complete and you can perform the upgrade as provided in /usr/src/UPDATING. Once upgraded, I believe you can rebuild the system yet again under 4.0 and enable KERBEROS in make.conf, although I haven't tried it I think I saw it posted here before...might be an exercise for myself later tonight. ;-) Hope this helps, +----------------------------------------------------------------------- | Christopher J. Gibbons UNIX Systems Admin. gibbons@cs.unr.edu +----------------------------------------------------------------------- From: Scott Allendorf Subject: 3.4S->4.0S upgrade: make buildworld failing Date: Tue, 21 Mar 2000 15:25:29 -0600 (CST) > I am attempting to upgrade from 3.4-STABLE (cvsupped/built late last > week) to 4.0-STABLE cvsupped this morning into a clean /usr/src. The > supfile was /usr/src/share/examples/cvsup/stable-supfile with cvs-crypto > uncommented and RELENG_3 changed to RELENG_4. Whenever MAKE_KERBEROS4 is > uncommented in /etc/make.conf, "make buildworld" fails with the error > shown below. Adding "RSAREF= YES" to /etc/make.conf does not change > anything. Commenting out the MAKE_KERBEROS4 definition allows the build > to complete. Is anyone else seeing this? Is it pilot error or have I > stumbled onto a problem or an omission in the instructions in > /usr/src/UPDATING? > > Cheers, > > Scott > > Script started on Tue Mar 21 13:03:32 2000 > > host# grep -v ^\# /etc/make.conf > CFLAGS= -O -pipe > COPTFLAGS= -O -pipe > COMPAT1X= yes > COMPAT20= yes > COMPAT21= yes > COMPAT22= yes > HAVE_MOTIF= yes > USA_RESIDENT= YES > MAKE_KERBEROS4= yes > SUP_UPDATE= yes > SUP= /usr/local/bin/cvsup > SUPFLAGS= -g -L 2 > SUPFILE= /usr/local/etc/cvsup/stable-supfile > SUPFILE2= /usr/local/etc/cvsup/ports-supfile > TOP_TABLE_SIZE= 101 > > host# cd /usr/src > host# ls /usr/obj > host# make buildworld > > -------------------------------------------------------------- > >>> Rebuilding the temporary build tree > -------------------------------------------------------------- > > ... All was well until ... > > ===> libkadm > ln -sf /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/include/protos.H protos.h > rm -f .depend > mkdep -f .depend -a -I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/include -I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../include -I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/krb -I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kdb -I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm -I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/roken -I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb -I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm -I/usr/obj/usr/src/kerberosIV/lib/libkadm -I/usr/src/kerberosIV/lib/libkadm/../../include -DHAVE_CONFIG_H -I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -I/usr/obj/usr/src/i386/usr/include /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_cli_wrap.c /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_stream.c /usr/src/kerberosIV/lib/libkadm/..! > ! > /../../crypto/kerberosIV/lib/kadm/kadm_supp.c /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.c /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/check_password.c > In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:75, > from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_cli_wrap.c:30: > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: invalid macro name > In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:78, > from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_cli_wrap.c:30: > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: warning: `ERROR_TABLE_BASE_' redefined > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: warning: this is the location of the previous definition > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: invalid macro name > In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:75, > from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_stream.c:38: > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: invalid macro name > In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:78, > from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_stream.c:38: > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: warning: `ERROR_TABLE_BASE_' redefined > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: warning: this is the location of the previous definition > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: invalid macro name > In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:75, > from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_supp.c:36: > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: invalid macro name > In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:78, > from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_supp.c:36: > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: warning: `ERROR_TABLE_BASE_' redefined > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: warning: this is the location of the previous definition > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: invalid macro name > In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:75, > from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/check_password.c:34: > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: invalid macro name > In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:78, > from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/check_password.c:34: > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: warning: `ERROR_TABLE_BASE_' redefined > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: warning: this is the location of the previous definition > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: invalid macro name > mkdep: compile failed > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > host# exit > > Script done on Tue Mar 21 13:19:42 2000 > > > > 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 Tue Mar 21 14:42:48 2000 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 82A2637BD02 for ; Tue, 21 Mar 2000 14:42:41 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id QAA23313; Tue, 21 Mar 2000 16:42:26 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-98.max1.wa.cyberlynk.net(207.227.118.98) by peak.mountin.net via smap (V1.3) id sma023310; Tue Mar 21 16:42:02 2000 Message-Id: <4.3.2.20000321162831.00af09d0@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Tue, 21 Mar 2000 16:39:01 -0600 To: "Sameer R. Manek" , From: "Jeffrey J. Mountin" Subject: Re: unusual cvsup message 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 04:28 PM 3/19/00 -0800, Sameer R. Manek wrote: >I got this message on a cvsup performed today, at about Sun Mar 19 15:07:18 >PST 2000, anyone else get a similar message? and should i be concerned about >it? Not quite the same here: Should not be a problem, since the entire file is fetched. > Edit src/sys/contrib/dev/oltr/trlld.h >src/sys/contrib/dev/oltr/trlld.h: Cannot get edited text: "d" edit command >specifies line past end of base delta -- will transfer entire file Edit src/sys/contrib/dev/oltr/trlld.h Add delta 1.3.2.1 2000.03.19.00.32.34 lile src/sys/contrib/dev/oltr/trlld.h: Checksum mismatch -- will transfer entire file As of about an hour ago with virgin 4.0R (first rollese) sources. 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 Mar 21 14:49:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 214.norrgarden.se (214.norrgarden.se [195.100.133.214]) by hub.freebsd.org (Postfix) with ESMTP id E0DA637BCEB for ; Tue, 21 Mar 2000 14:49:41 -0800 (PST) (envelope-from cj@214.norrgarden.se) Received: (from cj@localhost) by 214.norrgarden.se (8.9.3/8.9.3) id XAA25891 for freebsd-stable@freebsd.org; Tue, 21 Mar 2000 23:49:38 +0100 (CET) (envelope-from cj) Date: Tue, 21 Mar 2000 23:49:37 +0100 From: Carl Johan Madestrand To: freebsd-stable@freebsd.org Subject: make world fails Message-ID: <20000321234937.A188@214.norrgarden.se> 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 cvsupped today, 4.0-STABLE, make buildworld. The compilation fails after a while. ===> rpcsvc rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/key_prot.x -o key_prot.h rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/klm_prot.x -o klm_prot.h rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/mount.x -o mount.h rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/nfs_prot.x -o nfs_prot.h rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/nlm_prot.x -o nlm_prot.h rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/rex.x -o rex.h rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/rnusers.x -o rnusers.h rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/rquota.x -o rquota.h rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/rstat.x -o rstat.h rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/rwall.x -o rwall.h rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/sm_inter.x -o sm_inter.h rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/spray.x -o spray.h unsigned hnt usec; ^^^^^^^^^^^^^^^^^^^^^^^^^ rpcgen: /usr/src/include/rpcsvc/spray.x, line 51: expected ';' *** Error code 1 Any Ideas? -- - Carl Johan Madestrand - IRC: Lord_CJ - ICQ: 46955545 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 14:53:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from student-mailhub.dcu.ie (ns.dcu.ie [136.206.1.3]) by hub.freebsd.org (Postfix) with ESMTP id C6EE837B560 for ; Tue, 21 Mar 2000 14:53:08 -0800 (PST) (envelope-from drjolt@redbrick.dcu.ie) Received: from enigma.redbrick.dcu.ie (postfix@enigma.redbrick.dcu.ie [136.206.15.5]) by student-mailhub.dcu.ie (8.9.3/8.9.3/893-FD) with ESMTP id WAA14589 for ; Tue, 21 Mar 2000 22:53:08 GMT Received: by enigma.redbrick.dcu.ie (Postfix, from userid 2034) id CF3CE7C94; Tue, 21 Mar 2000 22:53:07 +0000 (GMT) Date: Tue, 21 Mar 2000 22:53:07 +0000 From: David Murphy To: stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Message-ID: <20000321225307.C46913@enigma.redbrick.dcu.ie> References: <20000319220453.A65973@ipass.net> <005d01bf9221$4660ac60$0304020a@NENYA> <20000320153429.A1373@ipass.net> <20000321121048.E49550@enigma.redbrick.dcu.ie> <20000321141055.E5367@enigma.redbrick.dcu.ie> <20000321163707.L5367@enigma.redbrick.dcu.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from blk@skynet.be on Tue, Mar 21, 2000 at 07:00:16PM +0100 X-no-archive: yes Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting by Brad Knowles : > If that is the impression you have gotten, then I apologize. I am > not saying that 4.0 is not yet ready for installation on your > desktops and other non-production servers, in fact that is precisely > where it should be installed, and by a broader audience than it has > gotten so far. > I *am* saying that I do not think that it is ready yet for > installation on production servers, just like Solaris 8 is not yet > ready for installation on production servers. Then we're in agreement on what an X.0 release should be. I'm genuinely glad we understand each other, and would suggest that a note similar to the above in the release notes/announcement would greatly improve the new user's understanding of what X.0-RELEASE is and is not suited for/aimed at. But (there's always a but), it should be simple to find out how to upgrade from the previous release. That's my sole complaint about 4.0. -- When asked if it is true that he uses his wheelchair as a weapon he will reply: "That's a malicious rumour. I'll run over anyone who repeats it." Stephen Hawking - [http://www.smh.com.au/news/0001/07/features/features1.html] David Murphy - For PGP public key, send mail with Subject: send-pgp-key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 14:56:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 677F437B764 for ; Tue, 21 Mar 2000 14:56:22 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA24664; Tue, 21 Mar 2000 15:56:10 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA26291; Tue, 21 Mar 2000 15:55:56 -0700 (MST) Message-Id: <200003212255.PAA26291@harmony.village.org> To: "Jeffrey J. Mountin" Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions Cc: stable@FreeBSD.ORG In-reply-to: Your message of "Tue, 21 Mar 2000 16:17:58 CST." <4.3.2.20000321160347.00ad9b20@207.227.119.2> References: <4.3.2.20000321160347.00ad9b20@207.227.119.2> <38D50DBC.88FA8E4D@glue.umd.edu> <38D3AB72.366D851D@glue.umd.edu> <200003152159.OAA89926@harmony.village.org> <38D03E64.3D17FC34@glue.umd.edu> <200003190433.VAA04863@harmony.village.org> Date: Tue, 21 Mar 2000 15:55:56 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <4.3.2.20000321160347.00ad9b20@207.227.119.2> "Jeffrey J. Mountin" writes: : Are you saying that da0a is (almost) functionally equivalent to da0s3a if : slice 3 is the first FBSD slice. Thought they were for "dangerously : dedicated" partitions. No. That's not correct. While they are used in dangerously (and stupidly) dedicated mode, they can be used at any time. I still have some mount points on my -current machine that refer to sd1c because I've been too lazy to update them. : Sounds similar to da0 being the same as da0s1 for disklabel. Hmmm... Not quite. Those aren't really the same. : >It is a shame that you can't use them to mount / on / in an : >emergency. The consistancy checks won't let you. : : Agreed. The few times I've needed to use a fixit floppy or CD... : Let's just say it isn't fun. 8-/ But if you can mount it as /mnt, then you can usually fix it. :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 14:57:15 2000 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 2F72637BD70 for ; Tue, 21 Mar 2000 14:56:55 -0800 (PST) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id RAA92311 for ; Tue, 21 Mar 2000 17:57:22 -0500 (EST) (envelope-from bandix@looksharp.net) Date: Tue, 21 Mar 2000 17:57:22 -0500 (EST) From: "Brandon D. Valentine" To: FreeBSD-STABLE Subject: Re: make world fails In-Reply-To: <20000321234937.A188@214.norrgarden.se> 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, 21 Mar 2000, Carl Johan Madestrand wrote: >rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/spray.x -o spray.h > unsigned hnt usec; Last time I checked there was no type unsigned hnt in the standard library. ;-) It should read unsigned int. Not sure who's fault that is. ------------------------------------------------------------- | -Brandon D. Valentine bandix at looksharp.net | bandix on EFnet IRC BVRiker on AIM ------------------------------------------------------------- | "...and as for hackers, we note that all of those known to | The Register are so strapped financially that seizing their | property would be tantamount to squeezing blood from a | stone." -- The Register, 02/17/2000 ------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 15: 1:29 2000 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 63D8337C0BE for ; Tue, 21 Mar 2000 15:01:24 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id RAA23439; Tue, 21 Mar 2000 17:00:07 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-98.max1.wa.cyberlynk.net(207.227.118.98) by peak.mountin.net via smap (V1.3) id sma023434; Tue Mar 21 17:00:01 2000 Message-Id: <4.3.2.20000321165220.00be68a0@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Tue, 21 Mar 2000 16:59:49 -0600 To: John Reynolds~ , stable@FreeBSD.ORG From: "Jeffrey J. Mountin" Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) In-Reply-To: <14551.44129.972535.210497@hip186.ch.intel.com> References: <13387.953657029@zippy.cdrom.com> <20000321121048.E49550@enigma.redbrick.dcu.ie> <13387.953657029@zippy.cdrom.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 10:07 AM 3/21/00 -0700, John Reynolds~ wrote: >I would have to agree with Jordan here. Of course with the plethora of PC >hardware combinations out there (with some of the marginally designed >components people pick up) it is impossible for the developers to make sure >100% of everything "works as expected (TM)." > >I went through the 2.2.8->3.0 transition and now I've installed 4.0-RC, RC2, >and RC3 on the same hardware that I did the 2.2.8->3.0 transition on and I can >say without a doubt that 4.0 is a *much* better ".0" release than 3.0 was. And I will second this a few times over. >This "crypto" thing is tripping people up, but it's just a matter of RTFM, not >instability of the software. There is more tripping involved with doing a 3.x -> 4.0 source upgrade. Seems to be an endless discussion about upgrading from source and AFAICR is much more toublesome than the 2.x - 3.0 with aout -> elf. Can't see it for a production environment. Rather swap a disk or server. Less pain, problems, and much easier to keep downtime at a minimum in the event something doesn't work out right. 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 Mar 21 15: 8: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from student-mailhub.dcu.ie (ns.dcu.ie [136.206.1.3]) by hub.freebsd.org (Postfix) with ESMTP id 41D9237BD2F for ; Tue, 21 Mar 2000 15:06:59 -0800 (PST) (envelope-from drjolt@redbrick.dcu.ie) Received: from enigma.redbrick.dcu.ie (postfix@enigma.redbrick.dcu.ie [136.206.15.5]) by student-mailhub.dcu.ie (8.9.3/8.9.3/893-FD) with ESMTP id XAA10611 for ; Tue, 21 Mar 2000 23:06:49 GMT Received: by enigma.redbrick.dcu.ie (Postfix, from userid 2034) id 933AB7C94; Tue, 21 Mar 2000 23:06:49 +0000 (GMT) Date: Tue, 21 Mar 2000 23:06:49 +0000 From: David Murphy To: stable@FreeBSD.org Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Message-ID: <20000321230649.D46913@enigma.redbrick.dcu.ie> References: <20000321141055.E5367@enigma.redbrick.dcu.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@FreeBSD.org on Tue, Mar 21, 2000 at 10:49:45AM -0800 X-no-archive: yes Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting by Kris Kennaway : > > Actually, I was thinking more along the lines of commercial unix > > OSes, Sun for example, and I use this example because I'm familiar > > with them, put out an Early Access version of Solaris 8 some > > months before formally releasing Solaris 8. Effectively, this is > > the same timescale FreeBSD is going to run on, but the early > > access version is labelled -RELEASE. > No, the early-access version is labelled 4.0-RC1. If you're not > willing to jump on board during the testing phase when we say "okay, > we think this is pretty much ready unless anyone finds bugs in the > next 30 days (which turned into over 2 months in the end)", then > don't complain when 4.0 is released and you find a bug that could > have been fixed earlier. It's as simple as that - if there are bugs > we don't get alerted about during the publicized "prerelease" cycle > (and thanks to all those who *did* jump on board and help us improve > the quality of 4.0!), then they'll have to be fixed post-release. Yes, that's all fine, and although I'm sure you'd rather not believe me, I understand that perfectly well. What I *am* complaining about is people who answer "Hey, there's this bug in X.0-RELEASE" with "Well, X.0-RELEASE is out there for people who are willing to jump on board during the testing phase, didn't you know that? Fool.". Basically, I'm saying stop using the "It's a test release" justification once it goes to -RELEASE. > > As opposed to what? People staying away from x.0-RELEASE in > > droves, because they find out it's a beta, AFTER they've been > > confused by the naming policy? > As others have pointed out, it's not a "beta" - but it *is* new > technology which must be expected to have some bugs. This is the > case *all over the computer industry* - every dot-zero release has > some level of bugginess, because by definition the dot-zero means > it's got a lot of new code in it, and humans are bad programmers. > If you don't understand this reality, then you've either been conned > by the marketing apparati of big companies into thinking that > dot-zero releases only contain wonderful new features that you > really need, or you don't understand this game we're in all that > well. Yes, I know. I didn't just fall crawl out of the primordial soup and start posting to freebsd-stable - I *do* expect bugs in each and every version of each and ever OS to grace the face of the planet, but I do *not* expect to have "It's only a test release" shouted at me when I complain about something that's been -RELEASE-d. > Perhaps if we ran multimedia ads across the world and > charged people exorbitant license fees for the upgrade then they'd > be happier. > Well, at least you don't have to listen to them accuse you of being totaly fscking clueless when you dare to point out a problems post-release. -- When asked if it is true that he uses his wheelchair as a weapon he will reply: "That's a malicious rumour. I'll run over anyone who repeats it." Stephen Hawking - [http://www.smh.com.au/news/0001/07/features/features1.html] David Murphy - For PGP public key, send mail with Subject: send-pgp-key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 15: 9:34 2000 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 D10FA37BD0A for ; Tue, 21 Mar 2000 15:09:29 -0800 (PST) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id SAA92437 for ; Tue, 21 Mar 2000 18:10:05 -0500 (EST) (envelope-from bandix@looksharp.net) Date: Tue, 21 Mar 2000 18:10:05 -0500 (EST) From: "Brandon D. Valentine" To: FreeBSD-STABLE Subject: dot-0 releases In-Reply-To: <20000321225307.C46913@enigma.redbrick.dcu.ie> 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 About time this thread got its own subject line. On Tue, 21 Mar 2000, David Murphy wrote: >Then we're in agreement on what an X.0 release should be. I'm >genuinely glad we understand each other, and would suggest that a note >similar to the above in the release notes/announcement would greatly >improve the new user's understanding of what X.0-RELEASE is and is not >suited for/aimed at. From http://www.cdrom.com/titles/freebsd/bsd40offer.phtml: "FreeBSD 4.0 will probably be released in March 2000 as a fully-operational release, rather than a Snapshot. However, we don't expect all FreeBSD customers are quite ready for a major "dot-0" release so we're only offering it to those of you brave souls who REALLY want it." From http://www.freebsdmall.com/software/: "FreeBSD 4.0 - A full, professional quality, UNIX-compatible operating system. Prerelease for developers and early-adopters. Not appropriate for production-level environment yet." If you're a new user the above certainly warns you. If you're getting 4.0 via cvsup, installing over the internet or are downloading the setup files from an ftp site, chances are you also are bright enough to do a little bit of research before installing. Generalizations aside, there will always be brutes who would rather learn to wear safety goggles after something in their blue collar environment decides to go careening into their cornea. ------------------------------------------------------------- | -Brandon D. Valentine bandix at looksharp.net | bandix on EFnet IRC BVRiker on AIM ------------------------------------------------------------- | "...and as for hackers, we note that all of those known to | The Register are so strapped financially that seizing their | property would be tantamount to squeezing blood from a | stone." -- The Register, 02/17/2000 ------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 15:28:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from student-mailhub.dcu.ie (ns.dcu.ie [136.206.1.3]) by hub.freebsd.org (Postfix) with ESMTP id 189C037BCEB for ; Tue, 21 Mar 2000 15:28:32 -0800 (PST) (envelope-from drjolt@redbrick.dcu.ie) Received: from enigma.redbrick.dcu.ie (postfix@enigma.redbrick.dcu.ie [136.206.15.5]) by student-mailhub.dcu.ie (8.9.3/8.9.3/893-FD) with ESMTP id XAA11357 for ; Tue, 21 Mar 2000 23:28:25 GMT Received: by enigma.redbrick.dcu.ie (Postfix, from userid 2034) id 444D37C94; Tue, 21 Mar 2000 23:28:25 +0000 (GMT) Date: Tue, 21 Mar 2000 23:28:25 +0000 From: David Murphy To: FreeBSD-STABLE Subject: Re: dot-0 releases Message-ID: <20000321232825.E46913@enigma.redbrick.dcu.ie> References: <20000321225307.C46913@enigma.redbrick.dcu.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from bandix@looksharp.net on Tue, Mar 21, 2000 at 06:10:05PM -0500 X-no-archive: yes Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting by "Brandon D. Valentine" : > >Then we're in agreement on what an X.0 release should be. I'm > >genuinely glad we understand each other, and would suggest that a note > >similar to the above in the release notes/announcement would greatly > >improve the new user's understanding of what X.0-RELEASE is and is not > >suited for/aimed at. > >From http://www.cdrom.com/titles/freebsd/bsd40offer.phtml: > >From http://www.freebsdmall.com/software/: Those are nice clear statements, which is exactly the sort of thing I'm advocating. However, while both notices are very likely to be visible to the individual looking to purchase a CD, neither are in the normal "line of sight" for people downloading FreeBSD 4.0. My suggestion is that this be remedied, by placing such statements in the release announcement, and the release notes. I expect most people, downloaders and CD purchasers, read those. -- When asked if it is true that he uses his wheelchair as a weapon he will reply: "That's a malicious rumour. I'll run over anyone who repeats it." Stephen Hawking - [http://www.smh.com.au/news/0001/07/features/features1.html] David Murphy - For PGP public key, send mail with Subject: send-pgp-key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 15:39: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2135237BD0A for ; Tue, 21 Mar 2000 15:39:05 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA24827; Tue, 21 Mar 2000 16:39:02 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA26656; Tue, 21 Mar 2000 16:38:48 -0700 (MST) Message-Id: <200003212338.QAA26656@harmony.village.org> To: Brad Knowles Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Cc: "Jordan K. Hubbard" , David Murphy , stable@FreeBSD.ORG In-reply-to: Your message of "Tue, 21 Mar 2000 19:35:38 +0100." References: <13451.953657593@zippy.cdrom.com> Date: Tue, 21 Mar 2000 16:38:48 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Brad Knowles writes: : However, that's precisely the kind of additional work that needs : to get folded into 4.0, so that 4.1 or 4.2 *is* ready for general use : in a production environment. What, specifically, is broken in 4.0 that would preclude its use in production systems? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 15:41:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 0D9B237B910 for ; Tue, 21 Mar 2000 15:41:41 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA18279; Tue, 21 Mar 2000 15:40:29 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: David Murphy Cc: FreeBSD-STABLE Subject: Re: dot-0 releases In-reply-to: Your message of "Tue, 21 Mar 2000 23:28:25 GMT." <20000321232825.E46913@enigma.redbrick.dcu.ie> Date: Tue, 21 Mar 2000 15:40:29 -0800 Message-ID: <18276.953682029@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Those are nice clear statements, which is exactly the sort of thing > I'm advocating. However, while both notices are very likely to be Actually, those our outdated statements and I'm going to ask the Walnut Creek CDROM postmaster to remove them. They only send a confusing message. Thanks for the reminder. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 16: 3:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 83F0637BBE8 for ; Tue, 21 Mar 2000 16:03:26 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA24940 for ; Tue, 21 Mar 2000 17:03:22 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA26866 for ; Tue, 21 Mar 2000 17:03:08 -0700 (MST) Message-Id: <200003220003.RAA26866@harmony.village.org> Subject: Re: 3.4->4.0 ld-elf.so.1 error? To: FreeBSD-STABLE Date: Tue, 21 Mar 2000 17:03:08 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've updated the UPDATING document somewhat. I've moved the common items to the front, but only in 4.x stable. I've suggested using buildkernel and installkernel because that's less painful than the ldconfig vs LD_LIBRARY_PATH machinations that one would have to go through. And I've put a section in there to install modules. Please, everyon, rip it to shreds and let me know what's messed up. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 16: 8:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9A38637B819 for ; Tue, 21 Mar 2000 16:08:45 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA24968 for ; Tue, 21 Mar 2000 17:08:41 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA26930 for ; Tue, 21 Mar 2000 17:08:28 -0700 (MST) Message-Id: <200003220008.RAA26930@harmony.village.org> Subject: Re: 3.4->4.0 ld-elf.so.1 error? Cc: FreeBSD-STABLE In-reply-to: Your message of "Tue, 21 Mar 2000 17:03:08 MST." <200003220003.RAA26866@harmony.village.org> References: <200003220003.RAA26866@harmony.village.org> Date: Tue, 21 Mar 2000 17:08:27 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003220003.RAA26866@harmony.village.org> Warner Losh writes: : I've updated the UPDATING document somewhat. I've moved the common : items to the front, but only in 4.x stable. I've suggested using : buildkernel and installkernel because that's less painful than the : ldconfig vs LD_LIBRARY_PATH machinations that one would have to go : through. : : And I've put a section in there to install modules. : : Please, everyon, rip it to shreds and let me know what's messed up. I have none of the following topics in it: What do I need to change in my /etc/make.conf The KERBEROS issues that are being talked about today. mergemaster I'm looking for something fairly minimal. The docs people should likely come up with something better, maybe based on this, so that the large number of people that want to upgrade have something better than a file that started out life intending to do heads-up in -current style rather than in -stable style :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 16:13:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from firewall.symark.com (firewall.symark.westlake.iswest.net [207.178.203.34]) by hub.freebsd.org (Postfix) with ESMTP id 8367937BC7F for ; Tue, 21 Mar 2000 16:13:28 -0800 (PST) (envelope-from ggross@symark.com) Received: (from mailer@localhost) by firewall.symark.com (8.9.3/8.9.3) id QAA01811; Tue, 21 Mar 2000 16:13:21 -0800 Received: from minnow.symark.com(128.1.1.70) by firewall.symark.com via smap (V2.1/2.1+anti-relay+anti-spam) id xma001803; Tue, 21 Mar 00 16:13:09 -0800 Date: Tue, 21 Mar 2000 16:12:58 -0800 (PST) From: Glen Gross X-Sender: ggross@minnow To: "Brandon D. Valentine" Cc: FreeBSD-STABLE Subject: Re: dot-0 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 Just a quick note... despite my problems with the upgrade process, I have found the r.c. 3 snapshot to be a pleasure to install and run. It is remarkably good despite its rough edges and I think all the programmers should be commended for their excellent work. It's great to be able to install KDE and have X working right "out of the box." Glen Gross Unix Technical Support Specialist SYMARK SOFTWARE 5716 Corsa Avenue, Suite 200 Westlake Village, CA 91362 Main: 818-865-6100 FAX: 818-889-1894 http://www.symark.com Technical Support: unix-support@symark.com On Tue, 21 Mar 2000, Brandon D. Valentine wrote: > About time this thread got its own subject line. > > On Tue, 21 Mar 2000, David Murphy wrote: > > >Then we're in agreement on what an X.0 release should be. I'm > >genuinely glad we understand each other, and would suggest that a note > >similar to the above in the release notes/announcement would greatly > >improve the new user's understanding of what X.0-RELEASE is and is not > >suited for/aimed at. > > >From http://www.cdrom.com/titles/freebsd/bsd40offer.phtml: > > "FreeBSD 4.0 will probably be released in March 2000 as a > fully-operational release, rather than a Snapshot. However, we don't > expect all FreeBSD customers are quite ready for a major "dot-0" release > so we're only offering it to those of you brave souls who REALLY want > it." > > >From http://www.freebsdmall.com/software/: > > "FreeBSD 4.0 - A full, professional quality, UNIX-compatible operating > system. Prerelease for developers and early-adopters. Not appropriate > for production-level environment yet." > > If you're a new user the above certainly warns you. If you're getting 4.0 > via cvsup, installing over the internet or are downloading the > setup files from an ftp site, chances are you also are bright enough to do a > little bit of research before installing. Generalizations aside, there > will always be brutes who would rather learn to wear safety goggles > after something in their blue collar environment decides to go > careening into their cornea. > > ------------------------------------------------------------- > | -Brandon D. Valentine bandix at looksharp.net > | bandix on EFnet IRC BVRiker on AIM > ------------------------------------------------------------- > | "...and as for hackers, we note that all of those known to > | The Register are so strapped financially that seizing their > | property would be tantamount to squeezing blood from a > | stone." -- The Register, 02/17/2000 > ------------------------------------------------------------- > > > > 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 Tue Mar 21 16:27:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pobox.rwwa.com (pobox.rwwa.com [216.254.75.81]) by hub.freebsd.org (Postfix) with ESMTP id 219D737B819 for ; Tue, 21 Mar 2000 16:27:25 -0800 (PST) (envelope-from witr@rwwa.com) Received: from rwwa.com (spooky.rwwa.com [192.124.97.13]) by pobox.rwwa.com (8.9.3/8.9.3) with ESMTP id TAA16338; Tue, 21 Mar 2000 19:28:56 -0500 (EST) (envelope-from witr@rwwa.com) Message-Id: <200003220028.TAA16338@pobox.rwwa.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: stable@FreeBSD.ORG Cc: witr@pobox.rwwa.com Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) In-Reply-To: Your message of "Tue, 21 Mar 2000 10:34:59 PST." <13940.953663699@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Mar 2000 19:27:29 -0500 From: Robert Withrow Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jkh@zippy.cdrom.com said: :-> If the regular subscribers won't get 4.x until it's 4.1 and 4.0 is :-> as stable as 3.4, then why weren't we even offered the same choice :-> we had with the 2.2.8->3.0 transition (get them all - and 3.0 wasn't :-> all that stable). Is there a reason that 4.0 isn't being shipped as :-> part of the regular stable sub? :-You are offered the same choice; all you need to do is call Walnut :-Creek CDROM (or email orders@cdrom.com) and indicate your preference. :-Their current plan is based purely on what we expected the :-*perception* out there to be, not reality. Eh? To paraphrase Blind Watermellon: "Where it say that?" I didn't get any mail (or email), and I don't see this information posted on the web page or listed in the announcement... I'll be kinda upset if I don't the 4.0 CD set when I expect it via my subscription! Please point all of us to the information. --------------------------------------------------------------------- Robert Withrow, R.W. Withrow Associates, Swampscott MA, witr@rwwa.COM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 16:28:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 5A49237BCDA for ; Tue, 21 Mar 2000 16:28:38 -0800 (PST) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id QAA71408; Tue, 21 Mar 2000 16:27:33 -0800 (PST) (envelope-from Doug@gorean.org) Date: Tue, 21 Mar 2000 16:27:33 -0800 (PST) From: Doug Barton X-Sender: doug@dt051n0b.san.rr.com To: David Murphy Cc: "Jordan K. Hubbard" , stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) In-Reply-To: <20000321170118.M5367@enigma.redbrick.dcu.ie> 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, 21 Mar 2000, David Murphy wrote: > Well, to be perfectly honest, I don't know what the 2.X->3.X upgrade > procedure was like, Remarkably similar. We put the big, hairy, compatability breaking changes in the major version bumps. We have learned a few lessons from the last version upgrade cycle, some are left to be learned anew. > but upgrading from 3.4 to 4.0 is fiddly, and it > doesn't help that the instructions are counterintuitively at the > bottom of /usr/src/UPDATING which, to the untrained eye, looks like a > changelog, and lusers like me don't read changelogs to see if someone > happened to put vital instructions at the bottom of it. Caveat compiler. We NEVER suggest that lusers (or, less experienced users) upgrade from source, even for a point release. We ALWAYS tell them to upgrade from CD, or wipe their disk and do a clean install. If you choose the upgrade from source path, YOU take responsibility for adequately educating yourself. Period, end of story. Doug -- "While the future's there for anyone to change, still you know it seems, it would be easier sometimes to change the past" - Jackson Browne, "Fountain of Sorrow" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 16:34:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from melete.ch.intel.com (melete.ch.intel.com [143.182.246.25]) by hub.freebsd.org (Postfix) with ESMTP id 37C1937BE15 for ; Tue, 21 Mar 2000 16:34:24 -0800 (PST) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by melete.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.19 2000/01/29 00:15:43 dmccart Exp $) with ESMTP id AAA11147 for ; Wed, 22 Mar 2000 00:35:40 GMT Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id RAA03843 for ; Tue, 21 Mar 2000 17:33:18 -0700 (MST) X-Envelope-To: X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id TAA06983; Tue, 21 Mar 2000 19:34:23 -0500 (EST) X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14552.5390.672257.480799@hip186.ch.intel.com> Date: Tue, 21 Mar 2000 17:34:22 -0700 (MST) To: stable@freebsd.org Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) In-Reply-To: <200003220028.TAA16338@pobox.rwwa.com> References: <13940.953663699@zippy.cdrom.com> <200003220028.TAA16338@pobox.rwwa.com> X-Mailer: VM 6.75 under Emacs 20.3.11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Tuesday, March 21, Robert Withrow wrote: ] > > :-You are offered the same choice; all you need to do is call Walnut > :-Creek CDROM (or email orders@cdrom.com) and indicate your preference. > :-Their current plan is based purely on what we expected the > :-*perception* out there to be, not reality. > > Eh? To paraphrase Blind Watermellon: "Where it say that?" > > I didn't get any mail (or email), and I don't see this information posted > on the web page or listed in the announcement... I'll be kinda upset if > I don't the 4.0 CD set when I expect it via my subscription! > > Please point all of us to the information. As will a lot of other people I'm sure ... I mailed orders@cdrom.com a while ago about this and they told me since I'd talked to them than 4.0 would be shipped to me via the subscription--I hope they don't foobar it ... Whatever the "default policy" for 4.0 is going to be, they should at least post it to freebsd-announce with a pointer saying "to change this, call us at 1-800-whatever" .... -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 16:39:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 2D3E337BA9B for ; Tue, 21 Mar 2000 16:39:24 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA18576; Tue, 21 Mar 2000 16:39:07 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Robert Withrow Cc: stable@FreeBSD.ORG, witr@pobox.rwwa.com Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) In-reply-to: Your message of "Tue, 21 Mar 2000 19:27:29 EST." <200003220028.TAA16338@pobox.rwwa.com> Date: Tue, 21 Mar 2000 16:39:06 -0800 Message-ID: <18573.953685546@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hold the presses. I'm talking with Walnut Creek CDROM right now about just sending 4.0 to the subscribers after all. You're about the 2000th person to ask me. :) - Jordan > > jkh@zippy.cdrom.com said: > :-> If the regular subscribers won't get 4.x until it's 4.1 and 4.0 is > :-> as stable as 3.4, then why weren't we even offered the same choice > :-> we had with the 2.2.8->3.0 transition (get them all - and 3.0 wasn't > :-> all that stable). Is there a reason that 4.0 isn't being shipped as > :-> part of the regular stable sub? > > :-You are offered the same choice; all you need to do is call Walnut > :-Creek CDROM (or email orders@cdrom.com) and indicate your preference. > :-Their current plan is based purely on what we expected the > :-*perception* out there to be, not reality. > > Eh? To paraphrase Blind Watermellon: "Where it say that?" > > I didn't get any mail (or email), and I don't see this information posted > on the web page or listed in the announcement... I'll be kinda upset if > I don't the 4.0 CD set when I expect it via my subscription! > > Please point all of us to the information. > > > --------------------------------------------------------------------- > Robert Withrow, R.W. Withrow Associates, Swampscott MA, witr@rwwa.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 Tue Mar 21 16:43:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from charon.ipass.net (charon.ipass.net [198.79.53.8]) by hub.freebsd.org (Postfix) with ESMTP id F339337BECF; Tue, 21 Mar 2000 16:43:09 -0800 (PST) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-1-66.dialup.rdu.ipass.net [209.170.132.66]) by charon.ipass.net (8.9.3/8.9.3) with ESMTP id TAA08283; Tue, 21 Mar 2000 19:42:49 -0500 (EST) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id TAA01592; Tue, 21 Mar 2000 19:45:10 -0500 (EST) (envelope-from rhh) Date: Tue, 21 Mar 2000 19:45:09 -0500 From: Randall Hopper To: Brad Knowles Cc: stable@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Message-ID: <20000321194509.A1273@ipass.net> References: <200003191838.KAA40955@rah.star-gate.com> <000701bf91d5$4aebeb60$0304020a@NENYA> <001a01bf91c1$7f62a4b0$0304020a@NENYA> <200003191838.KAA40955@rah.star-gate.com> <20000319220453.A65973@ipass.net> <005d01bf9221$4660ac60$0304020a@NENYA> <20000320153429.A1373@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from blk@skynet.be on Tue, Mar 21, 2000 at 10:41:07AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles: |At 3:34 PM -0500 2000/3/20, Randall Hopper wrote: | |> From what I hear, it sounds like we need some more testing time too. | | Yeah, we do. This is what an x.0-RELEASE is all about. The ... | However, IMO anyone using an x.0-RELEASE on a production box |basically gets what they deserve. This is more appropriate for |development/test/play boxes, ... ... |This is *why* they're getting an x.0-RELEASE out now, so that a wider |community of people with more unusual hardware and applications *can* |see it, and report the bugs back so that these problems can be fixed. ... |It has been stated many times over that -CURRENT isn't guaranteed to do |anything (including compile or run), except have a higher probability of |toasting your machine and your application. ... | If you want to play with x.0-RELEASE, you have to realize that |there are some rough spots and some sharp edges that have not yet |been detected, or if they have been detected they haven't yet been |dealt with. So again, you have to be prepared for the possibility of |being cut. I appreciate your response. I think we're talking the same language. The main new piece of information to me that you mentioned (somewhat of a surprise in fact) is that x.0-RELEASE is really only for "development/test/play" boxes (and thus really a -CURRENT) and not for production and user's-primary-PC boxes at home. I wasn't aware of this, but I appreciate you filling me in. In general, is this true just for the x.0-RELEASE, or for x.*-RELEASE where x is the latest version in CMS (just as 4.x is now)? That is, what is the view of core on this in terms of planning a feature set and stability target for a -RELEASE? Thanks, Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 16:51:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from minubian.houabg.com (minubian.houabg.com [206.109.247.11]) by hub.freebsd.org (Postfix) with ESMTP id 65AAD37BB6E for ; Tue, 21 Mar 2000 16:51:41 -0800 (PST) (envelope-from dchapman@houabg.com) Received: from houcbs2.houabg.com (mailhost.houabg.com [206.109.247.20]) by minubian.houabg.com (8.8.8/8.8.8) with ESMTP id TAA09977 for ; Tue, 21 Mar 2000 19:40:06 -0600 (CST) (envelope-from dchapman@houabg.com) Received: from 216-118-21-147.pdq.net by houcbs2.houabg.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1457.7) id GP4JPBAY; Tue, 21 Mar 2000 18:58:47 -0600 Message-ID: <010201bf9399$21158100$931576d8@inethouston.net> From: "David W. Chapman Jr." To: "Randall Hopper" Cc: References: <200003191838.KAA40955@rah.star-gate.com> <000701bf91d5$4aebeb60$0304020a@NENYA> <001a01bf91c1$7f62a4b0$0304020a@NENYA> <200003191838.KAA40955@rah.star-gate.com> <20000319220453.A65973@ipass.net> <005d01bf9221$4660ac60$0304020a@NENYA> <20000320153429.A1373@ipass.net> <20000321194509.A1273@ipass.net> Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Date: Tue, 21 Mar 2000 18:54:07 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is common practice for any operating system. Any x.0 version of any operating system should not be used in a production system until major bugs are found and fixed. ----- Original Message ----- From: "Randall Hopper" To: "Brad Knowles" Cc: ; Sent: Tuesday, March 21, 2000 6:45 PM Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) > Brad Knowles: > |At 3:34 PM -0500 2000/3/20, Randall Hopper wrote: > | > |> From what I hear, it sounds like we need some more testing time too. > | > | Yeah, we do. This is what an x.0-RELEASE is all about. The > ... > | However, IMO anyone using an x.0-RELEASE on a production box > |basically gets what they deserve. This is more appropriate for > |development/test/play boxes, ... > ... > |This is *why* they're getting an x.0-RELEASE out now, so that a wider > |community of people with more unusual hardware and applications *can* > |see it, and report the bugs back so that these problems can be fixed. > ... > > |It has been stated many times over that -CURRENT isn't guaranteed to do > |anything (including compile or run), except have a higher probability of > |toasting your machine and your application. > ... > | If you want to play with x.0-RELEASE, you have to realize that > |there are some rough spots and some sharp edges that have not yet > |been detected, or if they have been detected they haven't yet been > |dealt with. So again, you have to be prepared for the possibility of > |being cut. > > I appreciate your response. I think we're talking the same language. > > The main new piece of information to me that you mentioned (somewhat of a > surprise in fact) is that x.0-RELEASE is really only for > "development/test/play" boxes (and thus really a -CURRENT) and not for > production and user's-primary-PC boxes at home. I wasn't aware of this, > but I appreciate you filling me in. > > In general, is this true just for the x.0-RELEASE, or for x.*-RELEASE where > x is the latest version in CMS (just as 4.x is now)? That is, what is the > view of core on this in terms of planning a feature set and stability > target for a -RELEASE? > > Thanks, > > Randall > > > > 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 Tue Mar 21 16:58: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 8F03437BECF; Tue, 21 Mar 2000 16:58:01 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA18690; Tue, 21 Mar 2000 16:58:09 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Randall Hopper Cc: Brad Knowles , stable@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) In-reply-to: Your message of "Tue, 21 Mar 2000 19:45:09 EST." <20000321194509.A1273@ipass.net> Date: Tue, 21 Mar 2000 16:58:09 -0800 Message-ID: <18687.953686689@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The main new piece of information to me that you mentioned (somewhat of a > surprise in fact) is that x.0-RELEASE is really only for > "development/test/play" boxes (and thus really a -CURRENT) and not for > production and user's-primary-PC boxes at home. I wasn't aware of this, > but I appreciate you filling me in. Sorry, I wouldn't take that as gospel any longer either. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 16:59:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 5650937BB6E for ; Tue, 21 Mar 2000 16:59:30 -0800 (PST) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id QAA71649; Tue, 21 Mar 2000 16:58:34 -0800 (PST) (envelope-from Doug@gorean.org) Date: Tue, 21 Mar 2000 16:58:34 -0800 (PST) From: Doug Barton X-Sender: doug@dt051n0b.san.rr.com To: Brad Knowles Cc: "Jordan K. Hubbard" , David Murphy , stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) 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, 21 Mar 2000, Brad Knowles wrote: > At 8:53 AM -0800 2000/3/21, Jordan K. Hubbard wrote: > > > Actually, it's my understanding that Yahoo already has 4.0 in > > production. For those that aren't aware, I am a Yahoo! employee, and here in San Diego we've been using 4.0 for 8 months. We were on the bleeding edge of the NFS fixes, and I was able to help out (in a small way) by testing source in a real world, heavy NFS environment. Of course, all of the credit for the fixes goes to Matt (et al), I just tested stuff. :) In Santa Clara (Yahoo!'s corporate HQ) most of the stuff is still 3.x, but I'm told that some of the production stuff is moving to 4.0 now. > However, that doesn't mean that I believe that 4.0 is ready for > general use in a production environment. > > IMO, the guys at Yahoo! know enough about systems like this (and > probably helped write goodly portions of them) that they can take OS > versions that are not quite ready for general use in a production > environment, and they can make them ready. Well, thank you. :) I would say that for the most part I agree with Jordan in the sense that once you have it installed, 4.0 is just as stable as 3.x, in about 80% of the cases. It's the edge cases that need work, like unusual hardware configurations, etc. If you install it and it works, there is no need to fear it blowing up on you unexpectedly. That said, you should treat this like any other software upgrade from any other vendor. Put it on a test machine first, and gradually increase the load till you're up to capacity. That's just responsible system administration. We can only test the system on configurations we have. You've mentioned Sun several times. Back in my company's pre-Yahoo! days we beat the snot out of our sun web servers, doing things that were mentioned in the documentation, but no one had ever done exactly the way we were doing them. At the risk of sounding immodest, many of the special, custom-rolled solaris 2.5 patches that sun developed specifically for us ended up in the gold version of solaris 2.6. Same situation exactly, and no different because it was a "commercial" product. What's my point? Simply that this is the most -release worthy .0 version I've seen in 3 major version upgrades, and I'm proud to be associated with it. The bugs that are left (and of course, there are some) are the kinds of things that can only be found through more extensive use, which will only come if we encourage people, rather than discourage them. :) Doug PS, Although I wish it weren't necessary, just in case someone gets a wild hair... "My opinions are mine, and mine alone. Nothing I say now, have said in the past, or will say in the future represents the official position of Yahoo!, Inc. in any way shape or form." Yadda yadda. -- "While the future's there for anyone to change, still you know it seems, it would be easier sometimes to change the past" - Jackson Browne, "Fountain of Sorrow" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 17: 4:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dragonfire.penguinpowered.com (dragonfire.reno.nv.us [207.228.2.94]) by hub.freebsd.org (Postfix) with SMTP id 9525A37BCE1 for ; Tue, 21 Mar 2000 17:04:44 -0800 (PST) (envelope-from gibbons@dragonfire.penguinpowered.com) Received: (qmail 48614 invoked by uid 0); 22 Mar 2000 01:04:37 -0000 Received: from localhost (127.0.0.1) by localhost with SMTP; 22 Mar 2000 01:04:37 -0000 To: imp@village.org Cc: stable@FreeBSD.ORG Subject: Re: 3.4->4.0 ld-elf.so.1 error? In-Reply-To: <200003220008.RAA26930@harmony.village.org> References: <200003220003.RAA26866@harmony.village.org> <200003220008.RAA26930@harmony.village.org> X-Mailer: Mew version 1.94.1 on XEmacs 21.1 (Canyonlands) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000321170437K.gibbons@dragonfire.penguinpowered.com> Date: Tue, 21 Mar 2000 17:04:37 -0800 From: Christopher J.Gibbons X-Dispatcher: imput version 20000228(IM140) Lines: 67 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner, Something like this might help (would have helped me when I did my upgrade from 3.4) in /usr/src/UPDATING: (feel free to include/exclude/edit/shred) If you are using Kerberos, and before running the make buildworld command comment out the line that reads MAKE_KERBEROS4=yes in /etc/make.conf. Secondly, comment out the linux_enable=yes in /etc/rc.conf <-- that one got me first time through, thank goodness for backups. ;-) Once 4.0 is running and completely installed uncomment the MAKE_KERBEROS4=yes in /etc/make.conf. Run make buildworld again to build the kerberized version and then go about the usual steps for re-installing the OS from source. Basically, one is simply re-building and re-installing 4.0 a second time to get kerberos to build and install properly. This is also a good time to uncomment linux_enable=yes in /etc/rc.conf if linux emulation is so desired. Of course, _The_Better_Way_ would be to fix the 4.0 KerberosIV portion so it compiles under 3.4; however, that may not be an option simply because of the quasi-3.4/4.0 state when it builds. Hope this helps, /----------------------------------------------------------------------- | Christopher J. Gibbons UNIX Systems Admin. gibbons@cs.unr.edu |----------------------------------------------------------------------- | "Discovered that neither the Mossad nor Cuba were willing to pay a | living wage for computer espionage. Fell into System Administration." \----------------------------------------------------------------------- From: Warner Losh Subject: Re: 3.4->4.0 ld-elf.so.1 error? Date: Tue, 21 Mar 2000 17:08:27 -0700 > In message <200003220003.RAA26866@harmony.village.org> Warner Losh writes: > : I've updated the UPDATING document somewhat. I've moved the common > : items to the front, but only in 4.x stable. I've suggested using > : buildkernel and installkernel because that's less painful than the > : ldconfig vs LD_LIBRARY_PATH machinations that one would have to go > : through. > : > : And I've put a section in there to install modules. > : > : Please, everyon, rip it to shreds and let me know what's messed up. > > I have none of the following topics in it: > What do I need to change in my /etc/make.conf > The KERBEROS issues that are being talked about today. > mergemaster > > I'm looking for something fairly minimal. The docs people should > likely come up with something better, maybe based on this, so that the > large number of people that want to upgrade have something better than > a file that started out life intending to do heads-up in -current > style rather than in -stable style :-) > > Warner > > > 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 Tue Mar 21 17:15:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 538A737C010 for ; Tue, 21 Mar 2000 17:15:14 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA25208; Tue, 21 Mar 2000 18:15:12 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA27430; Tue, 21 Mar 2000 18:14:58 -0700 (MST) Message-Id: <200003220114.SAA27430@harmony.village.org> To: "Christopher J. Gibbons" Subject: Re: 3.4->4.0 ld-elf.so.1 error? Cc: stable@FreeBSD.ORG In-reply-to: Your message of "Tue, 21 Mar 2000 17:04:37 PST." <20000321170437K.gibbons@dragonfire.penguinpowered.com> References: <20000321170437K.gibbons@dragonfire.penguinpowered.com> <200003220003.RAA26866@harmony.village.org> <200003220008.RAA26930@harmony.village.org> Date: Tue, 21 Mar 2000 18:14:58 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000321170437K.gibbons@dragonfire.penguinpowered.com> "Christopher J. Gibbons" writes: : Something like this might help (would have helped me when I did my upgrade : from 3.4) in /usr/src/UPDATING: (feel free to include/exclude/edit/shred) : : If you are using Kerberos, and before running the make buildworld command : comment out the line that reads MAKE_KERBEROS4=yes in /etc/make.conf. OK. : Secondly, comment out the linux_enable=yes in /etc/rc.conf <-- that one : got me first time through, thank goodness for backups. ;-) This is no longer necessary, since I've added install new modules to the list :-) : Once 4.0 is running and completely installed uncomment the : MAKE_KERBEROS4=yes in /etc/make.conf. Run make buildworld again : to build the kerberized version and then go about the usual steps : for re-installing the OS from source. Basically, one is simply : re-building and re-installing 4.0 a second time to get kerberos : to build and install properly. : : This is also a good time to uncomment linux_enable=yes in : /etc/rc.conf if linux emulation is so desired. : : Of course, _The_Better_Way_ would be to fix the 4.0 KerberosIV portion so it : compiles under 3.4; however, that may not be an option simply because of the : quasi-3.4/4.0 state when it builds. OK. Thanks for the info. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 17:37:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dns.sunline.net (dns.sunline.net [207.30.56.2]) by hub.freebsd.org (Postfix) with ESMTP id B9BBB37BDD0 for ; Tue, 21 Mar 2000 17:37:32 -0800 (PST) (envelope-from scorpio@sunline.net) Received: from jeff.sunline.net (jeff.sunline.net [207.30.56.254]) by dns.sunline.net (8.8.8/8.8.8) with ESMTP id UAA19591 for ; Tue, 21 Mar 2000 20:34:18 -0500 (EST) Message-Id: <4.3.0.20000321203146.00a78940@mail.afcon.net> X-Sender: drkshdw@mail.afcon.net X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Tue, 21 Mar 2000 20:32:28 -0500 To: freebsd-stable@freebsd.org From: Jeff Palmer Subject: Re: dot-0 releases 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 Pardon me if I make an idiot of myself.. But the whole "debate" (for lack of a better term) seems to be about 4.0-STABLE being STABLE. Seems to me that if it's not meant for production machines, it probably should be -RELEASE or -RC as opposed to -STABLE I would say the label "-STABLE" should mean it's golden, ready to go. -RC would mean it's doing pretty well, more people can trust it, but not quite production machine ready.. -RELEASE would mean please play with it, and report any bugs, it shouldn't crash on you, or make you reformat, but it's not really for everyone.. -CURRENT would be like "not for the weak" expect problems, and possibly reformats.. unless you are good enough with unix/programming to debug error messages. For those of you who are questioning, these are my interpretations of what the labels SHOULD mean, and not reality.. Something labeled "STABLE" in my definition would mean ready for mass market So maybe the switch to 4.0-STABLE was premature? just my two cents.. Jeff Palmer scorpio@sunline.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 17:45:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.ddg.com (eunuch.ddg.com [216.30.58.66]) by hub.freebsd.org (Postfix) with ESMTP id 81C7A37C006 for ; Tue, 21 Mar 2000 17:45:16 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from nomad.dataplex.net (24.28.73.209) by mail.ddg.com with SMTP (Eudora Internet Mail Server 2.1); Tue, 21 Mar 2000 19:45:03 -0600 From: Richard Wackerbarth To: "Jordan K. Hubbard" Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Date: Tue, 21 Mar 2000 19:38:42 -0600 X-Mailer: KMail [version 1.0.29] Content-Type: text/plain Cc: stable@FreeBSD.ORG References: <13387.953657029@zippy.cdrom.com> In-Reply-To: <13387.953657029@zippy.cdrom.com> MIME-Version: 1.0 Message-Id: <00032119450200.18784@nomad.dataplex.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 21 Mar 2000, Jordan K. Hubbard wrote: > Actually, the problem is that we ARE now doing good quality "dot-zero" > releases IMHO, the problen is not so much the -RELEASE as it is the -STABLE which preceeded it. I think we should continue to call 4.0 -CURRENT for a while and change it to -STABLE only when we have enough tire kicking that we can, in confidence, tell anyone to install it on their production system. (Perhaps just before 4.1 comes out). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 17:54:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 45B1737B6D2 for ; Tue, 21 Mar 2000 17:54:08 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id 3DA79DE13; Wed, 22 Mar 2000 01:15:53 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <18276.953682029@zippy.cdrom.com> References: <18276.953682029@zippy.cdrom.com> Date: Wed, 22 Mar 2000 01:11:20 +0100 To: "Jordan K. Hubbard" , David Murphy From: Brad Knowles Subject: Re: dot-0 releases Cc: FreeBSD-STABLE Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 3:40 PM -0800 2000/3/21, Jordan K. Hubbard wrote: > Actually, those our outdated statements and I'm going to ask the > Walnut Creek CDROM postmaster to remove them. They only send a > confusing message. Thanks for the reminder. :) So, you're saying that it's perfectly safe for me to replace the one and only news peering server that we have (currently running 3.x) with one running 4.0-RELEASE, and if we have any problems then you'll personally fly out here to fix it? ;-) I hope you'll forgive me if I tend to be slightly more conservative than this, and if I recommend that others do the same. We're not all clones of David Greenman, Jordan K. Hubbard, or Mike O'Dell. ;-) -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 18:15:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from student-mailhub.dcu.ie (ns.dcu.ie [136.206.1.3]) by hub.freebsd.org (Postfix) with ESMTP id 914C337B9D0 for ; Tue, 21 Mar 2000 18:15:07 -0800 (PST) (envelope-from drjolt@redbrick.dcu.ie) Received: from enigma.redbrick.dcu.ie (postfix@enigma.redbrick.dcu.ie [136.206.15.5]) by student-mailhub.dcu.ie (8.9.3/8.9.3/893-FD) with ESMTP id CAA12513 for ; Wed, 22 Mar 2000 02:15:05 GMT Received: by enigma.redbrick.dcu.ie (Postfix, from userid 2034) id E56217C94; Wed, 22 Mar 2000 01:54:00 +0000 (GMT) Date: Wed, 22 Mar 2000 01:54:00 +0000 From: David Murphy To: stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Message-ID: <20000322015400.B34538@enigma.redbrick.dcu.ie> References: <20000321170118.M5367@enigma.redbrick.dcu.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from Doug@gorean.org on Tue, Mar 21, 2000 at 04:27:33PM -0800 X-no-archive: yes Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting by Doug Barton : > > but upgrading from 3.4 to 4.0 is fiddly, and it > > doesn't help that the instructions are counterintuitively at the > > bottom of /usr/src/UPDATING which, to the untrained eye, looks like a > > changelog, and lusers like me don't read changelogs to see if someone > > happened to put vital instructions at the bottom of it. > Caveat compiler. We NEVER suggest that lusers (or, less > experienced users) upgrade from source, even for a point release. We > ALWAYS tell them to upgrade from CD, or wipe their disk and do a clean > install. If you choose the upgrade from source path, YOU take > responsibility for adequately educating yourself. Period, end of story. Where, where, WHERE the F*** do "WE" say that? I'm stupid, point it out to me. REERENCE the blindingly obvious piece of documentation I so obviously missed. $50 Amazon gift certificate thing to the first person that points out where on www.freebsd.org this is clearly stated. No, refernces to mailing list postings won't do - I want to see where a perfectly ordinary intelligent sysadmin new to FreeBSD would find this information. Go on, I fscking DARE somebody. -- When asked if it is true that he uses his wheelchair as a weapon he will reply: "That's a malicious rumour. I'll run over anyone who repeats it." Stephen Hawking - [http://www.smh.com.au/news/0001/07/features/features1.html] David Murphy - For PGP public key, send mail with Subject: send-pgp-key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 18:26:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from student-mailhub.dcu.ie (ns.dcu.ie [136.206.1.3]) by hub.freebsd.org (Postfix) with ESMTP id 1A57737BD6A for ; Tue, 21 Mar 2000 18:26:12 -0800 (PST) (envelope-from drjolt@redbrick.dcu.ie) Received: from enigma.redbrick.dcu.ie (postfix@enigma.redbrick.dcu.ie [136.206.15.5]) by student-mailhub.dcu.ie (8.9.3/8.9.3/893-FD) with ESMTP id CAA17493; Wed, 22 Mar 2000 02:24:51 GMT Received: by enigma.redbrick.dcu.ie (Postfix, from userid 2034) id 821237C94; Wed, 22 Mar 2000 02:24:52 +0000 (GMT) Date: Wed, 22 Mar 2000 02:24:52 +0000 From: David Murphy To: Doug@gorean.org Cc: freebsd-stable@freebsd.org Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Message-ID: <20000322022452.C34538@enigma.redbrick.dcu.ie> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from Doug@gorean.org on Tue, Mar 21, 2000 at 04:58:34PM -0800 X-no-archive: yes Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting by Doug Barton : > You've mentioned Sun several times. Back in my company's pre-Yahoo! > days we beat the snot out of our sun web servers, doing things that > were mentioned in the documentation, but no one had ever done > exactly the way we were doing them. At the risk of sounding > immodest, many of the special, custom-rolled solaris 2.5 patches > that sun developed specifically for us ended up in the gold version > of solaris 2.6. Same situation exactly, and no different because it > was a "commercial" product. Yes, Solaris 2.5.1 was a disaster as a web server. It was more-or-less the first release of Solaris exposed to 'real' levels of web traffic, and they found out they had a lot of work to do to make it a viable web serving platform. They had to make a lot of changes, you got a lot of custom patches, and they were later integrated into a later version of Solaris. As you say, no different because it was a commercial product. No doubt, you had some hassle convincing them it needed fixing, you had to quantify your problem to the Sun support people, etc. The difference, I hope is that you weren't expected to justify your basic eligibility to posess a copy of Solaris, or your right to suggest that it had a problem, or even your right to whine when something was broken that should not have been. > What's my point? Simply that this is the most -release worthy .0 > version I've seen in 3 major version upgrades, and I'm proud to be > associated with it. The bugs that are left (and of course, there are > some) are the kinds of things that can only be found through more > extensive use, which will only come if we encourage people, rather > than discourage them. :) Well, I personally have been using FreeBSD on and off since 2.1-R, and yes, that means I am not and was not a regular tracker of -stable, and was always a great proponent of it, but quite frankly, my recent experiences with it have caused me to seriously question my sanity in going anywhere near it, and that has nothing to do with the quality of the software. Think about that. At the end of the day, if you're not a kernel hacker, hell, if you're not a hacker of any shape or form, it doesn't matter a whit whether you have the source code or not. It hardly matters that you get the OS for free when the alternative is paying a few dollars for a Solaris licence on a seven figure equipment order. The difference used to be that you could get technically expert, friendly, email support from the free OSes, but these days that's gone right out the window, so if I'm paying for support, I may as well pay for people that are paid to give me some credit for having a clue, as well as knowing their own stuff. -- When asked if it is true that he uses his wheelchair as a weapon he will reply: "That's a malicious rumour. I'll run over anyone who repeats it." Stephen Hawking - [http://www.smh.com.au/news/0001/07/features/features1.html] David Murphy - For PGP public key, send mail with Subject: send-pgp-key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 18:36:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 1D07137C174; Tue, 21 Mar 2000 18:36:25 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id SAA84076; Tue, 21 Mar 2000 18:36:25 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 21 Mar 2000 18:36:25 -0800 (PST) From: Kris Kennaway To: David Murphy Cc: Doug@gorean.org, freebsd-stable@freebsd.org Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) In-Reply-To: <20000322022452.C34538@enigma.redbrick.dcu.ie> 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, 22 Mar 2000, David Murphy wrote: > that you could get technically expert, friendly, email support from > the free OSes, but these days that's gone right out the window, so if > I'm paying for support, I may as well pay for people that are paid to > give me some credit for having a clue, as well as knowing their own > stuff. If you don't like the quality of free FreeBSD support, pay for a FreeBSD support contract. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 18:48:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from student-mailhub.dcu.ie (ns.dcu.ie [136.206.1.3]) by hub.freebsd.org (Postfix) with ESMTP id 8787D37BD7C for ; Tue, 21 Mar 2000 18:47:56 -0800 (PST) (envelope-from drjolt@redbrick.dcu.ie) Received: from enigma.redbrick.dcu.ie (postfix@enigma.redbrick.dcu.ie [136.206.15.5]) by student-mailhub.dcu.ie (8.9.3/8.9.3/893-FD) with ESMTP id CAA19012 for ; Wed, 22 Mar 2000 02:47:40 GMT Received: by enigma.redbrick.dcu.ie (Postfix, from userid 2034) id 745FF7C94; Wed, 22 Mar 2000 02:45:50 +0000 (GMT) Date: Wed, 22 Mar 2000 02:45:50 +0000 From: David Murphy To: freebsd-stable@FreeBSD.org Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Message-ID: <20000322024550.D34538@enigma.redbrick.dcu.ie> References: <20000322022452.C34538@enigma.redbrick.dcu.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@FreeBSD.org on Tue, Mar 21, 2000 at 06:36:25PM -0800 X-no-archive: yes Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting by Kris Kennaway : > On Wed, 22 Mar 2000, David Murphy wrote: > > that you could get technically expert, friendly, email support > > from the free OSes, but these days that's gone right out the > > window, so if I'm paying for support, I may as well pay for people > > that are paid to give me some credit for having a clue, as well as > > knowing their own stuff. > If you don't like the quality of free FreeBSD support, pay for a > FreeBSD support contract. Could do that. Could just use the support contract I've got already, for Solaris, and implement anything mission-critical on Solaris. Path of least hassle? -- When asked if it is true that he uses his wheelchair as a weapon he will reply: "That's a malicious rumour. I'll run over anyone who repeats it." Stephen Hawking - [http://www.smh.com.au/news/0001/07/features/features1.html] David Murphy - For PGP public key, send mail with Subject: send-pgp-key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 18:56: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail5.uunet.ca (mail5.uunet.ca [142.77.1.28]) by hub.freebsd.org (Postfix) with ESMTP id 71F4237BFF1 for ; Tue, 21 Mar 2000 18:55:58 -0800 (PST) (envelope-from matt@ARPA.MAIL.NET) Received: from epsilon.lucida.qc.ca ([216.95.146.6]) by mail5.uunet.ca with ESMTP id <232983-3897>; Tue, 21 Mar 2000 21:57:02 -0500 Date: Tue, 21 Mar 2000 21:54:24 -0500 From: Matt Heckaman X-Sender: matt@epsilon.lucida.qc.ca To: FreeBSD-STABLE Subject: Problem with ad* driver. Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1803559075-953693664=:319" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1803559075-953693664=:319 Content-Type: TEXT/PLAIN; charset=US-ASCII I'm still having a problem with the ad driver, this is under 4.0-STABLE cvsupped about 4 hours ago, in an attempt to solve this problem. This is, I believe, what Jordan re-rolled 4.0-R for, and he said it was fixed in stable as well so.. Here's what I get for example: root[epsilon]:~# fdisk /dev/ad1 fdisk: can't open device /dev/ad1 fdisk: cannot open disk /dev/ad1: Input/output error [same error for disklabel, mount, anything] [from dmesg] ad1: HARD READ ERROR blk# 0ata0-slave: WARNING: WAIT_READY active=ATA_ACTIVE_ATA ad1: HARD READ ERROR blk# 0 status=59 error=04 ad1: DMA problem fallback to PIO mode ad1: reading primary partition table: error reading fsbn 0 [my relevent dmesg] ad0: 8063MB [16383/16/63] at ata0-master using UDMA33 ad1: 1549MB [3148/16/63] at ata0-slave using WDMA2 acd0: CDROM at ata1-master using PIO4 [ ls -l /dev/ad1* ] crw-r----- 1 root operator 116, 0x0001000a Mar 21 21:14 /dev/ad1 crw-r----- 1 root operator 116, 8 Mar 21 21:14 /dev/ad1a crw-r----- 1 root operator 116, 9 Mar 21 21:14 /dev/ad1b crw-r----- 1 root operator 116, 10 Mar 21 21:14 /dev/ad1c crw-r----- 1 root operator 116, 11 Mar 21 21:14 /dev/ad1d crw-r----- 1 root operator 116, 12 Mar 21 21:14 /dev/ad1e crw-r----- 1 root operator 116, 13 Mar 21 21:14 /dev/ad1f crw-r----- 1 root operator 116, 14 Mar 21 21:14 /dev/ad1g crw-r----- 1 root operator 116, 15 Mar 21 21:14 /dev/ad1h crw-r----- 1 root operator 116, 0x0002000a Mar 21 21:14 /dev/ad1s1 crw-r----- 1 root operator 116, 0x00020008 Mar 19 17:00 /dev/ad1s1a crw-r----- 1 root operator 116, 0x00020009 Mar 19 17:00 /dev/ad1s1b crw-r----- 1 root operator 116, 0x0002000a Mar 19 17:00 /dev/ad1s1c crw-r----- 1 root operator 116, 0x0002000b Mar 19 17:00 /dev/ad1s1d crw-r----- 1 root operator 116, 0x0002000c Mar 19 17:00 /dev/ad1s1e crw-r----- 1 root operator 116, 0x0002000d Mar 19 17:00 /dev/ad1s1f crw-r----- 1 root operator 116, 0x0002000e Mar 19 17:00 /dev/ad1s1g crw-r----- 1 root operator 116, 0x0002000f Mar 19 17:00 /dev/ad1s1h crw-r----- 1 root operator 116, 0x0003000a Mar 21 21:14 /dev/ad1s2 crw-r----- 1 root operator 116, 0x0004000a Mar 21 21:14 /dev/ad1s3 crw-r----- 1 root operator 116, 0x0005000a Mar 21 21:14 /dev/ad1s4 I've attached my kernel configuration and my complete dmesg just incase there's something I'm doing that is causing this. ad0 works fine as well, it's just ad1 that refuses to work. The cd-rom works as well. This is quite a frustrating problem for me as I desperately need the extra space. As always, your help is appreciated. I'm not sure where to turn on this problem as it's supposed to be fixed as I understand it. The evidence would make it appear otherwise though. Also, before I forget, this drive worked perfectly in 3.4-S under the wd drivers. Matt -- Matt Heckaman [matt@arpa.mail.net|matt@relic.net] [Please do not send me] !Powered by FreeBSD/x86! [http://www.freebsd.org] [any SPAM (UCE) e-mail] --0-1803559075-953693664=:319 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="dmesg.txt" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: dmesg.txt Content-Disposition: attachment; filename="dmesg.txt" Q29weXJpZ2h0IChjKSAxOTkyLTIwMDAgVGhlIEZyZWVCU0QgUHJvamVjdC4N CkNvcHlyaWdodCAoYykgMTk4MiwgMTk4NiwgMTk4OSwgMTk5MSwgMTk5Mw0K CVRoZSBSZWdlbnRzIG9mIHRoZSBVbml2ZXJzaXR5IG9mIENhbGlmb3JuaWEu IEFsbCByaWdodHMgcmVzZXJ2ZWQuDQpGcmVlQlNEIDQuMC1TVEFCTEUgIzA6 IFR1ZSBNYXIgMjEgMjE6Mjg6NTQgRVNUIDIwMDANCiAgICByb290QGVwc2ls b24ubHVjaWRhLnFjLmNhOi91c3Ivc3JjL3N5cy9jb21waWxlL0VQU0lMT04N ClRpbWVjb3VudGVyICJpODI1NCIgIGZyZXF1ZW5jeSAxMTkzMTgyIEh6DQpU aW1lY291bnRlciAiVFNDIiAgZnJlcXVlbmN5IDQwMDkxMTQ1OCBIeg0KQ1BV OiBQZW50aXVtIElJL1BlbnRpdW0gSUkgWGVvbi9DZWxlcm9uICg0MDAuOTEt TUh6IDY4Ni1jbGFzcyBDUFUpDQogIE9yaWdpbiA9ICJHZW51aW5lSW50ZWwi ICBJZCA9IDB4NjYwICBTdGVwcGluZyA9IDANCiAgRmVhdHVyZXM9MHgxODNm OWZmPEZQVSxWTUUsREUsUFNFLFRTQyxNU1IsUEFFLE1DRSxDWDgsU0VQLE1U UlIsUEdFLE1DQSxDTU9WLFBBVCxQU0UzNixNTVgsRlhTUj4NCnJlYWwgbWVt b3J5ICA9IDEzNDE1MjE5MiAoMTMxMDA4SyBieXRlcykNCmF2YWlsIG1lbW9y eSA9IDEyNjUyMTM0NCAoMTIzNTU2SyBieXRlcykNClByZWxvYWRlZCBlbGYg a2VybmVsICJrZXJuZWwiIGF0IDB4YzAzMzAwMDAuDQpQZW50aXVtIFBybyBN VFJSIHN1cHBvcnQgZW5hYmxlZA0KbnB4MDogPG1hdGggcHJvY2Vzc29yPiBv biBtb3RoZXJib2FyZA0KbnB4MDogSU5UIDE2IGludGVyZmFjZQ0KcGNpYjA6 IDxJbnRlbCA4MjQ0M0JYICg0NDAgQlgpIGhvc3QgdG8gUENJIGJyaWRnZT4g b24gbW90aGVyYm9hcmQNCnBjaTA6IDxQQ0kgYnVzPiBvbiBwY2liMA0KcGNp YjE6IDxJbnRlbCA4MjQ0M0JYICg0NDAgQlgpIFBDSS1QQ0kgKEFHUCkgYnJp ZGdlPiBhdCBkZXZpY2UgMS4wIG9uIHBjaTANCnBjaTE6IDxQQ0kgYnVzPiBv biBwY2liMQ0KcGNpMTogPE1hdHJveCBNR0EgRzIwMCBBR1AgZ3JhcGhpY3Mg YWNjZWxlcmF0b3I+IGF0IDAuMCBpcnEgMTENCmlzYWIwOiA8SW50ZWwgODIz NzFBQiBQQ0kgdG8gSVNBIGJyaWRnZT4gYXQgZGV2aWNlIDcuMCBvbiBwY2kw DQppc2EwOiA8SVNBIGJ1cz4gb24gaXNhYjANCmF0YXBjaTA6IDxJbnRlbCBQ SUlYNCBBVEEzMyBjb250cm9sbGVyPiBwb3J0IDB4ZjAwMC0weGYwMGYgYXQg ZGV2aWNlIDcuMSBvbiBwY2kwDQphdGEwOiBhdCAweDFmMCBpcnEgMTQgb24g YXRhcGNpMA0KYXRhMTogYXQgMHgxNzAgaXJxIDE1IG9uIGF0YXBjaTANCnBj aTA6IDxJbnRlbCA4MjM3MUFCL0VCIChQSUlYNCkgVVNCIGNvbnRyb2xsZXI+ IGF0IDcuMiBpcnEgMTANCmNoaXAxOiA8SW50ZWwgODIzNzFBQiBQb3dlciBt YW5hZ2VtZW50IGNvbnRyb2xsZXI+IHBvcnQgMHg1MDAwLTB4NTAwZiBhdCBk ZXZpY2UgNy4zIG9uIHBjaTANCnhsMDogPDNDb20gM2M5MDVCLVRYIEZhc3Qg RXRoZXJsaW5rIFhMPiBwb3J0IDB4ZTQwMC0weGU0N2YgbWVtIDB4ZWEwMDAw MDAtMHhlYTAwMDA3ZiBpcnEgMTAgYXQgZGV2aWNlIDExLjAgb24gcGNpMA0K eGwwOiBFdGhlcm5ldCBhZGRyZXNzOiAwMDoxMDo0YjowZjplNjpiNg0KbWlp YnVzMDogPE1JSSBidXM+IG9uIHhsMA0KeGxwaHkwOiA8M0NvbSBpbnRlcm5h bCBtZWRpYSBpbnRlcmZhY2U+IG9uIG1paWJ1czANCnhscGh5MDogIDEwYmFz ZVQsIDEwYmFzZVQtRkRYLCAxMDBiYXNlVFgsIDEwMGJhc2VUWC1GRFgsIGF1 dG8NCnhsMDogc3VwcGx5aW5nIEVVSTY0OiAwMDoxMDo0YjpmZjpmZTowZjpl NjpiNg0KZmRjMDogPE5FQyA3MjA2NUIgb3IgY2xvbmU+IGF0IHBvcnQgMHgz ZjAtMHgzZjUsMHgzZjcgaXJxIDYgZHJxIDIgb24gaXNhMA0KZmRjMDogRklG TyBlbmFibGVkLCA4IGJ5dGVzIHRocmVzaG9sZA0KZmQwOiA8MTQ0MC1LQiAz LjUiIGRyaXZlPiBvbiBmZGMwIGRyaXZlIDANCmF0a2JkYzA6IDxrZXlib2Fy ZCBjb250cm9sbGVyIChpODA0Mik+IGF0IHBvcnQgMHg2MC0weDZmIG9uIGlz YTANCmF0a2JkMDogPEFUIEtleWJvYXJkPiBpcnEgMSBvbiBhdGtiZGMwDQp2 Z2EwOiA8R2VuZXJpYyBJU0EgVkdBPiBhdCBwb3J0IDB4M2MwLTB4M2RmIGlv bWVtIDB4YTAwMDAtMHhiZmZmZiBvbiBpc2EwDQpzYzA6IDxTeXN0ZW0gY29u c29sZT4gb24gaXNhMA0Kc2MwOiBWR0EgPDE2IHZpcnR1YWwgY29uc29sZXMs IGZsYWdzPTB4MjAwPg0Kc2lvMCBhdCBwb3J0IDB4M2Y4LTB4M2ZmIGlycSA0 IGZsYWdzIDB4MTAgb24gaXNhMA0Kc2lvMDogdHlwZSAxNjU1MEENCnNpbzEg YXQgcG9ydCAweDJmOC0weDJmZiBpcnEgMyBvbiBpc2EwDQpzaW8xOiB0eXBl IDE2NTUwQQ0KcHBjMDogPFBhcmFsbGVsIHBvcnQ+IGF0IHBvcnQgMHgzNzgt MHgzN2YgaXJxIDcgb24gaXNhMA0KcHBjMDogU01DLWxpa2UgY2hpcHNldCAo RUNQL0VQUC9QUzIvTklCQkxFKSBpbiBDT01QQVRJQkxFIG1vZGUNCnBwYzA6 IEZJRk8gd2l0aCAxNi8xNi8xNiBieXRlcyB0aHJlc2hvbGQNCnBwaTA6IDxQ YXJhbGxlbCBJL08+IG9uIHBwYnVzMA0Kc2JjMDogPENyZWF0aXZlIFZpQlJB MTZDPiBhdCBwb3J0IDB4MjIwLTB4MjJmLDB4MzMwLTB4MzMxLDB4Mzg4LTB4 MzhiIGlycSA1IGRycSAxLDUgb24gaXNhMA0Kc2JjMDogc2V0dGluZyBjYXJk IHRvIGlycSA1LCBkcnEgMSwgNQ0KcGNtMDogPFNCIERTUCA0LjEzPiBvbiBz YmMwDQp1bmtub3duMDogPEdhbWU+IGF0IHBvcnQgMHgyMDAtMHgyMDcgb24g aXNhMA0KSVAgcGFja2V0IGZpbHRlcmluZyBpbml0aWFsaXplZCwgZGl2ZXJ0 IGRpc2FibGVkLCBydWxlLWJhc2VkIGZvcndhcmRpbmcgZGlzYWJsZWQsIGRl ZmF1bHQgdG8gYWNjZXB0LCBsb2dnaW5nIGRpc2FibGVkDQphZDA6IDgwNjNN QiA8V0RDIEFDMzg0MDBMPiBbMTYzODMvMTYvNjNdIGF0IGF0YTAtbWFzdGVy IHVzaW5nIFVETUEzMw0KYWQxOiAxNTQ5TUIgPFdEQyBBQzIxNjAwSD4gWzMx NDgvMTYvNjNdIGF0IGF0YTAtc2xhdmUgdXNpbmcgV0RNQTINCmFjZDA6IENE Uk9NIDxNQVRTSElUQSBDUi01ODk+IGF0IGF0YTEtbWFzdGVyIHVzaW5nIFBJ TzQNCnZpbnVtOiBsb2FkZWQNCk1vdW50aW5nIHJvb3QgZnJvbSB1ZnM6L2Rl di9hZDBzMWENCnhsMDogc3RhcnRpbmcgREFEIGZvciBmZTgwOjAwMDE6OjAy MTA6NGJmZjpmZTBmOmU2YjYNCnhsMDogREFEIGNvbXBsZXRlIGZvciBmZTgw OjAwMDE6OjAyMTA6NGJmZjpmZTBmOmU2YjYgLSBubyBkdXBsaWNhdGVzIGZv dW5kDQphZDE6IEhBUkQgUkVBRCBFUlJPUiBibGsjIDBhdGEwLXNsYXZlOiBX QVJOSU5HOiBXQUlUX1JFQURZIGFjdGl2ZT1BVEFfQUNUSVZFX0FUQQ0KYWQx OiBIQVJEIFJFQUQgRVJST1IgYmxrIyAwIHN0YXR1cz01OSBlcnJvcj0wNA0K YWQxOiBETUEgcHJvYmxlbSBmYWxsYmFjayB0byBQSU8gbW9kZQ0KYWQxOiBy ZWFkaW5nIHByaW1hcnkgcGFydGl0aW9uIHRhYmxlOiBlcnJvciByZWFkaW5n IGZzYm4gMA0K --0-1803559075-953693664=:319 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=EPSILON Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: EPSILON Content-Disposition: attachment; filename=EPSILON IyBFUFNJTE9OLkxVQ0lEQS5RQy5DQSwgNC4wLVNUQUJMRSBLRVJORUwNCiMg Q3JlYXRlZDogTWFyY2ggMTkgMjAwMA0KDQptYWNoaW5lCQlpMzg2DQpjcHUJ CUk2ODZfQ1BVDQppZGVudAkJRVBTSUxPTg0KbWF4dXNlcnMJMTI4DQpvcHRp b25zICAgICAgICAgTk1CQ0xVU1RFUlM9MTYzODQNCg0KIyBNYWluIE9wdGlv bnMNCm9wdGlvbnMJCU1BVEhfRU1VTEFURQkJIyBTdXBwb3J0IGZvciB4ODcg ZW11bGF0aW9uDQpvcHRpb25zCQlJTkVUCQkJIyBJbnRlck5FVHdvcmtpbmcN Cm9wdGlvbnMJCUlORVQ2CQkJIyBJUHY2IGNvbW11bmljYXRpb25zIHByb3Rv Y29scw0Kb3B0aW9ucyAgICAgICAgIEZGUyAgICAgICAgICAgICAgICAgICAg ICMgQmVya2VsZXkgRmFzdCBGaWxlc3lzdGVtDQpvcHRpb25zCQlGRlNfUk9P VAkJIyBGRlMgdXNhYmxlIGFzIHJvb3QgZGV2aWNlDQpvcHRpb25zICAgICAg ICAgTkZTICAgICAgICAgICAgICAgICAgICAgIyBOZXR3b3JrIEZpbGVzeXN0 ZW0NCm9wdGlvbnMgICAgICAgICBQUk9DRlMgICAgICAgICAgICAgICAgICAj IFByb2Nlc3MgZmlsZXN5c3RlbQ0Kb3B0aW9ucwkJTVNET1NGUwkJCSMgTVNE T1MgRmlsZXN5c3RlbQ0Kb3B0aW9ucwkJQ0Q5NjYwICAgICAgICAgICAgICAg ICAgIyBJU08gOTY2MCBGaWxlc3lzdGVtDQpvcHRpb25zCQlDRDk2NjBfUk9P VCAgICAgICAgICAgICAjIENELVJPTSB1c2FibGUgYXMgcm9vdC4gIkNEOTY2 MCINCm9wdGlvbnMgICAgICAgICBDT01QQVRfNDMgICAgICAgICAgICAgICAj IENvbXBhdGlibGUgd2l0aCBCU0QgNC4zDQpvcHRpb25zICAgICAgICAgQ09N UEFUX0xJTlVYICAgICAgICAgICAgIyBDb21wYXRpYmxlIHdpdGggTGludXgN Cm9wdGlvbnMJCVVDT05TT0xFCQkjIEFsbG93IHVzZXJzIHRvIGdyYWIgdGhl IGNvbnNvbGUNCm9wdGlvbnMJCVVTRVJDT05GSUcJCSMgYm9vdCAtYyBlZGl0 b3INCm9wdGlvbnMJCVZJU1VBTF9VU0VSQ09ORklHCSMgdmlzdWFsIGJvb3Qg LWMgZWRpdG9yDQpvcHRpb25zICAgICAgICAgS1RSQUNFICAgICAgICAgICAg ICAgICAgIyBrdHJhY2UoMSkgc3lzY2FsbCB0cmFjZSBzdXBwb3J0DQoNCiMg UE9TSVggT3B0aW9ucw0Kb3B0aW9ucyAJUDEwMDNfMUINCm9wdGlvbnMgCV9L UE9TSVhfUFJJT1JJVFlfU0NIRURVTElORw0Kb3B0aW9ucyAJX0tQT1NJWF9W RVJTSU9OPTE5OTMwOUwNCg0KIyBTWVNWIE9wdGlvbnMNCm9wdGlvbnMgICAg ICAgICBTWVNWU0hNDQpvcHRpb25zICAgICAgICAgU1lTVlNFTQ0Kb3B0aW9u cyAgICAgICAgIFNZU1ZNU0cNCg0KIyBGaXJld2FsbCBPcHRpb25zDQpvcHRp b25zICAgICAgICAgSVBGSVJFV0FMTA0Kb3B0aW9ucyAgICAgICAgIElQRklS RVdBTExfREVGQVVMVF9UT19BQ0NFUFQNCg0KZGV2aWNlCQlpc2ENCmRldmlj ZQkJZWlzYQ0KZGV2aWNlCQlwY2kNCg0KIyBGbG9wcHkgZHJpdmVzDQpkZXZp Y2UJCWZkYzAJYXQgaXNhPyBwb3J0IElPX0ZEMSBpcnEgNiBkcnEgMg0KZGV2 aWNlCQlmZDAJYXQgZmRjMCBkcml2ZSAwDQpkZXZpY2UJCWZkMQlhdCBmZGMw IGRyaXZlIDENCg0KIyBBVEEgYW5kIEFUQVBJIGRldmljZXMNCmRldmljZQkJ YXRhMAlhdCBpc2E/IHBvcnQgSU9fV0QxIGlycSAxNA0KZGV2aWNlCQlhdGEx CWF0IGlzYT8gcG9ydCBJT19XRDIgaXJxIDE1DQpkZXZpY2UJCWF0YQ0KZGV2 aWNlCQlhdGFkaXNrCQkjIEFUQSBkaXNrIGRyaXZlcw0KZGV2aWNlCQlhdGFw aWNkCQkjIEFUQVBJIENEUk9NIGRyaXZlcw0KZGV2aWNlCQlhdGFwaWZkCQkj IEFUQVBJIGZsb3BweSBkcml2ZXMNCmRldmljZQkJYXRhcGlzdAkJIyBBVEFQ SSB0YXBlIGRyaXZlcw0Kb3B0aW9ucyAJQVRBX1NUQVRJQ19JRAkjIFN0YXRp YyBkZXZpY2UgbnVtYmVyaW5nDQoNCiMgYXRrYmRjMCBjb250cm9scyBib3Ro IHRoZSBrZXlib2FyZCBhbmQgdGhlIFBTLzIgbW91c2UNCmRldmljZQkJYXRr YmRjMAlhdCBpc2E/IHBvcnQgSU9fS0JEDQpkZXZpY2UJCWF0a2JkMAlhdCBh dGtiZGM/IGlycSAxDQpkZXZpY2UJCXZnYTAJYXQgaXNhPw0KDQojIHN5c2Nv bnMgaXMgdGhlIGRlZmF1bHQgY29uc29sZSBkcml2ZXIsIHJlc2VtYmxpbmcg YW4gU0NPIGNvbnNvbGUNCmRldmljZQkJc2MwCWF0IGlzYT8NCg0KIyBGbG9h dGluZyBwb2ludCBzdXBwb3J0IC0gZG8gbm90IGRpc2FibGUuDQpkZXZpY2UJ CW5weDAJYXQgbmV4dXM/IHBvcnQgSU9fTlBYIGlycSAxMw0KDQojIFNlcmlh bCAoQ09NKSBwb3J0cw0KZGV2aWNlCQlzaW8wCWF0IGlzYT8gcG9ydCBJT19D T00xIGZsYWdzIDB4MTAgaXJxIDQNCmRldmljZQkJc2lvMQlhdCBpc2E/IHBv cnQgSU9fQ09NMiBpcnEgMw0KZGV2aWNlCQlzaW8yCWF0IGlzYT8gZGlzYWJs ZSBwb3J0IElPX0NPTTMgaXJxIDUNCmRldmljZQkJc2lvMwlhdCBpc2E/IGRp c2FibGUgcG9ydCBJT19DT000IGlycSA5DQoNCiMgUGFyYWxsZWwgcG9ydA0K ZGV2aWNlCQlwcGMwCWF0IGlzYT8gaXJxIDcNCmRldmljZQkJcHBidXMJCSMg UGFyYWxsZWwgcG9ydCBidXMgKHJlcXVpcmVkKQ0KZGV2aWNlCQlwcGkJCSMg UGFyYWxsZWwgcG9ydCBpbnRlcmZhY2UgZGV2aWNlDQoNCiMgRm9yIFBuUC9Q Q0kgc291bmQgY2FyZHMNCmRldmljZQkJcGNtDQoNCiMgUENJIEV0aGVybmV0 IE5JQ3MgdGhhdCB1c2UgdGhlIGNvbW1vbiBNSUkgYnVzIGNvbnRyb2xsZXIg Y29kZS4NCmRldmljZQkJbWlpYnVzCQkjIE1JSSBidXMgc3VwcG9ydA0KZGV2 aWNlCQl4bAkJIyAzQ29tIDNjOTB4IChgYEJvb21lcmFuZycnLCBgYEN5Y2xv bmUnJykNCg0KIyBQc2V1ZG8gZGV2aWNlcw0KcHNldWRvLWRldmljZQlicGYJ NAkjIEJlcmtlbGV5IHBhY2tldCBmaWx0ZXINCnBzZXVkby1kZXZpY2UJcHR5 CTMyCSMgUHNldWRvLXR0eXMgKHRlbG5ldCBldGMpDQpwc2V1ZG8tZGV2aWNl CXNucAk0CSMgU25vb3AgZGV2aWNlIC0gdG8gbG9vayBhdCBwdHkvdnR5L2V0 Yy4uDQpwc2V1ZG8tZGV2aWNlCWxvb3AJCSMgTmV0d29yayBsb29wYmFjaw0K cHNldWRvLWRldmljZQlldGhlcgkJIyBFdGhlcm5ldCBzdXBwb3J0DQpwc2V1 ZG8tZGV2aWNlICAgdmludW0JCSMgVmludW0gY29uY2F0L21pcnJvci9yYWlk IGRyaXZlcg0KcHNldWRvLWRldmljZQlzcGxhc2ggICAgICAgICAgIyBTcGxh c2ggc2NyZWVuL3NjcmVlbiBzYXZlcg0KDQojIFBzZXVkbyBkZXZpY2VzIGZv ciBJUHY2DQpwc2V1ZG8tZGV2aWNlCWdpZgkxCSMgSVB2NiBhbmQgSVB2NCB0 dW5uZWxpbmcNCnBzZXVkby1kZXZpY2UJZmFpdGgJMQkjIElQdjYtdG8tSVB2 NCByZWxheWluZyAodHJhbnNsYXRpb24pDQo= --0-1803559075-953693664=:319-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 19:54: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 0A92E37BBE8 for ; Tue, 21 Mar 2000 19:54:05 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id TAA73189; Tue, 21 Mar 2000 19:53:05 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38D843A1.E986798D@gorean.org> Date: Tue, 21 Mar 2000 19:53:05 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-HEAD-0320 i386) X-Accept-Language: en MIME-Version: 1.0 To: Brad Knowles Cc: "Jordan K. Hubbard" , David Murphy , FreeBSD-STABLE Subject: Re: dot-0 releases References: <18276.953682029@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: > > At 3:40 PM -0800 2000/3/21, Jordan K. Hubbard wrote: > > > Actually, those our outdated statements and I'm going to ask the > > Walnut Creek CDROM postmaster to remove them. They only send a > > confusing message. Thanks for the reminder. :) > > So, you're saying that it's perfectly safe for me to replace the > one and only news peering server that we have (currently running 3.x) > with one running 4.0-RELEASE No, don't be ridiculous. We're saying that you should have no more problems upgrading freebsd than you would any other piece of software, but no rational sysadmin would put something like this into production untested. -- "While the future's there for anyone to change, still you know it seems, it would be easier sometimes to change the past" - Jackson Browne, "Fountain of Sorrow" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 20:11:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from BSDpc.geek4food.org (adsl-216-103-105-71.dsl.snfc21.pacbell.net [216.103.105.71]) by hub.freebsd.org (Postfix) with ESMTP id CCF0D37BB18 for ; Tue, 21 Mar 2000 20:11:10 -0800 (PST) (envelope-from andy@geek4food.org) Received: from mega.geek4food.org (mega.geek4food.org [192.168.1.57]) by BSDpc.geek4food.org (Postfix) with ESMTP id E4FD03F2; Wed, 22 Mar 2000 04:11:06 +0000 (GMT) Received: from mega.geek4food.org (localhost.geek4food.org [127.0.0.1]) by mega.geek4food.org (8.9.3/8.9.3) with ESMTP id UAA31479; Tue, 21 Mar 2000 20:11:06 -0800 (PST) (envelope-from andy@geek4food.org) Message-Id: <200003220411.UAA31479@mega.geek4food.org> To: "Jordan K. Hubbard" Cc: Brad Knowles , David Murphy , stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) In-reply-to: Your message of "Tue, 21 Mar 2000 11:25:45 PST." <14317.953666745@zippy.cdrom.com> Date: Tue, 21 Mar 2000 20:11:06 -0800 From: Andy Sparrow Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Your message dated: Tue, 21 Mar 2000 11:25:45 PST >> I can't speak for the relative quality of 4.0 versus 3.0, but >> I'll take your word for it. However, if you're going to compare 4.0 >> to 3.4, then I think a perfect counter-example is the message that >> got this whole thread started -- voxware. > >I don't understand where voxware comes into this. As many people have >already noted (repeatedly), voxware was NOT removed from 4.0, it's >purely a 5.0 issue. Yes, but, as was pointed out on the thread that this TFH seems to have erupted from (in -multimedia) for some of us, it's getting pretty difficult to use voxware on 4.x. And some of us (primarily those with AWE hardware wavetable cards) would like to continue using it, as it provides significant functionality for which there is no replacement available (as yet). However, on 4.x, the AWE support no longer works, because the necessary 'pnp' command in 'userconfig' to prod the "magic" (e.g. hidden) AWE registers has been ripped out[1]. Furthermore, some of us with integrated Vibra16 chipsets on the mobo find that these are no longer usable with voxware[2], thus forcing us to decide between voxware/AWE/3.x and pcm/4.x. This is a particularly gnarly choice if your box with said integrated Vibra16 is SMP, you run NFS and wish to use Linux emulation etc., as all these things are improving much more rapidly in 4.x than they are in 3.x... Cheers, AS [1] Actually, I don't fully understand why this happened either - it seemed like a very nice feature to be able to force some miscreant Plug'n'Pray device into using a known, "safe" configuration to me. [2] Apparently, this is expected behaviour, solution is to use 'pcm' instead. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 20:50:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from BSDpc.geek4food.org (adsl-216-103-105-71.dsl.snfc21.pacbell.net [216.103.105.71]) by hub.freebsd.org (Postfix) with ESMTP id 0DA3937C120 for ; Tue, 21 Mar 2000 20:50:36 -0800 (PST) (envelope-from andy@geek4food.org) Received: from mega.geek4food.org (mega.geek4food.org [192.168.1.57]) by BSDpc.geek4food.org (Postfix) with ESMTP id 3959B420 for ; Wed, 22 Mar 2000 04:50:35 +0000 (GMT) Received: from mega.geek4food.org (localhost.geek4food.org [127.0.0.1]) by mega.geek4food.org (8.9.3/8.9.3) with ESMTP id UAA31802 for ; Tue, 21 Mar 2000 20:50:34 -0800 (PST) (envelope-from andy@geek4food.org) Message-Id: <200003220450.UAA31802@mega.geek4food.org> To: stable@FreeBSD.ORG Subject: ncr problems on 3.4-Stable Date: Tue, 21 Mar 2000 20:50:34 -0800 From: Andy Sparrow Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all. I've been running 3.x-stable on a firewall box for months and months, and it's been very, well, stable :=) Recently, it's started intermittantly (every week or so) giving problems like the following (somewhat trimmed) output: Mar 17 18:34:32 BSDpc syslogd: /var/log/messages: Input/output error Mar 17 18:34:32 BSDpc /kernel: ncr0:0: ERROR (0:c1) (9-ab-2) (e0/5) @ (script 6bc:190001ff). Mar 17 18:34:32 BSDpc /kernel: ncr0: script cmd = 89030000 Mar 17 18:34:32 BSDpc /kernel: ncr0: regdump: da 10 80 05 47 e0 00 0f fe 09 80 ab 80 00 0b 00. Mar 17 18:34:32 BSDpc /kernel: ncr0: have to clear fifos. Mar 17 18:34:32 BSDpc /kernel: ncr0: restart (fatal error). Mar 17 18:34:32 BSDpc /kernel: (da0:ncr0:0:0:0): COMMAND FAILED (9 ff) @0xc078f200. Mar 17 18:34:32 BSDpc /kernel: swap_pager: indefinite wait buffer: device: 0x30401, blkno: 832, size: 4096 Mar 17 18:34:32 BSDpc last message repeated 2 times Mar 17 18:34:32 BSDpc /kernel: ncr0: timeout nccb=0xc078f200 (skip) Mar 17 18:34:32 BSDpc last message repeated 2 times Mar 17 18:34:32 BSDpc /kernel: ncr0: timeout nccb=0xc078f200 (skip) Mar 17 18:34:32 BSDpc /kernel: ncr0: timeout nccb=0xc0791e00 (skip) Mar 17 18:34:32 BSDpc /kernel: ncr0: timeout nccb=0xc0791c00 (skip) Mar 17 18:34:32 BSDpc /kernel: swap_pager: indefinite wait buffer: device: 0x30401, blkno: 832, size: 4096 Mar 17 18:34:32 BSDpc /kernel: swap_pager: indefinite wait buffer: device: 0x30401, blkno: 28272, size: 8192 Mar 17 18:34:32 BSDpc /kernel: ncr0: timeout nccb=0xc078f200 (skip) Mar 17 18:34:32 BSDpc /kernel: ncr0: timeout nccb=0xc0791e00 (skip) Mar 17 18:34:32 BSDpc /kernel: ncr0: timeout nccb=0xc0791c00 (skip) Mar 17 18:34:32 BSDpc /kernel: swap_pager: indefinite wait buffer: device: 0x30401, blkno: 832, size: 4096 Mar 17 18:34:32 BSDpc /kernel: swap_pager: indefinite wait buffer: device: 0x30401, blkno: 28272, size: 8192 Mar 17 18:34:32 BSDpc /kernel: ncr0: timeout nccb=0xc078f200 (skip) Mar 17 18:34:32 BSDpc /kernel: swap_pager: I/O error - pagein failed; blkno 28272, size 8192, error 5 Mar 17 18:34:32 BSDpc /kernel: vm_fault: pager read error, pid 447 (getty) Mar 17 18:34:32 BSDpc /kernel: swap_pager: I/O error - pagein failed; blkno 832, size 4096, error 5 Mar 17 18:34:32 BSDpc /kernel: vm_fault: pager read error, pid 30582 (master) Mar 17 18:34:33 BSDpc /kernel: ncr0: timeout nccb=0xc0791e00 (skip) Mar 17 18:34:36 BSDpc /kernel: ncr0: timeout nccb=0xc0791c00 (skip) Mar 17 18:34:52 BSDpc /kernel: swap_pager: indefinite wait buffer: device: 0x30401, blkno: 10720, size: 4096 At this point, rebooting is really the only option. Hardware is an Intel 430VX chipset with a 233MMX CPU fitted, 32Mb true parity memory, and two PCI NIC cards, along with a TekRam DC-390 F (I think, AMD 53c875 chipset, anyway) SCSI card. Here's the dmesg output: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.4-STABLE #19: Sun Mar 12 13:07:22 PST 2000 root@BSDpc.geek4food.org:/usr/src/sys/compile/BSDpc Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 233864380 Hz CPU: Pentium/P55C (233.86-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Features=0x8001bf real memory = 33554432 (32768K bytes) avail memory = 29917184 (29216K bytes) Preloaded elf kernel "kernel" at 0xc02d1000. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 fxp0: rev 0x02 int a irq 11 on pci0.8.0 fxp0: Ethernet address 00:a0:c9:6f:ac:13 de0: rev 0x23 int a irq 10 on pci0.9.0 de0: SMC 8432BTA 21040 [10Mb/s] pass 2.3 de0: address 00:00:c0:80:04:be ncr0: rev 0x03 int a irq 9 on pci0.10.0 Probing for PnP devices: CSN 1 Vendor ID: BRI9400 [0x0094490a] Serial 0xfd15c320 Comp ID: @@@0000 [0x00000000] Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A ppc0 at 0x378 irq 7 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppb0: IEEE1284 device found /NIBBLE Probing for PnP devices on ppbus0: ppbus0: PRINTER BJL,BJRaster3,BSCC lpt0: on ppbus 0 lpt0: Interrupt-driven port fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-32 wd0: 516MB (1058400 sectors), 1050 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa wdc1: unit 0 (wd2): , DMA, 32-bit, multi-block-16 wd2: 3020MB (6185088 sectors), 6136 cyls, 16 heads, 63 S/T, 512 B/S wdc1: unit 1 (atapi): , removable, accel, dma, iordy acd0: drive speed 1377 - 2755KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA, packet track acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Intel Pentium detected, installing workaround for F00F bug Errr, what's going on? Is this a hardware problem (the boot/swap drive is a slow old Fujitsu 500Mb drive, which always seemed to work fine before), or something wacky with either CAM or the NCR support? I can happily replace the hardware, but if there's anything that should be done to identify some weird problem, I'd be happy to help out as best I can (like providing access, additional information etc). Cheers, AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 21: 0:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id CFA6A37C063 for ; Tue, 21 Mar 2000 21:00:25 -0800 (PST) (envelope-from mmercer@ipass.net) Received: from ipass.net (dsl-2-196.dsl.rdu.ipass.net [209.170.144.196] (may be forged)) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id AAA19139 for ; Wed, 22 Mar 2000 00:00:23 -0500 (EST) Message-ID: <38D85367.366CBA66@ipass.net> Date: Wed, 22 Mar 2000 00:00:23 -0500 From: "Michael E. Mercer" Reply-To: mmercer@ipass.net, mmercer@nortelnetworks.com X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... References: <38D6F515.D0536435@ipass.net> <20000320234144.B9150@stat.Duke.EDU> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, this did not work either... the pnp stuff is complaining it can not assign resources... eeprom failed to come ready -> still on the ep0 device... finds it again with ep1 except this time it is using irq 11 which irq 11 was already assigned to a PCI device (video card) nothing else from what I saw was using irq 10.... I booted with -c , went to visual, and NOTHING was in the NETWORK selection... I could not find ep0 or ep1 in any selection... I can not send my kernel config, since I have no connection and I do not feel like retyping it here... any other suggestions please? later Michael Mercer mmercer@ipass.net Sean O'Connell wrote: > Michael E. Mercer stated: > > hello, > > > > I have a 3com 3C509-TPO Etherlink III card... > > I have just upgraded my pentium 200 MMX machine to 4.0-Stable. > > Everything seems to be going well except that it fails with > > ep0: <3Com 3C509-TPO Etherlink III> at port 0x300-0x30f irq 10 on isa0 > > ep0: eeprom failed to come ready. > > last line repeated 4 more times... > > > > then later during the boot process it finds the same card on a different port > > and everything is fine... except now I can not get to the outside world... > > > > ep0: <3Com 3C509-TPO Etherlink III> at port 0x210-0x21f irq 10 on isa0 > > > > What is the problem here.... normally with me it is user error so let me know... > > > > Thanks > Michael Mercer- > > What do have in your kernel config? Try adding > > options PNPBIOS > device ep > > Also, make sure that nothing else is using irq 10 on your box. Was > it using these settings in its previous incarnation? > > ----------------------------------------------------------------------- > Sean O'Connell Email: sean@stat.Duke.EDU > Institute of Statistics and Decision Sciences Phone: (919) 684-5419 > Duke University Fax: (919) 684-8594 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 Tue Mar 21 21:10:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id A896337BAC3 for ; Tue, 21 Mar 2000 21:10:11 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA19473; Tue, 21 Mar 2000 21:08:54 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Brad Knowles Cc: David Murphy , FreeBSD-STABLE Subject: Re: dot-0 releases In-reply-to: Your message of "Wed, 22 Mar 2000 01:11:20 +0100." Date: Tue, 21 Mar 2000 21:08:54 -0800 Message-ID: <19470.953701734@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So, you're saying that it's perfectly safe for me to replace the > one and only news peering server that we have (currently running 3.x) > with one running 4.0-RELEASE, and if we have any problems then you'll > personally fly out here to fix it? ;-) It's never perfectly safe to go from one OS revision to another, whether that's 3.x -> 4.0 or 2.1.5 -> 2.2.8. It's all in the skill of the administrator and is pretty much release # neutral unless we've really screwed up over here. Should be no problem for you Brad, you're a big dog, right? :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 21:59:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 5005A37BD89 for ; Tue, 21 Mar 2000 21:59:36 -0800 (PST) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn36.imasy.or.jp [202.227.24.228]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id OAA23262; Wed, 22 Mar 2000 14:59:31 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <200003220559.OAA23262@tasogare.imasy.or.jp> To: mmercer@ipass.net, mmercer@nortelnetworks.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... In-Reply-To: Your message of "Wed, 22 Mar 2000 00:00:23 -0500" <38D85367.366CBA66@ipass.net> References: <38D85367.366CBA66@ipass.net> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 22 Mar 2000 14:59:30 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Subject: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... How did you fix this? I'm having the same problem but in 5-CURRENT... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 22:18:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89]) by hub.freebsd.org (Postfix) with ESMTP id 68B7A37C173 for ; Tue, 21 Mar 2000 22:18:06 -0800 (PST) (envelope-from forrestc@workhorse.iMach.com) Received: from localhost (forrestc@localhost) by workhorse.iMach.com (8.9.3/8.9.3) with ESMTP id XAA01964; Tue, 21 Mar 2000 23:13:43 -0700 (MST) Date: Tue, 21 Mar 2000 23:13:41 -0700 (MST) From: "Forrest W. Christian" To: Jeff Palmer Cc: freebsd-stable@FreeBSD.ORG Subject: Re: dot-0 releases In-Reply-To: <4.3.0.20000321203146.00a78940@mail.afcon.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 I'm going to make a single statement and then shut up (which is weird for me).... It has been my experience over many many years that "dot-0" releases (meaning the initial release after a major change) are NOT what you want to stake your livelihood on no matter the product (whether it be FreeBSD, or Windows or Novell or...") or how well the product was tested by the "manufacturer". (well I lied, one more...) If you expect a .0 release to be 100% stable, you have either not been around the industry long enough or you haven't learned from the past. - Forrest W. Christian (forrestc@imach.com) KD7EHZ ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 22:28:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from account.abs.net (account.abs.net [207.114.5.70]) by hub.freebsd.org (Postfix) with ESMTP id 1A74C37C08E; Tue, 21 Mar 2000 22:28:36 -0800 (PST) (envelope-from howardl@account.abs.net) Received: (from howardl@localhost) by account.abs.net (8.9.3/8.9.3+RBL+DUL+RSS+ORBS) id BAA97796; Wed, 22 Mar 2000 01:28:34 -0500 (EST) (envelope-from howardl) From: Howard Leadmon Message-Id: <200003220628.BAA97796@account.abs.net> Subject: CVS Trouble, even under 4.0-RELEASE (alpha) HELP! To: freebsd-stable@freebsd.org, freebsd-alpha@freebsd.org Date: Wed, 22 Mar 2000 01:28:34 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL72 (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 Hello Everyone, I really thought my problems with CVS were first with going from a -CURRENT version to the -RELEASE or -STABLE code, but I can see I am now wrong. The part about this all is that I used to do my CVS updates under 3.4 and 4.0-CURRENT just fine, then about a week before it was all released it seems like everything fell apart, and running a cvsup and make world now gives me a trashed and barely operational server. To try and debug this, I setup another DEC Alpha machine, and then loaded the actual 4.0-RELEASE from ftp.freebsd.org, and the machine came up just fine. I then setup the cvs configs (I will include them below) and went on to update my machine from 4.0-RELEASE to 4.0-STABLE (only a few days have passed, so should not be any big deal). After the cvsup, I then built a new kernel and all was fine, loaded it, rebooted, and all was happy. I then went on and did a 'make buildworld' which when done I performed a 'make installworld', and again so far all seemed good. I then rebooted the machine and after booting I then get some weird syslog messages on the console that show no information, this though seemed like a minor inconvenience. Doing a 'uname -a' showed me that yes I am at 4.0-STABLE and the update seemed successful. Now for where the problems start, I went back to my sources and tried to again build a new kernel. I did a 'make clean' and then followed it by running a 'make depend', this time I get: # make depend cc -c -O2 -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -Wa,-mev56 ../../alpha/alpha/genassym.c In file included from ../../alpha/alpha/genassym.c:43: ../../sys/systm.h:331: invalid #-line In file included from ../../alpha/alpha/genassym.c:45, from ../../alpha/alpha/genassym.c:43: ../../sys/proc.h:47: invalid #-line In file included from ../../sys/signal.h:245, from ../../sys/proc.h:50, from ../../alpha/alpha/genassym.c:43: ../../sys/ucontext.h:34: invalid #-line ../../alpha/alpha/genassym.c:44: #-lines for entering and leaving files don't match In file included from ../../alpha/alpha/genassym.c:50: ../../sys/socket.h:232: invalid #-line In file included from ../../alpha/alpha/genassym.c:51: ../../sys/resource.h:101: invalid #-line ../../sys/resource.h:123: invalid #-line In file included from ../../alpha/alpha/genassym.c:52: ../../sys/resourcevar.h:98: invalid #-line In file included from ../../alpha/alpha/genassym.c:59, from ../../alpha/alpha/genassym.c:52: ../../vm/vm_map.h:380: invalid #-line In file included from ../../netinet/in.h:446, from ../../alpha/alpha/genassym.c:62, from ../../alpha/alpha/genassym.c:59, from ../../alpha/alpha/genassym.c:52: ../../netinet6/in6.h:453: invalid #-line In file included from ../../alpha/alpha/genassym.c:65, from ../../alpha/alpha/genassym.c:59, from ../../alpha/alpha/genassym.c:52: ../../nfs/nfs.h:728: invalid #-line *** Error code 1 Stop in /usr/src/sys/compile/ALPHA. OUCH! So I thought let's see how bad another attempt at doing running a 'make buildworld' fails, and what do I get: # make buildworld -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- rm -rf /usr/obj/usr/src/alpha mkdir -p /usr/obj/usr/src/alpha/usr/bin mkdir -p /usr/obj/usr/src/alpha/usr/lib/compat/aout mkdir -p /usr/obj/usr/src/alpha/usr/games mkdir -p /usr/obj/usr/src/alpha/usr/libdata/ldscripts mkdir -p /usr/obj/usr/src/alpha/usr/libexec/elf mkdir -p /usr/obj/usr/src/alpha/usr/sbin mkdir -p /usr/obj/usr/src/alpha/usr/share/misc mkdir -p /usr/obj/usr/src/alpha/usr/include/arpa mkdir -p /usr/obj/usr/src/alpha/usr/include/g++/std mkdir -p /usr/obj/usr/src/alpha/usr/include/objc mkdir -p /usr/obj/usr/src/alpha/usr/include/protocols mkdir -p /usr/obj/usr/src/alpha/usr/include/readline mkdir -p /usr/obj/usr/src/alpha/usr/include/rpc mkdir -p /usr/obj/usr/src/alpha/usr/include/rpcsvc mkdir -p /usr/obj/usr/src/alpha/usr/include/openssl mkdir -p /usr/obj/usr/src/alpha/usr/include/security mkdir -p /usr/obj/usr/src/alpha/usr/include/ss ln -sf /usr/src/sys /usr/obj/usr/src/alpha/sys -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/alpha DESTDIR=/usr/obj/usr/src/alpha INSTALL="sh /usr/src/tools/install.sh" MACHINE_ARCH=alpha TOOLS_PREFIX=/usr/obj/usr/src/alpha PATH=/usr/obj/usr/src/alpha/usr/sbin:/usr/obj/usr/src/alpha/usr/bin:/usr/obj/usr/src/alpha/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make -f Makefile.inc1 -DNOMAN -DNOINFO -DNOHTML bootstrap-tools cd /usr/src/games/fortune/strfile; make obj; make depend; make all; make install /usr/obj/usr/src/alpha/usr/src/games/fortune/strfile created for /usr/src/games/fortune/strfile rm -f .depend mkdep -f .depend -a -I/usr/obj/usr/src/alpha/usr/include /usr/src/games/fortune/strfile/strfile.c cd /usr/src/games/fortune/strfile; make _EXTRADEPEND echo strfile: /usr/obj/usr/src/alpha/usr/lib/libc.a >> .depend cc -O2 -pipe -Wall -I/usr/obj/usr/src/alpha/usr/include -c /usr/src/games/fortune/strfile/strfile.c In file included from /usr/src/games/fortune/strfile/strfile.c:56: /usr/include/stdlib.h:182: invalid #-line In file included from /usr/src/games/fortune/strfile/strfile.c:58, from /usr/src/games/fortune/strfile/strfile.c:56: /usr/include/string.h:98: invalid #-line *** Error code 1 Stop in /usr/src/games/fortune/strfile. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. As you can see, same basic problem, it's upset about files that seem to have the #'s in them. The above machine was loaded from the default release code on ftp.freebsd.org, and only changes were that I added the binary packages of cvsup-bin and a few shells, so really a stock Alpha with FBSD 4.0 on it. If I cvsup my Intel boxes, they all seem fine, and I used to be able to update my Alpha, but something happened a week or two before the RELEASE version of 4.0 came out that broke everything for me. I have reloaded several of my alpha's, and this test machine at least 4 different times just to test if it would blow up each time, and at what point it did. Every time, it ends up in this shape, and is basically an unusable machine as I would be unable to ever apply any kernel patches or updates, and any security fixes that wander down the road. I am at a total loss as to what I am doing wrong here, and what changed that caused what used to work for me to break so badly. If anyone has any clues, or thinks they can help me figure this out please let me know, as right now I have about a half dozen Alpha boxes that I can't really use FBSD on, or at least not anything but the most basic default load. Finally here is what I use to cvsup, if there is something wrong with what I am doing hopefully someone can set me on the right path: *default tag=RELENG_4 *default host=cvsup6.FreeBSD.org *default prefix=/usr *default base=/usr/local/etc/cvs/source *default release=cvs delete use-rel-suffix src-all cvs-crypto I will look forward to any help someone can offer, and hopefully I can get my Alpha's back on the right track like I have working fine with my Intel's.. --- Howard Leadmon - howardl@abs.net - http://www.abs.net ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 22:37:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 80DD837C155 for ; Tue, 21 Mar 2000 22:37:41 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id BAA51822; Wed, 22 Mar 2000 01:37:11 -0500 (EST) Date: Wed, 22 Mar 2000 01:37:10 -0500 (EST) From: "Matthew N. Dodd" To: Mitsuru IWASAKI Cc: mmercer@ipass.net, mmercer@nortelnetworks.com, freebsd-stable@FreeBSD.ORG Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... In-Reply-To: <200003220559.OAA23262@tasogare.imasy.or.jp> 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, 22 Mar 2000, Mitsuru IWASAKI wrote: > Subject: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... > > How did you fix this? I'm having the same problem but in 5-CURRENT... Mr. Mercer emailed me in private and reconfigured his card manually. If you're having the same problems then please provide me with the following. - Output of a verbose boot. - The configuration of your machine. (devices, resources etc.) - The output of 'ident /sys/dev/ep/*', or if you're installing a snapshot, the exact version of the snapshot. Your problem is likely due to pilot error but if this is gonna be a common problem then I should probably make the driver a little smarter. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 21 22:58:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 38E1037BC00 for ; Tue, 21 Mar 2000 22:58:49 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id WAA74599; Tue, 21 Mar 2000 22:57:59 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38D86EF7.2595FA9F@gorean.org> Date: Tue, 21 Mar 2000 22:57:59 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: David Murphy Cc: stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) References: <20000321170118.M5367@enigma.redbrick.dcu.ie> <20000322015400.B34538@enigma.redbrick.dcu.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Murphy wrote: > > Quoting > by Doug Barton : > > > > but upgrading from 3.4 to 4.0 is fiddly, and it > > > doesn't help that the instructions are counterintuitively at the > > > bottom of /usr/src/UPDATING which, to the untrained eye, looks like a > > > changelog, and lusers like me don't read changelogs to see if someone > > > happened to put vital instructions at the bottom of it. > > > Caveat compiler. We NEVER suggest that lusers (or, less > > experienced users) upgrade from source, even for a point release. We > > ALWAYS tell them to upgrade from CD, or wipe their disk and do a clean > > install. If you choose the upgrade from source path, YOU take > > responsibility for adequately educating yourself. Period, end of story. > > Where, where, WHERE the F*** do "WE" say that? I'm stupid, point it > out to me. REERENCE the blindingly obvious piece of documentation I so > obviously missed. ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/4.0-RELEASE/UPGRADE.TXT > $50 Amazon gift certificate thing to the first > person that points out where on www.freebsd.org this is clearly > stated. No, refernces to mailing list postings won't do - I want to > see where a perfectly ordinary intelligent sysadmin new to FreeBSD > would find this information. Go on, I fscking DARE somebody. Actually what you see on the web page clearly stated in numerous places is that upgrading from source is NOT for the faint of heart. I put a sternly worded message in my 2.2.8->3.2 upgrade web page that told the user that they would be better off using sysinstall. But, that page isn't on a freebsd site, so I guess I don't win your bet. It's easy to fall into the trap of thinking that upgrade from source is the preferred way to do it while reading the development lists, but those lists are for developers. We have always recommended other methods for general users. Your point is well taken though, maybe it's time for a more clear message in the handbook. Jim, you listening? :) Doug -- "While the future's there for anyone to change, still you know it seems, it would be easier sometimes to change the past" - Jackson Browne, "Fountain of Sorrow" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 0:40:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ns2.infologigruppen.se (ns2.infologigruppen.se [212.214.163.69]) by hub.freebsd.org (Postfix) with ESMTP id 9D8CD37C114 for ; Wed, 22 Mar 2000 00:40:12 -0800 (PST) (envelope-from Goran.Lowkrantz@infologigruppen.se) Received: (from uucp@localhost) by ns2.infologigruppen.se (8.9.3/8.9.3) id JAA91640; Wed, 22 Mar 2000 09:40:06 +0100 (CET) (envelope-from Goran.Lowkrantz@infologigruppen.se) Received: from valhall.ign.se(192.168.3.1) via SMTP by bifrost-net.ign.se, id smtpdZ91638; Wed Mar 22 09:40:05 2000 Received: by valhall.ign.se with Internet Mail Service (5.5.2448.0) id ; Wed, 22 Mar 2000 09:40:48 +0100 Message-ID: From: "Lowkrantz, Goran" To: "'stable@FreeBSD.ORG'" Cc: "'Greg Lehey'" Subject: RE: Amanda ond Vinum - Problem found Date: Wed, 22 Mar 2000 09:40:47 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, I found what the probelm is. Two things: 1 - Vinum re-builds all devices in /dev/vinum on boot but while the man page and all examples show them owned by root.operator, mine are owned by root.wheel. How do I change the ownership of the devices permanently? 2 - Amanda tries to be smart and find a character device mapping to the given backup device, which is assumed to be a block device. There is code that should find that the given device is a charakter device but it don't seems to work correctly with Vinum drives. As this is the first full release of no unique raw devices, would it be possible to have Vinum create some kind of hard links with matching r-prefix, as a compatibility option during the first releases of FBSD 4? I would assume that there are quite a few programs out there with hardcoded r's. Cheers, GLZ > -----Original Message----- > From: Lowkrantz, Goran [mailto:Goran.Lowkrantz@infologigruppen.se] > Sent: Tuesday, March 21, 2000 9:31 AM > To: 'stable@FreeBSD.ORG' > Subject: Amanda ond Vinum > > > On the first backup of a new Vinum system, somthing odd > happened. It seems > liek Vinum reset the ownership of the devices. > > Description: > We configured four RAID-5 disks to a fileserver following > vinum(8). All > working well. > Then added the four new volumes to Amanda disklist and did an > amcheck. This > risulted in warnings that Amanda couldn't access the devised due to > permission denied. So I changed the group ownership to operator, reran > amcheck and this them no errors. > > During the night, the backup failed and when I checked the > permissions they > had changed back to group wheel. > > I have reset the permissions and enabled more debugging on > amanada for this > nights backup but if there are any suggestions I'd appreciate them. > > > Appended: > uname -a > ls -l /dev/vinum > vinum list > vinum_history > Amanda Tape Server Host Check > Amanda report > > Cheers, > GLZ > --- > Goran Lowkrantz Email : goran.lowkrantz@infologigruppen.se > Infologigruppen Alfa AB Telephone: Nat 070-587 8782 Fax: > Nat 070-615 > 8782 > Box 202 Int +46 70-587 8782 > Int +46 70-615 > 8782 > 941 25 Pitea, Sweden > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 0:40:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id E32D137C308 for ; Wed, 22 Mar 2000 00:40:39 -0800 (PST) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn39.imasy.or.jp [202.227.24.231]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id RAA03625; Wed, 22 Mar 2000 17:40:35 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <200003220840.RAA03625@tasogare.imasy.or.jp> To: winter@jurai.net Cc: freebsd-stable@FreeBSD.ORG Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... In-Reply-To: Your message of "Wed, 22 Mar 2000 01:37:10 -0500 (EST)" References: X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 22 Mar 2000 17:40:35 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 203 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 22 Mar 2000, Mitsuru IWASAKI wrote: > > Subject: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... > > > > How did you fix this? I'm having the same problem but in 5-CURRENT... > > Mr. Mercer emailed me in private and reconfigured his card manually. > > If you're having the same problems then please provide me with the > following. > > - Output of a verbose boot. > - The configuration of your machine. (devices, resources etc.) > - The output of 'ident /sys/dev/ep/*', or if you're installing a snapshot, > the exact version of the snapshot. Certainly. Attached gzip+tar+uuencoded file contains dmesg.boot - Output of a verbose boot (w/o ep driver in configuration). CELERON - My kernel configuration file. dmesg.3-stable - Output of dmesg from 3.3-STABLE with ep0 on the same machie where ep device was successfully probe/attached. Files in /sys/dev/ep/ are the latest version as of 22nd March. % ident /sys/dev/ep/*.c if_ep.c: $FreeBSD: src/sys/dev/ep/if_ep.c,v 1.99 2000/03/13 11:59:21 mdodd Exp $ if_ep_eisa.c: $FreeBSD: src/sys/dev/ep/if_ep_eisa.c,v 1.18 2000/01/14 07:14:00 peter Exp $ if_ep_isa.c: $FreeBSD: src/sys/dev/ep/if_ep_isa.c,v 1.8 2000/01/23 08:46:21 mdodd Exp $ if_ep_mca.c: $FreeBSD: src/sys/dev/ep/if_ep_mca.c,v 1.2 1999/10/27 06:25:15 mdodd Exp $ if_ep_pccard.c: $FreeBSD: src/sys/dev/ep/if_ep_pccard.c,v 1.12 2000/01/15 05:21:43 mdodd Exp $ If `device ep' line is enabled in my configuration, the following messages come up and boot procedure seems to stop... ep0: <3Com 3C509-TPO Etherlink III> at port 0x300-0x30f irq 10 on isa0 ep0: eeprom failed to come ready. ep0: eeprom failed to come ready. ep0: eeprom failed to come ready. ep0: eeprom failed to come ready. ep0: eeprom failed to come ready. ep0: Ethernet address 00:00:00:00:00:00 I already tried these tree configurations on ep, but all failed. device ep device ep0 at isa? port 0x210 irq 5 device ep0 at isa? port 0x300 irq 10 I sure that the last one is working configuraion on 4-CURRENT last time (around Nov. or Dec. 1999) and the latest 3-STABLE. Thanks. begin 644 ep.tar.gz M'XL(`&I[V#@``^Q;;7/B2)*>K_`KZMQ?S!S857KC)<:]@P';;!M#&-SKO8X) MHI!*1FN0-))PV_/K+[-40N*M3=_>[XHE3R]897M<%4J]>%NVAD]J&_& MQC=SXYNEOGF.\)-2J9,:4WG)7U>QB.*2KI6#,/$"/R:E07MR,^T-'F[;DUZI M]&&\"L,@2H@;1.2U42=BN5IP),TY^G>]20E(^WXB(KC_&D3/GO^T26!)BM&+ M1>Q@N5SYGLW3WC`*DL`.%G%.?W4U1NI+$3V+A7@C5SQ.R)6W$/%;G(CE!N'T M?CB$V3_`+5G%?+80A,,B>7XRXQSG3RY5.O-R*3F_ZX MN#GCSK@_[?9NV_^\8!!I:.E#5RSX&SGU?+*,*V0FP!P%FLX,#(T@><[\T!G> MC8>W:+SMQ2+X2J2-DR0@3Q&?@2$(,$$_#A:%G7L8]^Z![:I_#5PSW(J:383C M)4&4$WWNCQ_:M],"[8<7+UZ!-1SB^#2Y;W=ZJ*?G).*V.&45$J<.55CL/\>? MQS<#I,+;6IR\@9;B.0>5DZ6TSTWBP?AZBW@)6\"?!/EU)58BWAJZMS.T6/)P M#@HL4(X@^.M3=HE;&L3>*\D:8/?YHI9X2T'$J[1^H,_YII]&PW'_<3JZ[P_O M^Y-_3L>=FU[WX;9_=YT10?SI#$;3R_9=][8/LGRXYXD@"V_I)63&'9@@7'@@ M2VK\$.%BOKX/;6_'GH:WW?ZX#>.0X<(A<$N=?D8.MYOD MV4P\X10NX.?\;T1&O/YP^H\N(U[T*V%&D8[MH=-2.K-(5[QWO/@9MX&T)R`O M?$FEV)@_]&PGHQGUP?O0)Q79>E70-QU/VI-^9]KOXKXFX%9V%NO\U7(F(@R^ MZW'GMASRIJTU#4JX[Y#`GP4\D;2QE& M\#>91\'J:9XM$J:1LTKQN!RR4M#C\\RQ=[?RTV5WDT:2I-1_2S=OW?_RE-M" M.8S%R@EJJB\.%SR>%U25$V9M?O@J&WT!IVLNP-WH,9U&S^4(EQ0SJYP8-LIY MX;X-GC\*OH*1#K@/CKT$_>5S>L'N\L#8&7$7_"DF])51.9-19-DU6F!)K5;? M6N,B"$)4?7:.X?<9MY^WR`1$T@CI>GCCBV0=VK94MB@QH/J$-`LRONV/M@C" M,"Q2C$;;!,G*3TW!?H99X!N0G6T/DKQ)FK0Q2=[0S,0"Q9*&MDF]E.:F#O\3 M:;8G6R1/GELR@$CF+.@V<&.HR='!-JE=#J>:7`72UY*@)LDC/+;PB#J%^._' M:>:T+)ARN7"RK.D" M13=\AVX5S^1PT'FYW\-73T*J_5KX$%+L@B2>U-[)S6K)?=+/AB;=-(ZXT2[&N>#C.Y&E_WAN%S^D)F"",OE MOQK%_<\_#J1X3V)&EH5KY:\-O':9/*JETL3@$'W`D)\ M$I/`E:CHP<>\./:2-VSI\(4'*,OW^!D!'$7DP(`,!:"I%^&X$G"I!40)(AK`CPY`4Y@1-NY?D" M3[(%C-MWH)&^(O0EXT2$(1[@T`(\5X(G*U#!!<3VANXV7?>GJ]%#]?.@5^WV MJJ-QKSH9=ZJ#\7UUU.Y5!YU>M?/8J(Y[H^I@<@^-U]C8KG8&P\]`,4$.W:H. M!H_5J\?Q_<TKGTBL[=$0+K+7[BWI@1"K5XW M6-/4@!"0@@3<@4T1"Y<\IRG62?KW!`\D^FI3;:;#[IP5B!$S`TIV MO:=I;$=>",?5.:+<\Y3S#/LVV)M@?R-,\U=+.-8#@NO-$D(B?-Q9!\9/`3L6 MDQ3J`#0B01F>Z+15MN=>"$;TD]P+TM`,0[]\)/,@3A#`2\+('69GBETKL.MUUKZ4LP(W(LTM;FW-;0"WYX@I?ED/ M,.KW'PU,KVJ0UZ#I]KL]K#TD4;```UT/PPK#,"F$OBN$A`/+-1S8-TY1'+V, M*`:&&>ND:36P]A'./3N6@`F8.*15:T:*"2+A,H?13#/7B0;+>F?36&N#8N2/ M,JI6N3.^@VSHL_"=`!??(I/.P*1-2K[0UR:D%I9CTE\`($8(#J&I;O$F;]@$ MJT62_N>??P;#E/14?7XY)!"&,+E'*Y@9@!FV82T!;EOD\W4;-+8`CI^815Z\ M*,&ZC:H#Q=4T8P.OIA_+"D&FQFW1&EQ<'&L9(,Y)$]D40:9X;CT/X+*427<; M-;RZ*0PKXK(";8LD;P"#F66:M(TM+.76)+>FN/4""]MD^;J6DKDH)G/KJEJ1 M\2!%BZQ\#XC(Z5>'5M"N+@>U[M_OVC6]3IL,%@SM+=*PFOK@$L)'O4%UPZ`D M!H@=1'$%#HRZ96G$?EN`GD!Y<\$=N+-T,CZ?5(G)-')Y/B[.Q7`NMC47:U`Y M%RR"U35JX62ZJ>E@G,7)=`-R[6,F4]IB=;GTNEJZ65@ZRY#X.:J9.M4G[G-&F^;$*#K$,7C!85=$E(K@&D?-6YC;J2-9B2!P*")!6 MH_GI\ASDKH+'6)\NBXE M6*R6@BS$BUC$BF@@[#GWO7C9(N)?H"%9G04@^;;N=R#X\+)ZBC3A4-:A'3]!>V8II:8 M6Z_`$,U7WODJ";_\^#`9_?@+X8X386V'TI9%6\UZR^*M)F\U;!F'U'@S.9[C M0AP#/_AY/^PB?-__$$_N/F^';^KT$4J*_S?Z/.,/^GEO;O_/_/^.S)_S&A)IC& M9XDXG(L8)?XJ'&">T5KGX?Z^!_[YP=H$`E9+,UN&N0D$T%UW4,#>]!]EF$'* M@DYN8S##X'5V=D8@VTX;6@12?:,)09P""H"PC1@AZY+PP$SAP>TG?(`S[6/_ MM-.^[5_>MR?]X1WQ(79`:+<]UP/!:Y`!XVR.18XWN@B)H+A#QBIF#A MP!FBUHF!3R3SP$GQ3)98]_OG^2UY%(%__O\)ZE`3$P\)=2R:(YCY6^S9.;$] M7_EH`*URFA0R](.:3&,I2.FZD"Y`GF`9Z0`PGMDD(:3-,!82Z8%L0X(XDJ>J%B!TC7,;^61 ME#XLP2$PJP'S4?")NDU;T#5O#_*.-[DM+C4UT`=2X%V%@*>^8`\AMP*WDY4A M34>^EDS'<3[`6L@NAX8TJQSZ84J0BH3IN223:<):`(<523,)7%1ORV'@4VIF M!$EKLF%O`$DZ@53$8.4A'M/IT+'WY*>VDV86K7*[,^JW(#6@;MTU:!DKK2TX MP"&L+%-CGZ&CEDV+0(PP=6(P`F`&<%&#$T,`(X%,EQ;^0U(%[>6TP]CL^\;_ M\I%TOX,A79NF0^+B"`Q34@6J^86=02C&+^4[RKJ%$`T?5].X@@Q>208YZ1SQZ``Q\2Z?<1^%+FC7P!^I:/(4!3^;J-0^`2R$&>C]!0YL&H?!/(:\O24&9S/G26O8IR&^[C0J^ M)D%?&Q*HF7:!B2LNED:4A@)SR)C=5R2Y[3Y!'@U1NZ02.0!_,I9=0$Q`^$>^ MS)WH`F]@+C0Z04X]YZ+.FK1!&U9%98D_+7$98?IZ`D+=XW))?"0'S.W10-KR M#AOTMU2^G-&H704LZ8-["YE(8]-WJ2Q#MW^-RC"*[%9=3C$:7SY6]I9?MO0B M55+[6'J16%^*B_D&"`3W.!%"JQ>8%&LNY5(F7@T1!O2!?`B2L!?]P)5\Y5*\ MF@'\\B":"$#U%Y24`'`%OL.C-_F]7%KR\`NCOV3`&&8!+""(#ALRX[$@PD@U M52428V@@4^8*[XG,#HEL;(O,#HO,MD1F[TW+BIK2BM.R@YIB1VCJO6F+JV7K M:1E.V_B]&Z1]8X-PH.(]+6]8V"L'HN MC8Y5DW_]2W(JMZXB7\#8MW-&NG,&4\4W;6,# MUY7^\BK>-;1OC0]\4B;%B-WHS)A`RNQ^-5]A>SJ>?-E$5M6@%5('7Q3;ZZY*N_PX<%-=0= M))L.QPP_6^J<^\X"DU6E5\!XB@ER3T8-Q'L5.8ZY?U6,[O865I4]'3DDG7F, M=-J6=*:2SGQ/NFQ'#DBW?OKRNZ33WY>N3ND^W1ETI[=@3,8N:U&QFE2LN1;= MV!1=\KTGNK$E>EU"#DKKN>AV076J**)D@/E5"49)(`O\[S"],GF&H\FZ[@9W MW:7'\&,XD/%@@[EQ!*>K)G;U(J=Q#*>A..O?S:FD=6??S6DK3O>[.5U7T`)S MD5_;5/%[]F%MV8>M3-O.[8/N->W,>NE^Z]50.(WE8FW:[@$NCES\>[D@A-7P M^FV^]S11W]($59Y"KJ6C6W*=HC+0"[C MFUSOGI5T:TG`!4N":S%J&OOTK>7>9^P33S[:=P\N2G*]*][V60Y<()Y1=%IM M_XFCSG)MKS6@9+E@=%.R_2RO#7E(%-;#CF)K&O)L6;/91W'9,HD6^63N'K9W MM;>=:VC*7K5<>XW]\UL,;8OMV3P5`AI'";"=3C24`(U<`+[?N&V9SMB'TQE^ ME'EO)P5V-ZPW95QOU@\)<(!/I`!(&'KQI#N.-4,'[[&^NVQSQVTT M6+:6N(3``U:%3?WVY`>_KVT[XHT!2\L=M?4".3KTZ(O>Z& M3@J`LX9(E%,B7KTX`9B2/E?TQ2L(@`^PY.LC\HV8]&=".0\[GL>+^11_=R>F M`-\63B3\%CY(`#ID++S]M9'_BU(JUZYPH06_9;@0+L(Z=>@QI:159+ M%`*$*(]!6U5&J'HA"ROWD_7/#3[F[V>I\5.R5OH;P%44(;R$AN)<^.M4_&4! MXCHX<*QZQO.<"0:V`/;$^(R<:I4RCMLB][UQ;X*_,0*PFZPB'X9Q1(M2E^\0 MI!4%Z..R3Y8[\&^5@.B,LG.&1J95Y!,%UWM*'PUE3XG@/,'S0KW;IWZ:(2M* MGZ_;107I=O:NC1=`,IB]:P-MF':Z:\6Y"-AQN"I>J[+0UL*WY4[-2CXM@`#7 M36EQ_%9A?)`S2FPI&IRA,%4K>ZTG2RTEFX4=910[Y!%?B@1_\;D*L1J`Y83: M*BR;E+`&'M3YXSK]O]NYUI^V82#^O7_%?1M(I;7CI$W0BL0>0HPA)DW[C/J( MH:*D4=.NXK_?W=G.PPT%Q@N`#@6M!.[(AQ`*2*<1H9FD(8NJ6#)`@@;$";?J9#":.$(*(:`-% M,A6#2D"-04U`3:&C9J#05T2"*=/@1>PG%$E@SH`B7W^"\\PDH`@(R?DE5%Y] MFO+%TYS9P'%HYJCJ,A/ MNHL2V^HVEZ<`KN(1A.ON($E]#%D;HQT&*UIPL/=%<3W#93)=TXY0/.`6.U\L MH$@YR:HUY3?'=?'#2LQ]AU3]@-ID=]ERFW%&P<3"&IMM&:BK!=]8[B%7A%72 M6SZ6341LIN/L`YZV!<$F"%:UW*QJ(SZ_I[1=<:]NR.:B0BS/@.4)?'D"2SNU M\[)G1AG.:8G1^&$7/YCBATC\P(#\TL-<*/D,#F:&S@*=.E]B`**??HD.>RUQNHT4`YB'H' M)+,1>C\;&8TJ^/HN$T&I"$81\H'6,;6SUN3;6`B@1J.IN"6,Y237N'F6W0G<6]&^@I#]0\K.K-$D&CA44DTW@WISK!9+'W& M-W/=TB1WFX+=)N4U%>L=7EPM76LDM\76R!!XWKPE`/=O!B9M14/_VS"\.E7BXH0RHT>A>=\"5_O3,5"`&Q]%EZ94R'7/<67$:HY!B+'P5P,9=XJ30C9J-I(?* M0DJO93LS^=.C8C'^G;Y49W*W,@-U%N_5&0]D:%]?OF'8/$MG\J]UYK=LL85\ MW7*A.;ZBY'LD*\9XC9=DV8Q$DZY%V3_.KT2IZQOKE1EM'+KR$W2%=+KJLB26@.(/_T+9R27M.@PIE(I7CP137Y-TB(Q/WZ1=H/O:IZ7W4 /GOS_>?N?/TLFJ_H`4``` ` end To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 0:48:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id EE70C37C0CE for ; Wed, 22 Mar 2000 00:48:22 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id DAA53386; Wed, 22 Mar 2000 03:48:18 -0500 (EST) Date: Wed, 22 Mar 2000 03:48:18 -0500 (EST) From: "Matthew N. Dodd" To: Mitsuru IWASAKI Cc: freebsd-stable@FreeBSD.ORG Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... In-Reply-To: <200003220840.RAA03625@tasogare.imasy.or.jp> 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, 22 Mar 2000, Mitsuru IWASAKI wrote: > Certainly. Attached gzip+tar+uuencoded file contains > dmesg.boot - Output of a verbose boot (w/o ep driver in configuration). Could I have this with the ep driver configured? > If `device ep' line is enabled in my configuration, the following > messages come up and boot procedure seems to stop... > > ep0: <3Com 3C509-TPO Etherlink III> at port 0x300-0x30f irq 10 on isa0 > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: Ethernet address 00:00:00:00:00:00 Yep, but I need the output of a verbose boot when you get this error message. > I already tried these tree configurations on ep, but all failed. > > device ep > device ep0 at isa? port 0x210 irq 5 > device ep0 at isa? port 0x300 irq 10 This isn't supported anymore with the ep driver. > > I sure that the last one is working configuraion on 4-CURRENT > last time (around Nov. or Dec. 1999) and the latest 3-STABLE. > > Thanks. > > begin 644 ep.tar.gz > M'XL(`&I[V#@``^Q;;7/B2)*>K_`KZMQ?S!S857KC)<:]@P';;!M#&-SKO8X) > MHI!*1FN0-))PV_/K+[-40N*M3=_ M^",_C%++,,@/A+"ZR?`O?*CZ2XAE4HN0.K4L6C=,2H&,4 MCPCYP?O*8_[L':3[.A=B\6<(].=^EMR>>[XHE3R]897M<%4J]>%NVAD]J&_& > MQC=SXYNEOGF.\)-2J9,:4WG)7U>QB.*2KI6#,/$"/R:E07MR,^T-'F[;DUZI > M]&&\"L,@2H@;1.2U42=BN5IP),TY^G>]20E(^WXB(KC_&D3/GO^T26!)BM&+ > M1>Q@N5SYGLW3WC`*DL`.%G%.?W4U1NI+$3V+A7@C5SQ.R)6W$/%;G(CE!N'T > M?CB$V3_`+5G%?+80A, M/NBJL8&J2[R8 M<`H"C;O#L1(;;_=.T.DVP4&ELL=#@O??(,M$Z71K]\/!EC15DA+MD61T/^RD > M@HRBP!9Q3-Q],B>7XRXQSG3RY5.O-R*3F_ZX > MN#GCSK@_[?9NV_^\8!!I:.E#5RSX&SGU?+*,*V0FP!P%FLX,#(T@><[\T!G> > MC8>W:+SMQ2+X2J2-DR0@3Q&?@2$(,$$_#A:%G7L8]^Z![:I_#5PSW(J:383C > M)4&4$WWNCQ_:M],"[8<7+UZ!-1SB^#2Y;W=ZJ*?G).*V.&45$J<.55CL/\>? > MQS<#I,+;6IR\@9;B.0>5DZ6TSTWBP?AZBW@)6\"?!/EU)58BWAJZMS.T6/)P > M#@HL4(X@^.M3=HE;&L3>*\D:8/?YHI9X2T'$J[1^H,_YII]&PW'_<3JZ[P_O > M^Y-_3L>=FU[WX;9_=YT10?SI#$;3R_9=][8/LGRXYXD@"V_I)63&'9@@7'@@ > M2VK\$.%BOKX/;6_'GH:WW?ZX#>.0X<(A<$N=?D8.MYOD > MV4P\X10NX.?\;T1&O/YP^H\N(U[T*V%&D8[MH=-2.K-(5[QWO/@9MX&T)R`O > M?$FEV)@_]&PGHQGUP?O0)Q79>E70-QU/VI-^9]KOXKXFX%9V%NO\U7(F(@R^ > MZW'GMASRIJTU#4JX[Y#`GP4\ M$SD<*;K0:">D;2QE& > M\#>91\'J:9XM$J:1LTKQN!RR4M#C\\RQ=[?RTV5WDT:2I-1_2S=OW?_RE-M" > M.8S%R@EJJB\.%SR>%U25$V9M?O@J&WT!IVLNP-WH,9U&S^4(EQ0SJYP8-LIY > MX;X-GC\*OH*1#K@/CKT$_>5S>L'N\L#8&7$7_"DF])51.9-19-DU6F!)K5;? > M6N,B"$)4?7:.X?<9MY^WR`1$T@CI>GCCBV0=VK94MB@QH/J$-`LRONV/M@C" > M,"Q2C$;;!,G*3TW!?H99X!N0G6T/DKQ)FK0Q2=[0S,0"Q9*&MDF]E.:F#O\3 > M:;8G6R1/GELR@$CF+.@V<&.HR='!-JE=#J>:7`72UY*@)LDC/+;PB#J%^._' > M:>:T+)ARN7"RK.D" > M13=\AVX5S^1PT'FYW\-73T*J_5KX$%+L@B2>U-[)S6K)?=+/AB;=-(Z M7"6YL6\RXN0=BS"1NQ5)P?+VI?+Z+N[(^0"^D1A.5#S;:N0^%1&:,$#)/7%X > M@5=R#@(X[O/&R`O2\?@R`/I[+R`(708CG8`GOXDH/Z4^]\;M8K)U??EP-1WW > M_ZMW8="F1=68)+3!:3=\B;YJ6NIQ)H1K\/#<$4V2L_$MMA/PP4E_T+MG)[D0 > M<%H/VJ,+BVTVW?4OM.VF\07;:7O8X1S?[I`-1X,+C6ZV/0QZFS/<#-JWMT!F > MTHW&0?OQXN0TO1E=CW\ MQKWK"]8HY#'#J\G#J`N(9)PW=KN7^9?>XT2[&N>#C.Y&E_WAN%S^D)F"",OE > MOQK%_<\_#J1X3V MFB?DU*X0UFQJ-;@TR54D!&*IOF^?E;>)&EH5KY:\-O':9/*JETL3@$'W`D)\ > M$I/`E:CHP<>\./:2-VSI\(4'*,OW^!D!'$7DP(`,!:"I%^& M;WOD`VV1?T#N,H"MTC1(=5JZWC(T\O?QA&B`X\IH1VH'?[;AM(L"OW6^BJ/S > M.+*5;9\#C#RW`2X"HCS/*A43P!]VL,+#@IQX# M^:W<&3VT2"<=FISJ5OW,I+7!S6_$:E@U>X$G"I!40)(AK`CPY`4Y@1-NY?D" > M3[(%C-MWH)&^(O0EXT2$(1[@T`(\5X(G*U#!!<3VANXV7?>GJ]%#]?.@5^WV > MJJ-QKSH9=ZJ#\7UUU.Y5!YU>M?/8J(Y[H^I@<@^-U]C8KG8&P\]`,4$.W:H. > M!H_5J\?Q_<TKGTBL[=$0+K+7[BWI@1"K5XW > M6-/4@!"0@@3<@4T1"Y<\IRG62?KW!`\D^FI3;:;#[IP5B!$S`TIV > MO:=I;$=>",?5.:+<\Y3S#/LVV)M@?R-,\U=+.-8#@NO-$D(B?-Q9!\9/`3L6 > MDQ3J`#0B01F>Z+15MN=>"$;TD]P+TM`,0[]\)/,@3A#`2\+( MZC@`P$1Z!O\D.SO(WKX>'69GBETKL.MUUKZ4LP(W(LTM;FW-;0"WYX@I?ED/ > M,.KW'PU,KVJ0UZ#I]KL]K#TD4;```UT/PPK#,"F$OBN$A`/+-1S8-TY1'+V, > M*`:&&>ND:36P]A'./3N6@`F8.*15:T:*"2+A,H?13#/7B0;+>F?36&N#8N2/ > M,JI6N3.^@VSHL_"=`!??(I/.P*1-2K[0UR:D%I9CTE\`($8(#J&I;O$F;]@$ > MJT62_N>??P;#E/14?7XY)!"&,+E'*Y@9@!FV82T!;EOD\W4;-+8`CI^815Z\ > M*,&ZC:H#Q=4T8P.OIA_+"D&FQFW1&EQ<'&L9(,Y)$]D40:9X;CT/X+*427<; > M-;RZ*0PKXK(";8LD;P"#F66:M(TM+.76)+>FN/4""]MD^;J6DKDH)G/KJEJ1 > M\2!%BZQ\#XC(Z5>'5M"N+@>U[M_OVC6]3IL,%@SM+=*PFOK@$L)'O4%UPZ`D > M!H@=1'$%#HRZ96G$?EN`GD!Y<\$=N+-T,CZ?5(G)-')Y/B[.Q7`NMC47:U`Y > M%RR"U35JX62ZJ>E@G,7)=`-R[6,F4]IB=;GTNEJZ65@ZRY MMHFJ>#X.:J9.M4G[G-&F^;$*#K$,7C!85=$E(K@&D?-6YC;J2-9B2!P*")!6 > MH_GI\ASDKH+'6)\NBXE > M6*R6@BS$BUC$BF@@[#GWO7C9(N)?H"%9G04@^;;N=R# M)INDH;P*2E@$`"F=,B-ZQWQM$FG#IW$%=84>X\+)ZBC3A4-:A'3]!>V8II:8 > M6Z_`$,U7WODJ";_\^#`9_?@+X8X386V'TI9%6\UZR^*M)F\U;!F'U'@S.9[C > M0AP# M,>/_AY/^PB?-__$$_N/F^';^KT$4J*_S?Z/.,/^GEO;O_/_/^.S)_S&A)IC& > M9XDXG(L8)?XJ'&">T5KGX?Z^!_[YP=H$`E9+,UN&N0D$T%UW4,#>]!]EF$'* > M@DYN8S##X'5V=D8@VTX;6@12?:,)09P""H"PC1@AZY+PP$SAP>TG?(`S[6/_ > MM-.^[5_>MR?]X1WQ(79`:+<]UP/!:Y`!XVR.18XWN@B)H+A#QBIF#A > MP!FBUHF!3R3SP$GQ3)98]_OG^2UY%(%__O\)ZE`3$P\)=2R:(YCY6^S9.;$] > M7_EH`*URFA0R](.:3&,I2.FZD"Y`GF`9Z0`PGMDD(:3-,!82Z M8#JT0SA;,\$FZD;&MH.V+`.RI(:!:$LWF;66=>8%L0X(XDJ>J%B!TC7,;^61 > ME#XLP2$PJP'S4?")NDU;T#5O#_*.-[DM+C4UT`=2X%V%@*>^8`\AMP*WDY4A > M34>^EDS'<3[`6L@NAX8TJQSZ84J0BH3IN223:<):`(<523,)7%1ORV'@4VIF > M!$EKLF%O`$DZ@53$8.4A'M/IT+'WY*>VDV86K7*[,^JW(#6@;MTU:!DKK2TX > MP"&L+%-CGZ&CEDV+0(PP=6(P`F`&<%&#$T,`(X%,EQ;^0U(%[>6TP]CL^\;_ > M\I%TOX,A79NF0^+B"`Q34@6J^86=02C& M/>+^4[RKJ%$`T?5].X@@Q>208YZ1SQZ``Q\2Z?<1^%+FC7P!^I:/( M5[O]\2<"W>4!3^;J-0^`2R$&>C]!0YL&H?!/(:\O24&9S/G26O8IR&^[C0J^ > M)D%?&Q*HF7:!B2LNED:4A@)SR)C=5R2Y[3Y!'@U1NZ02.0!_,I9=0$Q`^$>^ > MS)WH`F]@+C0Z04X]YZ+.FK1!&U9%98D_+7$98?IZ`D+=XW))?"0'S.W10-KR > M#AOTMU2^G-&H704LZ8-["YE(8]-WJ2Q#MW^-RC"*[%9=3C$:7SY6]I9?MO0B > M55+[6'J16%^*B_D&"`3W.!%"JQ>8%&LNY5(F7@T1!O2!?`B2L!?]P)5\Y5*\ > MF@'\\B":"$#U%Y24`'`%OL.C-_F]7%KR\`NCOV3`&&8!+""(#ALRX[$@PD@U > M52428V@@4^8*[XG,#HEL;(O,#HO,MD1F[TW+BIK2BM.R@YIB1VCJO6F+JV7K > M:1E.V_B]&Z1]8X-PH.( MA)$OPCQ^$?J![6[\+SA&\QV1Q9%Z-W5=ST1N--RBA=*UR/KO]F6E=Y[J73/- > M(]R;;KIW0?&J$JO*E!]537,F(^QLMT:\#G;XS!R93MO7H\HZW/%U80%2H*P^ > MBD.Q/7.PLA?SC8!ZL)"]+6]8V"L'HN > MC8Y5DW_ MDU5,+R!'3&\9W'X'35;`Q7Q75VU93;-0S50+1P*V(6]]6][ZIKP-Q?*N+'MH > M:$Y#,YJBO(9JRPJ1A1)D)B^^MK%C".>]2W(JMZXB7\#8MW-&NG,&4\4W;6,# > MUY7^\BK>-;1OC0]\4B;%B-WHS)A`RNQ^-5]A>SJ>?-E$5M6@%5( M0')ZCI=JFM:PC%F3JXC3-SVU8DTUQH=0(3[*``_=?EASQ(,.I1V1VK78MFN] > MZ)GO/OPX/1C@*CBJ?/BQ!CM@AFKKJV3!(X"%0,$47"R/[D;4H&@*CB/+!DLN > MK0F3X9U.W,^LD^[V!BK(@3_4Y7.$NIN&-Q0.5+T`>'7Q3;ZZY*N_PX<%-=0= > M))L.QPP_6^J<^\X"DU6E5\!XB@ER3T8-Q'L5.8ZY?U6,[O865I4]'3DDG7F, > M=-J6=*:2SGQ/NFQ'#DBW?OKRNZ33WY>N3ND^W1ETI[=@3,8N:U&QFE2LN1;= > MV!1=\KTGNK$E>EU"#DKKN>AV076J**)D@/E5"49)(`O\[S"],GF&H\FZ[@9W > MW:7'\&,XD/%@@[EQ!*>K)G;U(J=Q#*>A..O?S:FD=6??S6DK3O>[.5U7T`)S > MD5_;5/%[]F%MV8>M3-O.[8/N->W,>NE^Z]50.(WE8FW:[@$NCES\>[D@A-7P > M^FV^]S11W]($59Y" M9ON%DX];ZP<5-SM&N.:6<#,EW"P73J?Z7L5IN[VY;.G#>KJ6C6W*=HC+0"[C > MFUSOGI5T:TG`!4N":S%J&OOTK>7>9^P33S[:=P\N2G*]*][V60Y<()Y1=%IM > M_XFCSG)MKS6@9+E@=%.R_2RO#7E(%-;#CF)K&O)L6;/91W'9,HD6^63N'K9W > MM;>=:VC*7K5<>XW]\UL,;8OMV3P5`AI'";"=3C24`(U<`+[?N&V9SMB'TQE^ > ME'EO)P5V-ZPW95QOU@\)<(!/I`!(&'KQI#N.-4,'[[&^NVQSQVTT > M6+:6N(3``U:%3?WVY`>_KVT[XHT!2\L=M?4".3KTZ(O>Z& > M3@J`LX9(E%,B7KTX`9B2/E?TQ2L(@`^PY.LC\HV8]&=".0\[GL>+^11_=R>F > M`-\63B3\%CY(`#ID++S]M9'_BU(JUZYPH06_9;@0+L(Z=>@QI:159+ > M%`*$*(]!6U5&J'HA"ROWD_7/#3[F[V>I\5.R5OH;P%44(;R$AN)<^.M4_&4! > MXCHX<*QZQO.<"0:V`/;$^(R<:I4RCMLB][UQ;X*_,0*PFZPB'X9Q1(M2E^\0 > MI!4%Z..R3Y8[\&^5@.B,LG.&1J95Y!,%UWM*'PUE3XG@/,'S0KW;IWZ:(2M* > MGZ_;107I=O:NC1=`,IB]:P-MF':Z:\6Y"-AQN"I>J[+0UL*WY4[-2CXM@`#7 > M36EQ_%9A?)`S2FPI&IRA,%4K>ZTG2RTEFX M7SW`YE_3YV`SS)BEW;=T[1G1O(\W,,S*;>4=910[Y!%?B@1_\;D*L1J`Y83: > M*BR;E+`&'M3YXSK]O]NYUI^V82#^O7_%?1M(I;7CI$W0BL0>0HPA)DW[C/J( > MH:*D4=.NXK_?W=G.PPT%Q@ MEM"9:)":>N`#@6M!.[(AQ`*2*<1H9FD(8NJ6#)`@@;$";?J9#":.$(*(:`-% > M,A6#2D"-04U`3:&C9J#05T2"*=/@1>PG%$E@SH`B7W^"\\PDH`@(R?DE5%Y] > MFO+%TYS9P MN-6`P)7<%[\]73`;"FKN?IYA?Y?-Q2-O"@?%0T$,RL>'%HYJCJ,A/ > MNHL2V^HVEZ<`KN(1A.ON($E]#%D;HQT&*UIPL/=%<3W#93)=TXY0/.`6.U\L > MH$@YR:HUY3?'=?'#2LQ]AU3]@-ID=]ERFW%&P<3"&IMM&:BK!=]8[B%7A%72 > M6SZ6341LIN/L`YZV!<$F"%:UW*QJ(SZ_I[1=<:]NR.:B0BS/@.4)?'D"2SNU > M\[)G1AG.:8G1^&$7/YCBATC\P( MT-),FC36Y66:^!&)T--[2J*HU'%8Y^[2'#MK9&#[!PUIV.6JO*C*,2J='?X/ > M5Y81KGW)=I&K_L_3\1V5OU.6KV%225^"H95@3).K.I8^A=\_+F<8U/M7+D#3 > MK&]8ZCZO!'FIS\M[@BR+Y),I,OX^S^[@_/R\P5V:P)&V%9B.#Y^,9RDNY/5J > M3L4(((X%K#\TL-<*/D,#F:&S@*=.E]B`**??HD.>RUQNHT4`YB'H' > M)+,1>C\;&8TJ^/HN$T&I"$81\H'6,;6SUN3;6`B@1J.IN"6,Y237N' M$\Y\9EKR/*\U9>F6W0G<6]&^@I#]0\K.K-$D&CA44DTW@WISK!9+'W& > M-W/=TB1WFX+=)N4U%>L=7EPM76LDM\76R!!XWKPE`/=O!B9M M59YPTI.R1YTQV_Q>14/_VS"\.E7BXH0RHT>A>=\"5_O3,5"`& M8Z0K^O,,SR!%\8)\?6M>Q]%EZ94R'7/<67$:HY!B+'P5P,9=XJ30C9J-I(?* > M0DJO93LS^=.C8C'^G;Y49W*W,@-U%N_5&0]D:%]?OF'8/$MG\J]UYK=LL85\ > MW7*A.;ZBY'LD*\9XC9=DV8Q$DZY%V3_.KT2IZQOKE1EM M^D)E'EQ*8LM.X,!>'+KR$W2%=+KJLB26@.(/_T+9R27M M9P14J",+9]"AYTC)*P[+#!1A.0B?'`6AC!(+\<`;D0SA&*XNF#1H(24""@,; > M.@PIE(I7CP137Y-TB(Q/WZ1=H/O:IZ7W4 > /GOS_>?N?/TLFJ_H`4``` > ` > end > -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 1:11:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id D354C37BA53 for ; Wed, 22 Mar 2000 01:11:19 -0800 (PST) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn13.imasy.or.jp [202.227.24.205]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id SAA11923; Wed, 22 Mar 2000 18:11:17 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <200003220911.SAA11923@tasogare.imasy.or.jp> To: winter@jurai.net Cc: iwasaki@jp.FreeBSD.org, freebsd-stable@FreeBSD.ORG Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... In-Reply-To: Your message of "Wed, 22 Mar 2000 03:48:18 -0500 (EST)" References: X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 22 Mar 2000 18:11:17 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 50 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 22 Mar 2000, Mitsuru IWASAKI wrote: > > Certainly. Attached gzip+tar+uuencoded file contains > > dmesg.boot - Output of a verbose boot (w/o ep driver in configuration). > > Could I have this with the ep driver configured? Grrr, It's too difficult because I can't do anything after the messsage even etner DDB or pause screen and back scrolling... > > If `device ep' line is enabled in my configuration, the following > > messages come up and boot procedure seems to stop... > > > > ep0: <3Com 3C509-TPO Etherlink III> at port 0x300-0x30f irq 10 on isa0 > > ep0: eeprom failed to come ready. > > ep0: eeprom failed to come ready. > > ep0: eeprom failed to come ready. > > ep0: eeprom failed to come ready. > > ep0: eeprom failed to come ready. > > ep0: Ethernet address 00:00:00:00:00:00 > > Yep, but I need the output of a verbose boot when you get this error > message. I can get only last 24 lines but prior lines seems to be the same as posted before. EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A mss_detect, busy still set (0xff) ep0: <3Com 3C509-TPO Etherlink III> at port 0x300-0x30f irq 10 on isa0 ep0: eeprom failed to come ready. ep0: eeprom failed to come ready. ep0: eeprom failed to come ready. ep0: eeprom failed to come ready. ep0: eeprom failed to come ready. ep0: Ethernet address 00:00:00:00:00:00 Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 1:15:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 91A5A37B538 for ; Wed, 22 Mar 2000 01:15:47 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id EAA53695; Wed, 22 Mar 2000 04:15:42 -0500 (EST) Date: Wed, 22 Mar 2000 04:15:42 -0500 (EST) From: "Matthew N. Dodd" To: Mitsuru IWASAKI Cc: freebsd-stable@FreeBSD.ORG Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... In-Reply-To: <200003220911.SAA11923@tasogare.imasy.or.jp> 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, 22 Mar 2000, Mitsuru IWASAKI wrote: > > Could I have this with the ep driver configured? > > Grrr, It's too difficult because I can't do anything after the messsage > even etner DDB or pause screen and back scrolling... Use the serial console. I have a feeling that you may have a version of the 3c509 that supports PnP but does not indicate that in the EEPROM config. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 1:39:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from student-mailhub.dcu.ie (ns.dcu.ie [136.206.1.3]) by hub.freebsd.org (Postfix) with ESMTP id DEB4337BA53 for ; Wed, 22 Mar 2000 01:39:01 -0800 (PST) (envelope-from drjolt@redbrick.dcu.ie) Received: from enigma.redbrick.dcu.ie (postfix@enigma.redbrick.dcu.ie [136.206.15.5]) by student-mailhub.dcu.ie (8.9.3/8.9.3/893-FD) with ESMTP id JAA31331 for ; Wed, 22 Mar 2000 09:39:00 GMT Received: by enigma.redbrick.dcu.ie (Postfix, from userid 2034) id 1193F7C94; Wed, 22 Mar 2000 09:37:10 +0000 (GMT) Date: Wed, 22 Mar 2000 09:37:09 +0000 From: David Murphy To: stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Message-ID: <20000322093709.A48595@enigma.redbrick.dcu.ie> References: <20000321170118.M5367@enigma.redbrick.dcu.ie> <20000322015400.B34538@enigma.redbrick.dcu.ie> <38D86EF7.2595FA9F@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38D86EF7.2595FA9F@gorean.org>; from Doug@gorean.org on Tue, Mar 21, 2000 at 10:57:59PM -0800 X-no-archive: yes Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting <38D86EF7.2595FA9F@gorean.org> by Doug Barton : > Actually what you see on the web page clearly stated in numerous > places is that upgrading from source is NOT for the faint of heart. > I put a sternly worded message in my 2.2.8->3.2 upgrade web page > that told the user that they would be better off using sysinstall. > But, that page isn't on a freebsd site, so I guess I don't win your > bet. I'm afraid not 8) > It's easy to fall into the trap of thinking that upgrade from source > is the preferred way to do it while reading the development lists, > but those lists are for developers. We have always recommended other > methods for general users. > Your point is well taken though, maybe it's time for a more clear > message in the handbook. Jim, you listening? :) It's probably even easier than you realise to fall into thinking source upgrades are the way to keep up with -stable, since what *is* in the handbook is section 18.2.2 [1], which says: "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.0-RELEASE at the time of this writing) since the stable branch is effectively a bug-fix stream relative to the previous release." It then goes on to explain about CTM, cvsup, etc. All this creates in the mind of the reader the perception that source updates are a valid way to keep a production system up to scratch. What's missing, what is *not* there (yet), is the proviso that general users should not try to use this method across major revisions. [1] http://www.freebsd.org/handbook/current-stable.html -- When asked if it is true that he uses his wheelchair as a weapon he will reply: "That's a malicious rumour. I'll run over anyone who repeats it." Stephen Hawking - [http://www.smh.com.au/news/0001/07/features/features1.html] David Murphy - For PGP public key, send mail with Subject: send-pgp-key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 1:39:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.13.27]) by hub.freebsd.org (Postfix) with ESMTP id 2BE3237C179 for ; Wed, 22 Mar 2000 01:39:39 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id JAA00348; Wed, 22 Mar 2000 09:45:08 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <00032119450200.18784@nomad.dataplex.net> Date: Wed, 22 Mar 2000 09:45:08 -0000 (GMT) From: "Steve O'Hara-Smith" To: Richard Wackerbarth Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for impro Cc: stable@FreeBSD.ORG, "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Mar-00 Richard Wackerbarth wrote: > On Tue, 21 Mar 2000, Jordan K. Hubbard wrote: >> Actually, the problem is that we ARE now doing good quality "dot-zero" >> releases > > IMHO, the problen is not so much the -RELEASE as it is the -STABLE which > preceeded it. I think we should continue to call 4.0 -CURRENT for a while and > change it to -STABLE only when we have enough tire kicking that we can, in > confidence, tell anyone to install it on their production system. (Perhaps > just > before 4.1 comes out). Alternative naming suggestion : 3.X -SOLID 4.X -STABLE 5.X -CURRENT The basis of this is that since 3.0 there have really been three tracks nearly all the time with the oldest being the most suitable for 'fit and forget' maximum reliablilty, the middle one for general use (with up to date features and hardware support) and the newest (-CURRENT) bleeding as much as it needs to for the sake of progress. Or aternatively viewed technology is developed on -CURRENT, matured in -STABLE and hammered under -SOLID. Then those that think -STABLE isn't good enough can be pointed to -SOLID with clear implications in the naming. Last time I looked stable did not necessarily carry the same sort of implications as solid. OK, so it's a daft idea. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 1:49: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from server.hmm.za.net (admin.bsdonline.org [196.28.82.142]) by hub.freebsd.org (Postfix) with ESMTP id D528637C15E for ; Wed, 22 Mar 2000 01:48:50 -0800 (PST) (envelope-from david@campsbay.za.net) Received: from DAVID (david [192.168.1.2]) by server.hmm.za.net (8.9.3/8.9.3) with SMTP id LAA00424 for ; Wed, 22 Mar 2000 11:50:04 +0200 (SAST) (envelope-from david@campsbay.za.net) Message-ID: <00ce01bf93e3$f7c538e0$0201a8c0@DAVID> From: "David" To: Subject: ep problem Date: Wed, 22 Mar 2000 11:49:48 +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.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No ep driver is working with FreeBSD 4.0-release i know that, it even stalls on install when i install from the boot disks... Now i would like to know if i downloaded 4.0-stable and boot disks from there would that fix the problem ? Would the boot disks work from there and the actual ep driver ? please respond bye ----- Original Message ----- From: "Mitsuru IWASAKI" To: Cc: ; Sent: Wednesday, March 22, 2000 11:11 AM Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... > > On Wed, 22 Mar 2000, Mitsuru IWASAKI wrote: > > > Certainly. Attached gzip+tar+uuencoded file contains > > > dmesg.boot - Output of a verbose boot (w/o ep driver in configuration). > > > > Could I have this with the ep driver configured? > > Grrr, It's too difficult because I can't do anything after the messsage > even etner DDB or pause screen and back scrolling... > > > > If `device ep' line is enabled in my configuration, the following > > > messages come up and boot procedure seems to stop... > > > > > > ep0: <3Com 3C509-TPO Etherlink III> at port 0x300-0x30f irq 10 on isa0 > > > ep0: eeprom failed to come ready. > > > ep0: eeprom failed to come ready. > > > ep0: eeprom failed to come ready. > > > ep0: eeprom failed to come ready. > > > ep0: eeprom failed to come ready. > > > ep0: Ethernet address 00:00:00:00:00:00 > > > > Yep, but I need the output of a verbose boot when you get this error > > message. > > I can get only last 24 lines but prior lines seems to be the same as > posted before. > > EGA/VGA parameters to be used for mode 24 > 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 > bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 > b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=0x200> > sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) > sio0: irq maps: 0x1 0x11 0x1 0x1 > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1: irq maps: 0x1 0x9 0x1 0x1 > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > mss_detect, busy still set (0xff) > ep0: <3Com 3C509-TPO Etherlink III> at port 0x300-0x30f irq 10 on isa0 > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: Ethernet address 00:00:00:00:00:00 > > Thanks. > > > 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 Mar 22 2:40:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id A23F037C171 for ; Wed, 22 Mar 2000 02:40:26 -0800 (PST) (envelope-from nbm@sunesi.net) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 12XiWZ-000A6i-00; Wed, 22 Mar 2000 12:38:03 +0200 Date: Wed, 22 Mar 2000 12:38:03 +0200 From: Neil Blakey-Milner To: Doug Barton Cc: David Murphy , "Jordan K. Hubbard" , stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Message-ID: <20000322123803.A38424@mithrandr.moria.org> References: <20000321170118.M5367@enigma.redbrick.dcu.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue 2000-03-21 (16:27), Doug Barton wrote: > Remarkably similar. We put the big, hairy, compatability breaking > changes in the major version bumps. We have learned a few lessons from the > last version upgrade cycle, some are left to be learned anew. In my opinion, the 3.4 -> 4.0 upgrade is remarkably painless. It's just the hairy explanations that are being thrown around about how to do it correctly in 25 steps. I've successfully done a 3.4 -> 4.0 upgrade in exactly these steps: cd /usr/src make buildworld make buildkernel make installkernel reboot (single) cd /usr/src make -k installworld make installworld That '-k installworld' is the only "fiddly" bit. No, I didn't "cd /dev && sh MAKEDEV all", since 4.0 seems to support the 'wd' compatibility perfectly. > Caveat compiler. We NEVER suggest that lusers (or, less > experienced users) upgrade from source, even for a point release. We > ALWAYS tell them to upgrade from CD, or wipe their disk and do a clean > install. If you choose the upgrade from source path, YOU take > responsibility for adequately educating yourself. Period, end of story. I think that's a bit strong. It is suggested that certain people track -STABLE, for example, and for the most part, it's painless. Tracking -CURRENT is a different story. I can't say I've seen a statement that says "ALWAYS upgrade via CD, do not use the source, since it's heavy wizardry". I started tracking -STABLE about 4 days after I installed FreeBSD, and I know many others (my "converts"), who do the same, and have no hassles. By being "STABLE", it means that the prescribed 'make world' upgrade path should work, unless specifically mentioned in UPDATING or similar. If there are hassles, then this list is the place to air them. Neil -- Neil Blakey-Milner nbm@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 3: 2:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from infos1.casaccia.enea.it (INFOS1.casaccia.enea.it [192.107.71.175]) by hub.freebsd.org (Postfix) with ESMTP id E080D37C172 for ; Wed, 22 Mar 2000 03:02:14 -0800 (PST) (envelope-from poggif@casaccia.enea.it) Received: from studi7106 (STUDI7106.casaccia.enea.it [192.107.77.106]) by infos1.casaccia.enea.it (8.9.1/8.9.1) with SMTP id MAA21805 for ; Wed, 22 Mar 2000 12:02:45 +0100 (MET) Message-Id: <3.0.5.32.20000322120150.00920100@infos1.casaccia.enea.it> X-Sender: poggif@infos1.casaccia.enea.it X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Wed, 22 Mar 2000 12:01:50 +0100 To: stable@FreeBSD.ORG From: Fabrizio Poggi Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for impro In-Reply-To: References: <00032119450200.18784@nomad.dataplex.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09.45 22/03/00 -0000, you wrote: > suggestion : > > 3.X -SOLID > 4.X -STABLE > 5.X -CURRENT > > OK, so it's a daft idea. That it seems better than stable/release/current. Good idea. If I take a look, I have the exact perspective of the degree of stability. Current & Stable are the best, Release is a bit obscure. It is possible from this mailing list launch suggestion for the development team? Regards, Fabrizio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 3:18: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.13.27]) by hub.freebsd.org (Postfix) with ESMTP id A731C37C1A5 for ; Wed, 22 Mar 2000 03:18:00 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id LAA00414; Wed, 22 Mar 2000 11:23:16 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3.0.5.32.20000322120150.00920100@infos1.casaccia.enea.it> Date: Wed, 22 Mar 2000 11:23:16 -0000 (GMT) From: "Steve O'Hara-Smith" To: Fabrizio Poggi Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for impro Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Mar-00 Fabrizio Poggi wrote: > At 09.45 22/03/00 -0000, you wrote: > > >> suggestion : >> >> 3.X -SOLID >> 4.X -STABLE >> 5.X -CURRENT >> >> OK, so it's a daft idea. > > That it seems better than stable/release/current. Good idea. If I take a Glad you like it, thanks. Just to clarify, RELEASE is a bit different in that -STABLE and -CURRENT are tracks of development while -RELEASE is a point on one of the tracks (usually -STABLE). There are expected (I think) to be releases on both the 3.x and 4.x tracks for a while. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 3:22: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from green.wl.vg (green.wl.vg.49.203.204.in-addr.arpa [204.203.49.94]) by hub.freebsd.org (Postfix) with ESMTP id B5B7737C0E7 for ; Wed, 22 Mar 2000 03:22:01 -0800 (PST) (envelope-from patrick@whetstonelogic.com) Received: from whetstonelogic.com (pathome [209.9.69.194]) by green.wl.vg (8.9.3/8.9.3) with ESMTP id DAA72775; Wed, 22 Mar 2000 03:21:29 -0800 (PST) (envelope-from patrick@whetstonelogic.com) Message-ID: <38D8ACCA.66037213@whetstonelogic.com> Date: Wed, 22 Mar 2000 06:21:46 -0500 From: Patrick Gardella Organization: Whetstone Logic, Inc. X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Brandon D. Valentine" Cc: FreeBSD-STABLE Subject: Re: SMP oddity References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Brandon D. Valentine" wrote: > > On Mon, 20 Mar 2000, Tod Luginbuhl wrote: > > >I am running 3.4-RELEASE on a dual Pentium-III 450mHz ASUS P2BDS > >system. I install the patch this afternoon by hand, rebuilt and install > >the new kernel. The information cpu clock speed information comes up > >correctly now when booting the new kernel. I haven't done extensive > >system testing yet, but the kernel seems to be stable. > > On that note, since I booted with the patched kernel the other day I > started up RC5 and gave the machine a good burn-in and it's running with > no problems whatsoever. In fact, I've had an ssh session open to it for > the past 72 hours that hasn't so much as hiccuped. Considering the > relative triviality of the patch and the fact that Mr. Luginbuhl echoes > my success I'd say it's a safe commit. It's been committed. Patrick ---------- Patrick Gardella patrick@whetstonelogic.com VP-Technology patrick@freebsd.org Whetstone Logic, Inc. This space intentionally left blank. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 3:29:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id B3A0D37C1A5 for ; Wed, 22 Mar 2000 03:29:27 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id D58711811B; Wed, 22 Mar 2000 12:28:52 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <19470.953701734@zippy.cdrom.com> References: <19470.953701734@zippy.cdrom.com> Date: Wed, 22 Mar 2000 11:48:51 +0100 To: "Jordan K. Hubbard" From: Brad Knowles Subject: Re: dot-0 releases Cc: David Murphy , FreeBSD-STABLE Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:08 PM -0800 2000/3/21, Jordan K. Hubbard wrote: > Should be no problem for you Brad, > you're a big dog, right? :) Dog? Yes, probably. Big? I don't think I'm qualified to answer that question. I feel like I'm only now beginning to start to really get into FreeBSD, although I've run 3.2-RELEASE on a production news peering server since last August. I had no bloody friggin' clue what I was doing then, but I figured it had to be better than the dead server it was replacing. I've just installed 4.0-STABLE on a second disk in the machine that will become our replacement news spool server, primarily to be able to play with things like vinum and rawio, and to see what it can do for me. I am still of the opinion that when this machine goes into production, it will probably be on 3.4-STABLE -- I just don't know 4.0-STABLE well enough yet. I ain't no Matt Dillon, Jordan K. Hubbard, Mike O'Dell, David Greenman, Doug Barton, Joe Greco, Mike Horwath, Russell Vincent, or anybody else like that. I like to think that I've learned a little something in the ten-plus years I've been doing Unix system administration, large-scale Internet mail systems administration, consulting, etc..., but I have a long ways to go before I can hope to compare to people like this. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 3:33:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.ddg.com (eunuch.ddg.com [216.30.58.66]) by hub.freebsd.org (Postfix) with ESMTP id 9CFBD37C05D for ; Wed, 22 Mar 2000 03:33:55 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from nomad.dataplex.net (24.28.73.209) by mail.ddg.com with SMTP (Eudora Internet Mail Server 2.1); Wed, 22 Mar 2000 05:33:54 -0600 From: Richard Wackerbarth To: Fabrizio Poggi Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for impro Date: Wed, 22 Mar 2000 05:26:12 -0600 X-Mailer: KMail [version 1.0.29] Content-Type: text/plain References: <00032119450200.18784@nomad.dataplex.net> <3.0.5.32.20000322120150.00920100@infos1.casaccia.enea.it> In-Reply-To: <3.0.5.32.20000322120150.00920100@infos1.casaccia.enea.it> Cc: stable@FreeBSD.ORG MIME-Version: 1.0 Message-Id: <00032205335100.01108@nomad.dataplex.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 22 Mar 2000, Fabrizio Poggi wrote: > At 09.45 22/03/00 -0000, you wrote: > > suggestion : > > > > 3.X -SOLID > > 4.X -STABLE > > 5.X -CURRENT > > > > OK, so it's a daft idea. > > That it seems better than stable/release/current. "-RELEASE" is not a state. It is a point in time. The other terms refer to the continuum between releases. I still think that "current" is misleading to newbies and should be called "development". > It is possible from this > mailing list launch suggestion for the development team? I don't think so. It seems that "its their sand box" and they really don't care how unfriendly their practices are to mere "users" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 3:58:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from nexus.plymovent.se (nexus.plymovent.se [212.247.77.253]) by hub.freebsd.org (Postfix) with ESMTP id 8FC9537C108 for ; Wed, 22 Mar 2000 03:58:43 -0800 (PST) (envelope-from thomas.uhrfelt@plymovent.se) Received: from tu ([192.168.1.21]) by nexus.plymovent.se (8.9.3/8.9.3) with SMTP id NAA91674; Wed, 22 Mar 2000 13:40:04 +0100 (CET) (envelope-from thomas.uhrfelt@plymovent.se) Received: by localhost with Microsoft MAPI; Wed, 22 Mar 2000 12:59:13 +0100 Message-ID: <01BF93FE.6BFBBEE0.thomas.uhrfelt@plymovent.se> From: Thomas Uhrfelt Reply-To: "thomas.uhrfelt@plymovent.se" To: "'Richard Wackerbarth'" Cc: "'freebsd-stable@freebsd.org'" Subject: SV: Voxware is toast. Get used to it. (Re: Suggestions for impro Date: Wed, 22 Mar 2000 12:59:12 +0100 Organization: PlymoVent AB X-Mailer: Microsoft Internet-e-post/MAPI - 8.0.0.4211 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 > "-RELEASE" is not a state. It is a point in time. > The other terms refer to the continuum between releases. > > I still think that "current" is misleading to newbies and should be called > "development". I have no religious views at all on the subject, so either way is fine by me. The reason why it's called CURRENT I belive is due to the fact thats where the focal point on the project is. New things gets adopted and basically - that's where FreeBSD is, not neccessarily the users. > > It is possible from this > > mailing list launch suggestion for the development team? > > I don't think so. It seems that "its their sand box" and they really don't care > how unfriendly their practices are to mere "users" Your statement is highly unfair, I have been swimming in this community pond for the last 18 months, and I never experienced the core as elitist or anything near that. Not to mention that the FreeBSD support model is unparalleled. I get better support from the FreeBSD community that I do from $10K support contracts. Regards, Thomas Uhrfelt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 4: 4:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.13.27]) by hub.freebsd.org (Postfix) with ESMTP id A88BA37BB66 for ; Wed, 22 Mar 2000 04:04:13 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id MAA00447; Wed, 22 Mar 2000 12:09:37 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <00032205335100.01108@nomad.dataplex.net> Date: Wed, 22 Mar 2000 12:09:37 -0000 (GMT) From: "Steve O'Hara-Smith" To: Richard Wackerbarth Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for impro Cc: stable@FreeBSD.ORG, Fabrizio Poggi Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Mar-00 Richard Wackerbarth wrote: >> It is possible from this >> mailing list launch suggestion for the development team? > > I don't think so. It seems that "its their sand box" and they really don't > care > how unfriendly their practices are to mere "users" I think that is unfair (and I am not in core or committers or even much of a contributer). The main developers of FreeBSD do read this list and do respond to suggestions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 4:18:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.icehouse.net (mail.icehouse.net [204.203.53.2]) by hub.freebsd.org (Postfix) with ESMTP id 6F06F37B881 for ; Wed, 22 Mar 2000 04:18:50 -0800 (PST) (envelope-from franco@icehouse.net) Received: from localhost.localdomain (webmail.icehouse.net [204.203.53.38]) by mail.icehouse.net (8.9.3/8.9.3/Debian/GNU) with ESMTP id EAA09775; Wed, 22 Mar 2000 04:11:30 -0800 Received: (from nobody@localhost) by localhost.localdomain (8.9.3/8.9.3) id EAA03295; Wed, 22 Mar 2000 04:11:27 -0800 Date: Wed, 22 Mar 2000 04:11:27 -0800 Message-Id: <200003221211.EAA03295@localhost.localdomain> X-Authentication-Warning: localhost.localdomain: nobody set sender to franco@icehouse.net using -f From: Franco Gasperino To: Neil Blakey-Milner Reply-To: Franco Gasperino Cc: Doug Barton , David Murphy , "Jordan K. Hubbard" , stable@FreeBSD.ORG References: <20000321170118.M5367@enigma.redbrick.dcu.ie> <20000322123803.A38424@mithrandr.moria.org> In-Reply-To: <20000322123803.A38424@mithrandr.moria.org> MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP3 Imap webMail Program 2.0.11 Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Neil Blakey-Milner : [snip] > I've successfully done a 3.4 -> 4.0 upgrade in exactly these steps: > > cd /usr/src > make buildworld > make buildkernel > make installkernel > reboot (single) > cd /usr/src > make -k installworld > make installworld > > That '-k installworld' is the only "fiddly" bit. [snip] As a C programmer, and Linux user for about 5 years, im very comfortable with my recent changes to free/open bsds. I find them very refreshing. But, With the handbook saying to cvsup, then makeworld (which failed for me), or the UPGRADING file saying buildworld (which worked for me and really shouldn't be at the bottom of the file =)), then 'install kernel as usual', with that being different on the web site than what's above, i've bombed my system. I'm not upset in the least, always some potholes in the road, and i'm very impressed with what this system has done thus far compared to any linux distro. But i believe someone needs to release a "File to end all questions" on exactly HOW to upgrade from source. Maybe subsections on the web site? > > Neil > -- Franco Gasperino Network Administrator Icehouse Net Services 509-444-1590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 4:28: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 4534D37B986 for ; Wed, 22 Mar 2000 04:28:01 -0800 (PST) (envelope-from mmercer@ipass.net) Received: from ipass.net (dsl-2-196.dsl.rdu.ipass.net [209.170.144.196] (may be forged)) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id HAA12149; Wed, 22 Mar 2000 07:27:50 -0500 (EST) Message-ID: <38D8BC46.7BBC0FF9@ipass.net> Date: Wed, 22 Mar 2000 07:27:51 -0500 From: "Michael E. Mercer" Reply-To: mmercer@ipass.net X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Matthew N. Dodd" Cc: Mitsuru IWASAKI , freebsd-stable@FreeBSD.ORG Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good morning all, I had to boot to WinBlows and set the PnP mode on the card itself off. When I did that, everything worked. This involved running a batch file on Disk 2 that was supplied with the card, but I had to install a different driver, the one for ISA mode, the driver that was installed was for PnP mode. This is what is actually painful to accomplish... Mitsuru, Now how you can capture the dmesg output, just boot to single user mode boot -s mount -a dmesg this should get all information easily enough. Matthew, If you still want me to try to reproduce the problem, I will but it will have to wait for the weekend. My wife was upset enough she had no computer for 2 days while I upgraded... later Michael Mercer mmercer@ipass.net "Matthew N. Dodd" wrote: > On Wed, 22 Mar 2000, Mitsuru IWASAKI wrote: > > > Could I have this with the ep driver configured? > > > > Grrr, It's too difficult because I can't do anything after the messsage > > even etner DDB or pause screen and back scrolling... > > Use the serial console. > > I have a feeling that you may have a version of the 3c509 that supports > PnP but does not indicate that in the EEPROM config. > > -- > | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | > | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | > | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-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 Mar 22 4:38:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from twizors.rug.ac.be (twizors.rug.ac.be [157.193.55.153]) by hub.freebsd.org (Postfix) with ESMTP id 7F83337B8CB for ; Wed, 22 Mar 2000 04:38:11 -0800 (PST) (envelope-from ageorges@twizors.rug.ac.be) Received: from localhost (ageorges@localhost) by twizors.rug.ac.be (8.9.3/8.9.3) with ESMTP id NAA02372; Wed, 22 Mar 2000 13:44:20 +0100 (CET) (envelope-from ageorges@twizors.rug.ac.be) Date: Wed, 22 Mar 2000 13:44:20 +0100 (CET) From: Andy Georges To: Thomas Uhrfelt Cc: "'Richard Wackerbarth'" , "'freebsd-stable@freebsd.org'" Subject: Re: SV: Voxware is toast. Get used to it. (Re: Suggestions for impro In-Reply-To: <01BF93FE.6BFBBEE0.thomas.uhrfelt@plymovent.se> 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 > > "-RELEASE" is not a state. It is a point in time. > > The other terms refer to the continuum between releases. i used to have some problems understanding the difference between -STABLE and -RELEASE but i think this points it out nicely > I have no religious views at all on the subject, so either way is fine by > me. The reason why it's called CURRENT I belive is due to the fact thats > where the focal point on the project is. New things gets adopted and > basically - that's where FreeBSD is, not neccessarily the users. -CURRENT looks like a good name to me, but one should still inform new users that it's the edge. Once you have read that in the handbook or someplace else, i feel you know enough to decide with what you'll go. -- zors To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 4:48:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 20E3437B986 for ; Wed, 22 Mar 2000 04:48:30 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id HAA55319; Wed, 22 Mar 2000 07:48:23 -0500 (EST) Date: Wed, 22 Mar 2000 07:48:22 -0500 (EST) From: "Matthew N. Dodd" To: "Michael E. Mercer" Cc: Mitsuru IWASAKI , freebsd-stable@FreeBSD.ORG Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... In-Reply-To: <38D8BC46.7BBC0FF9@ipass.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 Wed, 22 Mar 2000, Michael E. Mercer wrote: > I had to boot to WinBlows and set the PnP mode on the card itself off. > When I did that, everything worked. This involved running a batch file > on Disk 2 that was supplied with the card, but I had to install a > different driver, the one for ISA mode, the driver that was installed > was for PnP mode. This is what is actually painful to accomplish... Uh. Boot DOS. Get the 3c509 driver/util disk. Run '3C5X9CFG'. No drivers or booting of windows required. > If you still want me to try to reproduce the problem, I will but it > will have to wait for the weekend. My wife was upset enough she had no > computer for 2 days while I upgraded... As you like it. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 4:54:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.ddg.com (eunuch.ddg.com [216.30.58.66]) by hub.freebsd.org (Postfix) with ESMTP id 6D3A537BAE9 for ; Wed, 22 Mar 2000 04:54:05 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from nomad.dataplex.net (24.28.73.209) by mail.ddg.com with SMTP (Eudora Internet Mail Server 2.1); Wed, 22 Mar 2000 06:54:01 -0600 From: Richard Wackerbarth To: thomas.uhrfelt@plymovent.se Subject: Re: SV: Voxware is toast. Get used to it. (Re: Suggestions for impro Date: Wed, 22 Mar 2000 06:24:14 -0600 X-Mailer: KMail [version 1.0.29] Content-Type: text/plain Cc: freebsd-stable@freebsd.org References: <01BF93FE.6BFBBEE0.thomas.uhrfelt@plymovent.se> In-Reply-To: <01BF93FE.6BFBBEE0.thomas.uhrfelt@plymovent.se> MIME-Version: 1.0 Message-Id: <00032206535801.01108@nomad.dataplex.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 22 Mar 2000, Thomas Uhrfelt wrote: > > "-RELEASE" is not a state. It is a point in time. > > The other terms refer to the continuum between releases. > > > > I still think that "current" is misleading to newbies and should be > called > > "development". > > I have no religious views at all on the subject, so either way is fine by > me. The reason why it's called CURRENT I belive is due to the fact thats > where the focal point on the project is. New things gets adopted and > basically - that's where FreeBSD is, not neccessarily the users. Yes, I understand the basis. FreeBSD was viewed as a DEVELOPMENT project and everything was referenced in that context > > > It is possible from this > > > mailing list launch suggestion for the development team? > > > > I don't think so. It seems that "its their sand box" and they really > > don't care how unfriendly their practices are to mere "users" > > Your statement is highly unfair, I have been swimming in this community > pond for the last 18 months, and I never experienced the core as elitist or > anything near that. Only 18 months! I've got FreeBSD systems still up that haven't been rebooted in that period. Unfortunately, Moore's Law may be the uptime killer :-) Before you pass judgment, you should read some of the "You F&*(&king idiot, RTFM!" replies that used to go out in response to questions from new, would be, users. > Not to mention that the FreeBSD support model is > unparalleled. I get better support from the FreeBSD community that I do > from $10K support contracts. I don't dispute this at all. It IS one of the real selling points. However, IMHO, FreeBSD has a "reputation" for being (to be polite) "elitist". If the project ever wants to break out of the "developer's sandbox", it MUST attract "mere users". I think that many of the developers ignore the "tax" that they pay in answering the same support questions over and over. The developers are so set in their ways that they fail to accept the fact that "cosmetic" changes can have real benefit. There is a pervasive "if it's not code, it's worthless" attitude. They prefer to make others suffer so they can continue in their comfortable ruts. That's why I call it a "developer's sandbox". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 4:56:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from infos1.casaccia.enea.it (INFOS1.casaccia.enea.it [192.107.71.175]) by hub.freebsd.org (Postfix) with ESMTP id 67AE737B986 for ; Wed, 22 Mar 2000 04:55:52 -0800 (PST) (envelope-from poggif@casaccia.enea.it) Received: from studi7106 (STUDI7106.casaccia.enea.it [192.107.77.106]) by infos1.casaccia.enea.it (8.9.1/8.9.1) with SMTP id NAA28611; Wed, 22 Mar 2000 13:56:32 +0100 (MET) Message-Id: <3.0.5.32.20000322135537.0091ae90@infos1.casaccia.enea.it> X-Sender: poggif@infos1.casaccia.enea.it X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Wed, 22 Mar 2000 13:55:37 +0100 To: Richard Wackerbarth From: Fabrizio Poggi Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for impro Cc: stable@FreeBSD.ORG In-Reply-To: <00032205335100.01108@nomad.dataplex.net> References: <3.0.5.32.20000322120150.00920100@infos1.casaccia.enea.it> <00032119450200.18784@nomad.dataplex.net> <3.0.5.32.20000322120150.00920100@infos1.casaccia.enea.it> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05.26 22/03/00 -0600, Richard Wackerbarth wrote: >"-RELEASE" is not a state. It is a point in time. >The other terms refer to the continuum between releases. > >I still think that "current" is misleading to newbies and should be called >"development". I *know* that -RELEASE is misleading fo newbies----;)) Regards, Fabrizio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 5: 1:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id 7AF2037B5CB for ; Wed, 22 Mar 2000 05:01:36 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id IAA11472; Wed, 22 Mar 2000 08:01:30 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id IAA02636; Wed, 22 Mar 2000 08:01:28 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id IAA22823; Wed, 22 Mar 2000 08:01:27 -0500 (EST) Date: Wed, 22 Mar 2000 08:01:27 -0500 (EST) From: Thomas David Rivers Message-Id: <200003221301.IAA22823@lakes.dignus.com> To: jkh@zippy.cdrom.com, witr@rwwa.com Subject: V4.0 and Walnut Creek Subscriptions... Cc: stable@FreeBSD.ORG, witr@pobox.rwwa.com In-Reply-To: <18573.953685546@zippy.cdrom.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hold the presses. I'm talking with Walnut Creek CDROM right now about > just sending 4.0 to the subscribers after all. You're about the > 2000th person to ask me. :) > > - Jordan > Uh... wait... Yesterday (Tuesday), following the previous instructions, I sent Walnut Creek an order form; and they said they'll be happy to charge my credit card, and my order was processed, etc... Will I now get *two* copies of 4.0? I think we're now "mid-stream" and changing horses isn't best done here... - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 5: 9:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 359A037B625 for ; Wed, 22 Mar 2000 05:09:25 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id IAA55556; Wed, 22 Mar 2000 08:08:51 -0500 (EST) Date: Wed, 22 Mar 2000 08:08:51 -0500 (EST) From: "Matthew N. Dodd" To: David Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ep problem In-Reply-To: <00ce01bf93e3$f7c538e0$0201a8c0@DAVID> 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, 22 Mar 2000, David wrote: > No ep driver is working with FreeBSD 4.0-release i know that, it even > stalls on install when i install from the boot disks... More info? What does it say on bootup? Are you using the config editor to disable other ISA devices that you don't have? > Now i would like to know if i downloaded 4.0-stable and boot disks > from there would that fix the problem ? Would the boot disks work from > there and the actual ep driver ? please respond bye I've got just about every version of the 3c509 and an example of the EISA and PCMCIA cards; all of them work. Provide more details before you make broad statements. > ----- Original Message ----- > From: "Mitsuru IWASAKI" > To: > Cc: ; > Sent: Wednesday, March 22, 2000 11:11 AM > Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... > > > > > On Wed, 22 Mar 2000, Mitsuru IWASAKI wrote: > > > > Certainly. Attached gzip+tar+uuencoded file contains > > > > dmesg.boot - Output of a verbose boot (w/o ep driver in > configuration). > > > > > > Could I have this with the ep driver configured? > > > > Grrr, It's too difficult because I can't do anything after the messsage > > even etner DDB or pause screen and back scrolling... > > > > > > If `device ep' line is enabled in my configuration, the following > > > > messages come up and boot procedure seems to stop... > > > > > > > > ep0: <3Com 3C509-TPO Etherlink III> at port 0x300-0x30f irq 10 on isa0 > > > > ep0: eeprom failed to come ready. > > > > ep0: eeprom failed to come ready. > > > > ep0: eeprom failed to come ready. > > > > ep0: eeprom failed to come ready. > > > > ep0: eeprom failed to come ready. > > > > ep0: Ethernet address 00:00:00:00:00:00 > > > > > > Yep, but I need the output of a verbose boot when you get this error > > > message. > > > > I can get only last 24 lines but prior lines seems to be the same as > > posted before. > > > > EGA/VGA parameters to be used for mode 24 > > 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 > > bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 > > b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c > > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff > > sc0: on isa0 > > sc0: VGA <16 virtual consoles, flags=0x200> > > sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) > > sio0: irq maps: 0x1 0x11 0x1 0x1 > > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > > sio0: type 16550A > > sio1: irq maps: 0x1 0x9 0x1 0x1 > > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > > sio1: type 16550A > > mss_detect, busy still set (0xff) > > ep0: <3Com 3C509-TPO Etherlink III> at port 0x300-0x30f irq 10 on isa0 > > ep0: eeprom failed to come ready. > > ep0: eeprom failed to come ready. > > ep0: eeprom failed to come ready. > > ep0: eeprom failed to come ready. > > ep0: eeprom failed to come ready. > > ep0: Ethernet address 00:00:00:00:00:00 > > > > Thanks. > > > > > > 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 > -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 5:14:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from nexus.plymovent.se (nexus.plymovent.se [212.247.77.253]) by hub.freebsd.org (Postfix) with ESMTP id 01F7137B5FC for ; Wed, 22 Mar 2000 05:14:22 -0800 (PST) (envelope-from thomas.uhrfelt@plymovent.se) Received: from tu ([192.168.1.21]) by nexus.plymovent.se (8.9.3/8.9.3) with SMTP id OAA92389; Wed, 22 Mar 2000 14:55:44 +0100 (CET) (envelope-from thomas.uhrfelt@plymovent.se) Received: by localhost with Microsoft MAPI; Wed, 22 Mar 2000 14:14:49 +0100 Message-ID: <01BF9408.FBFEEB20.thomas.uhrfelt@plymovent.se> From: Thomas Uhrfelt Reply-To: "thomas.uhrfelt@plymovent.se" To: "'Richard Wackerbarth'" Cc: "'freebsd-stable@freebsd.org'" Subject: SV: SV: Voxware is toast. Get used to it. (Re: Suggestions for impro Date: Wed, 22 Mar 2000 14:14:48 +0100 Organization: PlymoVent AB X-Mailer: Microsoft Internet-e-post/MAPI - 8.0.0.4211 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 > > Your statement is highly unfair, I have been swimming in this community > > pond for the last 18 months, and I never experienced the core as elitist or > > anything near that. > > Only 18 months! I've got FreeBSD systems still up that haven't been rebooted in > that period. Unfortunately, Moore's Law may be the uptime killer :-) > > Before you pass judgment, you should read some of the > "You F&*(&king idiot, RTFM!" replies that used to go out in response to > questions from new, would be, users. Sorry, I might have been a bit vague - I have looked at FreeBSD on and off for the last 3 or 4 years - but didnt put it in professional production usage until about 18 months - and then I started to leech on all the knowledge the community posses to solve some problems. And yes I know some answers in the past been more than a little unfriendly, but I don't blame them. I can take a GO RTFM answer - because I know I somtimes is a bit overly lazy and want a quick answer. But knowledge isnt like FreeBSD - it doesn't come for free. I am by you standards probably a new user, but I feel like this: - if I want to use "their" software to run "my" system .. it's up to me to make the best of it. Please don't take this as an OK to be rude or anything to new users, it's just that I feel like many "would be" users wants to much served on their plate - too fast. > > Not to mention that the FreeBSD support model is > > unparalleled. I get better support from the FreeBSD community that I do > > from $10K support contracts. > > I don't dispute this at all. It IS one of the real selling points. > > However, IMHO, FreeBSD has a "reputation" for being (to be polite) "elitist". > If the project ever wants to break out of the "developer's sandbox", it MUST > attract "mere users". I belive it has already broken out of the developers sandbox. And I don't think it's a wish from the current general FreeBSD population that we should attract more first-timers in masses. I could be wrong on this one I know .. but it's still my impression. > I think that many of the developers ignore the "tax" that they pay in answering > the same support questions over and over. This is very true indeed, but I don't want those changes in the system .. I want updates in the handbook and the FAQ. > The developers are so set in their > ways that they fail to accept the fact that "cosmetic" changes can have real > benefit. There is a pervasive "if it's not code, it's worthless" attitude. They > prefer to make others suffer so they can continue in their comfortable ruts. > That's why I call it a "developer's sandbox". This is actually one of the reasons I like FreeBSD so much (but it also annoys me sometimes ofcourse) .. I don't feel comfortable with a oneclick checkbox doing multiple operations. FreeBSD forces me to think each step though and this in the end will save me a lot of headaches. I am by no means a unix guru or anything - but for a guy coming from the win32 and OS2 camp .. it's certainly refreshing. Thomas Uhrfelt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 5:38:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from erouter0.it-datacntr.louisville.edu (erouter0.it-datacntr.louisville.edu [136.165.1.36]) by hub.freebsd.org (Postfix) with ESMTP id 4BB4537B99A for ; Wed, 22 Mar 2000 05:38:08 -0800 (PST) (envelope-from k.stevenson@louisville.edu) Received: from osaka.louisville.edu (osaka.louisville.edu [136.165.1.114]) by erouter0.it-datacntr.louisville.edu (Postfix) with ESMTP id 9227A24F5B; Wed, 22 Mar 2000 08:38:08 -0500 (EST) Received: by osaka.louisville.edu (Postfix, from userid 15) id E09A018605; Wed, 22 Mar 2000 08:38:07 -0500 (EST) Date: Wed, 22 Mar 2000 08:38:07 -0500 From: Keith Stevenson To: "Matthew N. Dodd" Cc: "Michael E. Mercer" , Mitsuru IWASAKI , freebsd-stable@FreeBSD.ORG Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... Message-ID: <20000322083807.C8858@osaka.louisville.edu> References: <38D8BC46.7BBC0FF9@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 22, 2000 at 07:48:22AM -0500, Matthew N. Dodd wrote: > > Boot DOS. > > Get the 3c509 driver/util disk. > > Run '3C5X9CFG'. > > No drivers or booting of windows required. > I saw a similar problem when I upgraded from 3.4-RELEASE to 5.0-CURRENT. My ep card started fine under 3.4, but choked with the eeprom messages when booting my new current kernel. I was able to get my card working by booting into the kernel configuration tool (boot -c) and disabling all of the other network devices which were compiled in. (This was with a generic kernel.) Once I had done that, the ep driver was able to work with my card. (Strangely enough, the ep driver doesn't appear anywhere in the kernel config screen.) Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville k.stevenson@louisville.edu PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 5:46:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 1CFDD37BB4F for ; Wed, 22 Mar 2000 05:46:55 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id IAA55926; Wed, 22 Mar 2000 08:46:49 -0500 (EST) Date: Wed, 22 Mar 2000 08:46:49 -0500 (EST) From: "Matthew N. Dodd" To: Keith Stevenson Cc: "Michael E. Mercer" , Mitsuru IWASAKI , freebsd-stable@FreeBSD.ORG Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... In-Reply-To: <20000322083807.C8858@osaka.louisville.edu> 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, 22 Mar 2000, Keith Stevenson wrote: > I saw a similar problem when I upgraded from 3.4-RELEASE to > 5.0-CURRENT. My ep card started fine under 3.4, but choked with the > eeprom messages when booting my new current kernel. I was able to get > my card working by booting into the kernel configuration tool (boot > -c) and disabling all of the other network devices which were compiled > in. (This was with a generic kernel.) Once I had done that, the ep > driver was able to work with my card. Yep. Its likely some of the 'legacy' (non-newbus) drivers stomp on the card. You should -always- disable devices that you don't have in your system. > (Strangely enough, the ep driver doesn't appear anywhere in the kernel > config screen.) Correct. The 'ep' driver in 4.0/current doesn't have any need for the user to specify settings. The kernel config screen is really for devices that are so broken that we can't 'ask' them what their configuration is or otherwise discover it unassisted. Ideally all drivers should use non-destructive probes and should attempt to discover cards and configurations without user intervention. Some hardware is too stupid for this and in other cases, the drivers need to be 'fixed'. I was only able to beat up the 'ep' and 'ex' drivers (and even then there are still problems.) The other problem is that we've got no really good way to ask the resource manager 'has someone reserved this resource for future use?' This too is being addressed. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 6: 0:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.ddg.com (eunuch.ddg.com [216.30.58.66]) by hub.freebsd.org (Postfix) with ESMTP id B2E4537BB4F for ; Wed, 22 Mar 2000 06:00:13 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from nomad.dataplex.net (24.28.73.209) by mail.ddg.com with SMTP (Eudora Internet Mail Server 2.1); Wed, 22 Mar 2000 08:00:11 -0600 From: Richard Wackerbarth To: thomas.uhrfelt@plymovent.se Subject: Re: Get used to it. Date: Wed, 22 Mar 2000 07:23:25 -0600 X-Mailer: KMail [version 1.0.29] Content-Type: text/plain Cc: freebsd-stable@freebsd.org References: <01BF9408.FBFEEB20.thomas.uhrfelt@plymovent.se> In-Reply-To: <01BF9408.FBFEEB20.thomas.uhrfelt@plymovent.se> MIME-Version: 1.0 Message-Id: <00032208000803.01108@nomad.dataplex.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 22 Mar 2000, Thomas Uhrfelt wrote: > And yes I know some > answers in the past been more than a little unfriendly, but I don't blame > them. I can take a GO RTFM answer Yes, but that is only because you are knowledgable of the culture. As computers have gotten bigger and faster, the OS has become much more complicated. The learning curve is huge. Even after decades, I don't pretend to know how many parts of it work. I am quite happy to treat those parts as "black boxes" unless I need to tweek them. > I feel like this: - if I want to use "their" software to run "my" system .. That's the fundamental problem -- an "us" and "them" attitude. Until it becomes an "our" attitude, the schism will continue to limit the "community". > I get better support from the FreeBSD community that I do from $10K > support contracts. Yes, the real value is in the COMMUNITY. > I belive it has already broken out of the developers sandbox. And I don't > think it's a wish from the current general FreeBSD population that we > should attract more first-timers in masses. I could be wrong on this one I > know .. but it's still my impression. We need to work toward developing a "knowledge ladder". By chopping off the bottom rungs, you guarantee that, in the long run, the community will wither. When it finally comes down to the bottom line, a growing community with "acceptable" technology will beat out the "elitist niche" even though they have superior technology. > This is very true indeed, but I don't want those changes in the system .. I > want updates in the handbook and the FAQ. Beef up the suspension on every vehicle rather than straightening and paving the road :-) > I don't feel comfortable with a oneclick > checkbox doing multiple operations. FreeBSD forces me to think each step > though "One click" solutions save a lot of time... if, and it's a big IF, 1) The developer of the button really designs it correctly 2) There is an over-ride so that it is not the only option. > and this in the end will save me a lot of headaches. Only if you are ever able to get started. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 6:30:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from shemp.palomine.net (shemp.palomine.net [205.198.88.200]) by hub.freebsd.org (Postfix) with SMTP id 86A5837BB0A for ; Wed, 22 Mar 2000 06:30:29 -0800 (PST) (envelope-from cjohnson@palomine.net) Received: (qmail 55522 invoked by uid 1000); 22 Mar 2000 14:30:22 -0000 Date: Wed, 22 Mar 2000 09:30:22 -0500 From: Chris Johnson To: stable@freebsd.org Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Message-ID: <20000322093022.A55380@palomine.net> References: <20000321170118.M5367@enigma.redbrick.dcu.ie> <20000322123803.A38424@mithrandr.moria.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000322123803.A38424@mithrandr.moria.org>; from nbm@mithrandr.moria.org on Wed, Mar 22, 2000 at 12:38:03PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 22, 2000 at 12:38:03PM +0200, Neil Blakey-Milner wrote: > In my opinion, the 3.4 -> 4.0 upgrade is remarkably painless. I'll go along with that. I've been surprised by all these reports of how hairy the upgrade procedure is. I did it, and found myself saying, "That's it?" > I've successfully done a 3.4 -> 4.0 upgrade in exactly these steps: > > cd /usr/src > make buildworld > make buildkernel > make installkernel > reboot (single) > cd /usr/src > make -k installworld > make installworld This is what I did, and I even did it multi-user. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 7: 6:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id 0B6E637C077 for ; Wed, 22 Mar 2000 07:06:47 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id E1BDEE897 for ; Wed, 22 Mar 2000 10:06:44 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id KAA27763; Wed, 22 Mar 2000 10:06:44 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14552.57732.739752.665443@onceler.kcilink.com> Date: Wed, 22 Mar 2000 10:06:44 -0500 (EST) To: stable@FreeBSD.ORG Subject: "dangerously dedicated" In-Reply-To: <200003212255.PAA26291@harmony.village.org> References: <4.3.2.20000321160347.00ad9b20@207.227.119.2> <38D50DBC.88FA8E4D@glue.umd.edu> <38D3AB72.366D851D@glue.umd.edu> <200003152159.OAA89926@harmony.village.org> <38D03E64.3D17FC34@glue.umd.edu> <200003190433.VAA04863@harmony.village.org> <200003212255.PAA26291@harmony.village.org> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "WL" == Warner Losh writes: WL> In message <4.3.2.20000321160347.00ad9b20@207.227.119.2> "Jeffrey J. Mountin" writes: WL> : Are you saying that da0a is (almost) functionally equivalent to WL> da0s3a if : slice 3 is the first FBSD slice. Thought they were WL> for "dangerously : dedicated" partitions. WL> No. That's not correct. While they are used in dangerously (and WL> stupidly) dedicated mode, they can be used at any time. I still have WL> some mount points on my -current machine that refer to sd1c because WL> I've been too lazy to update them. Why is using /dev/da0a stupid? FreeBSD is the only system I've encountered that totally locks up (during a 3.3-RELEASE install from CD) when there is no fdisk disk label. Is that why it is stupid? BSD/OS and Linux (RedHat 6.1) both deal with the lack of an fdisk disk label just fine, and BSD/OS doesn't even require one, letting you use the direct unix partitioning scheme. I much prefer it that way as it just makes sense on a dedicated box, which is what all of mine are. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 PGP & MIME spoken here http://www.kciLink.com/home/khera/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 7:31: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id D1D7337BA53; Wed, 22 Mar 2000 07:31:03 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA02106; Wed, 22 Mar 2000 10:31:03 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id KAA07654; Wed, 22 Mar 2000 10:30:33 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 22 Mar 2000 10:30:32 -0500 (EST) To: Howard Leadmon Cc: freebsd-alpha@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Compiler problems with -O2 (was Re: CVS Trouble, even under 4.0-RELEASE (alpha) HELP!) In-Reply-To: <200003220628.BAA97796@account.abs.net> References: <200003220628.BAA97796@account.abs.net> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14552.58589.119082.742615@grasshopper.cs.duke.edu> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Get rid of -O2 in /etc/make.conf; comment out the CFLAGS line. You should NEVER, EVER build _anything_ with -O2 on an alpha. The compiler is very fragile and has been known to do odd things when compiling -O2. I'm starting to think that any optimizations other than -O should probably be disabled in the compiler to keep people from blowing their feet off like you've just done. I'd suggest re-loading the machine from the cd at this point, or building a world on another machine which has a good world & doing a make installworld via NFS mounts. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 7:32:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kcmso1.proxy.att.com (kcmso1.att.com [192.128.133.69]) by hub.freebsd.org (Postfix) with ESMTP id DE02537B56B for ; Wed, 22 Mar 2000 07:32:23 -0800 (PST) (envelope-from jwb@homer.att.com) Received: from ulysses.homer.att.com ([135.205.193.4]) by kcmso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id KAA04463 for ; Wed, 22 Mar 2000 10:32:22 -0500 (EST) Received: from akiva.homer.att.com (akiva.homer.att.com [135.205.198.103]) by ulysses.homer.att.com (8.9.3/8.9.3) with ESMTP id KAA04414 for ; Wed, 22 Mar 2000 10:32:21 -0500 (EST) Received: from akiva.homer.att.com (localhost [127.0.0.1]) by akiva.homer.att.com (8.8.8+Sun/8.8.8) with ESMTP id KAA10998 for ; Wed, 22 Mar 2000 10:32:21 -0500 (EST) Message-Id: <200003221532.KAA10998@akiva.homer.att.com> X-Mailer: exmh version 2.0.3 3/22/1999 To: freebsd-stable@FreeBSD.ORG Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions [Failure] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 22 Mar 2000 10:32:20 -0500 From: "J. W. Ballantine" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sometime in recorded history Warner Losh wrote: Let me know if the following doesn't work: > To update from 3.x to 4.0 stable > -------------------------------- > cd /usr/src > make buildworld > cd sbin/mknod > make install > > [*] > reboot > > cd /usr/src > make -DNOINFO installworld > make installworld > > [*] You may need to switch from wd to ad ala 19991210 > > To build a kernel > ----------------- > Update config, genassym and go: > cd src/usr.bin/genassym > make depend all install > cd ../../usr.sbin/config > make depend all install > cd ../../sys/i386/conf > config YOUR_KERNEL_HERE > cd ../../compile/YOUR_KERNEL_HERE > make depend && make > make install > > To rebuild disk /dev entries > ---------------------------- > > MAKEDEV should be copied from src/etc/MAKEDEV to /dev before > starting the following: > > For N in the list of disks > MAKEDEV N # eg ad0 > for M in the list of slices > MAKEDEV NsMa # eg ad0s1a > So, being the brave (and foolish) soul, I set my cvsup releng tag to RELENG_4 and cvsup the sources with src-all and cvs-crypto. I then edit /etc/make.conf to set USA_RESIDENT, cd to /usr/src and do a make buildworld and it starts: -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- rm -rf /usr/obj/usr/src/i386 mkdir -p /usr/obj/usr/src/i386/usr/bin mkdir -p /usr/obj/usr/src/i386/usr/lib/compat/aout mkdir -p /usr/obj/usr/src/i386/usr/games mkdir -p /usr/obj/usr/src/i386/usr/libdata/ldscripts mkdir -p /usr/obj/usr/src/i386/usr/libexec/elf mkdir -p /usr/obj/usr/src/i386/usr/sbin mkdir -p /usr/obj/usr/src/i386/usr/share/misc mkdir -p /usr/obj/usr/src/i386/usr/include/arpa mkdir -p /usr/obj/usr/src/i386/usr/include/g++/std mkdir -p /usr/obj/usr/src/i386/usr/include/objc mkdir -p /usr/obj/usr/src/i386/usr/include/protocols mkdir -p /usr/obj/usr/src/i386/usr/include/readline mkdir -p /usr/obj/usr/src/i386/usr/include/rpc mkdir -p /usr/obj/usr/src/i386/usr/include/rpcsvc mkdir -p /usr/obj/usr/src/i386/usr/include/openssl mkdir -p /usr/obj/usr/src/i386/usr/include/security mkdir -p /usr/obj/usr/src/i386/usr/include/ss ln -sf /usr/src/sys /usr/obj/usr/src/i386/sys -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- Several hours later (well it is a pentium 90) it ends with: cc -O -pipe -DLIBWRAP -DLOGIN_ACCESS -I/usr/src/secure/usr.sbin/sshd/../../.. /usr.bin/login -I/usr/obj/usr/src/i386/usr/include - o sshd sshd.o auth-rhosts.o auth-passwd.o auth-rsa.o auth-rh-rsa.o pty.o log-server.o login.o servconf.o serverloop.o login_access.o -L/usr/obj/usr/src/secure/usr.sbin/sshd/../../lib/libssh -lssh -lcrypt -lcrypto -lutil -lz -lwrap gzip -cn /usr/src/secure/usr.sbin/sshd/../../../crypto/openssh/sshd.8 > sshd.8.gz ===> etc ===> etc/sendmail rm -f freebsd.cf (cd /usr/src/etc/sendmail && m4 -D_CF_DIR_=/usr/src/etc/sendmail/../../contr ib/sendmail/cf/ /usr/src/etc/sendmail/../../contrib/sen dmail/cf/m4/cf.m4 freebsd.mc) > freebsd.cf chmod 444 freebsd.cf you have mail in /var/mail/root I then continue on with: # cd sbin/mknod # make install install -c -s -o root -g wheel -m 555 mknod /sbin install -c -o root -g wheel -m 444 mknod.8.gz /usr/share/man/man8 # cd /usr/src/usr.bin/genassym # make depend all install install -c -s -o root -g wheel -m 555 genassym /usr/bin install -c -o root -g wheel -m 444 genassym.8.gz /usr/share/man/man8 # cd ../../usr.sbin/config # make depend all install install -c -s -o root -g wheel -m 555 config /usr/sbin install -c -o root -g wheel -m 444 config.8.gz /usr/share/man/man8 # cd ../../sys/i386/conf # config GENERIC /usr/libexec/ld-elf.so.1: Shared object "libc.so.4" not found Ah ha, the famous "libc.so.4" not found error, quick check the archives and find I need to set LD_LIBRARY_PATH to point to /usr/obj/usr/src/lib/libc I do this and start from that point in the instructions: # cd /usr/src/sys/i386/conf # config GENERIC Don't forget to do a ``make depend'' Kernel build directory is ../../compile/GENERIC # cd ../../compile/GENERIC # make depend && make cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer- arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf ../../i386/i386/genassym.c genassym genassym.o >assym.s rm -f param.c And a couple of hours later: sh ../../conf/newvers.sh GENERIC cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer- arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf vers.c linking kernel text data bss dec hex filename 2174751 142284 123136 2440171 253beb kernel At this point I feel really brave and: # make install chflags noschg /kernel mv /kernel /kernel.old install -c -m 555 -o root -g wheel -fschg kernel /kernel Having commited to this point I then: # cp /usr/src/etc/MAKEDEV . # ./MAKEDEV all Although this may have been not needed, since I'm using da devices, not wd. I then shutdown now to single user mode, cd to /usr/src and do ``make -DNOINFO installworld''. This starts and continues to /bin/test where it fails due to a kernel failure. When I try to reboot the system, with the RELENG_4 kernel I get: / not unmounted cleanly, run fsck and reboot. I go into single user mode and run fsck ; fsck -p ; fsck /dev/da0s1a and a few sync's thrown in just for good luck, but still the same error. When I try to reboot with kernel.old (3.4-STABLE), it fails. Other than reinstalling the 3.4-RELEASE binaries, and thoughts on how to set / to showin it was unmounted cleanly?? thanks for any advice or thoughts, Jim Ballantine To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 7:51:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from europe.std.com (europe.std.com [199.172.62.20]) by hub.freebsd.org (Postfix) with ESMTP id D788737C1D4 for ; Wed, 22 Mar 2000 07:51:17 -0800 (PST) (envelope-from kwc@world.std.com) Received: from world.std.com (root@world-f.std.com [199.172.62.5]) by europe.std.com (8.9.3/8.9.3) with ESMTP id KAA16846 for ; Wed, 22 Mar 2000 10:51:12 -0500 (EST) Received: (from kwc@localhost) by world.std.com (8.9.3/8.9.3) id KAA05168; Wed, 22 Mar 2000 10:48:20 -0500 (EST) Date: Wed, 22 Mar 2000 10:48:20 -0500 (EST) From: Kenneth W Cochran Message-Id: <200003221548.KAA05168@world.std.com> To: freebsd-stable@freebsd.org Subject: Linux ext2 fs support changes in -stable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi... I "track" -stable (RELENG_3) roughly weekly. I have ext2 filesystem support in my kernel config. Somewhat all-of-a-sudden, I am unable to r/w mount a Linux ext2 filesystem on the same hdd with my BSD. I get in my syslog (& on console): /kernel: WARNING: R/W mount of dev 0xe040a denied due to unsupported optional features This is when I try "mount_ext2fs /dev/da1s...". I can mount things there readonly just fine. What are "unsupported optional features?" Read/write mounting of filesystems on /dev/da1 used to work, but it has been a few weeks (a month?) since I've tried it. I *can* r/w mount ext2 filesystems on my "other" hdd (/dev/da0s3 & /dev/da0s4). I do remember seeing some deltas in my cvsup logs that applied to ext2 fs support... What happened? What's going on here? Naturally, faq & doc pointers quite welcome. :) -kc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 8:10:29 2000 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 C95C437C13D for ; Wed, 22 Mar 2000 08:10:22 -0800 (PST) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id LAA20341 for stable@freebsd.org; Wed, 22 Mar 2000 11:10:21 -0500 (EST) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200003221610.LAA20341@blackhelicopters.org> Subject: dot-0 releases To: stable@freebsd.org Date: Wed, 22 Mar 2000 11:10:21 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As someone who's survived the 2.1->2.2 upgrade, the 2.2->3.0 upgrade, and now the 3.x->4.0 upgrade, I've seen the same discussions every time. People say, "The upgrade path is too hard." People say, "x.0 is safe to use." "No, it's not." "Yes, it is." People say, "The naming scheme is confusing. How about ..." Go search in the -stable archives. I bet the keyword "upgrade" will turn up some of old niggling. These horses were beaten to death when 2.2.0 came out, were propped up mummified when 3.0 came out, and are now skeletons wired together right next to Mr. Tyrranosaurus and Mrs. Diplodocus. One of the things I enjoy about the FreeBSD community is that we are, traditionally, all professionals. Many Linux folks started out doing Linux for fun, whereas the people here are using FreeBSD for honest-to-god work in real-world environments. Originally, to get a job where you had to be a FreeBSD admin, you had to be a UNIX admin. The clue quotient was much higher. (Then there were people like me. But I digress.) If you're an experienced sysadmin, upgrading from source is no big deal. If you're less experienced, then it is a big deal. The documentation can't tell anyone if they personally should upgrade from source. I've been upgrading from source since 97, and only been running FreeBSD since 95. And I have a degree in English, having failed my first term computer class. (There are those who might claim a senior thesis on _Gravity's_Rainbow_ make one eminently qualified to be a UNIX sysadmin. But again, I digress.) While NT might have convinced many people that they can be system administrators without knowing a damn thing about how computers work, the FreeBSD community has always assumed that you know what you're doing. The documentation is written to that audience, and is only now shifting to include less experienced users. I don't think even Nik would claim it's perfect. docs@freebsd.org would welcome patches, I'm sure. And perhaps 5.0 will be a "God help you if you run this release." (I don't think so, with the improvements in quality control for 4.x, but who can say now?) As far as 4.0 goes: I'm usually the paranoid one. My preferred method of determining when to upgrade is when my old version of FreeBSD is about to lose all support. I still have 2.2-stable boxes out there, because they work. So, I've installed 4.0 on two brand-new production machines. Whoa. Much improved all around... I break out my script kiddie tools and slam them, and they just won't die. Suck 80 meg/second between them, via NFS & Diablo... the rest of the office Ethernet dies, the other users show up to damage my head/neck integrity, but FreeBSD keep going. Maybe I'll go buy that switch for a test network now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 8:11:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ns.binep.ac.ru (ns.binep.ac.ru [193.233.37.5]) by hub.freebsd.org (Postfix) with ESMTP id 1081337C1D5 for ; Wed, 22 Mar 2000 08:11:07 -0800 (PST) (envelope-from goshik@binep.ac.ru) Received: from serv2.binep.ac.ru (serv2 [193.233.44.77]) by ns.binep.ac.ru (8.9.3/8.9.3) with SMTP id TAA99633; Wed, 22 Mar 2000 19:19:01 +0300 (MSK) (envelope-from goshik@binep.ac.ru) Reply-To: "Igor B. Bykhalo" From: "Igor B. Bykhalo" To: "Matthew N. Dodd" Cc: Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... Date: Wed, 22 Mar 2000 19:01:54 +0300 Message-ID: <01bf9417$f1b51b80$0000e9c1@serv2.binep.ac.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.0913.2206 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0913.2200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Original Message----- From: Matthew N. Dodd [...snip...] > >Yep. Its likely some of the 'legacy' (non-newbus) drivers stomp on the >card. You should -always- disable devices that you don't have in your >system. > >> (Strangely enough, the ep driver doesn't appear anywhere in the kernel >> config screen.) > >Correct. The 'ep' driver in 4.0/current doesn't have any need for the >user to specify settings. The kernel config screen is really for devices >that are so broken that we can't 'ask' them what their configuration is or >otherwise discover it unassisted. [...snip...] So is it recommended to put ISA cards into PnP mode? I'm asking because I have a couple of boxes with two and three 3C509B cards in them. In this case, 1) how should look the corresponding line in kernel config? Just device ep0 ? 2) how I bind IP addresses to desired cards? And one more question: 3c5x9cfg.exe utility in the config section has "Optimisation"(?) entry, where you can select "server", "client", etc. What is recommended? Or just don't bother? TIA, Igor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 8:14:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lunatic.oneinsane.net (lunatic.oneinsane.net [207.113.133.231]) by hub.freebsd.org (Postfix) with ESMTP id D6B4437C13D for ; Wed, 22 Mar 2000 08:14:29 -0800 (PST) (envelope-from insane@lunatic.oneinsane.net) Received: by lunatic.oneinsane.net (Postfix, from userid 1000) id C3BB1180; Wed, 22 Mar 2000 08:14:25 -0800 (PST) Date: Wed, 22 Mar 2000 08:14:25 -0800 From: Ron 'The InSaNe One' Rosson To: freebsd-stable@freebsd.org Subject: Processed Orders?? Message-ID: <20000322081425.A50173@lunatic.oneinsane.net> Reply-To: Ron Rosson Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD lunatic.oneinsane.net 3.4-STABLE X-Moon: The Moon is Waning Gibbous (94% of Full) X-Opinion: What you read here is my IMHO X-Disclaimer: I am a firm believer in RTFM X-WWW: http://www.oneinsane.net X-PGP-KEY: http://www.oneinsane.net/~insane/insane2-pgp5i.txt X-Uptime: 8:12AM up 6 days, 22:13, 2 users, load averages: 0.08, 0.02, 0.01 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If we have recieved confirmations on our orders for 4.0 what is going to happen. Looks like the post from the last 48 hours spurred alot of requests for 4.0 that where unexpected. (according to emails in this list). Just curious on the outcome that has yet to be posted ;-) TIA -- ------------------------------------------------------------------- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was /dev/null and *void() ------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 8:20:19 2000 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 776B637C1E7 for ; Wed, 22 Mar 2000 08:20:14 -0800 (PST) (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 IAA19514; Wed, 22 Mar 2000 08:19:08 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda19511; Wed Mar 22 08:18:53 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id IAA03516; Wed, 22 Mar 2000 08:18:53 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdkO3510; Wed Mar 22 08:18:51 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id IAA00950; Wed, 22 Mar 2000 08:18:50 -0800 (PST) Message-Id: <200003221618.IAA00950@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdCQz945; Wed Mar 22 08:18:33 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: Richard Wackerbarth Cc: thomas.uhrfelt@plymovent.se, freebsd-stable@FreeBSD.ORG Subject: Re: Get used to it. In-reply-to: Your message of "Wed, 22 Mar 2000 07:23:25 CST." <00032208000803.01108@nomad.dataplex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 22 Mar 2000 08:18:33 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please read my comments on -chat. From an amateur psychologist's it might be some food for thought. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC In message <00032208000803.01108@nomad.dataplex.net>, Richard Wackerbarth write s: > On Wed, 22 Mar 2000, Thomas Uhrfelt wrote: > > And yes I know some > > answers in the past been more than a little unfriendly, but I don't blame > > them. I can take a GO RTFM answer > Yes, but that is only because you are knowledgable of the culture. > As computers have gotten bigger and faster, the OS has become much more > complicated. The learning curve is huge. Even after decades, I don't pretend > to > know how many parts of it work. I am quite happy to treat those parts as "bla > ck > boxes" unless I need to tweek them. > > > I feel like this: - if I want to use "their" software to run "my" system .. > > That's the fundamental problem -- an "us" and "them" attitude. > Until it becomes an "our" attitude, the schism will continue to limit the > "community". > > > I get better support from the FreeBSD community that I do from $10K > > support contracts. > > Yes, the real value is in the COMMUNITY. > > > I belive it has already broken out of the developers sandbox. And I don't > > think it's a wish from the current general FreeBSD population that we > > should attract more first-timers in masses. I could be wrong on this one I > > know .. but it's still my impression. > > We need to work toward developing a "knowledge ladder". By chopping off the > bottom rungs, you guarantee that, in the long run, the community will wither. > > When it finally comes down to the bottom line, a growing community with > "acceptable" technology will beat out the "elitist niche" even though they ha > ve > superior technology. > > > This is very true indeed, but I don't want those changes in the system .. I > > > want updates in the handbook and the FAQ. > Beef up the suspension on every vehicle rather than straightening and paving > the road :-) > > > I don't feel comfortable with a oneclick > > checkbox doing multiple operations. FreeBSD forces me to think each step > > though > "One click" solutions save a lot of time... > if, and it's a big IF, > 1) The developer of the button really designs it correctly > 2) There is an over-ride so that it is not the only option. > > > and this in the end will save me a lot of headaches. > Only if you are ever able to get started. > > > 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 Mar 22 8:38:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay.rtsnet.ru (bravo.rtsnet.ru [194.247.132.8]) by hub.freebsd.org (Postfix) with ESMTP id E0E7937C036 for ; Wed, 22 Mar 2000 08:38:11 -0800 (PST) (envelope-from igor@rtsnet.ru) Received: from shogun.rtsnet.ru (shogun.rtsnet.ru [172.16.4.32]) by relay.rtsnet.ru (Postfix) with ESMTP id 6E631198C17 for ; Wed, 22 Mar 2000 19:38:03 +0300 (MSK) Received: (from igor@localhost) by shogun.rtsnet.ru (8.9.3/8.9.3/Zynaps) id TAA03187; Wed, 22 Mar 2000 19:38:03 +0300 (MSK) Date: Wed, 22 Mar 2000 19:38:03 +0300 From: Igor Vinokurov To: freebsd-stable@freebsd.org Subject: new RELENG3 snapshots Message-ID: <20000322193803.A3142@shogun.rtsnet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i X-Zynaps-Sent: igor@rtsnet.ru Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Any plans to continue upload new snapshots of RELENG3 to ftp://releng3.freebsd.org/pub/FreeBSD/snapshots/i386/? Now 3.4-20000311-STABLE :( How about 3.4-20000322-STABLE? :) -- Igor Vinokurov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 8:40:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 8B40437BE0A for ; Wed, 22 Mar 2000 08:40:12 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id LAA58022; Wed, 22 Mar 2000 11:40:03 -0500 (EST) Date: Wed, 22 Mar 2000 11:40:03 -0500 (EST) From: "Matthew N. Dodd" To: "Igor B. Bykhalo" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... In-Reply-To: <01bf9417$f1b51b80$0000e9c1@serv2.binep.ac.ru> 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, 22 Mar 2000, Igor B. Bykhalo wrote: > So is it recommended to put ISA cards into PnP mode? I'm asking > because I have a couple of boxes with two and three 3C509B cards in > them. In this case, PnP mode seems to work just fine here. > 1) how should look the corresponding line in kernel config? > Just > > device ep0 Yes, or even device ep > 2) how I bind IP addresses to desired cards? I suspect that boards in PnP mode will be probed in order of their ethernet MAC address, which will probably correspond with their PnP serial number, which is likely used as part of the isolation protocol (which determines detection order.) > And one more question: 3c5x9cfg.exe utility in the config section has > "Optimisation"(?) entry, where you can select "server", "client", etc. > What is recommended? Or just don't bother? I suspect that those entries are there for use by the driver. Our driver doesn't make use of them so not bothering works just fine. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 8:54:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from student-mailhub.dcu.ie (ns.dcu.ie [136.206.1.3]) by hub.freebsd.org (Postfix) with ESMTP id 4DA9737C2A3 for ; Wed, 22 Mar 2000 08:54:11 -0800 (PST) (envelope-from drjolt@redbrick.dcu.ie) Received: from enigma.redbrick.dcu.ie (postfix@enigma.redbrick.dcu.ie [136.206.15.5]) by student-mailhub.dcu.ie (8.9.3/8.9.3/893-FD) with ESMTP id QAA21145 for ; Wed, 22 Mar 2000 16:54:09 GMT Received: by enigma.redbrick.dcu.ie (Postfix, from userid 2034) id 19C4C7CC8; Wed, 22 Mar 2000 16:52:24 +0000 (GMT) Date: Wed, 22 Mar 2000 16:52:24 +0000 From: David Murphy To: stable@FreeBSD.ORG Subject: Re: dot-0 releases Message-ID: <20000322165223.K48595@enigma.redbrick.dcu.ie> References: <200003221610.LAA20341@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003221610.LAA20341@blackhelicopters.org>; from mwlucas@blackhelicopters.org on Wed, Mar 22, 2000 at 11:10:21AM -0500 X-no-archive: yes Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting <200003221610.LAA20341@blackhelicopters.org> by Michael Lucas : > If you're an experienced sysadmin, upgrading from source is no big > deal. If you're less experienced, then it is a big deal. The > documentation can't tell anyone if they personally should upgrade > from source. If you are an experienced FreeBSD sysadmin, then upgrading from source is no big deal. The assumption that people are either experienced FreeBSD admins, or they are completely clueless about unix, while apparently widely made by experienced FreeBSD admins, is *not* valid. The documentation should, of course, aim to teach everyone, but I suggest an intermediate target to aim for: teaching the experienced, skilful systems administrator unfamiliar with FreeBSD about FreeBSD's particular quirks. It would also greatly help if the people who write the manuals [Handbook, Release Notes and Release Announcements] and the people who make pronouncements on mailing lists such as these synced up a little. What I mean is, the clueful sysadmin new to FreeBSD will RTFM. They will then proceed based on that info. Example: If TFM only talks about upgrading from source, the clueful sysadmin will believe that upgrading from source is the way to upgrade. [NB, the handbook only talks about upgrading from source]. The clueful sysadmin should not then be told that upgrading from source is the not recommended for those who are not experienced FreeBSD sysadmins. Please decide on a recommendation, and put it in TFM (handbook). Please announce this on -stable, so people on stable can at least say if they're quoting "official policy" or their own personal policy. Example: If TFM designates something as a .0 release, the clueful sysadmin will treat it as such. [NB, the release notes and release annoucement designate 4.0-RELEASE, as opposed to 4.0-RC]. The clueful sysadmin should not then be told that .0 is still a release candidate. Please decide on a designation, and put it in TFM (release notes and release announcement). Please announce this on -stable, so people on stable can at least say if they're quoting "official policy" or their own personal policy. Please stop flaming people to a crisp for being able to RTFM, but not being able to Read Your F'ing Minds. -- When asked if it is true that he uses his wheelchair as a weapon he will reply: "That's a malicious rumour. I'll run over anyone who repeats it." Stephen Hawking - [http://www.smh.com.au/news/0001/07/features/features1.html] David Murphy - For PGP public key, send mail with Subject: send-pgp-key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 9: 1:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 79A8537B895; Wed, 22 Mar 2000 09:01:46 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id JAA41344; Wed, 22 Mar 2000 09:01:46 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 22 Mar 2000 09:01:46 -0800 (PST) From: Kris Kennaway To: David Murphy Cc: stable@FreeBSD.ORG Subject: How to actually make a difference (Re: dot-0 releases) In-Reply-To: <20000322165223.K48595@enigma.redbrick.dcu.ie> 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, 22 Mar 2000, David Murphy wrote: > The documentation should, of course, aim to teach everyone, but I > suggest an intermediate target to aim for: teaching the experienced, > skilful systems administrator unfamiliar with FreeBSD about FreeBSD's > particular quirks. > > It would also greatly help if the people who write the manuals > [Handbook, Release Notes and Release Announcements] and the people who > make pronouncements on mailing lists such as these synced up a little. With all the wastage of words on this topic, you (and others) could have written the simple patches to the documentation which clarify the "upgrading from source" issues and any others you may have. The doc committers don't have some god-given mandate on system documentation, you know. The first draft might not be acceptable to everyone, but it would be a start, and it would be a hell of a lot more constructive than just saying "something should be done to improve the documentation, by god". If you don't understand SGML, write in plain text and someone will be happy to mark it up for you once it's written. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 9:20:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from student-mailhub.dcu.ie (ns.dcu.ie [136.206.1.3]) by hub.freebsd.org (Postfix) with ESMTP id BD6E237C047 for ; Wed, 22 Mar 2000 09:20:07 -0800 (PST) (envelope-from drjolt@redbrick.dcu.ie) Received: from enigma.redbrick.dcu.ie (postfix@enigma.redbrick.dcu.ie [136.206.15.5]) by student-mailhub.dcu.ie (8.9.3/8.9.3/893-FD) with ESMTP id RAA22046 for ; Wed, 22 Mar 2000 17:19:57 GMT Received: by enigma.redbrick.dcu.ie (Postfix, from userid 2034) id DA6E27C98; Wed, 22 Mar 2000 17:19:57 +0000 (GMT) Date: Wed, 22 Mar 2000 17:19:57 +0000 From: David Murphy To: stable@FreeBSD.org Subject: Re: How to actually make a difference (Re: dot-0 releases) Message-ID: <20000322171957.L48595@enigma.redbrick.dcu.ie> References: <20000322165223.K48595@enigma.redbrick.dcu.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@FreeBSD.org on Wed, Mar 22, 2000 at 09:01:46AM -0800 X-no-archive: yes Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting by Kris Kennaway : > On Wed, 22 Mar 2000, David Murphy wrote: > With all the wastage of words on this topic, you (and others) could > have written the simple patches to the documentation which clarify > the "upgrading from source" issues and any others you may have. The > doc committers don't have some god-given mandate on system > documentation, you know. Yes, at this point, we have certainly spent more time discussing than it would have taken to just fix the manual, *however*... > The first draft might not be acceptable to everyone, but it would be > a start, and it would be a hell of a lot more constructive than just > saying "something should be done to improve the documentation, by > god". ...it would be a damn sight more constructive to say "What you've done isn't what we recommend you do. Unfortunately, the documentation does not yet reflect our current recommendations. If you write up your experiences, we'll incorporate them into the documentation" instead of saying "Fool! Don't you know the way we do things here?". Basically, if people considered what was and was not currently in the handbook before flaming, you wouldn't have people complaining that they were flamend because the manual's not up to date. -- When asked if it is true that he uses his wheelchair as a weapon he will reply: "That's a malicious rumour. I'll run over anyone who repeats it." Stephen Hawking - [http://www.smh.com.au/news/0001/07/features/features1.html] David Murphy - For PGP public key, send mail with Subject: send-pgp-key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 9:36: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from phb.avic.dk (phb.avic.dk [194.234.178.52]) by hub.freebsd.org (Postfix) with ESMTP id BE8C637C1C5 for ; Wed, 22 Mar 2000 09:35:59 -0800 (PST) (envelope-from jens@fallesen.dk) Received: from fallesen.dk (41.ppp1-13.worldonline.dk [212.54.71.169]) by phb.avic.dk (8.9.3/8.9.3/PHB/11[AntiSpam]) with ESMTP id SAA28207 for ; Wed, 22 Mar 2000 18:35:48 +0100 (CET) Message-ID: <38D90474.83554A30@fallesen.dk> Date: Wed, 22 Mar 2000 18:35:48 +0100 From: Jens Fallesen Organization: AVIC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: da, en MIME-Version: 1.0 To: stable@freebsd.org Subject: HP CD-R problems in 4.0-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 there, In my PC I have the following configuration: 1st IDE, 1st drive: Hard disk (ad0) 1st IDE, 2nd drive: ZIP drive (afd0) 2nd IDE, 1st drive: DVD-ROM (acd0) 2nd IDE, 2nd drive: CD-RW (acd1) This worked fine with 3.4-STABLE but after an otherwise succesful upgrade to 4.0-STABLE (last cvsup was Tuesday at approximately 1700 UTC) I have been unable to use my CD-RW drive. When I look into /var/log/messages I get this: Mar 22 18:19:44 dilbert /kernel: ad0: 12893MB [26197/16/63] at ata0-master using UDMA33 Mar 22 18:19:44 dilbert /kernel: afd0: 96MB [96/64/32] at ata0-slave using PIO3 Mar 22 18:19:44 dilbert /kernel: acd0: DVD-ROM at ata1-master using PIO4 Mar 22 18:19:44 dilbert /kernel: acd1: CD-RW at ata1-slave using PIO3 Mar 22 18:19:44 dilbert /kernel: Mounting root from ufs:/dev/ad0s2a (The same info is in dmesg.) The drive is there, so is the device (made several times using ./MAKEDEV acd1). However, when I try to mount the drives: dilbert:/home/jf# mount -t cd9660 /dev/acd0c /cdrom dilbert:/home/jf# mount -t cd9660 /dev/acd1c /hpcd cd9660: Device not configured dilbert:/home/jf# I have searched the mailing list, release notes, and everything else I could get hold of and I can't seem to find out what's happening. Am I overlooking some very important thing here or is there a (known) problem? -- Jens Fallesen O- Hedegaardsvej 41 st th, 2300 Copenhagen S, Denmark Phone: (+45) 32 86 18 99 * Fax: (+45) 32 86 17 99 CCIE #5470 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 10:23:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 2F50937BB43 for ; Wed, 22 Mar 2000 10:23:36 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA22101; Wed, 22 Mar 2000 10:23:31 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Thomas David Rivers Cc: witr@rwwa.com, stable@FreeBSD.ORG, witr@pobox.rwwa.com Subject: Re: V4.0 and Walnut Creek Subscriptions... In-reply-to: Your message of "Wed, 22 Mar 2000 08:01:27 EST." <200003221301.IAA22823@lakes.dignus.com> Date: Wed, 22 Mar 2000 10:23:31 -0800 Message-ID: <22098.953749411@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No, you won't get two copies. > > > > > Hold the presses. I'm talking with Walnut Creek CDROM right now about > > just sending 4.0 to the subscribers after all. You're about the > > 2000th person to ask me. :) > > > > - Jordan > > > > Uh... wait... > > Yesterday (Tuesday), following the previous instructions, I sent Walnut > Creek an order form; and they said they'll be happy to charge my credit card , > and my order was processed, etc... > > Will I now get *two* copies of 4.0? > > I think we're now "mid-stream" and changing horses isn't best done here... > > - Dave Rivers - > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 10:26:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id EE04B37B807 for ; Wed, 22 Mar 2000 10:26:28 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id TAA30625 for stable@freebsd.org; Wed, 22 Mar 2000 19:26:27 +0100 (CET) (envelope-from asmodai) Date: Wed, 22 Mar 2000 19:26:27 +0100 From: Jeroen Ruigrok van der Werven To: stable@freebsd.org Subject: PATCH! groff breaking world in 3-STABLE PATCH! Message-ID: <20000322192627.A30592@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="XsQoSWH+UP9D9v3l" X-Mailer: Mutt 1.0.1i Organisation: bART Internet Services B.V. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Hi guys, please try this patch as it solves the problems encountered with groff wrt the safer macro in 3-STABLE. With thanks to Bruce D. Evans for his help. Please report successes and failures back to me... -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl Earth to earth, ashes to ashes, dust to dust... --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="Makefile.inc1.patch" --- src/Makefile.inc1.orig Wed Mar 22 15:01:10 2000 +++ src/Makefile.inc1 Wed Mar 22 15:11:00 2000 @@ -183,6 +183,8 @@ COMPILER_ENV= BISON_SIMPLE=${TOOLROOT}/usr/share/misc/bison.simple \ COMPILER_PATH=${TOOLROOT}/usr/libexec:${TOOLROOT}/usr/bin \ GCC_EXEC_PREFIX=${WORLDTMP}${SHLIBDIR}:${WORLDTMP}/usr/lib/ \ + GROFF_FONT_PATH=${WORLDTMP}/usr/share/groff_font \ + GROFF_TMAC_PATH=${WORLDTMP}/usr/share/tmac \ LD_LIBRARY_PATH=${TOOLROOT}${SHLIBDIR} \ LIBRARY_PATH=${WORLDTMP}${SHLIBDIR}:${WORLDTMP}/usr/lib --XsQoSWH+UP9D9v3l-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 10:46:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 31B9037C355 for ; Wed, 22 Mar 2000 10:46:22 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id KAA09742; Wed, 22 Mar 2000 10:46:14 -0800 (PST) Date: Wed, 22 Mar 2000 10:46:14 -0800 From: Brooks Davis To: Vivek Khera Cc: stable@FreeBSD.ORG Subject: Re: "dangerously dedicated" Message-ID: <20000322104614.A22584@orion.ac.hmc.edu> References: <38D50DBC.88FA8E4D@glue.umd.edu> <38D3AB72.366D851D@glue.umd.edu> <200003152159.OAA89926@harmony.village.org> <38D03E64.3D17FC34@glue.umd.edu> <200003190433.VAA04863@harmony.village.org> <200003212255.PAA26291@harmony.village.org> <14552.57732.739752.665443@onceler.kcilink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <14552.57732.739752.665443@onceler.kcilink.com>; from khera@kciLink.com on Wed, Mar 22, 2000 at 10:06:44AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 22, 2000 at 10:06:44AM -0500, Vivek Khera wrote: > >>>>> "WL" == Warner Losh writes: > > WL> In message <4.3.2.20000321160347.00ad9b20@207.227.119.2> "Jeffrey J. Mountin" writes: > > WL> : Are you saying that da0a is (almost) functionally equivalent to > WL> da0s3a if : slice 3 is the first FBSD slice. Thought they were > WL> for "dangerously : dedicated" partitions. > > WL> No. That's not correct. While they are used in dangerously (and > WL> stupidly) dedicated mode, they can be used at any time. I still have > WL> some mount points on my -current machine that refer to sd1c because > WL> I've been too lazy to update them. > > Why is using /dev/da0a stupid? FreeBSD is the only system I've > encountered that totally locks up (during a 3.3-RELEASE install from > CD) when there is no fdisk disk label. Is that why it is stupid? > > BSD/OS and Linux (RedHat 6.1) both deal with the lack of an fdisk disk > label just fine, and BSD/OS doesn't even require one, letting you use > the direct unix partitioning scheme. I much prefer it that way as it > just makes sense on a dedicated box, which is what all of mine are. It generally works just fine. I even have one machine configured that way. IIRC, the problem is that some over helpful BIOS implementations have decided that they should only try to boot disks which don't have an MSDOS partition table on them. This has nothing to do with FreeBSD and everything to do with the morons who write BIOSes for WinBlows. It doesn't hurt anything to slap an MSDOS partion onto the disk so you might as well do it. Call it insurance. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 11:14:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 859FF37C1E9 for ; Wed, 22 Mar 2000 11:14:47 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id TAA49591; Wed, 22 Mar 2000 19:13:24 GMT (envelope-from nik) Date: Wed, 22 Mar 2000 19:13:24 +0000 From: Nik Clayton To: Michael Lucas Cc: stable@freebsd.org Subject: Re: dot-0 releases Message-ID: <20000322191324.A49128@catkin.nothing-going-on.org> References: <200003221610.LAA20341@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <200003221610.LAA20341@blackhelicopters.org>; from Michael Lucas on Wed, Mar 22, 2000 at 11:10:21AM -0500 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 22, 2000 at 11:10:21AM -0500, Michael Lucas wrote: > The documentation is written to that audience, and is only now > shifting to include less experienced users. I don't think even Nik > would claim it's perfect. docs@freebsd.org would welcome patches, I'm > sure. Absolutely. We can only document what we can test. I had an abortive -stable to -current experience a week ago, which is why the section in the Handbook hasn't been updated -- I've used a binary upgrade to go from 3.x to 4.0. If you've had it work successfully, submit doc patches. People will thank you. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 11:32:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id E9B5937C209 for ; Wed, 22 Mar 2000 11:32:03 -0800 (PST) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn27.imasy.or.jp [202.227.24.219]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id EAA03407; Thu, 23 Mar 2000 04:31:58 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <200003221931.EAA03407@tasogare.imasy.or.jp> To: winter@jurai.net Cc: iwasaki@jp.FreeBSD.org, freebsd-stable@FreeBSD.ORG Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... In-Reply-To: Your message of "Wed, 22 Mar 2000 04:15:42 -0500 (EST)" References: X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 23 Mar 2000 04:31:57 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 417 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > > Grrr, It's too difficult because I can't do anything after the messsage > > even etner DDB or pause screen and back scrolling... > > Use the serial console. Sorry, I don't have null-modem cable or 3c5x9cfg.exe or DOS here, but I did some hacks. By follwing patch made referring to 3-STABLE code, system was passed ep probe/attach routine with correct mac address and stopped /etc/rc.network in userland now. BTW, I found very strange thing, my system stopped at epstop() in ep_attach()... Index: if_ep.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ep/if_ep.c,v retrieving revision 1.99 diff -u -r1.99 if_ep.c --- if_ep.c 2000/03/13 11:59:21 1.99 +++ if_ep.c 2000/03/22 18:44:55 @@ -270,7 +270,9 @@ sc->gone = 0; +#if 0 ep_get_macaddr(sc, (u_char *)&sc->arpcom.ac_enaddr); +#endif /* * Setup the station address @@ -278,6 +280,9 @@ p = (u_short *)&sc->arpcom.ac_enaddr; GO_WINDOW(2); for (i = 0; i < 3; i++) { +#if 1 + p[i] = htons(sc->epb.eth_addr[i]); +#endif outw(BASE + EP_W2_ADDR_0 + (i * 2), ntohs(p[i])); } @@ -331,8 +336,9 @@ EP_FSET(sc, F_RX_FIRST); sc->top = sc->mcur = 0; +#if 0 epstop(sc); - +#endif return 0; } Index: if_ep_isa.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ep/if_ep_isa.c,v retrieving revision 1.8 diff -u -r1.8 if_ep_isa.c --- if_ep_isa.c 2000/01/23 08:46:21 1.8 +++ if_ep_isa.c 2000/03/22 18:45:22 @@ -145,6 +145,8 @@ return (NULL); } +u_short ep_isa_eth_addr[16][3]; /* irq, addr */ + static void ep_isa_identify (driver_t *driver, device_t parent) { @@ -158,6 +160,7 @@ u_int32_t ioport; u_int32_t isa_id; device_t child; + u_short eth_addr[3]; outb(ELINK_ID_PORT, 0); outb(ELINK_ID_PORT, 0); @@ -195,6 +198,10 @@ (void)get_eeprom_data(ELINK_ID_PORT, j); } + for (j = 0; j < 3; j++) { + eth_addr[j] = get_eeprom_data(ELINK_ID_PORT, j); + } + /* * Construct an 'isa_id' in 'EISA' * format. @@ -218,6 +225,10 @@ data = get_eeprom_data(ELINK_ID_PORT, EEPROM_RESOURCE_CFG); irq = (data >> 12); + for (j = 0; j < 3; j++) { + ep_isa_eth_addr[irq][j] = eth_addr[j]; + } + /* Retreive IOPORT */ data = get_eeprom_data(ELINK_ID_PORT, EEPROM_ADDR_CFG); #ifdef PC98 @@ -305,6 +316,7 @@ { struct ep_softc * sc = device_get_softc(dev); int error = 0; + int irq, i; if ((error = ep_alloc(dev))) { device_printf(dev, "ep_alloc() failed! (%d)\n", error); @@ -315,6 +327,11 @@ GO_WINDOW(0); SET_IRQ(BASE, rman_get_start(sc->irq)); + + irq = bus_get_resource_start(dev, SYS_RES_IRQ, 0); + for (i= 0; i < 3; i++) { + sc->epb.eth_addr[i] = ep_isa_eth_addr[irq][i]; + } if ((error = ep_attach(sc))) { device_printf(dev, "ep_attach() failed! (%d)\n", error); Index: if_epvar.h =================================================================== RCS file: /home/ncvs/src/sys/dev/ep/if_epvar.h,v retrieving revision 1.4 diff -u -r1.4 if_epvar.h --- if_epvar.h 2000/01/15 05:21:43 1.4 +++ if_epvar.h 2000/03/22 18:09:32 @@ -27,6 +27,7 @@ int cmd_off; /* command offset (bit shift) */ int mii_trans; /* activate MII transiever */ u_short res_cfg; /* resource configuration */ + u_short eth_addr[3]; /* Ethernet address */ }; /* Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #14: Thu Mar 23 03:45:36 JST 2000 root@celeron:/usr/src/sys/compile/CELERON Calibrating clock(s) ... TSC clock: 367492994 Hz, i8254 clock: 1193158 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium II/Pentium II Xeon/Celeron (367.50-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x660 Stepping = 0 Features=0x183f9ff real memory = 134205440 (131060K bytes) Physical memory chunk(s): 0x00001000 - 0x0009ffff, 651264 bytes (159 pages) 0x0039b000 - 0x07ff2fff, 130383872 bytes (31832 pages) avail memory = 126472192 (123508K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f9ce0 bios32: Entry = 0xf0520 (c00f0520) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x720 pnpbios: Found PnP BIOS data at 0xc00fd120 pnpbios: Entry = f0000:d150 Rev = 1.0 pnpbios: OEM ID cd041 Other BIOS signatures found: ACPI: 000f7f40 VESA: information block 56 45 53 41 02 01 8a 4e 00 c0 00 00 00 00 ad 4e 00 c0 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 23 mode(s) found VESA: v1.2, 4096k memory, flags:0x0, mode table:0xc00c4ead (c0004ead) VESA: S3 Incorporated. Vision968 Pentium Pro MTRR support enabled md0: Malloc disk Creating DISK md0 Math emulator present pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) pcib0: on motherboard found-> vendor=0x8086, dev=0x7190, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base e4000000, size 26, enabled found-> vendor=0x8086, dev=0x7191, revid=0x03 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 0000d800, size 4, enabled found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=12 map[20]: type 1, range 32, base 0000d400, size 5, enabled found-> vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[90]: type 1, range 32, base 0000e800, size 4, enabled found-> vendor=0x5333, dev=0x88f0, revid=0x00 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=255 map[10]: type 1, range 32, base e0000000, size 25, enabled pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xd800 ata0: mask=03 status0=50 status1=50 ata0: mask=03 status0=50 status1=50 ata0: devices = 0x3 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xd808 ata1: mask=03 status0=50 status1=50 ata1: mask=03 status0=00 status1=00 ata1: devices = 0x4 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xd400-0xd41f irq 12 at device 4.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 0xe800-0xe80f at device 4.3 on pci0 pci0: (vendor=0x5333, dev=0x88f0) at 12.0 pnpbios: 14 devices, largest 114 bytes PNP0401: adding dma mask 0x8 PNP0401: adding irq mask 0x80 PNP0401: adding io range 0x378-0x37f, size=0x8, align=0 PNP0401: adding io range 0x778-0x77f, size=0x8, align=0 PNP0401: start dependant pnpbios: handle 1 device ID PNP0401 (0104d041) PNP0501: adding irq mask 0x10 PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0 PNP0501: start dependant pnpbios: handle 2 device ID PNP0501 (0105d041) PNP0501: adding irq mask 00x8 PNP0501: adding io range 0x2f8-0x2ff, size=0x8, align=0 PNP0501: start dependant pnpbios: handle 3 device ID PNP0501 (0105d041) PNP0700: adding irq mask 0x40 PNP0700: adding dma mask 0x4 PNP0700: adding io range 0x3f2-0x3f5, size=0x4, align=0 PNP0700: start dependant pnpbios: handle 4 device ID PNP0700 (0007d041) PNP0c01: adding memory range 0-0x9ffff, size=0xa0000 PNP0c01: adding memory range 0x100000-0x7ffffff, size=0x7f00000 PNP0c01: adding memory range 0xe8000-0xeffff, size=0x8000 PNP0c01: adding memory range 0xf0000-0xf3fff, size=0x4000 PNP0c01: adding memory range 0xf4000-0xf7fff, size=0x4000 PNP0c01: adding memory range 0xf8000-0xfbfff, size=0x4000 PNP0c01: adding memory range 0xfc000-0xfffff, size=0x4000 PNP0c01: adding memory range 0xfffe0000-0xffffffff, size=0x20000 PNP0c01: start dependant pnpbios: handle 6 device ID PNP0c01 (010cd041) PNP0000: adding irq mask 00x4 PNP0000: adding io range 0x20-0x21, size=0x2, align=0 PNP0000: adding io range 0xa0-0xa1, size=0x2, align=0 PNP0000: adding io range 0x4d0-0x4d1, size=0x2, align=0 PNP0000: start dependant pnpbios: handle 7 device ID PNP0000 (0000d041) PNP0100: adding irq mask 00x1 PNP0100: adding io range 0x40-0x43, size=0x4, align=0 PNP0100: start dependant pnpbios: handle 8 device ID PNP0100 (0001d041) PNP0b00: adding irq mask 0x100 PNP0b00: adding io range 0x70-0x71, size=0x2, align=0 PNP0b00: start dependant pnpbios: handle 9 device ID PNP0b00 (000bd041) PNP0303: adding irq mask 00x2 PNP0303: adding io range 0x60-0x60, size=0x1, align=0 PNP0303: adding io range 0x64-0x64, size=0x1, align=0 PNP0303: start dependant pnpbios: handle 10 device ID PNP0303 (0303d041) PNP0c04: adding irq mask 0x2000 PNP0c04: adding io range 0xf0-0xf0, size=0x1, align=0 PNP0c04: start dependant pnpbios: handle 11 device ID PNP0c04 (040cd041) PNP0200: adding dma mask 0x10 PNP0200: adding io range 0-0xf, size=0x10, align=0 PNP0200: adding io range 0x80-0x90, size=0x11, align=0 PNP0200: adding io range 0x94-0x9f, size=0xc, align=0 PNP0200: adding io range 0xc0-0xde, size=0x1f, align=0 PNP0200: start dependant pnpbios: handle 12 device ID PNP0200 (0002d041) PNP0800: adding io range 0x61-0x61, size=0x1, align=0x1 PNP0800: start dependant pnpbios: handle 13 device ID PNP0800 (0008d041) PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0 PNP0a03: start dependant pnpbios: handle 14 device ID PNP0a03 (030ad041) PNP0c02: adding io range 0x290-0x297, size=0x8, align=0 PNP0c02: adding io range 0xe400-0xe43f, size=0x40, align=0 PNP0c02: adding io range 0xe800-0xe83f, size=0x40, align=0 PNP0c02: start dependant pnpbios: handle 15 device ID PNP0c02 (020cd041) Trying Read_Port at 203 Trying Read_Port at 243 TCM5090: adding irq mask 0x9ea8 TCM5090: adding io range 0x210-0x3ef, size=0x10, align=0x10 ata-: ata0 exists, using next available unit number ata-: ata1 exists, using next available unit number isa0: if_ep: <3Com 3C509-TP EtherLink III> at port 0x300-0x310 irq 10 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0067 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x700ff fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A mss_detect, busy still set (0xff) pca0 at port 0x40 on isa0 ep0: <3Com 3C509-TP EtherLink III> at port 0x300-0x30f irq 10 on isa0 ep0: eeprom failed to come ready. ep0: eeprom failed to come ready. ep0: Ethernet address 00:60:97:6a:9a:8c ep0: supplying EUI64: 00:60:97:ff:fe:6a:9a:8c bpf: ep0 attached isa_probe_children: probing PnP devices unknown0: at port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on isa0 unknown: can't assign resources unknown: can't assign resources unknown1: at port 0x3f2-0x3f5 irq 6 drq 2 on isa0 unknown2: at iomem 0-0x9ffff,0x100000-0x7ffffff,0xe8000-0xeffff,0xf0000-0xf3fff,0xf4000-0xf7fff,0xf8000-0xfbfff,0xfc000-0xfffff,0xfffe0000-0xffffffff on isa0 unknown: can't assign resources unknown3: at port 0x40-0x43 irq 0 on isa0 unknown4: at port 0x70-0x71 irq 8 on isa0 unknown: can't assign resources unknown5: at port 0xf0 irq 13 on isa0 unknown6: at port 0-0xf,0x80-0x90,0x94-0x9f,0xc0-0xde drq 4 on isa0 pca1: at port 0x61 on isa0 unknown7: at port 0xcf8-0xcff on isa0 unknown8: at port 0x290-0x297,0xe400-0xe43f,0xe800-0xe83f on isa0 ep1: <3Com 3C509B-TP EtherLink III (PnP)> at port 0x210-0x21f irq 5 on isa0 ep1: Ethernet address 00:00:00:00:00:00 bpf: ep1 attached BIOS Geometries: 0:03fffe3f 0..1023=1024 cylinders, 0..254=255 heads, 1..63=63 sectors 1:03ff0f3f 0..1023=1024 cylinders, 0..15=16 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: sl0 attached bpf: ppp0 attached new masks: bio 4008d000, tty 4003001a, net 4007043a bpf: lo0 attached bpf: gif0 attached bpf: gif1 attached bpf: gif2 attached bpf: gif3 attached bpf: stf0 attached bpf: faith0 attached ata0-master: success setting up UDMA2 mode on PIIX4 chip ad0: ATA-4 disk at ata0 as master ad0: 8693MB (17803440 sectors), 17662 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 32 depth queue, UDMA33 ad0: piomode=4 dmamode=2 udmamode=4 cblid=1 Creating DISK ad0 Creating DISK wd0 ata0-slave: success setting up UDMA2 mode on PIIX4 chip ad1: ATA-4 disk at ata0 as slave ad1: 17206MB (35239680 sectors), 34960 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 32 depth queue, UDMA33 ad1: piomode=4 dmamode=2 udmamode=4 cblid=1 Creating DISK ad1 Creating DISK wd1 ata1-master: piomode=0 dmamode=-1 udmamode=-1 dmaflag=0 ata1-master: success setting up PIO0 mode on generic chip acd0: CDROM drive at ata1 as master acd0: read 689KB/s (689KB/s), 256KB buffer, PIO0 acd0: Reads: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked Mounting root from ufs:wd1s2a wd1s1: type 0xa5, start 63, end = 524159, size 524097 : OK wd1s2: type 0xa5, start 524160, end = 1048319, size 524160 : OK wd1s3: type 0xa5, start 1048320, end = 35239679, size 34191360 : OK start_init: trying /sbin/init To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 11:59:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 0482137B795 for ; Wed, 22 Mar 2000 11:59:12 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id OAA60622; Wed, 22 Mar 2000 14:59:03 -0500 (EST) Date: Wed, 22 Mar 2000 14:59:03 -0500 (EST) From: "Matthew N. Dodd" To: Mitsuru IWASAKI Cc: freebsd-stable@FreeBSD.ORG Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... In-Reply-To: <200003221931.EAA03407@tasogare.imasy.or.jp> 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, 23 Mar 2000, Mitsuru IWASAKI wrote: > Sorry, I don't have null-modem cable or 3c5x9cfg.exe or DOS here, but > I did some hacks. By follwing patch made referring to 3-STABLE code, > system was passed ep probe/attach routine with correct mac address and > stopped /etc/rc.network in userland now. BTW, I found very strange > thing, my system stopped at epstop() in ep_attach()... You've totally not solved the problem. This is what is happening: - The PnP enumerator runs and identifies PnP devices. - The 3c509 board is found and a device is created. - ep_isa_identify() runs and finds -the same board- and pulls the last configured (with 3c5x9cfg.exe) settings from the EEPROM. The board is activated. - ep_isa_probe() runs against the device created by ep_isa_identify(). - The PnP system activates the 3c509 device that the enumerator found and assigns it resources. - ep_isa_probe() runs against the PnP device. - ep_isa_attach() runs against both devices, confusing them to no end. If you want a quick hack, comment out the IDENTIFY device method in if_ep_isa.c. The 3.4 driver doesn't do the right thing. Just hacking the driver so it prints out the right ethernet address isn't the goal. The goal is to figure out why we aren't able to detect that the 3c509 is in PnP mode in ep_isa_identify(). The documentation I have suggests that only the 3c509-B indicates PnP mode via the bits tested; this didn't concern me as the normal 3c509s don't have a PnP setting available in the 3c5x9cfg.exe util. If there is some other way of activing PnP (maybe the 'TEST' area of the board has a pencil mark in it?) then I need to figure out how to catch this condition. You need to get 3c5x9cfg.exe and run it. I have a feeling that your EEPROM may have some corruption or something. Also, pull your card and erase any markings in the test area of the card. ftp://ftp.3com.com/pub/nic/3c5x9/3c5x9x.exe is the 3c5x9 driver/util disk. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 12: 3:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from account.abs.net (account.abs.net [207.114.5.70]) by hub.freebsd.org (Postfix) with ESMTP id C00BD37BAAD; Wed, 22 Mar 2000 12:03:14 -0800 (PST) (envelope-from howardl@account.abs.net) Received: (from howardl@localhost) by account.abs.net (8.9.3/8.9.3+RBL+DUL+RSS+ORBS) id PAA51043; Wed, 22 Mar 2000 15:03:09 -0500 (EST) (envelope-from howardl) From: Howard Leadmon Message-Id: <200003222003.PAA51043@account.abs.net> Subject: Re: Compiler problems with -O2 (was Re: CVS Trouble, even under 4.0-RELEASE (alpha) HELP!) In-Reply-To: <14552.58589.119082.742615@grasshopper.cs.duke.edu> from Andrew Gallatin at "Mar 22, 2000 10:30:32 am" To: Andrew Gallatin Date: Wed, 22 Mar 2000 15:03:09 -0500 (EST) Cc: freebsd-alpha@FreeBSD.org, freebsd-stable@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL72 (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 Actually I have several Alpha's, and one I have to reload due to this, so I will give this a try on the other machine and will let you know if I have good success with it. If this all works, then I agree with you that we want to avoid, or at least note the problem with -O2 as I have been using that when making software on my Intel machines for a long time, so just assumed it was OK to do the same on the Alpha.. > Get rid of -O2 in /etc/make.conf; comment out the CFLAGS line. You > should NEVER, EVER build _anything_ with -O2 on an alpha. The > compiler is very fragile and has been known to do odd things when > compiling -O2. I'm starting to think that any optimizations other > than -O should probably be disabled in the compiler to keep people > from blowing their feet off like you've just done. > > I'd suggest re-loading the machine from the cd at this point, or > building a world on another machine which has a good world & doing a > make installworld via NFS mounts. > > Drew > > ------------------------------------------------------------------------------ > Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin > Duke University Email: gallatin@cs.duke.edu > Department of Computer Science Phone: (919) 660-6590 > --- Howard Leadmon - howardl@abs.net - http://www.abs.net ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 12:41:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.nerv.nu (cx639627-c.irvn1.occa.home.com [24.0.209.134]) by hub.freebsd.org (Postfix) with ESMTP id 11A5937C2BC; Wed, 22 Mar 2000 12:41:22 -0800 (PST) (envelope-from nugundam@nerv.nu) Received: from localhost (nugundam@localhost) by mail.nerv.nu (8.9.3/8.9.3) with ESMTP id MAA34309; Wed, 22 Mar 2000 12:47:14 -0800 (PST) (envelope-from nugundam@greenwood3.nerv.nu) Date: Wed, 22 Mar 2000 12:47:14 -0800 (PST) From: Joseph Lee To: Warner Losh Cc: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: netgear fa410TX and 4.x problems In-Reply-To: <200003200748.AAA13449@harmony.village.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, 20 Mar 2000, Warner Losh wrote: > What's the ethernet address printed on the card? I just made a fix to > if_ed.c that might fix your problem. I've not MFC'd it yet, but will > shortly. Are you in a position to try it? Sorry for the delay. Just got back from SD2000 in San Jose. Anyways, I can try it (the patch is in archives?). I'm getting a mac of all aa:aa:.. 8-bit card, NE1000, currently. pccard says "kludge version>". I can do a dmesg dump if you want. Thanks. -- Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ # Anime Expo 2000 >> www.anime-expo.org/ > # FreeBSD: The Power to Serve >> www.freebsd.org > # The Ultimate Online Speed-Shop >> www.racesearch.com / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 13: 4:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id BCEBB37BA13; Wed, 22 Mar 2000 13:04:39 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA29561; Wed, 22 Mar 2000 14:04:38 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA33511; Wed, 22 Mar 2000 14:04:37 -0700 (MST) Message-Id: <200003222104.OAA33511@harmony.village.org> To: Joseph Lee Subject: Re: netgear fa410TX and 4.x problems Cc: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, msmith@FreeBSD.ORG In-reply-to: Your message of "Wed, 22 Mar 2000 12:47:14 PST." References: Date: Wed, 22 Mar 2000 14:04:37 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Joseph Lee writes: : Sorry for the delay. Just got back from SD2000 in San Jose. : : Anyways, I can try it (the patch is in archives?). I'm getting a mac of all : aa:aa:.. 8-bit card, NE1000, currently. : : pccard says "kludge version>". I can do a dmesg dump if you want. Since I committed the patches to if_ed in the last 24 hours, I'll guess that you don't have them. Please try them and let me know. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 13: 7:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mg134-217.ricochet.net [204.179.134.217]) by hub.freebsd.org (Postfix) with ESMTP id A36C837B84D for ; Wed, 22 Mar 2000 13:07:41 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA01236; Wed, 22 Mar 2000 13:10:25 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003222110.NAA01236@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Vivek Khera Cc: stable@FreeBSD.ORG Subject: Re: "dangerously dedicated" In-reply-to: Your message of "Wed, 22 Mar 2000 10:06:44 EST." <14552.57732.739752.665443@onceler.kcilink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 22 Mar 2000 13:10:23 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Why is using /dev/da0a stupid? FreeBSD is the only system I've > encountered that totally locks up (during a 3.3-RELEASE install from > CD) when there is no fdisk disk label. Is that why it is stupid? You can't boot from a disk that doesn't have an MBR on it. This is a feature of the PC BIOS, and it can't be worked around. > BSD/OS and Linux (RedHat 6.1) both deal with the lack of an fdisk disk > label just fine, and BSD/OS doesn't even require one, letting you use > the direct unix partitioning scheme. I much prefer it that way as it > just makes sense on a dedicated box, which is what all of mine are. You're out of your depth here, unfortunately. Both of these systems do install an MBR, they just don't tell you that they are. Regardless of what you think, the only correct way to divvy up a disk on a PC is to start with an MBR and work down from there. There is no other way to do this properly, and to think otherwise merely demonstrates your ignorance. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 13:13:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id 9311737B5C4; Wed, 22 Mar 2000 13:13:36 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 51E5DE896; Wed, 22 Mar 2000 16:13:35 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id QAA29364; Wed, 22 Mar 2000 16:13:35 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14553.14207.194024.839781@onceler.kcilink.com> Date: Wed, 22 Mar 2000 16:13:35 -0500 (EST) To: Mike Smith Cc: stable@FreeBSD.ORG Subject: Re: "dangerously dedicated" In-Reply-To: <200003222110.NAA01236@mass.cdrom.com> References: <14552.57732.739752.665443@onceler.kcilink.com> <200003222110.NAA01236@mass.cdrom.com> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "MS" == Mike Smith writes: MS> Regardless of what you think, the only correct way to divvy up a disk on MS> a PC is to start with an MBR and work down from there. There is no other MS> way to do this properly, and to think otherwise merely demonstrates your MS> ignorance. Excuse me, but an MBR is not an FDISK label. I had a system that had BSD/OS instaled on it with no FDISK label and it worked just fine. Linux detected the disk and installed fine, as well. The only time I ever needed to have an FDISK label on a PeeCee was when trying to boot with a silly NCR scsi controller that demanded one. An empty one was fine. Tried to install FreeBSD on it and it just hung when probing for devices. I finally booted a freedos disk and ran it's fdisk program to put in an empty FDISK label. Then FreeBSD was able to use the disk. Who's demonstrating ignorance here? -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 PGP & MIME spoken here http://www.kciLink.com/home/khera/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 13:24:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mg134-217.ricochet.net [204.179.134.217]) by hub.freebsd.org (Postfix) with ESMTP id 6E83837B65E; Wed, 22 Mar 2000 13:24:16 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA01303; Wed, 22 Mar 2000 13:27:08 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003222127.NAA01303@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Vivek Khera Cc: Mike Smith , stable@freebsd.org Subject: Re: "dangerously dedicated" In-reply-to: Your message of "Wed, 22 Mar 2000 16:13:35 EST." <14553.14207.194024.839781@onceler.kcilink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 22 Mar 2000 13:27:08 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >>>>> "MS" == Mike Smith writes: > > MS> Regardless of what you think, the only correct way to divvy up a disk on > MS> a PC is to start with an MBR and work down from there. There is no other > MS> way to do this properly, and to think otherwise merely demonstrates your > MS> ignorance. > > Excuse me, but an MBR is not an FDISK label. I had a system that had > BSD/OS instaled on it with no FDISK label and it worked just fine. The first 512 bytes of any disk attached to a PC are assumed to be a valid MBR. Such a valid MBR includes boot code, a table describing four disk regions and a checksum. This table of disk regions must be present; you cannot expect reliable operation without it. > Who's demonstrating ignorance here? "It works for me" isn't even close to a valid argument. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 14:28: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay.ipf.net (relay.gigabell.net [195.211.211.23]) by hub.freebsd.org (Postfix) with SMTP id 17F6637C2EA for ; Wed, 22 Mar 2000 14:27:51 -0800 (PST) (envelope-from jachmann@gigabell.net) Received: (qmail 83607 invoked from network); 22 Mar 2000 22:27:46 -0000 Received: from habbib.bauernstand.org (HELO gigabell.net) (195.88.64.7) by relay.gigabell.net with SMTP; 22 Mar 2000 22:27:46 -0000 Message-ID: <38D948E1.50F3FC58@gigabell.net> Date: Wed, 22 Mar 2000 23:27:45 +0100 From: Christian Jachmann Organization: Gigabell AG X-Mailer: Mozilla 4.07 [en] (X11; I; Linux 2.2.2 i586) MIME-Version: 1.0 To: "stable@freebsd.org" Subject: 3.4-Stable crashes..(heavy diskio+networking) 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 running 3.4 Stable here, machine is a central newsfeed. Machine is running INN 2.2.2 (latest Snapshot) Network thrououtput is several hundred Gigabytes a Day. We do have about 150 streaming connections on this site. It reboots about every 24 hours. Is it bad ram ? or the temperature ? Maybe someone give me a hint. --------------------- Debuging Information: --------------------- Output of gdb: gdb -k kernel.14 vmcore.14 IdlePTD 2433024 initial pcb at 1f0594 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x12 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0148ff0 stack pointer = 0x10:0xda886dac frame pointer = 0x10:0xda886dc8 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 = 2542 (innfeed) interrupt mask = trap number = 12 panic: page fault syncing disks... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x12 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0148ff0 stack pointer = 0x10:0xda8868dc frame pointer = 0x10:0xda8868f8 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 = 2542 (innfeed) interrupt mask = trap number = 12 panic: page fault dumping to dev 20401, offset 524288 dump 768 767 766 765 764 763 762 761 760 759 758 757 756 755 754 753 752 751 750 749 748 747 746 745 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:285 285 dumppcb.pcb_cr3 = rcr3(); #0 boot (howto=260) at ../../kern/kern_shutdown.c:285 #1 0xc0132b1d in panic (fmt=0xc01d78d2 "page fault") at ../../kern/kern_shutdown.c:446 #2 0xc01b66b2 in trap_fatal (frame=0xda8868a0, eva=18) at ../../i386/i386/trap.c:942 #3 0xc01b636b in trap_pfault (frame=0xda8868a0, usermode=0, eva=18) at ../../i386/i386/trap.c:835 #4 0xc01b5fca in trap (frame={tf_es = -1072234480, tf_ds = -981401584, tf_edi = 0, tf_esi = 0, tf_ebp = -628594440, tf_isp = -628594488, tf_ebx = 0, tf_edx = -2147483648, tf_ecx = 40, tf_eax = 40, tf_trapno = 12, tf_err = 0, tf_eip = -1072394256, tf_cs = 8, tf_eflags = 66118, tf_esp = 0, tf_ss = -1073610752}) at ../../i386/i386/trap.c:437 #5 0xc0148ff0 in m_copym (m=0x0, off0=0, len=46, wait=1) at ../../kern/uipc_mbuf.c:433 #6 0xc01747d2 in tcp_output (tp=0xd9e4ff00) at ../../netinet/tcp_output.c:505 #7 0xc0175931 in tcp_fasttimo () at ../../netinet/tcp_timer.c:106 #8 0xc014883b in pffasttimo (arg=0x0) at ../../kern/uipc_domain.c:292 #9 0xc0137332 in softclock () at ../../kern/kern_timeout.c:132 #10 0xc01ad563 in doreti_swi () #11 0xc015181f in getblk (vp=0xda7d69c0, blkno=1048720, size=8192, slpflag=0, slptimeo=0) at ../../kern/vfs_bio.c:1437 #12 0xc015019d in bread (vp=0xda7d69c0, blkno=1048720, size=8192, cred=0x0, bpp=0xda886ae0) at ../../kern/vfs_bio.c:282 #13 0xc01834d0 in ffs_update (vp=0xda863f80, waitfor=0) at ../../ufs/ffs/ffs_inode.c:98 #14 0xc0187e5f in ffs_fsync (ap=0xda886c5c) at ../../ufs/ffs/ffs_vnops.c:258 #15 0xc01977f2 in vm_object_page_clean (object=0xda83083c, start=0, end=0, flags=0) at vnode_if.h:499 #16 0xc01585e5 in vfs_msync (mp=0xc58c5e00, flags=2) at ../../kern/vfs_subr.c:2473 #17 0xc0159518 in sync (p=0xc0204318, uap=0x0) at ../../kern/vfs_syscalls.c:548 #18 0xc01326c5 in boot (howto=256) at ../../kern/kern_shutdown.c:203 #19 0xc0132b1d in panic (fmt=0xc01d78d2 "page fault") at ../../kern/kern_shutdown.c:446 #20 0xc01b66b2 in trap_fatal (frame=0xda886d70, eva=18) at ../../i386/i386/trap.c:942 #21 0xc01b636b in trap_pfault (frame=0xda886d70, usermode=0, eva=18) at ../../i386/i386/trap.c:835 #22 0xc01b5fca in trap (frame={tf_es = -980418544, tf_ds = -980418544, tf_edi = 0, tf_esi = 0, tf_ebp = -628593208, tf_isp = -628593256, tf_ebx = 0, tf_edx = 0, tf_ecx = 40, tf_eax = 40, tf_trapno = 12, tf_err = 0, tf_eip = -1072394256, tf_cs = 8, tf_eflags = 66118, tf_esp = 0, tf_ss = -1073610752}) at ../../i386/i386/trap.c:437 #23 0xc0148ff0 in m_copym (m=0x0, off0=0, len=46, wait=1) at ../../kern/uipc_mbuf.c:433 #24 0xc01747d2 in tcp_output (tp=0xd9e4ff00) at ../../netinet/tcp_output.c:505 #25 0xc017608a in tcp_usr_send (so=0xd97e7f00, flags=0, m=0xc188b800, nam=0x0, control=0x0, p=0xda7da520) at ../../netinet/tcp_usrreq.c:395 #26 0xc014aa8e in sosend (so=0xd97e7f00, addr=0x0, uio=0xda886f40, top=0xc188b800, control=0x0, flags=0, p=0xda7da520) at ../../kern/uipc_socket.c:530 #27 0xc0140944 in soo_write (fp=0xc59c9f80, uio=0xda886f40, cred=0xc58fbc80, flags=0) at ../../kern/sys_socket.c:82 #28 0xc013da55 in writev (p=0xda7da520, uap=0xda886f94) at ../../kern/sys_generic.c:447 #29 0xc01b690f in syscall (frame={tf_es = 134676519, tf_ds = -1078001625, tf_edi = 1, tf_esi = 1, tf_ebp = -1077946012, tf_isp = -628592668, tf_ebx = 8388608, tf_edx = 134763136, tf_ecx = 134763136, tf_eax = 121, tf_trapno = 22, tf_err = 2, tf_eip = 671933924, tf_cs = 31, tf_eflags = 514, tf_esp = -1077946056, tf_ss = 39}) at ../../i386/i386/trap.c:1100 #30 0xc01ac28c in Xint0x80_syscall () #31 0x805246d in ?? () sysctl -a: ---------- ern.ostype: FreeBSD kern.osrelease: 3.4-STABLE kern.osrevision: 199506 kern.version: FreeBSD 3.4-STABLE #0: Tue Mar 21 22:33:28 CET 2000 root@newscore.gigabell.net:/usr/src/sys/compile/MY kern.maxvnodes: 56501 kern.maxproc: 8212 kern.maxfiles: 16424 kern.argmax: 65536 kern.securelevel: -1 kern.hostname: newscore.gigabell.net kern.hostid: 0 kern.clockrate: { hz = 100, tick = 10000, tickadj = 5, profhz = 1024, stathz = 128 } kern.posix1version: 199009 kern.ngroups: 16 kern.job_control: 1 kern.saved_ids: 0 kern.boottime: { sec = 953741562, usec = 345570 } Wed Mar 22 17:12:42 2000 kern.domainname: kern.osreldate: 340001 kern.bootfile: /kernel kern.maxfilesperproc: 16424 kern.maxprocperuid: 8211 kern.dumpdev: { major = 4, minor = 131073 } kern.ipc.maxsockbuf: 262144 kern.ipc.sockbuf_waste_factor: 8 kern.ipc.somaxconn: 128 kern.ipc.max_linkhdr: 16 kern.ipc.max_protohdr: 40 kern.ipc.max_hdr: 56 kern.ipc.max_datalen: 40 kern.ipc.nmbclusters: 26112 kern.ipc.maxsockets: 26112 kern.dummy: 0 kern.ps_strings: -1077944336 kern.usrstack: -1077944320 kern.logsigexit: 1 kern.init_path: /sbin/init:/sbin/oinit:/sbin/init.bak:/stand/sysinstall kern.module_path: /;/boot/;/modules/ kern.acct_suspend: 2 kern.acct_resume: 4 kern.acct_chkfreq: 15 kern.timecounter.method: 0 kern.fast_vfork: 1 kern.sugid_coredump: 0 kern.corefile: %N.core kern.quantum: 100000 kern.ccpu: 1948 kern.fscale: 2048 kern.devstat.numdevs: 5 kern.devstat.generation: 5 kern.devstat.version: 3 kern.consmute: 0 vm.loadavg: { 0.48 0.45 0.46 } vm.v_free_min: 1329 vm.v_free_target: 4352 vm.v_free_reserved: 365 vm.v_inactive_target: 6528 vm.v_cache_min: 4352 vm.v_cache_max: 8704 vm.v_pageout_free_min: 34 vm.pageout_algorithm: 0 vm.swap_enabled: 1 vm.swap_idle_threshold1: 2 vm.swap_idle_threshold2: 10 vm.stats.sys.v_swtch: 25744685 vm.stats.sys.v_trap: 22613584 vm.stats.sys.v_syscall: 104406487 vm.stats.sys.v_intr: 41945786 vm.stats.sys.v_soft: 18841317 vm.stats.vm.v_vm_faults: 9333924 vm.stats.vm.v_cow_faults: 56013 vm.stats.vm.v_cow_optim: 16775 vm.stats.vm.v_zfod: 8412442 vm.stats.vm.v_ozfod: 5240413 vm.stats.vm.v_swapin: 0 vm.stats.vm.v_swapout: 0 vm.stats.vm.v_swappgsin: 0 vm.stats.vm.v_swappgsout: 0 vm.stats.vm.v_vnodein: 22365 vm.stats.vm.v_vnodeout: 400767 vm.stats.vm.v_vnodepgsin: 27144 vm.stats.vm.v_vnodepgsout: 479341 vm.stats.vm.v_intrans: 2823 vm.stats.vm.v_reactivated: 2881 vm.stats.vm.v_pdwakeups: 1673 vm.stats.vm.v_pdpages: 6431353 vm.stats.vm.v_dfree: 1165 vm.stats.vm.v_pfree: 72864 vm.stats.vm.v_tfree: 8578235 vm.stats.vm.v_page_size: 4096 vm.stats.vm.v_page_count: 193159 vm.stats.vm.v_free_reserved: 365 vm.stats.vm.v_free_target: 4352 vm.stats.vm.v_free_min: 1329 vm.stats.vm.v_free_count: 544 vm.stats.vm.v_wire_count: 5717 vm.stats.vm.v_active_count: 54885 vm.stats.vm.v_inactive_target: 6528 vm.stats.vm.v_inactive_count: 124409 vm.stats.vm.v_cache_count: 7575 vm.stats.vm.v_cache_min: 4352 vm.stats.vm.v_cache_max: 8704 vm.stats.vm.v_pageout_free_min: 34 vm.stats.vm.v_interrupt_free_min: 2 vm.stats.misc.zero_page_count: 374 vm.stats.misc.cnt_prezero: 6271661 vm.pageout_stats_max: 4352 vm.pageout_full_stats_interval: 20 vm.pageout_stats_interval: 5 vm.pageout_stats_free_max: 5 vm.swap_idle_enabled: 0 vm.defer_swapspace_pageouts: 0 vm.disable_swapspace_pageouts: 0 vm.max_page_launder: 32 vm.zone: ITEM SIZE LIMIT USED FREE REQUESTS PIPE: 160, 0, 2, 100, 2507 unpcb: 64, 0, 25, 103, 728 ripcb: 96, 26112, 0, 42, 0 tcpcb: 288, 26112, 131, 65, 2991 udpcb: 96, 26112, 5, 79, 921 unpcb: 64, 0, 0, 0, 0 socket: 160, 26112, 161, 89, 4650 AIOLIO: 704, 0, 0, 0, 0 AIOL: 64, 0, 0, 0, 0 AIOCB: 128, 0, 0, 0, 0 AIOP: 32, 0, 0, 0, 0 AIO: 96, 0, 0, 0, 0 VNODE: 192, 0, 410, 120, 405 NAMEI: 1024, 0, 0, 16, 110867 VMSPACE: 192, 0, 22, 42, 1825 PROC: 352, 0, 25, 33, 1828 DP fakepg: 64, 0, 0, 0, 0 PV ENTRY: 28, 2035610, 64396, 132209, 10097287 MAP ENTRY: 40, 0, 664, 178, 1967785 KMAP ENTRY: 40, 48417, 51, 179, 1616 MAP: 100, 0, 7, 3, 7 VM OBJECT: 124, 0, 604, 81, 32505 vm.zone_kmem_pages: 28 vm.zone_kmem_kvaspace: 70139904 vm.zone_kern_pages: 63 vfs.numdirtybuffers: 52 vfs.lodirtybuffers: 139 vfs.hidirtybuffers: 279 vfs.numfreebuffers: 2026 vfs.lofreebuffers: 120 vfs.hifreebuffers: 240 vfs.maxbufspace: 8544256 vfs.bufspace: 8544256 vfs.maxvmiobufspace: 5696170 vfs.vmiospace: 8510464 vfs.maxmallocbufspace: 427212 vfs.bufmallocspace: 13312 vfs.kvafreespace: 311296 vfs.cache.numneg: 19 vfs.cache.numcache: 306 vfs.cache.numcalls: 371609 vfs.cache.dothits: 352 vfs.cache.dotdothits: 85 vfs.cache.numchecks: 386235 vfs.cache.nummiss: 10008 vfs.cache.nummisszap: 9212 vfs.cache.numposzaps: 3417 vfs.cache.numposhits: 318935 vfs.cache.numnegzaps: 2760 vfs.cache.numneghits: 26840 vfs.cache.maxaliases: 4 vfs.cache.numcwdcalls: 136 vfs.cache.numcwdfail1: 0 vfs.cache.numcwdfail2: 0 vfs.cache.numcwdfail3: 0 vfs.cache.numcwdfail4: 0 vfs.cache.numcwdfound: 136 vfs.mod0: 0 vfs.mod1: 0 vfs.usermount: 0 vfs.aio.max_aio_per_proc: 32 vfs.aio.max_aio_queue_per_proc: 256 vfs.aio.max_aio_procs: 32 vfs.aio.num_aio_procs: 0 vfs.aio.num_queue_count: 0 vfs.aio.max_aio_queue: 1024 vfs.aio.target_aio_procs: 0 vfs.aio.max_buf_aio: 16 vfs.aio.num_buf_aio: 0 vfs.aio.aiod_lifetime: 3000 vfs.aio.aiod_timeout: 1000 vfs.ffs.doreallocblks: 1 vfs.ffs.doasyncfree: 1 net.local.stream.sendspace: 8192 net.local.stream.recvspace: 8192 net.local.dgram.maxdgram: 2048 net.local.dgram.recvspace: 4096 net.local.inflight: 0 net.inet.ip.portrange.lowfirst: 1023 net.inet.ip.portrange.lowlast: 600 net.inet.ip.portrange.first: 1024 net.inet.ip.portrange.last: 5000 net.inet.ip.portrange.hifirst: 49152 net.inet.ip.portrange.hilast: 65535 net.inet.ip.forwarding: 0 net.inet.ip.redirect: 1 net.inet.ip.ttl: 64 net.inet.ip.rtexpire: 3600 net.inet.ip.rtminexpire: 10 net.inet.ip.rtmaxcache: 128 net.inet.ip.sourceroute: 0 net.inet.ip.intr_queue_maxlen: 50 net.inet.ip.intr_queue_drops: 0 net.inet.ip.accept_sourceroute: 0 net.inet.ip.fastforwarding: 0 net.inet.ip.subnets_are_local: 0 net.inet.icmp.maskrepl: 0 net.inet.icmp.icmplim: -1 net.inet.icmp.drop_redirect: 0 net.inet.icmp.log_redirect: 0 net.inet.icmp.bmcastecho: 0 net.inet.tcp.rfc1323: 0 net.inet.tcp.rfc1644: 0 net.inet.tcp.mssdflt: 512 net.inet.tcp.rttdflt: 3 net.inet.tcp.keepidle: 14400 net.inet.tcp.keepintvl: 150 net.inet.tcp.sendspace: 16384 net.inet.tcp.recvspace: 16384 net.inet.tcp.keepinit: 150 net.inet.tcp.log_in_vain: 0 net.inet.tcp.delayed_ack: 1 net.inet.tcp.pcbcount: 131 net.inet.tcp.always_keepalive: 1 net.inet.udp.checksum: 1 net.inet.udp.maxdgram: 9216 net.inet.udp.recvspace: 41600 net.inet.udp.log_in_vain: 0 net.inet.raw.maxdgram: 8192 net.inet.raw.recvspace: 8192 net.link.generic.system.ifcount: 2 net.link.ether.inet.prune_intvl: 300 net.link.ether.inet.max_age: 1200 net.link.ether.inet.host_down_time: 20 net.link.ether.inet.maxtries: 5 net.link.ether.inet.useloopback: 1 net.link.ether.inet.proxyall: 0 debug.enter_debugger: debug.elf_trace: 0 debug.fdexpand: 16 debug.debugger_on_panic: 0 debug.ttydebug: 0 debug.nchash: 65535 debug.ncnegfactor: 16 debug.numneg: 19 debug.numcache: 306 debug.vfscache: 1 debug.vnsize: 168 debug.ncsize: 36 debug.numvnodes: 410 debug.wantfreevnodes: 25 debug.freevnodes: 125 debug.busyprt: 0 debug.disablecwd: 0 debug.bpf_bufsize: 4096 debug.ncr_debug: 0 hw.machine: i386 hw.model: Pentium III hw.ncpu: 1 hw.byteorder: 1234 hw.physmem: 803508224 hw.usermem: 780095488 hw.pagesize: 4096 hw.floatingpoint: 1 hw.machine_arch: i386 hw.availpages: 196009 machdep.consdev: { major = 0, minor = 0 } machdep.adjkerntz: 0 machdep.disable_rtc_set: 0 machdep.wall_cmos_clock: 0 machdep.do_dump: 1 machdep.ispc98: 0 machdep.msgbuf: machdep.msgbuf_clear: 0 machdep.i8254_freq: 1193182 machdep.tsc_freq: 451024885 machdep.conspeed: 9600 user.cs_path: /usr/bin:/bin:/usr/sbin:/sbin: user.bc_base_max: 99 user.bc_dim_max: 2048 user.bc_scale_max: 99 user.bc_string_max: 1000 user.coll_weights_max: 0 user.expr_nest_max: 32 user.line_max: 2048 user.re_dup_max: 255 user.posix2_version: 199212 user.posix2_c_bind: 0 user.posix2_c_dev: 0 user.posix2_char_term: 0 user.posix2_fort_dev: 0 user.posix2_fort_run: 0 user.posix2_localedef: 0 user.posix2_sw_dev: 0 user.posix2_upe: 0 user.stream_max: 20 user.tzname_max: 255 p1003_1b.asynchronous_io: 0 p1003_1b.mapped_files: 0 p1003_1b.memlock: 0 p1003_1b.memlock_range: 0 p1003_1b.memory_protection: 0 p1003_1b.message_passing: 0 p1003_1b.prioritized_io: 0 p1003_1b.priority_scheduling: 0 p1003_1b.realtime_signals: 0 p1003_1b.semaphores: 0 p1003_1b.fsync: 0 p1003_1b.shared_memory_objects: 0 p1003_1b.synchronized_io: 0 p1003_1b.timers: 0 p1003_1b.aio_listio_max: 0 p1003_1b.aio_max: 0 p1003_1b.aio_prio_delta_max: 0 p1003_1b.delaytimer_max: 0 p1003_1b.mq_open_max: 0 p1003_1b.pagesize: 4096 p1003_1b.rtsig_max: 0 p1003_1b.sem_nsems_max: 0 p1003_1b.sem_value_max: 0 p1003_1b.sigqueue_max: 0 p1003_1b.timer_max: 0 here is dmesg: -------------- Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.4-STABLE #0: Tue Mar 21 22:33:28 CET 2000 root@newscore.gigabell.net:/usr/src/sys/compile/MY Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 451024885 Hz CPU: Pentium III (451.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383f9ff> real memory = 805306368 (786432K bytes) avail memory = 780439552 (762148K bytes) Preloaded elf kernel "kernel" at 0xc0240000. Pentium Pro MTRR support enabled Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x02 on pci0.4.0 chip3: rev 0x02 on pci0.4.3 fxp0: rev 0x08 int a irq 12 on pci0.9.0 fxp0: Ethernet address 00:90:27:9d:1f:1f ncr0: rev 0x02 int a irq 10 on pci0.11.0 Probing for devices on PCI bus 1: vga0: rev 0x5c int a irq 11 on pci1.0.0 Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Waiting 3 seconds for SCSI devices to settle changing root device to da0s1a da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 34732MB (71132960 512 byte sectors: 255H 63S/T 4427C) WARNING: / was not properly dismounted Start pid=2 Start pid=3 Start pid=4 Kernel config: -------------- machine "i386" cpu "I686_CPU" ident MY maxusers 512 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=3000 #Be pessimistic about Joe SCSI device options FAILSAFE #Be conservative options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores config kernel root on da0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 controller ncr0 # NCR/Symbios Logic controller scbus0 # SCSI bus (required) device da0 # Direct Access (disks) device pass0 # Passthrough device (direct SCSI) controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device vga0 at isa? port ? conflicts device sc0 at isa? tty device npx0 at isa? port IO_NPX irq 13 device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device pty 16 # Pseudo-ttys (telnet etc) pseudo-device bpfilter 4 #Berkeley packet filter options DDB options DDB_UNATTENDED options DIAGNOSTIC options NMBCLUSTERS=26112 ---------------------------------- BYe -- Christian Jachmann GIGABELL AG - Technik ++49 69 17084-0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 14:32:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail4.uunet.ca (mail4.uunet.ca [209.167.141.34]) by hub.freebsd.org (Postfix) with ESMTP id E332E37C398 for ; Wed, 22 Mar 2000 14:32:16 -0800 (PST) (envelope-from matt@ARPA.MAIL.NET) Received: from epsilon.lucida.qc.ca ([216.95.146.6]) by mail4.uunet.ca with ESMTP id <207443-26265>; Wed, 22 Mar 2000 17:32:04 -0500 Date: Wed, 22 Mar 2000 17:32:04 -0500 From: Matt Heckaman X-Sender: matt@epsilon.lucida.qc.ca To: Christian Jachmann Cc: "stable@freebsd.org" Subject: Re: 3.4-Stable crashes..(heavy diskio+networking) 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 [...] : It reboots about every 24 hours. : : Is it bad ram ? : or the temperature ? : Maybe someone give me a hint. This may sound silly, but have you looked at the value for your NMBCLUSTERS? FreeBSD panics when it runs out of them, as can happen in a high network load situation. I scale mine based on the bandwidth and assume a worst case scenario of a denial of service attack. I've found 16,384 good for T1+, moving to double that for 10Mbit, as for beyond that, I've never worked with anything that high. Matt -- Matt Heckaman [matt@arpa.mail.net|matt@relic.net] [Please do not send me] !Powered by FreeBSD/x86! [http://www.freebsd.org] [any SPAM (UCE) e-mail] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 14:34:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id C1B8F37C272; Wed, 22 Mar 2000 14:34:42 -0800 (PST) (envelope-from obrien@NUXI.ucdavis.edu) Received: from dragon.nuxi.com (root@d60-024.leach.ucdavis.edu [169.237.60.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA41431; Wed, 22 Mar 2000 14:34:41 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA97436; Wed, 22 Mar 2000 13:09:01 -0800 (PST) (envelope-from obrien) Date: Wed, 22 Mar 2000 13:09:01 -0800 From: "David O'Brien" To: Howard Leadmon Cc: freebsd-alpha@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Compiler problems with -O2 (was Re: CVS Trouble, even under 4.0-RELEASE (alpha) HELP!) Message-ID: <20000322130901.A97411@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <14552.58589.119082.742615@grasshopper.cs.duke.edu> <200003222003.PAA51043@account.abs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003222003.PAA51043@account.abs.net>; from howardl@account.abs.net on Wed, Mar 22, 2000 at 03:03:09PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 22, 2000 at 03:03:09PM -0500, Howard Leadmon wrote: > want to avoid, or at least note the problem with -O2 as I have been using > that when making software on my Intel machines for a long time, so just > assumed it was OK to do the same on the Alpha.. It isn't officially OK from the perspective of the FreeBSD Project. "-O2" has been the cause of problems on the i386 arch too. Thus my constant yelling about it that nobody pays attention to. I'm on the virge of turning off "-O2" on both Alpha and i386. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 14:37:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id 0022037C2D2 for ; Wed, 22 Mar 2000 14:37:53 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id LAA84469; Thu, 23 Mar 2000 11:02:33 -0600 (CST) From: Joe Greco Message-Id: <200003231702.LAA84469@aurora.sol.net> Subject: Re: dot-0 releases To: blk@skynet.be Date: Thu, 23 Mar 2000 11:02:33 -0600 (CST) Cc: stable@freebsd.org Reply-To: chat@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One Brad Knowles uttered the following words: > I ain't no Matt Dillon, Jordan K. Hubbard, Mike O'Dell, David > Greenman, Doug Barton, Joe Greco, Mike Horwath, Russell Vincent, or > anybody else like that. > > I like to think that I've learned a little something in the > ten-plus years I've been doing Unix system administration, > large-scale Internet mail systems administration, consulting, etc..., > but I have a long ways to go before I can hope to compare to people > like this. OMG, now, that is just the worst bit of bootlicking I've seen this year. -- ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 14:40:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wit401310.student.utwente.nl (wit401310.student.utwente.nl [130.89.236.150]) by hub.freebsd.org (Postfix) with ESMTP id 1CA8D37C2C3 for ; Wed, 22 Mar 2000 14:40:40 -0800 (PST) (envelope-from dalroi@wit401310.student.utwente.nl) Received: from wit401310.student.utwente.nl (localhost [127.0.0.1]) by wit401310.student.utwente.nl (Postfix) with ESMTP id 5CF061F05; Wed, 22 Mar 2000 23:40:58 +0100 (CET) Date: Wed, 22 Mar 2000 23:40:58 +0100 (CET) From: Alban Hertroys Subject: Re: 4.0 Install World problems on all systems To: Joe Gleason Cc: bod@tasam.com, freebsd-stable@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Message-Id: <20000322224058.5CF061F05@wit401310.student.utwente.nl> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21 Mar, Joe Gleason wrote: > cp /usr/obj/usr/src/i386/usr/bin/install-info /usr/bin > > If this is done after make buildworld and before installworld, it should > be groovy. > > The old version of install-info does not work correctly when doing > the installworld. This reminds me of the trouble I got after doing that. I had missed the notion that i neded to compile a new kernel first, so after doing this my /bin/sh's exec-ed by make started raining core-dumps on me. No need to say my install was pretty much screwed after that. The only thing still working was the shell I statred the make installworld from... Eventually I managed to get things working from the emergency holographic shell in the install boot floppies (Unfortunately I did install /bin first, which happily overwrote most of my /etc files). To prevent this in the future: Maybe it is an idea to test if the newly compiled versions of installation programs like sh, cp, mv, etc. actually do work in the current environment? That gives a good warning that something is going wrong, and it doesn't screw up your working OS. Now I suppose this doesn't *ensure* a correct install, but it does decrease the risks. Another suggestion: In sysinstall, make /bin and /etc two different install sets instead of the one that's in it now, so that installing just /bin to recover the programs you need doesn't erase your setup. -- Alban Hertroys http://wit401310.student.utwente.nl - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This person has performed an illegal operation and will be shot down. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 14:42: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay.ipf.net (relay.gigabell.net [195.211.211.23]) by hub.freebsd.org (Postfix) with SMTP id AE60A37C282 for ; Wed, 22 Mar 2000 14:41:57 -0800 (PST) (envelope-from jachmann@gigabell.net) Received: (qmail 86401 invoked from network); 22 Mar 2000 22:41:56 -0000 Received: from habbib.bauernstand.org (HELO gigabell.net) (195.88.64.7) by relay.gigabell.net with SMTP; 22 Mar 2000 22:41:56 -0000 Message-ID: <38D94C33.F7EE5A89@gigabell.net> Date: Wed, 22 Mar 2000 23:41:55 +0100 From: Christian Jachmann Organization: Gigabell AG X-Mailer: Mozilla 4.07 [en] (X11; I; Linux 2.2.2 i586) MIME-Version: 1.0 To: Matt Heckaman Cc: "stable@freebsd.org" Subject: Re: 3.4-Stable crashes..(heavy diskio+networking) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Heckaman wrote: > > [...] > : It reboots about every 24 hours. > : > : Is it bad ram ? > : or the temperature ? > : Maybe someone give me a hint. > > This may sound silly, but have you looked at the value for your > NMBCLUSTERS? FreeBSD panics when it runs out of them, as can happen in a > high network load situation. I scale mine based on the bandwidth and > assume a worst case scenario of a denial of service attack. I've found > 16,384 good for T1+, moving to double that for 10Mbit, as for beyond that, > I've never worked with anything that high. Yes,I rised it several weeks ago, root@newscore>netstat -m 569/1984 mbufs in use: 347 mbufs allocated to data 222 mbufs allocated to packet headers 214/714/26112 mbuf clusters in use (current/peak/max) 1676 Kbytes allocated to network (29% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines looks not so bad, or ? But system still crashes. BYe -- Christian Jachmann Gigabell AG - Technik ++49 69 17084-0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 14:42:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from account.abs.net (account.abs.net [207.114.5.70]) by hub.freebsd.org (Postfix) with ESMTP id B0BC237B6A8; Wed, 22 Mar 2000 14:42:28 -0800 (PST) (envelope-from howardl@account.abs.net) Received: (from howardl@localhost) by account.abs.net (8.9.3/8.9.3+RBL+DUL+RSS+ORBS) id RAA61811; Wed, 22 Mar 2000 17:42:27 -0500 (EST) (envelope-from howardl) From: Howard Leadmon Message-Id: <200003222242.RAA61811@account.abs.net> Subject: Re: Compiler problems with -O2 (was Re: CVS Trouble, even under 4.0-RELEASE (alpha) HELP!) In-Reply-To: <20000322130901.A97411@dragon.nuxi.com> from "David O'Brien" at "Mar 22, 2000 01:09:01 pm" To: obrien@FreeBSD.ORG Date: Wed, 22 Mar 2000 17:42:27 -0500 (EST) Cc: freebsd-alpha@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL72 (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 > > want to avoid, or at least note the problem with -O2 as I have been using > > that when making software on my Intel machines for a long time, so just > > assumed it was OK to do the same on the Alpha.. > > It isn't officially OK from the perspective of the FreeBSD Project. "-O2" > has been the cause of problems on the i386 arch too. Thus my constant > yelling about it that nobody pays attention to. > > I'm on the virge of turning off "-O2" on both Alpha and i386. > > -- > -- David (obrien@NUXI.com) Well I can see your point, one would have thought as the compilers have evolved stuff like this would have been fixed and working OK, so much for that thought. If I am not the only of-the-wall person who has made this mistake, maybe at a minimum a note should be in the various config files, or at least in the notes stating that it's strongly advised one not use the -O2 flag while compiling the OS, as it can cause things to break. Guess I just got lucky on the Intel boxes, so live and learn. FYI, I am currently recompiling 4.0-STABLE on one of my Alpha's, and guess in a few hours I'll see if all works OK after an installworld and a quick reboot.. :) --- Howard Leadmon - howardl@abs.net - http://www.abs.net ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 14:42:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 82B7937C539; Wed, 22 Mar 2000 14:42:42 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA13386; Wed, 22 Mar 2000 17:42:33 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id RAA08255; Wed, 22 Mar 2000 17:42:03 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 22 Mar 2000 17:42:03 -0500 (EST) To: obrien@FreeBSD.ORG Cc: Howard Leadmon , freebsd-alpha@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Compiler problems with -O2 (was Re: CVS Trouble, even under 4.0-RELEASE (alpha) HELP!) In-Reply-To: <20000322130901.A97411@dragon.nuxi.com> References: <14552.58589.119082.742615@grasshopper.cs.duke.edu> <200003222003.PAA51043@account.abs.net> <20000322130901.A97411@dragon.nuxi.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14553.19348.115781.273817@grasshopper.cs.duke.edu> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien writes: > On Wed, Mar 22, 2000 at 03:03:09PM -0500, Howard Leadmon wrote: > > want to avoid, or at least note the problem with -O2 as I have been using > > that when making software on my Intel machines for a long time, so just > > assumed it was OK to do the same on the Alpha.. > > It isn't officially OK from the perspective of the FreeBSD Project. "-O2" > has been the cause of problems on the i386 arch too. Thus my constant > yelling about it that nobody pays attention to. > > I'm on the virge of turning off "-O2" on both Alpha and i386. You certainly have my vote. I take it the O2 bugs are not unique to us, but rather they are generic across all OSes that gcc version 2.95.2 runs on? Do the gcc people know these problems exist? Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 14:54:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hub.ucsb.edu (hub.ucsb.edu [128.111.24.40]) by hub.freebsd.org (Postfix) with ESMTP id 64B2B37C296 for ; Wed, 22 Mar 2000 14:54:11 -0800 (PST) (envelope-from behl@ucsb.edu) Received: from kahuna.ucsb.edu ([128.111.27.27]) by hub.ucsb.edu with esmtp id 12Xu0w-0006Jo-00; Wed, 22 Mar 2000 14:54:10 -0800 Date: Wed, 22 Mar 2000 14:54:09 -0800 (PST) From: Jeff Behl X-Sender: behl@localhost.localdomain To: Christian Jachmann Cc: "stable@freebsd.org" Subject: Re: 3.4-Stable crashes..(heavy diskio+networking) In-Reply-To: <38D948E1.50F3FC58@gigabell.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 We've had this type of error before and while it's normally defective memory we also once found the culprit to be a bad power supply. The power supply would "brown out", or loose power momentarily and then regain it quickly. I only discovered this being the problem after putting the machine on my desktop and observing it momentarily loose/regain power. Most times it would keep on chugging but once in a while you'd get a panic due to a page fault... Jeff On Wed, 22 Mar 2000, Christian Jachmann wrote: > > Hi, > > I'm running 3.4 Stable here, machine is a central newsfeed. > Machine is running INN 2.2.2 (latest Snapshot) > Network thrououtput is several hundred Gigabytes a Day. > We do have about 150 streaming connections on this site. > > It reboots about every 24 hours. > > Is it bad ram ? > or the temperature ? > Maybe someone give me a hint. > > > --------------------- > Debuging Information: > --------------------- > > Output of gdb: > > gdb -k kernel.14 vmcore.14 > > IdlePTD 2433024 > initial pcb at 1f0594 > panicstr: page fault > panic messages: > --- > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x12 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc0148ff0 > stack pointer = 0x10:0xda886dac > frame pointer = 0x10:0xda886dc8 > 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 = 2542 (innfeed) > interrupt mask = > trap number = 12 > panic: page fault > > syncing disks... > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x12 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc0148ff0 > stack pointer = 0x10:0xda8868dc > frame pointer = 0x10:0xda8868f8 > 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 = 2542 (innfeed) > interrupt mask = > trap number = 12 > panic: page fault > > dumping to dev 20401, offset 524288 > dump 768 767 766 765 764 763 762 761 760 759 758 757 756 755 754 753 752 > 751 750 749 748 747 746 745 > 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 > --- > #0 boot (howto=260) at ../../kern/kern_shutdown.c:285 > 285 dumppcb.pcb_cr3 = rcr3(); > > #0 boot (howto=260) at ../../kern/kern_shutdown.c:285 > #1 0xc0132b1d in panic (fmt=0xc01d78d2 "page fault") > at ../../kern/kern_shutdown.c:446 > #2 0xc01b66b2 in trap_fatal (frame=0xda8868a0, eva=18) > at ../../i386/i386/trap.c:942 > #3 0xc01b636b in trap_pfault (frame=0xda8868a0, usermode=0, eva=18) > at ../../i386/i386/trap.c:835 > #4 0xc01b5fca in trap (frame={tf_es = -1072234480, tf_ds = -981401584, > tf_edi = 0, tf_esi = 0, tf_ebp = -628594440, tf_isp = -628594488, > tf_ebx = 0, tf_edx = -2147483648, tf_ecx = 40, tf_eax = 40, > tf_trapno = 12, tf_err = 0, tf_eip = -1072394256, tf_cs = 8, > tf_eflags = 66118, tf_esp = 0, tf_ss = -1073610752}) > at ../../i386/i386/trap.c:437 > #5 0xc0148ff0 in m_copym (m=0x0, off0=0, len=46, wait=1) > at ../../kern/uipc_mbuf.c:433 > #6 0xc01747d2 in tcp_output (tp=0xd9e4ff00) at > ../../netinet/tcp_output.c:505 > #7 0xc0175931 in tcp_fasttimo () at ../../netinet/tcp_timer.c:106 > #8 0xc014883b in pffasttimo (arg=0x0) at ../../kern/uipc_domain.c:292 > #9 0xc0137332 in softclock () at ../../kern/kern_timeout.c:132 > #10 0xc01ad563 in doreti_swi () > #11 0xc015181f in getblk (vp=0xda7d69c0, blkno=1048720, size=8192, > slpflag=0, > slptimeo=0) at ../../kern/vfs_bio.c:1437 > #12 0xc015019d in bread (vp=0xda7d69c0, blkno=1048720, size=8192, > cred=0x0, > bpp=0xda886ae0) at ../../kern/vfs_bio.c:282 > #13 0xc01834d0 in ffs_update (vp=0xda863f80, waitfor=0) > at ../../ufs/ffs/ffs_inode.c:98 > #14 0xc0187e5f in ffs_fsync (ap=0xda886c5c) at > ../../ufs/ffs/ffs_vnops.c:258 > #15 0xc01977f2 in vm_object_page_clean (object=0xda83083c, start=0, > end=0, > flags=0) at vnode_if.h:499 > #16 0xc01585e5 in vfs_msync (mp=0xc58c5e00, flags=2) > at ../../kern/vfs_subr.c:2473 > #17 0xc0159518 in sync (p=0xc0204318, uap=0x0) at > ../../kern/vfs_syscalls.c:548 > #18 0xc01326c5 in boot (howto=256) at ../../kern/kern_shutdown.c:203 > #19 0xc0132b1d in panic (fmt=0xc01d78d2 "page fault") > at ../../kern/kern_shutdown.c:446 > #20 0xc01b66b2 in trap_fatal (frame=0xda886d70, eva=18) > at ../../i386/i386/trap.c:942 > #21 0xc01b636b in trap_pfault (frame=0xda886d70, usermode=0, eva=18) > at ../../i386/i386/trap.c:835 > #22 0xc01b5fca in trap (frame={tf_es = -980418544, tf_ds = -980418544, > tf_edi = 0, tf_esi = 0, tf_ebp = -628593208, tf_isp = -628593256, > tf_ebx = 0, tf_edx = 0, tf_ecx = 40, tf_eax = 40, tf_trapno = 12, > tf_err = 0, tf_eip = -1072394256, tf_cs = 8, tf_eflags = 66118, > tf_esp = 0, tf_ss = -1073610752}) at ../../i386/i386/trap.c:437 > #23 0xc0148ff0 in m_copym (m=0x0, off0=0, len=46, wait=1) > at ../../kern/uipc_mbuf.c:433 > #24 0xc01747d2 in tcp_output (tp=0xd9e4ff00) at > ../../netinet/tcp_output.c:505 > #25 0xc017608a in tcp_usr_send (so=0xd97e7f00, flags=0, m=0xc188b800, > nam=0x0, > control=0x0, p=0xda7da520) at ../../netinet/tcp_usrreq.c:395 > #26 0xc014aa8e in sosend (so=0xd97e7f00, addr=0x0, uio=0xda886f40, > top=0xc188b800, control=0x0, flags=0, p=0xda7da520) > at ../../kern/uipc_socket.c:530 > #27 0xc0140944 in soo_write (fp=0xc59c9f80, uio=0xda886f40, > cred=0xc58fbc80, > flags=0) at ../../kern/sys_socket.c:82 > #28 0xc013da55 in writev (p=0xda7da520, uap=0xda886f94) > at ../../kern/sys_generic.c:447 > #29 0xc01b690f in syscall (frame={tf_es = 134676519, tf_ds = > -1078001625, > tf_edi = 1, tf_esi = 1, tf_ebp = -1077946012, tf_isp = -628592668, > tf_ebx = 8388608, tf_edx = 134763136, tf_ecx = 134763136, tf_eax = > 121, > tf_trapno = 22, tf_err = 2, tf_eip = 671933924, tf_cs = 31, > tf_eflags = 514, tf_esp = -1077946056, tf_ss = 39}) > at ../../i386/i386/trap.c:1100 > #30 0xc01ac28c in Xint0x80_syscall () > #31 0x805246d in ?? () > > sysctl -a: > ---------- > ern.ostype: FreeBSD > kern.osrelease: 3.4-STABLE > kern.osrevision: 199506 > kern.version: FreeBSD 3.4-STABLE #0: Tue Mar 21 22:33:28 CET 2000 > root@newscore.gigabell.net:/usr/src/sys/compile/MY > > kern.maxvnodes: 56501 > kern.maxproc: 8212 > kern.maxfiles: 16424 > kern.argmax: 65536 > kern.securelevel: -1 > kern.hostname: newscore.gigabell.net > kern.hostid: 0 > kern.clockrate: { hz = 100, tick = 10000, tickadj = 5, profhz = 1024, > stathz = 128 } > kern.posix1version: 199009 > kern.ngroups: 16 > kern.job_control: 1 > kern.saved_ids: 0 > kern.boottime: { sec = 953741562, usec = 345570 } Wed Mar 22 17:12:42 > 2000 > kern.domainname: > kern.osreldate: 340001 > kern.bootfile: /kernel > kern.maxfilesperproc: 16424 > kern.maxprocperuid: 8211 > kern.dumpdev: { major = 4, minor = 131073 } > kern.ipc.maxsockbuf: 262144 > kern.ipc.sockbuf_waste_factor: 8 > kern.ipc.somaxconn: 128 > kern.ipc.max_linkhdr: 16 > kern.ipc.max_protohdr: 40 > kern.ipc.max_hdr: 56 > kern.ipc.max_datalen: 40 > kern.ipc.nmbclusters: 26112 > kern.ipc.maxsockets: 26112 > kern.dummy: 0 > kern.ps_strings: -1077944336 > kern.usrstack: -1077944320 > kern.logsigexit: 1 > kern.init_path: /sbin/init:/sbin/oinit:/sbin/init.bak:/stand/sysinstall > kern.module_path: /;/boot/;/modules/ > kern.acct_suspend: 2 > kern.acct_resume: 4 > kern.acct_chkfreq: 15 > kern.timecounter.method: 0 > kern.fast_vfork: 1 > kern.sugid_coredump: 0 > kern.corefile: %N.core > kern.quantum: 100000 > kern.ccpu: 1948 > kern.fscale: 2048 > kern.devstat.numdevs: 5 > kern.devstat.generation: 5 > kern.devstat.version: 3 > kern.consmute: 0 > vm.loadavg: { 0.48 0.45 0.46 } > vm.v_free_min: 1329 > vm.v_free_target: 4352 > vm.v_free_reserved: 365 > vm.v_inactive_target: 6528 > vm.v_cache_min: 4352 > vm.v_cache_max: 8704 > vm.v_pageout_free_min: 34 > vm.pageout_algorithm: 0 > vm.swap_enabled: 1 > vm.swap_idle_threshold1: 2 > vm.swap_idle_threshold2: 10 > vm.stats.sys.v_swtch: 25744685 > vm.stats.sys.v_trap: 22613584 > vm.stats.sys.v_syscall: 104406487 > vm.stats.sys.v_intr: 41945786 > vm.stats.sys.v_soft: 18841317 > vm.stats.vm.v_vm_faults: 9333924 > vm.stats.vm.v_cow_faults: 56013 > vm.stats.vm.v_cow_optim: 16775 > vm.stats.vm.v_zfod: 8412442 > vm.stats.vm.v_ozfod: 5240413 > vm.stats.vm.v_swapin: 0 > vm.stats.vm.v_swapout: 0 > vm.stats.vm.v_swappgsin: 0 > vm.stats.vm.v_swappgsout: 0 > vm.stats.vm.v_vnodein: 22365 > vm.stats.vm.v_vnodeout: 400767 > vm.stats.vm.v_vnodepgsin: 27144 > vm.stats.vm.v_vnodepgsout: 479341 > vm.stats.vm.v_intrans: 2823 > vm.stats.vm.v_reactivated: 2881 > vm.stats.vm.v_pdwakeups: 1673 > vm.stats.vm.v_pdpages: 6431353 > vm.stats.vm.v_dfree: 1165 > vm.stats.vm.v_pfree: 72864 > vm.stats.vm.v_tfree: 8578235 > vm.stats.vm.v_page_size: 4096 > vm.stats.vm.v_page_count: 193159 > vm.stats.vm.v_free_reserved: 365 > vm.stats.vm.v_free_target: 4352 > vm.stats.vm.v_free_min: 1329 > vm.stats.vm.v_free_count: 544 > vm.stats.vm.v_wire_count: 5717 > vm.stats.vm.v_active_count: 54885 > vm.stats.vm.v_inactive_target: 6528 > vm.stats.vm.v_inactive_count: 124409 > vm.stats.vm.v_cache_count: 7575 > vm.stats.vm.v_cache_min: 4352 > vm.stats.vm.v_cache_max: 8704 > vm.stats.vm.v_pageout_free_min: 34 > vm.stats.vm.v_interrupt_free_min: 2 > vm.stats.misc.zero_page_count: 374 > vm.stats.misc.cnt_prezero: 6271661 > vm.pageout_stats_max: 4352 > vm.pageout_full_stats_interval: 20 > vm.pageout_stats_interval: 5 > vm.pageout_stats_free_max: 5 > vm.swap_idle_enabled: 0 > vm.defer_swapspace_pageouts: 0 > vm.disable_swapspace_pageouts: 0 > vm.max_page_launder: 32 > vm.zone: > ITEM SIZE LIMIT USED FREE REQUESTS > > PIPE: 160, 0, 2, 100, 2507 > unpcb: 64, 0, 25, 103, 728 > ripcb: 96, 26112, 0, 42, 0 > tcpcb: 288, 26112, 131, 65, 2991 > udpcb: 96, 26112, 5, 79, 921 > unpcb: 64, 0, 0, 0, 0 > socket: 160, 26112, 161, 89, 4650 > AIOLIO: 704, 0, 0, 0, 0 > AIOL: 64, 0, 0, 0, 0 > AIOCB: 128, 0, 0, 0, 0 > AIOP: 32, 0, 0, 0, 0 > AIO: 96, 0, 0, 0, 0 > VNODE: 192, 0, 410, 120, 405 > NAMEI: 1024, 0, 0, 16, 110867 > VMSPACE: 192, 0, 22, 42, 1825 > PROC: 352, 0, 25, 33, 1828 > DP fakepg: 64, 0, 0, 0, 0 > PV ENTRY: 28, 2035610, 64396, 132209, 10097287 > MAP ENTRY: 40, 0, 664, 178, 1967785 > KMAP ENTRY: 40, 48417, 51, 179, 1616 > MAP: 100, 0, 7, 3, 7 > VM OBJECT: 124, 0, 604, 81, 32505 > vm.zone_kmem_pages: 28 > vm.zone_kmem_kvaspace: 70139904 > vm.zone_kern_pages: 63 > vfs.numdirtybuffers: 52 > vfs.lodirtybuffers: 139 > vfs.hidirtybuffers: 279 > vfs.numfreebuffers: 2026 > vfs.lofreebuffers: 120 > vfs.hifreebuffers: 240 > vfs.maxbufspace: 8544256 > vfs.bufspace: 8544256 > vfs.maxvmiobufspace: 5696170 > vfs.vmiospace: 8510464 > vfs.maxmallocbufspace: 427212 > vfs.bufmallocspace: 13312 > vfs.kvafreespace: 311296 > vfs.cache.numneg: 19 > vfs.cache.numcache: 306 > vfs.cache.numcalls: 371609 > vfs.cache.dothits: 352 > vfs.cache.dotdothits: 85 > vfs.cache.numchecks: 386235 > vfs.cache.nummiss: 10008 > vfs.cache.nummisszap: 9212 > vfs.cache.numposzaps: 3417 > vfs.cache.numposhits: 318935 > vfs.cache.numnegzaps: 2760 > vfs.cache.numneghits: 26840 > vfs.cache.maxaliases: 4 > vfs.cache.numcwdcalls: 136 > vfs.cache.numcwdfail1: 0 > vfs.cache.numcwdfail2: 0 > vfs.cache.numcwdfail3: 0 > vfs.cache.numcwdfail4: 0 > vfs.cache.numcwdfound: 136 > vfs.mod0: 0 > vfs.mod1: 0 > vfs.usermount: 0 > vfs.aio.max_aio_per_proc: 32 > vfs.aio.max_aio_queue_per_proc: 256 > vfs.aio.max_aio_procs: 32 > vfs.aio.num_aio_procs: 0 > vfs.aio.num_queue_count: 0 > vfs.aio.max_aio_queue: 1024 > vfs.aio.target_aio_procs: 0 > vfs.aio.max_buf_aio: 16 > vfs.aio.num_buf_aio: 0 > vfs.aio.aiod_lifetime: 3000 > vfs.aio.aiod_timeout: 1000 > vfs.ffs.doreallocblks: 1 > vfs.ffs.doasyncfree: 1 > net.local.stream.sendspace: 8192 > net.local.stream.recvspace: 8192 > net.local.dgram.maxdgram: 2048 > net.local.dgram.recvspace: 4096 > net.local.inflight: 0 > net.inet.ip.portrange.lowfirst: 1023 > net.inet.ip.portrange.lowlast: 600 > net.inet.ip.portrange.first: 1024 > net.inet.ip.portrange.last: 5000 > net.inet.ip.portrange.hifirst: 49152 > net.inet.ip.portrange.hilast: 65535 > net.inet.ip.forwarding: 0 > net.inet.ip.redirect: 1 > net.inet.ip.ttl: 64 > net.inet.ip.rtexpire: 3600 > net.inet.ip.rtminexpire: 10 > net.inet.ip.rtmaxcache: 128 > net.inet.ip.sourceroute: 0 > net.inet.ip.intr_queue_maxlen: 50 > net.inet.ip.intr_queue_drops: 0 > net.inet.ip.accept_sourceroute: 0 > net.inet.ip.fastforwarding: 0 > net.inet.ip.subnets_are_local: 0 > net.inet.icmp.maskrepl: 0 > net.inet.icmp.icmplim: -1 > net.inet.icmp.drop_redirect: 0 > net.inet.icmp.log_redirect: 0 > net.inet.icmp.bmcastecho: 0 > net.inet.tcp.rfc1323: 0 > net.inet.tcp.rfc1644: 0 > net.inet.tcp.mssdflt: 512 > net.inet.tcp.rttdflt: 3 > net.inet.tcp.keepidle: 14400 > net.inet.tcp.keepintvl: 150 > net.inet.tcp.sendspace: 16384 > net.inet.tcp.recvspace: 16384 > net.inet.tcp.keepinit: 150 > net.inet.tcp.log_in_vain: 0 > net.inet.tcp.delayed_ack: 1 > net.inet.tcp.pcbcount: 131 > net.inet.tcp.always_keepalive: 1 > net.inet.udp.checksum: 1 > net.inet.udp.maxdgram: 9216 > net.inet.udp.recvspace: 41600 > net.inet.udp.log_in_vain: 0 > net.inet.raw.maxdgram: 8192 > net.inet.raw.recvspace: 8192 > net.link.generic.system.ifcount: 2 > net.link.ether.inet.prune_intvl: 300 > net.link.ether.inet.max_age: 1200 > net.link.ether.inet.host_down_time: 20 > net.link.ether.inet.maxtries: 5 > net.link.ether.inet.useloopback: 1 > net.link.ether.inet.proxyall: 0 > debug.enter_debugger: > debug.elf_trace: 0 > debug.fdexpand: 16 > debug.debugger_on_panic: 0 > debug.ttydebug: 0 > debug.nchash: 65535 > debug.ncnegfactor: 16 > debug.numneg: 19 > debug.numcache: 306 > debug.vfscache: 1 > debug.vnsize: 168 > debug.ncsize: 36 > debug.numvnodes: 410 > debug.wantfreevnodes: 25 > debug.freevnodes: 125 > debug.busyprt: 0 > debug.disablecwd: 0 > debug.bpf_bufsize: 4096 > debug.ncr_debug: 0 > hw.machine: i386 > hw.model: Pentium III > hw.ncpu: 1 > hw.byteorder: 1234 > hw.physmem: 803508224 > hw.usermem: 780095488 > hw.pagesize: 4096 > hw.floatingpoint: 1 > hw.machine_arch: i386 > hw.availpages: 196009 > machdep.consdev: { major = 0, minor = 0 } > machdep.adjkerntz: 0 > machdep.disable_rtc_set: 0 > machdep.wall_cmos_clock: 0 > machdep.do_dump: 1 > machdep.ispc98: 0 > machdep.msgbuf: > machdep.msgbuf_clear: 0 > machdep.i8254_freq: 1193182 > machdep.tsc_freq: 451024885 > machdep.conspeed: 9600 > user.cs_path: /usr/bin:/bin:/usr/sbin:/sbin: > user.bc_base_max: 99 > user.bc_dim_max: 2048 > user.bc_scale_max: 99 > user.bc_string_max: 1000 > user.coll_weights_max: 0 > user.expr_nest_max: 32 > user.line_max: 2048 > user.re_dup_max: 255 > user.posix2_version: 199212 > user.posix2_c_bind: 0 > user.posix2_c_dev: 0 > user.posix2_char_term: 0 > user.posix2_fort_dev: 0 > user.posix2_fort_run: 0 > user.posix2_localedef: 0 > user.posix2_sw_dev: 0 > user.posix2_upe: 0 > user.stream_max: 20 > user.tzname_max: 255 > p1003_1b.asynchronous_io: 0 > p1003_1b.mapped_files: 0 > p1003_1b.memlock: 0 > p1003_1b.memlock_range: 0 > p1003_1b.memory_protection: 0 > p1003_1b.message_passing: 0 > p1003_1b.prioritized_io: 0 > p1003_1b.priority_scheduling: 0 > p1003_1b.realtime_signals: 0 > p1003_1b.semaphores: 0 > p1003_1b.fsync: 0 > p1003_1b.shared_memory_objects: 0 > p1003_1b.synchronized_io: 0 > p1003_1b.timers: 0 > p1003_1b.aio_listio_max: 0 > p1003_1b.aio_max: 0 > p1003_1b.aio_prio_delta_max: 0 > p1003_1b.delaytimer_max: 0 > p1003_1b.mq_open_max: 0 > p1003_1b.pagesize: 4096 > p1003_1b.rtsig_max: 0 > p1003_1b.sem_nsems_max: 0 > p1003_1b.sem_value_max: 0 > p1003_1b.sigqueue_max: 0 > p1003_1b.timer_max: 0 > > here is dmesg: > -------------- > Copyright (c) 1992-1999 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights > reserved. > FreeBSD 3.4-STABLE #0: Tue Mar 21 22:33:28 CET 2000 > root@newscore.gigabell.net:/usr/src/sys/compile/MY > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 451024885 Hz > CPU: Pentium III (451.02-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x673 Stepping = 3 > > Features=0x383f9ff> > real memory = 805306368 (786432K bytes) > avail memory = 780439552 (762148K bytes) > Preloaded elf kernel "kernel" at 0xc0240000. > Pentium Pro MTRR support enabled > Probing for devices on PCI bus 0: > chip0: rev 0x03 on pci0.0.0 > chip1: rev 0x03 on pci0.1.0 > chip2: rev 0x02 on pci0.4.0 > chip3: rev 0x02 on pci0.4.3 > fxp0: rev 0x08 int a irq 12 on > pci0.9.0 > fxp0: Ethernet address 00:90:27:9d:1f:1f > ncr0: rev 0x02 int a irq 10 on pci0.11.0 > Probing for devices on PCI bus 1: > vga0: rev 0x5c int a irq 11 on > pci1.0.0 > Probing for devices on the ISA bus: > sc0 on isa > sc0: VGA color <16 virtual consoles, flags=0x0> > atkbdc0 at 0x60-0x6f on motherboard > atkbd0 irq 1 on isa > sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > sio0: type 16550A > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: FIFO enabled, 8 bytes threshold > fd0: 1.44MB 3.5in > vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa > npx0 on motherboard > npx0: INT 16 interface > Waiting 3 seconds for SCSI devices to settle > changing root device to da0s1a > da0 at ncr0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing > Enabled > da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) > da1 at ncr0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing > Enabled > da1: 34732MB (71132960 512 byte sectors: 255H 63S/T 4427C) > WARNING: / was not properly dismounted > Start pid=2 > Start pid=3 > Start pid=4 > > > Kernel config: > -------------- > machine "i386" > cpu "I686_CPU" > ident MY > maxusers 512 > options INET #InterNETworking > options FFS #Berkeley Fast Filesystem > options FFS_ROOT #FFS usable as root device [keep > this!] > options MFS #Memory Filesystem > options PROCFS #Process filesystem > options "COMPAT_43" #Compatible with BSD 4.3 [KEEP > THIS!] > options SCSI_DELAY=3000 #Be pessimistic about Joe SCSI > device > options FAILSAFE #Be conservative > options KTRACE #ktrace(1) syscall trace support > options SYSVSHM #SYSV-style shared memory > options SYSVMSG #SYSV-style message queues > options SYSVSEM #SYSV-style semaphores > > config kernel root on da0 > > controller isa0 > controller pci0 > > controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 > disk fd0 at fdc0 drive 0 > > controller ncr0 # NCR/Symbios Logic > controller scbus0 # SCSI bus (required) > device da0 # Direct Access (disks) > device pass0 # Passthrough device (direct SCSI) > > controller atkbdc0 at isa? port IO_KBD tty > device atkbd0 at isa? tty irq 1 > device vga0 at isa? port ? conflicts > device sc0 at isa? tty > > device npx0 at isa? port IO_NPX irq 13 > > device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 > device sio1 at isa? port "IO_COM2" tty irq 3 > > > device fxp0 # Intel EtherExpress PRO/100B (82557, > 82558) > > pseudo-device loop # Network loopback > pseudo-device ether # Ethernet support > pseudo-device pty 16 # Pseudo-ttys (telnet etc) > pseudo-device bpfilter 4 #Berkeley packet filter > > options DDB > options DDB_UNATTENDED > options DIAGNOSTIC > > options NMBCLUSTERS=26112 > > ---------------------------------- > > > BYe > -- > Christian Jachmann > GIGABELL AG - Technik > ++49 69 17084-0 > > > 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 Mar 22 14:55:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.uunet.ca (mail1.uunet.ca [209.167.141.3]) by hub.freebsd.org (Postfix) with ESMTP id 6C74A37C296 for ; Wed, 22 Mar 2000 14:55:29 -0800 (PST) (envelope-from matt@ARPA.MAIL.NET) Received: from epsilon.lucida.qc.ca ([216.95.146.6]) by mail1.uunet.ca with ESMTP id <146289-8123>; Wed, 22 Mar 2000 17:55:27 -0500 Date: Wed, 22 Mar 2000 17:55:26 -0500 From: Matt Heckaman X-Sender: matt@epsilon.lucida.qc.ca To: Christian Jachmann Cc: "stable@freebsd.org" Subject: Re: 3.4-Stable crashes..(heavy diskio+networking) In-Reply-To: <38D94C33.F7EE5A89@gigabell.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 Wed, 22 Mar 2000, Christian Jachmann wrote: [...] : Yes,I rised it several weeks ago, : : root@newscore>netstat -m : 569/1984 mbufs in use: : 347 mbufs allocated to data : 222 mbufs allocated to packet headers : 214/714/26112 mbuf clusters in use (current/peak/max) : 1676 Kbytes allocated to network (29% in use) : 0 requests for memory denied : 0 requests for memory delayed : 0 calls to protocol drain routines : : looks not so bad, or ? : : But system still crashes. : : BYe : -- : Christian Jachmann : Gigabell AG - Technik : ++49 69 17084-0 Looks good to me, though if you have expierenced high network bursts, that could be blown over, I've blown 32k on 10Mbit under a heavy dos, which I don't think would be out of the realm of possibility, it's my understanding that news servers are heavy on the bandwidth, yes? Could also be a file descriptor problem, though that seems less likely to me. Do you see a panic or does it just reboot without that? Are you able to obtain a kernel dump should a panic be the case? Matt -- Matt Heckaman [matt@arpa.mail.net|matt@relic.net] [Please do not send me] !Powered by FreeBSD/x86! [http://www.freebsd.org] [any SPAM (UCE) e-mail] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 15: 1:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3EDEB37C5AA for ; Wed, 22 Mar 2000 15:01:16 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA30223; Wed, 22 Mar 2000 16:01:11 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA34410; Wed, 22 Mar 2000 16:01:10 -0700 (MST) Message-Id: <200003222301.QAA34410@harmony.village.org> To: Vivek Khera Subject: Re: "dangerously dedicated" Cc: stable@FreeBSD.ORG In-reply-to: Your message of "Wed, 22 Mar 2000 10:06:44 EST." <14552.57732.739752.665443@onceler.kcilink.com> References: <14552.57732.739752.665443@onceler.kcilink.com> <4.3.2.20000321160347.00ad9b20@207.227.119.2> <38D50DBC.88FA8E4D@glue.umd.edu> <38D3AB72.366D851D@glue.umd.edu> <200003152159.OAA89926@harmony.village.org> <38D03E64.3D17FC34@glue.umd.edu> <200003190433.VAA04863@harmony.village.org> <200003212255.PAA26291@harmony.village.org> Date: Wed, 22 Mar 2000 16:01:10 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14552.57732.739752.665443@onceler.kcilink.com> Vivek Khera writes: : Why is using /dev/da0a stupid? FreeBSD is the only system I've : encountered that totally locks up (during a 3.3-RELEASE install from : CD) when there is no fdisk disk label. Is that why it is stupid? I didn't say that using da0a is stupid. I said using dangerously dedicated mode is stupid. Based on the number of times I've shot myself in the foot trying to use dangaerously dedicated devices over the years, I'll never use them again. : BSD/OS and Linux (RedHat 6.1) both deal with the lack of an fdisk disk : label just fine, and BSD/OS doesn't even require one, letting you use : the direct unix partitioning scheme. I much prefer it that way as it : just makes sense on a dedicated box, which is what all of mine are. FreeBSD lets you do this as well. Are you sure that Linux doesn't require fdisk disks? Linux/i386 doesn't have another form of disk partitioning. You always use fdisk labels. And this goes back to at least 0.98p14 or so. Of course, I've not tried any linux newer than 2.1. I have 0 experience with BSD/OS. I've just had bad luck with Dangerously Dedicated devices over the years. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 15: 2:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay.ipf.net (relay.gigabell.net [195.211.211.23]) by hub.freebsd.org (Postfix) with SMTP id 7AEFA37B793 for ; Wed, 22 Mar 2000 15:02:44 -0800 (PST) (envelope-from jachmann@gigabell.net) Received: (qmail 90602 invoked from network); 22 Mar 2000 23:02:41 -0000 Received: from habbib.bauernstand.org (HELO gigabell.net) (195.88.64.7) by relay.gigabell.net with SMTP; 22 Mar 2000 23:02:41 -0000 Message-ID: <38D9510F.214590D5@gigabell.net> Date: Thu, 23 Mar 2000 00:02:39 +0100 From: Christian Jachmann Organization: Gigabell AG X-Mailer: Mozilla 4.07 [en] (X11; I; Linux 2.2.2 i586) MIME-Version: 1.0 To: Matt Heckaman Cc: "stable@freebsd.org" Subject: Re: 3.4-Stable crashes..(heavy diskio+networking) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Heckaman wrote: > > On Wed, 22 Mar 2000, Christian Jachmann wrote: > [...] > : Yes,I rised it several weeks ago, > : > : root@newscore>netstat -m > : 569/1984 mbufs in use: > : 347 mbufs allocated to data > : 222 mbufs allocated to packet headers > : 214/714/26112 mbuf clusters in use (current/peak/max) > : 1676 Kbytes allocated to network (29% in use) > : 0 requests for memory denied > : 0 requests for memory delayed > : 0 calls to protocol drain routines > : > : looks not so bad, or ? > : > : But system still crashes. > : > : BYe > : -- > : Christian Jachmann > : Gigabell AG - Technik > : ++49 69 17084-0 > > Looks good to me, though if you have expierenced high network bursts, that > could be blown over, I've blown 32k on 10Mbit under a heavy dos, which I > don't think would be out of the realm of possibility, it's my understanding > that news servers are heavy on the bandwidth, yes? OK, I rised it again -> 128K lets wait a night and see whats happen. > Could also be a file > descriptor problem, though that seems less likely to me. Do you see a panic > or does it just reboot without that? Are you able to obtain a kernel dump > should a panic be the case? Yes I've got a dump here. look at my first eMail, it should contain all the necessary data. BYe -- Christian Jachmann Gigabell AG - Technik ++49 69 17084-0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 15: 2:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3C2DE37C398 for ; Wed, 22 Mar 2000 15:02:48 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA30231; Wed, 22 Mar 2000 16:02:43 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA34431; Wed, 22 Mar 2000 16:02:42 -0700 (MST) Message-Id: <200003222302.QAA34431@harmony.village.org> To: "J. W. Ballantine" Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions [Failure] Cc: freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Wed, 22 Mar 2000 10:32:20 EST." <200003221532.KAA10998@akiva.homer.att.com> References: <200003221532.KAA10998@akiva.homer.att.com> Date: Wed, 22 Mar 2000 16:02:42 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003221532.KAA10998@akiva.homer.att.com> "J. W. Ballantine" writes: : I then shutdown now to single user mode, cd to /usr/src and : do ``make -DNOINFO installworld''. This starts and continues to /bin/test : where it fails due to a kernel failure. ??? : When I try to reboot the system, with the RELENG_4 kernel I get: : / not unmounted cleanly, run fsck and reboot. : I go into single user mode and run fsck ; fsck -p ; fsck /dev/da0s1a : and a few sync's thrown in just for good luck, but still the same error. What's the error? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 15: 4:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id AF59637C327 for ; Wed, 22 Mar 2000 15:04:24 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA30240; Wed, 22 Mar 2000 16:04:19 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA34449; Wed, 22 Mar 2000 16:04:19 -0700 (MST) Message-Id: <200003222304.QAA34449@harmony.village.org> To: David Murphy Subject: Re: How to actually make a difference (Re: dot-0 releases) Cc: stable@FreeBSD.ORG In-reply-to: Your message of "Wed, 22 Mar 2000 17:19:57 GMT." <20000322171957.L48595@enigma.redbrick.dcu.ie> References: <20000322171957.L48595@enigma.redbrick.dcu.ie> <20000322165223.K48595@enigma.redbrick.dcu.ie> Date: Wed, 22 Mar 2000 16:04:19 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What's missing from the current -stable UPDATING file? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 15: 5:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from spyregroup.com (ns1.spyregroup.com [63.86.70.82]) by hub.freebsd.org (Postfix) with SMTP id 960AF37B64F for ; Wed, 22 Mar 2000 15:05:05 -0800 (PST) (envelope-from damascus@eden.rutgers.edu) Received: (qmail 1016 invoked from network); 22 Mar 2000 18:05:03 -0000 Received: from damascus.dorm.rutgers.edu (HELO damascus) (165.230.0.68) by ns1.spyregroup.com with SMTP; 22 Mar 2000 18:05:03 -0000 Message-Id: <4.2.2.20000322175820.00e0e8c0@email.eden.rutgers.edu> X-Sender: damascus@email.eden.rutgers.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Wed, 22 Mar 2000 18:04:48 -0500 To: Christian Jachmann , "stable@freebsd.org" From: Carroll Kong Subject: Re: 3.4-Stable crashes..(heavy diskio+networking) In-Reply-To: <38D948E1.50F3FC58@gigabell.net> 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:27 PM 3/22/00 +0100, Christian Jachmann wrote: >Hi, > >I'm running 3.4 Stable here, machine is a central newsfeed. >Machine is running INN 2.2.2 (latest Snapshot) >Network thrououtput is several hundred Gigabytes a Day. >We do have about 150 streaming connections on this site. > >It reboots about every 24 hours. > >Is it bad ram ? >or the temperature ? >Maybe someone give me a hint. Ok. Your Maxusers seems a bit high. However, I have heard from several people (it was not really too decisive even after looking at the archives) that this is ok. How long has the system been working for? Is this problem just recent? Did it just occur after you inserted some new ram. The error was a page fault. My guess is ram, or swap disk. (I could not tell if you were swapping or not). What brand name RAM? How old is the ram? My guess is heavily on the ram. I highly doubt if the program would die that it would die like this. It would most likely die on it's own without rebooting the whole machine. (Unless maxusers =512 has put you over the hardware limit somewhere, although I am not sure). -Carroll Kong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 15:18:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay.ipf.net (relay.gigabell.net [195.211.211.23]) by hub.freebsd.org (Postfix) with SMTP id 64DBF37B586 for ; Wed, 22 Mar 2000 15:18:24 -0800 (PST) (envelope-from jachmann@gigabell.net) Received: (qmail 94383 invoked from network); 22 Mar 2000 23:18:22 -0000 Received: from habbib.bauernstand.org (HELO gigabell.net) (195.88.64.7) by relay.gigabell.net with SMTP; 22 Mar 2000 23:18:22 -0000 Message-ID: <38D954BC.4D49C9FA@gigabell.net> Date: Thu, 23 Mar 2000 00:18:20 +0100 From: Christian Jachmann Organization: Gigabell AG X-Mailer: Mozilla 4.07 [en] (X11; I; Linux 2.2.2 i586) MIME-Version: 1.0 To: Carroll Kong Cc: "stable@freebsd.org" Subject: Re: 3.4-Stable crashes..(heavy diskio+networking) References: <4.2.2.20000322175820.00e0e8c0@email.eden.rutgers.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Carroll Kong wrote: > > At 11:27 PM 3/22/00 +0100, Christian Jachmann wrote: > >Hi, > > > >I'm running 3.4 Stable here, machine is a central newsfeed. > >Machine is running INN 2.2.2 (latest Snapshot) > >Network thrououtput is several hundred Gigabytes a Day. > >We do have about 150 streaming connections on this site. > > > >It reboots about every 24 hours. > > > >Is it bad ram ? > >or the temperature ? > >Maybe someone give me a hint. > > Ok. Your Maxusers seems a bit high. However, I have heard from several > people (it was not really too decisive even after looking at the archives) > that this is ok. How long has the system been working for? Is this It has been working in 2.2.* Release for about half a year, whithout any problem. After upgrading to 3.* (now 3.4) we got those crashes.... > problem just recent? Did it just occur after you inserted some new > ram. The error was a page fault. My guess is ram, or swap disk. (I could > not tell if you were swapping or not). What brand name RAM? How old is > the ram? My guess is heavily on the ram. I highly doubt if the program System is not swaping. I'll change the ram soon. But something interesting is in the gdb output : Fatal trap 12: page fault while in kernel mode fault virtual address = 0x12 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0148ff0 stack pointer = 0x10:0xda886dac frame pointer = 0x10:0xda886dc8 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 = 2542 (innfeed) interrupt mask = trap number = 12 panic: page fault syncing disks... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x12 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0148ff0 stack pointer = 0x10:0xda8868dc frame pointer = 0x10:0xda8868f8 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 = 2542 (innfeed) interrupt mask = trap number = 12 panic: page fault --- looks like I got two page faults. same is also in the backtrace: #0 boot (howto=260) at ../../kern/kern_shutdown.c:285 #1 0xc0132b1d in panic (fmt=0xc01d78d2 "page fault") at ../../kern/kern_shutdown.c:446 #2 0xc01b66b2 in trap_fatal (frame=0xda8868a0, eva=18) at ../../i386/i386/trap.c:942 #3 0xc01b636b in trap_pfault (frame=0xda8868a0, usermode=0, eva=18) at ../../i386/i386/trap.c:835 #4 0xc01b5fca in trap (frame={tf_es = -1072234480, tf_ds = -981401584, tf_edi = 0, tf_esi = 0, tf_ebp = -628594440, tf_isp = -628594488, tf_ebx = 0, tf_edx = -2147483648, tf_ecx = 40, tf_eax = 40, tf_trapno = 12, tf_err = 0, tf_eip = -1072394256, tf_cs = 8, tf_eflags = 66118, tf_esp = 0, tf_ss = -1073610752}) at ../../i386/i386/trap.c:437 #5 0xc0148ff0 in m_copym (m=0x0, off0=0, len=46, wait=1) at ../../kern/uipc_mbuf.c:433 #6 0xc01747d2 in tcp_output (tp=0xd9e4ff00) at ../../netinet/tcp_output.c:505 and somewhat before: #17 0xc0159518 in sync (p=0xc0204318, uap=0x0) at ../../kern/vfs_syscalls.c:548 #18 0xc01326c5 in boot (howto=256) at ../../kern/kern_shutdown.c:203 #19 0xc0132b1d in panic (fmt=0xc01d78d2 "page fault") at ../../kern/kern_shutdown.c:446 #20 0xc01b66b2 in trap_fatal (frame=0xda886d70, eva=18) at ../../i386/i386/trap.c:942 #21 0xc01b636b in trap_pfault (frame=0xda886d70, usermode=0, eva=18) at ../../i386/i386/trap.c:835 #22 0xc01b5fca in trap (frame={tf_es = -980418544, tf_ds = -980418544, tf_edi = 0, tf_esi = 0, tf_ebp = -628593208, tf_isp = -628593256, tf_ebx = 0, tf_edx = 0, tf_ecx = 40, tf_eax = 40, tf_trapno = 12, tf_err = 0, tf_eip = -1072394256, tf_cs = 8, tf_eflags = 66118, tf_esp = 0, tf_ss = -1073610752}) at ../../i386/i386/trap.c:437 #23 0xc0148ff0 in m_copym (m=0x0, off0=0, len=46, wait=1) at ../../kern/uipc_mbuf.c:433 #24 0xc01747d2 in tcp_output (tp=0xd9e4ff00) at ../../netinet/tcp_output.c:505 #25 0xc017608a in tcp_usr_send (so=0xd97e7f00, flags=0, m=0xc188b800, nam=0x0, a second page fault.... Strage ? BYe -- Christian Jachmann Gigabell AG - Technik ++49 69 17084-0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 15:26:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from student-mailhub.dcu.ie (ns.dcu.ie [136.206.1.3]) by hub.freebsd.org (Postfix) with ESMTP id A477037C33C for ; Wed, 22 Mar 2000 15:26:34 -0800 (PST) (envelope-from drjolt@redbrick.dcu.ie) Received: from enigma.redbrick.dcu.ie (postfix@enigma.redbrick.dcu.ie [136.206.15.5]) by student-mailhub.dcu.ie (8.9.3/8.9.3/893-FD) with ESMTP id XAA01450 for ; Wed, 22 Mar 2000 23:26:30 GMT Received: by enigma.redbrick.dcu.ie (Postfix, from userid 2034) id 083E37C8D; Wed, 22 Mar 2000 23:24:40 +0000 (GMT) Date: Wed, 22 Mar 2000 23:24:40 +0000 From: David Murphy To: stable@FreeBSD.ORG Subject: Re: How to actually make a difference (Re: dot-0 releases) Message-ID: <20000322232440.B52554@enigma.redbrick.dcu.ie> References: <20000322171957.L48595@enigma.redbrick.dcu.ie> <20000322165223.K48595@enigma.redbrick.dcu.ie> <20000322171957.L48595@enigma.redbrick.dcu.ie> <200003222304.QAA34449@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003222304.QAA34449@harmony.village.org>; from imp@village.org on Wed, Mar 22, 2000 at 04:04:19PM -0700 X-no-archive: yes Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting <200003222304.QAA34449@harmony.village.org> by Warner Losh : > What's missing from the current -stable UPDATING file? Nothing, it's got what's needed now. The only thing I'd say is unresolved is whether it should warn people off updating via source, or not, depending on what people want to recommend... -- When asked if it is true that he uses his wheelchair as a weapon he will reply: "That's a malicious rumour. I'll run over anyone who repeats it." Stephen Hawking - [http://www.smh.com.au/news/0001/07/features/features1.html] David Murphy - For PGP public key, send mail with Subject: send-pgp-key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 15:30:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id 1517537C320 for ; Wed, 22 Mar 2000 15:30:20 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 5F40AE897; Wed, 22 Mar 2000 18:30:19 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id SAA30347; Wed, 22 Mar 2000 18:30:19 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14553.22411.265795.429126@onceler.kcilink.com> Date: Wed, 22 Mar 2000 18:30:19 -0500 (EST) To: Warner Losh Cc: stable@FreeBSD.ORG Subject: Re: "dangerously dedicated" In-Reply-To: <200003222301.QAA34410@harmony.village.org> References: <14552.57732.739752.665443@onceler.kcilink.com> <4.3.2.20000321160347.00ad9b20@207.227.119.2> <38D50DBC.88FA8E4D@glue.umd.edu> <38D3AB72.366D851D@glue.umd.edu> <200003152159.OAA89926@harmony.village.org> <38D03E64.3D17FC34@glue.umd.edu> <200003190433.VAA04863@harmony.village.org> <200003212255.PAA26291@harmony.village.org> <200003222301.QAA34410@harmony.village.org> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "WL" == Warner Losh writes: WL> I didn't say that using da0a is stupid. I said using dangerously WL> dedicated mode is stupid. Based on the number of times I've shot I guess I don't see how to use, eg, da0a without being "dangerously dedicated". When I did my install of FBSD 3.3, the partitioning process asked if I was sharing the disk or not. I said no, so it took over the entire disk, but I still get the long-sliced names like /dev/wd0s1a rather than the /dev/wd0a I'd expect since there is only one slice on the whole disk. My zip drive uses /dev/da0a after I did a newfs on it, though. WL> FreeBSD lets you do this as well. Are you sure that Linux doesn't WL> require fdisk disks? Linux/i386 doesn't have another form of disk Linux requires it to run, but doesn't hang forever if it doesn't exist. FreeBSD is the only system I've encountered so far that will lock up (ie, does not respond to any keyboard requests or terminate its probe) when scanning a disk without an FDISK table. I needed to use freedos to add one to this particular drive. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 PGP & MIME spoken here http://www.kciLink.com/home/khera/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 15:35:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89]) by hub.freebsd.org (Postfix) with ESMTP id C43CC37C28D for ; Wed, 22 Mar 2000 15:35:17 -0800 (PST) (envelope-from forrestc@workhorse.iMach.com) Received: from localhost (forrestc@localhost) by workhorse.iMach.com (8.9.3/8.9.3) with ESMTP id QAA12090; Wed, 22 Mar 2000 16:30:11 -0700 (MST) Date: Wed, 22 Mar 2000 16:30:07 -0700 (MST) From: "Forrest W. Christian" To: Christian Jachmann Cc: Carroll Kong , "stable@freebsd.org" Subject: Off-topic News: WAS: Re: 3.4-Stable crashes..(heavy diskio+networking) In-Reply-To: <38D954BC.4D49C9FA@gigabell.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 Thu, 23 Mar 2000, Christian Jachmann wrote: > > >I'm running 3.4 Stable here, machine is a central newsfeed. > > >Machine is running INN 2.2.2 (latest Snapshot) > > >Network thrououtput is several hundred Gigabytes a Day. > > >We do have about 150 streaming connections on this site. I know this doesn't solve your problem but have you looked at the highwind products (Typhoon and Cyclone/Breeze)? See http://bcandid.com/products/index.html Although I haven't run a news server for a while now, when I did, these products saved us literally hundreds if not thousands of dollars of hardware. We went from a load average of 10+ on a $10,000 Sparc to <.1 on the same hardware switching from INN to cyclone. It looks like INN has implemented some of the functionality which make these products sooooo fast, but it might still be worth a look. FWIW, the box "average uptime" also went from typically a day or so with INN to weeks or months with cyclone. The OS would croak about once a day with INN, quite frequently requiring a manual fsck -y. - Forrest W. Christian (forrestc@imach.com) KD7EHZ ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 15:36:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from field.videotron.net (field.videotron.net [205.151.222.108]) by hub.freebsd.org (Postfix) with ESMTP id 70CAD37B596 for ; Wed, 22 Mar 2000 15:36:35 -0800 (PST) (envelope-from luc_m@videotron.ca) Received: from videotron.ca ([24.200.211.63]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FRU00G2GK2OUO@field.videotron.net> for stable@freebsd.org; Wed, 22 Mar 2000 18:32:54 -0500 (EST) Date: Wed, 22 Mar 2000 18:32:22 -0500 From: Luc Morin Subject: Re: HP CD-R problems in 4.0-STABLE To: Jens Fallesen , stable@freebsd.org Message-id: <38D95806.F925D5C0@videotron.ca> MIME-version: 1.0 X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-STABLE i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en References: <38D90474.83554A30@fallesen.dk> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jens Fallesen wrote: > Hi there, > > In my PC I have the following configuration: > > 1st IDE, 1st drive: Hard disk (ad0) > 1st IDE, 2nd drive: ZIP drive (afd0) > 2nd IDE, 1st drive: DVD-ROM (acd0) > 2nd IDE, 2nd drive: CD-RW (acd1) > > This worked fine with 3.4-STABLE but after an otherwise succesful > upgrade to 4.0-STABLE (last cvsup was Tuesday at approximately 1700 > UTC) I have been unable to use my CD-RW drive. > > When I look into /var/log/messages I get this: > > Mar 22 18:19:44 dilbert /kernel: ad0: 12893MB > [26197/16/63] at ata0-master using UDMA33 > Mar 22 18:19:44 dilbert /kernel: afd0: 96MB > [96/64/32] at ata0-slave using PIO3 > Mar 22 18:19:44 dilbert /kernel: acd0: DVD-ROM 0110> at ata1-master using PIO4 > Mar 22 18:19:44 dilbert /kernel: acd1: CD-RW CD-Writer Plus 8100> at ata1-slave using PIO3 > Mar 22 18:19:44 dilbert /kernel: Mounting root from ufs:/dev/ad0s2a > > (The same info is in dmesg.) > > The drive is there, so is the device (made several times using > ./MAKEDEV acd1). However, when I try to mount the drives: > > dilbert:/home/jf# mount -t cd9660 /dev/acd0c /cdrom > dilbert:/home/jf# mount -t cd9660 /dev/acd1c /hpcd > cd9660: Device not configured > dilbert:/home/jf# > > I have searched the mailing list, release notes, and everything else I > could get hold of and I can't seem to find out what's happening. > > Am I overlooking some very important thing here or is there a (known) > problem? > > -- > Jens Fallesen O- > Hedegaardsvej 41 st th, 2300 Copenhagen S, Denmark > Phone: (+45) 32 86 18 99 * Fax: (+45) 32 86 17 99 > CCIE #5470 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message Hi, I just had a similar problem, and solved it by making sure I had the proper version of /dev/MAKEDEV, as older versions will not build the /dev/acd* nodes with the proper major/minor. To make sure, you should have something like: bash-2.03# ls -l acd* crw-r----- 1 root operator 117, 0 Mar 22 18:31 acd0a crw-r----- 1 root operator 117, 2 Mar 22 18:31 acd0c crw-r----- 1 root operator 117, 8 Mar 22 18:31 acd1a crw-r----- 1 root operator 117, 10 Mar 22 18:31 acd1c and BTW, to make the acd1* nodes, you must use: ./MAKEDEV acd2 Hope this helps Luc Morin Electrical Engineering Technologist To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 15:44:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 3514F37C2DE; Wed, 22 Mar 2000 15:44:19 -0800 (PST) (envelope-from blk@skynet.be) Received: from [194.78.238.239] (dialup1071.brussels2.skynet.be [194.78.238.239]) by trinity.skynet.be (Postfix) with ESMTP id E520B180BC; Thu, 23 Mar 2000 00:44:12 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <20000322130901.A97411@dragon.nuxi.com> References: <14552.58589.119082.742615@grasshopper.cs.duke.edu> <200003222003.PAA51043@account.abs.net> <20000322130901.A97411@dragon.nuxi.com> Date: Thu, 23 Mar 2000 00:16:43 +0100 To: obrien@FreeBSD.ORG, Howard Leadmon From: Brad Knowles Subject: Re: Compiler problems with -O2 (was Re: CVS Trouble, even under 4.0-RELEASE (alpha) HELP!) Cc: freebsd-alpha@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:09 PM -0800 2000/3/22, David O'Brien wrote: > I'm on the virge of turning off "-O2" on both Alpha and i386. Cool! Can I put in -O39696943125454932 and you'll save me from myself on that, too? ;-) Seriously, I have to wonder why people can't take the recommendation that you should use nothing more than -O, and that anything more is only likely to increase your probability of crashing, toasting the system, etc.... I'm sorry, at best here we're talking a few tenths of a percentage point of increased speed (if that), and maybe a few milliseconds saved -- right? -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 15:44:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 2CCE737B5CC for ; Wed, 22 Mar 2000 15:44:30 -0800 (PST) (envelope-from blk@skynet.be) Received: from [194.78.238.239] (dialup1071.brussels2.skynet.be [194.78.238.239]) by trinity.skynet.be (Postfix) with ESMTP id D985F180D5; Thu, 23 Mar 2000 00:44:21 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: References: Date: Thu, 23 Mar 2000 00:20:32 +0100 To: Matt Heckaman , Christian Jachmann From: Brad Knowles Subject: Re: 3.4-Stable crashes..(heavy diskio+networking) Cc: "stable@freebsd.org" Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 5:32 PM -0500 2000/3/22, Matt Heckaman wrote: > This may sound silly, but have you looked at the value for your > NMBCLUSTERS? FreeBSD panics when it runs out of them, as can happen in a > high network load situation. I scale mine based on the bandwidth and > assume a worst case scenario of a denial of service attack. I've found > 16,384 good for T1+, moving to double that for 10Mbit, as for beyond that, > I've never worked with anything that high. At the bottom of his kernel config, he's got: options NMBCLUSTERS=26112 This would seem to beat your 16384 (which also happens to be the value I use in our news peering server running 3.2-RELEASE, although we're running Diablo and not INN and we're not doing the volumes of traffic he is). -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 15:44:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 9FEC937C419; Wed, 22 Mar 2000 15:44:45 -0800 (PST) (envelope-from blk@skynet.be) Received: from [194.78.238.239] (dialup1071.brussels2.skynet.be [194.78.238.239]) by trinity.skynet.be (Postfix) with ESMTP id 88F1D180CF; Thu, 23 Mar 2000 00:44:35 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <200003231702.LAA84469@aurora.sol.net> References: <200003231702.LAA84469@aurora.sol.net> Date: Thu, 23 Mar 2000 00:21:45 +0100 To: chat@FreeBSD.ORG From: Brad Knowles Subject: Re: dot-0 releases Cc: stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:02 AM -0600 2000/3/23, Joe Greco wrote: > OMG, now, that is just the worst bit of bootlicking I've seen this year. Enjoy it while you can! I'm just buttering you up so that you'll stay SANE until May.... ;-) -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 15:54:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D00D237C2DF for ; Wed, 22 Mar 2000 15:54:10 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA30536; Wed, 22 Mar 2000 16:54:02 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA34951; Wed, 22 Mar 2000 16:54:01 -0700 (MST) Message-Id: <200003222354.QAA34951@harmony.village.org> To: Vivek Khera Subject: Re: "dangerously dedicated" Cc: stable@FreeBSD.ORG In-reply-to: Your message of "Wed, 22 Mar 2000 18:30:19 EST." <14553.22411.265795.429126@onceler.kcilink.com> References: <14553.22411.265795.429126@onceler.kcilink.com> <14552.57732.739752.665443@onceler.kcilink.com> <4.3.2.20000321160347.00ad9b20@207.227.119.2> <38D50DBC.88FA8E4D@glue.umd.edu> <38D3AB72.366D851D@glue.umd.edu> <200003152159.OAA89926@harmony.village.org> <38D03E64.3D17FC34@glue.umd.edu> <200003190433.VAA04863@harmony.village.org> <200003212255.PAA26291@harmony.village.org> <200003222301.QAA34410@harmony.village.org> Date: Wed, 22 Mar 2000 16:54:01 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14553.22411.265795.429126@onceler.kcilink.com> Vivek Khera writes: : I guess I don't see how to use, eg, da0a without being "dangerously : dedicated". vi /etc/fstab. Or just use the names directly to the raw commands. : WL> FreeBSD lets you do this as well. Are you sure that Linux doesn't : WL> require fdisk disks? Linux/i386 doesn't have another form of disk : : Linux requires it to run, but doesn't hang forever if it doesn't : exist. FreeBSD is the only system I've encountered so far that will : lock up (ie, does not respond to any keyboard requests or terminate : its probe) when scanning a disk without an FDISK table. I needed to : use freedos to add one to this particular drive. : FreeBSD doesn't hang forever either. I have some systems that have been in faithful service for years using dangerously dedicated mode. I've had lots of problems getting the geometry right in the BIOS when I've done this and once it was done I didn't want to mess with it at all. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 15:58:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from limerick.tchden.org (limerick.tchden.org [207.174.34.128]) by hub.freebsd.org (Postfix) with ESMTP id 361C737B8DC for ; Wed, 22 Mar 2000 15:58:20 -0800 (PST) (envelope-from groman.jeff@tchden.org) Received: from tchden.org (localhost [127.0.0.1]) by limerick.tchden.org (8.9.3/8.9.3) with ESMTP id QAA19026 for ; Wed, 22 Mar 2000 16:58:13 GMT (envelope-from groman.jeff@tchden.org) Message-ID: <38D8FBA2.2B237F24@tchden.org> Date: Wed, 22 Mar 2000 16:58:10 +0000 From: Jeff Groman X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.unix.bsd.freebsd.misc To: stable@FreeBSD.ORG Subject: KDE application errors-- Help Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone seen errors like this? bash-2.03$ korganizer /usr/libexec/ld-elf.so.1: /usr/local/lib/libkfm.so.2: Undefined symbol "__ti7QDialog" bash-2.03$ konsole QFont::load: Internal error Abort trap (core dumped) bash-2.03$ I'm running 3.4. Thanks, Jeff -- Jeff Groman IS Department, Childrens Hospital, Denver groman.jeff@tchden.org 303 864 5671 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 16: 0:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 3FDE437C34E for ; Wed, 22 Mar 2000 16:00:24 -0800 (PST) (envelope-from blk@skynet.be) Received: from [194.78.238.239] (dialup1071.brussels2.skynet.be [194.78.238.239]) by morpheus.skynet.be (Postfix) with ESMTP id 72299D9C5; Thu, 23 Mar 2000 01:00:21 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <4.2.2.20000322175820.00e0e8c0@email.eden.rutgers.edu> References: <4.2.2.20000322175820.00e0e8c0@email.eden.rutgers.edu> Date: Thu, 23 Mar 2000 00:49:09 +0100 To: Carroll Kong , Christian Jachmann , "stable@freebsd.org" From: Brad Knowles Subject: Re: 3.4-Stable crashes..(heavy diskio+networking) Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 6:04 PM -0500 2000/3/22, Carroll Kong wrote: > Ok. Your Maxusers seems a bit high. Good point. I had missed that. I have recently had it confirmed to me that having maxusers > 128 *continues* to be a problem with even the latest 3.4-STABLE, so you should back that off and instead set individually the things that you need to be raised but which are normally calculated based on maxusers. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 16: 0:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id DE6B937C51D for ; Wed, 22 Mar 2000 16:00:32 -0800 (PST) (envelope-from blk@skynet.be) Received: from [194.78.238.239] (dialup1071.brussels2.skynet.be [194.78.238.239]) by morpheus.skynet.be (Postfix) with ESMTP id 3DA14DA4C; Thu, 23 Mar 2000 01:00:25 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: References: Date: Thu, 23 Mar 2000 00:59:09 +0100 To: "Forrest W. Christian" , Christian Jachmann From: Brad Knowles Subject: Re: Off-topic News: WAS: Re: 3.4-Stable crashes..(heavy diskio+networking) Cc: Carroll Kong , "stable@freebsd.org" Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:30 PM -0700 2000/3/22, Forrest W. Christian wrote: > I know this doesn't solve your problem but have you looked at the highwind > products (Typhoon and Cyclone/Breeze)? See > http://bcandid.com/products/index.html They aren't available for FreeBSD. They make heavy use of threading, and do not perform well under current versions of the OS. There used to be a version available for FreeBSD, but it has since been withdrawn due to excessive problems. > Although I haven't run a news server for a while now, when I did, these > products saved us literally hundreds if not thousands of dollars of > hardware. We went from a load average of 10+ on a $10,000 Sparc to <.1 > on the same hardware switching from INN to cyclone. It looks like INN has > implemented some of the functionality which make these products sooooo > fast, but it might still be worth a look. Cyclone and the other bCandid products may help reduce end-to-end latency throughout the system and may be very easy to manage with a nice GUI, etc..., but I know of at least one very large news site (one of the biggest on the 'net ;-) that has experienced too many problems with it and they are reverting to INN, which they have a *lot* of previous experience with. Speaking for myself, I think I can do most of the things Cyclone/bCandid might be able to do for me, but using freely available software such as Diablo. I'd pay a lot less money, and I wouldn't be forced to use hardware that handles threading well, so I could keep my FreeBSD boxes and not have to turn them in for Sun Solaris/SPARC boxen. In fact, there are some things that Diablo can do that even Cyclone/bCandid can't, and there are major news sites that may run Cyclone on their news peers (they don't want to drop too far out of the Top Ten), but they prefer Diablo and that is what is on their news spool & news reader servers. > FWIW, the box "average uptime" also went from typically a day or so with > INN to weeks or months with cyclone. The OS would croak about once a day > with INN, quite frequently requiring a manual fsck -y. INN can be pretty cranky, if you don't have it configured just right. I believe that Diablo tends to be quite a bit less cranky, and is quite a bit easier to manage, add new feeds, etc.... There's also some really cool code that will be coming out soon with Diablo, which I think will give it a major leg up on all the other systems. Besides, the Father of Diablo is Matt Dillon, and he's now deeply involved in fixing large portions of some of the deepest darkest code within FreeBSD, so it's only right that we would advocate the use of his program on mailing lists associated with him. ;-) -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 16: 6:52 2000 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 F3C8137C337; Wed, 22 Mar 2000 16:06:46 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e2N0U7222431; Wed, 22 Mar 2000 16:30:07 -0800 (PST) Date: Wed, 22 Mar 2000 16:30:07 -0800 From: Alfred Perlstein To: Brad Knowles Cc: obrien@FreeBSD.ORG, Howard Leadmon , freebsd-alpha@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Compiler problems with -O2 (was Re: CVS Trouble, even under 4.0-RELEASE (alpha) HELP!) Message-ID: <20000322163007.D21029@fw.wintelcom.net> References: <14552.58589.119082.742615@grasshopper.cs.duke.edu> <200003222003.PAA51043@account.abs.net> <20000322130901.A97411@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from blk@skynet.be on Thu, Mar 23, 2000 at 12:16:43AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Brad Knowles [000322 16:15] wrote: > At 1:09 PM -0800 2000/3/22, David O'Brien wrote: > > > I'm on the virge of turning off "-O2" on both Alpha and i386. > > Cool! Can I put in -O39696943125454932 and you'll save me from > myself on that, too? ;-) > > > Seriously, I have to wonder why people can't take the > recommendation that you should use nothing more than -O, and that > anything more is only likely to increase your probability of > crashing, toasting the system, etc.... > > I'm sorry, at best here we're talking a few tenths of a > percentage point of increased speed (if that), and maybe a few > milliseconds saved -- right? Actually the difference between -O and -O2 the times i've looked at the generated code was substantial, but I guess that brings along complexity that still needs to be worked out. :( -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 16:30:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89]) by hub.freebsd.org (Postfix) with ESMTP id A452637B84E for ; Wed, 22 Mar 2000 16:30:12 -0800 (PST) (envelope-from forrestc@workhorse.iMach.com) Received: from localhost (forrestc@localhost) by workhorse.iMach.com (8.9.3/8.9.3) with ESMTP id RAA12662; Wed, 22 Mar 2000 17:24:25 -0700 (MST) Date: Wed, 22 Mar 2000 17:24:24 -0700 (MST) From: "Forrest W. Christian" To: Brad Knowles Cc: Christian Jachmann , Carroll Kong , "stable@freebsd.org" Subject: Re: Off-topic News: WAS: Re: 3.4-Stable crashes..(heavy diskio+networking) 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 I guess it's been longer than I had realized since we switched from local news to outsourcing. (Believe me I've been happy to NOT have that nightmare) On Thu, 23 Mar 2000, Brad Knowles wrote: > In fact, there are some things that Diablo can do that even > Cyclone/bCandid can't, and there are major news sites that may run > Cyclone on their news peers (they don't want to drop too far out of > the Top Ten), but they prefer Diablo and that is what is on their > news spool & news reader servers. When I last evaluated these, diablo was (I believe) either not capable of supporting readers or something else threw it out of the running.... Then again, that was before we switched from the Slow Solaris Boxes.... > INN can be pretty cranky, if you don't have it configured just right. Amen. Has there been any progress made on a decent news CACHE software? I'd love to try something the likes of nntpcache, but hopefully something that works better than nntpcache did a couple of years ago. - Forrest W. Christian (forrestc@imach.com) KD7EHZ ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 16:43:16 2000 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 4253037B84E for ; Wed, 22 Mar 2000 16:43:11 -0800 (PST) (envelope-from conrads@cx344940-a.meta1.la.home.com) Received: (from conrads@localhost) by cx344940-a.meta1.la.home.com (8.9.3/8.9.3) id SAA77822 for stable@freebsd.org; Wed, 22 Mar 2000 18:43:07 -0600 (CST) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 22 Mar 2000 18:43:06 -0600 (CST) Organization: @Home Network From: Conrad Sabatier To: stable@freebsd.org Subject: What does "Voxware still supported in 4.0" mean exactly? Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've seen several people state that Voxware is still "supported" under 4.0, and I really have to stop and scratch my head and ask, is this some new definition of the word "supported" I was not previously aware of? Trying to use Voxware under 4.0 is, as I learned the hard and painful way, anything but easy (I've already gone back to 3.4 because of it). In fact, it's damned near impossible with certain PnP hardware, the AWE 64 being one notable example. Without the good ol' pnp commands at boottime, the AWE's wavetable is dead in the water, and if you're unfortunate enough to also have PnP motherboard audio that CANNOT BE DISABLED due to the removal of the pnp commands (my BIOS provides no facility for disabling it either), you wind up with a real mess on your hands. Not to mention that, if you compile Voxware into your kernel, at boot time you're greeted with some rather unfriendly messages chiding you for doing so, and strongly suggesting (coercing?) that you use the new pcm drivers instead. It's rather disturbing to me to think that, as FreeBSD progresses along through this and that version, I'll have no choice but to be left in the dust, or sacrifice certain functionality that I've come to know and love, or (God forbid) migrate to another platform altogether. One really must question what kind of "progress" it is that breaks things that formerly worked (and worked very well at that), and offers no new alternatives. -- Conrad Sabatier http://members.home.net/conrads/ ICQ# 1147270 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 16:46:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from xxx.video-collage.com (xxx.video-collage.com [209.122.149.226]) by hub.freebsd.org (Postfix) with ESMTP id 744FD37B8A3; Wed, 22 Mar 2000 16:46:24 -0800 (PST) (envelope-from mi@video-collage.com) X-Relay-IP: ‚  Received: from dufus.video-collage.com (dufus [10.222.222.77]) by xxx.video-collage.com (8.9.1a/8.9.1) with ESMTP id TAA08116; Wed, 22 Mar 2000 19:46:22 -0500 (EST) Received: from dufus.video-collage.com (localhost.video-collage.com [127.0.0.1]) by dufus.video-collage.com (8.9.3/8.9.3) with ESMTP id TAA79141; Wed, 22 Mar 2000 19:46:19 -0500 (EST) (envelope-from mi@xxx) Message-Id: <200003230046.TAA79141@dufus.video-collage.com> Date: Wed, 22 Mar 2000 19:46:19 -0500 (EST) From: mi@video-collage.com, UNEXPECTED_DATA_AFTER_ADDRESS@.SYNTAX-ERROR Reply-To: mi@aldan.algebra.com Subject: benefits of -ON+1 (Re: Compiler problems with -O2 ...) To: Brad Knowles Cc: obrien@FreeBSD.ORG, Howard Leadmon , freebsd-alpha@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG 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 On 23 Mar, Brad Knowles wrote: = I'm sorry, at best here we're talking a few tenths of a = percentage point of increased speed (if that), and maybe a few = milliseconds saved -- right? I have some benchmark results at http://virtual-estates.net/bm/ ... It analyzes archivers (gzip and bzip). Bzip is not as hand-optimized as gzip (which uses asm on i386), and it shows -- -O3 makes it noticeably faster compared to -O, while gzip is faster with -O... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 17:11:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id EC15737B9C1 for ; Wed, 22 Mar 2000 17:11:19 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p30-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.31]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id KAA15058; Thu, 23 Mar 2000 10:09:37 +0900 (JST) Message-ID: <38D966CE.2080999D@newsguy.com> Date: Thu, 23 Mar 2000 09:35:26 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Andy Sparrow Cc: "Jordan K. Hubbard" , Brad Knowles , David Murphy , stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) References: <200003220411.UAA31479@mega.geek4food.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andy Sparrow wrote: > > [1] Actually, I don't fully understand why this happened either - it seemed > like a very nice feature to be able to force some miscreant Plug'n'Pray > device into using a known, "safe" configuration to me. It happened because the devices now don't need the user to tell them what the settings are. They can infer that from PnP information (which is what PnP was designed for, in first place). > But why doesn't Voxware find it then? Because Voxware has not been changed to do so. Which get us back to the maintenance issue, which gets us to Voxware being dropped from 5.0-current. Or, simply put, all Voxware problems result from nobody working on it. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@zurichgnomes.bsdconspiracy.net One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 17:17: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from aragorn.neomedia.it (aragorn.neomedia.it [195.103.207.6]) by hub.freebsd.org (Postfix) with ESMTP id BDB6737B8A3 for ; Wed, 22 Mar 2000 17:16:55 -0800 (PST) (envelope-from bartequi@neomedia.it) Received: from bartequi.ottodomain.org (ppp2-pa5.neomedia.it [195.103.207.114]) by aragorn.neomedia.it (8.9.3/8.9.3) with SMTP id CAA01444; Thu, 23 Mar 2000 02:16:42 +0100 (CET) From: Salvo Bartolotta Date: Thu, 23 Mar 2000 01:20:28 GMT Message-ID: <20000323.1202800@bartequi.ottodomain.org> Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions [Failure] To: Warner Losh Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <200003222302.QAA34431@harmony.village.org> References: <200003221532.KAA10998@akiva.homer.att.com> <200003222302.QAA34431@harmony.village.org> X-Mailer: SuperCalifragilis 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 >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 3/23/00, 12:02:42 AM, Warner Losh wrote regarding R= e:=20 HEADS UP: 3.x -> 4.0-STABLE upgrade instructions [Failure] : > In message <200003221532.KAA10998@akiva.homer.att.com> "J. W.=20 Ballantine" writes: > : I then shutdown now to single user mode, cd to /usr/src and > : do ``make -DNOINFO installworld''. This starts and continues to=20 /bin/test > : where it fails due to a kernel failure. > ??? > : When I try to reboot the system, with the RELENG_4 kernel I get: > : / not unmounted cleanly, run fsck and reboot. > : I go into single user mode and run fsck ; fsck -p ; fsck /dev/da0s1a= > : and a few sync's thrown in just for good luck, but still the same=20 error. > What's the error? > Warner Dear Warner Losh, I met an analogous error (due to a reboot) when upgrading to the=20 (then) 4-0 CURRENT. =20 I may be wrong, but I am afraid fsck, at this stage, is NOT able to=20 correct the problems. Personally, I booted from *another* FreeBSD slice and ran fsck from=20 there over the "would-be current" partitions :-) After which=20 operation, I was able to complete the (then) dreaded make world. Since=20 then , it has (apparently) worked like charm for me, at least as far=20 as my tasks are concerned :-)=20 HTH, Salvo =20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 17:20:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9C6F237B586 for ; Wed, 22 Mar 2000 17:20:43 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA30881; Wed, 22 Mar 2000 18:20:38 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA35511; Wed, 22 Mar 2000 18:20:37 -0700 (MST) Message-Id: <200003230120.SAA35511@harmony.village.org> To: Salvo Bartolotta Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions [Failure] Cc: freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Thu, 23 Mar 2000 01:20:28 GMT." <20000323.1202800@bartequi.ottodomain.org> References: <20000323.1202800@bartequi.ottodomain.org> <200003221532.KAA10998@akiva.homer.att.com> <200003222302.QAA34431@harmony.village.org> Date: Wed, 22 Mar 2000 18:20:37 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000323.1202800@bartequi.ottodomain.org> Salvo Bartolotta writes: : I may be wrong, but I am afraid fsck, at this stage, is NOT able to : correct the problems. I think that this is due to bad dev notes. that's the symptom that was reported at the time. : Personally, I booted from *another* FreeBSD slice and ran fsck from : there over the "would-be current" partitions :-) After which : operation, I was able to complete the (then) dreaded make world. Since : then , it has (apparently) worked like charm for me, at least as far : as my tasks are concerned :-) That works too :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 17:27:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from weeble.dyndns.org (ubppp234-38.dialin.buffalo.edu [128.205.234.38]) by hub.freebsd.org (Postfix) with ESMTP id F0F1737B6BA; Wed, 22 Mar 2000 17:27:08 -0800 (PST) (envelope-from cjm2@earthling.net) Received: from shithead (shithead.weeble.dyndns.org [10.0.0.2]) by weeble.dyndns.org (8.9.3/8.9.3) with SMTP id UAA32400; Wed, 22 Mar 2000 20:26:32 -0500 (EST) (envelope-from cjm2@earthling.net) From: "C J Michaels" To: "Brad Knowles" , , "Howard Leadmon" Cc: , Subject: RE: Compiler problems with -O2 (was Re: CVS Trouble, even under 4.0-RELEASE (alpha) HELP!) Date: Wed, 22 Mar 2000 20:26:50 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Seriously. I can see adding a warning, but restricting people completely is another story. One of the main reasons I run FreeBSD is the flexability it provides me compared to other operating systems. Even if that's the flexability to shoot myself in the foot. FWIW, I've never had a problem with anything I've compiled with "-O2", but I guess I'm just lucky, eh? -Chris -----Original Message----- From: owner-freebsd-stable@FreeBSD.ORG [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Brad Knowles Sent: Wednesday, March 22, 2000 6:17 PM To: obrien@FreeBSD.ORG; Howard Leadmon Cc: freebsd-alpha@FreeBSD.ORG; freebsd-stable@FreeBSD.ORG Subject: Compiler problems with -O2 (was Re: CVS Trouble, even under 4.0-RELEASE (alpha) HELP!) At 1:09 PM -0800 2000/3/22, David O'Brien wrote: > I'm on the virge of turning off "-O2" on both Alpha and i386. Cool! Can I put in -O39696943125454932 and you'll save me from myself on that, too? ;-) Seriously, I have to wonder why people can't take the recommendation that you should use nothing more than -O, and that anything more is only likely to increase your probability of crashing, toasting the system, etc.... I'm sorry, at best here we're talking a few tenths of a percentage point of increased speed (if that), and maybe a few milliseconds saved -- right? -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium 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 Mar 22 17:34: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 8F23337B6EF for ; Wed, 22 Mar 2000 17:33:57 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p04-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.133]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id KAA21029; Thu, 23 Mar 2000 10:33:53 +0900 (JST) Message-ID: <38D97407.14B4B772@newsguy.com> Date: Thu, 23 Mar 2000 10:31:51 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Kenneth W Cochran Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Linux ext2 fs support changes in -stable References: <200003221548.KAA05168@world.std.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth W Cochran wrote: > > Somewhat all-of-a-sudden, I am unable to r/w mount a Linux ext2 > filesystem on the same hdd with my BSD. I get in my syslog (& > on console): > /kernel: WARNING: R/W mount of dev 0xe040a denied due to > unsupported optional features This is telling you that this file system has features (put in the by a recent version of Linux, most likely) which our ext2fs code does not understand. Since we don't understand it, allowing a R/W mount is dangerous. You can read more about this using the cvsweb to check the commit logs for the ext2fs files. This was bde's (Bruce Evans) changes. I can see the point in wanting to force a R/W mount, on the grounds that you know more about your setup than the software does (which is the whole point of the software denying you R/W access in the first place :), but you'll need to convince Bruce, not me, of that. Convincing Bruce is easy, as long as he agrees with you to begin with. If he doesn't... -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@zurichgnomes.bsdconspiracy.net One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 17:34:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 7BD0937B6EF for ; Wed, 22 Mar 2000 17:34:09 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p04-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.133]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id KAA21010; Thu, 23 Mar 2000 10:33:47 +0900 (JST) Message-ID: <38D97069.C5811525@newsguy.com> Date: Thu, 23 Mar 2000 10:16:25 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: Thomas David Rivers , witr@rwwa.com, stable@FreeBSD.ORG, witr@pobox.rwwa.com Subject: Re: V4.0 and Walnut Creek Subscriptions... References: <22098.953749411@zippy.cdrom.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 K. Hubbard" wrote: > > No, you won't get two copies. Just charged twice. ;-> -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@zurichgnomes.bsdconspiracy.net One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 18:25: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 9673E37B51D; Wed, 22 Mar 2000 18:25:01 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id SAA99506; Wed, 22 Mar 2000 18:25:02 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 22 Mar 2000 18:25:02 -0800 (PST) From: Kris Kennaway To: Jeff Groman Cc: stable@FreeBSD.ORG Subject: Re: KDE application errors-- Help In-Reply-To: <38D8FBA2.2B237F24@tchden.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, 22 Mar 2000, Jeff Groman wrote: > Has anyone seen errors like this? > > bash-2.03$ korganizer > /usr/libexec/ld-elf.so.1: /usr/local/lib/libkfm.so.2: Undefined symbol > "__ti7QDialog" > bash-2.03$ konsole > QFont::load: Internal error > Abort trap (core dumped) > bash-2.03$ > > I'm running 3.4. Try rebuilding all of the KDE ports and associated dependencies..something looks out of sync. cd /usr/ports/x11/kde11 make ALWAYS_BUILD_DEPENDS=1 FORCE_PKG_REGISTER=1 all install clean and go and get a large cup of coffee :-) Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 19: 9:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 1ABEC37B532 for ; Wed, 22 Mar 2000 19:09:53 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA24060; Wed, 22 Mar 2000 19:08:58 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Conrad Sabatier Cc: stable@FreeBSD.ORG Subject: Re: What does "Voxware still supported in 4.0" mean exactly? In-reply-to: Your message of "Wed, 22 Mar 2000 18:43:06 CST." Date: Wed, 22 Mar 2000 19:08:58 -0800 Message-ID: <24057.953780938@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's rather disturbing to me to think that, as FreeBSD progresses along > through this and that version, I'll have no choice but to be left in the > dust, or sacrifice certain functionality that I've come to know and love, > or (God forbid) migrate to another platform altogether. Or get another sound card? Sorry, but I had to note this as an additional option which, unless you're incredibly poverty-stricken, should not be ruled out for *any* hardware. I replaced my AWE32 board long ago, and purely because of its oversize form-factor. I now use the on-board Vibra16X audio capabilities of the motherboard I replaced my old one with. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 19:18:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from h006097780c24.ne.mediaone.net (h006097780c24.ne.mediaone.net [24.218.250.124]) by hub.freebsd.org (Postfix) with ESMTP id 7698837B894 for ; Wed, 22 Mar 2000 19:18:12 -0800 (PST) (envelope-from deimos@lewman.org) Received: from lewman.org (localhost [127.0.0.1]) by h006097780c24.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id WAA52459 for ; Wed, 22 Mar 2000 22:17:42 -0500 (EST) (envelope-from deimos@lewman.org) Message-ID: <38D98CD6.BFAB40BD@lewman.org> Date: Wed, 22 Mar 2000 22:17:42 -0500 From: deimos Organization: Lewman Industries X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@FreeBSD.ORG Subject: Re: What does "Voxware still supported in 4.0" mean exactly? References: <24057.953780938@zippy.cdrom.com> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------msB469C250E728817F52742412" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------msB469C250E728817F52742412 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Jordan K. Hubbard" wrote: > > Or get another sound card? Sorry, but I had to note this as an > additional option which, unless you're incredibly poverty-stricken, > should not be ruled out for *any* hardware. I replaced my AWE32 board What about those of us with AWE64 GOLD boards? The board itself does quite well with most PCI based boards available today. As for upgrades, would a Vibra16 really count as an upgrade? If we're going to be forced to use newer boards, what about SoundBlaster Live, Diamond Fusion, and other modern Aureal/Dolby based PCI sound boards? Will pcm support those out of the box, or are we now going to have to wait for some other driver to be developed? I'm all for progress, but I fail to see how going from my AWE64GOLD to a Vibra16 (or another lesser sound card) is going to be worth anything. If I'm going to be forced to ugprade, I'd rather get state of the art today; hoping it will last another 3 years as my current card has. Just my US$0.02. -- | Andy | e-mail | web | | | andy@lewman.com | www.lewman.com | Know thyself. If you need help, call the C.I.A. --------------msB469C250E728817F52742412 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIJkAYJKoZIhvcNAQcCoIIJgTCCCX0CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC B10wggQnMIIDkKADAgECAhAXN8ogLRsvAwDJMiA8WgnMMA0GCSqGSIb3DQEBBAUAMIHMMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTk5MDUxMDAwMDAw MFoXDTAwMDUwOTIzNTk1OVowggEPMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO ZXRzY2FwZSBGdWxsIFNlcnZpY2UxFjAUBgNVBAMUDUFuZHJldyBMZXdtYW4xHjAcBgkqhkiG 9w0BCQEWD2FuZHlAbGV3bWFuLmNvbTBcMA0GCSqGSIb3DQEBAQUAA0sAMEgCQQC/EaQmMjUQ gdB4D3aH5as3M8CQY0I1RmgYevC7MoGkHezh80n+0XeGNEYE6LpMtwnAmv4NYPbwktR2EAz1 RaTPAgMBAAGjggEGMIIBAjAJBgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUB BwEBMIGOMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsG AQUFBwICMFYwFRYOVmVyaVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3Jw LiBieSByZWZlcmVuY2UgbGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEE BAMCB4AwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xhc3Mx LmNybDANBgkqhkiG9w0BAQQFAAOBgQBLxOO6fPb6g7wDdf3nyY05xisVS88KGnl3MXhU4Y7N /rdCNVgoDy4Yj7qrdieJUMLAKZq91PkshncU4Ezzj94H8jmsbwSLOod9biAJ3s58fL6MREdD vH0Xp0cw9k3JMpi4ipM5DkYfbeiCCczfvgYyY7Jly4cl/Iw08l4yQK239TCCAy4wggKXoAMC AQICEQDSdi6NFAw9fbKoJV2v7g11MA0GCSqGSIb3DQEBAgUAMF8xCzAJBgNVBAYTAlVTMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMgUHJpbWFy eSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw05ODA1MTIwMDAwMDBaFw0wODA1MTIyMzU5 NTlaMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1 c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJ bmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3Mg MSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMIGfMA0G CSqGSIb3DQEBAQUAA4GNADCBiQKBgQC7WkSKBBa7Vf0DeootlE8VeDa4DUqyb5xUv7zodyqd ufBou5XZMUFweoFLuUgTVi3HCOGEQqvAopKrRFyqQvCCDgLpL/vCO7u+yScKXbawNkIztW5U iE+HSr8Z2vkV6A+HthzjzMaajn9qJJLj/OBluqexfu/J2zdqyErICQbkmQIDAQABo3wwejAR BglghkgBhvhCAQEEBAMCAQYwRwYDVR0gBEAwPjA8BgtghkgBhvhFAQcBATAtMCsGCCsGAQUF BwIBFh93d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBMA8GA1UdEwQIMAYBAf8CAQAw CwYDVR0PBAQDAgEGMA0GCSqGSIb3DQEBAgUAA4GBAIi4Nzvd2pQ3AK2qn+GBAXEekmptL/bx ndPKZDjcG5gMB4ZbhRVqD7lJhaSV8Rd9Z7R/LSzdmkKewz60jqrlCwbe8lYq+jPHvhnXU0zD vcjjF7WkSUJj7MKmFw9dWBpJPJBcVaNlIAD9GCDlX4KmsaiSxVhqwY0DPOvDzQWikK5uMYIB +zCCAfcCAQEwgeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0 ZWQCEBc3yiAtGy8DAMkyIDxaCcwwCQYFKw4DAhoFAKCBsTAYBgkqhkiG9w0BCQMxCwYJKoZI hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMDAzMjMwMzE3NDJaMCMGCSqGSIb3DQEJBDEWBBT+ 9EABrcXLQndnWopiWl8g2v/MvjBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG SIb3DQMCAgIAgDAHBgUrDgMCBzANBggqhkiG9w0DAgIBQDANBggqhkiG9w0DAgIBKDANBgkq hkiG9w0BAQEFAARAdwZNm8wTxpaJ9PKHw2H9JSVugaDZL8gnTXtEcIq0TFTfE7n6P3/vt1mU ZnA5o91QOJhZ0ub5uNhXbsIz+WdzFw== --------------msB469C250E728817F52742412-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 19:20:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 07B5237B593 for ; Wed, 22 Mar 2000 19:20:36 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id NAA16937; Thu, 23 Mar 2000 13:49:46 +1030 (CST) (envelope-from doconnor@gsoft.com.au) 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: <24057.953780938@zippy.cdrom.com> Date: Thu, 23 Mar 2000 13:49:46 +1030 (CST) From: "Daniel O'Connor" To: "Jordan K. Hubbard" Subject: Re: What does "Voxware still supported in 4.0" mean exactly? Cc: stable@FreeBSD.ORG, Conrad Sabatier Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Mar-00 Jordan K. Hubbard wrote: > Or get another sound card? Sorry, but I had to note this as an > additional option which, unless you're incredibly poverty-stricken, > should not be ruled out for *any* hardware. I replaced my AWE32 board > long ago, and purely because of its oversize form-factor. I now use > the on-board Vibra16X audio capabilities of the motherboard I replaced > my old one with. And given the AWE works fine for actually playing PCM audio its not like you lose 100% of your functionality. Lack of awe0 is annoying but I don't listen to midi very often :) d--- 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 Wed Mar 22 19:24:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 28C6D37BA3D for ; Wed, 22 Mar 2000 19:24:32 -0800 (PST) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id A42A21C4D; Wed, 22 Mar 2000 22:24:28 -0500 (EST) Date: Wed, 22 Mar 2000 22:24:28 -0500 From: Bill Fumerola To: deimos Cc: stable@FreeBSD.ORG Subject: Re: What does "Voxware still supported in 4.0" mean exactly? Message-ID: <20000322222428.E25438@jade.chc-chimes.com> References: <24057.953780938@zippy.cdrom.com> <38D98CD6.BFAB40BD@lewman.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38D98CD6.BFAB40BD@lewman.org>; from deimos@lewman.org on Wed, Mar 22, 2000 at 10:17:42PM -0500 X-Operating-System: FreeBSD 3.2-RELEASE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 22, 2000 at 10:17:42PM -0500, deimos wrote: > What about those of us with AWE64 GOLD boards? The board itself does > quite well with most PCI based boards available today. As for upgrades, > would a Vibra16 really count as an upgrade? > > If we're going to be forced to use newer boards, what about > SoundBlaster Live, Diamond Fusion, and other modern Aureal/Dolby based > PCI sound boards? Will pcm support those out of the box, or are we now > going to have to wait for some other driver to be developed? > > I'm all for progress, but I fail to see how going from my AWE64GOLD to > a Vibra16 (or another lesser sound card) is going to be worth anything. > If I'm going to be forced to ugprade, I'd rather get state of the art > today; hoping it will last another 3 years as my current card has. pcm0: port 0xdcc0-0xdcff irq 10 at device 9.0 on pci1 SB64 works fine for me, I'm currently listening to 'RATM - No Shelter' and it sounds great. A beta SBLive driver is available right now, and new card drivers have been coming in at a steady pace since Cameron took over. Extracting datasheets from corporate whores is the largest roadblock at this point. Naturally, your patches are just as welcome as anyone elses. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: billf@chc-chimes.com / billf@FreeBSD.org Office: 800-252-2421 x128 / Cell: 248-761-7272 PS. the voxware drivers aren't the answer either. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 19:26:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 9B0CC37B5F1 for ; Wed, 22 Mar 2000 19:26:36 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA24243; Wed, 22 Mar 2000 19:26:47 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: deimos Cc: stable@FreeBSD.ORG Subject: Re: What does "Voxware still supported in 4.0" mean exactly? In-reply-to: Your message of "Wed, 22 Mar 2000 22:17:42 EST." <38D98CD6.BFAB40BD@lewman.org> Date: Wed, 22 Mar 2000 19:26:47 -0800 Message-ID: <24240.953782007@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What about those of us with AWE64 GOLD boards? The board itself does > quite well with most PCI based boards available today. As for upgrades, > would a Vibra16 really count as an upgrade? Why not send us one and we'll have Cameron Grant look at it? He is somewhat constrained by the hardware available to him, and being off in the UK and stuck in a wheelchair to boot doesn't exactly give him the best access. > If we're going to be forced to use newer boards, what about > SoundBlaster Live, Diamond Fusion, and other modern Aureal/Dolby based > PCI sound boards? Will pcm support those out of the box, or are we now > going to have to wait for some other driver to be developed? It doesn't support them out of the box now, but I can tell you that Cameron is certainly working on at least the Soundblaster Live support since we did send him one and I've heard him complaining bitterly about it on several occasions. :) If somebody wants to send him a Diamond Fusion card, I would be happy to "broker" the deal. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 19:34:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from h006097780c24.ne.mediaone.net (h006097780c24.ne.mediaone.net [24.218.250.124]) by hub.freebsd.org (Postfix) with ESMTP id 91EE137B75A for ; Wed, 22 Mar 2000 19:34:06 -0800 (PST) (envelope-from andy@lewman.org) Received: from lewman.org (localhost [127.0.0.1]) by h006097780c24.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id WAA93895; Wed, 22 Mar 2000 22:33:30 -0500 (EST) (envelope-from andy@lewman.org) Message-ID: <38D9908A.C2D5773D@lewman.org> Date: Wed, 22 Mar 2000 22:33:30 -0500 From: deimos Organization: Lewman Industries X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Jordan K. Hubbard" , stable@freebsd.org Subject: Re: What does "Voxware still supported in 4.0" mean exactly? References: <24240.953782007@zippy.cdrom.com> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms8142795EBC0CAB6A00251423" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------ms8142795EBC0CAB6A00251423 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Jordan K. Hubbard" wrote: > Why not send us one and we'll have Cameron Grant look at it? He is > somewhat constrained by the hardware available to him, and being off > in the UK and stuck in a wheelchair to boot doesn't exactly give him > the best access. To where do I mail one? I'll happily spend the $25 for an AWE64Gold. As for the Diamond Fusion, I may buy one for him as well, as long as I get it back when the drivers work. :P -- | Andy | e-mail | web | | | andy@lewman.com | www.lewman.com | Know thyself. If you need help, call the C.I.A. --------------ms8142795EBC0CAB6A00251423 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIJkAYJKoZIhvcNAQcCoIIJgTCCCX0CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC B10wggQnMIIDkKADAgECAhAXN8ogLRsvAwDJMiA8WgnMMA0GCSqGSIb3DQEBBAUAMIHMMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTk5MDUxMDAwMDAw MFoXDTAwMDUwOTIzNTk1OVowggEPMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO ZXRzY2FwZSBGdWxsIFNlcnZpY2UxFjAUBgNVBAMUDUFuZHJldyBMZXdtYW4xHjAcBgkqhkiG 9w0BCQEWD2FuZHlAbGV3bWFuLmNvbTBcMA0GCSqGSIb3DQEBAQUAA0sAMEgCQQC/EaQmMjUQ gdB4D3aH5as3M8CQY0I1RmgYevC7MoGkHezh80n+0XeGNEYE6LpMtwnAmv4NYPbwktR2EAz1 RaTPAgMBAAGjggEGMIIBAjAJBgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUB BwEBMIGOMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsG AQUFBwICMFYwFRYOVmVyaVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3Jw LiBieSByZWZlcmVuY2UgbGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEE BAMCB4AwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xhc3Mx LmNybDANBgkqhkiG9w0BAQQFAAOBgQBLxOO6fPb6g7wDdf3nyY05xisVS88KGnl3MXhU4Y7N /rdCNVgoDy4Yj7qrdieJUMLAKZq91PkshncU4Ezzj94H8jmsbwSLOod9biAJ3s58fL6MREdD vH0Xp0cw9k3JMpi4ipM5DkYfbeiCCczfvgYyY7Jly4cl/Iw08l4yQK239TCCAy4wggKXoAMC AQICEQDSdi6NFAw9fbKoJV2v7g11MA0GCSqGSIb3DQEBAgUAMF8xCzAJBgNVBAYTAlVTMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMgUHJpbWFy eSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw05ODA1MTIwMDAwMDBaFw0wODA1MTIyMzU5 NTlaMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1 c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJ bmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3Mg MSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMIGfMA0G CSqGSIb3DQEBAQUAA4GNADCBiQKBgQC7WkSKBBa7Vf0DeootlE8VeDa4DUqyb5xUv7zodyqd ufBou5XZMUFweoFLuUgTVi3HCOGEQqvAopKrRFyqQvCCDgLpL/vCO7u+yScKXbawNkIztW5U iE+HSr8Z2vkV6A+HthzjzMaajn9qJJLj/OBluqexfu/J2zdqyErICQbkmQIDAQABo3wwejAR BglghkgBhvhCAQEEBAMCAQYwRwYDVR0gBEAwPjA8BgtghkgBhvhFAQcBATAtMCsGCCsGAQUF BwIBFh93d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBMA8GA1UdEwQIMAYBAf8CAQAw CwYDVR0PBAQDAgEGMA0GCSqGSIb3DQEBAgUAA4GBAIi4Nzvd2pQ3AK2qn+GBAXEekmptL/bx ndPKZDjcG5gMB4ZbhRVqD7lJhaSV8Rd9Z7R/LSzdmkKewz60jqrlCwbe8lYq+jPHvhnXU0zD vcjjF7WkSUJj7MKmFw9dWBpJPJBcVaNlIAD9GCDlX4KmsaiSxVhqwY0DPOvDzQWikK5uMYIB +zCCAfcCAQEwgeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0 ZWQCEBc3yiAtGy8DAMkyIDxaCcwwCQYFKw4DAhoFAKCBsTAYBgkqhkiG9w0BCQMxCwYJKoZI hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMDAzMjMwMzMzMzBaMCMGCSqGSIb3DQEJBDEWBBTL fqNEhl4OM5M1P1GsoLio9ue8wDBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG SIb3DQMCAgIAgDAHBgUrDgMCBzANBggqhkiG9w0DAgIBQDANBggqhkiG9w0DAgIBKDANBgkq hkiG9w0BAQEFAARAuQX9xlvgCVg9+MrDjRZcrQ239Az9rhJUyvoWbDTUkqzEgfpAjepxlATA HFAzVTAupKmlIbQ7cd8MgMg7TIS5ww== --------------ms8142795EBC0CAB6A00251423-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 19:53:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from web114.yahoomail.com (web114.yahoomail.com [205.180.60.86]) by hub.freebsd.org (Postfix) with SMTP id 8080337BA18 for ; Wed, 22 Mar 2000 19:53:26 -0800 (PST) (envelope-from ixkatl@yahoo.com) Received: (qmail 2060 invoked by uid 60001); 23 Mar 2000 03:53:25 -0000 Message-ID: <20000323035325.2059.qmail@web114.yahoomail.com> Received: from [207.172.145.108] by web114.yahoomail.com; Wed, 22 Mar 2000 19:53:25 PST Date: Wed, 22 Mar 2000 19:53:25 -0800 (PST) From: Andrew Sherrod Subject: Re: KDE application errors-- Help To: Jeff Groman , stable@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 Did you install GNOME and/or Enlightenment after KDE? This gave me similar problems. As stated in the other reply, reinstalling all KDE sources seems to work (most of the time. I still have one machine I can't get to work right.) I opened a PR on this. (If it is the GNOME/Enlightenment/KDE problem) --- Jeff Groman wrote: > Has anyone seen errors like this? > > bash-2.03$ korganizer > /usr/libexec/ld-elf.so.1: > /usr/local/lib/libkfm.so.2: Undefined symbol > "__ti7QDialog" > bash-2.03$ konsole > QFont::load: Internal error > Abort trap (core dumped) > bash-2.03$ > > I'm running 3.4. > > Thanks, > > Jeff > > > -- > Jeff Groman > IS Department, Childrens Hospital, Denver > groman.jeff@tchden.org > 303 864 5671 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the > message > ===== 'During my service in the United States Congress, I took the initiative in creating the Internet.' - Al Gore, March 9, 1999: On CNN's Late Edition __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.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 Mar 22 19:53:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 49ACF37B825 for ; Wed, 22 Mar 2000 19:53:56 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id TAA85808; Wed, 22 Mar 2000 19:53:44 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38D99548.3201BC6D@gorean.org> Date: Wed, 22 Mar 2000 19:53:44 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-HEAD-0320 i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Vivek Khera , stable@FreeBSD.ORG Subject: Re: "dangerously dedicated" References: <14552.57732.739752.665443@onceler.kcilink.com> <4.3.2.20000321160347.00ad9b20@207.227.119.2> <38D50DBC.88FA8E4D@glue.umd.edu> <38D3AB72.366D851D@glue.umd.edu> <200003152159.OAA89926@harmony.village.org> <38D03E64.3D17FC34@glue.umd.edu> <200003190433.VAA04863@harmony.village.org> <200003212255.PAA26291@harmony.village.org> <200003222301.QAA34410@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > I didn't say that using da0a is stupid. I said using dangerously > dedicated mode is stupid. Based on the number of times I've shot > myself in the foot trying to use dangaerously dedicated devices over > the years, I'll never use them again. I'm curious, what kind of problems have you had, and how is using the compatability slice an improvement? I've always used "dangerously dedicated" on my freebsd-only disks, and I've never had a problem. Not disagreeing, just curious, Doug -- "So, the cows were part of a dream that dreamed itself into existence, is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 20: 1:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3228737C29A for ; Wed, 22 Mar 2000 20:01:10 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA31397; Wed, 22 Mar 2000 21:01:08 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA36386; Wed, 22 Mar 2000 21:01:07 -0700 (MST) Message-Id: <200003230401.VAA36386@harmony.village.org> To: Doug Barton Subject: Re: "dangerously dedicated" Cc: Vivek Khera , stable@FreeBSD.ORG In-reply-to: Your message of "Wed, 22 Mar 2000 19:53:44 PST." <38D99548.3201BC6D@gorean.org> References: <38D99548.3201BC6D@gorean.org> <14552.57732.739752.665443@onceler.kcilink.com> <4.3.2.20000321160347.00ad9b20@207.227.119.2> <38D50DBC.88FA8E4D@glue.umd.edu> <38D3AB72.366D851D@glue.umd.edu> <200003152159.OAA89926@harmony.village.org> <38D03E64.3D17FC34@glue.umd.edu> <200003190433.VAA04863@harmony.village.org> <200003212255.PAA26291@harmony.village.org> <200003222301.QAA34410@harmony.village.org> Date: Wed, 22 Mar 2000 21:01:07 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38D99548.3201BC6D@gorean.org> Doug Barton writes: : I'm curious, what kind of problems have you had, and how is using the : compatability slice an improvement? I've always used "dangerously : dedicated" on my freebsd-only disks, and I've never had a problem. I've had two classes of problems. First, I've needed to set a special disk geometry in the fdisk partition. I'm not sure why it matters, but it seems to make a big difference on some of my isa scsi machines. I've also had problems with partitions starting at offset 0. While ufs does offset things by 16 blocks, and the boot1 bootblock seems to have the fdisk partition table encoded in it (well, at least it seems to preserve what's there, if anything), I've had some problems that went away when I went to having a fdisk partition and starting at an offset of 16 or so. Most of these experiences were in the 1.x and 2.0 days. Bruce's slice code has vastly improved the situation. The second class of problems came into play when I later desided to install Win95 on some of may machines. Its installation program did bad things to the dangerously dedicated disks. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 20: 3: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id E2FBA37C29F for ; Wed, 22 Mar 2000 20:03:00 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id UAA85859; Wed, 22 Mar 2000 20:02:06 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38D9973E.DF9BCB73@gorean.org> Date: Wed, 22 Mar 2000 20:02:06 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-HEAD-0320 i386) X-Accept-Language: en MIME-Version: 1.0 To: David Murphy Cc: stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) References: <20000321170118.M5367@enigma.redbrick.dcu.ie> <20000322015400.B34538@enigma.redbrick.dcu.ie> <38D86EF7.2595FA9F@gorean.org> <20000322093709.A48595@enigma.redbrick.dcu.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Murphy wrote: > > Quoting <38D86EF7.2595FA9F@gorean.org> > by Doug Barton : > > > Actually what you see on the web page clearly stated in numerous > > places is that upgrading from source is NOT for the faint of heart. > > I put a sternly worded message in my 2.2.8->3.2 upgrade web page > > that told the user that they would be better off using sysinstall. > > But, that page isn't on a freebsd site, so I guess I don't win your > > bet. > > I'm afraid not 8) I can't help pointing out that you deleted the part of my post which did refer you to the official freebsd.org site that clearly describes the recommended upgrading method. > It's probably even easier than you realise to fall into thinking > source upgrades are the way to keep up with -stable, since what *is* > in the handbook is section 18.2.2 [1], which says: But that's not what we were discussing. We were discussing upgrades to -release. -- "So, the cows were part of a dream that dreamed itself into existence, is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 20: 7:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 7747037B990 for ; Wed, 22 Mar 2000 20:07:48 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id UAA85866; Wed, 22 Mar 2000 20:06:25 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38D99841.87E51C7D@gorean.org> Date: Wed, 22 Mar 2000 20:06:25 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-HEAD-0320 i386) X-Accept-Language: en MIME-Version: 1.0 To: Brad Knowles Cc: David Murphy , stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions forimproving newpcm performance?) References: <200003191838.KAA40955@rah.star-gate.com> <000701bf91d5$4aebeb60$0304020a@NENYA> <001a01bf91c1$7f62a4b0$0304020a@NENYA> <200003191838.KAA40955@rah.star-gate.com> <20000319220453.A65973@ipass.net> <005d01bf9221$4660ac60$0304020a@NENYA> <20000320153429.A1373@ipass.net> <20000321121048.E49550@enigma.redbrick.dcu.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: > > At 12:10 PM +0000 2000/3/21, David Murphy wrote: > > > The problem is, -RELEASE is pushed out like a new release of a > > commercial OS, with big announcements, etc. etc., so people expect it > > to have been subject to a similar level of prerelease beta testing. > > It has gotten *way* more testing than any Microsoft x.0 release, > but it's still not ready for prime-time. Don't be silly. MS (for all their flaws) has an extremely sophisticated hardware compatability testing facility. In contrast freebsd supports less hardware, has a much smaller installed base, and is free to say, "no driver for you? tough bananas" to any hardware it doesn't want to support. Given the virtually non-existent adherence to standards in the PC hardware biz, and given its goals, it's amazing that windows works at all. For what it does it does extremely well. Doug -- "So, the cows were part of a dream that dreamed itself into existence, is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 20: 8:48 2000 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 7B3B737BA18 for ; Wed, 22 Mar 2000 20:08:40 -0800 (PST) (envelope-from jcm@dogma.freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3) for stable@freebsd.org id 12XyvH-000BQA-00; Thu, 23 Mar 2000 04:08:39 +0000 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id EAA77285 for stable@freebsd.org; Thu, 23 Mar 2000 04:08:39 GMT (envelope-from jcm) Date: Thu, 23 Mar 2000 04:08:39 +0000 From: j mckitrick To: stable@freebsd.org Subject: parallel zip driver Message-ID: <20000323040839.A77245@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 anyone had a chance to investigate the PR about the timeout problem with parallel port zip drives? jm -- -------------------------------------------- Jonathon McKitrick -- jcm@freebsd-uk.eu.org "Doors to the pleasures of heaven or hell, and i didn't care which." -------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 20: 8:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 23DD437C3A0 for ; Wed, 22 Mar 2000 20:08:51 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA31422; Wed, 22 Mar 2000 21:08:49 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA36458; Wed, 22 Mar 2000 21:08:48 -0700 (MST) Message-Id: <200003230408.VAA36458@harmony.village.org> To: Doug Barton Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Cc: David Murphy , stable@FreeBSD.ORG In-reply-to: Your message of "Wed, 22 Mar 2000 20:02:06 PST." <38D9973E.DF9BCB73@gorean.org> References: <38D9973E.DF9BCB73@gorean.org> <20000321170118.M5367@enigma.redbrick.dcu.ie> <20000322015400.B34538@enigma.redbrick.dcu.ie> <38D86EF7.2595FA9F@gorean.org> <20000322093709.A48595@enigma.redbrick.dcu.ie> Date: Wed, 22 Mar 2000 21:08:48 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38D9973E.DF9BCB73@gorean.org> Doug Barton writes: : But that's not what we were discussing. We were discussing upgrades to : -release. In time, I'm sure that the 3.x->4.0 upgrading section of UPDATING will migrate to the handbook. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 20:15:34 2000 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 A54C737C232 for ; Wed, 22 Mar 2000 20:15:28 -0800 (PST) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id XAA05794; Wed, 22 Mar 2000 23:15:43 -0500 (EST) (envelope-from bandix@looksharp.net) Date: Wed, 22 Mar 2000 23:15:43 -0500 (EST) From: "Brandon D. Valentine" To: Christian Jachmann Cc: Carroll Kong , "stable@freebsd.org" Subject: Re: 3.4-Stable crashes..(heavy diskio+networking) In-Reply-To: <38D954BC.4D49C9FA@gigabell.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 Thu, 23 Mar 2000, Christian Jachmann wrote: >It has been working in 2.2.* Release for about half a year, whithout any >problem. >After upgrading to 3.* (now 3.4) we got those crashes.... You may want to try rebuilding INN from the port again. Do a make deinstall and then delete the distfile and make install again. Chances are you are using an outdated version of INN which was probably built aout during your 2.2.x days. That's certainly no definitive answer, but it should help things and certainly cannot hurt. The panic log you quoted said the panic occured while innfeed was the current process. ------------------------------------------------------------- | -Brandon D. Valentine bandix at looksharp.net | bandix on EFnet IRC BVRiker on AIM ------------------------------------------------------------- | "...and as for hackers, we note that all of those known to | The Register are so strapped financially that seizing their | property would be tantamount to squeezing blood from a | stone." -- The Register, 02/17/2000 ------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 20:58:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from h006097780c24.ne.mediaone.net (h006097780c24.ne.mediaone.net [24.218.250.124]) by hub.freebsd.org (Postfix) with ESMTP id 9F6A937B557 for ; Wed, 22 Mar 2000 20:58:10 -0800 (PST) (envelope-from andy@lewman.com) Received: from lewman.com (localhost [127.0.0.1]) by h006097780c24.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id XAA00355 for ; Wed, 22 Mar 2000 23:57:46 -0500 (EST) (envelope-from andy@lewman.com) Message-ID: <38D9A44A.14385938@lewman.com> Date: Wed, 22 Mar 2000 23:57:46 -0500 From: Andy Organization: Lewman Industries X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: cvsup to RELENG_4 = 5.0-CURRENT? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just cvsup'd from my freshly installed 4.0 system, using the following supfile, and now that I reboot, and do a uname -a; I find I am in 5.0-CURRENT? supfile is: # Defaults that apply to all the collections *default host=cvsup5.FreeBSD.org *default base=/usr *default prefix=/usr # The following line is for 4-stable. If you want 3.x-stable, change # "RELENG_4" to "RELENG_3". *default release=cvs tag=RELENG_4 *default delete use-rel-suffix *default release=cvs tag=. *default compress src-all cvs-crypto ports-all My uname -a output is: FreeBSD phreakr.lewman.com 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Wed Mar 22 23:44:39 EST 2000 root@phreakr.lewman.com:/usr/src/sys/compile/PHREAKR i386 Did I miss something? -- | Andy | e-mail | web | | | andy@lewman.com | www.lewman.com | Worst Month of the Year: February. February has only 28 days in it, which means that if you rent an apartment, you are paying for three full days you don't get. Try to avoid Februarys whenever possible. -- Steve Rubenstein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 21: 0:32 2000 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 B5EA637B96A for ; Wed, 22 Mar 2000 21:00:27 -0800 (PST) (envelope-from twschulz@gloria.cord.edu) Received: from localhost (twschulz@localhost) by gloria.cord.edu (8.9.0/8.9.1) with ESMTP id WAA14600; Wed, 22 Mar 2000 22:59:43 -0600 (CST) Date: Wed, 22 Mar 2000 22:59:43 -0600 (CST) From: Trenton Schulz To: deimos Cc: "Jordan K. Hubbard" , stable@FreeBSD.ORG Subject: Re: What does "Voxware still supported in 4.0" mean exactly? In-Reply-To: <38D9908A.C2D5773D@lewman.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, 22 Mar 2000, deimos wrote: > "Jordan K. Hubbard" wrote: > > > > Why not send us one and we'll have Cameron Grant look at it? He is > > somewhat constrained by the hardware available to him, and being off > > in the UK and stuck in a wheelchair to boot doesn't exactly give him > > the best access. > > To where do I mail one? I'll happily spend the $25 for an AWE64Gold. > As for the Diamond Fusion, I may buy one for him as well, as long as I > get it back when the drivers work. :P Actually, I think you mean Diamond Monster Sound. If it weren't for me being a poor college student and liking to have sound (at least in Windows :( ) I would gladly send him my Monster Sound MX300. As it is now, I need it. -- 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 Wed Mar 22 21: 3:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.WorldMediaCo.com (mail.omaha.com [63.64.101.17]) by hub.freebsd.org (Postfix) with ESMTP id 28E1337B623 for ; Wed, 22 Mar 2000 21:03:14 -0800 (PST) (envelope-from jameso@cx676171-b.omhan1.ne.home.com) Received: from cx676171-b.omhan1.ne.home.com.cx676171-b.omhan1.ne.home.com ([24.7.33.47]) by mail1.WorldMediaCo.com (Post.Office MTA v3.5.3 release 223 ID# 0-55573U2500L250S0V35) with SMTP id com; Wed, 22 Mar 2000 22:29:37 -0600 Date: Wed, 22 Mar 2000 23:03:03 -0600 (CST) From: jameso@elwood.net Reply-To: jameso@elwood.net Subject: Re: cvsup to RELENG_4 = 5.0-CURRENT? To: Andy Cc: stable@freebsd.org In-Reply-To: <38D9A44A.14385938@lewman.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Message-Id: <20000323050314.28E1337B623@hub.freebsd.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22 Mar, Andy wrote: > Did I miss something? Yes, notice this part in your config here: > supfile is: > *default release=cvs tag=RELENG_4 > *default delete use-rel-suffix > *default release=cvs tag=. Notice your mistake? Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 21: 8:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from h006097780c24.ne.mediaone.net (h006097780c24.ne.mediaone.net [24.218.250.124]) by hub.freebsd.org (Postfix) with ESMTP id B005F37BA59 for ; Wed, 22 Mar 2000 21:08:15 -0800 (PST) (envelope-from andy@lewman.com) Received: from lewman.com (localhost [127.0.0.1]) by h006097780c24.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id AAA00451; Thu, 23 Mar 2000 00:07:45 -0500 (EST) (envelope-from andy@lewman.com) Message-ID: <38D9A6A1.9ACDB117@lewman.com> Date: Thu, 23 Mar 2000 00:07:45 -0500 From: Andy Organization: Lewman Industries X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: jameso@be.elwood.net Cc: stable@freebsd.org Subject: Re: cvsup to RELENG_4 = 5.0-CURRENT? References: <20000323050314.28E1337B623@hub.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jameso@elwood.net wrote: > > *default release=cvs tag=RELENG_4 > > *default delete use-rel-suffix > > *default release=cvs tag=. > > Notice your mistake? Apparently, yes I did miss something. Jeez, I need sleep. Duh. Thanks, and sorry to bother everyone with that. :P -- | Andy | e-mail | web | | | andy@lewman.com | www.lewman.com | Bore, n.: A guy who wraps up a two-minute idea in a two-hour vocabulary. -- Walter Winchell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 21: 9:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mostgraveconcern.com (rno-dsl0b-240.gbis.net [216.82.145.240]) by hub.freebsd.org (Postfix) with ESMTP id 05DE037C3AA for ; Wed, 22 Mar 2000 21:09:38 -0800 (PST) (envelope-from dan@mostgraveconcern.com) Received: from danco (danco.mostgraveconcern.com [10.0.0.2]) by mostgraveconcern.com (8.9.3/8.9.3) with SMTP id VAA43030; Wed, 22 Mar 2000 21:09:30 -0800 (PST) (envelope-from dan@mostgraveconcern.com) Message-ID: <021c01bf9485$f84fbe00$0200000a@danco> Reply-To: "Dan O'Connor" From: "Dan O'Connor" To: "Andy" , Subject: Re: cvsup to RELENG_4 = 5.0-CURRENT? Date: Wed, 22 Mar 2000 21:09:30 -0800 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.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >*default release=cvs tag=RELENG_4 >*default delete use-rel-suffix >*default release=cvs tag=. > > My uname -a output is: > >FreeBSD phreakr.lewman.com 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Wed Mar > Did I miss something? Yes. You redefined 'tag=' to be '.', which is 'head', i.e., 5.0-CURRENT. Do this instead: *default release=cvs tag=RELENG_4 *default delete use-rel-suffix *default compress src-all cvs-crypto ports-all tag=. --Dan -- Dan O'Connor On Matters of Most Grave Concern http://www.mostgraveconcern.com -----Original Message----- From: Andy To: stable@FreeBSD.ORG Date: Wednesday, March 22, 2000 8:58 PM Subject: cvsup to RELENG_4 = 5.0-CURRENT? >I just cvsup'd from my freshly installed 4.0 system, using the following >supfile, and now that I reboot, and do a uname -a; I find I am in >5.0-CURRENT? > >supfile is: ># Defaults that apply to all the collections >*default host=cvsup5.FreeBSD.org >*default base=/usr >*default prefix=/usr ># The following line is for 4-stable. If you want 3.x-stable, change ># "RELENG_4" to "RELENG_3". >*default release=cvs tag=RELENG_4 >*default delete use-rel-suffix >*default release=cvs tag=. >*default compress >src-all >cvs-crypto >ports-all > >22 23:44:39 EST 2000 >root@phreakr.lewman.com:/usr/src/sys/compile/PHREAKR i386 > > > Did I miss something? > > >-- > >| Andy | e-mail | web | >| | andy@lewman.com | www.lewman.com | > >Worst Month of the Year: > February. February has only 28 days in it, which means that if >you rent an apartment, you are paying for three full days you don't >get. Try to avoid Februarys whenever possible. > -- Steve Rubenstein > > >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 Mar 22 21: 9:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id 53A2B37BA59 for ; Wed, 22 Mar 2000 21:09:50 -0800 (PST) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id AAA50980; Thu, 23 Mar 2000 00:09:48 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id AAA08707; Thu, 23 Mar 2000 00:09:46 -0500 (EST) Message-Id: <4.2.2.20000323000752.0513a130@mail.sentex.net> X-Sender: mdtancsa@mail.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 23 Mar 2000 00:09:42 -0500 To: Andy From: Mike Tancsa Subject: Re: cvsup to RELENG_4 = 5.0-CURRENT? Cc: stable@freebsd.org In-Reply-To: <38D9A44A.14385938@lewman.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:57 PM 3/22/2000 -0500, Andy wrote: >I just cvsup'd from my freshly installed 4.0 system, using the following >supfile, and now that I reboot, and do a uname -a; I find I am in >5.0-CURRENT? > >supfile is: ># Defaults that apply to all the collections >*default host=cvsup5.FreeBSD.org >*default base=/usr >*default prefix=/usr ># The following line is for 4-stable. If you want 3.x-stable, change ># "RELENG_4" to "RELENG_3". >*default release=cvs tag=RELENG_4 >*default delete use-rel-suffix >*default release=cvs tag=. >*default compress >src-all >cvs-crypto >ports-all > > My uname -a output is: > >FreeBSD phreakr.lewman.com 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Wed Mar >22 23:44:39 EST 2000 >root@phreakr.lewman.com:/usr/src/sys/compile/PHREAKR i386 > > > Did I miss something? > You have >*default release=cvs tag=RELENG_4 >*default release=cvs tag=. I guess it takes the second which is HEAD or current... You want just *default release=cvs tag=RELENG_4 --Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 21:34:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from corinth.bossig.com (corinth.bossig.com [208.26.239.66]) by hub.freebsd.org (Postfix) with ESMTP id E8FCE37B9D5 for ; Wed, 22 Mar 2000 21:34:22 -0800 (PST) (envelope-from kstewart@3-cities.com) Received: from 3-cities.com (kenn3079.bossig.com [208.26.243.79]) by corinth.bossig.com (Rockliffe SMTPRA 3.4.7) with ESMTP id ; Wed, 22 Mar 2000 21:20:50 -0800 Message-ID: <38D9A759.AECD3FEC@3-cities.com> Date: Wed, 22 Mar 2000 21:10:49 -0800 From: Kent Stewart Organization: BOSSig X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Doug Barton Cc: Warner Losh , Vivek Khera , stable@FreeBSD.ORG Subject: Re: "dangerously dedicated" References: <14552.57732.739752.665443@onceler.kcilink.com> <4.3.2.20000321160347.00ad9b20@207.227.119.2> <38D50DBC.88FA8E4D@glue.umd.edu> <38D3AB72.366D851D@glue.umd.edu> <200003152159.OAA89926@harmony.village.org> <38D03E64.3D17FC34@glue.umd.edu> <200003190433.VAA04863@harmony.village.org> <200003212255.PAA26291@harmony.village.org> <200003222301.QAA34410@harmony.village.org> <38D99548.3201BC6D@gorean.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Barton wrote: > > Warner Losh wrote: > > > I didn't say that using da0a is stupid. I said using dangerously > > dedicated mode is stupid. Based on the number of times I've shot > > myself in the foot trying to use dangaerously dedicated devices over > > the years, I'll never use them again. > > I'm curious, what kind of problems have you had, and how is using the > compatability slice an improvement? I've always used "dangerously > dedicated" on my freebsd-only disks, and I've never had a problem. When I first started using FreeBSD back in Feb 99, I tried to use DD disks and the system would not begin the boot process. It would count memory and hang. We are talking about three different drives and the boot would fail if any were DD. It was like the bios queried the HDs and the HD would not respond and the bios just sat there waiting for the response. The second I "fdisk /mbr" the drives the system would boot. The drives that I had these problems with were all Western Digital. Two of them died, one was in warranty and was replaced but while it was in the mail I, replaced it with a Maxtor UDMA 33. It is on the shelf because I can't see replacing a UDMA33 drive with one that only does PIO4. Kent > > Not disagreeing, just curious, > > Doug > -- > "So, the cows were part of a dream that dreamed itself into > existence, > is that possible?" asked the student incredulously. > The master simply replied, "Mu." > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://www.3-cities.com/~kstewart/index.html http://daily.daemonnews.org/ SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 22:15:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.on.home.com (ha1.rdc1.on.wave.home.com [24.2.9.66]) by hub.freebsd.org (Postfix) with ESMTP id 2C27B37B574 for ; Wed, 22 Mar 2000 22:15:23 -0800 (PST) (envelope-from genew@mail.rdc1.on.wave.home.com) Received: from CR121722-a ([24.112.206.235]) by mail.rdc1.on.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <20000323061521.FVAM1324.mail.rdc1.on.home.com@CR121722-a> for ; Wed, 22 Mar 2000 22:15:21 -0800 From: genew@home.com To: FreeBSD-STABLE Date: Thu, 23 Mar 2000 01:20:47 -0500 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: 4.0 - buildworld errors again. X-mailer: Pegasus Mail for Win32 (v3.12b) Message-Id: <20000323061521.FVAM1324.mail.rdc1.on.home.com@CR121722-a> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello folks, First off I want to thank you all for the help I received about the libc.so.4 I did the make install in the lib directory and it worked. now I have a new error cc -c -I/usr/obj/usr/src/gnu/usr.bin/perl/perl -DVERSION=\"0.10\" -DXS_VERSION=\"0.10\" -DPIC -fpic - I/usr/obj/usr/src/gnu/usr.bin/perl/perl -DSDBM -DDUFF hash.c Pid 32977 (perl), uid 0: Exited on signal 11 core dump Segmentation fault - core dumped error code 139 STOP error code 1 I inquired on #freebsd about error code 139 but was told it only goes up to 86. how can I fix this? Gene Wright To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 22 22:56:13 2000 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 562E837C35B for ; Wed, 22 Mar 2000 22:56:08 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id AAA06650; Thu, 23 Mar 2000 00:55:58 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-87.max1.wa.cyberlynk.net(207.227.118.87) by peak.mountin.net via smap (V1.3) id sma006647; Thu Mar 23 00:55:41 2000 Message-Id: <4.3.2.20000323002543.00a99c00@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Thu, 23 Mar 2000 00:55:29 -0600 To: Vivek Khera From: "Jeffrey J. Mountin" Subject: Re: "dangerously dedicated" Cc: stable@FreeBSD.ORG In-Reply-To: <14553.22411.265795.429126@onceler.kcilink.com> References: <200003222301.QAA34410@harmony.village.org> <14552.57732.739752.665443@onceler.kcilink.com> <4.3.2.20000321160347.00ad9b20@207.227.119.2> <38D50DBC.88FA8E4D@glue.umd.edu> <38D3AB72.366D851D@glue.umd.edu> <200003152159.OAA89926@harmony.village.org> <38D03E64.3D17FC34@glue.umd.edu> <200003190433.VAA04863@harmony.village.org> <200003212255.PAA26291@harmony.village.org> <200003222301.QAA34410@harmony.village.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 06:30 PM 3/22/00 -0500, Vivek Khera wrote: >I guess I don't see how to use, eg, da0a without being "dangerously >dedicated". When I did my install of FBSD 3.3, the partitioning >process asked if I was sharing the disk or not. I said no, so it took >over the entire disk, but I still get the long-sliced names like >/dev/wd0s1a rather than the /dev/wd0a I'd expect since there is only >one slice on the whole disk. My zip drive uses /dev/da0a after I did >a newfs on it, though. In fstab you could use wd0a rather than wd0s1a. Is it DD, no. Does it work, yes. Is doing so a good idea, not sure. Just dropped the s1 part from every device in fstab and rebooted with no problem. Not having to 'sh MAKEDEV wds1a' when updating /dev (or adding it to MAKEDEV.local) is about the only advantage, but that doesn't help much since vinum is using the slice versions. Maybe it could use the non-slice versions, but don't care to try at this moment. 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 Wed Mar 22 23: 7: 4 2000 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 E43CB37BA59; Wed, 22 Mar 2000 23:06:57 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id AAA22252; Thu, 23 Mar 2000 00:06:52 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200003230706.AAA22252@freeway.dcfinc.com> Subject: Re: Compiler problems with -O2 (was Re: CVS Trouble, even under 4.0-RELEASE (alpha) HELP!) In-Reply-To: <20000322163007.D21029@fw.wintelcom.net> from Alfred Perlstein at "Mar 22, 0 04:30:07 pm" To: bright@wintelcom.net (Alfred Perlstein) Date: Thu, 23 Mar 2000 00:06:51 -0700 (MST) Cc: blk@skynet.be, obrien@FreeBSD.ORG, howardl@account.abs.net, freebsd-alpha@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com 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 >> I'm sorry, at best here we're talking a few tenths of a >> percentage point of increased speed (if that), and maybe a few >> milliseconds saved -- right? > > Actually the difference between -O and -O2 the times i've looked > at the generated code was substantial, but I guess that brings > along complexity that still needs to be worked out. :( FWIW, I've used -O2 on my 2.2.8-STABLE systems with absolutely no (apparent) problems. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net 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 Mar 22 23:26:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id 0E81937C3CF for ; Wed, 22 Mar 2000 23:26:08 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.231.174]) by smtp04.wxs.nl (Netscape Messaging Server 4.05) with ESMTP id FRV5ZK03.607; Thu, 23 Mar 2000 08:26:08 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id IAA17594; Thu, 23 Mar 2000 08:25:21 +0100 (CET) (envelope-from asmodai) Date: Thu, 23 Mar 2000 08:25:21 +0100 From: Jeroen Ruigrok/Asmodai To: Trenton Schulz Cc: deimos , "Jordan K. Hubbard" , stable@FreeBSD.ORG Subject: Re: What does "Voxware still supported in 4.0" mean exactly? Message-ID: <20000323082521.A17278@daemon.ninth-circle.org> References: <38D9908A.C2D5773D@lewman.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from twschulz@gloria.cord.edu on Wed, Mar 22, 2000 at 10:59:43PM -0600 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000323 08:00], Trenton Schulz (twschulz@gloria.cord.edu) wrote: >Actually, I think you mean Diamond Monster Sound. If it weren't for me >being a poor college student and liking to have sound (at least in Windows >:( ) I would gladly send him my Monster Sound MX300. As it is now, I need >it. Or, bug the manufacturers of those cards into releasing datasheets/programmers documentation. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Any fool can make a rule. And every fool will mind it... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 0:19:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from screech.weirdnoise.com (209-128-78-198.bayarea.net [209.128.78.198]) by hub.freebsd.org (Postfix) with ESMTP id 3CE4137BDE4; Thu, 23 Mar 2000 00:19:09 -0800 (PST) (envelope-from edhall@screech.weirdnoise.com) Received: from screech.weirdnoise.com (localhost [127.0.0.1]) by screech.weirdnoise.com (8.9.3/8.9.3) with ESMTP id AAA12969; Thu, 23 Mar 2000 00:20:06 -0800 Message-Id: <200003230820.AAA12969@screech.weirdnoise.com> X-Mailer: exmh version 2.0.2 To: Andrew Gallatin Cc: obrien@FreeBSD.ORG, Howard Leadmon , freebsd-alpha@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, edhall@screech.weirdnoise.com Subject: Re: Compiler problems with -O2 (was Re: CVS Trouble, even under 4.0-RELEASE (alpha) HELP!) In-Reply-To: Message from Andrew Gallatin of "Wed, 22 Mar 2000 17:42:03 EST." <14553.19348.115781.273817@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Mar 2000 00:20:06 -0800 From: Ed Hall Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Gallatin writes: : I take it the O2 bugs are not unique to us, but rather they are : generic across all OSes that gcc version 2.95.2 runs on? Do the gcc : people know these problems exist? Just FYI, the Linux kernel is compiled with: -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -mno-fp-regs \ -ffixed-8 -fno-strict-aliasing on Alpha, and seems quite stable with these flags. Yes, this is with GCC 2.95.2. On applications, I've seen gains of about 20% for the higher levels of optimization (for example, CSound processes a particular piece in 79 seconds when compiled with just -O, and 65 seconds with -O2). This is a useful improvement, though one that has to be balanced with the risks. I'm frankly astonished that it has been suggested that higher optimizations be disabled. Blindly compiling the world at -O2 may be folly, but using optimization can be quite useful for selected applications. The EGCS (now GCC) group does respond to bug reports, but they are to be forgiven if they give priority to "C code fragment X yields invalid assembler code Y" over "application Z is somehow broken by option W" reports. Like many free software projects (and some not-so-free ones) GCC has a limited number of developers capable of correcting its ills, so I'm sure some extra legwork on our part will increase the chance that issues will be addressed. I'm no stranger to optimizer bugs. But as often as not, the code I've seen fail under optimization is bad code. Optimization moves locals from the stack into registers (and vice-versa), reorders and removes redundant loads and stores, and does other things that cause bugs to surface. This is why it is a good idea to track down, if possible, the actual cause of the failure. -Ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 0:40:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ZGIA.zp.ua (ZGIA.zp.ua [212.35.173.98]) by hub.freebsd.org (Postfix) with ESMTP id 6CDD337BABF for ; Thu, 23 Mar 2000 00:40:28 -0800 (PST) (envelope-from laa@zgia.zp.ua) Received: from localhost (laa@localhost) by ZGIA.zp.ua (8.9.3/8.9.3) with ESMTP id KAA60602; Thu, 23 Mar 2000 10:36:29 +0200 (EET) (envelope-from laa@zgia.zp.ua) Date: Thu, 23 Mar 2000 10:36:29 +0200 (EET) From: Alexandr Listopad To: Andy Cc: stable@FreeBSD.ORG Subject: Re: cvsup to RELENG_4 = 5.0-CURRENT? In-Reply-To: <38D9A44A.14385938@lewman.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 > >I just cvsup'd from my freshly installed 4.0 system, using the following >supfile, and now that I reboot, and do a uname -a; I find I am in >5.0-CURRENT? > >supfile is: ># Defaults that apply to all the collections >*default host=cvsup5.FreeBSD.org >*default base=/usr >*default prefix=/usr ># The following line is for 4-stable. If you want 3.x-stable, change ># "RELENG_4" to "RELENG_3". >*default release=cvs tag=RELENG_4 ^^^^^^^^^^^^ - 1 >*default delete use-rel-suffix >*default release=cvs tag=. ^^^^^ - 2 >*default compress >src-all >cvs-crypto >ports-all > cvsup(1) : Default settings may be specified in a line whose collection name is *default. Such defaults will apply to subsequent lines in the supfile. Multiple *default lines may be present. New values augment or override any defaults specified earlier in the supfile. Values specified explicit- ly for a collection override any default values. you are so lazy... -- Laa. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 1:26:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 1B40437B591 for ; Thu, 23 Mar 2000 01:26:26 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id 69842DAFE; Thu, 23 Mar 2000 10:26:12 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: References: Date: Thu, 23 Mar 2000 09:57:54 +0100 To: "Forrest W. Christian" From: Brad Knowles Subject: Re: Off-topic News: WAS: Re: 3.4-Stable crashes..(heavy diskio+networking) Cc: Christian Jachmann , Carroll Kong , "stable@freebsd.org" Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 5:24 PM -0700 2000/3/22, Forrest W. Christian wrote: > Has there been any progress made on a decent news CACHE software? > > I'd love to try something the likes of nntpcache, but hopefully something > that works better than nntpcache did a couple of years ago. In this role, I think Diablo/dreaderd actually works pretty good. You do have to take a header-only feed from the server that assigns the article ids, but from there the dreaderd servers can pull a copy of the article from any server they know about, and it only needs to support the standard "ARTICLE " command format (which I think all current news spool server software can handle), and then they hand out overview and history from local disk, as well as locally cached articles. I'd encourage you to come to SANE 2000 and attend Joe Greco's presentation that will be describing the large-scale USENET news server system he has built/is building, its architecture, etc.... See in general, and in particular. You might also be interested in Poul-Henning Kamp's presentation "Confining the Omnipotent root", which is going to be describing the new jail() facility in FreeBSD 4.0-STABLE. See for more details. Disclaimer: I am on the Program Committee for SANE 2000, and I am the sponsoring committee member for Joe's presentation as well as Jon Lasser's "Bastille Linux: Security through Transparency" presentation (see for details). -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 2:17:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from student-mailhub.dcu.ie (ns.dcu.ie [136.206.1.3]) by hub.freebsd.org (Postfix) with ESMTP id 3E13037BEFD for ; Thu, 23 Mar 2000 02:17:20 -0800 (PST) (envelope-from drjolt@redbrick.dcu.ie) Received: from enigma.redbrick.dcu.ie (postfix@enigma.redbrick.dcu.ie [136.206.15.5]) by student-mailhub.dcu.ie (8.9.3/8.9.3/893-FD) with ESMTP id KAA22278 for ; Thu, 23 Mar 2000 10:17:17 GMT Received: by enigma.redbrick.dcu.ie (Postfix, from userid 2034) id 09D747CB6; Thu, 23 Mar 2000 10:15:47 +0000 (GMT) Date: Thu, 23 Mar 2000 10:15:46 +0000 From: David Murphy To: stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Message-ID: <20000323101546.A32653@enigma.redbrick.dcu.ie> References: <20000321170118.M5367@enigma.redbrick.dcu.ie> <20000322015400.B34538@enigma.redbrick.dcu.ie> <38D86EF7.2595FA9F@gorean.org> <20000322093709.A48595@enigma.redbrick.dcu.ie> <38D9973E.DF9BCB73@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38D9973E.DF9BCB73@gorean.org>; from Doug@gorean.org on Wed, Mar 22, 2000 at 08:02:06PM -0800 X-no-archive: yes Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting <38D9973E.DF9BCB73@gorean.org> by Doug Barton : > David Murphy wrote: > > > > Quoting <38D86EF7.2595FA9F@gorean.org> > > by Doug Barton : > > > > > Actually what you see on the web page clearly stated in numerous > > > places is that upgrading from source is NOT for the faint of > > > heart. I can't help pointing out that you still haven't referenced any of these numerous places on www.freebsd.org. > I can't help pointing out that you deleted the part of my post > which did refer you to the official freebsd.org site that clearly > describes the recommended upgrading method. You referenced ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/4.0-RELEASE/UPGRADE.TXT, which explains how to perform a binary upgrade of FreeBSD. I made no further reference to that text because, as I (believed I had) clearly explained in comprehensible English, that text isn't anywhere on www.freebsd.org. The manual, in case you're unfamiliar with the new user's general perception of the user manual, is where the new user expects to find the recommended procedures for working on the system. If the manual contains one procedure for upgrading the system, the new user will assume that one procedure is the recommended way to upgrade the system. If the manual contained more than one procedure, it would be necessary for the text of the manual to explicity explain the pros and cons of the different methods of upgrading presented, so that the user could make a decision based on their level of skill between the alternatives presented. However, when alternatives are not presented, when no other upgrade procedures are referenced by the manual, the user will presume that the procedure presented in the manual is recommended and valid for all users. -- When asked if it is true that he uses his wheelchair as a weapon he will reply: "That's a malicious rumour. I'll run over anyone who repeats it." Stephen Hawking - [http://www.smh.com.au/news/0001/07/features/features1.html] David Murphy - For PGP public key, send mail with Subject: send-pgp-key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 2:36:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from yyy.or.jp (mail.yyy.or.jp [202.214.252.21]) by hub.freebsd.org (Postfix) with SMTP id 2D5E437B5D4 for ; Thu, 23 Mar 2000 02:36:45 -0800 (PST) (envelope-from kawai@yyy.or.jp) Received: (qmail 11402 invoked from network); 23 Mar 2000 19:36:43 +0900 Received: from naoko3.yyy.or.jp (HELO Pro233) (210.174.138.136) by mail.yyy.or.jp with SMTP; 23 Mar 2000 19:36:43 +0900 Message-Id: <4.2.0.58.J.20000323193524.00a3bd50@mail.yyy.or.jp> X-Sender: kawai@mail.yyy.or.jp X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J Date: Thu, 23 Mar 2000 19:36:46 +0900 To: freebsd-stable@FreeBSD.org From: Toshifumi Kawai Subject: 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 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 Thu Mar 23 2:53:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from twizors.rug.ac.be (twizors.rug.ac.be [157.193.55.153]) by hub.freebsd.org (Postfix) with ESMTP id 2E60837B6BA for ; Thu, 23 Mar 2000 02:53:47 -0800 (PST) (envelope-from ageorges@twizors.rug.ac.be) Received: from localhost (ageorges@localhost) by twizors.rug.ac.be (8.9.3/8.9.3) with ESMTP id MAA27699 for ; Thu, 23 Mar 2000 12:00:09 +0100 (CET) (envelope-from ageorges@twizors.rug.ac.be) Date: Thu, 23 Mar 2000 12:00:09 +0100 (CET) From: Andy Georges To: freebsd-stable@freeBSD.org Subject: building new kernel before or after installing the world 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'm tracking -stable with this in my supfile *default host=cvsup.nl.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_3 *default delete use-rel-suffix I did not override these settings. in a previous post on this list i've seen the following: > cd /usr/src > make buildworld > make buildkernel > make installkernel > reboot (single) > cd /usr/src > make -k installworld > make installworld (this was for a 3.4 -> 4.0 upgrade.) now the handbook specifies: You should build your new kernel after you have completed make world (or make installworld). If you do not want to do this (perhaps you want to confirm that the kernel builds before updating your system) you may have problems. These may be because your config(8) command is out of date with respect to your kernel sources. so what will it be? (a) make buildworld make installworld make buildkernel or (b) make buildworld make buildkernel make installworld And euhm another small question. I cvsupped my src tree tuesday (with the stable-supfile), but doing a make buildkernel does not work: make: don't know how to make buildkernel. stop. is this because i have to follow (a), or because the dar thingie didn't update my Makefile (it is dated -rw-r--r-- 1 root wheel 5753 Aug 29 1999 /usr/src/Makefile ) When i look on ftp://ftp.freeBSD.org/pub/FreeBSD/FreeBSD-stable/src, the Makefile there has the same date as mine, so I suppose this is a good one. andy ========================================================================== Dept. of Applied Mathematics and Computer Science, University of Ghent Krijgslaan 281 - S9, B - 9000 Ghent, Belgium Phone: +32-9-264.47.66, Fax: +32-9-264.49.95 E-mail: andy.georges@rug.ac.be ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 3:22:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.on.home.com (ha1.rdc1.on.wave.home.com [24.2.9.66]) by hub.freebsd.org (Postfix) with ESMTP id 0574637C40B for ; Thu, 23 Mar 2000 03:22:16 -0800 (PST) (envelope-from genew@mail.rdc1.on.wave.home.com) Received: from CR121722-a ([24.112.206.235]) by mail.rdc1.on.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <20000323112214.GCJV1324.mail.rdc1.on.home.com@CR121722-a> for ; Thu, 23 Mar 2000 03:22:14 -0800 From: genew@home.com To: FreeBSD-STABLE Date: Thu, 23 Mar 2000 06:26:16 -0500 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: additional segmentation faults X-mailer: Pegasus Mail for Win32 (v3.12b) Message-Id: <20000323112214.GCJV1324.mail.rdc1.on.home.com@CR121722-a> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In my previous post I did not notice 2 other places where there were segmentation faults. 1st pid 32875 (perl), uid 0: exited on signal 11 (core dumped) Segmentation fault - core dumped Running '/usr/obj/usr/src/gnu/usr.bin/perl/perl/perl - I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib /usr/obj/usr/src/gnu/usr.bin/perl/perl/lib/ExtUtils/xsubpp -v 2>&1' exits with status 139 at (eval 34) line 17. 2nd (right after) pid 32877 (perl), uid 0: exited on signal 11 (core dumped) Segmentation fault - core dumped Running '/usr/obj/usr/src/gnu/usr.bin/perl/perl/perl /usr/obj/usr/src/gnu/usr.bin/perl/perl/lib/ExtUtils/xsubpp temp000 2>&1' exits with status 139 at (eval 34) line 43. then it proceeds to write the makefile for sdbm and SDBM_File and stops while compiling hash.c with another error code 139 and stops I hope this helps Gene Wright To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 3:45:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 79D3337C42B for ; Thu, 23 Mar 2000 03:45:02 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p34-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.99]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id UAA14483; Thu, 23 Mar 2000 20:44:50 +0900 (JST) Message-ID: <38D9FB58.88B0D750@newsguy.com> Date: Thu, 23 Mar 2000 20:09:12 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: deimos , stable@FreeBSD.ORG Subject: Re: What does "Voxware still supported in 4.0" mean exactly? References: <24240.953782007@zippy.cdrom.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 K. Hubbard" wrote: > > It doesn't support them out of the box now, but I can tell you that > Cameron is certainly working on at least the Soundblaster Live support > since we did send him one and I've heard him complaining bitterly > about it on several occasions. :) If somebody wants to send him > a Diamond Fusion card, I would be happy to "broker" the deal. Yeah, I heard Kris saying she's returning any new card they receive until they receive a set of ear plugs. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@zurichgnomes.bsdconspiracy.net One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 4:11: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sr14.nsw-remote.bigpond.net.au (sr14.nsw-remote.bigpond.net.au [24.192.3.29]) by hub.freebsd.org (Postfix) with ESMTP id 5CFDD37C405 for ; Thu, 23 Mar 2000 04:10:58 -0800 (PST) (envelope-from areilly@nsw.bigpond.net.au) Received: from areilly.bpc-users.org (CPE-144-132-171-71.nsw.bigpond.net.au [144.132.171.71]) by sr14.nsw-remote.bigpond.net.au (Pro-8.9.3/8.9.3) with SMTP id XAA06204 for ; Thu, 23 Mar 2000 23:10:55 +1100 (EDT) Received: (qmail 29999 invoked by uid 1000); 23 Mar 2000 12:10:57 -0000 From: "Andrew Reilly" Date: Thu, 23 Mar 2000 23:10:57 +1100 To: stable@FreeBSD.org Subject: src/UPDATING for RELENG_3 to RELENG_4 upgrade works. Message-ID: <20000323231057.A27794@gurney.reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just thought I'd drop a thank-you note to the relevant gurus. Previous major-number upgrades I've done have always been by binary installation of the base distribution, but this time (mostly on the strength of Jordan's enthusiasm) I thought I'd give the source upgrade route a go. I cvsupped RELENG_4 (and the internat crypto stuff), and followed the directions in UPDATING. Everything seems to have gone beautifully. Even the switch from wd to ad drives. Here are a few minor gotchas I found. Nothing to do with problems in the upgrade process, just things that I found I needed to tweak in my configuration. * You really have to use the make buildkernel method to build the 4.0 kernel. I suspect that that must use the new-but-not-installed config or something. A normal "config GURNEY" in sys/i386/conf didn't work, but "make buildkernel KERNEL=GURNEY" worked for me. * Having a kernel called /GURNEY now, rather than /kernel requires that the file loader.conf.local contains kernel="/GURNEY", otherwise the boot loader will load up the old 3.4-STABLE kernel. * I run qmail, so I had to tweak /etc/mail/mailer.conf to point to /var/qmail/bin/sendmail. I've got mailq and newaliases pointing to /usr/bin/true, since there don't seem to be qmail equivalents. * My 10-baseT ethernet card, a PCI RealTek 8029-based "NE2000 clone" moved from ed1 to ed0, so I had to change rc.conf, start_if.ed1 (and rename it), and my firewall script to accommodate that. * Squid didn't want to run. Something about being unable to run the dnsserver processes. It's possible that that was related to the firewall being broken, but it went away with a pkg_delete and a rebuild. Oh, I was confused for a while by leaving the IPFIREWALL_* and IPDIVERT options out of my new config file (my firewall script bombed), and I had left pcm out too. The PCM device moved from dsp1 to dsp0, so I did a ./MAKEDEV snd0, and all was well there too. (AudioPCI ES1371) Oh: would it be possible to make mergemaster ignore files that differed only in the $FreeBSD$ revision tag? That would save a lot of fairly pointless keying. Thanks again, everyone. -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 5: 0: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id E9AE137BE84; Thu, 23 Mar 2000 04:59:58 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id 6B221181D1; Thu, 23 Mar 2000 13:59:10 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <20000322163007.D21029@fw.wintelcom.net> References: <14552.58589.119082.742615@grasshopper.cs.duke.edu> <200003222003.PAA51043@account.abs.net> <20000322130901.A97411@dragon.nuxi.com> <20000322163007.D21029@fw.wintelcom.net> Date: Thu, 23 Mar 2000 13:58:11 +0100 To: Alfred Perlstein From: Brad Knowles Subject: Re: Compiler problems with -O2 (was Re: CVS Trouble, even under 4.0-RELEASE (alpha) HELP!) Cc: obrien@FreeBSD.ORG, Howard Leadmon , freebsd-alpha@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:30 PM -0800 2000/3/22, Alfred Perlstein wrote: > Actually the difference between -O and -O2 the times i've looked > at the generated code was substantial, but I guess that brings > along complexity that still needs to be worked out. :( I don't suppose you know of a web page that summarizes these kinds of results, do you? I'd be curious to see what kinds of optimizations might make what kinds of differences with what kinds of applications, the kernel, etc.... Thanks! -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 5: 0:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 794BD37C496; Thu, 23 Mar 2000 05:00:12 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id 9F1A71813F; Thu, 23 Mar 2000 13:59:00 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <200003230820.AAA12969@screech.weirdnoise.com> References: <200003230820.AAA12969@screech.weirdnoise.com> Date: Thu, 23 Mar 2000 13:57:06 +0100 To: Ed Hall , Andrew Gallatin From: Brad Knowles Subject: Re: Compiler problems with -O2 (was Re: CVS Trouble, even under 4.0-RELEASE (alpha) HELP!) Cc: obrien@FreeBSD.ORG, Howard Leadmon , freebsd-alpha@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, edhall@screech.weirdnoise.com Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:20 AM -0800 2000/3/23, Ed Hall wrote: > I'm frankly astonished that it has been suggested that higher optimizations > be disabled. Blindly compiling the world at -O2 may be folly, but using > optimization can be quite useful for selected applications. In all seriousness, I'd be just as happy to have extremely strong warnings against using anything but -O by default (i.e., setting it in /etc/make.conf or setting "makeoptions" in your kernel configuration), with the caveat that the potential consequences can be exceptionally dire (such as having your entire machine toasted, etc...) if you decide that you want to take the risk and build your kernel with "-O2 -march=pentium" or whatever. People should be able to use whatever optimization they want on userland programs, and if they're stupid enough to aim thermonuclear weapons at their feet when doing the same with the kernel, well then maybe the Darwin effect will help the rest of us get a little more sleep. ;-) -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 5:29:43 2000 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 4292137C462 for ; Thu, 23 Mar 2000 05:29:41 -0800 (PST) (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 FAA23104; Thu, 23 Mar 2000 05:27:21 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda23102; Thu Mar 23 05:27:09 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id FAA03868; Thu, 23 Mar 2000 05:27:08 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdxW3865; Thu Mar 23 05:26:51 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id FAA00923; Thu, 23 Mar 2000 05:26:50 -0800 (PST) Message-Id: <200003231326.FAA00923@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdUuI918; Thu Mar 23 05:26:24 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: "Daniel C. Sobral" Cc: "Jordan K. Hubbard" , Thomas David Rivers , witr@rwwa.com, stable@FreeBSD.ORG, witr@pobox.rwwa.com Subject: Re: V4.0 and Walnut Creek Subscriptions... In-reply-to: Your message of "Thu, 23 Mar 2000 10:16:25 +0900." <38D97069.C5811525@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Mar 2000 05:26:24 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38D97069.C5811525@newsguy.com>, "Daniel C. Sobral" writes: > "Jordan K. Hubbard" wrote: > > > > No, you won't get two copies. > > Just charged twice. ;-> What? Are you saying WC is actually a law firm? Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC 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 Thu Mar 23 5:59:32 2000 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 285F737B5E9 for ; Thu, 23 Mar 2000 05:59:27 -0800 (PST) (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 FAA23151; Thu, 23 Mar 2000 05:59:22 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda23147; Thu Mar 23 05:59:09 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id FAA03958; Thu, 23 Mar 2000 05:59:09 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdJK3956; Thu Mar 23 05:58:51 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id FAA01112; Thu, 23 Mar 2000 05:58:50 -0800 (PST) Message-Id: <200003231358.FAA01112@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdAQ1106; Thu Mar 23 05:57:54 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: Vivek Khera Cc: stable@FreeBSD.ORG Subject: Re: "dangerously dedicated" In-reply-to: Your message of "Wed, 22 Mar 2000 18:30:19 EST." <14553.22411.265795.429126@onceler.kcilink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Mar 2000 05:57:54 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14553.22411.265795.429126@onceler.kcilink.com>, Vivek Khera writes: > >>>>> "WL" == Warner Losh writes: > > WL> I didn't say that using da0a is stupid. I said using dangerously > WL> dedicated mode is stupid. Based on the number of times I've shot > > I guess I don't see how to use, eg, da0a without being "dangerously > dedicated". When I did my install of FBSD 3.3, the partitioning > process asked if I was sharing the disk or not. I said no, so it took > over the entire disk, but I still get the long-sliced names like > /dev/wd0s1a rather than the /dev/wd0a I'd expect since there is only > one slice on the whole disk. My zip drive uses /dev/da0a after I did > a newfs on it, though. > > WL> FreeBSD lets you do this as well. Are you sure that Linux doesn't > WL> require fdisk disks? Linux/i386 doesn't have another form of disk > > Linux requires it to run, but doesn't hang forever if it doesn't > exist. FreeBSD is the only system I've encountered so far that will > lock up (ie, does not respond to any keyboard requests or terminate > its probe) when scanning a disk without an FDISK table. I needed to > use freedos to add one to this particular drive. What's there to scan? The MBR always lives on the first sector of the disk. If it hung it was the BIOS that hung because it had nothing else to do. Do you understand how the MBR works? I didn't think so. Well here's a course in MBR 101. We'll have a test on this material on Friday. 1. BIOS reads the first sector of the disk. 2. If the last byte of the sector != 0xaa55, stop and hang 3. If the MBR checksum doesn't match the MBR, stop and hang. (Some BIOSes skip this step or just complain that that a virus has been installed and continue to boot anyway). 4. Jump to the MBR and start executing it. 5. The MBR will scan it's table of four entries and load the boot record from the partition that is marked active. 6. The MBR will test the last byte of the sector it just loaded for 0xaa55. If it's 0xaa55 and if the checksum matches (some MBR's don't bother to check the checksum), it will jump to the boot record. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC 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 Thu Mar 23 6:17:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rock.ghis.net (rock.ghis.net [209.222.164.7]) by hub.freebsd.org (Postfix) with ESMTP id 59E0937C4AD for ; Thu, 23 Mar 2000 06:17:20 -0800 (PST) (envelope-from will@blackdawn.com) Received: from argon.blackdawn.com (deepspace9.dcds.edu [207.231.151.2]) by rock.ghis.net (8.9.3/8.9.3) with ESMTP id GAA33137; Thu, 23 Mar 2000 06:16:30 -0800 (PST) Received: by argon.blackdawn.com (Postfix, from userid 1000) id 4F27F19E0; Thu, 23 Mar 2000 09:15:53 -0500 (EST) Date: Thu, 23 Mar 2000 09:15:53 -0500 From: Will Andrews To: "Daniel C. Sobral" Cc: "Jordan K. Hubbard" , deimos , stable@FreeBSD.ORG Subject: Re: What does "Voxware still supported in 4.0" mean exactly? Message-ID: <20000323091553.G422@argon.blackdawn.com> References: <24240.953782007@zippy.cdrom.com> <38D9FB58.88B0D750@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38D9FB58.88B0D750@newsguy.com>; from dcs@newsguy.com on Thu, Mar 23, 2000 at 08:09:12PM +0900 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 23, 2000 at 08:09:12PM +0900, Daniel C. Sobral wrote: > Yeah, I heard Kris saying she's returning any new card they receive > until they receive a set of ear plugs. :-) *cough* nothing better than builtin earplugs. ;-> > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > capo@zurichgnomes.bsdconspiracy.net *cough* -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 6:27: 6 2000 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 850C437C45B; Thu, 23 Mar 2000 06:26:58 -0800 (PST) (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 GAA23245; Thu, 23 Mar 2000 06:26:23 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda23243; Thu Mar 23 06:26:15 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id GAA04097; Thu, 23 Mar 2000 06:26:15 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdNP4095; Thu Mar 23 06:25:51 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id GAA01222; Thu, 23 Mar 2000 06:25:51 -0800 (PST) Message-Id: <200003231425.GAA01222@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdCH1214; Thu Mar 23 06:24:55 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: Andrew Gallatin Cc: obrien@FreeBSD.ORG, Howard Leadmon , freebsd-alpha@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Compiler problems with -O2 (was Re: CVS Trouble, even under 4.0-RELEASE (alpha) HELP!) In-reply-to: Your message of "Wed, 22 Mar 2000 17:42:03 EST." <14553.19348.115781.273817@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Mar 2000 06:24:54 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14553.19348.115781.273817@grasshopper.cs.duke.edu>, Andrew Gallatin writes: > > David O'Brien writes: > > On Wed, Mar 22, 2000 at 03:03:09PM -0500, Howard Leadmon wrote: > > > want to avoid, or at least note the problem with -O2 as I have been usin > g > > > that when making software on my Intel machines for a long time, so just > > > assumed it was OK to do the same on the Alpha.. > > > > It isn't officially OK from the perspective of the FreeBSD Project. "-O2" > > has been the cause of problems on the i386 arch too. Thus my constant > > yelling about it that nobody pays attention to. > > > > I'm on the virge of turning off "-O2" on both Alpha and i386. > > You certainly have my vote. > > I take it the O2 bugs are not unique to us, but rather they are > generic across all OSes that gcc version 2.95.2 runs on? Do the gcc > people know these problems exist? How about a compromise? Just print a nasty message every time -O2 is specified: BEWARE: -O2 may cause some applications to break or may cause your system to fail to boot. Be sure you absolutely know what you are doing before using -O2 optimisation. Then enclose it in stars (*) or bangs (!). Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC 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 Thu Mar 23 6:36: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dfw7-1.relay.mail.uu.net (dfw7-1.relay.mail.uu.net [199.171.54.106]) by hub.freebsd.org (Postfix) with ESMTP id 50ABC37C495 for ; Thu, 23 Mar 2000 06:35:58 -0800 (PST) (envelope-from boyd@vacationclub.com) Received: from mcnc-mdm1-ex07.marriott.com by dfw7sosrv11.alter.net with ESMTP (peer crosschecked as: host036.marriott.com [162.130.1.36]) id QQihtq10432 for ; Thu, 23 Mar 2000 14:35:55 GMT Received: from oberon.vacationclub.com (172.16.24.79 [172.16.24.79]) by mcnc-mdm1-ex07.marriott.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id HKTMZ5YR; Thu, 23 Mar 2000 09:35:42 -0500 Received: (from boyd@localhost) by oberon.vacationclub.com (8.9.3/8.9.3) id JAA19289; Thu, 23 Mar 2000 09:35:50 -0500 (EST) (envelope-from boyd) Date: Thu, 23 Mar 2000 09:35:50 -0500 (EST) Message-Id: <200003231435.JAA19289@oberon.vacationclub.com> To: freebsd-stable@freebsd.org Subject: When to remove .ctm-status? From: Daniel Boyd Reply-To: Daniel Boyd Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I want a src-4 tree. I am following this procedure: 1. Apply src-cur deltas up to src-cur.4274.gz. 2. Apply src-4.0000.from-src-cur.4274.gz. 3. Apply src-4.0001.gz. (and carry on with src-4.0002, etc.) Two questions: 1. When do I remove .ctm-status? 2. As a check, what should I see in .ctm-status after step 3? -- Daniel F. Boyd, UNIX System Administrator, Marriott Vacation Club 1200 US 98 South, Suite 23 / Lakeland FL 33801 / 941-688-7700 x4875 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 6:39:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lowrider.lewman.org (lowrider.lewman.org [209.67.240.52]) by hub.freebsd.org (Postfix) with ESMTP id 645F637B6DD for ; Thu, 23 Mar 2000 06:39:22 -0800 (PST) (envelope-from deimos@lowrider.lewman.org) Received: from localhost (deimos@localhost) by lowrider.lewman.org (8.9.3/8.9.3) with ESMTP id JAA76604; Thu, 23 Mar 2000 09:40:27 -0500 (EST) (envelope-from deimos@lowrider.lewman.org) Date: Thu, 23 Mar 2000 09:40:27 -0500 (EST) From: deimos To: Alexandr Listopad Cc: stable@FreeBSD.ORG Subject: Re: cvsup to RELENG_4 = 5.0-CURRENT? 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 Thu, 23 Mar 2000, Alexandr Listopad wrote: > >*default release=cvs tag=. > ^^^^^ - 2 > > >*default compress > >src-all > >cvs-crypto > >ports-all > > > > cvsup(1) : > > Default settings may be specified in a line whose collection name is > *default. Such defaults will apply to subsequent lines in the supfile. > Multiple *default lines may be present. New values augment or override > any defaults specified earlier in the supfile. Values specified explicit- > ly for a collection override any default values. > > > you are so lazy... Ya know, I did realize I made a mistake, and apologized for the WOB. I haven't done a dumb thing like this since 2.2, forgive me for not being perfect. Jeez. -- | Andy | e-mail | web | finger | | | andy@lewman.com | www.lewman.com | alewman@shore.net | "... an experienced, industrious, ambitious, and often quite often picturesque liar." -- Mark Twain To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 7:41:32 2000 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 74D1137B5C3 for ; Thu, 23 Mar 2000 07:41:28 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id HAA60696; Thu, 23 Mar 2000 07:41:13 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200003231541.HAA60696@gndrsh.dnsmgr.net> Subject: Re: "dangerously dedicated" In-Reply-To: <200003231358.FAA01112@cwsys.cwsent.com> from Cy Schubert - ITSD Open Systems Group at "Mar 23, 2000 05:57:54 am" To: Cy.Schubert@uumail.gov.bc.ca (Cy Schubert - ITSD Open Systems Group) Date: Thu, 23 Mar 2000 07:41:13 -0800 (PST) Cc: khera@kciLink.com (Vivek Khera), 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 ... > What's there to scan? The MBR always lives on the first sector of the > disk. If it hung it was the BIOS that hung because it had nothing else > to do. > > Do you understand how the MBR works? I didn't think so. Well here's a > course in MBR 101. We'll have a test on this material on Friday. And here is the matterial for MBR 102... 0. Set the drive list to those devices found by the hardware POST, commonly 0x01, 0x80, 0x81 for a floppy and dual hardrive machine. > 1. BIOS reads the first sector of the disk. > > 2. If the last byte of the sector != 0xaa55, stop and hang 2. If the last byte of the sector != 0xaa55 go to the next drive in the drive list and back step 1, if this was the last drive on the list print an error and hang. > 3. If the MBR checksum doesn't match the MBR, stop and hang. (Some > BIOSes > skip this step or just complain that that a virus has been installed > and continue to boot anyway). 3. If the checksum fails go to the next drive in the drive list and back to step 1. Very few bioses do not check the checksum. > 4. Jump to the MBR and start executing it. 4. Jump to the MBR code loaded, hang here if we loaded garbage from the disk drive usually. (Ie, signature 0xaa55 is present and checksum was good, but the MBR code itself is toasted.) > 5. The MBR will scan it's table of four entries and load the boot > record > from the partition that is marked active. Some MBR's hang here if no valid partition table, or more than one marked active. > 6. The MBR will test the last byte of the sector it just loaded for > 0xaa55. > If it's 0xaa55 and if the checksum matches (some MBR's don't bother > to > check the checksum), it will jump to the boot record. If the boot record is toast hang here.... The major error in MBR 101 is that it is not the BIOS that usually hangs, they are fairly well behaved, is what hangs is the code loaded from the hard drive and jumped to in 4 or 6. -- 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 Thu Mar 23 8:26:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dragonfire.penguinpowered.com (dragonfire.reno.nv.us [207.228.2.94]) by hub.freebsd.org (Postfix) with SMTP id D5D9F37B66B for ; Thu, 23 Mar 2000 08:26:40 -0800 (PST) (envelope-from gibbons@dragonfire.penguinpowered.com) Received: (qmail 91974 invoked by uid 0); 23 Mar 2000 16:26:38 -0000 Received: from localhost (127.0.0.1) by localhost with SMTP; 23 Mar 2000 16:26:38 -0000 To: freebsd-stable@freebsd.org Subject: No KERBEROS4 support in rshd & rlogind (4.0S) X-Mailer: Mew version 1.94.1 on XEmacs 21.1 (Canyonlands) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000323082638X.gibbons@dragonfire.penguinpowered.com> Date: Thu, 23 Mar 2000 08:26:38 -0800 From: Christopher J.Gibbons X-Dispatcher: imput version 20000228(IM140) Lines: 91 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think I found a problem with the Kerberos4 builds of rshd and rlogind in 4.0-Stable (cvsup'd early this morning too). When I enable MAKE_KERBEROS4=yes in /etc/make.conf, it builds the kerberos4 binaries: ksrvutil, kerberos, kadmind, etc. However, the rshd and rlogind binaries are still the non-kerberized versions. NOTE, that rsh and rlogin themselves have kerberos support, it is simply their daemon counterparts that are lacking kerberos. Here is the output of doing a rsh and rlogin into my master server from itself with valid tickets. [gibbons@hercules gibbons]$ rsh hercules date rsh: kcmd: connection unexpectedly closed. rsh: warning, using standard rsh: can't provide Kerberos auth data The corresponding /var/log/messages entry: Mar 23 08:12:52 hercules rshd[91934]: usage: rshd [-alnDL] Mar 23 08:12:52 hercules rshd[91935]: auth_pam: Permission denied Mar 23 08:12:52 hercules rshd[91935]: PAM authentication failed Notice the usage output--it is not accepting the kerberos flag (-k) from inetd.conf. Hence, I believe the PAM errors are simply a condition of the rshd command spitting out a usage message. ldd's of the binaries show they do not have the kerberos or crypto libraries compiled in either: /usr/libexec/rshd: libpam.so.1 => /usr/lib/libpam.so.1 (0x28066000) libutil.so.3 => /usr/lib/libutil.so.3 (0x2806f000) libc.so.4 => /usr/lib/libc.so.4 (0x28079000) /usr/libexec/rlogind: libutil.so.3 => /usr/lib/libutil.so.3 (0x28066000) libpam.so.1 => /usr/lib/libpam.so.1 (0x28070000) libc.so.4 => /usr/lib/libc.so.4 (0x28079000) However, kerberized telnet works just fine: [gibbons@hercules gibbons]$ telnet -a hercules Trying 192.168.0.1... Connected to hercules.dragonfire.penguinpowered.com. Escape character is '^]'. [ Trying KERBEROS4 ... ] [ Kerberos V4 accepts you ] [ Kerberos V4 challenge successful ] Last login: Thu Mar 23 08:18:35 from hercules Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.0-STABLE (HERCULES) #0: Wed Mar 22 15:38:10 PST 2000 Welcome to FreeBSD! Secondly, "passwd" generates the following errors when a user tries to change their kerberos password, yet it may be related to rsh and rlogin not working properly: [gibbons@hercules gibbons]$ passwd realm DRAGONFIRE.PENGUINPOWERED.COM Old password for gibbons: New Password for gibbons: Verifying password - New Password for gibbons: Verify failure Error reading new password, password unchanged. [gibbons@hercules gibbons]$ passwd realm DRAGONFIRE.PENGUINPOWERED.COM Old password for gibbons: New Password for gibbons: Verifying password - New Password for gibbons: passwd in free(): warning: junk pointer, too high to make sense. kpasswd: Couldn't access ticket file attempting to change password. Password NOT changed. Kerberos logs the attempt to change a password, but there is nothing else in the log files to indicate anything failed for the passwd change. I wish I could have provided a fix or patch diffs, rather than simply pointing out what looks like a bug. Thanks!!! /----------------------------------------------------------------------- | Christopher J. Gibbons UNIX Systems Admin. gibbons@cs.unr.edu |----------------------------------------------------------------------- | "Discovered that neither the Mossad nor Cuba were willing to pay a | living wage for computer espionage. Fell into System Administration." \----------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 8:49:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.WorldMediaCo.com (mail.pro-privacy.com [63.64.101.17]) by hub.freebsd.org (Postfix) with ESMTP id A0AFC37C4C6 for ; Thu, 23 Mar 2000 08:49:20 -0800 (PST) (envelope-from jogorman@worldmediaco.com) Received: from elwood.net ([63.64.101.10]) by mail1.WorldMediaCo.com (Post.Office MTA v3.5.3 release 223 ID# 0-55573U2500L250S0V35) with ESMTP id com; Thu, 23 Mar 2000 10:15:43 -0600 Message-ID: <38DA4B34.179C6AD1@elwood.net> Date: Thu, 23 Mar 2000 10:49:56 -0600 From: jogorman@worldmediaco.com (WMC, O'Gorman, James) X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Andrew Reilly Cc: stable@FreeBSD.org Subject: Re: src/UPDATING for RELENG_3 to RELENG_4 upgrade works. References: <20000323231057.A27794@gurney.reilly.home> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Reilly wrote: > > I just thought I'd drop a thank-you note to the relevant gurus. > Previous major-number upgrades I've done have always been by binary > installation of the base distribution, but this time (mostly on > the strength of Jordan's enthusiasm) I thought I'd give the source > upgrade route a go. I cvsupped RELENG_4 (and the internat crypto > stuff), and followed the directions in UPDATING. Everything seems > to have gone beautifully. Even the switch from wd to ad drives. I have to second that. I upgraded last night as well, and really I do not see what all the fuss is about. I first installed a new GENERIC and booted off that, then when that was done, I installed my custom kernel. Things went great. And there is alot of improvment, boot times are great now. The one and only problem that I have had that I have not fixed yet is with xdm. I had started it from rc.local before, but now when rc.local starts is, the keyboard will not interact with it. If I comment out that line, boot up normal and log in as root and then start xdm things are fine. I have not put any effort into fixing it yet, so I am sure it is something simple I am missing. All in all, I have thank all members of the FreeBSD team for making a upgrade via-source path that is quick, painless and works. Great job. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 8:55: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id 12A2337C4F4 for ; Thu, 23 Mar 2000 08:54:59 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (mi@rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id LAA47896; Thu, 23 Mar 2000 11:54:50 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id LAA28916; Thu, 23 Mar 2000 11:54:50 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <200003231654.LAA28916@rtfm.newton> Subject: starting xdm (Re: src/UPDATING for RELENG_3 to RELENG_4 upgrade works.) In-Reply-To: <38DA4B34.179C6AD1@elwood.net> from "WMC, O'Gorman, James" at "Mar 23, 2000 10:49:56 am" To: "WMC, O'Gorman, James" Date: Thu, 23 Mar 2000 11:54:50 -0500 (EST) Cc: stable@freebsd.org X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"; Thu, 23 Mar 2000 08:59:31 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id JAA23713; Thu, 23 Mar 2000 09:58:40 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200003231658.JAA23713@freeway.dcfinc.com> Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) In-Reply-To: <20000323101546.A32653@enigma.redbrick.dcu.ie> from David Murphy at "Mar 23, 0 10:15:46 am" To: drjolt@redbrick.dcu.ie (David Murphy) Date: Thu, 23 Mar 2000 09:58:40 -0700 (MST) Cc: stable@FreeBSD.ORG Reply-To: chad@DCFinc.com 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 Murphy wrote: > The manual, in case you're unfamiliar with the new user's general > perception of the user manual, is where the new user expects to find > the recommended procedures for working on the system. If the manual > contains one procedure for upgrading the system, the new user will > assume that one procedure is the recommended way to upgrade the > system. If the manual contained more than one procedure, it would be > necessary for the text of the manual to explicity explain the pros and > cons of the different methods of upgrading presented, so that the user > could make a decision based on their level of skill between the > alternatives presented. However, when alternatives are not presented, > when no other upgrade procedures are referenced by the manual, the > user will presume that the procedure presented in the manual is > recommended and valid for all users. As has been mentioned before, the documentation group would be grateful for any patches you'd like to submit. In fact, someone even offered to convert plain text from you into SGML and edit/commit it. Perhaps you've lost sight of the fact that the whole FreeBSD project is, outside of a very few guiding entities, done by volunteers. So, if you see something you think is wrong, and you feel strongly about it, volunteer. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net 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 Mar 23 9: 4:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from thehousleys.net (frenchknot.ne.mediaone.net [24.147.224.201]) by hub.freebsd.org (Postfix) with ESMTP id 3875D37BA4D for ; Thu, 23 Mar 2000 09:04:14 -0800 (PST) (envelope-from jim@thehousleys.net) Received: from thehousleys.net (housley@baby.int.thehousleys.net [192.168.0.24]) by thehousleys.net (8.9.3/8.9.3) with ESMTP id MAA25726; Thu, 23 Mar 2000 12:04:08 -0500 (EST) Message-ID: <38DA4E88.A8466B45@thehousleys.net> Date: Thu, 23 Mar 2000 12:04:08 -0500 From: James Housley Organization: The Housleys dot Net X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mikhail Teterin , freebsd-stable@freebsd.org Subject: Re: starting xdm (Re: src/UPDATING for RELENG_3 to RELENG_4 upgrade works.) References: <200003231654.LAA28916@rtfm.newton> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin wrote: > > I had that problem -- don't know why, but if you put a 1 or 2 second > delay into the rc.local before xdm it will start nicely. > I have needed up to 10secs (older 486DX4) to start xdm since 2.2.5 Jim -- Nothing is fool proof, because fools are too ingenious. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 9: 9:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pan.ch.intel.com (pan.ch.intel.com [143.182.246.24]) by hub.freebsd.org (Postfix) with ESMTP id 9A42337B5A4 for ; Thu, 23 Mar 2000 09:09:46 -0800 (PST) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by pan.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.19 2000/01/29 00:15:43 dmccart Exp $) with ESMTP id KAA03079 for ; Thu, 23 Mar 2000 10:09:29 -0700 (MST) Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id KAA06623 for ; Thu, 23 Mar 2000 10:08:24 -0700 (MST) X-Envelope-To: X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id MAA26842; Thu, 23 Mar 2000 12:09:28 -0500 (EST) X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14554.20424.548258.530333@hip186.ch.intel.com> Date: Thu, 23 Mar 2000 10:09:28 -0700 (MST) To: stable@freebsd.org Subject: Re: What does "Voxware still supported in 4.0" mean exactly? In-Reply-To: <24240.953782007@zippy.cdrom.com> References: <38D98CD6.BFAB40BD@lewman.org> <24240.953782007@zippy.cdrom.com> X-Mailer: VM 6.75 under Emacs 20.3.11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Wednesday, March 22, Jordan K. Hubbard wrote: ] > > What about those of us with AWE64 GOLD boards? The board itself does > > quite well with most PCI based boards available today. As for upgrades, > > would a Vibra16 really count as an upgrade? > > Why not send us one and we'll have Cameron Grant look at it? He is > somewhat constrained by the hardware available to him, and being off > in the UK and stuck in a wheelchair to boot doesn't exactly give him > the best access. > > > If we're going to be forced to use newer boards, what about > > SoundBlaster Live, Diamond Fusion, and other modern Aureal/Dolby based > > PCI sound boards? Will pcm support those out of the box, or are we now > > going to have to wait for some other driver to be developed? > > It doesn't support them out of the box now, but I can tell you that > Cameron is certainly working on at least the Soundblaster Live support > since we did send him one and I've heard him complaining bitterly > about it on several occasions. :) If somebody wants to send him > a Diamond Fusion card, I would be happy to "broker" the deal. The following is not venom directed at jkh, or anybody in general--it is an honest question/statement/opinion: Rather than having a user send Cameron Grant a Diamond Fusion Card, or any other "bleeding edge" or "old 'n' crusty" sound card to play with, shouldn't FreeBSD, Inc. or Walnut Creek itself be proactively shipping willing developers like this all the hardware they can purchase? I know that it is done, has been done, and will continue to be done--it just seems to me like another appropriate time to spend <= $100US from the profits generated by CD sales. There are many many of us who faithfully buy the CD subscription and basically use the discs as shiny playtoys for our toddlers. I will continue to buy it too because "money gets rolled back into the project for further development" and with such limited time, that's how I "support" FreeBSD (along with evangelism being the only "FreeBSD leper" here at work amongst the Linux-ites). I think that users sending people who have the time and talent for writing drivers for the hardware is a grand idea. But, I think an equally grand idea is onsie-twosie hardware (such as sound cards, NICs, etc.) being purchased by Walnut Creek and/or FreeBSD, Inc. "automatically." Comments? (again, this is not meant to be accusatory to jkh or anybody specifically, and I'm not asking for "justification of my CD purchase" in any way ... just stating my US $0.02). Cheers, -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 9:12:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.WorldMediaCo.com (mail.pro-privacy.com [63.64.101.17]) by hub.freebsd.org (Postfix) with ESMTP id 6F7F037BCD5 for ; Thu, 23 Mar 2000 09:12:06 -0800 (PST) (envelope-from jogorman@worldmediaco.com) Received: from elwood.net ([63.64.101.10]) by mail1.WorldMediaCo.com (Post.Office MTA v3.5.3 release 223 ID# 0-55573U2500L250S0V35) with ESMTP id com for ; Thu, 23 Mar 2000 10:38:25 -0600 Message-ID: <38DA5086.9C80CF2@elwood.net> Date: Thu, 23 Mar 2000 11:12:38 -0600 From: jogorman@worldmediaco.com (WMC, O'Gorman, James) X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en,pdf MIME-Version: 1.0 To: stable@freebsd.org Subject: Re: starting xdm (Re: src/UPDATING for RELENG_3 to RELENG_4 upgrade works.) References: <200003231654.LAA28916@rtfm.newton> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin wrote: > right way is, probably, to fire it from /etc/ttys -- see the xdm > entry there and change ``off'' to ``on''... Then (if you do not have > X running) ``kill -1 1''. I have to thank Alan and Mikhail both for sending me this answer. It will save me some time tonight. Thanks! Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 9:59:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mg-20425418-10.ricochet.net [204.254.18.10]) by hub.freebsd.org (Postfix) with ESMTP id A19B537BEC9 for ; Thu, 23 Mar 2000 09:59:49 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA01088; Thu, 23 Mar 2000 10:01:28 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003231801.KAA01088@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Reynolds~ Cc: stable@freebsd.org Subject: Re: What does "Voxware still supported in 4.0" mean exactly? In-reply-to: Your message of "Thu, 23 Mar 2000 10:09:28 MST." <14554.20424.548258.530333@hip186.ch.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Mar 2000 10:01:27 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The following is not venom directed at jkh, or anybody in general--it is an > honest question/statement/opinion: > > Rather than having a user send Cameron Grant a Diamond Fusion Card, or any > other "bleeding edge" or "old 'n' crusty" sound card to play with, shouldn't > FreeBSD, Inc. or Walnut Creek itself be proactively shipping willing > developers like this all the hardware they can purchase? I know that it is > done, has been done, and will continue to be done--it just seems to me like > another appropriate time to spend <= $100US from the profits generated by CD > sales. What makes you think that we haven't? The problem is simply that it's very hard to _buy_ a lot of these cards, and if someone already has one, asking them to send it to Cameron is a lot more effective than wasting a day of my or Bill Swingle's time trying to find the one yak repair shop and soundcard dealer in Outer Mongolia that still has one in stock, finding some way of paying them in goat's cheese and then having Ghengis Khan's last living relative stick the card into his yakskin bag and storm all the way across Europe to deliver it. At last count, I think we've bought, borrowed and cajoled about twenty or so cards and sent them off to Cameron. I don't know what makes you think that we're _entirely_ stupid or greedy, especially since it's not like it's a secret or anything that we do this regularly. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 10:23:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pan.ch.intel.com (pan.ch.intel.com [143.182.246.24]) by hub.freebsd.org (Postfix) with ESMTP id 9FA2937C4C6 for ; Thu, 23 Mar 2000 10:23:12 -0800 (PST) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by pan.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.19 2000/01/29 00:15:43 dmccart Exp $) with ESMTP id LAA29747 for ; Thu, 23 Mar 2000 11:23:10 -0700 (MST) Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id LAA23651 for ; Thu, 23 Mar 2000 11:22:06 -0700 (MST) X-Envelope-To: X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id NAA29440; Thu, 23 Mar 2000 13:23:10 -0500 (EST) X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14554.24845.963542.299903@hip186.ch.intel.com> Date: Thu, 23 Mar 2000 11:23:09 -0700 (MST) To: stable@freebsd.org Subject: hardware (was: What does "Voxware still supported in 4.0" mean exactly?) In-Reply-To: <200003231801.KAA01088@mass.cdrom.com> References: <14554.20424.548258.530333@hip186.ch.intel.com> <200003231801.KAA01088@mass.cdrom.com> X-Mailer: VM 6.75 under Emacs 20.3.11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Thursday, March 23, Mike Smith wrote: ] > > The following is not venom directed at jkh, or anybody in general--it is an > > honest question/statement/opinion: > > > > Rather than having a user send Cameron Grant a Diamond Fusion Card, or any > > other "bleeding edge" or "old 'n' crusty" sound card to play with, shouldn't > > FreeBSD, Inc. or Walnut Creek itself be proactively shipping willing > > developers like this all the hardware they can purchase? I know that it is > > done, has been done, and will continue to be done--it just seems to me like > > another appropriate time to spend <= $100US from the profits generated by CD > > sales. > > What makes you think that we haven't? The problem is simply that it's > very hard to _buy_ a lot of these cards, and if someone already has one, > asking them to send it to Cameron is a lot more effective than wasting a > day of my or Bill Swingle's time trying to find the one yak repair shop > and soundcard dealer in Outer Mongolia that still has one in stock, > finding some way of paying them in goat's cheese and then having Ghengis > Khan's last living relative stick the card into his yakskin bag and storm > all the way across Europe to deliver it. > > At last count, I think we've bought, borrowed and cajoled about twenty or > so cards and sent them off to Cameron. I don't know what makes you think > that we're _entirely_ stupid or greedy, especially since it's not like > it's a secret or anything that we do this regularly. > JUST HOLD ON THERE TEX!!!!!!! The first line of my message was: > > The following is not venom directed at jkh, or anybody in general--it is an repeat: "not venom". Also read in my message that I said I *know* that it is regularly done (buying hardware and shipping it to developers). Read what I said, then post your comments. A more appropriate response would have simply been "some older cards are harder to find, if you or anyone within earshot of this message has one we could use or buy, please let us know so we can continue our regular program of buying hardware for developers." Are there posts to freebsd-multimedia/-hardware asking if people have these older items they are willing to donate? Might save a trip to Outer Mongolia. I do _not_ think that you are "entirely stupid or greedy." _I_ am not completely stupid either, thank you, so please turn your ``you dumb____'' attitude and sarcasm down several notches .... -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 10:24:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 3E6D837C546; Thu, 23 Mar 2000 10:24:44 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id 937E818220; Thu, 23 Mar 2000 19:23:08 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <200003231801.KAA01088@mass.cdrom.com> References: <200003231801.KAA01088@mass.cdrom.com> Date: Thu, 23 Mar 2000 19:18:09 +0100 To: Mike Smith , John Reynolds~ From: Brad Knowles Subject: Re: What does "Voxware still supported in 4.0" mean exactly? Cc: stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:01 AM -0800 2000/3/23, Mike Smith wrote: > At last count, I think we've bought, borrowed and cajoled about twenty or > so cards and sent them off to Cameron. I don't know what makes you think > that we're _entirely_ stupid or greedy, especially since it's not like > it's a secret or anything that we do this regularly. Here's another idea -- make a list of cards that you know of that there are problems with, but that you guys can't find. Some of us might happen to frequent computer shows or have some old hardware we can scrounge up, and might be willing to give that to you (to give to Cameron), or trade them for X future issues of the CD-ROM sets. I certainly don't mind spending $25 (or $50, or $100) to help support the FreeBSD project, and I don't really care too much how I spend that money. I'd prefer to spend it in a way that materially helps the project, and it seems to me that helping to find and donate bleeding-edge or ancient hardware for which we do not have good support might be a better way to do that than to buy a subscription of coasters. A central database done with PHP3+MySQL of hardware you're specifically looking for shouldn't be too hard to implement, should it? -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 10:31:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mg-20425418-10.ricochet.net [204.254.18.10]) by hub.freebsd.org (Postfix) with ESMTP id 40DD737C5FC for ; Thu, 23 Mar 2000 10:31:16 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA01282; Thu, 23 Mar 2000 10:32:31 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003231832.KAA01282@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Brad Knowles Cc: John Reynolds~ , stable@FreeBSD.ORG Subject: Re: What does "Voxware still supported in 4.0" mean exactly? In-reply-to: Your message of "Thu, 23 Mar 2000 19:18:09 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Mar 2000 10:32:30 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 10:01 AM -0800 2000/3/23, Mike Smith wrote: > > > At last count, I think we've bought, borrowed and cajoled about twenty or > > so cards and sent them off to Cameron. I don't know what makes you think > > that we're _entirely_ stupid or greedy, especially since it's not like > > it's a secret or anything that we do this regularly. > > Here's another idea -- make a list of cards that you know of that > there are problems with, but that you guys can't find. Some of us > might happen to frequent computer shows or have some old hardware we > can scrounge up, and might be willing to give that to you (to give to > Cameron), or trade them for X future issues of the CD-ROM sets. Cameron has this list; either he or Bill Swingle ought to be able to put it somewhere fairly prominent. > I certainly don't mind spending $25 (or $50, or $100) to help > support the FreeBSD project, and I don't really care too much how I > spend that money. I'd prefer to spend it in a way that materially > helps the project, and it seems to me that helping to find and donate > bleeding-edge or ancient hardware for which we do not have good > support might be a better way to do that than to buy a subscription > of coasters. It's the donation of your time and eyes that _really_ counts here, and it would be _greatly_ appreciated. > A central database done with PHP3+MySQL of hardware you're > specifically looking for shouldn't be too hard to implement, should > it? Probably not; it's just a question of finding someone to develop and maintain such an animal. The BSD Driver Database goes a long way towards this, but I haven't seen much activity from M. Yancey lately. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 10:32: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from goodnet.com (goodnet.com [207.98.129.1]) by hub.freebsd.org (Postfix) with ESMTP id DCE1437C59F for ; Thu, 23 Mar 2000 10:32:00 -0800 (PST) (envelope-from gches@goodnet.com) Received: from localhost (gches@localhost) by goodnet.com with ESMTP id LAA10100 for ; Thu, 23 Mar 2000 11:31:45 -0700 (MST) Date: Thu, 23 Mar 2000 11:31:44 -0700 (MST) From: "Geoffrey T. Cheshire" To: freebsd-stable Subject: What cruft to remove after 3.4 -> 4.0? 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 all, Well, I guess I'm one of the lucky non-kernel-hackers to not have a big problem upgrading 3.4 -> 4.0 via source (though I did get bit by the install-info incompatibility). Now that my box is up with a 4.0 kernel and world, I'd like to start removing redundant packages. For example, OpenSSH was, IIRC, a port but is now a core component, so you get copies in both /usr and /usr/local. Is there a canonical list of things like this to pare? Should I use pkg_delete? Thanks for any suggestions, Geoff Geoffrey T. Cheshire To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 10:33:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id E24B837B9AC for ; Thu, 23 Mar 2000 10:33:52 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (mi@rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id NAA48105 for ; Thu, 23 Mar 2000 13:33:48 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id NAA29969 for stable@freebsd.org; Thu, 23 Mar 2000 13:33:48 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <200003231833.NAA29969@rtfm.newton> Subject: Re: What does "Voxware still supported in 4.0" mean exactly? In-Reply-To: from Brad Knowles at "Mar 23, 2000 07:18:09 pm" To: stable@freebsd.org Date: Thu, 23 Mar 2000 13:33:48 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"; Thu, 23 Mar 2000 10:43:17 -0800 (PST) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by pan.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.19 2000/01/29 00:15:43 dmccart Exp $) with ESMTP id LAA06294 for ; Thu, 23 Mar 2000 11:43:17 -0700 (MST) Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id LAA26228 for ; Thu, 23 Mar 2000 11:42:12 -0700 (MST) X-Envelope-To: X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id NAA00400; Thu, 23 Mar 2000 13:43:16 -0500 (EST) X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14554.26052.433543.757976@hip186.ch.intel.com> Date: Thu, 23 Mar 2000 11:43:16 -0700 (MST) To: stable@freebsd.org Subject: Re: What does "Voxware still supported in 4.0" mean exactly? In-Reply-To: References: <200003231801.KAA01088@mass.cdrom.com> X-Mailer: VM 6.75 under Emacs 20.3.11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Thursday, March 23, Brad Knowles wrote: ] > At 10:01 AM -0800 2000/3/23, Mike Smith wrote: > > > At last count, I think we've bought, borrowed and cajoled about twenty or > > so cards and sent them off to Cameron. I don't know what makes you think > > that we're _entirely_ stupid or greedy, especially since it's not like > > it's a secret or anything that we do this regularly. > > Here's another idea -- make a list of cards that you know of that > there are problems with, but that you guys can't find. Some of us > might happen to frequent computer shows or have some old hardware we > can scrounge up, and might be willing to give that to you (to give to > Cameron), or trade them for X future issues of the CD-ROM sets. > > I certainly don't mind spending $25 (or $50, or $100) to help > support the FreeBSD project, and I don't really care too much how I > spend that money. I'd prefer to spend it in a way that materially > helps the project, and it seems to me that helping to find and donate > bleeding-edge or ancient hardware for which we do not have good > support might be a better way to do that than to buy a subscription > of coasters. Thank you Brad, this is the underlying point of my original message. I guess I didn't state it clearly enough. I wouldn't mind doing the above either. There have been mentions of "why doesn't somebody start a ``hardware for FreeBSD developer's fund''?" on these lists before. I don't really remember the details of the answers received--suffice to say that the jist of the answer was "we already use CD profit sales to buy hardware." If there is simply a communication problem here, let's try to overcome it. i.e. developers *have* hardware but can't find that one "special" card they want--or don't have the resources to get the "latest" card they're dying to tear into. Let's publicize both cases if they exist so that no needless yelling back and forth happens and we can move the project further ahead. Cheers, -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 10:46:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from student-mailhub.dcu.ie (ns.dcu.ie [136.206.1.3]) by hub.freebsd.org (Postfix) with ESMTP id 96D6E37C67F for ; Thu, 23 Mar 2000 10:46:13 -0800 (PST) (envelope-from drjolt@redbrick.dcu.ie) Received: from enigma.redbrick.dcu.ie (postfix@enigma.redbrick.dcu.ie [136.206.15.5]) by student-mailhub.dcu.ie (8.9.3/8.9.3/893-FD) with ESMTP id SAA19731 for ; Thu, 23 Mar 2000 18:46:08 GMT Received: by enigma.redbrick.dcu.ie (Postfix, from userid 2034) id 2618B7CB6; Thu, 23 Mar 2000 18:44:19 +0000 (GMT) Date: Thu, 23 Mar 2000 18:44:19 +0000 From: David Murphy To: stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Message-ID: <20000323184419.B27223@enigma.redbrick.dcu.ie> References: <20000323101546.A32653@enigma.redbrick.dcu.ie> <200003231658.JAA23713@freeway.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003231658.JAA23713@freeway.dcfinc.com>; from chad@DCFinc.com on Thu, Mar 23, 2000 at 09:58:40AM -0700 X-no-archive: yes Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting <200003231658.JAA23713@freeway.dcfinc.com> by "Chad R. Larson" : > Perhaps you've lost sight of the fact that the whole FreeBSD project > is, outside of a very few guiding entities, done by volunteers. So, > if you see something you think is wrong, and you feel strongly about > it, volunteer. After the treatment I've received on this list, I'm afraid I do not feel very motivated to voluteer my time. I guess that's just human nature. -- When asked if it is true that he uses his wheelchair as a weapon he will reply: "That's a malicious rumour. I'll run over anyone who repeats it." Stephen Hawking - [http://www.smh.com.au/news/0001/07/features/features1.html] David Murphy - For PGP public key, send mail with Subject: send-pgp-key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 10:49:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 54DA737BEB3; Thu, 23 Mar 2000 10:49:18 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id 6897ADB75; Thu, 23 Mar 2000 19:49:14 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <200003231832.KAA01282@mass.cdrom.com> References: <200003231832.KAA01282@mass.cdrom.com> Date: Thu, 23 Mar 2000 19:48:35 +0100 To: Mike Smith From: Brad Knowles Subject: Re: What does "Voxware still supported in 4.0" mean exactly? Cc: John Reynolds~ , stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:32 AM -0800 2000/3/23, Mike Smith wrote: > It's the donation of your time and eyes that _really_ counts here, and it > would be _greatly_ appreciated. I'll certainly do what I can here, although I doubt what skills I have will be all that useful. However, I do hope to be able to use projects related to FreeBSD to help increase the quality of my skills, and make them more useful. So, perhaps, over time they will become more valuable. I'm just trying to find additional ways that I can help, perhaps ones where I can make more of an immediately useful impact than I can today with my time and what little skills I have. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 10:51: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.nerv.nu (cx639627-c.irvn1.occa.home.com [24.0.209.134]) by hub.freebsd.org (Postfix) with ESMTP id 0440637C4EB; Thu, 23 Mar 2000 10:50:57 -0800 (PST) (envelope-from nugundam@nerv.nu) Received: from localhost (nugundam@localhost) by mail.nerv.nu (8.9.3/8.9.3) with ESMTP id KAA38174; Thu, 23 Mar 2000 10:56:54 -0800 (PST) (envelope-from nugundam@greenwood3.nerv.nu) Date: Thu, 23 Mar 2000 10:56:54 -0800 (PST) From: Joseph Lee To: Warner Losh Cc: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: netgear fa410TX and 4.x problems In-Reply-To: <200003222104.OAA33511@harmony.village.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, 22 Mar 2000, Warner Losh wrote: > Since I committed the patches to if_ed in the last 24 hours, I'll > guess that you don't have them. Please try them and let me know. Tastes great! Thanks. Works like a charm now. I guess I forgot that 4.x isn't -current anymore. Thanks a lot. -- Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ # Anime Expo 2000 >> www.anime-expo.org/ > # FreeBSD: The Power to Serve >> www.freebsd.org > # The Ultimate Online Speed-Shop >> www.racesearch.com / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 10:54:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mg-20425418-10.ricochet.net [204.254.18.10]) by hub.freebsd.org (Postfix) with ESMTP id C590237B583 for ; Thu, 23 Mar 2000 10:54:46 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA01378; Thu, 23 Mar 2000 10:54:43 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003231854.KAA01378@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Reynolds~ Cc: stable@freebsd.org Subject: Re: What does "Voxware still supported in 4.0" mean exactly? In-reply-to: Your message of "Thu, 23 Mar 2000 11:43:16 MST." <14554.26052.433543.757976@hip186.ch.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Mar 2000 10:54:43 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Thank you Brad, this is the underlying point of my original message. I guess I > didn't state it clearly enough. I wouldn't mind doing the above either. There > have been mentions of "why doesn't somebody start a ``hardware for FreeBSD > developer's fund''?" on these lists before. I don't really remember the > details of the answers received--suffice to say that the jist of the answer > was "we already use CD profit sales to buy hardware." No, that doesn't suffice. Donations to FreeBSD Inc. have always been used for the best interests of the project; this includes buying hardware as required or as incentives to developers that have put in stellar efforts. > If there is simply a communication problem here, let's try to overcome it. > i.e. developers *have* hardware but can't find that one "special" card they > want--or don't have the resources to get the "latest" card they're dying to > tear into. Let's publicize both cases if they exist so that no needless > yelling back and forth happens and we can move the project further ahead. You appear to be largely ignoring one of my jobs. 8) I've been one of the people responsible for making this happen for a while now, so don't be so surprised that I'm a little ticked off that you don't seem to have noticed. Suffice it to say, perhaps, that as a general rule hardware _does_ end up in the hands of people that can do something with it, and that this hardware comes from wherever seems to be the most effective source at the time. We don't make a lot of noise about it at least in part because this isn't about making noise, it's about getting things done. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 11: 2:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 5ED0537CA89; Thu, 23 Mar 2000 11:02:28 -0800 (PST) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id DDF4B9B17; Thu, 23 Mar 2000 14:02:22 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 82EB5BA1D; Thu, 23 Mar 2000 14:02:22 -0500 (EST) Date: Thu, 23 Mar 2000 14:02:21 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Brad Knowles Cc: Mike Smith , John Reynolds~ , stable@FreeBSD.ORG Subject: Re: What does "Voxware still supported in 4.0" mean exactly? 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 Thu, 23 Mar 2000, Brad Knowles wrote: > A central database done with PHP3+MySQL of hardware you're > specifically looking for shouldn't be too hard to implement, should > it? > http://www.posi.net/freebsd/drivers/ ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: 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 Thu Mar 23 11: 3:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mg-20425418-10.ricochet.net [204.254.18.10]) by hub.freebsd.org (Postfix) with ESMTP id 93AE437C6E6 for ; Thu, 23 Mar 2000 11:02:43 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA01427; Thu, 23 Mar 2000 11:04:24 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003231904.LAA01427@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Reynolds~ Cc: stable@freebsd.org Subject: Re: hardware (was: What does "Voxware still supported in 4.0" mean exactly?) In-reply-to: Your message of "Thu, 23 Mar 2000 11:23:09 MST." <14554.24845.963542.299903@hip186.ch.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Mar 2000 11:04:23 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > JUST HOLD ON THERE TEX!!!!!!! The first line of my message was: > > > > The following is not venom directed at jkh, or anybody in general--it is an > > repeat: "not venom". Also read in my message that I said I *know* that it is > regularly done (buying hardware and shipping it to developers). Which is why you ask: "shouldn't FreeBSD, Inc. or Walnut Creek itself be proactively shipping willing developers like this all the hardware they can purchase?" > Read what I said, then post your comments. A more appropriate response would > have simply been "some older cards are harder to find, if you or anyone within > earshot of this message has one we could use or buy, please let us know so we > can continue our regular program of buying hardware for developers." Are there > posts to freebsd-multimedia/-hardware asking if people have these older items > they are willing to donate? Might save a trip to Outer Mongolia. Again, this is the danger of walking into something and making assumptions. We've been there and done that (and are there, and are doing that) already. If you think that there's something that we ought to be doing, chances are pretty good that we've already thought of it as well, and if we're not doing it there's probably a good reason. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 11:15:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.Stanford.EDU (smtp.Stanford.EDU [171.64.14.23]) by hub.freebsd.org (Postfix) with ESMTP id 237DB37C52D; Thu, 23 Mar 2000 11:15:31 -0800 (PST) (envelope-from cscox@stanford.edu) Received: from cardinal0.Stanford.EDU (cardinal0.Stanford.EDU [171.64.14.231]) by smtp.Stanford.EDU (8.9.3/8.9.3) with ESMTP id LAA22302; Thu, 23 Mar 2000 11:15:27 -0800 (PST) Date: Thu, 23 Mar 2000 11:15:27 -0800 (PST) From: Charles Cox To: Cy Schubert - ITSD Open Systems Group Cc: Andrew Gallatin , obrien@FreeBSD.ORG, Howard Leadmon , freebsd-alpha@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Compiler problems with -O2 (was Re: CVS Trouble, even under 4.0-RELEASE (alpha) HELP!) In-Reply-To: <200003231425.GAA01222@cwsys.cwsent.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 I would like to add that some of us who do a lot of numerically intensive programming, and that need to squeeze every last available cycle out of our CPU's would really appreciate having -O2 available for userland programs. To me, getting rid of the -O2+ switch would be like outlawing cars because someone had a really bad car accident. Just like driving a car, using gcc and the -O2 switch safely are the USER's responsibility. Having said this though, I do fully support having comments in make.conf, and documentation elsewhere that cautions against compiling a kernel with -O2. CC On Thu, 23 Mar 2000, Cy Schubert - ITSD Open Systems Group wrote: > In message <14553.19348.115781.273817@grasshopper.cs.duke.edu>, Andrew > Gallatin > writes: > > > > David O'Brien writes: > > > On Wed, Mar 22, 2000 at 03:03:09PM -0500, Howard Leadmon wrote: > > > > want to avoid, or at least note the problem with -O2 as I have been usin > > g > > > > that when making software on my Intel machines for a long time, so just > > > > assumed it was OK to do the same on the Alpha.. > > > > > > It isn't officially OK from the perspective of the FreeBSD Project. "-O2" > > > has been the cause of problems on the i386 arch too. Thus my constant > > > yelling about it that nobody pays attention to. > > > > > > I'm on the virge of turning off "-O2" on both Alpha and i386. > > > > You certainly have my vote. > > > > I take it the O2 bugs are not unique to us, but rather they are > > generic across all OSes that gcc version 2.95.2 runs on? Do the gcc > > people know these problems exist? > > How about a compromise? Just print a nasty message every time -O2 is > specified: > > BEWARE: -O2 may cause some applications to break or may cause your > system to fail to boot. Be sure you absolutely know what you are doing > before using -O2 optimisation. > > Then enclose it in stars (*) or bangs (!). > > > Regards, Phone: (250)387-8437 > Cy Schubert Fax: (250)387-5766 > Team Leader, Sun/DEC 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 11:24: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 7EC2937BE11; Thu, 23 Mar 2000 11:23:54 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA06427; Thu, 23 Mar 2000 14:23:42 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id OAA09970; Thu, 23 Mar 2000 14:23:12 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 23 Mar 2000 14:23:12 -0500 (EST) To: Charles Cox Cc: Cy Schubert - ITSD Open Systems Group , Andrew Gallatin , obrien@FreeBSD.ORG, Howard Leadmon , freebsd-alpha@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Compiler problems with -O2 (was Re: CVS Trouble, even under 4.0-RELEASE (alpha) HELP!) In-Reply-To: References: <200003231425.GAA01222@cwsys.cwsent.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14554.28033.439748.801349@grasshopper.cs.duke.edu> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Charles Cox writes: > I would like to add that some of us who do a lot of numerically intensive > programming, and that need to squeeze every last available cycle out of > our CPU's would really appreciate having -O2 available for userland > programs. To me, getting rid of the -O2+ switch would be like outlawing > cars because someone had a really bad car accident. Just like driving a > car, using gcc and the -O2 switch safely are the USER's > responsibility. Having said this though, I do fully support having > comments in make.conf, and documentation elsewhere that cautions against > compiling a kernel with -O2. > > CC You're missing the point almost entirely. FreeBSD's stock gcc -O2 is demonstrably __broken__ on the alpha. You cannot trust code it outputs. If you want to obtain results as quickly as possible & do not care if they are correct, it would be much faster to read them from /dev/zero. ;-) ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 11:31:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from anarcat.dyndns.org (phobos.IRO.UMontreal.CA [132.204.20.20]) by hub.freebsd.org (Postfix) with ESMTP id D4A4937BEB3; Thu, 23 Mar 2000 11:31:19 -0800 (PST) (envelope-from spidey@anarcat.dyndns.org) Received: by anarcat.dyndns.org (Postfix, from userid 1000) id 925441BEE; Thu, 23 Mar 2000 13:48:33 -0500 (EST) From: Spidey MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14554.26368.221170.289689@anarcat.dyndns.org> Date: Thu, 23 Mar 2000 13:48:32 -0500 (EST) To: Warner Losh Cc: freebsd-stable@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Small spaces In-Reply-To: <200003190502.WAA04970@harmony.village.org> References: <20000318220747.F5039@pir.net> <38D43E0E.1DDECC10@confusion.net> <200003190502.WAA04970@harmony.village.org> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Reply-To: beaupran@iro.umontreal.ca Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently installed PicoBSD on a 386 with 4Mb RAM and 80Mb HD. I ended up installing a new 3.x kernel and FBSD binaries 'cause picobsd's were a little buggy and the systeme used a MFS root which obviously was too much for 4mb! I lost the box recently when the root crashed. I never got to use the drive again, but it showed me how one can use PicoBSD to 'invade' a very small box with FBSD binaries. --- At 22:02 of March 18, Big Brother made Warner Losh write: > I have a 4.0-stable system running in 17MB of a 48MB CF card stuck in > an IDE <-> CF adapter from www.tapr.org. I installed select binaries > and libraries with a custom script. More heavy weight than picobsd, > but a little easier to hack on after the fact. This is with ssh and > enough of a world to test load new drivers and nfs mount my > development environment. > > I think that if I were to build a shared /bin and /sbin that I could > get this below 13MB. Since there's only one partition I don't think > it will matter that they aren't statically linked. And the CF part is > easy/fast enough to recreate that it is a small risk. > > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Si l'image donne l'illusion de savoir C'est que l'adage pretend que pour croire, L'important ne serait que de voir Lofofora To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 11:31:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from anarcat.dyndns.org (phobos.IRO.UMontreal.CA [132.204.20.20]) by hub.freebsd.org (Postfix) with ESMTP id D4A4937BEB3; Thu, 23 Mar 2000 11:31:19 -0800 (PST) (envelope-from spidey@anarcat.dyndns.org) Received: by anarcat.dyndns.org (Postfix, from userid 1000) id 925441BEE; Thu, 23 Mar 2000 13:48:33 -0500 (EST) From: Spidey MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14554.26368.221170.289689@anarcat.dyndns.org> Date: Thu, 23 Mar 2000 13:48:32 -0500 (EST) To: Warner Losh Cc: freebsd-stable@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Small spaces In-Reply-To: <200003190502.WAA04970@harmony.village.org> References: <20000318220747.F5039@pir.net> <38D43E0E.1DDECC10@confusion.net> <200003190502.WAA04970@harmony.village.org> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Reply-To: beaupran@iro.umontreal.ca Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently installed PicoBSD on a 386 with 4Mb RAM and 80Mb HD. I ended up installing a new 3.x kernel and FBSD binaries 'cause picobsd's were a little buggy and the systeme used a MFS root which obviously was too much for 4mb! I lost the box recently when the root crashed. I never got to use the drive again, but it showed me how one can use PicoBSD to 'invade' a very small box with FBSD binaries. --- At 22:02 of March 18, Big Brother made Warner Losh write: > I have a 4.0-stable system running in 17MB of a 48MB CF card stuck in > an IDE <-> CF adapter from www.tapr.org. I installed select binaries > and libraries with a custom script. More heavy weight than picobsd, > but a little easier to hack on after the fact. This is with ssh and > enough of a world to test load new drivers and nfs mount my > development environment. > > I think that if I were to build a shared /bin and /sbin that I could > get this below 13MB. Since there's only one partition I don't think > it will matter that they aren't statically linked. And the CF part is > easy/fast enough to recreate that it is a small risk. > > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Si l'image donne l'illusion de savoir C'est que l'adage pretend que pour croire, L'important ne serait que de voir Lofofora To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 12: 4:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 51B3F37B9B0 for ; Thu, 23 Mar 2000 12:04:32 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (dcs@p21-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.150]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id FAA13282; Fri, 24 Mar 2000 05:04:07 +0900 (JST) Message-ID: <38DA785C.585CC385@newsguy.com> Date: Fri, 24 Mar 2000 05:02:36 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Cy Schubert - ITSD Open Systems Group Cc: "Jordan K. Hubbard" , Thomas David Rivers , witr@rwwa.com, stable@FreeBSD.ORG, witr@pobox.rwwa.com Subject: Re: V4.0 and Walnut Creek Subscriptions... References: <200003231326.FAA00923@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: > > In message <38D97069.C5811525@newsguy.com>, "Daniel C. Sobral" writes: > > "Jordan K. Hubbard" wrote: > > > > > > No, you won't get two copies. > > > > Just charged twice. ;-> > > What? Are you saying WC is actually a law firm? Ah, but it isn't WC anymore, is it? Now it's BSDI. :-) Besides, Jordan is a lawyer script(*), didn't you know? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@zurichgnomes.bsdconspiracy.net One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. (*) Contrary to popular belief, Jordan is a Prolog script, not a Perl script. It's the kids these days, thinking the .pl extension refered to Perl... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 12:25:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 3053D37C52C; Thu, 23 Mar 2000 12:25:09 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id MAA13022; Thu, 23 Mar 2000 12:25:08 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 23 Mar 2000 12:25:08 -0800 (PST) From: Kris Kennaway To: "Geoffrey T. Cheshire" Cc: freebsd-stable Subject: Re: What cruft to remove after 3.4 -> 4.0? 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 Thu, 23 Mar 2000, Geoffrey T. Cheshire wrote: > Is there a canonical list of things like this to pare? Should I use > pkg_delete? Here's the canonical list: openssl openssh :-) Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 12:26:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id A946A37C542; Thu, 23 Mar 2000 12:26:18 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id MAA13090; Thu, 23 Mar 2000 12:26:18 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 23 Mar 2000 12:26:18 -0800 (PST) From: Kris Kennaway To: "WMC, O'Gorman, James" Cc: stable@freebsd.org Subject: Re: starting xdm (Re: src/UPDATING for RELENG_3 to RELENG_4 upgrade works.) In-Reply-To: <38DA5086.9C80CF2@elwood.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 Thu, 23 Mar 2000, WMC, O'Gorman, James wrote: > Mikhail Teterin wrote: > > right way is, probably, to fire it from /etc/ttys -- see the xdm > > entry there and change ``off'' to ``on''... Then (if you do not have > > X running) ``kill -1 1''. > > I have to thank Alan and Mikhail both for sending me this answer. It > will save me some time tonight. It's also been in the FAQ for donkey's years ;-) Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 12:29:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from goodnet.com (goodnet.com [207.98.129.1]) by hub.freebsd.org (Postfix) with ESMTP id 21FE237C52F; Thu, 23 Mar 2000 12:28:46 -0800 (PST) (envelope-from gches@goodnet.com) Received: from localhost (gches@localhost) by goodnet.com with ESMTP id NAA21234; Thu, 23 Mar 2000 13:28:39 -0700 (MST) Date: Thu, 23 Mar 2000 13:28:38 -0700 (MST) From: "Geoffrey T. Cheshire" To: Kris Kennaway Cc: freebsd-stable Subject: Re: What cruft to remove after 3.4 -> 4.0? 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 Thu, 23 Mar 2000, Kris Kennaway wrote: > openssl > openssh > > :-) There, that was easy! Thanks, Geoff Geoffrey T. Cheshire To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 12:31:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pan.ch.intel.com (pan.ch.intel.com [143.182.246.24]) by hub.freebsd.org (Postfix) with ESMTP id 444A937C55F for ; Thu, 23 Mar 2000 12:31:10 -0800 (PST) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by pan.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.19 2000/01/29 00:15:43 dmccart Exp $) with ESMTP id NAA09026 for ; Thu, 23 Mar 2000 13:31:08 -0700 (MST) Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id NAA11096 for ; Thu, 23 Mar 2000 13:29:58 -0700 (MST) X-Envelope-To: X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id PAA05336; Thu, 23 Mar 2000 15:31:03 -0500 (EST) X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14554.32518.827188.334324@hip186.ch.intel.com> Date: Thu, 23 Mar 2000 13:31:02 -0700 (MST) To: stable@freebsd.org Subject: Re: What does "Voxware still supported in 4.0" mean exactly? In-Reply-To: <200003231854.KAA01378@mass.cdrom.com> References: <14554.26052.433543.757976@hip186.ch.intel.com> <200003231854.KAA01378@mass.cdrom.com> X-Mailer: VM 6.75 under Emacs 20.3.11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Thursday, March 23, Mike Smith wrote: ] > > No, that doesn't suffice. Donations to FreeBSD Inc. have always been > used for the best interests of the project; this includes buying hardware > as required or as incentives to developers that have put in stellar > efforts. Is there a pointer you can provide for an address to write to (e-mail or snail) to get more information about doing this? I've scanned/searched the FreeBSD website and also cdrom.com and can't find anything specific to this topic. If it's been posted before, sorry. Information overload..... > You appear to be largely ignoring one of my jobs. 8) I've been one of > the people responsible for making this happen for a while now, so don't > be so surprised that I'm a little ticked off that you don't seem to have > noticed. Well, I do actively read -stable, -qa, -multimedia, -hackers-digest, -emulation, -doc, and -questions-digest. I guess I just missed the fact that this is part of your job description in that amount of traffic. Honest Abe. Didn't know it ... (I also checked http://www.freebsd.org/handbook/staff-who.html and didn't find mention of it). I plead forgiveness. > Suffice it to say, perhaps, that as a general rule hardware _does_ end up > in the hands of people that can do something with it, and that this > hardware comes from wherever seems to be the most effective source at the I believe you. This thread is now closed....... -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 12:35:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.Stanford.EDU (smtp.Stanford.EDU [171.64.14.23]) by hub.freebsd.org (Postfix) with ESMTP id A95FC37C54B; Thu, 23 Mar 2000 12:35:38 -0800 (PST) (envelope-from cscox@stanford.edu) Received: from cardinal0.Stanford.EDU (cardinal0.Stanford.EDU [171.64.14.231]) by smtp.Stanford.EDU (8.9.3/8.9.3) with ESMTP id MAA14646; Thu, 23 Mar 2000 12:35:35 -0800 (PST) Date: Thu, 23 Mar 2000 12:35:35 -0800 (PST) From: Charles Cox To: Andrew Gallatin Cc: Cy Schubert - ITSD Open Systems Group , obrien@FreeBSD.ORG, Howard Leadmon , freebsd-alpha@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Compiler problems with -O2 (was Re: CVS Trouble, even under 4.0-RELEASE (alpha) HELP!) In-Reply-To: <14554.28033.439748.801349@grasshopper.cs.duke.edu> 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, 23 Mar 2000, Andrew Gallatin wrote: > > Charles Cox writes: > > I would like to add that some of us who do a lot of numerically intensive > > programming, and that need to squeeze every last available cycle out of > > our CPU's would really appreciate having -O2 available for userland > > programs. To me, getting rid of the -O2+ switch would be like outlawing > > cars because someone had a really bad car accident. Just like driving a > > car, using gcc and the -O2 switch safely are the USER's > > responsibility. Having said this though, I do fully support having > > comments in make.conf, and documentation elsewhere that cautions against > > compiling a kernel with -O2. > > > > CC > > You're missing the point almost entirely. FreeBSD's stock gcc -O2 is > demonstrably __broken__ on the alpha. You cannot trust code it > outputs. > > If you want to obtain results as quickly as possible & do not care if > they are correct, it would be much faster to read them from > /dev/zero. ;-) > Oh, well that's a little different then, isn't it? CC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 13: 3:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 1BC7037B9B0; Thu, 23 Mar 2000 13:03:08 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id AF1E5180F5; Thu, 23 Mar 2000 22:02:56 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <14554.28033.439748.801349@grasshopper.cs.duke.edu> References: <200003231425.GAA01222@cwsys.cwsent.com> <14554.28033.439748.801349@grasshopper.cs.duke.edu> Date: Thu, 23 Mar 2000 21:59:52 +0100 To: Andrew Gallatin , Charles Cox From: Brad Knowles Subject: Re: Compiler problems with -O2 (was Re: CVS Trouble, even under 4.0-RELEASE (alpha) HELP!) Cc: Cy Schubert - ITSD Open Systems Group , Andrew Gallatin , obrien@FreeBSD.ORG, Howard Leadmon , freebsd-alpha@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:23 PM -0500 2000/3/23, Andrew Gallatin wrote: > If you want to obtain results as quickly as possible & do not care if > they are correct, it would be much faster to read them from > /dev/zero. ;-) Nah, that would actually be correct if you were looking to find out what the value of zero is. ;-) -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 13:43: 5 2000 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 15C4F37B9B0 for ; Thu, 23 Mar 2000 13:42:53 -0800 (PST) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id QAA12434; Thu, 23 Mar 2000 16:43:15 -0500 (EST) (envelope-from bandix@looksharp.net) Date: Thu, 23 Mar 2000 16:43:15 -0500 (EST) From: "Brandon D. Valentine" To: "Rodney W. Grimes" Cc: Cy Schubert - ITSD Open Systems Group , Vivek Khera , stable@FreeBSD.ORG Subject: Re: "dangerously dedicated" In-Reply-To: <200003231541.HAA60696@gndrsh.dnsmgr.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 Thu, 23 Mar 2000, Rodney W. Grimes wrote: >2. If the last byte of the sector != 0xaa55 go to the next drive in > the drive list and back step 1, if this was the last drive on the > list print an error and hang. On i386 machines this is usually something lame like: NO ROM BASIC SYSTEM HALTED despite the fact that no machine has included a ROM BASIC since the last of the IBM PS/2 386s came out. However most of the BIOSes until *very* recently still contained code that would check for a ROM BASIC after searching the entire drive list and try booting from that. Now if only we could convince them to put that back in except have it look for a forth interpreter in ROM. ------------------------------------------------------------- | -Brandon D. Valentine bandix at looksharp.net | bandix on EFnet IRC BVRiker on AIM ------------------------------------------------------------- | "...and as for hackers, we note that all of those known to | The Register are so strapped financially that seizing their | property would be tantamount to squeezing blood from a | stone." -- The Register, 02/17/2000 ------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 13:49: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from midway.uchicago.edu (midway.uchicago.edu [128.135.12.12]) by hub.freebsd.org (Postfix) with ESMTP id 4F55A37B9B0 for ; Thu, 23 Mar 2000 13:48:50 -0800 (PST) (envelope-from dbsypher@uchicago.edu) Received: from harper.uchicago.edu (root@harper.uchicago.edu [128.135.12.7]) by midway.uchicago.edu (8.9.3/8.9.3) with ESMTP id PAA28181; Thu, 23 Mar 2000 15:48:33 -0600 (CST) From: dbsypher@uchicago.edu Received: from c40948-a (c40948-a.plstn1.sfba.home.com [24.11.129.121]) by harper.uchicago.edu (8.9.3/8.9.3) with ESMTP id PAA12014; Thu, 23 Mar 2000 15:48:27 -0600 (CST) Message-Id: <4.2.2.20000323134038.00b3e6c0@nsit-popmail.uchicago.edu> X-Sender: dbsypher@nsit-popmail.uchicago.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 23 Mar 2000 13:48:23 -0800 To: Daniel Boyd , freebsd-stable@FreeBSD.ORG Subject: Re: When to remove .ctm-status? In-Reply-To: <200003231435.JAA19289@oberon.vacationclub.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 09:35 AM 3/23/00 -0500, Daniel Boyd wrote: >I want a src-4 tree. > >I am following this procedure: > >1. Apply src-cur deltas up to src-cur.4274.gz. >2. Apply src-4.0000.from-src-cur.4274.gz. >3. Apply src-4.0001.gz. > (and carry on with src-4.0002, etc.) > >Two questions: > >1. When do I remove .ctm-status? According to Chuck Robey's announcement on the 18th, you'd remove .ctm-status after step 2. >2. As a check, what should I see in .ctm-status after step 3? 0004 (since the latest delta is src-4.0004). Theoretically, of course. I haven't actually done this :) On a side note, Chuck Robey, Master of All Things CTM, has previously pointed out to me that -stable and -current aren't appropriate lists to ask ctm questions, and that questions like those should be sent to ctm@freebsd.org (which isn't really a list, just himself). Not to say that I personally understand when it stops being a -stable question and starts being a ctm question, but... -Charon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 13:50:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from account.abs.net (account.abs.net [207.114.5.70]) by hub.freebsd.org (Postfix) with ESMTP id 39A2B37BA8D; Thu, 23 Mar 2000 13:50:37 -0800 (PST) (envelope-from howardl@account.abs.net) Received: (from howardl@localhost) by account.abs.net (8.9.3/8.9.3+RBL+DUL+RSS+ORBS) id QAA55404; Thu, 23 Mar 2000 16:50:29 -0500 (EST) (envelope-from howardl) From: Howard Leadmon Message-Id: <200003232150.QAA55404@account.abs.net> Subject: Re: CVS Trouble, even under 4.0-RELEASE (alpha) HELP! In-Reply-To: <200003220628.BAA97796@account.abs.net> from Howard Leadmon at "Mar 22, 2000 01:28:34 am" To: freebsd-stable@freebsd.org, freebsd-alpha@freebsd.org Date: Thu, 23 Mar 2000 16:50:29 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL72 (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 OK, here is the followup report to my initial posting.. :) The recommendation that -O2 was breaking things was correct on the Alpha, and I have actually done a complete re-install and make world just using -O and all seems happy now. I know the FBSD project doesn't condone the use of -O2, but from all my experiences with the Intel port this works just fine. Needless to say this is *not* the case with the Alpha port, and I will be sure not to try that again.. :) Anyway many thanks to all that responded trying to help, and hopefully I can now setup a usable Alpha box.. --- Howard Leadmon - howardl@abs.net - http://www.abs.net ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 14: 4:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from post1.inre.asu.edu (post1.inre.asu.edu [129.219.13.100]) by hub.freebsd.org (Postfix) with ESMTP id 7568137C5ED for ; Thu, 23 Mar 2000 14:04:21 -0800 (PST) (envelope-from brian.sander@asu.edu) Received: from smtp.asu.edu (smtp.asu.edu [129.219.13.92]) by asu.edu (PMDF V5.2-31 #33824) with ESMTP id <0FRW008A8ALCUW@asu.edu> for freebsd-stable@FreeBSD.org; Thu, 23 Mar 2000 15:03:13 -0700 (MST) Received: from asu.edu ([129.219.123.141]) by smtp.asu.edu (8.9.3/8.9.3) with ESMTP id PAA13525 for ; Thu, 23 Mar 2000 15:04:56 -0700 (MST) Date: Thu, 23 Mar 2000 15:12:08 -0700 From: BrianSander Subject: subscribe To: freebsd-stable@FreeBSD.org Message-id: <38DA96B8.B54D3C68@asu.edu> MIME-version: 1.0 X-Mailer: Mozilla 4.72 [en] (WinNT; I) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en 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 Thu Mar 23 14:16:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail-03-real.cdsnet.net (mail-03-real.cdsnet.net [204.118.244.93]) by hub.freebsd.org (Postfix) with SMTP id F168737B5AB for ; Thu, 23 Mar 2000 14:16:09 -0800 (PST) (envelope-from mrcpu@internetcds.com) Received: (qmail 58620 invoked from network); 23 Mar 2000 22:16:06 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail-03-real.cdsnet.net with SMTP; 23 Mar 2000 22:16:06 -0000 Date: Thu, 23 Mar 2000 14:12:31 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: stable@freebsd.org Subject: Samba perf in the toilet with 4.0 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 have reviewed the mail logs about this, and messing with patch-ah didn't fix anything for me. I just update my nicely working 3.4 box to 4.0-stable from a day ago. Connected from win2000, and was moving some files, and it just seemed slow. So I look with netstat, and I'm getting less than 100k/second out of the box. With 3.4, I was getting 3-4MB/sec. No errors, no collisions, 100mbit full duplex. I tried the 2.0.7 prerelease of samba and it isn't running any better. Not sure what's going on. May have to drop back to 3.4 if this isn't easily fixed. Other than this issue, everything I've been using has worked fine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 14:16:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from phoenix.welearn.com.au (phoenix.welearn.com.au [139.130.44.81]) by hub.freebsd.org (Postfix) with ESMTP id E252037C6C2 for ; Thu, 23 Mar 2000 14:16:16 -0800 (PST) (envelope-from jon@phoenix.welearn.com.au) Received: (from jon@localhost) by phoenix.welearn.com.au (8.9.3/8.9.3) id JAA41042 for stable@FreeBSD.ORG; Fri, 24 Mar 2000 09:16:04 +1100 (EST) (envelope-from jon) Date: Fri, 24 Mar 2000 09:16:01 +1100 From: Jonathan Michaels Cc: stable@FreeBSD.ORG Subject: Re: What does "Voxware still supported in 4.0" mean exactly? Message-ID: <20000324091556.B40513@phoenix.welearn.com.au> Reply-To: jon@welearn.com.au References: <14554.26052.433543.757976@hip186.ch.intel.com> <200003231854.KAA01378@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <200003231854.KAA01378@mass.cdrom.com>; from Mike Smith on Thu, Mar 23, 2000 at 10:54:43AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG all, On Thu, Mar 23, 2000 at 10:54:43AM -0800, Mike Smith wrote: > > > > Thank you Brad, this is the underlying point of my original message. I guess I > > didn't state it clearly enough. I wouldn't mind doing the above either. There > > have been mentions of "why doesn't somebody start a ``hardware for FreeBSD > > developer's fund''?" on these lists before. I don't really remember the > > details of the answers received--suffice to say that the jist of the answer > > was "we already use CD profit sales to buy hardware." > > No, that doesn't suffice. Donations to FreeBSD Inc. have always been > used for the best interests of the project; this includes buying hardware > as required or as incentives to developers that have put in stellar > efforts. pity this cannot include a few simple things like a text interface disabled people could use. or an easily managable (waste of resources, my personal opinion) gui. much is made of people getting thier hands dirty with makingcode work .. most genuinely disabled people have difficulty handling the keyboard letalone the complexities of coding. we as a rule have to rely upon the generiousity of others to get those very things that the "others", that is those upon whome we are forced to rely, take fro granted .. almost as thier god given right. so becaue we cannot code we cannot get because those of teh "others" cannot be bothered to find out whatit is that is required in the frst place, they as a class think that thier vague assumptions of what its like or what they thinkmight be required is no subsitute for geting intimate with a disabled person and finding out what the real problems are and how best to make the path easier to navigate. this in tern would produce significant benifits for the "abled body" majority. i'd givemy eye teeth to be able to write code, debug and build tools .. but i cannot and in all likelyhood will never be able to .. and so i will be forced to use the screen that i can afford that is slowly destroying my already severly damaged eye mucles. every bodies eye get tired, every bodies eye mucles get weak it would serve severybodies purrpose to have a relaible stable text screen driver that wold support 20line my 60 char, or 20x40 or 10 line by 70 char. i'm sure that taking the current state of the art and a few pokes here and thier a result could be had failrly quicly, or so itwas back when i was learning my trade and the state of teh art was a motorola mc68b09e and its comlimentry screen driver a mc?4481 or someting like that, its been over 25 years and my memory isnt what it used t be. trying as always jonathan -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 14:21:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smartie.braingarage.com (m206-51.dsl.tsoft.com [198.144.206.51]) by hub.freebsd.org (Postfix) with ESMTP id 7BD7337C76D for ; Thu, 23 Mar 2000 14:21:45 -0800 (PST) (envelope-from robert@braingarage.com) Received: (from nobody@localhost) by smartie.braingarage.com (8.9.3/8.9.3) id OAA03748; Thu, 23 Mar 2000 14:21:31 -0800 (PST) (envelope-from robert@braingarage.com) Date: Thu, 23 Mar 2000 14:21:31 -0800 (PST) From: robert bowen Message-Id: <200003232221.OAA03748@smartie.braingarage.com> X-Authentication-Warning: smartie.braingarage.com: nobody set sender to robert@braingarage.com using -f To: freebsd-stable@freebsd.org Reply-To: robert@braingarage.com MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP3 Imap webMail Program 2.0.11 Subject: What else to remove after 4.0 upgrade Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are there any binary files that have changed location or gone away since 3.4-R? I saw the post on "cruft" but I am worried that after a binary 4.0R upgrade there will be some "leftovers" in /bin or /usr/bin that are not overwritten by the new release (because they are not included or changed in location) Thanks again To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 14:23:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 23EB737C729 for ; Thu, 23 Mar 2000 14:22:53 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA36109; Thu, 23 Mar 2000 15:22:49 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA44344; Thu, 23 Mar 2000 15:22:44 -0700 (MST) Message-Id: <200003232222.PAA44344@harmony.village.org> To: Andy Georges Subject: Re: building new kernel before or after installing the world Cc: freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Thu, 23 Mar 2000 12:00:09 +0100." References: Date: Thu, 23 Mar 2000 15:22:44 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It doesn't generally matter. In the 3.x -> 4.0 upgrade path, one needs to do kernel before the installworld due to changes in how signals were handled. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 14:24:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7390C37B6AF for ; Thu, 23 Mar 2000 14:24:22 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA36118; Thu, 23 Mar 2000 15:24:16 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA44364; Thu, 23 Mar 2000 15:24:12 -0700 (MST) Message-Id: <200003232224.PAA44364@harmony.village.org> To: "Andrew Reilly" Subject: Re: src/UPDATING for RELENG_3 to RELENG_4 upgrade works. Cc: stable@FreeBSD.ORG In-reply-to: Your message of "Thu, 23 Mar 2000 23:10:57 +1100." <20000323231057.A27794@gurney.reilly.home> References: <20000323231057.A27794@gurney.reilly.home> Date: Thu, 23 Mar 2000 15:24:12 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000323231057.A27794@gurney.reilly.home> "Andrew Reilly" writes: : * You really have to use the make buildkernel method to build the : 4.0 kernel. I suspect that that must use the new-but-not-installed : config or something. A normal "config GURNEY" in sys/i386/conf : didn't work, but "make buildkernel KERNEL=GURNEY" worked for me. Right. The config / make method can be made to work, but it is too hard to document for novice users. : * Having a kernel called /GURNEY now, rather than /kernel : requires that the file loader.conf.local contains kernel="/GURNEY", : otherwise the boot loader will load up the old 3.4-STABLE kernel. Or stop the boot, unload the /kernel and boot /GURNET. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 14:27: 2 2000 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 5610537CA0B; Thu, 23 Mar 2000 14:26:31 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.12 #1) id 12YFz6-0005Cn-00; Thu, 23 Mar 2000 22:21:44 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7) id 12YFzB-000DHx-00; Thu, 23 Mar 2000 22:21:49 +0000 Date: Thu, 23 Mar 2000 22:21:49 +0000 From: Ben Smithurst To: hackers@freebsd.org, stable@freebsd.org Subject: repeatable lockup (pipe related?) Message-ID: <20000323222149.C87103@strontium.scientia.demon.co.uk> 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 I've noticed a problem which seems to cause a repeatable lockup in both RELENG_3 and RELENG_4 (I don't have any -current machines to test on). basically, I've been able to repeat it by creating a file containing .SH foo, bar, baz and then a lot of junk text (I appended /etc/rc and /etc/rc.network). Then, when I do nroff -ms foo.ms 2>&1 | less and quit 'less' straight away, the whole system seems to lockup. ^T worked (sometimes), and showed troff using lots of system time (no user time). ping from another host worked, ctrl-alt-esc dropped into DDB ok, but that was about all. (ctrl-alt-del didn't work.) Of course, when it first happened I wasn't trying to process /etc/rc* files with nroff, :-) that's just a case which works (or not) and you guys should be able to use to reproduce it. There's probably an easier way, too, but what the hell. (It seems it doesn't always happen, but normally within a few tries it does.) Can anyone else repeat this? If not, I'll be happy to try to supply any other details you want. (Either that or assume my system is seriously screwed in some way, and you can assume I'm an idiot.) part of the backtrace is: #12 0xc01ecd30 in atkbd_isa_intr (arg=0xc023c5e0) at ../../isa/atkbd_isa.c:120 #13 0xc0131f1c in tsleep (ident=0xc5fdfca0, priority=272, wmesg=0xc01f557d "pipbww", timo=0) at ../../kern/kern_synch.c:480 #14 0xc013df68 in pipe_write (fp=0xc0893a40, uio=0xc601ceec, cred=0xc07bf880, flags=0, p=0xc5afdbe0) at ../../kern/sys_pipe.c:794 #15 0xc013c363 in dofilewrite (p=0xc5afdbe0, fp=0xc0893a40, fd=2, buf=0x807dc60, nbyte=32, offset=-1, flags=0) at ../../sys/file.h:156 #16 0xc013c267 in write (p=0xc5afdbe0, uap=0xc601cf80) at ../../kern/sys_generic.c:298 #17 0xc01e7336 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 134732896, tf_esi = 134732696, tf_ebp = -1077938268, tf_isp = -972959788, tf_ebx = 672301476, tf_edx = 134732696, tf_ecx = 134732696, tf_eax = 4, tf_trapno = 22, tf_err = 2, tf_eip = 672262004, tf_cs = 31, tf_eflags = 663, tf_esp = -1077938312, tf_ss = 47}) at ../../i386/i386/trap.c:1073 everything above frame 13 looks like it's DDB related to me. ps shows, root@strontium:/var/crash# ps -N debug.14 -M vmcore.14 -axl UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 1000 55894 1 0 18 0 1320 0 opause Is #C2 0:00.13 (zsh) 1000 60555 55894 0 28 0 1004 0 - R+ #C2 0:00.01 (groff) 1000 60703 55894 0 -6 0 892 0 pipecl DE+ #C2 0:00.01 (less) 1000 61398 60555 295 -6 0 1692 0 - R+ #C2 0:00.16 (troff) ... [unrelated things, I think] If anyone can shed any light on this, that'd be great. Thanks... -- Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 14:29:59 2000 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 84A7237C742; Thu, 23 Mar 2000 14:28:00 -0800 (PST) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id RAA12713; Thu, 23 Mar 2000 17:28:48 -0500 (EST) (envelope-from bandix@looksharp.net) Date: Thu, 23 Mar 2000 17:28:48 -0500 (EST) From: "Brandon D. Valentine" To: Mike Smith Cc: John Reynolds~ , stable@FreeBSD.ORG Subject: Re: What does "Voxware still supported in 4.0" mean exactly? In-Reply-To: <200003231801.KAA01088@mass.cdrom.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 Thu, 23 Mar 2000, Mike Smith wrote: >What makes you think that we haven't? The problem is simply that it's >very hard to _buy_ a lot of these cards, and if someone already has one, >asking them to send it to Cameron is a lot more effective than wasting a >day of my or Bill Swingle's time trying to find the one yak repair shop >and soundcard dealer in Outer Mongolia that still has one in stock, >finding some way of paying them in goat's cheese and then having Ghengis >Khan's last living relative stick the card into his yakskin bag and storm >all the way across Europe to deliver it. > >At last count, I think we've bought, borrowed and cajoled about twenty or >so cards and sent them off to Cameron. I don't know what makes you think >that we're _entirely_ stupid or greedy, especially since it's not like >it's a secret or anything that we do this regularly. I'd have to concur. I'd also have to add that purchasing cards "automatically" is a rather stupid idea. Unless you've got documentation in hand from the manufacturer it's often a futile effort to write a driver regardless of how many cards you've got. There is only so much reverse engineering can do for you. Not to mention the amount of time it takes to write a driver that way. If this guy really thinks this is such an issue(which I don't, I think the current methods work just dandy) he needs to develop an answer. One possible idea is an http accessible database that lists "want ads" from developers stating specifically what they have documentation for and would like to start hacking on. In this way people who have that extra hardware available could step up and enter it into the database. A developer could be free to choose whichever of the volunteered entries he would like and get the stuff mailed his way. If the owner would like his hardware back when the development process is over then the database would keep track of his identity(privately of course) for the developer to ship it back. ------------------------------------------------------------- | -Brandon D. Valentine bandix at looksharp.net | bandix on EFnet IRC BVRiker on AIM ------------------------------------------------------------- | "...and as for hackers, we note that all of those known to | The Register are so strapped financially that seizing their | property would be tantamount to squeezing blood from a | stone." -- The Register, 02/17/2000 ------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 14:38: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sstar.com (sstar.com [209.102.160.1]) by hub.freebsd.org (Postfix) with ESMTP id C98D437B65C for ; Thu, 23 Mar 2000 14:37:38 -0800 (PST) (envelope-from king@sstar.com) Received: from jking ([134.132.75.164]) by sstar.com with SMTP (IPAD 2.52) id 2722300; Thu, 23 Mar 2000 16:37:26 -0600 Message-ID: <00af01bf9518$5daf5a70$a44b8486@jking> From: "Jim King" To: "Jaye Mathisen" , References: Subject: Re: Samba perf in the toilet with 4.0 Date: Thu, 23 Mar 2000 16:37:26 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG fwiw, I'm getting 3-4 MB/sec on an Alpha running 4.0 from last week and Samba 2.0.6. ----- Original Message ----- From: "Jaye Mathisen" To: Sent: Thursday, March 23, 2000 4:12 PM Subject: Samba perf in the toilet with 4.0 > > > I have reviewed the mail logs about this, and messing with patch-ah didn't > fix anything for me. > > I just update my nicely working 3.4 box to 4.0-stable from a day ago. > > Connected from win2000, and was moving some files, and it just seemed > slow. > > So I look with netstat, and I'm getting less than 100k/second out of the > box. > > With 3.4, I was getting 3-4MB/sec. > > No errors, no collisions, 100mbit full duplex. > > I tried the 2.0.7 prerelease of samba and it isn't running any better. > > Not sure what's going on. May have to drop back to 3.4 if this isn't > easily fixed. > > Other than this issue, everything I've been using has worked fine. > > > > 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 Mar 23 14:45: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id AFF4737C5F2; Thu, 23 Mar 2000 14:44:44 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA05041; Thu, 23 Mar 2000 14:44:41 -0800 (PST) (envelope-from dillon) Date: Thu, 23 Mar 2000 14:44:41 -0800 (PST) From: Matthew Dillon Message-Id: <200003232244.OAA05041@apollo.backplane.com> To: Ben Smithurst Cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: repeatable lockup (pipe related?) References: <20000323222149.C87103@strontium.scientia.demon.co.uk> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : .SH foo, bar, baz : :and then a lot of junk text (I appended /etc/rc and /etc/rc.network). Then, :when I do : : nroff -ms foo.ms 2>&1 | less : :and quit 'less' straight away, the whole system seems to lockup. ^T :worked (sometimes), and showed troff using lots of system time (no user :time). ping from another host worked, ctrl-alt-esc dropped into DDB ok, :but that was about all. (ctrl-alt-del didn't work.) : :Of course, when it first happened I wasn't trying to process /etc/rc* Awweeesome :-) I was able to repeat it. Should be trivial to fix... obviously a bug in the pipe code somewhere. I'm working on it. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 14:58:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sr14.nsw-remote.bigpond.net.au (sr14.nsw-remote.bigpond.net.au [24.192.3.29]) by hub.freebsd.org (Postfix) with ESMTP id 7AB4537BB2B for ; Thu, 23 Mar 2000 14:58:05 -0800 (PST) (envelope-from a.reilly@lake.com.au) Received: from areilly.bpc-users.org (CPE-144-132-171-71.nsw.bigpond.net.au [144.132.171.71]) by sr14.nsw-remote.bigpond.net.au (Pro-8.9.3/8.9.3) with SMTP id JAA06672 for ; Fri, 24 Mar 2000 09:22:05 +1100 (EDT) Received: (qmail 71043 invoked by uid 1000); 23 Mar 2000 22:22:03 -0000 From: "Andrew Reilly" Date: Fri, 24 Mar 2000 09:22:03 +1100 To: "WMC, O'Gorman, James" Cc: Andrew Reilly , stable@FreeBSD.org Subject: Re: src/UPDATING for RELENG_3 to RELENG_4 upgrade works. Message-ID: <20000324092203.B66456@gurney.reilly.home> References: <20000323231057.A27794@gurney.reilly.home> <38DA4B34.179C6AD1@elwood.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <38DA4B34.179C6AD1@elwood.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 23, 2000 at 10:49:56AM -0600, WMC, O'Gorman, James wrote: > The one and only problem that I have had that I have not fixed yet is > with xdm. I had started it from rc.local before, but now when rc.local > starts is, the keyboard will not interact with it. If I comment out that > line, boot up normal and log in as root and then start xdm things are > fine. I have not put any effort into fixing it yet, so I am sure it is > something simple I am missing. Just turn the "off" to "on" in the ttyv8/xdm line in /etc/ttys. No need to fire it up from rc.anything. That has the added advantage of automatically restarting it, if the server breaks. -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 15:22:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from blockhead.mincom.com (blockhead2.mincom.com [203.15.57.33]) by hub.freebsd.org (Postfix) with ESMTP id 7EE7F37C64F for ; Thu, 23 Mar 2000 15:21:20 -0800 (PST) (envelope-from philh@mincom.com) Received: (from uucp@localhost) by blockhead.mincom.com (8.9.3/8.9.3) id JAA03988 for ; Fri, 24 Mar 2000 09:21:07 +1000 (EST) (envelope-from philh@mincom.com) Received: from porthole.mincom.oz.au(172.17.100.2) via SMTP by blockhead.mincom.oz.au, id smtpdjR3986; Fri Mar 24 09:21:00 2000 Received: (from philh@localhost) by porthole.mincom.oz.au (8.9.3/8.9.3/mincom) id JAA24183 for stable@freebsd.org; Fri, 24 Mar 2000 09:21:00 +1000 (EST) (envelope-from philh) Date: Fri, 24 Mar 2000 09:20:59 +1000 From: Phil Homewood To: stable@freebsd.org Subject: System lockup, 3.4-STABLE, two machines Message-ID: <20000324092059.R13576@mincom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The last two days have seen two lockups on one of our firewall machines. Box is pingable, accepts TCP connections but does nothing more. syslog shows it logging "MARK" every five minutes even when unresponsive. First thought: DoS attack. After cvsupping and recompiling kernel and world yesterday (and forgetting to do the sysctl's for restrict_rst and drop_synfin, d'oh!) it still locked up - but the running kernel had no DDB to investigate. (Now corrected.) So, I decide just for sanity to update one of our other firewall machines as well (as it didn't have the restrict_rst, drop_synfin and icmp_bandlim options). Halfway through "make update" it, too, locked up. Fortunately, this one has DDB compiled in, and I was able to escape to debugger. "trace" shows: db> trace Debugger(c0202755) at Debugger+0x37 scgetc(c0233d44,2,0,c0233d44,0) at scgetc+0x7d8 sckbdevent(c0233d44,0,0,0,c82ab360) at sckbdevent+0x58 atkbd_intr(c0233d44,0,0,0,c01cca5e) at atkbd_intr+0x1f atkbd_isa_intr(0,80000000,80000010,10,0) at atkbd_isa_intr+0x20 Xresume1() at Xresume1+0x2b --- interrupt, eip = 0xc01d588d, esp = 0xc020e244, ebp = 0 --- default_halt() at default_halt+0x1 I have a "ps" dump as well as some "show" output and a vmcore if it helps. Panic forced, system is now dumping (after "syncing disks" failed.) Does the above mean anything to anyone? We did see this behaviour a few months ago but since the last cvsup mid-January it's been behaving. The fact that two machines (similar configs) crashed within a short time of each other is making me think DoS, however it could be something benign in network code that is triggering the fault (if one firewall is unreachable, connections fall back to one of the others...) dmesg from the first machine (that crashed twice, without DDB): Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.4-STABLE #6: Thu Mar 23 13:47:35 MST 2000 root@:/usr/src/sys/compile/DENFW Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 400910905 Hz CPU: Pentium II/Xeon/Celeron (400.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 100663296 (98304K bytes) avail memory = 95154176 (92924K bytes) Preloaded elf kernel "kernel" at 0xc025b000. Pentium Pro MTRR support enabled Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip3: rev 0x02 on pci0.7.3 xl0: <3Com 3c905B-TX Fast Etherlink XL> rev 0x30 int a irq 10 on pci0.16.0 xl0: Ethernet address: 00:50:04:af:54:4e xl0: autoneg complete, link status good (half-duplex, 10Mbps) xl1: <3Com 3c905-TX Fast Etherlink XL> rev 0x00 int a irq 12 on pci0.17.0 xl1: Ethernet address: 00:60:97:93:61:a3 xl1: autoneg complete, link status good (half-duplex, 10Mbps) Probing for devices on PCI bus 1: vga0: rev 0x7a on pci1.0.0 Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A, console sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppi0: on ppbus 0 plip0: on ppbus 0 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to deny, logging limited to 100 packets/entry by default changing root device to wd0s1a and the second (the one where I got the ddb output above): Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.4-STABLE #2: Tue Jan 18 09:46:22 EST 2000 root@blocker.mincom.oz.au:/usr/src/sys/compile/BLOCKER Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 400911726 Hz CPU: Celeron (400.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183f9ff real memory = 134217728 (131072K bytes) avail memory = 127754240 (124760K bytes) Preloaded elf kernel "kernel" at 0xc027e000. Pentium Pro MTRR support enabled Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip3: rev 0x02 on pci0.7.3 xl0: <3Com 3c905B-TX Fast Etherlink XL> rev 0x30 int a irq 11 on pci0.14.0 xl0: Ethernet address: 00:10:5a:72:43:a0 xl0: autoneg complete, link status good (half-duplex, 10Mbps) xl1: <3Com 3c905B-TX Fast Etherlink XL> rev 0x24 int a irq 10 on pci0.18.0 xl1: Ethernet address: 00:10:4b:c5:b6:14 xl1: autoneg complete, link status good (half-duplex, 10Mbps) ahc0: rev 0x00 int a irq 15 on pci0.19.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs xl2: <3Com 3c905B-TX Fast Etherlink XL> rev 0x24 int a irq 15 on pci0.20.0 xl2: Ethernet address: 00:10:4b:c5:c3:4d xl2: autoneg complete, link status good (half-duplex, 10Mbps) Probing for devices on PCI bus 1: vga0: rev 0x7a on pci1.0.0 Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A, console sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (atapi): , removable, dma, iordis acd0: drive speed 6890KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked ppc0 not found vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface IP packet filtering initialized, divert disabled, rule-based forwarding disabled, logging limited to 100 packets/entry by default Waiting 2 seconds for SCSI devices to settle cda0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) hanging root device to da0s1a (The hardware was sourced from two different vendors - the firewalls are in two different countries.) I'm off to build world on the second machine in the hope that the TCP/ICMP changes recently will halt this game. But I'd like to know if anyone else has seen this, or knows whether I'm heading in the right direction with the DoS theory. Thanks in advance for any advice... -- This transmission is for the intended addressee only and is confidential information. If you have received this transmission in error, please delete it and notify the sender. The contents of this email are the opinion of the writer and are not endorsed by Mincom Ltd unless expressly stated otherwise. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 15:34:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tranq1.tranquility.net (tranq1.tranquility.net [206.156.230.1]) by hub.freebsd.org (Postfix) with ESMTP id A73D937B669 for ; Thu, 23 Mar 2000 15:34:17 -0800 (PST) (envelope-from stephen@math.missouri.edu) Received: from math.missouri.edu (stephen.tranquility.net [206.156.230.78]) by tranq1.tranquility.net (8.9.2/8.9.2) with ESMTP id RAA24702 for ; Thu, 23 Mar 2000 17:34:16 -0600 (CST) Message-ID: <38DAAA38.858C2A4B@math.missouri.edu> Date: Thu, 23 Mar 2000 17:35:20 -0600 From: Stephen Montgomery-Smith X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.0.36 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Problem with NIC card GFC2204 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just got a GFC2204 card and I'm trying to get it to work with FreeBSD 3.3 stable. So I added the ax0 device into the kernel config, compiled the kernel, and rebooted. Right at the beginning of the kernel's boot up, I got a panic with the message: ifmedia_set: no match for 0x0/0xffffffff This was just after it recognised the NIC card, and said the ethernet (??) address was 00:c0:ca:19:b6:06 (whatever that is). I can see in the program /sys/net/if_media.c where this panic is created, but otherwise I have no idea why it does this. I should add that this GFG2204 card has the AX88141 chip instead of the AX88140A chip that is listed in the FreeBSD handbook. -- Stephen Montgomery-Smith stephen@math.missouri.edu 307 Math Science Building stephen@showme.missouri.edu Department of Mathematics stephen@missouri.edu University of Missouri-Columbia Columbia, MO 65211 USA Phone (573) 882 4540 Fax (573) 882 1869 http://www.math.missouri.edu/~stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 15:36:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 325B637B58C; Thu, 23 Mar 2000 15:36:34 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id PAA35104; Thu, 23 Mar 2000 15:36:34 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 23 Mar 2000 15:36:34 -0800 (PST) From: Kris Kennaway To: robert bowen Cc: freebsd-stable@freebsd.org Subject: Re: What else to remove after 4.0 upgrade In-Reply-To: <200003232221.OAA03748@smartie.braingarage.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 Thu, 23 Mar 2000, robert bowen wrote: > Are there any binary files that have changed location or > gone away since 3.4-R? I saw the post on "cruft" but I > am worried that after a binary 4.0R upgrade there will > be some "leftovers" in /bin or /usr/bin that are not > overwritten by the new release (because they are not > included or changed in location) find / -ctime +<#foo> -ls where <#foo> is greater than the number of days since you installed 4.0-R but less than the time since your previous 3.4-R build. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 16: 8:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 6CE2B37C575; Thu, 23 Mar 2000 16:08:13 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p39-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.104]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id JAA18231; Fri, 24 Mar 2000 09:08:00 +0900 (JST) Message-ID: <38DAACEF.1F55DF96@newsguy.com> Date: Fri, 24 Mar 2000 08:46:55 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Charles Cox Cc: Cy Schubert - ITSD Open Systems Group , Andrew Gallatin , obrien@FreeBSD.ORG, Howard Leadmon , freebsd-alpha@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Compiler problems with -O2 (was Re: CVS Trouble, even under4.0-RELEASE (alpha) HELP!) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Charles Cox wrote: > > I would like to add that some of us who do a lot of numerically intensive > programming, and that need to squeeze every last available cycle out of > our CPU's would really appreciate having -O2 available for userland > programs. To me, getting rid of the -O2+ switch would be like outlawing > cars because someone had a really bad car accident. Just like driving a > car, using gcc and the -O2 switch safely are the USER's > responsibility. Having said this though, I do fully support having > comments in make.conf, and documentation elsewhere that cautions against > compiling a kernel with -O2. Whatever. Remember, though, that compiling with -O2 *WILL* result in bad code. It's not that someone had an accident. Is that the breaks don't work one time out of five. Just wait your turn... -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@zurichgnomes.bsdconspiracy.net One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 16:35:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id A5D1F37B5BE for ; Thu, 23 Mar 2000 16:35:40 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p39-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.104]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id JAA23779; Fri, 24 Mar 2000 09:35:00 +0900 (JST) Message-ID: <38DAB405.C57FD8F4@newsguy.com> Date: Fri, 24 Mar 2000 09:17:09 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: "Brandon D. Valentine" Cc: "Rodney W. Grimes" , Cy Schubert - ITSD Open Systems Group , Vivek Khera , stable@FreeBSD.ORG Subject: Re: "dangerously dedicated" References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Brandon D. Valentine" wrote: > > On i386 machines this is usually something lame like: > NO ROM BASIC > SYSTEM HALTED > despite the fact that no machine has included a ROM BASIC since the last > of the IBM PS/2 386s came out. However most of the BIOSes until *very* > recently still contained code that would check for a ROM BASIC after > searching the entire drive list and try booting from that. Now if only > we could convince them to put that back in except have it look for a > forth interpreter in ROM. Nah, that's the wrong approach. The right approach is for that BIOS *be* written in Forth to begin with. OpenBoot, anyone? :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@zurichgnomes.bsdconspiracy.net One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 16:54: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9A03F37BB0B; Thu, 23 Mar 2000 16:53:54 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA06073; Thu, 23 Mar 2000 16:53:53 -0800 (PST) (envelope-from dillon) Date: Thu, 23 Mar 2000 16:53:53 -0800 (PST) From: Matthew Dillon Message-Id: <200003240053.QAA06073@apollo.backplane.com> To: Matthew Dillon Cc: Ben Smithurst , hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: repeatable lockup (pipe related?) References: <20000323222149.C87103@strontium.scientia.demon.co.uk> <200003232244.OAA05041@apollo.backplane.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :: .SH foo, bar, baz :: ::and then a lot of junk text (I appended /etc/rc and /etc/rc.network). Then, ::when I do :: :: nroff -ms foo.ms 2>&1 | less :: ::and quit 'less' straight away, the whole system seems to lockup. ^T ::worked (sometimes), and showed troff using lots of system time (no user ::time). ping from another host worked, ctrl-alt-esc dropped into DDB ok, I've committed a fix to this in -current, 4.x, and 3.x. Rev 1.61 kern/sys_pipe.c (current), 1.60.2.1 in RELENG_4, something else in RELENG_3. Sorry 2.2.x'rs, three is my limit :-) What happens is that the pipe writer checks for the reader going away before entering the while() loop on the write, but only checks sporatically inside that loop. There are situations where the reader may go away while the writer is blocked and cause the writer to enter into an infinite loop because the writer believes there is a reader 'reading' when, in fact, the reader side is stuck in pipeclose(). They two sides then play ping-pong tsleep/wakeup with each other forever. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 16:56:13 2000 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 490E537C5DC for ; Thu, 23 Mar 2000 16:56:06 -0800 (PST) (envelope-from djkanter@nwu.edu) Received: (from mailnull@localhost) by hecky.it.northwestern.edu (8.8.7/8.8.7) id SAA13348 for ; Thu, 23 Mar 2000 18:56:05 -0600 (CST) Received: from localhost.localdomain (coconut-25-028045.nuts.nwu.edu [165.124.28.45]) by hecky.acns.nwu.edu via smap (V2.0) id xma013185; Thu, 23 Mar 00 18:55:35 -0600 Received: (from david@localhost) by localhost.localdomain (8.9.3/8.9.3) id SAA88731 for freebsd-stable@freebsd.org; Thu, 23 Mar 2000 18:11:54 -0600 (CST) (envelope-from david) Date: Thu, 23 Mar 2000 18:11:53 -0600 From: David Kanter To: FreeBSD stable Subject: C++ writing/compiling with 3.4 stable Message-ID: <20000323181153.A88716@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Organization: Northwestern University X-Operating-System: FreeBSD localhost.localdomain 3.4-STABLE FreeBSD 3.4-STABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How ANSI/ISO-compliant is 3.4 stable? I ask because compiling a C++ program I just wrote needed the header files with the .h extension, and didn't like using namespace std; And which version of gcc should I use? There is a 2.95 (egcs) and 2.8.1 (gcc) but the glibstdc++ seems to want 2.8.1 -- David Kanter djkanter@nwu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 17: 1:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 0111A37B5F2 for ; Thu, 23 Mar 2000 17:01:56 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id RAA10548; Thu, 23 Mar 2000 17:01:53 -0800 (PST) Date: Thu, 23 Mar 2000 17:01:53 -0800 From: Brooks Davis To: David Kanter Cc: FreeBSD stable Subject: Re: C++ writing/compiling with 3.4 stable Message-ID: <20000323170153.A9236@orion.ac.hmc.edu> References: <20000323181153.A88716@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <20000323181153.A88716@localhost.localdomain>; from djkanter@nwu.edu on Thu, Mar 23, 2000 at 06:11:53PM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 23, 2000 at 06:11:53PM -0600, David Kanter wrote: > How ANSI/ISO-compliant is 3.4 stable? I ask because compiling a C++ program > I just wrote needed the header files with the .h extension, and didn't like > using namespace std; > > And which version of gcc should I use? There is a 2.95 (egcs) and 2.8.1 > (gcc) but the glibstdc++ seems to want 2.8.1 You're almost certaintly going to want 2.95. It's much closer to ANSI compliance. If you can, you might want to consider upgrading to 4.0 as it has gcc 2.95.2 built in. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 17: 8: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 35AF037BB9D for ; Thu, 23 Mar 2000 17:07:51 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA37075 for ; Thu, 23 Mar 2000 18:07:42 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA45828 for ; Thu, 23 Mar 2000 18:07:37 -0700 (MST) Message-Id: <200003240107.SAA45828@harmony.village.org> Subject: Re: What does "Voxware still supported in 4.0" mean exactly? To: stable@FreeBSD.ORG In-reply-to: Your message of "Thu, 23 Mar 2000 17:28:48 EST." References: Date: Thu, 23 Mar 2000 18:07:37 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I know that Walnut creek was most generous in their support of me in my cardbus efforts. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 17: 9:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8692A37B942 for ; Thu, 23 Mar 2000 17:09:52 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA37087; Thu, 23 Mar 2000 18:09:50 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA45855; Thu, 23 Mar 2000 18:09:46 -0700 (MST) Message-Id: <200003240109.SAA45855@harmony.village.org> To: David Kanter Subject: Re: C++ writing/compiling with 3.4 stable Cc: FreeBSD stable In-reply-to: Your message of "Thu, 23 Mar 2000 18:11:53 CST." <20000323181153.A88716@localhost.localdomain> References: <20000323181153.A88716@localhost.localdomain> Date: Thu, 23 Mar 2000 18:09:46 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000323181153.A88716@localhost.localdomain> David Kanter writes: : How ANSI/ISO-compliant is 3.4 stable? I ask because compiling a C++ program : I just wrote needed the header files with the .h extension, and didn't like : using namespace std; : : And which version of gcc should I use? There is a 2.95 (egcs) and 2.8.1 : (gcc) but the glibstdc++ seems to want 2.8.1 Use 2.95. 2.8.1 is better than 2.7, but still has some significant issues in the dark corners of the language. Don't worry about glibstdc++... It has been subsumed by libstdc++. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 17:26:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from firebat.Bushong.NET (c128625-a.frmt1.sfba.home.com [24.5.196.12]) by hub.freebsd.org (Postfix) with ESMTP id 335F937C5B4 for ; Thu, 23 Mar 2000 17:26:40 -0800 (PST) (envelope-from dbushong@firebat.Bushong.NET) Received: (from dbushong@localhost) by firebat.Bushong.NET (8.9.3/8.9.3) id RAA48438; Thu, 23 Mar 2000 17:25:46 -0800 (PST) (envelope-from dbushong) Date: Thu, 23 Mar 2000 17:25:42 -0800 From: David Bushong To: Mikhail Teterin Cc: "WMC, O'Gorman, James" , stable@FreeBSD.ORG Subject: Re: starting xdm (Re: src/UPDATING for RELENG_3 to RELENG_4 upgrade works.) Message-ID: <20000323172542.I49204@Bushong.NET> References: <38DA4B34.179C6AD1@elwood.net> <200003231654.LAA28916@rtfm.newton> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003231654.LAA28916@rtfm.newton>; from mi@kot.ne.mediaone.net on Thu, Mar 23, 2000 at 11:54:50AM -0500 X-Floating-Sheep-Port: 0xbaa Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My friend also noted that X has a little document feature where you can tell it which vty to start on, solving the race condition (which I ran into as well). Just change in the line in /usr/X11R6/lib/X11/xdm/Xservers (or /etc/X11/xdm/Xservers if you're running XFree86 4.0) from: :0 local /usr/X11R6/bin/X to :0 local /usr/X11R6/bin/X vt8 This assumes you want X on /dev/ttyv7, a.k.a. F8 The advantage of this over the /etc/ttys method is that you can actually kill off xdm without editing /etc/ttys and HUPing init. --David Bushong On Thu, Mar 23, 2000 at 11:54:50AM -0500, Mikhail Teterin wrote: > WMC, O'Gorman, James once stated: > > =The one and only problem that I have had that I have not fixed yet > =is with xdm. I had started it from rc.local before, but now when > =rc.local starts is, the keyboard will not interact with it. If I > =comment out that line, boot up normal and log in as root and then > =start xdm things are fine. I have not put any effort into fixing it > =yet, so I am sure it is something simple I am missing. > > I had that problem -- don't know why, but if you put a 1 or 2 second > delay into the rc.local before xdm it will start nicely. > > The right way is, probably, to fire it from /etc/ttys -- see the xdm > entry there and change ``off'' to ``on''... Then (if you do not have > X running) ``kill -1 1''. > > -mi > > > 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 Mar 23 19:55:12 2000 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 A02A937C511 for ; Thu, 23 Mar 2000 19:55:08 -0800 (PST) (envelope-from djkanter@nwu.edu) Received: (from mailnull@localhost) by hecky.it.northwestern.edu (8.8.7/8.8.7) id VAA17294 for ; Thu, 23 Mar 2000 21:55:07 -0600 (CST) Received: from localhost.localdomain (areca-47-028115.nuts.nwu.edu [165.124.28.115]) by hecky.acns.nwu.edu via smap (V2.0) id xma017270; Thu, 23 Mar 00 21:54:47 -0600 Received: (from david@localhost) by localhost.localdomain (8.9.3/8.9.3) id VAA97116 for freebsd-stable@FreeBSD.ORG; Thu, 23 Mar 2000 21:54:42 -0600 (CST) (envelope-from david) Date: Thu, 23 Mar 2000 21:54:40 -0600 From: David Kanter To: FreeBSD stable Subject: Re: C++ writing/compiling with 3.4 stable Message-ID: <20000323215440.A97097@localhost.localdomain> References: <20000323181153.A88716@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000323181153.A88716@localhost.localdomain>; from djkanter@nwu.edu on Thu, Mar 23, 2000 at 06:11:53PM -0600 X-Organization: Northwestern University X-Operating-System: FreeBSD localhost.localdomain 3.4-STABLE FreeBSD 3.4-STABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm a little worried here: I just did make deinstall in the 2.8.1 directory, but gcc still exists on the system. I'm making 2.95 now, but is there going to be some kind of conflict, i.e., two versions on the same box? I don't get the feeling 2.8.1 is totally off the system...even though the package name no longer shows up. And which library ports should I get? Will they automatically come with the 2.95 make? On Thu, Mar 23, 2000 at 06:11:53PM -0600, David Kanter wrote: > How ANSI/ISO-compliant is 3.4 stable? I ask because compiling a C++ program > I just wrote needed the header files with the .h extension, and didn't like > using namespace std; > > And which version of gcc should I use? There is a 2.95 (egcs) and 2.8.1 > (gcc) but the glibstdc++ seems to want 2.8.1 > -- > David Kanter > djkanter@nwu.edu > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message ---end quoted text--- -- David Kanter djkanter@nwu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 19:55:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from shell13.ba.best.com (shell13.ba.best.com [206.184.139.144]) by hub.freebsd.org (Postfix) with ESMTP id 074E537C54B for ; Thu, 23 Mar 2000 19:55:25 -0800 (PST) (envelope-from rone@ennui.org) Received: (from rone@localhost) by shell13.ba.best.com (8.9.3/8.9.2/best.sh) id TAA21830; Thu, 23 Mar 2000 19:55:10 -0800 (PST) From: remorse code Message-Id: <200003240355.TAA21830@shell13.ba.best.com> Subject: Re: What does "Voxware still supported in 4.0" mean exactly? In-Reply-To: <200003240107.SAA45828@harmony.village.org> from Warner Losh at "Mar 23, 0 06:07:37 pm" To: imp@village.org (Warner Losh) Date: Thu, 23 Mar 2000 19:55:09 -0800 (PST) Cc: stable@FreeBSD.ORG X-URL: http://ennui.org/rone/ X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh writes: I know that Walnut creek was most generous in their support of me in my cardbus efforts. Walnut Creek gave me $2.1 million! rone -- Insultant: n. Contract worker who gets paid an obscene hourly wage to insult full-time company employees. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 19:55:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from vivaldi.pn.npi.msu.ru (gw.pn.npi.msu.ru [193.232.127.202]) by hub.freebsd.org (Postfix) with ESMTP id BB0C337C54B for ; Thu, 23 Mar 2000 19:55:31 -0800 (PST) (envelope-from svysh@pn.sinp.msu.ru) Received: from handel (handel [195.208.223.24]) by vivaldi.pn.npi.msu.ru (8.10.0/8.10.0) with SMTP id e2O3tD400708; Fri, 24 Mar 2000 06:55:17 +0300 (MSK) Message-Id: <3.0.5.32.20000324065537.007bc7d0@vivaldi> X-Sender: svysh@vivaldi (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Fri, 24 Mar 2000 06:55:37 +0300 To: freebsd-stable@freebsd.org From: Sergei Vyshenski Subject: perl vs buildworld and piping in 4.0 Cc: genew@home.com, laa@zgia.zp.ua Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Was only able to build perl inside buildworld, after switching off of all compiler optimization and piping in make.conf (that is returning to default #CFLAGS= -O -pipe ) More to that, previous (crashed) runs of buildword, left ill configuration files in /usr/src/contrib/perl5/..., which survived subsequent run of "make clean" in /usr/src. Had to spot them by date, and remove by hand. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 19:59:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 5058E37C08A for ; Thu, 23 Mar 2000 19:59:46 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA29183; Thu, 23 Mar 2000 19:59:53 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Toshifumi Kawai Cc: freebsd-stable@FreeBSD.ORG Subject: Re: In-reply-to: Your message of "Thu, 23 Mar 2000 19:36:46 +0900." <4.2.0.58.J.20000323193524.00a3bd50@mail.yyy.or.jp> Date: Thu, 23 Mar 2000 19:59:53 -0800 Message-ID: <29180.953870393@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you're receiving this message, it's because you just sent a "subscribe" message erroneously to one of our mailing lists, resulting in thousands (and, in some cases, tens of thousands) of people seeing a "subscribe me" message in their mailboxes when they have absolutely nothing to do with the process of adding users like yourself to our mailing lists. This is a poor introduction, at best, and what we really suggest to people is that they read our mailing list FAQ at: http://www.freebsd.org/handbook/eresources.html#ERESOURCES-MAIL Paying particular attention to section 27.1.2: "How to subscribe." You should also be very sure to read section 27.1.3 as well, the mailing list charters. These describe very precisely just how each mailing list may be used and the range of topics allowed for each one. This will help you from making the SECOND most common new user mistake which is to post messages on subject A incorrectly to a mailing list devoted exclusively to the discussion of subject B. The FreeBSD mailing lists have gotten simply huge, with discussion traffic often exceeding 500,000 messages a week, and your cooperation is greatly appreciated in trying to keep the "noise level" down to manageable proportions so that those actually involved in project development, as well as the users of the project, can remain active members of the mailing lists. Thank you. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 22:11:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from isds.duke.edu (davinci.isds.duke.edu [152.3.22.1]) by hub.freebsd.org (Postfix) with ESMTP id 1581D37B64C for ; Thu, 23 Mar 2000 22:11:32 -0800 (PST) (envelope-from sto@stat.Duke.EDU) Received: from cayenne.isds.duke.edu (cayenne.isds.duke.edu [152.3.22.11]) by isds.duke.edu (8.8.8/8.8.8) with ESMTP id BAA30444 for ; Fri, 24 Mar 2000 01:11:31 -0500 (EST) Received: (from sto@localhost) by cayenne.isds.duke.edu (8.8.8/8.8.8) id BAA10646 for freebsd-stable@FreeBSD.ORG; Fri, 24 Mar 2000 01:11:30 -0500 (EST) Date: Fri, 24 Mar 2000 01:11:30 -0500 From: "Sean O'Connell" To: FreeBSD stable Subject: 4.0-RELEASE ISO and XDM authentication failure Message-ID: <20000324011130.F10585@stat.Duke.EDU> Reply-To: "Sean O'Connell" Mail-Followup-To: FreeBSD stable Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Organization: Institute of Statistics and Decision Sciences Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi- I downloaded the 4.0 iso image and installed it on my Sony 505TR. It went quite well. The only odd thing I had to do was ifconfig ep0 up when trying to get at the cdrom via nfs. The machine is nearly back to functional. There was one thing that surprised me and I hadn't noticed this in the RC series was that xdm is trying to use XDM-AUTHENTICATION-1 by default and it failed miserably. I install XFree86 from within sysinstall (not the package). I had to add an entry: DisplayManager._0.authName: MIT-MAGIC-COOKIE-1 otherwise, I couldn't login ... I suppose that I could actually shoot for tougher security on xdm, but I have never had this happen to me before. Not sure what happened. S ----------------------------------------------------------------------- Sean O'Connell Email: sean@stat.Duke.EDU Institute of Statistics and Decision Sciences Phone: (919) 684-5419 Duke University Fax: (919) 684-8594 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 22:19:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 8E3A637B6A2 for ; Thu, 23 Mar 2000 22:19:17 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA29520; Thu, 23 Mar 2000 22:19:26 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: deimos Cc: stable@freebsd.org Subject: Re: What does "Voxware still supported in 4.0" mean exactly? In-reply-to: Your message of "Wed, 22 Mar 2000 22:33:30 EST." <38D9908A.C2D5773D@lewman.org> Date: Thu, 23 Mar 2000 22:19:26 -0800 Message-ID: <29517.953878766@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Send mail to cg@freebsd.org and he should be able to provide you with all his address information. Thanks! - Jordan > This is a cryptographically signed message in MIME format. > > --------------ms8142795EBC0CAB6A00251423 > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > > "Jordan K. Hubbard" wrote: > > > > Why not send us one and we'll have Cameron Grant look at it? He is > > somewhat constrained by the hardware available to him, and being off > > in the UK and stuck in a wheelchair to boot doesn't exactly give him > > the best access. > > To where do I mail one? I'll happily spend the $25 for an AWE64Gold. > As for the Diamond Fusion, I may buy one for him as well, as long as I > get it back when the drivers work. :P > > -- > > | Andy | e-mail | web | > | | andy@lewman.com | www.lewman.com | > > Know thyself. If you need help, call the C.I.A. > --------------ms8142795EBC0CAB6A00251423 > Content-Type: application/x-pkcs7-signature; name="smime.p7s" > Content-Transfer-Encoding: base64 > Content-Disposition: attachment; filename="smime.p7s" > Content-Description: S/MIME Cryptographic Signature > > MIIJkAYJKoZIhvcNAQcCoIIJgTCCCX0CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC > B10wggQnMIIDkKADAgECAhAXN8ogLRsvAwDJMiA8WgnMMA0GCSqGSIb3DQEBBAUAMIHMMRcw > FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y > azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 > IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp > dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTk5MDUxMDAwMDAw > MFoXDTAwMDUwOTIzNTk1OVowggEPMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE > CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y > ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV > UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO > ZXRzY2FwZSBGdWxsIFNlcnZpY2UxFjAUBgNVBAMUDUFuZHJldyBMZXdtYW4xHjAcBgkqhkiG > 9w0BCQEWD2FuZHlAbGV3bWFuLmNvbTBcMA0GCSqGSIb3DQEBAQUAA0sAMEgCQQC/EaQmMjUQ > gdB4D3aH5as3M8CQY0I1RmgYevC7MoGkHezh80n+0XeGNEYE6LpMtwnAmv4NYPbwktR2EAz1 > RaTPAgMBAAGjggEGMIIBAjAJBgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUB > BwEBMIGOMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsG > AQUFBwICMFYwFRYOVmVyaVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3Jw > LiBieSByZWZlcmVuY2UgbGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEE > BAMCB4AwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xhc3Mx > LmNybDANBgkqhkiG9w0BAQQFAAOBgQBLxOO6fPb6g7wDdf3nyY05xisVS88KGnl3MXhU4Y7N > /rdCNVgoDy4Yj7qrdieJUMLAKZq91PkshncU4Ezzj94H8jmsbwSLOod9biAJ3s58fL6MREdD > vH0Xp0cw9k3JMpi4ipM5DkYfbeiCCczfvgYyY7Jly4cl/Iw08l4yQK239TCCAy4wggKXoAMC > AQICEQDSdi6NFAw9fbKoJV2v7g11MA0GCSqGSIb3DQEBAgUAMF8xCzAJBgNVBAYTAlVTMRcw > FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMgUHJpbWFy > eSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw05ODA1MTIwMDAwMDBaFw0wODA1MTIyMzU5 > NTlaMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1 > c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJ > bmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3Mg > MSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMIGfMA0G > CSqGSIb3DQEBAQUAA4GNADCBiQKBgQC7WkSKBBa7Vf0DeootlE8VeDa4DUqyb5xUv7zodyqd > ufBou5XZMUFweoFLuUgTVi3HCOGEQqvAopKrRFyqQvCCDgLpL/vCO7u+yScKXbawNkIztW5U > iE+HSr8Z2vkV6A+HthzjzMaajn9qJJLj/OBluqexfu/J2zdqyErICQbkmQIDAQABo3wwejAR > BglghkgBhvhCAQEEBAMCAQYwRwYDVR0gBEAwPjA8BgtghkgBhvhFAQcBATAtMCsGCCsGAQUF > BwIBFh93d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBMA8GA1UdEwQIMAYBAf8CAQAw > CwYDVR0PBAQDAgEGMA0GCSqGSIb3DQEBAgUAA4GBAIi4Nzvd2pQ3AK2qn+GBAXEekmptL/bx > ndPKZDjcG5gMB4ZbhRVqD7lJhaSV8Rd9Z7R/LSzdmkKewz60jqrlCwbe8lYq+jPHvhnXU0zD > vcjjF7WkSUJj7MKmFw9dWBpJPJBcVaNlIAD9GCDlX4KmsaiSxVhqwY0DPOvDzQWikK5uMYIB > +zCCAfcCAQEwgeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp > U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv > cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln > biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0 > ZWQCEBc3yiAtGy8DAMkyIDxaCcwwCQYFKw4DAhoFAKCBsTAYBgkqhkiG9w0BCQMxCwYJKoZI > hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMDAzMjMwMzMzMzBaMCMGCSqGSIb3DQEJBDEWBBTL > fqNEhl4OM5M1P1GsoLio9ue8wDBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG > SIb3DQMCAgIAgDAHBgUrDgMCBzANBggqhkiG9w0DAgIBQDANBggqhkiG9w0DAgIBKDANBgkq > hkiG9w0BAQEFAARAuQX9xlvgCVg9+MrDjRZcrQ239Az9rhJUyvoWbDTUkqzEgfpAjepxlATA > HFAzVTAupKmlIbQ7cd8MgMg7TIS5ww== > --------------ms8142795EBC0CAB6A00251423-- > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 22:40:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 6CD3D37BB8B for ; Thu, 23 Mar 2000 22:40:06 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA30102; Thu, 23 Mar 2000 22:39:28 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: John Reynolds~ Cc: stable@FreeBSD.ORG Subject: Re: What does "Voxware still supported in 4.0" mean exactly? In-reply-to: Your message of "Thu, 23 Mar 2000 10:09:28 MST." <14554.20424.548258.530333@hip186.ch.intel.com> Date: Thu, 23 Mar 2000 22:39:28 -0800 Message-ID: <30099.953879968@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Rather than having a user send Cameron Grant a Diamond Fusion Card, or any > other "bleeding edge" or "old 'n' crusty" sound card to play with, shouldn't > FreeBSD, Inc. or Walnut Creek itself be proactively shipping willing > developers like this all the hardware they can purchase? I know that it is It already purchases tens of thousands of dollars worth of such equipment a year. We can't do it all, however, and need your help. Some of it isn't even the money, it's the time of individuals we can't really spare right now to go out and purchase/ship the stuff. From that perspective, it makes far more sense to have dozens or even hundreds of people providing stuff directly to developers rather than somehow expecting one very small organization to handle each and everyone's needs. That's just not even possible. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 23 22:54:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from server1.huntsvilleal.com (server1.huntsvilleal.com [207.13.224.7]) by hub.freebsd.org (Postfix) with ESMTP id B018E37B6EC for ; Thu, 23 Mar 2000 22:54:29 -0800 (PST) (envelope-from kris@hiwaay.net) Received: from barricuda.bsd.nws.net (kris.huntsvilleal.com [207.13.224.46]) by server1.huntsvilleal.com (8.9.3/8.9.3) with ESMTP id BAA02067; Fri, 24 Mar 2000 01:35:35 -0500 Received: from localhost (localhost [127.0.0.1]) by barricuda.bsd.nws.net (8.9.3/8.9.3) with ESMTP id AAA69779; Fri, 24 Mar 2000 00:54:23 -0600 (CST) (envelope-from kris@hiwaay.net) Date: Fri, 24 Mar 2000 00:54:23 -0600 (CST) From: Kris Kirby To: "Jordan K. Hubbard" Cc: John Reynolds~ , stable@FreeBSD.ORG Subject: Re: What does "Voxware still supported in 4.0" mean exactly? In-Reply-To: <30099.953879968@zippy.cdrom.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 ----- Kris Kirby, KE4AHR | TGIFreeBSD... 'Nuff said. | ------------------------------------------------------- "God gave them the ability to reproduce... ... Science gave us the hope they won't." -KBK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 0:28:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ZGIA.zp.ua (ZGIA.zp.ua [212.35.173.98]) by hub.freebsd.org (Postfix) with ESMTP id 9109637BCAF for ; Fri, 24 Mar 2000 00:27:59 -0800 (PST) (envelope-from laa@zgia.zp.ua) Received: from localhost (laa@localhost) by ZGIA.zp.ua (8.9.3/8.9.3) with ESMTP id KAA85456 for ; Fri, 24 Mar 2000 10:25:58 +0200 (EET) (envelope-from laa@zgia.zp.ua) Date: Fri, 24 Mar 2000 10:25:58 +0200 (EET) From: Alexandr Listopad To: stable@freebsd.org Subject: building kernel 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 cvsuped a few hours ago RELENG_4: root@vic# cd /usr/src/sys/i386/conf root@vic# config -r Laa Removing old directory ../../compile/Laa: Done. Don't forget to do a ``make depend'' Kernel build directory is ../../compile/Laa root@vic# cd ../../compile/Laa root@vic# make depend all install : ... -mpreferred-stack-boundary=2 setdef1.c touch hack.c cc -elf -shared -nostdlib hack.c -o hack.So rm -f hack.c sh ../../conf/newvers.sh LAA cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing -prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -no stdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 vers.c linking kernel vpo.o: In function `vpo_attach': vpo.o(.text+0xcf): undefined reference to `cam_simq_alloc' vpo.o(.text+0x100): undefined reference to `cam_sim_alloc' vpo.o(.text+0x110): undefined reference to `cam_simq_free' vpo.o(.text+0x11e): undefined reference to `xpt_bus_register' vpo.o(.text+0x13a): undefined reference to `xpt_create_path' vpo.o(.text+0x153): undefined reference to `xpt_bus_deregister' vpo.o(.text+0x15d): undefined reference to `cam_sim_free' vpo.o: In function `vpo_action': vpo.o(.text+0x459): undefined reference to `xpt_done' vpo.o(.text+0x469): undefined reference to `xpt_ Stop in /usr/src/sys/compile/Laa. root@vic# -- Laa. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 0:39:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 57C0D37BB8D for ; Fri, 24 Mar 2000 00:39:14 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id AAA99528; Fri, 24 Mar 2000 00:38:47 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38DB2997.B5F6FDCD@gorean.org> Date: Fri, 24 Mar 2000 00:38:47 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0322 i386) X-Accept-Language: en MIME-Version: 1.0 To: Sergei Vyshenski Cc: freebsd-stable@freebsd.org, genew@home.com, laa@zgia.zp.ua Subject: Re: perl vs buildworld and piping in 4.0 References: <3.0.5.32.20000324065537.007bc7d0@vivaldi> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sergei Vyshenski wrote: > > Was only able to build perl inside buildworld, after > switching off of all compiler optimization and piping in make.conf > (that is returning to default > #CFLAGS= -O -pipe > ) > > More to that, previous (crashed) runs of buildword, > left ill configuration files in /usr/src/contrib/perl5/..., > which survived subsequent run of "make clean" in /usr/src. > Had to spot them by date, and remove by hand. 'make cleandir' in /usr/src should get all of those. If it doesn't, please send a PR. (Come to think of it, TMK there shouldn't be any files created in /usr/src by a buildworld...) Good luck in any case, Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 3:22:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from node11a94.a2000.nl (node11a94.a2000.nl [24.132.26.148]) by hub.freebsd.org (Postfix) with SMTP id A68C237B60A for ; Fri, 24 Mar 2000 03:22:49 -0800 (PST) (envelope-from ronald@node11a94.a2000.nl) Received: (qmail 57546 invoked from network); 24 Mar 2000 11:22:44 -0000 Received: from node11a94.a2000.nl (24.132.26.148) by node11a94.a2000.nl with SMTP; 24 Mar 2000 11:22:44 -0000 Date: Fri, 24 Mar 2000 12:22:43 +0100 (CET) From: Ronald Klop To: David Kanter Cc: FreeBSD stable Subject: Re: C++ writing/compiling with 3.4 stable In-Reply-To: <20000323215440.A97097@localhost.localdomain> 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, 23 Mar 2000, David Kanter wrote: > I'm a little worried here: I just did make deinstall in the 2.8.1 directory, > but gcc still exists on the system. I'm making 2.95 now, but is there going > to be some kind of conflict, i.e., two versions on the same box? I don't get > the feeling 2.8.1 is totally off the system...even though the package name > no longer shows up. Installing 2.95 from the ports will create a binary named g++295 or something like that. It confused me ones, because g++ will still be the old version. If you are using bash, 'g++' will help to find all the g++ versions. Succes, Ronald. > > And which library ports should I get? Will they automatically come with the > 2.95 make? > > On Thu, Mar 23, 2000 at 06:11:53PM -0600, David Kanter wrote: > > How ANSI/ISO-compliant is 3.4 stable? I ask because compiling a C++ program > > I just wrote needed the header files with the .h extension, and didn't like > > using namespace std; > > > > And which version of gcc should I use? There is a 2.95 (egcs) and 2.8.1 > > (gcc) but the glibstdc++ seems to want 2.8.1 > > -- > > David Kanter > > djkanter@nwu.edu > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > ---end quoted text--- > > -- Ronald Klop http://node11a94.a2000.nl/~ronald/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 4:39:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 023F137B686 for ; Fri, 24 Mar 2000 04:39:29 -0800 (PST) (envelope-from jedgar@fxp.org) Received: from earth.fxp (oca-u1-17.hitter.net [207.192.78.17]) by pawn.primelocation.net (Postfix) with ESMTP id EE1509B17; Fri, 24 Mar 2000 07:39:21 -0500 (EST) Date: Fri, 24 Mar 2000 07:39:21 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: jedgar@earth.fxp To: Alexandr Listopad Cc: stable@freebsd.org Subject: Re: building kernel 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 Fri, 24 Mar 2000, Alexandr Listopad wrote: > vpo.o: In function `vpo_attach': > vpo.o(.text+0xcf): undefined reference to `cam_simq_alloc' > vpo.o(.text+0x100): undefined reference to `cam_sim_alloc' > vpo.o(.text+0x110): undefined reference to `cam_simq_free' > vpo.o(.text+0x11e): undefined reference to `xpt_bus_register' > vpo.o(.text+0x13a): undefined reference to `xpt_create_path' > vpo.o(.text+0x153): undefined reference to `xpt_bus_deregister' > vpo.o(.text+0x15d): undefined reference to `cam_sim_free' > vpo.o: In function `vpo_action': > vpo.o(.text+0x459): undefined reference to `xpt_done' > vpo.o(.text+0x469): undefined reference to `xpt_ > You are trying to compile in vpo support without the required scsi support. From LINT: # vpo Iomega Zip Drive # Requires SCSI disk support ('scbus' and 'da'), best # performance is achieved with ports in EPP 1.9 mode. ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: 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 Fri Mar 24 6:34:40 2000 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 4802C37B657 for ; Fri, 24 Mar 2000 06:34:35 -0800 (PST) (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 GAA03294; Fri, 24 Mar 2000 06:31:20 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda03292; Fri Mar 24 06:31:15 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id GAA07299; Fri, 24 Mar 2000 06:31:15 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdEt7291; Fri Mar 24 06:31:09 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id GAA05074; Fri, 24 Mar 2000 06:31:08 -0800 (PST) Message-Id: <200003241431.GAA05074@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdub5070; Fri Mar 24 06:30:53 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: John Reynolds~ Cc: stable@FreeBSD.ORG Subject: Re: What does "Voxware still supported in 4.0" mean exactly? In-reply-to: Your message of "Thu, 23 Mar 2000 10:09:28 MST." <14554.20424.548258.530333@hip186.ch.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Mar 2000 06:30:53 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14554.20424.548258.530333@hip186.ch.intel.com>, John Reynolds~ writ es: > > [ On Wednesday, March 22, Jordan K. Hubbard wrote: ] > > > What about those of us with AWE64 GOLD boards? The board itself does > > > quite well with most PCI based boards available today. As for upgrades, > > > would a Vibra16 really count as an upgrade? > > > > Why not send us one and we'll have Cameron Grant look at it? He is > > somewhat constrained by the hardware available to him, and being off > > in the UK and stuck in a wheelchair to boot doesn't exactly give him > > the best access. > > > > > If we're going to be forced to use newer boards, what about > > > SoundBlaster Live, Diamond Fusion, and other modern Aureal/Dolby based > > > PCI sound boards? Will pcm support those out of the box, or are we now > > > going to have to wait for some other driver to be developed? > > > > It doesn't support them out of the box now, but I can tell you that > > Cameron is certainly working on at least the Soundblaster Live support > > since we did send him one and I've heard him complaining bitterly > > about it on several occasions. :) If somebody wants to send him > > a Diamond Fusion card, I would be happy to "broker" the deal. > > The following is not venom directed at jkh, or anybody in general--it is an > honest question/statement/opinion: > > Rather than having a user send Cameron Grant a Diamond Fusion Card, or any > other "bleeding edge" or "old 'n' crusty" sound card to play with, shouldn't > FreeBSD, Inc. or Walnut Creek itself be proactively shipping willing > developers like this all the hardware they can purchase? I know that it is > done, has been done, and will continue to be done--it just seems to me like > another appropriate time to spend <= $100US from the profits generated by CD > sales. > > There are many many of us who faithfully buy the CD subscription and basicall > y > use the discs as shiny playtoys for our toddlers. I will continue to buy it > too because "money gets rolled back into the project for further development" > and with such limited time, that's how I "support" FreeBSD (along with > evangelism being the only "FreeBSD leper" here at work amongst the > Linux-ites). > > I think that users sending people who have the time and talent for writing > drivers for the hardware is a grand idea. But, I think an equally grand idea > is onsie-twosie hardware (such as sound cards, NICs, etc.) being purchased by > Walnut Creek and/or FreeBSD, Inc. "automatically." Comments? > > (again, this is not meant to be accusatory to jkh or anybody specifically, an > d > I'm not asking for "justification of my CD purchase" in any way ... just > stating my US $0.02). That's $25/CDROM release. I'm not sure how much support that would get you. RedHat charges from $30 for web-based installation support to $150 for 30 days of full support. FreeBSD is a volunteer effort. Many people have devoted much time to this project only to be slammed for one thing or another. How many times have I seen this discussion on this list? I've run out of fingers and toes counting the number of times I've seen this discussion over the years. If people want support, purchase a commercial UNIX from any of the commercial UNIX vendors. Not only that but support contracts are available for FreeBSD. Heck, send me enough money and I'll provide support. I've worked for two commercial product development companies as a developer. Product development ain't cheap, nor is support. If you have a complaint, here are your options: 1. Go somewhere else and buy a commercial UNIX (or Windows) and support for it. 2. Get a FreeBSD support contract. 3. Roll up your sleeves and help out with the effort. Just quit complaining and do something constructive! There are a lot of people who have sacrificed to contribute to this project and I for one appreciate their contributions! Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC 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 Fri Mar 24 6:41:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by hub.freebsd.org (Postfix) with SMTP id 2C31A37B5D7 for ; Fri, 24 Mar 2000 06:41:35 -0800 (PST) (envelope-from ira@MIT.EDU) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA14864; Fri, 24 Mar 00 09:41:28 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id JAA28849 for ; Fri, 24 Mar 2000 09:41:33 -0500 (EST) Received: from mint-square.mit.edu (MINT-SQUARE.MIT.EDU [18.184.0.36]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id JAA17775 for ; Fri, 24 Mar 2000 09:41:32 -0500 (EST) Received: (from ira@localhost) by mint-square.mit.edu (8.9.3) id JAA01619; Fri, 24 Mar 2000 09:41:32 -0500 (EST) Message-Id: <200003241441.JAA01619@mint-square.mit.edu> To: freebsd-stable@freebsd.org Subject: ATA + DMA for Libretto 100CT? (4.0-STABLE) Date: Fri, 24 Mar 2000 09:41:32 -0500 From: Ira L Cooper Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any information I can give people to help make this combination possible? Can it be made to work at all? ;) Note: So far the machine works, but it seems REALLY slow :(. Please followup to ira@mit.edu as well as the list over this weekend. dmesg from the machine: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-STABLE #3: Fri Mar 24 12:25:12 GMT 2000 ira@:/usr/src/STABLE/src/sys/compile/BLACKBOX Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P55C (quarter-micron) (166.63-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x581 Stepping = 1 Features=0x8001bf real memory = 67174400 (65600K bytes) avail memory = 62029824 (60576K bytes) Preloaded elf kernel "kernel" at 0xc02eb000. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pci0: at 4.0 chip1: port 0xffe0-0xffff irq 11 at device 17.0 on pci0 pcic-pci0: at device 19.0 on pci0 pcic-pci1: at device 19.1 on pci0 isa0: on motherboard fdc0: direction bit not set fdc0: cmd 3 failed at out byte 1 of 3 ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> pcic0: at port 0x3e0 iomem 0xd0000 irq 10 on isa0 pcic0: management irq 10 pccard0: on pcic0 pccard1: on pcic0 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: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 ad0: 11513MB [23392/16/63] at ata0-master using BIOSPIO Mounting root from ufs:/dev/ad0s1a pccard: card inserted, slot 0 ed1 at port 0x340-0x35f irq 3 slot 0 on pccard0 ed1: supplying EUI64: 00:80:c6:ff:fe:f6:a4:23 ed1: address 00:80:c6:f6:a4:23, type NE2000 (16 bit) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 7: 1:39 2000 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 E494837BB9B for ; Fri, 24 Mar 2000 07:01:31 -0800 (PST) (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 GAA03357; Fri, 24 Mar 2000 06:58:21 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda03355; Fri Mar 24 06:58:15 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id GAA07438; Fri, 24 Mar 2000 06:58:15 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdSi7436; Fri Mar 24 06:58:09 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id GAA05156; Fri, 24 Mar 2000 06:58:09 -0800 (PST) Message-Id: <200003241458.GAA05156@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpddv5150; Fri Mar 24 06:57:50 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: John Reynolds~ Cc: stable@FreeBSD.ORG Subject: Re: What does "Voxware still supported in 4.0" mean exactly? In-reply-to: Your message of "Fri, 24 Mar 2000 06:30:53 PST." <200003241431.GAA05074@cwsys.cwsent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Mar 2000 06:57:50 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG BTW, this was not directed at you specifically but at many of those who complain about support. Please don't take this a my flaming you but instead flaming those who expect commercial support from a freeware project. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC In message <200003241431.GAA05074@cwsys.cwsent.com>, Cy Schubert - ITSD Open Sy stems Group writes: > In message <14554.20424.548258.530333@hip186.ch.intel.com>, John > Reynolds~ writ > es: > > > > [ On Wednesday, March 22, Jordan K. Hubbard wrote: ] > > > > What about those of us with AWE64 GOLD boards? The board itsel > f does > > > > quite well with most PCI based boards available today. As for upgrades > , > > > > would a Vibra16 really count as an upgrade? > > > > > > Why not send us one and we'll have Cameron Grant look at it? He is > > > somewhat constrained by the hardware available to him, and being off > > > in the UK and stuck in a wheelchair to boot doesn't exactly give him > > > the best access. > > > > > > > If we're going to be forced to use newer boards, what about > > > > SoundBlaster Live, Diamond Fusion, and other modern Aureal/Dolby based > > > > PCI sound boards? Will pcm support those out of the box, or are we now > > > > going to have to wait for some other driver to be developed? > > > > > > It doesn't support them out of the box now, but I can tell you that > > > Cameron is certainly working on at least the Soundblaster Live support > > > since we did send him one and I've heard him complaining bitterly > > > about it on several occasions. :) If somebody wants to send him > > > a Diamond Fusion card, I would be happy to "broker" the deal. > > > > The following is not venom directed at jkh, or anybody in general--it is an > > honest question/statement/opinion: > > > > Rather than having a user send Cameron Grant a Diamond Fusion Card, or any > > other "bleeding edge" or "old 'n' crusty" sound card to play with, shouldn' > t > > FreeBSD, Inc. or Walnut Creek itself be proactively shipping willing > > developers like this all the hardware they can purchase? I know that it is > > done, has been done, and will continue to be done--it just seems to me like > > another appropriate time to spend <= $100US from the profits generated by C > D > > sales. > > > > There are many many of us who faithfully buy the CD subscription and basica > ll > > y > > use the discs as shiny playtoys for our toddlers. I will continue to buy it > > too because "money gets rolled back into the project for further developmen > t" > > and with such limited time, that's how I "support" FreeBSD (along with > > evangelism being the only "FreeBSD leper" here at work amongst the > > Linux-ites). > > > > I think that users sending people who have the time and talent for writing > > drivers for the hardware is a grand idea. But, I think an equally grand ide > a > > is onsie-twosie hardware (such as sound cards, NICs, etc.) being purchased > by > > Walnut Creek and/or FreeBSD, Inc. "automatically." Comments? > > > > (again, this is not meant to be accusatory to jkh or anybody specifically, > an > > d > > I'm not asking for "justification of my CD purchase" in any way ... just > > stating my US $0.02). > > That's $25/CDROM release. I'm not sure how much support that would get > you. RedHat charges from $30 for web-based installation support to > $150 for 30 days of full support. > > FreeBSD is a volunteer effort. Many people have devoted much time to > this project only to be slammed for one thing or another. How many > times have I seen this discussion on this list? I've run out of > fingers and toes counting the number of times I've seen this discussion > over the years. > > If people want support, purchase a commercial UNIX from any of the > commercial UNIX vendors. Not only that but support contracts are > available for FreeBSD. Heck, send me enough money and I'll provide > support. I've worked for two commercial product development companies > as a developer. Product development ain't cheap, nor is support. > > If you have a complaint, here are your options: > > 1. Go somewhere else and buy a commercial UNIX (or Windows) and support > for it. > > 2. Get a FreeBSD support contract. > > 3. Roll up your sleeves and help out with the effort. > > Just quit complaining and do something constructive! There are a lot > of people who have sacrificed to contribute to this project and I for > one appreciate their contributions! > > > Regards, Phone: (250)387-8437 > Cy Schubert Fax: (250)387-5766 > Team Leader, Sun/DEC 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 7:39:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zipcode.corp.home.net (zipcode.corp.home.net [24.0.26.58]) by hub.freebsd.org (Postfix) with ESMTP id 0953E37B6A5 for ; Fri, 24 Mar 2000 07:39:13 -0800 (PST) (envelope-from manek@ecst.csuchico.edu) Received: from after (shiva-user17.corp.home.net [24.0.8.147]) by zipcode.corp.home.net (8.9.3/8.9.3) with SMTP id HAA07911; Fri, 24 Mar 2000 07:38:59 -0800 (PST) From: "Sameer R. Manek" To: , Subject: bad file permissions Date: Fri, 24 Mar 2000 07:39:19 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Last night someone uploaded a new iso image to ftp://ftp.freebsd.org/.0/FreeBSD/releases/i386/ISO-IMAGES but they accidentally forgot to correct the file permissions. Can someone correct that? -rw------- 1 2035 207 656562176 Mar 24 08:13 4.0-install.iso Sameer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 8: 0:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.hcisp.net (Stargate.hcisp.net [208.60.89.18]) by hub.freebsd.org (Postfix) with SMTP id 4C7A437BB51 for ; Fri, 24 Mar 2000 08:00:15 -0800 (PST) (envelope-from tim@mysql.com) Received: (qmail 10247 invoked from network); 24 Mar 2000 16:06:19 -0000 Received: from modem4.hcisp.net (HELO threads.polyesthetic.msg) (208.60.89.70) by stargate.hcisp.net with SMTP; 24 Mar 2000 16:06:19 -0000 Received: (qmail 31054 invoked by uid 1001); 24 Mar 2000 15:59:54 -0000 From: "Thimble Smith" Date: Fri, 24 Mar 2000 10:59:54 -0500 To: FreeBSD stable Cc: "G. Adam Stanislav" Subject: Re: C++ writing/compiling with 3.4 stable Message-ID: <20000324105954.L30485@threads.polyesthetic.msg> References: <20000323181153.A88716@localhost.localdomain> <200003240109.SAA45855@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003240109.SAA45855@harmony.village.org>; from imp@village.org on Thu, Mar 23, 2000 at 06:09:46PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 23, 2000 at 06:09:46PM -0700, Warner Losh wrote: >Use 2.95. 2.8.1 is better than 2.7, but still has some significant >issues in the dark corners of the language. Don't worry about >glibstdc++... It has been subsumed by libstdc++. Kind of on this topic, has anyone gotten libstdc++-v3 to compile? It wants wchar support, and FreeBSD doesn't have it (yet). I've seen some mention of support for it being developed at: http://www.whizkidtech.net/i18n/wc/ http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=3480389+3483352+/usr/local/www/db/text/1999/freebsd-hackers/19990509.freebsd-hackers But it looks like that hasn't been touched since May 1999. Is there anything that's useable enough to get libstdc++-v3 to work? Does anybody want some help working on it? Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 8:13:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by hub.freebsd.org (Postfix) with ESMTP id A9DCE37B506 for ; Fri, 24 Mar 2000 08:13:13 -0800 (PST) (envelope-from adamo@dblab.ece.ntua.gr) Received: from dblab.ece.ntua.gr (ithaca.dbnet.ece.ntua.gr [147.102.12.1]) by ulysses.noc.ntua.gr (8.9.3/8.9.3) with ESMTP id SAA85616; Fri, 24 Mar 2000 18:13:07 +0200 (EET) Received: from mbazo.dbnet.ece.ntua.gr (mbazo.dbnet.ece.ntua.gr [147.102.12.8]) by dblab.ece.ntua.gr (8.10.0/8.10.0) with ESMTP id e2OGD1B98606; Fri, 24 Mar 2000 18:13:06 +0200 (EET) From: Yiorgos Adamopoulos Date: Fri, 24 Mar 2000 18:13:01 +0200 To: Jaye Mathisen Subject: Re: Samba perf in the toilet with 4.0 Cc: stable@FreeBSD.ORG In-Reply-To: References: Message-ID: X-Mailer: Execmail for Win32 Version 5.0.1 Build (55) 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, 23 Mar 2000 14:12:31 -0800 (PST) Jaye Mathisen wrote: > Not sure what's going on. May have to drop back to 3.4 if this isn't > easily fixed. Could this be due to the bandwidth limitation rules on 4.0? -- Yiorgos Adamopoulos, adamo@ieee.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 8:52:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ne.home.com (ha1.rdc1.ne.home.com [24.2.4.66]) by hub.freebsd.org (Postfix) with ESMTP id E72D537B612 for ; Fri, 24 Mar 2000 08:52:29 -0800 (PST) (envelope-from jgowdy@home.com) Received: from cx443070a ([24.4.93.90]) by mail.rdc1.ne.home.com (InterMail v4.01.01.00 201-229-111) with SMTP id <20000324165220.DBUT14878.mail.rdc1.ne.home.com@cx443070a>; Fri, 24 Mar 2000 08:52:20 -0800 Message-ID: <003701bf95b2$961159a0$0100000a@vista1.sdca.home.com> From: "Jeremiah Gowdy" To: , "Sergei Vyshenski" Cc: , References: <3.0.5.32.20000324065537.007bc7d0@vivaldi> Subject: Re: perl vs buildworld and piping in 4.0 Date: Fri, 24 Mar 2000 09:01:23 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Was only able to build perl inside buildworld, after > switching off of all compiler optimization and piping in make.conf > (that is returning to default > #CFLAGS= -O -pipe > ) > > More to that, previous (crashed) runs of buildword, > left ill configuration files in /usr/src/contrib/perl5/..., > which survived subsequent run of "make clean" in /usr/src. > Had to spot them by date, and remove by hand. Yeah, I'm totally getting the same crap, I've failed make buildworld a hundred times. It's driving me insane. I even rm -rf /usr/src and cvsup again. Happens every time. I thought it was because I use SMP and was running make -j2 or -j4, but even after building without -jX (much slower) I got the same crash. I think it's saying mkdir: File Exists: or something. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 9:16:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from europe.std.com (europe.std.com [199.172.62.20]) by hub.freebsd.org (Postfix) with ESMTP id CE45C37B747 for ; Fri, 24 Mar 2000 09:16:33 -0800 (PST) (envelope-from kwc@world.std.com) Received: from world.std.com (root@world-f.std.com [199.172.62.5]) by europe.std.com (8.9.3/8.9.3) with ESMTP id MAA14699 for ; Fri, 24 Mar 2000 12:16:29 -0500 (EST) Received: (from kwc@localhost) by world.std.com (8.9.3/8.9.3) id MAA22784; Fri, 24 Mar 2000 12:10:57 -0500 (EST) Date: Fri, 24 Mar 2000 12:10:57 -0500 (EST) From: Kenneth W Cochran Message-Id: <200003241710.MAA22784@world.std.com> To: freebsd-stable@freebsd.org Subject: Questions source-upgrading 3.4-s to 4.0-s Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG s Questions source-upgrading 3.4-s to 4.0-s Hi, Sorry for the length of this message. I've been following the "upgrading" thread on -stable & I could use some clarification as to the "whys & hows" of this procedure. Perhaps this might be a "guide" as to some things that might merit further explanation in the relevant documentation? I track RELENG_3 (more or less) & I'm contemplating & trying to grok the 3.4-stable --> 4.0 stable upgrading process by source, & since I've never (yet :) done a major "source" upgrade, I could use just a bit of errr, "hand-holding..." I'm trying to avoid a "chicken-and-egg" problem... Overview It appears that my new 4.0 system (& the new C compiler) will be built using the 3.4-stable tools; is this ok? I'm guessing that the "last step(s)" of this process is to re-gen (cvsup/make [build, install]world...), just as I've always done with 3.x. It also appears that I cannot run a 3.x kernel with a 4.x userland (or is that a 4.x kernel with a 3.x userland?), so I have to get my userland built but not installed, then build, install & boot my new 4.x kernel, & *then* do my userland install (installworld). Is this correct? Here are the relevant sections from src/UPDATING with my questions interspersed. I'm in the "context" 3.4-stable, updated & built within the past couple of weeks. Naturally, FAQ/doc/etc. pointers are quite welcome. (What are the Really Good FMs to RT? :) Or should I just wait for the CDs & do my upgrade the Good Old Fashioned Way (ie. back up my stuff & reinstall "fresh" from the CDs...)? :) ****************************** 4.0 RELEASE ****************************** To update from 3.x to 4.0 stable -------------------------------- [***] - I'm using the 4.x-stable-supfile from the examples in 3.4-s. What are the best things to un-comment in that config? (to handle crypto things, for example...) - What's the difference between what I'd get as North American vs not? (& what's the best way to "identify" myself as North American? (What is going to ship on the CDs?) cd /usr/src [**] make buildworld - Ok... This will take my new 4.x /usr/src & make a nice new /usr/obj... - MAKE_KERBEROS4 is already commented-out in my /etc/make.conf, so I should be ok here? cd sbin/mknod make install - What's this about? Is this /usr/sbin/mknod or is it /usr/src/sbin/mknod? How does this differ from cd /dev; sh MAKEDEV? cd sys/modules make install - Same here... What's this about? I'm thinking this (& previous are relative to (my new 4.x) /usr/src, ie. /usr/src/sys/modules, or perhaps /sys/modules... - My questions/commentary are below, in that section... [*] - My system is all-scsi (/dev/da*). Do I need to do anything special? - "As above?" Again, how does this differ from cd /dev; sh MAKEDEV? reboot - If I understand correctly, hit the spacebar & type -s? - Looks to me like I need to make sure my filesystems are properly mounted. How is the best way to do this as single-user? (mount -a, IIRC...) cd /usr/src make -DNOINFO installworld - Why -DNOINFO? make installworld - & my guess is that this "corrects" the -DNOINFO installworld I just did? reboot - At this time I'm guessing it would be a Very Good Idea to do at least a [build, install]world, so as to get everything built with the new C compiler & tools, etc... [*] You may need to switch from wd to ad ala 19991210 [**] If you have any of the following in your /etc/make.conf, please comment them out before following these instructions and then do a make buildworld + make installworld after you are back to above: MAKE_KERBEROS4 [***] Update to 4.0-stable sources. Make sure that you get all the parts. If you are using cvsup files that are older than a couple of months, be sure they have all the components listed in /usr/share/examples/cvsup. Crypto and secure are now required. To build a kernel ----------------- cd /usr/src # If you have not already done so, please buildworld here make buildkernel KERNEL= make installkernel KERNEL= # Verify that the new kernel works, it will be installed as # /YOUR_KERNEL_HERE chflags noschg /kernel mv /kernel /kernel.old mv /YOUR_KERNEL_HERE /kernel chflags schg /kernel - Is this still the same as: cd /sys/i386/conf config cd /sys/compile/GENERIC make depend make make install - Other than that, I'm guessing that I need to build & install the GENERIC kernel? ---------------------------------------- Many thanks for your help & for this wonderful OS! -kc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 9:23:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from screech.weirdnoise.com (209-128-78-198.bayarea.net [209.128.78.198]) by hub.freebsd.org (Postfix) with ESMTP id 70C3437B712; Fri, 24 Mar 2000 09:23:07 -0800 (PST) (envelope-from edhall@screech.weirdnoise.com) Received: from screech.weirdnoise.com (localhost [127.0.0.1]) by screech.weirdnoise.com (8.9.3/8.9.3) with ESMTP id JAA26268; Fri, 24 Mar 2000 09:24:10 -0800 Message-Id: <200003241724.JAA26268@screech.weirdnoise.com> X-Mailer: exmh version 2.0.2 To: Andrew Gallatin Cc: freebsd-alpha@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Compiler problems with -O2 (was Re: CVS Trouble, even under 4.0-RELEASE (alpha) HELP!) In-Reply-To: Message from Andrew Gallatin of "Thu, 23 Mar 2000 14:23:12 EST." <14554.28033.439748.801349@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Mar 2000 09:24:10 -0800 From: Ed Hall Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Gallatin : : You're missing the point almost entirely. FreeBSD's stock gcc -O2 is : demonstrably __broken__ on the alpha. You cannot trust code it : outputs. Interesting. Do we have a test case we can pass along to the gcc folks? Any idea why the Linux folks seem to have better luck with "gcc -O2"? Do they configure gcc differently? (I'm willing to look into it if no one here knows.) I find it interesting that Howard Leadmon's problem with "gcc -O2" showed up as breakage in gcc itself--code that I would assume would be identical to what Linux uses. Specifically, the function check_newline() in /usr/src/contrib/gcc/c-lex.c would seem to be misbehaving. Linux builds gcc with -O2 by default, yet c-lex.c would seem to compile OK there. How are we different? -Ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 9:32:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from europe.std.com (europe.std.com [199.172.62.20]) by hub.freebsd.org (Postfix) with ESMTP id A3B7D37B854 for ; Fri, 24 Mar 2000 09:32:07 -0800 (PST) (envelope-from kwc@world.std.com) Received: from world.std.com (root@world-f.std.com [199.172.62.5]) by europe.std.com (8.9.3/8.9.3) with ESMTP id MAA17789; Fri, 24 Mar 2000 12:32:03 -0500 (EST) Received: (from kwc@localhost) by world.std.com (8.9.3/8.9.3) id MAA06724; Fri, 24 Mar 2000 12:27:12 -0500 (EST) Date: Fri, 24 Mar 2000 12:27:12 -0500 (EST) From: Kenneth W Cochran Message-Id: <200003241727.MAA06724@world.std.com> To: "Daniel C. Sobral" Subject: Re: Linux ext2 fs support changes in -stable Cc: freebsd-stable@freebsd.org References: <200003221548.KAA05168@world.std.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From dcs@newsguy.com Wed Mar 22 20:35:12 2000 >Date: Thu, 23 Mar 2000 10:31:51 +0900 >CC: freebsd-stable@FreeBSD.ORG >Subject: Re: Linux ext2 fs support changes in -stable > >Kenneth W Cochran wrote: >> Somewhat all-of-a-sudden, I am unable to r/w mount a Linux ext2 >> filesystem on the same hdd with my BSD. I get in my syslog (& >> on console): >> /kernel: WARNING: R/W mount of dev 0xe040a denied due to >> unsupported optional features > >This is telling you that this file system has features (put in >the by a recent version of Linux, most likely) which our ext2fs >code does not understand. Since we don't understand it, allowing >a R/W mount is dangerous. Makes sense... Interesting that this does not happen on my other hdd; I bet I made those filesystems under a previous Linux version... >You can read more about this using the cvsweb to check the commit >logs for the ext2fs files. This was bde's (Bruce Evans) changes. > >I can see the point in wanting to force a R/W mount, on the >grounds that you know more about your setup than the software >does (which is the whole point of the software denying you R/W >access in the first place :), but you'll need to convince Bruce, >not me, of that. > >Convincing Bruce is easy, as long as he agrees with you to begin >with. If he doesn't... I must assume that Bruce had Good Reason for changing this behavior... >-- >Daniel C. Sobral (8-DCS) >dcs@newsguy.com >dcs@freebsd.org >capo@zurichgnomes.bsdconspiracy.net I hope this is "temporary" & gets "fixed" soon; I've found *BSD's support of ext2 to be much more reliable than Linux's support for ufs... -kc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 9:46:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 0AE5E37BE5B for ; Fri, 24 Mar 2000 09:46:43 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id JAA02858; Fri, 24 Mar 2000 09:46:41 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38DBAA01.199856BB@gorean.org> Date: Fri, 24 Mar 2000 09:46:41 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0322 i386) X-Accept-Language: en MIME-Version: 1.0 To: Jeremiah Gowdy Cc: freebsd-stable@FreeBSD.ORG, Sergei Vyshenski , genew@home.com, laa@zgia.zp.ua Subject: Re: perl vs buildworld and piping in 4.0 References: <3.0.5.32.20000324065537.007bc7d0@vivaldi> <003701bf95b2$961159a0$0100000a@vista1.sdca.home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeremiah Gowdy wrote: > Yeah, I'm totally getting the same crap, I've failed make buildworld a > hundred times. It's driving me insane. I even rm -rf /usr/src and cvsup > again. Happens every time. I thought it was because I use SMP and was > running make -j2 or -j4, but even after building without -jX (much slower) I > got the same crash. I think it's saying mkdir: File Exists: or something. I vaguely remember something like this a while back. I deleted the directory that it was complaining about (so make could create it itself) and I was back in business. -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 10:41:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.va.home.com (ha1.rdc1.va.home.com [24.2.32.66]) by hub.freebsd.org (Postfix) with ESMTP id D52EF37B877 for ; Fri, 24 Mar 2000 10:41:26 -0800 (PST) (envelope-from jgowdy@home.com) Received: from cx443070a ([24.4.93.90]) by mail.rdc1.va.home.com (InterMail v4.01.01.00 201-229-111) with SMTP id <20000324184124.WVHQ12441.mail.rdc1.va.home.com@cx443070a>; Fri, 24 Mar 2000 10:41:24 -0800 Message-ID: <001101bf95c1$d2d27d60$0100000a@vista1.sdca.home.com> From: "Jeremiah Gowdy" To: "Doug Barton" Cc: , "Sergei Vyshenski" , , References: <3.0.5.32.20000324065537.007bc7d0@vivaldi> <003701bf95b2$961159a0$0100000a@vista1.sdca.home.com> <38DBAA01.199856BB@gorean.org> Subject: Re: perl vs buildworld and piping in 4.0 Date: Fri, 24 Mar 2000 10:50:27 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Yeah, I'm totally getting the same crap, I've failed make buildworld a > > hundred times. It's driving me insane. I even rm -rf /usr/src and cvsup > > again. Happens every time. I thought it was because I use SMP and was > > running make -j2 or -j4, but even after building without -jX (much slower) I > > got the same crash. I think it's saying mkdir: File Exists: or something. > > I vaguely remember something like this a while back. I deleted the > directory that it was complaining about (so make could create it itself) > and I was back in business. hmm. I'll try that. Right now I've cvsupped 4.0 stable, and I'm building world as I type this. If it doesn't work, I'll burn my neighbor's house down, go on an insane killing spree, and when I get done, I'll come back, cvsup 4 release again, and see if I can't get the buildworld to work. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 10:56:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mecca.servint.com (mecca.servint.com [209.50.225.14]) by hub.freebsd.org (Postfix) with ESMTP id B535737B5BC for ; Fri, 24 Mar 2000 10:56:53 -0800 (PST) (envelope-from loschert@servint.com) Received: from delft.servint.com (207-172-86-44.s44.tnt6.rcm.va.dialup.rcn.com [207.172.86.44]) by mecca.servint.com (8.9.3/8.9.0) with ESMTP id OAA26676 for ; Fri, 24 Mar 2000 14:15:45 -0500 (EST) Received: (qmail 61752 invoked by uid 1000); 24 Mar 2000 18:55:23 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 24 Mar 2000 18:55:23 -0000 Date: Fri, 24 Mar 2000 13:55:23 -0500 (EST) From: Matt Loschert To: Kenneth W Cochran Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Questions source-upgrading 3.4-s to 4.0-s In-Reply-To: <200003241710.MAA22784@world.std.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 Fri, 24 Mar 2000, Kenneth W Cochran wrote: > It appears that my new 4.0 system (& the new C compiler) will be > built using the 3.4-stable tools; is this ok? I'm guessing that > the "last step(s)" of this process is to re-gen (cvsup/make > [build, install]world...), just as I've always done with 3.x. Before building your new 4.0 userland, the buildworld process builds the 4.0 compiler (gcc-2.95.2) (along with other build tools), and then uses that to compile everything (including recompiling the compiler). > It also appears that I cannot run a 3.x kernel with a 4.x > userland (or is that a 4.x kernel with a 3.x userland?), so I > have to get my userland built but not installed, then build, > install & boot my new 4.x kernel, & *then* do my userland > install (installworld). Is this correct? Yes, that's correct. > [***] > - I'm using the 4.x-stable-supfile from the examples in > 3.4-s. What are the best things to un-comment in that > config? (to handle crypto things, for example...) Make sure you specify to make 4.0-STABLE your default: *default tag=RELENG_4 Use the following to get all 4.0-STABLE source including crypto: src-all cvs-crypto If you want the latest ports collection and documentation, specify: ports-all tag=. doc-all tag=. > - What's the difference between what I'd get as North > American vs not? (& what's the best way to "identify" > myself as North American? (What is going to ship on > the CDs?) Offhand, I am not sure what all of the differences are. To identify yourself as from USA, specify USA_RESIDENT="YES" in /etc/make.conf. Then, point cvsup to a USA cvsup server in your supfile using something like: *default host=cvsup.FreeBSD.org > cd /usr/src > [**] > make buildworld > - Ok... This will take my new 4.x /usr/src & make a nice > new /usr/obj... Yes. > - MAKE_KERBEROS4 is already commented-out in my > /etc/make.conf, so I should be ok here? Yes. > cd sbin/mknod > make install > - What's this about? Is this /usr/sbin/mknod or is it > /usr/src/sbin/mknod? > How does this differ from cd /dev; sh MAKEDEV? cd /usr/src/sbin/mknod && make install > cd sys/modules > make install > - Same here... What's this about? I'm thinking this (& > previous are relative to (my new 4.x) /usr/src, ie. > /usr/src/sys/modules, or perhaps /sys/modules... cd /usr/src/sys/modules && make install > [*] > - My system is all-scsi (/dev/da*). Do I need to do > anything special? Not if you have da* sepecified for you SCSI hard drives. If you have sd* devices, these need to be updated to da*. > - "As above?" Again, how does this differ from cd /dev; > sh MAKEDEV? You need the new MAKEDEV script for 4.0 from /usr/src/etc. As far as I know, once you copy the new script into /dev, 'sh MAKEDEV all' should work fine. I could be wrong for certain configurations. > reboot > > - If I understand correctly, hit the spacebar & type -s? You probably should boot into single-user, but I have done it successfully after booting multi-user. > cd /usr/src > make -DNOINFO installworld > - Why -DNOINFO? The new texinfo IIRC relies on new features that are not part of the build chain. It tries to install itself using the existing install-info program that does not have the features and bombs out. -DNOINFO skips installing the info files, thus not needing the new install-info. > make installworld > - & my guess is that this "corrects" the -DNOINFO > installworld I just did? This essentially just installs the info files that were left out during the previous step. > reboot > > - At this time I'm guessing it would be a Very Good Idea > to do at least a [build, install]world, so as to get > everything built with the new C compiler & tools, etc... Not necessary. As mentioned above, the new compiler was used to do last buildworld. > To build a kernel > ----------------- > cd /usr/src > # If you have not already done so, please buildworld here > make buildkernel KERNEL= > make installkernel KERNEL= > # Verify that the new kernel works, it will be installed as > # /YOUR_KERNEL_HERE > chflags noschg /kernel > mv /kernel /kernel.old > mv /YOUR_KERNEL_HERE /kernel > chflags schg /kernel > > - Is this still the same as: > cd /sys/i386/conf > > config > cd /sys/compile/GENERIC > make depend > make > make install The kernel build process that you are familiar with relies on already installed tools. Since the new 4.0 tools are not installed at this point, you can't use them to build your 4.0 kernel. The buildkernel and installkernel targets use tools built (but not installed) during the buildworld phase to ensure that everything is in sync. > - Other than that, I'm guessing that I need to build & > install the GENERIC kernel? For the upgrade, yes, install GENERIC. Once you have rebooted after the upgrade, it is much safer to rebuild your custom kernel. Hope this helps. - Matt -- Matt Loschert loschert@servint.com Software Engineer voice (703) 847-1381 ServInt Internet Services fax (703) 847-1383 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 11:22:42 2000 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 A9FBB37B5C8; Fri, 24 Mar 2000 11:22:32 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.12 #1) id 12YY2R-0006Eo-00; Fri, 24 Mar 2000 17:38:23 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7) id 12YY2Q-0004rv-00; Fri, 24 Mar 2000 17:38:22 +0000 Date: Fri, 24 Mar 2000 17:38:22 +0000 From: Ben Smithurst To: Matthew Dillon Cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: repeatable lockup (pipe related?) Message-ID: <20000324173822.G87103@strontium.scientia.demon.co.uk> References: <20000323222149.C87103@strontium.scientia.demon.co.uk> <200003232244.OAA05041@apollo.backplane.com> <200003240053.QAA06073@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003240053.QAA06073@apollo.backplane.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > I've committed a fix to this in -current, 4.x, and 3.x. Rev 1.61 > kern/sys_pipe.c (current), 1.60.2.1 in RELENG_4, something else in > RELENG_3. Sorry 2.2.x'rs, three is my limit :-) Thanks! I'll try it tonight. -- Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 11:35:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from csla.csl.sri.com (csla.csl.sri.com [192.12.33.2]) by hub.freebsd.org (Postfix) with ESMTP id B397837B860 for ; Fri, 24 Mar 2000 11:35:31 -0800 (PST) (envelope-from gilham@snapdragon.csl.sri.com) Received: from snapdragon.csl.sri.com (snapdragon.csl.sri.com [130.107.18.20]) by csla.csl.sri.com (8.9.1/8.9.1) with ESMTP id LAA14801 for ; Fri, 24 Mar 2000 11:35:30 -0800 (PST) Message-Id: <200003241935.LAA14801@csla.csl.sri.com> To: stable@FreeBSD.ORG Subject: XDM (was Re: src/UPDATING for RELENG_3 to RELENG_4 upgrade works.) In-reply-to: Your message of "Fri, 24 Mar 2000 09:22:03 +1100." <20000324092203.B66456@gurney.reilly.home> Date: Fri, 24 Mar 2000 11:35:29 -0800 From: Fred Gilham Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Reilly wrote: > On Thu, Mar 23, 2000 at 10:49:56AM -0600, WMC, O'Gorman, James wrote: > > The one and only problem that I have had that I have not fixed yet is > > with xdm. I had started it from rc.local before, but now when rc.local > > starts is, the keyboard will not interact with it. If I comment out that > > line, boot up normal and log in as root and then start xdm things are > > fine. I have not put any effort into fixing it yet, so I am sure it is > > something simple I am missing. > > Just turn the "off" to "on" in the ttyv8/xdm line in /etc/ttys. > No need to fire it up from rc.anything. That has the added advantage > of automatically restarting it, if the server breaks. For a long time I've done something a bit different, that seems to work well. I start xdm using a /usr/X11R6/etc/rc.d/xdm.sh script: ---------------------------------------- if [ -x /usr/X11R6/bin/xdm -a -f /usr/X11R6/lib/X11/xdm/xdm-config ]; then /usr/X11R6/bin/xdm -config /usr/X11R6/lib/X11/xdm/xdm-config & echo "xdm" fi ---------------------------------------- In /etc/ttys I have the following: ttyv3 "/usr/X11R6/bin/Xwrapper -bpp 24 -indirect snapdragon" xterm on secure (You can change the ttyv3 above to ttyv8 or whatever.) I comment out the server entry in /usr/X11R6/lib/X11/xdm/Xservers: ... # #:0 local /usr/X11R6/bin/X The nice thing about the above is that you get a chooser so if other machines on your network are running xdm you can log on to them directly, using your desktop as an X terminal. You can still log in to your own machine with Xterms or virtual consoles. -Fred Gilham gilham@csl.sri.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 12:49:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from europe.std.com (europe.std.com [199.172.62.20]) by hub.freebsd.org (Postfix) with ESMTP id B796E37B66A for ; Fri, 24 Mar 2000 12:49:02 -0800 (PST) (envelope-from kwc@world.std.com) Received: from world.std.com (root@world-f.std.com [199.172.62.5]) by europe.std.com (8.9.3/8.9.3) with ESMTP id PAA27456; Fri, 24 Mar 2000 15:48:57 -0500 (EST) Received: (from kwc@localhost) by world.std.com (8.9.3/8.9.3) id PAA00854; Fri, 24 Mar 2000 15:44:25 -0500 (EST) Date: Fri, 24 Mar 2000 15:44:25 -0500 (EST) From: Kenneth W Cochran Message-Id: <200003242044.PAA00854@world.std.com> To: Matt Loschert Subject: Re: Questions source-upgrading 3.4-s to 4.0-s Cc: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From loschert@servint.com Fri Mar 24 14:02:06 2000 >Date: Fri, 24 Mar 2000 13:55:23 -0500 (EST) >Subject: Re: Questions source-upgrading 3.4-s to 4.0-s > >On Fri, 24 Mar 2000, Kenneth W Cochran wrote: >> It appears that my new 4.0 system (& the new C compiler) will be >> built using the 3.4-stable tools; is this ok? I'm guessing that >> the "last step(s)" of this process is to re-gen (cvsup/make >> [build, install]world...), just as I've always done with 3.x. > >Before building your new 4.0 userland, the buildworld process >builds the 4.0 compiler (gcc-2.95.2) (along with other build >tools), and then uses that to compile everything (including >recompiling the compiler). So buildworld runs in its "own complete isolated" environment? IOW, buildworld uses its "own" tools, etc., & doesn't need ie. /bin, /usr/bin ... ?? (Except for a few basic things, like the compiler (with which to "bootstrap" itself?"... :) >> It also appears that I cannot run a 3.x kernel with a 4.x >> userland (or is that a 4.x kernel with a 3.x userland?), so I >> have to get my userland built but not installed, then build, >> install & boot my new 4.x kernel, & *then* do my userland >> install (installworld). Is this correct? > >Yes, that's correct. Makes sense... So noted... >> [***] >> - I'm using the 4.x-stable-supfile from the examples in >> 3.4-s. What are the best things to un-comment in that >> config? (to handle crypto things, for example...) > >Make sure you specify to make 4.0-STABLE your default: >*default tag=RELENG_4 That's already in the example 4.x supfile & I've been running this cvsup in "test" mode just to See What It Does... >Use the following to get all 4.0-STABLE source including crypto: >src-all Of course... :) >cvs-crypto UPDATING says "Crypto & secure are now required." That, as I understand would be src-crypto and src-secure. How would these differ from cvs-crypto? Ie. would it be "better" to use those 2 "tags" or to use the one cvs-crypto? I suppose what I may be asking is "how do I make my new system look most like the distributed CDs?" >If you want the latest ports collection and documentation, specify: >ports-all tag=. >doc-all tag=. I do that with a separate cvsup file/job... >> - What's the difference between what I'd get as North >> American vs not? (& what's the best way to "identify" >> myself as North American? (What is going to ship on >> the CDs?) > >Offhand, I am not sure what all of the differences are. To >identify yourself as from USA, specify USA_RESIDENT="YES" in >/etc/make.conf. Then, point cvsup to a USA cvsup server in your Aha! (Thanks... :) >supfile using something like: >*default host=cvsup.FreeBSD.org I use one "closer..." >> cd /usr/src >> [**] >> make buildworld >> - Ok... This will take my new 4.x /usr/src & make a nice >> new /usr/obj... >Yes. Okay/check... >> - MAKE_KERBEROS4 is already commented-out in my >> /etc/make.conf, so I should be ok here? >Yes. Okay/check... >> cd sbin/mknod >> make install >> - What's this about? Is this /usr/sbin/mknod or is it >> /usr/src/sbin/mknod? >> How does this differ from cd /dev; sh MAKEDEV? > >cd /usr/src/sbin/mknod && make install Along the lines of "dotting all the "i"s & "crossong all the "t"s", I believe it would be a Good Idea to make this more explicit in the instructions... :) >> cd sys/modules >> make install >> - Same here... What's this about? I'm thinking this (& >> previous are relative to (my new 4.x) /usr/src, ie. >> /usr/src/sys/modules, or perhaps /sys/modules... > >cd /usr/src/sys/modules && make install Here, too... :) >> [*] >> - My system is all-scsi (/dev/da*). Do I need to do >> anything special? > >Not if you have da* sepecified for you SCSI hard drives. If you >have sd* devices, these need to be updated to da*. My devices are indeed da*; it was fresh-installed from the 3.4-RELEASE CDs, so it appears that I can skip this step? My /etc/fstab should also be ok? >> - "As above?" Again, how does this differ from cd /dev; >> sh MAKEDEV? > >You need the new MAKEDEV script for 4.0 from /usr/src/etc. As >far as I know, once you copy the new script into /dev, 'sh >MAKEDEV all' should work fine. I could be wrong for certain >configurations. Hmmm... Perhaps this needs more clarification? >> reboot >> >> - If I understand correctly, hit the spacebar & type -s? > >You probably should boot into single-user, but I have done it >successfully after booting multi-user. I'm one of those "safety freaks" who always goes single-user for installworld... :) >> cd /usr/src >> make -DNOINFO installworld >> - Why -DNOINFO? > >The new texinfo IIRC relies on new features that are not part of >the build chain. It tries to install itself using the existing >install-info program that does not have the features and bombs out. > >-DNOINFO skips installing the info files, thus not needing the >new install-info. Ah! Thanks! >> make installworld >> - & my guess is that this "corrects" the -DNOINFO >> installworld I just did? > >This essentially just installs the info files that were left out >during the previous step. Makes sense now; thanks! >> reboot >> >> - At this time I'm guessing it would be a Very Good Idea >> to do at least a [build, install]world, so as to get >> everything built with the new C compiler & tools, etc... > >Not necessary. As mentioned above, the new compiler was used to >do last buildworld. Interesting... :) >> To build a kernel >> ----------------- >> cd /usr/src >> # If you have not already done so, please buildworld here >> make buildkernel KERNEL= >> make installkernel KERNEL= >> # Verify that the new kernel works, it will be installed as >> # /YOUR_KERNEL_HERE >> chflags noschg /kernel >> mv /kernel /kernel.old >> mv /YOUR_KERNEL_HERE /kernel >> chflags schg /kernel >> >> - Is this still the same as: >> cd /sys/i386/conf >> >> config >> cd /sys/compile/GENERIC >> make depend >> make >> make install > >The kernel build process that you are familiar with relies on >already installed tools. Since the new 4.0 tools are not >installed at this point, you can't use them to build your 4.0 >kernel. The buildkernel and installkernel targets use tools >built (but not installed) during the buildworld phase to ensure >that everything is in sync. Aha! :) >> - Other than that, I'm guessing that I need to build & >> install the GENERIC kernel? > >For the upgrade, yes, install GENERIC. Once you have rebooted >after the upgrade, it is much safer to rebuild your custom kernel. So, substitute GENERIC for "YOUR_KERNEL_HERE?" >Hope this helps. Very much! Many thanks! I think it would be a Very Good Idea to get "appropriate portions" of this information into the UPDATING instructions; it might help slow down the upgrading-deluge "here" on -stable... :) -kc >- Matt >-- >Matt Loschert loschert@servint.com >Software Engineer voice (703) 847-1381 >ServInt Internet Services fax (703) 847-1383 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 13:22:17 2000 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 12CB737BC6C for ; Fri, 24 Mar 2000 13:22:13 -0800 (PST) (envelope-from conrads@cx344940-a.meta1.la.home.com) Received: (from conrads@localhost) by cx344940-a.meta1.la.home.com (8.9.3/8.9.3) id PAA67733; Fri, 24 Mar 2000 15:22:08 -0600 (CST) (envelope-from conrads) 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: <24057.953780938@zippy.cdrom.com> Date: Fri, 24 Mar 2000 15:22:08 -0600 (CST) Organization: @Home Network From: Conrad Sabatier To: "Jordan K. Hubbard" Subject: Re: What does "Voxware still supported in 4.0" mean exactly? Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Mar-00 Jordan K. Hubbard wrote: >> It's rather disturbing to me to think that, as FreeBSD progresses along >> through this and that version, I'll have no choice but to be left in >> the dust, or sacrifice certain functionality that I've come to know >> and love, or (God forbid) migrate to another platform altogether. > > Or get another sound card? Sorry, but I had to note this as an > additional option which, unless you're incredibly poverty-stricken, > should not be ruled out for *any* hardware. I smell shades of M$ here. :-) Seriously, isn't that one of the chief criticisms of Microsoft, that every time they release a new version of Windows, you have to plunk down for {more,better,faster,newer,bigger} hardware in order to make the best use of it? Despite this frequently noted complaint, the fact remains that Windows still continues to work with much older hardware. Why shouldn't FreeBSD? One particularly worrisome note (well, to me, anyway) that appeared in this thread mentioned the requirement to use "options OLD_ISA" (or something like that) to get Voxware to work in 4.0/CURRENT. Is support for older, pure ISA machines going away, too? Granted, sooner or later there comes a time in the life of every OS when support for certain types of dinosaur hardware is finally abandoned, but I hardly think the AWE boards could properly be described as ancient, outdated, or seldom used anymore. And yes, for some of us, money *is* a concern. If it weren't, I certainly wouldn't still be running this 4-5 year old 166 MHz Pentium box. :-) > I replaced my AWE32 board long ago, and purely because of its oversize > form-factor. I now use the on-board Vibra16X audio capabilities of the > motherboard I replaced my old one with. I'm quite happy with my AWE 64 and see no need to replace it, and I've expanded its onboard RAM to the maximum possible (24 MB) in order to use those wonderful-sounding, super-duper 12 MB Soundfonts for MIDI, so you might say I have a bit of an investment in it as well. If the new pcm driver supported the card as well as Voxware, I'd certainly have no complaint, and would readily make the switch. But until pcm allows me to use the wavetable device (including support for user loading of Soundfonts) and is capable of controlling the card's nifty added features such as reverb and chorus, it makes no sense at all for me to "upgrade" to 4.0, when doing so represents a definite "downgrade" in at least one department. And besides, where's the MIDI? :-) While I can certainly appreciate the FreeBSD development team's desire for a more modern, unified and well-integrated driver than Voxware, until such time as it can provide the same functionality as the older driver, I do strongly believe that Voxware should continue to be supported, and that pcm still should be considered as an "experimental" option only. In addition, I really would like to see user control over PnP devices (via the pnp boot config command) brought back. It's just way too useful a thing to throw away altogether. -- Conrad Sabatier http://members.home.net/conrads/ ICQ# 1147270 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 13:24:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from xxx.video-collage.com (xxx.video-collage.com [209.122.149.226]) by hub.freebsd.org (Postfix) with ESMTP id 05EFD37B5EE; Fri, 24 Mar 2000 13:24:19 -0800 (PST) (envelope-from mi@video-collage.com) X-Relay-IP: ‚  Received: from dufus.video-collage.com (dufus [10.222.222.77]) by xxx.video-collage.com (8.9.1a/8.9.1) with ESMTP id QAA00650; Fri, 24 Mar 2000 16:24:16 -0500 (EST) From: Mikhail Teterin Received: (from mi@localhost) by dufus.video-collage.com (8.9.3/8.9.3) id QAA85888; Fri, 24 Mar 2000 16:24:16 -0500 (EST) (envelope-from mi@xxx) Message-Id: <200003242124.QAA85888@dufus.video-collage.com> Subject: AHC_SCBPAGING_ENABLE on 2.2.8-STABLE To: stable@FreeBSD.org Date: Fri, 24 Mar 2000 16:24:16 -0500 (EST) Cc: gibbs@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL68 (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 Hello! Is the AHC_SCBPAGING_ENABLE safe to use with aic7880 adapter on the latest (cvsuped two days ago) 2.2.8-STABLE? The comment in LINT still warns against it, but it seems to be the standard in 4.0 and 3.4 now... What about other options -- AHC_ALLOW_MEMIO, AHC_TAGENABLE? Thanks in advance! -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 13:42:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 5FE9B37B66A; Fri, 24 Mar 2000 13:42:32 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA58589; Fri, 24 Mar 2000 13:42:32 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 24 Mar 2000 13:42:32 -0800 (PST) From: Kris Kennaway To: Conrad Sabatier Cc: "Jordan K. Hubbard" , stable@FreeBSD.ORG Subject: Re: What does "Voxware still supported in 4.0" mean exactly? 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 Fri, 24 Mar 2000, Conrad Sabatier wrote: > Despite this frequently noted complaint, the fact remains that Windows > still continues to work with much older hardware. Why shouldn't FreeBSD? Are you even listening, Conrad? I don't think you are. > One particularly worrisome note (well, to me, anyway) that appeared in this > thread mentioned the requirement to use "options OLD_ISA" (or something > like that) to get Voxware to work in 4.0/CURRENT. Is support for older, > pure ISA machines going away, too? Get your facts straight: 1) 5.0, not 4.0 2) No > Granted, sooner or later there comes a time in the life of every OS when > support for certain types of dinosaur hardware is finally abandoned, but I > hardly think the AWE boards could properly be described as ancient, > outdated, or seldom used anymore. This point has already been addressed. > If the new pcm driver supported the card as well as Voxware, I'd certainly > have no complaint, and would readily make the switch. But until pcm > allows me to use the wavetable device (including support for user loading > of Soundfonts) and is capable of controlling the card's nifty added > features such as reverb and chorus, it makes no sense at all for me to > "upgrade" to 4.0, when doing so represents a definite "downgrade" in at > least one department. > > And besides, where's the MIDI? :-) And just who has the gun pointed at your head forcing you to upgrade to 4.0? If 3.4 works for you, stick with 3.4. If pcm is broken for you in 4.0, wait until it's fixed. > While I can certainly appreciate the FreeBSD development team's desire for > a more modern, unified and well-integrated driver than Voxware, until such > time as it can provide the same functionality as the older driver, I do > strongly believe that Voxware should continue to be supported, and that > pcm still should be considered as an "experimental" option only. Amancio Hasty has already volunteered to maintain Voxware..I fail to see why you're still complainining when all of these things *HAVE BEEN ADDRESSED IN PRIOR MEAILS*. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 13:44: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id 9CC0537BB10; Fri, 24 Mar 2000 13:43:58 -0800 (PST) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id OAA47137; Fri, 24 Mar 2000 14:43:50 -0700 (MST) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <200003242143.OAA47137@caspian.plutotech.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mikhail Teterin Cc: stable@FreeBSD.org, gibbs@FreeBSD.org Subject: Re: AHC_SCBPAGING_ENABLE on 2.2.8-STABLE In-Reply-To: Your message of "Fri, 24 Mar 2000 16:24:16 EST." <200003242124.QAA85888@dufus.video-collage.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Mar 2000 14:43:50 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Hello! Is the AHC_SCBPAGING_ENABLE safe to use with aic7880 adapter on >the latest (cvsuped two days ago) 2.2.8-STABLE? The comment in LINT >still warns against it, but it seems to be the standard in 4.0 and 3.4 >now... What about other options -- AHC_ALLOW_MEMIO, AHC_TAGENABLE? > >Thanks in advance! > > -mi No, the option is not safe. Development on the 2.2 era SCSI system stopped some time ago and the problems with SCB paging were never addressed there. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 13:54: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from xxx.video-collage.com (xxx.video-collage.com [209.122.149.226]) by hub.freebsd.org (Postfix) with ESMTP id 65A5937B540; Fri, 24 Mar 2000 13:53:52 -0800 (PST) (envelope-from mi@dufus.video-collage.com) X-Relay-IP: ‚  Received: from dufus.video-collage.com (dufus [10.222.222.77]) by xxx.video-collage.com (8.9.1a/8.9.1) with ESMTP id QAA00731; Fri, 24 Mar 2000 16:53:46 -0500 (EST) Message-Id: <200003242153.QAA00731@xxx.video-collage.com> Date: Fri, 24 Mar 2000 16:53:43 -0500 (EST) From: mi@video-collage.com Reply-To: Mikhail Teterin Subject: Re: AHC_SCBPAGING_ENABLE on 2.2.8-STABLE To: "Justin T. Gibbs" Cc: stable@FreeBSD.ORG In-Reply-To: <200003242143.OAA47137@caspian.plutotech.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24 Mar, Justin T. Gibbs wrote: = >Hello! Is the AHC_SCBPAGING_ENABLE safe to use with aic7880 adapter = >on the latest (cvsuped two days ago) 2.2.8-STABLE? The comment in = >LINT still warns against it, but it seems to be the standard in = >4.0 and 3.4 now... What about other options -- AHC_ALLOW_MEMIO, = >AHC_TAGENABLE? = No, the option is not safe. Development on the 2.2 era SCSI system = stopped some time ago and the problems with SCB paging were never = addressed there. Thanks for the prompt response. Will I know, I'm in trouble right away (at boot), or will it mysteriously crash some time later? In other words, can I find out if it is safe for my hardware right away? What about the other two AHC_* options? Thanks, -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 13:55: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tristo.netinc.ca (primary.2gen.net [209.240.46.188]) by hub.freebsd.org (Postfix) with ESMTP id D8E4637BFED for ; Fri, 24 Mar 2000 13:54:47 -0800 (PST) (envelope-from mike@2Gen.net) Received: from localhost (mike@localhost) by tristo.netinc.ca (8.9.3/8.9.1) with ESMTP id SAA15816 for ; Fri, 24 Mar 2000 18:08:16 -0500 (EST) Date: Fri, 24 Mar 2000 18:08:16 -0500 (EST) From: Michael DeMutis X-Sender: mike@tristo.netinc.ca To: stable@FreeBSD.org Subject: CVSupFile 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 Here is my "cvsupfile" *default host=cvsup2.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs *default tag=RELENG_3 *default delete use-rel-suffix src-all src-crypto src-secure *default tag=. ports-all doc-all Do I need that 2nd occurance of "*default tag=." I'm looking to stay current with the 3.x-STABLE tree. Does this look right? Also - one more question. If I had previously downloaded all the 4.0 sources by changing the above to RELENG_4 and then changed it back to RELENG_3 is there anything I need to worry about when I compile? When cvs runs will it get rid of what it previously downloaded for 4.0 and replace it with the proper 3.x sources? These questions may seem foolish, but I just need to be sure as this is a production machine. Thanks -mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 14:10:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 52E6F37B7CD for ; Fri, 24 Mar 2000 14:10:34 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA21373; Fri, 24 Mar 2000 14:10:35 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Conrad Sabatier Cc: stable@FreeBSD.ORG Subject: Re: What does "Voxware still supported in 4.0" mean exactly? In-reply-to: Your message of "Fri, 24 Mar 2000 15:22:08 CST." Date: Fri, 24 Mar 2000 14:10:35 -0800 Message-ID: <21370.953935835@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Seriously, isn't that one of the chief criticisms of Microsoft, that every > time they release a new version of Windows, you have to plunk down for > {more,better,faster,newer,bigger} hardware in order to make the best use > of it? Microsoft is a company with billions of dollars in assets. FreeBSD is almost entirely volunteer supported, and those few people in active FreeBSD employ are not paid to work on audio support. If Microsoft is therefore unable or unwilling to continue to support old hardware, even with their resources, then please explain to me how it is you can expect FreeBSD to do more with volunteers. > Despite this frequently noted complaint, the fact remains that Windows > still continues to work with much older hardware. Why shouldn't FreeBSD? Indeed, why shouldn't it, and so where's your contribution to making it be so? That's the only thing that's going to help you here and these complaints truly do not address the issue at its most fundamentally important level: It takes someone to do the work even when it comes to maintaining old things at some minimum level of functionality and in a volunteer project, you should always be prepared to either volunteer yourself or shut up at some point. That decision point has now arrived in your case and it's up to you to decide which fork in the road you want to take. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 14:18:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.hcisp.net (Stargate.hcisp.net [208.60.89.18]) by hub.freebsd.org (Postfix) with SMTP id 8679637B57A for ; Fri, 24 Mar 2000 14:18:20 -0800 (PST) (envelope-from tim@mysql.com) Received: (qmail 12569 invoked from network); 24 Mar 2000 22:24:27 -0000 Received: from modem9.hcisp.net (HELO threads.polyesthetic.msg) (208.60.89.75) by stargate.hcisp.net with SMTP; 24 Mar 2000 22:24:27 -0000 Received: (qmail 37534 invoked by uid 1001); 24 Mar 2000 22:17:16 -0000 From: "Thimble Smith" Date: Fri, 24 Mar 2000 17:17:16 -0500 To: freebsd-stable@freebsd.org Subject: pthread_kill() not killing thread Message-ID: <20000324171716.E37030@threads.polyesthetic.msg> 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. I'm running 4.0-STABLE cvsup'd on Tuesday (21 Mar). It looks like pthread_kill() isn't killing the thread; I could be doing something wrong, of course. Here's the output of my test program: tim:/tmp$ cc -o simple simple.c -pthread tim:/tmp$ ./simple main-thrd: letting test thread start up... test-body: unblocking signal and looping... test-body: sleeping... main-thrd: sleeping... test-body: sleeping... main-thrd: killing test thread... main-thrd: waiting a sec... test-body: sleeping... main-thrd: unblocking TERM signal here... main-thrd: waiting a sec... test-body: sleeping... main-thrd: exiting test-body: sleeping... test-body: sleeping... test-body: sleeping... test-body: sleeping... test-body: returning tim:/tmp$ The TERM signal never gets delivered to the test thread. Here is the code: #include #include #include #include #include #include #include pthread_t test_thread; sigset_t set; void *test_body(void *arg) { int i; fprintf(stderr, "test-body: looping...\n"); /* this SIG_UNBLOCK doesn't have any effect */ /*assert( pthread_sigmask(SIG_UNBLOCK, &set, NULL) == 0);*/ for (i = 0; i < 8; ++i) { fprintf(stderr, "test-body: sleeping...\n"); sleep(1); } fprintf(stderr, "test-body: returning\n"); return NULL; } int main (void) { pthread_attr_t attrs; sigemptyset(&set); sigaddset(&set, SIGTERM); assert( pthread_sigmask(SIG_UNBLOCK, &set, NULL) == 0); assert( pthread_attr_init(&attrs) == 0); assert( pthread_attr_setdetachstate(&attrs, PTHREAD_CREATE_DETACHED) == 0); assert( pthread_create(&test_thread, &attrs, test_body, NULL) == 0 ); assert( pthread_attr_destroy(&attrs) == 0); fprintf(stderr, "main-thrd: letting test thread start up...\n"); sleep(1); /* I should have this uncommented for a real program, but it doesn't make any difference here - the signal isn't delivered. */ /*assert( pthread_sigmask(SIG_BLOCK, &set, NULL) == 0);*/ fprintf(stderr, "main-thrd: sleeping...\n"); sleep(1); fprintf(stderr, "main-thrd: killing test thread...\n"); assert( pthread_kill(test_thread, SIGTERM) == 0); fprintf(stderr, "main-thrd: waiting a sec...\n"); sleep(1); /* With LinuxThreads, this would cause the program to terminate. But with -stable, this has no effect. */ fprintf(stderr, "main-thrd: unblocking TERM signal here...\n"); assert( pthread_sigmask(SIG_UNBLOCK, &set, NULL) == 0); fprintf(stderr, "main-thrd: waiting a sec...\n"); sleep(1); fprintf(stderr, "main-thrd: exiting\n"); pthread_exit(NULL); /*exit(EXIT_SUCCESS);*/ } The extra pthread_sigmask(SIG_UNBLOCK, &set) that is in test_body() doesn't make any difference. Am I doing something wrong? Or should I file a problem report? Thanks, Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 14:26: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.ddg.com (eunuch.ddg.com [216.30.58.66]) by hub.freebsd.org (Postfix) with ESMTP id EFF2C37BD16 for ; Fri, 24 Mar 2000 14:26:01 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from nomad.dataplex.net (24.28.73.209) by mail.ddg.com with SMTP (Eudora Internet Mail Server 2.1); Fri, 24 Mar 2000 16:25:53 -0600 From: Richard Wackerbarth To: jkh@zippy.cdrom.com Subject: Re: What does "Voxware still supported in 4.0" mean exactly? Date: Fri, 24 Mar 2000 16:25:52 -0600 X-Mailer: KMail [version 1.1.37] Content-Type: text/plain Cc: stable@FreeBSD.ORG References: <21370.953935835@zippy.cdrom.com> In-Reply-To: <21370.953935835@zippy.cdrom.com> MIME-Version: 1.0 Message-Id: <00032416255200.06951@nomad.dataplex.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 24 Mar 2000, Jordan K. Hubbard wrote: > Microsoft is a company with billions of dollars in assets. FreeBSD is > almost entirely volunteer supported, FreeBSD has billions of bits in assets. But the price of a bit isn't what it used to be. :-) > and those few people in active > FreeBSD employ are not paid to work on audio support. If Microsoft is > therefore unable or unwilling to continue to support old hardware, Actually. M$S never really "supported" the devices. They made the vendors GIVE them the drivers. As a result, the unsupported devices are mostly because the VENDOR doesn't support the old hardware. M$S moves forward with their development just as FreeBSD does. The device support is "up for grabs". As a hardware vendor, why should I continue to support old hardware? There is profit only in additional sales. The original sales price never included years of "support". I only wish that the vendors would release technical info on unsupported hardware. But that would reduce the market for new hardware. :-( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 14:49:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from katroo.Sendmail.COM (katroo.Sendmail.COM [209.246.26.35]) by hub.freebsd.org (Postfix) with ESMTP id 6A61337BD21 for ; Fri, 24 Mar 2000 14:49:15 -0800 (PST) (envelope-from chrisd@sendmail.com) Received: from sendmail.com (gabriel.Sendmail.COM [10.210.100.74]) by katroo.Sendmail.COM (8.9.3/8.9.3) with ESMTP id OAA26116 for ; Fri, 24 Mar 2000 14:49:13 -0800 (PST) Message-ID: <38DBF0E9.E290CC4A@sendmail.com> Date: Fri, 24 Mar 2000 14:49:13 -0800 From: Christian DeKonink Organization: Sendmail, Inc - Services Department X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: perl not working 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 just installed 4.0 -release When ever I run perl i get the following errors and my program fails. perl: Warning: Setting locale failed perl: Warning: Please check that you locale settings: LC_ALL = C LC_CTYPE = en_US LANG = C are supported and installed on your system perl: warning: Falling back to standard locale ("C"). I set the variable via the shell before running but I still get this Any help would be appreciated. -- Christian DeKonink Technical Support Engineer Sendmail Inc. www.sendmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 14:54: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pan.ch.intel.com (pan.ch.intel.com [143.182.246.24]) by hub.freebsd.org (Postfix) with ESMTP id D028A37BD4A for ; Fri, 24 Mar 2000 14:53:45 -0800 (PST) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by pan.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.19 2000/01/29 00:15:43 dmccart Exp $) with ESMTP id PAA18965; Fri, 24 Mar 2000 15:53:35 -0700 (MST) Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id PAA15135; Fri, 24 Mar 2000 15:52:30 -0700 (MST) X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id RAA19208; Fri, 24 Mar 2000 17:53:35 -0500 (EST) X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14555.61934.240666.370558@hip186.ch.intel.com> Date: Fri, 24 Mar 2000 15:53:34 -0700 (MST) To: Christian DeKonink Cc: freebsd-stable@freebsd.org Subject: Re: perl not working In-Reply-To: <38DBF0E9.E290CC4A@sendmail.com> References: <38DBF0E9.E290CC4A@sendmail.com> X-Mailer: VM 6.75 under Emacs 20.3.11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Friday, March 24, Christian DeKonink wrote: ] > Hi I just installed 4.0 -release > > When ever I run perl i get the following errors and my program fails. > > perl: Warning: Setting locale failed > perl: Warning: Please check that you locale settings: > LC_ALL = C > LC_CTYPE = en_US > LANG = C > are supported and installed on your system > perl: warning: Falling back to standard locale ("C"). > > I set the variable via the shell before running but I still get this > > Any help would be appreciated. > I have the following in my /etc/csh.cshrc: setenv LC_ALL en_US.ISO_8859-1 setenv LC_CTYPE en_US.ISO_8859-1 setenv LANG en_US.ISO_8859-1 it fixed all of those warnings/problems, etc. -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 14:54:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from semail01.eng.us.uu.net (semail01.eng.us.uu.net [199.170.214.69]) by hub.freebsd.org (Postfix) with ESMTP id 4A2E937BCFE for ; Fri, 24 Mar 2000 14:54:09 -0800 (PST) (envelope-from stripes@eng.us.uu.net) Received: from garotte.eng.us.uu.net by semail01.eng.us.uu.net with ESMTP (peer crosschecked as: garotte.eng.us.uu.net [199.170.215.24]) id RAA13768; Fri, 24 Mar 2000 17:53:31 -0500 (EST) Received: from garotte.eng.us.uu.net by garotte.eng.us.uu.net with ESMTP (peer crosschecked as: localhost.eng.us.uu.net [127.0.0.1]) id RAA01871; Fri, 24 Mar 2000 17:53:31 -0500 (EST) Message-Id: To: usb-bsd@egroups.com, stable@freebsd.org Subject: USB error messages talking to D-Link DSB-H3E under FreeBSD4.0 Date: Fri, 24 Mar 2000 17:53:31 -0500 From: "Josh M. Osborne" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On my brand spanking new 4.0 system (installed so I can try some USB stuff) I get the following from the kernel: ohci0: mem 0xe6100000-0xe6100fff irq 12 at device 7 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered uhub1: Texas Instruments UT-USB41 hub, class 9/0, rev 1.10/1.10, addr 2 uhub1: 4 ports with 4 removable, self powered uhub1: port 4, set config at addr 3 failed uhub1: device problem, disabling port 4 The usb0 and uhub0 are (I assume) part of my motherbord, a Gigabyte 7IX. The "uhub1" is a D-Link "DSB-H3E", which is 3 USB ports and an itegrated 10baseT Ethernet part (I think the ethernet is a Kawasaki LSI KU5KUSB101B part). It is my guess that the port 4 that has the "device problem" is the ethernet. I added all the USB debugging options I saw in the LINT config, and an extra message "uhub_explore: usb_new_device failed, error=INVAL" shows up. chip1: at device 7.3 on pci0 ohci0: mem 0xe6100000-0xe6100fff irq 12 at device 7.4 o n pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered uhub1: Texas Instruments UT-USB41 hub, class 9/0, rev 1.10/1.10, addr 2 uhub1: 4 ports with 4 removable, self powered uhub_explore: usb_new_device failed, error=INVAL uhub1: device problem, disabling port 4 Does anyone have an ideas on anything else to try? Also, in case I can't get this device working, does anyone have any experiance with the ARK UB7132T (a similar device that also uses the Kawasaki LSI KU5KUSB101B part, but is made by another bunch of folks, and is in fact the unit I thought I had bought... until I looked at the box) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 15: 0:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from code.cs.unm.edu (code.cs.unm.edu [198.83.92.110]) by hub.freebsd.org (Postfix) with ESMTP id 005D737BC8A for ; Fri, 24 Mar 2000 15:00:43 -0800 (PST) (envelope-from spcoltri@code.cs.unm.edu) Received: from code.cs.unm.edu (localhost [127.0.0.1]) by code.cs.unm.edu (8.9.3/8.9.3) with ESMTP id PAA26547; Fri, 24 Mar 2000 15:59:19 -0700 (MST) (envelope-from spcoltri@code.cs.unm.edu) Message-Id: <200003242259.PAA26547@code.cs.unm.edu> To: John Reynolds~ Cc: Christian DeKonink , freebsd-stable@FreeBSD.ORG Subject: Re: perl not working In-Reply-To: Your message of "Fri, 24 Mar 2000 15:53:34 MST." <14555.61934.240666.370558@hip186.ch.intel.com> Date: Fri, 24 Mar 2000 15:59:18 -0700 From: Steve Coltrin Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I have the following in my /etc/csh.cshrc: >setenv LC_ALL en_US.ISO_8859-1 >setenv LC_CTYPE en_US.ISO_8859-1 >setenv LANG en_US.ISO_8859-1 >it fixed all of those warnings/problems, etc. For those users who use csh :) Of course, this is no problem on a one-user machine, but a better (?) way to fix it definitively would be to add the vars to the setenv= clause of the default: entry in /etc/login.conf . >-Jr -spc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 15: 8:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from katroo.Sendmail.COM (katroo.Sendmail.COM [209.246.26.35]) by hub.freebsd.org (Postfix) with ESMTP id DBECF37B517 for ; Fri, 24 Mar 2000 15:08:14 -0800 (PST) (envelope-from chrisd@sendmail.com) Received: from sendmail.com (gabriel.Sendmail.COM [10.210.100.74]) by katroo.Sendmail.COM (8.9.3/8.9.3) with ESMTP id PAA28905; Fri, 24 Mar 2000 15:04:43 -0800 (PST) Message-ID: <38DBF48B.B8A63D85@sendmail.com> Date: Fri, 24 Mar 2000 15:04:43 -0800 From: Christian DeKonink Organization: Sendmail, Inc - Services Department X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Steve Coltrin Cc: John Reynolds~ , freebsd-stable@FreeBSD.ORG Subject: Re: perl not working References: <200003242259.PAA26547@code.cs.unm.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for all your help. Its working now. Chris Steve Coltrin wrote: > > >I have the following in my /etc/csh.cshrc: > > >setenv LC_ALL en_US.ISO_8859-1 > >setenv LC_CTYPE en_US.ISO_8859-1 > >setenv LANG en_US.ISO_8859-1 > > >it fixed all of those warnings/problems, etc. > > For those users who use csh :) > > Of course, this is no problem on a one-user machine, but a better (?) way to > fix it definitively would be to add the vars to the setenv= clause of the > default: entry in /etc/login.conf . > > >-Jr > > -spc -- Christian DeKonink Technical Support Engineer Sendmail Inc. www.sendmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 15: 8:25 2000 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 CD8DB37B796 for ; Fri, 24 Mar 2000 15:08:18 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id SAA08054; Fri, 24 Mar 2000 18:07:30 -0500 (EST) Date: Fri, 24 Mar 2000 18:07:30 -0500 (EST) From: Daniel Eischen Message-Id: <200003242307.SAA08054@pcnet1.pcnet.com> To: freebsd-stable@FreeBSD.ORG, tim@mysql.com Subject: Re: pthread_kill() not killing thread Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thimble Smith wrote: > Hi. I'm running 4.0-STABLE cvsup'd on Tuesday (21 Mar). It > looks like pthread_kill() isn't killing the thread; I could be > doing something wrong, of course. Here's the output of my test > program: [ ... ] > The extra pthread_sigmask(SIG_UNBLOCK, &set) that is in test_body() > doesn't make any difference. > > Am I doing something wrong? Or should I file a problem report? My "interpretation" of the POSIX spec was that intra-process signals sent via pthread_kill() were treated differently than if the signal was sent to the process. I'll have to go back and re-read the POSIX spec -- perhaps I misunderstood it. At any rate, FreeBSDs threads implementation of pthread_kill() will not have the same effect as kill(2) -- the process will not be terminated by issuing a pthread_kill(thrd, SIGTERM) to a thread. Signals sent to threads via pthread_kill will invoke a signal handler if it is installed and will interrupt the thread from its current operation (returning -1 with EINTR). This all assumes that the thread isn't masking the signal, and that the handler isn't installed with SA_RESTART. Other conflicting "views" of the POSIX spec are certainly welcome. We will make every effort to conform to the spec. Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 16: 3:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.twave.net (twave.net [206.100.228.5]) by hub.freebsd.org (Postfix) with SMTP id 478CE37B6C6 for ; Fri, 24 Mar 2000 16:03:47 -0800 (PST) (envelope-from brameld@twave.net) Received: from [208.47.188.48] by mail.twave.net (NTMail 3.03.0018/1.abwg) with ESMTP id va478213 for ; Fri, 24 Mar 2000 19:03:33 -0500 From: Walter Brameld To: "Jeremiah Gowdy" , "Doug Barton" Subject: Re: perl vs buildworld and piping in 4.0 Date: Fri, 24 Mar 2000 19:03:08 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: , "Sergei Vyshenski" , , References: <3.0.5.32.20000324065537.007bc7d0@vivaldi> <38DBAA01.199856BB@gorean.org> <001101bf95c1$d2d27d60$0100000a@vista1.sdca.home.com> In-Reply-To: <001101bf95c1$d2d27d60$0100000a@vista1.sdca.home.com> MIME-Version: 1.0 Message-Id: <00032419033202.10255@Bozo_3.BozoLand.domain> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 24 Mar 2000, in a never-ending search for enlightenment, Jeremiah Gowdy wrote: > > > Yeah, I'm totally getting the same crap, I've failed make buildworld a > > > hundred times. It's driving me insane. I even rm -rf /usr/src and cvsup > > > again. Happens every time. I thought it was because I use SMP and was > > > running make -j2 or -j4, but even after building without -jX (much > slower) I > > > got the same crash. I think it's saying mkdir: File Exists: or > something. > > > > I vaguely remember something like this a while back. I deleted the > > directory that it was complaining about (so make could create it itself) > > and I was back in business. > > hmm. I'll try that. Right now I've cvsupped 4.0 stable, and I'm building > world as I type this. If it doesn't work, I'll burn my neighbor's house > down, go on an insane killing spree, and when I get done, I'll come back, > cvsup 4 release again, and see if I can't get the buildworld to work. Sounds like a plan to me..... -- Walter Brameld Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? Walter: And what does THIS button do?? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 16:56:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from nautilus.shore.net (nautilus.shore.net [207.244.124.104]) by hub.freebsd.org (Postfix) with ESMTP id E8F0437B72B for ; Fri, 24 Mar 2000 16:56:49 -0800 (PST) (envelope-from tjlegg@shore.net) Received: from eskimos.the-eleven.com [207.244.92.51] by nautilus.shore.net with esmtp (Exim) id 12YesO-0004xu-00; Fri, 24 Mar 2000 19:56:28 -0500 Mime-Version: 1.0 X-Sender: tjlegg@shell2.shore.net Message-Id: In-Reply-To: <200003242044.PAA00854@world.std.com> References: <200003242044.PAA00854@world.std.com> Date: Fri, 24 Mar 2000 19:56:18 -0500 To: Kenneth W Cochran , Matt Loschert From: Tom Legg Subject: Re: Questions source-upgrading 3.4-s to 4.0-s Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 3:44 PM -0500 3/24/2000, Kenneth W Cochran wrote: > >From loschert@servint.com Fri Mar 24 14:02:06 2000 >>Date: Fri, 24 Mar 2000 13:55:23 -0500 (EST) >>Subject: Re: Questions source-upgrading 3.4-s to 4.0-s >> > >On Fri, 24 Mar 2000, Kenneth W Cochran wrote: > >>Use the following to get all 4.0-STABLE source including crypto: >>src-all > >Of course... :) > >>cvs-crypto > >UPDATING says "Crypto & secure are now required." That, as I >understand would be src-crypto and src-secure. How would these >differ from cvs-crypto? Ie. would it be "better" to use those 2 >"tags" or to use the one cvs-crypto? I suppose what I may be >asking is "how do I make my new system look most like the >distributed CDs?" Well those two are missing src-sys-crypto which is the kicker. You can build a GENERIC kernel without src-sys-crytpo, but I know that a custom kernel with IPSEC will not build without these sources. I'm not sure how the newly built in ssh and ssl support are affected by a lack of src-sys-crypto. Any of the developers care to answer that one? And cvs-crypto is an umbrella tag that includes src-crypto, src-secure, and src-sys-crypto. One versus three. Your choice. -- ----- Tom Legg tjlegg@shore.net http://www.shore.net/~tjlegg/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 16:59:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id D601137B5B4 for ; Fri, 24 Mar 2000 16:59:53 -0800 (PST) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id QAA06823; Fri, 24 Mar 2000 16:59:43 -0800 (PST) (envelope-from Doug@gorean.org) Date: Fri, 24 Mar 2000 16:59:43 -0800 (PST) From: Doug Barton X-Sender: doug@dt051n0b.san.rr.com To: Michael DeMutis Cc: stable@FreeBSD.org Subject: Re: CVSupFile 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 Fri, 24 Mar 2000, Michael DeMutis wrote: > Here is my "cvsupfile" > > *default host=cvsup2.FreeBSD.org > *default base=/usr > *default prefix=/usr > *default release=cvs > *default tag=RELENG_3 > *default delete use-rel-suffix > > src-all > src-crypto > src-secure > *default tag=. > ports-all > doc-all > > > Do I need that 2nd occurance of "*default tag=." Yes. > I'm looking to stay current with the 3.x-STABLE tree. > Does this look right? Yes. > Also - one more question. > > If I had previously downloaded all the 4.0 sources by changing the above > to RELENG_4 and then changed it back to RELENG_3 is there anything I need > to worry about when I compile? Yes. If you've previously built and installed 4.0 you have to wipe your disk to downgrade. If you haven't, I'd 'rm /usr/src/*' and check the sources out again, just to be on the safe side. Good luck, Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 17:22:58 2000 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 11FE937BE11 for ; Fri, 24 Mar 2000 17:22:54 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id UAA23271; Fri, 24 Mar 2000 20:22:37 -0500 (EST) Date: Fri, 24 Mar 2000 20:22:37 -0500 (EST) From: Daniel Eischen Message-Id: <200003250122.UAA23271@pcnet1.pcnet.com> To: freebsd-stable@FreeBSD.ORG, tim@mysql.com Subject: Re: pthread_kill() not killing thread Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thimble Smith wrote: > Hi. I'm running 4.0-STABLE cvsup'd on Tuesday (21 Mar). It > looks like pthread_kill() isn't killing the thread; I could be > doing something wrong, of course. Here's the output of my test > program: From the POSIX spec (ISO/IEC 9945-1:1996), B.3.3.10, page 444: "Note that pthread_kill() only causes the signal to be handled in the context of the given thread; the signal action (termination or stopping) affects the process as a whole." OK, that pretty much confirms what you found. FreeBSD is not sending the signal to the process when there is no installed signal handler. I'll fix this. Thanks for pointing this out :-) Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 17:46:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from silver.he.net (silver.he.net [216.218.151.2]) by hub.freebsd.org (Postfix) with ESMTP id 43A8A37B6F6 for ; Fri, 24 Mar 2000 17:46:49 -0800 (PST) (envelope-from george@galis.org) Received: from bourne.net (root@access-240-163-163.ixpres.com [216.240.163.163]) by silver.he.net (8.8.6/8.8.2) with ESMTP id RAA13557 for ; Fri, 24 Mar 2000 17:46:18 -0800 X-Authentication-Warning: bourne.net: gx set sender to using -f Date: Fri, 24 Mar 2000 17:46:45 -0800 From: George Georgalis To: freebsd-stable@FreeBSD.ORG Subject: Re: Linux ext2 fs support changes in -stable Message-ID: <20000324174645.A956@localhost> References: <200003221548.KAA05168@world.std.com> <200003241727.MAA06724@world.std.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003241727.MAA06724@world.std.com>; from kwc@world.std.com on Fri, Mar 24, 2000 at 12:27:12PM -0500 X-Operating-System: Linux bourne Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>Kenneth W Cochran wrote: >>> Somewhat all-of-a-sudden, I am unable to r/w mount a Linux ext2 >>> filesystem on the same hdd with my BSD. I get in my syslog (& >>> on console): >>> /kernel: WARNING: R/W mount of dev 0xe040a denied due to >>> unsupported optional features >> >>This is telling you that this file system has features (put in >>the by a recent version of Linux, most likely) which our ext2fs >>code does not understand. Since we don't understand it, allowing >>a R/W mount is dangerous. > >Makes sense... Interesting that this does not happen on my other >hdd; I bet I made those filesystems under a previous Linux version... > >>You can read more about this using the cvsweb to check the commit Hi All, I'm entirely new to BSD but I do have a few years of Linux experience. I'm glad to see interest in accessing ext2! But I'll admit this list is a bit more than I can follow, usually. I would like to throw in, ext3 should be Linux standard this summer or fall with the release of stable 2.4.0 Linux kernel. The big highlight (besides being very different) being a journaling feature, allowing quick recovery from events like power failure. In the mean time, I'll be tuning my BSD skills, but since I'm a newbie, could someone recommend a lower volume and less technical list? I know nothing of BSD's filesystem, or similar hurtles, please respond directly if appropriate. TIA, // George -- +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ GEORGE GEORGALIS . ICXC . 858.621.9488 george@galis.org . . NIKI . . PO Box 3342 http://galis.org/george . . La Jolla, CA 92038 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 18:20:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id A63D137B5B6; Fri, 24 Mar 2000 18:20:16 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id SAA06158; Fri, 24 Mar 2000 18:20:17 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 24 Mar 2000 18:20:17 -0800 (PST) From: Kris Kennaway To: Tom Legg Cc: Kenneth W Cochran , Matt Loschert , freebsd-stable@freebsd.org Subject: Re: Questions source-upgrading 3.4-s to 4.0-s 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 Fri, 24 Mar 2000, Tom Legg wrote: > Well those two are missing src-sys-crypto which is the kicker. You > can build a GENERIC kernel without src-sys-crytpo, but I know that a > custom kernel with IPSEC will not build without these sources. I'm > not sure how the newly built in ssh and ssl support are affected by a > lack of src-sys-crypto. Any of the developers care to answer that one? No effect. They only affect in-kernel uses of crypto, currently ipsec. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 21:11:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mecca.servint.com (mecca.servint.com [209.50.225.14]) by hub.freebsd.org (Postfix) with ESMTP id 1CDFD37B7FB for ; Fri, 24 Mar 2000 21:11:55 -0800 (PST) (envelope-from loschert@servint.com) Received: from delft.servint.com (207-172-62-105.s105.tnt2.rcm.va.dialup.rcn.com [207.172.62.105]) by mecca.servint.com (8.9.3/8.9.0) with ESMTP id AAA21680 for ; Sat, 25 Mar 2000 00:30:53 -0500 (EST) Received: (qmail 64199 invoked by uid 1000); 25 Mar 2000 05:11:44 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 25 Mar 2000 05:11:44 -0000 Date: Sat, 25 Mar 2000 00:11:44 -0500 (EST) From: Matt Loschert To: Kenneth W Cochran Cc: freebsd-stable@freebsd.org Subject: Re: Questions source-upgrading 3.4-s to 4.0-s In-Reply-To: <200003242044.PAA00854@world.std.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 Fri, 24 Mar 2000, Kenneth W Cochran wrote: > So buildworld runs in its "own complete isolated" environment? > IOW, buildworld uses its "own" tools, etc., & doesn't need ie. > /bin, /usr/bin ... ?? (Except for a few basic things, like the > compiler (with which to "bootstrap" itself?"... :) Exactly. The only time there are snags is when an install or building tool is not included in the world building tool chain. AFAIK, this is the reason for the installworld -DNOINFO hack. install-info is not part of the build chain, but the install relies upon it (and in the case of the 3.x->4.0 upgrade, it relies on a new feature for the version not yet installed on the system). I could be mistaken on this point, but this is how I interpreted the discussion on -current. > >cvs-crypto > > UPDATING says "Crypto & secure are now required." That, as I > understand would be src-crypto and src-secure. How would these > differ from cvs-crypto? Ie. would it be "better" to use those 2 > "tags" or to use the one cvs-crypto? I suppose what I may be > asking is "how do I make my new system look most like the > distributed CDs?" As mentioned in another reply, cvs-crypto is simply a crypto catch-all tag. I prefer it because I want all crypto and thus I see it as cleaner. It's just personal preference though. > >If you want the latest ports collection and documentation, specify: > >ports-all tag=. > >doc-all tag=. > > I do that with a separate cvsup file/job... Why? Cvsup ports and docs more or less often? I just lump them all into my sup-file, along with src-all and cvs-crypto for RELENG_3, RELENG_4, and -CURRENT, all going into different directories. That way I can read through the source changes to all of the active branches, or upgrade/downgrade any way I want. > >supfile using something like: > >*default host=cvsup.FreeBSD.org > > I use one "closer..." Yeah, that was what I was getting at with the "something like" :) > >cd /usr/src/sbin/mknod && make install > > Along the lines of "dotting all the "i"s & "crossong all the > "t"s", I believe it would be a Good Idea to make this more > explicit in the instructions... :) Warner Losh is the man in charge of the UPDATING file. You might want to pass the suggestion along to him. > My devices are indeed da*; it was fresh-installed from the > 3.4-RELEASE CDs, so it appears that I can skip this step? > My /etc/fstab should also be ok? It should be. I have had no problems, but disks and devices are not my strong area. > >You need the new MAKEDEV script for 4.0 from /usr/src/etc. As > >far as I know, once you copy the new script into /dev, 'sh > >MAKEDEV all' should work fine. I could be wrong for certain > >configurations. > > Hmmm... Perhaps this needs more clarification? Again, devices are not my cup of tea. I have always just copied the new MAKEDEV into /dev and run 'sh MAKEDEV all'. Never had any problem, but again, that doesn't mean I haven't been doing something wrong. > >You probably should boot into single-user, but I have done it > >successfully after booting multi-user. > > I'm one of those "safety freaks" who always goes single-user for > installworld... :) That's probably smart. I am sure some day I will get bitten doing this. Until then, I will probably just live dangerously. > >For the upgrade, yes, install GENERIC. Once you have rebooted > >after the upgrade, it is much safer to rebuild your custom kernel. > > So, substitute GENERIC for "YOUR_KERNEL_HERE?" GENERIC for the initial upgrade kernel, YOUR_KERNEL_HERE after upgrade complete. > I think it would be a Very Good Idea to get "appropriate > portions" of this information into the UPDATING instructions; it > might help slow down the upgrading-deluge "here" on -stable... :) Again, send your suggestions to Warner Losh . He maintains the UPDATING file. Enjoy 4.0. - Matt -- Matt Loschert loschert@servint.com Software Engineer voice (703) 847-1381 ServInt Internet Services fax (703) 847-1383 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 24 23:12:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id A8E0937B7F7 for ; Fri, 24 Mar 2000 23:12:08 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p15-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.144]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id QAA04790; Sat, 25 Mar 2000 16:11:47 +0900 (JST) Message-ID: <38DC55BC.BA2240C2@newsguy.com> Date: Sat, 25 Mar 2000 14:59:24 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Conrad Sabatier Cc: stable@FreeBSD.ORG Subject: Re: What does "Voxware still supported in 4.0" mean exactly? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you will allow me, I'll explain the issues here. Conrad Sabatier wrote: > > I smell shades of M$ here. :-) > > Seriously, isn't that one of the chief criticisms of Microsoft, that every > time they release a new version of Windows, you have to plunk down for > {more,better,faster,newer,bigger} hardware in order to make the best use > of it? FreeBSD has always been infamous for picky hardware support. It's not a matter for more/better/faster/newer/bigger so much as this-or-nothing. This is a simple case of developer base. We have *one* person actively working on sound support, aside from japanese developers (which, unfortunately, are quite insular). Whatever HE spends time writing a driver for, that's what we support (support, as in _actively_). Now, on to existing support & Voxware stuff... > Despite this frequently noted complaint, the fact remains that Windows > still continues to work with much older hardware. Why shouldn't FreeBSD? Because we are evolving. Instead of burdening the OS with tons of older systems and interfaces that are not being actively maintened and would only: a) waste developer's time or b) bit-rot, resulting in some nasty remarks the first time someone stumbles on a bug besides increasing kernel size, and possibly making it impossible to speed up certain things or even adopt some new hardware standards, we simply *dump* the old interfaces. Whatever is being _actively_ supported, gets rewritten for the new interface. Whatever isn't, stop being supported at all. There is no way to be lean and mean and keep 10 years old interfaces that have long stopped being used in active development at the same time, sorry. And one thing we *DO* want is to be lean and mean. > One particularly worrisome note (well, to me, anyway) that appeared in this > thread mentioned the requirement to use "options OLD_ISA" (or something > like that) to get Voxware to work in 4.0/CURRENT. Is support for older, > pure ISA machines going away, too? No, Voxware is NOT being dropped on 4.0, and NO ONE ever said so. I have been reading this thread, and NOT A SINGLE TIME a committer said so. That said, it is quite possible that Voxware will stop being supported on 5.0-current in a short time. Now... you see that "OLD_ISA" up there? That's not a statement about ISA, it's about the kernel interface for ISA device drivers. We have been replacing our device driver interface with what we call "newbus". Newbus is _necessary_ to support some newer hardware. For 4.0, some compatibility interfaces were created so that drivers that were not converted continued to work. This compatibility interface is what OLD_ISA refers to. This was over a year ago. Some drivers were not converted in _all this time_, because _no one is working on them_. That includes Voxware. Notice, though, that Voxware is still working, to some extent. We have not yet completely removed support for the old interfaces, we have just made as much noise as possible about it, so that anyone who still cares about these drivers will feel compelled to actually work on them to bring them up to date. What we cannot do is stop FreeBSD development just because no one care enough about Voxware to keep it up to date (well, no one with the necessary skills, granted). And, then, there is all the complain about Voxware on 4.0 and the infamour "pnp" userconfig statements. Come on, guys, that was one of the most shameful things we had. Magic incantations one had to enter at boot to get one's sound card working, and which could only be found through careful tumbing through ancient tomes and mailing list archives. It was ridiculous to the point that a non-PnP device was easier to configure than a PnP one! Well, 4.0 does the right stuff: if you have PnP devices, it *recognizes them*, and configures the driver automatically. Only the driver has to use the new interface, which *supports* such behavior. That's one of the reasons we evolved so: that you'll never have to configure a PnP device by hand. Of course, Voxware won't understand this, unless someone port it to the newer interfaces. Voxware is dying because NO ONE IS SUPPORTING IT. We are not killing it on purpose. It's just a casualty of evolution. > Granted, sooner or later there comes a time in the life of every OS when > support for certain types of dinosaur hardware is finally abandoned, but I > hardly think the AWE boards could properly be described as ancient, > outdated, or seldom used anymore. Unfortunately, the AWE boards are not competing with other sound cards. They are competing with AMI MegaRaid SCSI controllers, with Alpha-based architectures, with PCMCIA and CardBUS and USB. *THAT'S* what's killing AWE: the new hardware standards we are supporting. Heck, even PnP in a decent way, instead of the nasty hack used on 3.x. It's just an unfortunate coincidence that the only driver supporting the AWE wavetable MIDI synthetizing happens to be a driver for which no active developer exists. If a driver has no developers... > While I can certainly appreciate the FreeBSD development team's desire for > a more modern, unified and well-integrated driver than Voxware, until such > time as it can provide the same functionality as the older driver, I do > strongly believe that Voxware should continue to be supported, and that > pcm still should be considered as an "experimental" option only. Yeah, well, you are right. Wait just a second while I remove support for Alpha and USB.... > In addition, I really would like to see user control over PnP devices (via > the pnp boot config command) brought back. It's just way too useful a > thing to throw away altogether. There is nothing useful about it. That's not how PnP devices are supposed to work. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@zurichgnomes.bsdconspiracy.net One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 0:36:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 205C837B5BC for ; Sat, 25 Mar 2000 00:36:41 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA42611; Sat, 25 Mar 2000 01:36:37 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA61278; Sat, 25 Mar 2000 01:36:28 -0700 (MST) Message-Id: <200003250836.BAA61278@harmony.village.org> To: "Daniel C. Sobral" Subject: Re: What does "Voxware still supported in 4.0" mean exactly? Cc: Conrad Sabatier , stable@FreeBSD.ORG In-reply-to: Your message of "Sat, 25 Mar 2000 14:59:24 +0900." <38DC55BC.BA2240C2@newsguy.com> References: <38DC55BC.BA2240C2@newsguy.com> Date: Sat, 25 Mar 2000 01:36:28 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38DC55BC.BA2240C2@newsguy.com> "Daniel C. Sobral" writes: : This is a simple case of developer base. We have *one* person actively : working on sound support, aside from japanese developers (which, : unfortunately, are quite insular). Whatever HE spends time writing a : driver for, that's what we support (support, as in _actively_). Heh. Sounds familiar :-). Actually, the Japanese laptop developers aren't that insular. One does need to make efforts to learn Japanese and those efforts will be rewarded with some of the Japanese developers learning English. It takes a lot of time, energy and effort to establish ones self in the mailing lists. It is likely worth the efforts, but when you are only one person, and have only a limited amount of time to spend, it does take away from the development time. Add to that the support load for the pccard stuff, and I've not had much time to move things forward on the new stuff. The big exceptions to this have been because the company I work for told me to do work that happened to overlap into the pccard sphere enough for me to resovlve issues surrounding it. There are days I wish that I could be three different people. One to do my day job, one to handle communicating with the Japenese as well as doing support on the existing software, and one to work on cardbus... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 5: 1:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id 0317B37B69D for ; Sat, 25 Mar 2000 05:01:48 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id OAA00318 for stable@FreeBSD.ORG; Sat, 25 Mar 2000 14:01:33 +0100 (MET) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id NAA25465 for stable@FreeBSD.ORG; Sat, 25 Mar 2000 13:53:09 +0100 (CET) (envelope-from andreas) Date: Sat, 25 Mar 2000 13:53:09 +0100 From: Andreas Klemm To: stable@FreeBSD.ORG Subject: HEADS-UP please: syslogd problems in 4.0: rejected in rule 0 due to port mismatch. Message-ID: <20000325135309.A25393@titan.klemm.gtn.com> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i X-Operating-System: FreeBSD 4.0-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My cisco is unable to write to the syslog daemon. Even adding the IP address with -a flags doesn't cure the problem. syslogd -d -v -a 172.16.2.2/32 allowaddr: rule 0: numeric, addr = 172.16.2.2, mask = 255.255.255.255; port = 514 off & running.... init cfline("*.err;kern.debug;auth.notice;mail.crit /dev/console", f, "*") cfline("*.notice;kern.debug;lpr.info;mail.crit;news.err /var/log/messages", f, "*") cfline("security.* /var/log/security", f, "*") cfline("mail.info /var/log/maillog", f, "*") cfline("lpr.info /var/log/lpd-errs", f, "*") cfline("cron.* /var/log/cron", f, "*") cfline("*.err root", f, "*") cfline("*.notice;news.err root", f, "*") cfline("*.alert root", f, "*") cfline("*.emerg *", f, "*") cfline("*.* /var/log/all.log", f, "*") cfline("local5.* /var/log/cisco.log", f, "*") cfline("local5.* /dev/console", f, "*") cfline("local6.info /var/log/tacacs.log", f, "*") cfline("news.crit /var/log/news/news.crit", f, "*") cfline("news.err /var/log/news/news.err", f, "*") cfline("news.notice /var/log/news/news.notice", f, "*") cfline("*.* /var/log/slip.log", f, "startslip") cfline("*.* /var/log/ppp.log", f, "ppp") 7 3 2 3 5 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 X CONSOLE: /dev/console 7 5 2 5 5 5 6 3 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 X FILE: /var/log/messages X X X X X X X X X X X X X 8 X X X X X X X X X X X FILE: /var/log/security X X 6 X X X X X X X X X X X X X X X X X X X X X X FILE: /var/log/maillog X X X X X X 6 X X X X X X X X X X X X X X X X X X FILE: /var/log/lpd-errs X X X X X X X X X 8 X X X X X X X X X X X X X X X FILE: /var/log/cron 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 X USERS: root, 5 5 5 5 5 5 5 3 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 X USERS: root, 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 X USERS: root, 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 X WALL: 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 X FILE: /var/log/all.log X X X X X X X X X X X X X X X X X X X X X 8 X X X FILE: /var/log/cisco.log X X X X X X X X X X X X X X X X X X X X X 8 X X X CONSOLE: /dev/console X X X X X X X X X X X X X X X X X X X X X X 6 X X FILE: /var/log/tacacs.log X X X X X X X 2 X X X X X X X X X X X X X X X X X FILE: /var/log/news/news.crit X X X X X X X 3 X X X X X X X X X X X X X X X X X FILE: /var/log/news/news.err X X X X X X X 5 X X X X X X X X X X X X X X X X X FILE: /var/log/news/news.notice 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 X FILE: /var/log/slip.log (startslip) 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 X FILE: /var/log/ppp.log (ppp) logmsg: pri 56, flags 4, from titan, msg syslogd: restart Logging to FILE /var/log/all.log syslogd: restarted cvthname(172.16.2.2) validate: dgram from IP 172.16.2.2, port 49902, name cisco.klemm.gtn.com; rejected in rule 0 due to port mismatch. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ What happened ? -- Andreas Klemm http://people.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD New APSFILTER 520 and songs from our band - http://people.freebsd.org/~andreas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 5:15:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id E551637B702 for ; Sat, 25 Mar 2000 05:15:28 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id OAA02020 for stable@FreeBSD.ORG; Sat, 25 Mar 2000 14:15:14 +0100 (MET) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id OAA26465 for stable@FreeBSD.ORG; Sat, 25 Mar 2000 14:13:44 +0100 (CET) (envelope-from andreas) Date: Sat, 25 Mar 2000 14:13:44 +0100 From: Andreas Klemm To: stable@FreeBSD.ORG Subject: Re: HEADS-UP please: syslogd problems in 4.0: rejected in rule 0 due to port mismatch. Message-ID: <20000325141343.A26444@titan.klemm.gtn.com> References: <20000325135309.A25393@titan.klemm.gtn.com> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i In-Reply-To: <20000325135309.A25393@titan.klemm.gtn.com>; from andreas@klemm.gtn.com on Sat, Mar 25, 2000 at 01:53:09PM +0100 X-Operating-System: FreeBSD 4.0-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 25, 2000 at 01:53:09PM +0100, Andreas Klemm wrote: > My cisco is unable to write to the syslog daemon. > Even adding the IP address with -a flags doesn't cure the problem. > > syslogd -d -v -a 172.16.2.2/32 Well, to be more precise, syslogd runs, but -a doesn't allow me to accept only syslog updates from my cisco. First I overlooked -s after mergemaster run... -- Andreas Klemm http://people.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD New APSFILTER 520 and songs from our band - http://people.freebsd.org/~andreas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 6:50:52 2000 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 982C437B8D9; Sat, 25 Mar 2000 06:50:45 -0800 (PST) (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 GAA08551; Sat, 25 Mar 2000 06:50:38 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda08549; Sat Mar 25 06:50:23 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id GAA31063; Sat, 25 Mar 2000 06:50:23 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdt31053; Sat Mar 25 06:49:37 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id GAA28467; Sat, 25 Mar 2000 06:49:36 -0800 (PST) Message-Id: <200003251449.GAA28467@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdX28463; Sat Mar 25 06:49:14 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: Kris Kennaway Cc: "Geoffrey T. Cheshire" , freebsd-stable Subject: Re: What cruft to remove after 3.4 -> 4.0? In-reply-to: Your message of "Thu, 23 Mar 2000 12:25:08 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 25 Mar 2000 06:49:12 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Kri s Kennaway writes: > On Thu, 23 Mar 2000, Geoffrey T. Cheshire wrote: > > > Is there a canonical list of things like this to pare? Should I use > > pkg_delete? > > Here's the canonical list: > > openssl > openssh krb5 pipsecd Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC 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 Mar 25 6:58:52 2000 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 6B5E537B5B1 for ; Sat, 25 Mar 2000 06:58:48 -0800 (PST) (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 GAA08565; Sat, 25 Mar 2000 06:56:39 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda08563; Sat Mar 25 06:56:23 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id GAA31088; Sat, 25 Mar 2000 06:56:22 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdK31086; Sat Mar 25 06:55:37 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id GAA28504; Sat, 25 Mar 2000 06:55:35 -0800 (PST) Message-Id: <200003251455.GAA28504@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdY28497; Sat Mar 25 06:54:57 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: "Daniel C. Sobral" Cc: Cy Schubert - ITSD Open Systems Group , "Jordan K. Hubbard" , Thomas David Rivers , witr@rwwa.com, stable@FreeBSD.ORG, witr@pobox.rwwa.com Subject: Re: V4.0 and Walnut Creek Subscriptions... In-reply-to: Your message of "Fri, 24 Mar 2000 05:02:36 +0900." <38DA785C.585CC385@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 25 Mar 2000 06:54:57 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38DA785C.585CC385@newsguy.com>, "Daniel C. Sobral" writes: > Cy Schubert - ITSD Open Systems Group wrote: > > > > In message <38D97069.C5811525@newsguy.com>, "Daniel C. Sobral" writes: > > > "Jordan K. Hubbard" wrote: > > > > > > > > No, you won't get two copies. > > > > > > Just charged twice. ;-> > > > > What? Are you saying WC is actually a law firm? > > Ah, but it isn't WC anymore, is it? Now it's BSDI. :-) Besides, Jordan > is a lawyer script(*), didn't you know? On the serious side... I take it that the rumours about BSDI purchasing WC were correct. I wonder what implications that will have on FreeBSD. I hope they'll be as or more successful than RedHat. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC 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 Mar 25 8:36:47 2000 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 97D6A37B6E1 for ; Sat, 25 Mar 2000 08:36:44 -0800 (PST) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id LAA30868; Sat, 25 Mar 2000 11:36:47 -0500 (EST) (envelope-from bandix@looksharp.net) Date: Sat, 25 Mar 2000 11:36:47 -0500 (EST) From: "Brandon D. Valentine" To: FreeBSD-STABLE Cc: Conrad Sabatier Subject: Re: What does "Voxware still supported in 4.0" mean exactly? 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 Fri, 24 Mar 2000, Kris Kennaway wrote: >> One particularly worrisome note (well, to me, anyway) that appeared in this >> thread mentioned the requirement to use "options OLD_ISA" (or something >> like that) to get Voxware to work in 4.0/CURRENT. Is support for older, >> pure ISA machines going away, too? > >Get your facts straight: > >1) 5.0, not 4.0 >2) No Do people honestly think ISA support is disappearing? From an OS that just released its first version that supports MCA busses? If anything old, obscure hardware support is getting better, not going away. The only thing going away is the old method of interfacing ISA drivers with the kernel. Everything is moving to newbus, and I can think of very few drivers which aren't making that transition. And if someone jumped up and down screaming bloody murder that their favorite driver hadn't been newbussed yet, and there wasn't a replacement, I'm sure something would be done. ------------------------------------------------------------- | -Brandon D. Valentine bandix at looksharp.net | bandix on EFnet IRC BVRiker on AIM ------------------------------------------------------------- | "...and as for hackers, we note that all of those known to | The Register are so strapped financially that seizing their | property would be tantamount to squeezing blood from a | stone." -- The Register, 02/17/2000 ------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 8:47:47 2000 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 20BB937B8F4 for ; Sat, 25 Mar 2000 08:47:40 -0800 (PST) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id LAA30969 for ; Sat, 25 Mar 2000 11:47:43 -0500 (EST) (envelope-from bandix@looksharp.net) Date: Sat, 25 Mar 2000 11:47:43 -0500 (EST) From: "Brandon D. Valentine" To: FreeBSD-STABLE Subject: Re: What does "Voxware still supported in 4.0" mean exactly? In-Reply-To: <38DC55BC.BA2240C2@newsguy.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 Sat, 25 Mar 2000, Daniel C. Sobral wrote: >Unfortunately, the AWE boards are not competing with other sound cards. >They are competing with AMI MegaRaid SCSI controllers, with Alpha-based >architectures, with PCMCIA and CardBUS and USB. *THAT'S* what's killing >AWE: the new hardware standards we are supporting. Heck, even PnP in a >decent way, instead of the nasty hack used on 3.x. It's just an >unfortunate coincidence that the only driver supporting the AWE >wavetable MIDI synthetizing happens to be a driver for which no active >developer exists. If a driver has no developers... And there is not one single good reason why one couldn't strip out the AWE wavetable MIDI code from Voxware and port it to newpcm. If you need MIDI that badly, DO IT. The code already exists, it is not a matter of getting documentation. It is a simple matter of porting. ------------------------------------------------------------- | -Brandon D. Valentine bandix at looksharp.net | bandix on EFnet IRC BVRiker on AIM ------------------------------------------------------------- | "...and as for hackers, we note that all of those known to | The Register are so strapped financially that seizing their | property would be tantamount to squeezing blood from a | stone." -- The Register, 02/17/2000 ------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 9:13: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bluebottle.calcaphon.com (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 1ED5237B790 for ; Sat, 25 Mar 2000 09:12:56 -0800 (PST) (envelope-from n_hibma@calcaphon.com) Received: from henny.calcaphon.com (henny.calcaphon.com [10.0.0.36]) by bluebottle.calcaphon.com (8.9.3/8.9.1) with ESMTP id RAA23605; Sat, 25 Mar 2000 17:17:05 GMT (envelope-from n_hibma@calcaphon.com) Date: Sat, 25 Mar 2000 17:10:29 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: usb-bsd@egroups.com Cc: stable@freebsd.org Subject: Re: [usb-bsd] USB error messages talking to D-Link DSB-H3E under FreeBSD4.0 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 Try and connect the USB device to the machine directly. Nick On Fri, 24 Mar 2000, Josh M. Osborne wrote: > On my brand spanking new 4.0 system (installed so I can try some USB > stuff) I get the following from the kernel: > > ohci0: mem 0xe6100000-0xe6100fff irq 12 at device 7 on pci0 > usb0: OHCI version 1.0, legacy support > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 4 ports with 4 removable, self powered > uhub1: Texas Instruments UT-USB41 hub, class 9/0, rev 1.10/1.10, addr 2 > uhub1: 4 ports with 4 removable, self powered > uhub1: port 4, set config at addr 3 failed > uhub1: device problem, disabling port 4 > > The usb0 and uhub0 are (I assume) part of my motherbord, a Gigabyte > 7IX. The "uhub1" is a D-Link "DSB-H3E", which is 3 USB ports and > an itegrated 10baseT Ethernet part (I think the ethernet is a > Kawasaki LSI KU5KUSB101B part). > > It is my guess that the port 4 that has the "device problem" is > the ethernet. > > I added all the USB debugging options I saw in the LINT config, and > an extra message "uhub_explore: usb_new_device failed, error=INVAL" > shows up. > > chip1: at device 7.3 on pci0 > ohci0: mem 0xe6100000-0xe6100fff irq 12 at device 7.4 o > n pci0 > usb0: OHCI version 1.0, legacy support > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 4 ports with 4 removable, self powered > uhub1: Texas Instruments UT-USB41 hub, class 9/0, rev 1.10/1.10, addr 2 > uhub1: 4 ports with 4 removable, self powered > uhub_explore: usb_new_device failed, error=INVAL > uhub1: device problem, disabling port 4 > > Does anyone have an ideas on anything else to try? > > > > Also, in case I can't get this device working, does anyone have > any experiance with the ARK UB7132T (a similar device that also > uses the Kawasaki LSI KU5KUSB101B part, but is made by another > bunch of folks, and is in fact the unit I thought I had bought... > until I looked at the box) > > ------------------------------------------------------------------------ > Learn more with SmartPlanet. It's a new way of learning online. > SmartPlanet offers hundreds of courses to take on your time, > in your space. Join for FREE today! > http://click.egroups.com/1/1704/6/_/85983/_/953938458/ > > eGroups.com Home: http://www.egroups.com/group/usb-bsd/ > http://www.egroups.com - Simplifying group communications > > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 10:24:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp8.teleport.com (smtp8.teleport.com [192.108.254.52]) by hub.freebsd.org (Postfix) with SMTP id 3D68437B8C5 for ; Sat, 25 Mar 2000 10:24:42 -0800 (PST) (envelope-from pl@teleport.com) Received: (qmail 397 invoked from network); 25 Mar 2000 18:24:29 -0000 Received: from user2.teleport.com (qmailr@192.108.254.12) by smtp8.teleport.com with SMTP; 25 Mar 2000 18:24:29 -0000 Received: (qmail 5406 invoked by uid 64886); 25 Mar 2000 18:24:29 -0000 Date: Sat, 25 Mar 2000 10:24:29 -0800 (PST) From: Patrick Lewis To: freebsd-stable@freebsd.org Subject: buildworld fails, hardware? 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 have been trying off an on for the last couple of weeks to rebuild my system via make world & friends (I have never done this before). Currently, I have 3.4-RELEASE, and am trying to move to STABLE (RELENG_3). cvsup appears to work as expected. Basic system info: AMD k6-3, 128MB Ram, SCSI disk system. Other than this issue, the machine has worked flawlessly, albeit under light loads. Whenever I do a make buildworld, I always fail. For instance: cc -O -pipe -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config -DFREEBSD_NATIVE -DDEFAULT_TARGET_VERSION=\"2.7.2.3\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/expr.c -o expr.o {standard input}: Assembler messages: {standard input}:14114: Error: no such 386 instruction: `mowl' *** Error code 1 Stop. ... and: cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/ld/i386 -I/usr/src/gnu/usr.bin/binutils/ld -I/usr/src/gnu/usr.bin/binutils/ld/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/include -DDEFAULT_EMULATION=\"elf_i386\" -DTARGET=\"i386-unknown-freebsdelf\" -DSCRIPTDIR=\"/usr/obj/usr/src/tmp/usr/libdata\" -I/usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld -I/usr/obj/usr/src/tmp/usr/include -c ldlex.c {standard input}: Assembler messages: {standard input}:4428: Error: Rest of line ignored. First ignored character valued 0xb. *** Error code 1 Stop. ... and: cc -O -pipe -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config -DFREEBSD_NATIVE -DDEFAULT_TARGET_VERSION=\"2.7.2.3\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/combine.c -o combine.o {standard input}: Assembler messages: {standard input}:19565: Error: invalid character (0xb) in first operand *** Error code 1 Stop. To me, funky fails at differing times when compiling identical source points to a hardware problem, although it doesn't look like memory problems that are described in the Handbook (Signal 11). In the mailing list archives, I saw similar assembler type errors described with K6 chips (a K6 bug), but it looks like these were resolved by AMD a long time ago. I guess my questions are: 1) Is this a hardware issue? Could it be anything else? 2) If it is a hardware issue, any ideas what it might be? Can I narrow the options down further without buying new hardware? 3) Am I forgetting something really stupid? Thanks in advance. Patrick Lewis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 11:18:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 6FCFA37B8D9 for ; Sat, 25 Mar 2000 11:18:35 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id OAA20466; Sat, 25 Mar 2000 14:18:31 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200003251918.OAA20466@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Nick Hibma Cc: usb-bsd@egroups.com, stable@FreeBSD.ORG, stripes@eng.us.uu.net X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: [usb-bsd] USB error messages talking to D-Link DSB-H3E under FreeBSD4.0 References: In-reply-to: Your message of "Sat, 25 Mar 2000 17:10:29 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 25 Mar 2000 14:18:31 -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick, I don't think that it's possible to do so, as this is probably more like a multifunction device with a 4 port USB hub, where one of the ports internally is connected to the USB Ethernet device. In fact, that TI USB hub is the same part embedded in my Microsoft USB keyboard, which has two USB device ports, the keyboard, and an HID device. Seems like it's a popular part. louie > > Try and connect the USB device to the machine directly. > > Nick > > On Fri, 24 Mar 2000, Josh M. Osborne wrote: > > > On my brand spanking new 4.0 system (installed so I can try some USB > > stuff) I get the following from the kernel: > > > > ohci0: mem 0xe6100000-0xe6100fff irq 12 at device 7 on pci0 > > usb0: OHCI version 1.0, legacy support > > usb0: on ohci0 > > usb0: USB revision 1.0 > > uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > > uhub0: 4 ports with 4 removable, self powered > > uhub1: Texas Instruments UT-USB41 hub, class 9/0, rev 1.10/1.10, addr 2 > > uhub1: 4 ports with 4 removable, self powered > > uhub1: port 4, set config at addr 3 failed > > uhub1: device problem, disabling port 4 > > > > The usb0 and uhub0 are (I assume) part of my motherbord, a Gigabyte > > 7IX. The "uhub1" is a D-Link "DSB-H3E", which is 3 USB ports and > > an itegrated 10baseT Ethernet part (I think the ethernet is a > > Kawasaki LSI KU5KUSB101B part). > > > > It is my guess that the port 4 that has the "device problem" is > > the ethernet. > > > > I added all the USB debugging options I saw in the LINT config, and > > an extra message "uhub_explore: usb_new_device failed, error=INVAL" > > shows up. > > > > chip1: at device 7.3 on pci0 > > ohci0: mem 0xe6100000-0xe6100fff irq 12 at device 7.4 o > > n pci0 > > usb0: OHCI version 1.0, legacy support > > usb0: on ohci0 > > usb0: USB revision 1.0 > > uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > > uhub0: 4 ports with 4 removable, self powered > > uhub1: Texas Instruments UT-USB41 hub, class 9/0, rev 1.10/1.10, addr 2 > > uhub1: 4 ports with 4 removable, self powered > > uhub_explore: usb_new_device failed, error=INVAL > > uhub1: device problem, disabling port 4 > > > > Does anyone have an ideas on anything else to try? > > > > > > > > Also, in case I can't get this device working, does anyone have > > any experiance with the ARK UB7132T (a similar device that also > > uses the Kawasaki LSI KU5KUSB101B part, but is made by another > > bunch of folks, and is in fact the unit I thought I had bought... > > until I looked at the box) > > > > ------------------------------------------------------------------------ > > Learn more with SmartPlanet. It's a new way of learning online. > > SmartPlanet offers hundreds of courses to take on your time, > > in your space. Join for FREE today! > > http://click.egroups.com/1/1704/6/_/85983/_/953938458/ > > > > eGroups.com Home: http://www.egroups.com/group/usb-bsd/ > > http://www.egroups.com - Simplifying group communications > > > > > > -- > n_hibma@webweaving.org > n_hibma@freebsd.org USB project > http://www.etla.net/~n_hibma/ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-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 Mar 25 12:21:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.gmx.net (mail1.gmx.net [194.221.183.61]) by hub.freebsd.org (Postfix) with SMTP id DD8C437B951 for ; Sat, 25 Mar 2000 12:21:37 -0800 (PST) (envelope-from Gerhard.Sittig@gmx.net) Received: (qmail 15034 invoked by uid 0); 25 Mar 2000 20:21:35 -0000 Received: from pc19f5ac3.dip.t-dialin.net (HELO speedy.gsinet) (193.159.90.195) by mail1.gmx.net with SMTP; 25 Mar 2000 20:21:35 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id UAA06801 for stable@FreeBSD.ORG; Sat, 25 Mar 2000 20:37:30 +0100 Date: Sat, 25 Mar 2000 20:37:30 +0100 From: Gerhard Sittig To: stable@FreeBSD.ORG Subject: Re: What does "Voxware still supported in 4.0" mean exactly? Message-ID: <20000325203730.B24822@speedy.gsinet> Mail-Followup-To: stable@FreeBSD.ORG References: <38DC55BC.BA2240C2@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38DC55BC.BA2240C2@newsguy.com>; from dcs@newsguy.com on Sat, Mar 25, 2000 at 02:59:24PM +0900 Organization: System Defenestrators Inc. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 25, 2000 at 14:59 +0900, Daniel C. Sobral wrote: > > Conrad Sabatier wrote: > > > > In addition, I really would like to see user control over PnP > > devices (via the pnp boot config command) brought back. It's > > just way too useful a thing to throw away altogether. > > There is nothing useful about it. That's not how PnP devices > are supposed to work. Please forgive my ignorance on this subject, but does it mean a user (or better: admin) has _NO_ control any longer over the way resources are managed (assigned)? Can you direct me to a place I can learn more about the way things work now? The reason for my question is: Pure PnP machines might be easy to handle this way and automatic measures can work. BUT when I have a machine with a BIOS not supporting me (when reserving resources and assigning them) or when I have legacy hardware I don't want to or cannot load a driver for and thus reserve its resources, there seems to be no way to keep the PnP manager from arranging collisions and make things worse than necessary. I don't care very much about how PnP was _meant_ to work -- I've seen too many broken implementations (this is valid for PCI, too). That's when I wish to gain manual control or at least influence over these mechanisms when automation fails. So I would like to have something comparable to the isapnp tools I know from Linux: They provide means to identify and dump components and their requirements, they can determine working arrangements _and_ leave manual intervention as a last resort for the problematic cases. Even if I cannot keep the automatic manager from assigning any "free" resources to the found components, _I_ want to state _what_'s free for them! If you can tell me I have this chance then I may follow you in that more control is not really useful. If I don't have the chance to keep collisions with legacy stuff from occuring then something important is missing. > -- > Daniel C. Sobral (8-DCS) BTW your sigdashes seem to miss the trailing space. This prevents decent reader software from recognizing the remaining stuff as a sig. Please make it read "-- ". Thanks! 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 Sat Mar 25 13: 6: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 29B6337B974; Sat, 25 Mar 2000 13:06:03 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA84849; Sat, 25 Mar 2000 13:06:03 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 25 Mar 2000 13:06:02 -0800 (PST) From: Kris Kennaway To: Cy Schubert - ITSD Open Systems Group Cc: "Geoffrey T. Cheshire" , freebsd-stable Subject: Re: What cruft to remove after 3.4 -> 4.0? In-Reply-To: <200003251449.GAA28467@cwsys.cwsent.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 Sat, 25 Mar 2000, Cy Schubert - ITSD Open Systems Group wrote: > > Here's the canonical list: > > > > openssl > > openssh > > krb5 This isn't in the base system. We have heimdal-kerberos5, but it's not nearly as complete or functional as MIT-kerberos5 > pipsecd Again, we have *an* ipsec implementation, but it's not pipsecd and people don't necessarily have to make the transition if it's working properly for them. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 13:48:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from netcom.com (netcom8.netcom.com [199.183.9.108]) by hub.freebsd.org (Postfix) with ESMTP id 1ADEB37B80B for ; Sat, 25 Mar 2000 13:48:23 -0800 (PST) (envelope-from stanb@netcom.com) Received: (from stanb@localhost) by netcom.com (8.9.3/8.9.3) id NAA19065 for freebsd-stable@freebsd.org; Sat, 25 Mar 2000 13:48:15 -0800 (PST) From: Stan Brown Message-Id: <200003252148.NAA19065@netcom.com> Subject: Why is the ep network driver not in the 4.0 install kernel? To: freebsd-stable@freebsd.org (FreeBSD Stable List) Date: Sat, 25 Mar 2000 16:48:15 -0500 (EST) X-Mailer: ELM [version 2.5 PL3] 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 I am trying to install 4.0 on a machine this weekend to try it out. I normall install via ftp from my home network. The machine in question has a 3COM NIC in it. Imagine my suprise when entering the kernel visula configurator to ind no ep driver! Why is this? How can I install on this machine without it? -- Stan Brown stanb@netcom.com 404-996-6955 Factory Automation Systems Atlanta Ga. -- Look, look, see Windows 95. Buy, lemmings, buy! Pay no attention to that cliff ahead... Henry Spencer (c) 1998 Stan Brown. Redistribution via the Microsoft Network is prohibited. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 14: 1: 0 2000 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 E11BD37B80B for ; Sat, 25 Mar 2000 14:00:57 -0800 (PST) (envelope-from djkanter@nwu.edu) Received: (from mailnull@localhost) by hecky.it.northwestern.edu (8.8.7/8.8.7) id QAA28822 for ; Sat, 25 Mar 2000 16:00:57 -0600 (CST) Received: from localhost.localdomain (coconut-36-028056.nuts.nwu.edu [165.124.28.56]) by hecky.acns.nwu.edu via smap (V2.0) id xma028805; Sat, 25 Mar 00 16:00:48 -0600 Received: (from david@localhost) by localhost.localdomain (8.9.3/8.9.3) id PAA57457 for freebsd-stable@freebsd.org; Sat, 25 Mar 2000 15:04:03 -0600 (CST) (envelope-from david) Date: Sat, 25 Mar 2000 15:04:03 -0600 From: David Kanter To: FreeBSD stable Subject: CVSup and source tree Message-ID: <20000325150403.A57446@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Organization: Northwestern University X-Operating-System: FreeBSD localhost.localdomain 3.4-STABLE FreeBSD 3.4-STABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think I accidentally deleted a few files from my source tree (hit control-C before it got too far). Can I just run cvsup on the stable branch and automatically get any files I may have blown away? -- David Kanter djkanter@nwu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 14: 3:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 91F8937B80B; Sat, 25 Mar 2000 14:03:22 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA97698; Sat, 25 Mar 2000 14:03:23 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 25 Mar 2000 14:03:22 -0800 (PST) From: Kris Kennaway To: David Kanter Cc: FreeBSD stable Subject: Re: CVSup and source tree In-Reply-To: <20000325150403.A57446@localhost.localdomain> 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, 25 Mar 2000, David Kanter wrote: > I think I accidentally deleted a few files from my source tree (hit > control-C before it got too far). Can I just run cvsup on the stable branch > and automatically get any files I may have blown away? Yes. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 14:54: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from erouter0.it-datacntr.louisville.edu (erouter0.it-datacntr.louisville.edu [136.165.1.36]) by hub.freebsd.org (Postfix) with ESMTP id 5430A37B76E for ; Sat, 25 Mar 2000 14:54:04 -0800 (PST) (envelope-from k.stevenson@louisville.edu) Received: from osaka.louisville.edu (osaka.louisville.edu [136.165.1.114]) by erouter0.it-datacntr.louisville.edu (Postfix) with ESMTP id 10E6624E5E; Sat, 25 Mar 2000 17:54:02 -0500 (EST) Received: by osaka.louisville.edu (Postfix, from userid 15) id EBE0018605; Sat, 25 Mar 2000 17:53:57 -0500 (EST) Date: Sat, 25 Mar 2000 17:53:57 -0500 From: Keith Stevenson To: Stan Brown Cc: FreeBSD Stable List Subject: Re: Why is the ep network driver not in the 4.0 install kernel? Message-ID: <20000325175357.B73082@osaka.louisville.edu> References: <200003252148.NAA19065@netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003252148.NAA19065@netcom.com>; from stanb@netcom.com on Sat, Mar 25, 2000 at 04:48:15PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 25, 2000 at 04:48:15PM -0500, Stan Brown wrote: > I am trying to install 4.0 on a machine this weekend to try it out. I > normall install via ftp from my home network. > > The machine in question has a 3COM NIC in it. Imagine my suprise when > entering the kernel visula configurator to ind no ep driver! > > Why is this? How can I install on this machine without it? I asked a similar question and was told that the kernel configurator only shows drivers which are not capable of asking the card for its configuration. The ep driver behaves itself well, so it doesn't have to be in the configurator. I had problems getting 4.0 and 5.0 to boot on the 3c509 system until I went into the configurator and disabled all of the other network devices. Disabling all unnecessary drivers seems to be a best practice when running GENERIC. Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville k.stevenson@louisville.edu PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 14:56:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 4C00037B8B5 for ; Sat, 25 Mar 2000 14:56:35 -0800 (PST) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn36.imasy.or.jp [202.227.24.228]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id HAA22589; Sun, 26 Mar 2000 07:56:26 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <200003252256.HAA22589@tasogare.imasy.or.jp> To: winter@jurai.net Cc: iwasaki@jp.FreeBSD.org, freebsd-stable@FreeBSD.ORG Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... In-Reply-To: Your message of "Wed, 22 Mar 2000 14:59:03 -0500 (EST)" References: X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 26 Mar 2000 07:56:22 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 82 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > You've totally not solved the problem. I just want to get verbose boot messages by solving `eeprom failed to come ready' and locking up problem quickly. I also don't think that's hack for true solution... BTW, thanks for your explanations and advices. I bought and install FD drive, then configure my 509B NIC with 3c5x9cfg.exe in Non-PnP mode. Now I'm able to use it on 4-stable and 5-current (but still have problems in PnP mode)! As you said, my 3c509's EEPROM seems have some corruption, that's why FreeBSD 4-stable and 5-current can't handle it while it works fine on 3-stable or Linux with no problems. With 3c5x9cfg.exe, I configured my NIC, IRQ = 10, port = 0x300, PnP enabled first, I got following boot messages and networking very slow because of IRQ (5) conflicts with my SB sound card (non-PnP ISA), I suspect. TCM5090: adding irq mask 0x9ea8 TCM5090: adding io range 0x210-0x3ef, size=0x10, align=0x10 : isa0: if_ep: <3Com 3C509-TP EtherLink III> at 0x300 in PnP mode! : ^^^ configured io-port address isa_probe_children: probing PnP devices ep0: <3Com 3C509B-TP EtherLink III (PnP)> at port 0x210-0x21f irq 5 on isa0 ^^^ not 300 ^ not 10 So I configured my NIC again with 3c5x9cfg.exe to PnP disabled then OK. Now I have a proposal. How about the restoration of traditional isa ep configuration like this? device ep0 at isa? port 0x300 irq 10 Giving configuraion hints would be useful for NIC which has corrupted EEPROM by long time usage or can conflict on resources with other devices unkown by kernel. I have 3 more boxes with 509B running on 3-stable. None of them have FD drive unfortunately, so I won't upgrade them to 4-stable. # I probably install Linux for them in the future :) This is my understanding what is happening now: > > - The PnP enumerator runs and identifies PnP devices. > - The 3c509 board is found and a device is created. sys/isa/pnp.c:pnp_identify(), pnp_isolation_protocol(), pnp_create_devices() and sys/isa/pnpparse.c:pnp_parse_resources() are doing this, and output these messages. Trying Read_Port at 243 TCM5090: adding irq mask 0x9ea8 TCM5090: adding io range 0x210-0x3ef, size=0x10, align=0x10 > - ep_isa_identify() runs and finds -the same board- and > pulls the last configured (with 3c5x9cfg.exe) settings > from the EEPROM. The board is activated. ep_isa_identify() reads settings from EEPROM and retrieves IRQ and IOPORT, then just prints this without creating device if PnP mode. isa0: if_ep: <3Com 3C509-TP EtherLink III> at 0x300 in PnP mode! > - ep_isa_probe() runs against the device created by > ep_isa_identify(). Now in PnP mode, ep_isa_probe() can't be called because the device wasn't created. > - The PnP system activates the 3c509 device that the > enumerator found and assigns it resources. sys/isa/isa_common.c:isa_probe_children(), isa_assign_resources() determine resources to allocate for the device based on struct isa_config entries created by pnp_parse_resources() (?), they aren't the same as the last configured settings from EEPROM. Unfortunately assigned IRQ conflicts with SB card which not probed by kernel. This makes networking very slow I guess. Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 15: 6: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 3D5B737B6A1 for ; Sat, 25 Mar 2000 15:05:57 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id SAA11119; Sat, 25 Mar 2000 18:05:41 -0500 (EST) Date: Sat, 25 Mar 2000 18:05:41 -0500 (EST) From: "Matthew N. Dodd" To: Mitsuru IWASAKI Cc: freebsd-stable@FreeBSD.ORG Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... In-Reply-To: <200003252256.HAA22589@tasogare.imasy.or.jp> 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, 26 Mar 2000, Mitsuru IWASAKI wrote: > BTW, thanks for your explanations and advices. I bought and install > FD drive, then configure my 509B NIC with 3c5x9cfg.exe in Non-PnP > mode. Now I'm able to use it on 4-stable and 5-current (but still > have problems in PnP mode)! As you said, my 3c509's EEPROM seems have > some corruption, that's why FreeBSD 4-stable and 5-current can't > handle it while it works fine on 3-stable or Linux with no problems. > > With 3c5x9cfg.exe, I configured my NIC, IRQ = 10, port = 0x300, PnP > enabled first, I got following boot messages and networking very slow > because of IRQ (5) conflicts with my SB sound card (non-PnP ISA), I > suspect. Do you have drivers installed for your sound card? If not then the PnP system has no way of knowing that irq 5 is used. You might also try setting irq 5 to 'legacy/ISA' in your BIOS. > TCM5090: adding irq mask 0x9ea8 > TCM5090: adding io range 0x210-0x3ef, size=0x10, align=0x10 > : > isa0: if_ep: <3Com 3C509-TP EtherLink III> at 0x300 in PnP mode! > : ^^^ configured io-port address > isa_probe_children: probing PnP devices > ep0: <3Com 3C509B-TP EtherLink III (PnP)> at port 0x210-0x21f irq 5 on isa0 > ^^^ not 300 ^ not 10 Yep, this is exactly correct. The driver is using the PnP instance which configures the card for the first available port and irq. > Now I have a proposal. How about the restoration of traditional isa > ep configuration like this? > > device ep0 at isa? port 0x300 irq 10 No, thats not the solution. If I do anything it will be to validate the EEPROM checksum in the driver 'probe' routine and bail if a board has an invalid checksum. > Giving configuraion hints would be useful for NIC which has corrupted > EEPROM by long time usage or can conflict on resources with other > devices unkown by kernel. I have 3 more boxes with 509B running on > 3-stable. None of them have FD drive unfortunately, so I won't > upgrade them to 4-stable. > > # I probably install Linux for them in the future :) Go for it. Their 3c509 support is worse than ours. > This is my understanding what is happening now: > > > > - The PnP enumerator runs and identifies PnP devices. > > - The 3c509 board is found and a device is created. > > sys/isa/pnp.c:pnp_identify(), pnp_isolation_protocol(), > pnp_create_devices() and sys/isa/pnpparse.c:pnp_parse_resources() are > doing this, and output these messages. > > Trying Read_Port at 243 > TCM5090: adding irq mask 0x9ea8 > TCM5090: adding io range 0x210-0x3ef, size=0x10, align=0x10 > > > - ep_isa_identify() runs and finds -the same board- and > > pulls the last configured (with 3c5x9cfg.exe) settings > > from the EEPROM. The board is activated. > > ep_isa_identify() reads settings from EEPROM and retrieves IRQ and IOPORT, > then just prints this without creating device if PnP mode. > > isa0: if_ep: <3Com 3C509-TP EtherLink III> at 0x300 in PnP mode! But it wasn't printing this message earlier! It sounds like everything works as it is supposed to after you ran the 3C5X9CFG.EXE util. > > - ep_isa_probe() runs against the device created by > > ep_isa_identify(). > > Now in PnP mode, ep_isa_probe() can't be called because the device > wasn't created. But it was created before when the card was in PnP mode but not reporting it via the EEPROM. > > - The PnP system activates the 3c509 device that the > > enumerator found and assigns it resources. > > sys/isa/isa_common.c:isa_probe_children(), isa_assign_resources() > determine resources to allocate for the device based on struct > isa_config entries created by pnp_parse_resources() (?), they aren't > the same as the last configured settings from EEPROM. Unfortunately > assigned IRQ conflicts with SB card which not probed by kernel. > This makes networking very slow I guess. No, the resources that are in the EEPROM and the resources PnP activated boards use are totally different. The settings in the EEPROM are actually just 'hints'; I could make the driver override them and use whatever I want. Until the adapter is 'activated' to a specific configuration it has no IRQ/port. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 15:46:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 1BF0037B8E7 for ; Sat, 25 Mar 2000 15:46:16 -0800 (PST) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn36.imasy.or.jp [202.227.24.228]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id IAA26624; Sun, 26 Mar 2000 08:46:13 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <200003252346.IAA26624@tasogare.imasy.or.jp> To: winter@jurai.net Cc: iwasaki@jp.FreeBSD.org, freebsd-stable@FreeBSD.ORG Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... In-Reply-To: Your message of "Sat, 25 Mar 2000 18:05:41 -0500 (EST)" References: X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 26 Mar 2000 08:46:12 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 27 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, # As always, your response is too fast :-) I almost agree with you, but one thing; > Do you have drivers installed for your sound card? If not then the PnP > system has no way of knowing that irq 5 is used. You might also try How about installation process? Currently our kernel in installer doesn't have sound card drivers, that mean we probably unable to use ep during installation on such box. In this case, only user knows actual configuraion and tell it to kernel by UserConfig, but the PnP system doesn't. > setting irq 5 to 'legacy/ISA' in your BIOS. Of course I set it in BIOS already. > > # I probably install Linux for them in the future :) > > Go for it. Their 3c509 support is worse than ours. I know, just kidding :-) The ep driver have become elegant by your efforts. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 16:33:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.hcisp.net (Stargate.hcisp.net [208.60.89.18]) by hub.freebsd.org (Postfix) with SMTP id D22FC37B8E7 for ; Sat, 25 Mar 2000 16:33:51 -0800 (PST) (envelope-from tim@mysql.com) Received: (qmail 17868 invoked from network); 26 Mar 2000 00:39:57 -0000 Received: from modem2.hcsip.net (HELO threads.polyesthetic.msg) (208.60.89.68) by stargate.hcisp.net with SMTP; 26 Mar 2000 00:39:57 -0000 Received: (qmail 38659 invoked by uid 1001); 25 Mar 2000 00:16:02 -0000 From: "Thimble Smith" Date: Fri, 24 Mar 2000 19:16:02 -0500 To: Daniel Eischen Cc: freebsd-stable@FreeBSD.ORG Subject: Re: pthread_kill() not killing thread Message-ID: <20000324191602.A38647@threads.polyesthetic.msg> References: <200003242307.SAA08054@pcnet1.pcnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003242307.SAA08054@pcnet1.pcnet.com>; from eischen@vigrid.com on Fri, Mar 24, 2000 at 06:07:30PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 24, 2000 at 06:07:30PM -0500, Daniel Eischen wrote: >My "interpretation" of the POSIX spec was that intra-process signals >sent via pthread_kill() were treated differently than if the signal was >sent to the process. I'll have to go back and re-read the POSIX spec -- >perhaps I misunderstood it. > >At any rate, FreeBSDs threads implementation of pthread_kill() will >not have the same effect as kill(2) -- the process will not be terminated >by issuing a pthread_kill(thrd, SIGTERM) to a thread. Signals sent >to threads via pthread_kill will invoke a signal handler if it is >installed and will interrupt the thread from its current operation >(returning -1 with EINTR). This all assumes that the thread isn't >masking the signal, and that the handler isn't installed with SA_RESTART. OK. Thanks. What I'm really trying to do is figure out why MySQL will hang if you try to shut it down when there is a connection open to it. You then have to kill the mysqld process with -9 in order to get rid of it. :( There's a program in the source distribution that tests the thread signal handling: mysys/test_thr_alarm. It hangs in a similar way. I'm trying to figure out why. So, if anybody knows threads well and also has MySQL on their box, and feels like checking it out, I'd be happy. I'm sure I'll figure it out eventually (and it'll be worth it to learn more about threads), but if anybody can do it in a few seconds I'd appreciate it. Tim -- Tim Smith < tim@mysql.com > :MySQL Development Team: Boone, NC USA. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 16:43:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 5183837B8E7 for ; Sat, 25 Mar 2000 16:43:27 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id TAA11929; Sat, 25 Mar 2000 19:43:22 -0500 (EST) Date: Sat, 25 Mar 2000 19:43:22 -0500 (EST) From: "Matthew N. Dodd" To: Mitsuru IWASAKI Cc: freebsd-stable@FreeBSD.ORG Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... In-Reply-To: <200003252346.IAA26624@tasogare.imasy.or.jp> 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, 26 Mar 2000, Mitsuru IWASAKI wrote: > How about installation process? Currently our kernel in installer > doesn't have sound card drivers, that mean we probably unable to use > ep during installation on such box. In this case, only user knows > actual configuraion and tell it to kernel by UserConfig, but the PnP > system doesn't. Ah. So what we really want is some mechanism to tell the kernel 'hey, you! don't use this ioport/irq whatever.' (or otherwise mark some resources as not being available to PnP devices.) > > Go for it. Their 3c509 support is worse than ours. > > I know, just kidding :-) The ep driver have become elegant by your > efforts. I'm pretty close to a solution for the 'ie' driver and the 'ex' driver already shares the honor of not using implicit kernel settings to configure cards; if I have my way, very few boards will have user configurable settings. Driver specific workarounds aren't going to cut it so we'll have to figure out how to do the above at some point. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 16:47:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.westbend.net (ns1.westbend.net [209.224.254.131]) by hub.freebsd.org (Postfix) with ESMTP id 3C47F37B94B for ; Sat, 25 Mar 2000 16:47:16 -0800 (PST) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [209.224.254.141]) by mail.westbend.net (8.9.3/8.9.3) with SMTP id SAA57332; Sat, 25 Mar 2000 18:47:07 -0600 (CST) (envelope-from hetzels@westbend.net) Message-ID: <013401bf96bc$cfa9e820$8dfee0d1@westbend.net> From: "Scot W. Hetzel" To: "Mitsuru IWASAKI" Cc: References: <200003252256.HAA22589@tasogare.imasy.or.jp> Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... Date: Sat, 25 Mar 2000 18:47:06 -0600 Organization: West Bend Internet MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.3825.400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.3825.400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "Mitsuru IWASAKI" > With 3c5x9cfg.exe, I configured my NIC, IRQ = 10, port = 0x300, PnP > enabled first, I got following boot messages and networking very slow > because of IRQ (5) conflicts with my SB sound card (non-PnP ISA), I > suspect. > > > Giving configuraion hints would be useful for NIC which has corrupted > EEPROM by long time usage or can conflict on resources with other > devices unkown by kernel. I have 3 more boxes with 509B running on > 3-stable. None of them have FD drive unfortunately, so I won't > upgrade them to 4-stable. > # I probably install Linux for them in the future :) > I don't know if this will work, but you could try executing 3c5x9cfg.exe with the doscmd program on those other 3 systems. SYNOPSIS doscmd -23AbDEfHIMOPRrtVvXxYz -c file -d file -i port[:cnt] -o port[:cnt] -S int -U int [cmd [args ...]] DESCRIPTION Doscmd can either emulate a subset of DOS and run the single command cmd args, or it can be used to emulate a PC and boot DOS, which allows it to run a larger variety of DOS applications. It should be noted that MS DOS 6.2 and higher appear to cause difficulties for doscmd. To boot DOS, either provide the -b flag or omit the cmd argument. If -b is specified, cmd and args are ignored. Another alternative is swap cards between systems: 1. pull the working card out of the system with the floppy drive 2. put it into one of the other systems. 3. put the other systems card into the system with the floppy drive 4. re-configure the card with 3c5x9cfg.exe 5. repeat step 1-4 until all cards are re-configured. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 16:52:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 1C66237B9AB for ; Sat, 25 Mar 2000 16:52:26 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id TAA11986; Sat, 25 Mar 2000 19:52:20 -0500 (EST) Date: Sat, 25 Mar 2000 19:52:20 -0500 (EST) From: "Matthew N. Dodd" To: "Scot W. Hetzel" Cc: Mitsuru IWASAKI , freebsd-stable@FreeBSD.ORG Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... In-Reply-To: <013401bf96bc$cfa9e820$8dfee0d1@westbend.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 Sat, 25 Mar 2000, Scot W. Hetzel wrote: > I don't know if this will work, but you could try executing > 3c5x9cfg.exe with the doscmd program on those other 3 systems. I find its useful to always create a 10-15 meg DOS partition on all my machines. That way I can keep copies of hardware config utils etc (or more commonly EISA config stuff). You can mount the stuff up in FreeBSD to add/delete things from the DOS partition. The 'doscmd' solution might work but you'd have to run it with the right flags to allow it access to the real IO ports. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 16:54:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wally.bellnetworks.net (www.bellnetworks.net [216.214.153.70]) by hub.freebsd.org (Postfix) with ESMTP id 4BFFC37B7B2 for ; Sat, 25 Mar 2000 16:54:26 -0800 (PST) (envelope-from jerry@bellnetworks.net) Received: from itbell (dhcp-247.bellnetworks.net [208.177.187.247]) by wally.bellnetworks.net (8.9.3/8.9.3) with SMTP id TAA68911 for ; Sat, 25 Mar 2000 19:54:22 -0500 (EST) (envelope-from jerry@bellnetworks.net) Message-ID: <00b401bf9659$1d965370$f7bbb1d0@netrex.com> From: "Jerry Bell" To: Subject: ps, w, top and netstat problem Date: Sat, 25 Mar 2000 07:53:27 -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.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I recently ran a make world and kernel rebuild on a 4.0 RELEASE installation (After cvsupping the latest RELENG_4 sources). After the rebuild I get this: dogbert# w 7:50PM up 1 day, 10:57, 0 users, load averages: 0.00, 0.00, 0.00 USER TTY FROM LOGIN@ IDLE WHAT w: proc size mismatch (32364 total, 1056 chunks): Undefined error: 0 dogbert# ps -x ps: proc size mismatch (24012 total, 1056 chunks) dogbert# top kvm_open: proc size mismatch (32364 total, 1056 chunks) top: Out of memory. dogbert# netstat -a dogbert# dogbert# uname -a FreeBSD dogbert.bellnetworks.net 4.0-STABLE FreeBSD 4.0-STABLE #0: Fri Mar 24 12:44:30 GMT 2000 jerry@dogbert.bellnetworks.net:/usr/src/sys/compile/GENERIC i386 Can anyone point me in the right direction to get this fixed? Thank you! Jerry Bell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 17:12:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D457237B51B for ; Sat, 25 Mar 2000 17:12:24 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA47347; Sat, 25 Mar 2000 18:12:18 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA76635; Sat, 25 Mar 2000 18:12:07 -0700 (MST) Message-Id: <200003260112.SAA76635@harmony.village.org> To: "Matthew N. Dodd" Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... Cc: Mitsuru IWASAKI , freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Sat, 25 Mar 2000 19:43:22 EST." References: Date: Sat, 25 Mar 2000 18:12:07 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Matthew N. Dodd" writes: : Ah. So what we really want is some mechanism to tell the kernel 'hey, : you! don't use this ioport/irq whatever.' (or otherwise mark some : resources as not being available to PnP devices.) I think that a null driver could easily be written. I also think that combined with the hint mechanism I posted to new-bus a couple of days ago this could be a viable way to reserve interrupts from the boot loader. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 17:50:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id F196137B97E for ; Sat, 25 Mar 2000 17:50:06 -0800 (PST) (envelope-from jim@nasby.net) Received: from nasby.net (sysnasby@2.nasby.dsl.enteract.com [216.80.51.18]) by mail.enteract.com (8.9.3/8.9.3) with ESMTP id TAA47952; Sat, 25 Mar 2000 19:50:05 -0600 (CST) (envelope-from jim@nasby.net) Message-ID: <38DD6CCB.A9B05C05@nasby.net> Date: Sat, 25 Mar 2000 19:50:03 -0600 From: "Jim C. Nasby" Organization: distributed.net X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en-US,en MIME-Version: 1.0 To: Jerry Bell Cc: stable@freebsd.org Subject: Re: ps, w, top and netstat problem References: <00b401bf9659$1d965370$f7bbb1d0@netrex.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It looks like you're not running a rebuilt kernel... I suggest you try recompiling your kernel again (do a config -r just to be safe). If you still have problems, try a cd /dev && sh MAKEDEV all, but this doesn't look to be permissions problems (which MAKEDEV all will fix). Jerry Bell wrote: > > Hello, > > I recently ran a make world and kernel rebuild on a 4.0 RELEASE installation > (After cvsupping the latest RELENG_4 sources). > > After the rebuild I get this: > > dogbert# w > 7:50PM up 1 day, 10:57, 0 users, load averages: 0.00, 0.00, 0.00 > USER TTY FROM LOGIN@ IDLE WHAT > w: proc size mismatch (32364 total, 1056 chunks): Undefined error: 0 > dogbert# ps -x > ps: proc size mismatch (24012 total, 1056 chunks) > dogbert# top > kvm_open: proc size mismatch (32364 total, 1056 chunks) > top: Out of memory. > dogbert# netstat -a > dogbert# > dogbert# uname -a > FreeBSD dogbert.bellnetworks.net 4.0-STABLE FreeBSD 4.0-STABLE #0: Fri Mar > 24 12:44:30 GMT 2000 > jerry@dogbert.bellnetworks.net:/usr/src/sys/compile/GENERIC i386 > > Can anyone point me in the right direction to get this fixed? > > Thank you! > > Jerry Bell > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- 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 Sat Mar 25 18:26:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wally.bellnetworks.net (www.bellnetworks.net [216.214.153.70]) by hub.freebsd.org (Postfix) with ESMTP id 6061437B8FD for ; Sat, 25 Mar 2000 18:26:53 -0800 (PST) (envelope-from jerry@bellnetworks.net) Received: from itbell (dhcp-247.bellnetworks.net [208.177.187.247]) by wally.bellnetworks.net (8.9.3/8.9.3) with SMTP id VAA77428; Sat, 25 Mar 2000 21:26:23 -0500 (EST) (envelope-from jerry@bellnetworks.net) Message-ID: <00ec01bf9665$f5399c40$f7bbb1d0@netrex.com> From: "Jerry Bell" To: "Jim C. Nasby" Cc: References: <00b401bf9659$1d965370$f7bbb1d0@netrex.com> <38DD6CCB.A9B05C05@nasby.net> Subject: Re: ps, w, top and netstat problem Date: Sat, 25 Mar 2000 09:25:23 -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.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, I am running a rebuilt kernel. For sanity's sake, I just rebuilt it again, with the config -r, and run MAKEDEV all (copied from /usr/src/etc). Anyway, I'm still having the same problem. Thanks for the help! Jerry ----- Original Message ----- From: Jim C. Nasby To: Jerry Bell Cc: Sent: Saturday, March 25, 2000 8:50 PM Subject: Re: ps, w, top and netstat problem > It looks like you're not running a rebuilt kernel... I suggest you try > recompiling your kernel again (do a config -r just to be safe). > > If you still have problems, try a cd /dev && sh MAKEDEV all, but this > doesn't look to be permissions problems (which MAKEDEV all will fix). > > Jerry Bell wrote: > > > > Hello, > > > > I recently ran a make world and kernel rebuild on a 4.0 RELEASE installation > > (After cvsupping the latest RELENG_4 sources). > > > > After the rebuild I get this: > > > > dogbert# w > > 7:50PM up 1 day, 10:57, 0 users, load averages: 0.00, 0.00, 0.00 > > USER TTY FROM LOGIN@ IDLE WHAT > > w: proc size mismatch (32364 total, 1056 chunks): Undefined error: 0 > > dogbert# ps -x > > ps: proc size mismatch (24012 total, 1056 chunks) > > dogbert# top > > kvm_open: proc size mismatch (32364 total, 1056 chunks) > > top: Out of memory. > > dogbert# netstat -a > > dogbert# > > dogbert# uname -a > > FreeBSD dogbert.bellnetworks.net 4.0-STABLE FreeBSD 4.0-STABLE #0: Fri Mar > > 24 12:44:30 GMT 2000 > > jerry@dogbert.bellnetworks.net:/usr/src/sys/compile/GENERIC i386 > > > > Can anyone point me in the right direction to get this fixed? > > > > Thank you! > > > > Jerry Bell > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > -- > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 19:19:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from nautilus.shore.net (nautilus.shore.net [207.244.124.104]) by hub.freebsd.org (Postfix) with ESMTP id C288337B594 for ; Sat, 25 Mar 2000 19:19:19 -0800 (PST) (envelope-from tjlegg@shore.net) Received: from eskimos.the-eleven.com [207.244.92.51] by nautilus.shore.net with esmtp (Exim) for freebsd-stable@freebsd.org id 12Z3a9-0003nt-00; Sat, 25 Mar 2000 22:19:17 -0500 Mime-Version: 1.0 X-Sender: tjlegg@shell2.shore.net Message-Id: Date: Sat, 25 Mar 2000 22:19:05 -0500 To: freebsd-stable@freebsd.org From: Tom Legg Subject: Minor rc.network bug for 4.0 and ipfw Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't want to file a bug report for this until I can hear some discussion about the direction of ipfw. (is FreeBSD moving towards a system that prefers loading modules like ipfw for machines that might prefer denying all lkm?) The current situation creates a potential problem for 4.0 admins (at least I didn't notice it until I upgraded to the 4.0 kernel) If you compile a kernel with ipfw in the kernel but do nothing to modify /etc/defaults/rc.conf and boot, net.inet.ip.fw.enable is set to 1 and since the defaults for enable is NO, no further action is done upon the firewall scripts. Since the current /etc/rc.network only seems to check for firewall_enable="yes", it doesn't seem to reverse the default (which is enable=1) and at the same time doesn't read any of the options about what type of firewall the user would like. I've written a test patch for /etc/rc.network that checks for the case firewall_enable="no" and set net.inet.ip.fw.enable to 0. (note: this has to go at least before the dhcp client invocation *grin*) But something seems wrong about doing a check during a boot to reset the sysctl value to the "default". I would think a better approach would be to keep the kernel code with enable=0 and then let /etc/rc.network load the kernel modules if necessary and enable the firewall if firewall_enable="yes". -- ----- Tom Legg tjlegg@shore.net http://www.shore.net/~tjlegg/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 19:45:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id C173437B8AD for ; Sat, 25 Mar 2000 19:45:25 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id TAA08244; Sat, 25 Mar 2000 19:45:13 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38DD87C8.8D8FC976@gorean.org> Date: Sat, 25 Mar 2000 19:45:12 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0322 i386) X-Accept-Language: en MIME-Version: 1.0 To: Tom Legg Cc: freebsd-stable@freebsd.org Subject: Re: Minor rc.network bug for 4.0 and ipfw References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom Legg wrote: > The current situation creates a potential problem for 4.0 admins (at > least I didn't notice it until I upgraded to the 4.0 kernel) This situation hasn't changed. It's always been this way. > If you compile a kernel with ipfw in the kernel but do nothing to > modify /etc/defaults/rc.conf and boot, net.inet.ip.fw.enable is set > to 1 and since the defaults for enable is NO, no further action is > done upon the firewall scripts. The theory is that a sysadmin who is enabling these options will have read the documentation and done what he can to properly prepare. For those who are concerned about foot shooting, the "default to accept" kernel option is available. If you're really needing a secure firewall, it's more important that it is secure from boot, with or without the ability to read the rc scripts. If you don't need that level of security, other options are available to you. Good luck, Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 20: 7: 5 2000 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 54F1137B717 for ; Sat, 25 Mar 2000 20:07:01 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id VAA04621; Sat, 25 Mar 2000 21:06:57 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200003260406.VAA04621@freeway.dcfinc.com> Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... In-Reply-To: from "Matthew N. Dodd" at "Mar 25, 0 07:43:22 pm" To: winter@jurai.net (Matthew N. Dodd) Date: Sat, 25 Mar 2000 21:06:57 -0700 (MST) Cc: stable@FreeBSD.org Reply-To: chad@DCFinc.com 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, Matthew N. Dodd wrote: > I'm pretty close to a solution for the 'ie' driver and the 'ex' > driver already shares the honor of not using implicit kernel > settings to configure cards; if I have my way, very few boards will > have user configurable settings. Driver specific workarounds aren't > going to cut it so we'll have to figure out how to do the above at > some point. This makes me wary. One of the reasons I like UNIX is the assumptions implicit in its organization that the users might actually know what they're doing. Every time Microsoft and the PC industry have tried to remove the responsibility and control from the users (EISA--no jumpers, Plug-n-Pray--no config program), they've generally made things worse. C'mon. How many of you have had a sound card magically decide to move back to its old home, right on top of your new Ethernet NIC? Raise your hands. And how long did it take for you to figure it out? How many boards did you pull, and then re-insert (rebooting each time) to see what makes the NIC run again? How many of you have purchased a shiny new NIC, and then had to go find a DOS machine you could open up so you could find out how the card was configured? I mean, if all that stuff would work as intended, it would be a free ride. But in the real world, it doesn't. The specifications are poorly published, not definitive, and sometimes partially ignored by the manufacturers. And you're left with no way to determine what went wrong, or to fix it if you do figure it out. I liked it best when the boards had jumpers and wouldn't move around in the I/O space unless I told them to. And I didn't have to keep a bootable DOS around somewhere just so I could "configure" the boards. And some stray, random panic or mis-behaved program couldn't scramble your machine's organization. Bah! This, to me, isn't progress. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net 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 Sat Mar 25 20: 8:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from polaris.shore.net (polaris.shore.net [207.244.124.105]) by hub.freebsd.org (Postfix) with ESMTP id 8055537B83A for ; Sat, 25 Mar 2000 20:08:45 -0800 (PST) (envelope-from tjlegg@shore.net) Received: from eskimos.the-eleven.com [207.244.92.51] by polaris.shore.net with esmtp (Exim) id 12Z4Ly-0002N2-00; Sat, 25 Mar 2000 23:08:42 -0500 Mime-Version: 1.0 X-Sender: tjlegg@shell2.shore.net Message-Id: In-Reply-To: <38DD87C8.8D8FC976@gorean.org> References: <38DD87C8.8D8FC976@gorean.org> Date: Sat, 25 Mar 2000 23:08:29 -0500 To: Doug Barton From: Tom Legg Subject: Re: Minor rc.network bug for 4.0 and ipfw Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 7:45 PM -0800 3/25/2000, Doug Barton wrote: >Tom Legg wrote: > >> The current situation creates a potential problem for 4.0 admins (at >> least I didn't notice it until I upgraded to the 4.0 kernel) > > This situation hasn't changed. It's always been this way. > >> If you compile a kernel with ipfw in the kernel but do nothing to >> modify /etc/defaults/rc.conf and boot, net.inet.ip.fw.enable is set >> to 1 and since the defaults for enable is NO, no further action is >> done upon the firewall scripts. > > The theory is that a sysadmin who is enabling these options will have >read the documentation and done what he can to properly prepare. For >those who are concerned about foot shooting, the "default to accept" >kernel option is available. > > If you're really needing a secure firewall, it's more important that it >is secure from boot, with or without the ability to read the rc scripts. >If you don't need that level of security, other options are available to >you. No problems here really. But it does seem to be really silly then to have a default rc.conf firewall_enable flag set to "NO" when the kernel flag default when compiled in is set to "YES". In fact the current situation renders the rc.conf flag for firewall_enable mute. You might as well eliminate the flag and have /etc/rc.network check whether net.inet.ip.fw.enable=1 and go from there. -- ----- Tom Legg tjlegg@shore.net http://www.shore.net/~tjlegg/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 20:14: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 5176D37B879 for ; Sat, 25 Mar 2000 20:13:52 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id UAA08293; Sat, 25 Mar 2000 20:13:47 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38DD8E7B.CA0781BD@gorean.org> Date: Sat, 25 Mar 2000 20:13:47 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0322 i386) X-Accept-Language: en MIME-Version: 1.0 To: Tom Legg Cc: freebsd-stable@freebsd.org Subject: Re: Minor rc.network bug for 4.0 and ipfw References: <38DD87C8.8D8FC976@gorean.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom Legg wrote: > In fact the current situation renders the rc.conf flag for > firewall_enable mute. You might as well eliminate the flag and have > /etc/rc.network check whether net.inet.ip.fw.enable=1 and go from > there. I think you mean moot. :) In any case, the current set of options allows a user to specify the settings in rc.conf without compiling the ipfw stuff into the kernel. Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 20:24:36 2000 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 A541E37B943 for ; Sat, 25 Mar 2000 20:24:25 -0800 (PST) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id XAA35600; Sat, 25 Mar 2000 23:24:26 -0500 (EST) (envelope-from bandix@looksharp.net) Date: Sat, 25 Mar 2000 23:24:26 -0500 (EST) From: "Brandon D. Valentine" To: Doug Barton Cc: Tom Legg , freebsd-stable@FreeBSD.ORG Subject: Re: Minor rc.network bug for 4.0 and ipfw In-Reply-To: <38DD8E7B.CA0781BD@gorean.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 Sat, 25 Mar 2000, Doug Barton wrote: >Tom Legg wrote: > >> In fact the current situation renders the rc.conf flag for >> firewall_enable mute. You might as well eliminate the flag and have >> /etc/rc.network check whether net.inet.ip.fw.enable=1 and go from >> there. > > I think you mean moot. :) In any case, the current set of options >allows a user to specify the settings in rc.conf without compiling the >ipfw stuff into the kernel. > >Doug No, actually mute is appropriate. firewall_enable is not allowed to express itself if ipfw is compiled in. Even when firewall_enable is explicitly set to "NO", as it is in /etc/defaults/rc.conf, it's voice is not heard and net.inet.ip.fw.enable is set true. Not saying anything about the merits of either default setup, just that mute is an appropriate adjective. ------------------------------------------------------------- | -Brandon D. Valentine bandix at looksharp.net | bandix on EFnet IRC BVRiker on AIM ------------------------------------------------------------- | "...and as for hackers, we note that all of those known to | The Register are so strapped financially that seizing their | property would be tantamount to squeezing blood from a | stone." -- The Register, 02/17/2000 ------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 20:29: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0CF2637B594 for ; Sat, 25 Mar 2000 20:29:03 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA47726; Sat, 25 Mar 2000 21:29:01 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA77635; Sat, 25 Mar 2000 21:28:49 -0700 (MST) Message-Id: <200003260428.VAA77635@harmony.village.org> To: chad@DCFinc.com Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... Cc: winter@jurai.net (Matthew N. Dodd), stable@FreeBSD.ORG In-reply-to: Your message of "Sat, 25 Mar 2000 21:06:57 MST." <200003260406.VAA04621@freeway.dcfinc.com> References: <200003260406.VAA04621@freeway.dcfinc.com> Date: Sat, 25 Mar 2000 21:28:49 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003260406.VAA04621@freeway.dcfinc.com> "Chad R. Larson" writes: : Every time Microsoft and the PC industry have tried to remove the : responsibility and control from the users (EISA--no jumpers, : Plug-n-Pray--no config program), they've generally made things worse. So you're saying that pci was a bad idea? : each time) to see what makes the NIC run again? How many of you : have purchased a shiny new NIC, and then had to go find a DOS : machine you could open up so you could find out how the card was : configured? None since I started buying pci nic cards :-). : Bah! This, to me, isn't progress. Yes. All those nasty problems with PCI cards sure isn't progress :-) Joking aside. To be honest, I've had fewer problems with the ISA Plug and Play cards as more and more of the drivers have been converted to grok PnP. I've had to properly configure the PnP BIOS settings when I've mixed non-PnP and PnP cards. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 20:30: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id AAFEE37B99C for ; Sat, 25 Mar 2000 20:29:52 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id XAA13938; Sat, 25 Mar 2000 23:29:49 -0500 (EST) Date: Sat, 25 Mar 2000 23:29:49 -0500 (EST) From: "Matthew N. Dodd" To: "Chad R. Larson" Cc: stable@FreeBSD.org Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... In-Reply-To: <200003260406.VAA04621@freeway.dcfinc.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 Sat, 25 Mar 2000, Chad R. Larson wrote: > This makes me wary. One of the reasons I like UNIX is the assumptions > implicit in its organization that the users might actually know what > they're doing. This has nothing to do with UNIX. This has everything to do with being able to determine card config without user intervention. If I can give the driver the ability to detect the board and retreive its config with 100% accuracy then thats a far better solution than trusting the user to remember the settings and properly communicate them to the kernel. > Every time Microsoft and the PC industry have tried to remove the > responsibility and control from the users (EISA--no jumpers, > Plug-n-Pray--no config program), they've generally made things worse. PnP works fine for me. EISA works fine for me. The PeeCee industry didn't do such a bad job on PCI, which not surprisingly, works fine for me. If you want to fiddle around with your hardware and feel 'in control', feel free to play with old VAXen and QBUS or something. My goal is to reduce support load by taking advantage of the features of the hardware that permit the kernel/drivers to 'do the right thing'. > C'mon. How many of you have had a sound card magically decide to move > back to its old home, right on top of your new Ethernet NIC? Raise > your hands. And how long did it take for you to figure it out? How > many boards did you pull, and then re-insert (rebooting each time) to > see what makes the NIC run again? How many of you have purchased a > shiny new NIC, and then had to go find a DOS machine you could open up > so you could find out how the card was configured? I'm not advocating that drivers 'guess' what config the card has. If you pull your average 3c509 and drop it in a CURRENT box, the driver -will- find the current config. It will even use that config if nothing else is conflicting. The ability to manually provide 'hints' isn't going to alter the config of the card. If you go slapping new hardware in a box without making sure its set to non-conflicting resources then you get what you deserve. Hints aren't gonna fix that problem either. If you've got totally broken hardware that doesn't stay where you tell it then you're pretty much fucked, and hints aren't gonna fix your problem. > I mean, if all that stuff would work as intended, it would be a free > ride. But in the real world, it doesn't. The specifications are > poorly published, not definitive, and sometimes partially ignored by > the manufacturers. And you're left with no way to determine what went > wrong, or to fix it if you do figure it out. Again, I'm not coding the drivers to guess wildly. I'm modifying only the drivers for the hardware which I'm able to perform accurate enumeration and resource identification on. > I liked it best when the boards had jumpers and wouldn't move around > in the I/O space unless I told them to. And I didn't have to keep a > bootable DOS around somewhere just so I could "configure" the boards. > And some stray, random panic or mis-behaved program couldn't scramble > your machine's organization. So how exactly does the ability to provide manual 'hints' to the driver help you? Just because you tell the kernel 'hey, I think that there should be a 3c509 at port 0x300, irq 5.' doesn't mean that the driver is gonna magically reconfigure the board for you. (though I suspect I could make it do that, but still.) If you're gonna use non PnP hardware, or hardware which requires software setup then you're gonna have to contend with booting DOS to configure that hardware. I reccomend putting a 10-15 meg partition on all systems anyway. If you don't like this idea, then replace all your ISA hardware with PCI. The PeeCee is tied to DOS even though thats fairly distasteful to use Unix people. Feel free to write a unix based config util for the 3c509 or other boards which you use that require software setup. Until then, you're stuck with DOS. (And at least you're not trying to use ISA boards with an Alpha) > Bah! This, to me, isn't progress. Sure it is. You're just venting about it and don't really have a clear idea what you object to. :) And if you think EISA got your goat you should try MCA (which thankfully doesn't suffer from having ISA slots to contend with.) -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 20:31:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 9703337B986 for ; Sat, 25 Mar 2000 20:31:47 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id XAA13960; Sat, 25 Mar 2000 23:31:43 -0500 (EST) Date: Sat, 25 Mar 2000 23:31:42 -0500 (EST) From: "Matthew N. Dodd" To: Ted Spradley Cc: chad@DCFinc.com, stable@FreeBSD.ORG Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... In-Reply-To: <200003260424.WAA52534@set.spradley.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 Sat, 25 Mar 2000, Ted Spradley wrote: > > Bah! This, to me, isn't progress. > > Amen, brother! Right on! Its good to know that more than one person isn't able to understand the issues here. :) -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 20:34:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from polaris.shore.net (polaris.shore.net [207.244.124.105]) by hub.freebsd.org (Postfix) with ESMTP id DBF0037B8ED for ; Sat, 25 Mar 2000 20:34:42 -0800 (PST) (envelope-from tjlegg@shore.net) Received: from eskimos.the-eleven.com [207.244.92.51] by polaris.shore.net with esmtp (Exim) id 12Z4l6-0004f7-00; Sat, 25 Mar 2000 23:34:40 -0500 Mime-Version: 1.0 X-Sender: tjlegg@shell2.shore.net Message-Id: In-Reply-To: <38DD8E7B.CA0781BD@gorean.org> References: <38DD87C8.8D8FC976@gorean.org> <38DD8E7B.CA0781BD@gorean.org> Date: Sat, 25 Mar 2000 23:34:27 -0500 To: Doug Barton From: Tom Legg Subject: Re: Minor rc.network bug for 4.0 and ipfw Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 8:13 PM -0800 3/25/2000, Doug Barton wrote: >Tom Legg wrote: > >> In fact the current situation renders the rc.conf flag for >> firewall_enable mute. You might as well eliminate the flag and have >> /etc/rc.network check whether net.inet.ip.fw.enable=1 and go from >> there. > > I think you mean moot. :) In any case, the current set of options >allows a user to specify the settings in rc.conf without compiling the >ipfw stuff into the kernel. > >Doug I'm SHIRLEY not arguing against allowing the rc scripts loading the kernel modules if firewall_enable="YES". All I'm saying is that an admin that is sophisticated enough to compile a custom kernel with IPFW is also sophisticated enough to change the rc flag to "YES" when they want the firewall enabled. But I "pity the foo" that has to come and adminster a system where firewall_enable="NO" in boot up does not mean net.inet.ip.fw.enable=0 . when 0=1 even us poor luser FreeBSD admin wannabes get confused (how the h*ll can we blue screen for division by 0 if 0=1?) -- ----- Tom Legg tjlegg@shore.net http://www.shore.net/~tjlegg/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 20:39:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id C1E2237B652 for ; Sat, 25 Mar 2000 20:39:45 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id UAA08364; Sat, 25 Mar 2000 20:39:43 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38DD948F.D6735548@gorean.org> Date: Sat, 25 Mar 2000 20:39:43 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0322 i386) X-Accept-Language: en MIME-Version: 1.0 To: Tom Legg Cc: freebsd-stable@freebsd.org Subject: Re: Minor rc.network bug for 4.0 and ipfw References: <38DD87C8.8D8FC976@gorean.org> <38DD8E7B.CA0781BD@gorean.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom Legg wrote: > All I'm saying is that an admin that is sophisticated enough to > compile a custom kernel with IPFW is also sophisticated enough to > change the rc flag to "YES" when they want the firewall enabled. But > I "pity the foo" that has to come and adminster a system where > firewall_enable="NO" in boot up does not mean net.inet.ip.fw.enable=0 Yes, this has been argued ad infinitum. Check the mail archives if you're interested. What it boils down to is, we like it the way it is, and we expect people who load the gun to read how not to shoot their foot with it. Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 20:49: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from web214.mail.yahoo.com (web214.mail.yahoo.com [128.11.68.114]) by hub.freebsd.org (Postfix) with SMTP id EB5F537B507 for ; Sat, 25 Mar 2000 20:49:03 -0800 (PST) (envelope-from ianjhart@yahoo.com) Received: (qmail 4765 invoked by uid 60001); 26 Mar 2000 04:49:03 -0000 Message-ID: <20000326044903.4764.qmail@web214.mail.yahoo.com> Received: from [212.139.131.132] by web214.mail.yahoo.com; Sat, 25 Mar 2000 20:49:03 PST Date: Sat, 25 Mar 2000 20:49:03 -0800 (PST) From: Ian Hart Subject: Re: tun0 lost in 4.0 To: stable@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 Walter Brameld wrote: > > On Sun, 19 Mar 2000, in a never-ending search for enlightenment, Sergei Vyshenski wrote: > > Can not revive tun0 interface after moving to 4.0 from 3.4 > > in a way that src/UPDATING teaches. > > > > Kernel file has "pseudo-device tun 1", kernel builds ok; > > ./MAKEDEV tun0 in /dev does not complain; > > bbut ifconfig says: "interface tun0 does not exist" > > > > Actually, I need tun0 to accept incoming user-ppp, > > and would be happy to hear of workaround at least. > > > > Thank you in advance. > > Sergei > > Believe it should only be "pseudo-device tun" with no "1". > > -- > Walter Brameld Sergei, did you fix your problem? A bit late on this thread I know. The reason being - no modem for over a week. When I ran ppp and went to terminal mode there was no response at all from the modem. I was running 4.0-STABLE. Was A1 under 3.4-STABLE. I managed to get online (very) early Saturday morning to cvsup. Sometime during the power down/make world/reading of 500+ emails it broke again. It's currently working (obviously), but I'm too paranoid to do anything in case I break it again. I have set pseudo-device tun 1, contrary to GENERIC setting. The modem is a no-name (ORIGO) 56k6 Rockwell Voice, ISA with jumpers, set to COM 4 IRQ 9. Tried in the two machines I have at home. One with PNP COM ports, the other not. Could be broken hardware of course. I also find I can no longer authenticate on freeserve (UK). X-stream is okay. Can someone who uses freeserve confirm/deny connection with 4.0-STABLE. Could be broken ISP of course. Any assistance would be most welcome. I can provide dmesg or whatever, but I'm not sure that will help as it's currently okay. Could be broken 'userware' of course :-) On a positive note, at least I now know how to set up a gateway host and DNS servers. Next step - packet filtering and proxy servers. Joy Joy Joy. ian j hart PS. The upgrade 3.4-4.0 went more or less without a hitch. Slightly sweaty palms I couldn't remount / single user. Fixed that once I realised it was still on wd0 not ad0. PPS. This probably will not attach to the thread. I find I cannot send mail (ISP firewall?). Thank God for Yahoo in emergencies. __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.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 Mar 25 20:54:18 2000 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 83CFE37B943 for ; Sat, 25 Mar 2000 20:53:47 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id XAA06149; Sat, 25 Mar 2000 23:53:17 -0500 (EST) Date: Sat, 25 Mar 2000 23:53:16 -0500 (EST) From: Daniel Eischen To: Thimble Smith Cc: freebsd-stable@FreeBSD.ORG Subject: Re: pthread_kill() not killing thread In-Reply-To: <20000324191602.A38647@threads.polyesthetic.msg> 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 Fri, 24 Mar 2000, Thimble Smith wrote: > On Fri, Mar 24, 2000 at 06:07:30PM -0500, Daniel Eischen wrote: > >My "interpretation" of the POSIX spec was that intra-process signals > >sent via pthread_kill() were treated differently than if the signal was > >sent to the process. I'll have to go back and re-read the POSIX spec -- > >perhaps I misunderstood it. > > > >At any rate, FreeBSDs threads implementation of pthread_kill() will > >not have the same effect as kill(2) -- the process will not be terminated > >by issuing a pthread_kill(thrd, SIGTERM) to a thread. Signals sent > >to threads via pthread_kill will invoke a signal handler if it is > >installed and will interrupt the thread from its current operation > >(returning -1 with EINTR). This all assumes that the thread isn't > >masking the signal, and that the handler isn't installed with SA_RESTART. > > OK. Thanks. What I'm really trying to do is figure out why > MySQL will hang if you try to shut it down when there is a > connection open to it. You then have to kill the mysqld > process with -9 in order to get rid of it. :( > > There's a program in the source distribution that tests the > thread signal handling: mysys/test_thr_alarm. It hangs in > a similar way. I'm trying to figure out why. > > So, if anybody knows threads well and also has MySQL on their > box, and feels like checking it out, I'd be happy. I'm sure > I'll figure it out eventually (and it'll be worth it to learn > more about threads), but if anybody can do it in a few seconds > I'd appreciate it. I'll try to take a look at it. I have an older version of mysql installed (from ports) which I use to verify that basic connections still work. I'm having problems staying current on my laptop because FreeBSDs buildworld has become so bloat^H^H^H^H^Hneedy of disk space. It may be a bit before I can get a larger disk drive or install over NFS, but I will try to look at this as soon as possible. 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 Mar 25 21:26:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from oracle.clara.net (oracle.clara.net [195.8.69.94]) by hub.freebsd.org (Postfix) with ESMTP id B603537B988 for ; Sat, 25 Mar 2000 21:26:31 -0800 (PST) (envelope-from freebsd-ml@holistoid.com) Received: from [212.126.132.107] (helo=du-022-0107.claranet.co.uk) by oracle.clara.net with smtp (Exim 2.12 #2) id 12Z5ZG-000N4J-00 for freebsd-stable@FreeBSD.ORG; Sun, 26 Mar 2000 06:26:30 +0100 From: To: freebsd-stable@FreeBSD.ORG Subject: Date: Sun, 26 Mar 2000 06:26:00 +0100 Message-ID: X-Mailer: Forte Agent 1.7/32.534 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG auth 9face08c subscribe freebsd-stable freebsd-ml@holistoid.com auth 093954e4 subscribe freebsd-current freebsd-ml@holistoid.com auth 0d35e3e8 subscribe freebsd-newbies freebsd-ml@holistoid.com auth d62e7efc subscribe freebsd-questions freebsd-ml@holistoid.com auth 7544d3d9 subscribe freebsd-hardware freebsd-ml@holistoid.com auth 59a893ee subscribe freebsd-hackers freebsd-ml@holistoid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 25 21:53: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bongo.rbc.ru (bongo.rbc.ru [212.111.65.120]) by hub.freebsd.org (Postfix) with ESMTP id AE66137B8E2 for ; Sat, 25 Mar 2000 21:53:00 -0800 (PST) (envelope-from mike@rbc.ru) Received: from megera.rbc.ru (megera.rbc.ru [195.218.138.109]) by bongo.rbc.ru (Postfix) with ESMTP id E020E14F93 for ; Sun, 26 Mar 2000 09:52:58 +0400 (MSD) Received: (from root@localhost) by megera.rbc.ru (8.9.3/8.9.3) id JAA21198 for freebsd-stable@FreeBSD.ORG; Sun, 26 Mar 2000 09:53:23 +0400 (MSD) (envelope-from mike) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <00ec01bf9665$f5399c40$f7bbb1d0@netrex.com> Date: Sun, 26 Mar 2000 09:53:23 +0400 (MSD) Reply-To: mike@rbc.ru Organization: =?KOI8-R?Q?=F2=CF=D3=E2=C9=DA=CE=C5=D3=EB=CF=CE=D3=C1=CC=D4=C9=CE=C7?= From: "Mike Ju. Volkov" To: freebsd-stable@FreeBSD.ORG Subject: Re: ps, w, top and netstat problem Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Mar-00 Jerry Bell wrote: > Actually, I am running a rebuilt kernel. For sanity's sake, I just rebuilt > it again, with the config -r, and run MAKEDEV all (copied from > /usr/src/etc). > > Anyway, I'm still having the same problem. Try to remove PROCFS from kernel config. ---------------------------------- E-Mail: Mike Ju. Volkov Date: 26-Mar-00 Time: 09:51:35 ICQ: 5173328 --- Ban the bomb. Save the world for conventional warfare. ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message