From owner-freebsd-stable Sun Aug 20 2:30:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 562E837B43C for ; Sun, 20 Aug 2000 02:30:52 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id CAA12513 for ; Sun, 20 Aug 2000 02:30:52 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 20 Aug 2000 02:30:52 -0700 (PDT) From: Kris Kennaway To: stable@freebsd.org Subject: HEADS UP: OpenSSL 0.9.5a merge 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 just merged OpenSSL version 0.9.5a back to -stable. It's a bit of a large update (sorry, modem users) but it's worth it for the number of bugfixes, etc, since 0.9.4. I feel obliged to mention that one or two people had complained of weird problems using apache+modssl where netscape refused to authenticate to a server running -current (but IE worked fine) - but try as I might I could never replicate these problems on multiple machines, nor could I analyse a fault from the information they provided to me. In the end, the number of people who are successfully using SSL in -current, and the number of other people who need 0.9.5a, convinced me to do the merge. If you do have problems with the new version, please check the docs on www.openssl.org and www.modssl.org (or wherever) in case it's a FAQ and unrelated to my work, but tell me if not so I can look into it again. 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 Aug 20 2:59:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id 6D4B337B43C; Sun, 20 Aug 2000 02:59:26 -0700 (PDT) Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by piranha.amis.net (Postfix) with ESMTP id 00B0E5D1A; Sun, 20 Aug 2000 11:59:25 +0200 (CEST) Date: Sun, 20 Aug 2000 11:59:24 +0200 (CEST) From: Blaz Zupan X-Sender: blaz@titanic.medinet.si To: Kris Kennaway Cc: stable@freebsd.org Subject: Re: HEADS UP: OpenSSL 0.9.5a merge 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 feel obliged to mention that one or two people had complained of weird > problems using apache+modssl where netscape refused to authenticate to a > server running -current (but IE worked fine) - but try as I might I could > never replicate these problems on multiple machines, nor could I analyse a > fault from the information they provided to me. In the end, the number of > people who are successfully using SSL in -current, and the number of other > people who need 0.9.5a, convinced me to do the merge. It is actually quite interesting, I was one of those who complained that apache+modssl was not working with OpenSSL from 4.0-RELEASE. Upgrading to 4.1-RELEASE *fixed* the problems. I looked at the diffs between OpenSSL in 4.0 and 4.1 and they were minimal and absolutely irrelevant to the problems I was experiencing. That's *WEIRD*. Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 3: 1: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 55CA937B424; Sun, 20 Aug 2000 03:00:59 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id DAA14350; Sun, 20 Aug 2000 03:00:59 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 20 Aug 2000 03:00:59 -0700 (PDT) From: Kris Kennaway To: Blaz Zupan Cc: stable@freebsd.org Subject: Re: HEADS UP: OpenSSL 0.9.5a merge In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Aug 2000, Blaz Zupan wrote: > It is actually quite interesting, I was one of those who complained that > apache+modssl was not working with OpenSSL from 4.0-RELEASE. Upgrading to > 4.1-RELEASE *fixed* the problems. I looked at the diffs between OpenSSL in 4.0 > and 4.1 and they were minimal and absolutely irrelevant to the problems I was > experiencing. That's *WEIRD*. Indeed :-) Glad it's working for you..I'll put away the dead chicken. 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 Aug 20 3:43:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id 3603537B422 for ; Sun, 20 Aug 2000 03:43:54 -0700 (PDT) Received: (qmail 3604672 invoked from network); 20 Aug 2000 10:43:51 -0000 Received: from r121m50.cybercable.tm.fr (HELO qualys.com) ([195.132.121.50]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 20 Aug 2000 10:43:51 -0000 Message-ID: <399FB705.FDEA9DA8@qualys.com> Date: Sun, 20 Aug 2000 12:46:29 +0200 From: Maxime Henrion X-Mailer: Mozilla 4.74 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: world is broken (since openssl update) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, it seems there is a problem with the update of openssl. world doesnt build anymore. here is what happens : sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/inc/exception /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/inc/new /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/inc/new.h /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/inc/typeinfo /usr/obj/usr/src/i386/usr/include/g++ cd /usr/src/secure/lib/libcrypto; make beforeinstall mkdir -p openssl cp /usr/src/secure/lib/libcrypto/../libcrypto/opensslconf-i386.h /usr/src/secure/lib/libcrypto/opensslconf-i386.h openssl/opensslconf.h usage: cp [-R [-H | -L | -P]] [-f | -i] [-pv] src target cp [-R [-H | -L | -P]] [-f | -i] [-pv] src1 ... srcN directory *** Error code 64 Stop in /usr/src/secure/lib/libcrypto. *** Error code 1 it seems to be a little error in a Makefile :-) --- Maxime Henrion irc.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 3:57:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by hub.freebsd.org (Postfix) with ESMTP id 8E84837B423; Sun, 20 Aug 2000 03:57:15 -0700 (PDT) Received: from netcom1.netcom.com (user-2initcs.dialup.mindspring.com [165.121.117.156]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id GAA21072; Sun, 20 Aug 2000 06:57:07 -0400 (EDT) Received: by netcom1.netcom.com (Postfix, from userid 1000) id 87BE6E6A02; Sun, 20 Aug 2000 03:56:42 -0700 (PDT) From: Mike Harding To: kris@FreeBSD.org Cc: stable@FreeBSD.org In-reply-to: (message from Kris Kennaway on Sun, 20 Aug 2000 02:30:52 -0700 (PDT)) Subject: Re: HEADS UP: OpenSSL 0.9.5a merge References: Message-Id: <20000820105642.87BE6E6A02@netcom1.netcom.com> Date: Sun, 20 Aug 2000 03:56:42 -0700 (PDT) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris - is there going to be a way in make.conf or similar to pick up the assembly routines for RSA and the bulk crypto? It's twice as fast as the C version that was being built for 0.9.4, at least for RSA. Some of us commercial users have to double up the boxes or buy accelerators or explain why we're not using Linux to support lots of cold RSA connections. Failing that, can the ports be used to build Apache_modssl for 4-stable users? The update only took 5 minutes with a 56K modem. I can't try it right now as dial-on-demand dynamic ppp seems to be flaky with yesterday's buildworld - the 'sticky' default entry isn't working. Anyone else seeing this? - Mike H. X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 20 Aug 2000 02:30:52 -0700 (PDT) From: Kris Kennaway Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.ORG Precedence: bulk X-RULES: lists I've just merged OpenSSL version 0.9.5a back to -stable. It's a bit of a large update (sorry, modem users) but it's worth it for the number of bugfixes, etc, since 0.9.4. I feel obliged to mention that one or two people had complained of weird problems using apache+modssl where netscape refused to authenticate to a server running -current (but IE worked fine) - but try as I might I could never replicate these problems on multiple machines, nor could I analyse a fault from the information they provided to me. In the end, the number of people who are successfully using SSL in -current, and the number of other people who need 0.9.5a, convinced me to do the merge. If you do have problems with the new version, please check the docs on www.openssl.org and www.modssl.org (or wherever) in case it's a FAQ and unrelated to my work, but tell me if not so I can look into it again. 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 3:59: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gw-nl1.origin-it.com (gw-nl1.origin-it.com [193.79.128.34]) by hub.freebsd.org (Postfix) with ESMTP id D849C37B423; Sun, 20 Aug 2000 03:58:53 -0700 (PDT) Received: from mail.de.origin-it.com (localhost.origin-it.com [127.0.0.1]) by gw-nl1.origin-it.com with ESMTP id MAA03886; Sun, 20 Aug 2000 12:58:52 +0200 (MEST) (envelope-from Helge.Oldach@de.origin-it.com) Received: from smtprelay-de1.origin-it.com(172.16.188.53) by gw-nl1.origin-it.com via mwrap (4.0a) id xma003884; Sun, 20 Aug 00 12:58:52 +0200 Received: from mailhub.de.origin-it.com ([130.143.166.88]) by mail.de.origin-it.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id MAA22476; Sun, 20 Aug 2000 12:58:51 +0200 (MET DST) Received: from galaxy.de.cp.philips.com (galaxy.de.cp.philips.com [130.143.166.29]) by mailhub.de.origin-it.com (8.9.3/8.9.3/hmo09aug00) with ESMTP id MAA24034; Sun, 20 Aug 2000 12:58:49 +0200 (CEST) (envelope-from Helge.Oldach@de.origin-it.com) Received: (from hmo@localhost) by galaxy.de.cp.philips.com (8.9.3/8.9.3/hmo14aug98) id MAA28483; Sun, 20 Aug 2000 12:58:47 +0200 (MET DST) Message-Id: <200008201058.MAA28483@galaxy.de.cp.philips.com> Subject: Re: SAMBA and IP filtering In-Reply-To: from "O. Hartmann" at "Aug 18, 2000 12: 3:24 pm" To: ohartman@ipamzlx.physik.uni-mainz.de (O. Hartmann) Date: Sun, 20 Aug 2000 12:58:46 +0200 (MET DST) Cc: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org From: Helge Oldach X-Address: ORIGIN Deutschland GmbH, Billstrasse 80, D-20539 Hamburg, Germany X-Phone: +49 40 7886 464, Fax: +49 40 7886 235, Mobile: +49 172 4515513 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 O. Hartmann: >Is anybody out here who has IP filtering (IPFIREWALL) on and has still >full SAMBA access via NT clients? >I have the following problem: IP filtering is enabled and working well on >our FBSD 4.1 box running samba. One of the first rules is to allow all traffic >from and to the server via the local network, that means no restrictions. With >many services this runs well - but not for SAMBA! > >When trying to access a ip-filtering SAMBA server, I see its icon in the >network neightborhood environment, but when clicking on its icon, I get the >error message "Access denied, network path not found" after a while. Stopping >Ip-filtering solves the problem, but that is not the right solution, I think. >My question is, how to solve this problem. Actually there are two separate issues. To access a remote server you need unrestricted udp/137, udp/138 and tcp/139 from the clients to the server. Note that sometimes the source port is one of these as well, sometimes it is >1024. Your second paragraph appears like you want browsing. Make sure that network broadcasts will go through as well, i.e. you cannot restrict filter to just the server's and client's IP addresses but must include the appropriate network broadcast addresses as well. Helge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 4: 8:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6057437B423; Sun, 20 Aug 2000 04:08:08 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id EAA22996; Sun, 20 Aug 2000 04:08:08 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 20 Aug 2000 04:08:08 -0700 (PDT) From: Kris Kennaway To: Mike Harding Cc: stable@FreeBSD.org Subject: Re: HEADS UP: OpenSSL 0.9.5a merge In-Reply-To: <20000820105642.87BE6E6A02@netcom1.netcom.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, 20 Aug 2000, Mike Harding wrote: > > Kris - is there going to be a way in make.conf or similar to pick up > the assembly routines for RSA and the bulk crypto? It's twice as fast > as the C version that was being built for 0.9.4, at least for RSA. > Some of us commercial users have to double up the boxes or buy > accelerators or explain why we're not using Linux to support lots of > cold RSA connections. Yes, I have patches but need to figure out how they should be enabled: we need to do it properly, which means having a way to tell "make world" what types of CPU-specific optimizations (i.e. asm code) it should perform (e.g. if you have a Pentium II but there are no pentium II-specific optimizations, you still want pentium optimizations). > Failing that, can the ports be used to build Apache_modssl for > 4-stable users? If performance is critical you can remove the FORBIDDEN check in the openssl port (I assume thats what you meant) and use that, but it's not really supported and you may have to do some other hackery to bsd.port.mk to make it not look at the system 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 Sun Aug 20 4:16:16 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 79D3637B42C for ; Sun, 20 Aug 2000 04:16:11 -0700 (PDT) Received: (qmail 3661562 invoked from network); 20 Aug 2000 11:13:49 -0000 Received: from r121m50.cybercable.tm.fr (HELO qualys.com) ([195.132.121.50]) (envelope-sender ) by lafontaine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 20 Aug 2000 11:13:49 -0000 Message-ID: <399FBE0B.9D0CD532@qualys.com> Date: Sun, 20 Aug 2000 13:16:27 +0200 From: Maxime Henrion X-Mailer: Mozilla 4.74 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Maxime Henrion , freebsd-stable@freebsd.org Subject: Re: world is broken (since openssl update) References: <399FB705.FDEA9DA8@qualys.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops. Just re-cvsupped and it works. Sorry for the inconvenience. Maxime Henrion wrote: > Hi, > > it seems there is a problem with the update of openssl. world doesnt > build anymore. > here is what happens : > > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 > /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/inc/exception > /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/inc/new > /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/inc/new.h > /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/inc/typeinfo > /usr/obj/usr/src/i386/usr/include/g++ > cd /usr/src/secure/lib/libcrypto; make beforeinstall > mkdir -p openssl > cp /usr/src/secure/lib/libcrypto/../libcrypto/opensslconf-i386.h > /usr/src/secure/lib/libcrypto/opensslconf-i386.h openssl/opensslconf.h > usage: cp [-R [-H | -L | -P]] [-f | -i] [-pv] src target > cp [-R [-H | -L | -P]] [-f | -i] [-pv] src1 ... srcN directory > *** Error code 64 > > Stop in /usr/src/secure/lib/libcrypto. > *** Error code 1 > > it seems to be a little error in a Makefile :-) > > --- > Maxime Henrion > irc.freebsd.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 4:21:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by hub.freebsd.org (Postfix) with ESMTP id 79D8837B424; Sun, 20 Aug 2000 04:21:06 -0700 (PDT) Received: from netcom1.netcom.com (user-2initcs.dialup.mindspring.com [165.121.117.156]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id HAA25119; Sun, 20 Aug 2000 07:21:04 -0400 (EDT) Received: by netcom1.netcom.com (Postfix, from userid 1000) id 37099E6A02; Sun, 20 Aug 2000 04:21:02 -0700 (PDT) From: Mike Harding To: kris@FreeBSD.org Cc: stable@FreeBSD.org In-reply-to: (message from Kris Kennaway on Sun, 20 Aug 2000 04:08:08 -0700 (PDT)) Subject: Re: HEADS UP: OpenSSL 0.9.5a merge References: Message-Id: <20000820112102.37099E6A02@netcom1.netcom.com> Date: Sun, 20 Aug 2000 04:21:02 -0700 (PDT) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good morning! I am not the only one with insomnia. :) You sent me a patch set earlier but I could not get it to work. I think I can use the ports static libraries and put them in /usr/lib (ick) and then build Apache_modssl. Admittedly a hack but I need. I'll post my results. - Mike Harding X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 20 Aug 2000 04:08:08 -0700 (PDT) From: Kris Kennaway Cc: stable@FreeBSD.org Content-Type: TEXT/PLAIN; charset=US-ASCII X-RULES: lists On Sun, 20 Aug 2000, Mike Harding wrote: > > Kris - is there going to be a way in make.conf or similar to pick up > the assembly routines for RSA and the bulk crypto? It's twice as fast > as the C version that was being built for 0.9.4, at least for RSA. > Some of us commercial users have to double up the boxes or buy > accelerators or explain why we're not using Linux to support lots of > cold RSA connections. Yes, I have patches but need to figure out how they should be enabled: we need to do it properly, which means having a way to tell "make world" what types of CPU-specific optimizations (i.e. asm code) it should perform (e.g. if you have a Pentium II but there are no pentium II-specific optimizations, you still want pentium optimizations). > Failing that, can the ports be used to build Apache_modssl for > 4-stable users? If performance is critical you can remove the FORBIDDEN check in the openssl port (I assume thats what you meant) and use that, but it's not really supported and you may have to do some other hackery to bsd.port.mk to make it not look at the system 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 Sun Aug 20 4:30:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0927F37B443; Sun, 20 Aug 2000 04:30:20 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id EAA24230; Sun, 20 Aug 2000 04:30:20 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 20 Aug 2000 04:30:19 -0700 (PDT) From: Kris Kennaway To: Mike Harding Cc: stable@FreeBSD.org Subject: Re: HEADS UP: OpenSSL 0.9.5a merge In-Reply-To: <20000820112102.37099E6A02@netcom1.netcom.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, 20 Aug 2000, Mike Harding wrote: > > Good morning! I am not the only one with insomnia. :) > > You sent me a patch set earlier but I could not get it to work. I > think I can use the ports static libraries and put them in /usr/lib > (ick) and then build Apache_modssl. Admittedly a hack but I need. > I'll post my results. Actually I think the port builds dynamic libraries too..that should work. Now that I've MFCed OpenSSL 0.9.5a the patches may have a better chance of working, BTW (since they applied against -current). 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 Aug 20 4:32:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id D3C6837B423; Sun, 20 Aug 2000 04:32:27 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id EAA24297; Sun, 20 Aug 2000 04:32:27 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 20 Aug 2000 04:32:27 -0700 (PDT) From: Kris Kennaway To: Maxime Henrion Cc: freebsd-stable@freebsd.org Subject: Re: world is broken (since openssl update) In-Reply-To: <399FB705.FDEA9DA8@qualys.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, 20 Aug 2000, Maxime Henrion wrote: > it seems there is a problem with the update of openssl. world doesnt > build anymore. > here is what happens : You cvsupped (or maybe your server did) in about a 10 minute window before I committed the makefile changes. 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 Aug 20 4:39:43 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 C4AC237B422; Sun, 20 Aug 2000 04:39:40 -0700 (PDT) Received: from netcom1.netcom.com (user-2initcs.dialup.mindspring.com [165.121.117.156]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id HAA19855; Sun, 20 Aug 2000 07:39:38 -0400 (EDT) Received: by netcom1.netcom.com (Postfix, from userid 1000) id 36B8DE6A02; Sun, 20 Aug 2000 04:39:37 -0700 (PDT) From: Mike Harding To: kris@FreeBSD.org Cc: stable@FreeBSD.org In-reply-to: (message from Kris Kennaway on Sun, 20 Aug 2000 04:30:19 -0700 (PDT)) Subject: Re: HEADS UP: OpenSSL 0.9.5a merge References: Message-Id: <20000820113937.36B8DE6A02@netcom1.netcom.com> Date: Sun, 20 Aug 2000 04:39:37 -0700 (PDT) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris - would it be reasonable to support the port as a way to 'tune' your SSL? It already seems to pick up the right CPU and all and so you could theoretically do a NO_OPENSSL=YES if you are a power user and use the ports. You would just want the port to drop the library in the right place... - Mike H. X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 20 Aug 2000 04:30:19 -0700 (PDT) From: Kris Kennaway Cc: stable@FreeBSD.org Content-Type: TEXT/PLAIN; charset=US-ASCII X-RULES: lists On Sun, 20 Aug 2000, Mike Harding wrote: > > Good morning! I am not the only one with insomnia. :) > > You sent me a patch set earlier but I could not get it to work. I > think I can use the ports static libraries and put them in /usr/lib > (ick) and then build Apache_modssl. Admittedly a hack but I need. > I'll post my results. Actually I think the port builds dynamic libraries too..that should work. Now that I've MFCed OpenSSL 0.9.5a the patches may have a better chance of working, BTW (since they applied against -current). 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 Aug 20 4:47:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id EEC4F37B424; Sun, 20 Aug 2000 04:47:46 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id EAA25074; Sun, 20 Aug 2000 04:47:46 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 20 Aug 2000 04:47:46 -0700 (PDT) From: Kris Kennaway To: Mike Harding Cc: stable@FreeBSD.org Subject: Re: HEADS UP: OpenSSL 0.9.5a merge In-Reply-To: <20000820113937.36B8DE6A02@netcom1.netcom.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, 20 Aug 2000, Mike Harding wrote: > > Kris - would it be reasonable to support the port as a way to 'tune' > your SSL? It already seems to pick up the right CPU and all and so > you could theoretically do a NO_OPENSSL=YES if you are a power user > and use the ports. You would just want the port to drop the library > in the right place... I don't want to support that because it's a whole extra set of unknowns. I understand the lack of assembler code is an issue, but once that is solved it shouldn't be necessary. 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 Aug 20 5: 5:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 541F937B424 for ; Sun, 20 Aug 2000 05:05:30 -0700 (PDT) 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 NAA00827; Sun, 20 Aug 2000 13:02:47 +0100 (BST) (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.11.0/8.11.0) with ESMTP id e7KC2Wh03848; Sun, 20 Aug 2000 13:02:32 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200008201202.e7KC2Wh03848@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Gary Kline Cc: freebsd-stable@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: bad /dev/cuaa1?? In-Reply-To: Message from Gary Kline of "Sat, 19 Aug 2000 19:24:39 PDT." <200008200224.TAA36476@tao.thought.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Aug 2000 13:02:32 +0100 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > This is rather bizarre. I have two virtually identical USR modems; > I also have vitually identical ppp and tip and cu setup--I just > copied over tarballs from this system to sage.thought.org. > > According to ppp: > > Warning: deflink: /dev/cuaa1: Bad file descriptor Sounds like the device wasn't probed properly. Check out your dmesg output. [.....] > -- > Gary D. Kline kline@tao.thought.org Public service Unix -- 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 Aug 20 8:18:46 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 C97C037B43E for ; Sun, 20 Aug 2000 08:18:42 -0700 (PDT) Received: from cascade (cascade.veldy.net [192.168.0.1]) by veldy.net (Postfix) with SMTP id 7CAB08C16 for ; Sun, 20 Aug 2000 10:19:16 -0500 (CDT) Message-ID: <004c01c00ab9$eb7f9b50$0100a8c0@cascade> From: "Thomas T. Veldhouse" To: References: Subject: Re: HEADS UP: OpenSSL 0.9.5a merge Date: Sun, 20 Aug 2000 10:18:40 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The problem could have been related to the key type they were using. Netscape will not authenticate a DSA key. Sorry if this has already been mentioned. Tom Veldhouse veldy@veldy.net ----- Original Message ----- From: "Kris Kennaway" To: Sent: Sunday, August 20, 2000 4:30 AM Subject: HEADS UP: OpenSSL 0.9.5a merge > I've just merged OpenSSL version 0.9.5a back to -stable. It's a bit of a > large update (sorry, modem users) but it's worth it for the number of > bugfixes, etc, since 0.9.4. > > I feel obliged to mention that one or two people had complained of weird > problems using apache+modssl where netscape refused to authenticate to a > server running -current (but IE worked fine) - but try as I might I could > never replicate these problems on multiple machines, nor could I analyse a > fault from the information they provided to me. In the end, the number of > people who are successfully using SSL in -current, and the number of other > people who need 0.9.5a, convinced me to do the merge. > > If you do have problems with the new version, please check the docs on > www.openssl.org and www.modssl.org (or wherever) in case it's a FAQ and > unrelated to my work, but tell me if not so I can look into it again. > > Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 8:39:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id D0CB337B423 for ; Sun, 20 Aug 2000 08:39:27 -0700 (PDT) Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by piranha.amis.net (Postfix) with ESMTP id B78F45D1A; Sun, 20 Aug 2000 17:39:26 +0200 (CEST) Date: Sun, 20 Aug 2000 17:39:26 +0200 (CEST) From: Blaz Zupan X-Sender: blaz@titanic.medinet.si To: "Thomas T. Veldhouse" Cc: freebsd-stable@freebsd.org Subject: Re: HEADS UP: OpenSSL 0.9.5a merge In-Reply-To: <004c01c00ab9$eb7f9b50$0100a8c0@cascade> 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 > The problem could have been related to the key type they were using. > Netscape will not authenticate a DSA key. Sorry if this has already been > mentioned. Ehm, as I said, it works just fine with the OpenSSL 0.9.4 port and with 4.1-RELEASE. The key was generated by Thawte, but a self-generated and self-signed key exhibited exactly the same problem. But as I said, this problem is a thing of the past because it is gone in 4.1-RELEASE for whatever twisted reason. Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 9:34:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from qmail.corpex.net (qmail.corpex.net [195.153.247.40]) by hub.freebsd.org (Postfix) with SMTP id 49B5C37B43C for ; Sun, 20 Aug 2000 09:34:33 -0700 (PDT) Received: (qmail 60387 invoked from network); 20 Aug 2000 16:36:49 -0000 Received: from perseus.corpex.net (HELO perseus) (195.153.247.226) by qmail.corpex.net with SMTP; 20 Aug 2000 16:36:49 -0000 From: "Jonathan Defries" To: Subject: Password problems Date: Sun, 20 Aug 2000 17:34:29 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have a problem with password on 3.5-STABLE. If I run the passwd command, it takes nearly a minute to be prompted for the password. Could anyone suggest what to look for to try and solve this please? TIA, Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 9:37:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.forumone.com (orion.forumone.com [207.197.141.10]) by hub.freebsd.org (Postfix) with ESMTP id 4607037B424 for ; Sun, 20 Aug 2000 09:37:45 -0700 (PDT) Received: from orion.forumone.com (orion.forumone.com [207.197.141.10]) by mail.forumone.com (Postfix) with ESMTP id 83428AA13; Sun, 20 Aug 2000 12:37:31 -0400 (EDT) Date: Sun, 20 Aug 2000 12:37:31 -0400 (EDT) From: Joakim Ryden To: Jonathan Defries Cc: freebsd-stable@freebsd.org Subject: Re: Password problems 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 Make sure you don't have NIS enabled.. Joakim Today at 5:34pm owner-freebsd-stable@FreeBSD.ORG suggested: =>Hi, => =>I have a problem with password on 3.5-STABLE. => =>If I run the passwd command, it takes nearly a minute to be prompted =>for the password. Could anyone suggest what to look for to try and =>solve this please? => =>TIA, => => Jonathan => => => =>To Unsubscribe: send mail to majordomo@FreeBSD.org =>with "unsubscribe freebsd-stable" in the body of the message => +----------------------------------------------+ |Joakim Ryden | |jo@forumone.com | |http://www.forumone.com/consult | |"Communicate, collaborate, change the world." | +----------------------------------------------+ We're always looking for smart and web-savvy people like you! Learn more at http://www.forumone.com/consult/jobs.htm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 9:40:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from qmail.corpex.net (qmail.corpex.net [195.153.247.40]) by hub.freebsd.org (Postfix) with SMTP id E1FE237B440 for ; Sun, 20 Aug 2000 09:40:09 -0700 (PDT) Received: (qmail 67180 invoked from network); 20 Aug 2000 16:42:26 -0000 Received: from perseus.corpex.net (HELO perseus) (195.153.247.226) by qmail.corpex.net with SMTP; 20 Aug 2000 16:42:26 -0000 From: "Jonathan Defries" To: "Joakim Ryden" Cc: Subject: RE: Password problems Date: Sun, 20 Aug 2000 17:40:07 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My rc.conf says: nis_server_enable="NO" nis_client_enable="NO" Is this all I need to ensure it is not running? - Jonathan > > Make sure you don't have NIS enabled.. > > Joakim > > Today at 5:34pm owner-freebsd-stable@FreeBSD.ORG suggested: > > =>Hi, > => > =>I have a problem with password on 3.5-STABLE. > => > =>If I run the passwd command, it takes nearly a minute to be prompted > =>for the password. Could anyone suggest what to look for to try and > =>solve this please? > => > =>TIA, > => > => Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 9:44:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (Postfix) with ESMTP id B833737B42C for ; Sun, 20 Aug 2000 09:44:52 -0700 (PDT) Received: from tao.thought.org (tao.sea.tera.com [207.108.223.55]) by gershwin.tera.com (8.9.3/8.9.3) with ESMTP id JAA07434; Sun, 20 Aug 2000 09:45:08 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.9.3/8.7.3) id JAA41860; Sun, 20 Aug 2000 09:44:49 -0700 (PDT) Date: Sun, 20 Aug 2000 09:44:49 -0700 From: Gary Kline To: Brian Somers Cc: Gary Kline , freebsd-stable@FreeBSD.ORG Subject: Re: bad /dev/cuaa1?? Message-ID: <20000820094449.B41415@tao.thought.org> References: <200008201202.e7KC2Wh03848@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200008201202.e7KC2Wh03848@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Sun, Aug 20, 2000 at 01:02:32PM +0100 X-Organization: Thought Unlimited. Public service Unix since 1986. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 20, 2000 at 01:02:32PM +0100, Brian Somers wrote: > > > > This is rather bizarre. I have two virtually identical USR modems; > > I also have vitually identical ppp and tip and cu setup--I just > > copied over tarballs from this system to sage.thought.org. > > > > According to ppp: > > > > Warning: deflink: /dev/cuaa1: Bad file descriptor > > Sounds like the device wasn't probed properly. Check out your dmesg > output. > Yup; that lead to checking my BIOS and to the discovery --thanks to Sean O'Connell here whose eyesight is much better than mine--that my COM2 port was set to COM3. At any rate, things work ... . gary > -- Gary D. Kline kline@tao.thought.org Public service Unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 9:49:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.forumone.com (orion.forumone.com [207.197.141.10]) by hub.freebsd.org (Postfix) with ESMTP id 8DB2637B424 for ; Sun, 20 Aug 2000 09:49:15 -0700 (PDT) Received: from orion.forumone.com (orion.forumone.com [207.197.141.10]) by mail.forumone.com (Postfix) with ESMTP id BE50DA982; Sun, 20 Aug 2000 12:49:14 -0400 (EDT) Date: Sun, 20 Aug 2000 12:49:14 -0400 (EDT) From: Joakim Ryden To: Jonathan Defries Cc: freebsd-stable@freebsd.org Subject: RE: Password problems 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 Well.. if you've been messing with the yp* binaries make sure none of them are running still - if none of them are running I think we can rule out NIS as the problem maker and then I have no idea. :-) Joakim Today at 5:40pm Jonathan Defries suggested: =>My rc.conf says: => =>nis_server_enable="NO" =>nis_client_enable="NO" => =>Is this all I need to ensure it is not running? => => - Jonathan => =>> =>> Make sure you don't have NIS enabled.. =>> =>> Joakim =>> =>> Today at 5:34pm owner-freebsd-stable@FreeBSD.ORG suggested: =>> =>> =>Hi, =>> => =>> =>I have a problem with password on 3.5-STABLE. =>> => =>> =>If I run the passwd command, it takes nearly a minute to be prompted =>> =>for the password. Could anyone suggest what to look for to try and =>> =>solve this please? =>> => =>> =>TIA, =>> => =>> => Jonathan => => +----------------------------------------------+ |Joakim Ryden | |jo@forumone.com | |http://www.forumone.com/consult | |"Communicate, collaborate, change the world." | +----------------------------------------------+ We're always looking for smart and web-savvy people like you! Learn more at http://www.forumone.com/consult/jobs.htm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 9:59:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from qmail.corpex.net (qmail.corpex.net [195.153.247.40]) by hub.freebsd.org (Postfix) with SMTP id 7D26937B423 for ; Sun, 20 Aug 2000 09:59:52 -0700 (PDT) Received: (qmail 91982 invoked from network); 20 Aug 2000 17:02:09 -0000 Received: from perseus.corpex.net (HELO perseus) (195.153.247.226) by qmail.corpex.net with SMTP; 20 Aug 2000 17:02:09 -0000 From: "Jonathan Defries" To: "Joakim Ryden" Cc: Subject: RE: Password problems Date: Sun, 20 Aug 2000 17:59:49 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, thanks. There's none of them running. Guess we're both out of ideas for now :) Cheers anyway, Jonathan > Well.. if you've been messing with the yp* binaries make > sure none of them are running still - if none of them are > running I think we can rule out NIS as the problem maker and > then I have no idea. :-) > > Joakim > > > Today at 5:40pm Jonathan Defries suggested: > > =>My rc.conf says: > => > =>nis_server_enable="NO" > =>nis_client_enable="NO" > => > =>Is this all I need to ensure it is not running? > => > => - Jonathan > => > =>> > =>> Make sure you don't have NIS enabled.. > =>> > =>> Joakim > =>> > =>> Today at 5:34pm owner-freebsd-stable@FreeBSD.ORG suggested: > =>> > =>> =>Hi, > =>> => > =>> =>I have a problem with password on 3.5-STABLE. > =>> => > =>> =>If I run the passwd command, it takes nearly a minute to > be prompted > =>> =>for the password. Could anyone suggest what to look for to try and > =>> =>solve this please? > =>> => > =>> =>TIA, > =>> => > =>> => Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 13:48:58 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 919F637B422 for ; Sun, 20 Aug 2000 13:48:53 -0700 (PDT) Received: from localhost (trond@localhost) by ramstind.gtf.ol.no (8.9.3/8.9.3) with ESMTP id WAA70370; Sun, 20 Aug 2000 22:48:46 +0200 (CEST) (envelope-from trond@ramstind.gtf.ol.no) Date: Sun, 20 Aug 2000 22:48:46 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= To: Jonathan Defries Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Password problems In-Reply-To: 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, 20 Aug 2000, Jonathan Defries wrote: > If I run the passwd command, it takes nearly a minute to be prompted > for the password. Could anyone suggest what to look for to try and > solve this please? Set your NIS domain to NO in /etc/rc.conf. -- ---------------------------------------------------------------------- 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.5-S & 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 Aug 20 13:49:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.md.home.com (ha1.rdc1.md.home.com [24.2.2.66]) by hub.freebsd.org (Postfix) with ESMTP id 0A77437B422 for ; Sun, 20 Aug 2000 13:49:39 -0700 (PDT) Received: from BradLathan ([24.10.230.113]) by mail.rdc1.md.home.com (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20000820204938.FODE4590.mail.rdc1.md.home.com@BradLathan> for ; Sun, 20 Aug 2000 13:49:38 -0700 Message-ID: <001001c00ae8$11a832a0$71e60a18@dlcty1.va.home.com> From: "Bradley D Lathan" To: Subject: creating a second superuser account Date: Sun, 20 Aug 2000 16:49:00 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000D_01C00AC6.8A643800" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_000D_01C00AC6.8A643800 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable How do you create a second super user account i.e. for a person that = wants to program and have access to the compiler and write permissions Brad ------=_NextPart_000_000D_01C00AC6.8A643800 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
How do you create a second super user = account i.e.=20 for a person that wants to program and have access to the compiler and = write=20 permissions
 
Brad
------=_NextPart_000_000D_01C00AC6.8A643800-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 13:57:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (Postfix) with ESMTP id DA27837B424 for ; Sun, 20 Aug 2000 13:57:09 -0700 (PDT) Received: from tao.thought.org (tao.sea.tera.com [207.108.223.55]) by gershwin.tera.com (8.9.3/8.9.3) with ESMTP id NAA10066; Sun, 20 Aug 2000 13:57:25 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.9.3/8.7.3) id NAA43633; Sun, 20 Aug 2000 13:57:06 -0700 (PDT) Date: Sun, 20 Aug 2000 13:57:06 -0700 From: Gary Kline To: Doug White Cc: Gary Kline , freebsd-stable@FreeBSD.ORG Subject: Re: not in bitmap Message-ID: <20000820135706.A43483@tao.thought.org> References: <200008200341.UAA37091@tao.thought.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from dwhite@resnet.uoregon.edu on Sun, Aug 20, 2000 at 01:26:30PM -0700 X-Organization: Thought Unlimited. Public service Unix since 1986. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 20, 2000 at 01:26:30PM -0700, Doug White wrote: > On Sat, 19 Aug 2000, Gary Kline wrote: > > > sio1: configured irq 3 not in bitmap of probed irqs 0 > > This message means "I poked sio1 and it didn't generate any > interrupts." Are you sure it's enabled in the BIOS and set to the correct > I/O port (0x2F8)? > > The sio driver tries to be smart and figure out which IRQ the port is > sitting on. If the configured IRQ isn't in the set of IRQs that responded > when the port was poked then it fails with this message. If the bitmap is > '0' then no interrupts occured, which means the port is not responding on > the configured I/O port. > Someone other than me changed the COM2 configuration in the BIOS. But now everything is happy with the other platform and I ought to be able to dial out just-in-case I mess up this box during my update. *shudder* ;) gary > -- Gary D. Kline kline@tao.thought.org Public service Unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 14:26:12 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 2F03537B424; Sun, 20 Aug 2000 14:25:55 -0700 (PDT) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id RAA07155; Sun, 20 Aug 2000 17:25:55 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Sun, 20 Aug 2000 17:25:55 -0400 (EDT) From: "Brandon D. Valentine" To: Bradley D Lathan Cc: freebsd-questions@FreeBSD.ORG Subject: Re: creating a second superuser account In-Reply-To: <001001c00ae8$11a832a0$71e60a18@dlcty1.va.home.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 [Originted on -stable. I've moved it to -questions and Bcc:'d -stable to end it there] On Sun, 20 Aug 2000, Bradley D Lathan wrote: >How do you create a second super user account i.e. for a person that wants to program and have access to the compiler and write permissions Hey Brad, 1) Wrong mailing list. Try questions@freebsd.org. 2) This question is quite misguided. There is no reason to create a second superuser account just so somebody can program. They don't need superuser access for anything related to the compiler and they should have write permissions in their home directory. If this is unclear to you you need to rework your concept of permissions perhaps. Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 14:57:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n1f.san.rr.com (dt051n1f.san.rr.com [204.210.32.31]) by hub.freebsd.org (Postfix) with ESMTP id 2C56E37B424; Sun, 20 Aug 2000 14:57:25 -0700 (PDT) Received: from gorean.org (master [10.0.0.2]) by dt051n1f.san.rr.com (8.9.3/8.9.3) with ESMTP id OAA77188; Sun, 20 Aug 2000 14:57:20 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <39A05440.2D356BC9@gorean.org> Date: Sun, 20 Aug 2000 14:57:20 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: stable@FreeBSD.org Subject: Re: HEADS UP: OpenSSL 0.9.5a merge 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: > Glad it's working for you..I'll put away the dead chicken. You're using DEAD chickens? Well there's your problem.... Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 15:17:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (Postfix) with ESMTP id E791A37B423 for ; Sun, 20 Aug 2000 15:17:18 -0700 (PDT) Received: from tao.thought.org (tao.sea.tera.com [207.108.223.55]) by gershwin.tera.com (8.9.3/8.9.3) with ESMTP id PAA10973 for ; Sun, 20 Aug 2000 15:17:35 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.9.3/8.7.3) id PAA97711 for freebsd-stable@FreeBSD.ORG; Sun, 20 Aug 2000 15:17:15 -0700 (PDT) From: Gary Kline Message-Id: <200008202217.PAA97711@tao.thought.org> Subject: mkstemps To: freebsd-stable@FreeBSD.ORG Date: Sun, 20 Aug 2000 15:17:15 -0700 (PDT) Organization: <> thought.org: pvblic service Unix since 1986... <> 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 Well, my first snag. cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/objdump -I/usr/src/gnu/usr.bin/binutils/objdump/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/objdump/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/binutils/objdump/../libbinutils -I/usr/src/gnu/usr.bin/binutils/objdump/../../../../contrib/binutils/binutils -DBFD_VERSION=\"2.10.0\" -I/usr/obj/usr/src/i386/usr/include -o objdump objdump.o prdbg.o ../libbinutils/libbinutils.a ../libopcodes/libopcodes.a ../libbfd/libbfd.a ../libiberty/libiberty.a ../libiberty/libiberty.a(choose-temp.o): In function `make_temp_file': choose-temp.o(.text+0x264): undefined reference to `mkstemps' *** Error code 1 Stop. I added mkstemps.c to the SRCS in /usr/src/gnu/usr.bin/binutils/libiberty/Makefile and am munching forward; shouldn't someone CVS commit this fix? I just cvsup'd yesterday (19aug00) and this has been around for several days... gary -- Gary D. Kline kline@tao.thought.org Public service Unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 15:39:30 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 3D42637B43C; Sun, 20 Aug 2000 15:39:27 -0700 (PDT) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13QdkJ-000J4J-00; Mon, 21 Aug 2000 00:39:15 +0200 Date: Mon, 21 Aug 2000 00:39:15 +0200 From: Neil Blakey-Milner To: Doug Barton Cc: Kris Kennaway , stable@FreeBSD.org Subject: Re: HEADS UP: OpenSSL 0.9.5a merge Message-ID: <20000821003914.A73272@mithrandr.moria.org> References: <39A05440.2D356BC9@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <39A05440.2D356BC9@gorean.org>; from DougB@gorean.org on Sun, Aug 20, 2000 at 02:57:20PM -0700 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 Sun 2000-08-20 (14:57), Doug Barton wrote: > > Glad it's working for you..I'll put away the dead chicken. > > You're using DEAD chickens? Well there's your problem.... Well, with all that blood removed to form the $shape, I'd be surprised if any survived. Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 15:59:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 80E7A37B43F; Sun, 20 Aug 2000 15:59:24 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.9.3/8.9.3) id IAA30078; Mon, 21 Aug 2000 08:29:23 +0930 (CST) (envelope-from grog) Date: Mon, 21 Aug 2000 08:29:23 +0930 From: Greg Lehey To: FreeBSD Stable Users , FreeBSD Documenters Subject: Problems making release with -STABLE? Message-ID: <20000821082923.A40941@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anybody tried a make release on -STABLE lately? I've tried, and after 8 hours I get: ===> de_DE.ISO_8859-1/books/handbook install -C -o root -g wheel -m 444 book.html usage: install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-v] [-g group] [-m mode] [-o owner] directory ... *** Error code 64 I can go looking for the problems, but in this particular case it hardly seems worth the trouble. BTW, does anybody else find it strange that we need jade to make a release? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 16: 5: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from jeff.isni.net (user207302034.fl.sprint-hsd.net [207.30.203.4]) by hub.freebsd.org (Postfix) with ESMTP id 60B8A37B424; Sun, 20 Aug 2000 16:04:59 -0700 (PDT) Received: from localhost (jeff@localhost) by jeff.isni.net (8.11.0/8.11.0) with ESMTP id e7KN4rC10994; Sun, 20 Aug 2000 19:04:54 -0400 (EDT) X-Authentication-Warning: jeff.isni.net: jeff owned process doing -bs Date: Sun, 20 Aug 2000 19:04:47 -0400 (EDT) From: Jeff Palmer To: Doug Barton Cc: Kris Kennaway , stable@FreeBSD.ORG Subject: Re: HEADS UP: OpenSSL 0.9.5a merge In-Reply-To: <39A05440.2D356BC9@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 I only want grade "A" tenderloin, farm raised Perdue chickens in MY OS! Jeff On Sun, 20 Aug 2000, Doug Barton wrote: > Kris Kennaway wrote: > > > Glad it's working for you..I'll put away the dead chicken. > > You're using DEAD chickens? Well there's your problem.... > > Doug > > > 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 Aug 20 16:11:54 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 ADE4237B422; Sun, 20 Aug 2000 16:11:49 -0700 (PDT) Received: by pawn.primelocation.net (Postfix, from userid 1016) id C22389B05; Sun, 20 Aug 2000 19:11:48 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id B2CBABA03; Sun, 20 Aug 2000 19:11:48 -0400 (EDT) Date: Sun, 20 Aug 2000 19:11:48 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Greg Lehey Cc: FreeBSD Stable Users , FreeBSD Documenters Subject: Re: Problems making release with -STABLE? In-Reply-To: <20000821082923.A40941@wantadilla.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 21 Aug 2000, Greg Lehey wrote: > Has anybody tried a make release on -STABLE lately? I've tried, and > after 8 hours I get: > > ===> de_DE.ISO_8859-1/books/handbook > install -C -o root -g wheel -m 444 book.html > usage: install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 > install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 ... > fileN directory > install -d [-v] [-g group] [-m mode] [-o owner] directory ... > *** Error code 64 > > I can go looking for the problems, but in this particular case it > hardly seems worth the trouble. > It appears doc/de_DE.ISO_8859-1/books/Makefile.inc is missing. doc/en_EN.ISO_8859-1/books/Makefile.inc contains: DESTDIR?= ${DOCDIR}/en_US.ISO_8859-1/books/${.CURDIR:T} which should be necessary under de_DE.mumble/books also. > BTW, does anybody else find it strange that we need jade to make a > release? > Not if NODOC is set. ----- 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 Sun Aug 20 16:18:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from accord.grasslake.net (accord.grasslake.net [206.11.249.240]) by hub.freebsd.org (Postfix) with ESMTP id 5ABA937B422 for ; Sun, 20 Aug 2000 16:18:42 -0700 (PDT) Received: from k6 (k6.grasslake.net [192.168.2.1]) by accord.grasslake.net (8.9.3/8.9.3) with SMTP id SAA34436 for ; Sun, 20 Aug 2000 18:19:54 -0500 (CDT) (envelope-from swb@grasslake.net) Message-ID: <051e01c00afd$4d0e99a0$0102a8c0@k6> From: "Shawn Barnhart" To: Subject: SMP and system loads Date: Sun, 20 Aug 2000 18:21:00 -0500 Organization: Grasslake.Net 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 Do I need to do anything more than: # Required: options SMP options APIC_IO ...to get SMP working? I just stuffed the drives from a 4.1 system that had been running on a PII233 system with 96MB of RAM into a system with dual PII400s & 256MB RAM. I rebuilt my kernel with the above options in my config file. The previous system had been averaging about 45% CPU utilization, most of it coming from mrtg monitoring a longish list of devices. After running most of the day on the SMP-enabled kernel, the load average doesn't seem to have changed any. Now I realize that mrtg is mostly a perl script and isn't multithreaded, but given the fact that I'm running two CPUs, shouldn't the overall load average be no more than half of what it was? I'm doing same units of work but have twice as much CPU available for doing them. I get output when I run mptable and when I run top I can see active processes get scheduled on different CPUs, and dmesg reports SMP: AP CPU #1 Launched! ...so I'm fairly certain I'm actually running SMP.. What kind of clue am I missing? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 17:45:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id 3B3DE37B424 for ; Sun, 20 Aug 2000 17:45:28 -0700 (PDT) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 13QfiC-0003db-00; Sun, 20 Aug 2000 17:45:12 -0700 Date: Sun, 20 Aug 2000 17:45:07 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Shawn Barnhart Cc: freebsd-stable@FreeBSD.ORG Subject: Re: SMP and system loads In-Reply-To: <051e01c00afd$4d0e99a0$0102a8c0@k6> 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, 20 Aug 2000, Shawn Barnhart wrote: ... > The previous system had been averaging about 45% CPU utilization, most > of it coming from mrtg monitoring a longish list of devices. After > running most of the day on the SMP-enabled kernel, the load average > doesn't seem to have changed any. Systems load average is not equal to or comparable to CPU utilization. Apples and oranges. > Now I realize that mrtg is mostly a perl script and isn't multithreaded, > but given the fact that I'm running two CPUs, shouldn't the overall load > average be no more than half of what it was? I'm doing same units of > work but have twice as much CPU available for doing them. No. The load average should identical with the same load. The system load average is the average number of processes in the running (or in short term wait). The best thing for your application is to split your mrtg.cfg file into two, and run them through separate instances of mrtg. Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 17:46:28 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 10B7E37B423 for ; Sun, 20 Aug 2000 17:46:25 -0700 (PDT) Received: from sos (userhost.mdes.dk [130.228.127.200]) by www.menzor.dk (8.8.8/8.8.8) with SMTP id DAA25903 for ; Mon, 21 Aug 2000 03:36:18 +0200 (CEST) (envelope-from ml@seeberg.dk) Message-ID: <005b01c00b11$c8cbc180$deff58c1@sos> From: "Morten Seeberg" To: Subject: Booting 4.1 ISO on Thinkpads never work for me??? Date: Mon, 21 Aug 2000 02:47:36 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had a similar problem with the 4.0 image, and asked about it here, without any answers, now that I have the same problem with 4.1 on my new thinkpad 600x (had a 600e before), I thought someone should think about this. I burned the ISO from cdrom.com with cdrecord, and the laptop does boot the CD, but stops at the bootloader, and after a approx. 20-30 second timeout says that ItŽs confused and doesnŽt know which drive to boot from (theres Drive 0 = Floppy but taken over by CD (as far as I see it) and Drive 1 (my harddisk). I cannot boot from any of them, any suggestions? Doing the install via the floppies worked fine. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /\/\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 Sun Aug 20 17:51:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.lewman.org (lowrider.lewman.org [63.109.230.166]) by hub.freebsd.org (Postfix) with ESMTP id 3F8EB37B423 for ; Sun, 20 Aug 2000 17:51:10 -0700 (PDT) Received: by mail.lewman.org (Postfix, from userid 1004) id 5EBFA3D31; Sun, 20 Aug 2000 20:51:58 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.lewman.org (Postfix) with ESMTP id 5CFFC5BB9; Sun, 20 Aug 2000 20:51:58 -0400 (EDT) Date: Sun, 20 Aug 2000 20:51:58 -0400 (EDT) From: Sean Lutner X-Sender: sean@lowrider.lewman.org To: Bradley D Lathan Cc: freebsd-stable@freebsd.org Subject: Re: creating a second superuser account In-Reply-To: <001001c00ae8$11a832a0$71e60a18@dlcty1.va.home.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 /usr/ports/security/sudo It is your friend On Sun, 20 Aug 2000, Bradley D Lathan wrote: > How do you create a second super user account i.e. for a person that wants to program and have access to the compiler and write permissions > > Brad > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 17:59:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id C3F9A37B43F for ; Sun, 20 Aug 2000 17:59:05 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id SAA02213; Sun, 20 Aug 2000 18:12:05 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008210112.SAA02213@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Morten Seeberg" Cc: stable@freebsd.org Subject: Re: Booting 4.1 ISO on Thinkpads never work for me??? In-reply-to: Your message of "Mon, 21 Aug 2000 02:47:36 BST." <005b01c00b11$c8cbc180$deff58c1@sos> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Sun, 20 Aug 2000 18:12:05 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I had a similar problem with the 4.0 image, and asked about it here, wi= thout > any answers, now that I have the same problem with 4.1 on my new thinkp= ad > 600x (had a 600e before), I thought someone should think about this. > = > I burned the ISO from cdrom.com with cdrecord, and the laptop does boot= the > CD, but stops at the bootloader, and after a approx. 20-30 second timeo= ut > says that It=B4s confused and doesn=B4t know which drive to boot from (= theres > Drive 0 =3D Floppy but taken over by CD (as far as I see it) and Drive = 1 (my > harddisk). > = > I cannot boot from any of them, any suggestions? Thinkpads are troublesome when it comes to CDROMs. Until someone with = one either a) lends us one, or b) works it out for themselves, I'm not = sure we can do anything about this. The problem is fairly = straightforward, and I've explained it to several people (none of whom = have ever gotten back to me). -- = =2E.. every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 20:47:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30]) by hub.freebsd.org (Postfix) with ESMTP id 63BEB37B423 for ; Sun, 20 Aug 2000 20:47:48 -0700 (PDT) Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.9.3/8.9.3) id NAA24966; Mon, 21 Aug 2000 13:47:46 +1000 (EST) (envelope-from carl@xena.IPAustralia.gov.au) Received: from xena.aipo.gov.au(10.0.100.52) by pericles.IPAustralia.gov.au via smap (V2.0) id xma024959; Mon, 21 Aug 00 13:47:43 +1000 Received: from newton.aipo.gov.au (newton.aipo.gov.au [10.0.100.18]) by xena.aipo.gov.au (8.9.3/8.9.3) with ESMTP id NAA46257; Mon, 21 Aug 2000 13:53:28 +1000 (EST) (envelope-from carl@xena.ipaustralia.gov.au) Received: from localhost (carl@localhost) by newton.aipo.gov.au (8.9.3/8.9.3) with ESMTP id NAA41335; Mon, 21 Aug 2000 13:47:36 +1000 (EST) (envelope-from carl@xena.ipaustralia.gov.au) X-Authentication-Warning: newton.aipo.gov.au: carl owned process doing -bs Date: Mon, 21 Aug 2000 13:47:36 +1000 (EST) From: Carl Makin X-Sender: carl@newton.aipo.gov.au To: Sean Lutner Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Fibre Channel Cards? 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, 18 Aug 2000, Sean Lutner wrote: > production, so my question is whether or not there are drivers out there > for any fibre channel cards? A cluster or just a bunch of beefy x86 I've run a QLogic 2200 card with an IBM SAN data gateway to a ESS 2105 (Shark) and it worked well. Remember to compile the card firmware into the kernel or it doesn't initialise the card properly. Well it didn't in my case. Carl. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 20:51:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (Postfix) with ESMTP id 86A2937B42C for ; Sun, 20 Aug 2000 20:51:53 -0700 (PDT) Received: from tao.thought.org (tao.sea.tera.com [207.108.223.55]) by gershwin.tera.com (8.9.3/8.9.3) with ESMTP id UAA14437 for ; Sun, 20 Aug 2000 20:52:09 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.9.3/8.7.3) id UAA22713 for freebsd-stable@FreeBSD.ORG; Sun, 20 Aug 2000 20:51:50 -0700 (PDT) From: Gary Kline Message-Id: <200008210351.UAA22713@tao.thought.org> Subject: build of sys/modules bombs... To: freebsd-stable@FreeBSD.ORG Date: Sun, 20 Aug 2000 20:51:49 -0700 (PDT) Organization: <> thought.org: pvblic service Unix since 1986... <> 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 Can anybody give me some clues here? The modules can't find sys/time.h, but it is there. Could the links be messed up? After I did # make buildworld I did a successful make buildkernel KERNEL=GENERIC, then, cd'd to /sys/modules and a make install; the following happened. I *did* do a make clean before in /sys/modules before the make install. That was not in the UPDATING file. ===> accf_data Warning: Object directory not changed from original /usr/src/sys/modules/accf_da ta cc -O -pipe -DKERNEL -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wne sted-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -DKLD_MODULE -nostd inc -I- -I/usr/src/sys/modules/accf_data -I/usr/src/sys/modules/accf_data/@ -c /usr/src/sys/modules/accf_data/../../netinet/accf_data.c In file included from /usr/src/sys/modules/accf_data/@/sys/proc.h:52, from /usr/src/sys/modules/accf_data/../../netinet/accf_data.c:35: /usr/src/sys/modules/accf_data/@/sys/time.h:289: time.h: No such file or directory So far I'm further along that I'd thought. Does anybody know the magic incantation to help me? gary -- Gary D. Kline kline@tao.thought.org Public service Unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 21:41:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 090FB37B423; Sun, 20 Aug 2000 21:41:40 -0700 (PDT) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id WAA07768; Sun, 20 Aug 2000 22:41:30 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id WAA10471; Sun, 20 Aug 2000 22:40:24 -0600 (MDT) (envelope-from nate) Date: Sun, 20 Aug 2000 22:40:24 -0600 (MDT) Message-Id: <200008210440.WAA10471@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable To: Mike Smith Cc: "Morten Seeberg" , stable@FreeBSD.ORG Subject: Re: Booting 4.1 ISO on Thinkpads never work for me??? In-Reply-To: <200008210112.SAA02213@mass.osd.bsdi.com> References: <005b01c00b11$c8cbc180$deff58c1@sos> <200008210112.SAA02213@mass.osd.bsdi.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I had a similar problem with the 4.0 image, and asked about it here= , without > > any answers, now that I have the same problem with 4.1 on my new th= inkpad > > 600x (had a 600e before), I thought someone should think about this= . > >=20 > > I burned the ISO from cdrom.com with cdrecord, and the laptop does = boot the > > CD, but stops at the bootloader, and after a approx. 20-30 second t= imeout > > says that It=B4s confused and doesn=B4t know which drive to boot fr= om (theres > > Drive 0 =3D Floppy but taken over by CD (as far as I see it) and Dr= ive 1 (my > > harddisk). > >=20 > > I cannot boot from any of them, any suggestions? >=20 > Thinkpads are troublesome when it comes to CDROMs. Until someone wit= h=20 > one either a) lends us one, or b) works it out for themselves, I'm no= t=20 > sure we can do anything about this. The problem is fairly=20 > straightforward, and I've explained it to several people (none of who= m=20 > have ever gotten back to me). I've offered to let you sit down with my Thinkpad (600e) next time I'm in town. The offer still stands, and I'll be in town next week if you are interested in fixing this some evening. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 20 23: 3:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from grace.speakeasy.org (grace.speakeasy.org [216.254.0.2]) by hub.freebsd.org (Postfix) with SMTP id AF23537B424 for ; Sun, 20 Aug 2000 23:03:33 -0700 (PDT) Received: (qmail 13947 invoked by uid 17401); 21 Aug 2000 06:03:33 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 21 Aug 2000 06:03:33 -0000 Date: Sun, 20 Aug 2000 23:03:32 -0700 (PDT) From: Billy To: freebsd-smp@freebsd.org, freebsd-stable@freebsd.org Subject: My System Hangs/Deadlock? 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 am currently experiencing problems with my FreeBSD system. I just recently go in my dual celeron/abit box in and have just started to use it. I am experiencing a strange problem I've never seen before. Whenever I do some intensive work, my computer will lock up. I still see my terminal screen, but it will accept no keyboard/mouse/network input. It won't even return attempted network connections, it just sits there dead for all intents and purposes and will stay like this for as long as I leave it(the longest being ~24H). I have to do a hard reset to reboot my machine, at which point it commes up fine (usually, although I have had to fsck the disk once when I did this). I do have an SMP system, however this problem occurs on either SMP or non-SMP kernel. This also occurs with and without runnning X. I am running 4.1-STABLE FreeBSD 4.1-STABLE with an SMP kernel. I have one IDE disk (DMA not used because of previous problems). I have a fairly vanilla kernel config. All SCSI entries have been removed, as have device entries for devices I do not have. It does not look like a hardware problem to me (no kernel panics, no reboots, etc). It does look like a deadlocking problem of some kind, but I havn't seen anything in the mail archive or the newsgroups recently about deadlocks (except for something unrelated I think). If you have any ideas please let me know. It's kind of annoying for my non-windows box to need a hard reset. Relevant Hardware ================= Dual ABit BP6 2 Celeron 466 PPGA Maxtor 20GB 7200RPM Drive EIDE -billy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 0:25:27 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 D18D537B42C; Mon, 21 Aug 2000 00:25:22 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e7L7PLQ12357; Mon, 21 Aug 2000 00:25:21 -0700 (PDT) Date: Mon, 21 Aug 2000 00:25:21 -0700 From: Alfred Perlstein To: Billy Cc: freebsd-smp@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: My System Hangs/Deadlock? Message-ID: <20000821002520.I4854@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from billy@speakeasy.org on Sun, Aug 20, 2000 at 11:03:32PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Billy [000820 23:03] wrote: > > Whenever I do some intensive work, my computer will lock up. I still run a serial console and enable "break to debugger" see here: http://www.freebsd.org/handbook/kerneldebug.html get a traceback. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 0:43:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bart.acs.nmu.edu (bart.acs.nmu.edu [198.110.193.8]) by hub.freebsd.org (Postfix) with ESMTP id EB52237B423 for ; Mon, 21 Aug 2000 00:43:25 -0700 (PDT) Received: from eward3 (ADMPM322.NMU.EDU [198.110.207.37]) by bart.acs.nmu.edu (8.11.0/8.11.0) with SMTP id e7L7h8Z19128; Mon, 21 Aug 2000 03:43:22 -0400 (EDT) From: Chris Jesseman Date: Mon, 21 Aug 2000 07:44:12 GMT Message-ID: <20000821.7441229@mis.configured.host> Subject: Re: My System Hangs/Deadlock? To: Billy , freebsd-stable@FreeBSD.ORG In-Reply-To: References: X-Mailer: Mozilla/3.0 (compatible; StarOffice/5.2;Win32) X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I get similar results when I enable QUOTAs on my kernel. When I recompil= e=20 without quotas it don't lockup. I have a dual MB but only one slot=20 filled, SCSI, 4.1-STABLE. In the mean time, I operate without quotas, bu= t=20 eventually I will have to get them in place. My question: should I start= =20 looking at hardware or software configuration first? -Chris >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 8/21/00, 2:03:32 AM, Billy wrote regarding My=20= System Hangs/Deadlock?: > I am currently experiencing problems with my FreeBSD system. I just > recently go in my dual celeron/abit box in and have just started to > use it. I am experiencing a strange problem I've never seen before. > Whenever I do some intensive work, my computer will lock up. I still= > see my terminal screen, but it will accept no keyboard/mouse/network > input. It won't even return attempted network connections, it just > sits there dead for all intents and purposes and will stay like this > for as long as I leave it(the longest being ~24H). I have to do a > hard reset to reboot my machine, at which point it commes up fine > (usually, although I have had to fsck the disk once when I did this).= > I do have an SMP system, however this problem occurs on either SMP or= > non-SMP kernel. This also occurs with and without runnning X. > I am running 4.1-STABLE FreeBSD 4.1-STABLE with an SMP kernel. I have= > one IDE disk (DMA not used because of previous problems). I have a > fairly vanilla kernel config. All SCSI entries have been removed, as= > have device entries for devices I do not have. > It does not look like a hardware problem to me (no kernel panics, no > reboots, etc). It does look like a deadlocking problem of some kind,= > but I havn't seen anything in the mail archive or the newsgroups > recently about deadlocks (except for something unrelated I think). > If you have any ideas please let me know. It's kind of annoying for > my non-windows box to need a hard reset. > Relevant Hardware > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Dual ABit BP6 > 2 Celeron 466 PPGA > Maxtor 20GB 7200RPM Drive EIDE > -billy > 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 Aug 21 0:56:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from EI-Tiger.ChipChat.ne.jp (EI-Tiger.ChipChat.ne.jp [211.5.237.226]) by hub.freebsd.org (Postfix) with ESMTP id 745F337B43C for ; Mon, 21 Aug 2000 00:56:31 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by EI-Tiger.ChipChat.ne.jp (8.9.3/8.9.3) with ESMTP id HAA06432; Mon, 21 Aug 2000 07:56:16 GMT (envelope-from mrc@ChipChat.ne.jp) To: imp@village.org Cc: mrc@ChipChat.ne.jp, freebsd-stable@FreeBSD.ORG Subject: Re: Compact flash adaptor driver? In-Reply-To: <200008171757.LAA13217@harmony.village.org> References: <20000817205834D.mrc@ChipChat.ne.jp> <399BB7D6.DA03E7D6@cequrux.com> <200008171757.LAA13217@harmony.village.org> X-Mailer: Mew version 1.94.2 on XEmacs 21.1 (Carlsbad Caverns) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000821075615L.mrc@ChipChat.ne.jp> Date: Mon, 21 Aug 2000 07:56:15 GMT From: Marty Cawthon X-Dispatcher: imput version 20000228(IM140) Lines: 41 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Warner Losh imp> In message <20000817205834D.mrc@ChipChat.ne.jp> Marty Cawthon writes: imp> : I recently bought a SCSI device with a "Microtech" name on it. imp> : It is an external SCSI box with (1) slot for a PCCard and (1) slot for "Smartmedia". imp> : I remove the "Compact Flash" from my camera and put it in a PC-Card and mount it imp> : just like a SCSI "da" type device. imp> imp> Now that's cool. imp> imp> : I have also verified that it works with a "Smartmedia" chip from a Ricoh digital imp> : camera. I can mount both PC-Card and Smartmedia devices at the same time. Read imp> : (and write, I suppose) JPG files. imp> : imp> : I bought this device about 6 weeks ago, and at the time I learned that a similar imp> : model is available with a USB interface. The SCSI device cost about US$250.00. imp> : imp> : Thus far I am pleased with the operation and versatility that this device provides. imp> : I am not related or involved in the manufacture or marketing of the SCSI device, just imp> : a happy "MS-Free" FreeBSD user. imp> imp> Hmmm, do you have a pointer to this device? I'd love to play with imp> one. imp> imp> Warner I bought this unit from the USA, and I am now in Japan for a visit. I don't recall exactly the vendor that I bought my unit from. My receipt is filed in the USA and my secretary could not locate it. I did find the manufacturers homepage: http://www.microtechint.com/ From that URL you can see their many products and then do a search to find many of the vendors selling them. Good luck and "Happy Photos!" Marty Cawthon ChipChat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 1: 8:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from moon.harmonic.co.il (moon.harmonic.co.il [192.116.140.65]) by hub.freebsd.org (Postfix) with ESMTP id B3F3337B423 for ; Mon, 21 Aug 2000 01:08:44 -0700 (PDT) Received: (from nobody@localhost) by moon.harmonic.co.il (8.9.3/8.9.3) id LAA20766; Mon, 21 Aug 2000 11:07:42 +0300 To: Kevin Oberman Subject: Re: Crystal Semi (pcm) Audio card probing problem Message-ID: <966845262.39a0e34e8ebd2@webmail.harmonic.co.il> Date: Mon, 21 Aug 2000 11:07:42 +0300 From: Roman Shterenzon Cc: References: <200008192205.e7JM59U18356@ptavv.es.net> In-Reply-To: <200008192205.e7JM59U18356@ptavv.es.net> MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.0-pre13 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Kevin Oberman : > This may be related to the problem reported in the "pcm0 play interrupt > timeout, channel dead" thread. The problem in that the Crystal Audio > sound card on my ThinkPad 600E is inconsistently probed. The result is > that it is sometimes pcm0 and sometimes pcm1. > > If I get this from my device probe, the CS423x is pcm1: > csa0: mem > 0x50000000-0x500fffff,0x50100000-0x50100fff irq 11 at device 6.0 on pci0 > pcm0: on csa0 > pcm0: ac97 codec invalid or not present (id == 0) > device_probe_and_attach: pcm0 attach returned 6 > pcm1: at port 0x530-0x537,0x388-0x38b,0x220-0x233 irq 5 drq > 1,0 on isa0 > > But, it it probes like this, the "real" sound device is pcm0: > csa0: mem > 0x50000000-0x500fffff,0x50100000-0x50100fff irq 11 at device 6.0 on pci0 > device_probe_and_attach: csa0 attach returned 6 > pcm0: at port 0x530-0x537,0x388-0x38b,0x220-0x233 irq 5 > drq 1,0 on isa0 > > It seems about 50/50 on which way it probes for any given reboot. Of > course, every time it flips, I need to log in a s root and switch the > device over. This is at least a bit of a pain. > > Has anyone got an explanation of why this happens and if there is a > chance of getting it fixed? It bothers me when my system acts in a > non-deterministic fashion in something that should be as repeatable as > a device probe! It also wastes irq 11 in the first case and I have a > tight IRQ situation on that system, in any case. > > It's been doing this since I upgraded to 4.0-Stable about a month > after 4.0 was released and about three days after Xircom Ethernet > support went in. It may have been doing it under 3.4, but I never used > the audio, so I really don't know. > I have exactly the same problem on my 600E, and if you dig the mailing list, there is my mail (from previuos week I think). I ended up with making small script which does it for me. Seems that it's rather hardware "feature" than FreeBSD issue. I noticed that it usually happends if I boot from NT. When I poweron the computer in FreeBSD mode, it usually pcm1 and it works. Tell me, does lmmon work on your computer with device intpm device smbus device smb ? Mine doesn't work. Another "feature" of this thinkpad is that I couldn't manage to use "serial port", "modem" and "IrCOMM" at the same time, it doesn't have enought interrupts, and from what I understood sio driver doesn't support irq sharing on different devices. I think FreeBSD doesn't support this at all. I'm trying to port linux' tpctl (thinkpad control tool) to freebsd. It already compiles, now I'll need to use /dev/io instead of their module I guess. Does anyone ever tried to do it before? --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 1:27:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from citadel.cequrux.com (citadel.cequrux.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id 98F2537B424 for ; Mon, 21 Aug 2000 01:27:26 -0700 (PDT) Received: (from nobody@localhost) by citadel.cequrux.com (8.8.8/8.6.9) id KAA29147; Mon, 21 Aug 2000 10:26:03 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 29145; Mon Aug 21 10:25:49 2000 Message-ID: <39A0E829.B183E24C@cequrux.com> Date: Mon, 21 Aug 2000 10:28:25 +0200 From: Graham Wheeler Organization: Cequrux Technologies X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 2.2.8-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Randy Primeaux Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ps2 mouse errors (solution) References: <200008182038.NAA10998@relay.ultimanet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Randy Primeaux wrote: > > In my opinion, I do not see this as a flaw in psm, as the flag is > documented in the man page, and FreeBSD psm is not the only software > with this issue. Other mouse software, on other OS platforms, also > lose ps/2 sync through a keyboard-video-mouse switch. [Sigh] I'll say it again. There are TWO separate problems here, both of which will manifest as lost sync and the `out-of-sync' error message. One of them is due to the use of KVM boxes. The other isn't - it occurs, for example, on my Compaq laptop using the built-in touchpad, and has affected other people as well. I maintain that the latter is due to a bug or oversight in the psm driver, as tweaking the code in this driver has allowed me to circumvent the problem. However, my tweaks deal with the symptoms; I have not identified the underlying cause other than that it seems to be related to spurious data (rather than lost data). gram -- Dr Graham Wheeler E-mail: gram@cequrux.com Director, Research and Development WWW: http://www.cequrux.com CEQURUX Technologies Phone: +27(21)423-6065 Firewalls/VPN Specialists Fax: +27(21)424-3656 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 1:32:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from snoopy.brwn.org (intgw1.brwn.org [196.28.127.66]) by hub.freebsd.org (Postfix) with ESMTP id A97AB37B424; Mon, 21 Aug 2000 01:32:09 -0700 (PDT) Received: by snoopy.brwn.org (Postfix, from userid 1001) id E7C881D95; Mon, 21 Aug 2000 10:32:00 +0200 (SAST) Date: Mon, 21 Aug 2000 10:32:00 +0200 From: Willem Brown To: Greg Lehey Cc: FreeBSD Stable Users , FreeBSD Documenters Subject: Re: Problems making release with -STABLE? Message-ID: <20000821103200.J66585@snoopy.brwn.org> References: <20000821082923.A40941@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000821082923.A40941@wantadilla.lemis.com>; from grog@lemis.com on Mon, Aug 21, 2000 at 08:29:23AM +0930 X-Public-Key: http://willem.brwn.org/pubkey.txt X-Chat-Server: http://chat.brwn.org/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Mon, Aug 21, 2000 at 08:29:23AM +0930, Greg Lehey wrote: > Has anybody tried a make release on -STABLE lately? I've tried, and > after 8 hours I get: > > ===> de_DE.ISO_8859-1/books/handbook > install -C -o root -g wheel -m 444 book.html > usage: install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 > install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 ... > fileN directory > install -d [-v] [-g group] [-m mode] [-o owner] directory ... > *** Error code 64 > > I can go looking for the problems, but in this particular case it > hardly seems worth the trouble. > > BTW, does anybody else find it strange that we need jade to make a > release? It looks like it is trying to build sgmlformat using the chrooted copy of the ports and with all the required dependencies it ends up building a whole bunch of apps. jade gmake docbooks* w3m gnumake html-* ispell I think there is more but I don't have a log file handy. > > Greg > -- > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > Best Regards Willem Brown -- /* =============================================================== */ /* Linux, FreeBSD, NetBSD, OpenBSD. The choice is yours. */ /* =============================================================== */ No more blah, blah, blah! -- Kirk, "Miri", stardate 2713.6 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 1:39:59 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 2935A37B423; Mon, 21 Aug 2000 01:39:55 -0700 (PDT) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13Qn7K-000KBN-00; Mon, 21 Aug 2000 10:39:38 +0200 Date: Mon, 21 Aug 2000 10:39:38 +0200 From: Neil Blakey-Milner To: Greg Lehey Cc: FreeBSD Stable Users , FreeBSD Documenters Subject: Re: Problems making release with -STABLE? Message-ID: <20000821103938.A77515@mithrandr.moria.org> References: <20000821082923.A40941@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000821082923.A40941@wantadilla.lemis.com>; from grog@lemis.com on Mon, Aug 21, 2000 at 08:29:23AM +0930 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 Mon 2000-08-21 (08:29), Greg Lehey wrote: > BTW, does anybody else find it strange that we need jade to make a > release? Well, if you want documentation, it's about the only way. The release-meisters could always just install it from the generated packages, though. I believe setting "NODOC" disables the building of the docbook-based documentation in the release. Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 1:55:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from snafu.adept.org (adsl-63-201-63-44.dsl.snfc21.pacbell.net [63.201.63.44]) by hub.freebsd.org (Postfix) with ESMTP id 8498F37B424; Mon, 21 Aug 2000 01:55:01 -0700 (PDT) Received: by snafu.adept.org (Postfix, from userid 1000) id BAC5F9EE01; Mon, 21 Aug 2000 01:54:59 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by snafu.adept.org (Postfix) with ESMTP id AD2709B001; Mon, 21 Aug 2000 01:54:59 -0700 (PDT) Date: Mon, 21 Aug 2000 01:54:59 -0700 (PDT) From: Mike Hoskins To: Helge Oldach Cc: "O. Hartmann" , freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Subject: Re: SAMBA and IP filtering In-Reply-To: <200008201058.MAA28483@galaxy.de.cp.philips.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 -mrh On Sun, 20 Aug 2000, Helge Oldach wrote: > >Is anybody out here who has IP filtering (IPFIREWALL) on and has still > >full SAMBA access via NT clients? IPFW/Samba serving Win2k clients... close enough. > >I have the following problem: IP filtering is enabled and working well on > >our FBSD 4.1 box running samba. One of the first rules is to allow all traffic > >from and to the server via the local network, that means no restrictions. So... I guess you have something like: check-state allow ip from ${inet}:{$imask} to any keep-state > >many services this runs well - but not for SAMBA! It's working here... [30]root@snafu{mike}$ uname -a FreeBSD snafu.adept.org 4.1-STABLE FreeBSD 4.1-STABLE #0: Fri Aug 18 20:30:33 PDT 2000 mike@snafu.adept.org:/usr/src/sys/compile/SNAFU i386 [31]root@snafu{mike}$ pkg_info|grep samba samba-2.0.7 A free SMB and CIFS client and server for UNIX > >When trying to access a ip-filtering SAMBA server, I see its icon in the > >network neightborhood environment, but when clicking on its icon, I get the > >error message "Access denied, network path not found" after a while. Stopping > >Ip-filtering solves the problem, but that is not the right solution, I think. > >My question is, how to solve this problem. Are you running from inetd, or as daemons? What's your smb.conf file look like? Have you tried firing up a sniffer to see exactly what's going on when you '[click] on its icon'? -mrh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 1:56:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from snafu.adept.org (adsl-63-201-63-44.dsl.snfc21.pacbell.net [63.201.63.44]) by hub.freebsd.org (Postfix) with ESMTP id B9FA637B423 for ; Mon, 21 Aug 2000 01:56:57 -0700 (PDT) Received: by snafu.adept.org (Postfix, from userid 1000) id 9A9679EE01; Mon, 21 Aug 2000 01:56:56 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by snafu.adept.org (Postfix) with ESMTP id 8FC629B001; Mon, 21 Aug 2000 01:56:56 -0700 (PDT) Date: Mon, 21 Aug 2000 01:56:56 -0700 (PDT) From: Mike Hoskins To: Jonathan Defries Cc: freebsd-stable@freebsd.org Subject: Re: Password problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Aug 2000, Jonathan Defries wrote: > If I run the passwd command, it takes nearly a minute to be prompted > for the password. Could anyone suggest what to look for to try and > solve this please? Hmm. Last time I experienced something like this, I had ~20k users in /etc/passwd on 3.0-CURRENT (I belive it was). Don't ask why. ;) -mrh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 2: 0:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by hub.freebsd.org (Postfix) with ESMTP id F32A637B422 for ; Mon, 21 Aug 2000 02:00:43 -0700 (PDT) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.10.0/jtpda-5.3.3) with ESMTP id e7L90h959379 for ; Mon, 21 Aug 2000 11:00:43 +0200 (CEST) Received: from rose.lpthe.jussieu.fr ([134.157.10.102]) by parthe.lpthe.jussieu.fr (8.9.1a/jtpda-5.3.1) with ESMTP id LAA07335 for ; Mon, 21 Aug 2000 11:00:42 +0200 (MET DST) Received: (from michel@localhost) by rose.lpthe.jussieu.fr (8.9.3/8.9.3) id JAA00429 for freebsd-stable@FreeBSD.ORG; Mon, 21 Aug 2000 09:14:53 +0200 (CEST) (envelope-from michel) Date: Mon, 21 Aug 2000 09:14:53 +0200 From: Michel Talon To: freebsd-stable@FreeBSD.ORG Subject: Re: My System Hangs/Deadlock? Message-ID: <20000821091453.A399@lpthe.jussieu.fr> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 20, 2000 at 11:03:32PM -0700, Billy wrote: > I am currently experiencing problems with my FreeBSD system. I just > recently go in my dual celeron/abit box in and have just started to > use it. I am experiencing a strange problem I've never seen before. > > Whenever I do some intensive work, my computer will lock up. I still These cards support easy overclocking, no? Perhaps you could check cooling, notably the fans on the processors or even general cooling of the box. I have seen several times machines locking up just like yours, without any message. Each time it was a broken fan. -- Michel Talon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 3:54: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from teapot16.domain4.bigpond.com (teapot16.domain4.bigpond.com [139.134.5.164]) by hub.freebsd.org (Postfix) with SMTP id 6364C37B423 for ; Mon, 21 Aug 2000 03:54:05 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by teapot16.domain4.bigpond.com (NTMail 3.02.13) with ESMTP id ga216274 for ; Mon, 21 Aug 2000 20:43:33 +1000 Received: from WEBH-T-009-p-98-90.tmns.net.au ([139.134.98.90]) by mail4.bigpond.com (Claudes-Emergent-MailRouter V2.9 7/15667757); 21 Aug 2000 20:43:32 Message-ID: <39A1082B.40074134@echidna.stu.cowan.edu.au> Date: Mon, 21 Aug 2000 18:44:59 +0800 From: Trent Nelson X-Mailer: Mozilla 4.74 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Michael Matsumura Cc: freebsd-stable@FreeBSD.ORG Subject: Re: burncd... References: <20000818171043.B1936@jupiter.limit.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Matsumura wrote: > [root:~]# nice -20 burncd -s 2 -f /dev/acd1c data /usr/backup.iso fixate ^^^ You're running 'burncd' at the lowest possible priority (man nice(1)). Try `nice --20 ...'. > Michael Matsumura > michael@limit.org Regards, Trent. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 5:39:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from limit.org (limit.org [216.102.231.2]) by hub.freebsd.org (Postfix) with ESMTP id C7C5037B424 for ; Mon, 21 Aug 2000 05:39:19 -0700 (PDT) Received: (from michael@localhost) by limit.org (8.9.3/8.9.3) id FAA21849 for freebsd-stable@freebsd.org; Mon, 21 Aug 2000 05:38:57 -0700 (PDT) (envelope-from michael) Date: Mon, 21 Aug 2000 05:38:57 -0700 From: Michael Matsumura To: freebsd-stable@freebsd.org Subject: Re: burncd... Message-ID: <20000821053857.A21819@jupiter.limit.org> References: <20000818171043.B1936@jupiter.limit.org> <39A1082B.40074134@echidna.stu.cowan.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <39A1082B.40074134@echidna.stu.cowan.edu.au>; from tpnelson@echidna.stu.cowan.edu.au on Mon, Aug 21, 2000 at 06:44:59PM +0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is using tcsh, so it has its own 'nice' command... On Mon, Aug 21, 2000 at 06:44:59PM +0800, Trent Nelson wrote: > > > Michael Matsumura wrote: > > > [root:~]# nice -20 burncd -s 2 -f /dev/acd1c data /usr/backup.iso fixate > ^^^ > > You're running 'burncd' at the lowest possible priority (man nice(1)). > Try `nice --20 ...'. > > > Michael Matsumura > > michael@limit.org > > Regards, > > Trent. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Michael Matsumura michael@limit.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 6:36:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from qmail.corpex.net (qmail.corpex.net [195.153.247.40]) by hub.freebsd.org (Postfix) with SMTP id 34BDC37B423 for ; Mon, 21 Aug 2000 06:36:54 -0700 (PDT) Received: (qmail 52410 invoked from network); 21 Aug 2000 13:39:19 -0000 Received: from perseus.corpex.net (HELO perseus) (195.153.247.226) by qmail.corpex.net with SMTP; 21 Aug 2000 13:39:19 -0000 From: "Jonathan Defries" To: "Freebsd-Stable@Freebsd. Org" Subject: Too many open files Date: Mon, 21 Aug 2000 14:36:52 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I'm trying to run a caching nameserver on one of my web servers and it keeps complaining: socket(SOCK_DGRAM): Too many open files I have 4 servers with identical hardware, all running 3.5-STABLE with the same sort of loads on each, but this is the only one it is happening on. What's the best thing to do to try and alleviate this? I have maxusers set at 256, I've seen mention of a new kernel with a couple of extra options, would this be the way to go? - Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 6:42:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bbnrel4.net.external.hp.com (bbnrel4.net.external.hp.com [155.208.254.68]) by hub.freebsd.org (Postfix) with ESMTP id D78D637B42C for ; Mon, 21 Aug 2000 06:42:10 -0700 (PDT) Received: from hpcpbla.bri.hp.com (hpcpbla.bri.hp.com [15.144.112.65]) by bbnrel4.net.external.hp.com (Postfix) with ESMTP id 7499D135C0; Mon, 21 Aug 2000 15:42:03 +0200 (METDST) Received: from sse0691.bri.hp.com (sse0691.bri.hp.com [15.144.0.53]) by hpcpbla.bri.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.0) with ESMTP id OAA05669; Mon, 21 Aug 2000 14:42:01 +0100 (BST) Received: (from steve@localhost) by sse0691.bri.hp.com (8.9.3/8.9.3) id OAA44719; Mon, 21 Aug 2000 14:44:56 +0100 (BST) (envelope-from steve) Date: Mon, 21 Aug 2000 14:44:56 +0100 From: Steve Roome To: Matthieu Pasini Cc: si@mystery-machine.com, freebsd-stable@freebsd.org Subject: Re: The kernel freeze when initializing my ELSA MicroLink ISDN/PCI ... Message-ID: <20000821144456.A44445@moose.bri.hp.com> Mail-Followup-To: Steve Roome , Matthieu Pasini , si@mystery-machine.com, freebsd-stable@freebsd.org References: <001101c00941$6178ba00$56dd24c3@spoutnik> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <001101c00941$6178ba00$56dd24c3@spoutnik>; from mpasini@club-internet.fr on Fri, Aug 18, 2000 at 08:23:17PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 18, 2000 at 08:23:17PM +0200, Matthieu Pasini wrote: > Hello , > I compiled the kernel with the following code inside : > **************************************** > options ELSA_QS1PCI > device isic0 > pseudo-device "i4bq921" > pseudo-device "i4bq931" > pseudo-device "i4b" > pseudo-device "i4btrc" 4 > pseudo-device "i4bctl" > pseudo-device "i4brbch" 4 > pseudo-device "i4btel" 4 > pseudo-device "i4bipr" 4 > pseudo-device "i4bisppp" 4 > pseudo-device sppp4 > options IPR_VJ > ************************************************** > > And the kernel freeze when it reach the initialization of the card ..., it says me : > *************************************** > isic0: port ..... > isic0: Error, IPAC version 2 unknow > Fatal trap 12 : page fault while in kernel mode ... > *************************************** > And it asks me for reboot. > The problem is the same in 4.0-stable and in 4.1-stable. > If anyone have had the same problem as me or if anyone know more about what's happening, please mail me ... Look for patches on the mailing list. There's some minor changes that need to be done in /sys/i4b/layer1 (they're very minor really!), I can't be sure if they'll get rid of the panic, but they'll sort out the IPAC version 2 unknown, and I beleive they stop the panic too. I spend some of these weekend helping someone out with this problem, and frankly I've seen the patches, applied the patches and still can't quite figure out why no-one has merged them in. So if you get the patches, send-pr the changes and hopefully someone will commit them to the tree, or alternatively, if it's a new -stable you might want to get an easier set of patches from someone who's managed to get it into the tree and has access to the box still. Steve P.S. I've cc'd the guy who has a copy of the patch, so if you can't find it ask him. Sorry to hassle you Simon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 6:45:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from elend.fremde.com (elend.fremde.com [12.2.86.60]) by hub.freebsd.org (Postfix) with ESMTP id D05E137B423 for ; Mon, 21 Aug 2000 06:45:05 -0700 (PDT) Received: by elend.fremde.com (Postfix, from userid 1000) id 655EE1A083; Mon, 21 Aug 2000 09:44:59 -0400 (EDT) Date: Mon, 21 Aug 2000 09:44:59 -0400 From: oneiros To: freebsd-stable@freebsd.org Subject: ultra 160 scsi and performace Message-ID: <20000821094459.B29427@elend.fremde.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG greetings- can anyone tell me if support for the full 160mb/sec has been merged into -stable yet? after reading through the archives i found justin's patch, but i was hoping to avoid that. in short, my disk is still running at ultra-2 speeds :< many thanks, -justin da1: Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) ahc1: port 0xb000-0xb0ff mem 0xde800000-0xde800fff irq 11 at device 10.0 on pci0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 7:52: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from alpha.root-servers.ch (beta.root-servers.ch [195.49.33.19]) by hub.freebsd.org (Postfix) with SMTP id ACA3837B42C for ; Mon, 21 Aug 2000 07:52:00 -0700 (PDT) Received: (qmail 68581 invoked from network); 21 Aug 2000 14:51:59 -0000 Received: from client80-30.hispeed.ch (HELO 10.2.2.100) (62.2.80.30) by beta.root-servers.ch with SMTP; 21 Aug 2000 14:51:59 -0000 Date: Mon, 21 Aug 2000 16:53:53 +0200 From: Gabriel Ambuehl X-Mailer: The Bat! (v1.45 Beta/6) Personal Organization: BUZ Internet Services X-Priority: 3 (Normal) Message-ID: <20887676.20000821165353@buz.ch> To: Chris Cc: stable@freebsd.org Subject: Re[2]: FreeBSD 4.1-STABLE is about as stable as windows98 In-reply-To: <20000820205723.A9781@kingsqueak.org> References: <23125715669.20000820212932@buz.ch> <20000820205723.A9781@kingsqueak.org> 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 missed the start of this, but if this is VIA and UDMA66 with ICRC > errors and generally unstable fs's, count me in too. I just used sysctl > to put the drive into PIO mode to get around it for now. Not sure at what mode mines are running (most likely UDMA 33 as I can't use normal 80pin UDMA 66 cables for design reasons but I also don't care. I don't know of any IDE drive which can even do 33Mbyte/s) but as said, never had such problems in the last three months. Neither with 4STABLE nor with 4.1 STABLE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 8: 1:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from srcso.globis.ru (globis.ru [212.248.80.7]) by hub.freebsd.org (Postfix) with ESMTP id AD49237B422 for ; Mon, 21 Aug 2000 08:01:40 -0700 (PDT) Received: from raduga.dyndns.org (raduga.sochi.net [212.248.82.76]) by srcso.globis.ru (8.9.3/8.9.3) with ESMTP id TAA01390 for ; Mon, 21 Aug 2000 19:16:23 +0400 (MSD) (envelope-from igor@raduga.dyndns.org) Received: (from igor@localhost) by raduga.dyndns.org (8.10.0/8.10.0) id e7LF1Mv23809 for freebsd-stable@freebsd.org; Mon, 21 Aug 2000 19:01:22 +0400 Date: Mon, 21 Aug 2000 19:01:22 +0400 From: Igor Roboul To: freebsd-stable@freebsd.org Subject: make installworld fails Message-ID: <20000821190122.A23639@linux.rainbow> Reply-To: igorr@crosswinds.net Mail-Followup-To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i X-Operating-System: Linux linux.rainbow 2.2.14-plus-SMP X-Best-Window-Manager: Window Maker (www.windowmaker.org) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I have cvsuped FreeBSD 4.1 today and "make installworld" fails complaining that jail.ps is not found. I have done "make -k installworld" but I think that this is not very correct. Sorry for my bad English :-( -- Igor Roboul, Unix System Administrator & Programmer @ sanatorium "Raduga" http://www.brainbench.com/transcript.jsp?pid=304744 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 8:49:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ntua.gr (achilles.noc.ntua.gr [147.102.222.210]) by hub.freebsd.org (Postfix) with ESMTP id A103C37B424 for ; Mon, 21 Aug 2000 08:49:03 -0700 (PDT) Received: from netmode.ece.ntua.gr (dolly.netmode.ece.ntua.gr [147.102.13.10]) by ntua.gr (8.9.3/8.9.3) with ESMTP id SAA29801; Mon, 21 Aug 2000 18:48:58 +0300 (EET DST) Received: by netmode.ece.ntua.gr (Postfix, from userid 410) id 8E9FC85C3; Mon, 21 Aug 2000 18:34:49 +0300 (EET DST) Date: Mon, 21 Aug 2000 18:34:49 +0300 From: Panagiotis Astithas To: Shawn Barnhart Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ipfilter v. ipfw Message-ID: <20000821183449.B20824@netmode.ece.ntua.gr> Reply-To: past@netmode.ntua.gr Mail-Followup-To: Shawn Barnhart , freebsd-stable@FreeBSD.ORG References: <000f01c00939$0dd7b480$b8209fc0@marlowe><20000818141256.A29131@pir.net> <14749.32249.842000.944007@jef-nt.mdacc.tmc.edu> <002301c00946$67bd8c10$b8209fc0@marlowe> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <002301c00946$67bd8c10$b8209fc0@marlowe>; from swb@grasslake.net on Fri, Aug 18, 2000 at 01:59:14PM -0500 X-Organizational-Unit: Network Management and Optimal Design Laboratory X-Organization: National Technical University of Athens, GREECE X-Work-Phone: +30-1-772-1-450 X-Work-FAX: +30-1-772-1-452 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 18, 2000 at 01:59:14PM -0500, Shawn Barnhart wrote: > While I'm creating a potential religious debate, does ipfilter allow you > to output your rules in a format that enables them to be read in by ipf? > In other words, can you do ipf list > foo and then do ipf add -f foo ? > > One thing that bugs me about ipfw is that I've ended up rolling my own > script to rebuild my firewall rules at boot time from a file created by > doing ipfw list. > > (I keep thinking that there must be a smarter way to do this, but I'm > either too lazy or blind to see it). What I do is specify firewall_type="/etc/firewall.rules" in rc.conf, and add the rules in there. -past To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 9: 1:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from absinthe2.dyndns.org (adsl-63-192-101-92.dsl.chic01.pacbell.net [63.192.101.92]) by hub.freebsd.org (Postfix) with ESMTP id 0070C37B43F for ; Mon, 21 Aug 2000 09:01:38 -0700 (PDT) Received: (from fred@localhost) by absinthe2.dyndns.org (8.9.3/8.9.3) id JAA34360; Mon, 21 Aug 2000 09:01:31 -0700 (PDT) (envelope-from fred) Date: Mon, 21 Aug 2000 09:01:30 -0700 From: Fred Condo To: Jonathan Defries Cc: freebsd-stable@FreeBSD.org Subject: Re: Too many open files Message-ID: <20000821090130.A33288@absinthe.condo.chico.ca.us> Mail-Followup-To: Jonathan Defries , freebsd-stable@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jonathan@corpex.com on Mon, Aug 21, 2000 at 02:36:52PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 21, 2000 at 02:36:52PM +0100, Jonathan Defries wrote: > Hi all, > > I'm trying to run a caching nameserver on one of my web servers > and it keeps complaining: > > socket(SOCK_DGRAM): Too many open files > > I have 4 servers with identical hardware, all running 3.5-STABLE > with the same sort of loads on each, but this is the only one it > is happening on. > > What's the best thing to do to try and alleviate this? I have > maxusers set at 256, I've seen mention of a new kernel with a > couple of extra options, would this be the way to go? > > - Jonathan > > This should probably be on -questions, but... it may be that your process is running out of open files, not your kernel. See man ulimit or man login.conf. -- Fred Condo + fred@condo.chico.ca.us Not since Tom Hanks won an Oscar has there been that much acting in Philadelphia. -- Sen. Joe Lieberman, about the Republican Convention. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 9:34:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from alpha.root-servers.ch (beta.root-servers.ch [195.49.33.19]) by hub.freebsd.org (Postfix) with SMTP id 8EFFD37B424 for ; Mon, 21 Aug 2000 09:34:17 -0700 (PDT) Received: (qmail 97665 invoked from network); 21 Aug 2000 16:34:15 -0000 Received: from client80-30.hispeed.ch (HELO 10.2.2.100) (62.2.80.30) by beta.root-servers.ch with SMTP; 21 Aug 2000 16:34:15 -0000 Date: Mon, 21 Aug 2000 18:36:11 +0200 From: Gabriel Ambuehl X-Mailer: The Bat! (v1.45 Beta/6) Personal Organization: BUZ Internet Services X-Priority: 3 (Normal) Message-ID: <1887025101.20000821183611@buz.ch> To: Luke Hollins Cc: stable@freebsd.org Subject: Re[4]: FreeBSD 4.1-STABLE is about as stable as windows98 In-reply-To: References: 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 Luke, Monday, August 21, 2000, 5:59:54 PM, you wrote: > I am using: > FreeBSD 4.1-STABLE #0: Mon Aug 7 19:35:50 > atapci0: port 0xb800-0xb80f at device 4.1 on > pci0 > ad0: 19574MB [39770/16/63] at ata0-master using UDMA66 > with an 80 pin cable > I have never had any problems or errors with them We've got several of them (VIA MVP4, 128 MB SDRAM, I assume it's PC100): atapci0: port 0xd000-0xd00f at device 7.1 on pci0 ad0: 19574MB [39770/16/63] at ata0-master using UDMA66 (exactly the same config as it seems, we're using very short (<10cm) UDMA33 cables and it works like a charm) JFTR, another box (Asus P5A, Mach64, 128 MB PC133 SDRAM): atapci0: port 0xb400-0xb40f irq 0 at device 15.0 on pci0 ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable ad0: 26105MB [53040/16/63] at ata0-master using UDMA33 ad2: 26105MB [53040/16/63] at ata1-master using UDMA33 (this uses a standard (40cm?) UDMA33 cables) All are running just fine, the ALi Chipset, however, is somewhat slower than the VIA ones. Best regards, Gabriel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 9:39: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wyattearp.stanford.edu (wyattearp.Stanford.EDU [171.66.63.23]) by hub.freebsd.org (Postfix) with ESMTP id 2142F37B43E for ; Mon, 21 Aug 2000 09:39:00 -0700 (PDT) Received: (from richw@localhost) by wyattearp.stanford.edu (8.9.3/8.9.3) id JAA70746; Mon, 21 Aug 2000 09:38:22 -0700 (PDT) (envelope-from richw) Date: Mon, 21 Aug 2000 09:38:22 -0700 (PDT) From: Rich Wales X-Sender: richw@wyattearp.stanford.edu To: freebsd-stable@freebsd.org Subject: Re: ipfilter v. ipfw Message-ID: <200008211669319.richw@wyattearp.stanford.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My earlier question seems to have been lost amidst the debate about ipfilter vs. ipfw, so please forgive my restating it. I have a kernel (4.1-RELEASE) with both IPFIREWALL and IPFILTER support enabled. However, I am currently using only "ipfw" commands to set up my firewall; I'm not using any "ipf" commands at all. Is there any reason to expect a system configured in this way will be inherently unstable, simply because both firewall schemes have been included in the kernel, even though only one of them is being used? Perhaps I'll end up taking out the IPFILTER kernel support, just on principle, but I feel the question is still worth asking. Rich Wales richw@webcom.com http://www.webcom.com/richw/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 10: 4: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wyattearp.stanford.edu (wyattearp.Stanford.EDU [171.66.63.23]) by hub.freebsd.org (Postfix) with ESMTP id A706137B424 for ; Mon, 21 Aug 2000 10:04:00 -0700 (PDT) Received: (from richw@localhost) by wyattearp.stanford.edu (8.9.3/8.9.3) id KAA73125; Mon, 21 Aug 2000 10:03:28 -0700 (PDT) (envelope-from richw) Date: Mon, 21 Aug 2000 10:03:28 -0700 (PDT) From: Rich Wales X-Sender: richw@wyattearp.stanford.edu To: freebsd-stable@freebsd.org Subject: ATA66 cable being ignored? Message-ID: <200008211670886.richw@wyattearp.stanford.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My new Dell OptiPlex GX300 (running 4.1-RELEASE) came with an 80-wire ATA cable. I added a second drive and am using this cable for both drives. However, the kernel fails to recognize the cable and is limit- ing DMA speed accordingly. Any ideas? See below for the relevant portion of the "boot -v" output. I note the "cblid=0" value -- leading me to wonder if the problem might possibly be with the integrated ATA controller on the motherboard not sensing or reporting the cable properly. This is an 800-MHz Pentium III system, though, so I find it a bit hard to believe that it isn't UDMA66-capable. BTW, in the line which claims I have a non-ATA66 compliant cable, I believe the preferred spelling is "limited", with just one T (not two). Rich Wales richw@webcom.com http://www.webcom.com/richw/ ======================================================================== . . . atapci0: port 0xffa0-0xffaf at device 31.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xffa0 ata0: mask=03 status0=50 status1=50 ata0: mask=03 status0=50 status1=50 ata0: devices = 0x3 ata0: at 0x1f0 irq 14 on atapci0 . . . ata0-master: DMA limitted to UDMA33, non-ATA66 compliant cable ata0-master: success setting up UDMA2 mode on ICH chip ad0: ATA-5 disk at ata0 as master ad0: 14324MB (29336832 sectors), 29104 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad0: piomode=4 dmamode=2 udmamode=4 cblid=0 Creating DISK ad0 Creating DISK wd0 ata0-slave: success setting up UDMA2 mode on ICH chip ad1: ATA-4 disk at ata0 as slave ad1: 9617MB (19696320 sectors), 19540 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, UDMA33 ad1: piomode=4 dmamode=2 udmamode=2 cblid=0 Creating DISK ad1 Creating DISK wd1 ======================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 10:40:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id DFC9337B423 for ; Mon, 21 Aug 2000 10:40:54 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e7LHepF69416; Mon, 21 Aug 2000 10:40:52 -0700 (PDT) Date: Mon, 21 Aug 2000 10:40:51 -0700 (PDT) From: Doug White To: Jonathan Defries Cc: "Freebsd-Stable@Freebsd. Org" Subject: Re: Too many open files 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, 21 Aug 2000, Jonathan Defries wrote: > Hi all, > > I'm trying to run a caching nameserver on one of my web servers > and it keeps complaining: > > socket(SOCK_DGRAM): Too many open files In addition to the login.conf/limits hint, check the sysctl kern.maxfiles and kern.maxfilesperproc > What's the best thing to do to try and alleviate this? I have > maxusers set at 256, I've seen mention of a new kernel with a > couple of extra options, would this be the way to go? Note that bind opens two listening sockets per configured IP address. If you have several aliases on one interface it'll open 2*#IPs and probably hit the limit. You probably want to limit named to binding to specific IPs; see the 'listen-on' option, e.g. options { listen-on { 127.0.0.1; 192.168.1.2; }; }; Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 11:19: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from s1-c2.cnmnetwork.com (s1-c2.cnmnetwork.com [209.163.64.71]) by hub.freebsd.org (Postfix) with SMTP id 843CC37B422 for ; Mon, 21 Aug 2000 11:19:00 -0700 (PDT) Received: (qmail 2330 invoked from network); 21 Aug 2000 11:18:43 -0700 Received: from prometheus.cnmnetwork.com (HELO cnmnetwork.com) (irc@209.79.28.5) by s1-c2.cnmnetwork.com with SMTP; 21 Aug 2000 11:18:43 -0700 Message-ID: <39A171E8.F9BAAE26@cnmnetwork.com> Date: Mon, 21 Aug 2000 11:16:08 -0700 From: User Gilligan X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.1-20000817-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: automated freebsd stable installs. 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 installing FreeBSD on multiple machines on a LAN. I wanted to make the install process easier by using install.cfg. Is there any documentation out there other than the sample file /usr/src/release/sysinstall/install.cfg? I'd like to see exactly what my options are and how I could customize it. Mark Lovretovich mark@cnmnetwork.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 11:55:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from laxmls02.socal.rr.com (laxmls02.socal.rr.com [24.30.163.11]) by hub.freebsd.org (Postfix) with ESMTP id E015637B42C for ; Mon, 21 Aug 2000 11:55:19 -0700 (PDT) Received: from sc-24-160-53-139.socal.rr.com (sc-24-160-53-139.socal.rr.com [24.160.53.139]) by laxmls02.socal.rr.com (8.10.1/8.10.1) with ESMTP id e7LIsYT29237 for ; Mon, 21 Aug 2000 11:54:34 -0700 (PDT) Date: Mon, 21 Aug 2000 11:55:27 -0700 (PDT) From: Zigron X-Sender: zigron@Jeremy.cerebralmaelstrom.com To: freebsd-stable@freebsd.org Subject: 4.1-STABLE and usb mice? 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 Ever since I upgraded to 4.1-STABLE (about a week and a half ago, via CVSup), i've been having trouble with my Microsoft Intellimouse Explorer. The mouse-driver seems to die/crash in situations where my HDD is rather busy, e.g. copying huge files, doing big-greps, etcetera. Here's the error messages given on the console: --- Aug 21 11:16:42 Jeremy /kernel: uhub0: port error, restarting port 2 Aug 21 11:16:43 Jeremy /kernel: ums0: at uhub0 port 2 (addr 2) disconnected Aug 21 11:16:43 Jeremy /kernel: ums0: detached Aug 21 11:16:43 Jeremy moused: unable to open /dev/ums0: Device not configured --- Then it registers a reconnection and its fine, btu then it dies again, and so on, and so forth. Currently I have two mice installed so I can at least navigate myself out of X-windows when this occurs. I'm not sure what's up :) I can not guarantee I did not have the problem before the upgrade to 4.1, since this isn't exactly always regular or consistantly reproducable (just usually), but I was running FreeBSD for a couple weeks w/o a hitch and w/ the mouse fine. Thanks for any help you can offer. :) --Stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 12: 3:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from alpha.root-servers.ch (beta.root-servers.ch [195.49.33.19]) by hub.freebsd.org (Postfix) with SMTP id D8B0937B43C for ; Mon, 21 Aug 2000 12:03:41 -0700 (PDT) Received: (qmail 38510 invoked from network); 21 Aug 2000 19:03:38 -0000 Received: from client80-30.hispeed.ch (HELO 10.2.2.100) (62.2.80.30) by beta.root-servers.ch with SMTP; 21 Aug 2000 19:03:38 -0000 Date: Mon, 21 Aug 2000 21:05:33 +0200 From: Gabriel Ambuehl X-Mailer: The Bat! (v1.45 Beta/6) Personal Organization: BUZ Internet Services X-Priority: 3 (Normal) Message-ID: <13515987398.20000821210533@buz.ch> To: stable@freebsd.org Subject: make installworld over NFS doesn't work anymore 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, the following seems to be directly related to the MFC of OpenSSL 0.95a, because it worked for use before (/usr/src and /usr/obj are mounted via NFS, maproot=root, ro) sed '/^#ifndef NO_IDEA$/,/^#endif$/d' /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/evp.h > /usr/obj/usr/src/secure/lib/libcrypto/evp.h.new cannot create /usr/obj/usr/src/secure/lib/libcrypto/evp.h.new: permission denied *** Error code 2 Stop in /usr/src/secure/lib/libcrypto. *** Error code 1 sed didn't write into the obj tree before, I think (if it did, I couldn't understand why this worked before), so redirecting the output to somewhere else (/tmp?) would perhaps help. Best regards, Gabriel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 12:10:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wireco.net (mental.wireco.net [206.107.119.3]) by hub.freebsd.org (Postfix) with SMTP id 72AC437B737 for ; Mon, 21 Aug 2000 12:10:48 -0700 (PDT) Received: (qmail 27192 invoked from network); 21 Aug 2000 19:10:44 -0000 Received: from d23.johnson-city.tn.us.wireco.net (HELO challenger) (206.107.119.212) by mental.wireco.net with SMTP; 21 Aug 2000 19:10:44 -0000 Reply-To: From: "Andrew C. Hornback" To: Cc: Subject: RE: My System Hangs/Deadlock? Date: Mon, 21 Aug 2000 15:09:17 -0400 Message-ID: <007901c00ba3$60dcc5f0$d4776bce@challenger> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 In-Reply-To: <20000821091453.A399@lpthe.jussieu.fr> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Michel Talon > Sent: Monday, August 21, 2000 3:15 AM > To: freebsd-stable@FreeBSD.ORG > Subject: Re: My System Hangs/Deadlock? > > On Sun, Aug 20, 2000 at 11:03:32PM -0700, Billy wrote: > > I am currently experiencing problems with my FreeBSD system. I just > > recently go in my dual celeron/abit box in and have just started to > > use it. I am experiencing a strange problem I've never seen before. > > > > Whenever I do some intensive work, my computer will lock > up. I still > > These cards support easy overclocking, no? Perhaps you could > check cooling, > notably the fans on the processors or even general cooling of > the box. I have > seen several times machines locking up just like yours, > without any message. > Each time it was a broken fan. I thought I'd chime in on this one... When I used to work for a former employer, our main server was a Dual Cel/500 (not overclocked since I found out that they were) on an ABit board. It had the motherboard temp sensor and everything, but hadn't been configured to use it. One day, for on apparent reason, NT Server locked up on it cold as death (yeah, I know, normal mode of operation for NT)... Anyway, in doing the post mortem of it, it happened again. Being the crafty guy I am, I ripped the case off of it (at the time, it was the only machine in the server room/my office that had a case shell on it) I watched what it was doing... neither fan on the chips were turning. To tell you how bad this place was, I was told to just remove the fans and let it go. Now that would have been intelligent... (tells you the kind of management I was working for)... At any rate, the only real remedy for the situation was to replace both heatsink/fan combos and to get the machine cooled correctly. I ended up installing about 4 fans, and building a nice little scoop that ran from the air conditioning duct work into the machine. Never overheated since then. Point of all of this... make sure your machine is happy (i.e. cool) and you'll be happy... --- Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 14:13:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id AA25837B424 for ; Mon, 21 Aug 2000 14:13:48 -0700 (PDT) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id OAA00405; Mon, 21 Aug 2000 14:13:43 -0700 Message-ID: <39A19B87.B0BD0B30@urx.com> Date: Mon, 21 Aug 2000 14:13:43 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: igorr@crosswinds.net Cc: freebsd-stable@FreeBSD.ORG Subject: Re: make installworld fails References: <20000821190122.A23639@linux.rainbow> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Igor Roboul wrote: > > Hello, > > I have cvsuped FreeBSD 4.1 today and "make installworld" fails complaining > that jail.ps is not found. > I have done "make -k installworld" but I think that this is not very correct. Hi Igor, When I read your message, I cvsup'ed 4.1-stable at 1200 PDT (1900GMT) and then, from /usr/src I did 1. make buildworld 2. make buildkernel KERNEL=JADE 3. make installkernel KERNEL=JADE 4. reboot to single user 5. make installworld 6. mergemaster 7. reboot I didn't see any errors. Kent > > Sorry for my bad English :-( > > -- > Igor Roboul, Unix System Administrator & Programmer @ sanatorium "Raduga" > http://www.brainbench.com/transcript.jsp?pid=304744 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 14:21:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6FA3537B424; Mon, 21 Aug 2000 14:21:45 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA94997; Mon, 21 Aug 2000 14:21:45 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 21 Aug 2000 14:21:45 -0700 (PDT) From: Kris Kennaway To: Gabriel Ambuehl Cc: stable@freebsd.org Subject: Re: make installworld over NFS doesn't work anymore In-Reply-To: <13515987398.20000821210533@buz.ch> 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, 21 Aug 2000, Gabriel Ambuehl wrote: > Hello, > the following seems to be directly related to the MFC of OpenSSL > 0.95a, because it worked for use before (/usr/src and /usr/obj are > mounted via NFS, maproot=root, ro) > > sed '/^#ifndef NO_IDEA$/,/^#endif$/d' /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/evp.h > /usr/obj/usr/src/secure/lib/libcrypto/evp.h.new > cannot create /usr/obj/usr/src/secure/lib/libcrypto/evp.h.new: permission denied > *** Error code 2 > > Stop in /usr/src/secure/lib/libcrypto. > *** Error code 1 Make sure you are not doing a make world with -DNOCLEAN and -DNOCLEANDIR. If the problem persists, remove your /usr/obj directory and try again. 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 Aug 21 14:48: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.tn.home.com (ha1.rdc1.tn.home.com [24.2.7.66]) by hub.freebsd.org (Postfix) with ESMTP id 7DA7937B505 for ; Mon, 21 Aug 2000 14:48:06 -0700 (PDT) Received: from RELIABLE ([24.4.115.31]) by mail.rdc1.tn.home.com (InterMail vM.4.01.02.00 201-229-116) with ESMTP id <20000821214805.CNOQ12348.mail.rdc1.tn.home.com@RELIABLE>; Mon, 21 Aug 2000 14:48:05 -0700 Date: Mon, 21 Aug 2000 17:43:12 -0400 From: williamsl@home.com X-Mailer: The Bat! (v1.45) Personal Organization: Williams Enterprises X-Priority: 3 (Normal) Message-ID: <191180538689.20000821174312@home.com> To: Rich Wales Cc: freebsd-stable@FreeBSD.ORG Subject: Re[2]: ipfilter v. ipfw In-reply-To: <200008211669319.richw@wyattearp.stanford.edu> References: <200008211669319.richw@wyattearp.stanford.edu> 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 have several machines which have both IP-Filter and IP-FireWall support compiled in and even using a mixture of both (bad form I know but I was lazy/tired when I was updating some rules) I've never had any stability issues with the boxes. --Ben Williams mailto:received@email dot com Quoting Rich Wales Monday, August 21, 2000 > My earlier question seems to have been lost amidst the debate about > ipfilter vs. ipfw, so please forgive my restating it. > I have a kernel (4.1-RELEASE) with both IPFIREWALL and IPFILTER support > enabled. However, I am currently using only "ipfw" commands to set up > my firewall; I'm not using any "ipf" commands at all. > Is there any reason to expect a system configured in this way will be > inherently unstable, simply because both firewall schemes have been > included in the kernel, even though only one of them is being used? > Perhaps I'll end up taking out the IPFILTER kernel support, just on > principle, but I feel the question is still worth asking. > Rich Wales richw@webcom.com http://www.webcom.com/richw/ > 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 Aug 21 14:59: 1 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 AC2EC37B509 for ; Mon, 21 Aug 2000 14:58:58 -0700 (PDT) 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 RAA191918; Mon, 21 Aug 2000 17:58:50 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <200008211670886.richw@wyattearp.stanford.edu> References: <200008211670886.richw@wyattearp.stanford.edu> Date: Mon, 21 Aug 2000 17:59:20 -0400 To: Rich Wales , freebsd-stable@FreeBSD.ORG From: Garance A Drosihn Subject: Re: ATA66 cable being ignored? Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:03 AM -0700 8/21/00, Rich Wales wrote: >My new Dell OptiPlex GX300 (running 4.1-RELEASE) came with an 80-wire >ATA cable. I added a second drive and am using this cable for both >drives. However, the kernel fails to recognize the cable and is limit- >ing DMA speed accordingly. Any ideas? > >See below for the relevant portion of the "boot -v" output. I note the >"cblid=0" value -- leading me to wonder if the problem might possibly >be with the integrated ATA controller on the motherboard not sensing or >reporting the cable properly. This is an 800-MHz Pentium III system, >though, so I find it a bit hard to believe that it isn't UDMA66-capable. > >======================================================================== > >. . . >atapci0: port 0xffa0-0xffaf at device >31.1 on pci0 >ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xffa0 >ata0: mask=03 status0=50 status1=50 >ata0: mask=03 status0=50 status1=50 >ata0: devices = 0x3 >ata0: at 0x1f0 irq 14 on atapci0 >. . . >ata0-master: DMA limitted to UDMA33, non-ATA66 compliant cable >ata0-master: success setting up UDMA2 mode on ICH chip > >======================================================================== For what it's worth, I have been seeing this too. In my case I have two IDE controllers, one on the motherboard, and the other a PCI card from Promise. I'm pretty sure the cable is correct, although I haven't actually ripped the machine apart again to check it... In my case, I'm running 4.1-release --- 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 Mon Aug 21 15:18:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from front002.cluster1.charter.net (24-216-159-200.hsacorp.net [24.216.159.200]) by hub.freebsd.org (Postfix) with ESMTP id C1B9937B423 for ; Mon, 21 Aug 2000 15:18:48 -0700 (PDT) Received: from [24.217.6.45] (HELO dave.uhring.com) by front002.cluster1.charter.net (CommuniGate Pro SMTP 3.2.4) with SMTP id 16133616; Mon, 21 Aug 2000 18:17:24 -0400 From: Dave Uhring To: Zigron , freebsd-stable@freebsd.org Subject: Re: 4.1-STABLE and usb mice? Date: Mon, 21 Aug 2000 17:11:08 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: In-Reply-To: MIME-Version: 1.0 Message-Id: <00082117183801.00210@dave.uhring.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 21 Aug 2000, Zigron wrote: > Ever since I upgraded to 4.1-STABLE (about a week and a half ago, via > CVSup), i've been having trouble with my Microsoft Intellimouse > Explorer. The mouse-driver seems to die/crash in situations where my HDD > is rather busy, e.g. copying huge files, doing big-greps, etcetera. > > Here's the error messages given on the console: > > --- > > Aug 21 11:16:42 Jeremy /kernel: uhub0: port error, restarting port 2 > Aug 21 11:16:43 Jeremy /kernel: ums0: at uhub0 port 2 (addr > 2) disconnected > Aug 21 11:16:43 Jeremy /kernel: ums0: detached > Aug 21 11:16:43 Jeremy moused: unable to open /dev/ums0: Device not > configured > > --- > > Then it registers a reconnection and its fine, btu then it dies again, and > so on, and so forth. Currently I have two mice installed so I can at least > navigate myself out of X-windows when this occurs. > > I'm not sure what's up :) I can not guarantee I did not have the problem > before the upgrade to 4.1, since this isn't exactly always regular or > consistantly reproducable (just usually), but I was running FreeBSD for a > couple weeks w/o a hitch and w/ the mouse fine. > > Thanks for any help you can offer. :) > > --Stephen If you still have the USB to PS/2 adapter which should have come with your mouse use the PS/2 port for the mouse and in /etc/XF86Config, use this: Section "Pointer" Protocol "IntelliMouse" Device "/dev/mouse" ZAxisMapping 4 5 EndSection Now, if you make install /usr/ports/x11/imwheel, your wheel will work, also. I use the M$ IntelliMouse w/IntelliEye and have never had a bit of problem with it in any BSD, Linux or Windows. Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 15:27:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from front001.cluster1.charter.net (24-216-159-200.hsacorp.net [24.216.159.200]) by hub.freebsd.org (Postfix) with ESMTP id E9BF837B50B for ; Mon, 21 Aug 2000 15:27:31 -0700 (PDT) Received: from [24.217.6.45] (HELO dave.uhring.com) by front001.cluster1.charter.net (CommuniGate Pro SMTP 3.2.4) with SMTP id 16324589; Mon, 21 Aug 2000 18:27:31 -0400 From: Dave Uhring To: Gabriel Ambuehl , Chris Subject: Re: Re[2]: FreeBSD 4.1-STABLE is about as stable as windows98 Date: Mon, 21 Aug 2000 17:19:49 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: stable@freebsd.org References: <20000820205723.A9781@kingsqueak.org> <20887676.20000821165353@buz.ch> In-Reply-To: <20887676.20000821165353@buz.ch> MIME-Version: 1.0 Message-Id: <00082117273002.00210@dave.uhring.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 21 Aug 2000, Gabriel Ambuehl wrote: > > I missed the start of this, but if this is VIA and UDMA66 with ICRC > > errors and generally unstable fs's, count me in too. I just used sysctl > > to put the drive into PIO mode to get around it for now. > > Not sure at what mode mines are running (most likely UDMA 33 as I > can't use normal 80pin UDMA 66 cables for design reasons but I also > don't care. I don't know of any IDE drive which can even do 33Mbyte/s) > but as said, never had such problems in the last three months. > Neither with 4STABLE nor with 4.1 STABLE. > The IDE drives may or may not be capable of such data rates, however, when 4.1-stable kept giving me thousands of those errors with VIA MVP4 chipset, I overwrote FreeBSD with Linux. Linux and OpenBSD-2.7 both use the ATA-66 capability without errors and generally show a 25%-30% increase in performance over ATA-33 measured with Bonnie. So it isn't double the speed, it's still a marked improvement. The suggestion I received regarding replacement of the 80-wire cable with a 40-wire cable is specious and non-responsive. Apparently no one in a position to be able to properly evaluate this problem cares enough even to post. Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 15:49:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.wipol.uni-bonn.de (heidi.wipol.uni-bonn.de [131.220.48.160]) by hub.freebsd.org (Postfix) with ESMTP id 5D3C237B423 for ; Mon, 21 Aug 2000 15:49:08 -0700 (PDT) Received: by mail.wipol.uni-bonn.de (Postfix, from userid 506) id 47E6222856; Tue, 22 Aug 2000 00:47:35 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.wipol.uni-bonn.de (Postfix) with SMTP id 3C6912282B for ; Tue, 22 Aug 2000 00:47:35 +0200 (CEST) Date: Tue, 22 Aug 2000 00:47:35 +0200 (CEST) From: Noel Koethe X-Sender: noel@heidi.wipol.uni-bonn.de To: freebsd-stable@freebsd.org Subject: error with make buildkernel 4.1-RC -> 4.1-release Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I made the following without errors: # cd /usr/src/ # make update # make buildworld And then: #make buildkernel KERNEL=3DBSD and got: =2E.. cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=3D2 /usr/src/sys/kern/kern_exec.c In file included from /usr/src/sys/kern/kern_exec.c:55: /usr/src/sys/vm/vm_page.h:159: warning: `PQ_CACHESIZE' redefined /usr/src/sys/vm/vm_page.h:157: warning: this is the location of the previous definition /usr/src/sys/vm/vm_page.h:161: warning: `PQ_CACHESIZE' redefined /usr/src/sys/vm/vm_page.h:159: warning: this is the location of the previous definition /usr/src/sys/vm/vm_page.h:163: warning: `PQ_CACHESIZE' redefined /usr/src/sys/vm/vm_page.h:161: warning: this is the location of the previous definition /usr/src/sys/vm/vm_page.h:165: warning: `PQ_CACHESIZE' redefined /usr/src/sys/vm/vm_page.h:163: warning: this is the location of the previous definition In file included from /usr/src/sys/kern/kern_exec.c:55: /usr/src/sys/vm/vm_page.h:158: undefined or invalid # directive /usr/src/sys/vm/vm_page.h:160: undefined or invalid # directive /usr/src/sys/vm/vm_page.h:162: undefined or invalid # directive /usr/src/sys/vm/vm_page.h:164: undefined or invalid # directive *** Error code 1 Stop in /usr/obj/usr/src/sys/BSD. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Maybe you can help me. --=20 Noch einen sch=F6nen Tag Noel K=F6the To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 16:28: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id EC1BD37B616 for ; Mon, 21 Aug 2000 16:27:53 -0700 (PDT) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id QAA00270; Mon, 21 Aug 2000 16:27:32 -0700 Message-ID: <39A1BAE4.D9AE46C@urx.com> Date: Mon, 21 Aug 2000 16:27:32 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Noel Koethe Cc: freebsd-stable@FreeBSD.ORG Subject: Re: error with make buildkernel 4.1-RC -> 4.1-release References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Noel Koethe wrote: > > Hello, > > I made the following without errors: > > # cd /usr/src/ > # make update I don't see any reason for runing a make update. > # make buildworld > > And then: > > #make buildkernel KERNEL=BSD > > and got: > > ... > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys > -I/usr/src/sys/../include -D_KERNEL -include opt_global.h -elf > -mpreferred-stack-boundary=2 /usr/src/sys/kern/kern_exec.c > In file included from /usr/src/sys/kern/kern_exec.c:55: > /usr/src/sys/vm/vm_page.h:159: warning: `PQ_CACHESIZE' redefined > /usr/src/sys/vm/vm_page.h:157: warning: this is the location of the > previous definition > /usr/src/sys/vm/vm_page.h:161: warning: `PQ_CACHESIZE' redefined > /usr/src/sys/vm/vm_page.h:159: warning: this is the location of the > previous definition > /usr/src/sys/vm/vm_page.h:163: warning: `PQ_CACHESIZE' redefined I starte my cvsup at 1200 PDT (1900GMT) and did the following steps without any problems. BTW, I went from 4.1RC to 4.1-r to 4.1Stable using cvsup. 1. make buildworld 2. make buildkernel KERNEL=JADE 3. make installkernel KERNEL=JADE 4. reboot to single user 5. make installworld 6. mergemaster 7. reboot You might attach your cvsup-file and your BSD config file. Someone might see something. Kent -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 16:38:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from genius.systems.pavilion.net (genesis.tao.org.uk [194.242.131.254]) by hub.freebsd.org (Postfix) with ESMTP id 2B94F37B424 for ; Mon, 21 Aug 2000 16:38:36 -0700 (PDT) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id 7E1E79B07; Tue, 22 Aug 2000 00:38:30 +0100 (BST) Date: Tue, 22 Aug 2000 00:38:30 +0100 From: Josef Karthauser To: Kent Stewart Cc: Noel Koethe , freebsd-stable@FreeBSD.ORG Subject: Re: error with make buildkernel 4.1-RC -> 4.1-release Message-ID: <20000822003830.A1248@pavilion.net> Mail-Followup-To: Josef Karthauser , Kent Stewart , Noel Koethe , freebsd-stable@FreeBSD.ORG References: <39A1BAE4.D9AE46C@urx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39A1BAE4.D9AE46C@urx.com>; from kstewart@urx.com on Mon, Aug 21, 2000 at 04:27:32PM -0700 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 21, 2000 at 04:27:32PM -0700, Kent Stewart wrote: > > > Noel Koethe wrote: > > > > Hello, > > > > I made the following without errors: > > > > # cd /usr/src/ > > # make update > > I don't see any reason for runing a make update. Make update does a 'cvsup' if configured correctly in /etc/make.conf. It does nothing unless the make.conf parameters have been tweaked. Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 16:47:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dns.comrax.com (dns.comrax.com [194.90.246.124]) by hub.freebsd.org (Postfix) with ESMTP id C043037B618 for ; Mon, 21 Aug 2000 16:47:10 -0700 (PDT) Received: by dns.comrax.com (Postfix, from userid 100) id 9DF451C99E; Tue, 22 Aug 2000 02:47:05 +0300 (IDT) Received: from localhost (localhost [127.0.0.1]) by dns.comrax.com (Postfix) with ESMTP id 8516316E22 for ; Tue, 22 Aug 2000 02:47:05 +0300 (IDT) Date: Tue, 22 Aug 2000 02:47:05 +0300 (IDT) From: To: freebsd-stable@FreeBSD.ORG Subject: DoS attacks and FreeBSD. 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 all, One of our sites was a target for a DoS attempt tonight. The attempt failed. I have ipfw running on the server, and managed to block the IP's in question in time. My question is: suppose I was not near the PC at the time of the incident, how can I configure ipfw to automatically block cnnections originating from any IP and that is continuous in a suspecious manner? (let's say 50 concurrent connections to port 80 every second.) Is this possible in FreeBSD or/and in ipfw? Would like to know how... Thanks in advance. Noor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 16:59:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from merlin.prod.itd.earthlink.net (merlin.prod.itd.earthlink.net [207.217.120.156]) by hub.freebsd.org (Postfix) with ESMTP id 9144637B422 for ; Mon, 21 Aug 2000 16:59:19 -0700 (PDT) Received: from earthlink.net (1Cust86.tnt8.everett2.wa.da.uu.net [63.24.202.86]) by merlin.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id QAA05804; Mon, 21 Aug 2000 16:59:17 -0700 (PDT) Received: (from odyseus2000@localhost) by earthlink.net (8.9.3/8.9.3) id QAA79571; Mon, 21 Aug 2000 16:58:57 -0700 (PDT) (envelope-from odyseus2000) Date: Mon, 21 Aug 2000 16:58:56 -0700 From: David Burton To: Rich Wales , freebsd-stable@freebsd.org Subject: Re: ATA66 cable being ignored? Message-ID: <20000821165856.A79469@slick.earthlink.net> References: <200008211670886.richw@wyattearp.stanford.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200008211670886.richw@wyattearp.stanford.edu>; from richw@webcom.com on Mon, Aug 21, 2000 at 10:03:28AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Did the cable ever work with UDMA66? As far as possibilities with the cable, it could be that when it was manufactured that one of the lines didnt get cleanly cut, I forget which one it is but it allows it to sense the cable is for UDMA 66/100. You should be able to see where a machine has stamped a small cut in one of the wires. Or if the cable is 24 inches you could trying using a 18 inch cable, if possible. I believe 24 inches is the supposed max length, so using the shortest cable possible could make a difference. On Mon, Aug 21, 2000 at 10:03:28AM -0700, Rich Wales wrote: > My new Dell OptiPlex GX300 (running 4.1-RELEASE) came with an 80-wire > ATA cable. I added a second drive and am using this cable for both > drives. However, the kernel fails to recognize the cable and is limit- > ing DMA speed accordingly. Any ideas? > > See below for the relevant portion of the "boot -v" output. I note the > "cblid=0" value -- leading me to wonder if the problem might possibly > be with the integrated ATA controller on the motherboard not sensing or > reporting the cable properly. This is an 800-MHz Pentium III system, > though, so I find it a bit hard to believe that it isn't UDMA66-capable. > > BTW, in the line which claims I have a non-ATA66 compliant cable, I > believe the preferred spelling is "limited", with just one T (not two). > > Rich Wales richw@webcom.com http://www.webcom.com/richw/ > > ======================================================================== > > . . . > atapci0: port 0xffa0-0xffaf at device 31.1 on pci0 > ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xffa0 > ata0: mask=03 status0=50 status1=50 > ata0: mask=03 status0=50 status1=50 > ata0: devices = 0x3 > ata0: at 0x1f0 irq 14 on atapci0 > . . . > ata0-master: DMA limitted to UDMA33, non-ATA66 compliant cable > ata0-master: success setting up UDMA2 mode on ICH chip > ad0: ATA-5 disk at ata0 as master > ad0: 14324MB (29336832 sectors), 29104 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 1 depth queue, UDMA33 > ad0: piomode=4 dmamode=2 udmamode=4 cblid=0 > Creating DISK ad0 > Creating DISK wd0 > ata0-slave: success setting up UDMA2 mode on ICH chip > ad1: ATA-4 disk at ata0 as slave > ad1: 9617MB (19696320 sectors), 19540 cyls, 16 heads, 63 S/T, 512 B/S > ad1: 16 secs/int, 1 depth queue, UDMA33 > ad1: piomode=4 dmamode=2 udmamode=2 cblid=0 > Creating DISK ad1 > Creating DISK wd1 > > ======================================================================== > > > > 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 Aug 21 17:11:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from po3.glue.umd.edu (po3.glue.umd.edu [128.8.10.123]) by hub.freebsd.org (Postfix) with ESMTP id D4D4237B422 for ; Mon, 21 Aug 2000 17:11:56 -0700 (PDT) Received: from glue.umd.edu (poseidon.student.umd.edu [129.2.144.21]) by po3.glue.umd.edu (8.10.1/8.10.1) with ESMTP id e7M0BsH07466; Mon, 21 Aug 2000 20:11:54 -0400 (EDT) Message-ID: <39A1C549.5557E62E@glue.umd.edu> Date: Mon, 21 Aug 2000 20:11:53 -0400 From: Brandon Fosdick X-Mailer: Mozilla 4.74 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Rich Wales Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ATA66 cable being ignored? References: <200008211670886.richw@wyattearp.stanford.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rich Wales wrote: > > My new Dell OptiPlex GX300 (running 4.1-RELEASE) came with an 80-wire > ATA cable. I added a second drive and am using this cable for both > drives. However, the kernel fails to recognize the cable and is limit- > ing DMA speed accordingly. Any ideas? > > See below for the relevant portion of the "boot -v" output. I note the > "cblid=0" value -- leading me to wonder if the problem might possibly > be with the integrated ATA controller on the motherboard not sensing or > reporting the cable properly. This is an 800-MHz Pentium III system, > though, so I find it a bit hard to believe that it isn't UDMA66-capable. > > BTW, in the line which claims I have a non-ATA66 compliant cable, I > believe the preferred spelling is "limited", with just one T (not two). > > Rich Wales richw@webcom.com http://www.webcom.com/richw/ Are both drives ATA66? I built a new computer with a K7V (integrated ATA66 controller) and when I plugged my old ATA33 drive into the same cable (for copying stuff) I started getting the same messages. When I took the old drive off ATA66 started working again. I guess it can only go as fast as the slowest drive on the cable. -Brandon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 17:23:19 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 04DB137B424 for ; Mon, 21 Aug 2000 17:23:17 -0700 (PDT) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id RAA25598; Mon, 21 Aug 2000 17:23:09 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200008220023.RAA25598@freeway.dcfinc.com> Subject: Re: ATA66 cable being ignored? In-Reply-To: <39A1C549.5557E62E@glue.umd.edu> from Brandon Fosdick at "Aug 21, 0 08:11:53 pm" To: bfoz@glue.umd.edu (Brandon Fosdick) Date: Mon, 21 Aug 2000 17:23:09 -0700 (MST) Cc: richw@webcom.com, freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com Organization: DCF, Inc. X-O/S: FreeBSD 2.2.8-STABLE X-Unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Brandon Fosdick wrote: > Are both drives ATA66? I built a new computer with a K7V (integrated > ATA66 controller) and when I plugged my old ATA33 drive into the same > cable (for copying stuff) I started getting the same messages. When I > took the old drive off ATA66 started working again. I guess it can > only go as fast as the slowest drive on the cable. That's documented to be the case. In fact, I've also seen it recommended that ATA66 drives should be on an interface by themselves. -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 Mon Aug 21 17:40:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from snafu.adept.org (adsl-63-201-63-44.dsl.snfc21.pacbell.net [63.201.63.44]) by hub.freebsd.org (Postfix) with ESMTP id D890437B424 for ; Mon, 21 Aug 2000 17:40:18 -0700 (PDT) Received: by snafu.adept.org (Postfix, from userid 1000) id AF8229EE01; Mon, 21 Aug 2000 17:40:15 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by snafu.adept.org (Postfix) with ESMTP id AA8359B001; Mon, 21 Aug 2000 17:40:15 -0700 (PDT) Date: Mon, 21 Aug 2000 17:40:15 -0700 (PDT) From: Mike Hoskins To: Garance A Drosihn Cc: Rich Wales , freebsd-stable@FreeBSD.ORG Subject: Re: ATA66 cable being ignored? 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, 21 Aug 2000, Garance A Drosihn wrote: > For what it's worth, I have been seeing this too. In my case I > have two IDE controllers, one on the motherboard, and the other > a PCI card from Promise. I'm pretty sure the cable is correct, > although I haven't actually ripped the machine apart again to > check it... Hmm... Sounds exactly like what I saw under 4.0-release awhile back. Two ATA66 drives and one ATA33 drive... Both ATA66 units plugged into a Promise ATA66 PCI card, the ATA33 primary master on my mobo... All drives were treated like ATA33 units. I even talked to Promise. They went over a few BIOS settings and said everything was good hardware/system wise. -mrh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 17:48:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from snafu.adept.org (adsl-63-201-63-44.dsl.snfc21.pacbell.net [63.201.63.44]) by hub.freebsd.org (Postfix) with ESMTP id 96DE537B423 for ; Mon, 21 Aug 2000 17:48:30 -0700 (PDT) Received: by snafu.adept.org (Postfix, from userid 1000) id 6812B9EE01; Mon, 21 Aug 2000 17:48:27 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by snafu.adept.org (Postfix) with ESMTP id 6169D9B001; Mon, 21 Aug 2000 17:48:27 -0700 (PDT) Date: Mon, 21 Aug 2000 17:48:27 -0700 (PDT) From: Mike Hoskins To: Dave Uhring Cc: Gabriel Ambuehl , Chris , stable@freebsd.org Subject: Re: Re[2]: FreeBSD 4.1-STABLE is about as stable as windows98 In-Reply-To: <00082117273002.00210@dave.uhring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 21 Aug 2000, Dave Uhring wrote: Excuse me, I'm coming in on the middle of this... Mostly because it's common habit to ignore any messages with subjects like this ones. > The IDE drives may or may not be capable of such data rates, however, when > 4.1-stable kept giving me thousands of those errors with VIA MVP4 chipset, I > overwrote FreeBSD with Linux. Linux and OpenBSD-2.7 both use the ATA-66 > capability without errors and generally show a 25%-30% increase in performance > over ATA-33 measured with Bonnie. Who maintains the ATA code? Whomever it is, I'm sure they're very busy individauls. Possibly, they're not subscribed to this list and/or haven't checked mail recently (away working on projects). Have you contacted the maintainer(s)? Have you searched the mailing list archives? Have you tried asking in other closely related forums (hardware, fs and possibly hackers)? > The suggestion I received regarding replacement of the > 80-wire cable with a 40-wire cable is specious and non-responsive. Apparently > no one in a position to be able to properly evaluate this problem cares enough > even to post. Well, it was a response... Remember, no one guarantees how good or bad the responses you receive from a free, public mailing list will be. Before taking the time to provoke individuals in our community (at least, your sentence seems provocatory), why not skim some source code and work on a fix, or even just suggestions (or a dialog with the maintainer, anything that would help us) for improvements based upon your source review. Good luck, -mrh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 18:27:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 9B8B737B440 for ; Mon, 21 Aug 2000 18:27:47 -0700 (PDT) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id SAA00207; Mon, 21 Aug 2000 18:27:42 -0700 Message-ID: <39A1D70E.26DA70FB@urx.com> Date: Mon, 21 Aug 2000 18:27:42 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Josef Karthauser Cc: Noel Koethe , freebsd-stable@FreeBSD.ORG Subject: Re: error with make buildkernel 4.1-RC -> 4.1-release References: <39A1BAE4.D9AE46C@urx.com> <20000822003830.A1248@pavilion.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Josef Karthauser wrote: > > On Mon, Aug 21, 2000 at 04:27:32PM -0700, Kent Stewart wrote: > > > > > > Noel Koethe wrote: > > > > > > Hello, > > > > > > I made the following without errors: > > > > > > # cd /usr/src/ > > > # make update > > > > I don't see any reason for runing a make update. > > Make update does a 'cvsup' if configured correctly in /etc/make.conf. > It does nothing unless the make.conf parameters have been tweaked. I remembered that as I was going out the door to eat dinner. About half of the time I run cvsup in the gui mode so that I can save the log to disk. I've never updated using make. I updated two machines today and didn't have any problems rebuilding the systems. Kent > > Joe > -- > Josef Karthauser FreeBSD: How many times have you booted today? > Technical Manager Viagra for your server (http://www.uk.freebsd.org) > Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 18:32:35 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 BB9B937B42C for ; Mon, 21 Aug 2000 18:32:33 -0700 (PDT) Received: from thehousleys.net (baby.int.thehousleys.net. [192.168.0.24]) by thehousleys.net (8.9.3/8.9.3) with ESMTP id VAA61664 for ; Mon, 21 Aug 2000 21:32:28 -0400 (EDT) (envelope-from jim@thehousleys.net) Message-ID: <39A1D82C.FC1DF3BA@thehousleys.net> Date: Mon, 21 Aug 2000 21:32:28 -0400 From: James Housley Organization: The Housleys dot Net X-Mailer: Mozilla 4.73 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: IPv6 error "/kernel: nd6_ns_input: invalid hlim 253" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have two different networks with IPv4 in IPv6 tunnels to ToledoLink.com. On in the USA and one in Canada. The one in the USA has been up for a while and is working fine. The one in Canada is new. Both are running the exact same version of 4.1-STABLE. Canada, however, is attached via xDSL and PPPoE. When running ssh(IPv6) to Canada I get a lot, A LOT of "/kernel: nd6_ns_input: invalid hlim 253" on my USA machine. Is this because of the slighly smaller packet size of IPv6? Or is there a real problem I should be looking for? Jim -- "Eagles may soar, but weasels don't get sucked into jet engines" -- Anon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 18:35:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id 988B037B424 for ; Mon, 21 Aug 2000 18:35:28 -0700 (PDT) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id 486A4A845; Tue, 22 Aug 2000 11:36:50 +1000 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id 3B1E9544E; Tue, 22 Aug 2000 11:36:50 +1000 (EST) Date: Tue, 22 Aug 2000 11:36:50 +1000 (EST) From: andrew@ugh.net.au To: Jonathan Defries Cc: Joakim Ryden , freebsd-stable@freebsd.org Subject: RE: Password problems In-Reply-To: Message-ID: X-WonK: *wibble* 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, 20 Aug 2000, Jonathan Defries wrote: > OK, thanks. There's none of them running. Guess we're both out > of ideas for now :) You could try running passwd through gdb, gprof, truss or some other tool that lets you "see inside" the binary. It might give you a hint as to where its blocking...perhaps trying to aquire a lock? Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 19:55:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from prydn.tacni.net (207-55-167-109.dhc.net [207.55.167.109]) by hub.freebsd.org (Postfix) with SMTP id 7A3B637B423 for ; Mon, 21 Aug 2000 19:55:18 -0700 (PDT) Received: (qmail 21174 invoked by uid 1001); 22 Aug 2000 02:54:44 -0000 Date: Mon, 21 Aug 2000 21:54:44 -0500 From: Erich Zigler To: freebsd-stable@freebsd.org Subject: Oh the rapture Message-ID: <20000821215444.A21157@superhero.org> Mail-Followup-To: Erich Zigler , freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Eric-Conspiracy: There is no conspiracy. X-Shane: Hi Shane! Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is the error I get after cvsupping stable as of 08/21/2000 9:45 CDT Im trying to compile a new kernel. Could this be because Im building a kernel instead of a make world first. Should that matter if they are both 4.1-STABLE? The source tree and installed system. cd /usr/obj/usr/src/sys/PRYDN; MAKEOBJDIRPREFIX=/usr/obj COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.00503 DESTDIR=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin MACHINE=i386 make KERNEL=kernel all cc -c -x assembler-with-cpp -DLOCORE -O2 -pipe -mpentiumpro -march=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 /usr/src/sys/i386/i386/locore.s {standard input}: Assembler messages: {standard input}:1743: Error: .space specifies non-absolute value {standard input}:2454: Error: undefined symbol L0 in operation setting PTmap {standard input}:2454: Error: undefined symbol PDRSHIFT in operation setting PTmap {standard input}:1711: Error: undefined symbol L0 in operation {standard input}:1711: Error: undefined symbol PAGE_SIZE in operation {standard input}:1712: Error: undefined symbol L0 in operation {standard input}:1712: Error: undefined symbol PDESIZE in operation {standard input}:2454: Error: undefined symbol L0 in operation setting APTmap {standard input}:2454: Error: undefined symbol PDRSHIFT in operation setting APTmap {standard input}:1720: Error: undefined symbol L0 in operation {standard input}:1720: Error: undefined symbol PAGE_SIZE in operation {standard input}:1721: Error: undefined symbol L0 in operation {standard input}:1721: Error: undefined symbol PDESIZE in operation {standard input}:1927: Error: undefined symbol UPAGES in operation {standard input}:1927: Error: undefined symbol PAGE_SIZE in operation {standard input}:2315: Error: undefined symbol BI_ESYMTAB in operation {standard input}:2320: Error: undefined symbol BI_SYMTAB in operation {standard input}:2321: Error: undefined symbol BI_ESYMTAB in operation {standard input}:2325: Error: undefined symbol BI_KERNEND in operation {standard input}:2337: Error: undefined symbol PAGE_SIZE in operation {standard input}:2337: Error: undefined symbol PAGE_SIZE in operation {standard input}:2341: Error: undefined symbol PAGE_SIZE in operation {standard input}:2341: Error: undefined symbol PAGE_SIZE in operation {standard input}:2345: Error: undefined symbol UPAGES in operation {standard input}:2345: Error: undefined symbol PAGE_SIZE in operation {standard input}:2345: Error: undefined symbol UPAGES in operation {standard input}:2345: Error: undefined symbol PAGE_SIZE in operation {standard input}:2350: Error: undefined symbol PAGE_SIZE in operation {standard input}:2350: Error: undefined symbol PAGE_SIZE in operation {standard input}:2353: Error: undefined symbol PAGE_SIZE in operation {standard input}:2353: Error: undefined symbol PAGE_SIZE in operation {standard input}:2410: Error: undefined symbol PAGE_SHIFT in operation {standard input}:2426: Error: undefined symbol PAGE_SHIFT in operation {standard input}:2427: Error: undefined symbol PAGE_SHIFT in operation {standard input}:1853: Error: Subtraction of two symbols in different sections ".tmpstk" {.data section} - "KERNBASE" {*UND* section} at file address 28. {standard input}:1876: Error: Subtraction of two symbols in different sections "end" {*UND* section} - "KERNBASE" {*UND* section} at file address 38. {standard input}:1877: Error: Subtraction of two symbols in different sections "edata" {*UND* section} - "KERNBASE" {*UND* section} at file address 43. {standard input}:1889: Error: Subtraction of two symbols in different sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at file address 61. {standard input}:1905: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 81. {standard input}:2114: Error: Subtraction of two symbols in different sections "kernelname" {*UND* section} - "KERNBASE" {*UND* section} at file address 371. {standard input}:2142: Error: Subtraction of two symbols in different sections "bootinfo" {.data section} - "KERNBASE" {*UND* section} at file address 411. {standard input}:2162: Error: Subtraction of two symbols in different sections "boothowto" {*UND* section} - "KERNBASE" {*UND* section} at file address 435. {standard input}:2164: Error: Subtraction of two symbols in different sections "bootdev" {*UND* section} - "KERNBASE" {*UND* section} at file address 443. {standard input}:2202: Error: Subtraction of two symbols in different sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file address 495. {standard input}:2207: Error: Subtraction of two symbols in different sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file address 511. {standard input}:2208: Error: Subtraction of two symbols in different sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file address 521. {standard input}:2209: Error: Subtraction of two symbols in different sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file address 531. {standard input}:2210: Error: Subtraction of two symbols in different sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file address 541. {standard input}:2211: Error: Subtraction of two symbols in different sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file address 551. {standard input}:2230: Error: Subtraction of two symbols in different sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file address 592. {standard input}:2257: Error: Subtraction of two symbols in different sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file address 627. {standard input}:2258: Error: Subtraction of two symbols in different sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file address 637. {standard input}:2259: Error: Subtraction of two symbols in different sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file address 647. {standard input}:2265: Error: Subtraction of two symbols in different sections "cpu_high" {.data section} - "KERNBASE" {*UND* section} at file address 662. {standard input}:2266: Error: Subtraction of two symbols in different sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file address 668. {standard input}:2267: Error: Subtraction of two symbols in different sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file address 674. {standard input}:2268: Error: Subtraction of two symbols in different sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file address 680. {standard input}:2269: Error: Subtraction of two symbols in different sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file address 686. {standard input}:2273: Error: Subtraction of two symbols in different sections "cpu_id" {.data section} - "KERNBASE" {*UND* section} at file address 699. {standard input}:2274: Error: Subtraction of two symbols in different sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at file address 705. {standard input}:2281: Error: Subtraction of two symbols in different sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file address 722. {standard input}:2287: Error: Subtraction of two symbols in different sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file address 739. {standard input}:2291: Error: Subtraction of two symbols in different sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file address 751. {standard input}:2304: Error: Subtraction of two symbols in different sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at file address 762. {standard input}:2312: Error: Subtraction of two symbols in different sections "end" {*UND* section} - "KERNBASE" {*UND* section} at file address 784. {standard input}:2315: Error: Negative of non-absolute symbol KERNBASE {standard input}:2320: Error: Negative of non-absolute symbol KERNBASE {standard input}:2321: Error: Negative of non-absolute symbol KERNBASE {standard input}:2325: Error: Negative of non-absolute symbol KERNBASE {standard input}:2333: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 843. {standard input}:2334: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 849. {standard input}:2337: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 855. {standard input}:2337: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 867. {standard input}:2338: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 885. {standard input}:2341: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 891. {standard input}:2341: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 903. {standard input}:2342: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 921. {standard input}:2345: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 927. {standard input}:2345: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 939. {standard input}:2346: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 957. {standard input}:2348: Error: Subtraction of two symbols in different sections "proc0paddr" {.data section} - "KERNBASE" {*UND* section} at file address 969. {standard input}:2350: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 975. {standard input}:2350: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 987. {standard input}:2351: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1005. {standard input}:2353: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1011. {standard input}:2353: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1023. {standard input}:2354: Error: Subtraction of two symbols in different sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file address 1041. {standard input}:2356: Error: Subtraction of two symbols in different sections "vm86paddr" {.data section} - "KERNBASE" {*UND* section} at file address 1053. {standard input}:2371: Error: Subtraction of two symbols in different sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at file address 1063. {standard input}:2376: Error: Subtraction of two symbols in different sections "etext" {*UND* section} - "KERNBASE" {*UND* section} at file address 1080. {standard input}:2379: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1103. {standard input}:2382: Error: Subtraction of two symbols in different sections "etext" {*UND* section} - "KERNBASE" {*UND* section} at file address 1125. {standard input}:2388: Error: Subtraction of two symbols in different sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at file address 1146. {standard input}:2393: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1164. {standard input}:2396: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1183. {standard input}:2399: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 1205. {standard input}:2401: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1224. {standard input}:2404: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1247. {standard input}:2406: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1266. {standard input}:2411: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1308. {standard input}:2414: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1331. {standard input}:2416: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1350. {standard input}:2422: Error: Subtraction of two symbols in different sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file address 1392. {standard input}:2428: Error: Subtraction of two symbols in different sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file address 1434. {standard input}:2434: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1457. {standard input}:2437: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 1473. {standard input}:2440: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1496. {standard input}:2443: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 1515. {standard input}:2446: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 1538. {standard input}:2449: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 1557. *** Error code 1 Stop in /usr/obj/usr/src/sys/PRYDN. *** Error code 1 I thought that the kernel was compiled against the installed system libs and compiler not the ones being compiled in /usr/obj or am I way off base here? -- Erich Zigler Sr. System Administrator Tell init(8) to lock-n-load, we're goin' zombie slaying! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 20:17:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id B7BAD37B423 for ; Mon, 21 Aug 2000 20:17:51 -0700 (PDT) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id UAA00592; Mon, 21 Aug 2000 20:17:49 -0700 Message-ID: <39A1F0DD.AA954958@urx.com> Date: Mon, 21 Aug 2000 20:17:49 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Erich Zigler Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Oh the rapture References: <20000821215444.A21157@superhero.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Erich Zigler wrote: > > This is the error I get after cvsupping stable as of 08/21/2000 9:45 CDT > > Im trying to compile a new kernel. > Could this be because Im building a kernel instead of a make world first. > Should that matter if they are both 4.1-STABLE? The source tree and > installed system. > > cd /usr/obj/usr/src/sys/PRYDN; MAKEOBJDIRPREFIX=/usr/obj > COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin > LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib > OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec > PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.00503 > DESTDIR=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" > PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin > MACHINE=i386 make KERNEL=kernel all > cc -c -x assembler-with-cpp -DLOCORE -O2 -pipe -mpentiumpro > -march=pentiumpro -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys > -I/usr/src/sys/../include -D_KERNEL -include opt_global.h -elf > -mpreferred-stack-boundary=2 /usr/src/sys/i386/i386/locore.s > {standard input}: Assembler messages: > {standard input}:1743: Error: .space specifies non-absolute value > {standard input}:2454: Error: undefined symbol L0 in operation setting PTmap > {standard input}:2454: Error: undefined symbol PDRSHIFT in operation setting > PTmap > {standard input}:1711: Error: undefined symbol L0 in operation > > {standard input}:2446: Error: Subtraction of two symbols in different > sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file > address 1538. > {standard input}:2449: Error: Subtraction of two symbols in different > sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file > address 1557. > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/PRYDN. > *** Error code 1 > > I thought that the kernel was compiled against the installed system libs and > compiler not the ones being compiled in /usr/obj or am I way off base here? After 4.1, yes. If you read /usr/src/UPDATING, you have two choices. The first one runs like 1. make buildworld 2. make buildkernel KERNEL=PRYDN 3. make installkernel KERNEL=PRYDN 4. reboot to single user 5. make installworld 6. mergemaster 7. reboot The second one requires a make world first but if your build's don't work, you are to do the build[install]kernel method before talking about an error. A cvsup and a kernel make or a cvsup and a config kernel don't make the list. Kent > > -- > Erich Zigler Sr. System Administrator > > Tell init(8) to lock-n-load, we're goin' zombie slaying! > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 20:50:43 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 A591037B43F for ; Mon, 21 Aug 2000 20:50:37 -0700 (PDT) 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 XAA249518; Mon, 21 Aug 2000 23:50:33 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <200008220023.RAA25598@freeway.dcfinc.com> References: <200008220023.RAA25598@freeway.dcfinc.com> Date: Mon, 21 Aug 2000 23:50:17 -0400 To: chad@DCFinc.com, bfoz@glue.umd.edu (Brandon Fosdick) From: Garance A Drosihn Subject: Re: ATA66 cable being ignored? Cc: richw@webcom.com, 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 5:23 PM -0700 8/21/00, Chad R. Larson wrote: >As I recall, Brandon Fosdick wrote: > > Are both drives ATA66? I built a new computer with a K7V > > (integrated ATA66 controller) and when I plugged my old > > ATA33 drive into the same cable (for copying stuff) I > > started getting the same messages. When I took the old > > drive off ATA66 started working again. I guess it can > > only go as fast as the slowest drive on the cable. > >That's documented to be the case. > >In fact, I've also seen it recommended that ATA66 drives >should be on an interface by themselves. In my situation, I have two drives, both of which claim to be ATA66 capable. I have two separate controllers (not just interfaces, but entire controllers). One of the drives was a maxtor, and I have seen claims in other mail that maxtor didn't quite get their ATA66 drives working right. (note: I do not know that for a fact, I'm just saying I've read it). In any case, I could not get the machine to boot up if both drives were on the ATA66 controller, so (as luck would have it) I moved that Maxtor to the ATA33 controller, which is on the motherboard. The harddrive on the ATA66 controller is a 20-gig Seagate drive. The promise controller itself does seem to recognize it as an ATA66 device at bootup, but freebsd claims the cable can't handle it and drops back to ATA33. I'm about 95% sure I *do* have an ATA-66 cable in there, but given the way my machine is setup it would take at least an hour to find out for sure. It's also possible that I have some flags wrong or missing in my kernel config. My machine works well enough that I haven't been motivated to track this down, but if someone else is motivated and they come up with a quick fix then I'd give it a shot... :-) --- 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 Mon Aug 21 22:44:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp4.port.ru (mx5.port.ru [194.67.23.40]) by hub.freebsd.org (Postfix) with ESMTP id EECF637B42C for ; Mon, 21 Aug 2000 22:44:15 -0700 (PDT) Received: from [212.96.98.37] (helo=[212.96.98.37]) by smtp4.port.ru with esmtp (Exim 3.14 #44) id 13R6r6-000MUV-00; Tue, 22 Aug 2000 09:44:14 +0400 Date: Tue, 22 Aug 2000 09:44:00 +0400 (MSD) From: Jaroshenko Serge X-Sender: jaroshenko@freebsd.merlin.ru To: noor@comrax.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: DoS attacks and FreeBSD. 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 Hi! You can see /usr/ports/security/portsentry . Serge On Tue, 22 Aug 2000 noor@comrax.com wrote: > Hello all, > > One of our sites was a target for a DoS attempt tonight. The attempt > failed. > > I have ipfw running on the server, and managed to block the IP's in > question in time. My question is: suppose I was not near the PC at the > time of the incident, how can I configure ipfw to automatically block > cnnections originating from any IP and that is continuous in a suspecious > manner? (let's say 50 concurrent connections to port 80 every second.) > > Is this possible in FreeBSD or/and in ipfw? Would like to know how... > > Thanks in advance. > > Noor > > > > 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 Aug 21 22:45:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from prydn.tacni.net (207-55-167-109.dhc.net [207.55.167.109]) by hub.freebsd.org (Postfix) with SMTP id 3FFA837B424 for ; Mon, 21 Aug 2000 22:45:55 -0700 (PDT) Received: (qmail 84172 invoked by uid 1001); 22 Aug 2000 05:45:51 -0000 Date: Tue, 22 Aug 2000 00:45:51 -0500 From: Erich Zigler To: freebsd-stable@freebsd.org Subject: New Kernel Message-ID: <20000822004551.A78949@superhero.org> Mail-Followup-To: Erich Zigler , freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Eric-Conspiracy: There is no conspiracy. X-Shane: Hi Shane! Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm really unclear on the new kernel building system. I was walking a fellow System Administrator through configuring and compiling their kernel for the first time on a *BSD distribution. This was a fresh install of 4.1 so I had him install the sources from the CD he installed from. I then had him configure his kernel and try to compile it. Tons of errors. (Machine was not on the network so I was not able to get that information.) So now he is doing a make buildworld to hopefully fix the problems. I understand if you cvsup'ed your source tree to have to rebuild to update the kernel. But from a base installation? -- Erich Zigler Sr. System Administrator A dog teaches a boy fidelity, perseverance, and to turn around three times before lying down. -- Robert Benchley To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 22:54:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id AEEFE37B424 for ; Mon, 21 Aug 2000 22:54:49 -0700 (PDT) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 13R716-0003nS-00; Mon, 21 Aug 2000 22:54:32 -0700 Date: Mon, 21 Aug 2000 22:54:26 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Erich Zigler Cc: freebsd-stable@freebsd.org Subject: Re: New Kernel In-Reply-To: <20000822004551.A78949@superhero.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 Tue, 22 Aug 2000, Erich Zigler wrote: > first time on a *BSD distribution. This was a fresh install of 4.1 so I had > him install the sources from the CD he installed from. I then had him > configure his kernel and try to compile it. Tons of errors. (Machine was not Without a complete description of what you did, your report isn't very useful. It should be obvious that kernels are buildable from the source in a release, as how could your system boot if a kernel could not be built? Obviously, your kernel config file is broken (try with an unmodified GENERIC first), or the way you built the kernel is wrong. Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 23: 1:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mx.nkm.lt (mx.nkm.lt [193.219.211.9]) by hub.freebsd.org (Postfix) with SMTP id DAD6637B43E for ; Mon, 21 Aug 2000 22:58:54 -0700 (PDT) Received: (qmail 27026 invoked by uid 1073); 22 Aug 2000 05:58:47 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 22 Aug 2000 05:58:47 -0000 Date: Tue, 22 Aug 2000 07:58:47 +0200 (CEST) From: Domas Mituzas X-Sender: midom@mx.nkm.lt To: noor@comrax.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: DoS attacks and FreeBSD. 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 have ipfw running on the server, and managed to block the IP's in > question in time. My question is: suppose I was not near the PC at the > time of the incident, how can I configure ipfw to automatically block > cnnections originating from any IP and that is continuous in a suspecious > manner? (let's say 50 concurrent connections to port 80 every second.) Hi, it is possible to set up your ipfw firewall so it logs all setup connections to any socket, you specify. Therefore, your program or smple perl script may listen on that socket and make decisions by calling external program, e.g. ipfw again. Domas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 23: 8:23 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 EDF2337B422 for ; Mon, 21 Aug 2000 23:08:19 -0700 (PDT) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.16 #1) id 13R3fv-000Fy6-00; Tue, 22 Aug 2000 03:20:27 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.9.3/8.9.3) id DAA56307; Tue, 22 Aug 2000 03:20:26 +0100 (BST) (envelope-from ben) Date: Tue, 22 Aug 2000 03:20:26 +0100 From: Ben Smithurst To: Kent Stewart Cc: Josef Karthauser , Noel Koethe , freebsd-stable@FreeBSD.ORG Subject: Re: error with make buildkernel 4.1-RC -> 4.1-release Message-ID: <20000822032026.H20036@strontium.scientia.demon.co.uk> References: <39A1BAE4.D9AE46C@urx.com> <20000822003830.A1248@pavilion.net> <39A1D70E.26DA70FB@urx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <39A1D70E.26DA70FB@urx.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kent Stewart wrote: > About half of the time I run cvsup in the gui mode so that I can save > the log to disk. you can save the log to disk much easier in non-GUI mode, by the way. # cvsup -g -L2 supfile 2>&1 | tee cvsup.log -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 23:19: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 9FD8437B43C for ; Mon, 21 Aug 2000 23:19:40 -0700 (PDT) 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 AAA57136; Tue, 22 Aug 2000 00:19:39 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA01814; Tue, 22 Aug 2000 00:19:28 -0600 (MDT) Message-Id: <200008220619.AAA01814@harmony.village.org> To: Erich Zigler Subject: Re: Oh the rapture Cc: freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Mon, 21 Aug 2000 21:54:44 CDT." <20000821215444.A21157@superhero.org> References: <20000821215444.A21157@superhero.org> Date: Tue, 22 Aug 2000 00:19:28 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000821215444.A21157@superhero.org> Erich Zigler writes: : Im trying to compile a new kernel. : Could this be because Im building a kernel instead of a make world first. : Should that matter if they are both 4.1-STABLE? The source tree and : installed system. It shouldn't so long as your world tree is up to date and the build is up to date. It looks like genassym isn't being run, for some reason, which is likely why you are getting the errors that you are getting. Maybe you have trash left over from a prior run that's confusing things. Have you considered removing the obj dirs for this kernel and trying again? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 23:21:22 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 0F4E137B422 for ; Mon, 21 Aug 2000 23:21:20 -0700 (PDT) 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 AAA57155; Tue, 22 Aug 2000 00:21:18 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA01842; Tue, 22 Aug 2000 00:21:08 -0600 (MDT) Message-Id: <200008220621.AAA01842@harmony.village.org> To: kstewart@urx.com Subject: Re: Oh the rapture Cc: Erich Zigler , freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Mon, 21 Aug 2000 20:17:49 PDT." <39A1F0DD.AA954958@urx.com> References: <39A1F0DD.AA954958@urx.com> <20000821215444.A21157@superhero.org> Date: Tue, 22 Aug 2000 00:21:08 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39A1F0DD.AA954958@urx.com> Kent Stewart writes: : After 4.1, yes. If you read /usr/src/UPDATING, you have two choices. : The first one runs like : 1. make buildworld : 2. make buildkernel KERNEL=PRYDN : 3. make installkernel KERNEL=PRYDN : 4. reboot to single user : 5. make installworld : 6. mergemaster : 7. reboot Yes, for 4.1-stable to 4.1-stable you should have no need to do step 4, although prudence argues that you should test the new kernel before installing the new userland world. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 23:23:39 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 400A737B42C for ; Mon, 21 Aug 2000 23:23:37 -0700 (PDT) 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 AAA57179; Tue, 22 Aug 2000 00:23:36 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA01883; Tue, 22 Aug 2000 00:23:26 -0600 (MDT) Message-Id: <200008220623.AAA01883@harmony.village.org> To: Erich Zigler Subject: Re: New Kernel Cc: freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Tue, 22 Aug 2000 00:45:51 CDT." <20000822004551.A78949@superhero.org> References: <20000822004551.A78949@superhero.org> Date: Tue, 22 Aug 2000 00:23:25 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000822004551.A78949@superhero.org> Erich Zigler writes: : I'm really unclear on the new kernel building system. I was walking a fellow : System Administrator through configuring and compiling their kernel for the : first time on a *BSD distribution. This was a fresh install of 4.1 so I had : him install the sources from the CD he installed from. I then had him : configure his kernel and try to compile it. Tons of errors. (Machine was not : on the network so I was not able to get that information.) So now he is : doing a make buildworld to hopefully fix the problems. I understand if you : cvsup'ed your source tree to have to rebuild to update the kernel. But from : a base installation? From a base install, it should just work the same way it has forever. Assuming that the sources are really 4.1-RELEASE. My guess is that the he may be hitting the problem that is generally overlooked with config files, namely that they aren't too compatible between releases and you have to do lots of tweaking when upgrading. Or maybe he's remove required parts of the kernel config that appear to be optional but due to bugs they aren't. W/o more information, it is hard to know for sure. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 21 23:49:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id F1F2B37B424; Mon, 21 Aug 2000 23:49:47 -0700 (PDT) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id XAA01378; Mon, 21 Aug 2000 23:49:47 -0700 Message-ID: <39A2228B.99CB2F62@urx.com> Date: Mon, 21 Aug 2000 23:49:47 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Ben Smithurst Cc: Josef Karthauser , Noel Koethe , freebsd-stable@FreeBSD.org Subject: Re: error with make buildkernel 4.1-RC -> 4.1-release References: <39A1BAE4.D9AE46C@urx.com> <20000822003830.A1248@pavilion.net> <39A1D70E.26DA70FB@urx.com> <20000822032026.H20036@strontium.scientia.demon.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Smithurst wrote: > > Kent Stewart wrote: > > > About half of the time I run cvsup in the gui mode so that I can save > > the log to disk. > > you can save the log to disk much easier in non-GUI mode, by the way. > > # cvsup -g -L2 supfile 2>&1 | tee cvsup.log That is true. I hadn't even thought about doing it that way. Then, I make a slight command and end up with a couple of ways of handling it. I think one of the advantages of the GUI, it might be the only advantage, is that it lets you scroll through them first. I can use more to do that using the tee but cvsup has a nice scrollbar in the GUI mode. I also happen to like to do things like this in the command line mode. It looks like I will have a script that saves from the command line and one to fire it off in the GUI mode. BTW, I like the mergemaster addition to 18.4.7. I saw the commit and immediately updated the handbook on all three of the systems I use FreeBSD on. Thanks, Kent > > -- > Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 1:20:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id ADA4737B43C for ; Tue, 22 Aug 2000 01:20:16 -0700 (PDT) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id BAA01527; Tue, 22 Aug 2000 01:20:12 -0700 Message-ID: <39A237BC.D496F78B@urx.com> Date: Tue, 22 Aug 2000 01:20:12 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Erich Zigler , freebsd-stable@FreeBSD.ORG Subject: Re: Oh the rapture References: <39A1F0DD.AA954958@urx.com> <20000821215444.A21157@superhero.org> <200008220621.AAA01842@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 <39A1F0DD.AA954958@urx.com> Kent Stewart writes: > : After 4.1, yes. If you read /usr/src/UPDATING, you have two choices. > : The first one runs like > : 1. make buildworld > : 2. make buildkernel KERNEL=PRYDN > : 3. make installkernel KERNEL=PRYDN > : 4. reboot to single user > : 5. make installworld > : 6. mergemaster > : 7. reboot > > Yes, for 4.1-stable to 4.1-stable you should have no need to do step > 4, although prudence argues that you should test the new kernel before > installing the new userland world. That is why I like that scheme. It isn't much of a test but a simple boot does test the kernel and then I can install my world. If the kernel doesn't work, I still have a kernel.old and a working world that belongs to it. It also doesn't really take a lot of time to boot to single user mode on my machines. Kent > > Warner -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 1:22:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gatekeeper.tripos.com (gatekeeper.tripos.com [192.160.145.62]) by hub.freebsd.org (Postfix) with ESMTP id B749637B42C for ; Tue, 22 Aug 2000 01:22:27 -0700 (PDT) Received: (from uucp@localhost) by tripos.com (8.8.8+Sun) id DAA17921; Tue, 22 Aug 2000 03:22:25 -0500 (CDT) Received: from unknown(172.20.5.15) by gatekeeper.tripos.com via smap (V5.5) id xma017912; Tue, 22 Aug 00 03:22:23 -0500 Received: from tripos.com ([172.20.152.158]) by tripos.com (980919.SGI.STAND) via ESMTP id DAA92769; Tue, 22 Aug 2000 03:22:21 -0500 (CDT) Message-ID: <39A2382F.B18CE54D@tripos.com> Date: Tue, 22 Aug 2000 09:22:07 +0100 From: Steve Coles X-Mailer: Mozilla 4.7 [en-gb] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Rich Wales Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ATA66 cable being ignored? References: <200008211670886.richw@wyattearp.stanford.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "ad1: ATA-4 disk at ata0 as slave" Are you sure the Maxtor is UDMA-66 ? Isn't "ATA-4" UDMA-33 ? Steve Rich Wales wrote: > My new Dell OptiPlex GX300 (running 4.1-RELEASE) came with an 80-wire > ATA cable. I added a second drive and am using this cable for both > drives. However, the kernel fails to recognize the cable and is limit- > ing DMA speed accordingly. Any ideas? > > See below for the relevant portion of the "boot -v" output. I note the > "cblid=0" value -- leading me to wonder if the problem might possibly > be with the integrated ATA controller on the motherboard not sensing or > reporting the cable properly. This is an 800-MHz Pentium III system, > though, so I find it a bit hard to believe that it isn't UDMA66-capable. > > BTW, in the line which claims I have a non-ATA66 compliant cable, I > believe the preferred spelling is "limited", with just one T (not two). > > Rich Wales richw@webcom.com http://www.webcom.com/richw/ > > ======================================================================== > > . . . > atapci0: port 0xffa0-0xffaf at device 31.1 on pci0 > ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xffa0 > ata0: mask=03 status0=50 status1=50 > ata0: mask=03 status0=50 status1=50 > ata0: devices = 0x3 > ata0: at 0x1f0 irq 14 on atapci0 > . . . > ata0-master: DMA limitted to UDMA33, non-ATA66 compliant cable > ata0-master: success setting up UDMA2 mode on ICH chip > ad0: ATA-5 disk at ata0 as master > ad0: 14324MB (29336832 sectors), 29104 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 1 depth queue, UDMA33 > ad0: piomode=4 dmamode=2 udmamode=4 cblid=0 > Creating DISK ad0 > Creating DISK wd0 > ata0-slave: success setting up UDMA2 mode on ICH chip > ad1: ATA-4 disk at ata0 as slave > ad1: 9617MB (19696320 sectors), 19540 cyls, 16 heads, 63 S/T, 512 B/S > ad1: 16 secs/int, 1 depth queue, UDMA33 > ad1: piomode=4 dmamode=2 udmamode=2 cblid=0 > Creating DISK ad1 > Creating DISK wd1 > > ======================================================================== > > 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 Aug 22 1:39:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8951F37B423; Tue, 22 Aug 2000 01:39:56 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id BAA90627; Tue, 22 Aug 2000 01:39:56 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 22 Aug 2000 01:39:56 -0700 (PDT) From: Kris Kennaway To: Domas Mituzas Cc: noor@comrax.com, freebsd-stable@FreeBSD.ORG Subject: Re: DoS attacks and FreeBSD. 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, 22 Aug 2000, Domas Mituzas wrote: > > I have ipfw running on the server, and managed to block the IP's in > > question in time. My question is: suppose I was not near the PC at the > > time of the incident, how can I configure ipfw to automatically block > > cnnections originating from any IP and that is continuous in a suspecious > > manner? (let's say 50 concurrent connections to port 80 every second.) > > Hi, it is possible to set up your ipfw firewall so it logs all setup > connections to any socket, you specify. Therefore, your program or smple > perl script may listen on that socket and make decisions by calling > external program, e.g. ipfw again. Trivial DoS attack of another kind by simply spoofing connection attempts from a valid host and therefore tricking the script into blackholing it. Same may well go for portsentry depending on how it works (I don't know). A much better idea would be to do some kind of application-level rate limiting so that apache doesnt accept more connections from a source than it can handle. I don't know how or if it can do that, though. 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 Aug 22 1:46:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dns.comrax.com (dns.comrax.com [194.90.246.124]) by hub.freebsd.org (Postfix) with ESMTP id 0881337B424; Tue, 22 Aug 2000 01:46:12 -0700 (PDT) Received: from NOOR (unknown [156.27.243.27]) by dns.comrax.com (Postfix) with SMTP id 1573E1C99E; Tue, 22 Aug 2000 11:46:06 +0300 (IDT) From: "Noor Dawod" To: "Kris Kennaway" , "Domas Mituzas" Cc: Subject: RE: DoS attacks and FreeBSD. Date: Tue, 22 Aug 2000 11:43:53 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, it can, and I've alreaedy done just that. But then again, all other legitimate visitors will be locked out... Noor -----Original Message----- From: Kris Kennaway [mailto:kris@FreeBSD.org] Sent: Tuesday, August 22, 2000 10:40 AM To: Domas Mituzas Cc: noor@comrax.com; freebsd-stable@FreeBSD.ORG Subject: Re: DoS attacks and FreeBSD. On Tue, 22 Aug 2000, Domas Mituzas wrote: > > I have ipfw running on the server, and managed to block the IP's in > > question in time. My question is: suppose I was not near the PC at the > > time of the incident, how can I configure ipfw to automatically block > > cnnections originating from any IP and that is continuous in a suspecious > > manner? (let's say 50 concurrent connections to port 80 every second.) > > Hi, it is possible to set up your ipfw firewall so it logs all setup > connections to any socket, you specify. Therefore, your program or smple > perl script may listen on that socket and make decisions by calling > external program, e.g. ipfw again. Trivial DoS attack of another kind by simply spoofing connection attempts from a valid host and therefore tricking the script into blackholing it. Same may well go for portsentry depending on how it works (I don't know). A much better idea would be to do some kind of application-level rate limiting so that apache doesnt accept more connections from a source than it can handle. I don't know how or if it can do that, though. 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 Aug 22 1:58:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E8F2437B42C; Tue, 22 Aug 2000 01:58:41 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id BAA92364; Tue, 22 Aug 2000 01:58:41 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 22 Aug 2000 01:58:41 -0700 (PDT) From: Kris Kennaway To: Noor Dawod Cc: Domas Mituzas , freebsd-stable@FreeBSD.ORG Subject: RE: DoS attacks and FreeBSD. 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, 22 Aug 2000, Noor Dawod wrote: > Yes, it can, and I've alreaedy done just that. But then again, all other > legitimate visitors will be locked out... Depends how smart the rate-limiting is. If it's at the application level you know the connection (probably) isn't spoofed, which means you can rate-limit per IP. 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 Aug 22 3:34:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from qmail.corpex.net (qmail.corpex.net [195.153.247.40]) by hub.freebsd.org (Postfix) with SMTP id 2F1B537B423 for ; Tue, 22 Aug 2000 03:34:51 -0700 (PDT) Received: (qmail 48726 invoked from network); 22 Aug 2000 10:37:24 -0000 Received: from perseus.corpex.net (HELO perseus) (195.153.247.226) by qmail.corpex.net with SMTP; 22 Aug 2000 10:37:24 -0000 From: "Jonathan Defries" To: Cc: "Freebsd-Stable@Freebsd. Org" Subject: RE: Password problems Date: Tue, 22 Aug 2000 11:34:36 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Thanks for the suggestion. It keeps looping like this if I run truss: syscall gettimeofday(0xbfbfd58c,0x0) returns 0 (0x0) syscall select(0x5,0xbfbfd5fc,0x0,0x0,0xbfbfd584) returns 0 (0x0) syscall sendto(0x4,0x80529f0,0x38,0x0,0x8052808,0x10) returns 56 (0x38) syscall gettimeofday(0xbfbfd58c,0x0) returns 0 (0x0) syscall select(0x5,0xbfbfd5fc,0x0,0x0,0xbfbfd584) returns 0 (0x0) syscall sendto(0x4,0x80529f0,0x38,0x0,0x8052808,0x10) returns 56 (0x38) syscall gettimeofday(0xbfbfd58c,0x0) returns 0 (0x0) syscall select(0x5,0xbfbfd5fc,0x0,0x0,0xbfbfd584) returns 0 (0x0) syscall sendto(0x4,0x80529f0,0x38,0x0,0x8052808,0x10) returns 56 (0x38) syscall gettimeofday(0xbfbfd58c,0x0) returns 0 (0x0) Not good, I assume :) - Jonathan > -----Original Message----- > From: andrew@ugh.net.au [mailto:andrew@ugh.net.au] > Sent: 22 August 2000 02:37 > To: Jonathan Defries > Cc: Joakim Ryden; freebsd-stable@freebsd.org > Subject: RE: Password problems > > > > > On Sun, 20 Aug 2000, Jonathan Defries wrote: > > > OK, thanks. There's none of them running. Guess we're both out > > of ideas for now :) > > You could try running passwd through gdb, gprof, truss or some other tool > that lets you "see inside" the binary. It might give you a hint as to > where its blocking...perhaps trying to aquire a lock? > > Andrew > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 4: 9:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mix.unicon.ru (mix.unicon.ru [195.239.106.158]) by hub.freebsd.org (Postfix) with ESMTP id B8C4337B423; Tue, 22 Aug 2000 04:09:30 -0700 (PDT) Received: (from strange@localhost) by mix.unicon.ru (8.8.8/8.8.8) id SAA22467; Tue, 22 Aug 2000 18:09:23 +0700 (NSS) (envelope-from strange) Date: Tue, 22 Aug 2000 18:09:23 +0700 (NSS) Message-Id: <200008221109.SAA22467@mix.unicon.ru> To: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org From: strange@unicon.ru Subject: How can I obtain -stable for previous date ? Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm obtain -stable (RELENG_4) every 2 days via cvsup. And do make world every time... But after Aug 20, the system became unstable ;( It locks on hard loading (hard HDD usage), like a make release or even make buildworld ;( No panic, no crashdump, nothing, full lock... Just many HDD problems after hard reboot ;( How can I downgrade (build an previous stable) ? What should I tell to cvsup to extract this sources ? And maybe there is another solve of this problem ? I thing on hardware, change Ethernet card, HDD drives, memory... Same problem occured. My hardware: M/B Iwill DBD100 2xPIII (non overclocked !) freq 4.5 x 103 2x128Mb Promise ATA66 and 3 Seagate ATA66 HDD % dmesg Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.1-STABLE #1: Tue Aug 22 23:02:05 NOVST 2000 root@:/usr/src/sys/compile/REMIX2 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (463.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383fbff real memory = 268369920 (262080K bytes) config> en apm0 config> q avail memory = 257503232 (251468K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02ec000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02ec09c. Pentium Pro MTRR support enabled md0: Malloc disk apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: at device 7.1 on pci0 atapci0: Busmastering DMA not enabled pci0: at 7.2 Timecounter "PIIX" frequency 3579545 Hz chip1: port 0x5000-0x500f at device 7.3 on pci0 atapci1: port 0xe400-0xe43f,0xe000-0xe003,0xdc00-0xdc07,0xd800-0xd803,0xd400-0xd407 mem 0xdf200000-0xdf21ffff irq 16 at device 15.0 on pci0 ata2: at 0xd400 on atapci1 ata3: at 0xdc00 on atapci1 pci0: at 18.0 irq 18 dc0: port 0xe800-0xe87f mem 0xdf220000-0xdf2203ff irq 19 at device 19.0 on pci0 dc0: Ethernet address: 00:00:1c:b5:52:8f miibus0: on dc0 amphy0: on miibus0 amphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to deny, logging limited to 100 packets/entry by default DUMMYNET initialized (000608) SMP: AP CPU #1 Launched! ad4: 29188MB [59303/16/63] at ata2-master using UDMA66 ad6: 29188MB [59303/16/63] at ata3-master using UDMA66 ad7: 14652MB [29770/16/63] at ata3-slave using UDMA66 Mounting root from ufs:/dev/ad4s1a WARNING: / was not properly dismounted WBR Strange Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 4:10:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hand.dotat.at (CPE-144-132-129-157.nsw.bigpond.net.au [144.132.129.157]) by hub.freebsd.org (Postfix) with ESMTP id 0179437B42C for ; Tue, 22 Aug 2000 04:10:47 -0700 (PDT) Received: from fanf by hand.dotat.at with local (Exim 3.15 #3) id 13QIUS-00007s-00; Sat, 19 Aug 2000 23:57:28 +0000 Date: Sat, 19 Aug 2000 23:57:28 +0000 From: Tony Finch To: Doug Barton Cc: Gerhard Sittig , FreeBSD stable Subject: Re: remove empty TEMPROOT dirs at mergemaster's end? (was: cvs commit: src/usr.sbin/mergemaster mergemaster.sh) Message-ID: <20000819235728.B261@hand.dotat.at> References: <200008171114.e7HBEuq01585@hak.lan.Awfulhak.org> <20000818193708.T252@speedy.gsinet> <399EE6A7.5F82DD6C@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <399EE6A7.5F82DD6C@gorean.org> Organization: Covalent Technologies, Inc Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Barton wrote: > >For instance, if you actually wanted to prune the directory structure 'find -d >. -type d -links 2 -exec rmdir {} \;' would do a pretty good job.... You can use -delete instead of -exec rmdir {} \; and it'll be somewhat faster. Tony. -- en oeccget g mtcaa f.a.n.finch v spdlkishrhtewe y dot@dotat.at eatp o v eiti i d. fanf@covalent.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 4:35:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hal.medianet.ie (hal.medianet.ie [212.17.32.26]) by hub.freebsd.org (Postfix) with ESMTP id C147A37B423 for ; Tue, 22 Aug 2000 04:35:10 -0700 (PDT) Received: [from teebar.traveldev.com (rum.medianet.ie [212.17.34.203] by hal.medianet.ie (DIESPAM) with ESMTP id e7MBZ3p10273 for ; Tue, 22 Aug 2000 12:35:03 +0100] Received: from traveldev.com (dermot.traveldev.com [192.168.0.50]) by teebar.traveldev.com (8.10.2/8.10.2) with ESMTP id e7MBZBV76348 for ; Tue, 22 Aug 2000 12:35:11 +0100 (IST) Message-ID: <39A2656A.F156C9D9@traveldev.com> Date: Tue, 22 Aug 2000 12:35:06 +0100 From: Dermot McNally X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Numbering of fxp devices 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 have a box with two fxp devices which probe like this: fxp0: port 0x2000-0x203f mem 0xf4200000-0xf42fffff,0xf4300000-0xf4300fff irq 5 at device 4.0 on pci2 fxp0: Ethernet address 00:d0:b7:69:93:79 fxp1: port 0x1080-0x10bf mem 0xf4000000-0xf40fffff,0xf4100000-0xf4100fff irq 10 at device 14.0 on pci0 fxp1: Ethernet address 00:90:27:f7:06:2e One of these is integrated in the motherboard, the other is a card. What puzzles me is the order in which the devices are numbered. I had expected (for no particular reason) that the on-board device would come up as fxp0, but when I first installed 4.0-RELEASE, they came up the other way around. The order stayed this way for a couple of weeks during which I tracked -stable and made world frequently, but after one upgrade, the box came up with the on-board card claiming to be fxp0. However, not long afterwards, it reverted to the original behaviour. Now, obviously the numbering doesn't matter all that much. What _does_ matter is if the numbering is unpredictable at boot time (worst case) or if it may be reversed after a remote upgrade. Is this down to pure fluke or can I lock down the order in some way? Thanks, Dermot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 5: 9:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from alpha.root-servers.ch (beta.root-servers.ch [195.49.33.19]) by hub.freebsd.org (Postfix) with SMTP id 16DBD37B42C for ; Tue, 22 Aug 2000 05:09:56 -0700 (PDT) Received: (qmail 69173 invoked from network); 22 Aug 2000 12:09:54 -0000 Received: from client80-30.hispeed.ch (HELO 10.2.2.100) (62.2.80.30) by alpha.root-servers.ch with SMTP; 22 Aug 2000 12:09:54 -0000 Date: Tue, 22 Aug 2000 14:11:51 +0200 From: Gabriel Ambuehl X-Mailer: The Bat! (v1.45 Beta/6) Personal Organization: BUZ Internet Services X-Priority: 3 (Normal) Message-ID: <7057457679.20000822141151@buz.ch> To: noor@comrax.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: DoS attacks and FreeBSD. In-reply-To: References: 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 noor, Tuesday, August 22, 2000, 1:47:05 AM, you wrote: > cnnections originating from any IP and that is continuous in a suspecious > manner? (let's say 50 concurrent connections to port 80 every second.) I don't think you really want to have done this automatically... What about the big ISPs which are directing all traffic through transparent proxies? Best regards, Gabriel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 6:19:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cosa.uk-legal.net (cosa.uk-legal.net [212.240.216.34]) by hub.freebsd.org (Postfix) with ESMTP id ACABF37B423; Tue, 22 Aug 2000 06:19:27 -0700 (PDT) Received: by cosa.uk-legal.net (Postfix, from userid 1000) id 5AC4A112BA; Tue, 22 Aug 2000 14:17:54 +0100 (BST) Received: from localhost (localhost [127.0.0.1]) by cosa.uk-legal.net (Postfix) with ESMTP id 4A54032; Tue, 22 Aug 2000 14:17:54 +0100 (BST) Date: Tue, 22 Aug 2000 14:17:54 +0100 (BST) From: Andrew Tulloch To: strange@unicon.ru Cc: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Subject: Re: How can I obtain -stable for previous date ? In-Reply-To: <200008221109.SAA22467@mix.unicon.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 I had a similar problem with a hard lock doing a buildworld over the weekend. Just turned out to be my machine being in a new desk and one side had got covered up so not getting enough ventilation and overheated it seems. Gave it a bit more room and its been fine. built world again afterwards and it worked fine :) Andrew Tulloch - Systems Administrator - Legalex Ltd andrew@cosa.uk-legal.net FreeBSD: The Power To Serve... On Tue, 22 Aug 2000 strange@unicon.ru wrote: > > I'm obtain -stable (RELENG_4) every 2 days via cvsup. > And do make world every time... > But after Aug 20, the system became unstable ;( > It locks on hard loading (hard HDD usage), > like a make release or even make buildworld ;( > No panic, no crashdump, nothing, full lock... > Just many HDD problems after hard reboot ;( > > How can I downgrade (build an previous stable) ? > What should I tell to cvsup to extract this sources ? > > And maybe there is another solve of this problem ? > I thing on hardware, change Ethernet card, HDD drives, memory... > Same problem occured. > > My hardware: > M/B Iwill DBD100 > 2xPIII (non overclocked !) freq 4.5 x 103 > 2x128Mb > Promise ATA66 and 3 Seagate ATA66 HDD > % dmesg > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 4.1-STABLE #1: Tue Aug 22 23:02:05 NOVST 2000 > root@:/usr/src/sys/compile/REMIX2 > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium III/Pentium III Xeon/Celeron (463.91-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x673 Stepping = 3 > Features=0x383fbff > real memory = 268369920 (262080K bytes) > config> en apm0 > config> q > avail memory = 257503232 (251468K bytes) > Programming 24 pins in IOAPIC #0 > IOAPIC #0 intpin 2 -> irq 0 > FreeBSD/SMP: Multiprocessor motherboard > cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 > cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 > io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 > Preloaded elf kernel "kernel" at 0xc02ec000. > Preloaded userconfig_script "/boot/kernel.conf" at 0xc02ec09c. > Pentium Pro MTRR support enabled > md0: Malloc disk > apm0: on motherboard > apm: found APM BIOS v1.2, connected at v1.2 > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: at device 7.1 on pci0 > atapci0: Busmastering DMA not enabled > pci0: at 7.2 > Timecounter "PIIX" frequency 3579545 Hz > chip1: port 0x5000-0x500f at device 7.3 on pci0 > atapci1: port 0xe400-0xe43f,0xe000-0xe003,0xdc00-0xdc07,0xd800-0xd803,0xd400-0xd407 mem 0xdf200000-0xdf21ffff irq 16 at device 15.0 on pci0 > ata2: at 0xd400 on atapci1 > ata3: at 0xdc00 on atapci1 > pci0: at 18.0 irq 18 > dc0: port 0xe800-0xe87f mem 0xdf220000-0xdf2203ff irq 19 at device 19.0 on pci0 > dc0: Ethernet address: 00:00:1c:b5:52:8f > miibus0: on dc0 > amphy0: on miibus0 > amphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/16 bytes threshold > plip0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to deny, logging limited to 100 packets/entry by default > DUMMYNET initialized (000608) > SMP: AP CPU #1 Launched! > ad4: 29188MB [59303/16/63] at ata2-master using UDMA66 > ad6: 29188MB [59303/16/63] at ata3-master using UDMA66 > ad7: 14652MB [29770/16/63] at ata3-slave using UDMA66 > Mounting root from ufs:/dev/ad4s1a > WARNING: / was not properly dismounted > > > WBR Strange Alex > > > 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 Aug 22 7:16:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from alpha.root-servers.ch (beta.root-servers.ch [195.49.33.19]) by hub.freebsd.org (Postfix) with SMTP id EA43237B422 for ; Tue, 22 Aug 2000 07:16:37 -0700 (PDT) Received: (qmail 13038 invoked from network); 22 Aug 2000 14:16:36 -0000 Received: from client80-30.hispeed.ch (HELO 10.2.2.100) (62.2.80.30) by alpha.root-servers.ch with SMTP; 22 Aug 2000 14:16:36 -0000 Date: Tue, 22 Aug 2000 16:18:34 +0200 From: Gabriel Ambuehl X-Mailer: The Bat! (v1.45 Beta/6) Personal Organization: BUZ Internet Services X-Priority: 3 (Normal) Message-ID: <5665060291.20000822161834@buz.ch> To: Kris Kennaway Cc: stable@freebsd.org Subject: Re[2]: make installworld over NFS doesn't work anymore In-reply-To: References: 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 Kris, Monday, August 21, 2000, 11:21:45 PM, you wrote: > Make sure you are not doing a make world with -DNOCLEAN and > -DNOCLEANDIR. If the problem persists, remove your /usr/obj directory and > try again. I did a simple make buildworld. No hacks beside of the following: - UT_NAMESIZE 31 - MAXLOGNAME 32 - NOSENDMAIL the whole config worked several times before the MfC. I killed /usr/obj by hand, cvsupped at 11:30 GMT and started make buildworld which ran through without any problems but still, the make installworld over NFS doesn't work: sed '/^#ifndef NO_IDEA$/,/^#endif$/d' /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/evp.h > /usr/obj/usr/src/secure/lib/libcrypto/evp.h.new cannot create /usr/obj/usr/src/secure/lib/libcrypto/evp.h.new: permission denied *** Error code 2 Stop in /usr/src/secure/lib/libcrypto. *** Error code 1 Stop in /usr/src/secure/lib. *** Error code 1 Stop in /usr/src/secure. *** Error code 1 To be honest, I don't understand why installworld needs to write to /usr/obj as this is crying for problems when /usr/obj is mounted ro (which I think should be the case with -maproot=root NFS exports, YMV)... I don't think I'm the only one who wants to do make installworld from ro mounted places. Best regards, Gabriel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 7:47:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gatekeeper.veriohosting.com (gatekeeper.veriohosting.com [192.41.0.2]) by hub.freebsd.org (Postfix) with ESMTP id 2885337B424 for ; Tue, 22 Aug 2000 07:47:13 -0700 (PDT) Received: by gatekeeper.veriohosting.com; Tue, 22 Aug 2000 08:47:09 -0600 (MDT) Received: from unknown(192.168.1.7) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma021371; Tue, 22 Aug 00 08:46:46 -0600 Received: from vespa.orem.iserver.com (vespa.orem.iserver.com [192.168.1.144]) by orca.orem.veriohosting.com [Verio Web Hosting, Inc. 801.437.0200] (8.8.8) id IAA52030; Tue, 22 Aug 2000 08:46:45 -0600 (MDT) Date: Tue, 22 Aug 2000 08:57:58 -0600 (MDT) From: Fred Clift X-Sender: fred@vespa.orem.iserver.com To: Dermot McNally Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Numbering of fxp devices In-Reply-To: <39A2656A.F156C9D9@traveldev.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 > other way around. The order stayed this way for a couple of weeks during > which I tracked -stable and made world frequently, but after one > upgrade, the box came up with the on-board card claiming to be fxp0. > However, not long afterwards, it reverted to the original behaviour. > > Now, obviously the numbering doesn't matter all that much. What _does_ > matter is if the numbering is unpredictable at boot time (worst case) or > if it may be reversed after a remote upgrade. Is this down to pure fluke > or can I lock down the order in some way? I am not directly aware of what recent changes would have caused the change in probe order, but I can give you some ideas about where to look and then offer my comments about what I belive would be ideal. in FreeBSD <= 3.X it appears that all pci-to-pci busses were probed first, and then devices on them were probed in some fixed order. In FreeBSD >= 4.0 the 'newbus' code replaced a lot of the old bus code including probing and now the buses are probed kind of in a depth-first fashion, finding all devices on a particular bus and then moving on to another. Aparently, from your results, the order that the busses are probed has been changed or something similar. I pitty the guy with whom I exchanged emails a while back that is running a 6 or 8 port 'router' all with fxp cards. He was running 3.4 last I knew and was planning on waiting a LONG time before upgrading to 4.X because of the relative difficulty of figuring out which cards when where. What I would find to be the best of all possible worlds is if you could wire-down pci-card instances to particular instances of a driver - ie I want the first card on bus 2 to be fxp0 and the second card on bus 1 to be fxp1, etc... Of course this would depend on finding the busses in the right order, but... Unfortunately, I'm, uh, somewhat unexperience in this (and most of the rest) of the code and when I looked at it, all I got was a headache. How hard would it be to either provide a consistent mapping or to allow the hard-wiring of devices to drivers? Fred -- Fred Clift - fred@clift.org -- Remember: If brute force doesn't work, you're just not using enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 7:50:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gatekeeper.veriohosting.com (gatekeeper.veriohosting.com [192.41.0.2]) by hub.freebsd.org (Postfix) with ESMTP id DF4ED37B43C for ; Tue, 22 Aug 2000 07:50:49 -0700 (PDT) Received: by gatekeeper.veriohosting.com; Tue, 22 Aug 2000 08:50:49 -0600 (MDT) Received: from unknown(192.168.1.7) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma022172; Tue, 22 Aug 00 08:50:24 -0600 Received: from vespa.orem.iserver.com (vespa.orem.iserver.com [192.168.1.144]) by orca.orem.veriohosting.com [Verio Web Hosting, Inc. 801.437.0200] (8.8.8) id IAA52407; Tue, 22 Aug 2000 08:50:23 -0600 (MDT) Date: Tue, 22 Aug 2000 09:01:36 -0600 (MDT) From: Fred Clift X-Sender: fred@vespa.orem.iserver.com To: Dermot McNally Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Numbering of fxp devices 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 > in FreeBSD <= 3.X it appears that all pci-to-pci busses were probed first, make that pci-to-pci bridges :) oops -- Fred Clift - fred@clift.or -- Remember: If brute force doesn't work, you're just not using enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 7:55:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hal.medianet.ie (hal.medianet.ie [212.17.32.26]) by hub.freebsd.org (Postfix) with ESMTP id 3ECF137B446 for ; Tue, 22 Aug 2000 07:55:11 -0700 (PDT) Received: [from teebar.traveldev.com (trabant.clubi.ie [212.17.33.226] by hal.medianet.ie (DIESPAM) with ESMTP id e7MEt8O04475; Tue, 22 Aug 2000 15:55:08 +0100] Received: from traveldev.com (dermot.traveldev.com [192.168.0.50]) by teebar.traveldev.com (8.10.2/8.10.2) with ESMTP id e7MEtFV80415; Tue, 22 Aug 2000 15:55:15 +0100 (IST) Message-ID: <39A29450.FBDAEF13@traveldev.com> Date: Tue, 22 Aug 2000 15:55:12 +0100 From: Dermot McNally X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Fred Clift Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Numbering of fxp devices References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fred Clift wrote: > in FreeBSD <= 3.X it appears that all pci-to-pci busses were probed first, > and then devices on them were probed in some fixed order. > > In FreeBSD >= 4.0 the 'newbus' code replaced a lot of the old bus code Well, this certainly isn't what got me - The oldest release that has been on this particular box is 4.0-RELEASE. At almost all times, the card has probed before the onboard, and I'm beginning to think that it will stay that way. Maybe there was a glitch introduced into the code, which got quickly backed out? Dermot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 8:16:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from nbf-27.umd.edu (nbf-27.umd.edu [128.8.38.27]) by hub.freebsd.org (Postfix) with ESMTP id 6275237B43F for ; Tue, 22 Aug 2000 08:16:51 -0700 (PDT) Received: from glue.umd.edu (localhost [127.0.0.1]) by nbf-27.umd.edu (8.9.3/8.9.3) with ESMTP id LAA15436; Tue, 22 Aug 2000 11:16:40 -0400 (EDT) (envelope-from bfoz@glue.umd.edu) Message-ID: <39A29958.2252D81F@glue.umd.edu> Date: Tue, 22 Aug 2000 11:16:40 -0400 From: Brandon Fosdick X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: kstewart@urx.com, Erich Zigler , freebsd-stable@FreeBSD.ORG Subject: Re: Oh the rapture References: <39A1F0DD.AA954958@urx.com> <20000821215444.A21157@superhero.org> <200008220621.AAA01842@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 <39A1F0DD.AA954958@urx.com> Kent Stewart writes: > : After 4.1, yes. If you read /usr/src/UPDATING, you have two choices. > : The first one runs like > : 1. make buildworld > : 2. make buildkernel KERNEL=PRYDN > : 3. make installkernel KERNEL=PRYDN > : 4. reboot to single user > : 5. make installworld > : 6. mergemaster > : 7. reboot > > Yes, for 4.1-stable to 4.1-stable you should have no need to do step > 4, although prudence argues that you should test the new kernel before > installing the new userland world. In place of step 4 is it sufficient to just do `shutdown now'? I mount my /usr/src and /usr/obj with nfs which makes life a little more difficult if I do a full reboot. I always thought it was bad karma to boot a kernel that's out of sync with world. Brandon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 8:27:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cosa.uk-legal.net (cosa.uk-legal.net [212.240.216.34]) by hub.freebsd.org (Postfix) with ESMTP id A162A37B423 for ; Tue, 22 Aug 2000 08:27:08 -0700 (PDT) Received: by cosa.uk-legal.net (Postfix, from userid 1000) id 81F87112BA; Tue, 22 Aug 2000 16:25:30 +0100 (BST) Received: from localhost (localhost [127.0.0.1]) by cosa.uk-legal.net (Postfix) with ESMTP id 719D532; Tue, 22 Aug 2000 16:25:30 +0100 (BST) Date: Tue, 22 Aug 2000 16:25:30 +0100 (BST) From: Andrew Tulloch To: Dermot McNally Cc: Fred Clift , freebsd-stable@FreeBSD.ORG Subject: Re: Numbering of fxp devices In-Reply-To: <39A29450.FBDAEF13@traveldev.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've got a machine with two fxp devices in, it has always picked up the card first then the onboard one, which I also thought was odd. Although I've never noticed the order in which they were probed change. It ran 4.0-release then up'd to stable a couple of months ago, then to 4.1-stable shortly after 4.1-release. Andrew Tulloch - Systems Administrator - Legalex Ltd andrew@cosa.uk-legal.net FreeBSD: The Power To Serve... On Tue, 22 Aug 2000, Dermot McNally wrote: > Fred Clift wrote: > > > in FreeBSD <= 3.X it appears that all pci-to-pci busses were probed first, > > and then devices on them were probed in some fixed order. > > > > In FreeBSD >= 4.0 the 'newbus' code replaced a lot of the old bus code > > Well, this certainly isn't what got me - The oldest release that has > been on this particular box is 4.0-RELEASE. At almost all times, the > card has probed before the onboard, and I'm beginning to think that it > will stay that way. Maybe there was a glitch introduced into the code, > which got quickly backed out? > > Dermot > > > 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 Aug 22 8:44: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 F288F37B423 for ; Tue, 22 Aug 2000 08:44:48 -0700 (PDT) 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 JAA59976; Tue, 22 Aug 2000 09:44:47 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA04758; Tue, 22 Aug 2000 09:44:35 -0600 (MDT) Message-Id: <200008221544.JAA04758@harmony.village.org> To: Brandon Fosdick Subject: Re: Oh the rapture Cc: kstewart@urx.com, Erich Zigler , freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Tue, 22 Aug 2000 11:16:40 EDT." <39A29958.2252D81F@glue.umd.edu> References: <39A29958.2252D81F@glue.umd.edu> <39A1F0DD.AA954958@urx.com> <20000821215444.A21157@superhero.org> <200008220621.AAA01842@harmony.village.org> Date: Tue, 22 Aug 2000 09:44:35 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39A29958.2252D81F@glue.umd.edu> Brandon Fosdick writes: : I always thought it was bad karma to boot a kernel that's out of sync : with world. Geenrally there's nothing ill that will happen, except that things like dmesg, ps, etc stop working. These aren't needed to install the world. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 8:47:43 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 2739A37B42C for ; Tue, 22 Aug 2000 08:47:40 -0700 (PDT) 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 JAA59999; Tue, 22 Aug 2000 09:47:38 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA04810; Tue, 22 Aug 2000 09:47:26 -0600 (MDT) Message-Id: <200008221547.JAA04810@harmony.village.org> To: chip@chocobo.cx Subject: Re: Oh the rapture Cc: Brandon Fosdick , kstewart@urx.com, Erich Zigler , freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Tue, 22 Aug 2000 11:43:53 EDT." <20000822114353.A32952@setzer.chocobo.cx> References: <20000822114353.A32952@setzer.chocobo.cx> <39A1F0DD.AA954958@urx.com> <20000821215444.A21157@superhero.org> <200008220621.AAA01842@harmony.village.org> <39A29958.2252D81F@glue.umd.edu> Date: Tue, 22 Aug 2000 09:47:26 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000822114353.A32952@setzer.chocobo.cx> Chip Marshall writes: : I would think that the point of rebooting is to test the new kernel : before installing all the binaries that go with it. Just using : 'shutdown now' to get to single user mode and doing the installworld : before a reboot may leave you with a broken kernel, and going back to : an older kernel may not work in the brave new world. Yes. There was a point in the upgrade sequence when you needed the new kernel to run the binaries used to install the new binaries, but I think that we save them off now so that isn't strictly necessary. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 8:52:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hq1.tyfon.net (hq1.tyfon.net [213.212.29.17]) by hub.freebsd.org (Postfix) with ESMTP id EDF1C37B422 for ; Tue, 22 Aug 2000 08:52:02 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hq1.tyfon.net (Postfix) with ESMTP id 968971C7BB for ; Tue, 22 Aug 2000 17:51:57 +0200 (CEST) Date: Tue, 22 Aug 2000 17:51:57 +0200 (CEST) From: Dan Larsson To: FreeBSD Stable List Subject: Update perl along with src Message-ID: Organization: Tyfon Svenska AB MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is just a thought, would it be possible to update the perl modules along with the source when suping the src? make.conf feature? Regards +------ Dan Larsson | Tel: +46 8 550 120 21 Tyfon Svenska AB | Fax: +46 8 550 120 02 Public PGP keys | finger dl@hq1.tyfon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 9: 8:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 1FF0537B424 for ; Tue, 22 Aug 2000 09:08:39 -0700 (PDT) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id LAA60590; Tue, 22 Aug 2000 11:08:26 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Tue, 22 Aug 2000 11:08:26 -0500 (CDT) From: Chris Dillon To: Fred Clift Cc: Dermot McNally , freebsd-stable@FreeBSD.ORG Subject: Re: Numbering of fxp devices 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, 22 Aug 2000, Fred Clift wrote: > > other way around. The order stayed this way for a couple of weeks during > > which I tracked -stable and made world frequently, but after one > > upgrade, the box came up with the on-board card claiming to be fxp0. > > However, not long afterwards, it reverted to the original behaviour. > > > > Now, obviously the numbering doesn't matter all that much. What _does_ > > matter is if the numbering is unpredictable at boot time (worst case) or > > if it may be reversed after a remote upgrade. Is this down to pure fluke > > or can I lock down the order in some way? > > > I am not directly aware of what recent changes would have caused > the change in probe order, but I can give you some ideas about > where to look and then offer my comments about what I belive would > be ideal. > > in FreeBSD <= 3.X it appears that all pci-to-pci busses were > probed first, and then devices on them were probed in some fixed > order. > > In FreeBSD >= 4.0 the 'newbus' code replaced a lot of the old bus > code including probing and now the buses are probed kind of in a > depth-first fashion, finding all devices on a particular bus and > then moving on to another. Aparently, from your results, the > order that the busses are probed has been changed or something > similar. > > I pitty the guy with whom I exchanged emails a while back that is > running a 6 or 8 port 'router' all with fxp cards. He was running > 3.4 last I knew and was planning on waiting a LONG time before > upgrading to 4.X because of the relative difficulty of figuring > out which cards when where. That would be me, probably. :-) 7 NICs, one of which is dual-port, for a total of 8 ports. I recently moved all of those NICs from a Compaq Proliant 3000 running 3.4-STABLE into a new Proliant ML530 running 4.1-STABLE. The card order is definately weird, but that isn't so much FreeBSD's fault. Compaq was nice enough to label primary, secondary, and tertiary PCI bus slots on the back of the machine, but they aren't in order anyway. What I ended up doing was booting the system with all the cards installed, noting the MAC address of each interface, and then comparing that to physical slot locations. Not as nice as the sequential ordering in the Proliant 3000, but not a big deal either, as long as it doesn't change on me in the future without some warning. :-) > What I would find to be the best of all possible worlds is if you could > wire-down pci-card instances to particular instances of a driver - ie I > want the first card on bus 2 to be fxp0 and the second card on bus 1 to be > fxp1, etc... Of course this would depend on finding the busses in the > right order, but... This would be nice. But, if bus or device ordering changes, you'd still be up the same creek. You'd have to wire things down in a card-specific way and not a bus/slot-specific way. > Unfortunately, I'm, uh, somewhat unexperience in this (and most of the > rest) of the code and when I looked at it, all I got was a headache. How > hard would it be to either provide a consistent mapping or to allow the > hard-wiring of devices to drivers? -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures. ( 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 Tue Aug 22 9:28: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wyattearp.stanford.edu (wyattearp.Stanford.EDU [171.66.63.23]) by hub.freebsd.org (Postfix) with ESMTP id 4F80937B43E for ; Tue, 22 Aug 2000 09:28:00 -0700 (PDT) Received: (from richw@localhost) by wyattearp.stanford.edu (8.9.3/8.9.3) id JAA06732; Tue, 22 Aug 2000 09:27:00 -0700 (PDT) (envelope-from richw) Date: Tue, 22 Aug 2000 09:27:00 -0700 (PDT) From: Rich Wales X-Sender: richw@wyattearp.stanford.edu To: freebsd-stable@freebsd.org Subject: Re: ATA66 cable being ignored? Message-ID: <200008221604690.richw@wyattearp.stanford.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Coles wrote: > "ad1: ATA-4 disk at ata0 as slave" > Are you sure the Maxtor is UDMA-66? Isn't "ATA-4" UDMA-33? Very good point. In fact, this Maxtor disk is at least a year old -- truly ancient by modern standards :-} -- so I'm pretty sure it's not UDMA66. As I recall, the interface cable that originally came in the box with this particular drive was an older, 40-wire cable. So, until such time as I can rearrange my hardware -- either by upgrad- ing the old Maxtor to a newer drive, or else by freeing up a spot for the older drive on the secondary ATA controller -- I guess I'll just have to endure slower disk throughput. I suppose I'll somehow manage to survive. :-} This brings up another question, though. Is there any way to redo the kernel's device probe output so it doesn't try to blame the cable in cases like this? For example, if an ATA controller has two devices, and one is ATA-5 (or better?) but the other is not, then ata-dma.c could say something like "can't do UDMA66 with fast/slow device mix". Rich Wales richw@webcom.com http://www.webcom.com/richw/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 9:33:24 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 1EB3B37B423; Tue, 22 Aug 2000 09:33:18 -0700 (PDT) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.16 #1) id 13RGwH-000Gdw-00; Tue, 22 Aug 2000 17:30:13 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.9.3/8.9.3) id RAA12385; Tue, 22 Aug 2000 17:30:13 +0100 (BST) (envelope-from ben) Date: Tue, 22 Aug 2000 17:30:13 +0100 From: Ben Smithurst To: strange@unicon.ru Cc: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Subject: Re: How can I obtain -stable for previous date ? Message-ID: <20000822173013.M20036@strontium.scientia.demon.co.uk> References: <200008221109.SAA22467@mix.unicon.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200008221109.SAA22467@mix.unicon.ru> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG strange@unicon.ru wrote: > I'm obtain -stable (RELENG_4) every 2 days via cvsup. > And do make world every time... > But after Aug 20, the system became unstable ;( > It locks on hard loading (hard HDD usage), > like a make release or even make buildworld ;( > No panic, no crashdump, nothing, full lock... > Just many HDD problems after hard reboot ;( Look at the date= option in CVSup. date=[cc]yy.mm.dd.hh.mm.ss This specifies a date that should be used to select the revi- sions that are checked out from the CVS repository. The client will receive the revisions that were in effect at the specified date and time. So perhaps you want src-all date=2000.08.20.00.00.00 tag=RELENG_4 or something to get the code from midnight on the 20th August. But ideally you should try to find what is causing the problem, of course. I assume that will work anyway, I've never actually used the date option in CVSup myself. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 9:35:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from la-raid.lmki.net (la-raid.lmki.net [64.63.24.42]) by hub.freebsd.org (Postfix) with ESMTP id E02FB37B424 for ; Tue, 22 Aug 2000 09:35:35 -0700 (PDT) Received: from mail.gonescrappin.com - 64.63.34.48 by la-raid.lmki.net with Microsoft SMTPSVC(5.5.1774.114.11); Tue, 22 Aug 2000 09:30:35 -0700 Received: from c37560-b [24.13.134.122] by mail.gonescrappin.com (SMTPD32-6.00) id A34D29250100; Tue, 22 Aug 2000 08:59:09 -0700 From: "Scrapbooking Friend" To: Date: Tue, 22 Aug 00 09:51:02 Mountain Daylight Time Subject: Scrapbooking Web Site - www.gonescrappin.com X-Mailer: EMailing List Pro 3.0 Message-Id: <200008220859609.SM00212@c37560-b> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Announcing a great new Scrapbooking Web Site: www.gonescrappin.com. Our site has an exclusive new way to "Shop by Layouts!" Sign up for our newsletter and get 10% off your order until August 31. Hope you'll check it out! The Gone Scrappin' Team To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 9:54:11 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 CEEE337B424; Tue, 22 Aug 2000 09:54:03 -0700 (PDT) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id LAA04821; Tue, 22 Aug 2000 11:54:02 -0500 (CDT) (envelope-from jeff-ml@mountin.net) Received: from dial-103.max1.wa.cyberlynk.net(207.227.118.103) by peak.mountin.net via smap (V1.3) id sma004819; Tue Aug 22 11:53:48 2000 Message-Id: <4.3.2.20000822113358.00b86ac0@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Tue, 22 Aug 2000 11:51:24 -0500 To: Kris Kennaway , Noor Dawod From: "Jeffrey J. Mountin" Subject: RE: DoS attacks and FreeBSD. Cc: Domas Mituzas , freebsd-stable@FreeBSD.ORG In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:58 AM 8/22/00 -0700, Kris Kennaway wrote: >On Tue, 22 Aug 2000, Noor Dawod wrote: > > > Yes, it can, and I've alreaedy done just that. But then again, all other > > legitimate visitors will be locked out... > >Depends how smart the rate-limiting is. If it's at the application level >you know the connection (probably) isn't spoofed, which means you can >rate-limit per IP. In "Apache Modules with Perl and C" there is an example. It goes a bit further than IP by concatenating the IP with the user agent, which won't work if all the users behind a firewall/proxy have the exact same agent name, but then some hackery could be done for an exemption list. There are several variations or combinations that could be used. However, the example used might be better written in C for busy sites, which also avoid the memory overhead of using perl. There is still the problem of making a connection and sitting idle to tie up a process. The timeout could be reduced, but there might be problems for those with slow connections. Suffice to say there are always compromises, but with little work one can block most malicious spiders, etc with a combination of access controls. 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 Aug 22 10:45:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (Postfix) with ESMTP id 7383537B422 for ; Tue, 22 Aug 2000 10:45:32 -0700 (PDT) Received: from tao.thought.org (tao.sea.tera.com [207.108.223.55]) by gershwin.tera.com (8.9.3/8.9.3) with ESMTP id KAA01200 for ; Tue, 22 Aug 2000 10:45:49 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.9.3/8.7.3) id KAA79681 for freebsd-stable@FreeBSD.ORG; Tue, 22 Aug 2000 10:45:29 -0700 (PDT) From: Gary Kline Message-Id: <200008221745.KAA79681@tao.thought.org> Subject: 4.1 /etc/rc.conf and IPv6... To: freebsd-stable@FreeBSD.ORG Date: Tue, 22 Aug 2000 10:45:29 -0700 (PDT) Organization: <> thought.org: pvblic service Unix since 1986... <> 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 This is for the net gurus on this list. My 4.1 stuff builds-- though *not* matching the src/UPDATING instructions exactly. Everything looks go for a `shutdown now' to single-usr or a reboot and boot -s. Can I just drop in my current `ifconfig ed1' line (as ed0')? how do I join the v6 world? Currently, in /etc/rc.conf.local is: network_interfaces="lo0 ed1" # List of network interfaces (lo0 is loopback). ifconfig_lo0="inet 127.0.0.1" # default loopback device configuration. ifconfig_tun0="inet 207.108.223.55 207.108.223.19 netmask 0xffffff00" ######################## # ed1 configuration for tao (ed1 in FBSD-3.2) ######################## ifconfig ed1 inet 10.0.0.1 netmask 255.255.255.0 I'm guessing that this is likely to work in a 4.1 /etc/rc.conf.local. Am I being too optimistic? gary -- Gary D. Kline kline@tao.thought.org Public service Unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 11: 5: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mta05-svc.ntlworld.com (mta05-svc.ntlworld.com [62.253.162.45]) by hub.freebsd.org (Postfix) with ESMTP id 3D7E037B423; Tue, 22 Aug 2000 11:04:58 -0700 (PDT) Received: from parish.my.domain ([62.255.98.151]) by mta05-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000822180452.TJLE317.mta05-svc.ntlworld.com@parish.my.domain>; Tue, 22 Aug 2000 19:04:52 +0100 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id TAA01768; Tue, 22 Aug 2000 19:04:47 +0100 (BST) (envelope-from mark) Date: Tue, 22 Aug 2000 19:04:46 +0100 From: Mark Ovens To: Kent Stewart Cc: Ben Smithurst , Josef Karthauser , Noel Koethe , freebsd-stable@freebsd.org Subject: Re: error with make buildkernel 4.1-RC -> 4.1-release Message-ID: <20000822190445.C254@parish> References: <39A1BAE4.D9AE46C@urx.com> <20000822003830.A1248@pavilion.net> <39A1D70E.26DA70FB@urx.com> <20000822032026.H20036@strontium.scientia.demon.co.uk> <39A2228B.99CB2F62@urx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <39A2228B.99CB2F62@urx.com>; from kstewart@urx.com on Mon, Aug 21, 2000 at 11:49:47PM -0700 Organization: Total lack of Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 21, 2000 at 11:49:47PM -0700, Kent Stewart wrote: > > > Ben Smithurst wrote: > > > > Kent Stewart wrote: > > > > > About half of the time I run cvsup in the gui mode so that I can save > > > the log to disk. > > > > you can save the log to disk much easier in non-GUI mode, by the way. > > > > # cvsup -g -L2 supfile 2>&1 | tee cvsup.log > > That is true. I hadn't even thought about doing it that way. Then, I > make a slight command and end up with a couple of ways of handling it. > I think one of the advantages of the GUI, it might be the only > advantage, is that it lets you scroll through them first. I can use > more to do that using the tee but cvsup has a nice scrollbar in the > GUI mode. > Hmm, are you aware of some useful utilities hidden away in the contrib directory of the cvsup-bin tarball (that don't get installed by the port)? My favourite is cvsup2html which makes all the "Edit" and "Checkout" lines into links to the CVS repo on freefall? # cvsup2html < /usr/sup/cvsup.log > /usr/sup/cvsup.html cvsupchk is also useful; found loads of redundant files in my tree. From the README: This directory contains various utilities contributed by CVSup users. Please contact the individual authors of the utilities if you find bugs or have questions about them. cvsup2html Convert cvsup client log output into a web page, with each filename serving as a link to the cvsweb page for that file. cvsup2httplog Convert a cvsupd log file to standard httpd log file format, so that it can be analyzed by tools such as webalizer. cvsupchk Check for extraneous files in a tree maintained by CVSup. cvsupwho Show who is currently using your CVSup server. > I also happen to like to do things like this in the command line mode. > It looks like I will have a script that saves from the command line > and one to fire it off in the GUI mode. > > BTW, I like the mergemaster addition to 18.4.7. I saw the commit and > immediately updated the handbook on all three of the systems I use > FreeBSD on. > > Thanks, > > Kent > > > > > > -- > > Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D > > -- > Kent Stewart > Richland, WA > > mailto:kbstew99@hotmail.com > http://kstewart.urx.com/kstewart/index.html > FreeBSD News http://daily.daemonnews.org/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- 4.4 - The number of the Beastie ________________________________________________________________ 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark mailto:marko@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 Aug 22 11:17:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9A7C937B422; Tue, 22 Aug 2000 11:17:45 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id LAA36369; Tue, 22 Aug 2000 11:17:45 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 22 Aug 2000 11:17:45 -0700 (PDT) From: Kris Kennaway To: Dan Larsson Cc: FreeBSD Stable List Subject: Re: Update perl along with src 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, 22 Aug 2000, Dan Larsson wrote: > This is just a thought, would it be possible to update the perl modules > along with the source when suping the src? make.conf feature? Which perl modules? 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 Aug 22 11:46: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from server.raadinfo.net (smtp2.uwnet.nl [195.7.130.55]) by hub.freebsd.org (Postfix) with ESMTP id 9275C37B423 for ; Tue, 22 Aug 2000 11:46:00 -0700 (PDT) Received: from port174.isd.to (port174.isd.to [195.7.129.174]) by server.raadinfo.net (8.9.3/8.9.3) with ESMTP id UAA01827 for ; Tue, 22 Aug 2000 20:43:16 +0200 Received: (qmail 1362 invoked by uid 1000); 22 Aug 2000 18:47:48 -0000 From: "Andre Goeree" Date: Tue, 22 Aug 2000 20:47:48 +0200 To: freebsd-stable@freebsd.org Subject: /etc/defaults/rc.conf 4.1-STABLE-200-08-18 Message-ID: <20000822204748.A1334@freebee.attica.home> Reply-To: abgoeree@uwnet.nl Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Sender: abgoeree@uwnet.nl Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, After manually updating /etc from cvsupped sources (200-08-18) i noticed that /etc/rc.conf doesn't get (properly) loaded. Network daemons that are disabled in /etc/rc.conf get started, other switches don't work (firewall_quiet). It looks as if /etc/rc.conf doesn't get loaded at all.... What i did was: make buildworld etc. (steps in handbook & UPDATING) cd /usr/src/etc make DESTDIR=/var/tmp/root distrib-dirs distribution cd /var/tmp/root/etc cp rc* /etc/ (most of the rc files was changed) cd defaults cp * /etc/defaults/ (some changes here too) updated most if not all other files Could it be that i missed something? BTW: Temporarily fixed it myself by putting [ -f /etc/rc.conf ] && . /etc/rc.conf just after the last comment block in /etc/defaults/rc.conf. Hope that doesn't break anything :)....... -- Ago abgoeree@uwnet.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 13:32:16 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 7A94C37B423; Tue, 22 Aug 2000 13:32:05 -0700 (PDT) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.16 #1) id 13RJXp-000Gtv-00; Tue, 22 Aug 2000 20:17:09 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.9.3/8.9.3) id UAA00431; Tue, 22 Aug 2000 20:17:09 +0100 (BST) (envelope-from ben) Date: Tue, 22 Aug 2000 20:17:09 +0100 From: Ben Smithurst To: Mark Ovens Cc: freebsd-stable@freebsd.org Subject: Re: error with make buildkernel 4.1-RC -> 4.1-release Message-ID: <20000822201709.S20036@strontium.scientia.demon.co.uk> References: <39A1BAE4.D9AE46C@urx.com> <20000822003830.A1248@pavilion.net> <39A1D70E.26DA70FB@urx.com> <20000822032026.H20036@strontium.scientia.demon.co.uk> <39A2228B.99CB2F62@urx.com> <20000822190445.C254@parish> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000822190445.C254@parish> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Ovens wrote: > My favourite is cvsup2html which makes all the "Edit" and "Checkout" > lines into links to the CVS repo on freefall? > > # cvsup2html < /usr/sup/cvsup.log > /usr/sup/cvsup.html is similar to cvsup2html, but the output has more twiddly bits. Whether that's good or bad I'll leave you to decide. :-) It's probably slower and probably generates overly complex HTML, but what the hell. I guess I could send cvsuplog to John so he can put it in the contrib directory of future releases, but if everyone hates it except me I won't bother. ;-) -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 13:42: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mta02-svc.ntlworld.com (mta02-svc.ntlworld.com [62.253.162.42]) by hub.freebsd.org (Postfix) with ESMTP id 7E20A37B424; Tue, 22 Aug 2000 13:42:02 -0700 (PDT) Received: from parish.my.domain ([62.253.88.67]) by mta02-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000822214103.URMB3760.mta02-svc.ntlworld.com@parish.my.domain>; Tue, 22 Aug 2000 21:41:03 +0000 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id VAA59689; Tue, 22 Aug 2000 21:41:58 +0100 (BST) (envelope-from mark) Date: Tue, 22 Aug 2000 21:41:56 +0100 From: Mark Ovens To: Ben Smithurst Cc: freebsd-stable@freebsd.org Subject: Re: error with make buildkernel 4.1-RC -> 4.1-release Message-ID: <20000822214156.I254@parish> References: <39A1BAE4.D9AE46C@urx.com> <20000822003830.A1248@pavilion.net> <39A1D70E.26DA70FB@urx.com> <20000822032026.H20036@strontium.scientia.demon.co.uk> <39A2228B.99CB2F62@urx.com> <20000822190445.C254@parish> <20000822201709.S20036@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20000822201709.S20036@strontium.scientia.demon.co.uk>; from ben@freebsd.org on Tue, Aug 22, 2000 at 08:17:09PM +0100 Organization: Total lack of Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 22, 2000 at 08:17:09PM +0100, Ben Smithurst wrote: > Mark Ovens wrote: > > > My favourite is cvsup2html which makes all the "Edit" and "Checkout" > > lines into links to the CVS repo on freefall? > > > > # cvsup2html < /usr/sup/cvsup.log > /usr/sup/cvsup.html > > is > similar to cvsup2html, but the output has more twiddly bits. Whether > that's good or bad I'll leave you to decide. :-) It's probably slower > and probably generates overly complex HTML, but what the hell. > I like it :) > I guess I could send cvsuplog to John so he can put it in the contrib > directory of future releases, but if everyone hates it except me I won't > bother. ;-) > e-mail him and ask. > -- > Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- 4.4 - The number of the Beastie ________________________________________________________________ 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark mailto:marko@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 Aug 22 13:50:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freemail.aecinfo.com (host-45.toronto.bricsnet.com [209.146.217.45]) by hub.freebsd.org (Postfix) with ESMTP id 4278037B43C for ; Tue, 22 Aug 2000 13:50:30 -0700 (PDT) Received: from itdept (host-102.toronto.bricsnet.com [209.146.217.102]) by freemail.aecinfo.com (8.8.8/8.8.8) with SMTP id QAA26428 for ; Tue, 22 Aug 2000 16:55:54 -0400 (EDT) (envelope-from mitayai@bricsnet.com) Reply-To: From: "Will Mitayai Keeso Rowe" To: "FreeBSD-Stable" Subject: sendmail 8.11 Date: Tue, 22 Aug 2000 16:58:38 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are they are plans to merge sendmail 8.11 into 4.1-STABLE? -- Will Mitayai Keeso Rowe Director of Internet Technology Bricsnet NV mitayai@bricsnet.com http://www.bricsnet.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 13:52: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by hub.freebsd.org (Postfix) with ESMTP id 4526237B440 for ; Tue, 22 Aug 2000 13:51:59 -0700 (PDT) Received: from simoeon.sentex.net (simeon.sentex.ca [209.112.4.47]) by smtp1.sentex.ca (8.11.0/8.11.0) with ESMTP id e7MKpdH77244; Tue, 22 Aug 2000 16:51:39 -0400 (EDT) Message-Id: <4.3.2.7.0.20000822164634.02d9ece0@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 22 Aug 2000 16:47:04 -0400 To: , "FreeBSD-Stable" From: Mike Tancsa Subject: Re: sendmail 8.11 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:58 PM 8/22/00 -0400, Will Mitayai Keeso Rowe wrote: >Are they are plans to merge sendmail 8.11 into 4.1-STABLE? Soon. I asked this same question last week. See the archives for the answer as to the date, and other issues around 8.11 ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Sentex Communications mike@sentex.net Cambridge, Ontario Canada www.sentex.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 13:52:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id 9480A37B42C; Tue, 22 Aug 2000 13:52:28 -0700 (PDT) Date: Tue, 22 Aug 2000 13:52:28 -0700 From: David O'Brien To: Will Mitayai Keeso Rowe Cc: FreeBSD-Stable Subject: Re: sendmail 8.11 Message-ID: <20000822135228.A86875@hub.freebsd.org> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Will Mitayai Keeso Rowe on Tue, Aug 22, 2000 at 04:58:38PM -0400 X-Operating-System: FreeBSD 4.1-RELEASE 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 Tue, Aug 22, 2000 at 04:58:38PM -0400, Will Mitayai Keeso Rowe wrote: > Are they are plans to merge sendmail 8.11 into 4.1-STABLE? Yes, but it has only been in -CURRENT for a week now. Please have patience. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 13:55: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from horsey.gshapiro.net (horsey.gshapiro.net [209.220.147.178]) by hub.freebsd.org (Postfix) with ESMTP id 0DFD337B43C for ; Tue, 22 Aug 2000 13:55:04 -0700 (PDT) Received: (from gshapiro@localhost) by horsey.gshapiro.net (8.11.1.Alpha0/8.11.0) id e7MKsqQ04998; Tue, 22 Aug 2000 13:54:52 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14754.59548.160530.306473@horsey.gshapiro.net> Date: Tue, 22 Aug 2000 13:54:52 -0700 (PDT) From: Gregory Neil Shapiro To: Cc: "FreeBSD-Stable" Subject: Re: sendmail 8.11 In-Reply-To: References: X-Mailer: VM 6.75 under 21.2 (beta35) "Nike" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG mitayai> Are they are plans to merge sendmail 8.11 into 4.1-STABLE? Yes, this week most likely. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 14: 8:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 301BC37B43F for ; Tue, 22 Aug 2000 14:08:43 -0700 (PDT) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id XAA94741; Tue, 22 Aug 2000 23:08:42 +0200 (CEST) (envelope-from olli) Date: Tue, 22 Aug 2000 23:08:42 +0200 (CEST) Message-Id: <200008222108.XAA94741@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG Reply-To: freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD Feature/Question X-Newsgroups: list.freebsd-stable In-Reply-To: <8njn17$1jjt$1@atlantis.rz.tu-clausthal.de> Organization: Administration TU Clausthal MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In list.freebsd-stable Justin W. Pauler wrote: > This is something I have been wondering about for awhile and just thought > that it would be a nice feature. Its the output of 'mount'. I use it quite > often to see what filesystems are mounted. Only problem is, well it gets > kind of hard to read sometimes when you have several filesystems loaded. > At times the lines can wrap around and can get pretty long. FWIW, I've once written a small awk script for that. Try http://www.fromme.com/scripts/mnt (Download, copy to /usr/local/bin, chmod 755, rehash, and just type "mnt".) Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) Addresses will change soon!! If in doubt: www.fromme.com "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 16: 9:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-5-249.zoominternet.net [24.154.5.249]) by hub.freebsd.org (Postfix) with ESMTP id 49C8237B423 for ; Tue, 22 Aug 2000 16:09:11 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by topperwein.dyndns.org (8.9.3/8.9.3) with ESMTP id TAA01922; Tue, 22 Aug 2000 19:09:52 -0400 (EDT) (envelope-from behanna@zbzoom.net) Date: Tue, 22 Aug 2000 19:09:52 -0400 (EDT) From: Chris BeHanna Reply-To: behanna@zbzoom.net To: Andre Goeree Cc: freebsd-stable@freebsd.org Subject: Re: /etc/defaults/rc.conf 4.1-STABLE-200-08-18 In-Reply-To: <20000822204748.A1334@freebee.attica.home> 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, 22 Aug 2000, Andre Goeree wrote: > Hello, > > After manually updating /etc from cvsupped sources (200-08-18) > i noticed that /etc/rc.conf doesn't get (properly) loaded. > Network daemons that are disabled in /etc/rc.conf get started, > other switches don't work (firewall_quiet). > It looks as if /etc/rc.conf doesn't get loaded at all.... > > What i did was: > make buildworld etc. (steps in handbook & UPDATING) > cd /usr/src/etc > make DESTDIR=/var/tmp/root distrib-dirs distribution > cd /var/tmp/root/etc > cp rc* /etc/ (most of the rc files was changed) > cd defaults > cp * /etc/defaults/ (some changes here too) > updated most if not all other files > > Could it be that i missed something? Quite possibly. I just cvsupped last night (moving from 4.1 RC0 to 4.1-STABLE), and mergemaster showed quite a few changes to many startup scripts to make them test variables in rc.conf that they did not previously test. If you didn't take those changes, then it doesn't matter if you took the new rc.conf, because the old startup scripts by and large ignored it. -- Chris BeHanna Software Engineer (at yourfit.com) behanna@zbzoom.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 16:25:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 0A5A237B42C for ; Tue, 22 Aug 2000 16:25:23 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e7MNPLK99841; Tue, 22 Aug 2000 16:25:21 -0700 (PDT) Date: Tue, 22 Aug 2000 16:25:21 -0700 (PDT) From: Doug White To: User Gilligan Cc: freebsd-stable@FreeBSD.ORG Subject: Re: automated freebsd stable installs. In-Reply-To: <39A171E8.F9BAAE26@cnmnetwork.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 21 Aug 2000, User Gilligan wrote: > I am installing FreeBSD on multiple machines on a LAN. I wanted to make > the install process easier by using install.cfg. Is there any > documentation out there other than the sample file > /usr/src/release/sysinstall/install.cfg? I'd like to see exactly what > my options are and how I could customize it. Installing the sysinstall manpage gives explanations for all the options. It should be living in src/release/sysinstall/sysinstall.8. Note that the file is very order-dependent. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 16:38:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from home.halden.net (mail.halden.net [195.70.189.219]) by hub.freebsd.org (Postfix) with ESMTP id E98B237B43E for ; Tue, 22 Aug 2000 16:38:22 -0700 (PDT) Received: from - (ppp-109.halden.net [195.70.189.109]) by home.halden.net (8.9.3/8.8.7) with SMTP id BAA32158 for ; Wed, 23 Aug 2000 01:38:20 +0200 From: .@online.no Message-Id: <3.0.6.32.20000823014154.00796650@online.no> X-Sender: .@online.no (Unverified) X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 23 Aug 2000 01:41:54 +0200 To: freebsd-stable@freebsd.org Subject: Wants FreeBSD 4.0 or 4.1 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. Does anybody in Norway have any chance of making a copy of FreeBSD 4.0 or 4.1 ? Thanks for replying. :-) - "The manual said Windows 98 or better, so I installed Linux..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 18:52:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from user1.erieonline.com (user1.erieonline.com [63.164.22.8]) by hub.freebsd.org (Postfix) with ESMTP id 0D77A37B42C for ; Tue, 22 Aug 2000 18:52:06 -0700 (PDT) Received: from localhost (iansmith@localhost) by user1.erieonline.com (8.9.3/8.9.3) with ESMTP id VAA18688; Tue, 22 Aug 2000 21:51:39 -0400 Date: Tue, 22 Aug 2000 21:51:39 -0400 (EDT) From: Smith@ian.org X-Sender: iansmith@user1.erieonline.com To: Chris Dillon Cc: Dermot McNally , freebsd-stable@FreeBSD.ORG, Fred Clift Subject: Re: Numbering of fxp devices 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, 22 Aug 2000, Chris Dillon wrote: > 7 NICs, one of which is dual-port, for a total of 8 ports. I recently > moved all of those NICs from a Compaq Proliant 3000 running 3.4-STABLE > into a new Proliant ML530 running 4.1-STABLE. The card order is > definately weird, but that isn't so much FreeBSD's fault. Compaq was > nice enough to label primary, secondary, and tertiary PCI bus slots on > the back of the machine, but they aren't in order anyway. What I > ended up doing was booting the system with all the cards installed, > noting the MAC address of each interface, and then comparing that to > physical slot locations. Not as nice as the sequential ordering in > the Proliant 3000, but not a big deal either, as long as it doesn't > change on me in the future without some warning. :-) Might I ask what 2-port card you are using? I have a router with limited slots.. 3 ethernet and four T1 ports currently. I also wonder if there woudl be a way to map cards based on their MAC addresses, or is the MAC address discovery done way too late? Hmm.. maybe some sort of aliasing? A conf file could list device numbers and MAC addresses, so once the kernel finished finding everything, it could look through the cards and asign /dev/ether0 to one, /dev/ether1 to another, ect. Thinking on that.. I do like the aliasing idea. Maybe a /dev/ethernet/ directory where each card is listed by it's MAC address, then given symbolic names to create normal /dev entries that also get listed with ifconfig and such. -- Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 20:21:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sanson.reyes.somos.net (freyes.static.inch.com [216.223.199.224]) by hub.freebsd.org (Postfix) with ESMTP id 5C46837B422 for ; Tue, 22 Aug 2000 20:21:54 -0700 (PDT) Received: from tomasa (tomasa.reyes.somos.net [10.0.0.11]) by sanson.reyes.somos.net (8.9.3/8.9.3) with SMTP id XAA27385; Tue, 22 Aug 2000 23:12:44 -0400 (EDT) (envelope-from fran@reyes.somos.net) Message-Id: <200008230312.XAA27385@sanson.reyes.somos.net> From: "Francisco Reyes" To: "Doug Barton" , "Peter Jeremy" Cc: "Brian Somers" , "Doug Barton" , "FreeBSD stable" , "Gerhard Sittig" , "Jason T" Date: Tue, 22 Aug 2000 22:56:35 -0400 Reply-To: "Francisco Reyes" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 98 (4.10.2222) In-Reply-To: <399CDD7F.BDD360D0@gorean.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: remove empty TEMPROOT dirs at mergemaster's end? (was: cvs commit:src/usr.sbin/mergemaster mergemaster.sh) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Aug 2000 23:53:51 -0700, Doug Barton wrote: > Yes, thanks. This is close to the top of the wishlist. Where is the wishlist for mergemaster? Is it kept anywhere visible? I have one thing I have been thinking on giving it a try in a few weeks. Changing mergemaster to indicate files to be either ignored or copied. Kind of an exception file. Haven't looked at the code so I don't know how difficult it would be. The basic idea is that there are files which ones knows in advance what one wants done with the file. For example I always move the locate script from weekly to daily. I don't want mergemater to stop to tell me the file is missing. So this file would be ignored. The other case is files which one want copied without questions. All the files in /etc/defaults I never touch so I would prefer them to be merged without questions. francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 20:47: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by hub.freebsd.org (Postfix) with ESMTP id 00F4C37B423 for ; Tue, 22 Aug 2000 20:47:00 -0700 (PDT) Received: from svzserv.kemerovo.su (kost.svzserv.kemerovo.su [213.184.65.82]) by www.svzserv.kemerovo.su (8.9.3/8.9.3) with ESMTP id LAA51946 for ; Wed, 23 Aug 2000 11:46:48 +0800 (KRAST) (envelope-from eugen@svzserv.kemerovo.su) Message-ID: <39A34969.AB504CFF@svzserv.kemerovo.su> Date: Wed, 23 Aug 2000 11:47:53 +0800 From: Eugene Grosbein Organization: SVZServ X-Mailer: Mozilla 4.7 [en] (Win95; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: /kernel: ppp0: bad fsc 5d93, pkt len 88 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I have a problem with pppd/FreeBSD 4.1-STABLE. These is a dial-in(getty+pppd) server. It's FreeBSD 3.5-STABLE. There is a client box with modem. It's dial-boot box: FreeBSD 4.1-STABLE/Windows95 OSR2. If I make a call from Windows, everything is OK: ppp connection is stable, http/ftp/telnet - all works. If I boot 4.1-STABLE and make a call using pppd, strange things happen: ppp connection seems to be stable, ppp0 interface is up, routing is right. But no packets from server are received. In server's /etc/ppp/ip-up I run 'ping' against client box. I see, client's modem receives packets (RD flashes), but firewall and bpfilter does not see packets. If I put 'kdebug 1' to client's /etc/ppp/options, for EVERY incoming packet, client's kernel writes to console: /kernel: ppp0: bad fsc 5d93, pkt len 88 Numbers differ from packet to packet. The question is: what's going on, why OSR2<->pppd works, but pppd<->pppd does not? Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 20:50: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 4930237B43C for ; Tue, 22 Aug 2000 20:50:51 -0700 (PDT) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id XAA30680; Tue, 22 Aug 2000 23:50:29 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Tue, 22 Aug 2000 23:50:29 -0400 (EDT) From: "Brandon D. Valentine" To: Francisco Reyes Cc: Doug Barton , Peter Jeremy , Brian Somers , Doug Barton , FreeBSD stable , Gerhard Sittig , Jason T Subject: Re: remove empty TEMPROOT dirs at mergemaster's end? (was: cvs commit:src/usr.sbin/mergemaster mergemaster.sh) In-Reply-To: <200008230312.XAA27385@sanson.reyes.somos.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, 22 Aug 2000, Francisco Reyes wrote: >The other case is files which one want copied without questions. >All the files in /etc/defaults I never touch so I would prefer >them to be merged without questions. I would think that in keeping with POLA /etc/defaults should be merged without questions anyway. We've already decreed that we won't support changing the contents of that directory, why can't we assume that it hasn't changed and upgrade it automatically? In fact, maybe that should just be part of the installworld. I do like your idea of allowing specific mergemaster exceptions, perhaps in a mergemaster.conf file, of course you've got to decide where to put it since it would traditionally live under /etc and get upgraded while mergemaster is running. ;-) Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 21: 7: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with SMTP id E8E7137B443 for ; Tue, 22 Aug 2000 21:06:57 -0700 (PDT) Received: by border.alcanet.com.au id <115225>; Wed, 23 Aug 2000 14:06:43 +1000 Content-return: prohibited Date: Wed, 23 Aug 2000 14:06:40 +1000 From: Peter Jeremy Subject: Re: remove empty TEMPROOT dirs at mergemaster's end? (was: cvs commit:src/usr.sbin/mergemaster mergemaster.sh) In-reply-to: ; from bandix@looksharp.net on Tue, Aug 22, 2000 at 11:50:29PM -0400 To: "Brandon D. Valentine" Cc: Francisco Reyes , Doug Barton , Brian Somers , Doug Barton , FreeBSD stable , Gerhard Sittig , Jason T Mail-followup-to: "Brandon D. Valentine" , Francisco Reyes , Doug Barton , Brian Somers , Doug Barton , FreeBSD stable , Gerhard Sittig , Jason T Message-Id: <00Aug23.140643est.115225@border.alcanet.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.4i References: <200008230312.XAA27385@sanson.reyes.somos.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Aug-22 23:50:29 -0400, "Brandon D. Valentine" wrote: >On Tue, 22 Aug 2000, Francisco Reyes wrote: > >>The other case is files which one want copied without questions. >>All the files in /etc/defaults I never touch so I would prefer >>them to be merged without questions. > >I would think that in keeping with POLA /etc/defaults should be merged >without questions anyway. But displaying the differences means that you get to see what has changed (and hence what changes are needed in your local overrides). As an example, rc.conf was recently changed (in -current) to not start inetd, portmap or sendmail. If you are actually relying on any of these daemons, and you actually notice the differences in /etc/defaults/rc.conf, you will be able to update /etc/rc.conf without a period of head-scratching when they don't start. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 21:11:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by hub.freebsd.org (Postfix) with ESMTP id 1A45237B43F for ; Tue, 22 Aug 2000 21:11:40 -0700 (PDT) Received: from svzserv.kemerovo.su (kost.svzserv.kemerovo.su [213.184.65.82]) by www.svzserv.kemerovo.su (8.9.3/8.9.3) with ESMTP id MAA55436 for ; Wed, 23 Aug 2000 12:11:38 +0800 (KRAST) (envelope-from eugen@svzserv.kemerovo.su) Message-ID: <39A34F3B.F599D853@svzserv.kemerovo.su> Date: Wed, 23 Aug 2000 12:12:43 +0800 From: Eugene Grosbein Organization: SVZServ X-Mailer: Mozilla 4.7 [en] (Win95; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: Re: /kernel: ppp0: bad fsc 5d93, pkt len 88 References: <39A34969.AB504CFF@svzserv.kemerovo.su> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eugene Grosbein wrote: > > Hello! > > I have a problem with pppd/FreeBSD 4.1-STABLE. > > These is a dial-in(getty+pppd) server. It's FreeBSD 3.5-STABLE. > There is a client box with modem. It's dial-boot box: > FreeBSD 4.1-STABLE/Windows95 OSR2. It's dual-boot, really ;) Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 21:12:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sanson.reyes.somos.net (freyes.static.inch.com [216.223.199.224]) by hub.freebsd.org (Postfix) with ESMTP id F17DB37B43E for ; Tue, 22 Aug 2000 21:12:40 -0700 (PDT) Received: from tomasa (tomasa.reyes.somos.net [10.0.0.11]) by sanson.reyes.somos.net (8.9.3/8.9.3) with SMTP id AAA27522; Wed, 23 Aug 2000 00:03:48 -0400 (EDT) (envelope-from fran@reyes.somos.net) Message-Id: <200008230403.AAA27522@sanson.reyes.somos.net> From: "Francisco Reyes" To: "Brandon D. Valentine" Cc: "Brian Somers" , "Doug Barton" , "Doug Barton" , "FreeBSD stable" , "Gerhard Sittig" , "Jason T" , "Peter Jeremy" Date: Tue, 22 Aug 2000 23:46:17 -0400 Reply-To: "Francisco Reyes" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 98 (4.10.2222) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: remove empty TEMPROOT dirs at mergemaster's end? (was: cvs commit:src/usr.sbin/mergemaster mergemaster.sh) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 22 Aug 2000 23:50:29 -0400 (EDT), Brandon D. Valentine wrote: >I would think that in keeping with POLA /etc/defaults should be merged >without questions anyway. That is one case, although probably not the only one. >hasn't changed and upgrade it automatically? In fact, maybe that should >just be part of the installworld. That is one way to think of it, but I am one for flexibility. If someone is stubborn enough that they want to mess around the files on that directory then we should let them be. I like the flexibility that mergemater gives us. >I do like your idea of allowing >specific mergemaster exceptions, perhaps in a mergemaster.conf file, Yes that is the best approach. >course you've got to decide where to put it since it would traditionally >live under /etc and get upgraded while mergemaster is running. ;-) This shouldn't be a problem. Read the existing file off from /etc/.. put the content on memory and process the rest. When it get's to /etc/mergemater.conf it will treat it as any other file.. francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 22:22:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from howys.mid-wales.net (howys.mid-wales.net [195.74.101.9]) by hub.freebsd.org (Postfix) with ESMTP id A03BE37B43C for ; Tue, 22 Aug 2000 22:22:08 -0700 (PDT) Received: from enta (warp10-17.enta-net.co.uk [195.74.115.18]) by howys.mid-wales.net (8.9.3/8.9.1) with SMTP id GAA20206 for ; Wed, 23 Aug 2000 06:22:07 +0100 (BST) (envelope-from webmaster@mid-wales.net) Message-ID: <015801c00cc0$1923bac0$0500a8c0@enta> From: "webmaster" To: "FreeBSD stable" Subject: remove unsubscribe please Date: Wed, 23 Aug 2000 06:07:54 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0155_01C00CC8.7A171720" 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_0155_01C00CC8.7A171720 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ------=_NextPart_000_0155_01C00CC8.7A171720 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
------=_NextPart_000_0155_01C00CC8.7A171720-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 22:22:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tepid.osl.fast.no (tepid.osl.fast.no [213.188.9.130]) by hub.freebsd.org (Postfix) with ESMTP id 1354037B43F for ; Tue, 22 Aug 2000 22:22:21 -0700 (PDT) Received: from raw.gren.fast.no (fw-oslo.fast.no [213.188.9.129]) by tepid.osl.fast.no (8.9.3/8.9.1) with ESMTP id FAA55139; Wed, 23 Aug 2000 05:30:55 GMT (envelope-from raw@fast.no) Received: (from raw@localhost) by raw.gren.fast.no (8.9.3/8.9.3) id HAA11050; Wed, 23 Aug 2000 07:23:50 +0200 (CEST) (envelope-from raw) From: Raymond Wiker MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14755.24549.997007.261354@raw.gren.fast.no> Date: Wed, 23 Aug 2000 07:23:49 +0200 (CEST) Cc: freebsd-stable@FreeBSD.ORG Subject: Wants FreeBSD 4.0 or 4.1 In-Reply-To: <3.0.6.32.20000823014154.00796650@online.no> References: <3.0.6.32.20000823014154.00796650@online.no> 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 .@online.no writes: > > Hello. > Does anybody in Norway have any chance of > making a copy of FreeBSD 4.0 or 4.1 ? > Thanks for replying. > :-) I have a copy of FreeBSD 4.0R in front of me that you can have. Alternatively, I might be able to locate a copy of 4.1R over the weekend. Send me a mail if you're interested (with a valid From: field, preferably :-) //Raymond. -- Raymond Wiker Raymond.Wiker@fast.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 22:52: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hq1.tyfon.net (hq1.tyfon.net [213.212.29.17]) by hub.freebsd.org (Postfix) with ESMTP id C02DE37B443; Tue, 22 Aug 2000 22:51:57 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hq1.tyfon.net (Postfix) with ESMTP id 4008A1C7BB; Wed, 23 Aug 2000 07:51:55 +0200 (CEST) Date: Wed, 23 Aug 2000 07:51:55 +0200 (CEST) From: Dan Larsson To: Kris Kennaway Cc: FreeBSD Stable List Subject: Re: Update perl along with src In-Reply-To: Message-ID: Organization: Tyfon Svenska AB 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, 22 Aug 2000, Kris Kennaway wrote: | > This is just a thought, would it be possible to update the perl modules | > along with the source when suping the src? make.conf feature? | | Which perl modules? Those in /usr/libdata/perl/5.00503/ such as CGI.pm and its likes. I'm manually updating these by running CPAN after installworld, this wouldn't be necessary if the most recent versions we're installed however. | Regards +------ Dan Larsson | Tel: +46 8 550 120 21 Tyfon Svenska AB | Fax: +46 8 550 120 02 Public PGP keys | finger dl@hq1.tyfon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 22 22:54:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E5D9E37B422; Tue, 22 Aug 2000 22:54:47 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id WAA33594; Tue, 22 Aug 2000 22:54:47 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 22 Aug 2000 22:54:47 -0700 (PDT) From: Kris Kennaway To: Dan Larsson Cc: FreeBSD Stable List Subject: Re: Update perl along with src 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 Wed, 23 Aug 2000, Dan Larsson wrote: > On Tue, 22 Aug 2000, Kris Kennaway wrote: > > | > This is just a thought, would it be possible to update the perl modules > | > along with the source when suping the src? make.conf feature? > | > | Which perl modules? > > Those in /usr/libdata/perl/5.00503/ such as CGI.pm and its likes. > I'm manually updating these by running CPAN after installworld, this > wouldn't be necessary if the most recent versions we're installed however. Then the answer is "Not under the current FreeBSD build infrastructure". 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 Aug 23 0:53:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from alpha.root-servers.ch (beta.root-servers.ch [195.49.33.19]) by hub.freebsd.org (Postfix) with SMTP id 58C5437B43E for ; Wed, 23 Aug 2000 00:53:08 -0700 (PDT) Received: (qmail 14202 invoked from network); 22 Aug 2000 15:53:05 -0000 Received: from client80-30.hispeed.ch (HELO 10.2.2.100) (62.2.80.30) by alpha.root-servers.ch with SMTP; 22 Aug 2000 15:53:05 -0000 Date: Tue, 22 Aug 2000 17:55:01 +0200 From: Gabriel Ambuehl X-Mailer: The Bat! (v1.45 Beta/6) Personal Organization: BUZ Internet Services X-Priority: 3 (Normal) Message-ID: <7070847783.20000822175501@buz.ch> To: Edward Wolpert Cc: stable@freebsd.org Subject: Re[3]: make installworld over NFS doesn't work anymore In-reply-To: <200008221500.JAA84714@cthulhu.methodsystems.com> References: <200008221500.JAA84714@cthulhu.methodsystems.com> 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 Edward, Tuesday, August 22, 2000, 5:00:25 PM, you wrote: > Actually, you can mount /usr/src read-only, but not /usr/obj. You see, Prior to the MFC, this worked this way. > the make process 'writes' to /usr/obj for this very reason. Try the > install again, but with the drives mounted rw. I don't like that. If one box with rw access gets cracked, /usr/obj isn't trustable anymore... (not so much of a problem, but I dislike rw exports in all cases > Might I ask why you want to /usr/obj mounted ro? s.a. > If you have to install in alot of systems, why not make an install cd? Those servers haven't got CDROM and I don't feel like I want to drive to them... Beside that, a release CD would cause a lot of extra work. Best regards, Gabriel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 1:49:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tribble.medianet.ie (tribble.medianet.ie [212.17.32.6]) by hub.freebsd.org (Postfix) with ESMTP id 69F2437B42C for ; Wed, 23 Aug 2000 01:49:32 -0700 (PDT) Received: [from teebar.traveldev.com (salmon.medianet.ie [212.17.34.207]) by tribble.medianet.ie (DIESPAM) with ESMTP id e7N8nLv24066; Wed, 23 Aug 2000 09:49:21 +0100] Received: from traveldev.com (dermot.traveldev.com [192.168.0.50]) by teebar.traveldev.com (8.10.2/8.10.2) with ESMTP id e7N8nOV84703; Wed, 23 Aug 2000 09:49:24 +0100 (IST) Message-ID: <39A39010.79E1FA94@traveldev.com> Date: Wed, 23 Aug 2000 09:49:20 +0100 From: Dermot McNally X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Smith@ian.org Cc: Chris Dillon , freebsd-stable@FreeBSD.ORG, Fred Clift Subject: Re: Numbering of fxp devices References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Smith@ian.org wrote: > I also wonder if there woudl be a way to map cards based on their > MAC addresses, or is the MAC address discovery done way too late? I thought about that too, but decided that somebody would hit me if I suggested it... Dermot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 2:18:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from srcso.globis.ru (globis.ru [212.248.80.7]) by hub.freebsd.org (Postfix) with ESMTP id 921F337B42C for ; Wed, 23 Aug 2000 02:17:55 -0700 (PDT) Received: from raduga.dyndns.org (raduga.sochi.net [212.248.82.76]) by srcso.globis.ru (8.9.3/8.9.3) with ESMTP id NAA12096 for ; Wed, 23 Aug 2000 13:33:17 +0400 (MSD) (envelope-from igor@raduga.dyndns.org) Received: (from igor@localhost) by raduga.dyndns.org (8.10.0/8.10.0) id e7N9HHR13394 for freebsd-stable@freebsd.org; Wed, 23 Aug 2000 13:17:17 +0400 Date: Wed, 23 Aug 2000 13:17:17 +0400 From: Igor Roboul To: freebsd-stable@freebsd.org Subject: Re: make installworld over NFS doesn't work anymore Message-ID: <20000823131717.B12927@linux.rainbow> Reply-To: igorr@crosswinds.net Mail-Followup-To: freebsd-stable@freebsd.org References: <200008221500.JAA84714@cthulhu.methodsystems.com> <7070847783.20000822175501@buz.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <7070847783.20000822175501@buz.ch>; from gabriel_ambuehl@buz.ch on Tue, Aug 22, 2000 at 05:55:01PM +0200 X-Operating-System: Linux linux.rainbow 2.2.14-plus-SMP X-Best-Window-Manager: Window Maker (www.windowmaker.org) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 22, 2000 at 05:55:01PM +0200, Gabriel Ambuehl wrote: > > I don't like that. If one box with rw access gets cracked, /usr/obj > isn't trustable anymore... (not so much of a problem, but I dislike rw > exports in all cases Hello, but, if I think correctly, /usr/obj is machine dependent? If you have two systems, for example i386 & i686, you can have common source (/usr/src) but on i686 you may have CFLAGS=-march=pentiumpro in /etc/make.conf and on i386 does not. So /usr/src can be RO and on NFS, but /usr/obj need to be local (or common for equal architectures and rw) -- Igor Roboul, Unix System Administrator & Programmer @ sanatorium "Raduga" http://www.brainbench.com/transcript.jsp?pid=304744 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 2:43:29 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 119FC37B42C for ; Wed, 23 Aug 2000 02:43:21 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 23 Aug 2000 10:43:20 +0100 (BST) Date: Wed, 23 Aug 2000 10:43:20 +0100 From: David Malone To: igorr@crosswinds.net Cc: freebsd-stable@freebsd.org Subject: Re: make installworld over NFS doesn't work anymore Message-ID: <20000823104320.A77324@walton.maths.tcd.ie> References: <200008221500.JAA84714@cthulhu.methodsystems.com> <7070847783.20000822175501@buz.ch> <20000823131717.B12927@linux.rainbow> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20000823131717.B12927@linux.rainbow>; from igor@raduga.dyndns.org on Wed, Aug 23, 2000 at 01:17:17PM +0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 23, 2000 at 01:17:17PM +0400, Igor Roboul wrote: > but, if I think correctly, /usr/obj is machine dependent? If you have > two systems, for example i386 & i686, you can have common source (/usr/src) > but on i686 you may have CFLAGS=-march=pentiumpro in /etc/make.conf and > on i386 does not. > So /usr/src can be RO and on NFS, but /usr/obj need to be local (or common for > equal architectures and rw) Not really - if you think about it the system people install when the install from CD is all built from one /usr/src and installed from one /usr/obj. If you want to build different versions, then you have that option but it certainly doesn't have to be that way. As far as I remember, installing from a ro /usr/obj has worked for quite a long time, and should be fixed if it is broken. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 3:19:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mix.unicon.ru (mix.unicon.ru [195.239.106.158]) by hub.freebsd.org (Postfix) with ESMTP id 8F3A637B422 for ; Wed, 23 Aug 2000 03:19:38 -0700 (PDT) Received: (from strange@localhost) by mix.unicon.ru (8.8.8/8.8.8) id RAA02918 for freebsd-stable@freebsd.org; Wed, 23 Aug 2000 17:19:37 +0700 (NSS) (envelope-from strange) Message-Id: <200008231019.RAA02918@mix.unicon.ru> Subject: SMP problems (was: How can I obtain -stable for previous date) In-Reply-To: <20000822173013.M20036@strontium.scientia.demon.co.uk> from Ben Smithurst at "Aug 22, 2000 5:30:13 pm" To: freebsd-stable@freebsd.org Date: Wed, 23 Aug 2000 17:19:36 +0700 (NSS) From: strange@unicon.ru X-Class: Fast 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 > > But after Aug 20, the system became unstable ;( > > It locks on hard loading (hard HDD usage), > > like a make release or even make buildworld ;( > > No panic, no crashdump, nothing, full lock... > > Just many HDD problems after hard reboot ;( > > or something to get the code from midnight on the 20th August. But > ideally you should try to find what is causing the problem, of course. It seems to me, the problem is in SMP code, because in 1 CPU configuration with the same kernel all works fine. And when 2 CPU is installed, simple make -j4 buildworld lock the system after little period of time... Unfortunatelly I cant find what changes was made in smp stuff... WBR SA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 3:36:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from srcso.globis.ru (globis.ru [212.248.80.7]) by hub.freebsd.org (Postfix) with ESMTP id EA73C37B423 for ; Wed, 23 Aug 2000 03:36:37 -0700 (PDT) Received: from raduga.dyndns.org (raduga.sochi.net [212.248.82.76]) by srcso.globis.ru (8.9.3/8.9.3) with ESMTP id OAA12277; Wed, 23 Aug 2000 14:52:01 +0400 (MSD) (envelope-from igor@raduga.dyndns.org) Received: (from igor@localhost) by raduga.dyndns.org (8.10.0/8.10.0) id e7NAaLU14140; Wed, 23 Aug 2000 14:36:21 +0400 Date: Wed, 23 Aug 2000 14:36:21 +0400 From: Igor Roboul To: David Malone Cc: freebsd-stable@freebsd.org Subject: Re: make installworld over NFS doesn't work anymore Message-ID: <20000823143621.B14103@linux.rainbow> Reply-To: igorr@crosswinds.net Mail-Followup-To: David Malone , freebsd-stable@freebsd.org References: <200008221500.JAA84714@cthulhu.methodsystems.com> <7070847783.20000822175501@buz.ch> <20000823131717.B12927@linux.rainbow> <20000823104320.A77324@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <20000823104320.A77324@walton.maths.tcd.ie>; from dwmalone@maths.tcd.ie on Wed, Aug 23, 2000 at 10:43:20AM +0100 X-Operating-System: Linux linux.rainbow 2.2.14-plus-SMP X-Best-Window-Manager: Window Maker (www.windowmaker.org) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 23, 2000 at 10:43:20AM +0100, David Malone wrote: > Not really - if you think about it the system people install when the > install from CD is all built from one /usr/src and installed from one > /usr/obj. If you want to build different versions, then you have that > option but it certainly doesn't have to be that way. > > As far as I remember, installing from a ro /usr/obj has worked for > quite a long time, and should be fixed if it is broken. But he wish _build_ cvsupped tree with read-only /usr/obj :-( -- Igor Roboul, Unix System Administrator & Programmer @ sanatorium "Raduga" http://www.brainbench.com/transcript.jsp?pid=304744 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 3:57:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from citadel.cequrux.com (citadel.cequrux.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id CDFA137B423 for ; Wed, 23 Aug 2000 03:57:36 -0700 (PDT) Received: (from nobody@localhost) by citadel.cequrux.com (8.8.8/8.6.9) id MAA27449 for ; Wed, 23 Aug 2000 12:57:28 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 27322; Wed Aug 23 12:56:24 2000 Message-ID: <39A3AE82.FFCD5C19@cequrux.com> Date: Wed, 23 Aug 2000 12:59:14 +0200 From: Graham Wheeler Organization: Cequrux Technologies X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 2.2.8-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Configuring kernel for ISA cards Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all I sent this to frebsd-questions a while back but got no response, so let me try again here. FreeBSD 3.x introduced the new boot loader stuff. One of the consequences was that changing the kernel config at boot time did not save the changes to the kernel permanently. Instead, it seems, these changes are supposed to go in /boot/loader.rc. The docs seem very sparse about all of this, unless I've somehow missed the relevant material. Now, I was told that the same commands can be used in the loader.rc file as are used in the configuration editor. However, it seems to me that this only holds for PCI cards. When I have tried to configure the IRQ for an ISA card, the loader has complained about a syntax error. I believe the command I used was: irq ed0 10 (I can't confirm for sure, as the machine in question has died a horrible death - came in on Monday morning and half therr libraries in /usr/lib had had their inodes toasted somehow - they were now device nodes with garbgae flags and major/minor number settings. Any attempt at writing to the disk caused a page fault panic. I switched the HDD to another machine with the same results, so I am now reinstalling the OS (3.4 in this case) and doing a bad block scan to see if that helps. But I digress...) Can anyone tell me the right way to specify an IRQ and port setting for a legacy ISA card, without recompiling the kernel? gram To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 4: 9:38 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 BB54937B422 for ; Wed, 23 Aug 2000 04:09:36 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 23 Aug 2000 12:09:36 +0100 (BST) To: igorr@crosswinds.net Cc: freebsd-stable@freebsd.org Subject: Re: make installworld over NFS doesn't work anymore In-reply-to: Your message of "Wed, 23 Aug 2000 14:36:21 +0400." <20000823143621.B14103@linux.rainbow> X-Request-Do: Date: Wed, 23 Aug 2000 12:09:35 +0100 From: David Malone Message-ID: <200008231209.aa19212@salmon.maths.tcd.ie> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > But he wish _build_ cvsupped tree with read-only /usr/obj :-( I thought the issue was installworlds from a read only /usr/obj? Maybe I haven't been following the thread closely enough. buildworlds on a read only /usr/obj - that really would be something ;-) David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 4:16: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from srcso.globis.ru (globis.ru [212.248.80.7]) by hub.freebsd.org (Postfix) with ESMTP id 1E3FC37B424 for ; Wed, 23 Aug 2000 04:15:58 -0700 (PDT) Received: from raduga.dyndns.org (raduga.sochi.net [212.248.82.76]) by srcso.globis.ru (8.9.3/8.9.3) with ESMTP id PAA12393; Wed, 23 Aug 2000 15:31:20 +0400 (MSD) (envelope-from igor@raduga.dyndns.org) Received: (from igor@localhost) by raduga.dyndns.org (8.10.0/8.10.0) id e7NBFcP14620; Wed, 23 Aug 2000 15:15:38 +0400 Date: Wed, 23 Aug 2000 15:15:38 +0400 From: Igor Roboul To: David Malone Cc: freebsd-stable@freebsd.org Subject: Re: make installworld over NFS doesn't work anymore Message-ID: <20000823151538.A14603@linux.rainbow> Reply-To: igorr@crosswinds.net Mail-Followup-To: David Malone , freebsd-stable@freebsd.org References: <20000823143621.B14103@linux.rainbow> <200008231209.aa19212@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <200008231209.aa19212@salmon.maths.tcd.ie>; from dwmalone@maths.tcd.ie on Wed, Aug 23, 2000 at 12:09:35PM +0100 X-Operating-System: Linux linux.rainbow 2.2.14-plus-SMP X-Best-Window-Manager: Window Maker (www.windowmaker.org) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 23, 2000 at 12:09:35PM +0100, David Malone wrote: > > But he wish _build_ cvsupped tree with read-only /usr/obj :-( > > I thought the issue was installworlds from a read only /usr/obj? > Maybe I haven't been following the thread closely enough. Or maybe I? :-) -- Igor Roboul, Unix System Administrator & Programmer @ sanatorium "Raduga" http://www.brainbench.com/transcript.jsp?pid=304744 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 4:30:52 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 7016837B422 for ; Wed, 23 Aug 2000 04:30:25 -0700 (PDT) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id NAA08389 for freebsd-stable@freebsd.org; Wed, 23 Aug 2000 13:30:10 +0200 (MET DST) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id NAA05073 for freebsd-stable@freebsd.org; Wed, 23 Aug 2000 13:18:11 +0200 (CEST) (envelope-from andreas) Date: Wed, 23 Aug 2000 13:18:11 +0200 From: Andreas Klemm To: freebsd-stable@freebsd.org Subject: 4.1-STABLE panics on boot with Huyundai Laptop (P233) Message-ID: <20000823131811.A4418@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.2.4i X-Operating-System: FreeBSD 4.1-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: multipart/mixed; boundary="yrj/dFKFPuw6o+aM" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline My Laptop only runs on FreeBSD 3.x. FreeBSD 4.0 4.1 4.1-STABLE 5.0-current -> only panic on boot. I compiled a kernel with DDB support. This are the last messages on screen: pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port 0x3f4-0x3f7,0x374-0x377,0x1f4-0x1f7,0x174-0x177 at device 1.1 on pci0 atapci0: Busmasterinf DMA not supported ata-: ata2 exists, using next available unit number panic: resource_list_alloc: resource entry is busy Debugger<"panic"> trace shows the kernel functions that have been called so far. Debugger(...) at Debugger+0x34 panic(...) at panic+0x70 resource_list_alloc(...) pci_alloc_resource(...) BUS_ALLOC_RESOURCE(...) ata_pci_alloc_resource(...) BUS_ALLOC_RESOURCE(...) bus_alloc_resource(...) ata_probe(...) ata_pcisub_probe(...) DEVICE_PROBE(...) device_probe_child(...) device_probe_and_attach(...) bus_generic_attach(...) ata_pci_attach(...) DEVICE_ATTACH(...) device_probe_and_attach(...) bus_generic_attach(...) DEVICE_ATTACH(...) device_probe_and_attach(...) bus_generic_attach(...) DEVICE_ATTACH(...) device_probe_and_attach(...) bus_generic_attach(...) nexus_attach(...) DEVICE_ATTACH(...) device_probe_and_attach(...) root_bus_configure(...) configure(...) mi_startup(...) begin(...) In the attachement a session of booting FreeBSD 3.5-STABLE with boot_verbose and the kernel profile. Hope you can help. -- Andreas Klemm Powered by FreeBSD SMP Songs from our band >>64Bits<<............http://www.apsfilter.org/64bits.html My homepage................................ http://people.FreeBSD.ORG/~andreas Please note: Apsfilter got a NEW HOME................http://www.apsfilter.org/ --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="LAPTOP.dmesg" the University of California. All rights reserved. FreeBSD 3.5-STABLE #1: Wed Aug 23 12:12:27 CEST 2000 root@laptop.klemm.gtn.com:/usr/src/sys/compile/LAPTOP Calibrating clock(s) ... TSC clock: 232524334 Hz, i8254 clock: 1193168 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/P55C (232.53-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Features=0x8001bf real memory = 67108864 (65536K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x002d3000 - 0x03ffdfff, 64139264 bytes (15659 pages) avail memory = 62328832 (60868K bytes) Found BIOS32 Service Directory header at 0xc00ec050 Entry = 0xee600 (0xc00ee600) Rev = 0 Len = 1 PCI BIOS entry at 0x263e Other BIOS signatures found: ACPI: 00000000 $PnP: 000ff000 Preloaded elf kernel "kernel.ok" at 0xc02be000. pci_open(1): mode 1 addr port (0x0cf8) is 0x80000068 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=04061039) Probing for devices on PCI bus 0: found-> vendor=0x1039, dev=0x0406, revid=0x00 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip0: rev 0x00 on pci0.0.0 found-> vendor=0x1039, dev=0x0008, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 chip1: rev 0x01 on pci0.1.0 found-> vendor=0x1039, dev=0x0601, revid=0x01 class=01-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 00000174, size 2 map[1]: type 4, range 32, base 000001f4, size 2 map[2]: type 4, range 32, base 00000374, size 2 map[3]: type 4, range 32, base 000003f4, size 2 chip2: rev 0x01 on pci0.1.1 found-> vendor=0x1023, dev=0x9660, revid=0xd3 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=255 map[0]: type 1, range 32, base 08000000, size 22 map[1]: type 1, range 32, base 08800000, size 16 map[2]: type 1, range 32, base 08400000, size 22 vga0: rev 0xd3 int a irq 255 on pci0.6.0 found-> vendor=0x119b, dev=0x1221, revid=0x02 class=06-05-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=0 map[0]: type 4, range 32, base 000003e0, size 2 chip3: rev 0x02 int a irq 0 on pci0.13.0 found-> vendor=0x119b, dev=0x1221, revid=0x02 class=06-05-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=0 map[0]: type 4, range 32, base 000003e4, size 2 chip4: rev 0x02 int a irq 0 on pci0.14.0 Initializing PnP override table Probing for PnP devices: Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 No Plug-n-Play devices were found Probing for devices on the ISA bus: atkbd: the current kbd controller command byte 0067 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa sc0 on isa sc0: fb0 kbd0 sc0: VGA color <8 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0067 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 1c 03 3c psm: status 1c 03 3c psm: status 1c 03 3c psm: data 08 00 00 psm: status 10 00 64 psm: status 00 02 64 psm: data 08 00 00 psm: status 00 02 64 psm0 irq 12 on isa psm0: APM hooks installed. psm0: model Generic PS/2 mouse, device ID 0-00, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 sio0: irq maps: 0x9 0x19 0x9 0x9 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A mss_probe: no address supplied, try default 0x530 mss_detect error, busy still set (0xff) sb_probe: no address supplied, try defaults (0x220,0x240) pcm0 at 0x220 irq 5 drq 1 on isa ESS1868 (rev 11) 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: 3102MB (6354432 sectors), 6304 cyls, 16 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007 wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, ovlap, dma, iordis wdc1: ATAPI CD-ROMs not configured ppc: parallel port found at 0x378 ppc: chipset forced to generic ppc0: EPP SPP ppc0 at 0x378 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 xe0 not found vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0x0 size:0k 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 0d 0e 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 npx0 on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 641436818 bytes/sec bzero() bandwidth = 331564986 bytes/sec apm0: disabled, not probed. imasks: bio c008c040, tty c003103a, net c0060080 device combination doesn't support shared irq3 intr_connect(irq3) failed, result=-1 device combination doesn't support shared irq4 intr_connect(irq4) failed, result=-1 device combination doesn't support shared irq5 intr_connect(irq5) failed, result=-1 device combination doesn't support shared irq7 intr_connect(irq7) failed, result=-1 device combination doesn't support shared irq12 intr_connect(irq12) failed, result=-1 device combination doesn't support shared irq14 intr_connect(irq14) failed, result=-1 device combination doesn't support shared irq15 intr_connect(irq15) failed, result=-1 PC-Card VLSI 82C146 (5 mem & 2 I/O windows) pcic: controller irq 9 Initializing PC-card drivers: xe sio BIOS Geometries: 0:03127f3f 0..786=787 cylinders, 0..127=128 heads, 1..63=63 sectors 1:03feff00 0..1022=1023 cylinders, 0..255=256 heads, 1..0=0 sectors 2:03fdfe3f 0..1021=1022 cylinders, 0..254=255 heads, 1..63=63 sectors 3:03fe0200 0..1022=1023 cylinders, 0..2=3 heads, 1..0=0 sectors 0 accounted for Device configuration finished. Intel Pentium detected, installing workaround for F00F bug IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to deny, logging limited to 100 packets/entry by default bpf: lo0 attached DUMMYNET initialized (000212) Considering FFS root f/s. changing root device to wd0s2a wd0s1: type 0xb, start 63, end = 3693311, size 3693249 : OK wd0s2: type 0xa5, start 3693312, end = 6354431, size 2661120 : OK start_init: trying /sbin/init Card inserted, slot 0 Card inserted, slot 1 xe0: Xircom CE3, bonding version 0x45, 100Mbps capable xe0: DingoID = 0x444b, RevisionID = 0, VendorID = 0 xe0: Ethernet address 00:80:c7:61:c2:9f bpf: xe0 attached pid 169 (ntpd), uid 0: exited on signal 12 (core dumped) Linux-ELF exec handler installed splash: image decoder found: logo_saver --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=LAPTOP machine "i386" cpu "I586_CPU" cpu "I686_CPU" ident LAPTOP maxusers 64 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console 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 wd0 controller isa0 controller pnp0 # PnP support for ISA controller pci0 # Floppy drives controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 # IDE controller and disks options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 # ATAPI devices options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM # atkbdc0 controls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? tty # Floating point support - do not disable. device npx0 at isa? port IO_NPX irq 13 # Power management support (see LINT for more options) device apm0 at isa? disable flags 0x31 # Advanced Power Management # PCCARD (PCMCIA) support controller card0 device pcic0 at card? device pcic1 at card? # Serial (COM) ports device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 # Parallel port # # Note: The ppc0 entry is configured to support networking over the # parallel port. If you will be using it for printing, change # "net" to "tty", and review ppc(4) to ensure you have the # correct flags value. device ppc0 at isa? port? flags 0x40 net irq 7 controller ppbus0 # Parallel port bus (required) device lpt0 at ppbus? # Printer device ppi0 at ppbus? # Parallel port interface device #device plip0 at ppbus? # TCP/IP over parallel # requires PCCARD (PCMCIA) support to be activated device xe0 at isa? port? net irq ? # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support #pseudo-device sl 1 # Kernel SLIP #pseudo-device ppp 1 # Kernel PPP #pseudo-device tun 1 # Packet tunnel pseudo-device pty 16 # Pseudo-ttys (telnet etc) pseudo-device gzip # Exec gzipped a.out's # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. pseudo-device bpfilter 1 #Berkeley packet filter options MROUTING # Multicast routing options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about dropped packets options IPFIREWALL_FORWARD #enable transparent proxy support options "IPFIREWALL_VERBOSE_LIMIT=100" #limit verbosity options IPDIVERT #divert sockets options IPSTEALTH #support for stealth forwarding options "ICMP_BANDLIM" options DUMMYNET options SOFTUPDATES options MAXCONS=8 # number of virtual consoles options SC_HISTORY_SIZE=512 # number of history buffer lines device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x0 options SHOW_BUSYBUFS # List buffers that prevent root unmount options DDB --yrj/dFKFPuw6o+aM-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 5:16: 0 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 6F5C137B423 for ; Wed, 23 Aug 2000 05:15:36 -0700 (PDT) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id OAA12045 for freebsd-stable@FreeBSD.ORG; Wed, 23 Aug 2000 14:15:20 +0200 (MET DST) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id OAA13119; Wed, 23 Aug 2000 14:13:01 +0200 (CEST) (envelope-from andreas) Date: Wed, 23 Aug 2000 14:13:01 +0200 From: Andreas Klemm To: Andreas Klemm Cc: freebsd-stable@FreeBSD.ORG Subject: debug session (with comsonsole) Re: 4.1-STABLE panics on boot with Huyundai Laptop (P233)) Message-ID: <20000823141301.A13102@titan.klemm.gtn.com> References: <20000823131811.A4418@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Mutt/1.2.4i In-Reply-To: <20000823131811.A4418@titan.klemm.gtn.com>; from andreas@klemm.gtn.com on Wed, Aug 23, 2000 at 01:18:11PM +0200 X-Operating-System: FreeBSD 4.1-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 disk1s2a:> set boot_verbose=3D1 disk1s2a:> load kernel \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/= =08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08/kernel = text=3D0x132f17 -=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|= =08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08= \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/= =08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08= |=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-= =08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08= /=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\= =08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08= -=08\=08|=08/=08-=08\=08|=08/=08-=08\=08data=3D0x1aa38+0x1cc20 |=08/=08-=08= \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08syms=3D[0x4+0x22e80-=08\=08|=08= /=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08+0x4+0x2776b|= =08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08] disk1s2a:> boot Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.1-STABLE #0: Wed Aug 23 13:34:52 CEST 2000 root@titan.klemm.gtn.com:/usr/src/sys/compile/LAPTOP4 Calibrating clock(s) ... TSC clock: 232523307 Hz, i8254 clock: 1193163 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/P55C (232.53-MHz 586-class CPU) Origin =3D "GenuineIntel" Id =3D 0x543 Stepping =3D 3 Features=3D0x8001bf real memory =3D 67108864 (65536K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x002d0000 - 0x03ff7fff, 64126976 bytes (15656 pages) avail memory =3D 62615552 (61148K bytes) bios32: Found BIOS32 Service Directory header at 0xc00ec050 bios32: Entry =3D 0xee600 (c00ee600) Rev =3D 0 Len =3D 1 pcibios: PCI BIOS entry at 0x263e pnpbios: Found PnP BIOS data at 0xc00ff000 pnpbios: Entry =3D ea000:13de Rev =3D 1.0 pnpbios: OEM ID 744e Other BIOS signatures found: ACPI: 00000000 Preloaded elf kernel "kernel" at 0xc02b7000. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk Creating DISK md0 Math emulator present pci_open(1): mode 1 addr port (0x0cf8) is 0x800008b0 pci_open(1a): mode1res=3D0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=3D060000] [hdr=3D00] is there (id=3D04061039) pcib-: pcib0 exists, using next available unit number npx0: on motherboard npx0: INT 16 interface i586_bzero() bandwidth =3D 644329896 bytes/sec bzero() bandwidth =3D 331785003 bytes/sec pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=3D0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=3D060000] [hdr=3D00] is there (id=3D04061039) pcib0: on motherboard found-> vendor=3D0x1039, dev=3D0x0406, revid=3D0x00 class=3D06-00-00, hdrtype=3D0x00, mfdev=3D0 subordinatebus=3D0 secondarybus=3D0 found-> vendor=3D0x1039, dev=3D0x0008, revid=3D0x01 class=3D06-01-00, hdrtype=3D0x00, mfdev=3D1 subordinatebus=3D0 secondarybus=3D0 found-> vendor=3D0x1039, dev=3D0x0601, revid=3D0x01 class=3D01-01-00, hdrtype=3D0x00, mfdev=3D1 subordinatebus=3D0 secondarybus=3D0 map[10]: type 1, range 32, base 00000174, size 2 map[14]: type 1, range 32, base 000001f4, size 2 map[18]: type 1, range 32, base 00000374, size 2 map[1c]: type 1, range 32, base 000003f4, size 2 found-> vendor=3D0x1023, dev=3D0x9660, revid=3D0xd3 class=3D03-00-00, hdrtype=3D0x00, mfdev=3D0 subordinatebus=3D0 secondarybus=3D0 intpin=3Da, irq=3D255 map[10]: type 1, range 32, base 08000000, size 22 map[14]: type 1, range 32, base 08800000, size 16 map[18]: type 1, range 32, base 08400000, size 22 found-> vendor=3D0x119b, dev=3D0x1221, revid=3D0x02 class=3D06-05-00, hdrtype=3D0x00, mfdev=3D0 subordinatebus=3D0 secondarybus=3D0 intpin=3Da, irq=3D0 map[10]: type 1, range 32, base 000003e0, size 2 found-> vendor=3D0x119b, dev=3D0x1221, revid=3D0x02 class=3D06-05-00, hdrtype=3D0x00, mfdev=3D0 subordinatebus=3D0 secondarybus=3D0 intpin=3Da, irq=3D0 map[10]: type 1, range 32, base 000003e4, size 2 pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port 0x3f4-0x3f7,0x374-0x377,0x1f4-0x= 1f7,0x174-0x177 at device 1.1 on pci0 atapci0: Busmastering DMA not supported ata-: ata2 exists, using next available unit number panic: resource_list_alloc: resource entry is busy Debugger("panic") Stopped at Debugger+0x34: movb $0,in_Debugger.390 db> trace Debugger(c0211d03) at Debugger+0x34 panic(c0212680,2,1,ffffffff,1) at panic+0x70 resource_list_alloc(c0a1fe04,c0a1e080,c0a1fd80,4,c02cbd4c) at resource_list= _alloc+0xa0 pci_alloc_resource(c0a1e080,c0a1fd80,4,c02cbd4c,0) at pci_alloc_resource+0x= 38 BUS_ALLOC_RESOURCE(c0a1e080,c0a1fd80,4,c02cbd4c,0) at BUS_ALLOC_RESOURCE+0x= 43 ata_pci_alloc_resource(c0a1fd80,c0a1f880,4,c02cbde8,0) at ata_pci_alloc_res= ource+0x1be BUS_ALLOC_RESOURCE(c0a1fd80,c0a1f880,4,c02cbde8,0) at BUS_ALLOC_RESOURCE+0x= 43 bus_alloc_resource(c0a1f880,4,c02cbde8,0,ffffffff) at bus_alloc_resource+0x= 27 ata_probe(c0a1f880,c0a1f880,c0593a10,6011039,c02cbe10) at ata_probe+0xc9 ata_pcisub_probe(c0a1f880,c02cbe38,c0143459,c0a1f880,c0a1f880) at ata_pcisu= b_probe+0xc4 DEVICE_PROBE(c0a1f880,c0a1f880,c0a1fd80,0,1) at DEVICE_PROBE+0x2e device_probe_child(c0a1fd80,c0a1f880,c0a1f880,6011039,2000001) at device_pr= obe_child+0xc1 device_probe_and_attach(c0a1f880) at device_probe_and_attach+0x29 bus_generic_attach(c0a1fd80,c0a1fd80,c0a1e080,0,c0a1f900) at bus_generic_at= tach+0x16 ata_pci_attach(c0a1fd80,c02cbec4,c0143983,c0a1fd80,c0a1fd80) at ata_pci_att= ach+0x40d DEVICE_ATTACH(c0a1fd80,c0a1fd80,c0a1e180,0,c02cbed4) at DEVICE_ATTACH+0x2e device_probe_and_attach(c0a1fd80) at device_probe_and_attach+0x4f bus_generic_attach(c0a1e080,c02cbef8,c0143983,c0a1e080,c0a1e080) at bus_gen= eric_attach+0x16 DEVICE_ATTACH(c0a1e080,c0a1e080,c0a1e300,0,c02cbf08) at DEVICE_ATTACH+0x2e device_probe_and_attach(c0a1e080) at device_probe_and_attach+0x4f bus_generic_attach(c0a1e180,c02cbf2c,c0143983,c0a1e180,c0a1e180) at bus_gen= eric_attach+0x16 DEVICE_ATTACH(c0a1e180,c0a1e180,c0596880,0,c02cbf3c) at DEVICE_ATTACH+0x2e device_probe_and_attach(c0a1e180) at device_probe_and_attach+0x4f bus_generic_attach(c0a1e300,c0a1e300,c02cbf58,c011cb9e,c0a1e300) at bus_gen= eric_attach+0x16 nexus_attach(c0a1e300,c02cbf70,c0143983,c0a1e300,c0a1e300) at nexus_attach+= 0xd DEVICE_ATTACH(c0a1e300,c0a1e300,c0245a10,2d0000,c02cbf80) at DEVICE_ATTACH+= 0x2e device_probe_and_attach(c0a1e300) at device_probe_and_attach+0x4f root_bus_configure(c0596880,c022904c,0) at root_bus_configure+0x16 configure(0,2c9c00,2d0000,0,c011c5a4) at configure+0x33 mi_startup(c02cbfb4,b0206,ffe,2d0000,c0148071) at mi_startup+0x70 begin() at begin+0x4b NOW I SIMPLY TRIED TO BOOT ANY FURTHER BY CALLING mi_startup db> call mi_startup nexus-: nexus0 exists, using next available unit number apm-: apm0 exists, using next available unit number npx-: npx0 exists, using next available unit number pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=3D0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=3D060000] [hdr=3D00] is there (id=3D04061039) pcib-: pcib0 exists, using next available unit number pcib-: pcib0 exists, using next available unit number npx1: on motherboard npx1: INT 16 interface i586_bzero() bandwidth =3D 644745325 bytes/sec bzero() bandwidth =3D 645577792 bytes/sec pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=3D0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=3D060000] [hdr=3D00] is there (id=3D04061039) pcib2: on motherboard pci2: on pcib2 pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=3D0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=3D060000] [hdr=3D00] is there (id=3D04061039) pcib3: on motherboard pci3: on pcib3 Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices 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 ata0: iobase=3D0x01f0 altiobase=3D0x03f6 bmaddr=3D0x0000 ata0: mask=3D03 status0=3D50 status1=3D00 ata0: mask=3D03 status0=3D50 status1=3D00 ata0: devices =3D 0x1 ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata1: iobase=3D0x0170 altiobase=3D0x0376 bmaddr=3D0x0000 ata1: mask=3D03 status0=3D50 status1=3D01 ata1: mask=3D03 status0=3D00 status1=3D01 ata1: devices =3D 0xc ata1 at port 0x170-0x177,0x376 irq 15 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 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 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x1d0000 psm0: current command byte:0067 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 1c 03 3c psm: status 1c 03 3c psm: status 1c 03 3c psm: data 08 00 00 psm: status 10 00 64 psm: status 00 02 64 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0-00, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f 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=20 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96=20 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c=20 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff=20 VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81=20 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96=20 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c=20 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff=20 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=20 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96=20 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c=20 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff=20 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x100> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) pcic0: at port 0x3e0 iomem 0xd0000 irq 10 on isa0 pcic0: management irq 10 pccard0: on pcic0 pccard1: on pcic0 pcic1: not probed (disabled) sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x90 on isa0 sio0: type 16550A, console sio1: irq maps: 0x41 0x49 0x41 0x41 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: parallel port found at 0x378 ppc0: using extended I/O port range ppc0: EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 isa_probe_children: probing PnP devices BIOS Geometries: 0:03127f3f 0..786=3D787 cylinders, 0..127=3D128 heads, 1..63=3D63 sectors 1:03feff00 0..1022=3D1023 cylinders, 0..255=3D256 heads, 1..0=3D0 sectors 2:03fdfe3f 0..1021=3D1022 cylinders, 0..254=3D255 heads, 1..63=3D63 sectors 3:03fe0200 0..1022=3D1023 cylinders, 0..2=3D3 heads, 1..0=3D0 sectors 0 accounted for Device configuration finished. bpf: faith0 attached bpf: gif0 attached bpf: gif1 attached bpf: gif2 attached bpf: gif3 attached bpf: lo0 attached pccard: card inserted, slot 0 pccard: card inserted, slot 1 ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: ATA-3 disk at ata0 as master ad0: 3102MB (6354432 sectors), 6304 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, BIOSPIO ad0: piomode=3D4 dmamode=3D2 udmamode=3D2 cblid=3D0 Creating DISK ad0 Creating DISK wd0 Mounting root from ufs:wd0s2a wd0s1: type 0xb, start 63, end =3D 3693311, size 3693249 : OK wd0s2: type 0xa5, start 3693312, end =3D 6354431, size 2661120 : OK here the session and the machine hangs .... --=20 Andreas Klemm Powered by FreeBSD = SMP Songs from our band >>64Bits<<............http://www.apsfilter.org/64bits.h= tml My homepage................................ http://people.FreeBSD.ORG/~andr= eas Please note: Apsfilter got a NEW HOME................http://www.apsfilter.o= rg/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 5:56:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id 717E337B43C for ; Wed, 23 Aug 2000 05:56:38 -0700 (PDT) Received: from hamlet.nectar.com (hamlet.nectar.com [10.0.1.102]) by gw.nectar.com (Postfix) with ESMTP id D5EF71925D; Wed, 23 Aug 2000 07:56:37 -0500 (CDT) Received: (from nectar@localhost) by hamlet.nectar.com (8.9.3/8.9.3) id HAA08938; Wed, 23 Aug 2000 07:56:37 -0500 (CDT) (envelope-from nectar@spawn.nectar.com) Date: Wed, 23 Aug 2000 07:56:37 -0500 From: "Jacques A. Vidrine" To: Zigron Cc: freebsd-stable@freebsd.org Subject: Re: 4.1-STABLE and usb mice? Message-ID: <20000823075637.B1471@hamlet.nectar.com> Mail-Followup-To: "Jacques A. Vidrine" , Zigron , freebsd-stable@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from zigron@usa.net on Mon, Aug 21, 2000 at 11:55:27AM -0700 X-Url: http://www.nectar.com/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 21, 2000 at 11:55:27AM -0700, Zigron wrote: > Ever since I upgraded to 4.1-STABLE (about a week and a half ago, via > CVSup), i've been having trouble with my Microsoft Intellimouse > Explorer. The mouse-driver seems to die/crash in situations where my HDD > is rather busy, e.g. copying huge files, doing big-greps, etcetera. Very interesting. This is similar to symptoms I've seen (in 4.0-STABLE and 4.1-STABLE) with an Intellimouse, except using the PS/2 interface. When there is heavy disk activity, the mouse freaks out. Restarting moused recovers (though I have to restart X). After seeing your message, I just switched the mouse over to the USB interface to see what happens. -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 6: 1: 0 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 7975837B424 for ; Wed, 23 Aug 2000 06:00:41 -0700 (PDT) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id PAA15110 for freebsd-stable@freebsd.org; Wed, 23 Aug 2000 15:00:25 +0200 (MET DST) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id OAA15690 for freebsd-stable@freebsd.org; Wed, 23 Aug 2000 14:57:59 +0200 (CEST) (envelope-from andreas) Date: Wed, 23 Aug 2000 14:57:59 +0200 From: Andreas Klemm To: freebsd-stable@freebsd.org Subject: [andreas@klemm.gtn.com: debug session (with comsonsole) Re: 4.1-STABLE panics on boot with Huyundai Laptop (P233))] Message-ID: <20000823145759.B15421@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.2.4i X-Operating-System: FreeBSD 4.1-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: multipart/mixed; boundary="CUfgB8w4ZwR/yMy5" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --CUfgB8w4ZwR/yMy5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline This mail didn't show up after an hour or so, therefor I re-mail it, since it contains more complete debug session and is important for solving the problem, if there would be any taker. -- Andreas Klemm Powered by FreeBSD SMP Songs from our band >>64Bits<<............http://www.apsfilter.org/64bits.html My homepage................................ http://people.FreeBSD.ORG/~andreas Please note: Apsfilter got a NEW HOME................http://www.apsfilter.org/ --CUfgB8w4ZwR/yMy5 Content-Type: message/rfc822 Content-Disposition: inline Date: Wed, 23 Aug 2000 14:13:01 +0200 From: Andreas Klemm To: Andreas Klemm Cc: freebsd-stable@FreeBSD.ORG Subject: debug session (with comsonsole) Re: 4.1-STABLE panics on boot with Huyundai Laptop (P233)) Message-ID: <20000823141301.A13102@titan.klemm.gtn.com> References: <20000823131811.A4418@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Mutt/1.2.4i In-Reply-To: <20000823131811.A4418@titan.klemm.gtn.com>; from andreas@klemm.gtn.com on Wed, Aug 23, 2000 at 01:18:11PM +0200 X-Operating-System: FreeBSD 4.1-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular disk1s2a:> set boot_verbose=3D1 disk1s2a:> load kernel \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/= =08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08/kernel = text=3D0x132f17 -=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|= =08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08= \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/= =08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08= |=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-= =08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08= /=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\= =08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08= -=08\=08|=08/=08-=08\=08|=08/=08-=08\=08data=3D0x1aa38+0x1cc20 |=08/=08-=08= \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08syms=3D[0x4+0x22e80-=08\=08|=08= /=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08+0x4+0x2776b|= =08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08] disk1s2a:> boot Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.1-STABLE #0: Wed Aug 23 13:34:52 CEST 2000 root@titan.klemm.gtn.com:/usr/src/sys/compile/LAPTOP4 Calibrating clock(s) ... TSC clock: 232523307 Hz, i8254 clock: 1193163 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/P55C (232.53-MHz 586-class CPU) Origin =3D "GenuineIntel" Id =3D 0x543 Stepping =3D 3 Features=3D0x8001bf real memory =3D 67108864 (65536K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x002d0000 - 0x03ff7fff, 64126976 bytes (15656 pages) avail memory =3D 62615552 (61148K bytes) bios32: Found BIOS32 Service Directory header at 0xc00ec050 bios32: Entry =3D 0xee600 (c00ee600) Rev =3D 0 Len =3D 1 pcibios: PCI BIOS entry at 0x263e pnpbios: Found PnP BIOS data at 0xc00ff000 pnpbios: Entry =3D ea000:13de Rev =3D 1.0 pnpbios: OEM ID 744e Other BIOS signatures found: ACPI: 00000000 Preloaded elf kernel "kernel" at 0xc02b7000. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk Creating DISK md0 Math emulator present pci_open(1): mode 1 addr port (0x0cf8) is 0x800008b0 pci_open(1a): mode1res=3D0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=3D060000] [hdr=3D00] is there (id=3D04061039) pcib-: pcib0 exists, using next available unit number npx0: on motherboard npx0: INT 16 interface i586_bzero() bandwidth =3D 644329896 bytes/sec bzero() bandwidth =3D 331785003 bytes/sec pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=3D0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=3D060000] [hdr=3D00] is there (id=3D04061039) pcib0: on motherboard found-> vendor=3D0x1039, dev=3D0x0406, revid=3D0x00 class=3D06-00-00, hdrtype=3D0x00, mfdev=3D0 subordinatebus=3D0 secondarybus=3D0 found-> vendor=3D0x1039, dev=3D0x0008, revid=3D0x01 class=3D06-01-00, hdrtype=3D0x00, mfdev=3D1 subordinatebus=3D0 secondarybus=3D0 found-> vendor=3D0x1039, dev=3D0x0601, revid=3D0x01 class=3D01-01-00, hdrtype=3D0x00, mfdev=3D1 subordinatebus=3D0 secondarybus=3D0 map[10]: type 1, range 32, base 00000174, size 2 map[14]: type 1, range 32, base 000001f4, size 2 map[18]: type 1, range 32, base 00000374, size 2 map[1c]: type 1, range 32, base 000003f4, size 2 found-> vendor=3D0x1023, dev=3D0x9660, revid=3D0xd3 class=3D03-00-00, hdrtype=3D0x00, mfdev=3D0 subordinatebus=3D0 secondarybus=3D0 intpin=3Da, irq=3D255 map[10]: type 1, range 32, base 08000000, size 22 map[14]: type 1, range 32, base 08800000, size 16 map[18]: type 1, range 32, base 08400000, size 22 found-> vendor=3D0x119b, dev=3D0x1221, revid=3D0x02 class=3D06-05-00, hdrtype=3D0x00, mfdev=3D0 subordinatebus=3D0 secondarybus=3D0 intpin=3Da, irq=3D0 map[10]: type 1, range 32, base 000003e0, size 2 found-> vendor=3D0x119b, dev=3D0x1221, revid=3D0x02 class=3D06-05-00, hdrtype=3D0x00, mfdev=3D0 subordinatebus=3D0 secondarybus=3D0 intpin=3Da, irq=3D0 map[10]: type 1, range 32, base 000003e4, size 2 pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port 0x3f4-0x3f7,0x374-0x377,0x1f4-0x= 1f7,0x174-0x177 at device 1.1 on pci0 atapci0: Busmastering DMA not supported ata-: ata2 exists, using next available unit number panic: resource_list_alloc: resource entry is busy Debugger("panic") Stopped at Debugger+0x34: movb $0,in_Debugger.390 db> trace Debugger(c0211d03) at Debugger+0x34 panic(c0212680,2,1,ffffffff,1) at panic+0x70 resource_list_alloc(c0a1fe04,c0a1e080,c0a1fd80,4,c02cbd4c) at resource_list= _alloc+0xa0 pci_alloc_resource(c0a1e080,c0a1fd80,4,c02cbd4c,0) at pci_alloc_resource+0x= 38 BUS_ALLOC_RESOURCE(c0a1e080,c0a1fd80,4,c02cbd4c,0) at BUS_ALLOC_RESOURCE+0x= 43 ata_pci_alloc_resource(c0a1fd80,c0a1f880,4,c02cbde8,0) at ata_pci_alloc_res= ource+0x1be BUS_ALLOC_RESOURCE(c0a1fd80,c0a1f880,4,c02cbde8,0) at BUS_ALLOC_RESOURCE+0x= 43 bus_alloc_resource(c0a1f880,4,c02cbde8,0,ffffffff) at bus_alloc_resource+0x= 27 ata_probe(c0a1f880,c0a1f880,c0593a10,6011039,c02cbe10) at ata_probe+0xc9 ata_pcisub_probe(c0a1f880,c02cbe38,c0143459,c0a1f880,c0a1f880) at ata_pcisu= b_probe+0xc4 DEVICE_PROBE(c0a1f880,c0a1f880,c0a1fd80,0,1) at DEVICE_PROBE+0x2e device_probe_child(c0a1fd80,c0a1f880,c0a1f880,6011039,2000001) at device_pr= obe_child+0xc1 device_probe_and_attach(c0a1f880) at device_probe_and_attach+0x29 bus_generic_attach(c0a1fd80,c0a1fd80,c0a1e080,0,c0a1f900) at bus_generic_at= tach+0x16 ata_pci_attach(c0a1fd80,c02cbec4,c0143983,c0a1fd80,c0a1fd80) at ata_pci_att= ach+0x40d DEVICE_ATTACH(c0a1fd80,c0a1fd80,c0a1e180,0,c02cbed4) at DEVICE_ATTACH+0x2e device_probe_and_attach(c0a1fd80) at device_probe_and_attach+0x4f bus_generic_attach(c0a1e080,c02cbef8,c0143983,c0a1e080,c0a1e080) at bus_gen= eric_attach+0x16 DEVICE_ATTACH(c0a1e080,c0a1e080,c0a1e300,0,c02cbf08) at DEVICE_ATTACH+0x2e device_probe_and_attach(c0a1e080) at device_probe_and_attach+0x4f bus_generic_attach(c0a1e180,c02cbf2c,c0143983,c0a1e180,c0a1e180) at bus_gen= eric_attach+0x16 DEVICE_ATTACH(c0a1e180,c0a1e180,c0596880,0,c02cbf3c) at DEVICE_ATTACH+0x2e device_probe_and_attach(c0a1e180) at device_probe_and_attach+0x4f bus_generic_attach(c0a1e300,c0a1e300,c02cbf58,c011cb9e,c0a1e300) at bus_gen= eric_attach+0x16 nexus_attach(c0a1e300,c02cbf70,c0143983,c0a1e300,c0a1e300) at nexus_attach+= 0xd DEVICE_ATTACH(c0a1e300,c0a1e300,c0245a10,2d0000,c02cbf80) at DEVICE_ATTACH+= 0x2e device_probe_and_attach(c0a1e300) at device_probe_and_attach+0x4f root_bus_configure(c0596880,c022904c,0) at root_bus_configure+0x16 configure(0,2c9c00,2d0000,0,c011c5a4) at configure+0x33 mi_startup(c02cbfb4,b0206,ffe,2d0000,c0148071) at mi_startup+0x70 begin() at begin+0x4b NOW I SIMPLY TRIED TO BOOT ANY FURTHER BY CALLING mi_startup db> call mi_startup nexus-: nexus0 exists, using next available unit number apm-: apm0 exists, using next available unit number npx-: npx0 exists, using next available unit number pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=3D0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=3D060000] [hdr=3D00] is there (id=3D04061039) pcib-: pcib0 exists, using next available unit number pcib-: pcib0 exists, using next available unit number npx1: on motherboard npx1: INT 16 interface i586_bzero() bandwidth =3D 644745325 bytes/sec bzero() bandwidth =3D 645577792 bytes/sec pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=3D0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=3D060000] [hdr=3D00] is there (id=3D04061039) pcib2: on motherboard pci2: on pcib2 pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=3D0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=3D060000] [hdr=3D00] is there (id=3D04061039) pcib3: on motherboard pci3: on pcib3 Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices 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 ata0: iobase=3D0x01f0 altiobase=3D0x03f6 bmaddr=3D0x0000 ata0: mask=3D03 status0=3D50 status1=3D00 ata0: mask=3D03 status0=3D50 status1=3D00 ata0: devices =3D 0x1 ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata1: iobase=3D0x0170 altiobase=3D0x0376 bmaddr=3D0x0000 ata1: mask=3D03 status0=3D50 status1=3D01 ata1: mask=3D03 status0=3D00 status1=3D01 ata1: devices =3D 0xc ata1 at port 0x170-0x177,0x376 irq 15 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 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 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x1d0000 psm0: current command byte:0067 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 1c 03 3c psm: status 1c 03 3c psm: status 1c 03 3c psm: data 08 00 00 psm: status 10 00 64 psm: status 00 02 64 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0-00, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f 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=20 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96=20 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c=20 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff=20 VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81=20 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96=20 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c=20 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff=20 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=20 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96=20 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c=20 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff=20 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x100> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) pcic0: at port 0x3e0 iomem 0xd0000 irq 10 on isa0 pcic0: management irq 10 pccard0: on pcic0 pccard1: on pcic0 pcic1: not probed (disabled) sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x90 on isa0 sio0: type 16550A, console sio1: irq maps: 0x41 0x49 0x41 0x41 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: parallel port found at 0x378 ppc0: using extended I/O port range ppc0: EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 isa_probe_children: probing PnP devices BIOS Geometries: 0:03127f3f 0..786=3D787 cylinders, 0..127=3D128 heads, 1..63=3D63 sectors 1:03feff00 0..1022=3D1023 cylinders, 0..255=3D256 heads, 1..0=3D0 sectors 2:03fdfe3f 0..1021=3D1022 cylinders, 0..254=3D255 heads, 1..63=3D63 sectors 3:03fe0200 0..1022=3D1023 cylinders, 0..2=3D3 heads, 1..0=3D0 sectors 0 accounted for Device configuration finished. bpf: faith0 attached bpf: gif0 attached bpf: gif1 attached bpf: gif2 attached bpf: gif3 attached bpf: lo0 attached pccard: card inserted, slot 0 pccard: card inserted, slot 1 ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: ATA-3 disk at ata0 as master ad0: 3102MB (6354432 sectors), 6304 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, BIOSPIO ad0: piomode=3D4 dmamode=3D2 udmamode=3D2 cblid=3D0 Creating DISK ad0 Creating DISK wd0 Mounting root from ufs:wd0s2a wd0s1: type 0xb, start 63, end =3D 3693311, size 3693249 : OK wd0s2: type 0xa5, start 3693312, end =3D 6354431, size 2661120 : OK here the session and the machine hangs .... --=20 Andreas Klemm Powered by FreeBSD = SMP Songs from our band >>64Bits<<............http://www.apsfilter.org/64bits.h= tml My homepage................................ http://people.FreeBSD.ORG/~andr= eas Please note: Apsfilter got a NEW HOME................http://www.apsfilter.o= rg/ --CUfgB8w4ZwR/yMy5-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 6:23:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from magpage.com (trinity.magpage.com [216.155.0.8]) by hub.freebsd.org (Postfix) with ESMTP id 34C9F37B42C for ; Wed, 23 Aug 2000 06:23:27 -0700 (PDT) Received: from magpage.com (poomba.magpage.com [216.155.24.136]) by magpage.com (8.8.8/8.8.5) with ESMTP id NAA24285 for ; Wed, 23 Aug 2000 13:23:21 GMT Message-ID: <39A3D197.914762C7@magpage.com> Date: Wed, 23 Aug 2000 09:28:55 -0400 From: Daniel Frazier Organization: Magpage Internet Services X-Mailer: Mozilla 4.74 [en] (X11; U; Linux 2.0.36 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Trouble upgrading from 3.5-S to 4.1-S... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I finally bit the bullet and am upgrading my box at work to 4.1-STABLE. I'm following the instructions in UPDATING...I successfully made world, built and then installed a new kernel, and then this... poomba: /usr/src # cd /usr/src/sys/modules poomba: /usr/src/sys/modules # make install ===> accf_data install -c -o root -g wheel -m 555 accf_data.ko /modules install: accf_data.ko: No such file or directory *** Error code 71 Stop. *** Error code 1 Stop. Any ideas??? By the way, this is from sources I cvsupped 2 nights ago. Thanks. ---------------------------------------------------------------------- Daniel Frazier Tel: 302-239-5900 Ext. 231 System Administrator Fax: 302-239-3909 MAGPAGE, We Power the Internet WWW: http://www.magpage.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 6:33:43 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 72C5637B42C for ; Wed, 23 Aug 2000 06:33:38 -0700 (PDT) Received: from localhost (trond@localhost) by ramstind.gtf.ol.no (8.9.3/8.9.3) with ESMTP id PAA16880; Wed, 23 Aug 2000 15:33:33 +0200 (CEST) (envelope-from trond@ramstind.gtf.ol.no) Date: Wed, 23 Aug 2000 15:33:33 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= To: Daniel Frazier Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Trouble upgrading from 3.5-S to 4.1-S... In-Reply-To: <39A3D197.914762C7@magpage.com> 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 Wed, 23 Aug 2000, Daniel Frazier wrote: > Any ideas??? By the way, this is from sources I cvsupped 2 nights > ago. Thanks. Try make all install and not just make install -- ---------------------------------------------------------------------- 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.5-S & 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 Wed Aug 23 6:41: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from magpage.com (trinity.magpage.com [216.155.0.8]) by hub.freebsd.org (Postfix) with ESMTP id 661D337B424 for ; Wed, 23 Aug 2000 06:40:55 -0700 (PDT) Received: from magpage.com (poomba.magpage.com [216.155.24.136]) by magpage.com (8.8.8/8.8.5) with ESMTP id NAA31662; Wed, 23 Aug 2000 13:40:49 GMT Message-ID: <39A3D5AF.6B53A7ED@magpage.com> Date: Wed, 23 Aug 2000 09:46:23 -0400 From: Daniel Frazier Organization: Magpage Internet Services X-Mailer: Mozilla 4.74 [en] (X11; U; Linux 2.0.36 i386) X-Accept-Language: en MIME-Version: 1.0 To: Trond =?iso-8859-1?Q?Endrest=F8l?= Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Trouble upgrading from 3.5-S to 4.1-S... References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Trond Endrestøl wrote: > > On Wed, 23 Aug 2000, Daniel Frazier wrote: > > > Any ideas??? By the way, this is from sources I cvsupped 2 nights > > ago. Thanks. > Try > make all install > and not just > make install > Thanks for the quick response, Trond. That got me closer...but still no joy. /usr/src/sys/modules/accf_data/../../netinet/accf_data.c: In function `sohasdata': /usr/src/sys/modules/accf_data/../../netinet/accf_data.c:78: warning: implicit declaration of function `soisconnected' /usr/src/sys/modules/accf_data/../../netinet/accf_data.c: At top level: /usr/src/sys/modules/accf_data/../../netinet/accf_data.c:60: warning: `accf_data_mod' defined but not used *** Error code 1 Stop. *** Error code 1 Stop. -- ---------------------------------------------------------------------- Daniel Frazier Tel: 302-239-5900 Ext. 231 System Administrator Fax: 302-239-3909 MAGPAGE, We Power the Internet WWW: http://www.magpage.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 6:44:31 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 F1EB037B422 for ; Wed, 23 Aug 2000 06:44:26 -0700 (PDT) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.0/8.11.0) id e7NDMnq87336; Wed, 23 Aug 2000 14:22:49 +0100 (BST) (envelope-from nik) Date: Wed, 23 Aug 2000 14:22:46 +0100 From: Nik Clayton To: Graham Wheeler Cc: freebsd-stable@freebsd.org Subject: Re: Configuring kernel for ISA cards Message-ID: <20000823142246.A78421@canyon.nothing-going-on.org> References: <39A3AE82.FFCD5C19@cequrux.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39A3AE82.FFCD5C19@cequrux.com>; from gram@cequrux.com on Wed, Aug 23, 2000 at 12:59:14PM +0200 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 23, 2000 at 12:59:14PM +0200, Graham Wheeler wrote: > FreeBSD 3.x introduced the new boot loader stuff. One of the > consequences was that changing the kernel config at boot time did not > save the changes to the kernel permanently. Instead, it seems, these > changes are supposed to go in /boot/loader.rc. The docs seem very sparse > about all of this, unless I've somehow missed the relevant material. The docs are very sparse on this. Please, when you find out how it works, document it and submit it back to the project. Thanks. 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 Aug 23 7: 5:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rz.uni-ulm.de (sirius-giga.rz.uni-ulm.de [134.60.241.36]) by hub.freebsd.org (Postfix) with ESMTP id DBAE037B43E for ; Wed, 23 Aug 2000 07:05:19 -0700 (PDT) Received: from gmx.de (lilith.wohnheim.uni-ulm.de [134.60.106.64]) by mail.rz.uni-ulm.de (8.9.3/8.9.3) with ESMTP id QAA26649 for ; Wed, 23 Aug 2000 16:05:18 +0200 (MEST) Message-ID: <39A3DA1E.C267C603@gmx.de> Date: Wed, 23 Aug 2000 16:05:18 +0200 From: Siegbert Baude X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: de, en MIME-Version: 1.0 To: "freebsd-stable@freebsd.org" Subject: Error during make INSTALLworld Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, IŽm tracking 4.x STABLE normally without any problems, but faced some problems tonight and want to know: First question: Do I have a stable system now? Should I repeat the cvsup and make world? Second question: Why did the first make installworld fail? Kernel and buildworld were o.k. then! Third question: This was the first time I rebooted to single user mode instead of just "shutdown now". Is there any possibility that a new kernel with old userland can cause problems during "make installworld"? Fourth question: Are there any tools to check RAM integrity? Fifth question: In case this happens again, which information is important to gather, to be really able to hunt down the error? A FAQ or any RTFM? What happened tonight: - CVSupped - make buildworld without problems - make buildkernel KERNEL=LILITH and machine locked completely (no mouse or keys, only hard reset, no entry in logs, no core) - in the BIOS I checked processor temperature: within normal range (49°C, (about 115 Fahrenheit ???)) 3,3V level measured as 3,49V everything else within 1% tolerance, fans are working - rebooted to single user mode, to prevent any amoking daemons - make buildkernel KERNEL=LILITH again, this time no problem - make installkernel - reboot to single user mode - make installworld -> system lock with PAGE FAULT 12 (how can you stop the reboot countdown there or copy the message output? "Any key will reboot" was stated there, should I have tried ScrollLock nevertheless?) I remembered hints on this list, that PAGE FAULT 12 often points to faulty RAM, so checked RAM settings in the BIOS: I found that I had tweaked the CAS-Latency from 3 to 2 (Celeron FSB only 66MHz, with 100MHZ RAM, thought this should be safe; I changed this about half a year ago and with none of my systems on this machine faced ever any problems. But I added last week a SCSI-adapter with HD, CD and CD-RW. Can this influence the RAM-timing? Or maybe a slightly higher temperature in the case is just over the frontier of the RAM then?) - went back to standard RAM timing as suggested by SPD - booted to single user mode - make installworld again -> error some file not found ??? It was after 2 a.m. then, I decided to go to bed, to not produce any errors because of being too tired. Thought I could easily reproduce this error today, so I didnŽt write down the exact error position. Today: - boot to single user mode - make installworld to reproduce the error position Surprise: install without glimpse ! - left single user mode, checked logs: no errors, write down this mail Used hardware: ASUS P2B, Celeron 400, 128M DIMM 100Mhz, Elsa Erazor II, NIC with Realtek 8139 bash-2.04$ uname -a FreeBSD lilith.wohnheim.uni-ulm.de 4.1-STABLE FreeBSD 4.1-STABLE #0: Wed Aug 23 01:55:53 CEST 2000 coocoo@lilith.wohnheim.uni-ulm.de:/usr/obj/usr/src/sys/LILITH i386 Any comments really appreciated Thanks in advance Siegbert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 7:15:28 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 3B53237B43E for ; Wed, 23 Aug 2000 07:15:21 -0700 (PDT) Received: from feta.isds.duke.edu (feta.isds.duke.edu [152.3.22.76]) by isds.duke.edu (8.8.8/8.8.8) with ESMTP id KAA18146; Wed, 23 Aug 2000 10:15:20 -0400 (EDT) Received: (from sto@localhost) by feta.isds.duke.edu (8.9.3/8.9.3) id KAA04538; Wed, 23 Aug 2000 10:15:20 -0400 (EDT) (envelope-from sto) Date: Wed, 23 Aug 2000 10:15:20 -0400 From: "Sean O'Connell" To: Daniel Frazier Cc: FreeBSD stable Subject: Re: Trouble upgrading from 3.5-S to 4.1-S... Message-ID: <20000823101520.A4478@stat.Duke.EDU> Reply-To: "Sean O'Connell" References: <39A3D197.914762C7@magpage.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39A3D197.914762C7@magpage.com>; from dfrazier@magpage.com on Wed, Aug 23, 2000 at 09:28:55AM -0400 X-Organization: Institute of Statistics and Decision Sciences Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel Frazier stated: : Hello all, : I finally bit the bullet and am upgrading my box at work to 4.1-STABLE. I'm : following the instructions in UPDATING...I successfully made world, built and : then installed a new kernel, and then this... Daniel- If you installed the new kernel, then it installed the new modules. This assumes that you did a "make buildkernel KERNEL=GENERIC; make installkernel KERNEL=GENERIC". I believe this step in UPDATING needs to be removed because the buildkernel/installkernel targets include the building and installing of the modules (which can be annoying if you build/maintain multiple kernels ... -DNO_MODULES is your friend in this case). Do you have a /modules directory populated with new *.ko (same mod times as /kernel and a /modules.old? If so, you are in business and can forego that step. Hope this helps, 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 Wed Aug 23 7:26: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from magpage.com (trinity.magpage.com [216.155.0.8]) by hub.freebsd.org (Postfix) with ESMTP id 3CB4D37B423 for ; Wed, 23 Aug 2000 07:25:50 -0700 (PDT) Received: from magpage.com (poomba.magpage.com [216.155.24.136]) by magpage.com (8.8.8/8.8.5) with ESMTP id OAA20653; Wed, 23 Aug 2000 14:25:44 GMT Message-ID: <39A3E036.9C43E0CA@magpage.com> Date: Wed, 23 Aug 2000 10:31:18 -0400 From: Daniel Frazier Organization: Magpage Internet Services X-Mailer: Mozilla 4.74 [en] (X11; U; Linux 2.0.36 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Sean O'Connell" Cc: freebsd-stable@freebsd.org Subject: Re: Trouble upgrading from 3.5-S to 4.1-S... References: <39A3D197.914762C7@magpage.com> <20000823101520.A4478@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 Sean O'Connell wrote: > > Daniel Frazier stated: > : Hello all, > : I finally bit the bullet and am upgrading my box at work to 4.1-STABLE. I'm > : following the instructions in UPDATING...I successfully made world, built and > : then installed a new kernel, and then this... > > Daniel- > > If you installed the new kernel, then it installed the new modules. > This assumes that you did a "make buildkernel KERNEL=GENERIC; make > installkernel KERNEL=GENERIC". I believe this step in UPDATING needs > to be removed because the buildkernel/installkernel targets include > the building and installing of the modules (which can be annoying if > you build/maintain multiple kernels ... -DNO_MODULES is your friend > in this case). > > Do you have a /modules directory populated with new *.ko (same > mod times as /kernel and a /modules.old? If so, you are in business > and can forego that step. > > Hope this helps, > S Niiiice!!! Everything was just as you said. Thanks Sean, you're right, UPDATING needs to be updated... ---------------------------------------------------------------------- Daniel Frazier Tel: 302-239-5900 Ext. 231 System Administrator Fax: 302-239-3909 MAGPAGE, We Power the Internet WWW: http://www.magpage.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 7:43:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gatekeeper.whistle.com (gatekeeper.whistle.com [207.76.204.2]) by hub.freebsd.org (Postfix) with ESMTP id 8320537B423 for ; Wed, 23 Aug 2000 07:43:37 -0700 (PDT) Received: from pau-amma.whistle.com (pau-amma.whistle.com [207.76.205.64]) by gatekeeper.whistle.com (8.9.3/8.9.3) with ESMTP id HAA04877; Wed, 23 Aug 2000 07:43:02 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.3/8.9.3) id HAA35551; Wed, 23 Aug 2000 07:43:01 -0700 (PDT) (envelope-from dhw) Date: Wed, 23 Aug 2000 07:43:01 -0700 (PDT) From: David Wolfskill Message-Id: <200008231443.HAA35551@pau-amma.whistle.com> To: freebsd-stable@FreeBSD.ORG, strange@unicon.ru Subject: Re: SMP problems (was: How can I obtain -stable for previous date) In-Reply-To: <200008231019.RAA02918@mix.unicon.ru> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Wed, 23 Aug 2000 17:19:36 +0700 (NSS) >From: strange@unicon.ru >It seems to me, the problem is in SMP code, because >in 1 CPU configuration with the same kernel all works fine. >And when 2 CPU is installed, simple make -j4 buildworld >lock the system after little period of time... >Unfortunatelly I cant find what changes was made in smp stuff... You may have other information (possibly some that I edited out; possibly information you didn't state) that supports the idea that there may be a problem in FreeBSD's SMP code, but what you cite above does not (in and of itself) demonstrate that at all. As a case in point, when Doug Ambrisko was testing some machines (Intellistation M Pros) for deployment here as desktop workstation/build machines for the engineers, he found that running them with single CPUs worked OK, but he was able to get the machine to fail in SMP mode. (Sorry about the vagueness of the description, but it was a while ago, and the salient point for me -- as the one who needed to deploy the machines to my colleagues -- was that he was able to fix the problem.) It turned out that once he upgraded the BIOS on the machine, he was unable to reproduce that failure. Since then, we have been deploying the machines to the engineers, and have upgraded some to use 2 CPUs. To the best of my knowledge, we have had no SMP-related failures (and few others, either -- none of which have FreeBSD implicated enough to mention). So I just make it part of the standard process I go through after unpacking a box to ensure that the BIOS is updated. That way, should we want to add a CPU to some random Intellistation, we don't need to worry about the problem. Cheers, david (yeah, we have openings -- who doesn't....) -- David Wolfskill dhw@whistle.com UNIX System Administrator Desk: 650/577-7158 TIE: 8/499-7158 Cell: 650/759-0823 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 8: 5:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 1943437B43C for ; Wed, 23 Aug 2000 08:05:19 -0700 (PDT) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id KAA72261; Wed, 23 Aug 2000 10:05:12 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Wed, 23 Aug 2000 10:05:12 -0500 (CDT) From: Chris Dillon To: Smith@ian.org Cc: Dermot McNally , freebsd-stable@FreeBSD.ORG, Fred Clift Subject: Re: Numbering of fxp devices 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, 22 Aug 2000 Smith@ian.org wrote: > On Tue, 22 Aug 2000, Chris Dillon wrote: > > 7 NICs, one of which is dual-port, for a total of 8 ports. I recently > > moved all of those NICs from a Compaq Proliant 3000 running 3.4-STABLE > > into a new Proliant ML530 running 4.1-STABLE. The card order is > > definately weird, but that isn't so much FreeBSD's fault. Compaq was > > nice enough to label primary, secondary, and tertiary PCI bus slots on > > the back of the machine, but they aren't in order anyway. What I > > ended up doing was booting the system with all the cards installed, > > noting the MAC address of each interface, and then comparing that to > > physical slot locations. Not as nice as the sequential ordering in > > the Proliant 3000, but not a big deal either, as long as it doesn't > > change on me in the future without some warning. :-) > > Might I ask what 2-port card you are using? I have a router with > limited slots.. 3 ethernet and four T1 ports currently. The Intel dual-port. > I also wonder if there woudl be a way to map cards based on their > MAC addresses, or is the MAC address discovery done way too late? Way too late, I think, since the driver would have to attach before it could even query the card for its MAC address. If it were able to get the MAC, detach, re-attach, etc. until the right order was reached, that might work. > Hmm.. maybe some sort of aliasing? A conf file could list device > numbers and MAC addresses, so once the kernel finished finding > everything, it could look through the cards and asign /dev/ether0 > to one, /dev/ether1 to another, ect. Thats an idea, too... > Thinking on that.. I do like the aliasing idea. Maybe a > /dev/ethernet/ directory where each card is listed by it's MAC > address, then given symbolic names to create normal /dev entries > that also get listed with ifconfig and such. Yeah! I like that. I'll bet someone will come along and tell us why it isn't feasable, though. The biggest problem I can see is that network devices have never had device nodes, so they would truly have to be "symbolic" in more than one sense. :-) -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures. ( 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 Wed Aug 23 8:28: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wyattearp.stanford.edu (wyattearp.Stanford.EDU [171.66.63.23]) by hub.freebsd.org (Postfix) with ESMTP id D0E1737B42C for ; Wed, 23 Aug 2000 08:28:00 -0700 (PDT) Received: (from richw@localhost) by wyattearp.stanford.edu (8.9.3/8.9.3) id IAA17136; Wed, 23 Aug 2000 08:27:59 -0700 (PDT) (envelope-from richw) Date: Wed, 23 Aug 2000 08:27:59 -0700 (PDT) From: Rich Wales X-Sender: richw@wyattearp.stanford.edu To: freebsd-stable@freebsd.org Subject: 4.1-STABLE kernel with 4.1-RELEASE userland? Message-ID: <200008231415723.richw@wyattearp.stanford.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I decided yesterday to try cvsup'ing from 4.1-RELEASE to 4.1-STABLE. I started out with just the kernel. After making and installing a 4.1-STABLE kernel and modules, I rebooted. Assuming the new kernel worked, I planned to proceed with updating my userland stuff. Everything seemed to be OK after booting the new kernel, until the system got to my firewall (ipfw) rules -- all my "ipfw add" commands failed. I then tried to mount a CD. The "mount" command succeeded, and "df" showed the mounted CD, but I couldn't see any files on the CD, and I couldn't "umount" the CD. I brought the system back down and went back to my 4.1-RELEASE kernel and modules, and it's working fine now. I never did get around to updating any of my userland code, of course. Does this sound like expected behavior? I would have thought that a 4.1-STABLE kernel (and modules) would still be compatible with the 4.1-RELEASE userland binaries; is this not the case? Did I do some- thing obviously wrong here? FWIW, before compiling a 4.1-STABLE kernel from the cvsup'ed source, I removed my old kernel compilation directory and did everything from scratch ("config", "make depend", and "make"). Rich Wales richw@webcom.com http://www.webcom.com/richw/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 8:33:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from caffeine.gerp.org (caffeine.gerp.org [216.80.26.45]) by hub.freebsd.org (Postfix) with SMTP id B8AA637B422 for ; Wed, 23 Aug 2000 08:33:51 -0700 (PDT) Received: (qmail 20568 invoked by uid 100); 23 Aug 2000 15:21:15 -0000 Date: Wed, 23 Aug 2000 10:21:15 -0500 From: "Kevin M. Dulzo" To: Graham Wheeler Cc: freebsd-stable@freebsd.org Subject: Re: Configuring kernel for ISA cards Message-ID: <20000823102115.A15422@caffeine.gerp.org> Reply-To: kdulzo@gerp.org References: <39A3AE82.FFCD5C19@cequrux.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <39A3AE82.FFCD5C19@cequrux.com>; from gram@cequrux.com on Wed, Aug 23, 2000 at 12:59:14PM +0200 X-Operating-System: OpenBSD caffeine 2.7 CAFFEINE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 23, 2000 at 12:59:14PM +0200, Graham Wheeler wrote: > consequences was that changing the kernel config at boot time did not > save the changes to the kernel permanently. Instead, it seems, these > changes are supposed to go in /boot/loader.rc. The docs seem very sparse > about all of this, unless I've somehow missed the relevant material. > > Now, I was told that the same commands can be used in the loader.rc file > as are used in the configuration editor. However, it seems to me that > this only holds for PCI cards. When I have tried to configure the IRQ > for an ISA card, the loader has complained about a syntax error. > > I believe the command I used was: > > irq ed0 10 > The configuration commands go in /boot/kernel.conf. (Just tested on 4.1-stable) and thats where they went in 3.x as well. I'm not positive if the boot loaders are the same between 3.x and 4.x but by default the loader does NOT read the kernel.conf file unless it was installed by sysinstall in 4.x. The syntax to enable it is in the /boot/defaults/loader.conf and it is: userconfig_script_load="YES" -- :Kevin M. Dulzo:ccna.ccda:freebsd:everything_else: --eyes betray a soul and bear its thinking --beyond words they say so many things to me To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 8:51:25 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 7B24237B42C for ; Wed, 23 Aug 2000 08:51:22 -0700 (PDT) Received: from mpc-data.demon.co.uk ([158.152.55.245] helo=burton.mpc-data.co.uk) by anchor-post-31.mail.demon.net with esmtp (Exim 2.12 #1) id 13RcoB-000AxQ-0V for freebsd-stable@freebsd.org; Wed, 23 Aug 2000 16:51:20 +0100 Received: from lion.mpc-data.co.uk (root@lion.mpc-data.co.uk [192.150.92.1]) by burton.mpc-data.co.uk (8.8.7/8.8.5) with ESMTP id QAA31960 for ; Wed, 23 Aug 2000 16:51:11 +0100 Received: from lion.mpc-data.co.uk (IDENT:mpumford@localhost [127.0.0.1]) by lion.mpc-data.co.uk (8.9.3/8.8.5) with ESMTP id QAA14960 for ; Wed, 23 Aug 2000 16:51:15 +0100 Message-Id: <200008231551.QAA14960@lion.mpc-data.co.uk> X-Mailer: exmh version 2.0.3 To: freebsd-stable@freebsd.org Subject: Re: Configuring kernel for ISA cards In-Reply-To: Your message of "Wed, 23 Aug 2000 10:21:15 CDT." <20000823102115.A15422@caffeine.gerp.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 23 Aug 2000 16:51:15 +0100 From: Mike Pumford Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The configuration commands go in /boot/kernel.conf. (Just > tested on 4.1-stable) and thats where they went in 3.x as well. > > I'm not positive if the boot loaders are the same between 3.x and 4.x > but by default the loader does NOT read the kernel.conf file unless > it was installed by sysinstall in 4.x. The syntax to enable it is > in the /boot/defaults/loader.conf and it is: > userconfig_script_load="YES" > As with /etc/defaults/rc.conf you should not modify /boot/defaults/ loader.conf. You can just create a /boot/loader.conf with the overrides that you need. IIRC early 3.x bootloaders did not work this way. I think the changeover was at some point after 3.2-RELEASE. Mike > -- > :Kevin M. Dulzo:ccna.ccda:freebsd:everything_else: > --eyes betray a soul and bear its thinking > --beyond words they say so many things to me > > > > 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 Aug 23 9: 2:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fingers.noc.uunet.co.za (fingers.noc.uunet.co.za [196.31.1.59]) by hub.freebsd.org (Postfix) with ESMTP id DE6A837B424 for ; Wed, 23 Aug 2000 09:02:17 -0700 (PDT) Received: from robh (helo=localhost) by fingers.noc.uunet.co.za with local-smtp (Exim 3.13 #1) id 13Rcyj-0000yk-00 for freebsd-stable@freebsd.org; Wed, 23 Aug 2000 18:02:13 +0200 Date: Wed, 23 Aug 2000 18:02:13 +0200 (SAST) From: fingers X-Sender: robh@fingers.noc.uunet.co.za To: freebsd-stable@freebsd.org Subject: (probably stupid) question about onboard SoundBlaster 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 Ok, I've unfortunately got an onboard sound card of sorts. According to the bios, it's a "legacy SoundBlaster". Now I've tried reading varios doc's, but most of them are outdated. /usr/src/sys/i386/isa/sound/sound.doc talks about: Instructions on using audio on a FreeBSD 2.1 (or 2.0-current) system. I've tried many variatios of my kernel config, some trying pcm and snd, some trying sb0 and even the following which I found in the mailing list archives: controller pnp0 controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 but no matter what I get errors with a make, or something similar. If anyone's using a GA-6VX7-4X Gigabyte motherboard. If anyone can point me to some recent documentation that would still be relevant, or has some suggestions, please let me know. thanks --Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 9:16:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from citadel.cequrux.com (citadel.cequrux.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id 6B3D637B43C for ; Wed, 23 Aug 2000 09:16:21 -0700 (PDT) Received: (from nobody@localhost) by citadel.cequrux.com (8.8.8/8.6.9) id SAA27289 for ; Wed, 23 Aug 2000 18:16:18 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 27204; Wed Aug 23 18:15:10 2000 Message-ID: <39A3F93A.F83FC0E1@cequrux.com> Date: Wed, 23 Aug 2000 18:18:02 +0200 From: Graham Wheeler Organization: Cequrux Technologies X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 2.2.8-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: Configuring kernel for ISA cards References: <200008231551.QAA14960@lion.mpc-data.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Pumford wrote: > > > > > The configuration commands go in /boot/kernel.conf. (Just > > tested on 4.1-stable) and thats where they went in 3.x as well. > > > > I'm not positive if the boot loaders are the same between 3.x and 4.x > > but by default the loader does NOT read the kernel.conf file unless > > it was installed by sysinstall in 4.x. The syntax to enable it is > > in the /boot/defaults/loader.conf and it is: > > userconfig_script_load="YES" Its definitely being loaded. If I put commands in to configure the PCI cards, they work. Its just the commands that I would use in kernelconfig to configure an ISA card are causing syntax errors. So either the format shouldf be different, or there is no way anymore to configure the kernel for legacy ISA cards other than by recompiling. gram To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 9:25:21 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 2C86E37B423 for ; Wed, 23 Aug 2000 09:25:15 -0700 (PDT) Received: from feta.isds.duke.edu (feta.isds.duke.edu [152.3.22.76]) by isds.duke.edu (8.8.8/8.8.8) with ESMTP id MAA12630; Wed, 23 Aug 2000 12:25:14 -0400 (EDT) Received: (from sto@localhost) by feta.isds.duke.edu (8.9.3/8.9.3) id MAA04889; Wed, 23 Aug 2000 12:25:14 -0400 (EDT) (envelope-from sto) Date: Wed, 23 Aug 2000 12:25:14 -0400 From: "Sean O'Connell" To: fingers Cc: FreeBSD stable Subject: Re: (probably stupid) question about onboard SoundBlaster Message-ID: <20000823122514.I4478@stat.Duke.EDU> Reply-To: "Sean O'Connell" References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from fingers@fingers.co.za on Wed, Aug 23, 2000 at 06:02:13PM +0200 X-Organization: Institute of Statistics and Decision Sciences Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG fingers stated: : Hi all : : Ok, I've unfortunately got an onboard sound card of sorts. According to : the bios, it's a "legacy SoundBlaster". Now I've tried reading varios : doc's, but most of them are outdated. : : /usr/src/sys/i386/isa/sound/sound.doc talks about: : : Instructions on using audio on a FreeBSD 2.1 (or 2.0-current) system. : : I've tried many variatios of my kernel config, some trying pcm and snd, : some trying sb0 and even the following which I found in the mailing list : archives: : : : controller pnp0 : controller snd0 : device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr : device sbxvi0 at isa? drq 5 : device sbmidi0 at isa? port 0x330 : device opl0 at isa? port 0x388 : : : but no matter what I get errors with a make, or something similar. If : anyone's using a GA-6VX7-4X Gigabyte motherboard. If anyone can point me : to some recent documentation that would still be relevant, or has some : suggestions, please let me know. Rob- You don't mention what version of FreeBSD you are using .. 4.0, 4.1? Do you know if it is PCI or ISA .. what chipset is this using? If it is ISA... options PNPBIOS device pcm and then "cd /dev; sh MAKEDEV snd0" if it is pci and supported, the options PNPBIOS is probably not needed (but is useful for a lot of other things). So, I went to www.giga-byte.com and found the GA-6VX7-4X uses the Apollo Pro 133A. This probably means that it is a VIA soundcard built-in to the motherboard. Support for this card was recently added to -current (not sure if Cameron has MFC'd it .. you most likely can). Here is how: grab the latest copies of: via82c686.c and via82c686.h from http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/sound/pci/ and then add dev/sound/pci/via82c686.c optional pcm pci to /sys/conf/files just above dev/sound/pcm/ac97.c optional pcm Hope this helps. S PS. The original was written for 4.x and is located at http://www.inode.org/sw/auvia/ ----------------------------------------------------------------------- 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 Wed Aug 23 9:36:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from umc-mail01.missouri.edu (umc-mail01.missouri.edu [128.206.10.216]) by hub.freebsd.org (Postfix) with ESMTP id 3048F37B424 for ; Wed, 23 Aug 2000 09:36:57 -0700 (PDT) Received: by umc-mail01.missouri.edu with Internet Mail Service (5.5.2650.21) id ; Wed, 23 Aug 2000 11:36:55 -0500 Message-ID: <7B5F4A3DED02D411B49B0000E889ECB70122B48E@umc-mail02> From: "Salmons, Michael" To: "'freebsd-stable@FreeBSD.org'" Subject: Date: Wed, 23 Aug 2000 11:35:51 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe salmonsm@missouri.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 9:38:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from umc-mail01.missouri.edu (umc-mail01.missouri.edu [128.206.10.216]) by hub.freebsd.org (Postfix) with ESMTP id 421F437B424 for ; Wed, 23 Aug 2000 09:38:11 -0700 (PDT) Received: by umc-mail01.missouri.edu with Internet Mail Service (5.5.2650.21) id ; Wed, 23 Aug 2000 11:38:10 -0500 Message-ID: <7B5F4A3DED02D411B49B0000E889ECB70122B490@umc-mail02> From: "Salmons, Michael" To: "'freebsd-stable@FreeBSD.org'" Subject: sorry Date: Wed, 23 Aug 2000 11:37:06 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG obviously please ignore my previous message. How embarassing... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 9:45:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from front5m.grolier.fr (front5m.grolier.fr [195.36.216.55]) by hub.freebsd.org (Postfix) with ESMTP id 45B4B37B422 for ; Wed, 23 Aug 2000 09:45:01 -0700 (PDT) Received: from club-internet.fr (nas14-35.vlt.club-internet.fr [195.36.162.35]) by front5m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id SAA11036 for ; Wed, 23 Aug 2000 18:44:57 +0200 (MET DST) Message-ID: <39A40077.49F228E0@club-internet.fr> Date: Wed, 23 Aug 2000 18:48:55 +0200 From: David Scialom X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: UDMA66 not recognized Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have also the problem that my FreeBSD does not recognize my Matrox hard disk drive which is UDMA 66 and is connected to the first controller with a 80 pin cable. FreeBSD use only the drive with the UDMA 33 mode ( see my dmesg output below). It possible that the reason is that there is a second drive on the OTHER controller which does not support UDMA 66 ? Can someone help me? David ------------------------------------------------------------------------ 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 #0: Tue Aug 15 13:00:07 CEST 2000 root@lupo:/usr/src/sys/compile/MYKERNEL Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon (535.28-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x681 Stepping = 1 Features=0x383f9ff real memory = 67092480 (65520K bytes) config> di sn0 config> di lnc0 config> di le0 config> di ie0 config> di fe0 config> di ed0 config> di cs0 config> q avail memory = 60948480 (59520K bytes) Preloaded elf kernel "kernel" at 0xc03f0000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc03f009c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib2: at device 1.0 on pci0 pci1: on pcib2 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f 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 5 pcm0: port 0xd000-0xd03f irq 10 at device 11.0 on pci0 pci0: at 12.0 irq 11 pcib1: on motherboard pci2: on pcib1 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 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> 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: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: IEEE1284 device found /NIBBLE/ECP Probing for PnP devices on ppbus0: ppbus0: PJL,MLC,PCLXL,PCL,POSTSCRIPT ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 ad0: 9770MB [19852/16/63] at ata0-master using UDMA33 ad3: 3077MB [6253/16/63] at ata1-slave using UDMA33 acd0: CDROM at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s2a ---------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 9:51:30 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 711D237B423 for ; Wed, 23 Aug 2000 09:51:28 -0700 (PDT) Received: from thehousleys.net (baby.int.thehousleys.net. [192.168.0.24]) by thehousleys.net (8.9.3/8.9.3) with ESMTP id MAA10596; Wed, 23 Aug 2000 12:51:24 -0400 (EDT) (envelope-from jim@thehousleys.net) Message-ID: <39A4010C.8CD1C5D7@thehousleys.net> Date: Wed, 23 Aug 2000 12:51:24 -0400 From: James Housley Organization: The Housleys dot Net X-Mailer: Mozilla 4.73 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: David Scialom Cc: freebsd-stable@FreeBSD.ORG Subject: Re: UDMA66 not recognized References: <39A40077.49F228E0@club-internet.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Scialom wrote: > > I have also the problem that my FreeBSD does not recognize my Matrox > hard disk drive which is UDMA 66 and is connected to the first [snip] > atapci0: port 0xd800-0xd80f at device > 4.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 That is becuase it is only an ATA33 controller. Jim -- Do not meddle in the affairs of dragons, for you are crunchy and taste good with ketchup. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 9:55:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 0E15A37B42C for ; Wed, 23 Aug 2000 09:55:23 -0700 (PDT) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id e7NGtL914602; Wed, 23 Aug 2000 09:55:21 -0700 Date: Wed, 23 Aug 2000 09:55:21 -0700 From: Brooks Davis To: Rich Wales Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 4.1-STABLE kernel with 4.1-RELEASE userland? Message-ID: <20000823095521.A13699@Odin.AC.HMC.Edu> References: <200008231415723.richw@wyattearp.stanford.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200008231415723.richw@wyattearp.stanford.edu>; from richw@webcom.com on Wed, Aug 23, 2000 at 08:27:59AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 23, 2000 at 08:27:59AM -0700, Rich Wales wrote: > Does this sound like expected behavior? I would have thought that > a 4.1-STABLE kernel (and modules) would still be compatible with the > 4.1-RELEASE userland binaries; is this not the case? Did I do some- > thing obviously wrong here? It's not exactly expected behavior, but you are in an unsupported configuration. It's expected that thing's won't work right with an out of sync userland and kernel. Sometimes you get luckey and sometimes you don't. -- 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 Aug 23 10: 1:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from front6m.grolier.fr (front6m.grolier.fr [195.36.216.56]) by hub.freebsd.org (Postfix) with ESMTP id 7459A37B422 for ; Wed, 23 Aug 2000 10:01:22 -0700 (PDT) Received: from club-internet.fr (nas14-35.vlt.club-internet.fr [195.36.162.35]) by front6m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id TAA29764; Wed, 23 Aug 2000 19:01:13 +0200 (MET DST) Message-ID: <39A40446.7967E391@club-internet.fr> Date: Wed, 23 Aug 2000 19:05:10 +0200 From: David Scialom X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: James Housley Cc: freebsd-stable@FreeBSD.ORG Subject: Re: UDMA66 not recognized References: <39A40077.49F228E0@club-internet.fr> <39A4010C.8CD1C5D7@thehousleys.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I know that but the documentation of the mothercard (Asus P3V4X JumperFree) says: "UDMA66/Support: Comes with an on board PCI bus Master Controller with 2 connectors that support 4 IDE devices on 2 channel. Support UDMA 66, UDMA 33 PIO mode 3 & 4 and bus master IDE DMA mode 2." But freebsd does not seem to recognise UDMA 66? James Housley wrote: > David Scialom wrote: > > > > I have also the problem that my FreeBSD does not recognize my Matrox > > hard disk drive which is UDMA 66 and is connected to the first > > [snip] > > > atapci0: port 0xd800-0xd80f at device > > 4.1 on pci0 > > ata0: at 0x1f0 irq 14 on atapci0 > > ata1: at 0x170 irq 15 on atapci0 > > That is becuase it is only an ATA33 controller. > > Jim > > -- > Do not meddle in the affairs of dragons, for you are crunchy and taste > good with ketchup. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 10:20:46 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 D04F637B424 for ; Wed, 23 Aug 2000 10:20:44 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 0D3B6E881 for ; Wed, 23 Aug 2000 13:20:39 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.9.3/8.9.3) id NAA02885; Wed, 23 Aug 2000 13:20:38 -0400 (EDT) (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: <14756.2022.695697.5862@onceler.kciLink.com> Date: Wed, 23 Aug 2000 13:20:38 -0400 (EDT) To: stable@freebsd.org Subject: missing c++rt0.o file, where to get? X-Mailer: VM 6.72 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm attempting to build the plugger port, and it comes back with this error: make plugger.so CC=gcc XCFLAGS='-fpic -aout' LD=gcc XLDFLAGS='-shared -aout' gcc -shared -aout -o plugger.so plugger.o common.o ld: c++rt0.o: No such file or directory *** Error code 1 I'm guessing c++rt0.o is from the 2.x compatibility but I can't figure out from where to get it. I have the 2.x compatibility libraries installed. I'm running a freshly installed 4.1-R box upgraded to 4.1-STABLE. I see sources for /usr/src/lib/csu/i386/c++rt0.c but the Makefile in there doesn't seem to build with "-aout" option, so it is unlikely to be the right incantation. Any pointers from where to get this? I've filed a PR on plugger, but no response on it yet (over a week). -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 GPG & MIME spoken here http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 10:43:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from caffeine.gerp.org (caffeine.gerp.org [216.80.26.45]) by hub.freebsd.org (Postfix) with SMTP id 2B01737B423 for ; Wed, 23 Aug 2000 10:43:12 -0700 (PDT) Received: (qmail 6120 invoked by uid 100); 23 Aug 2000 17:30:35 -0000 Date: Wed, 23 Aug 2000 12:30:35 -0500 From: "Kevin M. Dulzo" To: Graham Wheeler Cc: freebsd-stable@freebsd.org Subject: Re: Configuring kernel for ISA cards Message-ID: <20000823123035.A15126@caffeine.gerp.org> Reply-To: kdulzo@gerp.org References: <200008231551.QAA14960@lion.mpc-data.co.uk> <39A3F93A.F83FC0E1@cequrux.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <39A3F93A.F83FC0E1@cequrux.com>; from gram@cequrux.com on Wed, Aug 23, 2000 at 06:18:02PM +0200 X-Operating-System: OpenBSD caffeine 2.7 CAFFEINE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 23, 2000 at 06:18:02PM +0200, Graham Wheeler wrote: > > Its definitely being loaded. If I put commands in to configure the PCI > cards, they work. Its just the commands that I would use in kernelconfig > to configure an ISA card are causing syntax errors. So either the format > shouldf be different, or there is no way anymore to configure the kernel > for legacy ISA cards other than by recompiling. > My apologies for failing to mention to put the command into the loader.conf file. I had all intentions of implying it. I placed the following lines into /boot/kernel.conf (again this is on 4.1-stable so I suppose its possible the older one is buggy or has a separate syntax) as a test. Again, this is NOT the loader.conf or loader.rc. loader.conf tells the loader to load /kernel.conf as a type of userconfig_script which is different than the syntax of the loader configuration files themselves. port sio0 0x2e8 irq sio0 7 These values are completely wrong, and different than the compiled in settings for sio0. And it probed and failed to attach at the address I specified in the kernel.conf (and hung the boot process for that matter). I used to do this in 3.x in /kernel.conf or /boot/kernel.conf without issue. -- :Kevin M. Dulzo:ccna.ccda:freebsd:everything_else: --eyes betray a soul and bear its thinking --beyond words they say so many things to me To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 10:47:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tsunami.reflectively.net (tsunami.reflectively.net [216.85.76.11]) by hub.freebsd.org (Postfix) with SMTP id 060BA37B422 for ; Wed, 23 Aug 2000 10:47:07 -0700 (PDT) Received: (qmail 79383 invoked from network); 23 Aug 2000 17:46:57 -0000 Received: from cc47835-b.chmbl1.ga.home.com (HELO vapor) (@24.5.106.158) by tsunami.reflectively.net with SMTP; 23 Aug 2000 17:46:57 -0000 Message-ID: <003801c00d2a$03c7ff00$0200000a@cm.420.net> From: "Robert Augustine" To: Subject: Random Reboots Date: Wed, 23 Aug 2000 13:46:04 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 Disposition-Notification-To: "Robert Augustine" X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Im running a 4.1-STABLE machine which is very recently cvs'uped. The hardware is an Athlon running on a FIC motherboard. I am receiving random reboots every like 3 days or so. Sometimes sooner sometimes later. Has anyone ever experienced these problems or know what could be the reason for this happening? -Robert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 10:52:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.fpsn.net (mail.fpsn.net [63.224.69.57]) by hub.freebsd.org (Postfix) with ESMTP id 53A9E37B423 for ; Wed, 23 Aug 2000 10:52:34 -0700 (PDT) Received: from sharky (adsl-151-202-97-90.bellatlantic.net [151.202.97.90]) by mail.fpsn.net (8.9.3/8.9.3) with SMTP id MAA60772; Wed, 23 Aug 2000 12:38:49 -0600 (MDT) (envelope-from simon@optinet.com) Message-Id: <200008231838.MAA60772@mail.fpsn.net> From: "Simon" To: "Robert Augustine" , "stable@FreeBSD.ORG" Date: Wed, 23 Aug 2000 13:56:07 -0400 Reply-To: "Simon" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 2000 (5.0.2195) In-Reply-To: <003801c00d2a$03c7ff00$0200000a@cm.420.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Random Reboots Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've exeprienced the same behavior with bad RAM in the system. Did you ever have this box running rock solid before? If not, consider replacing various part of your box to determine faulty hardware. Also, did you compile custom kernel? You can also try enabling kernel dumps to see where it screws up. -Simon On Wed, 23 Aug 2000 13:46:04 -0400, Robert Augustine wrote: > Hello, > Im running a 4.1-STABLE machine which is very recently cvs'uped. The >hardware is an Athlon running on a FIC motherboard. I am receiving random >reboots every like 3 days or so. Sometimes sooner sometimes later. Has >anyone ever experienced these problems or know what could be the reason for >this happening? > >-Robert > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 11: 3: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wyattearp.stanford.edu (wyattearp.Stanford.EDU [171.66.63.23]) by hub.freebsd.org (Postfix) with ESMTP id 1393037B422 for ; Wed, 23 Aug 2000 11:03:01 -0700 (PDT) Received: (from richw@localhost) by wyattearp.stanford.edu (8.9.3/8.9.3) id LAA03481; Wed, 23 Aug 2000 11:02:46 -0700 (PDT) (envelope-from richw) Date: Wed, 23 Aug 2000 11:02:46 -0700 (PDT) From: Rich Wales X-Sender: richw@wyattearp.stanford.edu To: freebsd-stable@freebsd.org Subject: Re: 4.1-STABLE kernel with 4.1-RELEASE userland? Message-ID: <200008231701226.richw@wyattearp.stanford.edu> 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 did a bit more research on this problem. The reason 4.1-RELEASE "ipfw" fails with a 4.1-STABLE kernel appears to be because struct ip_fw (in netinet/ip_fw.h) has had two new elements added in the middle (u_char fw_tcpopt, fw_tcpnopt). As a result, the "setsockopt" calls in "ipfw" failed with EINVAL (invalid argument). I haven't tried yet to figure out why CD-ROM file systems stopped working when I tried a 4.1-STABLE kernel with a 4.1-RELEASE userland. When I mounted a CD on /cdrom and tried "ls /cdrom", the kernel said "RRIP without PX field?" (isofs/cd9660/cd9660_rrip.c), and nothing at all was visible in the /cdrom directory. When I tried to unmount the CD, "umount" failed with an "invalid argument" message. I understand now that if I'm going to track -STABLE, I can't just track the kernel. For the moment, I think I'll have to stick with -RELEASE and wait to track -STABLE until I have time to deal with a more involved upgrade (including being able to back it out in case something doesn't work -- the machine in question is a semi-production system and I can't afford to have it stay broken for long). Rich Wales richw@webcom.com http://www.webcom.com/richw/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 11: 9:19 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 114C037B424 for ; Wed, 23 Aug 2000 11:09:17 -0700 (PDT) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 7D27E1C76; Wed, 23 Aug 2000 14:09:16 -0400 (EDT) Date: Wed, 23 Aug 2000 14:09:16 -0400 From: Bill Fumerola To: Rich Wales Cc: freebsd-stable@freebsd.org Subject: Re: 4.1-STABLE kernel with 4.1-RELEASE userland? Message-ID: <20000823140916.X57333@jade.chc-chimes.com> References: <200008231701226.richw@wyattearp.stanford.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200008231701226.richw@wyattearp.stanford.edu>; from richw@webcom.com on Wed, Aug 23, 2000 at 11:02:46AM -0700 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 23, 2000 at 11:02:46AM -0700, Rich Wales wrote: > OK, I did a bit more research on this problem. > > The reason 4.1-RELEASE "ipfw" fails with a 4.1-STABLE kernel appears to > be because struct ip_fw (in netinet/ip_fw.h) has had two new elements > added in the middle (u_char fw_tcpopt, fw_tcpnopt). As a result, the > "setsockopt" calls in "ipfw" failed with EINVAL (invalid argument). Speaking as the guilty party, I don't think that's a problem. Read on. > I haven't tried yet to figure out why CD-ROM file systems stopped > working when I tried a 4.1-STABLE kernel with a 4.1-RELEASE userland. > When I mounted a CD on /cdrom and tried "ls /cdrom", the kernel said > "RRIP without PX field?" (isofs/cd9660/cd9660_rrip.c), and nothing > at all was visible in the /cdrom directory. When I tried to unmount > the CD, "umount" failed with an "invalid argument" message. > > I understand now that if I'm going to track -STABLE, I can't just track > the kernel. For the moment, I think I'll have to stick with -RELEASE > and wait to track -STABLE until I have time to deal with a more involved > upgrade (including being able to back it out in case something doesn't > work -- the machine in question is a semi-production system and I can't > afford to have it stay broken for long). We've never supported a different userland then kernel, so this entire e-mail is old news. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 11:11:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 63B7A37B423 for ; Wed, 23 Aug 2000 11:11:55 -0700 (PDT) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id LAA03002; Wed, 23 Aug 2000 11:11:53 -0700 Message-ID: <39A413E9.148CC24D@urx.com> Date: Wed, 23 Aug 2000 11:11:53 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Rich Wales Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 4.1-STABLE kernel with 4.1-RELEASE userland? References: <200008231701226.richw@wyattearp.stanford.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rich Wales wrote: > > OK, I did a bit more research on this problem. > > The reason 4.1-RELEASE "ipfw" fails with a 4.1-STABLE kernel appears to > be because struct ip_fw (in netinet/ip_fw.h) has had two new elements > added in the middle (u_char fw_tcpopt, fw_tcpnopt). As a result, the > "setsockopt" calls in "ipfw" failed with EINVAL (invalid argument). > > I haven't tried yet to figure out why CD-ROM file systems stopped > working when I tried a 4.1-STABLE kernel with a 4.1-RELEASE userland. > When I mounted a CD on /cdrom and tried "ls /cdrom", the kernel said > "RRIP without PX field?" (isofs/cd9660/cd9660_rrip.c), and nothing > at all was visible in the /cdrom directory. When I tried to unmount > the CD, "umount" failed with an "invalid argument" message. > > I understand now that if I'm going to track -STABLE, I can't just track > the kernel. For the moment, I think I'll have to stick with -RELEASE > and wait to track -STABLE until I have time to deal with a more involved > upgrade (including being able to back it out in case something doesn't > work -- the machine in question is a semi-production system and I can't > afford to have it stay broken for long). The thing is you already have modules for 4.1-Stable installed and will have to back them out. I also think you will find fewer things broken on 4.1-Stable than with the release. Someone who wasn't involved with testing the transition from 4.0-stable to 4.1-R always seems to have something that needs to be fixed in the first week or two. Kent > > Rich Wales richw@webcom.com http://www.webcom.com/richw/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 11:13:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from linuxpower.p00t.net (d98.as4.nwbl0.wi.voyager.net [169.207.137.98]) by hub.freebsd.org (Postfix) with ESMTP id 2C6D737B42C for ; Wed, 23 Aug 2000 11:13:21 -0700 (PDT) Received: from localhost (trout@localhost) by linuxpower.p00t.net (8.10.2/8.10.2) with ESMTP id e7NINLs19740 for ; Wed, 23 Aug 2000 13:23:21 -0500 Date: Wed, 23 Aug 2000 13:23:21 -0500 (CDT) From: Tom Duffey To: stable@FreeBSD.ORG Subject: Update magic file 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 This message might apply to more than -STABLE, but I can't be certain since I haven't checked any of the other branches. The "file" command is unable to properly identify EPS binary files. The following patch, taken from the magic file included in the Slackware Linux distribution, fixes the problem. 3608a3609,3618 > # DOS EPS Binary File Header > # From: Ed Sznyter > 0 belong 0xC5D0D3C6 DOS EPS Binary File > >4 long >0 Postscript starts at byte %d > >>8 long >0 length %d > >>>12 long >0 Metafile starts at byte %d > >>>>16 long >0 length %d > >>>20 long >0 TIFF starts at byte %d > >>>>24 long >0 length %d > Tom Duffey -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Marge, you're my wife and I love you very much. But you're living in a world of makebelieve. With flowers and bells and leprechauns. And magic frogs with funny little hats... -- Homer Simpson Blood Feud To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 11:46: 6 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 B0FAB37B423; Wed, 23 Aug 2000 11:45:32 -0700 (PDT) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id UAA11873; Wed, 23 Aug 2000 20:45:16 +0200 (MET DST) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id UAA70728; Wed, 23 Aug 2000 20:42:17 +0200 (CEST) (envelope-from andreas) Date: Wed, 23 Aug 2000 20:42:17 +0200 From: Andreas Klemm To: freebsd-stable@FreeBSD.ORG Cc: sos@FreeBSD.ORG Subject: Re: 4.1-STABLE panics on boot with Huyundai Laptop (P233) Message-ID: <20000823204217.A70368@titan.klemm.gtn.com> References: <20000823131811.A4418@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000823131811.A4418@titan.klemm.gtn.com>; from andreas@klemm.gtn.com on Wed, Aug 23, 2000 at 01:18:11PM +0200 X-Operating-System: FreeBSD 4.1-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: multipart/mixed; boundary="1yeeQ81UyVL57Vl7" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --1yeeQ81UyVL57Vl7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi ! It turns out, that with the (new) ata driver the machine panics and with the old (obsoleted) wd driver the Laptopmachine boots flawlessly. Many thanks to "Sean O'Connell" who helped debugging and had the excellent idea to use the old wd driver to test his theory, that it might be ata driver related. Soeren could you perhaps help ? In the attachement 2 boot logs using comconsole. Do you have an idea, how to fix the 4.x ata panics during boot with my hardware ? Detailed logs in the attachement. BTW, comconsole is really great ! Hope you can help. Andreas /// -- Andreas Klemm Powered by FreeBSD SMP Songs from our band >>64Bits<<............http://www.apsfilter.org/64bits.html My homepage................................ http://people.FreeBSD.ORG/~andreas Please note: Apsfilter got a NEW HOME................http://www.apsfilter.org/ --1yeeQ81UyVL57Vl7 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="laptop.trouble.4.1-STABLE" Content-Transfer-Encoding: quoted-printable disk1s2a:>=20 disk1s2a:>=20 disk1s2a:> set boot?=08 =08_verbose'=08 =08=3D1 disk1s2a:> unload kernel disk1s2a:> load kernel \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/= =08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08/kernel = text=3D0x132f17 -=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|= =08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08= \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/= =08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08= |=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-= =08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08= /=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\= =08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08= -=08\=08|=08/=08-=08\=08|=08/=08-=08\=08data=3D0x1aa38+0x1cc20 |=08/=08-=08= \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08syms=3D[0x4+0x22e80-=08\=08|=08= /=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08+0x4+0x2776b|= =08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08] disk1s2a:> boot Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.1-STABLE #0: Wed Aug 23 13:34:52 CEST 2000 root@titan.klemm.gtn.com:/usr/src/sys/compile/LAPTOP4 Calibrating clock(s) ... TSC clock: 232523307 Hz, i8254 clock: 1193163 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/P55C (232.53-MHz 586-class CPU) Origin =3D "GenuineIntel" Id =3D 0x543 Stepping =3D 3 Features=3D0x8001bf real memory =3D 67108864 (65536K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x002d0000 - 0x03ff7fff, 64126976 bytes (15656 pages) avail memory =3D 62615552 (61148K bytes) bios32: Found BIOS32 Service Directory header at 0xc00ec050 bios32: Entry =3D 0xee600 (c00ee600) Rev =3D 0 Len =3D 1 pcibios: PCI BIOS entry at 0x263e pnpbios: Found PnP BIOS data at 0xc00ff000 pnpbios: Entry =3D ea000:13de Rev =3D 1.0 pnpbios: OEM ID 744e Other BIOS signatures found: ACPI: 00000000 Preloaded elf kernel "kernel" at 0xc02b7000. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk Creating DISK md0 Math emulator present pci_open(1): mode 1 addr port (0x0cf8) is 0x800008b0 pci_open(1a): mode1res=3D0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=3D060000] [hdr=3D00] is there (id=3D04061039) pcib-: pcib0 exists, using next available unit number npx0: on motherboard npx0: INT 16 interface i586_bzero() bandwidth =3D 644329896 bytes/sec bzero() bandwidth =3D 331785003 bytes/sec pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=3D0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=3D060000] [hdr=3D00] is there (id=3D04061039) pcib0: on motherboard found-> vendor=3D0x1039, dev=3D0x0406, revid=3D0x00 class=3D06-00-00, hdrtype=3D0x00, mfdev=3D0 subordinatebus=3D0 secondarybus=3D0 found-> vendor=3D0x1039, dev=3D0x0008, revid=3D0x01 class=3D06-01-00, hdrtype=3D0x00, mfdev=3D1 subordinatebus=3D0 secondarybus=3D0 found-> vendor=3D0x1039, dev=3D0x0601, revid=3D0x01 class=3D01-01-00, hdrtype=3D0x00, mfdev=3D1 subordinatebus=3D0 secondarybus=3D0 map[10]: type 1, range 32, base 00000174, size 2 map[14]: type 1, range 32, base 000001f4, size 2 map[18]: type 1, range 32, base 00000374, size 2 map[1c]: type 1, range 32, base 000003f4, size 2 found-> vendor=3D0x1023, dev=3D0x9660, revid=3D0xd3 class=3D03-00-00, hdrtype=3D0x00, mfdev=3D0 subordinatebus=3D0 secondarybus=3D0 intpin=3Da, irq=3D255 map[10]: type 1, range 32, base 08000000, size 22 map[14]: type 1, range 32, base 08800000, size 16 map[18]: type 1, range 32, base 08400000, size 22 found-> vendor=3D0x119b, dev=3D0x1221, revid=3D0x02 class=3D06-05-00, hdrtype=3D0x00, mfdev=3D0 subordinatebus=3D0 secondarybus=3D0 intpin=3Da, irq=3D0 map[10]: type 1, range 32, base 000003e0, size 2 found-> vendor=3D0x119b, dev=3D0x1221, revid=3D0x02 class=3D06-05-00, hdrtype=3D0x00, mfdev=3D0 subordinatebus=3D0 secondarybus=3D0 intpin=3Da, irq=3D0 map[10]: type 1, range 32, base 000003e4, size 2 pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port 0x3f4-0x3f7,0x374-0x377,0x1f4-0x= 1f7,0x174-0x177 at device 1.1 on pci0 atapci0: Busmastering DMA not supported ata-: ata2 exists, using next available unit number panic: resource_list_alloc: resource entry is busy Debugger("panic") Stopped at Debugger+0x34: movb $0,in_Debugger.390 db> trace Debugger(c0211d03) at Debugger+0x34 panic(c0212680,2,1,ffffffff,1) at panic+0x70 resource_list_alloc(c0a1fe04,c0a1e080,c0a1fd80,4,c02cbd4c) at resource_list= _alloc+0xa0 pci_alloc_resource(c0a1e080,c0a1fd80,4,c02cbd4c,0) at pci_alloc_resource+0x= 38 BUS_ALLOC_RESOURCE(c0a1e080,c0a1fd80,4,c02cbd4c,0) at BUS_ALLOC_RESOURCE+0x= 43 ata_pci_alloc_resource(c0a1fd80,c0a1f880,4,c02cbde8,0) at ata_pci_alloc_res= ource+0x1be BUS_ALLOC_RESOURCE(c0a1fd80,c0a1f880,4,c02cbde8,0) at BUS_ALLOC_RESOURCE+0x= 43 bus_alloc_resource(c0a1f880,4,c02cbde8,0,ffffffff) at bus_alloc_resource+0x= 27 ata_probe(c0a1f880,c0a1f880,c0593a10,6011039,c02cbe10) at ata_probe+0xc9 ata_pcisub_probe(c0a1f880,c02cbe38,c0143459,c0a1f880,c0a1f880) at ata_pcisu= b_probe+0xc4 DEVICE_PROBE(c0a1f880,c0a1f880,c0a1fd80,0,1) at DEVICE_PROBE+0x2e device_probe_child(c0a1fd80,c0a1f880,c0a1f880,6011039,2000001) at device_pr= obe_child+0xc1 device_probe_and_attach(c0a1f880) at device_probe_and_attach+0x29 bus_generic_attach(c0a1fd80,c0a1fd80,c0a1e080,0,c0a1f900) at bus_generic_at= tach+0x16 ata_pci_attach(c0a1fd80,c02cbec4,c0143983,c0a1fd80,c0a1fd80) at ata_pci_att= ach+0x40d DEVICE_ATTACH(c0a1fd80,c0a1fd80,c0a1e180,0,c02cbed4) at DEVICE_ATTACH+0x2e device_probe_and_attach(c0a1fd80) at device_probe_and_attach+0x4f bus_generic_attach(c0a1e080,c02cbef8,c0143983,c0a1e080,c0a1e080) at bus_gen= eric_attach+0x16 DEVICE_ATTACH(c0a1e080,c0a1e080,c0a1e300,0,c02cbf08) at DEVICE_ATTACH+0x2e device_probe_and_attach(c0a1e080) at device_probe_and_attach+0x4f bus_generic_attach(c0a1e180,c02cbf2c,c0143983,c0a1e180,c0a1e180) at bus_gen= eric_attach+0x16 DEVICE_ATTACH(c0a1e180,c0a1e180,c0596880,0,c02cbf3c) at DEVICE_ATTACH+0x2e device_probe_and_attach(c0a1e180) at device_probe_and_attach+0x4f bus_generic_attach(c0a1e300,c0a1e300,c02cbf58,c011cb9e,c0a1e300) at bus_gen= eric_attach+0x16 nexus_attach(c0a1e300,c02cbf70,c0143983,c0a1e300,c0a1e300) at nexus_attach+= 0xd DEVICE_ATTACH(c0a1e300,c0a1e300,c0245a10,2d0000,c02cbf80) at DEVICE_ATTACH+= 0x2e device_probe_and_attach(c0a1e300) at device_probe_and_attach+0x4f root_bus_configure(c0596880,c022904c,0) at root_bus_configure+0x16 configure(0,2c9c00,2d0000,0,c011c5a4) at configure+0x33 mi_startup(c02cbfb4,b0206,ffe,2d0000,c0148071) at mi_startup+0x70 begin() at begin+0x4b db> call mi_starti=08 =08up nexus-: nexus0 exists, using next available unit number apm-: apm0 exists, using next available unit number npx-: npx0 exists, using next available unit number pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=3D0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=3D060000] [hdr=3D00] is there (id=3D04061039) pcib-: pcib0 exists, using next available unit number pcib-: pcib0 exists, using next available unit number npx1: on motherboard npx1: INT 16 interface i586_bzero() bandwidth =3D 644745325 bytes/sec bzero() bandwidth =3D 645577792 bytes/sec pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=3D0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=3D060000] [hdr=3D00] is there (id=3D04061039) pcib2: on motherboard pci2: on pcib2 pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=3D0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=3D060000] [hdr=3D00] is there (id=3D04061039) pcib3: on motherboard pci3: on pcib3 Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices 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 ata0: iobase=3D0x01f0 altiobase=3D0x03f6 bmaddr=3D0x0000 ata0: mask=3D03 status0=3D50 status1=3D00 ata0: mask=3D03 status0=3D50 status1=3D00 ata0: devices =3D 0x1 ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata1: iobase=3D0x0170 altiobase=3D0x0376 bmaddr=3D0x0000 ata1: mask=3D03 status0=3D50 status1=3D01 ata1: mask=3D03 status0=3D00 status1=3D01 ata1: devices =3D 0xc ata1 at port 0x170-0x177,0x376 irq 15 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 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 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x1d0000 psm0: current command byte:0067 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 1c 03 3c psm: status 1c 03 3c psm: status 1c 03 3c psm: data 08 00 00 psm: status 10 00 64 psm: status 00 02 64 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0-00, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f 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=20 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96=20 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c=20 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff=20 VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81=20 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96=20 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c=20 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff=20 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=20 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96=20 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c=20 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff=20 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x100> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) pcic0: at port 0x3e0 iomem 0xd0000 irq 10 on isa0 pcic0: management irq 10 pccard0: on pcic0 pccard1: on pcic0 pcic1: not probed (disabled) sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x90 on isa0 sio0: type 16550A, console sio1: irq maps: 0x41 0x49 0x41 0x41 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: parallel port found at 0x378 ppc0: using extended I/O port range ppc0: EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 isa_probe_children: probing PnP devices BIOS Geometries: 0:03127f3f 0..786=3D787 cylinders, 0..127=3D128 heads, 1..63=3D63 sectors 1:03feff00 0..1022=3D1023 cylinders, 0..255=3D256 heads, 1..0=3D0 sectors 2:03fdfe3f 0..1021=3D1022 cylinders, 0..254=3D255 heads, 1..63=3D63 sectors 3:03fe0200 0..1022=3D1023 cylinders, 0..2=3D3 heads, 1..0=3D0 sectors 0 accounted for Device configuration finished. bpf: faith0 attached bpf: gif0 attached bpf: gif1 attached bpf: gif2 attached bpf: gif3 attached bpf: lo0 attached pccard: card inserted, slot 0 pccard: card inserted, slot 1 ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: ATA-3 disk at ata0 as master ad0: 3102MB (6354432 sectors), 6304 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, BIOSPIO ad0: piomode=3D4 dmamode=3D2 udmamode=3D2 cblid=3D0 Creating DISK ad0 Creating DISK wd0 Mounting root from ufs:wd0s2a wd0s1: type 0xb, start 63, end =3D 3693311, size 3693249 : OK wd0s2: type 0xa5, start 3693312, end =3D 6354431, size 2661120 : OK --1yeeQ81UyVL57Vl7 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="fbsd41.wd.log" Content-Transfer-Encoding: quoted-printable boot Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.1-STABLE #0: Wed Aug 23 20:23:44 CEST 2000 root@titan.klemm.gtn.com:/usr/src/sys/compile/LAPTOP4WD Calibrating clock(s) ... TSC clock: 232521599 Hz, i8254 clock: 1193154 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/P55C (232.53-MHz 586-class CPU) Origin =3D "GenuineIntel" Id =3D 0x543 Stepping =3D 3 Features=3D0x8001bf real memory =3D 67108864 (65536K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x002d5000 - 0x03ff7fff, 64106496 bytes (15651 pages) avail memory =3D 62590976 (61124K bytes) bios32: Found BIOS32 Service Directory header at 0xc00ec050 bios32: Entry =3D 0xee600 (c00ee600) Rev =3D 0 Len =3D 1 pcibios: PCI BIOS entry at 0x263e pnpbios: Found PnP BIOS data at 0xc00ff000 pnpbios: Entry =3D ea000:13de Rev =3D 1.0 pnpbios: OEM ID 744e Other BIOS signatures found: ACPI: 00000000 Preloaded elf kernel "kernel" at 0xc02bc000. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk Creating DISK md0 Math emulator present pci_open(1): mode 1 addr port (0x0cf8) is 0x800008b0 pci_open(1a): mode1res=3D0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=3D060000] [hdr=3D00] is there (id=3D04061039) pcib-: pcib0 exists, using next available unit number npx0: on motherboard npx0: INT 16 interface i586_bzero() bandwidth =3D 645577792 bytes/sec bzero() bandwidth =3D 331785003 bytes/sec pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=3D0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=3D060000] [hdr=3D00] is there (id=3D04061039) pcib0: on motherboard found-> vendor=3D0x1039, dev=3D0x0406, revid=3D0x00 class=3D06-00-00, hdrtype=3D0x00, mfdev=3D0 subordinatebus=3D0 secondarybus=3D0 found-> vendor=3D0x1039, dev=3D0x0008, revid=3D0x01 class=3D06-01-00, hdrtype=3D0x00, mfdev=3D1 subordinatebus=3D0 secondarybus=3D0 found-> vendor=3D0x1039, dev=3D0x0601, revid=3D0x01 class=3D01-01-00, hdrtype=3D0x00, mfdev=3D1 subordinatebus=3D0 secondarybus=3D0 map[10]: type 1, range 32, base 00000174, size 2 map[14]: type 1, range 32, base 000001f4, size 2 map[18]: type 1, range 32, base 00000374, size 2 map[1c]: type 1, range 32, base 000003f4, size 2 found-> vendor=3D0x1023, dev=3D0x9660, revid=3D0xd3 class=3D03-00-00, hdrtype=3D0x00, mfdev=3D0 subordinatebus=3D0 secondarybus=3D0 intpin=3Da, irq=3D255 map[10]: type 1, range 32, base 08000000, size 22 map[14]: type 1, range 32, base 08800000, size 16 map[18]: type 1, range 32, base 08400000, size 22 found-> vendor=3D0x119b, dev=3D0x1221, revid=3D0x02 class=3D06-05-00, hdrtype=3D0x00, mfdev=3D0 subordinatebus=3D0 secondarybus=3D0 intpin=3Da, irq=3D0 map[10]: type 1, range 32, base 000003e0, size 2 found-> vendor=3D0x119b, dev=3D0x1221, revid=3D0x02 class=3D06-05-00, hdrtype=3D0x00, mfdev=3D0 subordinatebus=3D0 secondarybus=3D0 intpin=3Da, irq=3D0 map[10]: type 1, range 32, base 000003e4, size 2 pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 ide_pci0: port 0x3f4-0x3f7,0x3= 74-0x377,0x1f4-0x1f7,0x174-0x177 at device 1.1 on pci0 ide_pci0: driver is using old-style compatability shims pci0: (vendor=3D0x1023, = dev=3D0x9660) at 6.0 chip1: port 0x3e0-0x3e= 3 irq 0 at device 13.0 on pci0 chip2: port 0x3e4-0x3e= 7 irq 0 at device 14.0 on pci0 pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=3D0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=3D060000] [hdr=3D00] is there (id=3D04061039) pcib1: on motherboard pci1: on pcib1 Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices 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 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): wd0: 3102MB (6354432 sectors), 6304 cyls, 16 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid =3D 0007, dmamword =3D 0407, apio =3D 0003, udma =3D= 0007 wdc0: driver is using old-style compatability shims wdc1 at port 0x170-0x177 irq 15 on isa0 wdc1: unit 0 (atapi): , removable, accel, ovlap, dma, iordis wcd0: drive speed 3445KB/sec, 128KB cache wcd0: supported read types: CD-R, CD-DA wcd0: Audio: play, 256 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: CD-ROM 120mm data disc loaded, unlocked wdc1: driver is using old-style compatability shims atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 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 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x1d0000 psm0: current command byte:0067 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 1c 03 3c psm: status 1c 03 3c psm: status 1c 03 3c psm: data 08 00 00 psm: status 10 00 64 psm: status 00 02 64 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0-00, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f 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=20 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96=20 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c=20 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff=20 VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81=20 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96=20 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c=20 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff=20 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=20 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96=20 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c=20 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff=20 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x100> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) pcic0: at port 0x3e0 iomem 0xd0000 irq 10 on isa0 pcic0: management irq 10 pccard0: on pcic0 pccard1: on pcic0 pcic1: not probed (disabled) sio0: irq maps: 0x241 0x251 0x241 0x241 sio0 at port 0x3f8-0x3ff irq 4 flags 0x90 on isa0 sio0: type 16550A, console sio1: irq maps: 0x241 0x249 0x241 0x241 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: parallel port found at 0x378 ppc0: using extended I/O port range ppc0: EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port isa_probe_children: probing PnP devices BIOS Geometries: 0:03127f3f 0..786=3D787 cylinders, 0..127=3D128 heads, 1..63=3D63 sectors 1:03feff00 0..1022=3D1023 cylinders, 0..255=3D256 heads, 1..0=3D0 sectors 2:03fdfe3f 0..1021=3D1022 cylinders, 0..254=3D255 heads, 1..63=3D63 sectors 3:03fe0200 0..1022=3D1023 cylinders, 0..2=3D3 heads, 1..0=3D0 sectors 0 accounted for Device configuration finished. bpf: faith0 attached bpf: gif0 attached bpf: gif1 attached bpf: gif2 attached bpf: gif3 attached bpf: lo0 attached Mounting root from ufs:wd0s2a pccard: card inserted, slot 0 pccard: card inserted, slot 1 wd0s1: type 0xb, start 63, end =3D 3693311, size 3693249 : OK wd0s2: type 0xa5, start 3693312, end =3D 6354431, size 2661120 : OK start_init: trying /sbin/init swapon: adding /dev/wd0s2b as swap device Automatic boot in progress... /dev/rwd0s2a: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/rwd0s2a: clean, 7392 free (192 frags, 900 blocks, 0.6% fragmentation) /dev/rwd0s2f: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/rwd0s2f: clean, 150535 free (711 frags, 18728 blocks, 0.1% fragmentati= on) /dev/rwd0s2e: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/rwd0s2e: clean, 84989 free (117 frags, 10609 blocks, 0.1% fragmentatio= n) link_elf: symbol checkalias undefined Aug 23 22:26:51 mfs: vfsload(mfs) dmesg: /dev/drum: Device not configured kldload: can't load pcic: No such file or directory PCCARD Memory address set to 0xd0000 Enable PC-card.Doing initial network setup: hostname. lo0: flags=3D8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000=20 panic: malloc type lacks magic Debugger("panic") Stopped at Debugger+0x34: movb $0,in_Debugger.390 db> t Debugger(c0214e03) at Debugger+0x34 panic(c021434c,c69f9ee4,c012cc7b,c0a9e218,c0594e80) at panic+0x70 malloc_init(c0a9e218) at malloc_init+0x19 linker_file_sysinit(c0a7cd00,c0a7cd00,0,c0a96000,c6525440) at linker_file_s= ysinit+0xc3 linker_load_file(c0a96000,c69f9f28,c6525440,1,c69f9f80) at linker_load_file= +0x94 kldload(c6525440,c69f9f80,bfbffdd4,1,0) at kldload+0xa2 syscall2(2f,2f,2f,0,1) at syscall2+0x1f1 Xint0x80_syscall() at Xint0x80_syscall+0x25 db> a=08 =08 --1yeeQ81UyVL57Vl7 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=LAPTOP4 machine i386 cpu I586_CPU cpu I686_CPU ident LAPTOP4 maxusers 64 options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev device isa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives options ATA_STATIC_ID #Static device numbering #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0 at atkbdc? irq 12 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) device apm0 at nexus? disable flags 0x20 # Advanced Power Management # PCCARD (PCMCIA) support device card device pcic0 at isa? irq 10 port 0x3e0 iomem 0xd0000 device pcic1 at isa? irq 11 port 0x3e2 iomem 0xd4000 disable # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x90 irq 4 device sio1 at isa? port IO_COM2 irq 3 # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer device ppi # Parallel port interface device #device plip # TCP/IP over parallel #device vpo # Requires scbus and da # Xircom Ethernet device xe # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support #pseudo-device sl 1 # Kernel SLIP #pseudo-device ppp 1 # Kernel PPP #pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" pseudo-device gif 4 # IPv6 and IPv4 tunneling pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter options INCLUDE_CONFIG_FILE # Include this file in kernel options DDB options BREAK_TO_DEBUGGER options CONSPEED=38400 options GDB_REMOTE_CHAT --1yeeQ81UyVL57Vl7 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=LAPTOP4WD machine i386 cpu I586_CPU cpu I686_CPU ident LAPTOP4WD maxusers 64 options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev device isa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 # ATA and ATAPI devices #device ata0 at isa? port IO_WD1 irq 14 #device ata1 at isa? port IO_WD2 irq 15 #device ata #device atadisk # ATA disk drives #options ATA_STATIC_ID #Static device numbering #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices device wdc0 at isa? port IO_WD1 irq 14 device wd0 at wdc0 drive 0 device wd1 at wdc0 drive 1 device wdc1 at isa? port IO_WD2 irq 15 device wd2 at wdc1 drive 0 device wd3 at wdc1 drive 1 device wcd # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0 at atkbdc? irq 12 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) device apm0 at nexus? disable flags 0x20 # Advanced Power Management # PCCARD (PCMCIA) support device card device pcic0 at isa? irq 10 port 0x3e0 iomem 0xd0000 device pcic1 at isa? irq 11 port 0x3e2 iomem 0xd4000 disable # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x90 irq 4 device sio1 at isa? port IO_COM2 irq 3 # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer device ppi # Parallel port interface device #device plip # TCP/IP over parallel #device vpo # Requires scbus and da # Xircom Ethernet device xe # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support #pseudo-device sl 1 # Kernel SLIP #pseudo-device ppp 1 # Kernel PPP #pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" pseudo-device gif 4 # IPv6 and IPv4 tunneling pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter options INCLUDE_CONFIG_FILE # Include this file in kernel options DDB options BREAK_TO_DEBUGGER options CONSPEED=38400 options GDB_REMOTE_CHAT --1yeeQ81UyVL57Vl7-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 12: 8:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n1f.san.rr.com (24-25-220-168.san.rr.com [24.25.220.168]) by hub.freebsd.org (Postfix) with ESMTP id B50EE37B422 for ; Wed, 23 Aug 2000 12:08:17 -0700 (PDT) Received: from slave (doug@slave [10.0.0.1]) by dt051n1f.san.rr.com (8.9.3/8.9.3) with ESMTP id MAA08003; Wed, 23 Aug 2000 12:07:29 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Wed, 23 Aug 2000 12:07:29 -0700 (PDT) From: Doug Barton X-Sender: doug@dt051n1f.san.rr.com To: Francisco Reyes Cc: FreeBSD stable Subject: mergemaster wishlist In-Reply-To: <200008230312.XAA27385@sanson.reyes.somos.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, 22 Aug 2000, Francisco Reyes wrote: > On Thu, 17 Aug 2000 23:53:51 -0700, Doug Barton wrote: > > > Yes, thanks. This is close to the top of the wishlist. > > > Where is the wishlist for mergemaster? > Is it kept anywhere visible? Define visible. :) I have a project list of things that people have asked for that I plan to include. It's not very long, but see below. > I have one thing I have been thinking on giving it a try in a > few weeks. > Changing mergemaster to indicate files to be either ignored or > copied. Kind of an exception file. > Haven't looked at the code so I don't know how difficult it > would be. It's not terribly difficult, it's just expensive computationally (although we're still talking about a relatively trivial expense, comparitively). The big problem with this idea is that I really hate it. I mean REALLY REALLY hate it. It violates one of the central design goals that I established for the thing way back when. > The basic idea is that there are files which ones knows in > advance what one wants done with the file. For example I always > move the locate script from weekly to daily. I don't want > mergemater to stop to tell me the file is missing. So this file > would be ignored. There are better ways to handle that. For example, you could leave an empty file with the same CVS Id in the "real" location. Then you won't be bothered by mm telling you that it's missing, AND you have the added benefit of knowing when it needs to be updated. > The other case is files which one want copied without questions. > All the files in /etc/defaults I never touch so I would prefer > them to be merged without questions. But if there are changes you SHOULD look to see what the changes are. I am working on an addition to mm that will show you how your rc.conf[.local] and make.conf file variables differ from those in /etc/defaults, but even that isn't foolproof. All that said, this is a frequent request (every couple months it pops up) so I am working on a way to do it which will satisfy the requestors and me both. Please don't ask about timelines, my life is rather chaotic right now. Thanks for your interest, Doug -- "Live free or die" - State motto of my ancestral homeland, New Hampshire Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 12:12:43 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 68EC937B422 for ; Wed, 23 Aug 2000 12:12:26 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id BA9DDE89F for ; Wed, 23 Aug 2000 15:12:25 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.9.3/8.9.3) id PAA00451; Wed, 23 Aug 2000 15:12:25 -0400 (EDT) (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: <14756.8729.629364.19998@onceler.kciLink.com> Date: Wed, 23 Aug 2000 15:12:25 -0400 (EDT) To: stable@freebsd.org Subject: ATAPI CD-ROM fails to mount on 4.1-STABLE X-Mailer: VM 6.72 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I updated my 4.1-STABLE yesterday. Today I tried to read a CD-ROM (the FreeBSD 4.1-R install CD, and also one generic data CD I made a while back that was ok on this system before) and the mount never completes. Here's what happens. I insert the CD and type "mount /cdrom". The mount command returns. The /var/log/messages syslog contains this entry: /kernel: cd9660: RockRidge Extension I do an "ls /cdrom" and I get either -r-xr-xr-x 1 root wheel 0 Dec 31 1969 /cdrom* or some generic "input/output error" from ls. Before the mount, the /cdrom directory looks like this: drwxr-xr-x 2 khera wheel 512 Aug 11 14:13 /cdrom The syslog now contains this entry: /kernel: RRIP without PX field? I can no longer umount or "eject -f" the drive: umount: unmount of /cdrom failed: Invalid argument eject: Device busy However, after running eject, I can manually eject the disk. The "mount" command says this: /dev/acd0c on /cdrom (cd9660, local, nodev, nosuid, read-only, mounted by khera, reads: sync 3 async 0) It matters not whether I run mount as root or as a user. The only way out is a reboot. Booting the 4.1-R kernel.GENERIC, I can mount and read the CD-ROM just fine. It worked fine as of last friday as well, when I last did an update and used the CD-ROM. To me, this rules out hardware problems. I just cvsup'd again, and rebuilt a kernel (with DMA for ATAPI turned off) but that made no difference. (about 2:30pm EDT 23-AUG-2000) Any clues as to what to do to get back my CD-ROM drive functionality? Anyone else experiencing this trouble? Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 12:17:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 30F6937B423 for ; Wed, 23 Aug 2000 12:17:15 -0700 (PDT) Received: (qmail 10764 invoked by uid 0); 23 Aug 2000 19:17:13 -0000 Received: from p3ee2160e.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.14) by mail.gmx.net with SMTP; 23 Aug 2000 19:17:13 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id SAA20184 for freebsd-stable@freebsd.org; Wed, 23 Aug 2000 18:39:06 +0200 Date: Wed, 23 Aug 2000 18:39:06 +0200 From: Gerhard Sittig To: freebsd-stable@freebsd.org Subject: Re: Configuring kernel for ISA cards Message-ID: <20000823183906.I252@speedy.gsinet> Mail-Followup-To: freebsd-stable@freebsd.org References: <39A3AE82.FFCD5C19@cequrux.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <39A3AE82.FFCD5C19@cequrux.com>; from gram@cequrux.com on Wed, Aug 23, 2000 at 12:59:14PM +0200 Organization: System Defenestrators Inc. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 23, 2000 at 12:59 +0200, Graham Wheeler wrote: > > FreeBSD 3.x introduced the new boot loader stuff. One of the > consequences was that changing the kernel config at boot time > did not save the changes to the kernel permanently. Instead, it > seems, these changes are supposed to go in /boot/loader.rc. The > docs seem very sparse about all of this, unless I've somehow > missed the relevant material. > > Now, I was told that the same commands can be used in the > loader.rc file as are used in the configuration editor. > However, it seems to me that this only holds for PCI cards. > When I have tried to configure the IRQ for an ISA card, the > loader has complained about a syntax error. > > I believe the command I used was: > > irq ed0 10 Have a look at (or create) the /boot/kernel.conf file. It takes whatever you want to do with the kernel config (like "boot -c" and doing things at the config prompt). And don't forget the final line with a "q" on it (don't know whether EOF will suffice for ending configuration -- and strictly speaking I don't want to test it out with the chance to have an unbootable machine afterwards:). Mine looks like this, you can use it as an example: ----- cat /boot/kernel.conf ------- di sio1 q ----------------------------------- Not really much, I know. But all to give you an idea. :) 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 Wed Aug 23 12:17:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n1f.san.rr.com (24-25-220-168.san.rr.com [24.25.220.168]) by hub.freebsd.org (Postfix) with ESMTP id C10AB37B423 for ; Wed, 23 Aug 2000 12:17:50 -0700 (PDT) Received: from slave (doug@slave [10.0.0.1]) by dt051n1f.san.rr.com (8.9.3/8.9.3) with ESMTP id MAA08091; Wed, 23 Aug 2000 12:17:43 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Wed, 23 Aug 2000 12:17:43 -0700 (PDT) From: Doug Barton X-Sender: doug@dt051n1f.san.rr.com To: Peter Jeremy Cc: FreeBSD stable Subject: Re: remove empty TEMPROOT dirs at mergemaster's end? (was: cvs commit:src/usr.sbin/mergemaster mergemaster.sh) In-Reply-To: <00Aug23.140643est.115225@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 23 Aug 2000, Peter Jeremy wrote: > But displaying the differences means that you get to see what has > changed (and hence what changes are needed in your local overrides). > > As an example, rc.conf was recently changed (in -current) to not > start inetd, portmap or sendmail. If you are actually relying on > any of these daemons, and you actually notice the differences in > /etc/defaults/rc.conf, you will be able to update /etc/rc.conf > without a period of head-scratching when they don't start. Or worse, complete inability to reach the box in the case of a remote upgrade. This is just about the best example I've seen in recent days of why I feel justified in "enforcing" the policy of making the administrator LOOK at the changes before installing. Thanks, Doug -- "Live free or die" - State motto of my ancestral homeland, New Hampshire Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 12:22:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rz.uni-ulm.de (sirius-giga.rz.uni-ulm.de [134.60.241.36]) by hub.freebsd.org (Postfix) with ESMTP id 4D08137B43C for ; Wed, 23 Aug 2000 12:22:15 -0700 (PDT) Received: from lilith.gmx.de (lilith.wohnheim.uni-ulm.de [134.60.106.64]) by mail.rz.uni-ulm.de (8.9.3/8.9.3) with ESMTP id VAA12307; Wed, 23 Aug 2000 21:22:11 +0200 (MEST) Message-Id: <4.3.2.7.2.20000823211710.00a96a10@imap.rz.uni-ulm.de> X-Sender: siegbert.baude@student.uni-ulm.de@imap.rz.uni-ulm.de X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 23 Aug 2000 21:22:11 +0200 To: Vivek Khera From: Siegbert Baude Subject: Re: missing c++rt0.o file, where to get? Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <14756.2022.695697.5862@onceler.kciLink.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Vivek, At 19:20 23.08.00, you wrote: >I'm attempting to build the plugger port, and it comes back with this >error: > >make plugger.so CC=3Dgcc XCFLAGS=3D'-fpic -aout' LD=3Dgcc XLDFLAGS=3D'-shar= ed -aout' >gcc -shared -aout -o plugger.so plugger.o common.o >ld: c++rt0.o: No such file or directory >*** Error code 1 > >I see sources for /usr/src/lib/csu/i386/c++rt0.c but the Makefile in >there doesn't seem to build with "-aout" option, so it is unlikely to >be the right incantation. I=B4ve asked the same question on freebsd-questions last week, until now no= =20 answer. If you figure out or get private mail-responses, it would be nice=20 if you inform me. Search on the mailing list of the last week for=20 freebsd-questions there you will find also a download address for the .o=20 file. (Someone posted this URL some months ago but with a typo, which I=20 corrected in this last mail. Sorry I don=B4t have it handy in the moment.) The correct solution would be of course to fix the port. Ciao Siegbert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 12:26:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay1.inwind.it (relay1.inwind.it [212.141.53.67]) by hub.freebsd.org (Postfix) with ESMTP id 0B13A37B423 for ; Wed, 23 Aug 2000 12:26:11 -0700 (PDT) Received: from gw5a60-1-d61.wind.it (212.141.86.61) by relay1.inwind.it (5.1.039) id 399AA5C50007B8DC for freebsd-stable@freebsd.org; Wed, 23 Aug 2000 21:26:09 +0200 Received: (qmail 1939 invoked by uid 1000); 23 Aug 2000 19:25:39 -0000 Date: Wed, 23 Aug 2000 21:25:38 +0200 From: Francesco Casadei To: freebsd-stable mailing list Subject: pcm0: hwptr went bacwards Message-ID: <20000823212538.A1801@goku.kasby> Mail-Followup-To: freebsd-stable mailing list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 4.1-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have cvsup'd and rebuilt world today (2000-08-23). No more clicks now from my sb16: the sound is simply perfect, but occasionally I get the following error message: Aug 23 21:05:45 goku /kernel: pcm0: hwptr went backwards 4128 -> 4112 Aug 23 21:05:45 goku /kernel: pcm0: hwptr went backwards 4128 -> 4112 Aug 23 21:05:45 goku /kernel: pcm0: hwptr went backwards 4176 -> 2456 Aug 23 21:05:45 goku /kernel: pcm0: hwptr went backwards 4176 -> 2456 Here's more info on my system: casimiro> uname -a FreeBSD goku.kasby 4.1-STABLE FreeBSD 4.1-STABLE #0: Wed Aug 23 15:52:29 CEST 2000 root@goku.kasby:/usr/obj/usr/src/sys/GOKU i386 casimiro> tail -3 /usr/src/sys/i386/conf/GOKU # Sound board device pcm device sbc0 at isa? port 0x220 irq 5 drq 1 flags 0x15 casimiro> cat /dev/sndstat FreeBSD Audio Driver (newpcm) Aug 23 2000 15:51:38 Installed devices: pcm0: at io 0x220 irq 5 drq 1:5 (1p/1r channels duplex) casimiro> dmesg | grep -E 'sbc|pcm' sbc0: at port 0x220-0x22f irq 5 drq 1 flags 0x15 on isa0 sbc0: setting card to irq 5, drq 1, 5 pcm0: on sbc0 Francesco Casadei To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 12:30:30 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 38F3237B42C for ; Wed, 23 Aug 2000 12:30:26 -0700 (PDT) Received: (from sto@localhost) by isds.duke.edu (8.8.8/8.8.8) id PAA23490; Wed, 23 Aug 2000 15:30:25 -0400 (EDT) Date: Wed, 23 Aug 2000 15:30:25 -0400 From: "Sean O'Connell" To: freebsd-stable@FreeBSD.ORG Cc: Vivek Khera , Siegbert Baude Subject: Re: missing c++rt0.o file, where to get? Message-ID: <20000823153025.A23264@stat.Duke.EDU> Reply-To: "Sean O'Connell" Mail-Followup-To: Sean O'Connell , freebsd-stable@FreeBSD.ORG, Vivek Khera , Siegbert Baude References: <14756.2022.695697.5862@onceler.kciLink.com> <4.3.2.7.2.20000823211710.00a96a10@imap.rz.uni-ulm.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2i In-Reply-To: <4.3.2.7.2.20000823211710.00a96a10@imap.rz.uni-ulm.de>; from Siegbert.Baude@gmx.de on Wed, Aug 23, 2000 at 09:22:11PM +0200 X-Organization: Institute of Statistics and Decision Sciences Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Siegbert Baude stated: : : IŽve asked the same question on freebsd-questions last week, until now no : answer. If you figure out or get private mail-responses, it would be nice : if you inform me. Search on the mailing list of the last week for : freebsd-questions there you will find also a download address for the .o : file. (Someone posted this URL some months ago but with a typo, which I : corrected in this last mail. Sorry I donŽt have it handy in the moment.) : The correct solution would be of course to fix the port. Siegbert and Vivek- I have put together a little package called fbsd-aout-libs-2.2.8 (not very imaginative .. I admit :). I originally put it together so my users could compile a.out stuff using the NAG f90 compiler (which thankfully now f95 and supports ELF). % ls -s FreeBSD/fbsd-aout-libs-2.2.8.tgz 4720 FreeBSD/fbsd-aout-libs-2.2.8.tgzeeBSD/fbsd-aout-libs-2.2.8.tgz % md5 FreeBSD/fbsd-aout-libs-2.2.8.tgz MD5 (FreeBSD/fbsd-aout-libs-2.2.8.tgz) = 7d9499e8e7637f194122860862619fec It is available via http get from http://www.stat.duke.edu/~sto/FreeBSD/fbsd-aout-libs-2.2.8.tgz Hope this helps, 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 Wed Aug 23 12:35:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 8F04637B423 for ; Wed, 23 Aug 2000 12:35:16 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13RgIp-00092J-00; Wed, 23 Aug 2000 19:35:11 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id VAA01374; Wed, 23 Aug 2000 21:35:21 +0200 (CEST) (envelope-from wkb) Date: Wed, 23 Aug 2000 21:35:21 +0200 From: Wilko Bulte To: Simon Cc: Robert Augustine , "stable@FreeBSD.ORG" Subject: Re: Random Reboots Message-ID: <20000823213521.C1257@freebie.demon.nl> References: <003801c00d2a$03c7ff00$0200000a@cm.420.net> <200008231838.MAA60772@mail.fpsn.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200008231838.MAA60772@mail.fpsn.net>; from simon@optinet.com on Wed, Aug 23, 2000 at 01:56:07PM -0400 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 23, 2000 at 01:56:07PM -0400, Simon wrote: > I've exeprienced the same behavior with bad RAM in the system. Did you ever have this box running rock solid before? Another famous/notorious one is insufficient CPU cooling or a weak/dying PSU W/ -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 13: 6: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hayward.u-net.com (hayward.u-net.com [193.119.181.49]) by hub.freebsd.org (Postfix) with ESMTP id 19FA737B423 for ; Wed, 23 Aug 2000 13:05:37 -0700 (PDT) Received: from localhost (alex@localhost) by hayward.u-net.com (8.9.3/8.9.3) with ESMTP id VAA05578 for ; Thu, 24 Aug 2000 21:07:14 +0100 (BST) (envelope-from xelah@xelah.com) X-Authentication-Warning: hayward.u-net.com: alex owned process doing -bs Date: Thu, 24 Aug 2000 21:07:13 +0100 (BST) From: Alex Hayward X-Sender: alex@hayward.u-net.com To: freebsd-stable@FreeBSD.ORG Subject: Re: UDMA66 not recognized In-Reply-To: <39A40446.7967E391@club-internet.fr> 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, 23 Aug 2000, David Scialom wrote: > James Housley wrote: > > > David Scialom wrote: > > > > > > I have also the problem that my FreeBSD does not recognize my Matrox > > > hard disk drive which is UDMA 66 and is connected to the first > > > > [snip] > > > > > atapci0: port 0xd800-0xd80f at device > > > 4.1 on pci0 > > > ata0: at 0x1f0 irq 14 on atapci0 > > > ata1: at 0x170 irq 15 on atapci0 > > > > That is becuase it is only an ATA33 controller. > > I know that but the documentation of the mothercard (Asus P3V4X > JumperFree) says: > > "UDMA66/Support: Comes with an on board PCI bus Master Controller with 2 > connectors that support 4 IDE devices on 2 channel. Support UDMA 66, UDMA > 33 PIO mode 3 & 4 and bus master IDE DMA mode 2." > > But freebsd does not seem to recognise UDMA 66? The 82C596 is ATA-33, whilst the 82C596B is ATA-66. AFAICS there is code to distinguish the two...have you looked at the label on the chip itself? As an aside I have the VIA 82C686, which is also ATA-66...it's detected as ATA-66, the disk is reported as being used with UDMA66 but I /still/ don't get UDMA66 speeds out of it. Instead I get ~22MB/s (from both the start and end of the disk), even if I take the other devices off the other channel. This is with both CURRENT and STABLE. My dmesg: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.1-STABLE #0: Mon Aug 21 17:18:42 BST 2000 toor@hayward.u-net.com:/mnt/mainpart1/usr-STABLE/obj/mnt/mainpart1/usr-STABLE/src/sys/HAYWARD Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (451.03-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 real memory = 134152192 (131008K bytes) avail memory = 127565824 (124576K bytes) Preloaded elf kernel "kernel" at 0xc0309000. DEVFS: ready for devices VESA: v2.0, 8192k memory, flags:0x1, mode table:0xc00c6964 (c0006964) VESA: Matrox Graphics Inc. K6-family MTRR support enabled (2 registers) md0: Malloc disk apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib2: at device 1.0 on pci0 pci1: on pcib2 pci1: at 0.0 irq 11 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xc000-0xc00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 chip2: port 0xd400-0xd403,0xd000-0xd003,0xcc00-0xccff irq 10 at device 7.5 on pci0 ed0: port 0xd800-0xd81f irq 5 at device 9.0 on pci0 ed0: address 00:40:95:43:7a:ef, type NE2000 (16 bit) pcm0: port 0xdc00-0xdc1f irq 9 at device 11.0 on pci0 pcib1: on motherboard pci2: on pcib1 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: 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> 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 (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port DEVFS: ready to run IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to accept, logging limited to 30 packets/entry by default IP Filter: v3.4.8 initialized. Default = pass all, Logging = enabled ad0: 29314MB [59560/16/63] at ata0-master using UDMA66 ast0: TAPE at ata1-master using WDMA2 acd0: CDROM at ata1-slave using WDMA2 Mounting root from ufs:/dev/ad0s2a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 13:20:39 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 D2ED137B423 for ; Wed, 23 Aug 2000 13:20:37 -0700 (PDT) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id QAA38891; Wed, 23 Aug 2000 16:21:14 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Wed, 23 Aug 2000 16:21:14 -0400 (EDT) From: Adam To: Alex Hayward Cc: freebsd-stable@FreeBSD.ORG Subject: Re: UDMA66 not recognized 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 >As an aside I have the VIA 82C686, which is also ATA-66...it's detected as >ATA-66, the disk is reported as being used with UDMA66 but I /still/ don't >get UDMA66 speeds out of it. Instead I get ~22MB/s (from both the start >and end of the disk), even if I take the other devices off the other >channel. This is with both CURRENT and STABLE. > >My dmesg: > >ad0: 29314MB [59560/16/63] at ata0-master using UDMA66 Sorry, but you cannot expect 66MB/sec from a single hard drive, not with todays hard drives at least. Not ide, not scsi, not windows, not unix. 22 is a good number for a 30g IDE drive. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 13:29:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from server.raadinfo.net (smtp2.uwnet.nl [195.7.130.55]) by hub.freebsd.org (Postfix) with ESMTP id 72BCC37B42C for ; Wed, 23 Aug 2000 13:29:04 -0700 (PDT) Received: from port84.isd.to (port84.isd.to [195.7.129.84]) by server.raadinfo.net (8.9.3/8.9.3) with ESMTP id WAA07318 for ; Wed, 23 Aug 2000 22:26:18 +0200 Received: (qmail 11682 invoked by uid 1000); 23 Aug 2000 20:08:44 -0000 From: "Andre Goeree" Date: Wed, 23 Aug 2000 22:08:44 +0200 To: Vivek Khera Cc: freebsd-stable@freebsd.org Subject: Re: ATAPI CD-ROM fails to mount on 4.1-STABLE Message-ID: <20000823220844.A11674@freebee.attica.home> Reply-To: abgoeree@uwnet.nl References: <14756.8729.629364.19998@onceler.kciLink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14756.8729.629364.19998@onceler.kciLink.com>; from khera@kciLink.com on Wed, Aug 23, 2000 at 03:12:25PM -0400 X-Sender: abgoeree@uwnet.nl Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 23, 2000 at 03:12:25PM -0400, Vivek Khera wrote: > I updated my 4.1-STABLE yesterday. Today I tried to read a CD-ROM > (the FreeBSD 4.1-R install CD, and also one generic data CD I made a > while back that was ok on this system before) and the mount never > completes. > > Here's what happens. > > I insert the CD and type "mount /cdrom". The mount command returns. > The /var/log/messages syslog contains this entry: > > /kernel: cd9660: RockRidge Extension > > I do an "ls /cdrom" and I get either > > -r-xr-xr-x 1 root wheel 0 Dec 31 1969 /cdrom* > > or some generic "input/output error" from ls. Before the mount, the > /cdrom directory looks like this: > > drwxr-xr-x 2 khera wheel 512 Aug 11 14:13 /cdrom > > > The syslog now contains this entry: > > /kernel: RRIP without PX field? > > I can no longer umount or "eject -f" the drive: > > umount: unmount of /cdrom failed: Invalid argument > > eject: Device busy > > However, after running eject, I can manually eject the disk. > > The "mount" command says this: > > /dev/acd0c on /cdrom (cd9660, local, nodev, nosuid, read-only, mounted by khera, reads: sync 3 async 0) > > It matters not whether I run mount as root or as a user. > > The only way out is a reboot. Booting the 4.1-R kernel.GENERIC, I can > mount and read the CD-ROM just fine. It worked fine as of last friday > as well, when I last did an update and used the CD-ROM. To me, this > rules out hardware problems. > > I just cvsup'd again, and rebuilt a kernel (with DMA for ATAPI turned > off) but that made no difference. (about 2:30pm EDT 23-AUG-2000) > > Any clues as to what to do to get back my CD-ROM drive functionality? > > Anyone else experiencing this trouble? > > Thanks. > Yes, The same story, the same problem.... -- Ago abgoeree@uwnet.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 13:31: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wyattearp.stanford.edu (wyattearp.Stanford.EDU [171.66.63.23]) by hub.freebsd.org (Postfix) with ESMTP id 7FEA337B422 for ; Wed, 23 Aug 2000 13:31:00 -0700 (PDT) Received: (from richw@localhost) by wyattearp.stanford.edu (8.9.3/8.9.3) id NAA17424; Wed, 23 Aug 2000 13:30:27 -0700 (PDT) (envelope-from richw) Date: Wed, 23 Aug 2000 13:30:27 -0700 (PDT) From: Rich Wales X-Sender: richw@wyattearp.stanford.edu To: freebsd-stable@freebsd.org Subject: Re: ATAPI CD-ROM fails to mount on 4.1-STABLE Message-ID: <200008232010244.richw@wyattearp.stanford.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vivek Khera wrote: > I updated my 4.1-STABLE yesterday. Today I tried to > read a CD-ROM (the FreeBSD 4.1-R install CD, and also > one generic data CD I made a while back that was ok > on this system before) and the mount never completes. What you described sounds exactly like the problem I had yesterday. Did you update your entire system to 4.1-STABLE, or just the kernel? If you updated only your kernel, the answer seems to be that you can't do that. Update everything, or else don't update anything. Rich Wales richw@webcom.com http://www.webcom.com/richw/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 14:30:17 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 B39D237B43F for ; Wed, 23 Aug 2000 14:30:07 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id F3E56E89F; Wed, 23 Aug 2000 17:30:06 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.9.3/8.9.3) id RAA02211; Wed, 23 Aug 2000 17:30:06 -0400 (EDT) (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: <14756.16990.843831.76961@onceler.kciLink.com> Date: Wed, 23 Aug 2000 17:30:06 -0400 (EDT) To: Rich Wales Cc: freebsd-stable@freebsd.org Subject: Re: ATAPI CD-ROM fails to mount on 4.1-STABLE In-Reply-To: <200008232010244.richw@wyattearp.stanford.edu> References: <200008232010244.richw@wyattearp.stanford.edu> X-Mailer: VM 6.72 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "RW" == Rich Wales writes: RW> Vivek Khera wrote: >> I updated my 4.1-STABLE yesterday. Today I tried to >> read a CD-ROM (the FreeBSD 4.1-R install CD, and also >> one generic data CD I made a while back that was ok >> on this system before) and the mount never completes. RW> What you described sounds exactly like the problem I had yesterday. RW> Did you update your entire system to 4.1-STABLE, or just the kernel? Yesterday I updated everything. Today I just did the kernel. No difference in breakage. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 15: 2:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hayward.u-net.com (hayward.u-net.com [193.119.181.49]) by hub.freebsd.org (Postfix) with ESMTP id 26C5A37B422 for ; Wed, 23 Aug 2000 15:02:42 -0700 (PDT) Received: from localhost (alex@localhost) by hayward.u-net.com (8.9.3/8.9.3) with ESMTP id XAA10767 for ; Thu, 24 Aug 2000 23:05:57 +0100 (BST) (envelope-from xelah@xelah.com) X-Authentication-Warning: hayward.u-net.com: alex owned process doing -bs Date: Thu, 24 Aug 2000 23:05:57 +0100 (BST) From: Alex Hayward X-Sender: alex@hayward.u-net.com To: freebsd-stable@FreeBSD.ORG Subject: Re: UDMA66 not recognized 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 Wed, 23 Aug 2000, Adam wrote: > >As an aside I have the VIA 82C686, which is also ATA-66...it's detected as > >ATA-66, the disk is reported as being used with UDMA66 but I /still/ don't > >get UDMA66 speeds out of it. Instead I get ~22MB/s (from both the start > >and end of the disk), even if I take the other devices off the other > >channel. This is with both CURRENT and STABLE. > > > >My dmesg: > > > >ad0: 29314MB [59560/16/63] at ata0-master using UDMA66 > > Sorry, but you cannot expect 66MB/sec from a single hard drive, not with > todays hard drives at least. Not ide, not scsi, not windows, not > unix. 22 is a good number for a 30g IDE drive. I don't expect 66MB/s. However, I do expect to get something closer to what the benchmarks in reviews have got for this drive (twenty some up to about 35 near the beginning of the disk). I'd also expect it to be slower at the end of the disk compared to the start which is what makes me think it hasn't reached the limit of the drive yet. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 15: 7:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mb01.swip.net (mb01.swip.net [193.12.122.205]) by hub.freebsd.org (Postfix) with ESMTP id D613D37B423 for ; Wed, 23 Aug 2000 15:07:24 -0700 (PDT) Received: from swipnet.se (d212-151-168-180.swipnet.se [212.151.168.180]) by mb01.swip.net (8.8.8/8.8.8) with ESMTP id AAA13953 for ; Thu, 24 Aug 2000 00:07:15 +0200 (MET DST) Message-ID: <39A44BA6.AF0311E6@swipnet.se> Date: Thu, 24 Aug 2000 00:09:42 +0200 From: je X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@FreeBSD.org Subject: subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 16:26:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id B6B9437B446 for ; Wed, 23 Aug 2000 16:26:09 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id QAA00873; Wed, 23 Aug 2000 16:39:30 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008232339.QAA00873@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dermot McNally Cc: freebsd-stable@freebsd.org Subject: Re: Numbering of fxp devices In-reply-to: Your message of "Tue, 22 Aug 2000 12:35:06 BST." <39A2656A.F156C9D9@traveldev.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 23 Aug 2000 16:39:30 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a box with two fxp devices which probe like this: > > fxp0: port 0x2000-0x203f mem > 0xf4200000-0xf42fffff,0xf4300000-0xf4300fff irq 5 at device 4.0 on pci2 > fxp0: Ethernet address 00:d0:b7:69:93:79 > fxp1: port 0x1080-0x10bf mem > 0xf4000000-0xf40fffff,0xf4100000-0xf4100fff irq 10 at device 14.0 on > pci0 > fxp1: Ethernet address 00:90:27:f7:06:2e > > One of these is integrated in the motherboard, the other is a card. What > puzzles me is the order in which the devices are numbered. I had > expected (for no particular reason) that the on-board device would come > up as fxp0, but when I first installed 4.0-RELEASE, they came up the > other way around. The order stayed this way for a couple of weeks during > which I tracked -stable and made world frequently, but after one > upgrade, the box came up with the on-board card claiming to be fxp0. > However, not long afterwards, it reverted to the original behaviour. > > Now, obviously the numbering doesn't matter all that much. What _does_ > matter is if the numbering is unpredictable at boot time (worst case) or > if it may be reversed after a remote upgrade. Is this down to pure fluke > or can I lock down the order in some way? The numbering is based on slot numbers as assigned by your BIOS. Things may be insanely permuted if/when you move things around, but they should stay stable otherwise. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 16:33:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from awww.jeah.net (awww.jeah.net [216.111.239.130]) by hub.freebsd.org (Postfix) with ESMTP id B0A9337B50D; Wed, 23 Aug 2000 16:32:46 -0700 (PDT) Received: (from chris@localhost) by awww.jeah.net (8.9.3/8.9.3) id SAA15508; Wed, 23 Aug 2000 18:33:21 -0500 (CDT) (envelope-from chris) Date: Wed, 23 Aug 2000 18:33:21 -0500 (CDT) From: Chris Byrnes Message-Id: <200008232333.SAA15508@awww.jeah.net> To: chris@awww.jeah.net, questions@freebsd.org, stable@freebsd.org Subject: WTF Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running 3.5-STABLE. Recently, my server has started rebooting, at random times, usually actually quite religiously about every 2 days. I thought it might be a RAM problem. Replaced with brand new RAM. Same problem. Any ideas, at all? Pllllllllllllease. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 16:40:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.fpsn.net (mail.fpsn.net [63.224.69.57]) by hub.freebsd.org (Postfix) with ESMTP id 8ABE337B618; Wed, 23 Aug 2000 16:40:40 -0700 (PDT) Received: from sharky (adsl-151-202-97-90.bellatlantic.net [151.202.97.90]) by mail.fpsn.net (8.9.3/8.9.3) with SMTP id SAA62332; Wed, 23 Aug 2000 18:30:24 -0600 (MDT) (envelope-from simon@optinet.com) Message-Id: <200008240030.SAA62332@mail.fpsn.net> From: "Simon" To: "chris@awww.jeah.net" , "questions@FreeBSD.ORG" , "stable@FreeBSD.ORG" Date: Wed, 23 Aug 2000 19:44:16 -0400 Reply-To: "Simon" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 2000 (5.0.2195) In-Reply-To: <200008232333.SAA15508@awww.jeah.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: WTF Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG it can be anything! and i mean anything! bad RAM, bad harddrive, bad CPU, etc... and i know EXACTLY how it feels when shit like this happens. Unfortunately, it's not always easy to determine the cause. Are you using %100 certified RAM for your motherboard? just because it's new doesn't mean jack. I had servers go wild with brand new out of the box RAM and harddrives. You said it only started recently, try to remember after what? some change you made? more load? do you have logs enabled? anything in there? do you monitor this machine? what's the load average like? swap usage, etc... what is it doing most of the time? -Simon On Wed, 23 Aug 2000 18:33:21 -0500 (CDT), Chris Byrnes wrote: >I'm running 3.5-STABLE. > >Recently, my server has started rebooting, at random times, usually >actually quite religiously about every 2 days. > >I thought it might be a RAM problem. Replaced with brand new RAM. >Same problem. > >Any ideas, at all? Pllllllllllllease. > >Chris > > >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 Aug 23 16:45:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from awww.jeah.net (awww.jeah.net [216.111.239.130]) by hub.freebsd.org (Postfix) with ESMTP id 5563637B61E; Wed, 23 Aug 2000 16:45:49 -0700 (PDT) Received: from localhost (chris@localhost) by awww.jeah.net (8.9.3/8.9.3) with ESMTP id SAA17551; Wed, 23 Aug 2000 18:46:27 -0500 (CDT) (envelope-from chris@jeah.net) Date: Wed, 23 Aug 2000 18:46:27 -0500 (CDT) From: Chris Byrnes To: Simon Cc: "questions@FreeBSD.ORG" , "stable@FreeBSD.ORG" Subject: Re: WTF In-Reply-To: <200008240030.SAA62332@mail.fpsn.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 SWAP usage has been high lately. It happened RIGHT after I upgraded the system to a new CPU, board, and RAM, and to 3.50STABLE. I thought maybe there was a OS issue with my SUP or something (I was hoping). That's when it started happening. God, I dont have TIME to weed thru trying new boards and new CPUs. I wish there was a quick fix. ------------------------------------------------- Chris Byrnes, Owner NSI NIC HANDLE CB5820 Jeah Communications http://www.jeah.net ------------------------------------------------- On Wed, 23 Aug 2000, Simon wrote: > it can be anything! and i mean anything! bad RAM, bad harddrive, bad CPU, etc... and i know EXACTLY how it feels > when shit like this happens. Unfortunately, it's not always easy to determine the cause. Are you using %100 certified > RAM for your motherboard? just because it's new doesn't mean jack. I had servers go wild with brand new out of the box > RAM and harddrives. You said it only started recently, try to remember after what? some change you made? more load? > do you have logs enabled? anything in there? do you monitor this machine? what's the load average like? swap usage, > etc... what is it doing most of the time? > > -Simon > > On Wed, 23 Aug 2000 18:33:21 -0500 (CDT), Chris Byrnes wrote: > > >I'm running 3.5-STABLE. > > > >Recently, my server has started rebooting, at random times, usually > >actually quite religiously about every 2 days. > > > >I thought it might be a RAM problem. Replaced with brand new RAM. > >Same problem. > > > >Any ideas, at all? Pllllllllllllease. > > > >Chris > > > > > >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 Aug 23 16:52:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.fpsn.net (mail.fpsn.net [63.224.69.57]) by hub.freebsd.org (Postfix) with ESMTP id BD3BF37B61F; Wed, 23 Aug 2000 16:52:40 -0700 (PDT) Received: from sharky (adsl-151-202-97-90.bellatlantic.net [151.202.97.90]) by mail.fpsn.net (8.9.3/8.9.3) with SMTP id SAA62397; Wed, 23 Aug 2000 18:42:32 -0600 (MDT) (envelope-from simon@optinet.com) Message-Id: <200008240042.SAA62397@mail.fpsn.net> From: "Simon" To: "Chris Byrnes" Cc: "questions@FreeBSD.ORG" , "stable@FreeBSD.ORG" Date: Wed, 23 Aug 2000 19:56:17 -0400 Reply-To: "Simon" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 2000 (5.0.2195) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: WTF Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From your description, I have to put a high bet on a faulty hardware you added or issues it has with existing hardware. If I were you, I would change the hardware exactly to what it was before and see if stays up for a week - that would eliminate the OS (which i doubt anyway). Then replace RAM and see if it crashes within another week. Then finally add the CPU. Or do this quick by stress testing the system. Of course if this a production box, you're pretty much stuck ;-( -Simon On Wed, 23 Aug 2000 18:46:27 -0500 (CDT), Chris Byrnes wrote: >SWAP usage has been high lately. It happened RIGHT after I upgraded the >system to a new CPU, board, and RAM, and to 3.50STABLE. I >thought maybe there was a OS issue with my SUP or something (I >was hoping). That's when it started >happening. God, I dont have TIME to weed thru trying new boards and new >CPUs. > >I wish there was a quick fix. > >------------------------------------------------- >Chris Byrnes, Owner NSI NIC HANDLE CB5820 >Jeah Communications http://www.jeah.net >------------------------------------------------- > >On Wed, 23 Aug 2000, Simon wrote: > >> it can be anything! and i mean anything! bad RAM, bad harddrive, bad CPU, etc... and i know EXACTLY how it feels >> when shit like this happens. Unfortunately, it's not always easy to determine the cause. Are you using %100 certified >> RAM for your motherboard? just because it's new doesn't mean jack. I had servers go wild with brand new out of the box >> RAM and harddrives. You said it only started recently, try to remember after what? some change you made? more load? >> do you have logs enabled? anything in there? do you monitor this machine? what's the load average like? swap usage, >> etc... what is it doing most of the time? >> >> -Simon >> >> On Wed, 23 Aug 2000 18:33:21 -0500 (CDT), Chris Byrnes wrote: >> >> >I'm running 3.5-STABLE. >> > >> >Recently, my server has started rebooting, at random times, usually >> >actually quite religiously about every 2 days. >> > >> >I thought it might be a RAM problem. Replaced with brand new RAM. >> >Same problem. >> > >> >Any ideas, at all? Pllllllllllllease. >> > >> >Chris >> > >> > >> >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 Aug 23 16:56:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wondermutt.net (host75-157.student.udel.edu [128.175.75.157]) by hub.freebsd.org (Postfix) with ESMTP id C346237B616; Wed, 23 Aug 2000 16:56:02 -0700 (PDT) Received: from morgaine.udel.edu (morgaine.wondermutt.net [192.168.1.2]) by wondermutt.net (8.9.3/8.9.3) with ESMTP id TAA67817; Wed, 23 Aug 2000 19:58:51 -0400 (EDT) (envelope-from papalia@udel.edu) Message-Id: <4.3.1.2.20000823195101.00abc910@mail.udel.edu> X-Sender: papalia@mail.udel.edu X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Wed, 23 Aug 2000 19:52:46 -0400 To: Chris Byrnes , Simon From: John Subject: Re: WTF Cc: "questions@FreeBSD.ORG" , "stable@FreeBSD.ORG" In-Reply-To: References: <200008240030.SAA62332@mail.fpsn.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 Anything showing up in your message log? (/var/log/messages). That could be helpful too. For right now though, you're really not giving very much info, other than info that pretty much boils down to that you "changed everything and now nothing works". --john >SWAP usage has been high lately. It happened RIGHT after I upgraded the >system to a new CPU, board, and RAM, and to 3.50STABLE. I >thought maybe there was a OS issue with my SUP or something (I >was hoping). That's when it started >happening. God, I dont have TIME to weed thru trying new boards and new >CPUs. > >I wish there was a quick fix. > > > it can be anything! and i mean anything! bad RAM, bad harddrive, bad > CPU, etc... and i know EXACTLY how it feels > > when shit like this happens. Unfortunately, it's not always easy to > determine the cause. Are you using %100 certified > > RAM for your motherboard? just because it's new doesn't mean jack. I > had servers go wild with brand new out of the box > > RAM and harddrives. You said it only started recently, try to remember > after what? some change you made? more load? > > do you have logs enabled? anything in there? do you monitor this > machine? what's the load average like? swap usage, > > etc... what is it doing most of the time? > > > > -Simon > > > > On Wed, 23 Aug 2000 18:33:21 -0500 (CDT), Chris Byrnes wrote: > > > > >I'm running 3.5-STABLE. > > > > > >Recently, my server has started rebooting, at random times, usually > > >actually quite religiously about every 2 days. > > > > > >I thought it might be a RAM problem. Replaced with brand new RAM. > > >Same problem. > > > > > >Any ideas, at all? Pllllllllllllease. > > > > > >Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 17: 1:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from awww.jeah.net (awww.jeah.net [216.111.239.130]) by hub.freebsd.org (Postfix) with ESMTP id 4E5E037B623; Wed, 23 Aug 2000 17:01:44 -0700 (PDT) Received: from localhost (chris@localhost) by awww.jeah.net (8.9.3/8.9.3) with ESMTP id TAA20147; Wed, 23 Aug 2000 19:02:21 -0500 (CDT) (envelope-from chris@jeah.net) Date: Wed, 23 Aug 2000 19:02:20 -0500 (CDT) From: Chris Byrnes To: John Cc: Simon , "questions@FreeBSD.ORG" , "stable@FreeBSD.ORG" Subject: Re: WTF In-Reply-To: <4.3.1.2.20000823195101.00abc910@mail.udel.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 Nothing in the log. I changed the CPU from an AMD K6 300 to an AMD K6-2 500.. Are there any known issues with that processor type/speed? ------------------------------------------------- Chris Byrnes, Owner NSI NIC HANDLE CB5820 Jeah Communications http://www.jeah.net ------------------------------------------------- On Wed, 23 Aug 2000, John wrote: > Anything showing up in your message log? (/var/log/messages). That could > be helpful too. For right now though, you're really not giving very much > info, other than info that pretty much boils down to that you "changed > everything and now nothing works". > > --john > > >SWAP usage has been high lately. It happened RIGHT after I upgraded the > >system to a new CPU, board, and RAM, and to 3.50STABLE. I > >thought maybe there was a OS issue with my SUP or something (I > >was hoping). That's when it started > >happening. God, I dont have TIME to weed thru trying new boards and new > >CPUs. > > > >I wish there was a quick fix. > > > > > it can be anything! and i mean anything! bad RAM, bad harddrive, bad > > CPU, etc... and i know EXACTLY how it feels > > > when shit like this happens. Unfortunately, it's not always easy to > > determine the cause. Are you using %100 certified > > > RAM for your motherboard? just because it's new doesn't mean jack. I > > had servers go wild with brand new out of the box > > > RAM and harddrives. You said it only started recently, try to remember > > after what? some change you made? more load? > > > do you have logs enabled? anything in there? do you monitor this > > machine? what's the load average like? swap usage, > > > etc... what is it doing most of the time? > > > > > > -Simon > > > > > > On Wed, 23 Aug 2000 18:33:21 -0500 (CDT), Chris Byrnes wrote: > > > > > > >I'm running 3.5-STABLE. > > > > > > > >Recently, my server has started rebooting, at random times, usually > > > >actually quite religiously about every 2 days. > > > > > > > >I thought it might be a RAM problem. Replaced with brand new RAM. > > > >Same problem. > > > > > > > >Any ideas, at all? Pllllllllllllease. > > > > > > > >Chris > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 17: 2:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from adsl-151-197-201-17.bellatlantic.net (adsl-151-197-201-17.bellatlantic.net [151.197.201.17]) by hub.freebsd.org (Postfix) with ESMTP id 588C837B650; Wed, 23 Aug 2000 17:02:14 -0700 (PDT) Received: from localhost (root@localhost) by adsl-151-197-201-17.bellatlantic.net (8.9.3/8.9.3) with ESMTP id UAA00283; Wed, 23 Aug 2000 20:02:11 -0400 (EDT) (envelope-from bleez@bellatlantic.net) Date: Wed, 23 Aug 2000 20:02:11 -0400 (EDT) From: Bryan Liesner X-Sender: root@adsl-151-197-201-17.bellatlantic.net To: Vivek Khera Cc: stable@freebsd.org, sos@freebsd.org Subject: Re: ATAPI CD-ROM fails to mount on 4.1-STABLE In-Reply-To: <14756.8729.629364.19998@onceler.kciLink.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 Wed, 23 Aug 2000, Vivek Khera wrote: >I updated my 4.1-STABLE yesterday. Today I tried to read a CD-ROM >(the FreeBSD 4.1-R install CD, and also one generic data CD I made a >while back that was ok on this system before) and the mount never >completes. > >Here's what happens. > >I insert the CD and type "mount /cdrom". The mount command returns. >The /var/log/messages syslog contains this entry: > > /kernel: cd9660: RockRidge Extension > >I do an "ls /cdrom" and I get either > > -r-xr-xr-x 1 root wheel 0 Dec 31 1969 /cdrom* I just did a make world/make kernel last night and I'm experiencing exactly the same problem. My cdrom dir after the mount looks like this: -r-xr-xr-x 1 root wheel 0 Dec 31 1969 /cdrom* Look at the date! (My system date IS correct) mount shows: /dev/acd1c on /cdrom (cd9660, local, read-only, reads: sync 3 async 0) The system log has this entry: Aug 23 19:48:32 gravy /kernel: cd9660: RockRidge Extension Aug 23 19:48:35 gravy /kernel: RRIP without PX field? ========================================================== = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = bleez@bellatlantic.net Home of the Gipper = ========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 17:14: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 603DC37B628; Wed, 23 Aug 2000 17:14:23 -0700 (PDT) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id RAA38249; Wed, 23 Aug 2000 17:13:54 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200008240013.RAA38249@gndrsh.dnsmgr.net> Subject: Re: WTF In-Reply-To: from Chris Byrnes at "Aug 23, 2000 07:02:20 pm" To: chris@jeah.net (Chris Byrnes) Date: Wed, 23 Aug 2000 17:13:54 -0700 (PDT) Cc: papalia@udel.edu (John), simon@optinet.com (Simon), questions@FreeBSD.ORG (questions@FreeBSD.ORG), stable@FreeBSD.ORG (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 > Nothing in the log. > > I changed the CPU from an AMD K6 300 to an AMD K6-2 500.. Are there any > known issues with that processor type/speed? K6-2 500's are very picky about cooling and power supply capacity. Did you use thermal grease and do you have an oversize heatsink with at least a 50 or 60mm fan on it? Have you tripple checked the CPU voltage setting? Did you happen to change from running a 66Mhz to 100MHz FSB when you went from the 300 to the 500? > ------------------------------------------------- > Chris Byrnes, Owner NSI NIC HANDLE CB5820 > Jeah Communications http://www.jeah.net > ------------------------------------------------- > > On Wed, 23 Aug 2000, John wrote: > > > Anything showing up in your message log? (/var/log/messages). That could > > be helpful too. For right now though, you're really not giving very much > > info, other than info that pretty much boils down to that you "changed > > everything and now nothing works". > > > > --john > > > > >SWAP usage has been high lately. It happened RIGHT after I upgraded the > > >system to a new CPU, board, and RAM, and to 3.50STABLE. I > > >thought maybe there was a OS issue with my SUP or something (I > > >was hoping). That's when it started > > >happening. God, I dont have TIME to weed thru trying new boards and new > > >CPUs. > > > > > >I wish there was a quick fix. > > > > > > > it can be anything! and i mean anything! bad RAM, bad harddrive, bad > > > CPU, etc... and i know EXACTLY how it feels > > > > when shit like this happens. Unfortunately, it's not always easy to > > > determine the cause. Are you using %100 certified > > > > RAM for your motherboard? just because it's new doesn't mean jack. I > > > had servers go wild with brand new out of the box > > > > RAM and harddrives. You said it only started recently, try to remember > > > after what? some change you made? more load? > > > > do you have logs enabled? anything in there? do you monitor this > > > machine? what's the load average like? swap usage, > > > > etc... what is it doing most of the time? > > > > > > > > -Simon > > > > > > > > On Wed, 23 Aug 2000 18:33:21 -0500 (CDT), Chris Byrnes wrote: > > > > > > > > >I'm running 3.5-STABLE. > > > > > > > > > >Recently, my server has started rebooting, at random times, usually > > > > >actually quite religiously about every 2 days. > > > > > > > > > >I thought it might be a RAM problem. Replaced with brand new RAM. > > > > >Same problem. > > > > > > > > > >Any ideas, at all? Pllllllllllllease. > > > > > > > > > >Chris > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 17:25: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id 1602A37B62F; Wed, 23 Aug 2000 17:24:59 -0700 (PDT) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id e7O0OhU04218; Wed, 23 Aug 2000 17:24:43 -0700 (PDT) Message-Id: <200008240024.e7O0OhU04218@ptavv.es.net> To: Chris Byrnes Cc: John , Simon , "questions@FreeBSD.ORG" , "stable@FreeBSD.ORG" Subject: Re: WTF In-reply-to: Your message of "Wed, 23 Aug 2000 19:02:20 CDT." Date: Wed, 23 Aug 2000 17:24:43 -0700 From: "Kevin Oberman" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Wed, 23 Aug 2000 19:02:20 -0500 (CDT) > From: Chris Byrnes > Sender: owner-freebsd-stable@FreeBSD.ORG > > Nothing in the log. > > I changed the CPU from an AMD K6 300 to an AMD K6-2 500.. Are there any > known issues with that processor type/speed? Thermal! My K6 ran well for the most part, but a buildworld would raise the temperature by 20 degrees (C) and then I would either an 11 or a 4. I popped the heat sink/fan and added a THIN layer of heat sink grease (available at most any electronics outlet inc. Radio Shack), replaced it, and buildworld ran fine. CPU temp went up, but never exceeded 48 degrees (C). Try running healthd (available in ports). Use "healthd -d" to continuously print out the temps of things, if you mobo supports it. (My ASUS P5A does.) It was certainly enlightening to see what was happening! R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 17:40:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cyrano.slash.netdot.net (PIMPDADDY.MIT.EDU [18.228.0.157]) by hub.freebsd.org (Postfix) with ESMTP id 1AF4837B424 for ; Wed, 23 Aug 2000 17:40:43 -0700 (PDT) Received: (from chaley@localhost) by cyrano.slash.netdot.net (8.9.3/8.9.3) id TAA40787 for stable@freebsd.org; Wed, 23 Aug 2000 19:56:24 -0400 (EDT) (envelope-from chaley) Date: Wed, 23 Aug 2000 19:56:23 -0400 From: Caleb Haley To: stable@freebsd.org Subject: Re: WTF Message-ID: <20000823195623.B40029@netdot.net> References: <200008232333.SAA15508@awww.jeah.net> <200008240030.SAA62332@mail.fpsn.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200008240030.SAA62332@mail.fpsn.net>; from simon@optinet.com on Wed, Aug 23, 2000 at 07:44:16PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 23 Aug 2000 18:33:21 -0500 (CDT), Chris Byrnes wrote: > > >I'm running 3.5-STABLE. > > > >Recently, my server has started rebooting, at random times, usually > >actually quite religiously about every 2 days. > > > >I thought it might be a RAM problem. Replaced with brand new RAM. > >Same problem. > > > >Any ideas, at all? Pllllllllllllease. man...the same thing was happening to me a few months ago, so i went to the store to buy new ram, but all they carried were 256meg dimms, which was definitely more than i needed. i bought it anyway. it didn't do the trick. i came to discover that the reboots were happening because my power supply was cutting out due to the copious pile of cathair on the power supply intake vent. either cheap pc power supplies or cats should be more tolerant to overheating. -- caleb haley To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 17:46:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from home.offwhite.net (home.offwhite.net [156.46.35.30]) by hub.freebsd.org (Postfix) with ESMTP id 2261137B424; Wed, 23 Aug 2000 17:46:31 -0700 (PDT) Received: from localhost (brennan@localhost) by home.offwhite.net (8.9.1/8.9.3) with ESMTP id TAA02039; Wed, 23 Aug 2000 19:46:28 -0500 (CDT) Date: Wed, 23 Aug 2000 19:46:28 -0500 (CDT) From: BWS - Offwhite To: Simon Cc: "chris@awww.jeah.net" , "questions@FreeBSD.ORG" , "stable@FreeBSD.ORG" Subject: Re: WTF In-Reply-To: <200008240030.SAA62332@mail.fpsn.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 had problems with a machine rebooting randomly, but regularly a while back. It was a fileserver which has slower IDE drives. The system disk was fighting to access virtual memory while the fileserver had 3 people writing to disk at the same time with very large files. It was fine if only one person saved a file at a time, but that cannot be expected with a fileserver. We solved it by making that server my new workstation and replacing it with a system with fast 3 SCSI drives. Then it worked fine. I noticed a mention in the /var/log/messages about a kernel panic. You may find the same. Brennan Stehling - web developer and sys admin projects: www.greasydaemon.com | www.onmilwaukee.com | www.sncalumni.com On Wed, 23 Aug 2000, Simon wrote: > it can be anything! and i mean anything! bad RAM, bad harddrive, bad CPU, etc... and i know EXACTLY how it feels > when shit like this happens. Unfortunately, it's not always easy to determine the cause. Are you using %100 certified > RAM for your motherboard? just because it's new doesn't mean jack. I had servers go wild with brand new out of the box > RAM and harddrives. You said it only started recently, try to remember after what? some change you made? more load? > do you have logs enabled? anything in there? do you monitor this machine? what's the load average like? swap usage, > etc... what is it doing most of the time? > > -Simon > > On Wed, 23 Aug 2000 18:33:21 -0500 (CDT), Chris Byrnes wrote: > > >I'm running 3.5-STABLE. > > > >Recently, my server has started rebooting, at random times, usually > >actually quite religiously about every 2 days. > > > >I thought it might be a RAM problem. Replaced with brand new RAM. > >Same problem. > > > >Any ideas, at all? Pllllllllllllease. > > > >Chris > > > > > >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-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 Wed Aug 23 17:46:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from front001.cluster1.charter.net (24-216-159-200.hsacorp.net [24.216.159.200]) by hub.freebsd.org (Postfix) with ESMTP id DBDBB37B43E; Wed, 23 Aug 2000 17:46:35 -0700 (PDT) Received: from [24.217.6.45] (HELO dave.uhring.com) by front001.cluster1.charter.net (CommuniGate Pro SMTP 3.2.4) with ESMTP id 16600155; Wed, 23 Aug 2000 20:46:34 -0400 Date: Wed, 23 Aug 2000 19:46:34 -0500 (CDT) From: Dave Uhring X-Sender: duhring@dave.uhring.com To: Chris Byrnes Cc: John , Simon , "questions@FreeBSD.ORG" , "stable@FreeBSD.ORG" Subject: Re: WTF 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 K6 300 has 66 MHz FSB, K6-2/500 has 100 MHz FSB. Are you using PC-100 SDRAM? If not, does your MB support using a 100 MHz FSB CPU with 66 MHz RAM? Did you make sure that your MB configuration settings match your hardware? Dave On Wed, 23 Aug 2000, Chris Byrnes wrote: > Nothing in the log. > > I changed the CPU from an AMD K6 300 to an AMD K6-2 500.. Are there any > known issues with that processor type/speed? > > ------------------------------------------------- > Chris Byrnes, Owner NSI NIC HANDLE CB5820 > Jeah Communications http://www.jeah.net > ------------------------------------------------- > > On Wed, 23 Aug 2000, John wrote: > > > Anything showing up in your message log? (/var/log/messages). That could > > be helpful too. For right now though, you're really not giving very much > > info, other than info that pretty much boils down to that you "changed > > everything and now nothing works". > > > > --john > > > > >SWAP usage has been high lately. It happened RIGHT after I upgraded the > > >system to a new CPU, board, and RAM, and to 3.50STABLE. I > > >thought maybe there was a OS issue with my SUP or something (I > > >was hoping). That's when it started > > >happening. God, I dont have TIME to weed thru trying new boards and new > > >CPUs. > > > > > >I wish there was a quick fix. > > > > > > > it can be anything! and i mean anything! bad RAM, bad harddrive, bad > > > CPU, etc... and i know EXACTLY how it feels > > > > when shit like this happens. Unfortunately, it's not always easy to > > > determine the cause. Are you using %100 certified > > > > RAM for your motherboard? just because it's new doesn't mean jack. I > > > had servers go wild with brand new out of the box > > > > RAM and harddrives. You said it only started recently, try to remember > > > after what? some change you made? more load? > > > > do you have logs enabled? anything in there? do you monitor this > > > machine? what's the load average like? swap usage, > > > > etc... what is it doing most of the time? > > > > > > > > -Simon > > > > > > > > On Wed, 23 Aug 2000 18:33:21 -0500 (CDT), Chris Byrnes wrote: > > > > > > > > >I'm running 3.5-STABLE. > > > > > > > > > >Recently, my server has started rebooting, at random times, usually > > > > >actually quite religiously about every 2 days. > > > > > > > > > >I thought it might be a RAM problem. Replaced with brand new RAM. > > > > >Same problem. > > > > > > > > > >Any ideas, at all? Pllllllllllllease. > > > > > > > > > >Chris > > > > > > > > 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 Aug 23 19: 4: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pop.hccnet.nl (pop.hccnet.nl [193.172.127.94]) by hub.freebsd.org (Postfix) with ESMTP id E76BE37B42C for ; Wed, 23 Aug 2000 19:03:57 -0700 (PDT) Received: from parmenides.utp.net by pop.hccnet.nl via uds8-115.dial.hccnet.nl [193.173.115.8] with ESMTP id EAA00713 (8.8.5/1.13); Thu, 24 Aug 2000 04:03:41 +0200 (MET DST) Received: from localhost (janko@localhost) by parmenides.utp.net (8.9.3/8.9.3) with ESMTP id TAA01327; Wed, 23 Aug 2000 19:08:08 GMT (envelope-from janko@parmenides.utp.net) Date: Wed, 23 Aug 2000 19:08:07 +0000 (GMT) From: Janko van Roosmalen To: Robert Augustine Cc: stable@FreeBSD.ORG Subject: Re: Random Reboots In-Reply-To: <003801c00d2a$03c7ff00$0200000a@cm.420.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 Check your powersupply. If it is 250 Watt throw it out and get at least a 300 Watt. We import and export computer cases by container and sell a lot of separate 300 Watt PSU's to customers for ATHLON users. 250 Watt is just not enough for this cpu. The Amd website www1.amd.com/athlon/power has a list of recommended power supplies. If you also run Windows on this machine you could check the FIC website and if it has a VIA chipset the VIA website (www.viatech.com/drivers/index.htm) for new drivers. Is the cooling OK? May-be inserting an extra wait state for the memory in your BIOS might help Janko On Wed, 23 Aug 2000, Robert Augustine wrote: > > Hello, > Im running a 4.1-STABLE machine which is very recently cvs'uped. The > hardware is an Athlon running on a FIC motherboard. I am receiving random > reboots every like 3 days or so. Sometimes sooner sometimes later. Has To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 19:32:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wysoft.tzo.com (c481444-a.bremtn1.wa.home.com [24.12.235.202]) by hub.freebsd.org (Postfix) with ESMTP id DC6D437B424 for ; Wed, 23 Aug 2000 19:32:34 -0700 (PDT) Received: from localhost (wysoft@localhost) by wysoft.tzo.com (8.9.3/8.9.3) with ESMTP id TAA16574; Wed, 23 Aug 2000 19:31:26 -0700 (PDT) (envelope-from wysoft@wysoft.tzo.com) Date: Wed, 23 Aug 2000 19:31:26 -0700 (PDT) From: Jeff Wyman To: Janko van Roosmalen Cc: Robert Augustine , stable@FreeBSD.ORG Subject: Re: Random Reboots 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 Wed, 23 Aug 2000, Janko van Roosmalen wrote: > Check your powersupply. > > If it is 250 Watt throw it out and get at least a 300 Watt. We import > and export computer cases by container and sell a lot of separate 300 > Watt PSU's to customers for ATHLON users. 250 Watt is just not enough for > this cpu. If this is an FIC SD-11 board, it should be known that this board is a very picky one when it comes to voltages - FIC released this board in a hurry when it was still a prototype, leaving many things in error on this board. One thing was the voltage regulators. There are very few on this board compared to other Athlon boards (including other FIC models) and this can make for rather dirty voltages being supplied to your CPU when combined with a culprit PS. However, 2 days is kind of a long time for these problems to arise. There's just too much crap that happens these days to rule it out though. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 20:16:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lamborghini.indocyber.com (lamborghini.indocyber.com [202.180.0.86]) by hub.freebsd.org (Postfix) with SMTP id 887AA37B424 for ; Wed, 23 Aug 2000 20:16:31 -0700 (PDT) Received: (qmail 5674 invoked from network); 24 Aug 2000 03:15:38 -0000 Received: from unknown (HELO maverick.indocyber.com) (202.155.43.94) by lamborghini.indocyber.com with SMTP; 24 Aug 2000 03:15:38 -0000 Received: (qmail 1547 invoked by uid 1000); 24 Aug 2000 03:15:44 -0000 Date: Thu, 24 Aug 2000 10:15:44 +0700 From: John Indra To: freebsd-stable@freebsd.org Subject: Is the ata driver buggy? [was Re: 4.1-STABLE panics on boot with Huyundai Laptop (P233)] Message-ID: <20000824101544.B722@indocyber.com> Mail-Followup-To: freebsd-stable@freebsd.org References: <20000823131811.A4418@titan.klemm.gtn.com> <20000823204217.A70368@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20000823204217.A70368@titan.klemm.gtn.com>; from andreas@klemm.gtn.com on Wed, Aug 23, 2000 at 08:42:17PM +0200 X-Mailer: Mutt 1.2.5i on FreeBSD 4.1-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 23, 2000 at 08:42:17PM +0200, Andreas Klemm wrote: |It turns out, that with the (new) ata driver the machine panics |and with the old (obsoleted) wd driver the Laptopmachine boots |flawlessly. Aha... here's what I found reasonable enough for the cause of lock-ups I've been having... I'm not expert enough to prove my statement, but I have a strong hunch that the ata driver is the prime suspect causing the lock-ups. When I found my machine lock-up, the harddrive LED light on all the time, and the harddrive is in condition of spinning... Never have an uptime of more than 2 days since upgrading to RELENG_4. Sigh... Like what I've describe before in my other message, the same machine that lock-up never had any unintentional reboots when running FreeBSD 3.4-RELEASE before... Regards, John Indra To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 20:40:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lamborghini.indocyber.com (lamborghini.indocyber.com [202.180.0.86]) by hub.freebsd.org (Postfix) with SMTP id 18DD037B42C for ; Wed, 23 Aug 2000 20:40:25 -0700 (PDT) Received: (qmail 6831 invoked from network); 24 Aug 2000 03:39:41 -0000 Received: from unknown (HELO maverick.indocyber.com) (202.155.43.94) by lamborghini.indocyber.com with SMTP; 24 Aug 2000 03:39:41 -0000 Received: (qmail 1769 invoked by uid 1000); 24 Aug 2000 03:39:47 -0000 Date: Thu, 24 Aug 2000 10:39:47 +0700 From: John Indra To: stable@freebsd.org Subject: Re: Random Reboots Message-ID: <20000824103947.C722@indocyber.com> References: <003801c00d2a$03c7ff00$0200000a@cm.420.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <003801c00d2a$03c7ff00$0200000a@cm.420.net>; from raugustine@reflectively.net on Wed, Aug 23, 2000 at 01:46:04PM -0400 X-Mailer: Mutt 1.2.5i on FreeBSD 4.1-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 23, 2000 at 01:46:04PM -0400, Robert Augustine wrote: | Im running a 4.1-STABLE machine which is very recently cvs'uped. The |hardware is an Athlon running on a FIC motherboard. I am receiving random |reboots every like 3 days or so. Sometimes sooner sometimes later. Has |anyone ever experienced these problems or know what could be the reason for |this happening? Aha... found another friend ;) I suspect that there is possibly a bug in the ata driver. Perhaps the differences between what happened to you and I was that my machine didn't reboot, it lock-up! When it lock-up the harddrive LED is on and spinning. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 21:23:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from drugs.dv.isc.org (drugs.dv.isc.org [130.155.191.236]) by hub.freebsd.org (Postfix) with ESMTP id 705FA37B424 for ; Wed, 23 Aug 2000 21:23:10 -0700 (PDT) Received: from nominum.com (localhost.dv.isc.org [127.0.0.1]) by drugs.dv.isc.org (8.9.3/8.9.3) with ESMTP id OAA00404 for ; Thu, 24 Aug 2000 14:25:38 +1000 (EST) (envelope-from marka@nominum.com) Message-Id: <200008240425.OAA00404@drugs.dv.isc.org> To: stable@freebsd.org From: Mark.Andrews@nominum.com Subject: HEADSUP: 4.1S installworld broken Date: Thu, 24 Aug 2000 14:25:38 +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG STRICTTMPPATH does not contain cp/ ===> gnu/usr.bin/binutils/doc cp -p /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/install.sh install cp:No such file or directory *** Error code 1 -- Mark Andrews, Nominum Inc. 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews@nominum.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 21:25:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sanson.reyes.somos.net (freyes.static.inch.com [216.223.199.224]) by hub.freebsd.org (Postfix) with ESMTP id C262A37B42C for ; Wed, 23 Aug 2000 21:25:17 -0700 (PDT) Received: from tomasa (tomasa.reyes.somos.net [10.0.0.11]) by sanson.reyes.somos.net (8.9.3/8.9.3) with SMTP id AAA31460; Thu, 24 Aug 2000 00:16:37 -0400 (EDT) (envelope-from fran@reyes.somos.net) Message-Id: <200008240416.AAA31460@sanson.reyes.somos.net> From: "Francisco Reyes" To: "David Wolfskill" Cc: "FreeBSD Stable List" Date: Thu, 24 Aug 2000 00:26:05 -0400 Reply-To: "Francisco Reyes" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 98 (4.10.2222) In-Reply-To: <200008230333.UAA33431@pau-amma.whistle.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: remove empty TEMPROOT dirs at mergemaster's end? Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 22 Aug 2000 20:33:11 -0700 (PDT), David Wolfskill wrote: >>Changing mergemaster to indicate files to be either ignored or >>copied. Kind of an exception file. > >In general, i think this is a good idea.... See the mail from Doug Barton with subject "mergemaster wishlist". He expresses some concerns with the idea. >But wouldn't you want the (possibly new/changed) "weekly" locate script >moved to daily? (How would you be informed of changes to it -- or would >you just want to automatically move it?) In an ideal world it would be nice if mergemaster supported mapping files from one place to another. Doug did mention one way to do it.. keep the cvs tag in weekly this way I know when the file changes. >Even in this case, though I don't change these files, I'd like to see >the modifications that come about as a result of an upgrade -- That is your choice and nobody is trying to take it away from you. :-) Having an exclude file allows those of us who don't want to look at the upgrades have a happier life. francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 21:36:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sanson.reyes.somos.net (freyes.static.inch.com [216.223.199.224]) by hub.freebsd.org (Postfix) with ESMTP id 01FEF37B42C for ; Wed, 23 Aug 2000 21:36:40 -0700 (PDT) Received: from tomasa (tomasa.reyes.somos.net [10.0.0.11]) by sanson.reyes.somos.net (8.9.3/8.9.3) with SMTP id AAA31509; Thu, 24 Aug 2000 00:28:05 -0400 (EDT) (envelope-from fran@reyes.somos.net) Message-Id: <200008240428.AAA31509@sanson.reyes.somos.net> From: "Francisco Reyes" To: "Doug Barton" Cc: "FreeBSD Stable List" Date: Thu, 24 Aug 2000 00:37:33 -0400 Reply-To: "Francisco Reyes" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 98 (4.10.2222) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: mergemaster wishlist Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 23 Aug 2000 12:07:29 -0700 (PDT), Doug Barton wrote: >> Changing mergemaster to indicate files to be either ignored or >> copied. Kind of an exception file. >It's not terribly difficult, it's just expensive computationally I gave this a little thought.. There is one way to go about it that will bypass comparisons altogheter. Instead of comparing each file against the exeption list one could process the exception list upfront. Files to be merged automatically will be copied.. files to be ignored would be deleted. What do you think of this approach? >There are better ways to handle that. For example, you could leave >an empty file with the same CVS Id in the "real" location. Then you won't >be bothered by mm telling you that it's missing, AND you have the added >benefit of knowing when it needs to be updated. You still have the inconvenience of having to move the file if there are changes. >But if there are changes you SHOULD look to see what the changes >are. There are lots of things one "should" that one doesn't. I believe programs should help people, not dictate their behavior. If someone can't sleep at night because they merged /etc/defaults without looking at it then they "SHOULD look to see what the changes".. for the rest of us.. it is good enough to just get the latest and greatest defaults. I am working on an addition to mm that will show you how your >rc.conf[.local] and make.conf file variables differ from those in >/etc/defaults, but even that isn't foolproof. And you talked about overhead. :-) rc.conf is small enough that people can just look at it why even bother parsing the entire default file to compare it against the /etc/rc.conf? This is just as subjective a "feature" as it is having the exclusion list. You also mentioned that the exclusion list "violates your design goals". What were those design goals? >All that said, this is a frequent request (every couple months it >pops up) so I am working on a way to do it which will satisfy the >requestors and me both. I think processing the exclusion file upfront may be a good solution that may make everyone happy. francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 21:37:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id D475D37B424 for ; Wed, 23 Aug 2000 21:37:16 -0700 (PDT) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id 40D4FA8AA; Thu, 24 Aug 2000 14:37:15 +1000 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id 3DBE9544F for ; Thu, 24 Aug 2000 14:37:15 +1000 (EST) Date: Thu, 24 Aug 2000 14:37:15 +1000 (EST) From: andrew@ugh.net.au To: freebsd-stable@freebsd.org Subject: installworld error - getrpcent Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I just installed world, cvsuped yesterday. Everything went OK except at the end of installworld: gzcat: /usr/share/man/man3/getrpcent.3.gz: not in gzip format everything else seems fine (although I cant read the getrpcent man page :-) Thanks, Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 21:49:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sanson.reyes.somos.net (freyes.static.inch.com [216.223.199.224]) by hub.freebsd.org (Postfix) with ESMTP id 2F93437B422 for ; Wed, 23 Aug 2000 21:49:31 -0700 (PDT) Received: from tomasa (tomasa.reyes.somos.net [10.0.0.11]) by sanson.reyes.somos.net (8.9.3/8.9.3) with SMTP id AAA31557; Thu, 24 Aug 2000 00:40:30 -0400 (EDT) (envelope-from fran@reyes.somos.net) Message-Id: <200008240440.AAA31557@sanson.reyes.somos.net> From: "Francisco Reyes" To: "Brandon D. Valentine" , "Peter Jeremy" Cc: "Brian Somers" , "Doug Barton" , "FreeBSD stable" , "Gerhard Sittig" , "Jason T" Date: Thu, 24 Aug 2000 00:49:55 -0400 Reply-To: "Francisco Reyes" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 98 (4.10.2222) In-Reply-To: <00Aug23.140643est.115225@border.alcanet.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: remove empty TEMPROOT dirs at mergemaster's end? (was: cvs commit:src/usr.sbin/mergemaster mergemaster.sh) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 23 Aug 2000 14:06:40 +1000, Peter Jeremy wrote: >As an example, rc.conf was recently changed (in -current) to not >start inetd, portmap or sendmail. If you are actually relying on >any of these daemons, and you actually notice the differences in >/etc/defaults/rc.conf, you will be able to update /etc/rc.conf >without a period of head-scratching when they don't start. I think that is a different problem alltogether. Whoever made that choice should warn the heck out of the rest of us, or even better stop and think real hard why is this been done. Perhaps it is security or some other "good" reason, but it is the equivalent of "breaking" things. For a computer or two it is not a big deal, but for a small shop which still has not figure out a way to automate distribution of updates this is a pain. francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 21:56:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sanson.reyes.somos.net (freyes.static.inch.com [216.223.199.224]) by hub.freebsd.org (Postfix) with ESMTP id 4408437B42C for ; Wed, 23 Aug 2000 21:56:40 -0700 (PDT) Received: from tomasa (tomasa.reyes.somos.net [10.0.0.11]) by sanson.reyes.somos.net (8.9.3/8.9.3) with SMTP id AAA31575; Thu, 24 Aug 2000 00:48:07 -0400 (EDT) (envelope-from fran@reyes.somos.net) Message-Id: <200008240448.AAA31575@sanson.reyes.somos.net> From: "Francisco Reyes" To: "Doug Barton" Cc: "FreeBSD Stable List" Date: Thu, 24 Aug 2000 00:57:31 -0400 Reply-To: "Francisco Reyes" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 98 (4.10.2222) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Mergemaster exception list Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 23 Aug 2000 12:17:43 -0700 (PDT), Doug Barton wrote: >Or worse, complete inability to reach the box in the case of a >remote upgrade. This is just about the best example I've seen in recent >days of why I feel justified in "enforcing" the policy of making the >administrator LOOK at the changes before installing. I understand your point, but this still doesn't change that this is "your" view of how things should be done. Each person/machine/situation has it's own set of needs. some people do remote upgrades... many others never will. For the majority of people who never even read the man pages for a particular software they will get the default behavior. For the rest of us an exception list is what we woud like. I am thinking I am going to do a "pre mergemaster" script. It would read a file in the form: D /some file C /some other file M /original /copy to D = delete from TEMPROOT location C = copy from TEMPROOT to production location M = move the file from TEMPROOT to arbitrary location. francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 22: 3: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sanson.reyes.somos.net (freyes.static.inch.com [216.223.199.224]) by hub.freebsd.org (Postfix) with ESMTP id 475BD37B423 for ; Wed, 23 Aug 2000 22:02:57 -0700 (PDT) Received: from tomasa (tomasa.reyes.somos.net [10.0.0.11]) by sanson.reyes.somos.net (8.9.3/8.9.3) with SMTP id AAA31598 for ; Thu, 24 Aug 2000 00:54:26 -0400 (EDT) (envelope-from fran@reyes.somos.net) Message-Id: <200008240454.AAA31598@sanson.reyes.somos.net> From: "Francisco Reyes" To: "FreeBSD Stable List" Date: Thu, 24 Aug 2000 01:03:50 -0400 Reply-To: "Francisco Reyes" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 98 (4.10.2222) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Upcoming rc.conf changes not loading certain currently loaded daemons Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On a recent email Peter Jeremy wrote: >..., rc.conf was recently changed (in -current) to not >start inetd, portmap or sendmail. If you are actually relying on >any of these daemons, and you actually notice the differences in >/etc/defaults/rc.conf, you will be able to update /etc/rc.conf >without a period of head-scratching when they don't start. What was the reason for these daemons been set to not start? Wouldn't this "break" working machines? francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 22:15:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from server.raadinfo.net (smtp2.uwnet.nl [195.7.130.55]) by hub.freebsd.org (Postfix) with ESMTP id A00BD37B422 for ; Wed, 23 Aug 2000 22:15:07 -0700 (PDT) Received: from port142.isd.to (port142.isd.to [195.7.129.142]) by server.raadinfo.net (8.9.3/8.9.3) with ESMTP id HAA08466 for ; Thu, 24 Aug 2000 07:12:20 +0200 Received: (qmail 721 invoked by uid 1000); 24 Aug 2000 05:16:59 -0000 From: "Andre Goeree" Date: Thu, 24 Aug 2000 07:16:59 +0200 To: Robert Gray Cc: freebsd-stable@freebsd.org Subject: Re: /etc/defaults/rc.conf 4.1-STABLE-200-08-18 (solved) Message-ID: <20000824071658.A701@freebee.attica.home> Reply-To: abgoeree@uwnet.nl References: <200008231405.IAA19222@calypso.boulderlabs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200008231405.IAA19222@calypso.boulderlabs.com>; from bob@cs.colorado.edu on Wed, Aug 23, 2000 at 08:05:47AM -0600 X-Sender: abgoeree@uwnet.nl Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 23, 2000 at 08:05:47AM -0600, Robert Gray wrote: > > I had a similar or the same problem. If this matches > your situation, please post this info to the group. > -bob > > -------------------- > From: Robert Gray > To: Bill Vermillion > Cc: markey@chcm.com > Subject: Problem solved: Re: rc.conf not loading > Date: Sat, 19 Aug 2000 08:03:38 -0600 > > > I found the problem. I had a slightly old rc.firewall and I > didn't notice the problem since all of my local firewall > differences were showing up. > > > Notice the small change in versions: > > diff rc.firewall.new rc.firewall > 3c3,4 > < # $FreeBSD: src/etc/rc.firewall,v 1.30.2.4 2000/05/28 19:17:15 asmodai Exp $ > --- > > # $FreeBSD: src/etc/rc.firewall,v 1.30 2000/02/06 19:24:37 paul Exp $ > > > 8d8 > < source_rc_confs > > It turns out rc.firewall re-reads /etc/defaults/rc.conf, but the > 1.30 version failed to re-read /etc/rc.conf. > > > P.S. To track it down, I moved /etc/rc to /etc/rc.real > and inserted this script in its place: > > #!/bin/sh > /sbin/mount / > /sbin/mount /usr > script /RC.script /etc/rc.real > > Then use "set -x" in the /etc/rc.real script to see what > is going on. > > -bob > Yes, it turned out to be rc.firewall My version is even older than yours..... Didn't notice the canges because i changed the name and location of the script.. If i run the updated version (src/etc/rc.firewall,v 1.30.2.5 2000/08/08) everything works fine :-). Problem solved, thanks. -- Ago abgoeree@uwnet.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 23 22:40:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.rdc1.sfba.home.com (mail1.rdc1.sfba.home.com [24.0.0.74]) by hub.freebsd.org (Postfix) with ESMTP id 2C16937B42C; Wed, 23 Aug 2000 22:40:04 -0700 (PDT) Received: from beastie.localdomain ([24.19.158.41]) by mail1.rdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000824054003.HDEQ14324.mail1.rdc1.sfba.home.com@beastie.localdomain>; Wed, 23 Aug 2000 22:40:03 -0700 Received: (from brian@localhost) by beastie.localdomain (8.9.3/8.8.7) id WAA43251; Wed, 23 Aug 2000 22:41:01 -0700 (PDT) (envelope-from brian) Date: Wed, 23 Aug 2000 22:41:01 -0700 From: "Brian O'Shea" To: Chris Byrnes Cc: Simon , "questions@FreeBSD.ORG" , "stable@FreeBSD.ORG" Subject: Re: WTF Message-ID: <20000823224101.S351@beastie.localdomain> Reply-To: boshea@ricochet.net Mail-Followup-To: Chris Byrnes , Simon , "questions@FreeBSD.ORG" , "stable@FreeBSD.ORG" References: <200008240030.SAA62332@mail.fpsn.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Chris Byrnes on Wed, Aug 23, 2000 at 06:46:27PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 23, 2000 at 06:46:27PM -0500, Chris Byrnes wrote: > SWAP usage has been high lately. It happened RIGHT after I upgraded the > system to a new CPU, board, and RAM, and to 3.50STABLE. I > thought maybe there was a OS issue with my SUP or something (I > was hoping). That's when it started happening. You have changed three variables, so it is difficult to determine which one (or which combination) might be responsible for your problem. However, here are some things that you might think about: How regularly does this happen? Is it always at the same time of day? Try to correlate the reboots with some other regular events. If possible, record all of the times when the reboots happen and plot them. Look at the data and try to see if they fit any other patterns. Even consider seemingly unrelated, external events such as spikes in the power usage in your building, or things that might cause temperature variations in the room where the machine is kept (such as sunlight coming in through a window, etc). > God, I dont have TIME to weed thru trying new boards and new > CPUs. > > I wish there was a quick fix. > A fix requires knowing what the problem is! -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 Wed Aug 23 23:51:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 0534137B423 for ; Wed, 23 Aug 2000 23:50:42 -0700 (PDT) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id NAA47085; Thu, 24 Aug 2000 13:49:26 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Thu, 24 Aug 2000 13:49:26 +0700 (NSS) From: Max Khon To: Vivek Khera Cc: stable@FreeBSD.ORG Subject: Re: missing c++rt0.o file, where to get? In-Reply-To: <14756.2022.695697.5862@onceler.kciLink.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 hi, there! On Wed, 23 Aug 2000, Vivek Khera wrote: > I'm attempting to build the plugger port, and it comes back with this > error: > > make plugger.so CC=gcc XCFLAGS='-fpic -aout' LD=gcc XLDFLAGS='-shared -aout' > gcc -shared -aout -o plugger.so plugger.o common.o > ld: c++rt0.o: No such file or directory > *** Error code 1 > > I'm guessing c++rt0.o is from the 2.x compatibility but I can't figure > out from where to get it. I have the 2.x compatibility libraries > installed. > > I'm running a freshly installed 4.1-R box upgraded to 4.1-STABLE. > > I see sources for /usr/src/lib/csu/i386/c++rt0.c but the Makefile in > there doesn't seem to build with "-aout" option, so it is unlikely to > be the right incantation. > > Any pointers from where to get this? as far as i remember the only place where you can get crt startup objects is 2.2.x-RELEASE distribution /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 0: 0:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 1559437B422 for ; Thu, 24 Aug 2000 00:00:17 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id AAA32173; Thu, 24 Aug 2000 00:00:07 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200008240700.AAA32173@pike.osd.bsdi.com> Subject: Re: HEADSUP: 4.1S installworld broken In-Reply-To: <200008240425.OAA00404@drugs.dv.isc.org> from "Mark.Andrews@nominum.com" at "Aug 24, 2000 02:25:38 pm" To: Mark.Andrews@nominum.com Date: Thu, 24 Aug 2000 00:00:07 -0700 (PDT) Cc: stable@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 Mark.Andrews@nominum.com wrote: > > STRICTTMPPATH does not contain cp/ > > ===> gnu/usr.bin/binutils/doc > cp -p /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/install.sh > install > cp:No such file or directory > *** Error code 1 Grrr, it worked here during my test build and install. :( You should just be able to add 'cp' to the list of files to copy in the 'installworld' target in src/Makefile.inc1. I'll try it again to see if I can reproduce the breakage. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 0:21: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from c014.sfo.cp.net (c014-h003.c014.sfo.cp.net [209.228.12.67]) by hub.freebsd.org (Postfix) with SMTP id 37DC037B423 for ; Thu, 24 Aug 2000 00:21:02 -0700 (PDT) Received: (cpmta 28819 invoked from network); 24 Aug 2000 00:21:01 -0700 Received: from d8c81e5f.dsl.flashcom.net (HELO quadrajet.flashcom.com) (216.200.30.95) by smtp.flashcom.net with SMTP; 24 Aug 2000 00:21:01 -0700 X-Sent: 24 Aug 2000 07:21:01 GMT Received: (from guy@localhost) by quadrajet.flashcom.com (8.9.3/8.9.3) id AAA26608; Thu, 24 Aug 2000 00:21:00 -0700 (PDT) (envelope-from gharris) Date: Thu, 24 Aug 2000 00:21:00 -0700 From: Guy Harris To: Tom Duffey Cc: stable@FreeBSD.ORG Subject: Re: Update magic file Message-ID: <20000824002100.G355@quadrajet.flashcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The "file" command is unable to properly identify EPS binary files. The > following patch, taken from the magic file included in the Slackware Linux > distribution, fixes the problem. Picking up the latest version of "file" from ftp://ftp.astron.com/pub/file/file-3.32.tar.gz (or a later version, if one comes out after my message arrives) will also fix the problem, and probably add other improvements as well. When last I picked up stuff from the FreeBSD "file" to merge into "file" as maintained by Christos Zoulas at Astron (he's now maintaining the "Ian Darwin" implementation of "file" that the BSDs and Linux distributions have picked up), it was a bit of a pain as, if I remember correctly, some files in the "Magdir" subdirectory of the source directory for "file" had different names in FreeBSD and in Christos' version. If anybody updates "file" in FreeBSD, they might want to try to minimize the differences between the file names, etc. (and send back to Christos any patches from FreeBSD). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 0:28:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from drugs.dv.isc.org (drugs.dv.isc.org [130.155.191.236]) by hub.freebsd.org (Postfix) with ESMTP id AE65B37B423 for ; Thu, 24 Aug 2000 00:28:04 -0700 (PDT) Received: from nominum.com (localhost.dv.isc.org [127.0.0.1]) by drugs.dv.isc.org (8.9.3/8.9.3) with ESMTP id RAA07747; Thu, 24 Aug 2000 17:29:43 +1000 (EST) (envelope-from marka@nominum.com) Message-Id: <200008240729.RAA07747@drugs.dv.isc.org> To: John Baldwin Cc: stable@FreeBSD.org From: Mark.Andrews@nominum.com Subject: Re: HEADSUP: 4.1S installworld broken In-reply-to: Your message of "Thu, 24 Aug 2000 00:00:07 MST." <200008240700.AAA32173@pike.osd.bsdi.com> Date: Thu, 24 Aug 2000 17:29:43 +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mark.Andrews@nominum.com wrote: > > > > STRICTTMPPATH does not contain cp/ > > > > ===> gnu/usr.bin/binutils/doc > > cp -p /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/instal > l.sh > > install > > cp:No such file or directory > > *** Error code 1 > > Grrr, it worked here during my test build and install. :( You should just > be able to add 'cp' to the list of files to copy in the 'installworld' > target in src/Makefile.inc1. I'll try it again to see if I can reproduce > the breakage. That should fix it. My full build environment is in pr=20815. I worked around the problem but felt a HEADSUP was warranted. Mark > > -- > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ -- Mark Andrews, Nominum Inc. 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews@nominum.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 1:11:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fingers.noc.uunet.co.za (fingers.noc.uunet.co.za [196.31.1.59]) by hub.freebsd.org (Postfix) with ESMTP id 6897537B423 for ; Thu, 24 Aug 2000 01:11:15 -0700 (PDT) Received: from robh (helo=localhost) by fingers.noc.uunet.co.za with local-smtp (Exim 3.13 #1) id 13Rs6J-0003YW-00; Thu, 24 Aug 2000 10:11:03 +0200 Date: Thu, 24 Aug 2000 10:11:03 +0200 (SAST) From: fingers X-Sender: robh@fingers.noc.uunet.co.za To: Francisco Reyes Cc: FreeBSD Stable List Subject: Re: Upcoming rc.conf changes not loading certain currently loaded daemons In-Reply-To: <200008240454.AAA31598@sanson.reyes.somos.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 Hi > What was the reason for these daemons been set to not start? > Wouldn't this "break" working machines? I don't know what percentage of installers are doing the same, but the first thing I do is disable them and kill 'em dead. --Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 1:22:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fs2.orientasia.uni-bonn.de (fs2.orientasia.uni-bonn.de [131.220.92.154]) by hub.freebsd.org (Postfix) with ESMTP id 4D4EF37B42C for ; Thu, 24 Aug 2000 01:22:32 -0700 (PDT) Received: from localhost (admin@localhost) by fs2.orientasia.uni-bonn.de (8.9.3/8.9.3) with ESMTP id KAA83037 for ; Thu, 24 Aug 2000 10:22:23 +0200 (CEST) (envelope-from admin@fs2.orientasia.uni-bonn.de) Date: Thu, 24 Aug 2000 10:22:22 +0200 (CEST) From: Administrator OrientAsia To: stable@FreeBSD.ORG Subject: Re: WTF In-Reply-To: <200008232333.SAA15508@awww.jeah.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, 23 Aug 2000, Chris Byrnes wrote: > I'm running 3.5-STABLE. > > Recently, my server has started rebooting, at random times, usually > actually quite religiously about every 2 days. > > I thought it might be a RAM problem. Replaced with brand new RAM. > Same problem. > > Any ideas, at all? Pllllllllllllease. I've had the same problem on a 4.X-STABLE machine for some time. In my case, it rebooted regularly and failed to compile larger stuff, such as kernels or make worlds, quite often. It stayed, even though I replaced the RAM. In my case, it was due to a faulty cache module (it's a board that still uses old COAST modules). It's running cacheless now, but it's running. Time to go looking for COAST modules, though :-) Philipp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 1:34: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id DA34737B43F; Thu, 24 Aug 2000 01:33:57 -0700 (PDT) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Thu, 24 Aug 2000 09:33:39 +0100 Message-ID: <39A4DDE1.17DFE7DC@cs.ucl.ac.uk> Date: Thu, 24 Aug 2000 09:33:37 +0100 From: Theo PAGTZIS Reply-To: t.pagtzis@cs.ucl.ac.uk Organization: UCL X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: el, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: help with restoring sh Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I have been upgrading from 3.4 to 4.1 and during the reboot I get a permission denied when it tries to exec the /bin/sh. I am trying to restore the file with one that is functioning properly..however I do not know how I should go about correcting my problem. I would appreciate any help as I am stranded with a server that is down at the moment... Thanks Theo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 1:43:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id AB12837B423 for ; Thu, 24 Aug 2000 01:43:21 -0700 (PDT) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Thu, 24 Aug 2000 09:43:16 +0100 Message-ID: <39A4E022.FC7C26D5@cs.ucl.ac.uk> Date: Thu, 24 Aug 2000 09:43:14 +0100 From: Theo PAGTZIS Reply-To: t.pagtzis@cs.ucl.ac.uk Organization: UCL X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: el, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: filename too long??? 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 have the following fstab file # Device Mountpoint FStype Options Dump Pass# /dev/wd0s1b none swap sw 0 0 /dev/wd0s1a / ufs rw 1 1 /dev/wd0s1f /usr ufs rw 2 2 /dev/wd0s1e /var ufs rw 2 2 /dev/wcd0c /mnt/cdrom cd9660 ro,noauto 0 0 /dev/fd0 /mnt/floppy msdos rw,noauto 0 0 proc /proc procfs rw 0 0 # you want to get the essential ports in one place to do one build and multi installs - faster starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/essential_port_pool /usr/pool nfs rw 0 0 starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/master_distfiles_ports /usr/ports/distfiles nfs rw 0 0 # this needs a soft link on the mounted folder, on the root dir starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/essential_config/elikonas /backupETC nfs rw 0 0 When I try to mount these stores I get : nfs: starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/essential_port_pool: File name too long nfs: starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/master_distfiles_ports: File name too long nfs: starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/essential_config/elikonas: File name too long This was not the case with Fbsd 3.4 Why is this happening? Is it because of the device name change because the machine boots fine without asking for an ad0 device set Theo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 2:18:12 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 CA12037B423 for ; Thu, 24 Aug 2000 02:18:08 -0700 (PDT) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.0/8.11.0) id e7O9DqB48447; Thu, 24 Aug 2000 10:13:52 +0100 (BST) (envelope-from nik) Date: Thu, 24 Aug 2000 10:13:52 +0100 From: Nik Clayton To: Francisco Reyes Cc: FreeBSD Stable List Subject: Re: Upcoming rc.conf changes not loading certain currently loaded daemons Message-ID: <20000824101352.A48334@canyon.nothing-going-on.org> References: <200008240454.AAA31598@sanson.reyes.somos.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200008240454.AAA31598@sanson.reyes.somos.net>; from fran@reyes.somos.net on Thu, Aug 24, 2000 at 01:03:50AM -0400 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 24, 2000 at 01:03:50AM -0400, Francisco Reyes wrote: > On a recent email Peter Jeremy wrote: > > >..., rc.conf was recently changed (in -current) to not > >start inetd, portmap or sendmail. If you are actually relying on > >any of these daemons, and you actually notice the differences in > >/etc/defaults/rc.conf, you will be able to update /etc/rc.conf > >without a period of head-scratching when they don't start. > > What was the reason for these daemons been set to not start? Now, if you have an empty /etc/rc.conf then (in theory) no network services are running. This also means that if you want to find out what services are started at boot time you only have to look in /etc/rc.conf, rather than having to look at /etc/defaults/rc.conf as well. > Wouldn't this "break" working machines? Only if you (1) Are running -current, and (2) don't read the mailing lists and the diffs mergemaster shows you. If both (1) and (2) are true then you shouldn't be running -current anyway. 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 Thu Aug 24 2:31:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from plum.flirble.org (plum.flirble.org [195.40.6.20]) by hub.freebsd.org (Postfix) with ESMTP id 2656B37B423; Thu, 24 Aug 2000 02:31:27 -0700 (PDT) Received: from scot (helo=localhost) by plum.flirble.org with local-esmtp (Exim 3.12 #5) id 13RtM6-000Mx1-00; Thu, 24 Aug 2000 10:31:26 +0100 Date: Thu, 24 Aug 2000 10:31:26 +0100 (BST) From: scot@poptart.org X-Sender: scot@plum.flirble.org To: Theo PAGTZIS Cc: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: help with restoring sh In-Reply-To: <39A4DDE1.17DFE7DC@cs.ucl.ac.uk> 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 Boot from a fix-it floppy and copy it there from the floppy... (and make sure the permissions are correct)... Scot On Thu, 24 Aug 2000, Theo PAGTZIS wrote: > Hi all, > > I have been upgrading from 3.4 to 4.1 and during the reboot I get a > permission denied when it tries to exec the /bin/sh. I am trying to > restore the file with one that is functioning properly..however I do not > know how I should go about correcting my problem. I would appreciate any > help as I am stranded with a server that is down at the moment... > > > Thanks > > Theo > > > > 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 Aug 24 5:11: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sanson.reyes.somos.net (freyes.static.inch.com [216.223.199.224]) by hub.freebsd.org (Postfix) with ESMTP id D485137B422 for ; Thu, 24 Aug 2000 05:10:54 -0700 (PDT) Received: from tomasa (tomasa.reyes.somos.net [10.0.0.11]) by sanson.reyes.somos.net (8.9.3/8.9.3) with SMTP id IAA32736; Thu, 24 Aug 2000 08:01:08 -0400 (EDT) (envelope-from fran@reyes.somos.net) Message-Id: <200008241201.IAA32736@sanson.reyes.somos.net> From: "Francisco Reyes" To: "fingers" Cc: "FreeBSD Stable List" Date: Thu, 24 Aug 2000 08:08:52 -0400 Reply-To: "Francisco Reyes" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 98 (4.10.2222) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: Upcoming rc.conf changes not loading certain currently loaded daemons Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 24 Aug 2000 10:11:03 +0200 (SAST), fingers wrote: >Hi > >> What was the reason for these daemons been set to not start? >> Wouldn't this "break" working machines? > >I don't know what percentage of installers are doing the same, That is the problem. Most likely nobody knows the percentage of people that use them vs the percentage that turns them off. >but the first thing I do is disable them and kill 'em dead. Perhaps this could be an installation flag. francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 5:12:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sanson.reyes.somos.net (freyes.static.inch.com [216.223.199.224]) by hub.freebsd.org (Postfix) with ESMTP id AF4EB37B423; Thu, 24 Aug 2000 05:12:14 -0700 (PDT) Received: from tomasa (tomasa.reyes.somos.net [10.0.0.11]) by sanson.reyes.somos.net (8.9.3/8.9.3) with SMTP id IAA32744; Thu, 24 Aug 2000 08:03:43 -0400 (EDT) (envelope-from fran@reyes.somos.net) Message-Id: <200008241203.IAA32744@sanson.reyes.somos.net> From: "Francisco Reyes" To: "Nik Clayton" Cc: "FreeBSD Stable List" Date: Thu, 24 Aug 2000 08:11:25 -0400 Reply-To: "Francisco Reyes" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 98 (4.10.2222) In-Reply-To: <20000824101352.A48334@canyon.nothing-going-on.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: Upcoming rc.conf changes not loading certain currently loaded daemons Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 24 Aug 2000 10:13:52 +0100, Nik Clayton wrote: >> What was the reason for these daemons been set to not start? > >Now, if you have an empty /etc/rc.conf then (in theory) no network services >are running. This also means that if you want to find out what services are >started at boot time you only have to look in /etc/rc.conf, rather than >having to look at /etc/defaults/rc.conf as well. Then shouldn't we add the current programs which get started to /etc/rc.conf? >> Wouldn't this "break" working machines? > >Only if you (1) Are running -current, and (2) don't read the mailing lists >and the diffs mergemaster shows you. > >If both (1) and (2) are true then you shouldn't be running -current anyway. I know this is currently in "current", but won't this eventually make it to stable? francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 5:22:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.il.home.com (ha1.rdc1.il.home.com [24.2.1.66]) by hub.freebsd.org (Postfix) with ESMTP id 5F51537B424 for ; Thu, 24 Aug 2000 05:22:11 -0700 (PDT) Received: from math.missouri.edu ([24.12.197.197]) by mail.rdc1.il.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000824122210.FPWV15750.mail.rdc1.il.home.com@math.missouri.edu> for ; Thu, 24 Aug 2000 05:22:10 -0700 Message-ID: <39A51372.66EC90DE@math.missouri.edu> Date: Thu, 24 Aug 2000 07:22:10 -0500 From: Stephen Montgomery-Smith X-Mailer: Mozilla 4.74 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD Stable List Subject: Problem changing ownership of a link Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If xxx is a soft link, I am finding that the chown command has no effect in changing ownership of xxx: if xxx is owned by bob, then chown fred xxx seems to have no effect at all. Is this how it should be? I'm finding this a bit frustrating. -- Stephen Montgomery-Smith stephen@math.missouri.edu 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 Aug 24 5:26:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mcp.csh.rit.edu (mcp.csh.rit.edu [129.21.60.9]) by hub.freebsd.org (Postfix) with ESMTP id 7DA8D37B424 for ; Thu, 24 Aug 2000 05:26:27 -0700 (PDT) Received: from fury.csh.rit.edu (fury.csh.rit.edu [129.21.60.5]) by mcp.csh.rit.edu (Postfix) with ESMTP id CB9BF348; Thu, 24 Aug 2000 08:26:26 -0400 (EDT) Received: (from jon@localhost) by fury.csh.rit.edu (8.9.3+Sun/8.9.1) id IAA01669; Thu, 24 Aug 2000 08:25:59 -0400 (EDT) Date: Thu, 24 Aug 2000 08:25:59 -0400 From: Jon Parise To: Stephen Montgomery-Smith Cc: FreeBSD Stable List Subject: Re: Problem changing ownership of a link Message-ID: <20000824082558.B1337@csh.rit.edu> Mail-Followup-To: Stephen Montgomery-Smith , FreeBSD Stable List References: <39A51372.66EC90DE@math.missouri.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <39A51372.66EC90DE@math.missouri.edu>; from stephen@math.missouri.edu on Thu, Aug 24, 2000 at 07:22:10AM -0500 X-Operating-System: SunOS 5.7 (sun4u) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 24, 2000 at 07:22:10AM -0500, Stephen Montgomery-Smith wrote: > If xxx is a soft link, I am finding that the chown > command has no effect in changing ownership of xxx: > > if xxx is owned by bob, then > chown fred xxx > seems to have no effect at all. % chown -h user symlink This should have been asked on -questions. -- Jon Parise (jon@csh.rit.edu) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 5:35:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (Postfix) with ESMTP id 955CF37B423 for ; Thu, 24 Aug 2000 05:35:10 -0700 (PDT) Received: from localhost (arg@localhost) by arg1.demon.co.uk (8.8.8/8.8.8) with ESMTP id NAA26823; Thu, 24 Aug 2000 13:33:51 +0100 (BST) (envelope-from arg@arg1.demon.co.uk) Date: Thu, 24 Aug 2000 13:33:51 +0100 (BST) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: Chris Dillon Cc: Smith@ian.org, Dermot McNally , freebsd-stable@freebsd.org, Fred Clift Subject: Re: Numbering of fxp devices 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 Wed, 23 Aug 2000, Chris Dillon & others wrote: > > > I also wonder if there woudl be a way to map cards based on their > > MAC addresses, or is the MAC address discovery done way too late? > > Way too late, I think, since the driver would have to attach before it > could even query the card for its MAC address. If it were able to get > the MAC, detach, re-attach, etc. until the right order was reached, > that might work. > > > Hmm.. maybe some sort of aliasing? A conf file could list device > > numbers and MAC addresses, so once the kernel finished finding > > everything, it could look through the cards and asign /dev/ether0 > > to one, /dev/ether1 to another, ect. > > Thats an idea, too... I think you're making this way harder than it needs to be. I use the following in /etc/rc.conf: ether=$(ifconfig ed1 |grep ether |cut -c 8-24) echo Ethernet address is ${ether} case ${ether} in 00:e0:29:32:67:7c) hostname="rig1.vnltest" ifconfig_ed1="inet 10.5.0.101 netmask 0xffffff00" ;; 00:e0:29:32:67:7f) hostname="rig2.vnltest" ifconfig_ed1="inet 10.5.0.102 netmask 0xffffff00" ;; 00:e0:29:32:6f:0d) hostname="rig3.vnltest" ifconfig_ed1="inet 10.5.0.103 netmask 0xffffff00" ;; *) echo "Unexpected ethernet address $ether - assuming rig4" hostname="rig4.vnltest" ifconfig_ed1="inet 10.5.0.104 netmask 0xffffff00" ;; esac This particular example is for a single interface - I use it on a bootable CD, so that I can just duplicate a single CD image for a bunch of machines, and have each of them come up with their individual configuration. For the multiple interface situation you've been talking about, a similar trivial piece of shellscript would let you assign ifconfig_xxx variables according to the MAC address. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 5:42:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.venon.com (ns1.venon.com [64.7.7.83]) by hub.freebsd.org (Postfix) with ESMTP id A41E537B506; Thu, 24 Aug 2000 05:42:43 -0700 (PDT) Received: from megalomaniac.biosys.net (megalomaniac.venon.com [64.7.7.82]) by ns1.venon.com (Postfix) with ESMTP id 44FD7D147F; Thu, 24 Aug 2000 08:45:10 -0400 (EDT) Message-Id: <4.3.2.7.2.20000824082639.00afffb8@mail.megapathdsl.net> X-Sender: (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 24 Aug 2000 08:45:39 -0400 To: freebsd-questions@freebsd.org From: Allen Landsidel Subject: cyrus imapd problems resolved.. Cc: freebsd-stable@freebsd.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 I'm crossposting this to freebsd-stable since the people responsible for this kind of thing usually are listening there... Thanks to a little elbow grease and a thanks to retch, I have managed to get cyrus running on my 3.5-Stable box. For those that didn't see my post -questions, in short, I tried to get cyrus up and running today but the sasl port was/is broken (/usr/ports/security/cyrus-sasl) which is required for authenticating users. It looks like the only problem with that is an incorrect MD5 hash. In my headsmashing though, I uncovered some things to update both that port, and /usr/ports/mail/cyrus as well to the latest version.. here are my notes.. hopefully they fall into the hands of whoever is responsible. Notes for /usr/ports/mail/cyrus : ./Makefile change version string to 1.6.24 (latest version).. always a good thing, and as it is now fetch will try about five different servers until it finds the old version. ./files/MD5 : Replace contents of file with : MD5 (cyrus-imapd-1.6.24.tar.gz) = 490a246e787581e0bbc558788ff5f562 --after fetch-- ./work/cyrus-imapd-1.6.24/sieve/comparator.h: Add "#include " before -- it's not included in the distribution for some reason, and breaks on compile on this file without it. Notes for /usr/ports/security/cyrus-sasl ./files/MD5 : Replace contents of file with : MD5 (cyrus-sasl-1.5.24.tar.gz) = ac3837c071c258b80021325936db2583 Notes general. After installation of the port, the user needs to run /usr/local/sbin/saslpasswd to create an entry in the sasl password database. The user they create (just to get things going here) should also have their name listed as an "admin" in imapd.conf. The first run of saslpasswd will create /usr/local/etc/sasldb.db which must be owned by cyrus:cyrus for auth to function.. so either saslpasswd must be run after suing to cyrus, the file must be chowned after being run by another user (which is what I did). I only mention this because the Cyrus documentation REALLY SUCKS and it was only after hours of scouring usenet that I came across this tidbit posted in an OpenBSD newsgroup where someone else was having similar problems. ------prologue------ cyrus finally seems to be working for me.. at least it let's me auth and mess around with cyradm which it wouldn't even do before. On the down side, I still get this weird error whenever I use imtest to check things out, although I think it may only be because I have not created any mailboxes yet. The error is... S: C01 OK Unknown error: -1904809442 .. then after I have entered the password, then done '. logout'... * BYE Unknown error: -1904809443 . OK Unknown error: -1904809442 I'll be checking that part out soon.. but hey, this is progress... hope this helps some people. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 6: 4:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dazed.slacker.com (dazed.slacker.com [208.15.208.76]) by hub.freebsd.org (Postfix) with SMTP id A648537B422 for ; Thu, 24 Aug 2000 06:04:20 -0700 (PDT) Received: (qmail 53784 invoked by uid 1000); 24 Aug 2000 13:04:19 -0000 Date: Thu, 24 Aug 2000 08:04:19 -0500 From: David McNett To: FreeBSD Stable List Subject: Re: Upcoming rc.conf changes not loading certain currently loaded daemons Message-ID: <20000824080419.B51628@dazed.slacker.com> References: <200008241201.IAA32736@sanson.reyes.somos.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200008241201.IAA32736@sanson.reyes.somos.net>; from fran@reyes.somos.net on Thu, Aug 24, 2000 at 08:08:52AM -0400 X-Operating-System: FreeBSD 4.1-STABLE i386 X-Distributed: Join the Effort! http://www.distributed.net/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Aug-2000, Francisco Reyes wrote: > On Thu, 24 Aug 2000 10:11:03 +0200 (SAST), fingers wrote: > >but the first thing I do is disable them and kill 'em dead. > > Perhaps this could be an installation flag. Personally, I think the change is a wonderful move. I frankly find it to be a bit of an embarassment to see FreeBSD installing out of the box with such protocols as telnet and rexec running by default. Ideally, I'd like to see the installer properly force the determination of USA_RESIDENT and install the appropriate rsaref / librsaintl libraries so a fresh install could sshd_enable="YES" in /etc/defaults/rc.conf If someone insists on using those antiquated and unsafe protocols like telnet and the r* services, we should at least make sure they're doing it on purpose and not just leaving the defaults in place out of ignorance. -- ________________________________________________________________________ |David McNett |To ensure privacy and data integrity this message has| |nugget@slacker.com|been encrypted using dual rounds of ROT-13 encryption| |Birmingham, AL USA|Please encrypt all important correspondence with PGP!| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 6: 7:34 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 527D337B423 for ; Thu, 24 Aug 2000 06:07:29 -0700 (PDT) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13Rwix-0006UR-00; Thu, 24 Aug 2000 15:07:15 +0200 Date: Thu, 24 Aug 2000 15:07:15 +0200 From: Neil Blakey-Milner To: Francisco Reyes Cc: FreeBSD Stable List Subject: Re: Upcoming rc.conf changes not loading certain currently loaded daemons Message-ID: <20000824150715.A24874@mithrandr.moria.org> References: <200008240454.AAA31598@sanson.reyes.somos.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200008240454.AAA31598@sanson.reyes.somos.net>; from fran@reyes.somos.net on Thu, Aug 24, 2000 at 01:03:50AM -0400 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 Thu 2000-08-24 (01:03), Francisco Reyes wrote: > What was the reason for these daemons been set to not start? > Wouldn't this "break" working machines? Only if you upgrade without reading the heads-up and warnings in UPDATING. The reason was to make things more obvious. If you have an empty /etc/rc.conf, you don't expect portmap and inetd to be running. (and when I'm through with it, sendmail won't be listening on port 25 by default either *evil.grin*) Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 7:18:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 0DAEB37B42C for ; Thu, 24 Aug 2000 07:18:07 -0700 (PDT) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id JAA82470; Thu, 24 Aug 2000 09:17:41 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Thu, 24 Aug 2000 09:17:41 -0500 (CDT) From: Chris Dillon To: Andrew Gordon Cc: Smith@ian.org, Dermot McNally , freebsd-stable@freebsd.org, Fred Clift Subject: Re: Numbering of fxp devices 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, 24 Aug 2000, Andrew Gordon wrote: > On Wed, 23 Aug 2000, Chris Dillon & others wrote: > > > > > I also wonder if there woudl be a way to map cards based on their > > > MAC addresses, or is the MAC address discovery done way too late? > > > > Way too late, I think, since the driver would have to attach before it > > could even query the card for its MAC address. If it were able to get > > the MAC, detach, re-attach, etc. until the right order was reached, > > that might work. > > > > > Hmm.. maybe some sort of aliasing? A conf file could list device > > > numbers and MAC addresses, so once the kernel finished finding > > > everything, it could look through the cards and asign /dev/ether0 > > > to one, /dev/ether1 to another, ect. > > > > Thats an idea, too... > > I think you're making this way harder than it needs to be. I use the > following in /etc/rc.conf: > > ether=$(ifconfig ed1 |grep ether |cut -c 8-24) > echo Ethernet address is ${ether} > case ${ether} in > 00:e0:29:32:67:7c) > hostname="rig1.vnltest" > ifconfig_ed1="inet 10.5.0.101 netmask 0xffffff00" > ;; > 00:e0:29:32:67:7f) > hostname="rig2.vnltest" > ifconfig_ed1="inet 10.5.0.102 netmask 0xffffff00" > ;; > 00:e0:29:32:6f:0d) > hostname="rig3.vnltest" > ifconfig_ed1="inet 10.5.0.103 netmask 0xffffff00" > ;; > *) > echo "Unexpected ethernet address $ether - assuming rig4" > hostname="rig4.vnltest" > ifconfig_ed1="inet 10.5.0.104 netmask 0xffffff00" > ;; > esac > > > This particular example is for a single interface - I use it on a > bootable CD, so that I can just duplicate a single CD image for a > bunch of machines, and have each of them come up with their > individual configuration. For the multiple interface situation > you've been talking about, a similar trivial piece of shellscript > would let you assign ifconfig_xxx variables according to the MAC > address. That works fine in the case of attaching an IP address to a given MAC address, but it still doesn't attach a specific device number to a given MAC. Being able to do so goes beyond just assigning IP addresses the old way, it also keeps things intuitive when dealing with lots if interfaces, as well as with any utility that takes an interface name instead of an IP address (tcpdump, etc.). -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures. ( 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 Aug 24 7:58: 6 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 D300E37B423 for ; Thu, 24 Aug 2000 07:58:03 -0700 (PDT) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.0/8.11.0) id e7OEgZu26860; Thu, 24 Aug 2000 15:42:35 +0100 (BST) (envelope-from nik) Date: Thu, 24 Aug 2000 15:42:35 +0100 From: Nik Clayton To: Neil Blakey-Milner Cc: Francisco Reyes , FreeBSD Stable List Subject: Re: Upcoming rc.conf changes not loading certain currently loaded daemons Message-ID: <20000824154235.B8893@canyon.nothing-going-on.org> References: <200008240454.AAA31598@sanson.reyes.somos.net> <20000824150715.A24874@mithrandr.moria.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20000824150715.A24874@mithrandr.moria.org>; from nbm@mithrandr.moria.org on Thu, Aug 24, 2000 at 03:07:15PM +0200 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 24, 2000 at 03:07:15PM +0200, Neil Blakey-Milner wrote: > (and when I'm through with it, sendmail won't be listening on port 25 by > default either *evil.grin*) Oi you! Get back to the doc/ tree :-) 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 Thu Aug 24 7:58:15 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 5A31B37B422; Thu, 24 Aug 2000 07:58:10 -0700 (PDT) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.0/8.11.0) id e7OEfko23502; Thu, 24 Aug 2000 15:41:46 +0100 (BST) (envelope-from nik) Date: Thu, 24 Aug 2000 15:41:45 +0100 From: Nik Clayton To: Francisco Reyes Cc: Nik Clayton , FreeBSD Stable List Subject: Re: Upcoming rc.conf changes not loading certain currently loaded daemons Message-ID: <20000824154145.A8893@canyon.nothing-going-on.org> References: <20000824101352.A48334@canyon.nothing-going-on.org> <200008241203.IAA32744@sanson.reyes.somos.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200008241203.IAA32744@sanson.reyes.somos.net>; from fran@reyes.somos.net on Thu, Aug 24, 2000 at 08:11:25AM -0400 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 24, 2000 at 08:11:25AM -0400, Francisco Reyes wrote: > On Thu, 24 Aug 2000 10:13:52 +0100, Nik Clayton wrote: > > >> What was the reason for these daemons been set to not start? > > > >Now, if you have an empty /etc/rc.conf then (in theory) no network services > >are running. This also means that if you want to find out what services are > >started at boot time you only have to look in /etc/rc.conf, rather than > >having to look at /etc/defaults/rc.conf as well. > > Then shouldn't we add the current programs which get started to > /etc/rc.conf? If you install using sysinstall then they are. Have you actually read the diffs and commit messages? If you're upgrading to -current using the source code then they're not. But that's fine, because if you're running -current then you're reading the -current mailing list, and you'll have seen the HEADS UP message that was posted about this. If you're running -stable then it's a non-issue, as these changes haven't been merged. > I know this is currently in "current", but won't this eventually > make it to stable? Maybe. I would have thought that's unlikely though. However, even if it is, there'll be a HEADS UP posted to this mailing list, so you'll be aware that it's an issue. 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 Thu Aug 24 8: 3: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 61E4E37B43E; Thu, 24 Aug 2000 08:02:04 -0700 (PDT) Received: from office.tor.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id ACAF8137F32; Thu, 24 Aug 2000 11:02:02 -0400 (EDT) Received: (from dgilbert@localhost) by office.tor.velocet.net (8.9.3/8.9.3) id LAA64688; Thu, 24 Aug 2000 11:02:02 -0400 (EDT) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="BzGFJYjy6O" Content-Transfer-Encoding: 7bit Message-ID: <14757.14569.732766.367692@trooper.velocet.net> Date: Thu, 24 Aug 2000 11:02:01 -0400 (EDT) To: freebsd-stable@freebsd.org, freebsd-scsi@freebsd.org Subject: Vinum 29160 detaches drives, invalidates RAID. X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --BzGFJYjy6O Content-Type: text/plain; charset=us-ascii Content-Description: message body text Content-Transfer-Encoding: 7bit I have a vinum test box with 8x driven by 2x running 4.1-RELEASE. The machine also has a 9G root SCSI drive that is on a non-LVD connector of the 29160 card. I'll include all the probe messages 'n such at the end, but I want to get to the description first. The 18G drives are all VINUM. It results in Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/vinum/raid 121691956 14986173 96970427 13% /raid I have loaded the drive with a copy of the FreeBSD cvs tree (that I cvsup) and a checked-out copy of the tree. I believe there is also a copy of the results of a make-release and other misc garbage. The drives are cabled 4 per controller with a certified LVD cable that ends with a certified LVD terminator. The root drive has a regular SCSI-2 cable and also an SE/LVD terminator. The 8 drives are in a separate case with redundant (and definately adequate) power. The root drive is on the main case's power. The whole thing is running on a PIII/450 with either 128M or 256M of RAM (depending on what I'm testing). ... so we know what the hardware is. I've been careful to cable and do this all properly. First of all, I'm very pleased with the speed. The system easily beats the AMI MegaRAID 1500 (same drives) with a whopping 35Mbyte/s in RAID-5 (vs. the 1500's 14Mbyte/s) for read. (They both score a dead heat of 4Mbyte/s write.) I have had no troubles with cvsup'ing and no troubles with multiple concurrent cvs checkouts. I have a script that tells me that the 8 drives are dispatching from 500 to 1000 transactions a second (summing up all the iostat figures) and "cvs update" on the FreeBSD src directory can get a combined r/w performance of about 5Mbyte/s on the array. However, the nightly find scripts almost always disable the array. Many, many messages of the form Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0x4a - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout resulting in Aug 24 02:04:44 news /kernel: raid.p0.s4: fatal write I/O error Aug 24 02:04:44 news /kernel: vinum: raid.p0.s4 is stale by force Aug 24 02:04:44 news /kernel: vinum: raid.p0 is degraded and then (as other disks do the same) Aug 24 02:04:44 news /kernel: raid.p0.s5: fatal read I/O error Aug 24 02:04:44 news /kernel: vinum: raid.p0.s5 is crashed by force Aug 24 02:04:44 news /kernel: vinum: raid.p0 is corrupt Now... if I reboot, and "vinum setstate up" all these drives, fsck completes without any complaint. I then generally have to "vinum rebuild parity" ... but I suppose that I'd expect that. The problem I'm having here (and I've had it before) is that the FreeBSD SCSI system seems to "give up" under conditions that others would keep retrying or resetting/retrying. It seems really, really, really important to me that we try harder to get a drive back online. This seems as if it could affect the long-term viability of a vinum-based raid server... not because vinum is bad, but because the SCSI subsystem is too fragile. --BzGFJYjy6O Content-Type: text/plain Content-Disposition: inline; filename="foo" Content-Transfer-Encoding: 7bit Aug 8 13:00:00 news newsyslog[408]: logfile turned over Aug 8 13:19:11 news ntpd[236]: time reset -0.210431 s Aug 8 16:00:04 news ntpd[236]: time reset -0.192604 s Aug 10 22:01:17 news shutdown: reboot by root: Aug 10 22:01:19 news syslogd: exiting on signal 15 Aug 10 22:16:07 news /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Aug 10 22:16:07 news /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Aug 10 22:16:07 news /kernel: The Regents of the University of California. All rights reserved. Aug 10 22:16:07 news /kernel: FreeBSD 4.1-RELEASE #100: Wed Aug 2 11:22:31 EDT 2000 Aug 10 22:16:07 news /kernel: root@news.velocet.net:/usr/src/sys/compile/NEWS Aug 10 22:16:07 news /kernel: Timecounter "i8254" frequency 1193182 Hz Aug 10 22:16:07 news /kernel: Timecounter "TSC" frequency 451024838 Hz Aug 10 22:16:07 news /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (451.02-MHz 686-class CPU) Aug 10 22:16:07 news /kernel: Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Aug 10 22:16:07 news /kernel: Features=0x383f9ff Aug 10 22:16:07 news /kernel: real memory = 134201344 (131056K bytes) Aug 10 22:16:07 news /kernel: avail memory = 127328256 (124344K bytes) Aug 10 22:16:07 news /kernel: Preloaded elf kernel "kernel" at 0xc030a000. Aug 10 22:16:07 news /kernel: Pentium Pro MTRR support enabled Aug 10 22:16:07 news /kernel: md0: Malloc disk Aug 10 22:16:07 news /kernel: npx0: on motherboard Aug 10 22:16:07 news /kernel: npx0: INT 16 interface Aug 10 22:16:07 news /kernel: pcib0: on motherboard Aug 10 22:16:07 news /kernel: pci0: on pcib0 Aug 10 22:16:07 news /kernel: pcib1: at device 1.0 on pci0 Aug 10 22:16:07 news /kernel: pci1: on pcib1 Aug 10 22:16:07 news /kernel: pci1: at 0.0 irq 11 Aug 10 22:16:07 news /kernel: isab0: at device 4.0 on pci0 Aug 10 22:16:07 news /kernel: isa0: on isab0 Aug 10 22:16:07 news /kernel: pci0: at 4.1 Aug 10 22:16:07 news /kernel: pci0: at 4.2 irq 12 Aug 10 22:16:07 news /kernel: chip1: port 0xe800-0xe80f at device 4.3 on pci0 Aug 10 22:16:07 news /kernel: ahc0: port 0xd000-0xd0ff mem 0xdb800000-0xdb800fff irq 12 at device 9.0 on pci0 Aug 10 22:16:07 news /kernel: ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 10 22:16:07 news /kernel: rl0: port 0xb800-0xb8ff mem 0xdb000000-0xdb0000ff irq 10 at device 11.0 on pci0 Aug 10 22:16:07 news /kernel: rl0: Ethernet address: 00:60:67:74:36:23 Aug 10 22:16:07 news /kernel: miibus0: on rl0 Aug 10 22:16:07 news /kernel: rlphy0: on miibus0 Aug 10 22:16:07 news /kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Aug 10 22:16:07 news /kernel: ahc1: port 0xb400-0xb4ff mem 0xda800000-0xda800fff irq 11 at device 12.0 on pci0 Aug 10 22:16:07 news /kernel: ahc1: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 10 22:16:07 news /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Aug 10 22:16:07 news /kernel: fdc0: FIFO enabled, 8 bytes threshold Aug 10 22:16:07 news /kernel: atkbdc0: at port 0x60,0x64 on isa0 Aug 10 22:16:07 news /kernel: atkbd0: irq 1 on atkbdc0 Aug 10 22:16:07 news /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Aug 10 22:16:07 news /kernel: sc0: on isa0 Aug 10 22:16:07 news /kernel: sc0: VGA <16 virtual consoles, flags=0x200> Aug 10 22:16:07 news /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Aug 10 22:16:07 news /kernel: sio0: type 16550A Aug 10 22:16:07 news /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Aug 10 22:16:07 news /kernel: sio1: type 16550A Aug 10 22:16:07 news /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 Aug 10 22:16:07 news /kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Aug 10 22:16:07 news /kernel: ppc0: FIFO with 16/16/9 bytes threshold Aug 10 22:16:07 news /kernel: ppi0: on ppbus0 Aug 10 22:16:07 news /kernel: lpt0: on ppbus0 Aug 10 22:16:07 news /kernel: lpt0: Interrupt-driven port Aug 10 22:16:07 news /kernel: plip0: on ppbus0 Aug 10 22:16:07 news /kernel: Waiting 5 seconds for SCSI devices to settle Aug 10 22:16:07 news /kernel: da1 at ahc0 bus 0 target 1 lun 0 Aug 10 22:16:07 news /kernel: da1: Fixed Direct Access SCSI-3 device Aug 10 22:16:07 news /kernel: da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 10 22:16:07 news /kernel: da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 10 22:16:07 news /kernel: da5 at ahc1 bus 0 target 5 lun 0 Aug 10 22:16:07 news /kernel: da5: Fixed Direct Access SCSI-3 device Aug 10 22:16:07 news /kernel: da5: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 10 22:16:07 news /kernel: da5: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 10 22:16:07 news /kernel: da2 at ahc0 bus 0 target 2 lun 0 Aug 10 22:16:07 news /kernel: da2: Fixed Direct Access SCSI-3 device Aug 10 22:16:07 news /kernel: da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 10 22:16:07 news /kernel: da2: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 10 22:16:07 news /kernel: da6 at ahc1 bus 0 target 6 lun 0 Aug 10 22:16:07 news /kernel: da6: Fixed Direct Access SCSI-3 device Aug 10 22:16:07 news /kernel: da6: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 10 22:16:07 news /kernel: da6: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 10 22:16:07 news /kernel: da3 at ahc0 bus 0 target 3 lun 0 Aug 10 22:16:07 news /kernel: da3: Fixed Direct Access SCSI-3 device Aug 10 22:16:07 news /kernel: da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 10 22:16:07 news /kernel: da3: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 10 22:16:07 news /kernel: da7 at ahc1 bus 0 target 8 lun 0 Aug 10 22:16:07 news /kernel: da7: Fixed Direct Access SCSI-3 device Aug 10 22:16:07 news /kernel: da7: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 10 22:16:07 news /kernel: da7: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 10 22:16:07 news /kernel: da4 at ahc0 bus 0 target 4 lun 0 Aug 10 22:16:07 news /kernel: da4: Fixed Direct Access SCSI-3 device Aug 10 22:16:07 news /kernel: da4: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 10 22:16:07 news /kernel: da4: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 10 22:16:07 news /kernel: da8 at ahc1 bus 0 target 9 lun 0 Aug 10 22:16:07 news /kernel: da8: Fixed Direct Access SCSI-3 device Aug 10 22:16:07 news /kernel: da8: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 10 22:16:07 news /kernel: da8: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 10 22:16:07 news /kernel: da0 at ahc0 bus 0 target 0 lun 0 Aug 10 22:16:07 news /kernel: da0: Fixed Direct Access SCSI-2 device Aug 10 22:16:07 news /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Aug 10 22:16:07 news /kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Aug 10 22:16:07 news /kernel: Mounting root from ufs:/dev/da0s1a Aug 10 22:16:07 news /kernel: vinum: loaded Aug 10 22:16:07 news /kernel: vinum: reading configuration from /dev/da8s1g Aug 10 22:16:07 news /kernel: vinum: updating configuration from /dev/da5s1g Aug 10 22:16:07 news /kernel: vinum: updating configuration from /dev/da4s1g Aug 10 22:16:07 news /kernel: vinum: updating configuration from /dev/da6s1g Aug 10 22:16:07 news /kernel: vinum: updating configuration from /dev/da7s1g Aug 10 22:16:07 news /kernel: vinum: updating configuration from /dev/da3s1g Aug 10 22:16:07 news /kernel: vinum: updating configuration from /dev/da2s1g Aug 10 22:16:07 news /kernel: vinum: updating configuration from /dev/da1s1g Aug 10 22:16:08 news savecore: no core dump Aug 10 22:16:04 news ntpd[169]: ntpd 4.0.99b Wed Aug 2 07:18:01 EDT 2000 (1) Aug 10 22:16:04 news ntpd[169]: using kernel phase-lock loop 2040 Aug 11 01:14:45 news ntpd[169]: time reset -0.133956 s Aug 11 12:45:25 news /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Aug 11 12:45:25 news /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Aug 11 12:45:25 news /kernel: The Regents of the University of California. All rights reserved. Aug 11 12:45:25 news /kernel: FreeBSD 4.1-RELEASE #100: Wed Aug 2 11:22:31 EDT 2000 Aug 11 12:45:25 news /kernel: root@news.velocet.net:/usr/src/sys/compile/NEWS Aug 11 12:45:25 news /kernel: Timecounter "i8254" frequency 1193182 Hz Aug 11 12:45:25 news /kernel: Timecounter "TSC" frequency 451024955 Hz Aug 11 12:45:25 news /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (451.02-MHz 686-class CPU) Aug 11 12:45:25 news /kernel: Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Aug 11 12:45:25 news /kernel: Features=0x383f9ff Aug 11 12:45:25 news /kernel: real memory = 134201344 (131056K bytes) Aug 11 12:45:25 news /kernel: avail memory = 127328256 (124344K bytes) Aug 11 12:45:25 news /kernel: Preloaded elf kernel "kernel" at 0xc030a000. Aug 11 12:45:25 news /kernel: Pentium Pro MTRR support enabled Aug 11 12:45:25 news /kernel: md0: Malloc disk Aug 11 12:45:26 news /kernel: npx0: on motherboard Aug 11 12:45:26 news /kernel: npx0: INT 16 interface Aug 11 12:45:26 news /kernel: pcib0: on motherboard Aug 11 12:45:26 news /kernel: pci0: on pcib0 Aug 11 12:45:26 news /kernel: pcib1: at device 1.0 on pci0 Aug 11 12:45:26 news /kernel: pci1: on pcib1 Aug 11 12:45:26 news /kernel: pci1: at 0.0 irq 11 Aug 11 12:45:26 news /kernel: isab0: at device 4.0 on pci0 Aug 11 12:45:26 news /kernel: isa0: on isab0 Aug 11 12:45:26 news /kernel: pci0: at 4.1 Aug 11 12:45:26 news /kernel: pci0: at 4.2 irq 12 Aug 11 12:45:26 news /kernel: chip1: port 0xe800-0xe80f at device 4.3 on pci0 Aug 11 12:45:26 news /kernel: ahc0: port 0xd000-0xd0ff mem 0xdb800000-0xdb800fff irq 12 at device 9.0 on pci0 Aug 11 12:45:26 news /kernel: ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 11 12:45:26 news /kernel: rl0: port 0xb800-0xb8ff mem 0xdb000000-0xdb0000ff irq 10 at device 11.0 on pci0 Aug 11 12:45:26 news /kernel: rl0: Ethernet address: 00:60:67:74:36:23 Aug 11 12:45:26 news /kernel: miibus0: on rl0 Aug 11 12:45:26 news /kernel: rlphy0: on miibus0 Aug 11 12:45:26 news /kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Aug 11 12:45:26 news /kernel: ahc1: port 0xb400-0xb4ff mem 0xda800000-0xda800fff irq 11 at device 12.0 on pci0 Aug 11 12:45:26 news /kernel: ahc1: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 11 12:45:26 news /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Aug 11 12:45:26 news /kernel: fdc0: FIFO enabled, 8 bytes threshold Aug 11 12:45:26 news /kernel: atkbdc0: at port 0x60,0x64 on isa0 Aug 11 12:45:26 news /kernel: atkbd0: irq 1 on atkbdc0 Aug 11 12:45:26 news /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Aug 11 12:45:26 news /kernel: sc0: on isa0 Aug 11 12:45:26 news /kernel: sc0: VGA <16 virtual consoles, flags=0x200> Aug 11 12:45:26 news /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Aug 11 12:45:26 news /kernel: sio0: type 16550A Aug 11 12:45:26 news /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Aug 11 12:45:26 news /kernel: sio1: type 16550A Aug 11 12:45:26 news /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 Aug 11 12:45:26 news /kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Aug 11 12:45:26 news /kernel: ppc0: FIFO with 16/16/9 bytes threshold Aug 11 12:45:26 news /kernel: ppi0: on ppbus0 Aug 11 12:45:26 news /kernel: lpt0: on ppbus0 Aug 11 12:45:26 news /kernel: lpt0: Interrupt-driven port Aug 11 12:45:26 news /kernel: plip0: on ppbus0 Aug 11 12:45:26 news /kernel: Waiting 5 seconds for SCSI devices to settle Aug 11 12:45:26 news /kernel: da1 at ahc0 bus 0 target 1 lun 0 Aug 11 12:45:26 news /kernel: da1: Fixed Direct Access SCSI-3 device Aug 11 12:45:26 news /kernel: da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 11 12:45:26 news /kernel: da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 11 12:45:26 news /kernel: da5 at ahc1 bus 0 target 5 lun 0 Aug 11 12:45:26 news /kernel: da5: Fixed Direct Access SCSI-3 device Aug 11 12:45:26 news /kernel: da5: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 11 12:45:26 news /kernel: da5: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 11 12:45:26 news /kernel: da2 at ahc0 bus 0 target 2 lun 0 Aug 11 12:45:26 news /kernel: da2: Fixed Direct Access SCSI-3 device Aug 11 12:45:26 news /kernel: da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 11 12:45:26 news /kernel: da2: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 11 12:45:26 news /kernel: da6 at ahc1 bus 0 target 6 lun 0 Aug 11 12:45:26 news /kernel: da6: Fixed Direct Access SCSI-3 device Aug 11 12:45:26 news /kernel: da6: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 11 12:45:26 news /kernel: da6: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 11 12:45:26 news /kernel: da3 at ahc0 bus 0 target 3 lun 0 Aug 11 12:45:26 news /kernel: da3: Fixed Direct Access SCSI-3 device Aug 11 12:45:26 news /kernel: da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 11 12:45:26 news /kernel: da3: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 11 12:45:26 news /kernel: da7 at ahc1 bus 0 target 8 lun 0 Aug 11 12:45:26 news /kernel: da7: Fixed Direct Access SCSI-3 device Aug 11 12:45:26 news /kernel: da7: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 11 12:45:26 news /kernel: da7: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 11 12:45:26 news /kernel: da4 at ahc0 bus 0 target 4 lun 0 Aug 11 12:45:26 news /kernel: da4: Fixed Direct Access SCSI-3 device Aug 11 12:45:26 news /kernel: da4: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 11 12:45:26 news /kernel: da4: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 11 12:45:26 news /kernel: da8 at ahc1 bus 0 target 9 lun 0 Aug 11 12:45:26 news /kernel: da8: Fixed Direct Access SCSI-3 device Aug 11 12:45:26 news /kernel: da8: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 11 12:45:26 news /kernel: da8: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 11 12:45:26 news /kernel: da0 at ahc0 bus 0 target 0 lun 0 Aug 11 12:45:26 news /kernel: da0: Fixed Direct Access SCSI-2 device Aug 11 12:45:26 news /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Aug 11 12:45:26 news /kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Aug 11 12:45:26 news /kernel: Mounting root from ufs:/dev/da0s1a Aug 11 12:45:26 news /kernel: WARNING: / was not properly dismounted Aug 11 12:45:26 news /kernel: vinum: loaded Aug 11 12:45:26 news /kernel: vinum: reading configuration from /dev/da8s1g Aug 11 12:45:26 news /kernel: vinum: updating configuration from /dev/da5s1g Aug 11 12:45:26 news /kernel: vinum: updating configuration from /dev/da6s1g Aug 11 12:45:26 news /kernel: vinum: updating configuration from /dev/da7s1g Aug 11 12:45:26 news /kernel: vinum: updating configuration from /dev/da2s1g Aug 11 12:45:26 news /kernel: vinum: updating configuration from /dev/da3s1g Aug 11 12:45:26 news /kernel: vinum: updating configuration from /dev/da4s1g Aug 11 12:45:26 news /kernel: vinum: updating configuration from /dev/da1s1g Aug 11 12:45:26 news savecore: no core dump Aug 11 12:45:27 news ntpd[169]: ntpd 4.0.99b Wed Aug 2 07:18:01 EDT 2000 (1) Aug 11 12:45:27 news ntpd[169]: using kernel phase-lock loop 2040 Aug 11 12:50:00 news ntpd[169]: time reset -0.317034 s Aug 11 12:50:00 news ntpd[169]: kernel pll status change 2041 Aug 11 13:09:29 news ntpd[169]: time reset 0.353537 s Aug 11 13:35:09 news ntpd[169]: time reset -0.289343 s Aug 11 15:06:05 news ntpd[169]: time reset -0.208662 s Aug 15 17:01:33 news ntpd[169]: time reset -0.213926 s Aug 15 17:20:53 news ntpd[169]: time reset 0.328963 s Aug 15 23:22:26 news ntpd[169]: time reset -0.152637 s Aug 18 02:09:05 news /kernel: Data modified on freelist: word 0 of object 0xc269a000 size 4096 previous type devbuf (0x0 != 0xdeadc0de) Aug 18 13:03:13 news /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Aug 18 13:03:13 news /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Aug 18 13:03:13 news /kernel: The Regents of the University of California. All rights reserved. Aug 18 13:03:13 news /kernel: FreeBSD 4.1-RELEASE #100: Wed Aug 2 11:22:31 EDT 2000 Aug 18 13:03:13 news /kernel: root@news.velocet.net:/usr/src/sys/compile/NEWS Aug 18 13:03:13 news /kernel: Timecounter "i8254" frequency 1193182 Hz Aug 18 13:03:13 news /kernel: Timecounter "TSC" frequency 451025238 Hz Aug 18 13:03:13 news /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (451.03-MHz 686-class CPU) Aug 18 13:03:13 news /kernel: Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Aug 18 13:03:13 news /kernel: Features=0x383f9ff Aug 18 13:03:13 news /kernel: real memory = 134201344 (131056K bytes) Aug 18 13:03:13 news /kernel: avail memory = 127328256 (124344K bytes) Aug 18 13:03:13 news /kernel: Preloaded elf kernel "kernel" at 0xc030a000. Aug 18 13:03:13 news /kernel: Pentium Pro MTRR support enabled Aug 18 13:03:13 news /kernel: md0: Malloc disk Aug 18 13:03:13 news /kernel: npx0: on motherboard Aug 18 13:03:13 news /kernel: npx0: INT 16 interface Aug 18 13:03:13 news /kernel: pcib0: on motherboard Aug 18 13:03:13 news /kernel: pci0: on pcib0 Aug 18 13:03:13 news /kernel: pcib1: at device 1.0 on pci0 Aug 18 13:03:13 news /kernel: pci1: on pcib1 Aug 18 13:03:13 news /kernel: pci1: at 0.0 irq 11 Aug 18 13:03:13 news /kernel: isab0: at device 4.0 on pci0 Aug 18 13:03:13 news /kernel: isa0: on isab0 Aug 18 13:03:13 news /kernel: pci0: at 4.1 Aug 18 13:03:13 news /kernel: pci0: at 4.2 irq 12 Aug 18 13:03:13 news /kernel: chip1: port 0xe800-0xe80f at device 4.3 on pci0 Aug 18 13:03:13 news /kernel: ahc0: port 0xd000-0xd0ff mem 0xdb800000-0xdb800fff irq 12 at device 9.0 on pci0 Aug 18 13:03:13 news /kernel: ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 18 13:03:13 news /kernel: rl0: port 0xb800-0xb8ff mem 0xdb000000-0xdb0000ff irq 10 at device 11.0 on pci0 Aug 18 13:03:13 news /kernel: rl0: Ethernet address: 00:60:67:74:36:23 Aug 18 13:03:13 news /kernel: miibus0: on rl0 Aug 18 13:03:13 news /kernel: rlphy0: on miibus0 Aug 18 13:03:13 news /kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Aug 18 13:03:13 news /kernel: ahc1: port 0xb400-0xb4ff mem 0xda800000-0xda800fff irq 11 at device 12.0 on pci0 Aug 18 13:03:13 news /kernel: ahc1: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 18 13:03:14 news /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Aug 18 13:03:14 news /kernel: fdc0: FIFO enabled, 8 bytes threshold Aug 18 13:03:14 news /kernel: atkbdc0: at port 0x60,0x64 on isa0 Aug 18 13:03:14 news /kernel: atkbd0: irq 1 on atkbdc0 Aug 18 13:03:14 news /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Aug 18 13:03:14 news /kernel: sc0: on isa0 Aug 18 13:03:14 news /kernel: sc0: VGA <16 virtual consoles, flags=0x200> Aug 18 13:03:14 news /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Aug 18 13:03:14 news /kernel: sio0: type 16550A Aug 18 13:03:14 news /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Aug 18 13:03:14 news /kernel: sio1: type 16550A Aug 18 13:03:14 news /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 Aug 18 13:03:14 news /kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Aug 18 13:03:14 news /kernel: ppc0: FIFO with 16/16/9 bytes threshold Aug 18 13:03:14 news /kernel: ppi0: on ppbus0 Aug 18 13:03:14 news /kernel: lpt0: on ppbus0 Aug 18 13:03:14 news /kernel: lpt0: Interrupt-driven port Aug 18 13:03:14 news /kernel: plip0: on ppbus0 Aug 18 13:03:14 news /kernel: Waiting 5 seconds for SCSI devices to settle Aug 18 13:03:14 news /kernel: da1 at ahc0 bus 0 target 1 lun 0 Aug 18 13:03:14 news /kernel: da1: Fixed Direct Access SCSI-3 device Aug 18 13:03:14 news /kernel: da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 13:03:14 news /kernel: da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 13:03:14 news /kernel: da5 at ahc1 bus 0 target 5 lun 0 Aug 18 13:03:14 news /kernel: da5: Fixed Direct Access SCSI-3 device Aug 18 13:03:14 news /kernel: da5: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 13:03:14 news /kernel: da5: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 13:03:14 news /kernel: da2 at ahc0 bus 0 target 2 lun 0 Aug 18 13:03:14 news /kernel: da2: Fixed Direct Access SCSI-3 device Aug 18 13:03:14 news /kernel: da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 13:03:14 news /kernel: da2: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 13:03:14 news /kernel: da6 at ahc1 bus 0 target 6 lun 0 Aug 18 13:03:14 news /kernel: da6: Fixed Direct Access SCSI-3 device Aug 18 13:03:14 news /kernel: da6: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 13:03:14 news /kernel: da6: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 13:03:14 news /kernel: da3 at ahc0 bus 0 target 3 lun 0 Aug 18 13:03:14 news /kernel: da3: Fixed Direct Access SCSI-3 device Aug 18 13:03:14 news /kernel: da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 13:03:14 news /kernel: da3: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 13:03:14 news /kernel: da7 at ahc1 bus 0 target 8 lun 0 Aug 18 13:03:14 news /kernel: da7: Fixed Direct Access SCSI-3 device Aug 18 13:03:14 news /kernel: da7: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 13:03:14 news /kernel: da7: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 13:03:14 news /kernel: da4 at ahc0 bus 0 target 4 lun 0 Aug 18 13:03:14 news /kernel: da4: Fixed Direct Access SCSI-3 device Aug 18 13:03:14 news /kernel: da4: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 13:03:14 news /kernel: da4: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 13:03:14 news /kernel: da8 at ahc1 bus 0 target 9 lun 0 Aug 18 13:03:14 news /kernel: da8: Fixed Direct Access SCSI-3 device Aug 18 13:03:14 news /kernel: da8: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 13:03:14 news /kernel: da8: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 13:03:14 news /kernel: da0 at ahc0 bus 0 target 0 lun 0 Aug 18 13:03:14 news /kernel: da0: Fixed Direct Access SCSI-2 device Aug 18 13:03:14 news /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Aug 18 13:03:14 news /kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Aug 18 13:03:14 news /kernel: Mounting root from ufs:/dev/da0s1a Aug 18 13:03:14 news /kernel: WARNING: / was not properly dismounted Aug 18 13:03:14 news /kernel: vinum: loaded Aug 18 13:03:14 news /kernel: vinum: reading configuration from /dev/da8s1g Aug 18 13:03:14 news /kernel: vinum: updating configuration from /dev/da5s1g Aug 18 13:03:14 news /kernel: vinum: updating configuration from /dev/da4s1g Aug 18 13:03:14 news /kernel: vinum: updating configuration from /dev/da6s1g Aug 18 13:03:14 news /kernel: vinum: updating configuration from /dev/da7s1g Aug 18 13:03:14 news /kernel: vinum: updating configuration from /dev/da3s1g Aug 18 13:03:14 news /kernel: vinum: updating configuration from /dev/da2s1g Aug 18 13:03:14 news /kernel: vinum: updating configuration from /dev/da1s1g Aug 18 13:03:14 news savecore: no core dump Aug 18 13:03:11 news ntpd[169]: ntpd 4.0.99b Wed Aug 2 07:18:01 EDT 2000 (1) Aug 18 13:03:11 news ntpd[169]: using kernel phase-lock loop 2040 Aug 18 12:41:34 news halt: halted by root Aug 18 16:41:34 news syslogd: exiting on signal 15 Aug 18 16:48:20 news /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Aug 18 16:48:20 news /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Aug 18 16:48:20 news /kernel: The Regents of the University of California. All rights reserved. Aug 18 16:48:20 news /kernel: FreeBSD 4.1-RELEASE #100: Wed Aug 2 11:22:31 EDT 2000 Aug 18 16:48:20 news /kernel: root@news.velocet.net:/usr/src/sys/compile/NEWS Aug 18 16:48:20 news /kernel: Timecounter "i8254" frequency 1193182 Hz Aug 18 16:48:20 news /kernel: Timecounter "TSC" frequency 451025041 Hz Aug 18 16:48:20 news /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (451.03-MHz 686-class CPU) Aug 18 16:48:20 news /kernel: Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Aug 18 16:48:20 news /kernel: Features=0x383f9ff Aug 18 16:48:20 news /kernel: real memory = 134201344 (131056K bytes) Aug 18 16:48:20 news /kernel: avail memory = 127328256 (124344K bytes) Aug 18 16:48:20 news /kernel: Preloaded elf kernel "kernel" at 0xc030a000. Aug 18 16:48:20 news /kernel: Pentium Pro MTRR support enabled Aug 18 16:48:20 news /kernel: md0: Malloc disk Aug 18 16:48:20 news /kernel: npx0: on motherboard Aug 18 16:48:20 news /kernel: npx0: INT 16 interface Aug 18 16:48:20 news /kernel: pcib0: on motherboard Aug 18 16:48:20 news /kernel: pci0: on pcib0 Aug 18 16:48:20 news /kernel: pcib1: at device 1.0 on pci0 Aug 18 16:48:20 news /kernel: pci1: on pcib1 Aug 18 16:48:20 news /kernel: pci1: at 0.0 irq 11 Aug 18 16:48:20 news /kernel: isab0: at device 4.0 on pci0 Aug 18 16:48:20 news /kernel: isa0: on isab0 Aug 18 16:48:20 news /kernel: pci0: at 4.1 Aug 18 16:48:20 news /kernel: pci0: at 4.2 irq 12 Aug 18 16:48:20 news /kernel: chip1: port 0xe800-0xe80f at device 4.3 on pci0 Aug 18 16:48:20 news /kernel: ahc0: port 0xd000-0xd0ff mem 0xdb800000-0xdb800fff irq 12 at device 9.0 on pci0 Aug 18 16:48:20 news /kernel: ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 18 16:48:20 news /kernel: rl0: port 0xb800-0xb8ff mem 0xdb000000-0xdb0000ff irq 10 at device 11.0 on pci0 Aug 18 16:48:20 news /kernel: rl0: Ethernet address: 00:60:67:74:36:23 Aug 18 16:48:20 news /kernel: miibus0: on rl0 Aug 18 16:48:20 news /kernel: rlphy0: on miibus0 Aug 18 16:48:20 news /kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Aug 18 16:48:20 news /kernel: ahc1: port 0xb400-0xb4ff mem 0xda800000-0xda800fff irq 11 at device 12.0 on pci0 Aug 18 16:48:20 news /kernel: ahc1: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 18 16:48:20 news /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Aug 18 16:48:20 news /kernel: fdc0: FIFO enabled, 8 bytes threshold Aug 18 16:48:20 news /kernel: atkbdc0: at port 0x60,0x64 on isa0 Aug 18 16:48:20 news /kernel: atkbd0: irq 1 on atkbdc0 Aug 18 16:48:20 news /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Aug 18 16:48:20 news /kernel: sc0: on isa0 Aug 18 16:48:20 news /kernel: sc0: VGA <16 virtual consoles, flags=0x200> Aug 18 16:48:20 news /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Aug 18 16:48:20 news /kernel: sio0: type 16550A Aug 18 16:48:20 news /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Aug 18 16:48:20 news /kernel: sio1: type 16550A Aug 18 16:48:20 news /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 Aug 18 16:48:20 news /kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Aug 18 16:48:20 news /kernel: ppc0: FIFO with 16/16/9 bytes threshold Aug 18 16:48:20 news /kernel: ppi0: on ppbus0 Aug 18 16:48:20 news /kernel: lpt0: on ppbus0 Aug 18 16:48:20 news /kernel: lpt0: Interrupt-driven port Aug 18 16:48:20 news /kernel: plip0: on ppbus0 Aug 18 16:48:20 news /kernel: unknown0: at port 0x3e0-0x3e1 on isa0 Aug 18 16:48:20 news /kernel: Waiting 5 seconds for SCSI devices to settle Aug 18 16:48:20 news /kernel: da1 at ahc0 bus 0 target 1 lun 0 Aug 18 16:48:20 news /kernel: da1: Fixed Direct Access SCSI-3 device Aug 18 16:48:20 news /kernel: da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:48:20 news /kernel: da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:48:20 news /kernel: da5 at ahc1 bus 0 target 5 lun 0 Aug 18 16:48:20 news /kernel: da5: Fixed Direct Access SCSI-3 device Aug 18 16:48:20 news /kernel: da5: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:48:20 news /kernel: da5: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:48:20 news /kernel: da2 at ahc0 bus 0 target 2 lun 0 Aug 18 16:48:20 news /kernel: da2: Fixed Direct Access SCSI-3 device Aug 18 16:48:20 news /kernel: da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:48:20 news /kernel: da2: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:48:20 news /kernel: da6 at ahc1 bus 0 target 6 lun 0 Aug 18 16:48:20 news /kernel: da6: Fixed Direct Access SCSI-3 device Aug 18 16:48:20 news /kernel: da6: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:48:20 news /kernel: da6: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:48:20 news /kernel: da3 at ahc0 bus 0 target 3 lun 0 Aug 18 16:48:20 news /kernel: da3: Fixed Direct Access SCSI-3 device Aug 18 16:48:20 news /kernel: da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:48:20 news /kernel: da3: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:48:20 news /kernel: da7 at ahc1 bus 0 target 8 lun 0 Aug 18 16:48:20 news /kernel: da7: Fixed Direct Access SCSI-3 device Aug 18 16:48:20 news /kernel: da7: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:48:20 news /kernel: da7: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:48:20 news /kernel: da4 at ahc0 bus 0 target 4 lun 0 Aug 18 16:48:20 news /kernel: da4: Fixed Direct Access SCSI-3 device Aug 18 16:48:20 news /kernel: da4: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:48:20 news /kernel: da4: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:48:20 news /kernel: da8 at ahc1 bus 0 target 9 lun 0 Aug 18 16:48:20 news /kernel: da8: Fixed Direct Access SCSI-3 device Aug 18 16:48:20 news /kernel: da8: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:48:20 news /kernel: da8: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:48:20 news /kernel: da0 at ahc0 bus 0 target 0 lun 0 Aug 18 16:48:20 news /kernel: da0: Fixed Direct Access SCSI-2 device Aug 18 16:48:20 news /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Aug 18 16:48:20 news /kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Aug 18 16:48:20 news /kernel: Mounting root from ufs:/dev/da0s1a Aug 18 16:48:20 news /kernel: vinum: loaded Aug 18 16:48:20 news /kernel: vinum: reading configuration from /dev/da7s1g Aug 18 16:48:20 news /kernel: vinum: updating configuration from /dev/da8s1g Aug 18 16:48:20 news /kernel: vinum: updating configuration from /dev/da5s1g Aug 18 16:48:20 news /kernel: vinum: updating configuration from /dev/da4s1g Aug 18 16:48:20 news /kernel: vinum: updating configuration from /dev/da6s1g Aug 18 16:48:20 news /kernel: vinum: updating configuration from /dev/da2s1g Aug 18 16:48:20 news /kernel: vinum: updating configuration from /dev/da3s1g Aug 18 16:48:21 news /kernel: vinum: updating configuration from /dev/da1s1g Aug 18 16:48:21 news savecore: no core dump Aug 18 16:48:21 news ntpd[169]: ntpd 4.0.99b Wed Aug 2 07:18:01 EDT 2000 (1) Aug 18 16:48:21 news ntpd[169]: using kernel phase-lock loop 2040 Aug 18 16:48:29 news login: ROOT LOGIN (root) ON ttyv0 Aug 18 16:50:34 news login: ROOT LOGIN (root) ON ttyv1 Aug 18 16:52:56 news ntpd[169]: time reset 0.215715 s Aug 18 16:52:56 news ntpd[169]: kernel pll status change 2041 Aug 18 16:55:24 news syslogd: exiting on signal 15 Aug 18 16:59:19 news /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Aug 18 16:59:19 news /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Aug 18 16:59:19 news /kernel: The Regents of the University of California. All rights reserved. Aug 18 16:59:19 news /kernel: FreeBSD 4.1-RELEASE #102: Fri Aug 18 12:53:36 EDT 2000 Aug 18 16:59:19 news /kernel: root@news.velocet.net:/usr/src/sys/compile/NEWS Aug 18 16:59:19 news /kernel: Timecounter "i8254" frequency 1193182 Hz Aug 18 16:59:19 news /kernel: Timecounter "TSC" frequency 451025505 Hz Aug 18 16:59:19 news /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (451.03-MHz 686-class CPU) Aug 18 16:59:19 news /kernel: Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Aug 18 16:59:19 news /kernel: Features=0x383f9ff Aug 18 16:59:19 news /kernel: real memory = 134201344 (131056K bytes) Aug 18 16:59:19 news /kernel: avail memory = 127229952 (124248K bytes) Aug 18 16:59:19 news /kernel: Preloaded elf kernel "kernel" at 0xc0321000. Aug 18 16:59:19 news /kernel: Pentium Pro MTRR support enabled Aug 18 16:59:19 news /kernel: md0: Malloc disk Aug 18 16:59:19 news /kernel: npx0: on motherboard Aug 18 16:59:19 news /kernel: npx0: INT 16 interface Aug 18 16:59:19 news /kernel: pcib0: on motherboard Aug 18 16:59:19 news /kernel: pci0: on pcib0 Aug 18 16:59:19 news /kernel: pcib1: at device 1.0 on pci0 Aug 18 16:59:19 news /kernel: pci1: on pcib1 Aug 18 16:59:19 news /kernel: pci1: at 0.0 irq 11 Aug 18 16:59:19 news /kernel: isab0: at device 4.0 on pci0 Aug 18 16:59:19 news /kernel: isa0: on isab0 Aug 18 16:59:19 news /kernel: atapci0: port 0xd800-0xd80f at device 4.1 on pci0 Aug 18 16:59:19 news /kernel: pci0: at 4.2 irq 12 Aug 18 16:59:19 news /kernel: chip1: port 0xe800-0xe80f at device 4.3 on pci0 Aug 18 16:59:19 news /kernel: ahc0: port 0xd000-0xd0ff mem 0xdb800000-0xdb800fff irq 12 at device 9.0 on pci0 Aug 18 16:59:19 news /kernel: ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 18 16:59:19 news /kernel: rl0: port 0xb800-0xb8ff mem 0xdb000000-0xdb0000ff irq 10 at device 11.0 on pci0 Aug 18 16:59:19 news /kernel: rl0: Ethernet address: 00:60:67:74:36:23 Aug 18 16:59:19 news /kernel: miibus0: on rl0 Aug 18 16:59:19 news /kernel: rlphy0: on miibus0 Aug 18 16:59:19 news /kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Aug 18 16:59:19 news /kernel: ahc1: port 0xb400-0xb4ff mem 0xda800000-0xda800fff irq 11 at device 12.0 on pci0 Aug 18 16:59:19 news /kernel: ahc1: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 18 16:59:19 news /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Aug 18 16:59:19 news /kernel: fdc0: FIFO enabled, 8 bytes threshold Aug 18 16:59:19 news /kernel: atkbdc0: at port 0x60,0x64 on isa0 Aug 18 16:59:19 news /kernel: atkbd0: irq 1 on atkbdc0 Aug 18 16:59:19 news /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Aug 18 16:59:19 news /kernel: sc0: on isa0 Aug 18 16:59:19 news /kernel: sc0: VGA <16 virtual consoles, flags=0x200> Aug 18 16:59:19 news /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Aug 18 16:59:19 news /kernel: sio0: type 16550A Aug 18 16:59:19 news /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Aug 18 16:59:19 news /kernel: sio1: type 16550A Aug 18 16:59:19 news /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 Aug 18 16:59:19 news /kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Aug 18 16:59:19 news /kernel: ppc0: FIFO with 16/16/9 bytes threshold Aug 18 16:59:19 news /kernel: ppi0: on ppbus0 Aug 18 16:59:19 news /kernel: lpt0: on ppbus0 Aug 18 16:59:19 news /kernel: lpt0: Interrupt-driven port Aug 18 16:59:19 news /kernel: plip0: on ppbus0 Aug 18 16:59:19 news /kernel: pcic2: at port 0x3e0-0x3e1 on isa0 Aug 18 16:59:19 news /kernel: pcic2: Polling mode Aug 18 16:59:19 news /kernel: pccard0: on pcic2 Aug 18 16:59:19 news /kernel: pccard1: on pcic2 Aug 18 16:59:19 news /kernel: Waiting 5 seconds for SCSI devices to settle Aug 18 16:59:19 news /kernel: da1 at ahc0 bus 0 target 1 lun 0 Aug 18 16:59:19 news /kernel: da1: Fixed Direct Access SCSI-3 device Aug 18 16:59:19 news /kernel: da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:59:19 news /kernel: da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:59:19 news /kernel: da5 at ahc1 bus 0 target 5 lun 0 Aug 18 16:59:19 news /kernel: da5: Fixed Direct Access SCSI-3 device Aug 18 16:59:19 news /kernel: da5: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:59:19 news /kernel: da5: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:59:19 news /kernel: da2 at ahc0 bus 0 target 2 lun 0 Aug 18 16:59:19 news /kernel: da2: Fixed Direct Access SCSI-3 device Aug 18 16:59:19 news /kernel: da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:59:19 news /kernel: da2: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:59:19 news /kernel: da6 at ahc1 bus 0 target 6 lun 0 Aug 18 16:59:19 news /kernel: da6: Fixed Direct Access SCSI-3 device Aug 18 16:59:19 news /kernel: da6: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:59:19 news /kernel: da6: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:59:19 news /kernel: da3 at ahc0 bus 0 target 3 lun 0 Aug 18 16:59:19 news /kernel: da3: Fixed Direct Access SCSI-3 device Aug 18 16:59:19 news /kernel: da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:59:19 news /kernel: da3: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:59:19 news /kernel: da7 at ahc1 bus 0 target 8 lun 0 Aug 18 16:59:19 news /kernel: da7: Fixed Direct Access SCSI-3 device Aug 18 16:59:19 news /kernel: da7: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:59:19 news /kernel: da7: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:59:19 news /kernel: da4 at ahc0 bus 0 target 4 lun 0 Aug 18 16:59:19 news /kernel: da4: Fixed Direct Access SCSI-3 device Aug 18 16:59:19 news /kernel: da4: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:59:19 news /kernel: da4: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:59:19 news /kernel: da8 at ahc1 bus 0 target 9 lun 0 Aug 18 16:59:19 news /kernel: da8: Fixed Direct Access SCSI-3 device Aug 18 16:59:19 news /kernel: da8: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 16:59:19 news /kernel: da8: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 16:59:20 news /kernel: da0 at ahc0 bus 0 target 0 lun 0 Aug 18 16:59:20 news /kernel: da0: Fixed Direct Access SCSI-2 device Aug 18 16:59:20 news /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Aug 18 16:59:20 news /kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Aug 18 16:59:20 news /kernel: Mounting root from ufs:/dev/da0s1a Aug 18 16:59:20 news /kernel: vinum: loaded Aug 18 16:59:20 news /kernel: vinum: reading configuration from /dev/da8s1g Aug 18 16:59:20 news /kernel: vinum: updating configuration from /dev/da7s1g Aug 18 16:59:20 news /kernel: vinum: updating configuration from /dev/da6s1g Aug 18 16:59:20 news /kernel: vinum: updating configuration from /dev/da5s1g Aug 18 16:59:20 news /kernel: vinum: updating configuration from /dev/da3s1g Aug 18 16:59:20 news /kernel: vinum: updating configuration from /dev/da4s1g Aug 18 16:59:20 news /kernel: vinum: updating configuration from /dev/da2s1g Aug 18 16:59:20 news /kernel: vinum: updating configuration from /dev/da1s1g Aug 18 16:59:20 news savecore: no core dump Aug 18 16:59:20 news ntpd[169]: ntpd 4.0.99b Wed Aug 2 07:18:01 EDT 2000 (1) Aug 18 16:59:20 news ntpd[169]: using kernel phase-lock loop 2040 Aug 18 16:59:29 news login: ROOT LOGIN (root) ON ttyv0 Aug 18 17:01:21 news /kernel: pccard: card inserted, slot 1 Aug 18 13:02:15 news pccardd[282]: No card in database for "(null)"("(null)") Aug 18 13:02:15 news pccardd[282]: pccardd started Aug 18 17:02:30 news /kernel: pccard: card removed, slot 1 Aug 18 17:02:40 news /kernel: pccard: card inserted, slot 1 Aug 18 13:02:46 news pccardd[282]: No card in database for "(null)"("(null)") Aug 18 17:03:36 news /kernel: pccard: card removed, slot 1 Aug 18 17:03:52 news /kernel: pccard: card inserted, slot 0 Aug 18 13:03:57 news pccardd[282]: No card in database for "(null)"("(null)") Aug 18 17:44:33 news sshd[458]: log: ROOT LOGIN as 'root' from trooper.velocet.net Aug 18 17:59:21 news /kernel: pccard: card removed, slot 0 Aug 18 18:03:17 news /kernel: pccard: card inserted, slot 1 Aug 18 14:03:22 news pccardd[282]: No card in database for "(null)"("(null)") Aug 18 18:03:31 news /kernel: pccard: card removed, slot 1 Aug 18 18:06:34 news /kernel: pccard: card inserted, slot 1 Aug 18 14:06:39 news pccardd[282]: No card in database for "(null)"("(null)") Aug 18 18:06:43 news /kernel: pccard: card removed, slot 1 Aug 18 18:18:38 news /kernel: pccard: card inserted, slot 0 Aug 18 14:18:44 news pccardd[282]: No card in database for "(null)"("(null)") Aug 18 14:40:12 news halt: halted by root Aug 18 18:40:12 news syslogd: exiting on signal 15 Aug 18 20:22:37 news /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Aug 18 20:22:37 news /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Aug 18 20:22:37 news /kernel: The Regents of the University of California. All rights reserved. Aug 18 20:22:37 news /kernel: FreeBSD 4.1-RELEASE #102: Fri Aug 18 12:53:36 EDT 2000 Aug 18 20:22:37 news /kernel: root@news.velocet.net:/usr/src/sys/compile/NEWS Aug 18 20:22:37 news /kernel: Timecounter "i8254" frequency 1193182 Hz Aug 18 20:22:37 news /kernel: Timecounter "TSC" frequency 451024973 Hz Aug 18 20:22:37 news /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (451.02-MHz 686-class CPU) Aug 18 20:22:37 news /kernel: Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Aug 18 20:22:37 news /kernel: Features=0x383f9ff Aug 18 20:22:37 news /kernel: real memory = 134201344 (131056K bytes) Aug 18 20:22:37 news /kernel: avail memory = 127229952 (124248K bytes) Aug 18 20:22:37 news /kernel: Preloaded elf kernel "kernel" at 0xc0321000. Aug 18 20:22:37 news /kernel: Pentium Pro MTRR support enabled Aug 18 20:22:37 news /kernel: md0: Malloc disk Aug 18 20:22:37 news /kernel: npx0: on motherboard Aug 18 20:22:37 news /kernel: npx0: INT 16 interface Aug 18 20:22:37 news /kernel: pcib0: on motherboard Aug 18 20:22:37 news /kernel: pci0: on pcib0 Aug 18 20:22:37 news /kernel: pcib1: at device 1.0 on pci0 Aug 18 20:22:37 news /kernel: pci1: on pcib1 Aug 18 20:22:37 news /kernel: pci1: at 0.0 irq 11 Aug 18 20:22:37 news /kernel: isab0: at device 4.0 on pci0 Aug 18 20:22:37 news /kernel: isa0: on isab0 Aug 18 20:22:37 news /kernel: atapci0: port 0xd800-0xd80f at device 4.1 on pci0 Aug 18 20:22:37 news /kernel: pci0: at 4.2 irq 12 Aug 18 20:22:37 news /kernel: chip1: port 0xe800-0xe80f at device 4.3 on pci0 Aug 18 20:22:37 news /kernel: ahc0: port 0xd000-0xd0ff mem 0xdb800000-0xdb800fff irq 12 at device 9.0 on pci0 Aug 18 20:22:37 news /kernel: ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 18 20:22:37 news /kernel: rl0: port 0xb800-0xb8ff mem 0xdb000000-0xdb0000ff irq 10 at device 11.0 on pci0 Aug 18 20:22:37 news /kernel: rl0: Ethernet address: 00:60:67:74:36:23 Aug 18 20:22:37 news /kernel: miibus0: on rl0 Aug 18 20:22:37 news /kernel: rlphy0: on miibus0 Aug 18 20:22:37 news /kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Aug 18 20:22:37 news /kernel: ahc1: port 0xb400-0xb4ff mem 0xda800000-0xda800fff irq 11 at device 12.0 on pci0 Aug 18 20:22:37 news /kernel: ahc1: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 18 20:22:37 news /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Aug 18 20:22:37 news /kernel: fdc0: FIFO enabled, 8 bytes threshold Aug 18 20:22:37 news /kernel: atkbdc0: at port 0x60,0x64 on isa0 Aug 18 20:22:37 news /kernel: atkbd0: irq 1 on atkbdc0 Aug 18 20:22:37 news /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Aug 18 20:22:37 news /kernel: sc0: on isa0 Aug 18 20:22:37 news /kernel: sc0: VGA <16 virtual consoles, flags=0x200> Aug 18 20:22:37 news /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Aug 18 20:22:37 news /kernel: sio0: type 16550A Aug 18 20:22:37 news /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Aug 18 20:22:37 news /kernel: sio1: type 16550A Aug 18 20:22:37 news /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 Aug 18 20:22:37 news /kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Aug 18 20:22:37 news /kernel: ppc0: FIFO with 16/16/9 bytes threshold Aug 18 20:22:37 news /kernel: ppi0: on ppbus0 Aug 18 20:22:38 news /kernel: lpt0: on ppbus0 Aug 18 20:22:38 news /kernel: lpt0: Interrupt-driven port Aug 18 20:22:38 news /kernel: plip0: on ppbus0 Aug 18 20:22:38 news /kernel: Waiting 5 seconds for SCSI devices to settle Aug 18 20:22:38 news /kernel: da1 at ahc0 bus 0 target 1 lun 0 Aug 18 20:22:38 news /kernel: da1: Fixed Direct Access SCSI-3 device Aug 18 20:22:38 news /kernel: da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 20:22:38 news /kernel: da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 20:22:38 news /kernel: da5 at ahc1 bus 0 target 5 lun 0 Aug 18 20:22:38 news /kernel: da5: Fixed Direct Access SCSI-3 device Aug 18 20:22:38 news /kernel: da5: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 20:22:38 news /kernel: da5: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 20:22:38 news /kernel: da2 at ahc0 bus 0 target 2 lun 0 Aug 18 20:22:38 news /kernel: da2: Fixed Direct Access SCSI-3 device Aug 18 20:22:38 news /kernel: da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 20:22:38 news /kernel: da2: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 20:22:38 news /kernel: da6 at ahc1 bus 0 target 6 lun 0 Aug 18 20:22:38 news /kernel: da6: Fixed Direct Access SCSI-3 device Aug 18 20:22:38 news /kernel: da6: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 20:22:38 news /kernel: da6: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 20:22:38 news /kernel: da3 at ahc0 bus 0 target 3 lun 0 Aug 18 20:22:38 news /kernel: da3: Fixed Direct Access SCSI-3 device Aug 18 20:22:38 news /kernel: da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 20:22:38 news /kernel: da3: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 20:22:38 news /kernel: da7 at ahc1 bus 0 target 8 lun 0 Aug 18 20:22:38 news /kernel: da7: Fixed Direct Access SCSI-3 device Aug 18 20:22:38 news /kernel: da7: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 20:22:38 news /kernel: da7: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 20:22:38 news /kernel: da4 at ahc0 bus 0 target 4 lun 0 Aug 18 20:22:38 news /kernel: da4: Fixed Direct Access SCSI-3 device Aug 18 20:22:38 news /kernel: da4: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 20:22:38 news /kernel: da4: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 20:22:38 news /kernel: da8 at ahc1 bus 0 target 9 lun 0 Aug 18 20:22:38 news /kernel: da8: Fixed Direct Access SCSI-3 device Aug 18 20:22:38 news /kernel: da8: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 18 20:22:38 news /kernel: da8: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 18 20:22:38 news /kernel: da0 at ahc0 bus 0 target 0 lun 0 Aug 18 20:22:38 news /kernel: da0: Fixed Direct Access SCSI-2 device Aug 18 20:22:38 news /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Aug 18 20:22:38 news /kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Aug 18 20:22:38 news /kernel: Mounting root from ufs:/dev/da0s1a Aug 18 20:22:38 news /kernel: vinum: loaded Aug 18 20:22:38 news /kernel: vinum: reading configuration from /dev/da8s1g Aug 18 20:22:38 news /kernel: vinum: updating configuration from /dev/da5s1g Aug 18 20:22:38 news /kernel: vinum: updating configuration from /dev/da6s1g Aug 18 20:22:38 news /kernel: vinum: updating configuration from /dev/da7s1g Aug 18 20:22:38 news /kernel: vinum: updating configuration from /dev/da1s1g Aug 18 20:22:38 news /kernel: vinum: updating configuration from /dev/da2s1g Aug 18 20:22:38 news /kernel: vinum: updating configuration from /dev/da3s1g Aug 18 20:22:38 news /kernel: vinum: updating configuration from /dev/da4s1g Aug 18 20:22:39 news savecore: no core dump Aug 18 20:22:39 news ntpd[236]: ntpd 4.0.99b Wed Aug 2 07:18:01 EDT 2000 (1) Aug 18 20:22:39 news ntpd[236]: using kernel phase-lock loop 2040 Aug 18 22:38:38 news ntpd[236]: time reset -0.142135 s Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): SCB 0x29 - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): SCB 0x1d - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): SCB 0xb0 - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): SCB 0x92 - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): SCB 0x57 - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): SCB 0xbe - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): SCB 0xc4 - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): SCB 0x2f - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): SCB 0xcc - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 20 02:04:38 news /kernel: (da7:ahc1:0:8:0): SCB 0xfd - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:39 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 20 02:04:39 news /kernel: (da7:ahc1:0:8:0): SCB 0x23 - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:39 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 20 02:04:39 news /kernel: (da6:ahc1:0:6:0): SCB 0xbf - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:39 news /kernel: (da6:ahc1:0:6:0): BDR message in message buffer Aug 20 02:04:40 news /kernel: (da6:ahc1:0:6:0): SCB 0xd4 - timed out in Data-out phase, SEQADDR == 0x5c Aug 20 02:04:40 news /kernel: (da6:ahc1:0:6:0): no longer in timeout, status = 34b Aug 20 02:04:40 news /kernel: ahc1: Issued Channel A Bus Reset. 51 SCBs aborted Aug 20 02:04:45 news /kernel: raid.p0.s5: fatal write I/O error Aug 20 02:04:45 news /kernel: vinum: raid.p0.s5 is stale by force Aug 20 02:04:45 news /kernel: vinum: raid.p0 is degraded Aug 20 02:04:45 news /kernel: raid.p0.s5: fatal write I/O error Aug 20 02:04:45 news last message repeated 9 times Aug 20 02:04:45 news /kernel: raid.p0.s6: fatal write I/O error Aug 20 02:04:46 news /kernel: vinum: raid.p0.s6 is stale by force Aug 20 02:04:46 news /kernel: vinum: raid.p0 is corrupt Aug 20 02:04:46 news /kernel: raid.p0.s5: fatal write I/O error Aug 20 02:04:46 news last message repeated 3 times Aug 22 06:38:02 news dhclient: New IP Address(rl0): 204.138.45.35 Aug 22 06:38:02 news dhclient: New Subnet Mask (rl0): 255.255.255.192 Aug 22 06:38:02 news dhclient: New Broadcast Address(rl0): 204.138.45.0 Aug 22 06:38:02 news dhclient: New Routers: 204.138.45.2 Aug 22 15:05:40 news login: ROOT LOGIN (root) ON ttyv0 Aug 22 15:05:50 news /kernel: pid 17260 (bash), uid 0: exited on signal 3 (core dumped) Aug 22 15:05:59 news syslogd: exiting on signal 15 Aug 22 15:10:15 news /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Aug 22 15:10:15 news /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Aug 22 15:10:15 news /kernel: The Regents of the University of California. All rights reserved. Aug 22 15:10:15 news /kernel: FreeBSD 4.1-RELEASE #102: Fri Aug 18 12:53:36 EDT 2000 Aug 22 15:10:15 news /kernel: root@news.velocet.net:/usr/src/sys/compile/NEWS Aug 22 15:10:15 news /kernel: Timecounter "i8254" frequency 1193182 Hz Aug 22 15:10:16 news /kernel: Timecounter "TSC" frequency 451025076 Hz Aug 22 15:10:16 news /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (451.03-MHz 686-class CPU) Aug 22 15:10:16 news /kernel: Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Aug 22 15:10:16 news /kernel: Features=0x383f9ff Aug 22 15:10:16 news /kernel: real memory = 134201344 (131056K bytes) Aug 22 15:10:16 news /kernel: avail memory = 127229952 (124248K bytes) Aug 22 15:10:16 news /kernel: Preloaded elf kernel "kernel" at 0xc0321000. Aug 22 15:10:16 news /kernel: Pentium Pro MTRR support enabled Aug 22 15:10:16 news /kernel: md0: Malloc disk Aug 22 15:10:16 news /kernel: npx0: on motherboard Aug 22 15:10:16 news /kernel: npx0: INT 16 interface Aug 22 15:10:16 news /kernel: pcib0: on motherboard Aug 22 15:10:16 news /kernel: pci0: on pcib0 Aug 22 15:10:16 news /kernel: pcib1: at device 1.0 on pci0 Aug 22 15:10:16 news /kernel: pci1: on pcib1 Aug 22 15:10:16 news /kernel: pci1: at 0.0 irq 11 Aug 22 15:10:16 news /kernel: isab0: at device 4.0 on pci0 Aug 22 15:10:16 news /kernel: isa0: on isab0 Aug 22 15:10:16 news /kernel: atapci0: port 0xd800-0xd80f at device 4.1 on pci0 Aug 22 15:10:16 news /kernel: pci0: at 4.2 irq 12 Aug 22 15:10:16 news /kernel: chip1: port 0xe800-0xe80f at device 4.3 on pci0 Aug 22 15:10:16 news /kernel: ahc0: port 0xd000-0xd0ff mem 0xdb800000-0xdb800fff irq 12 at device 9.0 on pci0 Aug 22 15:10:16 news /kernel: ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 22 15:10:16 news /kernel: rl0: port 0xb800-0xb8ff mem 0xdb000000-0xdb0000ff irq 10 at device 11.0 on pci0 Aug 22 15:10:16 news /kernel: rl0: Ethernet address: 00:60:67:74:36:23 Aug 22 15:10:16 news /kernel: miibus0: on rl0 Aug 22 15:10:16 news /kernel: rlphy0: on miibus0 Aug 22 15:10:16 news /kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Aug 22 15:10:16 news /kernel: ahc1: port 0xb400-0xb4ff mem 0xda800000-0xda800fff irq 11 at device 12.0 on pci0 Aug 22 15:10:16 news /kernel: ahc1: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 22 15:10:16 news /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Aug 22 15:10:16 news /kernel: fdc0: FIFO enabled, 8 bytes threshold Aug 22 15:10:16 news /kernel: atkbdc0: at port 0x60,0x64 on isa0 Aug 22 15:10:16 news /kernel: atkbd0: irq 1 on atkbdc0 Aug 22 15:10:16 news /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Aug 22 15:10:16 news /kernel: sc0: on isa0 Aug 22 15:10:16 news /kernel: sc0: VGA <16 virtual consoles, flags=0x200> Aug 22 15:10:16 news /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Aug 22 15:10:16 news /kernel: sio0: type 16550A Aug 22 15:10:16 news /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Aug 22 15:10:16 news /kernel: sio1: type 16550A Aug 22 15:10:16 news /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 Aug 22 15:10:16 news /kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Aug 22 15:10:16 news /kernel: ppc0: FIFO with 16/16/9 bytes threshold Aug 22 15:10:16 news /kernel: ppi0: on ppbus0 Aug 22 15:10:16 news /kernel: lpt0: on ppbus0 Aug 22 15:10:16 news /kernel: lpt0: Interrupt-driven port Aug 22 15:10:16 news /kernel: plip0: on ppbus0 Aug 22 15:10:16 news /kernel: Waiting 5 seconds for SCSI devices to settle Aug 22 15:10:16 news /kernel: da1 at ahc0 bus 0 target 1 lun 0 Aug 22 15:10:16 news /kernel: da1: Fixed Direct Access SCSI-3 device Aug 22 15:10:16 news /kernel: da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 22 15:10:16 news /kernel: da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 22 15:10:16 news /kernel: da5 at ahc1 bus 0 target 5 lun 0 Aug 22 15:10:16 news /kernel: da5: Fixed Direct Access SCSI-3 device Aug 22 15:10:16 news /kernel: da5: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 22 15:10:16 news /kernel: da5: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 22 15:10:16 news /kernel: da2 at ahc0 bus 0 target 2 lun 0 Aug 22 15:10:16 news /kernel: da2: Fixed Direct Access SCSI-3 device Aug 22 15:10:16 news /kernel: da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 22 15:10:16 news /kernel: da2: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 22 15:10:16 news /kernel: da6 at ahc1 bus 0 target 6 lun 0 Aug 22 15:10:16 news /kernel: da6: Fixed Direct Access SCSI-3 device Aug 22 15:10:16 news /kernel: da6: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 22 15:10:17 news /kernel: da6: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 22 15:10:17 news /kernel: da3 at ahc0 bus 0 target 3 lun 0 Aug 22 15:10:17 news /kernel: da3: Fixed Direct Access SCSI-3 device Aug 22 15:10:17 news /kernel: da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 22 15:10:17 news /kernel: da3: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 22 15:10:17 news /kernel: da7 at ahc1 bus 0 target 8 lun 0 Aug 22 15:10:17 news /kernel: da7: Fixed Direct Access SCSI-3 device Aug 22 15:10:17 news /kernel: da7: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 22 15:10:17 news /kernel: da7: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 22 15:10:17 news /kernel: da4 at ahc0 bus 0 target 4 lun 0 Aug 22 15:10:17 news /kernel: da4: Fixed Direct Access SCSI-3 device Aug 22 15:10:17 news /kernel: da4: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 22 15:10:17 news /kernel: da4: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 22 15:10:17 news /kernel: da8 at ahc1 bus 0 target 9 lun 0 Aug 22 15:10:17 news /kernel: da8: Fixed Direct Access SCSI-3 device Aug 22 15:10:17 news /kernel: da8: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 22 15:10:17 news /kernel: da8: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 22 15:10:17 news /kernel: da0 at ahc0 bus 0 target 0 lun 0 Aug 22 15:10:17 news /kernel: da0: Fixed Direct Access SCSI-2 device Aug 22 15:10:17 news /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Aug 22 15:10:17 news /kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Aug 22 15:10:17 news /kernel: Mounting root from ufs:/dev/da0s1a Aug 22 15:10:17 news /kernel: vinum: loaded Aug 22 15:10:17 news /kernel: vinum: reading configuration from /dev/da7s1g Aug 22 15:10:17 news /kernel: vinum: updating configuration from /dev/da8s1g Aug 22 15:10:17 news /kernel: vinum: updating configuration from /dev/da5s1g Aug 22 15:10:17 news /kernel: vinum: updating configuration from /dev/da6s1g Aug 22 15:10:17 news /kernel: vinum: updating configuration from /dev/da4s1g Aug 22 15:10:17 news /kernel: vinum: updating configuration from /dev/da2s1g Aug 22 15:10:17 news /kernel: vinum: updating configuration from /dev/da3s1g Aug 22 15:10:17 news /kernel: vinum: updating configuration from /dev/da1s1g Aug 22 15:10:17 news savecore: no core dump Aug 22 15:10:11 news ntpd[169]: ntpd 4.0.99b Wed Aug 2 07:18:01 EDT 2000 (1) Aug 22 15:10:11 news ntpd[169]: using kernel phase-lock loop 2040 Aug 22 15:16:41 news login: ROOT LOGIN (root) ON ttyv0 Aug 22 15:17:34 news login: ROOT LOGIN (root) ON ttyv1 Aug 22 17:51:43 news ntpd[169]: time reset -0.131985 s Aug 24 02:03:37 news /kernel: Data modified on freelist: word 0 of object 0xc269d000 size 4096 previous type devbuf (0x0 != 0xdeadc0de) Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0x4a - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0x2a - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0x17 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0x16 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0x37 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0xe - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0xf - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0x33 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0x58 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0x64 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0x85 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0x7f - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0x3b - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0x8b - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0xde - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0xd3 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0xd2 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0xb - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0x24 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0x44 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0xec - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0x7a - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): SCB 0xe3 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0x9d - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0x5f - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): SCB 0x97 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:04:37 news /kernel: (da8:ahc1:0:9:0): SCB 0xe0 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:37 news /kernel: (da8:ahc1:0:9:0): BDR message in message buffer Aug 24 02:04:39 news /kernel: (da8:ahc1:0:9:0): SCB 0xea - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:04:39 news /kernel: (da8:ahc1:0:9:0): no longer in timeout, status = 34b Aug 24 02:04:39 news /kernel: ahc1: Issued Channel A Bus Reset. 174 SCBs aborted Aug 24 02:04:44 news /kernel: raid.p0.s4: fatal write I/O error Aug 24 02:04:44 news /kernel: vinum: raid.p0.s4 is stale by force Aug 24 02:04:44 news /kernel: vinum: raid.p0 is degraded Aug 24 02:04:44 news /kernel: raid.p0.s5: fatal read I/O error Aug 24 02:04:44 news /kernel: vinum: raid.p0.s5 is crashed by force Aug 24 02:04:44 news /kernel: vinum: raid.p0 is corrupt Aug 24 02:04:44 news /kernel: raid.p0.s4: fatal write I/O error Aug 24 02:04:44 news /kernel: raid.p0.s5: fatal read I/O error Aug 24 02:04:44 news /kernel: raid.p0.s4: fatal write I/O error Aug 24 02:04:44 news /kernel: raid.p0.s6: fatal write I/O error Aug 24 02:04:44 news /kernel: vinum: raid.p0.s6 is stale by force Aug 24 02:04:44 news /kernel: raid.p0.s4: fatal write I/O error Aug 24 02:04:44 news last message repeated 2 times Aug 24 02:04:44 news /kernel: raid.p0.s5: fatal read I/O error Aug 24 02:04:44 news /kernel: raid.p0.s5: fatal read I/O error Aug 24 02:05:13 news /kernel: vinum: raid.p0.s5 is stale by force Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x8f - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x41 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x48 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0xc2 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x3d - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x13 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x25 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x9b - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x46 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0xbc - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x40 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x51 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x42 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x3c - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x27 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0xab - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x80 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x9d - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0xe3 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0xd2 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0xde - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): SCB 0x8b - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da6:ahc1:0:6:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): SCB 0x79 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): SCB 0x49 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): SCB 0x28 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): SCB 0xc - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): SCB 0x19 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): SCB 0xd6 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): SCB 0x45 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:44 news /kernel: (da7:ahc1:0:8:0): SCB 0xc3 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xbe - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xd5 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x6a - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x68 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x2d - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x82 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x9e - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x1c - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xb5 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xee - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x2b - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xdc - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x39 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x32 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xea - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x4 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x15 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xe1 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x94 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x56 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xdb - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x1a - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xc0 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xc5 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x9 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xbd - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x2f - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xe9 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xb7 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x86 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x9f - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x77 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x71 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0xa1 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:45 news /kernel: (da7:ahc1:0:8:0): SCB 0x96 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:46 news /kernel: (da7:ahc1:0:8:0): Other SCB Timeout Aug 24 02:05:46 news /kernel: (da8:ahc1:0:9:0): SCB 0x2 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:46 news /kernel: (da8:ahc1:0:9:0): BDR message in message buffer Aug 24 02:05:46 news /kernel: (da8:ahc1:0:9:0): SCB 0xe4 - timed out in Data-out phase, SEQADDR == 0x5c Aug 24 02:05:46 news /kernel: (da8:ahc1:0:9:0): no longer in timeout, status = 34b Aug 24 02:05:46 news /kernel: ahc1: Issued Channel A Bus Reset. 113 SCBs aborted Aug 24 02:05:51 news /kernel: raid.p0.s5: fatal write I/O error Aug 24 02:05:51 news last message repeated 14 times Aug 24 02:05:51 news /kernel: raid.p0.s6: fatal read I/O error Aug 24 02:05:51 news /kernel: vinum: raid.p0.s6 is crashed by force Aug 24 02:05:51 news /kernel: raid.p0.s5: fatal write I/O error Aug 24 02:05:51 news /kernel: raid.p0.s6: fatal write I/O error Aug 24 02:05:51 news /kernel: vinum: raid.p0.s6 is stale by force Aug 24 02:05:51 news /kernel: raid.p0.s7: fatal write I/O error Aug 24 02:05:51 news /kernel: vinum: raid.p0.s7 is stale by force Aug 24 02:05:51 news /kernel: raid.p0.s5: fatal write I/O error Aug 24 02:05:51 news last message repeated 2 times Aug 24 02:05:51 news /kernel: raid.p0.s6: fatal read I/O error Aug 24 02:05:51 news /kernel: vinum: raid.p0.s6 is crashed by force Aug 24 02:05:51 news /kernel: raid.p0.s6: fatal write I/O error Aug 24 02:05:51 news /kernel: vinum: raid.p0.s6 is stale by force Aug 24 02:05:51 news /kernel: raid.p0.s6: fatal write I/O error Aug 24 09:04:31 news reboot: rebooted by root Aug 24 13:04:31 news syslogd: exiting on signal 15 Aug 24 13:08:48 news /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Aug 24 13:08:48 news /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Aug 24 13:08:48 news /kernel: The Regents of the University of California. All rights reserved. Aug 24 13:08:48 news /kernel: FreeBSD 4.1-RELEASE #102: Fri Aug 18 12:53:36 EDT 2000 Aug 24 13:08:48 news /kernel: root@news.velocet.net:/usr/src/sys/compile/NEWS Aug 24 13:08:48 news /kernel: Timecounter "i8254" frequency 1193182 Hz Aug 24 13:08:48 news /kernel: Timecounter "TSC" frequency 451024938 Hz Aug 24 13:08:48 news /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (451.02-MHz 686-class CPU) Aug 24 13:08:48 news /kernel: Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Aug 24 13:08:48 news /kernel: Features=0x383f9ff Aug 24 13:08:48 news /kernel: real memory = 134201344 (131056K bytes) Aug 24 13:08:48 news /kernel: avail memory = 127229952 (124248K bytes) Aug 24 13:08:48 news /kernel: Preloaded elf kernel "kernel" at 0xc0321000. Aug 24 13:08:48 news /kernel: Pentium Pro MTRR support enabled Aug 24 13:08:48 news /kernel: md0: Malloc disk Aug 24 13:08:48 news /kernel: npx0: on motherboard Aug 24 13:08:48 news /kernel: npx0: INT 16 interface Aug 24 13:08:48 news /kernel: pcib0: on motherboard Aug 24 13:08:48 news /kernel: pci0: on pcib0 Aug 24 13:08:48 news /kernel: pcib1: at device 1.0 on pci0 Aug 24 13:08:48 news /kernel: pci1: on pcib1 Aug 24 13:08:48 news /kernel: pci1: at 0.0 irq 11 Aug 24 13:08:48 news /kernel: isab0: at device 4.0 on pci0 Aug 24 13:08:48 news /kernel: isa0: on isab0 Aug 24 13:08:48 news /kernel: atapci0: port 0xd800-0xd80f at device 4.1 on pci0 Aug 24 13:08:48 news /kernel: pci0: at 4.2 irq 12 Aug 24 13:08:48 news /kernel: chip1: port 0xe800-0xe80f at device 4.3 on pci0 Aug 24 13:08:48 news /kernel: ahc0: port 0xd000-0xd0ff mem 0xdb800000-0xdb800fff irq 12 at device 9.0 on pci0 Aug 24 13:08:48 news /kernel: ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 24 13:08:48 news /kernel: rl0: port 0xb800-0xb8ff mem 0xdb000000-0xdb0000ff irq 10 at device 11.0 on pci0 Aug 24 13:08:48 news /kernel: rl0: Ethernet address: 00:60:67:74:36:23 Aug 24 13:08:48 news /kernel: miibus0: on rl0 Aug 24 13:08:48 news /kernel: rlphy0: on miibus0 Aug 24 13:08:48 news /kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Aug 24 13:08:48 news /kernel: ahc1: port 0xb400-0xb4ff mem 0xda800000-0xda800fff irq 11 at device 12.0 on pci0 Aug 24 13:08:48 news /kernel: ahc1: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 24 13:08:48 news /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Aug 24 13:08:48 news /kernel: fdc0: FIFO enabled, 8 bytes threshold Aug 24 13:08:48 news /kernel: atkbdc0: at port 0x60,0x64 on isa0 Aug 24 13:08:48 news /kernel: atkbd0: irq 1 on atkbdc0 Aug 24 13:08:48 news /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Aug 24 13:08:48 news /kernel: sc0: on isa0 Aug 24 13:08:48 news /kernel: sc0: VGA <16 virtual consoles, flags=0x200> Aug 24 13:08:48 news /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Aug 24 13:08:48 news /kernel: sio0: type 16550A Aug 24 13:08:48 news /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Aug 24 13:08:48 news /kernel: sio1: type 16550A Aug 24 13:08:48 news /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 Aug 24 13:08:48 news /kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Aug 24 13:08:48 news /kernel: ppc0: FIFO with 16/16/9 bytes threshold Aug 24 13:08:48 news /kernel: ppi0: on ppbus0 Aug 24 13:08:48 news /kernel: lpt0: on ppbus0 Aug 24 13:08:48 news /kernel: lpt0: Interrupt-driven port Aug 24 13:08:48 news /kernel: plip0: on ppbus0 Aug 24 13:08:48 news /kernel: Waiting 5 seconds for SCSI devices to settle Aug 24 13:08:48 news /kernel: da1 at ahc0 bus 0 target 1 lun 0 Aug 24 13:08:48 news /kernel: da1: Fixed Direct Access SCSI-3 device Aug 24 13:08:48 news /kernel: da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 24 13:08:48 news /kernel: da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 24 13:08:48 news /kernel: da5 at ahc1 bus 0 target 5 lun 0 Aug 24 13:08:48 news /kernel: da5: Fixed Direct Access SCSI-3 device Aug 24 13:08:48 news /kernel: da5: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 24 13:08:48 news /kernel: da5: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 24 13:08:48 news /kernel: da2 at ahc0 bus 0 target 2 lun 0 Aug 24 13:08:48 news /kernel: da2: Fixed Direct Access SCSI-3 device Aug 24 13:08:48 news /kernel: da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 24 13:08:48 news /kernel: da2: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 24 13:08:48 news /kernel: da6 at ahc1 bus 0 target 6 lun 0 Aug 24 13:08:48 news /kernel: da6: Fixed Direct Access SCSI-3 device Aug 24 13:08:48 news /kernel: da6: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 24 13:08:48 news /kernel: da6: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 24 13:08:48 news /kernel: da3 at ahc0 bus 0 target 3 lun 0 Aug 24 13:08:48 news /kernel: da3: Fixed Direct Access SCSI-3 device Aug 24 13:08:48 news /kernel: da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 24 13:08:48 news /kernel: da3: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 24 13:08:48 news /kernel: da7 at ahc1 bus 0 target 8 lun 0 Aug 24 13:08:48 news /kernel: da7: Fixed Direct Access SCSI-3 device Aug 24 13:08:48 news /kernel: da7: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 24 13:08:48 news /kernel: da7: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 24 13:08:48 news /kernel: da4 at ahc0 bus 0 target 4 lun 0 Aug 24 13:08:48 news /kernel: da4: Fixed Direct Access SCSI-3 device Aug 24 13:08:48 news /kernel: da4: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 24 13:08:48 news /kernel: da4: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 24 13:08:48 news /kernel: da8 at ahc1 bus 0 target 9 lun 0 Aug 24 13:08:48 news /kernel: da8: Fixed Direct Access SCSI-3 device Aug 24 13:08:48 news /kernel: da8: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled Aug 24 13:08:48 news /kernel: da8: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Aug 24 13:08:48 news /kernel: da0 at ahc0 bus 0 target 0 lun 0 Aug 24 13:08:48 news /kernel: da0: Fixed Direct Access SCSI-2 device Aug 24 13:08:48 news /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Aug 24 13:08:48 news /kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Aug 24 13:08:48 news /kernel: Mounting root from ufs:/dev/da0s1a Aug 24 13:08:48 news /kernel: vinum: loaded Aug 24 13:08:48 news /kernel: vinum: reading configuration from /dev/da8s1g Aug 24 13:08:48 news /kernel: vinum: updating configuration from /dev/da6s1g Aug 24 13:08:48 news /kernel: vinum: updating configuration from /dev/da7s1g Aug 24 13:08:48 news /kernel: vinum: updating configuration from /dev/da5s1g Aug 24 13:08:48 news /kernel: vinum: updating configuration from /dev/da4s1g Aug 24 13:08:48 news /kernel: vinum: updating configuration from /dev/da3s1g Aug 24 13:08:48 news /kernel: vinum: updating configuration from /dev/da2s1g Aug 24 13:08:48 news /kernel: vinum: updating configuration from /dev/da1s1g Aug 24 13:08:49 news savecore: no core dump Aug 24 13:08:47 news ntpd[169]: ntpd 4.0.99b Wed Aug 2 07:18:01 EDT 2000 (1) Aug 24 13:08:47 news ntpd[169]: using kernel phase-lock loop 2040 --BzGFJYjy6O Content-Type: text/plain; charset=us-ascii Content-Description: message body and .signature Content-Transfer-Encoding: 7bit Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ --BzGFJYjy6O-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 8:15:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gatekeeper.veriohosting.com (gatekeeper.veriohosting.com [192.41.0.2]) by hub.freebsd.org (Postfix) with ESMTP id DBEE937B422 for ; Thu, 24 Aug 2000 08:15:23 -0700 (PDT) Received: by gatekeeper.veriohosting.com; Thu, 24 Aug 2000 09:15:23 -0600 (MDT) Received: from unknown(192.168.1.7) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma002978; Thu, 24 Aug 00 09:15:10 -0600 Received: from vespa.orem.iserver.com (vespa.orem.iserver.com [192.168.1.144]) by orca.orem.veriohosting.com [Verio Web Hosting, Inc. 801.437.0200] (8.8.8) id JAA46697; Thu, 24 Aug 2000 09:15:09 -0600 (MDT) Date: Thu, 24 Aug 2000 09:26:31 -0600 (MDT) From: Fred Clift X-Sender: fred@vespa.orem.iserver.com To: Andrew Gordon Cc: Chris Dillon , Smith@ian.org, Dermot McNally , freebsd-stable@freebsd.org Subject: Re: Numbering of fxp devices 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 think you're making this way harder than it needs to be. I use the > following in /etc/rc.conf: > > ether=$(ifconfig ed1 |grep ether |cut -c 8-24) > echo Ethernet address is ${ether} > case ${ether} in > 00:e0:29:32:67:7c) > hostname="rig1.vnltest" > ifconfig_ed1="inet 10.5.0.101 netmask 0xffffff00" > ;; > 00:e0:29:32:67:7f) ... This is fine if you just want a nice way to have the cards get the right IP addresses. And for most people, it probabably isn't really a big issue at all. I agree that this _mostly_ isn't necessary, and should definitely not be a priority. However... For us, we dont even use the second card as a network card -- it is merely a bootrom-delivery-mechanism. The second card doesn't have a cable plugged into it at all (the first is integrated onto the motherboard of the boxes and is connected to a switch at the top of the rack...) We do have an rc script that checks to see if there are two cards and if so, then we use fxp1 as our primary interface, ignoring the not-even-connected fxp0. The probelm is that because we have lots and lots of machines we dont have all our boxes at the same rev of FreeBSD and depending on the phase of the moon you may be using fxp1 or fxp0 as your only active interface. This actually hasn't been a terrible problem, but it leads to confusion, especially with our new admins. The less differences between boxes (even though the OS may be a different rev) the better. Differences just lead to extra administrative effort and can lead to problems. So, we seek to minimize visible differences like this. If we had network interface aliases, then we could just set the alias and then train our new sys-admins to always use the alias. Fred -- Fred Clift - fclift@verio.net -- Remember: If brute force doesn't work, you're just not using enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 8:18:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from citadel.cequrux.com (citadel.cequrux.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id 91E0837B424 for ; Thu, 24 Aug 2000 08:18:49 -0700 (PDT) Received: (from nobody@localhost) by citadel.cequrux.com (8.8.8/8.6.9) id RAA20397; Thu, 24 Aug 2000 17:18:22 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 20316; Thu Aug 24 17:17:34 2000 Message-ID: <39A53D40.5756D1F8@cequrux.com> Date: Thu, 24 Aug 2000 17:20:32 +0200 From: Graham Wheeler Organization: Cequrux Technologies X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 2.2.8-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: kdulzo@gerp.org Cc: freebsd-stable@freebsd.org Subject: Re: Configuring kernel for ISA cards References: <39A3AE82.FFCD5C19@cequrux.com> <20000823102115.A15422@caffeine.gerp.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kevin M. Dulzo" wrote: > > The configuration commands go in /boot/kernel.conf. (Just > tested on 4.1-stable) and thats where they went in 3.x as well. Yep this works for me, thanks! I'll write up a short description and post it to the list; after some peer review hopefully it can be added to the handbook. -- Dr Graham Wheeler E-mail: gram@cequrux.com Director, Research and Development WWW: http://www.cequrux.com CEQURUX Technologies Phone: +27(21)423-6065 Firewalls/VPN Specialists Fax: +27(21)424-3656 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 8:20: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 0DA0437B423 for ; Thu, 24 Aug 2000 08:20:08 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id A16EAE89F for ; Thu, 24 Aug 2000 11:20:07 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.9.3/8.9.3) id LAA03645; Thu, 24 Aug 2000 11:20:07 -0400 (EDT) (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: <14757.15655.515615.780499@onceler.kciLink.com> Date: Thu, 24 Aug 2000 11:20:07 -0400 (EDT) To: FreeBSD Stable List Subject: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) In-Reply-To: <20000824080419.B51628@dazed.slacker.com> References: <200008241201.IAA32736@sanson.reyes.somos.net> <20000824080419.B51628@dazed.slacker.com> X-Mailer: VM 6.72 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "DM" == David McNett writes: DM> If someone insists on using those antiquated and unsafe protocols like DM> telnet and the r* services, we should at least make sure they're doing it DM> on purpose and not just leaving the defaults in place out of ignorance. How do you make rdump/rmt work without the rcmd service? I've got a LAN and do all backups of workstations to one server with a tape drive. Without the rshd service, it won't work. You shouldn't claim people ignorant when there are no alternatives. But please, prove me wrong. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 GPG & MIME spoken here http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 8:21:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bumper.jellybaby.net (bumper.jellybaby.net [194.159.247.1]) by hub.freebsd.org (Postfix) with ESMTP id 8C15C37B42C for ; Thu, 24 Aug 2000 08:21:31 -0700 (PDT) Received: (from simond@localhost) by bumper.jellybaby.net (8.9.2/8.9.2) id QAA82640; Thu, 24 Aug 2000 16:21:23 +0100 (BST) (envelope-from simond) Date: Thu, 24 Aug 2000 16:21:23 +0100 From: simond@irrelevant.org To: Vivek Khera Cc: FreeBSD Stable List Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) Message-ID: <20000824162123.A80150@irrelevant.org> References: <200008241201.IAA32736@sanson.reyes.somos.net> <20000824080419.B51628@dazed.slacker.com> <14757.15655.515615.780499@onceler.kciLink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <14757.15655.515615.780499@onceler.kciLink.com>; from khera@kciLink.com on Thu, Aug 24, 2000 at 11:20:07AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 24, 2000 at 11:20:07AM -0400, Vivek Khera wrote: > >>>>> "DM" == David McNett writes: > > DM> If someone insists on using those antiquated and unsafe protocols like > DM> telnet and the r* services, we should at least make sure they're doing it > DM> on purpose and not just leaving the defaults in place out of ignorance. > > How do you make rdump/rmt work without the rcmd service? I've got a > LAN and do all backups of workstations to one server with a tape > drive. Without the rshd service, it won't work. > > You shouldn't claim people ignorant when there are no alternatives. > But please, prove me wrong. In that case just turn on the rshd from rc.conf, easy. -- Simon Dick simond@irrelevant.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 8:30:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lap1.sohara.org (pooh.elsevier.nl [145.36.13.27]) by hub.freebsd.org (Postfix) with ESMTP id 4699537B423 for ; Thu, 24 Aug 2000 08:30:25 -0700 (PDT) Received: (from steve@localhost) by lap1.sohara.org (8.9.3/8.9.3) id RAA01024; Thu, 24 Aug 2000 17:47:04 +0100 (IST) (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: <14757.15655.515615.780499@onceler.kciLink.com> Date: Thu, 24 Aug 2000 17:47:02 +0100 (IST) From: "Steve O'Hara-Smith" To: Vivek Khera Subject: RE: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes Cc: FreeBSD Stable List Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Aug-00 Vivek Khera wrote: > How do you make rdump/rmt work without the rcmd service? I've got a > LAN and do all backups of workstations to one server with a tape > drive. Without the rshd service, it won't work. I tend to use things based around: dump ... -f - | ssh ... Lots of additional arguments required of course. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 8:34: 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 B89E037B422 for ; Thu, 24 Aug 2000 08:34:02 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 5C574E89F for ; Thu, 24 Aug 2000 11:34:02 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.9.3/8.9.3) id LAA03657; Thu, 24 Aug 2000 11:34:02 -0400 (EDT) (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: <14757.16490.269381.416596@onceler.kciLink.com> Date: Thu, 24 Aug 2000 11:34:02 -0400 (EDT) To: FreeBSD Stable List Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) In-Reply-To: <20000824162123.A80150@irrelevant.org> References: <200008241201.IAA32736@sanson.reyes.somos.net> <20000824080419.B51628@dazed.slacker.com> <14757.15655.515615.780499@onceler.kciLink.com> <20000824162123.A80150@irrelevant.org> X-Mailer: VM 6.72 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "s" == simond writes: s> On Thu, Aug 24, 2000 at 11:20:07AM -0400, Vivek Khera wrote: >> >>>>> "DM" == David McNett writes: >> DM> If someone insists on using those antiquated and unsafe protocols like DM> telnet and the r* services, we should at least make sure they're doing it DM> on purpose and not just leaving the defaults in place out of ignorance. >> >> How do you make rdump/rmt work without the rcmd service? I've got a >> LAN and do all backups of workstations to one server with a tape >> drive. Without the rshd service, it won't work. s> In that case just turn on the rshd from rc.conf, easy. Yes, but then how does one ever eradicate "those antiquated and unsafe protocols" from the system? Is there a way to make rmt work without rshd? There will be a lot of unexpected breakage I'm sure. Perhaps it should be documented what normal use programs (like rdump/rrestore/tar using rmt) will break if you turn off certain services that are currently on by default. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 GPG & MIME spoken here http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 8:34: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 E4E6437B422 for ; Thu, 24 Aug 2000 08:34:40 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 8227EE89F for ; Thu, 24 Aug 2000 11:34:40 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.9.3/8.9.3) id LAA03661; Thu, 24 Aug 2000 11:34:40 -0400 (EDT) (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: <14757.16528.444156.103189@onceler.kciLink.com> Date: Thu, 24 Aug 2000 11:34:40 -0400 (EDT) To: FreeBSD Stable List Subject: RE: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes In-Reply-To: References: <14757.15655.515615.780499@onceler.kciLink.com> X-Mailer: VM 6.72 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "SO" == Steve O'Hara-Smith writes: SO> On 24-Aug-00 Vivek Khera wrote: >> How do you make rdump/rmt work without the rcmd service? I've got a >> LAN and do all backups of workstations to one server with a tape >> drive. Without the rshd service, it won't work. SO> I tend to use things based around: SO> dump ... -f - | ssh ... How does that detect end of tape and allow you to switch them? -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 GPG & MIME spoken here http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 8:35:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bumper.jellybaby.net (bumper.jellybaby.net [194.159.247.1]) by hub.freebsd.org (Postfix) with ESMTP id 05FA637B424 for ; Thu, 24 Aug 2000 08:35:36 -0700 (PDT) Received: (from simond@localhost) by bumper.jellybaby.net (8.9.2/8.9.2) id QAA83056; Thu, 24 Aug 2000 16:35:34 +0100 (BST) (envelope-from simond) Date: Thu, 24 Aug 2000 16:35:34 +0100 From: simond@irrelevant.org To: Vivek Khera Cc: FreeBSD Stable List Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) Message-ID: <20000824163533.B80150@irrelevant.org> References: <200008241201.IAA32736@sanson.reyes.somos.net> <20000824080419.B51628@dazed.slacker.com> <14757.15655.515615.780499@onceler.kciLink.com> <20000824162123.A80150@irrelevant.org> <14757.16490.269381.416596@onceler.kciLink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <14757.16490.269381.416596@onceler.kciLink.com>; from khera@kciLink.com on Thu, Aug 24, 2000 at 11:34:02AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 24, 2000 at 11:34:02AM -0400, Vivek Khera wrote: > >>>>> "s" == simond writes: > > s> On Thu, Aug 24, 2000 at 11:20:07AM -0400, Vivek Khera wrote: > >> >>>>> "DM" == David McNett writes: > >> > DM> If someone insists on using those antiquated and unsafe protocols like > DM> telnet and the r* services, we should at least make sure they're doing it > DM> on purpose and not just leaving the defaults in place out of ignorance. > >> > >> How do you make rdump/rmt work without the rcmd service? I've got a > >> LAN and do all backups of workstations to one server with a tape > >> drive. Without the rshd service, it won't work. > > s> In that case just turn on the rshd from rc.conf, easy. > > Yes, but then how does one ever eradicate "those antiquated and unsafe > protocols" from the system? Is there a way to make rmt work without > rshd? There will be a lot of unexpected breakage I'm sure. Perhaps > it should be documented what normal use programs (like > rdump/rrestore/tar using rmt) will break if you turn off certain > services that are currently on by default. Surely rmt could work over ssh? -- Simon Dick simond@irrelevant.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 8:45:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 5205337B422 for ; Thu, 24 Aug 2000 08:45:14 -0700 (PDT) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id RAA00742; Thu, 24 Aug 2000 17:45:13 +0200 (CEST) (envelope-from olli) Date: Thu, 24 Aug 2000 17:45:13 +0200 (CEST) Message-Id: <200008241545.RAA00742@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG Reply-To: freebsd-stable@FreeBSD.ORG Subject: Re: Numbering of fxp devices X-Newsgroups: list.freebsd-stable In-Reply-To: <8o3e6n$1sss$1@atlantis.rz.tu-clausthal.de> Organization: Administration TU Clausthal MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In list.freebsd-stable Fred Clift wrote: > only active interface. This actually hasn't been a terrible problem, but > it leads to confusion, especially with our new admins. The less > differences between boxes (even though the OS may be a different rev) the > better. Differences just lead to extra administrative effort and can lead > to problems. So, we seek to minimize visible differences like this. If > we had network interface aliases, then we could just set the alias and > then train our new sys-admins to always use the alias. Just an idea... You could check the MAC addresses upon booting (like the code that was posted earlier in this thread) and then assign physical interface names to "virtual" interface names (for example "eth0", "eth1", etc.) and write this to a configfile somewhere. Something like this (this is just a rough framework, and I haven't actually tested it): mv -f /etc/eth.conf /etc/eth.conf.old ifconfig -a \ | awk ' /^[a-z]/{ sub(":", ""); # get rid of ":" after iface name iface = $1; } /ether/{ print iface, $2; # print iface name and MAC addr }' \ | while read IFACE MAC; do case $MAC in 00:11:22:33:44:55) VIRT=eth0 eval ifconfig_$IFACE='"inet 10.20.30.40 netmask 0xffffff00"' ;; 66:77:88:99:aa:bb) VIRT=eth1 eval ifconfig_$IFACE='"inet 10.20.30.41 netmask 0xffffff00"' ;; ... *) echo "Unknown MAC address $MAC!!!" >&2 ;; esac echo $VIRT=$IFACE >> /etc/eth.conf done The above snippet will create a file /etc/eth.conf that contains lines like this: eth0=fxp1 eth1=fxp5 ... So you can just source that file and then use commands like ifconfig $eth0 inet foobar ... tcpdump -e -l -v -i $eth1 host baz etc... You can even change that snipped to use a config file that contains information about which MAC address should be what eth* name, so you don't have to "hardcode" that in the script. You could even distribute that mapping via NIS, so you can maintain that mapping on a central server for all machines. Uhm, thinking about it, this would require a working network before the interfaces are actually configured, so forget about that NIS idea. :-) Oh by the way, putting such script code into /etc/rc.conf is a rather bad idea. That file should only contain variable assignments, but not actual shell statements. Having said that, I don't know a place that's much better to put such things. It has to be after / has been mounted r/w, but before rc.network is executed. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) Addresses will change soon!! If in doubt: www.fromme.com "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 8:46:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lap1.sohara.org (pooh.elsevier.nl [145.36.13.27]) by hub.freebsd.org (Postfix) with ESMTP id 945B037B423 for ; Thu, 24 Aug 2000 08:46:21 -0700 (PDT) Received: (from steve@localhost) by lap1.sohara.org (8.9.3/8.9.3) id SAA01069; Thu, 24 Aug 2000 18:03:14 +0100 (IST) (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: <14757.16528.444156.103189@onceler.kciLink.com> Date: Thu, 24 Aug 2000 18:03:13 +0100 (IST) From: "Steve O'Hara-Smith" To: Vivek Khera Subject: RE: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes Cc: FreeBSD Stable List Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Aug-00 Vivek Khera wrote: > How does that detect end of tape and allow you to switch them? Good point, not one I've had to worry about. I don't know if the 'end of media indication' will make it through an ssh connection. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 8:51:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from c1030098-a.wtrlo1.ia.home.com (c1030098-a.wtrlo1.ia.home.com [24.14.126.45]) by hub.freebsd.org (Postfix) with ESMTP id 4828437B423; Thu, 24 Aug 2000 08:51:23 -0700 (PDT) Received: (from mdharnois@localhost) by c1030098-a.wtrlo1.ia.home.com (8.11.0/8.11.0) id e7OFpOZ55349; Thu, 24 Aug 2000 10:51:24 -0500 (CDT) (envelope-from mdharnois@home.com) X-Authentication-Warning: mharnois.workgroup.net: mdharnois set sender to mdharnois@home.com using -f To: Allen Landsidel Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: cyrus imapd problems resolved.. References: <4.3.2.7.2.20000824082639.00afffb8@mail.megapathdsl.net> From: Michael Harnois Date: 24 Aug 2000 10:51:24 -0500 In-Reply-To: Allen Landsidel's message of "Thu, 24 Aug 2000 08:45:39 -0400" Message-ID: <86g0nuk683.fsf@mharnois.workgroup.net> Lines: 30 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.2 (Nike) 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, 24 Aug 2000 08:45:39 -0400, Allen Landsidel said: > After installation of the port, the user needs to run > /usr/local/sbin/saslpasswd to create an entry in the sasl > password database. The user they create (just to get things > going here) should also have their name listed as an "admin" in > imapd.conf. I believe the docs suggest somewhere that the admin user should not be any normal user who receives mail. I use "cyrus." > I only mention this because the Cyrus documentation REALLY SUCKS > and it was only after hours of scouring usenet that I came > across this tidbit posted in an OpenBSD newsgroup where someone > else was having similar problems. Every time I've upgraded I've gone through hell. Thanks for working on this. Oh, another thing (in case anyone is listening) ... a make deinstall deletes the database index of the existing IMAP store. This is not a good thing, IMHO. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org I have always been among those who believed that the greatest freedom of speech was the greatest safety, because if a man is a fool the best thing to do is to encourage him to advertise the fact by speaking. --Woodrow Wilson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 8:54:46 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 B393A37B43C for ; Thu, 24 Aug 2000 08:54:41 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 3E1ABE8D1 for ; Thu, 24 Aug 2000 11:54:41 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.9.3/8.9.3) id LAA03730; Thu, 24 Aug 2000 11:54:41 -0400 (EDT) (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: <14757.17729.113055.693358@onceler.kciLink.com> Date: Thu, 24 Aug 2000 11:54:41 -0400 (EDT) To: FreeBSD Stable List Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) In-Reply-To: <20000824163533.B80150@irrelevant.org> References: <200008241201.IAA32736@sanson.reyes.somos.net> <20000824080419.B51628@dazed.slacker.com> <14757.15655.515615.780499@onceler.kciLink.com> <20000824162123.A80150@irrelevant.org> <14757.16490.269381.416596@onceler.kciLink.com> <20000824163533.B80150@irrelevant.org> X-Mailer: VM 6.72 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "s" == simond writes: s> Surely rmt could work over ssh? Apparently not with its current implementation. It also must fallback to using rcmd(3) for compatibility with other systems, if one were to implement the ssh layer. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 GPG & MIME spoken here http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 9: 2: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-5-249.zoominternet.net [24.154.5.249]) by hub.freebsd.org (Postfix) with ESMTP id 943A337B424 for ; Thu, 24 Aug 2000 09:02:01 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by topperwein.dyndns.org (8.9.3/8.9.3) with ESMTP id MAA09248; Thu, 24 Aug 2000 12:01:24 -0400 (EDT) (envelope-from behanna@zbzoom.net) Date: Thu, 24 Aug 2000 12:01:24 -0400 (EDT) From: Chris BeHanna Reply-To: behanna@zbzoom.net To: Neil Blakey-Milner Cc: Francisco Reyes , FreeBSD Stable List Subject: Re: Upcoming rc.conf changes not loading certain currently loaded daemons In-Reply-To: <20000824150715.A24874@mithrandr.moria.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 Thu, 24 Aug 2000, Neil Blakey-Milner wrote: > On Thu 2000-08-24 (01:03), Francisco Reyes wrote: > > What was the reason for these daemons been set to not start? > > Wouldn't this "break" working machines? > > Only if you upgrade without reading the heads-up and warnings in > UPDATING. > > The reason was to make things more obvious. If you have an empty > /etc/rc.conf, you don't expect portmap and inetd to be running. > > (and when I'm through with it, sendmail won't be listening on port 25 by > default either *evil.grin*) Won't that break things, though? Doesn't every other MTA in the world expect to send its SMTP traffic over port 25? If the answer is "no," then I'm very excited, because my ISP blocks ports 1-1024. -- Chris BeHanna Software Engineer (at yourfit.com) behanna@zbzoom.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 9: 4:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (Postfix) with ESMTP id 2AF1237B43E for ; Thu, 24 Aug 2000 09:04:17 -0700 (PDT) Received: from tundra.winternet.com (nrahlstr@tundra.winternet.com [198.174.169.11]) by icicle.winternet.com (8.9.3/8.9.3mc) with ESMTP id LAA03750; Thu, 24 Aug 2000 11:04:16 -0500 (CDT) SMTP "HELO" (ESMTP) greeting from tundra.winternet.com But _really_ from :: nrahlstr@tundra.winternet.com [198.174.169.11] SMTP "MAIL From" = nrahlstr@mail.winternet.com (Nathan Ahlstrom) SMTP "RCPT To" = Received: (from nrahlstr@localhost) by tundra.winternet.com (8.8.7/8.8.4) id LAA13326; Thu, 24 Aug 2000 11:04:15 -0500 (CDT) Date: Thu, 24 Aug 2000 11:04:15 -0500 From: Nathan Ahlstrom To: Vivek Khera Cc: FreeBSD Stable List Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) Message-ID: <20000824110414.C12752@winternet.com> Mail-Followup-To: Vivek Khera , FreeBSD Stable List References: <200008241201.IAA32736@sanson.reyes.somos.net> <20000824080419.B51628@dazed.slacker.com> <14757.15655.515615.780499@onceler.kciLink.com> <20000824162123.A80150@irrelevant.org> <14757.16490.269381.416596@onceler.kciLink.com> <20000824163533.B80150@irrelevant.org> <14757.17729.113055.693358@onceler.kciLink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <14757.17729.113055.693358@onceler.kciLink.com>; from khera@kciLink.com on Thu, Aug 24, 2000 at 11:54:41AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vivek Khera wrote: > >>>>> "s" == simond writes: > > s> Surely rmt could work over ssh? > > Apparently not with its current implementation. It also must fallback > to using rcmd(3) for compatibility with other systems, if one were to > implement the ssh layer. This PR may be of interest. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=15830 -- Nathan Ahlstrom / nrahlstr@winternet.com / nra@FreeBSD.org / PGP: 0x67BC9D19 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 9: 8:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from axolotl.ic.gc.ca (axolotl.ic.gc.ca [198.103.246.251]) by hub.freebsd.org (Postfix) with ESMTP id 3392037B422 for ; Thu, 24 Aug 2000 09:08:48 -0700 (PDT) Received: from localhost (antonio@localhost) by axolotl.ic.gc.ca (8.9.3/8.9.2) with SMTP id MAA55206; Thu, 24 Aug 2000 12:08:42 -0400 (EDT) (envelope-from antonio@axolotl.ic.gc.ca) Date: Thu, 24 Aug 2000 12:08:42 -0400 (EDT) From: Antonio Bemfica To: Vivek Khera Cc: FreeBSD Stable List Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) In-Reply-To: <14757.15655.515615.780499@onceler.kciLink.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, 24 Aug 2000, Vivek Khera wrote: > [..] How do you make rdump/rmt work without the rcmd service? I've got > a LAN and do all backups of workstations to one server with a tape > drive. Without the rshd service, it won't work. > > You shouldn't claim people ignorant when there are no alternatives. > But please, prove me wrong. [...] Have you considered amanda for your backups? It is in the ports. A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 9: 9:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from citadel.cequrux.com (citadel.cequrux.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id 0C07B37B423 for ; Thu, 24 Aug 2000 09:09:08 -0700 (PDT) Received: (from nobody@localhost) by citadel.cequrux.com (8.8.8/8.6.9) id SAA24896 for ; Thu, 24 Aug 2000 18:09:05 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 24814; Thu Aug 24 18:08:44 2000 Message-ID: <39A5493E.B130936C@cequrux.com> Date: Thu, 24 Aug 2000 18:11:42 +0200 From: Graham Wheeler Organization: Cequrux Technologies X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 2.2.8-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Requesting input for a handbook section entry Content-Type: multipart/mixed; boundary="------------069F5FA767340AFAE3E3409F" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------069F5FA767340AFAE3E3409F Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi all Following up on my query on ISA card configuration, I have written up a section for the Handbook on this. It's brief, may have inaccuracies, and certainly has ommisions. I have put comments in upper case enclosed in square braces for the areas that definitely need peer review/completion. Can peeps have a look at this, and send me comments, so that I can complete it and submit it to the doccie folks? Thanks gram -- Dr Graham Wheeler E-mail: gram@cequrux.com Director, Research and Development WWW: http://www.cequrux.com CEQURUX Technologies Phone: +27(21)423-6065 Firewalls/VPN Specialists Fax: +27(21)424-3656 --------------069F5FA767340AFAE3E3409F Content-Type: text/plain; charset=us-ascii; name="config.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="config.txt" Configuring An Already Compiled Kernel If you don't want to create a custom kernel, you can configure many hardware settings without doing so, by putting them in the /boot/kernel.conf file. This file contains a sequence of commands compatible with those that are supported by the kernel configuration editor (which you may have seen when you first installed FreeBSD, and which is also accessible by booting with a `-c' argument). Because the commands in this file are essentially fed to the kernel configuration editor, it is important to have the last command in the file be `q' for `quit'. [IS THE LAST SENTENCE TRUE? READING userconfig.c IT APPEARS THAT AN IMPLICIT QUIT WILL BE DONE IF NO `q' COMMAND IS PRESENT...] The commands that the kernel configuration editor understands are: di(sable) Disable device en(able) Enable device dr(q) Set DMA channel for device to ei(sa) Set number of EISA slots to probe f(lags) Set the device-specific flags for the device iom(em)
Sets the base address of the I/O memory ios(ize) Sets the size of the I/O memory ir(q) Set the IRQ for the device pn(p) enable Enable device pn(p) disable Disable device pn(p) os Set parameters using FreeBSD pn(p) bios Set parameters using BIOS pn(p) portX Set addr for port X (0..7) pn(p) memX Set addr for memory range X (0..3) pn(p) irqX Set irq X (0..1) to number, 0=unused pn(p) drqX Set drq X (0..1) to number, 4=unused po(rt) Set the I/O port base address for the device ex Exit (quit) q Quit The commands are shown with their full names, and the optional parts parenthesised. Thus, for example, the "enable" command can be abbreviated to "en". There are other commands, for example to list the devices or reset the CPU, but these only make sense when using the interactive editor, and not when using kernel.conf. , , ,
, are all numeric arguments. They can be either decimal numbers, or hexadecimal numbers (in which case they must be prefixed by "0x"). For Plug 'n' Play devices, is the slot number and the logical device number. [I'M JUST MAKING THIS UP; I HAVEN'T A CLUE REALLY WHAT THESE ARE; SOMEONE PLEASE ENLIGHTEN ME!] Here is a simple example, which sets the interrupt and port for device ed0 to be irq 10, port 0x320: irq ed0 10 port ed0 0x320 q --------------069F5FA767340AFAE3E3409F-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 9:20:28 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 679F637B424 for ; Thu, 24 Aug 2000 09:20:26 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id A9F1AE89F for ; Thu, 24 Aug 2000 12:20:25 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.9.3/8.9.3) id MAA04690; Thu, 24 Aug 2000 12:20:25 -0400 (EDT) (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: <14757.19273.536040.643538@onceler.kciLink.com> Date: Thu, 24 Aug 2000 12:20:25 -0400 (EDT) To: FreeBSD Stable List Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) In-Reply-To: <20000824110414.C12752@winternet.com> References: <200008241201.IAA32736@sanson.reyes.somos.net> <20000824080419.B51628@dazed.slacker.com> <14757.15655.515615.780499@onceler.kciLink.com> <20000824162123.A80150@irrelevant.org> <14757.16490.269381.416596@onceler.kciLink.com> <20000824163533.B80150@irrelevant.org> <14757.17729.113055.693358@onceler.kciLink.com> <20000824110414.C12752@winternet.com> X-Mailer: VM 6.72 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "NA" == Nathan Ahlstrom writes: NA> Vivek Khera wrote: >> >>>>> "s" == simond writes: >> s> Surely rmt could work over ssh? >> >> Apparently not with its current implementation. It also must fallback >> to using rcmd(3) for compatibility with other systems, if one were to >> implement the ssh layer. NA> This PR may be of interest. NA> http://www.FreeBSD.org/cgi/query-pr.cgi?pr=15830 Wow! If voting is considered, I vote for such a patch to be included. It makes sense considering that ssh is now part of the core system. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 GPG & MIME spoken here http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 9:21:39 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 9674F37B42C for ; Thu, 24 Aug 2000 09:21:35 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 1AB38E89F for ; Thu, 24 Aug 2000 12:21:35 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.9.3/8.9.3) id MAA04701; Thu, 24 Aug 2000 12:21:35 -0400 (EDT) (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: <14757.19342.974674.10754@onceler.kciLink.com> Date: Thu, 24 Aug 2000 12:21:34 -0400 (EDT) To: FreeBSD Stable List Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) In-Reply-To: References: <14757.15655.515615.780499@onceler.kciLink.com> X-Mailer: VM 6.72 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "AB" == Antonio Bemfica writes: AB> Have you considered amanda for your backups? It is in the ports. Does it avoid using rcmd/rsh? I looked at it a long time ago, but my manual scheme worked well enough for the small handful of hosts I need to backup. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 9:31:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gatekeeper.whistle.com (gatekeeper.whistle.com [207.76.204.2]) by hub.freebsd.org (Postfix) with ESMTP id 39E4237B423 for ; Thu, 24 Aug 2000 09:31:15 -0700 (PDT) Received: from pau-amma.whistle.com (pau-amma.whistle.com [207.76.205.64]) by gatekeeper.whistle.com (8.9.3/8.9.3) with ESMTP id JAA18645; Thu, 24 Aug 2000 09:30:45 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.3/8.9.3) id JAA40385; Thu, 24 Aug 2000 09:30:45 -0700 (PDT) (envelope-from dhw) Date: Thu, 24 Aug 2000 09:30:45 -0700 (PDT) From: David Wolfskill Message-Id: <200008241630.JAA40385@pau-amma.whistle.com> To: freebsd-stable@FreeBSD.ORG, khera@kciLink.com Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) In-Reply-To: <14757.19342.974674.10754@onceler.kciLink.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: Vivek Khera >Date: Thu, 24 Aug 2000 12:21:34 -0400 (EDT) >AB> Have you considered amanda for your backups? It is in the ports. >Does it avoid using rcmd/rsh? Yes; it uses its own protocol. (It can use .rhosts for "authentication", but current versions default to using a separate file, .amandahosts for that. It also uses its own UDP & TCP ports.) >I looked at it a long time ago, but my manual scheme worked well >enough for the small handful of hosts I need to backup. There may be other reasons to prefer such a scheme; for example, amanda does not append one day's run to another's; this is a design decision based on the concern that an inopportune event could cause what amanda thinks is an "append" to actually become an "overwrite"... thus destroying the integrity of some (or all) of the backups images on the tape in question. There are some folks working on approaches for permitting such appending, but like FreeBSD, it's a volunteer project, and the usual concerns regarding expectations of results are in order. Cheers, david (who uses amanda at work, and a home-grown script at home) -- David Wolfskill dhw@whistle.com UNIX System Administrator Desk: 650/577-7158 TIE: 8/499-7158 Cell: 650/759-0823 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 10:11:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from forrie.net (forrie.net [64.20.73.233]) by hub.freebsd.org (Postfix) with ESMTP id 9029837B43C for ; Thu, 24 Aug 2000 10:11:50 -0700 (PDT) Received: from forrie.forrie.com (dhcp-north-71-168.navipath.net [64.20.71.168]) by forrie.net with id e7OHBhs74020 for ; Thu, 24 Aug 2000 13:11:49 -0400 (EDT) Message-Id: <4.3.2.7.2.20000824130433.00c8eba0@64.20.73.233> X-Sender: forrie@64.20.73.233 X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 24 Aug 2000 13:06:30 -0400 To: freebsd-stable@freebsd.org From: Forrest Aldrich Subject: Installation NIC media selection (fxp0) on 4.1-STABLE 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 noted that with 4.1 stable (as of snapshot 0822) does not seem to set the media type on the NIC properly. This is what we've arrived at, after checking lots of other things (like switch ports, etc). Basically, what happens is that the NIC (fxp0) is configured, and it will connect and transfer files locally, but the throughput ends up being 12.x kb/sec.... horrific. BUT, it seems fine after the system is installed and rebooted. Anyone else note this problem? _F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 10:20: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-5-249.zoominternet.net [24.154.5.249]) by hub.freebsd.org (Postfix) with ESMTP id 8514437B422 for ; Thu, 24 Aug 2000 10:20:05 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by topperwein.dyndns.org (8.9.3/8.9.3) with ESMTP id NAA09512; Thu, 24 Aug 2000 13:21:39 -0400 (EDT) (envelope-from behanna@zbzoom.net) Date: Thu, 24 Aug 2000 13:21:39 -0400 (EDT) From: Chris BeHanna Reply-To: behanna@zbzoom.net To: Vivek Khera Cc: FreeBSD Stable List Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) In-Reply-To: <14757.15655.515615.780499@onceler.kciLink.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, 24 Aug 2000, Vivek Khera wrote: > >>>>> "DM" == David McNett writes: > > DM> If someone insists on using those antiquated and unsafe protocols like > DM> telnet and the r* services, we should at least make sure they're doing it > DM> on purpose and not just leaving the defaults in place out of ignorance. > > How do you make rdump/rmt work without the rcmd service? I've got a > LAN and do all backups of workstations to one server with a tape > drive. Without the rshd service, it won't work. Execute something like the following on the host that has the tape drive, where "remotehost" is the machine you want to back up: ssh user@remotehost "tar cvf - dir | gzip -c" | dd of=/dev/nsa0 bs=8k Your remote command could be a script of some kind. As long as it writes the archive to stdout, you can pipe it through ssh and send it wherever you like. -- Chris BeHanna Software Engineer (at yourfit.com) behanna@zbzoom.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 10:26:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id C2D1A37B424; Thu, 24 Aug 2000 10:26:39 -0700 (PDT) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e7OHQXW04754 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Thu, 24 Aug 2000 19:26:36 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e7OHQlq82861; Thu, 24 Aug 2000 19:26:48 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id TAA30136; Thu, 24 Aug 2000 19:26:43 +0200 (CEST) (envelope-from ticso) Date: Thu, 24 Aug 2000 19:26:42 +0200 From: Bernd Walter To: Theo PAGTZIS Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: help with restoring sh Message-ID: <20000824192642.B30092@cicely8.cicely.de> References: <39A4DDE1.17DFE7DC@cs.ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <39A4DDE1.17DFE7DC@cs.ucl.ac.uk>; from T.Pagtzis@cs.ucl.ac.uk on Thu, Aug 24, 2000 at 09:33:37AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 24, 2000 at 09:33:37AM +0100, Theo PAGTZIS wrote: > Hi all, > > I have been upgrading from 3.4 to 4.1 and during the reboot I get a > permission denied when it tries to exec the /bin/sh. I am trying to > restore the file with one that is functioning properly..however I do not > know how I should go about correcting my problem. I would appreciate any > help as I am stranded with a server that is down at the moment... With boot -s you on the loader prompt you can boot into single user mode. If asked for the shell to start try /bin/csh which is a different shell and then fix your problem. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 10:29: 5 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 0E9A937B422 for ; Thu, 24 Aug 2000 10:29:01 -0700 (PDT) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.10.1/8.10.1) with ESMTP id e7OHSxX27241 for ; Thu, 24 Aug 2000 13:28:59 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id NAA34868 for ; Thu, 24 Aug 2000 13:28:57 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id NAA78833 for freebsd-stable@freebsd.org; Thu, 24 Aug 2000 13:28:57 -0400 (EDT) Date: Thu, 24 Aug 2000 13:28:57 -0400 (EDT) From: Thomas David Rivers Message-Id: <200008241728.NAA78833@lakes.dignus.com> To: freebsd-stable@freebsd.org Subject: 4.1-RELEASE & Netscape (aout libraries) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that a fresh/clean install of 4.1-RELEASE didn't install the aout libraries. (/usr/lib/aout is empty) Thus, installing Netscape results in something that can't find libXt.so.6.0. Any idea about how/where to find the aout X11 libraries? [Also, I suppose the other aout libraries...] - Thanks - - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 10:29:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-5-249.zoominternet.net [24.154.5.249]) by hub.freebsd.org (Postfix) with ESMTP id 762BF37B423 for ; Thu, 24 Aug 2000 10:29:39 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by topperwein.dyndns.org (8.9.3/8.9.3) with ESMTP id NAA09556; Thu, 24 Aug 2000 13:31:03 -0400 (EDT) (envelope-from behanna@zbzoom.net) Date: Thu, 24 Aug 2000 13:31:03 -0400 (EDT) From: Chris BeHanna Reply-To: behanna@zbzoom.net To: Graham Wheeler Cc: freebsd-stable@freebsd.org Subject: Re: Requesting input for a handbook section entry In-Reply-To: <39A5493E.B130936C@cequrux.com> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/Mixed; BOUNDARY=------------069F5FA767340AFAE3E3409F Content-ID: 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. --------------069F5FA767340AFAE3E3409F Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: On Thu, 24 Aug 2000, Graham Wheeler wrote: > Hi all > > Following up on my query on ISA card configuration, I have written up a > section for the Handbook on this. It's brief, may have inaccuracies, and > certainly has ommisions. I have put comments in upper case enclosed in > square braces for the areas that definitely need peer review/completion. > Can peeps have a look at this, and send me comments, so that I can > complete it and submit it to the doccie folks? I thought the pnp command went away in 4.x. Is it back for 4.1? -- Chris BeHanna Software Engineer (at yourfit.com) behanna@zbzoom.net --------------069F5FA767340AFAE3E3409F Content-Type: TEXT/PLAIN; CHARSET=us-ascii; NAME="config.txt" Content-ID: Content-Description: Content-Disposition: INLINE; FILENAME="config.txt" Configuring An Already Compiled Kernel If you don't want to create a custom kernel, you can configure many hardware settings without doing so, by putting them in the /boot/kernel.conf file. This file contains a sequence of commands compatible with those that are supported by the kernel configuration editor (which you may have seen when you first installed FreeBSD, and which is also accessible by booting with a `-c' argument). Because the commands in this file are essentially fed to the kernel configuration editor, it is important to have the last command in the file be `q' for `quit'. [IS THE LAST SENTENCE TRUE? READING userconfig.c IT APPEARS THAT AN IMPLICIT QUIT WILL BE DONE IF NO `q' COMMAND IS PRESENT...] The commands that the kernel configuration editor understands are: di(sable) Disable device en(able) Enable device dr(q) Set DMA channel for device to ei(sa) Set number of EISA slots to probe f(lags) Set the device-specific flags for the device iom(em)
Sets the base address of the I/O memory ios(ize) Sets the size of the I/O memory ir(q) Set the IRQ for the device pn(p) enable Enable device pn(p) disable Disable device pn(p) os Set parameters using FreeBSD pn(p) bios Set parameters using BIOS pn(p) portX Set addr for port X (0..7) pn(p) memX Set addr for memory range X (0..3) pn(p) irqX Set irq X (0..1) to number, 0=unused pn(p) drqX Set drq X (0..1) to number, 4=unused po(rt) Set the I/O port base address for the device ex Exit (quit) q Quit The commands are shown with their full names, and the optional parts parenthesised. Thus, for example, the "enable" command can be abbreviated to "en". There are other commands, for example to list the devices or reset the CPU, but these only make sense when using the interactive editor, and not when using kernel.conf. , , ,
, are all numeric arguments. They can be either decimal numbers, or hexadecimal numbers (in which case they must be prefixed by "0x"). For Plug 'n' Play devices, is the slot number and the logical device number. [I'M JUST MAKING THIS UP; I HAVEN'T A CLUE REALLY WHAT THESE ARE; SOMEONE PLEASE ENLIGHTEN ME!] Here is a simple example, which sets the interrupt and port for device ed0 to be irq 10, port 0x320: irq ed0 10 port ed0 0x320 q --------------069F5FA767340AFAE3E3409F-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 10:33:38 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 10A0237B422 for ; Thu, 24 Aug 2000 10:33:34 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 740DCE89F for ; Thu, 24 Aug 2000 13:33:33 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.9.3/8.9.3) id NAA65880; Thu, 24 Aug 2000 13:33:33 -0400 (EDT) (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: <14757.23661.361639.463861@onceler.kciLink.com> Date: Thu, 24 Aug 2000 13:33:33 -0400 (EDT) To: freebsd-stable@freebsd.org Subject: Re: 4.1-RELEASE & Netscape (aout libraries) In-Reply-To: <200008241728.NAA78833@lakes.dignus.com> References: <200008241728.NAA78833@lakes.dignus.com> X-Mailer: VM 6.72 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "TDR" == Thomas David Rivers writes: TDR> It seems that a fresh/clean install of 4.1-RELEASE didn't TDR> install the aout libraries. (/usr/lib/aout is empty) TDR> Thus, installing Netscape results in something that can't find TDR> libXt.so.6.0. TDR> Any idea about how/where to find the aout X11 libraries? Yes. During install (or make installworld) select the FreeBSD 2.2 compatibility libraries for installation. This installs the necessary a.out system libs you need to run netscape (the package system will install the necessary X11 a.out libraries if it finds the 2.2 a.out system libs). However, this compatibility does not install /usr/lib/aout/c++rt0.o which is necessary for compiling a.out binaries (such as the plugger port, which links into netscape). For this, you need to pull it off of a 2.2.x binary distribution, as discussed here two days ago. Now, let's just convince Netscape to build a native 4.1 binary, eh? ;-) -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 GPG & MIME spoken here http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 10:36: 9 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 B15D737B424 for ; Thu, 24 Aug 2000 10:36:07 -0700 (PDT) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.10.1/8.10.1) with ESMTP id e7OHa5429198; Thu, 24 Aug 2000 13:36:05 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id NAA34893; Thu, 24 Aug 2000 13:36:04 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id NAA78958; Thu, 24 Aug 2000 13:36:04 -0400 (EDT) Date: Thu, 24 Aug 2000 13:36:04 -0400 (EDT) From: Thomas David Rivers Message-Id: <200008241736.NAA78958@lakes.dignus.com> To: freebsd-stable@FreeBSD.ORG, khera@kciLink.com Subject: Re: 4.1-RELEASE & Netscape (aout libraries) In-Reply-To: <14757.23661.361639.463861@onceler.kciLink.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vivek Khera wrote: > > >>>>> "TDR" == Thomas David Rivers writes: > > TDR> It seems that a fresh/clean install of 4.1-RELEASE didn't > TDR> install the aout libraries. (/usr/lib/aout is empty) > > > TDR> Thus, installing Netscape results in something that can't find > TDR> libXt.so.6.0. > > TDR> Any idea about how/where to find the aout X11 libraries? > > Yes. During install (or make installworld) select the FreeBSD 2.2 > compatibility libraries for installation. > > This installs the necessary a.out system libs you need to run netscape > (the package system will install the necessary X11 a.out libraries if > it finds the 2.2 a.out system libs). > > However, this compatibility does not install /usr/lib/aout/c++rt0.o > which is necessary for compiling a.out binaries (such as the plugger > port, which links into netscape). For this, you need to pull it off > of a 2.2.x binary distribution, as discussed here two days ago. > > Now, let's just convince Netscape to build a native 4.1 binary, eh? > ;-) > Hmm... I'm pretty sure I did select all of the compat options in sysinstall when I did the install... (is there a way, after the fact now, to see if I actually did, or if I'm simply mis-remembering, or, maybe - "missed" one of these?) - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 10:46:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cfdnet.me.tuns.ca (CFDnet.me.TUNS.Ca [134.190.50.164]) by hub.freebsd.org (Postfix) with ESMTP id 7AB3437B424 for ; Thu, 24 Aug 2000 10:46:55 -0700 (PDT) Received: from localhost (freebsd@localhost) by cfdnet.me.tuns.ca (8.9.3/8.9.3) with ESMTP id OAA45639; Thu, 24 Aug 2000 14:46:31 -0300 (ADT) (envelope-from freebsd@cfdnet.me.tuns.ca) Date: Thu, 24 Aug 2000 14:46:31 -0300 (ADT) From: Theo Bell To: Thomas David Rivers Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 4.1-RELEASE & Netscape (aout libraries) In-Reply-To: <200008241728.NAA78833@lakes.dignus.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 Hi, There is a port for the aout libraries: cd /usr/ports/x11/XFree86-aoutlibs make make install make clean That should get netscape up and running for you. HTH Theo On Thu, 24 Aug 2000, Thomas David Rivers wrote: > > It seems that a fresh/clean install of 4.1-RELEASE didn't > install the aout libraries. (/usr/lib/aout is empty) > > > Thus, installing Netscape results in something that can't find > libXt.so.6.0. > > Any idea about how/where to find the aout X11 libraries? > > [Also, I suppose the other aout libraries...] > > - Thanks - > - Dave Rivers - > > > 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 Aug 24 11:17:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gilmore.nas.nasa.gov (gilmore.nas.nasa.gov [129.99.32.17]) by hub.freebsd.org (Postfix) with ESMTP id 2DF4637B422 for ; Thu, 24 Aug 2000 11:17:26 -0700 (PDT) Received: from gilmore.nas.nasa.gov (tweten@localhost.nas.nasa.gov [127.0.0.1]) by gilmore.nas.nasa.gov (8.8.8/8.8.8) with ESMTP id LAA04262; Thu, 24 Aug 2000 11:16:58 -0700 (PDT) (envelope-from tweten@gilmore.nas.nasa.gov) Message-Id: <200008241816.LAA04262@gilmore.nas.nasa.gov> X-Mailer: exmh version 2.0.2 2/24/98 Reply-To: tweten@nas.nasa.gov To: David McNett Cc: FreeBSD Stable List Subject: Re: Upcoming rc.conf changes not loading certain currently loaded daemons From: Dave Tweten Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Aug 2000 11:16:57 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG nugget@slacker.com said: >If someone insists on using those antiquated and unsafe protocols like >telnet and the r* services, we should at least make sure they're doing >it on purpose and not just leaving the defaults in place out of >ignorance. So, just what is it you have against using OPIE? -- M/S 258-5 | 1024-bit PGP fingerprint: | tweten@nas.nasa.gov NASA Ames Research Center | 41 B0 89 0A 8F 94 6C 59 | (650) 604-4416 Moffett Field, CA 94035-1000 | 7C 80 10 20 25 C7 2F E6 | FAX: (650) 604-4377 We each earn what freedom of speech we defend for those who most offend us. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 11:47:34 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 7DF3C37B43C for ; Thu, 24 Aug 2000 11:47:29 -0700 (PDT) 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 MAA71646; Thu, 24 Aug 2000 12:47:27 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA11371; Thu, 24 Aug 2000 12:47:25 -0600 (MDT) Message-Id: <200008241847.MAA11371@harmony.village.org> To: Daniel Frazier Subject: Re: Trouble upgrading from 3.5-S to 4.1-S... Cc: "Sean O'Connell" , freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Wed, 23 Aug 2000 10:31:18 EDT." <39A3E036.9C43E0CA@magpage.com> References: <39A3E036.9C43E0CA@magpage.com> <39A3D197.914762C7@magpage.com> <20000823101520.A4478@stat.Duke.EDU> Date: Thu, 24 Aug 2000 12:47:25 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39A3E036.9C43E0CA@magpage.com> Daniel Frazier writes: : Niiiice!!! Everything was just as you said. Thanks Sean, you're right, UPDATING : needs to be updated... Several people have sent this update to me. I've just updated it. Sorry for the delay. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 12:57:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from envy.vuurwerk.nl (envy.vuurwerk.nl [194.178.232.112]) by hub.freebsd.org (Postfix) with SMTP id E999C37B42C for ; Thu, 24 Aug 2000 12:57:55 -0700 (PDT) Received: (qmail 188 invoked from network); 24 Aug 2000 19:58:42 -0000 Received: from kesteren.vuurwerk.nl (HELO daemon.vuurwerk.nl) (194.178.232.59) by envy.vuurwerk.nl with SMTP; 24 Aug 2000 19:58:42 -0000 Received: (nullmailer pid 19671 invoked by uid 11109); Thu, 24 Aug 2000 15:31:12 -0000 Date: Thu, 24 Aug 2000 17:31:11 +0200 From: Peter van Dijk To: FreeBSD Stable List Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) Message-ID: <20000824173111.G8936@vuurwerk.nl> Mail-Followup-To: Peter van Dijk , FreeBSD Stable List References: <200008241201.IAA32736@sanson.reyes.somos.net> <20000824080419.B51628@dazed.slacker.com> <14757.15655.515615.780499@onceler.kciLink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14757.15655.515615.780499@onceler.kciLink.com>; from khera@kciLink.com on Thu, Aug 24, 2000 at 11:20:07AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 24, 2000 at 11:20:07AM -0400, Vivek Khera wrote: > >>>>> "DM" == David McNett writes: > > DM> If someone insists on using those antiquated and unsafe protocols like > DM> telnet and the r* services, we should at least make sure they're doing it > DM> on purpose and not just leaving the defaults in place out of ignorance. > > How do you make rdump/rmt work without the rcmd service? I've got a > LAN and do all backups of workstations to one server with a tape > drive. Without the rshd service, it won't work. > > You shouldn't claim people ignorant when there are no alternatives. > But please, prove me wrong. He's specifically saying you are *not* ignorant. *most* people that have these services are ignorant. You are in the 'on purpose' category he mentions and there is no insult whatsoever towards that group. Greetz, Peter. -- [ircoper] petervd@vuurwerk.nl - Peter van Dijk / Hardbeat [student] Undernet:#groningen/wallops | IRCnet:/#alliance [developer] _____________ [disbeliever - the world is backwards] (__VuurWerk__(--*- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 13:18:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id CCC4F37B42C for ; Thu, 24 Aug 2000 13:18:31 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id NAA53651; Thu, 24 Aug 2000 13:18:20 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200008242018.NAA53651@pike.osd.bsdi.com> Subject: Re: HEADSUP: 4.1S installworld broken In-Reply-To: <200008240729.RAA07747@drugs.dv.isc.org> from "Mark.Andrews@nominum.com" at "Aug 24, 2000 05:29:43 pm" To: Mark.Andrews@nominum.com Date: Thu, 24 Aug 2000 13:18:20 -0700 (PDT) Cc: stable@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 Mark.Andrews@nominum.com wrote: > > > Mark.Andrews@nominum.com wrote: > > > > > > STRICTTMPPATH does not contain cp/ > > > > > > ===> gnu/usr.bin/binutils/doc > > > cp -p /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/instal > > l.sh > > > install > > > cp:No such file or directory > > > *** Error code 1 > > > > Grrr, it worked here during my test build and install. :( You should just > > be able to add 'cp' to the list of files to copy in the 'installworld' > > target in src/Makefile.inc1. I'll try it again to see if I can reproduce > > the breakage. > > That should fix it. My full build environment is in pr=20815. > I worked around the problem but felt a HEADSUP was warranted. > > Mark Hmm, I haven't been able to reproduce this problem: [12:57:47] (ttyp8) jhb@foo:...src/release/sysinstall > dir /tmp/install.74661/cp ls: /tmp/install.74661/cp: No such file or directory > tail /var/tmp/iw.out ===> wi install -c -o root -g wheel -m 555 if_wi.ko /modules ---------------------------------------- install started at 11:58:49 on 08/24/00 install finished at 12:37:31 on 08/24/00 ---------------------------------------- > uname -a FreeBSD foo.osd.bsdi.com 4.1-RC FreeBSD 4.1-RC #6: Fri Jul 14 14:15:27 PDT 2000 root@foo.osd.bsdi.com:/usr/src/sys/compile/FOO i386 -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 13:43:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 01.dhcp.hck.carroll.com (core1.hck.carroll.com [216.44.16.2]) by hub.freebsd.org (Postfix) with ESMTP id 1B8F037B423; Thu, 24 Aug 2000 13:43:37 -0700 (PDT) Received: (from damien@localhost) by 01.dhcp.hck.carroll.com (8.9.3/8.9.3) id QAA12303; Thu, 24 Aug 2000 16:44:04 -0400 (EDT) (envelope-from damien) Date: Wed, 9 Aug 2000 15:39:24 -0400 From: Damien Tougas To: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Subject: Ipnat fails under load? Message-ID: <20000809153924.C18771@carroll.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, After some period of time (anywhere from days to weeks), ipnat stops working properly. We ran a tcpdump on the interface while the problem was occurring, just to see what was going on. What we found was that any new connections attempted from 10.0.0.0/8 were going through with the ack bit set only, it is like the initial packet was somehow blocked. As a result, the server we were trying to contact replied with a tcp reset since it thought that we were trying to connect to a session that did not exist. Our first thought was that we might have ran out of ports, but we have since found that there are typically no more than about 3000 sessions active when this occurrs. The only way to get it to work again is to clear the ipnat tables and rules and re-initialize them using the following sequence: /usr/sbin/ipnat -CF /usr/sbin/ipnat -f /etc/rc.nat After that, everything works just fine. The config file we use (rc.nat) is very simple: map de0 10.0.0.0/8 -> 0/32 portmap tcp/udp 1025:65000 There are currently no other firewall rules being used. All IP addresses on the machine are static. The reason we use the 0/32 designation is to maintain configuration file consistancy across all servers. We are running ipnat on FreeBSD version 3.4-Stable, I am not sure exactly what version of ipfilter it is, it is the one that comes as part of the base OS. Any ideas? Thanks for your help. -- Damien Tougas Carroll-Net, Inc. http://www.carroll.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 13:44:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gateway.jumpweb.com (mgooderum1.dsl.uswest.net [209.180.19.145]) by hub.freebsd.org (Postfix) with ESMTP id 2402437B423 for ; Thu, 24 Aug 2000 13:44:10 -0700 (PDT) Received: from purgatory.jumpweb.com (purgatory [172.15.1.5]) by gateway.jumpweb.com (8.9.3/8.9.3) with ESMTP id PAA08836 for ; Thu, 24 Aug 2000 15:44:08 -0500 (CDT) (envelope-from mark@JUMPWEB.COM) Received: by purgatory.jumpweb.com with Internet Mail Service (5.5.2650.21) id ; Thu, 24 Aug 2000 15:44:08 -0500 Message-ID: <251BF6012D6B4A49A4109B1C3289A7B5BB78@purgatory.jumpweb.com> From: "Gooderum, Mark" To: freebsd-stable@FreeBSD.ORG Subject: RE: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes n ot loading certain currently loaded daemons) Date: Thu, 24 Aug 2000 15:44:08 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C00E0C.0CA87D07" 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_001_01C00E0C.0CA87D07 Content-Type: text/plain; charset="iso-8859-1" > >Does it avoid using rcmd/rsh? > > Yes; it uses its own protocol. (It can use .rhosts for > "authentication", but current versions default to using a > separate file, .amandahosts for that. It also uses its own UDP & TCP ports.) But amanda works by "trusting" the source IP/Port of the connection the same way rsh/rcmd do via .rhosts/hosts.equiv. So it's no more or less secure... Fundamentally in the normal out of box Unix you either are or aren't working in a trusted environment. For most of us I think you are. If you're on a wire that controls the machines and trust the users then things like rxxx are okay. Ff your box is on the internet or the campus CS lab wire, you're generally not. Anyway, by default, .rhosts and hosts.equiv are empty and therefor having rshd enabled isn't any risk beyond cleartext passwords on the wire (which also can't be sniffed w/o root if you have a "trusted" wire). FreeBSD (and almost _every_ other OS and Unix in fairness) out of the box isn't in shape to hang out bare on the Internet and just disabling telnet and rsh doesn't make it so. Also, most ISPs and companies _still_ don't have things like SSL support for POP or IMAP, so ending telnet and rsh cleartext PW's on the wire does little to really secure things since most of us use the same password everywhere. Not saying it's the right security answer, but user reality is just that. Interoperability is critical and although ssh has found its way into FreeBSD 4.1 as standard, it certainly isn't standard on Windows or most other Unixen and other OSes. Unless somebody wants to bite the bullet (and I for one am _not_ interested in trying) and write a "lockdown_freebsd" script that enables ipfw or ipfilter with some reasonable defaults, turns off various insecure services (including NFS...more implicit trust and/or cleartext PW's via pcnfsd) then just blindly disabling rsh/telnet does little to really impove the security of the box and does a lot to increase the confusion of the user and increase the amount of manual configuration the _average_ user needs to make the box function in the _average_ environment. -- Mark Gooderum mark@jumpweb.com ------_=_NextPart_001_01C00E0C.0CA87D07 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
RE: nuking "unsafe" protocols (was Re: Upcoming = rc.conf changes not loading certain currently loaded daemons)

> >Does it avoid using rcmd/rsh?
>
> Yes; it uses its own protocol.  (It can = use .rhosts for
> "authentication", but current = versions default to using a
> separate file, .amandahosts for that.  It = also uses its own UDP & TCP ports.)

But amanda works by "trusting" the source = IP/Port of the connection the same way rsh/rcmd do via = .rhosts/hosts.equiv.  So it's no more or less = secure...

Fundamentally in the normal out of box Unix you = either are or aren't working in a trusted environment.  For most = of us I think you are.  If you're on a wire that controls the = machines and trust the users then things like rxxx are okay.  Ff = your box is on the internet or the campus CS lab wire, you're generally = not.  Anyway, by default, .rhosts and hosts.equiv are empty and = therefor having rshd enabled isn't any risk beyond cleartext passwords = on the wire (which also can't be sniffed w/o root if you have a = "trusted" wire).  FreeBSD (and almost _every_ other OS = and Unix in fairness) out of the box isn't in shape to hang out bare on = the Internet and just disabling telnet and rsh doesn't make it = so.  Also, most ISPs and companies _still_ don't have things like = SSL support for POP or IMAP, so ending telnet and rsh cleartext PW's on = the wire does little to really secure things since most of us use the = same password everywhere.  Not saying it's the right security = answer, but user reality is just that.

Interoperability is critical and although ssh has = found its way into FreeBSD 4.1 as standard, it certainly isn't standard = on Windows or most other Unixen and other OSes.  Unless somebody = wants to bite the bullet (and I for one am _not_ interested in trying) = and write a "lockdown_freebsd" script that enables ipfw or = ipfilter with some reasonable defaults, turns off various insecure = services (including NFS...more implicit trust and/or cleartext PW's via = pcnfsd) then just blindly disabling rsh/telnet does little to really = impove the security of the box and does a lot to increase the confusion = of the user and increase the amount of manual configuration the = _average_ user needs to make the box function in the _average_ = environment.

--
Mark Gooderum
mark@jumpweb.com

------_=_NextPart_001_01C00E0C.0CA87D07-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 13:52:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cx587235-a.chnd1.az.home.com (cx587235-a.chnd1.az.home.com [24.11.88.170]) by hub.freebsd.org (Postfix) with ESMTP id 4B79237B42C for ; Thu, 24 Aug 2000 13:52:17 -0700 (PDT) Received: from whale.home-net (whale [192.168.1.2]) by cx587235-a.chnd1.az.home.com (8.9.3/8.9.3) with ESMTP id NAA08152 for ; Thu, 24 Aug 2000 13:52:17 -0700 (MST) (envelope-from jjreynold@home.com) Received: (from jjreynold@localhost) by whale.home-net (8.9.3/8.9.3) id NAA02226; Thu, 24 Aug 2000 13:52:17 -0700 (MST) (envelope-from jjreynold@home.com) From: John Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14757.35584.883502.284470@whale.home-net> Date: Thu, 24 Aug 2000 13:52:16 -0700 (MST) To: stable@freebsd.org Subject: Re: mergemaster wishlist In-Reply-To: <200008240428.AAA31509@sanson.reyes.somos.net> References: <200008240428.AAA31509@sanson.reyes.somos.net> X-Mailer: VM 6.75 under Emacs 20.7.1 Cc: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Thursday, August 24, Francisco Reyes wrote: ] > > I gave this a little thought.. There is one way to go about it > that will bypass comparisons altogheter. > > Instead of comparing each file against the exeption list one > could process the exception list upfront. > Files to be merged automatically will be copied.. files to be > ignored would be deleted. > > What do you think of this approach? you mean like this: --- /usr/sbin/mergemaster Thu Aug 10 07:13:42 2000 +++ mergemaster Wed Jul 19 22:04:07 2000 @@ -260,6 +260,23 @@ ;; esac + # Avoid comparing the files in IGNORE_FILE if the user specifies it in + # .mergemasterrc + # + case "${IGNORE_FILE}" in + '') ;; + *) echo "" + echo "*** IGNORE_FILE variable found in $HOME/.mergemasterrc" + echo " The following files will not be compared:" + echo "" + for tmpfile in `cat ${IGNORE_FILE} | xargs`; do + echo " - ${tmpfile}" + rm ${TEMPROOT}${tmpfile} + done + ;; + esac + + ;; # End of the "RERUN" test esac Just have IGNORE_FILE="/etc/mergemaster.ignore" # or whatever in your .mergemasterrc file and put 1 file per line in this file. Works for me. -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jjreynold@home.com FreeBSD 4.1-STABLE. FreeBSD: The Power to Serve. http://members.home.com/jjreynold/ Come join us!!! @ 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 Aug 24 14: 0: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 66F9937B424 for ; Thu, 24 Aug 2000 14:00:03 -0700 (PDT) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id e7OKxin12979; Thu, 24 Aug 2000 13:59:44 -0700 Date: Thu, 24 Aug 2000 13:59:44 -0700 From: Brooks Davis To: "Gooderum, Mark" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes n ot loading certain currently loaded daemons) Message-ID: <20000824135944.B12283@Odin.AC.HMC.Edu> References: <251BF6012D6B4A49A4109B1C3289A7B5BB78@purgatory.jumpweb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <251BF6012D6B4A49A4109B1C3289A7B5BB78@purgatory.jumpweb.com>; from mark@JUMPWEB.COM on Thu, Aug 24, 2000 at 03:44:08PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 24, 2000 at 03:44:08PM -0500, Gooderum, Mark wrote: > > Interoperability is critical and although ssh has found its way into > FreeBSD 4.1 as standard, it certainly isn't standard on Windows or > most other Unixen and other OSes. Unless somebody wants to bite the > bullet (and I for one am _not_ interested in trying) and write a > "lockdown_freebsd" script that enables ipfw or ipfilter with some > reasonable defaults, turns off various insecure services (including > NFS...more implicit trust and/or cleartext PW's via pcnfsd) then just > blindly disabling rsh/telnet does little to really impove the security > of the box and does a lot to increase the confusion of the user and > increase the amount of manual configuration the _average_ user needs > to make the box function in the _average_ environment. This change DOES NOT DISABLE INETD, PORTMAP, OR SENDMAIL ON NEW INSTALLS! What it does do is set the default in /etc/defaults/rc.conf to off and instruct sysinstall to turn them on in /etc/rc.conf. This means the fact that they are on is clear visiable in /etc/rc.conf instead of hidden in /etc/defaults/rc.conf. The idea is that you should be able to look in /etc/rc.conf and tell which services are enabled. Sysinstall will continue to enable many of them by default to make your life easier. I seriously doubt this change will be MFC'd and it only bites people to lame to follow the lists they have been repeatily told to follow. Heck, it's even in UPDATING. -- 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 Aug 24 14:23:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gateway.jumpweb.com (mgooderum1.dsl.uswest.net [209.180.19.145]) by hub.freebsd.org (Postfix) with ESMTP id AFD8E37B42C for ; Thu, 24 Aug 2000 14:23:23 -0700 (PDT) Received: from purgatory.jumpweb.com (purgatory [172.15.1.5]) by gateway.jumpweb.com (8.9.3/8.9.3) with ESMTP id QAA08901; Thu, 24 Aug 2000 16:23:20 -0500 (CDT) (envelope-from mark@JUMPWEB.COM) Received: by purgatory.jumpweb.com with Internet Mail Service (5.5.2650.21) id ; Thu, 24 Aug 2000 16:23:20 -0500 Message-ID: <251BF6012D6B4A49A4109B1C3289A7B5BB7A@purgatory.jumpweb.com> From: "Gooderum, Mark" To: "'Brooks Davis'" , "Gooderum, Mark" Cc: freebsd-stable@FreeBSD.ORG Subject: RE: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes n ot loading certain currently loaded daemons) Date: Thu, 24 Aug 2000 16:23:19 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C00E11.86239109" 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_001_01C00E11.86239109 Content-Type: text/plain; charset="iso-8859-1" > This change DOES NOT DISABLE INETD, PORTMAP, OR SENDMAIL ON NEW INSTALLS! > .... Sorry, mea culpa. I tried to follow the thread back through the subject change and the 30 messages and thought I had gotten it right, oops. -- Mark ------_=_NextPart_001_01C00E11.86239109 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: nuking "unsafe" protocols (was Re: Upcoming = rc.conf changes n ot loading certain currently loaded daemons)

> This change DOES NOT DISABLE INETD, PORTMAP, OR = SENDMAIL ON NEW INSTALLS!
> ....

Sorry, mea culpa.  I tried to follow the thread = back through the subject change and the 30 messages and thought I had = gotten it right, oops.

--
Mark


 

------_=_NextPart_001_01C00E11.86239109-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 14:54:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.denverweb.net (xenu.denverweb.net [199.45.153.14]) by hub.freebsd.org (Postfix) with SMTP id 92DFF37B424 for ; Thu, 24 Aug 2000 14:54:37 -0700 (PDT) Received: (qmail 58224 invoked from network); 24 Aug 2000 21:52:34 -0000 Received: from fc-pm3-01.enetis.net (HELO denverweb.net) (208.168.188.160) by xenu.denverweb.net with SMTP; 24 Aug 2000 21:52:34 -0000 Message-ID: <39A59992.F42F03EC@denverweb.net> Date: Thu, 24 Aug 2000 15:54:26 -0600 From: blaine X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Gooderum, Mark" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) References: <251BF6012D6B4A49A4109B1C3289A7B5BB78@purgatory.jumpweb.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Gooderum, Mark" wrote: > Interoperability is critical and although ssh has found its way into > FreeBSD 4.1 as standard, it certainly isn't standard on Windows or > most other Unixen and other OSes. Unless somebody wants to bite the > bullet (and I for one am _not_ interested in trying) and write a > "lockdown_freebsd" script that enables ipfw or ipfilter with some > reasonable defaults, turns off various insecure services (including > NFS...more implicit trust and/or cleartext PW's via pcnfsd) then just > blindly disabling rsh/telnet does little to really impove the security > of the box and does a lot to increase the confusion of the user and > increase the amount of manual configuration the _average_ user needs > to make the box function in the _average_ environment. Umm, why not just use openbsd if security is the primary concern? Blaine To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 14:56:37 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 2B09437B422 for ; Thu, 24 Aug 2000 14:56:34 -0700 (PDT) Received: from thehousleys.net (baby.int.thehousleys.net. [192.168.0.24]) by thehousleys.net (8.9.3/8.9.3) with ESMTP id RAA59536 for ; Thu, 24 Aug 2000 17:56:28 -0400 (EDT) (envelope-from jim@thehousleys.net) Message-ID: <39A59A0C.7588265E@thehousleys.net> Date: Thu, 24 Aug 2000 17:56:28 -0400 From: James Housley Organization: The Housleys dot Net X-Mailer: Mozilla 4.73 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) References: <251BF6012D6B4A49A4109B1C3289A7B5BB78@purgatory.jumpweb.com> <39A59992.F42F03EC@denverweb.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG blaine wrote: > Umm, why not just use openbsd if security is the primary concern? > Why shouldn't we provide the best level of security possible, using OpenBSD as a target? Jim -- 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 Aug 24 15: 0:54 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 389D737B424 for ; Thu, 24 Aug 2000 15:00:52 -0700 (PDT) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id AB5471C72; Thu, 24 Aug 2000 18:00:51 -0400 (EDT) Date: Thu, 24 Aug 2000 18:00:51 -0400 From: Bill Fumerola To: blaine Cc: "Gooderum, Mark" , freebsd-stable@FreeBSD.ORG Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) Message-ID: <20000824180051.D57333@jade.chc-chimes.com> References: <251BF6012D6B4A49A4109B1C3289A7B5BB78@purgatory.jumpweb.com> <39A59992.F42F03EC@denverweb.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <39A59992.F42F03EC@denverweb.net>; from blaine@denverweb.net on Thu, Aug 24, 2000 at 03:54:26PM -0600 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 24, 2000 at 03:54:26PM -0600, blaine wrote: > Umm, why not just use openbsd if security is the primary concern? Because no operating system overcomes stupidity. If you do insecure things, you have an insecure machine. If you do secure things, you'll have a reasonably secure machine. People put too much stock in marketing. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 15:14:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.denverweb.net (xenu.denverweb.net [199.45.153.14]) by hub.freebsd.org (Postfix) with SMTP id 2648437B423 for ; Thu, 24 Aug 2000 15:14:35 -0700 (PDT) Received: (qmail 61723 invoked from network); 24 Aug 2000 22:12:38 -0000 Received: from fc-pm3-01.enetis.net (HELO denverweb.net) (208.168.188.160) by xenu.denverweb.net with SMTP; 24 Aug 2000 22:12:38 -0000 Message-ID: <39A59E49.E3EE1196@denverweb.net> Date: Thu, 24 Aug 2000 16:14:33 -0600 From: blaine X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Bill Fumerola Cc: "Gooderum, Mark" , freebsd-stable@FreeBSD.ORG Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) References: <251BF6012D6B4A49A4109B1C3289A7B5BB78@purgatory.jumpweb.com> <39A59992.F42F03EC@denverweb.net> <20000824180051.D57333@jade.chc-chimes.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fumerola wrote: > On Thu, Aug 24, 2000 at 03:54:26PM -0600, blaine wrote: > > > Umm, why not just use openbsd if security is the primary concern? > > Because no operating system overcomes stupidity. True, but you have to do something insecure _on purpose_ .... out of the box, OpenBSD pretty tight, and you have to open services knowingly. FreeBSD is less secure as a default, and you have to work to close services down. I am sure that with little effort FreeBSD could be made more secure by default. In todays world, that is not really a bad thing. Perhaps an install option where you can choose the security model you want. Of course, the real difference between genius and stupidity is, Genius has it's limits. :-P Cheers, Blaine To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 15:15:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.iglobal.net (mail.iglobal.net [209.164.193.7]) by hub.freebsd.org (Postfix) with ESMTP id 7F65437B422 for ; Thu, 24 Aug 2000 15:15:28 -0700 (PDT) Received: from dtnm125 (crouhier.iglobal.net [207.43.204.222]) by mail.iglobal.net (8.10.0/8.10.0) with SMTP id e7OMFJO28371 for ; Thu, 24 Aug 2000 17:15:20 -0500 Message-ID: <000001c00e17$e7f98520$7dca12ac@comp.mooreus.com> From: "Chris Rouhier" To: Subject: Date: Thu, 24 Aug 2000 12:39:43 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C00DC8.60F40900" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C00DC8.60F40900 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ------=_NextPart_000_0007_01C00DC8.60F40900 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
------=_NextPart_000_0007_01C00DC8.60F40900-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 15:18:48 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 3EE8537B43C for ; Thu, 24 Aug 2000 15:18:44 -0700 (PDT) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id SAA08046; Thu, 24 Aug 2000 18:18:51 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Thu, 24 Aug 2000 18:18:51 -0400 (EDT) From: "Brandon D. Valentine" To: Brooks Davis Cc: "Gooderum, Mark" , freebsd-stable@FreeBSD.ORG Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes n ot loading certain currently loaded daemons) In-Reply-To: <20000824135944.B12283@Odin.AC.HMC.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, 24 Aug 2000, Brooks Davis wrote: >This change DOES NOT DISABLE INETD, PORTMAP, OR SENDMAIL ON NEW INSTALLS! >What it does do is set the default in /etc/defaults/rc.conf to off >and instruct sysinstall to turn them on in /etc/rc.conf. This means >the fact that they are on is clear visiable in /etc/rc.conf instead of >hidden in /etc/defaults/rc.conf. The idea is that you should be able to >look in /etc/rc.conf and tell which services are enabled. Sysinstall >will continue to enable many of them by default to make your life >easier. Sounds like a bikeshed to me. Who's got the paintbrush? Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 15:22:23 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 79EE237B424 for ; Thu, 24 Aug 2000 15:22:21 -0700 (PDT) Received: from thehousleys.net (baby.int.thehousleys.net. [192.168.0.24]) by thehousleys.net (8.9.3/8.9.3) with ESMTP id SAA69685 for ; Thu, 24 Aug 2000 18:22:21 -0400 (EDT) (envelope-from jim@thehousleys.net) Message-ID: <39A5A01D.77AD287F@thehousleys.net> Date: Thu, 24 Aug 2000 18:22:21 -0400 From: James Housley Organization: The Housleys dot Net X-Mailer: Mozilla 4.73 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) 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: > > Sounds like a bikeshed to me. Who's got the paintbrush? > I have brushes, but they only work on light-purple, semi-gloss paints. Where should I email them? Jim -- 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 Aug 24 15:46:58 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 BEBA037B422 for ; Thu, 24 Aug 2000 15:46:54 -0700 (PDT) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id SAA08304; Thu, 24 Aug 2000 18:46:57 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Thu, 24 Aug 2000 18:46:57 -0400 (EDT) From: "Brandon D. Valentine" To: James Housley Cc: freebsd-stable@FreeBSD.ORG Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) In-Reply-To: <39A5A01D.77AD287F@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 Thu, 24 Aug 2000, James Housley wrote: >"Brandon D. Valentine" wrote: >> >> Sounds like a bikeshed to me. Who's got the paintbrush? >> >I have brushes, but they only work on light-purple, semi-gloss paints. >Where should I email them? How about one to every single person who's needlessly dragged out this thread and filled my mailbox because they lack basic reading comprehension skills. ;-) Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 16: 6:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by hub.freebsd.org (Postfix) with ESMTP id DD99337B424 for ; Thu, 24 Aug 2000 16:06:28 -0700 (PDT) Received: from localhost.localdomain (user-33qtacm.dialup.mindspring.com [199.174.169.150]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id TAA02813 for ; Thu, 24 Aug 2000 19:06:26 -0400 (EDT) Received: (from david@localhost) by localhost.localdomain (8.9.3/8.9.3) id SAA25828 for freebsd-stable@freebsd.org; Thu, 24 Aug 2000 18:05:42 -0500 (CDT) (envelope-from david) Date: Thu, 24 Aug 2000 18:05:42 -0500 From: "David J. Kanter" To: FreeBSD stable Subject: Kernel won't compile (device xl) Message-ID: <20000824180542.A25814@localhost.localdomain> Mail-Followup-To: FreeBSD stable Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i X-Operating-System: FreeBSD 4.1-STABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've added support for a new Ethernet card, with device miibus and device xl. But when the kernel is compiling I get this error: if_xl.o: In function xl_attach': if_xl.o(.text+0x1c9a): undefined reference to ether_output' if_xl.o(.text+0x20c6): undefined reference to ether_ifattach' if_xl.o: In function xl_detach': if_xl.o(.text+0x210c): undefined reference to ether_ifdetach' if_xl.o: In function xl_rxeof': if_xl.o(.text+0x27b1): undefined reference to ether_input' if_xl.o: In function xl_ioctl': if_xl.o(.text+0x413e): undefined reference to ether_ioctl' *** Error code 1 Stop in /usr/obj/usr/src/sys/SPECIALK. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. su-2.04# What's wrong? -- David Kanter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 16:20:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zaphon.llamas.net (zaphon.llamas.net [207.203.36.210]) by hub.freebsd.org (Postfix) with SMTP id B467737B42C for ; Thu, 24 Aug 2000 16:20:44 -0700 (PDT) Received: (qmail 3592 invoked by uid 500); 24 Aug 2000 23:20:43 -0000 Date: Thu, 24 Aug 2000 16:20:43 -0700 From: Greg Rumple To: Damien Tougas Cc: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Ipnat fails under load? Message-ID: <20000824162043.R24089@zaphon.llamas.net> References: <20000809153924.C18771@carroll.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <20000809153924.C18771@carroll.net>; from damien@carroll.com on Wed, Aug 09, 2000 at 03:39:24PM -0400 X-Mailer: Mutt http://www.mutt.org/ X-Editor: Vim http://www.vim.org/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am experiencing very similar issues. I am running ipnat on FreeBSD 4.1-STABLE as of 8 days ago. I am running a tiny bit more sophisticated set of rules than you, but in reality not much different. I have a class C of machines (about 100 in total) run through the box (collapsed to a single IP). At any one time we have anywhere from 300-1000 connections through the nat, but this box is a P3-700 with 256 megs of ram. This is not an issue, were not experiencing any lag. What instead we are seeing is we just flat out lose connections to some machines until I as well do a full flush/reload. And today even that didn't fix it, I truly had to reboot the box. For example, I had a machine outside the nat, that I connect to regularly. I could not telnet to it, I could not ping it, or anything through the nat. I even tried from the nat directly, and couldn't do any of those items (this machine is in another facility). I could reach other machines 1 ip address above or below it though (which is what's weird). So I even brought up tcpdump on the external interface, and could see the echo requests and echo replies when pinging. Just the kernel wasn't picking them up. This is the third or fourth time I have reached such a state, and this time it could only be fixed via a reboot. Unfortunately I accidently killed the X term that I had all the tcpdump captures, and information in so I don't have that readily available. But I am seeing similar issues. This is a pretty heavy load for a nat, and we realize it, but it's our only option right now. And I really don't wanna use natd, since I would have to deal with ftp proxy/passive issues. * Damien Tougas (damien@carroll.com) [000824 20:44]: > Hello, > > After some period of time (anywhere from days to weeks), ipnat stops > working properly. We ran a tcpdump on the interface while the problem > was occurring, just to see what was going on. What we found was that > any new connections attempted from 10.0.0.0/8 were going through with > the ack bit set only, it is like the initial packet was somehow > blocked. As a result, the server we were trying to contact replied > with a tcp reset since it thought that we were trying to connect to a > session that did not exist. Our first thought was that we might have > ran out of ports, but we have since found that there are typically no > more than about 3000 sessions active when this occurrs. > > The only way to get it to work again is to clear the ipnat tables and > rules and re-initialize them using the following sequence: > > /usr/sbin/ipnat -CF /usr/sbin/ipnat -f /etc/rc.nat > > After that, everything works just fine. The config file we use > (rc.nat) is very simple: > > map de0 10.0.0.0/8 -> 0/32 portmap tcp/udp 1025:65000 > > There are currently no other firewall rules being used. All IP > addresses on the machine are static. The reason we use the 0/32 > designation is to maintain configuration file consistancy across all > servers. > > We are running ipnat on FreeBSD version 3.4-Stable, I am not sure > exactly what version of ipfilter it is, it is the one that comes as > part of the base OS. > > Any ideas? > > Thanks for your help. > > -- Damien Tougas Carroll-Net, Inc. http://www.carroll.com > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe > freebsd-stable" in the body of the message -- Greg Rumple grumple@zaphon.llamas.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 16:45:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 3D8A537B424 for ; Thu, 24 Aug 2000 16:45:51 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e7ONjl017168; Thu, 24 Aug 2000 16:45:48 -0700 (PDT) Date: Thu, 24 Aug 2000 16:45:47 -0700 (PDT) From: Doug White To: Andre Goeree Cc: freebsd-stable@FreeBSD.ORG Subject: Re: /etc/defaults/rc.conf 4.1-STABLE-200-08-18 In-Reply-To: <20000822204748.A1334@freebee.attica.home> 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, 22 Aug 2000, Andre Goeree wrote: > cd /var/tmp/root/etc > cp rc* /etc/ (most of the rc files was changed) > cd defaults > cp * /etc/defaults/ (some changes here too) > updated most if not all other files This is Bad(tm). Use mergemaster instead. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 16:46:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 668B537B422 for ; Thu, 24 Aug 2000 16:46:39 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e7ONkaD21268; Thu, 24 Aug 2000 16:46:36 -0700 (PDT) Date: Thu, 24 Aug 2000 16:46:36 -0700 (PDT) From: Doug White To: webmaster Cc: FreeBSD stable Subject: Re: remove unsubscribe please In-Reply-To: <015801c00cc0$1923bac0$0500a8c0@enta> 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 Unsubscribe yourself: the instructions are right down here vvvvvv To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 16:49:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id EA56137B42C for ; Thu, 24 Aug 2000 16:49:19 -0700 (PDT) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id QAA00848; Thu, 24 Aug 2000 16:49:18 -0700 Message-ID: <39A5B47D.A19EDE27@urx.com> Date: Thu, 24 Aug 2000 16:49:17 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "David J. Kanter" Cc: FreeBSD stable Subject: Re: Kernel won't compile (device xl) References: <20000824180542.A25814@localhost.localdomain> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David J. Kanter" wrote: > > I've added support for a new Ethernet card, with device miibus and device > xl. But when the kernel is compiling I get this error: > > if_xl.o: In function xl_attach': > if_xl.o(.text+0x1c9a): undefined reference to ether_output' > if_xl.o(.text+0x20c6): undefined reference to ether_ifattach' > if_xl.o: In function xl_detach': > if_xl.o(.text+0x210c): undefined reference to ether_ifdetach' > if_xl.o: In function xl_rxeof': > if_xl.o(.text+0x27b1): undefined reference to ether_input' > if_xl.o: In function xl_ioctl': > if_xl.o(.text+0x413e): undefined reference to ether_ioctl' > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/SPECIALK. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > su-2.04# > > What's wrong? Did you config and make depend? I just got through building a kernel with an xl0 in it. Kent > -- > David Kanter > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 16:55:30 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 3E09F37B422 for ; Thu, 24 Aug 2000 16:55:29 -0700 (PDT) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id CEF861C72; Thu, 24 Aug 2000 19:55:21 -0400 (EDT) Date: Thu, 24 Aug 2000 19:55:21 -0400 From: Bill Fumerola To: "David J. Kanter" Cc: FreeBSD stable Subject: Re: Kernel won't compile (device xl) Message-ID: <20000824195521.E57333@jade.chc-chimes.com> References: <20000824180542.A25814@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000824180542.A25814@localhost.localdomain>; from david.kanter@mindspring.com on Thu, Aug 24, 2000 at 06:05:42PM -0500 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 24, 2000 at 06:05:42PM -0500, David J. Kanter wrote: > I've added support for a new Ethernet card, with device miibus and device > xl. But when the kernel is compiling I get this error: > > if_xl.o: In function xl_attach': > if_xl.o(.text+0x1c9a): undefined reference to ether_output' > if_xl.o(.text+0x20c6): undefined reference to ether_ifattach' > if_xl.o: In function xl_detach': > if_xl.o(.text+0x210c): undefined reference to ether_ifdetach' > if_xl.o: In function xl_rxeof': > if_xl.o(.text+0x27b1): undefined reference to ether_input' > if_xl.o: In function xl_ioctl': > if_xl.o(.text+0x413e): undefined reference to ether_ioctl' > *** Error code 1 put 'device ether' back in your kernel? -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 17:39:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 3944237B424; Thu, 24 Aug 2000 17:39:26 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id RAA67914; Thu, 24 Aug 2000 17:39:26 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 24 Aug 2000 17:39:25 -0700 (PDT) From: Kris Kennaway To: blaine Cc: "Gooderum, Mark" , freebsd-stable@FreeBSD.ORG Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) In-Reply-To: <39A59992.F42F03EC@denverweb.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, 24 Aug 2000, blaine wrote: > Umm, why not just use openbsd if security is the primary concern? OpenBSD does not have exclusive rights to "OS security" 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 Aug 24 18:10:28 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 1CBBD37B422 for ; Thu, 24 Aug 2000 18:10:26 -0700 (PDT) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id VAA09429; Thu, 24 Aug 2000 21:10:34 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Thu, 24 Aug 2000 21:10:34 -0400 (EDT) From: Adam To: Forrest Aldrich Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Installation NIC media selection (fxp0) on 4.1-STABLE In-Reply-To: <4.3.2.7.2.20000824130433.00c8eba0@64.20.73.233> 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 Does this still happen if you specify something like this in the extra options box in sysinstall: media 100baseTX mediaopt full-duplex or 10baseT/UTP or half-duplex etc Perhaps its only broken for autodetect? On Thu, 24 Aug 2000, Forrest Aldrich wrote: >I've noted that with 4.1 stable (as of snapshot 0822) does not seem >to set the media type on the NIC properly. This is what we've >arrived at, after checking lots of other things (like switch ports, >etc). Basically, what happens is that the NIC (fxp0) is configured, >and it will connect and transfer files locally, but the throughput >ends up being 12.x kb/sec.... horrific. BUT, it seems fine after >the system is installed and rebooted. > >Anyone else note this problem? > > >_F > > > >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 Aug 24 19:26:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by hub.freebsd.org (Postfix) with ESMTP id 1F9AA37B43F for ; Thu, 24 Aug 2000 19:26:22 -0700 (PDT) Received: from localhost.localdomain (user-33qt9m3.dialup.mindspring.com [199.174.166.195]) by blount.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id WAA15296 for ; Thu, 24 Aug 2000 22:26:19 -0400 (EDT) Received: (from david@localhost) by localhost.localdomain (8.9.3/8.9.3) id VAA02073 for freebsd-stable@freebsd.org; Thu, 24 Aug 2000 21:16:20 -0500 (CDT) (envelope-from david) Date: Thu, 24 Aug 2000 21:16:20 -0500 From: "David J. Kanter" To: FreeBSD stable Subject: Re: Kernel won't compile (device xl) Message-ID: <20000824211620.A2051@localhost.localdomain> Mail-Followup-To: FreeBSD stable References: <20000824180542.A25814@localhost.localdomain> <20000824195521.E57333@jade.chc-chimes.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000824195521.E57333@jade.chc-chimes.com>; from billf@chimesnet.com on Thu, Aug 24, 2000 at 07:55:21PM -0400 X-Operating-System: FreeBSD 4.1-STABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 24, 2000 at 07:55:21PM -0400, Bill Fumerola wrote: > On Thu, Aug 24, 2000 at 06:05:42PM -0500, David J. Kanter wrote: > > I've added support for a new Ethernet card, with device miibus and device > > xl. But when the kernel is compiling I get this error: [snip] > put 'device ether' back in your kernel? ---end quoted text--- This was the problem. I was confused because I added the xl device since I'm getting DSL over PPPoE, but since it's not a "real" Ethernet I wasn't sure if I needed it...after all, I will be using the tunneling device. My goof. Thanks. -- David Kanter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 20:12: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 97B9437B43E for ; Thu, 24 Aug 2000 20:12:26 -0700 (PDT) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA73208; Thu, 24 Aug 2000 21:12:21 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost.village.org [127.0.0.1]) by billy-club.village.org (8.9.3/8.8.3) with ESMTP id VAA31659; Thu, 24 Aug 2000 21:12:30 -0600 (MDT) Message-Id: <200008250312.VAA31659@billy-club.village.org> To: Vivek Khera Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) Cc: FreeBSD Stable List In-reply-to: Your message of "Thu, 24 Aug 2000 11:54:41 EDT." <14757.17729.113055.693358@onceler.kciLink.com> References: <14757.17729.113055.693358@onceler.kciLink.com> <200008241201.IAA32736@sanson.reyes.somos.net> <20000824080419.B51628@dazed.slacker.com> <14757.15655.515615.780499@onceler.kciLink.com> <20000824162123.A80150@irrelevant.org> <14757.16490.269381.416596@onceler.kciLink.com> <20000824163533.B80150@irrelevant.org> Date: Thu, 24 Aug 2000 21:12:29 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14757.17729.113055.693358@onceler.kciLink.com> Vivek Khera writes: : s> Surely rmt could work over ssh? : : Apparently not with its current implementation. It also must fallback : to using rcmd(3) for compatibility with other systems, if one were to : implement the ssh layer. OpenBSD's dump has this functionality. Actually, it is in the rcmd library call. Looks like it would be relatively easy to bring into FreeBSD. Any takers? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 20:15:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sanson.reyes.somos.net (freyes.static.inch.com [216.223.199.224]) by hub.freebsd.org (Postfix) with ESMTP id 6046D37B422; Thu, 24 Aug 2000 20:15:50 -0700 (PDT) Received: from tomasa (tomasa.reyes.somos.net [10.0.0.11]) by sanson.reyes.somos.net (8.9.3/8.9.3) with SMTP id XAA35407; Thu, 24 Aug 2000 23:07:17 -0400 (EDT) (envelope-from fran@reyes.somos.net) Message-Id: <200008250307.XAA35407@sanson.reyes.somos.net> From: "Francisco Reyes" To: "Nik Clayton" Cc: "FreeBSD Stable List" , "Nik Clayton" Date: Thu, 24 Aug 2000 23:07:02 -0400 Reply-To: "Francisco Reyes" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 98 (4.10.2222) In-Reply-To: <20000824154145.A8893@canyon.nothing-going-on.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: Upcoming rc.conf changes not loading certain currently loaded daemons Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 24 Aug 2000 15:41:45 +0100, Nik Clayton wrote: >> I know this is currently in "current", but won't this eventually >> make it to stable? > >Maybe. I would have thought that's unlikely though. However, even if >it is, there'll be a HEADS UP posted to this mailing list, so you'll be >aware that it's an issue. Not all things make it to "HEADS UP" messages. I recall a few months back I found something which there had not been such message and the email I got was ... yes, but it is on the UPDATING document. It is a matter of experience to know to check UPDATING and I guess that I didn't have it at that point.. I am also sure many others new to tracking stable may not know of such file. Perpahs we could have a monthly "Staying stable file". Any opposition for such file? francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 20:17:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sanson.reyes.somos.net (freyes.static.inch.com [216.223.199.224]) by hub.freebsd.org (Postfix) with ESMTP id 94D1A37B422 for ; Thu, 24 Aug 2000 20:17:45 -0700 (PDT) Received: from tomasa (tomasa.reyes.somos.net [10.0.0.11]) by sanson.reyes.somos.net (8.9.3/8.9.3) with SMTP id XAA35419; Thu, 24 Aug 2000 23:08:03 -0400 (EDT) (envelope-from fran@reyes.somos.net) Message-Id: <200008250308.XAA35419@sanson.reyes.somos.net> From: "Francisco Reyes" To: "Neil Blakey-Milner" Cc: "FreeBSD Stable List" Date: Thu, 24 Aug 2000 23:07:47 -0400 Reply-To: "Francisco Reyes" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 98 (4.10.2222) In-Reply-To: <20000824150715.A24874@mithrandr.moria.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: Upcoming rc.conf changes not loading certain currently loaded daemons Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 24 Aug 2000 15:07:15 +0200, Neil Blakey-Milner wrote: >(and when I'm through with it, sendmail won't be listening on port 25 by >default either *evil.grin*) So where will it be listening? Any plans on moving this part of stable on the long term? francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 20:22:15 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 49A8937B423 for ; Thu, 24 Aug 2000 20:22:06 -0700 (PDT) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA73258; Thu, 24 Aug 2000 21:22:04 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost.village.org [127.0.0.1]) by billy-club.village.org (8.9.3/8.8.3) with ESMTP id VAA31765; Thu, 24 Aug 2000 21:22:12 -0600 (MDT) Message-Id: <200008250322.VAA31765@billy-club.village.org> To: Nathan Ahlstrom Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) Cc: Vivek Khera , FreeBSD Stable List In-reply-to: Your message of "Thu, 24 Aug 2000 11:04:15 CDT." <20000824110414.C12752@winternet.com> References: <20000824110414.C12752@winternet.com> <200008241201.IAA32736@sanson.reyes.somos.net> <20000824080419.B51628@dazed.slacker.com> <14757.15655.515615.780499@onceler.kciLink.com> <20000824162123.A80150@irrelevant.org> <14757.16490.269381.416596@onceler.kciLink.com> <20000824163533.B80150@irrelevant.org> <14757.17729.113055.693358@onceler.kciLink.com> Date: Thu, 24 Aug 2000 21:22:11 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000824110414.C12752@winternet.com> Nathan Ahlstrom writes: : This PR may be of interest. : http://www.FreeBSD.org/cgi/query-pr.cgi?pr=15830 Actually, no. It isn't that interesting. More interesting would be something like the following which does it for all rcmd based things. It is out of OpenBSD, and likely needs a couple of tweaks before it can be committed. Much more generic. :-) Comments? Warner Index: net/Makefile.inc =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/lib/libc/net/Makefile.inc,v retrieving revision 1.37 diff -u -r1.37 Makefile.inc --- net/Makefile.inc 2000/07/05 02:13:14 1.37 +++ net/Makefile.inc 2000/08/25 03:21:51 @@ -16,7 +16,7 @@ inet_pton.c ip6opt.c linkaddr.c map_v4v6.c name6.c ns_addr.c \ ns_name.c ns_netint.c \ ns_ntoa.c ns_parse.c ns_print.c ns_ttl.c nsap_addr.c \ - rcmd.c recv.c res_comp.c res_data.c res_debug.c \ + rcmd.c rcmdsh.c recv.c res_comp.c res_data.c res_debug.c \ res_init.c res_mkquery.c res_mkupdate.c res_query.c res_send.c \ res_update.c rthdr.c send.c vars.c # not supported: iso_addr.c Index: net/rcmd.c =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/lib/libc/net/rcmd.c,v retrieving revision 1.29 diff -u -r1.29 rcmd.c --- net/rcmd.c 2000/08/10 17:10:57 1.29 +++ net/rcmd.c 2000/08/25 03:21:54 @@ -47,6 +47,7 @@ #include #include #include +#include #include #include #include @@ -99,9 +100,27 @@ long oldmask; pid_t pid; int s, aport, lport, timo, error; - char c; + char c, *p; char num[8]; static char canonnamebuf[MAXDNAME]; /* is it proper here? */ + + /* call rcmdsh() with specified remote shell if appropriate. */ + if (!issetugid() && (p = getenv("RSH"))) { + struct servent *sp = getservbyname("shell", "tcp"); + + if (sp && sp->s_port == rport) + return (rcmdsh(ahost, rport, locuser, remuser, + cmd, p)); + } + + /* use rsh(1) if non-root and remote port is shell. */ + if (geteuid()) { + struct servent *sp = getservbyname("shell", "tcp"); + + if (sp && sp->s_port == rport) + return (rcmdsh(ahost, rport, locuser, remuser, + cmd, NULL)); + } pid = getpid(); Index: net/rcmdsh.3 =================================================================== RCS file: rcmdsh.3 diff -N rcmdsh.3 --- /dev/null Thu Aug 24 20:04:33 2000 +++ rcmdsh.3 Thu Aug 24 20:21:54 2000 @@ -0,0 +1,103 @@ +.\" $OpenBSD: rcmdsh.3,v 1.6 1999/07/05 04:41:00 aaron Exp $ +.\" +.\" Copyright (c) 1983, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by the University of +.\" California, Berkeley and its contributors. +.\" 4. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd September 1, 1996 +.Dt RCMDSH 3 +.Os +.Sh NAME +.Nm rcmdsh +.Nd return a stream to a remote command without superuser +.Sh SYNOPSIS +.Fd #include +.Ft int +.Fn rcmdsh "char **ahost" "int inport" "const char *locuser" "const char *remuser" "const char *cmd" "char *rshprog" +.Sh DESCRIPTION +The +.Fn rcmdsh +function +is used by normal users to execute a command on +a remote machine using an authentication scheme based +on reserved port numbers using +.Xr rshd 8 +or the value of +.Fa rshprog +(if non-null). +.Pp +The +.Fn rcmdsh +function +looks up the host +.Fa *ahost +using +.Xr gethostbyname 3 , +returning \-1 if the host does not exist. +Otherwise +.Fa *ahost +is set to the standard name of the host +and a connection is established to a server +residing at the well-known Internet port +.Li shell/tcp +(or whatever port is used by +.Fa rshprog +). The parameter +.Fa inport +is ignored; it is only included to provide an interface similar to +.Xr rcmd 3 . +.Pp +If the connection succeeds, +a socket in the +.Tn UNIX +domain of type +.Dv SOCK_STREAM +is returned to the caller, and given to the remote +command as stdin and stdout, and stderr. +.Sh DIAGNOSTICS +The +.Fn rcmdsh +function +returns a valid socket descriptor on success. +It returns \-1 on error and prints a diagnostic message on the standard error. +.Sh SEE ALSO +.Xr rsh 1 , +.Xr socketpair 2 , +.Xr rcmd 3 , +.Xr rshd 8 +.Sh BUGS +If +.Xr rsh 1 +gets an error a file descriptor is still returned instead of \-1. +.Sh HISTORY +The +.Fn rcmdsh +function first appeared in +.Ox 2.0 . Index: net/rcmdsh.c =================================================================== RCS file: rcmdsh.c diff -N rcmdsh.c --- /dev/null Thu Aug 24 20:04:33 2000 +++ rcmdsh.c Thu Aug 24 20:21:54 2000 @@ -0,0 +1,128 @@ +/* $OpenBSD: rcmdsh.c,v 1.5 1998/04/25 16:23:58 millert Exp $ */ + +/* + * This is an rcmd() replacement originally by + * Chris Siebenmann . + */ + +#if defined(LIBC_SCCS) && !defined(lint) +static char *rcsid = "$OpenBSD: rcmdsh.c,v 1.5 1998/04/25 16:23:58 millert Exp $"; +#endif /* LIBC_SCCS and not lint */ + +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include + +#ifndef _PATH_RSH +#define _PATH_RSH "/usr/bin/rsh" +#endif + +/* + * This is a replacement rcmd() function that uses the rsh(1) + * program in place of a direct rcmd(3) function call so as to + * avoid having to be root. Note that rport is ignored. + */ +/* ARGSUSED */ +int +rcmdsh(ahost, rport, locuser, remuser, cmd, rshprog) + char **ahost; + int rport; + const char *locuser, *remuser, *cmd; + char *rshprog; +{ + struct hostent *hp; + int cpid, sp[2]; + char *p; + struct passwd *pw; + + /* What rsh/shell to use. */ + if (rshprog == NULL) + rshprog = _PATH_RSH; + + /* locuser must exist on this host. */ + if ((pw = getpwnam(locuser)) == NULL) { + (void) fprintf(stderr, "rcmdsh: unknown user: %s\n", locuser); + return(-1); + } + + /* Validate remote hostname. */ + if (strcmp(*ahost, "localhost") != 0) { + if ((hp = gethostbyname(*ahost)) == NULL) { + herror(*ahost); + return(-1); + } + *ahost = hp->h_name; + } + + /* Get a socketpair we'll use for stdin and stdout. */ + if (socketpair(AF_UNIX, SOCK_STREAM, PF_UNSPEC, sp) < 0) { + perror("rcmdsh: socketpair"); + return(-1); + } + + cpid = fork(); + if (cpid < 0) { + perror("rcmdsh: fork failed"); + return(-1); + } else if (cpid == 0) { + /* + * Child. We use sp[1] to be stdin/stdout, and close sp[0]. + */ + (void) close(sp[0]); + if (dup2(sp[1], 0) < 0 || dup2(0, 1) < 0) { + perror("rcmdsh: dup2 failed"); + _exit(255); + } + /* Fork again to lose parent. */ + cpid = fork(); + if (cpid < 0) { + perror("rcmdsh: fork to lose parent failed"); + _exit(255); + } + if (cpid > 0) + _exit(0); + + /* In grandchild here. Become local user for rshprog. */ + if (setuid(pw->pw_uid)) { + (void) fprintf(stderr, "rcmdsh: setuid(%u): %s\n", + pw->pw_uid, strerror(errno)); + _exit(255); + } + + /* + * If remote host is "localhost" and local and remote user + * are the same, avoid running remote shell for efficiency. + */ + if (!strcmp(*ahost, "localhost") && !strcmp(locuser, remuser)) { + if (pw->pw_shell[0] == '\0') + rshprog = _PATH_BSHELL; + else + rshprog = pw->pw_shell; + p = strrchr(rshprog, '/'); + execlp(rshprog, p ? p+1 : rshprog, "-c", cmd, + (char *) NULL); + } else { + p = strrchr(rshprog, '/'); + execlp(rshprog, p ? p+1 : rshprog, *ahost, "-l", + remuser, cmd, (char *) NULL); + } + (void) fprintf(stderr, "rcmdsh: execlp %s failed: %s\n", + rshprog, strerror(errno)); + _exit(255); + } else { + /* Parent. close sp[1], return sp[0]. */ + (void) close(sp[1]); + /* Reap child. */ + (void) wait(NULL); + return(sp[0]); + } + /* NOTREACHED */ +} Index: net/res_query.c =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/lib/libc/net/res_query.c,v retrieving revision 1.19 diff -u -r1.19 res_query.c --- net/res_query.c 1999/11/04 04:30:44 1.19 +++ net/res_query.c 2000/08/25 03:21:55 @@ -76,6 +76,7 @@ #include #include +#include #include #include #include @@ -376,14 +377,23 @@ char *file; char buf[BUFSIZ]; static char abuf[MAXDNAME]; + struct stat sb; if (_res.options & RES_NOALIASES) return (NULL); - if (issetugid()) - return (NULL); file = getenv("HOSTALIASES"); if (file == NULL || (fp = fopen(file, "r")) == NULL) return (NULL); + if (issetugid()) { + if (fstat(fileno(fp), &sb)) { + fclose(fp); + return (NULL); + } + if ((sb.st_mode & 0444) != 0444) { + fclose(fp); + return (NULL); + } + } setbuf(fp, NULL); buf[sizeof(buf) - 1] = '\0'; while (fgets(buf, sizeof(buf), fp)) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 20:23: 1 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 5585B37B423 for ; Thu, 24 Aug 2000 20:22:58 -0700 (PDT) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA73277; Thu, 24 Aug 2000 21:22:56 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost.village.org [127.0.0.1]) by billy-club.village.org (8.9.3/8.8.3) with ESMTP id VAA31778; Thu, 24 Aug 2000 21:23:05 -0600 (MDT) Message-Id: <200008250323.VAA31778@billy-club.village.org> To: Vivek Khera Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) Cc: FreeBSD Stable List In-reply-to: Your message of "Thu, 24 Aug 2000 12:20:25 EDT." <14757.19273.536040.643538@onceler.kciLink.com> References: <14757.19273.536040.643538@onceler.kciLink.com> <200008241201.IAA32736@sanson.reyes.somos.net> <20000824080419.B51628@dazed.slacker.com> <14757.15655.515615.780499@onceler.kciLink.com> <20000824162123.A80150@irrelevant.org> <14757.16490.269381.416596@onceler.kciLink.com> <20000824163533.B80150@irrelevant.org> <14757.17729.113055.693358@onceler.kciLink.com> <20000824110414.C12752@winternet.com> Date: Thu, 24 Aug 2000 21:23:05 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14757.19273.536040.643538@onceler.kciLink.com> Vivek Khera writes: : Wow! If voting is considered, I vote for such a patch to be included. : It makes sense considering that ssh is now part of the core system. Actually, it turns out to be a bad idea and we should use, I think, the more generic rcmdsh from OpenBSD plus tweaks to rcmd_af. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 20:23:40 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 1A6F337B42C for ; Thu, 24 Aug 2000 20:23:38 -0700 (PDT) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA73292; Thu, 24 Aug 2000 21:23:36 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost.village.org [127.0.0.1]) by billy-club.village.org (8.9.3/8.8.3) with ESMTP id VAA31791; Thu, 24 Aug 2000 21:23:45 -0600 (MDT) Message-Id: <200008250323.VAA31791@billy-club.village.org> To: behanna@zbzoom.net Subject: Re: Requesting input for a handbook section entry Cc: Graham Wheeler , freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Thu, 24 Aug 2000 13:31:03 EDT." References: Date: Thu, 24 Aug 2000 21:23:45 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Chris BeHanna writes: : I thought the pnp command went away in 4.x. Is it back for 4.1? It is gone in 4.x. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 20:25: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 9F87337B423 for ; Thu, 24 Aug 2000 20:25:44 -0700 (PDT) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA73315; Thu, 24 Aug 2000 21:25:42 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost.village.org [127.0.0.1]) by billy-club.village.org (8.9.3/8.8.3) with ESMTP id VAA31807; Thu, 24 Aug 2000 21:25:52 -0600 (MDT) Message-Id: <200008250325.VAA31807@billy-club.village.org> To: James Housley Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) Cc: freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Thu, 24 Aug 2000 17:56:28 EDT." <39A59A0C.7588265E@thehousleys.net> References: <39A59A0C.7588265E@thehousleys.net> <251BF6012D6B4A49A4109B1C3289A7B5BB78@purgatory.jumpweb.com> <39A59992.F42F03EC@denverweb.net> Date: Thu, 24 Aug 2000 21:25:52 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39A59A0C.7588265E@thehousleys.net> James Housley writes: : blaine wrote: : > Umm, why not just use openbsd if security is the primary concern? : > : Why shouldn't we provide the best level of security possible, using : OpenBSD as a target? We should be targetting things at a much higher level than OpenBSD :-) Otherwise we run the risk of being an "also ran" in the security area. theo and folks over there have done a good job, and we need to do better. We're not there yet, however. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 20:27: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 43C6D37B42C; Thu, 24 Aug 2000 20:27:51 -0700 (PDT) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA73330; Thu, 24 Aug 2000 21:27:50 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost.village.org [127.0.0.1]) by billy-club.village.org (8.9.3/8.8.3) with ESMTP id VAA31827; Thu, 24 Aug 2000 21:27:58 -0600 (MDT) Message-Id: <200008250327.VAA31827@billy-club.village.org> To: "Francisco Reyes" Subject: Re: Upcoming rc.conf changes not loading certain currently loaded daemons Cc: "Nik Clayton" , "FreeBSD Stable List" In-reply-to: Your message of "Thu, 24 Aug 2000 23:07:02 EDT." <200008250307.XAA35407@sanson.reyes.somos.net> References: <200008250307.XAA35407@sanson.reyes.somos.net> Date: Thu, 24 Aug 2000 21:27:58 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200008250307.XAA35407@sanson.reyes.somos.net> "Francisco Reyes" writes: : UPDATING and I guess that I didn't have it at that point.. I am I guess it doesn't help that the UPDATING file says to read the whole UPDATING file before proceeding :-) On a more serious note, the UPDATING file is now mentioned in the handbook, but old timers need to learn to use it. warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 20:38:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id 1780037B423 for ; Thu, 24 Aug 2000 20:38:19 -0700 (PDT) Received: from localhost.localdomain (user-33qta7c.dialup.mindspring.com [199.174.168.236]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id XAA10931 for ; Thu, 24 Aug 2000 23:38:14 -0400 (EDT) Received: (from david@localhost) by localhost.localdomain (8.9.3/8.9.3) id WAA04975 for freebsd-stable@freebsd.org; Thu, 24 Aug 2000 22:26:50 -0500 (CDT) (envelope-from david) Date: Thu, 24 Aug 2000 22:26:50 -0500 From: "David J. Kanter" To: FreeBSD stable Subject: ATAPI_STATIC_ID Message-ID: <20000824222650.A4884@localhost.localdomain> Mail-Followup-To: FreeBSD stable Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i X-Operating-System: FreeBSD 4.1-STABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tried to build a kernel that had the ATAPI_STATIC_ID option, but config said that the option no longer exists. Huh? I've had this option since 4.0, and saw in both GENERIC and LINT that ATAPI_STATIC_ID does seem to exist. Can someone explain this to me. -- David Kanter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 21:17:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.mts.net (smtp1.mts.net [205.200.16.74]) by hub.freebsd.org (Postfix) with ESMTP id 4E28937B422 for ; Thu, 24 Aug 2000 21:17:06 -0700 (PDT) Received: from 3jane (a-142-199-res1.mts.net [205.200.142.199]) by smtp1.mts.net (8.10.1/8.8.8) with SMTP id e7P4GuM11177 for ; Thu, 24 Aug 2000 23:17:00 -0500 (CDT) From: "Ryan D. Walberg" To: Subject: Date: Thu, 24 Aug 2000 23:18:57 -0500 Message-ID: <000001c00e4b$972e1690$0501a8c0@3jane> 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.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe Ryan D. Walberg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 21:19:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.mts.net (smtp1.mts.net [205.200.16.74]) by hub.freebsd.org (Postfix) with ESMTP id 678A237B424 for ; Thu, 24 Aug 2000 21:19:47 -0700 (PDT) Received: from 3jane (a-142-199-res1.mts.net [205.200.142.199]) by smtp1.mts.net (8.10.1/8.8.8) with SMTP id e7P4JkM11511 for ; Thu, 24 Aug 2000 23:19:46 -0500 (CDT) From: "Ryan D. Walberg" To: Subject: Humblest apologies Date: Thu, 24 Aug 2000 23:21:48 -0500 Message-ID: <000201c00e4b$fcca8240$0501a8c0@3jane> 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.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry about that. I sent it to the wrong list. :P To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 21:49:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (Postfix) with ESMTP id 326B837B42C for ; Thu, 24 Aug 2000 21:49:46 -0700 (PDT) Received: from tao.thought.org (tao.sea.tera.com [207.108.223.55]) by gershwin.tera.com (8.9.3/8.9.3) with ESMTP id VAA26759 for ; Thu, 24 Aug 2000 21:50:03 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.9.3/8.7.3) id VAA05812 for freebsd-stable@FreeBSD.ORG; Thu, 24 Aug 2000 21:49:43 -0700 (PDT) From: Gary Kline Message-Id: <200008250449.VAA05812@tao.thought.org> Subject: mouse question.... To: freebsd-stable@FreeBSD.ORG Date: Thu, 24 Aug 2000 21:49:43 -0700 (PDT) Organization: <> thought.org: pvblic service Unix since 1986... <> 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 Hi, Y'all, This is a long shot, but here goes. --On my other FBSD system which is as 4.0, the mouse won't work. A friend just checked the hardware ports, switched the mouse from COM1 to COM2. (COM2 or, in the case of my modem, /dev/cuaa1, is working.) Zip; nothing. He tried the mouse on this system on the other. Again, nothinng. He thinks that in my upgrading to 4.0, part of my mouse software may have been hosed. Any suggestions how I can diagnose the software side of this? I'm stumped. thanks, gary -- Gary D. Kline kline@tao.thought.org Public service Unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 21:58:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id CD89B37B423 for ; Thu, 24 Aug 2000 21:58:13 -0700 (PDT) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id VAA00852; Thu, 24 Aug 2000 21:57:27 -0700 Message-ID: <39A5FCB7.D28142D9@urx.com> Date: Thu, 24 Aug 2000 21:57:27 -0700 From: Kent Stewart Organization: Dynacom Net X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Gary Kline Cc: freebsd-stable@FreeBSD.ORG Subject: Re: mouse question.... References: <200008250449.VAA05812@tao.thought.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gary Kline wrote: > > Hi, Y'all, > > This is a long shot, but here goes. --On my other FBSD system > which is as 4.0, the mouse won't work. A friend just checked > the hardware ports, switched the mouse from COM1 to COM2. (COM2 > or, in the case of my modem, /dev/cuaa1, is working.) Zip; > nothing. He tried the mouse on this system on the other. Again, > nothinng. He thinks that in my upgrading to 4.0, part of my > mouse software may have been hosed. > > Any suggestions how I can diagnose the software side of this? I have always use the configure option of sysinstall to figure my mice out. Kent > > I'm stumped. > > thanks, > > gary > > -- > Gary D. Kline kline@tao.thought.org Public service Unix > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html 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 Thu Aug 24 22:32: 3 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 B71FB37B42C for ; Thu, 24 Aug 2000 22:32:01 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e7P5Vwv06527; Thu, 24 Aug 2000 22:31:58 -0700 (PDT) Date: Thu, 24 Aug 2000 22:31:58 -0700 From: Alfred Perlstein To: Gary Kline Cc: freebsd-stable@FreeBSD.ORG Subject: Re: mouse question.... Message-ID: <20000824223158.J1209@fw.wintelcom.net> References: <200008250449.VAA05812@tao.thought.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200008250449.VAA05812@tao.thought.org>; from kline@thought.org on Thu, Aug 24, 2000 at 09:49:43PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Gary Kline [000824 21:50] wrote: > > Hi, Y'all, > > This is a long shot, but here goes. --On my other FBSD system > which is as 4.0, the mouse won't work. A friend just checked > the hardware ports, switched the mouse from COM1 to COM2. (COM2 > or, in the case of my modem, /dev/cuaa1, is working.) Zip; > nothing. He tried the mouse on this system on the other. Again, > nothinng. He thinks that in my upgrading to 4.0, part of my > mouse software may have been hosed. > > Any suggestions how I can diagnose the software side of this? > > I'm stumped. It's possible that there's a switch somewhere on the mouse that makes it go from "microsoft" to "mousesystems" try toggling the switch and alternating between moused settings for "microsoft" and "mousesystems". Some mice have the switch but "mousesystems" doesn't seem to work properly, so your best bet is to try both toggles with moused set as "microsoft", once you get that working you may want to try the other position and "mousesystems" in order to get use of your third button if you have one. If your mouse doesn't have a toggle... well then save this for future reference. :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 22:56:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp6.port.ru (mx6.port.ru [194.67.23.42]) by hub.freebsd.org (Postfix) with ESMTP id 6BFC137B423 for ; Thu, 24 Aug 2000 22:56:34 -0700 (PDT) Received: from [212.96.98.32] (helo=[212.96.98.32]) by smtp6.port.ru with esmtp (Exim 3.14 #4) id 13SCTg-0009Jb-00; Fri, 25 Aug 2000 09:56:33 +0400 Date: Fri, 25 Aug 2000 09:56:48 +0400 (MSD) From: Jaroshenko Serge X-Sender: jaroshenko@freebsd.merlin.ru To: "David J. Kanter" Cc: FreeBSD stable Subject: Re: ATAPI_STATIC_ID In-Reply-To: <20000824222650.A4884@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 Hi! ATA_STATIC_ID - !!!! ^^^^ Serge. On Thu, 24 Aug 2000, David J. Kanter wrote: > I tried to build a kernel that had the ATAPI_STATIC_ID option, but config > said that the option no longer exists. > > Huh? I've had this option since 4.0, and saw in both GENERIC and LINT that > ATAPI_STATIC_ID does seem to exist. > > Can someone explain this to me. > -- > David Kanter > > > 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 Aug 24 23:16:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from server.raadinfo.net (smtp2.uwnet.nl [195.7.130.55]) by hub.freebsd.org (Postfix) with ESMTP id BA58D37B424 for ; Thu, 24 Aug 2000 23:16:32 -0700 (PDT) Received: from port288.isd.to (port288.isd.to [195.7.130.236] (may be forged)) by server.raadinfo.net (8.9.3/8.9.3) with ESMTP id IAA13034 for ; Fri, 25 Aug 2000 08:13:42 +0200 Received: (qmail 795 invoked by uid 1000); 25 Aug 2000 06:19:04 -0000 From: "Andre Goeree" Date: Fri, 25 Aug 2000 08:19:04 +0200 To: stable@freebsd.org Subject: Re: ATAPI CD-ROM fails to mount on 4.1-STABLE Message-ID: <20000825081904.A618@freebee.attica.home> Reply-To: abgoeree@uwnet.nl References: <14756.8729.629364.19998@onceler.kciLink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14756.8729.629364.19998@onceler.kciLink.com>; from khera@kciLink.com on Wed, Aug 23, 2000 at 03:12:25PM -0400 X-Sender: abgoeree@uwnet.nl Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 23, 2000 at 03:12:25PM -0400, Vivek Khera wrote: > I updated my 4.1-STABLE yesterday. Today I tried to read a CD-ROM > (the FreeBSD 4.1-R install CD, and also one generic data CD I made a > while back that was ok on this system before) and the mount never > completes. > > Here's what happens. > > I insert the CD and type "mount /cdrom". The mount command returns. > The /var/log/messages syslog contains this entry: > > /kernel: cd9660: RockRidge Extension > > I do an "ls /cdrom" and I get either > > -r-xr-xr-x 1 root wheel 0 Dec 31 1969 /cdrom* > > or some generic "input/output error" from ls. Before the mount, the > /cdrom directory looks like this: > > drwxr-xr-x 2 khera wheel 512 Aug 11 14:13 /cdrom > > > The syslog now contains this entry: > > /kernel: RRIP without PX field? > > I can no longer umount or "eject -f" the drive: > > umount: unmount of /cdrom failed: Invalid argument > > eject: Device busy > > However, after running eject, I can manually eject the disk. > > The "mount" command says this: > > /dev/acd0c on /cdrom (cd9660, local, nodev, nosuid, read-only, mounted by khera, reads: sync 3 async 0) > > It matters not whether I run mount as root or as a user. > > The only way out is a reboot. Booting the 4.1-R kernel.GENERIC, I can > mount and read the CD-ROM just fine. It worked fine as of last friday > as well, when I last did an update and used the CD-ROM. To me, this > rules out hardware problems. > > I just cvsup'd again, and rebuilt a kernel (with DMA for ATAPI turned > off) but that made no difference. (about 2:30pm EDT 23-AUG-2000) > > Any clues as to what to do to get back my CD-ROM drive functionality? > > Anyone else experiencing this trouble? > > Thanks. Hello, Cvsup'ed src-all last night and made world, the problem is still there. It doesn't matter if i compile a GENERIC or a custom kernel. I'm very sure my source tree is up to date, hardware is ok. Any clues? -- Ago abgoeree@uwnet.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 24 23:40:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id A0E8037B423 for ; Thu, 24 Aug 2000 23:40:38 -0700 (PDT) Received: from 149.211.6.64.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Thu, 24 Aug 2000 23:39:29 -0700 Received: (from cjc@localhost) by 149.211.6.64.reflexcom.com (8.9.3/8.9.3) id XAA62421; Thu, 24 Aug 2000 23:40:35 -0700 (PDT) (envelope-from cjc) Date: Thu, 24 Aug 2000 23:40:35 -0700 From: "Crist J . Clark" To: Francisco Reyes Cc: Neil Blakey-Milner , FreeBSD Stable List Subject: Re: Upcoming rc.conf changes not loading certain currently loaded daemons Message-ID: <20000824234035.L28027@149.211.6.64.reflexcom.com> Reply-To: cjclark@alum.mit.edu References: <20000824150715.A24874@mithrandr.moria.org> <200008250308.XAA35419@sanson.reyes.somos.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200008250308.XAA35419@sanson.reyes.somos.net>; from fran@reyes.somos.net on Thu, Aug 24, 2000 at 11:07:47PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 24, 2000 at 11:07:47PM -0400, Francisco Reyes wrote: > On Thu, 24 Aug 2000 15:07:15 +0200, Neil Blakey-Milner wrote: > > >(and when I'm through with it, sendmail won't be listening on port 25 by > >default either *evil.grin*) > > So where will it be listening? > Any plans on moving this part of stable on the long term? I think he's implying it won't be listening anywhere. As in defaulting to, sendmail_enable="NO" In /etc/defaults/rc.conf. -- Crist J. Clark cjclark@alum.mit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 0:44:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from angel.elektra.ru (angel.Elektra.RU [193.125.98.3]) by hub.freebsd.org (Postfix) with ESMTP id B035D37B422 for ; Fri, 25 Aug 2000 00:44:38 -0700 (PDT) Received: from nc.elektra.ru (comm.nc.elektra.ru [193.125.98.89]) by angel.elektra.ru (8.9.3/8.9.3) with ESMTP id LAA08402 for ; Fri, 25 Aug 2000 11:45:04 +0400 (MSD) Message-ID: <39A6240E.3D8C47BF@nc.elektra.ru> Date: Fri, 25 Aug 2000 11:45:18 +0400 From: Denis Schepin Organization: GVC X-Mailer: Mozilla 4.73 [en] (Win98; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: stable@freebsd.org Subject: Compaq 2500 and SMP Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! My name is Denis. I use Compaq Proliant 2500 with OS FreeBSD -3.0-STBALE during three years. Smart RAID Array controller appear in my system recently. I use standart on-board controller ncr before. Now, I build system 4.1-STABLE with Smart RAID Controller where ROOTDEV /dev/idada0s1a . And appears problem with SMP . Then boot process kernel compiled with supporting SMP, broke when reach phrase Mount root device from /dev/idada0s1a and then nothings happen. When I compile the kernel without SMP, boot process is complete and machine work fine. Perhapes this question not for you, but could you tell me some ideas. Best regards Deniss. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 2:12:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from heinz.jollem.com (c187104187.telekabel.chello.nl [212.187.104.187]) by hub.freebsd.org (Postfix) with ESMTP id EE73F37B43C; Fri, 25 Aug 2000 02:12:09 -0700 (PDT) Received: (from ernst@localhost) by heinz.jollem.com (8.9.3/8.9.3) id LAA01733; Fri, 25 Aug 2000 11:11:03 +0200 (CEST) (envelope-from ernst) Date: Fri, 25 Aug 2000 11:11:03 +0200 From: Ernst de Haan To: Mike Muir Cc: questions@freebsd.org, stable@freebsd.org Subject: Re: pci error messages when using SB Live after update to 4.1-RC Message-ID: <20000825111103.B1613@c187104187.telekabel.chello.nl> References: <397DD1A6.442F858A@es.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <397DD1A6.442F858A@es.co.nz>; from mmuir@es.co.nz on Tue, Jul 25, 2000 at 10:43:02AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have exactly the same problem since I cvsupgraded from 4.0-S to 4.1-S. I also note that the sound seems distorted now, at times. Any ideas yet ? Ernst Mike Muir wrote: > Just cvsup'd and rebuilt to 4.1-RC from 4.0-S as of about a month and a > half ago, and am noticing some odd messages when playing anything with > the SB Live in this machine. Firstly, the pcm line from boot: > > pcm0: port 0xc800-0xc81f irq 18 at device 11.0 on > pci0 > > ... and /dev/sndstat: > > FreeBSD Audio Driver (newpcm) Jul 25 2000 01:50:41 > Installed devices: > pcm0: at io 0xc800 irq 18 (4p/3r channels duplex) > > Whenever I play a sound I recieve this message: > > pcm0: pci error > pcm0: pci error > > It doesn't seem to affect the playback at all (although I've noticed > some very subtle crackling -- an artifact that isn't occuring with > regularity however and is almost indetectable so it's not a great > concern, but could there be a correlation??) > > Is there any way I can get more detailed output of pcm0's activity so > that this might be easier for someone to debug? (is this even a problem, > or a message to ignore?) > > -mike. > > > 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 Fri Aug 25 2:50:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14]) by hub.freebsd.org (Postfix) with ESMTP id A460737B42C for ; Fri, 25 Aug 2000 02:50:35 -0700 (PDT) Received: from xpert.com ([146.101.65.232]) by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id MAA11803 for ; Fri, 25 Aug 2000 12:50:32 +0300 (IDT) Received: from localhost (roman@localhost) by xpert.com (8.9.3/8.9.3) with ESMTP id LAA38378 for ; Fri, 25 Aug 2000 11:50:12 +0200 (CEST) (envelope-from roman@xpert.com) Date: Fri, 25 Aug 2000 11:50:12 +0200 (CEST) From: Roman Shterenzon X-Sender: roman@excalibur.oven.org To: freebsd-stable@freebsd.org Subject: pkg_check Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1698059091-967197012=:25998" 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-1698059091-967197012=:25998 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello, I didn't find the functionality to check package integrity in the standard freebsd pkg_* utilities. (Perhaps I'm missing something?) So, I wrote this small perl script which does it for me. With this tool, one may use tripwire only on /var/db/pkg and skip /usr/local. What do you think about it? --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] --0-1698059091-967197012=:25998 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="pkg_check.pl" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="pkg_check.pl" IyEvdXNyL2Jpbi9wZXJsIC13DQojIFJvbWFuIFNodGVyZW56b24gPHJvbWFu QHhwZXJ0LmNvbT4gMjQvMDgvMjAwMA0KJFZlcnNpb249JzAuMDEnOw0KJERC PScvdmFyL2RiL3BrZyc7DQoNCiMgUHJpbnRIZWxwDQojDQojIFByaW50IHVz YWdlIGluZm9ybWF0aW9uDQpzdWIgUHJpbnRIZWxwIHsNCiAgIHByaW50IDw8 IkVPRiI7DQpwa2dfY2hlY2sgJFZlcnNpb24NClJvbWFuIFNodGVyZW56b24g PHJvbWFuXEB4cGVydC5jb20+DQoNClVzYWdlOiBwa2dfY2hlY2sgWy1hXSBw a2duYW1lDQotYQkJQ2hlY2sgTUQ1IHN1bXMgb2YgYWxsIGluc3RhbGxlZCBw YWNrYWdlcw0KDQpFT0YNCmV4aXQgMTsNCn0NCg0KJHBrZz1zaGlmdCB8fCAm UHJpbnRIZWxwOw0KDQpkaWUgIlBhY2thZ2UgJHBrZyBpc24ndCBpbnN0YWxs ZWRcbiIgdW5sZXNzKCAtZCAiJERCLyRwa2ciIHx8ICRwa2cgZXEgIi1hIiAp Ow0KaWYgKCAkcGtnIGVxICItYSIgKSB7DQogIG9wZW5kaXIoREgsICREQikg fHwgZGllICJDYW5ub3QgcmVhZCBkYXRhYmFzZSBkaXJlY3RvcnlcbiI7DQog IEBwa2c9Z3JlcCB7IC1kICIkREIvJF8iICYmIC9eW14uXS8gfSByZWFkZGly KERIKTsNCiAgY2xvc2VkaXIoREgpOw0KfQ0KZWxzZSB7IEBwa2cgPSAoICRw a2cgKTsgfQ0KDQpmb3JlYWNoICRwa2cgKCBAcGtnICkgew0KICBvcGVuKEZI LCAiJERCLyRwa2cvK0NPTlRFTlRTIikgfHwgZGllICJDYW5ub3Qgb3BlbiBw YWNrYWdlIGNvbnRlbnRzXG4iOw0KICB3aGlsZSAoPEZIPikgew0KICAgIGNo b21wOw0KICAgIGlmICggJF89fnMvXEBjd2QgLy8gKSB7DQogICAgICAkY3dk ID0gJF87DQogICAgfQ0KICAgIGVsc2lmICggL15bXkBdLyApIHsNCiAgICAg ICRmaWxlID0gJF87DQogICAgfSANCiAgICBlbHNpZiAoICRfPX4gcy9eXEBj b21tZW50IE1ENTovLyApIHsNCiAgICAgICRtZDVfcGtnPSRfOw0KICAgICAg aWYgKCAhICRmaWxlICkgew0KICAgICAgICBkaWUgIlVudXN1YWwgcGtnIGxp c3RpbmcsIGV4cGVjdGVkIG1kNSBhZnRlciBmaWxlbmFtZSwgZ290IG9ubHkg bWQ1XG4iOw0KICAgICAgfQ0KICAgICAgJGZpbGVuYW1lPSIkY3dkLyRmaWxl IjsNCiAgICAgIGlmICggLXIgIiRmaWxlbmFtZSIgKSB7DQogICAgICAgIGNo b21wKCAkbWQ1X2ZzPWAvc2Jpbi9tZDUgLXEgJGZpbGVuYW1lYCApOw0KICAg ICAgICBpZiAoICRtZDVfZnMgbmUgJG1kNV9wa2cgKSB7DQogICAgICAgICAg cHJpbnQgIldBUk5JTkc6ICRwa2c6ICRmaWxlbmFtZSBtZDUgc3VtIGRpZmZl cnMgZnJvbSB0aGUgb25lIGluIHBrZyBkYlxuIjsNCiAgICAgICAgfQ0KICAg ICAgICB1bmRlZigkZmlsZSk7DQogICAgICB9DQogICAgICBlbHNlIHsNCiAg ICAgICAgcHJpbnQgIkNhbm5vdCBhY2Nlc3MgJGZpbGVuYW1lIChpbnN1ZmZp Y2llbnQgYWNjZXNzIG9yIGluZXhpc3RlbnQpXG4iOw0KICAgICAgfQ0KICAg IH0NCiAgfSAgDQogIGNsb3NlKEZIKTsNCn0gIyBvZiB0aGUgb3V0ZXIgZm9y ZWFjaCBsb29wDQo= --0-1698059091-967197012=:25998-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 2:54:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14]) by hub.freebsd.org (Postfix) with ESMTP id 1DAC737B424 for ; Fri, 25 Aug 2000 02:54:34 -0700 (PDT) Received: from xpert.com ([146.101.65.232]) by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id MAA12319 for ; Fri, 25 Aug 2000 12:54:31 +0300 (IDT) Received: from localhost (roman@localhost) by xpert.com (8.9.3/8.9.3) with ESMTP id LAA38392 for ; Fri, 25 Aug 2000 11:54:12 +0200 (CEST) (envelope-from roman@xpert.com) Date: Fri, 25 Aug 2000 11:54:12 +0200 (CEST) From: Roman Shterenzon X-Sender: roman@excalibur.oven.org To: freebsd-stable@freebsd.org Subject: PERL_THREADED inconsistency 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, It seems to me, that PERL_THREADED /etc/make.conf variable isn't correctly described in the /etc/defaults/make.conf : excalibur:/home/roman% grep PERL_THREADED /etc/defaults/make.conf /usr/src/gnu/usr.bin/perl/Makefile.inc /etc/defaults/make.conf:#PERL_THREADED= true /usr/src/gnu/usr.bin/perl/Makefile.inc:PERL_THREADED?= no /usr/src/gnu/usr.bin/perl/Makefile.inc:.if ${PERL_THREADED} == "yes" It's should be "#PERL_THREADED=yes" in make.conf I guess.. --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 3:42:58 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 0858737B42C for ; Fri, 25 Aug 2000 03:42:55 -0700 (PDT) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13SGwX-0009Re-00; Fri, 25 Aug 2000 12:42:37 +0200 Date: Fri, 25 Aug 2000 12:42:37 +0200 From: Neil Blakey-Milner To: cjclark@alum.mit.edu Cc: Francisco Reyes , FreeBSD Stable List Subject: Re: Upcoming rc.conf changes not loading certain currently loaded daemons Message-ID: <20000825124237.A36221@mithrandr.moria.org> References: <20000824150715.A24874@mithrandr.moria.org> <200008250308.XAA35419@sanson.reyes.somos.net> <20000824234035.L28027@149.211.6.64.reflexcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000824234035.L28027@149.211.6.64.reflexcom.com>; from cjclark@reflexnet.net on Thu, Aug 24, 2000 at 11:40:35PM -0700 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 Thu 2000-08-24 (23:40), Crist J . Clark wrote: > > >(and when I'm through with it, sendmail won't be listening on port 25 by > > >default either *evil.grin*) > > > > So where will it be listening? > > Any plans on moving this part of stable on the long term? > > I think he's implying it won't be listening anywhere. As in defaulting > to, > > sendmail_enable="NO" > > In /etc/defaults/rc.conf. No, sendmail_flags="-q15m", not the current "-q15m -bd". Hey, it was mostly a joke. Obviously I'd have to motivate and convince people first. I only have one mail server on the network that receives mail, and 7 or 8 other machines that just send. Changing that on all of them was too much work. I can imagine there'll be others who agree. Obviously there'd be the option in sysinstall, and all the rest, sorted. And copious warnings in UPDATING and a HEADS-UP to the -STABLE list, and probably in the release notes. _If_ I can convince others that I'm right. Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 4: 1:33 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 13AD837B43C for ; Fri, 25 Aug 2000 04:01:31 -0700 (PDT) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.10.1/8.10.1) with ESMTP id e7PB1ST14454 for ; Fri, 25 Aug 2000 07:01:29 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id HAA36407; Fri, 25 Aug 2000 07:01:27 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id HAA85227; Fri, 25 Aug 2000 07:01:26 -0400 (EDT) Date: Fri, 25 Aug 2000 07:01:26 -0400 (EDT) From: Thomas David Rivers Message-Id: <200008251101.HAA85227@lakes.dignus.com> To: freebsd-stable@freebsd.org, rivers@dignus.com Subject: Re: 4.1-RELEASE & Netscape (aout libraries) In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just to have this in the archive somewhere, regarding the install of Netscape from ftp.netscape.com. First, the proper way to install Netscape is to use the port/package system; which probably has the right dependencies to get things installed. But, if you're like me and simply grabbed the Netscape files from ftp.netscape.com you will need to install the XFree86 3.3.3 aout package. The compat22 (and other compat distributions) contain the C libraries, etc... but, there are no X11 libraries. Simply use pkg_add to install the XFree86 aout package, and *poof* Netscape will work. - Thanks for everyone's assist - - Dave Rivers - -- rivers@dignus.com Work: (919) 676-0847 Get your mainframe (370) `C' compiler at http://www.dignus.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 4: 6:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id DB60F37B424 for ; Fri, 25 Aug 2000 04:06:23 -0700 (PDT) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id EAA01657 for ; Fri, 25 Aug 2000 04:05:07 -0700 Message-ID: <39A652D9.EC1EBDF6@urx.com> Date: Fri, 25 Aug 2000 04:04:57 -0700 From: Kent Stewart Organization: Dynacom Net X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: FreeBSD-Stable Subject: Can't mount 4.1 CDROM's Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On two recently built 4.1-Stable's, I am receiving the following messages when I try to mount any of the 4 CDROM in the 4.1 distribution. The messages are RRIP without PX field? Aug 25 03:59:15 jade /kernel: RRIP without PX field? Aug 25 03:59:15 jade /kernel: RRIP without PX field? Aug 25 03:59:15 jade mountd[95]: can't delete exports for /cdrom Aug 25 03:59:15 jade mountd[95]: can't delete exports for /cdrom The only way I can get the CD out of the cdrom drive has been to reboot. Kent -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.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 Fri Aug 25 4:37: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dart.sr.se (dart.SR.SE [193.12.91.98]) by hub.freebsd.org (Postfix) with ESMTP id 843E637B423 for ; Fri, 25 Aug 2000 04:36:59 -0700 (PDT) Received: from honken.sr.se ([134.25.128.27]) by dart.sr.se (8.9.3/8.9.3) with ESMTP id NAA93408 for ; Fri, 25 Aug 2000 13:36:55 +0200 (CEST) (envelope-from gunnar@pluto.sr.se) Received: from pluto.sr.se (pluto.SR.SE [134.25.193.91]) by honken.sr.se (8.9.3/8.9.3) with ESMTP id NAA64742 for ; Fri, 25 Aug 2000 13:36:55 +0200 (CEST) (envelope-from gunnar@pluto.sr.se) Received: (from gunnar@localhost) by pluto.sr.se (8.9.3/8.9.3) id NAA81263 for freebsd-stable@freebsd.org; Fri, 25 Aug 2000 13:36:54 +0200 (CEST) (envelope-from gunnar) Date: Fri, 25 Aug 2000 13:36:54 +0200 From: Gunnar Flygt To: FreeBSD Stable Subject: bktr-driver and XFree86 4 Message-ID: <20000825133654.A81066@sr.se> Reply-To: Gunnar Flygt Mail-Followup-To: Gunnar Flygt , FreeBSD Stable Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I installed today XFree86 6.4. I've got a Miro TV card that works (with 6.3) good with the bktr driver. But with XFree86 6.4 I get a very strange output from fxtv. The picture spills all over the screen independant of the size I have of the screen in fxtv. Has anyone else seen this problem? (The video card is Matrox Millennium G400, resolution 1280x1024, color depth 24) And the version of FreeBSD is 4.1-STABLE cvsup'ed and compiled 8th August. -- __o regards, Gunnar ---_ \<,_ email: flygt@sr.se ---- (_)/ (_) o _ _ _ _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 4:59: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by hub.freebsd.org (Postfix) with ESMTP id D51A037B42C for ; Fri, 25 Aug 2000 04:58:56 -0700 (PDT) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.10.0/jtpda-5.3.3) with ESMTP id e7PBwt987207 for ; Fri, 25 Aug 2000 13:58:55 +0200 (CEST) Received: from niobe.lpthe.jussieu.fr (root@niobe.lpthe.jussieu.fr [134.157.10.41]) by parthe.lpthe.jussieu.fr (8.9.1a/jtpda-5.3.1) with ESMTP id NAA20163 for ; Fri, 25 Aug 2000 13:58:55 +0200 (MET DST) Received: from (talon@localhost) by niobe.lpthe.jussieu.fr (8.9.3/jtpda-5.3.1) id NAA08821 for freebsd-stable@freebsd.org; Fri, 25 Aug 2000 13:58:54 +0200 (CEST) Date: Fri, 25 Aug 2000 13:58:54 +0200 From: Michel TALON To: freebsd-stable@freebsd.org Subject: GeForce Message-ID: <20000825135854.A8813@lpthe.jussieu.fr> Mail-Followup-To: freebsd-stable@freebsd.org 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 Hello, I am thinking to buy a new PC. I would like to buy a GeForce but i don't know if it is supported in FreeBSD. In fact there is a XFree driver, but there also exists linux kernel drivers, apparently related to some frame buffer device. I would be happy to have a positive answer, perhaps the kernel driver is not necessary when this frame buffer device is not enabled. Thanks very much -- Michel TALON To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 6: 5: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from user1.erieonline.com (user1.erieonline.com [63.164.22.8]) by hub.freebsd.org (Postfix) with ESMTP id 3B0F137B43C for ; Fri, 25 Aug 2000 06:05:01 -0700 (PDT) Received: from localhost (iansmith@localhost) by user1.erieonline.com (8.9.3/8.9.3) with ESMTP id JAA26817 for ; Fri, 25 Aug 2000 09:05:00 -0400 Date: Fri, 25 Aug 2000 09:05:00 -0400 (EDT) From: Smith@ian.org X-Sender: iansmith@user1.erieonline.com To: freebsd-stable@FreeBSD.ORG Subject: make release problem In-Reply-To: <4.3.2.7.2.20000824082639.00afffb8@mail.megapathdsl.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 am trying to make a release cd and I am having problems. I cvsuped to the latest of -stable, then did a 'make buildworld' and a 'make buildkernel' in /usr/src. Then I went to /usr/src/release and ran... make release \ BUILDNAME=4.1-STABLE \ CHROOTDIR=/usr/release \ RELEASETAG=RELENG_4 \ CVSROOT=/home/ncvs Everything goes fine for hours and hours and hours... and then stops here. Output is below... ----------------- cc -pg -O -pipe -DTERMIOS -DANSI_SOURCE \ -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto \ -I/usr/obj/usr/src/secure/lib/libcrypto -DNO_IDEA -DL_ENDIAN -DNO_IDEA \ -I/usr/obj/usr/src/i386/usr/include -c \ /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/pkcs7/pk7_doit.c \ -o pk7_doit.po install -C -o root -g wheel -m 444 book.html usage: install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-v] [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop in /usr/doc/de_DE.ISO_8859-1/books/handbook. *** Error code 1 ----------------- Any ideas? -- Smith@ian.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 6: 6:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 9D6FA37B422 for ; Fri, 25 Aug 2000 06:06:39 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id GAA77830; Fri, 25 Aug 2000 06:06:25 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200008251306.GAA77830@pike.osd.bsdi.com> Subject: Re: make release problem In-Reply-To: from "Smith@ian.org" at "Aug 25, 2000 09:05:00 am" To: Smith@ian.org Date: Fri, 25 Aug 2000 06:06:25 -0700 (PDT) Cc: stable@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 Smith@ian.org wrote: > I am trying to make a release cd and I am having problems. > > I cvsuped to the latest of -stable, then did a 'make buildworld' > and a 'make buildkernel' in /usr/src. Then I went to > /usr/src/release and ran... > > make release \ > BUILDNAME=4.1-STABLE \ > CHROOTDIR=/usr/release \ > RELEASETAG=RELENG_4 \ > CVSROOT=/home/ncvs > > Everything goes fine for hours and hours and hours... and then > stops here. Output is below... > > ----------------- > > cc -pg -O -pipe -DTERMIOS -DANSI_SOURCE \ > -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto \ > -I/usr/obj/usr/src/secure/lib/libcrypto -DNO_IDEA -DL_ENDIAN -DNO_IDEA \ > -I/usr/obj/usr/src/i386/usr/include -c \ > /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/pkcs7/pk7_doit.c \ > -o pk7_doit.po > install -C -o root -g wheel -m 444 book.html > usage: install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 > install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 ... > fileN directory > install -d [-v] [-g group] [-m mode] [-o owner] directory ... > *** Error code 64 Try it without the 'INSTALL=install -C' line in /etc/make.conf. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 6: 7: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id 9BB6337B440 for ; Fri, 25 Aug 2000 06:06:58 -0700 (PDT) Received: from hamlet.nectar.com (hamlet.nectar.com [10.0.1.102]) by gw.nectar.com (Postfix) with ESMTP id 708461925D; Fri, 25 Aug 2000 08:06:57 -0500 (CDT) Received: (from nectar@localhost) by hamlet.nectar.com (8.9.3/8.9.3) id IAA21619; Fri, 25 Aug 2000 08:06:57 -0500 (CDT) (envelope-from nectar@spawn.nectar.com) Date: Fri, 25 Aug 2000 08:06:57 -0500 From: "Jacques A. Vidrine" To: Gunnar Flygt Cc: FreeBSD Stable Subject: Re: bktr-driver and XFree86 4 Message-ID: <20000825080657.H9099@hamlet.nectar.com> Mail-Followup-To: "Jacques A. Vidrine" , Gunnar Flygt , FreeBSD Stable References: <20000825133654.A81066@sr.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20000825133654.A81066@sr.se>; from gunnar@pluto.sr.se on Fri, Aug 25, 2000 at 01:36:54PM +0200 X-Url: http://www.nectar.com/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 25, 2000 at 01:36:54PM +0200, Gunnar Flygt wrote: > I installed today XFree86 6.4. ^^^^^^ What is that? The latest version of XFree86 is 4.0.1. > I've got a Miro TV card that works (with > 6.3) good with the bktr driver. But with XFree86 6.4 I get a very > strange output from fxtv. The picture spills all over the screen > independant of the size I have of the screen in fxtv. > > Has anyone else seen this problem? (The video card is Matrox Millennium > G400, resolution 1280x1024, color depth 24) > > And the version of FreeBSD is 4.1-STABLE cvsup'ed and compiled 8th August. Just FYI, I'm running: bktr0: Hauppauge Model 62471 A (Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner, dbx stereo) Matrox MGA G400 AGP FreeBSD 4.1-STABLE (circa August 19) XFree86 Version 4.0.1 fxtv-1.02 and it works well. I've been running bktr + X on a couple of machines since about June 1998 and I haven't seen the type of problem you are describing. Perhaps you should post a description of your problem, the actual versions of FreeBSD + X you are running, and the output of `fxtv -debug startup' to freebsd-multimedia@freebsd.org. Maybe the folks there can help. Good luck, -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@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 Aug 25 6:11:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp03.mrf.mail.rcn.net (smtp03.mrf.mail.rcn.net [207.172.4.62]) by hub.freebsd.org (Postfix) with ESMTP id BB5BC37B42C for ; Fri, 25 Aug 2000 06:11:14 -0700 (PDT) Received: from [209.6.255.24] (helo=tigger.boston.bmc.com) by smtp03.mrf.mail.rcn.net with esmtp (Exim 3.15 #2) id 13SJGL-0002jv-00 for stable@FreeBSD.ORG; Fri, 25 Aug 2000 09:11:14 -0400 Received: (from drt@localhost) by tigger.boston.bmc.com (8.9.3/8.9.3) id JAA21170; Fri, 25 Aug 2000 09:00:02 -0400 (EDT) (envelope-from drt) To: stable@FreeBSD.ORG Subject: Re: ATAPI CD-ROM fails to mount on 4.1-STABLE References: <14756.8729.629364.19998@onceler.kciLink.com> <20000825081904.A618@freebee.attica.home> From: "David R. Tucker" Date: 25 Aug 2000 09:00:02 -0400 In-Reply-To: "Andre Goeree"'s message of "Fri, 25 Aug 2000 08:19:04 +0200" Message-ID: <86em3d8pil.fsf@tigger.boston.bmc.com> Lines: 16 X-Mailer: Gnus v5.7/Emacs 20.7 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Andre Goeree" writes: > Hello, > > Cvsup'ed src-all last night and made world, the problem is still there. > It doesn't matter if i compile a GENERIC or a custom kernel. > I'm very sure my source tree is up to date, hardware is ok. > > Any clues? I have the same problem with a CVSup from Monday. However, booting kernel.old (built August 3) instead fixes the problem without apparent side effects (i.e., ps and related programs work fine). -- David R. Tucker drt@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 6:13:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.prod.itd.earthlink.net [207.217.121.50]) by hub.freebsd.org (Postfix) with ESMTP id B73D937B422; Fri, 25 Aug 2000 06:13:32 -0700 (PDT) Received: from mickey (sdn-ar-002txhousP233.dialsprint.net [168.191.154.249]) by avocet.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with SMTP id GAA17187; Fri, 25 Aug 2000 06:13:31 -0700 (PDT) Reply-To: From: "Jason Holland" To: , , Subject: Non-recoverable failure in name resolution Date: Fri, 25 Aug 2000 08:13:05 -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) X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hello all, i'm having a problem i hope someone can help out with. i've searched the mailing lists, bug reports and newsgroups and haven't found much information on this problem. i've seen it reported in a few places, but with no reply to a fix or answer. i'm running Freebsd 4.1 stable, installed from the latest ISO grabbed off ftp.freebsd.org 2 days ago. i have setup a dns server, running bind 8.2.3-T5B from stable. nslookup returns correct information when i do host lookups bash-2.04# nslookup cs.selu.edu Server: localhost Address: 127.0.0.1 Name: cs.selu.edu Address: 147.174.59.5 bash-2.04# however, when i try to telnet, ssh or ftp to that address, i get this bash-2.04# telnet cs.selu.edu cs.selu.edu: Non-recoverable failure in name resolution bash-2.04# my /etc/host.conf file looks like this bash-2.04# cat /etc/host.conf order hosts,bind multi on bash-2.04# my /etc/resolv.conf file looks like this bash-2.04# cat /etc/resolv.conf search xxxxxxx.net nameserver 127.0.0.1 bash-2.04# my hostname, ip, and routes are correct, and i have network connectivity as telnet, ftp and ssh work correctly if i specify the IP address, instead of hostname. but who wants to type in an ip address everytime? :) btw, i tried adding a specific entry in my /etc/hosts file for that address, and i still get the same non-recoverable failure. and though i compiled a new kernel, it has no firewall support, so nothing is being blocked. one last point. if i shutdown the dns server, and put my isp's dns servers in resolv.conf, i get the same error. how can my dns server return a correct query via nslookup, but ftp, telnet or ssh fail??? this is very weird, not to mention annoying! if anyone could help me out, or point me in the right direction, i'd appreciate it. thanks!! jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 6:17:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dart.sr.se (dart.SR.SE [193.12.91.98]) by hub.freebsd.org (Postfix) with ESMTP id AB41737B42C for ; Fri, 25 Aug 2000 06:17:17 -0700 (PDT) Received: from honken.sr.se ([134.25.128.27]) by dart.sr.se (8.9.3/8.9.3) with ESMTP id PAA98922; Fri, 25 Aug 2000 15:17:06 +0200 (CEST) (envelope-from gunnar@pluto.sr.se) Received: from pluto.sr.se (pluto.SR.SE [134.25.193.91]) by honken.sr.se (8.9.3/8.9.3) with ESMTP id PAA72227; Fri, 25 Aug 2000 15:17:06 +0200 (CEST) (envelope-from gunnar@pluto.sr.se) Received: (from gunnar@localhost) by pluto.sr.se (8.9.3/8.9.3) id PAA83525; Fri, 25 Aug 2000 15:17:06 +0200 (CEST) (envelope-from gunnar) Date: Fri, 25 Aug 2000 15:17:06 +0200 From: Gunnar Flygt To: "Jacques A. Vidrine" Cc: FreeBSD Stable Subject: Re: bktr-driver and XFree86 4 Message-ID: <20000825151705.A83418@sr.se> Reply-To: Gunnar Flygt Mail-Followup-To: Gunnar Flygt , "Jacques A. Vidrine" , FreeBSD Stable References: <20000825133654.A81066@sr.se> <20000825080657.H9099@hamlet.nectar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000825080657.H9099@hamlet.nectar.com>; from n@nectar.com on Fri, Aug 25, 2000 at 08:06:57AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 25, 2000 at 08:06:57AM -0500, Jacques A. Vidrine wrote: > On Fri, Aug 25, 2000 at 01:36:54PM +0200, Gunnar Flygt wrote: > > I installed today XFree86 6.4. > ^^^^^^ > What is that? The latest version of XFree86 is 4.0.1. I'm so sorry, but that's how it was announced earlier, but of course it is 4.0.1 I guess anyone could guess that? > > > I've got a Miro TV card that works (with > > 6.3) good with the bktr driver. But with XFree86 6.4 I get a very > > strange output from fxtv. The picture spills all over the screen > > independant of the size I have of the screen in fxtv. > > > > Has anyone else seen this problem? (The video card is Matrox Millennium > > G400, resolution 1280x1024, color depth 24) > > > > And the version of FreeBSD is 4.1-STABLE cvsup'ed and compiled 8th August. > > Just FYI, I'm running: > > bktr0: Hauppauge Model 62471 A (Hauppauge WinCast/TV, Philips FR1236 > NTSC FM tuner, dbx stereo) > Matrox MGA G400 AGP > FreeBSD 4.1-STABLE (circa August 19) > XFree86 Version 4.0.1 > fxtv-1.02 > > and it works well. I've been running bktr + X on a couple of machines > since about June 1998 and I haven't seen the type of problem you are > describing. > > Perhaps you should post a description of your problem, the actual > versions of FreeBSD + X you are running, and the output of `fxtv -debug > startup' to freebsd-multimedia@freebsd.org. Maybe the folks there can > help. > > Good luck, > -- > Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org -- __o regards, Gunnar ---_ \<,_ email: flygt@sr.se ---- (_)/ (_) o _ _ _ _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 6:31:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by hub.freebsd.org (Postfix) with ESMTP id EDE6B37B43F for ; Fri, 25 Aug 2000 06:31:18 -0700 (PDT) Received: from mpc-data.demon.co.uk ([158.152.55.245] helo=burton.mpc-data.co.uk) by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1) id 13SJZk-000CPc-0B; Fri, 25 Aug 2000 13:31:17 +0000 Received: from lion.mpc-data.co.uk (root@lion.mpc-data.co.uk [192.150.92.1]) by burton.mpc-data.co.uk (8.8.7/8.8.5) with ESMTP id OAA19907; Fri, 25 Aug 2000 14:31:09 +0100 Received: from lion.mpc-data.co.uk (IDENT:mpumford@localhost [127.0.0.1]) by lion.mpc-data.co.uk (8.9.3/8.8.5) with ESMTP id OAA12146; Fri, 25 Aug 2000 14:31:07 +0100 Message-Id: <200008251331.OAA12146@lion.mpc-data.co.uk> X-Mailer: exmh version 2.0.3 To: Gunnar Flygt Cc: FreeBSD Stable Subject: Re: bktr-driver and XFree86 4 In-Reply-To: Your message of "Fri, 25 Aug 2000 13:36:54 +0200." <20000825133654.A81066@sr.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 25 Aug 2000 14:31:06 +0100 From: Mike Pumford Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I installed today XFree86 6.4. I've got a Miro TV card that works (with > 6.3) good with the bktr driver. But with XFree86 6.4 I get a very > strange output from fxtv. The picture spills all over the screen > independant of the size I have of the screen in fxtv. > > Has anyone else seen this problem? (The video card is Matrox Millennium > G400, resolution 1280x1024, color depth 24) > I had this problem with XFree86 4.0 on my Matrox G100 card. Switching to 16 bit colour depth makes it go away. I haven't had the time to try 4.0.1 at 24bit colour yet. I Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 6:35: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dart.sr.se (dart.SR.SE [193.12.91.98]) by hub.freebsd.org (Postfix) with ESMTP id 67D7137B423 for ; Fri, 25 Aug 2000 06:35:04 -0700 (PDT) Received: from honken.sr.se ([134.25.128.27]) by dart.sr.se (8.9.3/8.9.3) with ESMTP id PAA00156; Fri, 25 Aug 2000 15:34:50 +0200 (CEST) (envelope-from gunnar@pluto.sr.se) Received: from pluto.sr.se (pluto.SR.SE [134.25.193.91]) by honken.sr.se (8.9.3/8.9.3) with ESMTP id PAA73789; Fri, 25 Aug 2000 15:34:50 +0200 (CEST) (envelope-from gunnar@pluto.sr.se) Received: (from gunnar@localhost) by pluto.sr.se (8.9.3/8.9.3) id PAA85027; Fri, 25 Aug 2000 15:34:50 +0200 (CEST) (envelope-from gunnar) Date: Fri, 25 Aug 2000 15:34:50 +0200 From: Gunnar Flygt To: Mike Pumford Cc: FreeBSD Stable Subject: Re: bktr-driver and XFree86 4 Message-ID: <20000825153449.A85010@sr.se> Reply-To: Gunnar Flygt Mail-Followup-To: Gunnar Flygt , Mike Pumford , FreeBSD Stable References: <20000825133654.A81066@sr.se> <200008251331.OAA12146@lion.mpc-data.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200008251331.OAA12146@lion.mpc-data.co.uk>; from mpumford@mpc-data.co.uk on Fri, Aug 25, 2000 at 02:31:06PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 25, 2000 at 02:31:06PM +0100, Mike Pumford wrote: > > I installed today XFree86 6.4. I've got a Miro TV card that works (with > > 6.3) good with the bktr driver. But with XFree86 6.4 I get a very > > strange output from fxtv. The picture spills all over the screen > > independant of the size I have of the screen in fxtv. > > > > Has anyone else seen this problem? (The video card is Matrox Millennium > > G400, resolution 1280x1024, color depth 24) > > > I had this problem with XFree86 4.0 on my Matrox G100 card. Switching to > 16 bit colour depth makes it go away. I haven't had the time to try > 4.0.1 at 24bit colour yet. I That did it. It seems that fxtv get's totally confused when using 24bit color and XFree86 4.0.1 > > Mike > -- __o regards, Gunnar ---_ \<,_ email: flygt@sr.se ---- (_)/ (_) o _ _ _ _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 6:44: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id A96A537B424; Fri, 25 Aug 2000 06:44:00 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id GAA78622; Fri, 25 Aug 2000 06:43:48 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200008251343.GAA78622@pike.osd.bsdi.com> Subject: Re: cvs commit: src/sys/dev/ata ata-all.c ata-all.h ata-disk.c ata-dma.c atapi-cd.c atapi-cd.hh In-Reply-To: <200008220841.BAA90844@freefall.freebsd.org> from =?UNKNOWN-8BIT?Q?S=F8ren_Schmidt?= at "Aug 22, 2000 01:41:30 am" To: =?UNKNOWN-8BIT?Q?S=F8ren_Schmidt?= Date: Fri, 25 Aug 2000 06:43:48 -0700 (PDT) Cc: committers@FreeBSD.org, stable@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=UNKNOWN-8BIT Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Søren Schmidt wrote: > sos 2000/08/22 01:41:30 PDT > > Modified files: (Branch: RELENG_4) > sys/dev/ata ata-all.c ata-all.h ata-disk.c ata-dma.c > atapi-cd.c atapi-cd.h > Log: > MFC: > > Update with latest fixes from -current. > > ATA100 support. > New improved probe. > Multisector setup more restrictive ata-disk. > New error recovery in ata-disk. > Remove sequence checks in atapi-cd This breaks mounting of CD's with RockRidge extensions at least on -stable. Now when you mount a CD, it gives this error: Aug 25 05:34:46 foo /kernel: cd9660: RockRidge Extension Aug 25 05:34:46 foo /kernel: RRIP without PX field? However, it does get far enough into mounting the cdrom to get it in the list of mounts and to lock the drive: > df /cdrom Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/acd0c 125644 125644 0 100% /cdrom However, there is no actual data available: > dir /cdrom/ ls: /cdrom/: Not a directory However, /cdrom is a directory, that I normally mount CD's on. Also, I can't unmount it, even by force: > sudo umount -f /dev/acd0c umount: unmount of /cdrom failed: Invalid argument Thus, I am stuck with a locked, useless CD-ROM drive until I reboot. > uname -a FreeBSD foo.osd.bsdi.com 4.1-STABLE FreeBSD 4.1-STABLE #7: Thu Aug 24 12:34:50 PDT 2000 root@foo.osd.bsdi.com:/usr/src/sys/compile/FOO i386 .... atapci0: port 0xb800-0xb80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 .... acd0: CDROM at ata0-master using PIO4 -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 7: 0:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from teapot21.domain3.bigpond.com (teapot21.domain3.bigpond.com [139.134.5.159]) by hub.freebsd.org (Postfix) with SMTP id D00F437B423 for ; Fri, 25 Aug 2000 07:00:24 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by teapot21.domain3.bigpond.com (NTMail 3.02.13) with ESMTP id na938717 for ; Fri, 25 Aug 2000 23:52:53 +1000 Received: from CWIP-T-010-p-224-232.tmns.net.au ([203.54.224.232]) by mail3.bigpond.com (Claudes-Big-MailRouter V2.9b 5/762027); 25 Aug 2000 23:52:51 Message-ID: <39A67A13.A6783D21@telstra.com> Date: Fri, 25 Aug 2000 23:52:19 +1000 From: Wobbly Organization: TANTRUM X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 Cc: stable@FreeBSD.ORG Subject: Re: ATAPI CD-ROM fails to mount on 4.1-STABLE References: <14756.8729.629364.19998@onceler.kciLink.com> <20000825081904.A618@freebee.attica.home> <86em3d8pil.fsf@tigger.boston.bmc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Had a perfect system until yesterday, running 4.1-STABLE. cvsup -g -L 2 stable-supfile (previous cvsup was around a month ago) No changes required to kernel config file. make buildworld make buildkernel KERNEL=* make installkernel KERNEL=* single user make installworld mergemaster reboot CDROM's won't mount. The mount directory /cd0 as allocated in /etc/fstab... /dev/acd0c /cd0 cd9660 ro,noauto ...has turned itself into a FILE! Please explain? -r-xr-xr-x 1 root wheel 0 Jan 1 1970 cd0 Check the date out!! If I go try & mount my other cdrom drive, /cd1, it returns zero but won't list anything within the directory. cd /cd1 then umount /cd1 predictably returns device in use error, so it seems to function but obviously not well enough to access it. So I must reboot. Things revert to normal... drwxr-xr-x 2 root wheel 512 Jun 21 08:57 cd0 drwxr-xr-x 2 root wheel 512 Jun 21 08:57 cd1 -- (I'm GMT +10) This time I try mounting /cd1 first with a Windows 2000 CD. Zero result but still won't list the contents. umount /cd1, bung FreeBSD 4.0 RELEASE in the drawer then mount /cd1. Zero result but when I... bash-2.03# ls /cd1 /cd1 Aug 25 23:02:27 /kernel: RRIP without PX field? Aug 25 23:02:27 /kernel: RRIP without PX field? bash-2.03# mount /cd1 mount /cd1: not a directory bash-2.03# umount /cd1 umount: umount of /cd1 failed: Invalid argument bash-2.03# ls -l /cd* -r-xr-xr-x 1 root wheel 0 Jan 1 1970 /cd1 /cd0: Once again, the directory has become a file stamped with a date from the dark ages. Sorry team - this is not my idea of STABLE. Rosco. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 7: 3:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.prod.itd.earthlink.net [207.217.121.50]) by hub.freebsd.org (Postfix) with ESMTP id C255E37B423; Fri, 25 Aug 2000 07:03:02 -0700 (PDT) Received: from mickey (sdn-ar-002txhousP233.dialsprint.net [168.191.154.249]) by avocet.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with SMTP id HAA18601; Fri, 25 Aug 2000 07:02:58 -0700 (PDT) Reply-To: From: "Jason Holland" To: "Roberto Nunnari, AGIE" Cc: , , Subject: RE: Non-recoverable failure in name resolution Date: Fri, 25 Aug 2000 09:02:32 -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) X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 In-Reply-To: <39A688E5.DD1EBCC@agie.ch> Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Reverse lookup works fine > > Hi Jason. > > try this: > # nslookup 147.174.59.5 > > if that doesn't work it means that named is not set up > correctly for reverse address resolution. In fact, many > network servers do reverse address lookup. > > Cheers. > -- > Roberto Nunnari -software engineer- > mailto:roberto.nunnari@agie.ch > AGIE - http://www.agie.com > Via dei pioppi 16 tel: +41-91-8069138 > 6616 Losone """ > Switzerland (o o) > =======================oOO==(_)==OOo======================== > MY OPNIONS ARE NOT NECESSARELY THOSE OF MY EMPLOYER > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 7: 8:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gelrevision.nl (mail.gelrevision.nl [195.86.58.10]) by hub.freebsd.org (Postfix) with ESMTP id 8396737B42C for ; Fri, 25 Aug 2000 07:08:13 -0700 (PDT) Received: from [192.168.1.11] [195.86.231.176] by mail.gelrevision.nl with ESMTP (SMTPD32-6.00) id ADEC4AE011A; Fri, 25 Aug 2000 16:08:44 +0200 Date: Fri, 25 Aug 2000 16:11:04 +0200 (CEST) From: An'Era X-Sender: anera@AnEra.8.com To: stable@FreeBSD.org Subject: RTTVAR 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 guys, yesterday I upgraded userland from 4.1-R ro 4.1-S, I have been working w/ 4.0 for some time before it. Until this moment I have never seen/heard of the following message: AnEra# RTTVAR has grown to over 2.3 seconds, decreasing to 2.0 RTTVAR has grown to over 2.3 seconds, decreasing to 2.0 what does it mean and how should I deal w/ it? Thanks anyway, Maarten To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 7:10:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from web120.yahoomail.com (web120.yahoomail.com [205.180.60.121]) by hub.freebsd.org (Postfix) with SMTP id 7666537B423 for ; Fri, 25 Aug 2000 07:10:26 -0700 (PDT) Received: (qmail 24721 invoked by uid 60001); 25 Aug 2000 14:10:25 -0000 Message-ID: <20000825141025.24720.qmail@web120.yahoomail.com> Received: from [208.164.68.2] by web120.yahoomail.com; Fri, 25 Aug 2000 07:10:25 PDT Date: Fri, 25 Aug 2000 07:10:25 -0700 (PDT) From: Holtor Subject: sendmail 8.11 To: freebsd-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 I've seen quite a few e-mails about people wanting the new sendmail 8.11 merged into -stable. From those replies that was supposed to happen this week. I haven't seen an MFC yet and its Friday. I am also one who wants to see this get MFC'd right away. On a personal level I think everything in /usr/src/contrib should be kept updated and watched very closely. Bind for example on is 8.2.3-T6B with T5B still in contrib. Some other things seem out of date too. Is this because of a lack of commiters or just people having no time or perhaps other reasons? __________________________________________________ Do You Yahoo!? Yahoo! Mail - Free email you can access from anywhere! http://mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 7:46:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id B483F37B422; Fri, 25 Aug 2000 07:46:21 -0700 (PDT) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id 696F5A8AA; Sat, 26 Aug 2000 00:46:16 +1000 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id 6310654B5; Sat, 26 Aug 2000 00:46:16 +1000 (EST) Date: Sat, 26 Aug 2000 00:46:16 +1000 (EST) From: andrew@ugh.net.au To: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= Cc: stable@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/ata ata-all.c ata-all.h ata-disk.c ata-dma.c atapi-cd.c atapi-cd.hh In-Reply-To: <200008251343.GAA78622@pike.osd.bsdi.com> Message-ID: X-WonK: *wibble* 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, 25 Aug 2000, John Baldwin wrote: > This breaks mounting of CD's with RockRidge extensions at least on > -stable. But I can now turn on dma for my HD. Previously it would produce the: ad0: WRITE command timeout - resetting ata0: resetting devices .. done errors but now it seems to be working fine. Its only been a few hours but I've given it a good work out. Relevant dmesg lines: atapci0: port 0xecf0-0xecff at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 3079MB [6256/16/63] at ata0-master using WDMA2 Perhaps everyone else who was having problems should try turning DMA back on and see if things are working again...the speed is wonderful! Thanks for the fix, Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 8: 3:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from diskfarm.firehouse.net (rdu25-12-043.nc.rr.com [24.25.12.43]) by hub.freebsd.org (Postfix) with ESMTP id B5A0337B424 for ; Fri, 25 Aug 2000 08:03:09 -0700 (PDT) Received: (from abc@localhost) by diskfarm.firehouse.net (8.9.3/8.9.3) id PAA27334 for stable@FreeBSD.ORG; Fri, 25 Aug 2000 15:03:06 GMT (envelope-from abc) Date: Fri, 25 Aug 2000 15:02:51 +0000 From: Alan Clegg To: stable@FreeBSD.ORG Subject: Re: cvs commit: src/sys/dev/ata ata-all.c ata-all.h ata-disk.c ata-dma.c atapi-cd.c atapi-cd.hh Message-ID: <20000825150251.D25264@diskfarm.firehouse.net> References: <200008251343.GAA78622@pike.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from andrew@ugh.net.au on Sat, Aug 26, 2000 at 12:46:16AM +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Unless the network is lying to me again, andrew@ugh.net.au said: > > This breaks mounting of CD's with RockRidge extensions at least on > > -stable. > > But I can now turn on dma for my HD. Personally, I find the loss of CD-ROM access quite a bit more serious a problem than being able to turn on DMA for certain devices. Just my $0.02. AlanC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 8: 9:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtpo.ctimail.com (smtpo.ctimail.com [203.80.96.6]) by hub.freebsd.org (Postfix) with ESMTP id D929137B42C; Fri, 25 Aug 2000 08:09:17 -0700 (PDT) Received: from dennis (186_55user132.ctinets.com [203.186.55.132]) by smtpo.ctimail.com (8.9.3/8.9.3) with SMTP id XAA02780; Fri, 25 Aug 2000 23:13:23 +0800 (HKT) Message-ID: <000901c00ea7$44826f20$8437bacb@datawalker.com> From: =?iso-8859-1?B?pHCxag==?= To: Cc: Subject: Problem from 'make buildworld' Date: Fri, 25 Aug 2000 23:15:12 +0800 Organization: =?iso-8859-1?B?pHCxaslOra2kvaVx?= MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear sirs, Currently I used CVSup to update the source to 4.x-stable. But when I execute 'make buildworld' it shows the error message as below and stop: ../libiberty/libiberty.a(choose-temp.o): In function `make_temp_file': choose-temp.o(.text+0x264): undefined reference to `mkstemps' *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error Can you tell me how this problem can be solved? Hope to receive your solutions very soon Thanks in advance Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 8:13:44 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 E5D7037B422 for ; Fri, 25 Aug 2000 08:13:42 -0700 (PDT) Received: from pir by moek.pir.net with local (Exim) id 13SLAq-0000rh-00 for freebsd-stable@freebsd.org; Fri, 25 Aug 2000 11:13:40 -0400 Date: Fri, 25 Aug 2000 11:13:40 -0400 From: Peter Radcliffe To: freebsd-stable@freebsd.org Subject: Re: GeForce Message-ID: <20000825111340.P1236@pir.net> Reply-To: freebsd-stable@freebsd.org Mail-Followup-To: freebsd-stable@freebsd.org References: <20000825135854.A8813@lpthe.jussieu.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000825135854.A8813@lpthe.jussieu.fr>; from talon@lpthe.jussieu.fr on Fri, Aug 25, 2000 at 01:58:54PM +0200 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 Michel TALON probably said: > I am thinking to buy a new PC. I would like to buy a GeForce > but i don't know if it is supported in FreeBSD. In fact there is > a XFree driver, but there also exists linux kernel drivers, > apparently related to some frame buffer device. I would be happy > to have a positive answer, perhaps the kernel driver is not necessary > when this frame buffer device is not enabled. I'm using an AGP GeForce 1 in one of my dual boot machines. Works fine under freebsd and XFree. 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 Fri Aug 25 8:18:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mailwall1.statoil.com (mailwall.statoil.com [193.212.68.101]) by hub.freebsd.org (Postfix) with ESMTP id B98C337B43E for ; Fri, 25 Aug 2000 08:18:47 -0700 (PDT) Received: from statoil.no (mailhost.statoil.no [143.97.20.109]) by mailwall1.statoil.com (8.9.3/8.9.3) with ESMTP id RAA18687; Fri, 25 Aug 2000 17:18:46 +0200 (MET DST) Received: from stfo-lnsmtp2.statoil.no (stfo-lnsmtp2.st.statoil.no [143.97.20.149]) by statoil.no (8.9.3/8.9.3) with SMTP id RAA28453; Fri, 25 Aug 2000 17:18:45 +0200 (MET DST) Received: by stfo-lnsmtp2.statoil.no(Lotus SMTP MTA v4.6.6 (890.1 7-16-1999)) id 41256946.00599C23 ; Fri, 25 Aug 2000 17:18:46 +0100 X-Lotus-FromDomain: STATOIL@INTERNET From: "Lazaro Daniel Salem" To: FreeBSD-stable@FreeBSD.ORG Cc: lazaro@online.no Message-ID: <41256946.00599B6C.00@stfo-lnsmtp2.statoil.no> Date: Fri, 25 Aug 2000 17:18:34 +0100 Subject: Fail to"make buildworld" upgrading fresh 3.3-RELEASE using CD 4.1 -RELEASE source Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (ooops just before send this message to the list I read a similar report from smallkeung@iname.com through this list) Hi, This really surprises me, as I remember a posting to this list claiming a succesfull source upgrade (a la "make world") from a box running 2.2.8 to 4.1-STABLE ... So I wonder if this qualifies for a PR? Description: I installed a bare bones system using the 3.3-RELEASE CD-ROM (developer install), "minimally" configured the box so it is was a plain vainilla install, and then : vi /etc/make.conf <== uncommented CFLAGS and COPTFLAGS lines ("-O -pipe" ) mv /usr/src /usr/src-3.3 <== I know this is not conventional, but I think is irrelevant. mkdir -p /usr/src mount /cdrom <== after inserting teh 4.1-RELEASE CD cd /cdrom/src <== The full 4.1-RELEASE tree was already in place ./install.sh all script /var/tmp/make-buildworld-2000-08-23.log The script of the recorded session (reasonably trimmed) follows: ------------------------------------------------------------------------------- Script started on Wed Aug 23 23:23:18 2000 # 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 -------------------------------------------------------------- [...trimmed section here...] ===> objdump cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/objdump -I/usr/src/gnu/usr.bin/binutils/objdump/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/objdump/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/binutils/objdump/../libbinutils -I/usr/src/gnu/usr.bin/binutils/objdump/../../../../contrib/binutils/binutils -DBFD_VERSION=\"2.10.0\" -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/binutils/objdump/../../../../contrib/binutils/binutils/objdump.c cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/objdump -I/usr/src/gnu/usr.bin/binutils/objdump/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/objdump/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/binutils/objdump/../libbinutils -I/usr/src/gnu/usr.bin/binutils/objdump/../../../../contrib/binutils/binutils -DBFD_VERSION=\"2.10.0\" -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/binutils/objdump/../../../../contrib/binutils/binutils/prdbg.c cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/objdump -I/usr/src/gnu/usr.bin/binutils/objdump/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/objdump/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/binutils/objdump/../libbinutils -I/usr/src/gnu/usr.bin/binutils/objdump/../../../../contrib/binutils/binutils -DBFD_VERSION=\"2.10.0\" -I/usr/obj/usr/src/i386/usr/include -o objdump objdump.o prdbg.o ../libbinutils/libbinutils.a ../libopcodes/libopcodes.a ../libbfd/libbfd.a ../libiberty/libiberty.a ../libiberty/libiberty.a(choose-temp.o): In function `make_temp_file': choose-temp.o(.text+0x264): undefined reference to `mkstemps' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. # exit # exit ------------------------------------- End of script session here --------------- I want to mention that an absolutely similar "make buildworld" (same initial conditions) using the 3.5.1-RELEASE sources (instead of 4.1-RELEASE ones) worked without any problem. Thanks. P.S. please reply to salem@statoil.com with CC: lazaro@online.no ------------------------------------------------------------------- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 8:25:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gelrevision.nl (mail.gelrevision.nl [195.86.58.10]) by hub.freebsd.org (Postfix) with ESMTP id 8379C37B423 for ; Fri, 25 Aug 2000 08:25:16 -0700 (PDT) Received: from [192.168.1.11] [195.86.231.176] by mail.gelrevision.nl with ESMTP (SMTPD32-6.00) id AFFC1E760214; Fri, 25 Aug 2000 17:25:48 +0200 Date: Fri, 25 Aug 2000 17:28:10 +0200 (CEST) From: An'Era X-Sender: anera@AnEra.8.com To: FreeBSD-stable@FreeBSD.org Subject: RTTVAR 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 Hi guys, yesterday I upgraded userland from 4.1-R ro 4.1-S, I have been working w/ 4.0 for some time before it. Until this moment I have never seen/heard of the following message: AnEra# RTTVAR has grown to over 2.3 seconds, decreasing to 2.0 RTTVAR has grown to over 2.3 seconds, decreasing to 2.0 what does it mean and how should I deal w/ it? Thanks anyway, Maarten To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 8:32:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (Postfix) with ESMTP id 2CBDC37B440 for ; Fri, 25 Aug 2000 08:32:44 -0700 (PDT) Received: from tundra.winternet.com (nrahlstr@tundra.winternet.com [198.174.169.11]) by icicle.winternet.com (8.9.3/8.9.3mc) with ESMTP id KAA28284; Fri, 25 Aug 2000 10:32:42 -0500 (CDT) SMTP "HELO" (ESMTP) greeting from tundra.winternet.com But _really_ from :: nrahlstr@tundra.winternet.com [198.174.169.11] SMTP "MAIL From" = nrahlstr@mail.winternet.com (Nathan Ahlstrom) SMTP "RCPT To" = Received: (from nrahlstr@localhost) by tundra.winternet.com (8.8.7/8.8.4) id KAA18275; Fri, 25 Aug 2000 10:32:41 -0500 (CDT) Date: Fri, 25 Aug 2000 10:32:41 -0500 From: Nathan Ahlstrom To: Warner Losh Cc: Vivek Khera , FreeBSD Stable List Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) Message-ID: <20000825103240.A18222@winternet.com> Mail-Followup-To: Warner Losh , Vivek Khera , FreeBSD Stable List References: <200008241201.IAA32736@sanson.reyes.somos.net> <20000824080419.B51628@dazed.slacker.com> <14757.15655.515615.780499@onceler.kciLink.com> <20000824162123.A80150@irrelevant.org> <14757.16490.269381.416596@onceler.kciLink.com> <20000824163533.B80150@irrelevant.org> <14757.17729.113055.693358@onceler.kciLink.com> <20000824110414.C12752@winternet.com> <200008250322.VAA31765@billy-club.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200008250322.VAA31765@billy-club.village.org>; from imp@village.org on Thu, Aug 24, 2000 at 09:22:11PM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message <20000824110414.C12752@winternet.com> Nathan Ahlstrom writes: > : This PR may be of interest. > : http://www.FreeBSD.org/cgi/query-pr.cgi?pr=15830 > > Actually, no. It isn't that interesting. More interesting would be > something like the following which does it for all rcmd based things. > It is out of OpenBSD, and likely needs a couple of tweaks before it > can be committed. Much more generic. :-) > > Comments? I agree. I will try out your patch this weekend. -- Nathan Ahlstrom / nrahlstr@winternet.com / nra@FreeBSD.org / PGP: 0x67BC9D19 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 8:36:33 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 89A8337B43F for ; Fri, 25 Aug 2000 08:36:31 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 1848DE8D2 for ; Fri, 25 Aug 2000 11:36:31 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.9.3/8.9.3) id LAA68841; Fri, 25 Aug 2000 11:36:31 -0400 (EDT) (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: <14758.37502.989465.176825@onceler.kciLink.com> Date: Fri, 25 Aug 2000 11:36:30 -0400 (EDT) To: FreeBSD Stable List Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) In-Reply-To: <200008250322.VAA31765@billy-club.village.org> References: <20000824110414.C12752@winternet.com> <200008241201.IAA32736@sanson.reyes.somos.net> <20000824080419.B51628@dazed.slacker.com> <14757.15655.515615.780499@onceler.kciLink.com> <20000824162123.A80150@irrelevant.org> <14757.16490.269381.416596@onceler.kciLink.com> <20000824163533.B80150@irrelevant.org> <14757.17729.113055.693358@onceler.kciLink.com> <200008250322.VAA31765@billy-club.village.org> X-Mailer: VM 6.72 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "WL" == Warner Losh writes: WL> In message <20000824110414.C12752@winternet.com> Nathan Ahlstrom writes: WL> : This PR may be of interest. WL> : http://www.FreeBSD.org/cgi/query-pr.cgi?pr=15830 WL> Actually, no. It isn't that interesting. More interesting would be WL> something like the following which does it for all rcmd based things. WL> It is out of OpenBSD, and likely needs a couple of tweaks before it WL> can be committed. Much more generic. :-) Much more slick! I like the idea of making rcmd(3) be ssh-aware, with fallback to rsh for compatibility. It seems the only change I'll need to make to my backup process is to do it as a user of group operator rather than as root. Not a big issue. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 GPG & MIME spoken here http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 8:45:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from exchange.mistral.co.uk (gate.mistral.co.uk [195.184.225.3]) by hub.freebsd.org (Postfix) with ESMTP id 2A40837B43E for ; Fri, 25 Aug 2000 08:45:41 -0700 (PDT) Received: from bizboz.mistral.co.uk ([195.184.225.25]) by exchange.mistral.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id RQ0P8PJ9; Fri, 25 Aug 2000 16:37:26 +0100 Received: by bizboz.mistral.co.uk (Postfix, from userid 1000) id 1C6D233E; Fri, 25 Aug 2000 16:45:33 +0100 (BST) Date: Fri, 25 Aug 2000 16:45:32 +0100 From: Dominic Mitchell To: Holtor Cc: freebsd-stable@FreeBSD.ORG Subject: Re: sendmail 8.11 Message-ID: <20000825164532.A90681@bizboz.mistral.co.uk> References: <20000825141025.24720.qmail@web120.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000825141025.24720.qmail@web120.yahoomail.com>; from holtor@yahoo.com on Fri, Aug 25, 2000 at 07:10:25AM -0700 X-Warning: Incoming message from The Big Giant Head! X-OS: FreeBSD 4.1-RC i386 X-Uptime: 4:41PM up 36 days, 16 mins, 16 users, load averages: 0.09, 0.06, 0.06 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 25, 2000 at 07:10:25AM -0700, Holtor wrote: > I've seen quite a few e-mails about people wanting the new sendmail > 8.11 merged into -stable. From those replies that was supposed to > happen this week. I haven't seen an MFC yet and its Friday. I am also > one who wants to see this get MFC'd right away. Personally, I don't give a damn. I don't use it. If it's that desperate for you, you can always upgrade it yourself. > On a personal level I think everything in /usr/src/contrib should > be kept updated and watched very closely. Bind for example on is > 8.2.3-T6B with T5B still in contrib. Some other things seem out of > date too. Is this because of a lack of commiters or just people having > no time or perhaps other reasons? Realistically speaking it's probably down to available comitter time. Remember that this is -STABLE, though so things don't want to be just rushed in. That breaks things for people. The changes need to be made carefully and tested. Not only that, but the software needs to be tested in isolation outside of the FreeBSD tree first, as well. There's a lot to be said for not being first to rush new software into everything. -Dom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 8:58:39 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 8EE0637B423 for ; Fri, 25 Aug 2000 08:58:33 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 91B50E8D2 for ; Fri, 25 Aug 2000 11:58:32 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.9.3/8.9.3) id LAA68942; Fri, 25 Aug 2000 11:58:32 -0400 (EDT) (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: <14758.38824.440415.870831@onceler.kciLink.com> Date: Fri, 25 Aug 2000 11:58:32 -0400 (EDT) To: stable@freebsd.org Subject: NFS client ignores "read-only" attribute on file X-Mailer: VM 6.72 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have one MAJOR issue with the FreeBSD NFS client: it ignores read-only attribute on files owned by the current UID. Example. "kci" is a BSD/OS 4.0.1 server with all applicable patches. "onceler" is a FreeBSD 4.1-STABLE (current thru wednesday's version). The file system is served from kci to onceler. The FreeBSD system is the *only* one that ignores the read-only setting. Linux and other BSD/OS systems honor it as expected. On the server: [kci]% whoami khera [kci]% ls -l mysamplereadonlyfile -r--r--r-- 1 khera user 0 Aug 25 11:42 mysamplereadonlyfile [kci]% echo foo >> mysamplereadonlyfile mysamplereadonlyfile: Permission denied. [kci]% df . Filesystem 512-blocks Used Avail Capacity Mounted on /dev/sd1h 17227158 8928736 7437064 55% /u/kci1 On the FreeBSD 4.1-STABLE client: [onceler]% whoami khera [onceler]% ls -l mysamplereadonlyfile -r--r--r-- 1 khera user 0 Aug 25 11:42 mysamplereadonlyfile [onceler]% echo foo >> mysamplereadonlyfile [onceler]% ls -l mysamplereadonlyfile -r--r--r-- 1 khera user 4 Aug 25 11:44 mysamplereadonlyfile [onceler]% df . Filesystem 1K-blocks Used Avail Capacity Mounted on kci:/u/kci1 8613579 4464387 3718513 55% /amd/kci/u/kci1 On a Linux 2.2.10 (Redhat 6.0) client: [truffula]% whoami khera [truffula]% ls -l mysamplereadonlyfile -r--r--r-- 1 khera users 0 Aug 25 11:49 mysamplereadonlyfile [truffula]% echo foo >> mysamplereadonlyfile mysamplereadonlyfile: Permission denied. [truffula]% df . Filesystem 1k-blocks Used Available Use% Mounted on kci:/u/kci1 8613579 4464384 3718516 55% /n/kci1 On a BSD/OS 4.0.1 client: [brc]% whoami khera [brc]% ls -l mysamplereadonlyfile -r--r--r-- 1 khera user 0 Aug 25 11:49 mysamplereadonlyfile [brc]% echo foo >> mysamplereadonlyfile mysamplereadonlyfile: Permission denied. [brc]% df . Filesystem 512-blocks Used Avail Capacity Mounted on kci:/u/kci1 17227158 8928768 7437032 55% /amd/kci/u/kci1 On a BSD/OS 3.1 client: [zax]% whoami khera [zax]% ls -l mysamplereadonlyfile -r--r--r-- 1 khera user 0 Aug 25 11:49 mysamplereadonlyfile [zax]% echo foo >> mysamplereadonlyfile mysamplereadonlyfile: Permission denied. [zax]% df . Filesystem 512-blocks Used Avail Capacity Mounted on kci:/u/kci1 17227158 8928774 7437026 55% /amd/kci/u/kci1 Using a BSD/OS client (kci) from the FreeBSD box (onceler) as a NFS server: [onceler]% whoami khera [onceler]% ls -l myreadonlyfile -r--r--r-- 1 khera wheel 0 Aug 25 11:54 myreadonlyfile [onceler]% echo foo >> myreadonlyfile myreadonlyfile: Permission denied. [onceler]% df . Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1g 10401470 952122 8617231 10% /u/onceler1 [kci]% whoami khera [kci]% ls -l myreadonlyfile -r--r--r-- 1 khera wheel 0 Aug 25 11:54 myreadonlyfile [kci]% echo foo >> myreadonlyfile myreadonlyfile: Permission denied. [kci]% df . Filesystem 512-blocks Used Avail Capacity Mounted on onceler:/u/onceler1 20802940 1904244 17234462 10% /amd/onceler/u/onceler1 If I could ever get Linux to properly export to BSD/OS and/or FreeBSD, I'd try it as a server, but I think NFS on linux is a waste of my time. BSDi support feels that it is a client issue. I had the same problems with FreeBSD 3.5 NFS client. This messes me up all the time with RCS files that are read-only, and since FreeBSD client ignores that, I edit them without checking them out first, then when the file is checked out, away goes my work! I have lost much work because of this... Any ideas on what to do to fix it? -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 GPG & MIME spoken here http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 9: 8: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.venon.com (ns1.venon.com [64.7.7.83]) by hub.freebsd.org (Postfix) with ESMTP id 200F937B43C for ; Fri, 25 Aug 2000 09:08:07 -0700 (PDT) Received: from megalomaniac.biosys.net (megalomaniac.venon.com [64.7.7.82]) by ns1.venon.com (Postfix) with ESMTP id D88BCD147F for ; Fri, 25 Aug 2000 12:10:38 -0400 (EDT) Message-Id: <4.3.2.7.2.20000825120608.00b4d4a8@mail.megapathdsl.net> X-Sender: X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 25 Aug 2000 12:10:57 -0400 To: freebsd-stable@FreeBSD.ORG From: Allen Landsidel Subject: Re: NFS client ignores "read-only" attribute on file In-Reply-To: <14758.38824.440415.870831@onceler.kciLink.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:58 08/25/2000 -0400, Vivek Khera wrote: >I have one MAJOR issue with the FreeBSD NFS client: it ignores >read-only attribute on files owned by the current UID. > >Example. "kci" is a BSD/OS 4.0.1 server with all applicable patches. >"onceler" is a FreeBSD 4.1-STABLE (current thru wednesday's version). >The file system is served from kci to onceler. The FreeBSD system is >the *only* one that ignores the read-only setting. Linux and other >BSD/OS systems honor it as expected. I looked through your examples enough to say.. you proved your point.. :) This is surely the fault of whatever subsystem is responsible for user authentication.. I'm not familiar enough to say if it's the client or the server, but my gut instinct tells me it's the server. I would really uneducatedly guess that the server is not switching it's effective user id to that of the user issuing the request before the request is processed. If you could, can you see if you're allowed to modify files that you have read-only access to that are owned by another user/group? I suspect you'll be able to write to any file that you can read from. Leaving this responsibility to the client would be loony as all heck, considering anyone could then just hack up their own nfs client and use it to override file permissions on any server they had a valid user/pass on. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 9:26:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mike.net.dhis.org (hiper1-d144.stk.cwnet.com [209.142.56.144]) by hub.freebsd.org (Postfix) with ESMTP id D243637B422 for ; Fri, 25 Aug 2000 09:26:29 -0700 (PDT) Received: from es.co.nz (ogre.lan [192.168.100.1]) by mike.net.dhis.org (Postfix) with ESMTP id D48E5DF; Fri, 25 Aug 2000 09:26:22 -0700 (PDT) Message-ID: <39A69E2E.6157DC3D@es.co.nz> Date: Fri, 25 Aug 2000 09:26:22 -0700 From: Mike Muir Reply-To: mmuir@es.co.nz X-Mailer: Mozilla 4.73 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Michel TALON Cc: freebsd-stable@FreeBSD.ORG Subject: Re: GeForce References: <20000825135854.A8813@lpthe.jussieu.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michel TALON wrote: > > Hello, > > I am thinking to buy a new PC. I would like to buy a GeForce > but i don't know if it is supported in FreeBSD. In fact there is > a XFree driver, but there also exists linux kernel drivers, > apparently related to some frame buffer device. I would be happy > to have a positive answer, perhaps the kernel driver is not necessary > when this frame buffer device is not enabled. It does work fine, but without any real 3d acceleration under XFree86 4.x for now. -mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 9:33:21 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 EAAD637B43E for ; Fri, 25 Aug 2000 09:33:15 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 25 Aug 2000 17:33:14 +0100 (BST) Date: Fri, 25 Aug 2000 17:33:14 +0100 From: David Malone To: Vivek Khera Cc: stable@freebsd.org Subject: Re: NFS client ignores "read-only" attribute on file Message-ID: <20000825173313.A54258@walton.maths.tcd.ie> References: <14758.38824.440415.870831@onceler.kciLink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14758.38824.440415.870831@onceler.kciLink.com>; from khera@kciLink.com on Fri, Aug 25, 2000 at 11:58:32AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 25, 2000 at 11:58:32AM -0400, Vivek Khera wrote: > Example. "kci" is a BSD/OS 4.0.1 server with all applicable patches. > "onceler" is a FreeBSD 4.1-STABLE (current thru wednesday's version). > The file system is served from kci to onceler. The FreeBSD system is > the *only* one that ignores the read-only setting. Linux and other > BSD/OS systems honor it as expected. The BSD/OS server should not allow you to append to this file, so I would say the problem is with the server. Certainly, from a security point of view it would be the server's responsibility to impliment this. Checking the attributes of the file before writing in the client may even be difficult to get right in the client 'cos the server may do some sort of uid mapping. This problem doesn't seem to occur with a FreeBSD (4.1-STABLE) server. David. Script started on Fri Aug 25 17:26:37 2000 TERM: vt320 17:26:walton 1% df . Filesystem 1024-blocks Used Avail Capacity Mounted on u2.nfs:/u2 17773026 7401980 8949204 45% /u2 17:26:walton 2% ls -l hello ls: hello: No such file or directory 17:26:walton 3% touch hello 17:26:walton 4% chmod gu-w hello 17:27:walton 5% ls -l hello -r--r--r-- 1 dwmalone system 0 Aug 25 17:26 hello 17:27:walton 6% echo blah >> hello hello: Permission denied. 17:27:walton 7% ls -l hello -r--r--r-- 1 dwmalone system 0 Aug 25 17:26 hello To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 9:38:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 569C937B422 for ; Fri, 25 Aug 2000 09:38:38 -0700 (PDT) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id JAA02483; Fri, 25 Aug 2000 09:38:34 -0700 Message-ID: <39A6A10A.28C85CC4@urx.com> Date: Fri, 25 Aug 2000 09:38:34 -0700 From: Kent Stewart Organization: Dynacom Net X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Alan Clegg Cc: stable@FreeBSD.ORG Subject: Re: cvs commit: src/sys/dev/ata ata-all.c ata-all.h ata-disk.c ata-dma.c atapi-cd.c atapi-cd.hh References: <200008251343.GAA78622@pike.osd.bsdi.com> <20000825150251.D25264@diskfarm.firehouse.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alan Clegg wrote: > > Unless the network is lying to me again, andrew@ugh.net.au said: > > > > This breaks mounting of CD's with RockRidge extensions at least on > > > -stable. > > > > But I can now turn on dma for my HD. > > Personally, I find the loss of CD-ROM access quite a bit more serious a > problem than being able to turn on DMA for certain devices. I agree. I had to use my Win 2000 Server to add Bluefish last night. That and the reboot to get the CD out of the CDROM had me more than slightly irritated. > > Just my $0.02. > > AlanC > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html 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 Fri Aug 25 9:45:54 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 2187937B440 for ; Fri, 25 Aug 2000 09:45:52 -0700 (PDT) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id JAA18434; Fri, 25 Aug 2000 09:45:38 -0700 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda18429; Fri Aug 25 09:45:25 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id JAA19118; Fri, 25 Aug 2000 09:45:25 -0700 (PDT) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdf19116; Fri Aug 25 09:45:09 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.0/8.9.1) id e7PGj9p35623; Fri, 25 Aug 2000 09:45:09 -0700 (PDT) Message-Id: <200008251645.e7PGj9p35623@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdC35608; Fri Aug 25 09:44:30 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 4.1-RELEASE X-Sender: cy To: Vivek Khera Cc: stable@FreeBSD.ORG Subject: Re: NFS client ignores "read-only" attribute on file In-reply-to: Your message of "Fri, 25 Aug 2000 11:58:32 EDT." <14758.38824.440415.870831@onceler.kciLink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 25 Aug 2000 09:44:30 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14758.38824.440415.870831@onceler.kciLink.com>, Vivek Khera writes: > I have one MAJOR issue with the FreeBSD NFS client: it ignores > read-only attribute on files owned by the current UID. [much of note deleted for brevity] > Any ideas on what to do to fix it? I've tried your example on a couple of 4.1R systems I have at home and could not recreate the problem. I also tried your example here at work on a FreeBSD 4.1R client using a Solaris 2.6 server and a Solaris 2.6 client using a FreeBSD 4.1R client, also to no avail. Maybe something in NFS changed in FreeBSD since 4.1R? 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 Aug 25 9:56:22 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 4FBA537B423 for ; Fri, 25 Aug 2000 09:56:20 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 49773E8D2 for ; Fri, 25 Aug 2000 12:56:19 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.9.3/8.9.3) id MAA70088; Fri, 25 Aug 2000 12:56:19 -0400 (EDT) (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: <14758.42291.152000.544265@onceler.kciLink.com> Date: Fri, 25 Aug 2000 12:56:19 -0400 (EDT) To: FreeBSD-Stable Subject: Re: Can't mount 4.1 CDROM's In-Reply-To: <39A652D9.EC1EBDF6@urx.com> References: <39A652D9.EC1EBDF6@urx.com> X-Mailer: VM 6.72 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "KS" == Kent Stewart writes: KS> The only way I can get the CD out of the cdrom drive has been to reboot. If you type "eject -f acd0" you can manually eject the disk, but it still is unable to finish the mount or umount operations, and your mount point will look like an executable file rather than a directory, and have a date in 1969. Several other people have reported this in reply to my query over the last few days on this list. No fix has been forthcoming. My workaround is to run the 4.1-R kernel.GENERIC that was provided when I did my 4.1-R installation. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 GPG & MIME spoken here http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 10: 4:17 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 4CF1B37B423 for ; Fri, 25 Aug 2000 10:04:15 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 91A6EE8D2 for ; Fri, 25 Aug 2000 13:04:14 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.9.3/8.9.3) id NAA70262; Fri, 25 Aug 2000 13:04:14 -0400 (EDT) (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: <14758.42766.474382.118888@onceler.kciLink.com> Date: Fri, 25 Aug 2000 13:04:14 -0400 (EDT) To: freebsd-stable@freebsd.org Subject: Re: sendmail 8.11 In-Reply-To: <20000825141025.24720.qmail@web120.yahoomail.com> References: <20000825141025.24720.qmail@web120.yahoomail.com> X-Mailer: VM 6.72 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "H" == Holtor writes: H> On a personal level I think everything in H> /usr/src/contrib H> should be kept updated and watched very closely. Bind H> for example on is 8.2.3-T6B with T5B still in contrib. H> Some other things seem out of date too. Is this H> because H> of a lack of commiters or just people having no time H> or perhaps other reasons? Well, I think it is a matter of allocating time wisely. You say bind T6B is out, but we still have T5B. What if there are no change between these two versions that affect FreeBSD? Why bother updating it just to say you have the latest? If you *really* want bleeding edge, then it is not that much work to over-write the stuff you've got already. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 GPG & MIME spoken here http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 10: 6:16 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 0519B37B42C for ; Fri, 25 Aug 2000 10:06:15 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 7A5DCE8D2 for ; Fri, 25 Aug 2000 13:06:14 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.9.3/8.9.3) id NAA70329; Fri, 25 Aug 2000 13:06:14 -0400 (EDT) (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: <14758.42886.404967.601075@onceler.kciLink.com> Date: Fri, 25 Aug 2000 13:06:14 -0400 (EDT) To: stable@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/ata ata-all.c ata-all.h ata-disk.c ata-dma.c atapi-cd.c atapi-cd.hh In-Reply-To: References: <200008251343.GAA78622@pike.osd.bsdi.com> X-Mailer: VM 6.72 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "a" == andrew writes: a> Perhaps everyone else who was having problems should try turning DMA back a> on and see if things are working again...the speed is wonderful! DMA on/off for the ATAPI devices doesn't make a difference in the ability to mount the CDs. Though when it was working last week, it was wicked fast compared to my FreeBSD 3.5 installation on the same machine! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 10: 6:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (Postfix) with ESMTP id ADFD337B424 for ; Fri, 25 Aug 2000 10:06:14 -0700 (PDT) Received: from tao.thought.org (tao.sea.tera.com [207.108.223.55]) by gershwin.tera.com (8.9.3/8.9.3) with ESMTP id KAA10574; Fri, 25 Aug 2000 10:06:30 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.9.3/8.7.3) id KAA10644; Fri, 25 Aug 2000 10:06:10 -0700 (PDT) Date: Fri, 25 Aug 2000 10:06:09 -0700 From: Gary Kline To: Kent Stewart Cc: Gary Kline , freebsd-stable@FreeBSD.ORG Subject: Re: mouse question.... Message-ID: <20000825100609.A10594@tao.thought.org> References: <200008250449.VAA05812@tao.thought.org> <39A5FCB7.D28142D9@urx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <39A5FCB7.D28142D9@urx.com>; from kstewart@urx.com on Thu, Aug 24, 2000 at 09:57:27PM -0700 X-Organization: Thought Unlimited. Public service Unix since 1986. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 24, 2000 at 09:57:27PM -0700, Kent Stewart wrote: > > > Gary Kline wrote: > > > > Hi, Y'all, > > > > This is a long shot, but here goes. --On my other FBSD system > > which is as 4.0, the mouse won't work. A friend just checked > > the hardware ports, switched the mouse from COM1 to COM2. (COM2 > > or, in the case of my modem, /dev/cuaa1, is working.) Zip; > > nothing. He tried the mouse on this system on the other. Again, > > nothinng. He thinks that in my upgrading to 4.0, part of my > > mouse software may have been hosed. > > > > Any suggestions how I can diagnose the software side of this? > > I have always use the configure option of sysinstall to figure my mice out. > We tried this too... no success. Also, of course, XF86Setup. I was thinking it might be some hidden IRQ conflict, but trying the mouse on "COM2" disproved that. gary -- Gary D. Kline kline@tao.thought.org Public service Unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 10:14:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (Postfix) with ESMTP id CCBFA37B423 for ; Fri, 25 Aug 2000 10:14:36 -0700 (PDT) Received: from tao.thought.org (tao.sea.tera.com [207.108.223.55]) by gershwin.tera.com (8.9.3/8.9.3) with ESMTP id KAA11176; Fri, 25 Aug 2000 10:14:53 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.9.3/8.7.3) id KAA10736; Fri, 25 Aug 2000 10:14:32 -0700 (PDT) Date: Fri, 25 Aug 2000 10:14:32 -0700 From: Gary Kline To: Alfred Perlstein Cc: Gary Kline , freebsd-stable@FreeBSD.ORG Subject: Re: mouse question.... Message-ID: <20000825101432.B10594@tao.thought.org> References: <200008250449.VAA05812@tao.thought.org> <20000824223158.J1209@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000824223158.J1209@fw.wintelcom.net>; from bright@wintelcom.net on Thu, Aug 24, 2000 at 10:31:58PM -0700 X-Organization: Thought Unlimited. Public service Unix since 1986. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 24, 2000 at 10:31:58PM -0700, Alfred Perlstein wrote: > * Gary Kline [000824 21:50] wrote: > > > > Hi, Y'all, > > > > This is a long shot, but here goes. --On my other FBSD system > > which is as 4.0, the mouse won't work. A friend just checked > > the hardware ports, switched the mouse from COM1 to COM2. (COM2 > > or, in the case of my modem, /dev/cuaa1, is working.) Zip; > > nothing. He tried the mouse on this system on the other. Again, > > nothinng. He thinks that in my upgrading to 4.0, part of my > > mouse software may have been hosed. > > > > Any suggestions how I can diagnose the software side of this? > > > > I'm stumped. > > It's possible that there's a switch somewhere on the mouse that makes > it go from "microsoft" to "mousesystems" try toggling the switch > and alternating between moused settings for "microsoft" and > "mousesystems". > > Some mice have the switch but "mousesystems" doesn't seem to work > properly, so your best bet is to try both toggles with moused set > as "microsoft", once you get that working you may want to try > the other position and "mousesystems" in order to get use of your > third button if you have one. > > If your mouse doesn't have a toggle... well then save this for future > reference. :) > The mouse (Belkin? or something like that) has a switch between "Microsoft" and "PS2"; we didn't try the PS2 but the "Microsoft" setting definitely failed. The mouse on this box is that works here wouldn't work on the other FBSD computer. gary PS: It occurs to me to rcp over the /etc/XF86Config from here make the X -> link and try again with this mouse. Didn't think of that last night... . -- Gary D. Kline kline@tao.thought.org Public service Unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 10:15: 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 B395A37B423 for ; Fri, 25 Aug 2000 10:15:04 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 22643E8D3 for ; Fri, 25 Aug 2000 13:15:04 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.9.3/8.9.3) id NAA70412; Fri, 25 Aug 2000 13:15:04 -0400 (EDT) (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: <14758.43416.82239.11410@onceler.kciLink.com> Date: Fri, 25 Aug 2000 13:15:04 -0400 (EDT) To: freebsd-stable@FreeBSD.ORG Subject: Re: NFS client ignores "read-only" attribute on file In-Reply-To: <4.3.2.7.2.20000825120608.00b4d4a8@mail.megapathdsl.net> References: <14758.38824.440415.870831@onceler.kciLink.com> <4.3.2.7.2.20000825120608.00b4d4a8@mail.megapathdsl.net> X-Mailer: VM 6.72 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "AL" == Allen Landsidel writes: AL> server, but my gut instinct tells me it's the server. I would really AL> uneducatedly guess that the server is not switching it's effective user id AL> to that of the user issuing the request before the request is AL> processed. If you could, can you see if you're allowed to modify files AL> that you have read-only access to that are owned by another user/group? I AL> suspect you'll be able to write to any file that you can read from. Nope. If the file is owned by someone else, then all permissions checks work as expected. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 GPG & MIME spoken here http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 10:20: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 86CF537B422 for ; Fri, 25 Aug 2000 10:20:05 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 423B1E8D3 for ; Fri, 25 Aug 2000 13:20:04 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.9.3/8.9.3) id NAA70449; Fri, 25 Aug 2000 13:20:04 -0400 (EDT) (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: <14758.43716.147642.132756@onceler.kciLink.com> Date: Fri, 25 Aug 2000 13:20:04 -0400 (EDT) To: stable@FreeBSD.ORG Subject: Re: NFS client ignores "read-only" attribute on file In-Reply-To: <200008251645.e7PGj9p35623@cwsys.cwsent.com> References: <14758.38824.440415.870831@onceler.kciLink.com> <200008251645.e7PGj9p35623@cwsys.cwsent.com> X-Mailer: VM 6.72 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "CS" == Cy Schubert <- ITSD Open Systems Group > writes: CS> I've tried your example on a couple of 4.1R systems I have at home and CS> could not recreate the problem. I also tried your example here at work CS> on a FreeBSD 4.1R client using a Solaris 2.6 server and a Solaris 2.6 CS> client using a FreeBSD 4.1R client, also to no avail. CS> Maybe something in NFS changed in FreeBSD since 4.1R? Or maybe it is some cleverly disguised BSD/OS 4.0.1 NFS server issue... I don't know for sure. I'm going to set up my second FreeBSD box later today and will test freebsd as both client/server to see if maybe I'm doing something wrong... -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 GPG & MIME spoken here http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 10:24:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 6A21137B42C for ; Fri, 25 Aug 2000 10:24:42 -0700 (PDT) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id KAA02648; Fri, 25 Aug 2000 10:24:34 -0700 Message-ID: <39A6ABD2.D57FBC07@urx.com> Date: Fri, 25 Aug 2000 10:24:34 -0700 From: Kent Stewart Organization: Dynacom Net X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Vivek Khera Cc: FreeBSD-Stable Subject: Re: Can't mount 4.1 CDROM's References: <39A652D9.EC1EBDF6@urx.com> <14758.42291.152000.544265@onceler.kciLink.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vivek Khera wrote: > > >>>>> "KS" == Kent Stewart writes: > > KS> The only way I can get the CD out of the cdrom drive has been to reboot. > > If you type "eject -f acd0" you can manually eject the disk, but it > still is unable to finish the mount or umount operations, and your > mount point will look like an executable file rather than a directory, > and have a date in 1969. I saw that /cdrom had changed to cdrom* when I ran my ll alias. The eject will get me around rebooting the computer. That was the most irritating part. I couldn't eject and the device was permanently busy at that point. I was having problems building bluefish port and had to ftp the package from my Win 2000 Server. That was the only non-FreeBSD system that could read the CDROM. > > Several other people have reported this in reply to my query over the > last few days on this list. No fix has been forthcoming. > > My workaround is to run the 4.1-R kernel.GENERIC that was provided > when I did my 4.1-R installation. I rebuilt my kernel.GENERIC last night on my server. That didn't help and that is when I added my message to the queue. I had a suggestion from Sean to use cvsweb to back out the change to atapi-cd.[ch]. Thanks, Kent > > -- > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Vivek Khera, Ph.D. Khera Communications, Inc. > Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 > GPG & MIME spoken here http://www.khera.org/~vivek/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html 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 Fri Aug 25 10:25:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mproxy.zedo.fuedo.de (mproxy.zedo.fuedo.de [193.99.167.226]) by hub.freebsd.org (Postfix) with ESMTP id 9971D37B422; Fri, 25 Aug 2000 10:25:17 -0700 (PDT) Received: from master.zkom.de (master.zkom.de [193.99.166.6]) by mproxy.zedo.fuedo.de (8.9.3/8.9.3) with ESMTP id TAA23364; Fri, 25 Aug 2000 19:25:16 +0200 (CEST) Received: from zkom.de (jack.zkom.de [193.99.166.10]) by master.zkom.de (8.9.1a/8.8.8) with ESMTP id TAA05122; Fri, 25 Aug 2000 19:25:15 +0200 (CEST) (envelope-from hartung@zkom.de) Message-ID: <39A6AC0C.2F8A6D3B@zkom.de> Date: Fri, 25 Aug 2000 19:25:33 +0200 From: Michael Hartung Organization: ZKOM GmbH, Fax: +49 (0)231 9700 474, Germany X-Mailer: Mozilla 4.61 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-isp@freebsd.org Subject: HW-RAID1 FreeBSD 4.1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi girls and boys, We need to setup a server with HW-raid (RAID1 mirroring / 30-60Gbyte). LINT says: # RAID controllers device ida # Compaq Smart RAID device amr # AMI MegaRAID device mlx # Mylex DAC960 family Of course the OS schould be FreeBSD (4.1). Which controller is supported/a good choice? What about the configuration-SW? Is there a substitute for the Mylex DAC960 which is not longer available? Which Compaq, AMI models are supported? A nice weekend and thanks in advance. Michael Hartung -- Michael Hartung |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | ZKOM GmbH | | State Diagnostics Systems | | and Computer Networks | | | | WWW: www.zkom.de (WebCam) | | | | Joseph-von-Fraunhofer Str. 20 | | D-44227 Dortmund | | Germany | | E-mail: hartung@zkom.de | | Phone: +49 (0)231 / 9700 336 | | Fax: +49 (0)231 / 9700 474 | | Mobile: +49 (0)172 / 67 70 522 | | | | AG Dortmund HRB 12918 | | Managing Director: Dipl.-Ing. Michael Hartung | |_______________________________________________| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 10:41:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id D4C2137B43C for ; Fri, 25 Aug 2000 10:41:02 -0700 (PDT) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id KAA02689; Fri, 25 Aug 2000 10:40:26 -0700 Message-ID: <39A6AF8A.5813CBE4@urx.com> Date: Fri, 25 Aug 2000 10:40:26 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Wobbly Cc: stable@FreeBSD.ORG Subject: Re: ATAPI CD-ROM fails to mount on 4.1-STABLE References: <14756.8729.629364.19998@onceler.kciLink.com> <20000825081904.A618@freebee.attica.home> <86em3d8pil.fsf@tigger.boston.bmc.com> <39A67A13.A6783D21@telstra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wobbly wrote: > > Had a perfect system until yesterday, running 4.1-STABLE. > > cvsup -g -L 2 stable-supfile (previous cvsup was around a month ago) > > No changes required to kernel config file. > > make buildworld > make buildkernel KERNEL=* > make installkernel KERNEL=* You only have to go back to 20 August. The changes that broke atapi-cd.[ch] were made by SOS on 22 Aug 2000. The cvs log shows $FreeBSD: src/sys/dev/ata/atapi-cd.c,v 1.63 $FreeBSD: src/sys/dev/ata/atapi-cd.h,v 1.19 This was after the date of my kernel.old and my cvsup and rebuild last night. Kent > > single user > > make installworld > mergemaster > reboot > > CDROM's won't mount. > > The mount directory /cd0 as allocated in /etc/fstab... > > /dev/acd0c /cd0 cd9660 ro,noauto > > ...has turned itself into a FILE! Please explain? > > -r-xr-xr-x 1 root wheel 0 Jan 1 1970 cd0 > > Check the date out!! > > If I go try & mount my other cdrom drive, /cd1, it returns zero but > won't list anything within the directory. cd /cd1 then umount /cd1 > predictably returns device in use error, so it seems to function but > obviously not well enough to access it. > > So I must reboot. Things revert to normal... > > drwxr-xr-x 2 root wheel 512 Jun 21 08:57 cd0 > drwxr-xr-x 2 root wheel 512 Jun 21 08:57 cd1 -- (I'm GMT +10) > > This time I try mounting /cd1 first with a Windows 2000 CD. Zero result > but still won't list the contents. umount /cd1, bung FreeBSD 4.0 RELEASE > in the drawer then mount /cd1. Zero result but when I... > > bash-2.03# ls /cd1 > /cd1 > Aug 25 23:02:27 /kernel: RRIP without PX field? > Aug 25 23:02:27 /kernel: RRIP without PX field? > > bash-2.03# mount /cd1 > mount /cd1: not a directory > > bash-2.03# umount /cd1 > umount: umount of /cd1 failed: Invalid argument > > bash-2.03# ls -l /cd* > -r-xr-xr-x 1 root wheel 0 Jan 1 1970 /cd1 > > /cd0: > > Once again, the directory has become a file stamped with a date from > the dark ages. > > Sorry team - this is not my idea of STABLE. > > Rosco. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 10:49:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.venon.com (ns1.venon.com [64.7.7.83]) by hub.freebsd.org (Postfix) with ESMTP id 50BA237B43F for ; Fri, 25 Aug 2000 10:49:51 -0700 (PDT) Received: from megalomaniac.biosys.net (megalomaniac.venon.com [64.7.7.82]) by ns1.venon.com (Postfix) with ESMTP id 706FAD147F for ; Fri, 25 Aug 2000 13:52:18 -0400 (EDT) Message-Id: <4.3.2.7.2.20000825133648.00b5ca80@mail.megapathdsl.net> X-Sender: X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 25 Aug 2000 13:52:36 -0400 To: freebsd-stable@freebsd.org From: Allen Landsidel Subject: Re: NFS client ignores "read-only" attribute on file In-Reply-To: <14758.43416.82239.11410@onceler.kciLink.com> References: <4.3.2.7.2.20000825120608.00b4d4a8@mail.megapathdsl.net> <14758.38824.440415.870831@onceler.kciLink.com> <4.3.2.7.2.20000825120608.00b4d4a8@mail.megapathdsl.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 13:15 08/25/2000 -0400, you wrote: > >>>>> "AL" == Allen Landsidel writes: > >AL> server, but my gut instinct tells me it's the server. I would really >AL> uneducatedly guess that the server is not switching it's effective >user id >AL> to that of the user issuing the request before the request is >AL> processed. If you could, can you see if you're allowed to modify files >AL> that you have read-only access to that are owned by another >user/group? I >AL> suspect you'll be able to write to any file that you can read from. > >Nope. If the file is owned by someone else, then all permissions >checks work as expected. You know, I didn't quite get it before.. but kci is the server correct? All the other clients you listed are connection to that server? I really should know more about NFS before trying to figure this out, so pardon all the nfs-newbie questions... In my guess, the server would behave this way if the client was authing with higher user rights than your whoami is showing.. I'm assuming the authentication happens when the remote directory is first mounted, correct me if I'm wrong. If that's the case, then it's possible that you set up the nfs mount as root on the two clients that don't appear to be respecting the rights.. but here is the bottom line. The rights on the files are filesystem rights, set on the server, without any regard to NFS. The only users allowed to write to those files are users/groups with +w access, root, or of course anyone if it's world writable. The nfs server must run as a user, and the server itself is restricted by the rights assigned to the user that it runs as. Regardless of what the client tells it to do, it can't do it if the uid that it's running as doesn't have the permission. This means that the server must be running with at least and euid of root in order to carry out the request when it overwrites the file.. two possibilities come to mind regarding this. 1. The server is running as root, and the client is authing as root when it connects, thus giving the connection root privileges. 2. The server runs as the euid of the uid/passwd it is provided with when the connection is established, and again the client is providing valid root authentication when it connects. I don't believe that NFS runs like an inetd daemon does it, instantiated on a per/client basis? If not, then it must always be running with at least an euid of root so that it can access all the files regardless of who the calling user is. It's also possible that on the clients that fail, the NFS client is suid root? Again.. I don't know diddly about how NFS auth occurs or when.. but I imagine it asks for a uid/passwd when you run it to mount the remote directory? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 11:10:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from user1.erieonline.com (user1.erieonline.com [63.164.22.8]) by hub.freebsd.org (Postfix) with ESMTP id 5388237B50C for ; Fri, 25 Aug 2000 11:09:37 -0700 (PDT) Received: from localhost (iansmith@localhost) by user1.erieonline.com (8.9.3/8.9.3) with ESMTP id OAA00702; Fri, 25 Aug 2000 14:09:33 -0400 Date: Fri, 25 Aug 2000 14:09:33 -0400 (EDT) From: Smith@ian.org X-Sender: iansmith@user1.erieonline.com To: John Baldwin Cc: stable@FreeBSD.ORG Subject: Re: make release problem In-Reply-To: <200008251306.GAA77830@pike.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 25 Aug 2000, John Baldwin wrote: > > install -C -o root -g wheel -m 444 book.html > > usage: install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 > > install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 ... > > fileN directory > > install -d [-v] [-g group] [-m mode] [-o owner] directory ... > > *** Error code 64 > > Try it without the 'INSTALL=install -C' line in /etc/make.conf. There is no /etc/make.conf on this machine. -- Smith@ian.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 11:23:14 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 F034137B43E; Fri, 25 Aug 2000 11:23:10 -0700 (PDT) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 60F2B9B05; Fri, 25 Aug 2000 14:23:10 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 41228BA03; Fri, 25 Aug 2000 14:23:10 -0400 (EDT) Date: Fri, 25 Aug 2000 14:23:10 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Smith@ian.org Cc: freebsd-stable@FreeBSD.ORG, alex@FreeBSD.org Subject: Re: make release problem 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, 25 Aug 2000 Smith@ian.org wrote: > I am trying to make a release cd and I am having problems. > > I cvsuped to the latest of -stable, then did a 'make buildworld' > and a 'make buildkernel' in /usr/src. Then I went to > /usr/src/release and ran... > > make release \ > BUILDNAME=4.1-STABLE \ > CHROOTDIR=/usr/release \ > RELEASETAG=RELENG_4 \ > CVSROOT=/home/ncvs > > Everything goes fine for hours and hours and hours... and then > stops here. Output is below... > > ----------------- > > install -C -o root -g wheel -m 444 book.html > usage: install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 > install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 ... > fileN directory > install -d [-v] [-g group] [-m mode] [-o owner] directory ... > *** Error code 64 > > Stop in /usr/doc/de_DE.ISO_8859-1/books/handbook. > *** Error code 1 > This is due to a non-existent doc/de_DE.ISO_8859-1/books/handbook/Makefile.inc which should contain: DESTDIR?= ${DOCDIR}/de_DE.ISO_8859-1/books/${.CURDIR:T} in order to set DESTDIR (which the above command obviously does not have). Until this is fixed, your best bet is to build your release with NODOC set. ----- 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 Aug 25 11:29: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id 62AF037B446 for ; Fri, 25 Aug 2000 11:28:56 -0700 (PDT) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id e7PIStU27350 for ; Fri, 25 Aug 2000 11:28:56 -0700 (PDT) Message-Id: <200008251828.e7PIStU27350@ptavv.es.net> To: stable@freebsd.org Subject: pcm device locks on some errors Date: Fri, 25 Aug 2000 11:28:55 -0700 From: "Kevin Oberman" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have noticed that if I have problems with the pcm device (like a very busy CPU that can't keep it fed), the pcm device fails and I can't use it again without a reboot. Is this a known problem? Is there a workaround that can clear it? ThinkPad 600E running 4.1-Stable from August 18 using the integral Crystal Semiconductor audio and the pcm device. Thanks, R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 11:29: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 E7A0637B422 for ; Fri, 25 Aug 2000 11:29:23 -0700 (PDT) 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 MAA76312; Fri, 25 Aug 2000 12:29:19 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA18432; Fri, 25 Aug 2000 12:29:13 -0600 (MDT) Message-Id: <200008251829.MAA18432@harmony.village.org> To: "Lazaro Daniel Salem" Subject: Re: Fail to"make buildworld" upgrading fresh 3.3-RELEASE using CD 4.1 -RELEASE source Cc: FreeBSD-stable@FreeBSD.ORG, lazaro@online.no In-reply-to: Your message of "Fri, 25 Aug 2000 17:18:34 BST." <41256946.00599B6C.00@stfo-lnsmtp2.statoil.no> References: <41256946.00599B6C.00@stfo-lnsmtp2.statoil.no> Date: Fri, 25 Aug 2000 12:29:13 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <41256946.00599B6C.00@stfo-lnsmtp2.statoil.no> "Lazaro Daniel Salem" writes: : objdump.o prdbg.o ../libbinutils/libbinutils.a ../libopcodes/libopcodes.a : ../libbfd/libbfd.a ../libiberty/libiberty.a : ../libiberty/libiberty.a(choose-temp.o): In function `make_temp_file': : choose-temp.o(.text+0x264): undefined reference to `mkstemps' I think that you need to upgrade to 3.4 (or better yet 3.5.1) before you can make the jump to -stable. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 11:33:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mout2.silyn-tek.de (mout2.silyn-tek.de [194.25.165.70]) by hub.freebsd.org (Postfix) with ESMTP id 88BD037B509 for ; Fri, 25 Aug 2000 11:33:48 -0700 (PDT) Received: from [192.168.32.33] (helo=mx1.silyn-tek.de) by mout2.silyn-tek.de with esmtp (Exim 3.13 #1) id 13SOIV-0006V0-00; Fri, 25 Aug 2000 20:33:47 +0200 Received: from p3e9e2791.dip0.t-ipconnect.de ([62.158.39.145] helo=neutron.cichlids.com) by mx1.silyn-tek.de with esmtp (Exim 3.13 #1) id 13SOIU-0002jW-00; Fri, 25 Aug 2000 20:33:46 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id 82290AB91; Fri, 25 Aug 2000 20:35:02 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id 8EC6014B8A; Fri, 25 Aug 2000 20:33:27 +0200 (CEST) Date: Fri, 25 Aug 2000 20:33:27 +0200 From: Alexander Langer To: "Chris D. Faulhaber" Cc: Smith@ian.org, freebsd-stable@FreeBSD.ORG Subject: Re: make release problem Message-ID: <20000825203327.B43892@cichlids.cichlids.com> Mail-Followup-To: "Chris D. Faulhaber" , Smith@ian.org, freebsd-stable@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from jedgar@fxp.org on Fri, Aug 25, 2000 at 02:23:10PM -0400 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Chris D. Faulhaber (jedgar@fxp.org): > > This is due to a non-existent > doc/de_DE.ISO_8859-1/books/handbook/Makefile.inc which should contain: ok. I'll add it, thanks. Alex, who has obviously not tested release. *sigh* (ignore my private mail, Chris :) -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 11:35: 8 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 E91E137B423 for ; Fri, 25 Aug 2000 11:35:05 -0700 (PDT) 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 MAA76376; Fri, 25 Aug 2000 12:35:04 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA18552; Fri, 25 Aug 2000 12:34:59 -0600 (MDT) Message-Id: <200008251834.MAA18552@harmony.village.org> To: Vivek Khera Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) Cc: FreeBSD Stable List In-reply-to: Your message of "Fri, 25 Aug 2000 11:36:30 EDT." <14758.37502.989465.176825@onceler.kciLink.com> References: <14758.37502.989465.176825@onceler.kciLink.com> <20000824110414.C12752@winternet.com> <200008241201.IAA32736@sanson.reyes.somos.net> <20000824080419.B51628@dazed.slacker.com> <14757.15655.515615.780499@onceler.kciLink.com> <20000824162123.A80150@irrelevant.org> <14757.16490.269381.416596@onceler.kciLink.com> <20000824163533.B80150@irrelevant.org> <14757.17729.113055.693358@onceler.kciLink.com> <200008250322.VAA31765@billy-club.village.org> Date: Fri, 25 Aug 2000 12:34:59 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14758.37502.989465.176825@onceler.kciLink.com> Vivek Khera writes: : Much more slick! I like the idea of making rcmd(3) be ssh-aware, with : fallback to rsh for compatibility. It seems the only change I'll need : to make to my backup process is to do it as a user of group operator : rather than as root. Not a big issue. I have changes in my tree that ports the dump changes that OpenBSD did a while ago to make dump/restore not setgid anymore. But it requires that I port changes to wall to support -g. Alternatively, I need to add group support to syslogd, which would be much more generic (thanks to bde, I think, for this idea). Now, all I need is a good syntax for groups. Right now you have / -> log to file * -> all users @h -> log to host h | -> log to program u1,u2 -> log to users u1 and u2 and I'm thinking that : might be a good idea: :g -> log to all members of group g logged into the machine. I'm not sure which way to go at this point. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 11:40:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 469E137B423; Fri, 25 Aug 2000 11:40:13 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA82938; Fri, 25 Aug 2000 20:40:03 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200008251840.UAA82938@freebsd.dk> Subject: Re: cvs commit: src/sys/dev/ata ata-all.c ata-all.h ata-disk.c ata-dma.c atapi-cd.c atapi-cd.hh In-Reply-To: from "andrew@ugh.net.au" at "Aug 26, 2000 00:46:16 am" To: andrew@ugh.net.au Date: Fri, 25 Aug 2000 20:40:03 +0200 (CEST) Cc: sos@FreeBSD.org ([?X-UNKNOWN?]), stable@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems andrew@ugh.net.au wrote: > > > On Fri, 25 Aug 2000, John Baldwin wrote: > > > This breaks mounting of CD's with RockRidge extensions at least on > > -stable. That I've just fixed, too much current'ness crept in, sorry about that.. > But I can now turn on dma for my HD. Previously it would produce the: > > ad0: WRITE command timeout - resetting > ata0: resetting devices .. done > > errors but now it seems to be working fine. Its only been a few hours but > I've given it a good work out. Relevant dmesg lines: > > atapci0: port 0xecf0-0xecff at device 7.1 on > pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > ad0: 3079MB [6256/16/63] at ata0-master using > WDMA2 Glad to hear that! -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 11:53:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id D62B237B424 for ; Fri, 25 Aug 2000 11:53:49 -0700 (PDT) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id LAA00006; Fri, 25 Aug 2000 11:53:45 -0700 Message-ID: <39A6C0B8.9798A4F1@urx.com> Date: Fri, 25 Aug 2000 11:53:44 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Vivek Khera Cc: stable@FreeBSD.ORG Subject: Re: ATAPI CD-ROM fails to mount on 4.1-STABLE [FIXED] References: <14756.8729.629364.19998@onceler.kciLink.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just applied the diff's to atapi-cd.c that were just committed as version 1.48.2.5 and I have my atapi CDROM back. Kent Vivek Khera wrote: > > I updated my 4.1-STABLE yesterday. Today I tried to read a CD-ROM > (the FreeBSD 4.1-R install CD, and also one generic data CD I made a > while back that was ok on this system before) and the mount never > completes. > > Here's what happens. > > I insert the CD and type "mount /cdrom". The mount command returns. > The /var/log/messages syslog contains this entry: > > /kernel: cd9660: RockRidge Extension > > I do an "ls /cdrom" and I get either > > -r-xr-xr-x 1 root wheel 0 Dec 31 1969 /cdrom* > > or some generic "input/output error" from ls. Before the mount, the > /cdrom directory looks like this: > > drwxr-xr-x 2 khera wheel 512 Aug 11 14:13 /cdrom > > The syslog now contains this entry: > > /kernel: RRIP without PX field? > > I can no longer umount or "eject -f" the drive: > > umount: unmount of /cdrom failed: Invalid argument > > eject: Device busy > > However, after running eject, I can manually eject the disk. > > The "mount" command says this: > > /dev/acd0c on /cdrom (cd9660, local, nodev, nosuid, read-only, mounted by khera, reads: sync 3 async 0) > > It matters not whether I run mount as root or as a user. > > The only way out is a reboot. Booting the 4.1-R kernel.GENERIC, I can > mount and read the CD-ROM just fine. It worked fine as of last friday > as well, when I last did an update and used the CD-ROM. To me, this > rules out hardware problems. > > I just cvsup'd again, and rebuilt a kernel (with DMA for ATAPI turned > off) but that made no difference. (about 2:30pm EDT 23-AUG-2000) > > Any clues as to what to do to get back my CD-ROM drive functionality? > > Anyone else experiencing this trouble? > > Thanks. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 12: 4: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 4B4C637B422 for ; Fri, 25 Aug 2000 12:04:28 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id E0BBAE8D2 for ; Fri, 25 Aug 2000 15:04:18 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.9.3/8.9.3) id PAA72873; Fri, 25 Aug 2000 15:04:18 -0400 (EDT) (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: <14758.49970.815600.933815@onceler.kciLink.com> Date: Fri, 25 Aug 2000 15:04:18 -0400 (EDT) To: stable@FreeBSD.ORG Subject: Re: ATAPI CD-ROM fails to mount on 4.1-STABLE [FIXED] In-Reply-To: <39A6C0B8.9798A4F1@urx.com> References: <14756.8729.629364.19998@onceler.kciLink.com> <39A6C0B8.9798A4F1@urx.com> X-Mailer: VM 6.72 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "KS" == Kent Stewart writes: KS> I just applied the diff's to atapi-cd.c that were just committed as KS> version 1.48.2.5 and I have my atapi CDROM back. I'm about to reboot into such a kernel. I'm glad to hear it is fixed! -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 GPG & MIME spoken here http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 12: 6:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 4C66837B423 for ; Fri, 25 Aug 2000 12:06:38 -0700 (PDT) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id MAA00046; Fri, 25 Aug 2000 12:06:32 -0700 Message-ID: <39A6C3B8.FBE42898@urx.com> Date: Fri, 25 Aug 2000 12:06:32 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Lazaro Daniel Salem , FreeBSD-stable@FreeBSD.ORG, lazaro@online.no Subject: Re: Fail to"make buildworld" upgrading fresh 3.3-RELEASE using CD 4.1 -RELEASE source References: <41256946.00599B6C.00@stfo-lnsmtp2.statoil.no> <200008251829.MAA18432@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 Anyone in the process of cvsup'ing to 4.1-Stable need to re-cvsup. The atapi-cd.c module was broken on 22 Aug for cd9660 CDROM's and changes were just committed to fix it. I haven't re-cvsup'ed but applied the changes manually. After rebooting to the new kernel, I could mount my 4.1-R CDROM's. Kent Warner Losh wrote: > > In message <41256946.00599B6C.00@stfo-lnsmtp2.statoil.no> "Lazaro Daniel Salem" writes: > : objdump.o prdbg.o ../libbinutils/libbinutils.a ../libopcodes/libopcodes.a > : ../libbfd/libbfd.a ../libiberty/libiberty.a > : ../libiberty/libiberty.a(choose-temp.o): In function `make_temp_file': > : choose-temp.o(.text+0x264): undefined reference to `mkstemps' > > I think that you need to upgrade to 3.4 (or better yet 3.5.1) before > you can make the jump to -stable. > > Warner > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 12:11: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from accord.grasslake.net (accord.grasslake.net [206.11.249.240]) by hub.freebsd.org (Postfix) with ESMTP id DEC4437B42C for ; Fri, 25 Aug 2000 12:10:59 -0700 (PDT) Received: from marlowe (accord.grasslake.net [206.11.249.240]) by accord.grasslake.net (8.9.3/8.9.3) with SMTP id OAA06870 for ; Fri, 25 Aug 2000 14:12:16 -0500 (CDT) (envelope-from swb@grasslake.net) Message-ID: <012401c00ec8$4a7c6bd0$b8209fc0@marlowe> From: "Shawn Barnhart" To: Subject: Can I run two inetd processes? Date: Fri, 25 Aug 2000 14:11:35 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm pretty sure the answer to this is "yes", but if I use the -a option (probably along with -p) and a seperate config file when launching inetd, can I launch it twice? I'd like a "secure" inetd for my external NIC and a more permissive inetd for my internal connection. Is this how the -a option is supposed to be used? Is there a clean way to do this within rc.conf, or should the second one just get launched from /usr/local/etc/rc.d? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 12:11:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id 12B9137B506 for ; Fri, 25 Aug 2000 12:11:06 -0700 (PDT) Received: from hamlet.nectar.com (hamlet.nectar.com [10.0.1.102]) by gw.nectar.com (Postfix) with ESMTP id EF0341925F; Fri, 25 Aug 2000 14:11:05 -0500 (CDT) Received: (from nectar@localhost) by hamlet.nectar.com (8.9.3/8.9.3) id OAA22242; Fri, 25 Aug 2000 14:11:05 -0500 (CDT) (envelope-from nectar@spawn.nectar.com) Date: Fri, 25 Aug 2000 14:11:05 -0500 From: "Jacques A. Vidrine" To: Mike Pumford Cc: Gunnar Flygt , FreeBSD Stable Subject: Re: bktr-driver and XFree86 4 Message-ID: <20000825141105.B22129@hamlet.nectar.com> Mail-Followup-To: "Jacques A. Vidrine" , Mike Pumford , Gunnar Flygt , FreeBSD Stable References: <20000825133654.A81066@sr.se> <200008251331.OAA12146@lion.mpc-data.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200008251331.OAA12146@lion.mpc-data.co.uk>; from mpumford@mpc-data.co.uk on Fri, Aug 25, 2000 at 02:31:06PM +0100 X-Url: http://www.nectar.com/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 25, 2000 at 02:31:06PM +0100, Mike Pumford wrote: > I had this problem with XFree86 4.0 on my Matrox G100 card. Switching to > 16 bit colour depth makes it go away. I haven't had the time to try > 4.0.1 at 24bit colour yet. Hmm, good point. I also run at 16 bits. -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@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 Aug 25 12:23:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 92B8137B423 for ; Fri, 25 Aug 2000 12:23:07 -0700 (PDT) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id MAA00100; Fri, 25 Aug 2000 12:23:04 -0700 Message-ID: <39A6C798.8784C30A@urx.com> Date: Fri, 25 Aug 2000 12:23:04 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Lazaro Daniel Salem Cc: FreeBSD-stable@FreeBSD.ORG, lazaro@online.no Subject: Re: Fail to"make buildworld" upgrading fresh 3.3-RELEASE using CD 4.1-RELEASE source References: <41256946.00599B6C.00@stfo-lnsmtp2.statoil.no> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lazaro Daniel Salem wrote: > > (ooops just before send this message to the list I read a similar report > from smallkeung@iname.com through this list) > > Hi, > > This really surprises me, as I remember a posting to this list claiming > a succesfull source upgrade (a la "make world") from a box running 2.2.8 > to 4.1-STABLE ... So I wonder if this qualifies for a PR? You missed his follow up. IIRC, he installed to a new HD and then moved his 2.2.8 system over to the 4.1 system. It didn't count as a 2.2.8 to 4.1-Stable upgrade. Kent > > Description: > I installed a bare bones system using the 3.3-RELEASE CD-ROM (developer > install), > "minimally" configured the box so it is was a plain vainilla install, and then : > > vi /etc/make.conf <== uncommented CFLAGS and COPTFLAGS lines ("-O -pipe" ) > mv /usr/src /usr/src-3.3 <== I know this is not conventional, but I think is > irrelevant. > mkdir -p /usr/src > mount /cdrom <== after inserting teh 4.1-RELEASE CD > cd /cdrom/src <== The full 4.1-RELEASE tree was already in place > ./install.sh all > script /var/tmp/make-buildworld-2000-08-23.log > > The script of the recorded session (reasonably trimmed) follows: > ------------------------------------------------------------------------------- > > Script started on Wed Aug 23 23:23:18 2000 > # 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 > -------------------------------------------------------------- > > [...trimmed section here...] > > ===> objdump > cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/objdump > -I/usr/src/gnu/usr.bin/binutils/objdump/../libbfd/i386 > -I/usr/src/gnu/usr.bin/binutils/objdump/../../../../contrib/binutils/include > -I/usr/src/gnu/usr.bin/binutils/objdump/../libbinutils > -I/usr/src/gnu/usr.bin/binutils/objdump/../../../../contrib/binutils/binutils > -DBFD_VERSION=\"2.10.0\" -I/usr/obj/usr/src/i386/usr/include -c > /usr/src/gnu/usr.bin/binutils/objdump/../../../../contrib/binutils/binutils/objdump.c > > cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/objdump > -I/usr/src/gnu/usr.bin/binutils/objdump/../libbfd/i386 > -I/usr/src/gnu/usr.bin/binutils/objdump/../../../../contrib/binutils/include > -I/usr/src/gnu/usr.bin/binutils/objdump/../libbinutils > -I/usr/src/gnu/usr.bin/binutils/objdump/../../../../contrib/binutils/binutils > -DBFD_VERSION=\"2.10.0\" -I/usr/obj/usr/src/i386/usr/include -c > /usr/src/gnu/usr.bin/binutils/objdump/../../../../contrib/binutils/binutils/prdbg.c > > cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/objdump > -I/usr/src/gnu/usr.bin/binutils/objdump/../libbfd/i386 > -I/usr/src/gnu/usr.bin/binutils/objdump/../../../../contrib/binutils/include > -I/usr/src/gnu/usr.bin/binutils/objdump/../libbinutils > -I/usr/src/gnu/usr.bin/binutils/objdump/../../../../contrib/binutils/binutils > -DBFD_VERSION=\"2.10.0\" -I/usr/obj/usr/src/i386/usr/include -o objdump > objdump.o prdbg.o ../libbinutils/libbinutils.a ../libopcodes/libopcodes.a > ../libbfd/libbfd.a ../libiberty/libiberty.a > ../libiberty/libiberty.a(choose-temp.o): In function `make_temp_file': > choose-temp.o(.text+0x264): undefined reference to `mkstemps' > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > # exit > # exit > > ------------------------------------- End of script session here --------------- > I want to mention that an absolutely similar "make buildworld" (same initial > conditions) using the 3.5.1-RELEASE sources (instead of 4.1-RELEASE ones) > worked without any problem. > > Thanks. > > P.S. please reply to salem@statoil.com with CC: lazaro@online.no > > ------------------------------------------------------------------- > The information contained in this message may be CONFIDENTIAL and is intended > for the addressee only. Any unauthorised use, dissemination of the information > or copying of this message is prohibited. If you are not the addressee, please > notify the sender immediately by return e-mail and delete this message. > Thank you. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 12:25:25 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 92FA137B43C for ; Fri, 25 Aug 2000 12:25:23 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 25 Aug 2000 20:25:22 +0100 (BST) Date: Fri, 25 Aug 2000 20:25:22 +0100 From: David Malone To: Shawn Barnhart Cc: freebsd-stable@freebsd.org Subject: Re: Can I run two inetd processes? Message-ID: <20000825202522.A60106@walton.maths.tcd.ie> References: <012401c00ec8$4a7c6bd0$b8209fc0@marlowe> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <012401c00ec8$4a7c6bd0$b8209fc0@marlowe>; from swb@grasslake.net on Fri, Aug 25, 2000 at 02:11:35PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 25, 2000 at 02:11:35PM -0500, Shawn Barnhart wrote: > I'm pretty sure the answer to this is "yes", but if I use the -a option > (probably along with -p) and a seperate config file when launching inetd, > can I launch it twice? Yep - should work fine. > I'd like a "secure" inetd for my external NIC and a more permissive inetd > for my internal connection. Is this how the -a option is supposed to be > used? Is there a clean way to do this within rc.conf, or should the second > one just get launched from /usr/local/etc/rc.d? Start it from /usr/local/etc/rc.d or /etc/rc.local. You might also want to consider adding firewall rules to stop people sending packets to your outside interface, which are addressed to the inside interface. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 12:31: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 7632237B43C for ; Fri, 25 Aug 2000 12:30:53 -0700 (PDT) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id MAA00128; Fri, 25 Aug 2000 12:30:48 -0700 Message-ID: <39A6C968.C77BBB15@urx.com> Date: Fri, 25 Aug 2000 12:30:48 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Gary Kline Cc: Alfred Perlstein , freebsd-stable@FreeBSD.ORG Subject: Re: mouse question.... References: <200008250449.VAA05812@tao.thought.org> <20000824223158.J1209@fw.wintelcom.net> <20000825101432.B10594@tao.thought.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gary Kline wrote: > > On Thu, Aug 24, 2000 at 10:31:58PM -0700, Alfred Perlstein wrote: > > * Gary Kline [000824 21:50] wrote: > > > > > > Hi, Y'all, > > > > > > This is a long shot, but here goes. --On my other FBSD system > > > which is as 4.0, the mouse won't work. A friend just checked > > > the hardware ports, switched the mouse from COM1 to COM2. (COM2 > > > or, in the case of my modem, /dev/cuaa1, is working.) Zip; > > > nothing. He tried the mouse on this system on the other. Again, > > > nothinng. He thinks that in my upgrading to 4.0, part of my > > > mouse software may have been hosed. > > > > > > Any suggestions how I can diagnose the software side of this? > > > > > > I'm stumped. > > > > It's possible that there's a switch somewhere on the mouse that makes > > it go from "microsoft" to "mousesystems" try toggling the switch > > and alternating between moused settings for "microsoft" and > > "mousesystems". > > > > Some mice have the switch but "mousesystems" doesn't seem to work > > properly, so your best bet is to try both toggles with moused set > > as "microsoft", once you get that working you may want to try > > the other position and "mousesystems" in order to get use of your > > third button if you have one. > > > > If your mouse doesn't have a toggle... well then save this for future > > reference. :) > > > > The mouse (Belkin? or something like that) has a switch > between "Microsoft" and "PS2"; we didn't try the PS2 > but the "Microsoft" setting definitely failed. > > The mouse on this box is that works here wouldn't work on > the other FBSD computer. > > gary > > PS: It occurs to me to rcp over the /etc/XF86Config from here > make the X -> link and try again with this mouse. Didn't think > of that last night... . Did you use an adapter to connect from ps/2 to serial. No all adapters are created equal :). Only the one that came with the mouse has worked for me. Kent > > -- > Gary D. Kline kline@tao.thought.org Public service Unix > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 13: 2: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (Postfix) with ESMTP id 6438D37B43F for ; Fri, 25 Aug 2000 13:01:59 -0700 (PDT) Received: from tao.thought.org (tao.sea.tera.com [207.108.223.55]) by gershwin.tera.com (8.9.3/8.9.3) with ESMTP id NAA17472; Fri, 25 Aug 2000 13:02:15 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.9.3/8.7.3) id NAA12148; Fri, 25 Aug 2000 13:01:54 -0700 (PDT) Date: Fri, 25 Aug 2000 13:01:54 -0700 From: Gary Kline To: Kent Stewart Cc: Gary Kline , Alfred Perlstein , freebsd-stable@FreeBSD.ORG Subject: Re: mouse question.... Message-ID: <20000825130154.B12019@tao.thought.org> References: <200008250449.VAA05812@tao.thought.org> <20000824223158.J1209@fw.wintelcom.net> <20000825101432.B10594@tao.thought.org> <39A6C968.C77BBB15@urx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <39A6C968.C77BBB15@urx.com>; from kstewart@urx.com on Fri, Aug 25, 2000 at 12:30:48PM -0700 X-Organization: Thought Unlimited. Public service Unix since 1986. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 25, 2000 at 12:30:48PM -0700, Kent Stewart wrote: > > > Gary Kline wrote: > > > > The mouse (Belkin? or something like that) has a switch > > between "Microsoft" and "PS2"; we didn't try the PS2 > > but the "Microsoft" setting definitely failed. > > > > The mouse on this box is that works here wouldn't work on > > the other FBSD computer. > > > > gary > > > > PS: It occurs to me to rcp over the /etc/XF86Config from here > > make the X -> link and try again with this mouse. Didn't think > > of that last night... . > > Did you use an adapter to connect from ps/2 to serial. No all adapters > are created equal :). Only the one that came with the mouse has worked > for me. > Well, looks like, at a minimum, *this* mouse on my other machine wasn't working because my /etc/ttys entry for "COM2" was wrong. As for the ps/2 side of things, no, I didn't use any adaptor. The remote mouse was either a cheap or free mouse that CompUSA or whatever store was giving away. If it came with an adaptor, it's long lost! At any rate, in the "Microsoft" mode, the 1st and 3rd buttons (only) worked. Because I didn't use the keyboard/mouse/CRT that much, I didn't pay much attention to it. Now it's a different story. gary -- Gary D. Kline kline@tao.thought.org Public service Unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 13:31: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id BCDB637B43C for ; Fri, 25 Aug 2000 13:31:01 -0700 (PDT) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id NAA00312; Fri, 25 Aug 2000 13:30:57 -0700 Message-ID: <39A6D781.BDEC1113@urx.com> Date: Fri, 25 Aug 2000 13:30:57 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Gary Kline Cc: Alfred Perlstein , freebsd-stable@FreeBSD.ORG Subject: Re: mouse question.... References: <200008250449.VAA05812@tao.thought.org> <20000824223158.J1209@fw.wintelcom.net> <20000825101432.B10594@tao.thought.org> <39A6C968.C77BBB15@urx.com> <20000825130154.B12019@tao.thought.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gary Kline wrote: > > On Fri, Aug 25, 2000 at 12:30:48PM -0700, Kent Stewart wrote: > > > > > > Gary Kline wrote: > > > > > > The mouse (Belkin? or something like that) has a switch > > > between "Microsoft" and "PS2"; we didn't try the PS2 > > > but the "Microsoft" setting definitely failed. > > > > > > The mouse on this box is that works here wouldn't work on > > > the other FBSD computer. > > > > > > gary > > > > > > PS: It occurs to me to rcp over the /etc/XF86Config from here > > > make the X -> link and try again with this mouse. Didn't think > > > of that last night... . > > > > Did you use an adapter to connect from ps/2 to serial. No all adapters > > are created equal :). Only the one that came with the mouse has worked > > for me. > > > > Well, looks like, at a minimum, *this* mouse on my other machine > wasn't working because my /etc/ttys entry for "COM2" was wrong. > As for the ps/2 side of things, no, I didn't use any adaptor. Hind sight is great :). > > The remote mouse was either a cheap or free mouse that CompUSA or > whatever store was giving away. If it came with an adaptor, > it's long lost! At any rate, in the "Microsoft" mode, the > 1st and 3rd buttons (only) worked. Because I didn't use the > keyboard/mouse/CRT that much, I didn't pay much attention to > it. Now it's a different story. I understand that feeling well. The mouse port on my KVM switch died. It would work on my old Win 2000 system but not on FreeBSD. I only have one monitor and keyboard but now I have two mice. I was really thinking about having two of the cordless mice until I got serious and looked at the price. Kent > > gary > > -- > Gary D. Kline kline@tao.thought.org Public service Unix -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 14:23:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6050B37B422; Fri, 25 Aug 2000 14:23:55 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA15819; Fri, 25 Aug 2000 14:23:55 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 25 Aug 2000 14:23:55 -0700 (PDT) From: Kris Kennaway To: Roman Shterenzon Cc: freebsd-stable@freebsd.org Subject: Re: pkg_check 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, 25 Aug 2000, Roman Shterenzon wrote: > Hello, > I didn't find the functionality to check package integrity in the standard > freebsd pkg_* utilities. (Perhaps I'm missing something?) > So, I wrote this small perl script which does it for me. > With this tool, one may use tripwire only on /var/db/pkg and skip > /usr/local. > What do you think about it? Check out /usr/ports/Tools/scripts/consistency-check Does yours do anything different/better than this one? Perhaps you and the author of that script (nbm@freebsd.org) could collaborate. 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 Aug 25 15:11:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from drugs.dv.isc.org (drugs.dv.isc.org [130.155.191.236]) by hub.freebsd.org (Postfix) with ESMTP id 4889A37B42C for ; Fri, 25 Aug 2000 15:11:28 -0700 (PDT) Received: from nominum.com (localhost.dv.isc.org [127.0.0.1]) by drugs.dv.isc.org (8.9.3/8.9.3) with ESMTP id IAA03293; Sat, 26 Aug 2000 08:13:10 +1000 (EST) (envelope-from marka@nominum.com) Message-Id: <200008252213.IAA03293@drugs.dv.isc.org> To: John Baldwin Cc: stable@FreeBSD.org From: Mark.Andrews@nominum.com Subject: Re: HEADSUP: 4.1S installworld broken In-reply-to: Your message of "Thu, 24 Aug 2000 13:18:20 MST." <200008242018.NAA53651@pike.osd.bsdi.com> Date: Sat, 26 Aug 2000 08:13:10 +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mark.Andrews@nominum.com wrote: > > > > > Mark.Andrews@nominum.com wrote: > > > > > > > > STRICTTMPPATH does not contain cp/ > > > > > > > > ===> gnu/usr.bin/binutils/doc > > > > cp -p /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/in > stal > > > l.sh > > > > install > > > > cp:No such file or directory > > > > *** Error code 1 > > > > > > Grrr, it worked here during my test build and install. :( You should jus > t > > > be able to add 'cp' to the list of files to copy in the 'installworld' > > > target in src/Makefile.inc1. I'll try it again to see if I can reproduce > > > the breakage. > > > > That should fix it. My full build environment is in pr=20815. > > I worked around the problem but felt a HEADSUP was warranted. > > > > Mark > > Hmm, I haven't been able to reproduce this problem: > > [12:57:47] (ttyp8) jhb@foo:...src/release/sysinstall > > dir /tmp/install.74661/cp > ls: /tmp/install.74661/cp: No such file or directory > > tail /var/tmp/iw.out > ===> wi > install -c -o root -g wheel -m 555 if_wi.ko /modules > ---------------------------------------- > install started at 11:58:49 on 08/24/00 > install finished at 12:37:31 on 08/24/00 > ---------------------------------------- > > uname -a > FreeBSD foo.osd.bsdi.com 4.1-RC FreeBSD 4.1-RC #6: Fri Jul 14 14:15:27 PDT 20 > 00 root@foo.osd.bsdi.com:/usr/src/sys/compile/FOO i386 After more testing it is the result of building (just?) the following compatability libraries. COMPAT22=yes COMPAT3X=yes /usr/obj/usr/src/gnu/usr.bin/binutils/doc/install is not made by buildworld and as cp in not in the path installworld fails. ===> gnu/usr.bin/binutils/doc cp -p /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/install.sh install cp:No such file or directory *** Error code 1 Mark -- Mark Andrews, Nominum Inc. 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews@nominum.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 16:44:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 3F70937B424; Fri, 25 Aug 2000 16:44:26 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.9.3/8.9.3) id JAA66553; Sat, 26 Aug 2000 09:14:03 +0930 (CST) (envelope-from grog) Date: Sat, 26 Aug 2000 09:14:03 +0930 From: Greg Lehey To: Smith@ian.org, Alexander Langer Cc: freebsd-stable@FreeBSD.ORG, "Chris D. Faulhaber" Subject: Re: make release problem Message-ID: <20000826091403.D52219@wantadilla.lemis.com> References: <20000825203327.B43892@cichlids.cichlids.com> <4.3.2.7.2.20000824082639.00afffb8@mail.megapathdsl.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from Smith@ian.org on Fri, Aug 25, 2000 at 09:05:00AM -0400 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 25 August 2000 at 9:05:00 -0400, Smith@ian.org wrote: > I am trying to make a release cd and I am having problems. > > I cvsuped to the latest of -stable, then did a 'make buildworld' > and a 'make buildkernel' in /usr/src. Then I went to > /usr/src/release and ran... > > make release \ > BUILDNAME=4.1-STABLE \ > CHROOTDIR=/usr/release \ > RELEASETAG=RELENG_4 \ > CVSROOT=/home/ncvs > > Everything goes fine for hours and hours and hours... and then > stops here. Output is below... > > ----------------- > > cc -pg -O -pipe -DTERMIOS -DANSI_SOURCE \ > -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto \ > -I/usr/obj/usr/src/secure/lib/libcrypto -DNO_IDEA -DL_ENDIAN -DNO_IDEA \ > -I/usr/obj/usr/src/i386/usr/include -c \ > /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/pkcs7/pk7_doit.c \ > -o pk7_doit.po > install -C -o root -g wheel -m 444 book.html > usage: install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 > install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 ... > fileN directory > install -d [-v] [-g group] [-m mode] [-o owner] directory ... > *** Error code 64 > > Stop in /usr/doc/de_DE.ISO_8859-1/books/handbook. > *** Error code 1 > > ----------------- > > Any ideas? On Friday, 25 August 2000 at 20:33:27 +0200, Alexander Langer wrote: > Thus spake Chris D. Faulhaber (jedgar@fxp.org): > >> >> This is due to a non-existent >> doc/de_DE.ISO_8859-1/books/handbook/Makefile.inc which should contain: > > ok. I'll add it, thanks. > > Alex, > who has obviously not tested release. *sigh* > > (ignore my private mail, Chris :) Yes, I saw (and reported) this last week as well. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 17:27:41 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 C7CC337B422 for ; Fri, 25 Aug 2000 17:27:38 -0700 (PDT) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.10.1/8.10.1) with ESMTP id e7Q0RVb02335 for ; Fri, 25 Aug 2000 20:27:31 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id UAA37584 for ; Fri, 25 Aug 2000 20:27:30 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id UAA91074 for freebsd-stable@freebsd.org; Fri, 25 Aug 2000 20:27:29 -0400 (EDT) Date: Fri, 25 Aug 2000 20:27:29 -0400 (EDT) From: Thomas David Rivers Message-Id: <200008260027.UAA91074@lakes.dignus.com> To: freebsd-stable@freebsd.org Subject: natd & redirect with 4.1-RELEASE? Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to move a venerable 3.1-RELEASE gateway to 4.1-RELEASE, but I'm having a bit of a problem with natd & port redirection. The firewall type is `open', and I have the following options in the kernel: # # IP options # options MROUTING # Multicast routing options IPFIREWALL #firewall options IPFIREWALL_FORWARD #enable transparent proxy support options IPDIVERT #divert sockets /etc/rc.conf looks like: firewall_enable="YES" firewall_type=open # # enable natd - set the interface & flags to forward packets # appropriately. # natd_enable="YES" natd_interface="xl0" natd_flags="-l -m -u -redirect_port tcp 10.0.0.11:telnet 6666 -redirect_port udp 10.0.0.11:telnet 6666" This worked just fantastic with 3.1-RELEASE; but I can't seem to get it to work for 4.1-RELEASE. When you try to telnet to the gateway at port 6666, it just sits there... I've verified that the ipfw rules appear correct: # ipfw list 00050 divert 8668 ip from any to any via xl0 00100 allow ip from any to any via lo0 00200 deny ip from any to 127.0.0.0/8 65000 allow ip from any to any 65535 deny ip from any to any and, natd is running... Does anyone else have natd issues with 4.1-RELEASE? Have I left something out here? (Could IPFIREWALL_FORWARD be the culprit?) - Thanks - - Dave Rivers - -- rivers@dignus.com Work: (919) 676-0847 Get your mainframe (370) `C' compiler at http://www.dignus.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 19:55:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fatbastard.zialink.com (fatbastard.zialink.com [63.227.239.3]) by hub.freebsd.org (Postfix) with ESMTP id 4BB2A37B43E for ; Fri, 25 Aug 2000 19:55:36 -0700 (PDT) Received: from localhost (tucka@localhost) by fatbastard.zialink.com (8.9.3/8.9.3) with ESMTP id UAA03526 for ; Fri, 25 Aug 2000 20:55:40 -0600 (MDT) (envelope-from tucka@fatbastard.zialink.com) Date: Fri, 25 Aug 2000 20:55:40 -0600 (MDT) From: tucka To: freebsd-stable@freebsd.org Subject: ipnat fails under load 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 You can add me to the list of people who have problems with ipfilter under load. 3 boxes, 2 with 4.1-S ipf 3.4.8 and 1 with 4.0-S ipf 3.3.8. It doesn't seem to be so much a problem with how many clients are accessing the server, but rather just a matter of time. All 3 boxes consistently fail after 2 to 4 hours of use. Some can be "saved" via an ipf -Fa and reloading, but usually they need to be restarted. I've had to go back to SUSE *blech* on one box because it was just unusable. If there is any other info I can provide to help resolve this issue please don't hesitate to ask. Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 20: 5:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from flux.ptc.spbu.ru (flux.ptc.spbu.ru [195.19.225.195]) by hub.freebsd.org (Postfix) with ESMTP id 992A737B424; Fri, 25 Aug 2000 20:05:49 -0700 (PDT) Received: from snark.ptc.spbu.ru (snark.ptc.spbu.ru [195.19.225.131]) by flux.ptc.spbu.ru (8.9.3/8.9.3/cf-1.0.rbl) with ESMTP id HAA83988; Sat, 26 Aug 2000 07:05:43 +0400 (MSD) Received: (from uwe@localhost) by snark.ptc.spbu.ru (8.8.8+Sun/8.8.8) id HAA17041; Sat, 26 Aug 2000 07:05:42 +0400 (MSD) Date: Sat, 26 Aug 2000 07:05:42 +0400 From: "Valeriy E. Ushakov" To: freebsd-stable@FreeBSD.ORG Cc: Peter Wemm Subject: systat broken Message-ID: <20000826070542.B16988@snark.ptc.spbu.ru> Mail-Followup-To: freebsd-stable@FreeBSD.ORG, Peter Wemm Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.3i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After this commit systat can't be compiled since it still refers to m_mtypes. Revision 1.11 of src/usr.bin/systat/mbuf.c should be MFC'ed as well, it seems. peter 2000/08/25 16:18:53 PDT Modified files: (Branch: RELENG_4) sys/kern uipc_mbuf.c sys/sys mbuf.h usr.bin/netstat mbuf.c Log: MFC: kern/uipc_mbuf.c v1.53, sys/mbuf.h v1.52, netstat/mbuf.c v1.18 Make mbstat.m_mtypes seperate and viewable via sysctl. Expand the type from u_short to u_long to stop 64K wraparounds, especially on mbtypes[MT_FREE]. Also, the MT_FREE counter was never incremented on creation of new mbufs, so the freelist count was wrong. PR: kern/19809 Submitted by: Ian Dowse MFC forgotten by: albert Revision Changes Path 1.51.2.2 +4 -0 src/sys/kern/uipc_mbuf.c 1.44.2.6 +11 -9 src/sys/sys/mbuf.h 1.17.2.1 +50 -26 src/usr.bin/netstat/mbuf.c SY, Uwe -- uwe@ptc.spbu.ru | Zu Grunde kommen http://www.ptc.spbu.ru/~uwe/ | Ist zu Grunde gehen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 20:31:22 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 884D037B424 for ; Fri, 25 Aug 2000 20:31:14 -0700 (PDT) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id UAA20513; Fri, 25 Aug 2000 20:30:37 -0700 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda20509; Fri Aug 25 20:30:20 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id UAA52674; Fri, 25 Aug 2000 20:30:20 -0700 (PDT) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdQ52664; Fri Aug 25 20:29:25 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.0/8.9.1) id e7Q3TPq87381; Fri, 25 Aug 2000 20:29:25 -0700 (PDT) Message-Id: <200008260329.e7Q3TPq87381@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdz87369; Fri Aug 25 20:28:37 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 4.1-RELEASE X-Sender: cy To: tucka Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ipnat fails under load In-reply-to: Your message of "Fri, 25 Aug 2000 20:55:40 MDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 25 Aug 2000 20:28:37 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , tu cka writes: > You can add me to the list of people who have problems with ipfilter > under load. 3 boxes, 2 with 4.1-S ipf 3.4.8 and 1 with 4.0-S ipf 3.3.8. > It doesn't seem to be so much a problem with how many clients are > accessing the server, but rather just a matter of time. All 3 boxes > consistently fail after 2 to 4 hours of use. Some can be "saved" via > an ipf -Fa and reloading, but usually they need to be restarted. I've > had to go back to SUSE *blech* on one box because it was just unusable. > If there is any other info I can provide to help resolve this issue please > don't hesitate to ask. What's your configuration? Could you list your IPF and NAT rules? Next time you have a "freeze", issue ipfstat -s and ipfstat -sl. If you're using statefull filtering, could it be that your state table has filled. What type of traffic do you generally have going through your firewalls? If you use a lot of FTP and use the FTP proxy, 3.4.8 is broken for some FTP clients -- upgrade to 3.4.9. If you use RCMD proxy with rcp or krcp, your state and NAT tables will fill up very quickly, eventually hanging the box. I have IPF running on my gateway at home (4.1R), 4 FreeBSD 4.1-R systems at work (+ 12 Solaris systems), and on two systems at a friend's ISP (one running 3.4S and the other running 4.0R). The versions of IPF range from 3.3.7 - 3.4.9. All without problem. One thing to note is that I've disabled IPv6 in all of my kernels (primarily because I cannot get KRB5 to work through NAT with IPv6 enabled). This is just a hunch but if you do have IPv6 enabled try disabling it. You may want to send a question to the IP Filter mailing list (ipfilter@coombs.anu.edu.au) or visit the IP Filter Web site at http://coombs.anu.edu.au/~avalon/ip-filter.html which describes how to subscribe to the IP Filter mailing list. The short of it is that you need to do more homework before posting questions. 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 Aug 25 21:36:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from teapot21.domain3.bigpond.com (teapot21.domain3.bigpond.com [139.134.5.159]) by hub.freebsd.org (Postfix) with SMTP id 2850D37B42C for ; Fri, 25 Aug 2000 21:36:18 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by teapot21.domain3.bigpond.com (NTMail 3.02.13) with ESMTP id la953561 for ; Sat, 26 Aug 2000 14:36:53 +1000 Received: from CWIP-T-007-p-219-166.tmns.net.au ([203.54.219.166]) by mail3.bigpond.com (Claudes-Colossal-MailRouter V2.9b 5/883791); 26 Aug 2000 14:36:52 Message-ID: <39A74935.7C6EB8EF@telstra.com> Date: Sat, 26 Aug 2000 14:36:05 +1000 From: Wobbly Organization: TANTRUM X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Re: systat broken References: <20000826070542.B16988@snark.ptc.spbu.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yup, After being belted around the head by CDROM problems, buildworld now fails... cc -O -pipe -I/usr/src/usr.bin/systat/../../sys -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/systat/mbufs.c /usr/src/usr.bin/systat/mbufs.c: In function `showmbufs': /usr/src/usr.bin/systat/mbufs.c:111: structure has no member named `m_mtypes' /usr/src/usr.bin/systat/mbufs.c:112: structure has no member named `m_mtypes' /usr/src/usr.bin/systat/mbufs.c:133: structure has no member named `m_mtypes' /usr/src/usr.bin/systat/mbufs.c:134: structure has no member named `m_mtypes' *** Error code 1 Stop in /usr/src/usr.bin/systat. *** Error code 1 etc, etc. My whiney-ass opinion is as follows: I am now sitting here suffering from not one, but TWO botched comits to STABLE in a row. SLOW DOWN!!! It seems clear from these two incidents that comits to STABLE are being made WAY WAY too fast. Rosco. "Valeriy E. Ushakov" wrote: > > After this commit systat can't be compiled since it still refers to > m_mtypes. Revision 1.11 of src/usr.bin/systat/mbuf.c should be MFC'ed > as well, it seems. > > peter 2000/08/25 16:18:53 PDT > > Modified files: (Branch: RELENG_4) > sys/kern uipc_mbuf.c > sys/sys mbuf.h > usr.bin/netstat mbuf.c > Log: > MFC: kern/uipc_mbuf.c v1.53, sys/mbuf.h v1.52, netstat/mbuf.c v1.18 > Make mbstat.m_mtypes seperate and viewable via sysctl. Expand the > type from u_short to u_long to stop 64K wraparounds, especially on > mbtypes[MT_FREE]. Also, the MT_FREE counter was never incremented on > creation of new mbufs, so the freelist count was wrong. > > PR: kern/19809 > Submitted by: Ian Dowse > MFC forgotten by: albert > > Revision Changes Path > 1.51.2.2 +4 -0 src/sys/kern/uipc_mbuf.c > 1.44.2.6 +11 -9 src/sys/sys/mbuf.h > 1.17.2.1 +50 -26 src/usr.bin/netstat/mbuf.c > > SY, Uwe > -- > uwe@ptc.spbu.ru | Zu Grunde kommen > http://www.ptc.spbu.ru/~uwe/ | Ist zu Grunde gehen > > 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 Aug 25 23: 5:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from limit.org (limit.org [216.102.231.2]) by hub.freebsd.org (Postfix) with ESMTP id 3065D37B43C for ; Fri, 25 Aug 2000 23:05:25 -0700 (PDT) Received: (from michael@localhost) by limit.org (8.9.3/8.9.3) id XAA00801 for freebsd-stable@freebsd.org; Fri, 25 Aug 2000 23:05:21 -0700 (PDT) (envelope-from michael) Date: Fri, 25 Aug 2000 23:05:09 -0700 From: Michael Matsumura To: freebsd-stable@freebsd.org Subject: Promise Ultra66 Controller Card Message-ID: <20000825230509.A580@jupiter.limit.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just installed a Promise Ultra66 controller card, and...its not working... the card's BIOS booted up and detected my two hard drives...but the boot loader spit out the following: elf_loadexec: archsw.readin failed unable to load kernel: Aborted [root:~]# uname -a FreeBSD jupiter.limit.org 4.1-STABLE FreeBSD 4.1-STABLE #0: Fri Aug 25 21:35:53 PDT 2000 root@jupiter.limit.org:/usr/src/sys/compile/JUPITER i386 I've tried disabling the on-board IDE controller, but to no avail... :\ Yes, I'm using an 80-wire IDE cable and it boots up fine without the Promise controller... Suggestions are more than welcome, thanks :) -- Michael Matsumura michael@limit.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 25 23:10:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id CAEFB37B422 for ; Fri, 25 Aug 2000 23:10:50 -0700 (PDT) Received: from [128.9.176.135] (ras35.isi.edu [128.9.176.135]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id XAA05892; Fri, 25 Aug 2000 23:10:43 -0700 (PDT) User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022 Date: Fri, 25 Aug 2000 23:10:43 -0700 Subject: Re: Promise Ultra66 Controller Card From: Lars Eggert To: Michael Matsumura , Message-ID: In-Reply-To: <20000825230509.A580@jupiter.limit.org> 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 just installed a Promise Ultra66 controller card, and...its not > working... the card's BIOS booted up and detected my two hard drives...but > the boot loader spit out the following: > > elf_loadexec: archsw.readin failed > unable to load kernel: > Aborted I saw the same on one of a few identical machines - in our case, the card had a defect. -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 0:40:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id C7C3E37B423 for ; Sat, 26 Aug 2000 00:40:26 -0700 (PDT) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:rcRBVnbN0TFCWPZhfPQWucG0OuMIyzqx@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id QAA17332; Sat, 26 Aug 2000 16:40:12 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:FM6/6syVWdEXnd1MvtG1TNTrBcHouMiT@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id QAA26455; Sat, 26 Aug 2000 16:46:59 +0900 (JST) Message-Id: <200008260746.QAA26455@zodiac.mech.utsunomiya-u.ac.jp> To: Gary Kline Cc: freebsd-stable@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: mouse question.... In-reply-to: Your message of "Thu, 24 Aug 2000 21:49:43 MST." <200008250449.VAA05812@tao.thought.org> References: <200008250449.VAA05812@tao.thought.org> Date: Sat, 26 Aug 2000 16:46:58 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is a long shot, but here goes. --On my other FBSD system > which is as 4.0, the mouse won't work. A friend just checked > the hardware ports, switched the mouse from COM1 to COM2. (COM2 > or, in the case of my modem, /dev/cuaa1, is working.) Zip; > nothing. He tried the mouse on this system on the other. Again, > nothinng. He thinks that in my upgrading to 4.0, part of my > mouse software may have been hosed. > > Any suggestions how I can diagnose the software side of this? > > I'm stumped. It is not easy to determine what is wrong based on relatively few information. Please do the following to diagnose the problem. 1. Hook up the mouse (it's a serial mouse, right?) to COM1 2. Become root. 3. Don't run X yet. Kill `moused' if it is already running. (Run "ps aux | grep mouse" to see if it is running. Kill it if any.) 4. Run moused in the information mode as follows: moused -p /dev/cuaa0 -i all You should get some information if the mouse is a PnP mouse or a Microsoft-compatible mouse. Something like: /dev/cuaa0 serial microsoft generic 5. Run moused again, this time in the debug mode: moused -p /dev/cuaa0 -d -f If you move mouse and click buttons, you should see mouse status information should be printed. Type ^C to stop moused. If this seems Ok, then you should edit /etc/rc.conf and put the following lines there: moused_enable="YES" moused_type="auto" moused_port="/dev/cuaa0" Then, edit /etc/XF86Config and set the mouse protocol to "Auto" and the mouse device to "/dev/sysmouse". Start moused in the daemon mode by hand for now (this will automatically done the next time the system is rebooted.) moused -p /dev/cuaa0 -t auto 6. If moused says 'cannot determine mouse type...' in 4, the mouse may be a MouseSystems-compatible mouse, or it may be broken. If the mouse is considered MouseSystems-compatible, you can test the mouse as follows: moused -p /dev/cuaa0 -d -f -t mousesystems If this is successful Ok, then you should edit /etc/rc.conf and put the following lines there: moused_enable="YES" moused_type="mousesystems" moused_port="/dev/cuaa0" Edit /etc/XF86Config and set the mouse protocol to "Auto" and the mouse device to "/dev/sysmouse". Start moused in the daemon mode by hand for now (this will automatically done the next time the system is rebooted.) moused -p /dev/cuaa0 -t mousesystems Hope this might help.... Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 6:51:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.lewman.org (lowrider.lewman.org [63.109.230.166]) by hub.freebsd.org (Postfix) with ESMTP id 5DC7537B43C for ; Sat, 26 Aug 2000 06:51:45 -0700 (PDT) Received: by mail.lewman.org (Postfix, from userid 1001) id 92C4C3D31; Sat, 26 Aug 2000 09:51:44 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.lewman.org (Postfix) with ESMTP id 8DFDC5BB9 for ; Sat, 26 Aug 2000 09:51:44 -0400 (EDT) Date: Sat, 26 Aug 2000 09:51:44 -0400 (EDT) From: Andy X-Sender: deimos@lowrider.lewman.org To: freebsd-stable@freebsd.org Subject: Permanent boot loader problem with 4.1-R 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 installed 4.1-R off a cd last night. The bootloader installs and works fine, however I can't get rid of it now. I've got 2 UDMA66 drives setup as primary master/slave. Nothing appears to work to get rid of the boot loader. Here's what I've tried so far: I've booted with a dos disk, run fdisk /mbr, rebooted, fbsd boot loader still comes up. I've fired up a hex editor, and messed around with the mbr, fbsd boot loader still comes up. I've gone into fdisk and wiped all partitions on both drives, rebooted, fbsd boot loader comes up but can't load anything (obviously). I've now just tried changing the disk geom in the bios, fbsd boot loader still comes up. I've tried re-installing fbsd 4.1-R to consume both drives, re-install teh boot loader, and it sees the new installation, but when it goes to boot it gets "boot error". Run fdisk /mbr again, no luck, boot loader is still there. I've swapped drive positions, run fdisk /mbr, boot loader still is there. I've tried installing lilo, win2k, and winme just to see if anything will blow out the mbr at this point. Everytime, the fbsd boot loader returns. I give up. Wtf do I have to do to get rid of the thing? fwiw, in the hex editor, I see the other copy of the mbr, but can't move it to the first position because of some error when attempting to do so. Any help is really appreciated. -- | Andy | e-mail | web | | | andy@lewman.com | www.lewman.com | You will be surprised by a loud noise. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 7:37:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.lewman.org (lowrider.lewman.org [63.109.230.166]) by hub.freebsd.org (Postfix) with ESMTP id 6B7F437B424 for ; Sat, 26 Aug 2000 07:37:48 -0700 (PDT) Received: by mail.lewman.org (Postfix, from userid 1001) id 5CE633D31; Sat, 26 Aug 2000 10:38:03 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.lewman.org (Postfix) with ESMTP id 5B2225BB9 for ; Sat, 26 Aug 2000 10:38:03 -0400 (EDT) Date: Sat, 26 Aug 2000 10:38:03 -0400 (EDT) From: Andy X-Sender: deimos@lowrider.lewman.org To: freebsd-stable@freebsd.org Subject: Re: Permanent boot loader problem with 4.1-R In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 26 Aug 2000, Andy wrote: Well now, I feel dumb. The one thing I didn't try was to d/l Maxtor's silly maxblast software and do a destructive write scan on the drive. As it works sector by sector, it conveniently blows away any data in the drive whatsoever. Everything is working again, now I just have to reinstal my Oses. Sorry for the waste of bandwidth. -- | Andy | e-mail | web | | | andy@lewman.com | www.lewman.com | Lazlo's Chinese Relativity Axiom: No matter how great your triumphs or how tragic your defeats -- approximately one billion Chinese couldn't care less. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 10:10:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (Postfix) with ESMTP id E05FB37B422 for ; Sat, 26 Aug 2000 10:10:05 -0700 (PDT) Received: from tao.thought.org (tao.sea.tera.com [207.108.223.55]) by gershwin.tera.com (8.9.3/8.9.3) with ESMTP id KAA04838; Sat, 26 Aug 2000 10:10:21 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.9.3/8.7.3) id KAA24299; Sat, 26 Aug 2000 10:10:01 -0700 (PDT) Date: Sat, 26 Aug 2000 10:10:01 -0700 From: Gary Kline To: Kazutaka YOKOTA Cc: Gary Kline , freebsd-stable@FreeBSD.ORG Subject: Re: mouse question.... Message-ID: <20000826101000.A23999@tao.thought.org> References: <200008250449.VAA05812@tao.thought.org> <200008260746.QAA26455@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200008260746.QAA26455@zodiac.mech.utsunomiya-u.ac.jp>; from yokota@zodiac.mech.utsunomiya-u.ac.jp on Sat, Aug 26, 2000 at 04:46:58PM +0900 X-Organization: Thought Unlimited. Public service Unix since 1986. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Aug 26, 2000 at 04:46:58PM +0900, Kazutaka YOKOTA wrote: > > > This is a long shot, but here goes. --On my other FBSD system > > which is as 4.0, the mouse won't work. A friend just checked > > the hardware ports, switched the mouse from COM1 to COM2. (COM2 > > or, in the case of my modem, /dev/cuaa1, is working.) Zip; > > nothing. He tried the mouse on this system on the other. Again, > > nothinng. He thinks that in my upgrading to 4.0, part of my > > mouse software may have been hosed. > > > > Any suggestions how I can diagnose the software side of this? > > > > I'm stumped. > > It is not easy to determine what is wrong based on relatively > few information. > > Please do the following to diagnose the problem. > > 1. Hook up the mouse (it's a serial mouse, right?) to COM1 > > 2. Become root. > > 3. Don't run X yet. Kill `moused' if it is already running. > (Run "ps aux | grep mouse" to see if it is running. Kill it if any.) > > 4. Run moused in the information mode as follows: > moused -p /dev/cuaa0 -i all > You should get some information if the mouse is a PnP mouse or a > Microsoft-compatible mouse. Something like: > /dev/cuaa0 serial microsoft generic > > 5. Run moused again, this time in the debug mode: > moused -p /dev/cuaa0 -d -f > If you move mouse and click buttons, you should see mouse status > information should be printed. Type ^C to stop moused. > If this seems Ok, then you should edit /etc/rc.conf and > put the following lines there: > moused_enable="YES" > moused_type="auto" > moused_port="/dev/cuaa0" > Then, edit /etc/XF86Config and set the mouse protocol to "Auto" and > the mouse device to "/dev/sysmouse". > Start moused in the daemon mode by hand for now (this will automatically > done the next time the system is rebooted.) > moused -p /dev/cuaa0 -t auto > > 6. If moused says 'cannot determine mouse type...' in 4, the mouse > may be a MouseSystems-compatible mouse, or it may be broken. > If the mouse is considered MouseSystems-compatible, you can > test the mouse as follows: > moused -p /dev/cuaa0 -d -f -t mousesystems > If this is successful Ok, then you should edit /etc/rc.conf and > put the following lines there: > moused_enable="YES" > moused_type="mousesystems" > moused_port="/dev/cuaa0" > Edit /etc/XF86Config and set the mouse protocol to "Auto" and > the mouse device to "/dev/sysmouse". > Start moused in the daemon mode by hand for now (this will automatically > done the next time the system is rebooted.) > moused -p /dev/cuaa0 -t mousesystems > > Hope this might help.... > This has been very helpful. It tells me (I believe) that my upgrade installation of 4.0 was|is *not* faulty. And that the mouse is probably bad. Here is the output from (4) above: sage# moused -p /dev/cuaa0 -i all moused: cannot determine mouse type on /dev/cuaa0 /dev/cuaa0 unknown unknown generic And from (6): sage# moused -p /dev/cuaa0 -d -f -t mousesystems moused: port: /dev/cuaa0 interface: unknown type: mousesystems model: generic This mouse was an inexpensive give-away, switchable between "MS" and "PS/2", but even if I switch to the PS/2 setting, I get the same ``cannot determing'' diagnostic. It's time to buy a new mouse! Thanks very much for your help, gary -- Gary D. Kline kline@tao.thought.org Public service Unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 12: 2:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id B0B1F37B42C for ; Sat, 26 Aug 2000 12:02:45 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e7QJ2eg96633; Sat, 26 Aug 2000 12:02:41 -0700 (PDT) Date: Sat, 26 Aug 2000 12:02:40 -0700 (PDT) From: Doug White To: Thomas David Rivers Cc: freebsd-stable@FreeBSD.ORG Subject: Re: natd & redirect with 4.1-RELEASE? In-Reply-To: <200008260027.UAA91074@lakes.dignus.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, 25 Aug 2000, Thomas David Rivers wrote: > > I'm trying to move a venerable 3.1-RELEASE gateway to 4.1-RELEASE, > but I'm having a bit of a problem with natd & port redirection. > > The firewall type is `open', and I have the following > options in the kernel: > > /etc/rc.conf looks like: > > firewall_enable="YES" > firewall_type=open You might make this firewall_type="open" just to make sure it isn't interpreting something. > natd_enable="YES" > natd_interface="xl0" > natd_flags="-l -m -u -redirect_port tcp 10.0.0.11:telnet 6666 -redirect_port udp 10.0.0.11:telnet 6666" With that many flags, you should consider writing a natd.conf and using the -f flag to load it. Having a config file for natd makes it much easier to maintain (and reload at runtime since natd doesn't recognize SIGHUP). > This worked just fantastic with 3.1-RELEASE; but I can't seem to get > it to work for 4.1-RELEASE. When you try to telnet to the gateway > at port 6666, it just sits there... have you tried tcpdumping it? Perhaps it's doing a DNS lookup? You should also try compiling with IPFIREWALL_VERBOSE and set up logging on your rules to see where they're going. > Does anyone else have natd issues with 4.1-RELEASE? Have I left > something out here? (Could IPFIREWALL_FORWARD be the culprit?) divert doesn't touch fwd. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 12: 5:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id C920737B423 for ; Sat, 26 Aug 2000 12:05:28 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e7QJ5LF02491; Sat, 26 Aug 2000 12:05:22 -0700 (PDT) Date: Sat, 26 Aug 2000 12:05:21 -0700 (PDT) From: Doug White To: Andy Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Permanent boot loader problem with 4.1-R In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 26 Aug 2000, Andy wrote: > On Sat, 26 Aug 2000, Andy wrote: > > Well now, I feel dumb. The one thing I didn't try was to d/l Maxtor's > silly maxblast software and do a destructive write scan on the drive. As > it works sector by sector, it conveniently blows away any data in the > drive whatsoever. Everything is working again, now I just have to > reinstal my Oses. I bet it was picking up boot0 from the other disk :) Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 13:44:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id EB70337B423; Sat, 26 Aug 2000 13:44:13 -0700 (PDT) Received: from 149.211.6.64.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Sat, 26 Aug 2000 13:43:00 -0700 Received: (from cjc@localhost) by 149.211.6.64.reflexcom.com (8.9.3/8.9.3) id NAA79815; Sat, 26 Aug 2000 13:43:49 -0700 (PDT) (envelope-from cjc) Date: Sat, 26 Aug 2000 13:43:49 -0700 From: "Crist J . Clark" To: Kris Kennaway Cc: Roman Shterenzon , freebsd-stable@FreeBSD.ORG Subject: Re: pkg_check Message-ID: <20000826134349.C62475@149.211.6.64.reflexcom.com> Reply-To: cjclark@alum.mit.edu References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@FreeBSD.ORG on Fri, Aug 25, 2000 at 02:23:55PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 25, 2000 at 02:23:55PM -0700, Kris Kennaway wrote: > On Fri, 25 Aug 2000, Roman Shterenzon wrote: > > > Hello, > > I didn't find the functionality to check package integrity in the standard > > freebsd pkg_* utilities. (Perhaps I'm missing something?) > > So, I wrote this small perl script which does it for me. > > With this tool, one may use tripwire only on /var/db/pkg and skip > > /usr/local. > > What do you think about it? > > Check out > > /usr/ports/Tools/scripts/consistency-check > > Does yours do anything different/better than this one? Perhaps you and the > author of that script (nbm@freebsd.org) could collaborate. How about writing a modification to pkg_info(1) that does a check as an option? -- Crist J. Clark cjclark@alum.mit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 14: 4: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.lewman.org (lowrider.lewman.org [63.109.230.166]) by hub.freebsd.org (Postfix) with ESMTP id 8181937B42C for ; Sat, 26 Aug 2000 14:03:58 -0700 (PDT) Received: by mail.lewman.org (Postfix, from userid 1001) id B078A3D31; Sat, 26 Aug 2000 17:04:00 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.lewman.org (Postfix) with ESMTP id ABC3E5BB9 for ; Sat, 26 Aug 2000 17:04:00 -0400 (EDT) Date: Sat, 26 Aug 2000 17:04:00 -0400 (EDT) From: Andy X-Sender: deimos@lowrider.lewman.org Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Permanent boot loader problem with 4.1-R In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 26 Aug 2000, Doug White wrote: :I bet it was picking up boot0 from the other disk :) I thought of that too, hence the swapping of the disks exchanging the original master/slave positions. It didn't work. And for those telling me to "man fdisk", fdisk -B ad0 or ad1 didn't work either. Nothing worked, hence the reason I posted; albeit too soon. -- | Andy | e-mail | web | | | andy@lewman.com | www.lewman.com | Every little picofarad has a nanohenry all its own. -- Don Vonada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 14:53:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from 24-25-220-168.san.rr.com (24-25-220-168.san.rr.com [24.25.220.168]) by hub.freebsd.org (Postfix) with ESMTP id 3E79537B43F for ; Sat, 26 Aug 2000 14:53:38 -0700 (PDT) Received: from gorean.org (master [10.0.0.2]) by 24-25-220-168.san.rr.com (8.9.3/8.9.3) with ESMTP id OAA42426; Sat, 26 Aug 2000 14:53:21 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <39A83C51.9D4C125E@gorean.org> Date: Sat, 26 Aug 2000 14:53:21 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: strange@unicon.ru Cc: freebsd-stable@freebsd.org Subject: Re: SMP problems (was: How can I obtain -stable for previous date) References: <200008231019.RAA02918@mix.unicon.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG strange@unicon.ru wrote: > > > > But after Aug 20, the system became unstable ;( > > > It locks on hard loading (hard HDD usage), > > > like a make release or even make buildworld ;( > > > No panic, no crashdump, nothing, full lock... > > > Just many HDD problems after hard reboot ;( > > > > or something to get the code from midnight on the 20th August. But > > ideally you should try to find what is causing the problem, of course. > > It seems to me, the problem is in SMP code, because > in 1 CPU configuration with the same kernel all works fine. > And when 2 CPU is installed, simple make -j4 buildworld > lock the system after little period of time... > Unfortunatelly I cant find what changes was made in smp stuff... Take a look at the results of 'mptable' and compare them to the SMP values in your kernel config file. Good luck, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 14:53:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rccr1.rccr.cremona.it (rccr1.rccr.cremona.it [194.20.53.49]) by hub.freebsd.org (Postfix) with ESMTP id B8A8837B446 for ; Sat, 26 Aug 2000 14:53:49 -0700 (PDT) Received: from gw2b61-d46.wind.it (rccr1.rccr.cremona.it [194.20.53.49] (may be forged)) by rccr1.rccr.cremona.it (8.9.3/8.9.3) with SMTP id XAA23808 for ; Sat, 26 Aug 2000 23:53:47 +0200 Message-Id: <200008262153.XAA23808@rccr1.rccr.cremona.it> To: freebsd-stable@freebsd.org From: mirko.viviani@rccr.cremona.it Subject: soffice 5.2, linux emulator or... bug ? Date: Sat, 26 Aug 2000 23:53:48 +0000 X-Mailer: Endymion MailMan Standard Edition v3.0.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ciao I have installed staroffice 5.2 manually on FreeBSD 4.1 (linux-base_6.1) in /hd1 that is so mounted: /dev/da1s3a on /hd1 (ufs, local, noatime, writes: sync 1351 async 3119, reads: sync 6062 async 4031) All the installation is in /hd1/office52 Unfortunately every time I start soffice it open the panel with /hd1/office52/user/sofficerc could not be found... The directory has not permission problems, that file exists and if I remove that file soffice will recreate them... unfortunately it does not seem to be able to found it !! :-| I don't know how to do, but I cannot install as the ports want since I have no space in the main partition. If you have any hints please let me know. Thanks. -- Bye, Mirko (NeXTmail, MIME) PS: please reply in e-mail. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 14:59:40 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 07DBF37B42C for ; Sat, 26 Aug 2000 14:59:38 -0700 (PDT) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 237389B05; Sat, 26 Aug 2000 17:59:37 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 14155BA03; Sat, 26 Aug 2000 17:59:37 -0400 (EDT) Date: Sat, 26 Aug 2000 17:59:37 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: mirko.viviani@rccr.cremona.it Cc: freebsd-stable@freebsd.org Subject: Re: soffice 5.2, linux emulator or... bug ? In-Reply-To: <200008262153.XAA23808@rccr1.rccr.cremona.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 Sat, 26 Aug 2000 mirko.viviani@rccr.cremona.it wrote: > Ciao > > I have installed staroffice 5.2 manually on FreeBSD 4.1 (linux-base_6.1) > in /hd1 that is so mounted: > a) if you are not using the port, you may want to try it b) if you are using the port, you may want to cc: the Maintainer ----- 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 Sat Aug 26 16:42: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from lion.kgv.edu.hk (lion.kgv.edu.hk [152.101.128.1]) by hub.freebsd.org (Postfix) with SMTP id 8D0B037B423 for ; Sat, 26 Aug 2000 16:42:03 -0700 (PDT) Received: (qmail 77868 invoked from network); 26 Aug 2000 23:42:02 -0000 Received: from agate.kgv.edu.hk (HELO us) (152.101.128.31) by lion.kgv.edu.hk with SMTP; 26 Aug 2000 23:42:02 -0000 Message-Id: <3.0.6.32.20000827074204.007c7a80@kgv.net> X-Sender: jryan@kgv.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 27 Aug 2000 07:42:04 +0800 To: freebsd-stable@FreeBSD.ORG From: John Ryan Subject: 3.4STABLE to 4.1STABLE can't make modules 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 followed the instructions in UPDATING to the letter, but when I get to /usr/src/sys/modules make install, I get: bash-2.03# cd sys/modules bash-2.03# make install ===> accf_data install -c -o root -g wheel -m 555 accf_data.ko /modules install: accf_data.ko: No such file or directory *** Error code 71 I noticed in the archives, that other people are people are having this problem. Has anyone fixed it? What is accf_data.ko? I did a make update about about a week ago. Thanks John Ryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 16:57:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from drugs.dv.isc.org (drugs.dv.isc.org [130.155.191.236]) by hub.freebsd.org (Postfix) with ESMTP id 9999D37B423 for ; Sat, 26 Aug 2000 16:57:33 -0700 (PDT) Received: from nominum.com (localhost.dv.isc.org [127.0.0.1]) by drugs.dv.isc.org (8.9.3/8.9.3) with ESMTP id KAA06303; Sun, 27 Aug 2000 10:59:11 +1100 (EST) (envelope-from marka@nominum.com) Message-Id: <200008262359.KAA06303@drugs.dv.isc.org> To: John Ryan Cc: freebsd-stable@FreeBSD.ORG From: Mark.Andrews@nominum.com Subject: Re: 3.4STABLE to 4.1STABLE can't make modules In-reply-to: Your message of "Sun, 27 Aug 2000 07:42:04 +0800." <3.0.6.32.20000827074204.007c7a80@kgv.net> Date: Sun, 27 Aug 2000 10:59:11 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The modules are now built as part of "buildkernel" and get installed with "installkernel". Make sure NO_MODULES is set to false in /etc/make.conf or is not set in /etc/default/make.conf. The default has changed to building modules with the kernel rather than world and you need to override the old default. You can verify if the modules were installed w/ installkernel by looking at the modification times in /modules Mark > I've followed the instructions in UPDATING to the letter, but when I get to > /usr/src/sys/modules > make install, I get: > > bash-2.03# cd sys/modules > bash-2.03# make install > ===> accf_data > install -c -o root -g wheel -m 555 accf_data.ko /modules > install: accf_data.ko: No such file or directory > *** Error code 71 > > I noticed in the archives, that other people are people are having this > problem. Has anyone fixed it? What is accf_data.ko? > > I did a make update about about a week ago. > > Thanks > John Ryan > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Mark Andrews, Nominum Inc. 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews@nominum.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 18: 7:33 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 DEFD237B43E for ; Sat, 26 Aug 2000 18:07:18 -0700 (PDT) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id SAA23752; Sat, 26 Aug 2000 18:06:53 -0700 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda23750; Sat Aug 26 18:06:45 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id SAA01451; Sat, 26 Aug 2000 18:06:44 -0700 (PDT) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdTI1449; Sat Aug 26 18:06:01 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.0/8.9.1) id e7R160j00761; Sat, 26 Aug 2000 18:06:00 -0700 (PDT) Message-Id: <200008270106.e7R160j00761@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdsri757; Sat Aug 26 18:05:37 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 4.1-RELEASE X-Sender: cy To: "Chris D. Faulhaber" Cc: mirko.viviani@rccr.cremona.it, freebsd-stable@FreeBSD.ORG Subject: Re: soffice 5.2, linux emulator or... bug ? In-reply-to: Your message of "Sat, 26 Aug 2000 17:59:37 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 26 Aug 2000 18:05:37 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , " Chris D. Faulhaber" writes: > On Sat, 26 Aug 2000 mirko.viviani@rccr.cremona.it wrote: > > > Ciao > > > > I have installed staroffice 5.2 manually on FreeBSD 4.1 (linux-base_6.1) > > in /hd1 that is so mounted: > > > > a) if you are not using the port, you may want to try it > b) if you are using the port, you may want to cc: the Maintainer I've installed StarOffice 5.2 manually (I use ports except for Netscape and StarOffice) and have had no problems. To get StarOffice scripts to work properly I change the shells, #!/bin/sh, in the soffice and setup scripts to #!/compat/linux/bin/bash. 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 Aug 26 18:46:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by hub.freebsd.org (Postfix) with ESMTP id 4146037B423 for ; Sat, 26 Aug 2000 18:46:19 -0700 (PDT) Received: from localhost.localdomain (user-33qt9e7.dialup.mindspring.com [199.174.165.199]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id VAA00837 for ; Sat, 26 Aug 2000 21:46:17 -0400 (EDT) Received: (from david@localhost) by localhost.localdomain (8.9.3/8.9.3) id UAA00287 for freebsd-stable@freebsd.org; Sat, 26 Aug 2000 20:46:15 -0500 (CDT) (envelope-from david) Date: Sat, 26 Aug 2000 20:46:14 -0500 From: "David J. Kanter" To: FreeBSD stable Subject: CD-ROM: RRIP without PX field? Message-ID: <20000826204614.A272@localhost.localdomain> Mail-Followup-To: FreeBSD stable Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 4.1-STABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is very strange. I've compiled a new kernel and when I mount a CD (mount /cdrom) I get this in syslog: localhost /kernel: cd9660: RockRidge Extension localhost /kernel: RRIP without PX field? Then when I try to cd into /cdrom I get this: david@~ % cd /cdrom /cdrom: Not a directory. What's going on? The only thing I can think of is that I've added DMA support to the kernel. ad0: 12395MB [25184/16/63] at ata0-master using UDMA33 acd0: DVD-ROM at ata1-master using WDMA2 afd0: 96MB [96/64/32] at ata1-slave using PIO0 Any ideas? -- David Kanter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 18:55:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from front002.cluster1.charter.net (24-216-159-200.hsacorp.net [24.216.159.200]) by hub.freebsd.org (Postfix) with ESMTP id A1E9E37B424 for ; Sat, 26 Aug 2000 18:55:24 -0700 (PDT) Received: from [24.217.6.45] (HELO dave) by front002.cluster1.charter.net (CommuniGate Pro SMTP 3.2.4) with SMTP id 16894738; Sat, 26 Aug 2000 21:54:00 -0400 From: David Uhring To: "David J. Kanter" , FreeBSD stable Subject: Re: CD-ROM: RRIP without PX field? Date: Sat, 26 Aug 2000 20:53:07 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <20000826204614.A272@localhost.localdomain> In-Reply-To: <20000826204614.A272@localhost.localdomain> MIME-Version: 1.0 Message-Id: <00082620551600.31432@dave> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 26 Aug 2000, David J. Kanter wrote: > This is very strange. I've compiled a new kernel and when I mount a CD > (mount /cdrom) I get this in syslog: > > localhost /kernel: cd9660: RockRidge Extension > localhost /kernel: RRIP without PX field? > > Then when I try to cd into /cdrom I get this: > > david@~ % cd /cdrom > /cdrom: Not a directory. > > What's going on? > > The only thing I can think of is that I've added DMA support to the kernel. > > ad0: 12395MB [25184/16/63] at ata0-master using UDMA33 > acd0: DVD-ROM at ata1-master using WDMA2 > afd0: 96MB [96/64/32] at ata1-slave using PIO0 > > Any ideas? > -- > David Kanter > The ata driver appears to be broken as of 08/20/00. If you have a kernel dated shortly before that, use it. Fortunately, my /kernel.old is dated 08/19/00 and that is the one I am forced to use if I wish to access my CDROM. Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 19:13: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id E83FC37B422 for ; Sat, 26 Aug 2000 19:12:56 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id TAA23673; Sat, 26 Aug 2000 19:12:39 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200008270212.TAA23673@pike.osd.bsdi.com> Subject: Re: CD-ROM: RRIP without PX field? In-Reply-To: <20000826204614.A272@localhost.localdomain> from "David J. Kanter" at "Aug 26, 2000 08:46:14 pm" To: "David J. Kanter" Date: Sat, 26 Aug 2000 19:12:38 -0700 (PDT) Cc: stable@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 David J. Kanter wrote: > This is very strange. I've compiled a new kernel and when I mount a CD > (mount /cdrom) I get this in syslog: > > localhost /kernel: cd9660: RockRidge Extension > localhost /kernel: RRIP without PX field? > > Then when I try to cd into /cdrom I get this: > > david@~ % cd /cdrom > /cdrom: Not a directory. > > What's going on? The acd driver was broken. It has been fixed already though. cvsup and build a new kernel. > The only thing I can think of is that I've added DMA support to the kernel. > > ad0: 12395MB [25184/16/63] at ata0-master using UDMA33 > acd0: DVD-ROM at ata1-master using WDMA2 > afd0: 96MB [96/64/32] at ata1-slave using PIO0 > > Any ideas? > -- > David Kanter -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 19:14:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from adsl-151-197-201-20.bellatlantic.net (adsl-151-197-201-20.bellatlantic.net [151.197.201.20]) by hub.freebsd.org (Postfix) with ESMTP id 3F7E737B424 for ; Sat, 26 Aug 2000 19:14:12 -0700 (PDT) Received: from localhost (root@localhost) by adsl-151-197-201-20.bellatlantic.net (8.9.3/8.9.3) with ESMTP id WAA00348; Sat, 26 Aug 2000 22:14:05 -0400 (EDT) (envelope-from bleez@bellatlantic.net) Date: Sat, 26 Aug 2000 22:14:05 -0400 (EDT) From: Bryan Liesner X-Sender: root@adsl-151-197-201-20.bellatlantic.net To: David Uhring Cc: "David J. Kanter" , FreeBSD stable Subject: Re: CD-ROM: RRIP without PX field? In-Reply-To: <00082620551600.31432@dave> 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, 26 Aug 2000, David Uhring wrote: >On Sat, 26 Aug 2000, David J. Kanter wrote: >> This is very strange. I've compiled a new kernel and when I mount a CD >> (mount /cdrom) I get this in syslog: >> >> localhost /kernel: cd9660: RockRidge Extension >> localhost /kernel: RRIP without PX field? Re-cvsup - it's been corrected. -Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 19:16:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (Postfix) with ESMTP id 87AF337B423 for ; Sat, 26 Aug 2000 19:16:10 -0700 (PDT) Received: from tao.thought.org (tao.sea.tera.com [207.108.223.55]) by gershwin.tera.com (8.9.3/8.9.3) with ESMTP id TAA09071; Sat, 26 Aug 2000 19:16:27 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.9.3/8.7.3) id TAA27828; Sat, 26 Aug 2000 19:16:06 -0700 (PDT) Date: Sat, 26 Aug 2000 19:16:06 -0700 From: Gary Kline To: John Ryan Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 3.4STABLE to 4.1STABLE can't make modules Message-ID: <20000826191606.A27736@tao.thought.org> References: <3.0.6.32.20000827074204.007c7a80@kgv.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.20000827074204.007c7a80@kgv.net>; from jryan@kgv.edu.hk on Sun, Aug 27, 2000 at 07:42:04AM +0800 X-Organization: Thought Unlimited. Public service Unix since 1986. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 27, 2000 at 07:42:04AM +0800, John Ryan wrote: > I've followed the instructions in UPDATING to the letter, but when I get to > /usr/src/sys/modules > make install, I get: > > bash-2.03# cd sys/modules > bash-2.03# make install > ===> accf_data > install -c -o root -g wheel -m 555 accf_data.ko /modules > install: accf_data.ko: No such file or directory > *** Error code 71 > > I noticed in the archives, that other people are people are having this > problem. Has anyone fixed it? What is accf_data.ko? > I stumbled into this same err a week or so ago. The upshot of my experience is that when your # make buildkernel installkernel KERNEL=GENERIC completes, the kernel objects (*.ko files) will be in your root directory, in /modules. In other words, the UPDATING file is incorrect. I made changes to UPDATING and sent the maintainer a patch, but evidently he hasn't seen fit to use my patch. gary PS: Fellow engineer Sean O'Connell at Duke helped me out ... I'm just sharing along the assist. -- Gary D. Kline kline@tao.thought.org Public service Unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 19:21:13 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 D75CC37B422 for ; Sat, 26 Aug 2000 19:21:07 -0700 (PDT) Received: by kci.kciLink.com (Postfix, from userid 100) id 689A6E881; Sat, 26 Aug 2000 22:21:07 -0400 (EDT) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14760.31507.327463.250420@kci.kciLink.com> Date: Sat, 26 Aug 2000 22:21:07 -0400 (EDT) To: FreeBSD stable Subject: Re: CD-ROM: RRIP without PX field? In-Reply-To: <00082620551600.31432@dave> References: <20000826204614.A272@localhost.localdomain> <00082620551600.31432@dave> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "DU" == David Uhring writes: DU> The ata driver appears to be broken as of 08/20/00. If you have a DU> kernel dated shortly before that, use it. Fortunately, my DU> /kernel.old is dated 08/19/00 and that is the one I am forced to DU> use if I wish to access my CDROM. The patch to this was committed on Friday. Re-update your sources and build a new kernel. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 GPG & MIME spoken here http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 20:22: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (Postfix) with ESMTP id 083BC37B422 for ; Sat, 26 Aug 2000 20:21:57 -0700 (PDT) Received: from tao.thought.org (tao.sea.tera.com [207.108.223.55]) by gershwin.tera.com (8.9.3/8.9.3) with ESMTP id UAA09475; Sat, 26 Aug 2000 20:22:13 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.9.3/8.7.3) id UAA28285; Sat, 26 Aug 2000 20:21:52 -0700 (PDT) From: Gary Kline Message-Id: <200008270321.UAA28285@tao.thought.org> Subject: Re: mouse question.... To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Sat, 26 Aug 2000 20:21:52 -0700 (PDT) Cc: kline@thought.org (Gary Kline), freebsd-stable@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp In-Reply-To: <200008260746.QAA26455@zodiac.mech.utsunomiya-u.ac.jp> from "Kazutaka YOKOTA" at Aug 26, 2000 04:46:58 PM Organization: <> thought.org: pvblic service Unix since 1986... <> 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 According to Kazutaka YOKOTA: > > > Please do the following to diagnose the problem. > > 1. Hook up the mouse (it's a serial mouse, right?) to COM1 > > 2. Become root. > > 3. Don't run X yet. Kill `moused' if it is already running. > (Run "ps aux | grep mouse" to see if it is running. Kill it if any.) > > 4. Run moused in the information mode as follows: > moused -p /dev/cuaa0 -i all > You should get some information if the mouse is a PnP mouse or a > Microsoft-compatible mouse. Something like: > /dev/cuaa0 serial microsoft generic > > 5. Run moused again, this time in the debug mode: > moused -p /dev/cuaa0 -d -f > If you move mouse and click buttons, you should see mouse status > information should be printed. Type ^C to stop moused. > If this seems Ok, then you should edit /etc/rc.conf and > put the following lines there: > moused_enable="YES" > moused_type="auto" > moused_port="/dev/cuaa0" > Then, edit /etc/XF86Config and set the mouse protocol to "Auto" and > the mouse device to "/dev/sysmouse". > Start moused in the daemon mode by hand for now (this will automatically > done the next time the system is rebooted.) > moused -p /dev/cuaa0 -t auto > > 6. If moused says 'cannot determine mouse type...' in 4, the mouse > may be a MouseSystems-compatible mouse, or it may be broken. > If the mouse is considered MouseSystems-compatible, you can > test the mouse as follows: > moused -p /dev/cuaa0 -d -f -t mousesystems > If this is successful Ok, then you should edit /etc/rc.conf and > put the following lines there: > moused_enable="YES" > moused_type="mousesystems" > moused_port="/dev/cuaa0" > Edit /etc/XF86Config and set the mouse protocol to "Auto" and > the mouse device to "/dev/sysmouse". > Start moused in the daemon mode by hand for now (this will automatically > done the next time the system is rebooted.) > moused -p /dev/cuaa0 -t mousesystems > > This is getting stranger and stranger. I just bought a new Logitech mouse and have it plugged directly into the COM1 port. The results are the same as before for trying your (4) above, and moused -p /dev/cuaa0 -d -f -t mouseman moused: port: /dev/cuaa0 interface: unknown type: mouseman model: generic moused: received char 0x0 for the above. The ``received char 0x0'' only happened one time. Does this suggest anything to you? Or anyone else on the list? gary -- Gary D. Kline kline@tao.thought.org Public service Unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 20:41:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 4EAA837B43E for ; Sat, 26 Aug 2000 20:41:10 -0700 (PDT) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:ZSOXGCr2jhxDCQW21Er/Wg/0veO+ZdeO@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id MAA18681; Sun, 27 Aug 2000 12:41:09 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:wv61u2yFJ2Q8HVGlY0HleBKXrkQlEGKe@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id MAA09239; Sun, 27 Aug 2000 12:48:00 +0900 (JST) Message-Id: <200008270348.MAA09239@zodiac.mech.utsunomiya-u.ac.jp> To: Gary Kline Cc: freebsd-stable@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: mouse question.... In-reply-to: Your message of "Sat, 26 Aug 2000 20:21:52 MST." <200008270321.UAA28285@tao.thought.org> References: <200008270321.UAA28285@tao.thought.org> Date: Sun, 27 Aug 2000 12:47:59 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [...] > This is getting stranger and stranger. I just bought a new > Logitech mouse and have it plugged directly into the COM1 > port. > > The results are the same as before for trying your (4) above, > and > >moused -p /dev/cuaa0 -d -f -t mouseman >moused: port: /dev/cuaa0 interface: unknown type: mouseman model: generic >moused: received char 0x0 > > for the above. The ``received char 0x0'' only happened one time. When you moved the mouse, did you see any further messages? > Does this suggest anything to you? Or anyone else on the list? Is it a "plain" MouseMan? Is it a serial model? If it is a PS/2-port-only model or a PS/2-port and USB model, you cannot put it to a serial port. If it is a plain MouseMan (3 button mouse without a wheel), find a label on the belly of the mouse. You sould find the model # and description. If it says "Serial" or "Serial-MousePort", then you can plug it to a serial port. If it says "MousePort", it is a PS/2 model. Once you are sure that it is a serial mouse, try the following command ("auto" instead of "mouseman"). moused -p /dev/cuaa0 -d -f -t auto Unless your MouseMan is one of very old models, moused should be able to detect it is MouseMan. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 20:52:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from odin.egate.net (as2.dm.egate.net [216.235.1.5]) by hub.freebsd.org (Postfix) with ESMTP id 82E2837B42C for ; Sat, 26 Aug 2000 20:52:36 -0700 (PDT) Received: from localhost (buff@localhost) by odin.egate.net (8.9.3/8.9.1) with ESMTP id XAA11362 for ; Sat, 26 Aug 2000 23:52:26 -0400 (EDT) X-Authentication-Warning: odin.egate.net: buff owned process doing -bs Date: Sat, 26 Aug 2000 23:52:24 -0400 (EDT) From: William Denton X-Sender: buff@odin.egate.net To: freebsd-stable@FreeBSD.ORG Subject: What's the best way to build a GENERIC 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 Hi, Before the 'make buildkernel' change to STABLE last month, I had my usual kernel as /MYCROFT and the generic one as /GENERIC, and every now and then when I built a new world I'd install a new GENERIC to be on the safe side. (I once installed the wrong kernel on this machine, and had some trouble with an old GENERIC, so I like to keep it fairly up to date.) Now, though, what's the best way to build it? Building it the normal way will install it as /kernel, so I'd have to move it out of the way by hand. And what about modules? My custom kernel uses fewer, so would GENERIC run into trouble if it looked for them and they weren't there? Bill -- William Denton : Toronto, Canada : http://www.miskatonic.org/ : Caveat lector. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 20:59: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (Postfix) with ESMTP id 189DA37B422 for ; Sat, 26 Aug 2000 20:58:56 -0700 (PDT) Received: from tao.thought.org (tao.sea.tera.com [207.108.223.55]) by gershwin.tera.com (8.9.3/8.9.3) with ESMTP id UAA09693; Sat, 26 Aug 2000 20:59:12 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.9.3/8.7.3) id UAA28536; Sat, 26 Aug 2000 20:58:52 -0700 (PDT) From: Gary Kline Message-Id: <200008270358.UAA28536@tao.thought.org> Subject: Re: mouse question.... To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Sat, 26 Aug 2000 20:58:52 -0700 (PDT) Cc: kline@thought.org (Gary Kline), freebsd-stable@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp In-Reply-To: <200008270348.MAA09239@zodiac.mech.utsunomiya-u.ac.jp> from "Kazutaka YOKOTA" at Aug 27, 2000 12:47:59 PM Organization: <> thought.org: pvblic service Unix since 1986... <> 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 According to Kazutaka YOKOTA: > > > [...] > > This is getting stranger and stranger. I just bought a new > > Logitech mouse and have it plugged directly into the COM1 > > port. > > > > The results are the same as before for trying your (4) above, > > and > > > >moused -p /dev/cuaa0 -d -f -t mouseman > >moused: port: /dev/cuaa0 interface: unknown type: mouseman model: generic > >moused: received char 0x0 > > > > for the above. The ``received char 0x0'' only happened one time. > > When you moved the mouse, did you see any further messages? > No, nothing; and upon trying the moused command again, there were no debug messages at all. > > Does this suggest anything to you? Or anyone else on the list? > > Is it a "plain" MouseMan? Is it a serial model? If it is a > PS/2-port-only model or a PS/2-port and USB model, you cannot put it > to a serial port. > > If it is a plain MouseMan (3 button mouse without a wheel), > find a label on the belly of the mouse. You sould find the model # > and description. If it says "Serial" or "Serial-MousePort", then > you can plug it to a serial port. If it says "MousePort", it is > a PS/2 model. > > Once you are sure that it is a serial mouse, try the following > command ("auto" instead of "mouseman"). > > moused -p /dev/cuaa0 -d -f -t auto This is a "three button" serial mouse. I'll try the auto -t type. Yes! But still bizarre. Let's see if I can do it from an xterm here. Save typing. --yes. sage# moused -p /dev/cuaa0 -d -f -t auto moused: PnP COM device rev 1.0 probe... moused: modem status 0603 moused: alternate probe... moused: cannot determine mouse type on /dev/cuaa0 moused: port: /dev/cuaa0 interface: unknown type: unknown model: generic sage# Does this suggest that there is a modem on /dev/cuaa0? I thought the modem was yanked weeks or months ago. Does the status 0603 indicate a bad port, perhaps? gary > > Unless your MouseMan is one of very old models, moused should be > able to detect it is MouseMan. > > Kazu > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- Gary D. Kline kline@tao.thought.org Public service Unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 21:30: 7 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 5CE4E37B424 for ; Sat, 26 Aug 2000 21:30:04 -0700 (PDT) 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 WAA83303; Sat, 26 Aug 2000 22:30:02 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA83068; Sat, 26 Aug 2000 22:29:53 -0600 (MDT) Message-Id: <200008270429.WAA83068@harmony.village.org> To: John Ryan Subject: Re: 3.4STABLE to 4.1STABLE can't make modules Cc: freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Sun, 27 Aug 2000 07:42:04 +0800." <3.0.6.32.20000827074204.007c7a80@kgv.net> References: <3.0.6.32.20000827074204.007c7a80@kgv.net> Date: Sat, 26 Aug 2000 22:29:53 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3.0.6.32.20000827074204.007c7a80@kgv.net> John Ryan writes: : I've followed the instructions in UPDATING to the letter, but when I get to : /usr/src/sys/modules I've udpated the UPDATING file recently to remove this step. Please grab a new copy of UPDATING and try again. Basically, you just skip those two steps. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 21:33: 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 06B8E37B424 for ; Sat, 26 Aug 2000 21:32:58 -0700 (PDT) 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 WAA83316; Sat, 26 Aug 2000 22:32:56 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA83112; Sat, 26 Aug 2000 22:32:46 -0600 (MDT) Message-Id: <200008270432.WAA83112@harmony.village.org> To: Gary Kline Subject: Re: 3.4STABLE to 4.1STABLE can't make modules Cc: John Ryan , freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Sat, 26 Aug 2000 19:16:06 PDT." <20000826191606.A27736@tao.thought.org> References: <20000826191606.A27736@tao.thought.org> <3.0.6.32.20000827074204.007c7a80@kgv.net> Date: Sat, 26 Aug 2000 22:32:46 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000826191606.A27736@tao.thought.org> Gary Kline writes: : In other words, the UPDATING file is incorrect. I made changes : to UPDATING and sent the maintainer a patch, but evidently he : hasn't seen fit to use my patch. Are you sure? I'm pretty sure that this was fixed: revision 1.73.2.14 date: 2000/08/24 18:46:51; author: imp; state: Exp; lines: +1 -3 Remove manual installation of modules. installkernel does that. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 26 22:37:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from limit.org (limit.org [216.102.231.2]) by hub.freebsd.org (Postfix) with ESMTP id 4B18337B43E for ; Sat, 26 Aug 2000 22:37:36 -0700 (PDT) Received: (from michael@localhost) by limit.org (8.9.3/8.9.3) id WAA00892 for freebsd-stable@freebsd.org; Sat, 26 Aug 2000 22:37:36 -0700 (PDT) (envelope-from michael) Date: Sat, 26 Aug 2000 22:37:36 -0700 From: Michael Matsumura To: freebsd-stable@freebsd.org Subject: Re: Promise Ultra66 Controller Card Message-ID: <20000826223736.A876@jupiter.limit.org> References: <20000825230509.A580@jupiter.limit.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from larse@ISI.EDU on Fri, Aug 25, 2000 at 11:10:43PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've tried this card on Windows 98 (different hard drive), same motherboard, and it worked, so its probably not the card. Weird thing...when I have my second hard drive on the same IDE cable (non-bootable), it give me a different message... Disk error 0x80 (lba=0x13e94f) Invalid format compared to the error message WITH the other hard drive... On Fri, Aug 25, 2000 at 11:10:43PM -0700, Lars Eggert wrote: > > I saw the same on one of a few identical machines - in our case, the card > had a defect. > -- > Lars Eggert Information Sciences Institute > http://www.isi.edu/larse/ University of Southern California -- Michael Matsumura michael@limit.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message