From owner-freebsd-stable Sun Jun 7 06:01:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24889 for freebsd-stable-outgoing; Sun, 7 Jun 1998 06:01:47 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from colin.muc.de (root@colin.muc.de [193.174.4.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA24878 for ; Sun, 7 Jun 1998 06:01:43 -0700 (PDT) (envelope-from lutz@muc.de) Received: from tavari.muc.de ([193.174.4.22]) by colin.muc.de with SMTP id <140556-2>; Sun, 7 Jun 1998 14:37:24 +0200 Received: from muc.de (abraxas [192.168.42.5]) by tavari.muc.de (8.8.8/8.8.7) with ESMTP id MAA08136; Sun, 7 Jun 1998 12:42:26 +0200 (CEST) Message-ID: <357A6E91.FD2036C6@muc.de> Date: Sun, 7 Jun 1998 12:42:25 +0200 From: Lutz Albers X-Mailer: Mozilla 4.04 [en] (X11; U; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: Brian Somers , freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.6 ppp breaks compatability with T-Online ppp References: <199806061947.UAA29853@awfulhak.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers wrote: > > > On Thu, 28 May 1998, Brian Somers wrote: > > > > > Oops - this got lost in my piles of email :-( Sorry. > > > > > > Can you remove the ``set ifaddr 0 0'' and see if things get better ? > > > > Yes, that did it. Thanks, but why did it worked with the old code in 2.2.5 > > ? > > > > ciao > > lutz > > I'm not sure why ppp's behaving like this. I can't make this happen > myself unless I ``set ifaddr 0/32 0'', causing ppp to insist on > 0.0.0.0..... > > Does ``show ipcp'' show ``0.0.0.0/0'' or ``0.0.0.0/32'' ? With set ifaddr 0 0: ppp ON morranon> show ipcp IPCP [Initial] Defaults: My Address: 0.0.0.0/0 His Address: 0.0.0.0/32 Negotiation(trigger): MYADDR Without set ifaddr: IPCP [Initial] Defaults: My Address: 192.168.42.3/0 His Address: 0.0.0.0/0 Negotiation(trigger): MYADDR Note that 192.168.42.3 is the ip-address of the ethernet card in this box. ciao lutz -- Lutz Albers, lutz@muc.de Do not take life too seriously, you will never get out of it alive. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 7 06:57:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00540 for freebsd-stable-outgoing; Sun, 7 Jun 1998 06:57:02 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ints3.csie.nctu.edu.tw (james@ints3.csie.nctu.edu.tw [140.113.215.192]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00277 for ; Sun, 7 Jun 1998 06:54:59 -0700 (PDT) (envelope-from james@ints3.csie.nctu.edu.tw) Received: (from james@localhost) by ints3.csie.nctu.edu.tw (8.8.8/8.8.8) id VAA06424 for freebsd-stable@FreeBSD.ORG; Sun, 7 Jun 1998 21:53:54 +0800 (CST) (envelope-from james) From: Wei-Kai Wu Message-Id: <199806071353.VAA06424@ints3.csie.nctu.edu.tw> Subject: Stray Dequot, reboot ?! X-ELM-OSV: (Our standard violations) no-mime=1; no-hdr-encoding=1 To: freebsd-stable@FreeBSD.ORG (FreeBSD stable Mailing List) Date: Sun, 7 Jun 1998 21:53:53 +0800 (CST) X-Mailer: ELM [version 2.4ME+ PL31H (25)] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello: When I "reboot" my freebsd, (ctm src-2.2.0700) I always show me the messages: Stray Dequot ...(I can't copy in detail) Reboot in 15 seconds... Anyone knows what's the problem? Thanks a lot! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 7 07:05:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01710 for freebsd-stable-outgoing; Sun, 7 Jun 1998 07:05:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from techpower.net (hometeam@techpower.net [205.133.231.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA01701 for ; Sun, 7 Jun 1998 07:05:41 -0700 (PDT) (envelope-from hometeam@techpower.net) Received: from localhost (hometeam@localhost) by techpower.net (8.8.8/8.8.8) with SMTP id KAA00302 for ; Sun, 7 Jun 1998 10:05:07 -0400 (EDT) (envelope-from hometeam@techpower.net) Date: Sun, 7 Jun 1998 10:05:07 -0400 (EDT) From: Jt Reply-To: Jt To: freebsd-stable@FreeBSD.ORG Subject: stable broken 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 who broke stable? cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -nostdinc -I- -I. -I. ./.. -I../../../include -DAPM_BROKEN_STATCLOCK -DFAILSAFE -DCOMPAT_43 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL -DMAXUSERS=10 -UKERNEL ../../i386/i386/genassym.c In file included from ../../sys/types.h:48, from ../../../include/stdio.h:44, from ../../i386/i386/genassym.c:40: machine/ansi.h:41: warning: `/*' within comment In file included from ../../sys/types.h:49, from ../../../include/stdio.h:44, from ../../i386/i386/genassym.c:40: machine/types.h:37: unterminated `#if' conditional In file included from ../../sys/proc.h:45, from ../../i386/i386/genassym.c:43: machine/proc.h:37: unterminated `#if' conditional In file included from ../../vm/pmap.h:87, from ../../i386/i386/genassym.c:65: machine/pmap.h:209: warning: missing white space after `#define P' machine/pmap.h:217: unbalanced `#endif' *** Error code 1 ?? Must of been the adds last nite? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 7 07:13:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02862 for freebsd-stable-outgoing; Sun, 7 Jun 1998 07:13:40 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from fledge.watson.org (root@COPLAND.CODA.CS.CMU.EDU [128.2.222.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02825 for ; Sun, 7 Jun 1998 07:13:29 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id KAA08712 for ; Sun, 7 Jun 1998 10:13:27 -0400 (EDT) Date: Sun, 7 Jun 1998 10:13:26 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: stable@FreeBSD.ORG Subject: cvsuping the cvs tree Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm about to begin a fairly substantial set of changes to a -stable kernel to introduce authentication/authorization token handling support. However, I would like to continue tracking the -stable branch to catch bug fixes, new features, etc as they become available. Ideally, I'd also like to use the merge support in CVS to do this. What is the best way to do this on my local machine? Is anon CVS access sufficient to do cvs updates and checkouts, etc, for the merging? Can cvsup do this without zapping my source changes? :-) I was going to do this under -current, but most of my machines are -stable, and apparently you can't build -current world/kernel under -stable. The only local machine I have is a notebook running -current, but without enough disk space to build world. Thanks, Robert N Watson Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ robert@fledge.watson.org http://www.watson.org/~robert/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 7 07:15:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA03169 for freebsd-stable-outgoing; Sun, 7 Jun 1998 07:15:53 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pc23-c801.uibk.ac.at (fatal@pc23-c801.uibk.ac.at [138.232.92.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA03140 for ; Sun, 7 Jun 1998 07:15:47 -0700 (PDT) (envelope-from fatal@pc23-c801.uibk.ac.at) Received: (from fatal@localhost) by pc23-c801.uibk.ac.at (8.8.6/8.8.6) id QAA25006 for freebsd-stable@freebsd.org; Sun, 7 Jun 1998 16:15:56 +0200 From: Marco van Hylckama Vlieg Message-Id: <199806071415.QAA25006@pc23-c801.uibk.ac.at> Subject: make world fails To: freebsd-stable@FreeBSD.ORG Date: Sun, 7 Jun 1998 16:15:56 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I'm trying to make world on the the stable release and I get: (cd /usr/src/share/doc/papers/kernmalloc; soelim kernmalloc.t) > kernmalloc.ms vgrind -f < /usr/src/share/doc/papers/kernmalloc/appendix.t > appendix.ms vgrind: error 14 *** Error code 2 Stop. *** Error code 1 etc.etc.etc. Can anyone please tell me if this is a bug or if I'm doing something wrong? TIA Marco -- QQWT!"^""9QQQ ------------------------------------------------ QP' _%7? WindowMaker, the choice of a GNUstep Generation. P WQQ, http://www.windowmaker.org/ ' mWQh Marco's WindowMaker icons: .__s_QWQQ http://global.uibk.ac.at/~fatal/wmaker/ . ]QQQQQQQ@ L )WQQQQQQ( Marco van Hylckama Vlieg !`_ajQQQQQ@( fatal@global.uibk.ac.at (NeXTmail OK) "?TUVY"` ------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 7 07:23:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04095 for freebsd-stable-outgoing; Sun, 7 Jun 1998 07:23:00 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04063 for ; Sun, 7 Jun 1998 07:22:44 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id QAA13078; Sun, 7 Jun 1998 16:22:30 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Sun, 7 Jun 1998 16:22:29 +0200 (MET DST) Mime-Version: 1.0 To: KHamilton@Hunter.COM Cc: jdp@polstra.com, FreeBSD-Stable@FreeBSD.ORG Subject: Re: Boot floppy with CAM support? References: <92BD86195CB3D011832F0000C052D9E369096E@mystique.Hunter.COM> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-email-address-1: dag-erli@ifi.uio.no (for private or study-related mail) X-email-address-2: dagsm@hypnotech.no (for job-related mail) X-email-address-3: des@FreeBSD.org (for FreeBSD-related mail) X-email-address-4: finrod@ewox.org (for demoscene-related mail) X-disclaimer-1: I speak only for myself. The views expressed in this message X-disclaimer-2: are not those of the University of Oslo, the FreeBSD project, X-disclaimer-3: or any other organization or company to which I am or have at X-disclaimer-4: some time been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 07 Jun 1998 16:22:28 +0200 In-Reply-To: KHamilton@Hunter.COM's message of "Thu, 4 Jun 1998 15:11:51 -0500" Message-ID: Lines: 10 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG KHamilton@Hunter.COM writes: > Thanks. Any idea why the floppy with CAM in it can't see my Intel > Pro-100B card but the floppy without CAM can see the netcard just fine. Probably because the fxp driver was dropped to make room for the CAM code. Ask somebody who's running CAM to build you a custom install floppy. -- Noone else has a .sig like this one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 7 07:35:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05476 for freebsd-stable-outgoing; Sun, 7 Jun 1998 07:35:25 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05421 for ; Sun, 7 Jun 1998 07:34:16 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id QAA13646; Sun, 7 Jun 1998 16:34:11 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Sun, 7 Jun 1998 16:34:10 +0200 (MET DST) Mime-Version: 1.0 To: "Viren R. Shah" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NFS woes: FreeBSD client & Solaris 2.5.1 server References: <199806031230.IAA00642@fault.rstcorp.com> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-email-address-1: dag-erli@ifi.uio.no (for private or study-related mail) X-email-address-2: dagsm@hypnotech.no (for job-related mail) X-email-address-3: des@FreeBSD.org (for FreeBSD-related mail) X-email-address-4: finrod@ewox.org (for demoscene-related mail) X-disclaimer-1: I speak only for myself. The views expressed in this message X-disclaimer-2: are not those of the University of Oslo, the FreeBSD project, X-disclaimer-3: or any other organization or company to which I am or have at X-disclaimer-4: some time been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 07 Jun 1998 16:34:10 +0200 In-Reply-To: "Viren R. Shah"'s message of "Wed, 3 Jun 1998 08:30:07 -0400 (EDT)" Message-ID: Lines: 13 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Viren R. Shah" writes: > This box acts as a NFS server for most of the filesystems, and there > are no problems with the filesystems it is serving (NFSv2). > > However, it also mounts one filesystem from a Solaris 2.5.1 server: > snoop:/home/research on /home/research This is a FAQ. -- Noone else has a .sig like this one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 7 07:45:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06528 for freebsd-stable-outgoing; Sun, 7 Jun 1998 07:45:03 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from techpower.net (hometeam@techpower.net [205.133.231.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06519 for ; Sun, 7 Jun 1998 07:44:53 -0700 (PDT) (envelope-from hometeam@techpower.net) Received: from localhost (hometeam@localhost) by techpower.net (8.8.8/8.8.8) with SMTP id KAA01136 for ; Sun, 7 Jun 1998 10:44:21 -0400 (EDT) (envelope-from hometeam@techpower.net) Date: Sun, 7 Jun 1998 10:44:20 -0400 (EDT) From: Jt To: freebsd-stable@FreeBSD.ORG Subject: stable broken Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsup the include dir again and kernel making fine now.**shrugh** hometeam@techpower.net --We cannot all be masters, nor all masters Cannot be truly follow'd-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 7 07:50:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07571 for freebsd-stable-outgoing; Sun, 7 Jun 1998 07:50:23 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA07468; Sun, 7 Jun 1998 07:50:02 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id QAA14182; Sun, 7 Jun 1998 16:45:48 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Sun, 7 Jun 1998 16:45:47 +0200 (MET DST) Mime-Version: 1.0 To: Gary Kline Cc: malte@webmore.com, kline@thought.org, stable@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: X11 problem? References: <199806021728.KAA09756@athena.tera.com> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-email-address-1: dag-erli@ifi.uio.no (for private or study-related mail) X-email-address-2: dagsm@hypnotech.no (for job-related mail) X-email-address-3: des@FreeBSD.org (for FreeBSD-related mail) X-email-address-4: finrod@ewox.org (for demoscene-related mail) X-disclaimer-1: I speak only for myself. The views expressed in this message X-disclaimer-2: are not those of the University of Oslo, the FreeBSD project, X-disclaimer-3: or any other organization or company to which I am or have at X-disclaimer-4: some time been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 07 Jun 1998 16:45:46 +0200 In-Reply-To: Gary Kline's message of "Tue, 2 Jun 1998 10:28:47 -0700 (PDT)" Message-ID: Lines: 28 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gary Kline writes: > Anyhow, back to the W32 problem, one of the XFree86 people > tells me that the W32 server has known flaws. ((I read some > of them. This one may not have been reported until now.)) If you're running XFree86 3.3.x, you should probably consider using the SVAG server instead of the W32 server: The SVGA driver for ET4000 chipsets supports all color depths (8, 15, 16, 24 and 24 bpp) on most ET4000 chips starting with the ET4000W32i. The ET4000W32 only supports 8bpp. Depending on the RAMDAC and the support code in the SVGA server, some cards may only support a few of these color depths, or even only 8bpp. XF86_W32 gets phased out, now that the SVGA server with XAA acceleration is at least as fast as the W32 server but supports more cards and for some even higher color depths. For details about using the XF86_SVGA with W32 cards, look below. Note that currently not all cards that are accelerated by XF86_W32 are accelerated by XF86_SVGA at this moment (only ET6000 and ET4000W32p to be exact). -- Noone else has a .sig like this one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 7 10:09:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02057 for freebsd-stable-outgoing; Sun, 7 Jun 1998 10:09:10 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02028 for ; Sun, 7 Jun 1998 10:08:54 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id SAA15278; Sun, 7 Jun 1998 18:05:40 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199806071705.SAA15278@awfulhak.org> X-Mailer: exmh version 2.0.1 12/23/97 To: Lutz Albers cc: Brian Somers , freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.6 ppp breaks compatability with T-Online ppp In-reply-to: Your message of "Sun, 07 Jun 1998 12:42:25 +0200." <357A6E91.FD2036C6@muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Jun 1998 18:05:40 +0100 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > ppp ON morranon> show ipcp > IPCP [Initial] > Defaults: > My Address: 0.0.0.0/0 > His Address: 0.0.0.0/32 ****BZZZT**** Thanks. I've identified and fixed the problem in RELENG_2_2. It's already fixed in -current (``0'' always means ``0/0''). > Negotiation(trigger): MYADDR > > Without set ifaddr: > IPCP [Initial] > Defaults: > My Address: 192.168.42.3/0 > His Address: 0.0.0.0/0 > Negotiation(trigger): MYADDR > > Note that 192.168.42.3 is the ip-address of the ethernet card in this > box. > > ciao > lutz > > -- > Lutz Albers, lutz@muc.de > Do not take life too seriously, you will never get out of it alive. > -- 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 Jun 7 11:58:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18414 for freebsd-stable-outgoing; Sun, 7 Jun 1998 11:58:27 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18405; Sun, 7 Jun 1998 11:58:21 -0700 (PDT) (envelope-from kline@tera.com) Received: from athena.tera.com (athena.tera.com [207.224.230.127]) by gershwin.tera.com (8.8.8/8.8.8) with ESMTP id LAA29135; Sun, 7 Jun 1998 11:57:23 -0700 (PDT) From: Gary Kline Received: (from kline@localhost) by athena.tera.com (8.7.5/8.7.3) id LAA13533; Sun, 7 Jun 1998 11:57:17 -0700 (PDT) Message-Id: <199806071857.LAA13533@athena.tera.com> Subject: Re: X11 problem? In-Reply-To: from "Dag-Erling Coidan [Sm_rgrav]" at "Jun 7, 98 04:45:46 pm" To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?=) Date: Sun, 7 Jun 1998 11:57:16 -0700 (PDT) Cc: kline@tera.com, malte@webmore.com, kline@thought.org, stable@FreeBSD.ORG, questions@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL23 (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 According to Dag-Erling Coidan [Sm_rgrav]: > Gary Kline writes: > > Anyhow, back to the W32 problem, one of the XFree86 people > > tells me that the W32 server has known flaws. ((I read some > > of them. This one may not have been reported until now.)) > > If you're running XFree86 3.3.x, you should probably consider using > the SVAG server instead of the W32 server: > > > > The SVGA driver for ET4000 chipsets supports all color depths (8, 15, 16, 24 > and 24 bpp) on most ET4000 chips starting with the ET4000W32i. The ET4000W32 > only supports 8bpp. Depending on the RAMDAC and the support code in the SVGA > server, some cards may only support a few of these color depths, or even only > 8bpp. > > > > XF86_W32 gets phased out, now that the SVGA server with XAA acceleration is at > least as fast as the W32 server but supports more cards and for some even > higher color depths. For details about using the XF86_SVGA with W32 cards, look > below. Note that currently not all cards that are accelerated by XF86_W32 are > accelerated by XF86_SVGA at this moment (only ET6000 and ET4000W32p to be > exact). > Thanks. I wasn't clear on this until your posting encouraged me to take an hour or two and _try_ it. I've got a Cardex Challenger Pro and the latest SVGA driver does work! xvidtune has tweaked the display and it looks nice. I've already ordered ``Jordan's Pick'', the Matrox Millennium---figured that three years is worth a card upgrade. Maybe the Matrox with 4M will let me go to 1280x1024. For now, one step closer to being done upgrading. gary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 7 12:54:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26459 for freebsd-stable-outgoing; Sun, 7 Jun 1998 12:54:54 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pn.wagsky.com (wagsky.vip.best.com [206.86.71.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26440 for ; Sun, 7 Jun 1998 12:54:36 -0700 (PDT) (envelope-from Jeff@Wagsky.com) Received: from [192.168.6.3] (mac.pn.wagsky.com [192.168.6.3]) by pn.wagsky.com (8.8.8/8.8.8) with ESMTP id MAA00214 for ; Sun, 7 Jun 1998 12:54:33 -0700 (PDT) (envelope-from Jeff@Wagsky.com) X-Sender: wagsky@shell9.ba.best.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 7 Jun 1998 12:54:29 -0700 To: freebsd-stable@FreeBSD.ORG From: Jeff Kletsky Subject: rc.firewall and ipfw commands Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After building from 2.2.6-STABLE I came across a bit of a puzzle with the apparent loss of DNS and a lot of other services on my machine. The "problem" is that the rule numbers for the hard-wired rules in rc.firewall have been changed: $fwcmd add 100 pass all from any to any via lo0 $fwcmd add 200 deny all from any to 127.0.0.0/8 Now, if you are using the supplied named firewall options, you're ok. If you are using a file containing commands, or other utilities which modify the firewall, you could be in trouble (I happen to use the previously-unused rule 100 to monitor what's bringing up dial-on-demand ppp, so it is routinely deleted and added as the link changes state). Short-term fix: --------------- Leave the rules in place so the named firewall types work. Change rc.firewall to read: $fwcmd -f flush # because "-f flush" fails in a file* $fwcmd ${firewall_type} Long-term fix: -------------- Convince the powers that be to only add the "standard" rules for the named firewall types. Jeff * Including "-f flush" as the first line of the file causes the next ipfw command in the sequence to abort execution... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 7 13:20:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00380 for freebsd-stable-outgoing; Sun, 7 Jun 1998 13:20:07 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00256 for ; Sun, 7 Jun 1998 13:19:44 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id WAA08948; Sun, 7 Jun 1998 22:15:06 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id VAA11290; Sun, 7 Jun 1998 21:59:16 +0200 (CEST) (envelope-from andreas) Message-ID: <19980607215916.A7507@klemm.gtn.com> Date: Sun, 7 Jun 1998 21:59:16 +0200 From: Andreas Klemm To: Matthew Cashdollar , freebsd-stable@FreeBSD.ORG Subject: Re: bind 8 or 4 ? References: <19980604103724.A1480@rfcnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19980604103724.A1480@rfcnet.com>; from Matthew Cashdollar on Thu, Jun 04, 1998 at 10:37:24AM -0500 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jun 04, 1998 at 10:37:24AM -0500, Matthew Cashdollar wrote: > > Is stable going to be moving to bind 8? I am currently using 4 and > would like to upgrade, but if it is going to be in the base system > I'd rather wait instead of installing the port. I think FreeBSD-STABLE will stay at bind4. But where is the problem to use the bind8 port ? Usually you have a demand or not. And if you have, you can easily install the port ... -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 7 14:27:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09397 for freebsd-stable-outgoing; Sun, 7 Jun 1998 14:27:01 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mailq1.ncal.verio.com (mailq1.ncal.verio.com [204.247.247.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09357 for ; Sun, 7 Jun 1998 14:26:40 -0700 (PDT) (envelope-from pace@wco.com) Received: from shell.wco.com (root@shell.wco.com [199.4.94.16]) by mailq1.ncal.verio.com (8.8.7/8.8.7) with ESMTP id OAA10377 for ; Sun, 7 Jun 1998 14:26:33 -0700 (PDT) Received: from shell (pace@shell [199.4.94.16]) by shell.wco.com (8.8.5/8.8.5/WCO-18jul97) with SMTP id OAA10790 for ; Sun, 7 Jun 1998 14:26:32 -0700 (PDT) Date: Sun, 7 Jun 1998 14:26:30 -0700 (PDT) From: James Pace X-Sender: pace@shell Reply-To: James Pace cc: freebsd-stable@FreeBSD.ORG Subject: config broken? In-Reply-To: Message-ID: X-Url: http://www.pobox.com/~jepace X-Pgp-Fingerprint: 8C E7 12 5A 3A 8C 5C 4D EC 15 7B 65 EA 82 D2 BF X-Pgp-Keyid: A49EA4D9 X-Files: All Lies Lead To The Truth MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just rebuilt config, and now I'm getting: unknown option "COMPAT_43" unknown option "MSDOSFS" unknown option "NFS" unknown option "FFS" unknown option "INET" Help! Thanks, James This letter brought to you by: ************************************* ** James E. Pace ** ** http://www.pobox.com/~jepace ** ******************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 8 04:13:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA20207 for freebsd-stable-outgoing; Mon, 8 Jun 1998 04:13:56 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from conductor.synapse.net (conductor.synapse.net [199.84.54.18]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA20154 for ; Mon, 8 Jun 1998 04:13:45 -0700 (PDT) (envelope-from evanc@synapse.net) Received: (qmail 15845 invoked from network); 8 Jun 1998 11:13:45 -0000 Received: from localhost (HELO cello) (127.0.0.1) by localhost with SMTP; 8 Jun 1998 11:13:45 -0000 Message-ID: <00b101bd92ce$88052a00$c9252fce@cello.synapse.net> From: "Evan Champion" To: Subject: stable config broken? Date: Mon, 8 Jun 1998 07:13:57 -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 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsup'd last night and after make world, config appears to be broken: # config GENERIC GENERIC:119: unknown option "APM_BROKEN_STATCLOCK" GENERIC:35: unknown option "FAILSAFE" GENERIC:31: unknown option "COMPAT_43" GENERIC:28: unknown option "MSDOSFS" GENERIC:27: unknown option "NFS" GENERIC:26: unknown option "FFS" GENERIC:25: unknown option "INET" Kernel build directory is ../../compile/GENERIC Evan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 8 05:48:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA05253 for freebsd-stable-outgoing; Mon, 8 Jun 1998 05:48:14 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA05188 for ; Mon, 8 Jun 1998 05:48:08 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id MAA15218; Mon, 8 Jun 1998 12:48:05 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id OAA06971; Mon, 8 Jun 1998 14:47:34 +0200 (MET DST) Message-ID: <19980608144734.58881@follo.net> Date: Mon, 8 Jun 1998 14:47:34 +0200 From: Eivind Eklund To: Evan Champion , freebsd-stable@FreeBSD.ORG Subject: Re: stable config broken? References: <00b101bd92ce$88052a00$c9252fce@cello.synapse.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <00b101bd92ce$88052a00$c9252fce@cello.synapse.net>; from Evan Champion on Mon, Jun 08, 1998 at 07:13:57AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jun 08, 1998 at 07:13:57AM -0400, Evan Champion wrote: > I cvsup'd last night and after make world, config appears to be broken: > > # config GENERIC > GENERIC:119: unknown option "APM_BROKEN_STATCLOCK" > GENERIC:35: unknown option "FAILSAFE" > GENERIC:31: unknown option "COMPAT_43" > GENERIC:28: unknown option "MSDOSFS" > GENERIC:27: unknown option "NFS" > GENERIC:26: unknown option "FFS" > GENERIC:25: unknown option "INET" > Kernel build directory is ../../compile/GENERIC This is not dangerous - it is just warning messages (which should be considered as scary in -current, but not in -stable - not all options have been made 'known' in -stable). The merge that introduced them has been backed out, so they will be gone after your next cvsup. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 8 08:14:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29932 for freebsd-stable-outgoing; Mon, 8 Jun 1998 08:14:51 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gateman.zeus.leitch.com (gateman.zeus.leitch.com [204.187.61.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29515 for ; Mon, 8 Jun 1998 08:13:30 -0700 (PDT) (envelope-from woods@tap.zeus.leitch.com) Received: from zeus.leitch.com (tap.zeus.leitch.com [204.187.61.10]) by gateman.zeus.leitch.com (8.8.5/8.7.3/1.0) with ESMTP id LAA29109 for ; Mon, 8 Jun 1998 11:12:51 -0400 (EDT) Received: from brain.zeus.leitch.com (brain.zeus.leitch.com [204.187.61.32]) by zeus.leitch.com (8.7.5/8.7.3/1.0) with ESMTP id LAA20144 for ; Mon, 8 Jun 1998 11:12:55 -0400 (EDT) Received: (from woods@localhost) by brain.zeus.leitch.com (8.8.8/8.8.8) id LAA16030; Mon, 8 Jun 1998 11:12:55 -0400 (EDT) (envelope-from woods@tap.zeus.leitch.com) Date: Mon, 8 Jun 1998 11:12:55 -0400 (EDT) Message-Id: <199806081512.LAA16030@brain.zeus.leitch.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: woods@zeus.leitch.com (Greg A. Woods) To: freebsd-stable@FreeBSD.ORG Subject: Re: Matt Behrens: Re: kernel compile problem In-Reply-To: Richard Wackerbarth's message of "Fri, June 5, 1998 20:24:18 -0500" regarding "Re: Matt Behrens: Re: kernel compile problem" id References: <199806052348.JAA10962@gsms01.alcatel.com.au> X-Mailer: VM 6.45 under Emacs 20.2.1 Reply-To: freebsd-stable@FreeBSD.ORG Organization: Planix, Inc.; Toronto, Ontario; Canada Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Fri, June 5, 1998 at 20:24:18 (-0500), Richard Wackerbarth wrote: ] > Subject: Re: Matt Behrens: Re: kernel compile problem > > At 6:48 PM -0500 6/5/98, Peter Jeremy wrote: > >On Fri, 05 Jun 1998 06:42:00 -0500, Richard Wackerbarth > >wrote: > >> That brings us back to the question of "Why?". Should the 2.2 branch > >>have been changed now? Perhaps this aspect should have been frozen until > >>we are preparing for a 2.2.7 release. > > > >I think this is backwards. These sort of changes should be made well > >in advance of any proposed release so that they can be adequately > >tested (and backed out if serious problems arise). Putting `major' > >changes in just before a release is almost always a bad idea. > > It this case, I disagree. First, this is the "stable" branch. > We are not supposed to be "debugging" features here. Perhaps you're confusing "stable" and "release". I think all Peter was trying to say was that if changes are to be introduced to the RELENG_2_2 branch then they should be introduced as soon as possible so that they can be "debugged". I agree that this is especially important for "major" changes, no matter how well tested and "stable" they may be in the -current branch. > Unlike "current", users should expect to be able to build from it > at all times. By introducing changes to the kernel which require a > change to the config tool, the building of kernels is broken for > users who do not have the full source and manually overcome the > dependancy that is not handled automatically for them. That's definitely not the impression I had. I expect the live branch to be exactly that, a *live* branch with ongoing changes and corrections. I do expect the *releases* from the RELENG_2_2 branch to be 100% stable though. The handbook is, of course, a little vague on this matter: FreeBSD-stable is our development branch for a more low-key and conservative set of changes intended for our next mainstream release. Changes of an experimental or untested nature do not go into this branch However as someone quite familiar with CVS development techniques, and also given the nature of any software change, I can assure you that planning a stable product release is an entirely different matter than simply trying to work on a development branch where only the most conservative and well tested (on other branches) changes are introduced. As a matter of fact I'd like to see release branches fork off from each development branch simply so that there's no conflict between the "release" activities and ongoing "development". However since I don't actually have anything to do with the FreeBSD repository, and esp. not with the release process, except as a user, well, I guess what I'd like to see doesn't really matter all that much. > If we wait until just before a new release, the window whereby > they cannot build is reduced since they will get the new binary of > the config tool soon. That's a really bogus argument. -- Greg A. Woods +1 416 443-1734 VE3TCP Planix, Inc. ; Secrets of the Weird To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 8 08:35:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03123 for freebsd-stable-outgoing; Mon, 8 Jun 1998 08:35:48 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gateman.zeus.leitch.com (gateman.zeus.leitch.com [204.187.61.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03105 for ; Mon, 8 Jun 1998 08:35:34 -0700 (PDT) (envelope-from woods@tap.zeus.leitch.com) Received: from zeus.leitch.com (tap.zeus.leitch.com [204.187.61.10]) by gateman.zeus.leitch.com (8.8.5/8.7.3/1.0) with ESMTP id LAA29234 for ; Mon, 8 Jun 1998 11:34:57 -0400 (EDT) Received: from brain.zeus.leitch.com (brain.zeus.leitch.com [204.187.61.32]) by zeus.leitch.com (8.7.5/8.7.3/1.0) with ESMTP id LAA20247 for ; Mon, 8 Jun 1998 11:35:00 -0400 (EDT) Received: (from woods@localhost) by brain.zeus.leitch.com (8.8.8/8.8.8) id LAA16073; Mon, 8 Jun 1998 11:35:00 -0400 (EDT) (envelope-from woods@tap.zeus.leitch.com) Date: Mon, 8 Jun 1998 11:35:00 -0400 (EDT) Message-Id: <199806081535.LAA16073@brain.zeus.leitch.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: woods@zeus.leitch.com (Greg A. Woods) To: freebsd-stable@FreeBSD.ORG Subject: Re: cvsuping the cvs tree In-Reply-To: Robert Watson's message of "Sun, June 7, 1998 10:13:26 -0400" regarding "cvsuping the cvs tree" id References: X-Mailer: VM 6.45 under Emacs 20.2.1 Reply-To: freebsd-stable@FreeBSD.ORG Organization: Planix, Inc.; Toronto, Ontario; Canada Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Sun, June 7, 1998 at 10:13:26 (-0400), Robert Watson wrote: ] > Subject: cvsuping the cvs tree > > I'm about to begin a fairly substantial set of changes to a -stable kernel > to introduce authentication/authorization token handling support. > However, I would like to continue tracking the -stable branch to catch bug > fixes, new features, etc as they become available. Ideally, I'd also like > to use the merge support in CVS to do this. What is the best way to do > this on my local machine? Is anon CVS access sufficient to do cvs updates > and checkouts, etc, for the merging? Can cvsup do this without zapping my > source changes? :-) The only really sure way to do this is to use the CVS vendor-branch suppprt. You'll need to create a local CVS repository. Into that you should import "releases" of FreeBSD. From there you can check out a working directory and introduce your changes to that local copy. From then on when you import new FreeBSD releases CVS will be able to assist you in merging your changes with the new release code. You cannot do this with the CVSup'ed repository alone, at least not if you ever want to check in your own changes. The only thing the CVSup'ed repo is really good for is looking at log messages and diffs, and for 'cvs export'ing your own local copy. There are a couple of tricks here, of course. The first trick is in defining what "releases" are for your purposes. You could simply revert to using only official CVS releases and giving up on daily tracking of -stable. Or you could go as far as to do a daily 'cvs export' from the FreeBSD repository and 'cvs import' the result daily to your local repository. To date we've usually tried to pick points on the -stable branch that either appear to be really stable, or correspond closely to that point just after a true release when the release's most apparent bugs are fixed. The second trick is that "cvs import" will not "cvs remove" files that have been removed in the source release. You must do this yourself. It's not hard but it requires finding that list of removed files and running "cvs rm" and "cvs commit" with it (after confirming that there are no conflicts resulting from your own local changes). I have a simple script under development that does the mechanics of this for you. Send me e-mail if you would like to try a copy. Of course this whole process requires a fair bit of disk space. If you want to make your own "releases" of your locally hacked code (eg. to build a CD or to do installs from), then you'll need even more disk space. We currently have almost 2GB used in our /cvs (with both the CVSup'ed repositories, and our local copy, plus a spare backup copy), and have used up to 4GB doing builds and releases at any one time. You may also want several machines to do the actual builds and run tests on. -- Greg A. Woods +1 416 443-1734 VE3TCP Planix, Inc. ; Secrets of the Weird To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 8 15:17:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21181 for freebsd-stable-outgoing; Mon, 8 Jun 1998 15:17:01 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from csmd2.cs.uni-magdeburg.de (csmd2.cs.uni-magdeburg.de [141.44.22.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21154 for ; Mon, 8 Jun 1998 15:16:50 -0700 (PDT) (envelope-from jesse@prinz-atm.cs.Uni-Magdeburg.DE) Received: from pflaume.cs.uni-magdeburg.de (pflaume-atm [141.44.30.44]) by csmd2.cs.uni-magdeburg.de (8.8.8/8.8.8) with SMTP id AAA00747 for ; Tue, 9 Jun 1998 00:15:03 +0200 (MET DST) Received: by pflaume.cs.uni-magdeburg.de (SMI-8.6/SMI-SVR4) id AAA01480; Tue, 9 Jun 1998 00:15:02 +0200 Date: Tue, 9 Jun 1998 00:15:02 +0200 From: jesse@prinz-atm.cs.Uni-Magdeburg.DE (Roland Jesse) Message-Id: <199806082215.AAA01480@pflaume.cs.uni-magdeburg.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-stable@FreeBSD.ORG Subject: make in kdebase-4.1b port fails In-Reply-To: <199806080037.CAA28322@pflaume.cs.uni-magdeburg.de> References: <199806080037.CAA28322@pflaume.cs.uni-magdeburg.de> X-Mailer: VM 6.32 under Emacs 19.34.1 Reply-To: jesse@prinz-atm.cs.Uni-Magdeburg.DE X-Organization: University of Magdeburg X-Pgp-Fingerprint: 5D 08 5A E3 B4 AA 68 C1 FF 67 06 29 62 DD 9A D7 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I mailed the problem to the ports list before and got a reponse stating that there does not seem to be a problem building kdebase-4.1b on a FreeBSD-current system. Did anybody else run into the trouble outlined below and has an idea on how to solve it? Any hints are greatly appreciated. > # uname -sr > FreeBSD 2.2-STABLE > # cd /usr/ports/x11/kdebase > # make > >> Checksum OK for kdebase-beta4-1.src.tar.bz2. > ===> Extracting for kdebase-4.1b > ===> kdebase-4.1b depends on executable: bzip2 - found > ===> kdebase-4.1b depends on executable: moc - found > ===> kdebase-4.1b depends on shared library: qt\.1\.3[1-9] - found > ===> kdebase-4.1b depends on shared library: gif\.[23]\. - found > ===> kdebase-4.1b depends on shared library: jpeg\.9\. - found > ===> kdebase-4.1b depends on shared library: kdecore\.0\.9[0-9] - found > ===> kdebase-4.1b depends on shared library: kdeui\.0\.9[1-9] - found > ===> kdebase-4.1b depends on shared library: jscript\.0\.9[0-9] - found > ===> kdebase-4.1b depends on shared library: khtmlw\.0\.9[1-9] - found > ===> kdebase-4.1b depends on shared library: kfm\.0\.9[0-9] - found > ===> kdebase-4.1b depends on shared library: mediatool\.0\.[6-9] - found > ===> Patching for kdebase-4.1b > ===> Applying FreeBSD patches for kdebase-4.1b > 1 out of 1 hunks failed--saving rejects to kcontrol/Makefile.in.rej > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. Roland -- "Sorry, did I say something wrong? Pardon me for breathing, which I never do anyways so I don't know why I even bothered to say it... Oh God I'm soooo depressed." (Marvin) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 8 15:19:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21819 for freebsd-stable-outgoing; Mon, 8 Jun 1998 15:19:43 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21712 for ; Mon, 8 Jun 1998 15:19:27 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [208.2.87.10] (user10.dataplex.net [208.2.87.10]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id RAA09210; Mon, 8 Jun 1998 17:19:22 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <199806081512.LAA16030@brain.zeus.leitch.com> References: Richard Wackerbarth's message of "Fri, June 5, 1998 20:24:18 -0500" regarding "Re: Matt Behrens: Re: kernel compile problem" id <199806052348.JAA10962@gsms01.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 8 Jun 1998 17:18:21 -0500 To: freebsd-stable@FreeBSD.ORG From: Richard Wackerbarth Subject: Re: Matt Behrens: Re: kernel compile problem Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:12 AM -0500 6/8/98, Greg A. Woods wrote: >As a matter of fact I'd like to see release branches fork off from each >development branch simply so that there's no conflict between the >"release" activities and ongoing "development". However since I don't >actually have anything to do with the FreeBSD repository, and esp. not >with the release process, except as a user, well, I guess what I'd like >to see doesn't really matter all that much. > >> If we wait until just before a new release, the window whereby >> they cannot build is reduced since they will get the new binary of >> the config tool soon. > >That's a really bogus argument. The fundamental problem is that there are not enough "branches". As a result, the RELENG_2_2 branch is having to serve as both the development branch for 2.2.7 and the patch branch for 2.2.6. For the former purpose, ASAP is a good strategy. For the latter, any change to the tools destroys the ability of a user to apply patches to his kernel. I don't think that the "kernel only" source users would consider my argument at all bogus. For them, the 2.2 branch is BROKEN. They cannot apply the latest security updates which affect the kernel until 2.2.7 is released. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 8 16:18:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03235 for freebsd-stable-outgoing; Mon, 8 Jun 1998 16:18:10 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.deflux.org (root@squirrel.deflux.org [209.73.243.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03109 for ; Mon, 8 Jun 1998 16:17:26 -0700 (PDT) (envelope-from caleb@deflux.org) From: caleb@deflux.org Received: from squirrel.deflux.org (IDENT:caleb@localhost.fasthost.net [127.0.0.1]) by mail.deflux.org (8.9.0/8.9.0) with SMTP id TAA01004; Mon, 8 Jun 1998 19:13:57 -0400 (EDT) Date: Mon, 8 Jun 1998 19:13:36 -0400 (EDT) To: Evan Champion cc: freebsd-stable@FreeBSD.ORG Subject: Re: stable config broken? In-Reply-To: <00b101bd92ce$88052a00$c9252fce@cello.synapse.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 cvsup again..its fixed. On Mon, 8 Jun 1998, Evan Champion wrote: > I cvsup'd last night and after make world, config appears to be broken: > > # config GENERIC > GENERIC:119: unknown option "APM_BROKEN_STATCLOCK" > GENERIC:35: unknown option "FAILSAFE" > GENERIC:31: unknown option "COMPAT_43" > GENERIC:28: unknown option "MSDOSFS" > GENERIC:27: unknown option "NFS" > GENERIC:26: unknown option "FFS" > GENERIC:25: unknown option "INET" > Kernel build directory is ../../compile/GENERIC > > Evan > > > > 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 Jun 8 18:01:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA17070 for freebsd-stable-outgoing; Mon, 8 Jun 1998 18:01:19 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16966 for ; Mon, 8 Jun 1998 18:00:42 -0700 (PDT) (envelope-from gnb@bby.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id LAA03407; Tue, 9 Jun 1998 11:00:38 +1000 (EST) Received: from melba.bby.com.au(192.43.186.1) via SMTP by fw.bby.com.au, id smtpd003405; Tue Jun 9 01:00:31 1998 Received: from lightning (lightning.bby.com.au [192.43.186.20]) by melba.bby.com.au (8.8.2/8.8.2) with ESMTP id LAA04651; Tue, 9 Jun 1998 11:00:30 +1000 (EST) Message-Id: <199806090100.LAA04651@melba.bby.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: "Michael V. Harding" Cc: rkw@dataplex.net, witr@rwwa.com, hetzels@westbend.net, stable@FreeBSD.ORG Subject: Re: Where to start CTM with 2.2.6-RELEASE CD? In-reply-to: Your message of Wed, 03 Jun 1998 07:32:58 -0700. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 09 Jun 1998 11:00:28 +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks to all who responded. I was looking at CTM because I am behind a firewall on a 28k link on the other side of the Pacific. I know ftp works through the FW. However a quick peruse of the cvsup man page pointed out the "-P m" option and I was able to configure both cvsup and the firewall to allow me access to the cvsup.freebsd.org repository. I now have up-to-date kernel source (uncompilable because I have an old config(8) - more cvsup needed.) Greg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 8 21:18:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22806 for freebsd-stable-outgoing; Mon, 8 Jun 1998 21:18:04 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from amor.wcs.uq.edu.au (amor.wcs.uq.edu.au [130.102.222.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22705 for ; Mon, 8 Jun 1998 21:17:56 -0700 (PDT) (envelope-from garyr@amor.wcs.uq.edu.au) Received: (from garyr@localhost) by amor.wcs.uq.edu.au (8.8.8/8.8.8) id OAA01476; Tue, 9 Jun 1998 14:16:18 +1000 (EST) (envelope-from garyr) From: Gary Roberts Message-Id: <199806090416.OAA01476@amor.wcs.uq.edu.au> Subject: Re: stable config broken? In-Reply-To: <19980608144734.58881@follo.net> from Eivind Eklund at "Jun 8, 98 02:47:34 pm" To: eivind@yes.no (Eivind Eklund) Date: Tue, 9 Jun 1998 14:16:18 +1000 (EST) Cc: freebsd-stable@FreeBSD.ORG Organisation: Well Control Australia Phone: +617 3844 0400 Fax: +617 3844 0444 Reply-To: garyr@wcs.uq.edu.au (Gary Roberts) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eivind Eklund writes :- > > GENERIC:31: unknown option "COMPAT_43" > > GENERIC:28: unknown option "MSDOSFS" > > GENERIC:27: unknown option "NFS" > > GENERIC:26: unknown option "FFS" > > GENERIC:25: unknown option "INET" > > This is not dangerous - it is just warning messages (which should be > considered as scary in -current, but not in -stable - not all options > have been made 'known' in -stable). Is it really true that all these options that we've known and loved for years are truly deprecated?? They used to be `known' or were we just fooling ourselves?? Is this documented anywhere? For instance, quoting from the current LINT (2.2.6-RELEASE) # One of these is mandatory: options FFS #Fast filesystem options NFS #Network File System How can you describe them as not `known'?? Cheers, -- Gary Roberts (garyr@wcs.uq.edu.au) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 8 21:20:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA23454 for freebsd-stable-outgoing; Mon, 8 Jun 1998 21:20:41 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA23309 for ; Mon, 8 Jun 1998 21:20:12 -0700 (PDT) (envelope-from gnb@bby.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id OAA05040 for ; Tue, 9 Jun 1998 14:20:09 +1000 (EST) Received: from melba.bby.com.au(192.43.186.1) via SMTP by fw.bby.com.au, id smtpd005037; Tue Jun 9 04:20:06 1998 Received: from lightning (lightning.bby.com.au [192.43.186.20]) by melba.bby.com.au (8.8.2/8.8.2) with ESMTP id OAA10693 for ; Tue, 9 Jun 1998 14:20:05 +1000 (EST) Message-Id: <199806090420.OAA10693@melba.bby.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: stable@FreeBSD.ORG Subject: [Summary] Re: PPP on a dialback port? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 09 Jun 1998 14:20:00 +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: > Has anyone got a script they can send me that does ppp (kernel or user > mode) via a dialback modem connection? Thanks for various suggestions. This turned out to be much easier than I had dared dream. Summary: - read the Handbook for PPP overview stuff - read the ppp/pppd man page for how to use the chat program to do the dialing - read the chat man page, paying attention to the "HANGUP OFF" command, which even has an example for doing dialback. Greg, Now online. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 8 21:57:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA00543 for freebsd-stable-outgoing; Mon, 8 Jun 1998 21:57:07 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from titus.stade.co.uk (root@stade.demon.co.uk [158.152.29.164]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA00531 for ; Mon, 8 Jun 1998 21:56:45 -0700 (PDT) (envelope-from aw1@titus.stade.co.uk) Received: (from aw1@localhost) by titus.stade.co.uk (8.8.8/8.8.3) id EAA14126; Tue, 9 Jun 1998 04:06:50 +0100 (BST) Message-ID: <19980609040650.A12371@stade.co.uk> Date: Tue, 9 Jun 1998 04:06:50 +0100 From: Adrian Wontroba To: freebsd-stable@FreeBSD.ORG Subject: Re: make in kdebase-4.1b port fails Reply-To: aw1@stade.co.uk Mail-Followup-To: freebsd-stable@freebsd.org References: <199806080037.CAA28322@pflaume.cs.uni-magdeburg.de> <199806082215.AAA01480@pflaume.cs.uni-magdeburg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199806082215.AAA01480@pflaume.cs.uni-magdeburg.de>; from Roland Jesse on Tue, Jun 09, 1998 at 12:15:02AM +0200 Organization: Stade Computers Ltd, UK X-Phone: +(44) 121 681 6677 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 09, 1998 at 12:15:02AM +0200, Roland Jesse wrote: > I mailed the problem to the ports list before and got a reponse > stating that there does not seem to be a problem building kdebase-4.1b > on a FreeBSD-current system. I've had various problems in building the kde ports on a -stable system, which tend to go away if you pkg_delete -f all the kde components and everything they are directly dependant upon. However, this ... > > ===> Patching for kdebase-4.1b > > ===> Applying FreeBSD patches for kdebase-4.1b > > 1 out of 1 hunks failed--saving rejects to kcontrol/Makefile.in.rej > > *** Error code 1 ... smacks of your having a mismatched or out of date patch file collection. Here, patch-aj is the only one which changes any Makefile - and that is kdm/pics/Makefile.in. Try blowing away /usr/ports/x11/kdebase and recreating it (CVS or whatever). If this is any help, here are the patches for kdebase here, and it does patch OK. -rw-r--r-- 1 root wheel 541 Apr 26 09:15 /usr/ports/x11/kdebase/patches/patch-a0 -rw-r--r-- 1 root wheel 842 Apr 25 08:32 /usr/ports/x11/kdebase/patches/patch-aa -rw-r--r-- 1 root wheel 224 Apr 26 09:15 /usr/ports/x11/kdebase/patches/patch-ah -rw-r--r-- 1 root wheel 624 Mar 4 23:46 /usr/ports/x11/kdebase/patches/patch-ai -rw-r--r-- 1 root wheel 3284 Mar 4 23:33 /usr/ports/x11/kdebase/patches/patch-aj -rw-r--r-- 1 root wheel 246 Mar 4 23:33 /usr/ports/x11/kdebase/patches/patch-ak -rw-r--r-- 1 root wheel 2346 Mar 4 23:50 /usr/ports/x11/kdebase/patches/patch-al -rw-r--r-- 1 root wheel 446 Mar 4 23:34 /usr/ports/x11/kdebase/patches/patch-am -- Adrian Wontroba, Stade Computers Limited. phone: (+44) 121 681 6677 Mail info@accu.org for information about the Association of C and C++ Users or see To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 00:31:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18353 for freebsd-stable-outgoing; Tue, 9 Jun 1998 00:31:44 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18347 for ; Tue, 9 Jun 1998 00:31:34 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id RAA28501 for ; Tue, 9 Jun 1998 17:01:32 +0930 (CST) Message-Id: <199806090731.RAA28501@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: freebsd-stable@FreeBSD.ORG Subject: Can't compile -stable Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 09 Jun 1998 17:01:32 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am trying to do a buildworld on my -current machine to make a -stable system for another machine, but it breaks :( I did cd /remote1 cvs -d /usr/CVS-Repository co src cd src make buildworld MAKEOBJDIRPREFIX=/remote1 |& tee build.log The error I get is -> cc -nostdinc -O -DIPL_NAME=\"/dev/ipl\" -I- -I/remote1/obj/local1/src/usr.sbin/i pftest -I/local1/src/usr.sbin/ipftest/../../sys/netinet -I/local1/src/usr.sbin/i pftest/../../sys -I/local1/src/usr.sbin/ipftest/../../contrib/ipfilter -I/remo te1/obj/remote1/src/tmp/usr/include -c /local1/src/usr.sbin/ipftest/../../sys/ne tinet/ip_fil.c /local1/src/usr.sbin/ipftest/../../sys/netinet/ip_fil.c: In function `iplioctl': /local1/src/usr.sbin/ipftest/../../sys/netinet/ip_fil.c:353: argument `cmd' does n't match prototype /local1/src/usr.sbin/ipftest/../../sys/netinet/ip_fil.h:386: prototype declarati on *** Error code 1 Stop. Hmm.. having a look, I think the check for __FreeBSD_version >= 300003 might do some bad things (in ip_fil.h), but I don't know.. Of course I am assuming I can make a 2.2-stable from a 3.0-current :) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 05:29:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA03454 for freebsd-stable-outgoing; Tue, 9 Jun 1998 05:29:52 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.ukconnect.net (mail.ukconnect.net [195.219.13.4]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA03410 for ; Tue, 9 Jun 1998 05:29:40 -0700 (PDT) (envelope-from phil@virtek.com) Received: from wire1.ukconnect.net (wire1.ukconnect.net [195.219.13.179]) by mail.virtek.com (NTMail 3.03.0014/1.aa3h) with ESMTP id ba008269 for ; Tue, 9 Jun 1998 12:03:38 +0100 Message-Id: <3.0.3.32.19980609102008.01312100@mail.virtek.com> X-Sender: phil@mail.virtek.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Tue, 09 Jun 1998 10:20:08 +0100 To: freebsd-stable@FreeBSD.ORG From: Phil Allsopp Subject: Multitech ISDN Card Srivers 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 reliably informed that there are drivers available for the Multitech ISDN cards under Free BSD 2.2.5 Does anyone know where I could obtain such drivers ? Regards Phil To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 05:32:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA04229 for freebsd-stable-outgoing; Tue, 9 Jun 1998 05:32:09 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA04189 for ; Tue, 9 Jun 1998 05:32:01 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id MAA05983; Tue, 9 Jun 1998 12:08:15 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id OAA19488; Tue, 9 Jun 1998 14:07:35 +0200 (MET DST) Message-ID: <19980609140734.08169@follo.net> Date: Tue, 9 Jun 1998 14:07:34 +0200 From: Eivind Eklund To: "Daniel O'Connor" , freebsd-stable@FreeBSD.ORG Subject: Re: Can't compile -stable References: <199806090731.RAA28501@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199806090731.RAA28501@cain.gsoft.com.au>; from Daniel O'Connor on Tue, Jun 09, 1998 at 05:01:32PM +0930 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 09, 1998 at 05:01:32PM +0930, Daniel O'Connor wrote: > Hi, > I am trying to do a buildworld on my -current machine to make a -stable system > for another machine, but it breaks :( > > I did > > cd /remote1 > cvs -d /usr/CVS-Repository co src > cd src > make buildworld MAKEOBJDIRPREFIX=/remote1 |& tee build.log There is something seriously wrong here. Are you attempting to build -current on a -stable machine? The above sequence of commands check out -current... Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 05:33:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA04739 for freebsd-stable-outgoing; Tue, 9 Jun 1998 05:33:18 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from nohow.demon.co.uk (nohow.lib.surrey.ac.uk [131.227.178.102]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA04665 for ; Tue, 9 Jun 1998 05:33:11 -0700 (PDT) (envelope-from jose@nobody.org) Received: from localhost (jose@localhost) by nohow.demon.co.uk (8.8.8/8.8.8) with SMTP id NAA03474; Tue, 9 Jun 1998 13:31:09 +0100 (BST) (envelope-from jose@nohow.demon.co.uk) Date: Tue, 9 Jun 1998 13:31:09 +0100 (BST) From: Jose Marques To: Gary Kline cc: freebsd-stable@FreeBSD.ORG Subject: Re: X11 problem? In-Reply-To: <199806071857.LAA13533@athena.tera.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, 7 Jun 1998, Gary Kline wrote: [Snip] > I've already ordered ``Jordan's Pick'', the Matrox > Millennium---figured that three years is worth a card > upgrade. Maybe the Matrox with 4M will let me go > to 1280x1024. I use a MMII with 8MB. Generally very nice with XFree86 3.3.2. However, once in a while it will lock up the machine when starting. I don't know if this is a widespread problem - I've seen one other report on the news group. > For now, one step closer to being done upgrading. > > gary -- Jose Marques To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 05:33:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA04799 for freebsd-stable-outgoing; Tue, 9 Jun 1998 05:33:24 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA04726 for ; Tue, 9 Jun 1998 05:33:17 -0700 (PDT) (envelope-from erakupa@kk.etx.ericsson.se) Received: from kkb3 (kkb3.kk.etx.ericsson.se [130.100.97.23]) by penguin.wise.edt.ericsson.se (8.9.0/8.7.3/glacier-0.9) with SMTP id OAA25850 for ; Tue, 9 Jun 1998 14:33:13 +0200 (MET DST) Received: from kk662.kk.etx.ericsson.se by kkb3 (SMI-8.6/LME-2.2.6) id OAA01211; Tue, 9 Jun 1998 14:33:10 +0200 From: erakupa@kk.etx.ericsson.se (ETX-B-SL Martti Kuparinen) Received: by kk662.kk.etx.ericsson.se (SMI-8.6/client-1.6) id OAA13371; Tue, 9 Jun 1998 14:33:11 +0200 Date: Tue, 9 Jun 1998 14:33:11 +0200 Message-Id: <199806091233.OAA13371@kk662.kk.etx.ericsson.se> To: stable@FreeBSD.ORG Subject: Missing security advisories in ERRATA X-Sun-Charset: US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why the 2.2.6-RELEASE ERRATA says Current active security advisories for 2.2.6: None while there are active advisories (FreeBSD-SA-98:03 - FreeBSD-SA-98:05) which affect 2.2.6-RELEASE? Martti To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 06:25:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19063 for freebsd-stable-outgoing; Tue, 9 Jun 1998 06:25:10 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19049 for ; Tue, 9 Jun 1998 06:25:05 -0700 (PDT) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id JAA18891 for ; Tue, 9 Jun 1998 09:19:05 -0400 (EDT) Date: Tue, 9 Jun 1998 09:25:02 -0400 (EDT) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: freebsd-stable@FreeBSD.ORG Subject: npx0 problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a clients box that is doing the oddest thing. It has a kernel I built right after i installed 2.2.6 on this machine with npx0 being used no emulation. It is a 486-DX 50. CPU: i486 DX2 (486-class CPU) Origin = "GenuineIntel" Id = 0x435 Stepping=5 Features=0x3 npx0 flags 0x1 on motherboard npx0: INT 16 interface Here is the kernel config im TRYING to get to work. machine "i386" cpu "I486_CPU" ident PREMAC maxusers 64 options MATH_EMULATE options INET #InterNETworking options FFS options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options BOUNCE_BUFFERS #include support for DMA bounce buffers options "AUTO_EOI_1" options "AUTO_EOI_2" config kernel root on wd0 dumps on wd0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xa0ffa0ff vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Mandatory, don't remove device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 vector edintr pseudo-device loop pseudo-device ether pseudo-device log pseudo-device sl 1 pseudo-device ppp 1 pseudo-device vn 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory. # options SYSVSHM The bizaare thing is that the only kernel I can get working is kernel.safe the kernel i custom built right after I installed this machine. All the other kernels I have attempted to install hang on npx0 on bootup. This is a remote machine and I have not verfied this with my own eyes. This is what the client says. So all im wondering is if anyone else running -stable has seen this at all? I have cvsuped 3 different times to see if it was just a problem with stable. No go. I have even made world. from newer stable sources. So if anyone has seen this let me know, so I dont think im crazy. Either that or the client is NOT booting off the kernels im rebuilding even though he says he is. Chris -- "Linux... The choice of a GNUtered generation." ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.6 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 06:54:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA26293 for freebsd-stable-outgoing; Tue, 9 Jun 1998 06:54:29 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA05211 for ; Tue, 9 Jun 1998 03:26:43 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id KAA27177; Tue, 9 Jun 1998 10:26:42 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id MAA18694; Tue, 9 Jun 1998 12:26:05 +0200 (MET DST) Message-ID: <19980609122605.33967@follo.net> Date: Tue, 9 Jun 1998 12:26:05 +0200 From: Eivind Eklund To: Gary Roberts Cc: freebsd-stable@FreeBSD.ORG Subject: Re: stable config broken? References: <19980608144734.58881@follo.net> <199806090416.OAA01476@amor.wcs.uq.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199806090416.OAA01476@amor.wcs.uq.edu.au>; from Gary Roberts on Tue, Jun 09, 1998 at 02:16:18PM +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 09, 1998 at 02:16:18PM +1000, Gary Roberts wrote: > Eivind Eklund writes :- > > > > GENERIC:31: unknown option "COMPAT_43" > > > GENERIC:28: unknown option "MSDOSFS" > > > GENERIC:27: unknown option "NFS" > > > GENERIC:26: unknown option "FFS" > > > GENERIC:25: unknown option "INET" > > > > This is not dangerous - it is just warning messages (which should be > > considered as scary in -current, but not in -stable - not all options > > have been made 'known' in -stable). > > Is it really true that all these options that we've known and loved for > years are truly deprecated?? They used to be `known' or were we just > fooling ourselves?? Is this documented anywhere? Note the use of quotes around `known', indicating that this is a special form. No, they're not deprecated. They have never been `known' as seen from config(8) - they aren't in src/sys/conf/options or src/sys/i386/conf/options.i386, so config(8) don't know about them. In -current, all options in GENERIC and LINT has been added to the options files (with a lot of related work). For that case, the above warning message makes sense there - all options _should_ be known to the config system. The behaviour of config in -current has also been changed - it no longer delete the compile directory. Thus when the warning come, you are not guaranteed a correct build. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 07:32:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05593 for freebsd-stable-outgoing; Tue, 9 Jun 1998 07:32:53 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cesit1.unifi.it (cesit1.unifi.it [150.217.1.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05572 for ; Tue, 9 Jun 1998 07:32:38 -0700 (PDT) (envelope-from ugo@dsi.UNIFI.IT) Received: from aguirre.dsi.unifi.it by CESIT1.UNIFI.IT (PMDF V5.1-10 #23168) with SMTP id <01IY1F5KG6TE0002KH@CESIT1.UNIFI.IT> for freebsd-stable@FreeBSD.ORG; Tue, 9 Jun 1998 16:32:39 MET Received: from dsi.unifi.it (com5.unifi.it) by aguirre.dsi.unifi.it (4.1/SMI-4.1) id AA09484; Tue, 09 Jun 1998 16:32:33 +0200 Received: from pegasus.home.net (pegasus.home.net [192.168.1.3]) by dsi.unifi.it (8.8.8/8.8.8) with ESMTP id PAA05714; Tue, 09 Jun 1998 15:07:29 +0200 (MET DST envelope-from ugo) Received: (from ugo@localhost) by pegasus.home.net (8.8.8/8.8.8) id PAA00286; Tue, 09 Jun 1998 15:07:12 +0200 (MET DST envelope-from ugo) Date: Tue, 09 Jun 1998 15:07:12 +0200 (MET DST) From: Ugo Paternostro Subject: Re: PnP support for if_ed, and more... In-reply-to: <199806060023.CAA12451@labinfo.iet.unipi.it> To: Luigi Rizzo Cc: freebsd-stable@FreeBSD.ORG, eivind@yes.no, mike@smith.net.au Message-id: Organization: Not an organization MIME-version: 1.0 X-Mailer: XFMail 1.2 [p0] on FreeBSD Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Priority: 3 (Normal) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Jun-98 Luigi Rizzo wrote about "Re: PnP support for if_ed, and more...": >> P.S.: still offering a bit of manpower to do the work... :-) Well, let's say > > so, if you have the time, look at pnpinfo sources to see how the PnP Reading (this too). > (and sorry for not writing in italian, but this also goes to the list :) Don't worry: I know that I could tamper you for any information on PnP, maybe privately. Hey, I could also come there to Pisa in about one hour... ;-) > Luigi Rizzo | Dip. di Ingegneria dell'Informazione Bye, UP To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 07:34:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05869 for freebsd-stable-outgoing; Tue, 9 Jun 1998 07:34:20 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cesit1.unifi.it (cesit1.unifi.it [150.217.1.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05630 for ; Tue, 9 Jun 1998 07:33:01 -0700 (PDT) (envelope-from ugo@dsi.UNIFI.IT) Received: from aguirre.dsi.unifi.it by CESIT1.UNIFI.IT (PMDF V5.1-10 #23168) with SMTP id <01IY1F60QNVG0002K6@CESIT1.UNIFI.IT> for freebsd-stable@FreeBSD.ORG; Tue, 9 Jun 1998 16:33:01 MET Received: from dsi.unifi.it (com5.unifi.it) by aguirre.dsi.unifi.it (4.1/SMI-4.1) id AA09490; Tue, 09 Jun 1998 16:32:52 +0200 Received: from pegasus.home.net (pegasus.home.net [192.168.1.3]) by dsi.unifi.it (8.8.8/8.8.8) with ESMTP id PAA05710; Tue, 09 Jun 1998 15:05:19 +0200 (MET DST envelope-from ugo) Received: (from ugo@localhost) by pegasus.home.net (8.8.8/8.8.8) id PAA00280; Tue, 09 Jun 1998 15:05:01 +0200 (MET DST envelope-from ugo) Date: Tue, 09 Jun 1998 15:05:01 +0200 (MET DST) From: Ugo Paternostro Subject: Re: PnP support for if_ed, and more... In-reply-to: <199806060121.SAA02536@dingo.cdrom.com> To: Mike Smith Cc: Luigi Rizzo , freebsd-stable@FreeBSD.ORG, eivind@yes.no (Eivind Eklund) Message-id: Organization: Not an organization MIME-version: 1.0 X-Mailer: XFMail 1.2 [p0] on FreeBSD Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Priority: 3 (Normal) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Jun-98 Mike Smith wrote about "Re: PnP support for if_ed, and more...": >> P.S.: still offering a bit of manpower to do the work... :-) Well, let's say > > Get the table from > http://www.microsoft.com/hwdev/download/respec/devids.txt Got. Reading. > and then work out a mechanism to scan the 'compatible device ID' > descriptors (0x1c) and pretend that the device is one of these if the > first pass (try for an exact match on the device ID) fails. Ok, I will look at those in the next weeks (I have an exam at the university in the meanwhile, you know, nothing seriuos... :-) > \\ Sometimes you're ahead, \\ Mike Smith Bye, UP To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 08:25:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17852 for freebsd-stable-outgoing; Tue, 9 Jun 1998 08:25:34 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gateman.zeus.leitch.com (gateman.zeus.leitch.com [204.187.61.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17842 for ; Tue, 9 Jun 1998 08:25:25 -0700 (PDT) (envelope-from woods@tap.zeus.leitch.com) Received: from zeus.leitch.com (tap.zeus.leitch.com [204.187.61.10]) by gateman.zeus.leitch.com (8.8.5/8.7.3/1.0) with ESMTP id LAA05711 for ; Tue, 9 Jun 1998 11:24:39 -0400 (EDT) Received: from brain.zeus.leitch.com (brain.zeus.leitch.com [204.187.61.32]) by zeus.leitch.com (8.7.5/8.7.3/1.0) with ESMTP id LAA25132 for ; Tue, 9 Jun 1998 11:24:45 -0400 (EDT) Received: (from woods@localhost) by brain.zeus.leitch.com (8.8.8/8.8.8) id LAA10150; Tue, 9 Jun 1998 11:24:45 -0400 (EDT) (envelope-from woods@tap.zeus.leitch.com) Date: Tue, 9 Jun 1998 11:24:45 -0400 (EDT) Message-Id: <199806091524.LAA10150@brain.zeus.leitch.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: woods@zeus.leitch.com (Greg A. Woods) To: freebsd-stable@FreeBSD.ORG Subject: Re: Matt Behrens: Re: kernel compile problem In-Reply-To: Richard Wackerbarth's message of "Mon, June 8, 1998 17:18:21 -0500" regarding "Re: Matt Behrens: Re: kernel compile problem" id References: <199806052348.JAA10962@gsms01.alcatel.com.au> <199806081512.LAA16030@brain.zeus.leitch.com> X-Mailer: VM 6.45 under Emacs 20.2.1 Reply-To: freebsd-stable@FreeBSD.ORG Organization: Planix, Inc.; Toronto, Ontario; Canada Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Mon, June 8, 1998 at 17:18:21 (-0500), Richard Wackerbarth wrote: ] > Subject: Re: Matt Behrens: Re: kernel compile problem > > The fundamental problem is that there are not enough "branches". As > a result, the RELENG_2_2 branch is having to serve as both the > development branch for 2.2.7 and the patch branch for 2.2.6. > For the former purpose, ASAP is a good strategy. For the latter, > any change to the tools destroys the ability of a user to > apply patches to his kernel. I agree that more branches might be better, but more branches require more management, and I'm not sure that would be better for a mostly volunteer project. I've found that when you try to do release branch management on top of other ongoing development branches you pretty well have to have one or more people dedicated to repository management and maintenance, and it really is a *full* time job. The "freeze development now and begin to prepare release directly on the branch" mechanism works well enough, esp. for a -stable branch where the *real* development does happen on a separate branch. > I don't think that the "kernel only" source users would consider > my argument at all bogus. For them, the 2.2 branch is BROKEN. They > cannot apply the latest security updates which affect the kernel > until 2.2.7 is released. It's only broken until it's fixed, and the sooner it's fixed, the better, as then more people will be able to test them. The obvious fix has been discussed, and it seems as if it will be implemented. It has proven extremely effective in NetBSD. (I.e. to include src/usr.sbin/config and its contents in the kernel-only source distrbution collections available through ftp, sup, CVSup, CTM, etc.) BTW, anyone seriously trying to keep right up to the minute with security fixes and such would be better off with user-land only than with kernel-only. People with so few resources should let other people manage the source tree and they should stick to releases only. Working with a live CVS repository (or even a daily copy of it) is bound to produce unpredictable results. Anyone crying wolf at the slightest perturbance will go hoarse and loose their voice long before they become too annoying. ;-) -- Greg A. Woods +1 416 443-1734 VE3TCP Planix, Inc. ; Secrets of the Weird To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 10:35:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18897 for freebsd-stable-outgoing; Tue, 9 Jun 1998 10:35:01 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from alcatel.fr (news2.alcatel.fr [194.133.58.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18855 for ; Tue, 9 Jun 1998 10:34:46 -0700 (PDT) (envelope-from THIERRY.HERBELOT@telspace.alcatel.fr) From: THIERRY.HERBELOT@telspace.alcatel.fr Received: from alcatel.fr (gatekeeper-ssn.alcatel.fr [155.132.180.244]) by mailgate.alcatel.fr (ALCANET/SMTP.9.9.9) with ESMTP id RAA27073; Tue, 9 Jun 1998 17:43:31 +0200 Received: from aifhs1.alcatel.fr (aifhs1.alcatel.fr [155.132.180.86]) by aifhs2.alcatel.fr (ALCANET/SMTP2) with ESMTP id RAA25400; Tue, 9 Jun 1998 17:32:41 +0200 (MET DST) Received: from aifhs2.alcatel.fr (localhost [127.0.0.1]) by aifhs1.alcatel.fr (8.8.8/8.8.8) with ESMTP id RAA22902; Tue, 9 Jun 1998 17:36:04 +0200 (MET DST) Received: from lune.telspace.alcatel.fr (lune.telspace.alcatel.fr [155.132.144.65]) by aifhs2.alcatel.fr (ALCANET/SMTP2) with ESMTP id RAA25040; Tue, 9 Jun 1998 17:31:43 +0200 (MET DST) Received: from telss1 (telss1.telspace.alcatel.fr [155.132.51.4]) by lune.telspace.alcatel.fr (8.7.6/8.7.3) with SMTP id RAA04412; Tue, 9 Jun 1998 17:35:46 +0200 (MET DST) Received: from telspace.alcatel.fr by telss1 (4.1/SMI-4.1) id AA06198; Tue, 9 Jun 98 17:25:03 +0200 Received: from localhost by telspace.alcatel.fr with SMTP (1.40.112.12/16.2) id AA262955619; Tue, 9 Jun 1998 17:20:19 +0200 X-Openmail-Hops: 1 Date: Tue, 9 Jun 98 17:20:05 +0200 Message-Id: In-Reply-To: Subject: =?ISO-8859-1?Q?R=E9p_:_npx0_problems?= Mime-Version: 1.0 To: opsys@mail.webspan.net Cc: freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset=US-ASCII; name="Texte" Content-Disposition: inline; filename="Texte" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG could you be more precise on the way your client's box fails to boot a new kernel ? TfH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 13:12:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23976 for freebsd-stable-outgoing; Tue, 9 Jun 1998 13:12:42 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from kosh.cococo.net (kosh.cococo.net [208.134.89.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23892 for ; Tue, 9 Jun 1998 13:12:25 -0700 (PDT) (envelope-from kosh@kosh.cococo.net) Received: from localhost (kosh@localhost) by kosh.cococo.net (8.8.7/8.8.7) with SMTP id QAA06365; Tue, 9 Jun 1998 16:13:15 -0400 Date: Tue, 9 Jun 1998 16:13:15 -0400 (EDT) From: "Kelley L." To: "Greg A. Woods" cc: freebsd-stable@FreeBSD.ORG Subject: Re: Matt Behrens: Re: kernel compile problem In-Reply-To: <199806091524.LAA10150@brain.zeus.leitch.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 9 Jun 1998, Greg A. Woods wrote: > [ On Mon, June 8, 1998 at 17:18:21 (-0500), Richard Wackerbarth wrote: ] > > Subject: Re: Matt Behrens: Re: kernel compile problem > > > I don't think that the "kernel only" source users would consider > > my argument at all bogus. For them, the 2.2 branch is BROKEN. They > > cannot apply the latest security updates which affect the kernel > > until 2.2.7 is released. > > It's only broken until it's fixed, and the sooner it's fixed, the > better, as then more people will be able to test them. > > The obvious fix has been discussed, and it seems as if it will be > implemented. It has proven extremely effective in NetBSD. (I.e. to > include src/usr.sbin/config and its contents in the kernel-only source > distrbution collections available through ftp, sup, CVSup, CTM, etc.) > > BTW, anyone seriously trying to keep right up to the minute with > security fixes and such would be better off with user-land only than > with kernel-only. People with so few resources should let other people > manage the source tree and they should stick to releases only. > I've recently come over from linux land, and I think FreeBSD is much more stable. The recent linux kernels in the 2.0.x series seem to be incorporating too many new features, and they are for my part much less stable than they were before. Which brings me to the question, how does one keep FreeBSD up to date and secure? Wrong question, mainly concerned with just keeping it secure. I use RedHat, and they have the updates to use to keep all the packages up to date with security fixes. Does anything similar exist in FreeBSD. I'm a little new, so I'm just not familiar with all the FreeBSDisms yet. I've been keeping up with the Stable, by cvsup'ing and then make buildworld and make installworld, then rebuilding the kernel and rebooting. About once a week. I gathered this was the way to keep fairly secure, is this not a correct assessment? > Working with a live CVS repository (or even a daily copy of it) is bound > to produce unpredictable results. Anyone crying wolf at the slightest > perturbance will go hoarse and loose their voice long before they become > too annoying. ;-) > Which is why I read the stable list, to read about any problems others are having, before I waste any where from 3 to 5 hours making the world only to find out it didn't. Of course I would rather buildworld break, since it doesn't affect anthing until installworld is run. later Kelley To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 13:41:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00724 for freebsd-stable-outgoing; Tue, 9 Jun 1998 13:41:36 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00690; Tue, 9 Jun 1998 13:41:20 -0700 (PDT) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199806092041.NAA00690@hub.freebsd.org> Subject: Re: Matt Behrens: Re: kernel compile problem In-Reply-To: from "Kelley L." at "Jun 9, 98 04:13:15 pm" To: kosh@kosh.cococo.net (Kelley L.) Date: Tue, 9 Jun 1998 13:41:19 -0700 (PDT) Cc: woods@zeus.leitch.com, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kelley L. wrote: > > Which brings me to the question, how does one keep FreeBSD up to date > and secure? Wrong question, mainly concerned with just keeping it secure. > I use RedHat, and they have the updates to use to keep all the packages up > to date with security fixes. Does anything similar exist in FreeBSD. I'm a > little new, so I'm just not familiar with all the FreeBSDisms yet. subscribe to freebsd-security-notifications. take the steps specified whenever a security notification is issued. subscribing to freebsd-security and reading the mail would be an additional step....that way you get early warning on items that will be addressed via a security notification. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 14:23:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07740 for freebsd-stable-outgoing; Tue, 9 Jun 1998 14:23:28 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from solar.os.com (root@solar.os.com [209.113.221.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07657 for ; Tue, 9 Jun 1998 14:23:07 -0700 (PDT) (envelope-from craigs@os.com) Received: from fargo (fargo.os.com [209.113.221.2]) by solar.os.com (8.7/8.7.0) with SMTP id RAA06150 for ; Tue, 9 Jun 1998 17:23:20 -0400 Message-ID: <00aa01bd93ec$a118bd80$02dd71d1@fargo.os.com> From: "Craig Shrimpton" To: Subject: Anyone know what this SCSI error is about? Date: Tue, 9 Jun 1998 17:21:55 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My stable system has been running great except for this incident. I have all Adaptec options enabled and the system is barely loaded. The machine ran for several months with no ahc options and no errors so I'm wondering if this is a software issue. Thanks, Craig The error: Jun 6 03:32:57 orion /kernel: sd0(ahc0:0:0): SCB 0x1 - timed out in dataout phase, SCSISIGI == 0xe6 Jun 6 03:33:22 orion /kernel: SEQADDR = 0x127 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x13 Jun 6 03:33:22 orion /kernel: Ordered Tag queued Jun 6 03:33:22 orion /kernel: sd0(ahc0:0:0): SCB 0x0 timedout while recovery in progress Jun 6 03:33:22 orion /kernel: sd0(ahc0:0:0): SCB 0x2 timedout while recovery in progress Jun 6 03:33:22 orion /kernel: sd0(ahc0:0:0): SCB 0x3 timedout while recovery in progress Jun 6 03:33:22 orion /kernel: sd0(ahc0:0:0): SCB 0x1 - timed out in dataout phase, SCSISIGI == 0xe6 Jun 6 03:33:22 orion /kernel: SEQADDR = 0x127 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x13 Jun 6 03:33:22 orion /kernel: sd0(ahc0:0:0): abort message in message buffer Jun 6 03:33:22 orion /kernel: sd0(ahc0:0:0): SCB 0x0 - timed out in dataout phase, SCSISIGI == 0xf6 Jun 6 03:33:22 orion /kernel: SEQADDR = 0x127 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x13 Jun 6 03:33:22 orion /kernel: sd0(ahc0:0:0): no longer in timeout Jun 6 03:33:23 orion /kernel: sd0(ahc0:0:0): no longer in timeout Jun 6 03:33:23 orion /kernel: ahc0: Issued Channel A Bus Reset. 4 SCBs aborted Jun 6 03:33:23 orion /kernel: sd0(ahc0:0:0): SCB 0x3 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x Jun 6 03:33:23 orion /kernel: SEQADDR = 0x175 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x0 Jun 6 03:33:23 orion /kernel: Ordered Tag queued Jun 6 03:33:23 orion /kernel: sd0(ahc0:0:0): SCB 0x2 timedout while recovery in progress Jun 6 03:33:23 orion /kernel: sd0(ahc0:0:0): SCB 0x1 timedout while recovery in progress Jun 6 03:33:23 orion /kernel: sd0(ahc0:0:0): SCB 0x0 timedout while recovery in progress Jun 6 03:33:23 orion /kernel: sd0(ahc0:0:0): SCB 0x3 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x Jun 6 03:33:23 orion /kernel: SEQADDR = 0x175 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x0 Jun 6 03:33:23 orion /kernel: sd0(ahc0:0:0): Queueing an Abort SCB Jun 6 03:33:23 orion /kernel: sd0(ahc0:0:0): SCB 0x3 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x Jun 6 03:33:23 orion /kernel: SEQADDR = 0x175 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x0 Jun 6 03:33:23 orion /kernel: sd0(ahc0:0:0): no longer in timeout Jun 6 03:33:23 orion /kernel: ahc0: Issued Channel A Bus Reset. 5 SCBs aborted Jun 6 03:33:23 orion /kernel: sd0(ahc0:0:0): UNIT ATTENTION asc:29,0 Jun 6 03:33:23 orion /kernel: sd0(ahc0:0:0): Power on, reset, or bus device reset occurred field replaceable Jun 6 03:33:23 orion /kernel: , retries:2 My dmesg: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.6-STABLE #0: Mon May 18 17:53:01 EDT 1998 root@orion.os.com:/usr/src/sys/compile/ORION CPU: Pentium Pro (265.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x633 Stepping=3 Features=0x80fbff real memory = 268435456 (262144K bytes) avail memory = 260911104 (254796K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 pci0:7:2: Intel Corporation, device=0x7020, class=serial, subclass=0x03 int d irq 9 [no driver assigned] de0 rev 35 int a irq 11 on pci0:10:0 de0: SMC 8432BT 21040 [10Mb/s] pass 2.3 de0: address 00:00:c0:0f:41:0f ahc0 rev 1 int a irq 10 on pci0:13:0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16/255 SCBs ahc0 waiting for scsi devices to settle ahc0: target 0 Tagged Queuing Device (ahc0:0:0): "SEAGATE ST19171W 0024" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 8683MB (17783112 512 byte sectors) vga0 rev 6 int a irq 11 on pci0:14:0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in npx0 flags 0x1 on motherboard npx0: INT 16 interface de0: enabling 10baseT port To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 15:05:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14097 for freebsd-stable-outgoing; Tue, 9 Jun 1998 15:05:38 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.atipa.com (altrox.atipa.com [208.128.22.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA14068 for ; Tue, 9 Jun 1998 15:05:11 -0700 (PDT) (envelope-from freebsd@atipa.com) Received: (qmail 5283 invoked by uid 1017); 9 Jun 1998 21:02:16 -0000 Date: Tue, 9 Jun 1998 15:02:16 -0600 (MDT) From: Atipa To: jktheowl@bga.com cc: freebsd-stable@FreeBSD.ORG Subject: NIS client maintenance script 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 Everyone, You may find this script to be of use for NIS clients. It can be run from crontab every minute or so to make sure NIS connections are up and running. It disables NIS authentication during network failures, and resets and enables NIS if the connection is restored. Must be run as root. May work with /bin/sh, but I like bash better. WARNING!!! This may modify your /etc/master.password file. If you can not understand what it does, do not use it! :) Kevin ----- #!/usr/local/bin/bash # This script maintains NIS client connections on simple networks # Rev. 1.0, 05-09-98, Kevin McCarthy (kmcc@atipa.com) # It disables NIS authentication during network failures, and resets # and enables NIS if the connection is restored. # User defined variables nis_host="host.domain.tld" # required nis_domainname="freakazoid" # required ypbind_args="-s -ypsetme" # -s for security ypset_args="$nis_host" # "" for no ypset # Clearspace for readability echo " " # Find current state (bool) of NIS nis_state=`grep + /etc/master.passwd && ps ax |grep yp` if [ -n "$nis_state" ]; then echo NIS authentication is ON else echo NIS authentication is OFF fi # Set up NIS conditional functions function nis_down () { echo "Error: $nis_problem" if [ -n "$nis_state"]; then echo "Disabling NIS authentication" umask 077 grep -v + /etc/master.passwd > /root/mp.nonis mv /etc/master.passwd /etc/master.passwd.nis mv /root/mp.nonis /etc/master.passwd pwd_mkdb -p /etc/master.passwd else echo "NIS remaining disabled" fi exit 1 } function nis_reset () { if [ -n "$nis_problem"]; then echo "Error: $nis_problem" fi echo -n "Resetting NIS services... " killall ypbind >> /dev/null domainname $nis_domainname ypbind $ypbind_args if [ -n "$ypset_args"]; then ypset $ypset_args fi echo "Done" reset_done="true" } function nis_up () { if [ -z "$nis_state" ]; then echo "NIS services restored. Enabling NIS authentication" umask 077 mv /etc/master.passwd.nis /etc/master.passwd pwd_mkdb -p /etc/master.passwd fi nis_working="true" } echo -n "Network connecion to $nis_host is " up=`ping -c1 $nis_host | grep transmitted | awk -F, '{print $2}' \ | awk '{print $1}'` if [ "$up" = "1" ]; then echo ON else echo OFF nis_problem="host not reachable (ping failed)" nis_down fi while [ -z "$nis_working" ]; do # Check if NIS is bound nis_bound=`ypwhich` if [ "$nis_bound" = "$nis_host" ]; then echo NIS binding to $nis_bound is ON nis_up else if [ -z "$reset_done" ]; then nis_problem="NIS binding to $nis_host is OFF" nis_reset else echo "Reset Failed; disabling NIS services" nis_down fi fi done echo "Exiting" echo " " To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 15:42:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20487 for freebsd-stable-outgoing; Tue, 9 Jun 1998 15:42:27 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from megaweapon.zigg.com (ip144.grand-rapids2.mi.pub-ip.psi.net [38.12.209.144]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20444 for ; Tue, 9 Jun 1998 15:42:09 -0700 (PDT) (envelope-from matt@megaweapon.zigg.com) Received: from megaweapon.zigg.com (megaweapon.zigg.com [192.168.1.1]) by megaweapon.zigg.com (8.8.8/8.8.8) with SMTP id SAA00655; Tue, 9 Jun 1998 18:41:34 -0400 (EDT) (envelope-from matt@megaweapon.zigg.com) Date: Tue, 9 Jun 1998 18:41:34 -0400 (EDT) From: Matt Behrens To: "Kelley L." cc: "Greg A. Woods" , freebsd-stable@FreeBSD.ORG Subject: Re: Matt Behrens: Re: kernel compile 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 For what it's worth, I feel that it is quite important for kernel-only users to be able to continue to use the tools in an unbroken state for the period up to 3.0. Yes, you need to follow the list. Yes, you need to spend a little time to get -STABLE up and running. But until we create a collection tag "src-buildtools", I don't think we should be changing anything. (Consider some of the 28.8k link / 486-class systems I am maintaining. Consider I had to cvsup quite a bit on that machine just to upgrade the kernel because not only was config broken, but some of my source tree was broken too.) Anyway, that's my two cents. Now will everyone please take me poor ol' name off the subject line of this thread? :) On Tue, 9 Jun 1998, Kelley L. wrote: > > > On Tue, 9 Jun 1998, Greg A. Woods wrote: > > > [ On Mon, June 8, 1998 at 17:18:21 (-0500), Richard Wackerbarth wrote: ] > > > Subject: Re: Matt Behrens: Re: kernel compile problem > > > > > I don't think that the "kernel only" source users would consider > > > my argument at all bogus. For them, the 2.2 branch is BROKEN. They > > > cannot apply the latest security updates which affect the kernel > > > until 2.2.7 is released. > > > > It's only broken until it's fixed, and the sooner it's fixed, the > > better, as then more people will be able to test them. > > > > The obvious fix has been discussed, and it seems as if it will be > > implemented. It has proven extremely effective in NetBSD. (I.e. to > > include src/usr.sbin/config and its contents in the kernel-only source > > distrbution collections available through ftp, sup, CVSup, CTM, etc.) > > > > BTW, anyone seriously trying to keep right up to the minute with > > security fixes and such would be better off with user-land only than > > with kernel-only. People with so few resources should let other people > > manage the source tree and they should stick to releases only. > > > > I've recently come over from linux land, and I think FreeBSD is much > more stable. The recent linux kernels in the 2.0.x series seem to be > incorporating too many new features, and they are for my part much less > stable than they were before. > > Which brings me to the question, how does one keep FreeBSD up to date > and secure? Wrong question, mainly concerned with just keeping it secure. > I use RedHat, and they have the updates to use to keep all the packages up > to date with security fixes. Does anything similar exist in FreeBSD. I'm a > little new, so I'm just not familiar with all the FreeBSDisms yet. > > I've been keeping up with the Stable, by cvsup'ing and then make > buildworld and make installworld, then rebuilding the kernel and > rebooting. About once a week. I gathered this was the way to keep fairly > secure, is this not a correct assessment? > > > > > Working with a live CVS repository (or even a daily copy of it) is bound > > to produce unpredictable results. Anyone crying wolf at the slightest > > perturbance will go hoarse and loose their voice long before they become > > too annoying. ;-) > > > > Which is why I read the stable list, to read about any problems others > are having, before I waste any where from 3 to 5 hours making the world > only to find out it didn't. Of course I would rather buildworld break, > since it doesn't affect anthing until installworld is run. > > later > Kelley > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > Matt Behrens | http://www.zigg.com/ Network Operations, The Iserv Company | Proudly running FreeBSD; sworn MIS, Michigan Kenworth, Inc. | enemy of Linux, a free hack OS Chanop Script Coordinator, WWFIN | and Windows, a non-free hack OS! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 15:45:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21122 for freebsd-stable-outgoing; Tue, 9 Jun 1998 15:45:25 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.atipa.com (altrox.atipa.com [208.128.22.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA21002 for ; Tue, 9 Jun 1998 15:44:45 -0700 (PDT) (envelope-from freebsd@atipa.com) Received: (qmail 5430 invoked by uid 1017); 9 Jun 1998 21:41:50 -0000 Date: Tue, 9 Jun 1998 15:41:50 -0600 (MDT) From: Atipa To: jktheowl@bga.com cc: freebsd-stable@FreeBSD.ORG Subject: Re: NIS client maintenance script 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 Oops! I posted the wrong script.. :( Download the correct one from ftp://ftp.atipa.com/pub/FreeBSD/nis-client Kevin On Tue, 9 Jun 1998, Atipa wrote: > > Everyone, > > You may find this script to be of use for NIS clients. It can be run from > crontab every minute or so to make sure NIS connections are up and > running. > > It disables NIS authentication during network failures, and > resets and enables NIS if the connection is restored. > > Must be run as root. May work with /bin/sh, but I like bash better. > > WARNING!!! This may modify your /etc/master.password file. If you can not > understand what it does, do not use it! :) > > Kevin > > > ----- > #!/usr/local/bin/bash > > # This script maintains NIS client connections on simple networks > # Rev. 1.0, 05-09-98, Kevin McCarthy (kmcc@atipa.com) > > # It disables NIS authentication during network failures, and resets > # and enables NIS if the connection is restored. > > # User defined variables > nis_host="host.domain.tld" # required > nis_domainname="freakazoid" # required > ypbind_args="-s -ypsetme" # -s for security > ypset_args="$nis_host" # "" for no ypset > > # Clearspace for readability > echo " " > > # Find current state (bool) of NIS > nis_state=`grep + /etc/master.passwd && ps ax |grep yp` > if [ -n "$nis_state" ]; then > echo NIS authentication is ON > else > echo NIS authentication is OFF > fi > > # Set up NIS conditional functions > function nis_down () { > echo "Error: $nis_problem" > > if [ -n "$nis_state"]; then > echo "Disabling NIS authentication" > umask 077 > grep -v + /etc/master.passwd > /root/mp.nonis > mv /etc/master.passwd /etc/master.passwd.nis > mv /root/mp.nonis /etc/master.passwd > pwd_mkdb -p /etc/master.passwd > else > echo "NIS remaining disabled" > fi > > exit 1 > } > > function nis_reset () { > if [ -n "$nis_problem"]; then > echo "Error: $nis_problem" > fi > > echo -n "Resetting NIS services... " > killall ypbind >> /dev/null > domainname $nis_domainname > ypbind $ypbind_args > if [ -n "$ypset_args"]; then > ypset $ypset_args > fi > echo "Done" > > reset_done="true" > } > > function nis_up () { > if [ -z "$nis_state" ]; then > echo "NIS services restored. Enabling NIS authentication" > umask 077 > mv /etc/master.passwd.nis /etc/master.passwd > pwd_mkdb -p /etc/master.passwd > fi > > nis_working="true" > } > > echo -n "Network connecion to $nis_host is " > up=`ping -c1 $nis_host | grep transmitted | awk -F, '{print $2}' \ > | awk '{print $1}'` > if [ "$up" = "1" ]; then > echo ON > else > echo OFF > nis_problem="host not reachable (ping failed)" > nis_down > fi > > while [ -z "$nis_working" ]; do > # Check if NIS is bound > nis_bound=`ypwhich` > > if [ "$nis_bound" = "$nis_host" ]; then > echo NIS binding to $nis_bound is ON > nis_up > else > if [ -z "$reset_done" ]; then > nis_problem="NIS binding to $nis_host is OFF" > nis_reset > else > echo "Reset Failed; disabling NIS services" > nis_down > fi > fi > done > > echo "Exiting" > echo " " > > > 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 Jun 9 17:18:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08181 for freebsd-stable-outgoing; Tue, 9 Jun 1998 17:18:08 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.telstra.com.au (mail.telstra.com.au [192.148.160.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08076 for ; Tue, 9 Jun 1998 17:17:56 -0700 (PDT) (envelope-from MRyan@VICMAIN.YPA.telstra.com.au) Received: (from uucp@localhost) by mail.telstra.com.au (8.8.2/8.6.9) id KAA05353 for ; Wed, 10 Jun 1998 10:17:08 +1000 (EST) Received: from mail-gw.fwall.telstra.com.au(192.148.147.16) via SMTP by mail.telstra.com.au, id smtpd005262; Wed Jun 10 10:16:44 1998 Received: (from uucp@localhost) by mail-gw.fwall.telstra.com.au (8.8.2/8.6.9) id KAA13967 for ; Wed, 10 Jun 1998 10:16:43 +1000 (EST) Received: from cdn-mail.dn.itg.telecom.com.au(144.135.109.134) via SMTP by mail-gw.fwall.telstra.com.au, id smtpd013912; Wed Jun 10 10:16:16 1998 Received: from ypmail.nds.telecom.com.au (ypmail.nds.telecom.com.au [172.136.8.3]) by cdn-mail.dn.itg.telecom.com.au (8.8.2/8.6.9) with SMTP id KAA15836 for ; Wed, 10 Jun 1998 10:16:15 +1000 (EST) Received: by ypmail.nds.telecom.com.au with Microsoft Mail id <357DD051@ypmail.nds.telecom.com.au>; Wed, 10 Jun 98 10:16:17 EST From: "Ryan, Martin" To: "'freebsd-stable'" Subject: Auto installation scripts Date: Tue, 09 Jun 98 17:27:00 EST Message-ID: <357DD051@ypmail.nds.telecom.com.au> X-Mailer: Microsoft Mail V3.0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, Is there a way to feed the "installation kernel" on a boot floppy a config file such that it will do a complete installation without asking *any* questions? I've seen the sysinstall shortcuts stuff which would be fine except, as I understand it, this can only be used when you have a system that already has freebsd on it. I can make a mini kernel bootable floppy and then attach to an ftp server and download stuff etc but I just want to check that I'm not re-inventing some wheels by doing this. Many thanks for any pointers Martin Ryan Network Analyst Pacific Access Melbourne Australia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 17:18:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08328 for freebsd-stable-outgoing; Tue, 9 Jun 1998 17:18:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08307 for ; Tue, 9 Jun 1998 17:18:44 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id RAA15929; Tue, 9 Jun 1998 17:18:00 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: "Kelley L." cc: "Greg A. Woods" , freebsd-stable@FreeBSD.ORG Subject: Re: Matt Behrens: Re: kernel compile problem In-reply-to: Your message of "Tue, 09 Jun 1998 16:13:15 EDT." Date: Tue, 09 Jun 1998 17:17:59 -0700 Message-ID: <15925.897437879@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've been keeping up with the Stable, by cvsup'ing and then make > buildworld and make installworld, then rebuilding the kernel and > rebooting. About once a week. I gathered this was the way to keep fairly > secure, is this not a correct assessment? That is an entirely correct assessment. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 17:44:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA12167 for freebsd-stable-outgoing; Tue, 9 Jun 1998 17:44:31 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11989 for ; Tue, 9 Jun 1998 17:43:15 -0700 (PDT) (envelope-from Carl.Makin@ipaustralia.gov.au) From: Carl.Makin@ipaustralia.gov.au Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.8.5/8.6.12) id KAA18712; Wed, 10 Jun 1998 10:42:28 +1000 (EST) X-Authentication-Warning: pericles.IPAustralia.gov.au: smap set sender to using -f Received: from notesitc.aipo.gov.au(192.3.1.17) by pericles.IPAustralia.gov.au via smap (V2.0) id xma018703; Wed, 10 Jun 98 10:42:17 +1000 Received: by notesitc.aipo.gov.au(Lotus SMTP MTA v4.6.1 (569.2 2-6-1998)) id 4A25661F.0003DE0A ; Wed, 10 Jun 1998 10:42:14 +1000 X-Lotus-FromDomain: IP_AUSTRALIA To: Gary Kline , Jose Marques cc: freebsd-stable@FreeBSD.ORG Message-ID: <4A25661F.0003DB28.00@notesitc.aipo.gov.au> Date: Wed, 10 Jun 1998 10:18:05 +1000 Subject: Re[2]: X11 problem? 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 I have a MMII 4Mb in a "stable" box under XFree 3.3.2 here at work and haven't noticed this lockup. It has a 17inch monitor and runs at 1280x1024x16bpp at 76hz. I'm *very* happy with it! Carl. ______________________________ Reply Separator ____________________________ _____ Subject: Re: X11 problem? Author: Jose Marques at IP_AUSTRALIA Date: 09/6/98 12:31 On Sun, 7 Jun 1998, Gary Kline wrote: [Snip] > upgrade. Maybe the Matrox with 4M will let me go > to 1280x1024. I use a MMII with 8MB. Generally very nice with XFree86 3.3.2. However, once in a while it will lock up the machine when starting. I don't know To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 17:52:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13317 for freebsd-stable-outgoing; Tue, 9 Jun 1998 17:52:12 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA13235 for ; Tue, 9 Jun 1998 17:51:58 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id KAA05640; Wed, 10 Jun 1998 10:21:27 +0930 (CST) Message-Id: <199806100051.KAA05640@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Jose Marques cc: Gary Kline , freebsd-stable@FreeBSD.ORG Subject: Re: X11 problem? In-reply-to: Your message of "Tue, 09 Jun 1998 13:31:09 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Jun 1998 10:21:26 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I use a MMII with 8MB. Generally very nice with XFree86 3.3.2. However, > once in a while it will lock up the machine when starting. I don't know > if this is a widespread problem - I've seen one other report on the news > group. We use the same thing at work, I have seen the lockup twice.. Kind of annoying, but the card is very nice :) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 17:57:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14208 for freebsd-stable-outgoing; Tue, 9 Jun 1998 17:57:11 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA14196 for ; Tue, 9 Jun 1998 17:57:05 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id RAA16209; Tue, 9 Jun 1998 17:56:21 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: "Ryan, Martin" cc: "'freebsd-stable'" Subject: Re: Auto installation scripts In-reply-to: Your message of "Tue, 09 Jun 1998 17:27:00 EST." <357DD051@ypmail.nds.telecom.com.au> Date: Tue, 09 Jun 1998 17:56:21 -0700 Message-ID: <16206.897440181@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there a way to feed the "installation kernel" on a boot floppy a > config file > such that it will do a complete installation without asking *any* > questions? Yes, though it's definitely for advanced users only. You'll need to read the man page for sysinstall for a complete list of variables and functions which are available through that mechanism though, the /usr/src/release/sysinstall/install.cfg file also providing a working example. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 20:14:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06417 for freebsd-stable-outgoing; Tue, 9 Jun 1998 20:14:17 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA06412 for ; Tue, 9 Jun 1998 20:14:11 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id UAA13388; Tue, 9 Jun 1998 20:13:58 -0700 (PDT) (envelope-from jdp) Message-Id: <199806100313.UAA13388@austin.polstra.com> To: KHamilton@Hunter.COM Subject: Re: Boot floppy with CAM support? In-Reply-To: <92BD86195CB3D011832F0000C052D9E369096E@mystique.Hunter.COM> References: <92BD86195CB3D011832F0000C052D9E369096E@mystique.Hunter.COM> Organization: Polstra & Co., Seattle, WA Cc: stable@FreeBSD.ORG Date: Tue, 09 Jun 1998 20:13:58 -0700 From: John Polstra Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <92BD86195CB3D011832F0000C052D9E369096E@mystique.Hunter.COM>, wrote: > > http://www.freebsd.org/~abial/cam-boot/ > > -- > > Thanks. Any idea why the floppy with CAM in it can't see my Intel > Pro-100B card but the floppy without CAM can see the netcard just fine. I just booted from the CAM floppy for the first time today, or I would have replied sooner. It recognized fxp0 on my machine without any problems. The machine is a Toshiba Equium with the Intel Ethernet chip on the motherboard. I don't know why it's not working for you, but the driver is definitely configured into the kernel on the floppy. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 20:42:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10387 for freebsd-stable-outgoing; Tue, 9 Jun 1998 20:42:11 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10323 for ; Tue, 9 Jun 1998 20:41:46 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id UAA13708; Tue, 9 Jun 1998 20:41:36 -0700 (PDT) (envelope-from jdp) Message-Id: <199806100341.UAA13708@austin.polstra.com> To: flygt@sr.se Subject: Re: Yet another compile error In-Reply-To: <19980605084347.08598@sr.se> References: <078b01bd901e$4367b2d0$6cb611cb@saruman.scitec.com.au> <19980605084347.08598@sr.se> Organization: Polstra & Co., Seattle, WA Cc: stable@FreeBSD.ORG Date: Tue, 09 Jun 1998 20:41:36 -0700 From: John Polstra Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19980605084347.08598@sr.se>, Gunnar Flygt wrote: > Yes, but I told you my machine is behind a firewall, so I can't cvsup. > Otherwise I would have done that a long time ago. No one would be more happy > than me these days if I could use cvsup. Hey, I would be pretty happy if you could use CVSup. I want _everybody_ to use it. :-) Can't you persuade your firewall administrator to permit you to make an outbound connection to port 5999 of one specific machine? That's all you need, if you use "-P m" on the cvsup command line. Another possibility is to tunnel using ssh, as described in cvsup(1). But you need a login account on the CVSup server host to do that. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 21:55:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21210 for freebsd-stable-outgoing; Tue, 9 Jun 1998 21:55:03 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from roma.coe.ufrj.br (jonny@roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21201 for ; Tue, 9 Jun 1998 21:54:56 -0700 (PDT) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id BAA08663; Wed, 10 Jun 1998 01:54:42 -0300 (EST) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199806100454.BAA08663@roma.coe.ufrj.br> Subject: Re: Bug in mount_union In-Reply-To: <19321.896929928@time.cdrom.com> from "Jordan K. Hubbard" at "Jun 3, 98 08:12:08 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 10 Jun 1998 01:54:41 -0300 (EST) Cc: kazz-0@ca2.so-net.ne.jp, stable@FreeBSD.ORG 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 #define quoting(Jordan K. Hubbard) // > I found a bug in mount_union of 2.2-stable. // // Yikes! Somebody trying to use unionfs in 2.2! ;-) // // Seriously, that's not the only panic you're going to get if you try to // use that code in that branch. AFAIK, it's really only going to be a // practical option for 3.0 unless someone back-ports all the changes // which were necessary to make it truly work in -current. Indeed, last week I thought of using umapfs, just to find all problems above. :( I was planning a scheme to allow use of ffs zip disks in my machines, without having to allow userids to be seen. BTW: This made me think of a umapfs with a command line "one-userid-only" option, to avoid creating a umaptable file. I would even try to do that myself, but I have currently no developing access to a -current machine (pun intended). What do people think of that idea ? Is it worth to give it a try ? Jonny PS: Why ffs zip disks ? Because msdosfs is TOOOOOOOOO slow :), and sometimes it makes my system freeze (I'm searching for causes, but found no real clue yet). PS2: How is VFS code going -current ? Much better than in -stable ? -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 22:14:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24048 for freebsd-stable-outgoing; Tue, 9 Jun 1998 22:14:51 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from roma.coe.ufrj.br (jonny@roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24021 for ; Tue, 9 Jun 1998 22:14:46 -0700 (PDT) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id CAA08890; Wed, 10 Jun 1998 02:12:28 -0300 (EST) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199806100512.CAA08890@roma.coe.ufrj.br> Subject: Re: Matt Behrens: Re: kernel compile problem In-Reply-To: from Richard Wackerbarth at "Jun 5, 98 06:42:00 am" To: rkw@dataplex.net (Richard Wackerbarth) Date: Wed, 10 Jun 1998 02:12:28 -0300 (EST) Cc: lcremean@tidalwave.net, jkh@time.cdrom.com, stuart@internationalschool.co.uk, eivind@yes.no, gibbs@plutotech.com, stable@FreeBSD.ORG 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 #define quoting(Richard Wackerbarth) // >The more I look at this problem, the more i think that bundling config in // >the /usr/src/sys area instead of /usr/sbin makes more sense. /usr/sbin is a // >bad place for it anyway--it's really only meant for use on the kernel, at // >least in FreeBSD. It could be like /usr/src/sys/whatever/config... // // I disagree. It is not a part of the kernel. It is a tool used to generate // the kernel. Therefore, it's only useful with the kernel sources. // Should we move "gcc", "yacc", "perl", ... into the kernel space just // because (if) // they are used to build the kernel? I think that the answer is obviously "No". The big diference is that config can not be used to compile userland programs. Although Eivind talked about userland source configuration, config will still be only a source tree tool, I think. There's no need to have config around in /usr/sbin. // >PS: Even if people don't like the idea of moving it to /usr/src/sys, // >including it in the CVS and CVSup src-sys modules would work, since it would // >keep matching versions of config together. This would help, at least. Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 22:58:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA01408 for freebsd-stable-outgoing; Tue, 9 Jun 1998 22:58:54 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from xwin.webweaver.net (xwin.webweaver.net [208.138.29.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA01368 for ; Tue, 9 Jun 1998 22:58:43 -0700 (PDT) (envelope-from nicole@xwin.webweaver.net) Received: (from nicole@localhost) by xwin.webweaver.net (8.8.8/8.8.7) id XAA29180; Tue, 9 Jun 1998 23:04:16 -0700 (PDT) (envelope-from nicole) Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 In-Reply-To: <19980602172820.43891@easynet.fr> Date: Tue, 09 Jun 1998 23:04:16 -0700 (PDT) From: Nicole To: David Ramahefason Subject: RE: NEED HELP ON DPT INSTALL Cc: stable@FreeBSD.ORG Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id WAA01371 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 02-Jun-98 David Ramahefason wisely wrote: > well, > we've received a DPT today and tried to install freebsd > on it (2.2.6 with boo-dpt.flp). > First what are the recommended setup under the DTP mgr tool > to build a RAID 5 array ?? > It seems that the array has to be initialize with fdisk to be > recognize by freebsd... > So after finding this, we've rebooted under fbsd, the > partition and label part seem to work fine, but after this > the setup just hang on the cpio stuff from the boot disk... > Does anyone has an idea about this ?? > Hi first off, the card and the drives must be initialized via a dos boot and it's dos drivers disk. It takes a moment to pick up, but you get the hang of it. af ter booting to dos, insert the dos drivers disk and type dptmgr. This will let you set up the RAID style that you want and then add drives to it. Then you need to install FreeBSD via the dpt-boot.flp image. However.... Before rebooting after the install, you must drop into "alt F4" prompt window and buil d a kernal with the DPT support. The Generic kernel does not have it yet. BTW: I have yet to be able to do a make world with the DPT card and RAID 5. Wor ks great mirrord though. Nicole nicole@webweaver.net - http://www.webweaver.net/ webmistress@dangermouse.org - http://www.dangermouse.org/ ------------------------------------------------- -- Powered by Coka Cola and FreeBSD -- -- Stong enough for a man - But made for a Woman -- -- Microsoft: What bug would you like today? -- -- I tried an internal modem once, but it hurt when I walked -- --------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 23:11:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03088 for freebsd-stable-outgoing; Tue, 9 Jun 1998 23:11:42 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from xwin.webweaver.net (xwin.webweaver.net [208.138.29.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03064; Tue, 9 Jun 1998 23:11:34 -0700 (PDT) (envelope-from nicole@xwin.webweaver.net) Received: (from nicole@localhost) by xwin.webweaver.net (8.8.8/8.8.7) id XAA29238; Tue, 9 Jun 1998 23:17:09 -0700 (PDT) (envelope-from nicole) Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 In-Reply-To: Date: Tue, 09 Jun 1998 23:17:09 -0700 (PDT) From: Nicole To: Jaye Mathisen Subject: RE: Is the DPT client in -stable usable? Cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id XAA03070 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Jun-98 Jaye Mathisen wisely wrote: > > > I remember seeing some people were having problems building kernels after > 2.2.6 with DPT problems, but didn't see anything about resolution. > > I just got a new DPT in with firmware 07M0, and it seems to be OK > under the stock 2.2.6 kernel, but I want to keep up with developments > in -stable, but of course, don't want a non-bootable machine when I'm > done. > > DPT stuff works great if you A: setup and initialize the drivers via DOS B: Drop to F4 and build a kernel with DPT support as it does not have it in thei r yet. One HUGE problem I have found is that I can't make world when using RAID 5. I s ent in a message about that with no response. Same card same everying, redone wi th 2 drives mirrored works great. Also I had a card barf today doing a make world -j3 on a 400 MHZ pent II system . It bailed and rebooted the system. Without the j3 it seems to be OK. I plan on using Lots of these cards. So any&all insight/info would be welcome. Nicole nicole@webweaver.net - http://www.webweaver.net/ webmistress@dangermouse.org - http://www.dangermouse.org/ ------------------------------------------------- -- Powered by Coka Cola and FreeBSD -- -- Stong enough for a man - But made for a Woman -- -- Microsoft: What bug would you like today? -- -- I tried an internal modem once, but it hurt when I walked -- --------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 23:32:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA05738 for freebsd-stable-outgoing; Tue, 9 Jun 1998 23:32:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dreamer.dreamfire.net (qmailr@dreamfire.net [209.160.21.220]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA05722 for ; Tue, 9 Jun 1998 23:32:41 -0700 (PDT) (envelope-from sean@dreamfire.net) Received: (qmail 541 invoked from network); 10 Jun 1998 03:50:15 -0000 Received: from dreamfire.net (HELO dreamer.dreamfire.net) (209.160.21.220) by dreamfire.net with SMTP; 10 Jun 1998 03:50:15 -0000 Date: Tue, 9 Jun 1998 20:50:15 -0700 (PDT) From: Sean-Paul Rees To: freebsd-stable@FreeBSD.ORG Subject: Processor upgrade, minor problem. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- I just upgraded from my Pentium 133, to the Evergreen MxPro 200MHz MMX- and FreeBSD doesn't echo it's features like it did on the P133. This is what I get: FreeBSD 2.2.6-STABLE #0: Tue Jun 9 19:31:07 PDT 1998 root@dreamer.dreamfire.net:/usr/src/sys/compile/DREAMER CPU: Pentium (199.43-MHz 586-class CPU) Origin = "CentaurHauls" Id = 0x540 real memory = 100663296 (98304K bytes) instead of: FreeBSD 2.2.6-STABLE #0: Sat May 16 23:45:40 PDT 1998 root@dreamer.dreamfire.net:/usr/src/sys/compile/DREAMER CPU: Pentium (132.96-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52b Stepping=11 Features=0x1bf real memory = 100663296 (98304K bytes) Can anybody help? Sincerely, - -Sean-Paul Rees sean@dreamfire.net, SR5176 =============================================== = Sean-Paul Rees = Dream Fire Networks = = sean@dreamfire.net = Dream Fire Consulting = = = = "Marking your achievements, and improving = = upon them is better than any award anybody = = will bestow." -Sean-Paul Rees = =============================================== sig updated: 5/20/1998 Type bits/keyID Date User ID pub 2047/EF18B3ED 1998/04/11 Sean-Paul Rees -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQEVAwUBNX4CcbDu0TvvGLPtAQEilwf7Bj3DGYxHqASLJD32V3izwGkE8ONc5IDm vwc7ZfTDYuoadS7KtvDZ11WqU5FHsJ2RUINRxq+TXpCO9IqNRhlKf/0o1OlnilIo c0E6YaK9fQAAtvK1HDLWtBnGNNjaQMPaMYsKQXmtf1xURjJ+JdAqz4vSZ5wwClGp f65O4KhERdD9xIzaCcQLZz59M7w94SuCjTpEXiO7AbZRKTnlCWxIdEglXCf1wwoR iuVIFbrnMgijlI02bxfYJc4wUdnixMMIbwA2bV2vncedT0hvaSM2sgY0baOv1Eqm ACy+8AEd9W3XuNy3Ke+oN2LmCoyaPeShVwj0wwWDWi3oq2r/IzC7WA== =JDft -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 9 23:46:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08479 for freebsd-stable-outgoing; Tue, 9 Jun 1998 23:46:01 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from milou.wyssdata.ch (milou.wyssdata.ch [194.235.47.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA08170 for ; Tue, 9 Jun 1998 23:44:45 -0700 (PDT) (envelope-from blapp@attic.ch) Received: from attic.ch (oensingen-gate1-04.solnet.ch [194.235.47.99]) by milou.wyssdata.ch (8.9.0/8.9.0) with ESMTP id IAA14853 for ; Wed, 10 Jun 1998 08:52:11 +0200 (CEST) Message-ID: <357E3934.25B52B9E@attic.ch> Date: Wed, 10 Jun 1998 08:43:48 +0100 From: Martin Blapp Reply-To: blapp@attic.ch Organization: Attic Internet Promotions X-Mailer: Mozilla 4.05 [en] (WinNT; U) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Make buildworld problems ... References: 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 a box that is unable to build world. It's compiling about half an hour and then the following error occurs : Fatal Double fault eip = 0xf01d0f46 esp = 0xefbfb000 ebp = 0xefbeb00c panic : double fault and then the system tries to syncing discs and freezes :-( My System includes the following hardware : Cyrix PR200 (Cache disabled) 96 MB Ram Simms 60 ns Pentium Board (Cache onboard disabled) and 2 isa cards .... I've got 96 MB Ram and installing wasn't a problem. Nevertheless I thought it could be something similar like in the errata for 2.2.6. I'm trying now to compile with only 64 Mb Ram ... and will report if anything has changed ... Does anybody know this problem ? Is it a cyrix-specific problem ? Martin -- ------------------------------------------------------------------------ Martin Blapp, (blapp@attic.ch) Attic Internet Services, Bechburgstrasse 8, 4702 Oensingen, Switzerland Phone: +41 62 396 43 70, Fax: +41 62 396 43 72 PGP fingerprint: 4E96 1AE8 4AA6 AB40 1AD6 DB42 7623 995D 522A 1D38 ------------------------------------------------------------------------ Public key available at: http://www.attic.ch/pgp-public.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 00:30:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16591 for freebsd-stable-outgoing; Wed, 10 Jun 1998 00:30:00 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.telstra.com.au (mail.telstra.com.au [192.148.160.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA16584 for ; Wed, 10 Jun 1998 00:29:55 -0700 (PDT) (envelope-from MRyan@VICMAIN.YPA.telstra.com.au) Received: (from uucp@localhost) by mail.telstra.com.au (8.8.2/8.6.9) id RAA17311; Wed, 10 Jun 1998 17:29:19 +1000 (EST) Received: from mail-gw.fwall.telstra.com.au(192.148.147.16) via SMTP by mail.telstra.com.au, id smtpd016890; Wed Jun 10 17:28:13 1998 Received: (from uucp@localhost) by mail-gw.fwall.telstra.com.au (8.8.2/8.6.9) id RAA28534; Wed, 10 Jun 1998 17:28:11 +1000 (EST) Received: from cdn-mail.dn.itg.telecom.com.au(144.135.109.134) via SMTP by mail-gw.fwall.telstra.com.au, id smtpd028079; Wed Jun 10 17:27:26 1998 Received: from ypmail.nds.telecom.com.au (ypmail.nds.telecom.com.au [172.136.8.3]) by cdn-mail.dn.itg.telecom.com.au (8.8.2/8.6.9) with SMTP id RAA19242; Wed, 10 Jun 1998 17:27:24 +1000 (EST) Received: by ypmail.nds.telecom.com.au with Microsoft Mail id <357E355E@ypmail.nds.telecom.com.au>; Wed, 10 Jun 98 17:27:26 EST From: "Ryan, Martin" To: sto Cc: "'freebsd-stable'" Subject: RE: Auto installation scripts Date: Wed, 10 Jun 98 17:33:00 EST Message-ID: <357E355E@ypmail.nds.telecom.com.au> X-Mailer: Microsoft Mail V3.0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ---------- >Have you looked at the load config option from sysinstall? An > "example" file is in /usr/src/release/sysinstall/install.cfg ... >Hope this steers you in the right direction. >Sean -- Thanks Sean, this is what I'm after. Only one other small question; how do I get the install kernel to pick the config file up? The sysinstall man page says you can compile in a CONFIG_FILE option but this will create a new version of sysinstall - not the kernel thats on the boot floppy. Cheers, Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 00:34:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18000 for freebsd-stable-outgoing; Wed, 10 Jun 1998 00:34:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA17994 for ; Wed, 10 Jun 1998 00:34:45 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id AAA17851; Wed, 10 Jun 1998 00:32:31 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Joao Carlos Mendes Luis cc: rkw@dataplex.net (Richard Wackerbarth), lcremean@tidalwave.net, stuart@internationalschool.co.uk, eivind@yes.no, gibbs@plutotech.com, stable@FreeBSD.ORG Subject: Re: Matt Behrens: Re: kernel compile problem In-reply-to: Your message of "Wed, 10 Jun 1998 02:12:28 -0300." <199806100512.CAA08890@roma.coe.ufrj.br> Date: Wed, 10 Jun 1998 00:32:31 -0700 Message-ID: <17847.897463951@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The big diference is that config can not be used to compile userland > programs. Although Eivind talked about userland source configuration, > config will still be only a source tree tool, I think. There's no need > to have config around in /usr/sbin. I actually have to agree. Having config/ not come along with the ksrc distribution or get updated as part of src-sys with cvsup has been a major cause of agony for people who want to just update the kernel in order to fix some bug but don't want to cvsup src-all just so they can get a bloody config(8) which works with it! Justin's partial CAM changes to config have essentially made that an absolute requirement for anyone trying to get -stable, and it would be really nice if the -stable user got both sets of bits with one target. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 01:05:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23217 for freebsd-stable-outgoing; Wed, 10 Jun 1998 01:05:59 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23211 for ; Wed, 10 Jun 1998 01:05:53 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id BAA18050; Wed, 10 Jun 1998 01:05:07 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: "Ryan, Martin" cc: sto , "'freebsd-stable'" Subject: Re: Auto installation scripts In-reply-to: Your message of "Wed, 10 Jun 1998 17:33:00 EST." <357E355E@ypmail.nds.telecom.com.au> Date: Wed, 10 Jun 1998 01:05:06 -0700 Message-ID: <18046.897465906@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Thanks Sean, this is what I'm after. Only one other small question; how > do I get the install kernel to pick the config file up? It's easiest to just copy it onto the boot floppy (a UFS filesystem) and use the "Load config file" option to launch it unless you are the kind of hacking stud who can figure out how to repack an MFSCRUNCHed kernel or roll his own release. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 01:18:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA25323 for freebsd-stable-outgoing; Wed, 10 Jun 1998 01:18:32 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (jkh@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA25299 for ; Wed, 10 Jun 1998 01:18:24 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: (from jkh@localhost) by time.cdrom.com (8.8.8/8.8.8) id BAA18128 for stable@freebsd.org; Wed, 10 Jun 1998 01:17:46 -0700 (PDT) (envelope-from jkh) Date: Wed, 10 Jun 1998 01:17:46 -0700 (PDT) From: "Jordan K. Hubbard" Message-Id: <199806100817.BAA18128@time.cdrom.com> To: stable@FreeBSD.ORG Subject: Anyone running the linux emulation as an LKM under 2.2-stable? Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The reason I ask is that I'm no longer able to do so. All linux binaries coredump immediately if I attempt to use the Linux emulator as an LKM but work *fine* if I compile the kernel with COMPAT_LINUX and don't load the Linux LKM (actually, I can do _both_ but the LKM version isn't used if it's compiled in - perhaps a bug to allow both to be loaded like this?). Anyone even seeing the same symptoms? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 02:49:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11881 for freebsd-stable-outgoing; Wed, 10 Jun 1998 02:49:52 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from manchester.genrad.com (x191.genrad.co.uk [195.99.3.191] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA11843 for ; Wed, 10 Jun 1998 02:49:43 -0700 (PDT) (envelope-from swindellsr@genrad.co.uk) Date: Wed, 10 Jun 1998 02:49:43 -0700 (PDT) Message-Id: <199806100949.CAA11843@hub.freebsd.org> Received: from CDP275.uk.genrad.com by manchester.genrad.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1458.49) id M4QGHQRK; Wed, 10 Jun 1998 10:49:11 +0100 From: Robert Swindells To: stable@FreeBSD.ORG In-reply-to: <199806100817.BAA18128@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: Anyone running the linux emulation as an LKM under 2.2-stable? Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: >The reason I ask is that I'm no longer able to do so. All linux binaries >coredump immediately if I attempt to use the Linux emulator as an LKM but >work *fine* if I compile the kernel with COMPAT_LINUX and don't load >the Linux LKM (actually, I can do _both_ but the LKM version isn't used >if it's compiled in - perhaps a bug to allow both to be loaded like this?). It works ok for me. I last CVSUPed about 10 days ago though. >Anyone even seeing the same symptoms? I saw it once when I had forgotten to 'make install' the lkms after rebuilding the kernel. Robert Swindells ---------------------------------- Robert Swindells - GenRad Ltd. rjs@genrad.co.uk - Work rjs@fdy2.demon.co.uk - Home To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 04:03:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA29435 for freebsd-stable-outgoing; Wed, 10 Jun 1998 04:03:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ints3.csie.nctu.edu.tw (james@ints3.csie.nctu.edu.tw [140.113.215.192]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA29243 for ; Wed, 10 Jun 1998 04:02:34 -0700 (PDT) (envelope-from james@ints3.csie.nctu.edu.tw) Received: (from james@localhost) by ints3.csie.nctu.edu.tw (8.8.8/8.8.8) id TAA21341; Wed, 10 Jun 1998 19:01:04 +0800 (CST) (envelope-from james) Message-ID: <19980610190103.A21020@Kavalan.csie.NCTU.edu.tw> Date: Wed, 10 Jun 1998 19:01:03 +0800 From: Wei-Kai Wu To: freebsd-stable@FreeBSD.ORG Subject: Stray Dequot, reboot !? References: <199806071353.VAA06424@ints3.csie.nctu.edu.tw> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199806071353.VAA06424@ints3.csie.nctu.edu.tw>; from Wei-Kai Wu on Sun, Jun 07, 1998 at 09:53:53PM +0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I reboot, it shows some messages: panic: dqflush: stray dquot reboot ....15 seconds... version: src-2.2.0752 I can't find the keyword "dqflush" or "stray dquot" in /usr/src/sbin/reboot/*.c and /usr/src/sbin/shutdown/*.c Can anyone help me? Thanks a lot! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 05:28:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15314 for freebsd-stable-outgoing; Wed, 10 Jun 1998 05:28:32 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns11.rim.or.jp (root@ns11.rim.or.jp [202.247.130.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA15290 for ; Wed, 10 Jun 1998 05:28:23 -0700 (PDT) (envelope-from motoyuki@snipe.rim.or.jp) Received: from rayearth.rim.or.jp (rayearth.rim.or.jp [202.247.130.242]) by ns11.rim.or.jp (8.8.5/3.5Wpl2-ns11/RIMNET-2) with ESMTP id VAA02261 for ; Wed, 10 Jun 1998 21:28:20 +0900 (JST) Received: (from uucp@localhost) by rayearth.rim.or.jp (8.8.5/3.5Wpl2-uucp1/RIMNET) with UUCP id VAA23559 for freebsd-stable@freebsd.org; Wed, 10 Jun 1998 21:28:20 +0900 (JST) Received: from eddie.snipe.rim.or.jp (eddie.snipe.rim.or.jp [192.168.11.1]) by mserver.snipe.rim.or.jp (8.8.8/3.6W) with ESMTP id VAA17818; Wed, 10 Jun 1998 21:27:32 +0900 (JST) Received: from eddie.snipe.rim.or.jp (localhost.snipe.rim.or.jp [127.0.0.1]) by eddie.snipe.rim.or.jp (8.8.8/3.5Wpl7) with ESMTP id VAA00438; Wed, 10 Jun 1998 21:27:32 +0900 (JST) Message-Id: <199806101227.VAA00438@eddie.snipe.rim.or.jp> To: freebsd-stable@FreeBSD.ORG Cc: motoyuki@snipe.rim.or.jp X-Mailer: mh-e on Mule 2.3 / Emacs 19.28 Subject: Where are 2.2.5 updates? Date: Wed, 10 Jun 1998 21:27:31 +0900 From: Motoyuki Konno Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, 2.2.5-RELEASE Errata Notes: > o The appletalk stack was broken in 2.2.5 and, if you plan to run > appletalk, you should apply the following patch: > > ftp://ftp.freebsd.org/pub/FreeBSD/2.2.5-RELEASE/updates/atalk.diff.2.2 Since /pub/FreeBSD/2.2.5-RELEASE directory was deleted from ftp.freebsd.org, users of 2.2.5-RELEASE can not get the patch now. Where are the update patches? Many users still use 2.2.5-RELEASE, so they still need these patches. I think the update patch files should place in ftp://ftp.freebsd.org/pub/FreeBSD/updates/X.X.X-RELEASE. --- ------------------------------------------------------------------------ Motoyuki Konno mkonno@res.yamanashi-med.ac.jp (Univ) motoyuki@snipe.rim.or.jp (Home) Yamanashi Medical University http://www.st.rim.or.jp/~motoyuki/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 06:18:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA25108 for freebsd-stable-outgoing; Wed, 10 Jun 1998 06:18:06 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA24849 for ; Wed, 10 Jun 1998 06:16:58 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id GAA18039; Wed, 10 Jun 1998 06:16:46 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Motoyuki Konno cc: freebsd-stable@FreeBSD.ORG Subject: Re: Where are 2.2.5 updates? In-reply-to: Your message of "Wed, 10 Jun 1998 21:27:31 +0900." <199806101227.VAA00438@eddie.snipe.rim.or.jp> Date: Wed, 10 Jun 1998 06:16:46 -0700 Message-ID: <18035.897484606@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Since /pub/FreeBSD/2.2.5-RELEASE directory was deleted from > ftp.freebsd.org, users of 2.2.5-RELEASE can not get the patch now. > Where are the update patches? http://ftpsearch.no is your friend! :-) I found at least 5 other sites with the 2.2.5 bits up for FTP and grabbed the updates/ directory from one of them. It's back on the ftp.freebsd.org site (see below for location). > I think the update patch files should place in > ftp://ftp.freebsd.org/pub/FreeBSD/updates/X.X.X-RELEASE. I agree, done! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 06:21:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA26080 for freebsd-stable-outgoing; Wed, 10 Jun 1998 06:21:58 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA26039 for ; Wed, 10 Jun 1998 06:21:53 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [208.2.87.10] (user10.dataplex.net [208.2.87.10]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id IAA13803; Wed, 10 Jun 1998 08:21:01 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <17847.897463951@time.cdrom.com> References: Your message of "Wed, 10 Jun 1998 02:12:28 -0300." <199806100512.CAA08890@roma.coe.ufrj.br> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 10 Jun 1998 08:17:01 -0500 To: "Jordan K. Hubbard" From: Richard Wackerbarth Subject: Re: kernel compile problem Cc: Joao Carlos Mendes Luis , lcremean@tidalwave.net, stuart@internationalschool.co.uk, eivind@yes.no, gibbs@plutotech.com, stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:32 AM -0500 6/10/98, Jordan K. Hubbard wrote: >> The big diference is that config can not be used to compile userland >> programs. Although Eivind talked about userland source configuration, >> config will still be only a source tree tool, I think. There's no need >> to have config around in /usr/sbin. > >I actually have to agree. Having config/ not come along with the ksrc >distribution or get updated as part of src-sys with cvsup I think that the necessity to distribute config as a part of the kernel sources is something upon which there is no disagreement. The question about where to put those sources is a different matter. I argue that, since the tool is a userland program, /usr/sbin is the appropriate place for it to reside. Because of compile time options, etc. it does not belong in the src/sys subtree. The fact that its usefulness is of limited scope does not change its fundamental nature. There is a large set of tools which are needed to build a kernel. A binary version of each of them is distributed in the release. If any of them change, and the revised version is necessary to properly compile the latest version of the kernel, then arrangements need to be made to distribute those changes along with the changes to the kernel. However, this does not imply that the sources for the tool should be mixed with those of the kernel. The organization of the source tree needs to be determined by the structure of the system it represents. It should not be driven by the distribution mechanism. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 06:35:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA29704 for freebsd-stable-outgoing; Wed, 10 Jun 1998 06:35:38 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from psv.oss.uswest.net (psv.oss.uswest.net [204.147.85.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA29683 for ; Wed, 10 Jun 1998 06:35:32 -0700 (PDT) (envelope-from greg@psv.oss.uswest.net) Received: (from greg@localhost) by psv.oss.uswest.net (8.8.8/8.8.5) id IAA16264; Wed, 10 Jun 1998 08:33:43 -0500 (CDT) From: "Greg Rowe" Message-Id: <9806101333.ZM16262@psv.oss.uswest.net> Date: Wed, 10 Jun 1998 13:33:42 +0000 In-Reply-To: "Craig Shrimpton" "Anyone know what this SCSI error is about?" (Jun 9, 5:21pm) References: <00aa01bd93ec$a118bd80$02dd71d1@fargo.os.com> X-Mailer: Z-Mail (3.2.1 10apr95) To: "Craig Shrimpton" , Subject: Re: Anyone know what this SCSI error is about? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is a known problem with the Adaptec 2940UW's that report "rev 1". Justin is trying to get info out of Adaptec as to what the real issues are. Check the card, and the AIC chip should have a white label marking it as revision "E". Either replace the card with a Revision "D" or lower or set the transfer rate to the drives to 10MBS. That's the only option so far. There don't seem to be many revision "E's" in the channels, so it shouldn't be hard to find a good one. Greg On Jun 9, 5:21pm, Craig Shrimpton wrote: > Subject: Anyone know what this SCSI error is about? > My stable system has been running great except for this incident. I have > all Adaptec options enabled and the system is barely loaded. The machine > ran for several months with no ahc options and no errors so I'm wondering if > this is a software issue. > > Thanks, > > Craig > > The error: > > Jun 6 03:32:57 orion /kernel: sd0(ahc0:0:0): SCB 0x1 - timed out in dataout > phase, SCSISIGI == 0xe6 > Jun 6 03:33:22 orion /kernel: SEQADDR = 0x127 SCSISEQ = 0x12 SSTAT0 = 0x2 > SSTAT1 = 0x13 > Jun 6 03:33:22 orion /kernel: Ordered Tag queued > Jun 6 03:33:22 orion /kernel: sd0(ahc0:0:0): SCB 0x0 timedout while > recovery in progress > Jun 6 03:33:22 orion /kernel: sd0(ahc0:0:0): SCB 0x2 timedout while > recovery in progress > Jun 6 03:33:22 orion /kernel: sd0(ahc0:0:0): SCB 0x3 timedout while > recovery in progress > Jun 6 03:33:22 orion /kernel: sd0(ahc0:0:0): SCB 0x1 - timed out in dataout > phase, SCSISIGI == 0xe6 > Jun 6 03:33:22 orion /kernel: SEQADDR = 0x127 SCSISEQ = 0x12 SSTAT0 = 0x2 > SSTAT1 = 0x13 > Jun 6 03:33:22 orion /kernel: sd0(ahc0:0:0): abort message in message > buffer > Jun 6 03:33:22 orion /kernel: sd0(ahc0:0:0): SCB 0x0 - timed out in dataout > phase, SCSISIGI == 0xf6 > Jun 6 03:33:22 orion /kernel: SEQADDR = 0x127 SCSISEQ = 0x12 SSTAT0 = 0x2 > SSTAT1 = 0x13 > Jun 6 03:33:22 orion /kernel: sd0(ahc0:0:0): no longer in timeout > Jun 6 03:33:23 orion /kernel: sd0(ahc0:0:0): no longer in timeout > Jun 6 03:33:23 orion /kernel: ahc0: Issued Channel A Bus Reset. 4 SCBs > aborted > Jun 6 03:33:23 orion /kernel: sd0(ahc0:0:0): SCB 0x3 - timed out while > idle, LASTPHASE == 0x1, SCSISIGI == 0x > Jun 6 03:33:23 orion /kernel: SEQADDR = 0x175 SCSISEQ = 0x12 SSTAT0 = 0x2 > SSTAT1 = 0x0 > Jun 6 03:33:23 orion /kernel: Ordered Tag queued > Jun 6 03:33:23 orion /kernel: sd0(ahc0:0:0): SCB 0x2 timedout while > recovery in progress > Jun 6 03:33:23 orion /kernel: sd0(ahc0:0:0): SCB 0x1 timedout while > recovery in progress > Jun 6 03:33:23 orion /kernel: sd0(ahc0:0:0): SCB 0x0 timedout while > recovery in progress > Jun 6 03:33:23 orion /kernel: sd0(ahc0:0:0): SCB 0x3 - timed out while > idle, LASTPHASE == 0x1, SCSISIGI == 0x > Jun 6 03:33:23 orion /kernel: SEQADDR = 0x175 SCSISEQ = 0x12 SSTAT0 = 0x2 > SSTAT1 = 0x0 > Jun 6 03:33:23 orion /kernel: sd0(ahc0:0:0): Queueing an Abort SCB > Jun 6 03:33:23 orion /kernel: sd0(ahc0:0:0): SCB 0x3 - timed out while > idle, LASTPHASE == 0x1, SCSISIGI == 0x > Jun 6 03:33:23 orion /kernel: SEQADDR = 0x175 SCSISEQ = 0x12 SSTAT0 = 0x2 > SSTAT1 = 0x0 > Jun 6 03:33:23 orion /kernel: sd0(ahc0:0:0): no longer in timeout > Jun 6 03:33:23 orion /kernel: ahc0: Issued Channel A Bus Reset. 5 SCBs > aborted > Jun 6 03:33:23 orion /kernel: sd0(ahc0:0:0): UNIT ATTENTION asc:29,0 > Jun 6 03:33:23 orion /kernel: sd0(ahc0:0:0): Power on, reset, or bus > device reset occurred field replaceable > Jun 6 03:33:23 orion /kernel: , retries:2 > > > My dmesg: > > Copyright (c) 1992-1998 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > > FreeBSD 2.2.6-STABLE #0: Mon May 18 17:53:01 EDT 1998 > root@orion.os.com:/usr/src/sys/compile/ORION > CPU: Pentium Pro (265.91-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x633 Stepping=3 > > Features=0x80fbff MOV,MMX> > real memory = 268435456 (262144K bytes) > avail memory = 260911104 (254796K bytes) > Probing for devices on PCI bus 0: > chip0 rev 2 on pci0:0:0 > chip1 rev 1 on pci0:7:0 > chip2 rev 0 on pci0:7:1 > pci0:7:2: Intel Corporation, device=0x7020, class=serial, subclass=0x03 int > d irq 9 [no driver assigned] > de0 rev 35 int a irq 11 on pci0:10:0 > de0: SMC 8432BT 21040 [10Mb/s] pass 2.3 > de0: address 00:00:c0:0f:41:0f > ahc0 rev 1 int a irq 10 on pci0:13:0 > ahc0: aic7880 Wide Channel, SCSI Id=7, 16/255 SCBs > ahc0 waiting for scsi devices to settle > ahc0: target 0 Tagged Queuing Device > (ahc0:0:0): "SEAGATE ST19171W 0024" type 0 fixed SCSI 2 > sd0(ahc0:0:0): Direct-Access 8683MB (17783112 512 byte sectors) > vga0 rev 6 int a irq 11 on pci0:14:0 > Probing for devices on the ISA bus: > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: VGA color <16 virtual consoles, flags=0x0> > sio0 at 0x3f8-0x3ff irq 4 on isa > sio0: type 16550A > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > lpt0 at 0x378-0x37f irq 7 on isa > lpt0: Interrupt-driven port > lp0: TCP/IP capable interface > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: FIFO enabled, 8 bytes threshold > fd0: 1.44MB 3.5in > npx0 flags 0x1 on motherboard > npx0: INT 16 interface > de0: enabling 10baseT port > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message >-- End of excerpt from Craig Shrimpton -- Greg Rowe US WEST - !NTERACT Internet Services "To err is human, to really foul up requires the root password." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 07:23:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08756 for freebsd-stable-outgoing; Wed, 10 Jun 1998 07:23:24 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08706 for ; Wed, 10 Jun 1998 07:23:08 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id OAA27883; Wed, 10 Jun 1998 14:22:59 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id QAA03625; Wed, 10 Jun 1998 16:22:59 +0200 (MET DST) Message-ID: <19980610162258.38342@follo.net> Date: Wed, 10 Jun 1998 16:22:58 +0200 From: Eivind Eklund To: "Jordan K. Hubbard" , stable@FreeBSD.ORG Subject: Re: Anyone running the linux emulation as an LKM under 2.2-stable? References: <199806100817.BAA18128@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199806100817.BAA18128@time.cdrom.com>; from Jordan K. Hubbard on Wed, Jun 10, 1998 at 01:17:46AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jun 10, 1998 at 01:17:46AM -0700, Jordan K. Hubbard wrote: > The reason I ask is that I'm no longer able to do so. All linux binaries > coredump immediately if I attempt to use the Linux emulator as an LKM but > work *fine* if I compile the kernel with COMPAT_LINUX and don't load > the Linux LKM (actually, I can do _both_ but the LKM version isn't used > if it's compiled in - perhaps a bug to allow both to be loaded like this?). > > Anyone even seeing the same symptoms? I've seen reports of this after the signal-patches went in. However, I've not yet seen anybody be screwed if they had a correctly installed machine (ie, all of the cases were resolvable). If the kernel and the LKM need to be in sync WRT those patches, it should AFAIK be fine. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 07:30:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10341 for freebsd-stable-outgoing; Wed, 10 Jun 1998 07:30:08 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10201 for ; Wed, 10 Jun 1998 07:29:56 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id HAA18595; Wed, 10 Jun 1998 07:29:52 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Eivind Eklund cc: stable@FreeBSD.ORG Subject: Re: Anyone running the linux emulation as an LKM under 2.2-stable? In-reply-to: Your message of "Wed, 10 Jun 1998 16:22:58 +0200." <19980610162258.38342@follo.net> Date: Wed, 10 Jun 1998 07:29:52 -0700 Message-ID: <18591.897488992@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've seen reports of this after the signal-patches went in. However, > I've not yet seen anybody be screwed if they had a correctly installed > machine (ie, all of the cases were resolvable). > > If the kernel and the LKM need to be in sync WRT those patches, it > should AFAIK be fine. Nope, these LKM's are absolutely in-sync I'm quite sure (I've cleaned the source and obj trees with scouring powder and rebuilt from the latest cvsup'd bits, no joy :( ). So, can I infer from this that there are people who are _currently_ using the Linux LKM, do not compile their kernels with COMPAT_LINUX, and things are just fine with them in 2.2-stable? I'd just like to have this confirmed by *one* person since the LKM used to work fine for me too, up until about a week or two ago. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 07:42:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA13185 for freebsd-stable-outgoing; Wed, 10 Jun 1998 07:42:45 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA13147 for ; Wed, 10 Jun 1998 07:42:35 -0700 (PDT) (envelope-from jfieber@indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.8/8.8.7) with SMTP id JAA13103; Wed, 10 Jun 1998 09:42:28 -0500 (EST) Date: Wed, 10 Jun 1998 09:42:28 -0500 (EST) From: John Fieber To: "Jordan K. Hubbard" cc: stable@FreeBSD.ORG Subject: Re: Anyone running the linux emulation as an LKM under 2.2-stable? In-Reply-To: <199806100817.BAA18128@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 10 Jun 1998, Jordan K. Hubbard wrote: > The reason I ask is that I'm no longer able to do so. All linux binaries > coredump immediately if I attempt to use the Linux emulator as an LKM but > work *fine* if I compile the kernel with COMPAT_LINUX and don't load > Anyone even seeing the same symptoms? No. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 07:44:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA13715 for freebsd-stable-outgoing; Wed, 10 Jun 1998 07:44:31 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from solar.os.com (root@solar.os.com [209.113.221.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA13635 for ; Wed, 10 Jun 1998 07:44:19 -0700 (PDT) (envelope-from craigs@os.com) Received: from fargo (fargo.os.com [209.113.221.2]) by solar.os.com (8.7/8.7.0) with SMTP id KAA11311; Wed, 10 Jun 1998 10:44:32 -0400 Message-ID: <001601bd947e$1b9d3680$02dd71d1@fargo.os.com> From: "Craig Shrimpton" To: "Greg Rowe" , Subject: Re: Anyone know what this SCSI error is about? Date: Wed, 10 Jun 1998 10:43:18 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yep. It's an "E" all right. Is the fix being actively worked on or should I dump the card? Thanks, Craig > There is a known problem with the Adaptec 2940UW's that report "rev 1". Justin >is trying to get info out of Adaptec as to what the real issues are. Check the To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 07:52:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15886 for freebsd-stable-outgoing; Wed, 10 Jun 1998 07:52:48 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from couatl.uchicago.edu (couatl.uchicago.edu [128.135.21.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA15861 for ; Wed, 10 Jun 1998 07:52:40 -0700 (PDT) (envelope-from sfarrell@couatl.uchicago.edu) Received: (from sfarrell@localhost) by couatl.uchicago.edu (8.9.0/8.9.0) id JAA04827; Wed, 10 Jun 1998 09:52:34 -0500 (CDT) To: "Jordan K. Hubbard" Cc: stable@FreeBSD.ORG Subject: Re: Anyone running the linux emulation as an LKM under 2.2-stable? References: <199806100817.BAA18128@time.cdrom.com> From: stephen farrell Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: 10 Jun 1998 09:52:33 -0500 In-Reply-To: "Jordan K. Hubbard"'s message of "Wed, 10 Jun 1998 01:17:46 -0700 (PDT)" Message-ID: <8790n5ux5a.fsf@couatl.uchicago.edu> Lines: 19 X-Mailer: Gnus v5.6.9/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" writes: > The reason I ask is that I'm no longer able to do so. All linux binaries > coredump immediately if I attempt to use the Linux emulator as an LKM but > work *fine* if I compile the kernel with COMPAT_LINUX and don't load > the Linux LKM (actually, I can do _both_ but the LKM version isn't used > if it's compiled in - perhaps a bug to allow both to be loaded like this?). > > Anyone even seeing the same symptoms? I've seen this and panic's b/c the lkms of a 2.2.6-stable were older than the kernel of 2.2.6-stable. I'm not seeing these symptoms right now. -- Steve Farrell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 08:02:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18391 for freebsd-stable-outgoing; Wed, 10 Jun 1998 08:02:16 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from psv.oss.uswest.net (psv.oss.uswest.net [204.147.85.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18311 for ; Wed, 10 Jun 1998 08:02:02 -0700 (PDT) (envelope-from greg@psv.oss.uswest.net) Received: (from greg@localhost) by psv.oss.uswest.net (8.8.8/8.8.5) id KAA16653; Wed, 10 Jun 1998 10:00:13 -0500 (CDT) From: "Greg Rowe" Message-Id: <9806101500.ZM16651@psv.oss.uswest.net> Date: Wed, 10 Jun 1998 15:00:12 +0000 In-Reply-To: "Craig Shrimpton" "Re: Anyone know what this SCSI error is about?" (Jun 10, 10:43am) References: <001601bd947e$1b9d3680$02dd71d1@fargo.os.com> X-Mailer: Z-Mail (3.2.1 10apr95) To: "Craig Shrimpton" , Subject: Re: Anyone know what this SCSI error is about? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Justin may know better, but we do know that Adaptec had at least some problems with that Rev. We buy a lot of Adaptec cards and the bad ones only seemed to be in the channels for a short period of time late last year. We just asked our vendor to exchange the bad Rev E cards with Rev D which seem to be the only ones in the channels now. Greg On Jun 10, 10:43am, Craig Shrimpton wrote: > Subject: Re: Anyone know what this SCSI error is about? > Yep. It's an "E" all right. Is the fix being actively worked on or should > I dump the card? > > Thanks, > > Craig > > > > There is a known problem with the Adaptec 2940UW's that report "rev 1". > Justin > >is trying to get info out of Adaptec as to what the real issues are. Check > the > >-- End of excerpt from Craig Shrimpton -- Greg Rowe US WEST - !NTERACT Internet Services "To err is human, to really foul up requires the root password." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 08:08:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19860 for freebsd-stable-outgoing; Wed, 10 Jun 1998 08:08:50 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from passer.osg.gov.bc.ca (0@passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19815 for ; Wed, 10 Jun 1998 08:08:31 -0700 (PDT) (envelope-from cy@cschuber.net.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.0/8.6.10) id IAA24216; Wed, 10 Jun 1998 08:08:13 -0700 (PDT) Received: from cschuber.net.gov.bc.ca(142.31.240.113), claiming to be "cwsys.cwsent.com" via SMTP by passer.osg.gov.bc.ca, id smtpdaamcla; Wed Jun 10 08:07:40 1998 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.0/8.6.10) id IAA05083; Wed, 10 Jun 1998 08:05:38 -0700 (PDT) Message-Id: <199806101505.IAA05083@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdDk5070; Wed Jun 10 08:04:53 1998 X-Mailer: exmh version 2.0.2 2/24/98 Reply-to: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: cy To: Jeff Kletsky cc: freebsd-stable@FreeBSD.ORG Subject: Re: rc.firewall and ipfw commands In-reply-to: Your message of "Sun, 07 Jun 1998 12:54:29 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Jun 1998 08:04:50 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In my firewall configurations I modify rc.firewall to recognize a "user" firewall type (for user defined) and specify firewall_type="user" in my rc.conf. The "user" firewall type executes /usr/local/etc/rc.firewall.local instead of one of the predefined firewall types in rc.firewall. This may be a handy feature in the stock FreeBSD rc.firewall. If anyone wishes I can submit a PR to have this included in the FreeBSD distribution. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: cschuber@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Government of BC > After building from 2.2.6-STABLE I came across a bit of a puzzle with the > apparent loss of DNS and a lot of other services on my machine. The > "problem" is that the rule numbers for the hard-wired rules in rc.firewall > have been changed: > > $fwcmd add 100 pass all from any to any via lo0 > $fwcmd add 200 deny all from any to 127.0.0.0/8 > > Now, if you are using the supplied named firewall options, you're ok. If > you are using a file containing commands, or other utilities which modify > the firewall, you could be in trouble (I happen to use the > previously-unused rule 100 to monitor what's bringing up dial-on-demand > ppp, so it is routinely deleted and added as the link changes state). > > Short-term fix: > --------------- > Leave the rules in place so the named firewall types work. > Change rc.firewall to read: > > $fwcmd -f flush # because "-f flush" fails in a file* > $fwcmd ${firewall_type} > > > Long-term fix: > -------------- > > Convince the powers that be to only add the "standard" rules for the named > firewall types. > > > > Jeff > > * Including "-f flush" as the first line of the file causes the next ipfw > command in the sequence to abort execution... > > > > 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 Jun 10 08:23:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22681 for freebsd-stable-outgoing; Wed, 10 Jun 1998 08:23:14 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from passer.osg.gov.bc.ca (0@passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA22662 for ; Wed, 10 Jun 1998 08:23:04 -0700 (PDT) (envelope-from cy@cschuber.net.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.0/8.6.10) id IAA06702; Wed, 10 Jun 1998 08:23:03 -0700 (PDT) Received: from cschuber.net.gov.bc.ca(142.31.240.113), claiming to be "cwsys.cwsent.com" via SMTP by passer.osg.gov.bc.ca, id smtpdaalFBa; Wed Jun 10 08:22:47 1998 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.0/8.6.10) id IAA05119; Wed, 10 Jun 1998 08:20:39 -0700 (PDT) Message-Id: <199806101520.IAA05119@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdQw5111; Wed Jun 10 08:20:18 1998 X-Mailer: exmh version 2.0.2 2/24/98 Reply-to: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: cy To: Andreas Klemm cc: Matthew Cashdollar , freebsd-stable@FreeBSD.ORG Subject: Re: bind 8 or 4 ? In-reply-to: Your message of "Sun, 07 Jun 1998 21:59:16 +0200." <19980607215916.A7507@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Jun 1998 08:20:17 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, Jun 04, 1998 at 10:37:24AM -0500, Matthew Cashdollar wrote: > > > > Is stable going to be moving to bind 8? I am currently using 4 and > > would like to upgrade, but if it is going to be in the base system > > I'd rather wait instead of installing the port. > > I think FreeBSD-STABLE will stay at bind4. > > But where is the problem to use the bind8 port ? I installed it on one of my home machines to "experience" BIND 8, as I'm pondering doing the same at work. The upgrade was trivial. If BIND 8 was used in -stable, this would cause much of the same grief that we've just experienced with the latest round of changes that affected config and the previous changes to compatibility slices, because of the varying degrees of experience of people administering FreeBSD sites. I think that this type of upgrade should be left until 3.0 comes out. Even then a sysinstall should ask a question like "do you wish to upgrade to BIND 8?", then install the port and run the Perl script to convert any BIND 4 named.boot files to BIND 8 named.conf files. Then in 3.1 make BIND 8 the default. This should give everyone plenty of warning (though some may still not heed the warning and complain, but I guess that's life). Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: cschuber@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Government of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 08:28:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23939 for freebsd-stable-outgoing; Wed, 10 Jun 1998 08:28:08 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA23775 for ; Wed, 10 Jun 1998 08:27:49 -0700 (PDT) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es by polaris.we.lc.ehu.es (SMI-8.6/SMI-SVR4) id RAA03909; Wed, 10 Jun 1998 17:27:01 +0200 Message-ID: <357EA5C5.CF875B00@we.lc.ehu.es> Date: Wed, 10 Jun 1998 17:27:01 +0200 From: "Jose M. Alcaide" Organization: Universidad del País Vasco - Dept. Electricidad y Electrónica X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-STABLE i386) MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: stable@FreeBSD.ORG Subject: Re: Anyone running the linux emulation as an LKM under 2.2-stable? References: <199806100817.BAA18128@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: > > The reason I ask is that I'm no longer able to do so. All linux binaries > coredump immediately if I attempt to use the Linux emulator as an LKM but > work *fine* if I compile the kernel with COMPAT_LINUX and don't load > the Linux LKM (actually, I can do _both_ but the LKM version isn't used > if it's compiled in - perhaps a bug to allow both to be loaded like this?). > > Anyone even seeing the same symptoms? > I have just "made the world" ;-) using 2.2-STABLE sources fetched at Jun 10, 00:30 GMT. The Linux emulator LKM works OK for me. I'm not using COMPAT_LINUX in my kernel config file. -- JM ----------------------------------------------------------------------- Jose M. Alcaide | mailto:jose@we.lc.ehu.es Universidad del Pais Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electronica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-944647700 x2624 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 08:32:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25347 for freebsd-stable-outgoing; Wed, 10 Jun 1998 08:32:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25305 for ; Wed, 10 Jun 1998 08:32:36 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id JAA18289; Wed, 10 Jun 1998 09:27:05 -0600 (MDT) Date: Wed, 10 Jun 1998 09:27:05 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199806101527.JAA18289@narnia.plutotech.com> To: "Craig Shrimpton" cc: stable@FreeBSD.ORG Subject: Re: Anyone know what this SCSI error is about? Newsgroups: pluto.freebsd.stable In-Reply-To: <00aa01bd93ec$a118bd80$02dd71d1@fargo.os.com> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ahc0 rev 1 int a irq 10 on pci0:13:0 Your problem is that you are running a rev 1 aic7880 on a 440FX chipset. This has known problems and I'm working with Adaptec to determine more exactly what is going on and how the FreeBSD driver can work around it. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 08:44:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28132 for freebsd-stable-outgoing; Wed, 10 Jun 1998 08:44:09 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ghpc8.ihf.rwth-aachen.de (ghpc8.ihf.RWTH-Aachen.DE [134.130.90.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28042 for ; Wed, 10 Jun 1998 08:43:47 -0700 (PDT) (envelope-from tg@ghpc8.ihf.rwth-aachen.de) Received: from ghpc6.ihf.rwth-aachen.de (ghpc6.ihf.rwth-aachen.de [134.130.90.6]) by ghpc8.ihf.rwth-aachen.de (8.8.8/8.8.6) with ESMTP id RAA02901; Wed, 10 Jun 1998 17:43:26 +0200 (CEST) Received: (from tg@localhost) by ghpc6.ihf.rwth-aachen.de (8.8.8/8.8.5) id RAA03818; Wed, 10 Jun 1998 17:43:25 +0200 (CEST) To: "Jordan K. Hubbard" Cc: Eivind Eklund , stable@FreeBSD.ORG Subject: Re: Anyone running the linux emulation as an LKM under 2.2-stable? References: <18591.897488992@time.cdrom.com> From: Thomas Gellekum Date: 10 Jun 1998 17:43:25 +0200 In-Reply-To: "Jordan K. Hubbard"'s message of "Wed, 10 Jun 1998 07:29:52 -0700" Message-ID: <87emwxmfdu.fsf@ghpc6.ihf.rwth-aachen.de> Lines: 12 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" writes: > So, can I infer from this that there are people who are _currently_ > using the Linux LKM, do not compile their kernels with COMPAT_LINUX, > and things are just fine with them in 2.2-stable? I'd just like to have > this confirmed by *one* person since the LKM used to work fine for me > too, up until about a week or two ago. :-) _One_ or _two_? My current -stable system was built on May 27, and the Linux LKM works fine, and no, I've never used COMPAT_LINUX. tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 08:48:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29190 for freebsd-stable-outgoing; Wed, 10 Jun 1998 08:48:07 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gateman.zeus.leitch.com (gateman.zeus.leitch.com [204.187.61.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29115 for ; Wed, 10 Jun 1998 08:47:50 -0700 (PDT) (envelope-from woods@tap.zeus.leitch.com) Received: from zeus.leitch.com (tap.zeus.leitch.com [204.187.61.10]) by gateman.zeus.leitch.com (8.8.5/8.7.3/1.0) with ESMTP id LAA11417 for ; Wed, 10 Jun 1998 11:47:07 -0400 (EDT) Received: from brain.zeus.leitch.com (brain.zeus.leitch.com [204.187.61.32]) by zeus.leitch.com (8.7.5/8.7.3/1.0) with ESMTP id LAA00356 for ; Wed, 10 Jun 1998 11:47:14 -0400 (EDT) Received: (from woods@localhost) by brain.zeus.leitch.com (8.8.8/8.8.8) id LAA24462; Wed, 10 Jun 1998 11:47:14 -0400 (EDT) (envelope-from woods@tap.zeus.leitch.com) Date: Wed, 10 Jun 1998 11:47:14 -0400 (EDT) Message-Id: <199806101547.LAA24462@brain.zeus.leitch.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: woods@zeus.leitch.com (Greg A. Woods) To: freebsd-stable@FreeBSD.ORG Subject: Re: kernel compile problem In-Reply-To: Richard Wackerbarth's message of "Wed, June 10, 1998 08:17:01 -0500" regarding "Re: kernel compile problem" id References: <199806100512.CAA08890@roma.coe.ufrj.br> <17847.897463951@time.cdrom.com> X-Mailer: VM 6.45 under Emacs 20.2.1 Reply-To: freebsd-stable@FreeBSD.ORG Organization: Planix, Inc.; Toronto, Ontario; Canada Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Wed, June 10, 1998 at 08:17:01 (-0500), Richard Wackerbarth wrote: ] > Subject: Re: kernel compile problem > > I argue that, since the tool is a userland program, /usr/sbin is the > appropriate > place for it to reside. Because of compile time options, etc. it does not > belong in the src/sys subtree. The fact that its usefulness is of limited scope > does not change its fundamental nature. I think your argument can go one step further too. Within the stable release I think it would shake things up a whole lot more to move a tool about esp. if moving it meant not installing it in /usr/sbin/ any more. In any case, the fix is indeed quite trivial -- just include the directory src/usr.sbin/config and all its contents in all of the kernel-only source distributions. As I've said already, this *does* work extremely well in NetBSD-land. The sudden appearance of config(8) in the kenel distribution might remind all those people who've had trouble building kernels that this tool is an integral part of the kernel build process and any changes to that process require that both the tool and kernel sources that integrate with its output have to be kept 100% in sync. BTW, one thing that's never been done before, but which might be a good idea, would be to introduce backward compatability into config(8) so that the same binary could build all kernel releases. This isn't such a big problem for those of us who use something like CVS to track sources since we can ensure that we always have corresponding copies of the kernel and config(8) in our work areas, but for those that don't I can't think of a better idea. -- Greg A. Woods +1 416 443-1734 VE3TCP Planix, Inc. ; Secrets of the Weird To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 08:56:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01585 for freebsd-stable-outgoing; Wed, 10 Jun 1998 08:56:03 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from SCIENCE-GUY.npt.nuwc.navy.mil (SCIENCE-GUY.NPT.NUWC.NAVY.MIL [129.190.139.47]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01489 for ; Wed, 10 Jun 1998 08:55:42 -0700 (PDT) (envelope-from tod@SCIENCE-GUY.npt.nuwc.navy.mil) Received: from SCIENCE-GUY.npt.nuwc.navy.mil (LOCALHOST [127.0.0.1]) by SCIENCE-GUY.npt.nuwc.navy.mil (8.8.8/8.8.7) with ESMTP id LAA01525 for ; Wed, 10 Jun 1998 11:58:14 -0400 (EDT) Message-Id: <199806101558.LAA01525@SCIENCE-GUY.npt.nuwc.navy.mil> To: stable@FreeBSD.ORG Subject: Re: Anyone running the linux emulation as an LKM under 2.2-stable? In-reply-to: Your message of "Wed, 10 Jun 1998 01:17:46 PDT." <199806100817.BAA18128@time.cdrom.com> Date: Wed, 10 Jun 1998 11:58:14 -0400 From: Tod Luginbuhl Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan Hubbard asked... >The reason I ask is that I'm no longer able to do so. All linux binaries >coredump immediately if I attempt to use the Linux emulator as an LKM but >work *fine* if I compile the kernel with COMPAT_LINUX and don't load >the Linux LKM (actually, I can do _both_ but the LKM version isn't used >if it's compiled in - perhaps a bug to allow both to be loaded like this?). I've been using the LKM linux emulation under 2.2.6 with a kernel and buildworld from 29 May 1998. I haven't had any problems running Mathematica or Matlab (elf binaries), but my linux emulation is started during the boot process since I have the option set in rc.conf. I just checked, and I do not have the COMPAT_LINUX option set in my kernel configuration file. Tod -------------------------------------------------------------------------- Tod Luginbuhl email: t.e.luginbuhl@ieee.org Code 2121 luginbuhl@npt.nuwc.navy.mil Naval Undersea Warfare Center 1176 Howell Street Telephone: (401) 832-8241 Newport, Rhode Island FAX: (401) 841-7453 USA "Don't argue with drunks and fanatics!" -- Sun Wolf (Barbara Hambly) -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 09:01:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03033 for freebsd-stable-outgoing; Wed, 10 Jun 1998 09:01:39 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from manchester.genrad.com (x191.genrad.co.uk [195.99.3.191] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02981 for ; Wed, 10 Jun 1998 09:01:15 -0700 (PDT) (envelope-from swindellsr@genrad.co.uk) Date: Wed, 10 Jun 1998 09:01:15 -0700 (PDT) Message-Id: <199806101601.JAA02981@hub.freebsd.org> Received: from CDP275.uk.genrad.com by manchester.genrad.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1458.49) id M4QGHQ01; Wed, 10 Jun 1998 17:00:39 +0100 From: Robert Swindells To: jkh@time.cdrom.com CC: stable@FreeBSD.ORG In-reply-to: <18591.897488992@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: Anyone running the linux emulation as an LKM under 2.2-stable? Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >So, can I infer from this that there are people who are _currently_ >using the Linux LKM, do not compile their kernels with COMPAT_LINUX, >and things are just fine with them in 2.2-stable? I'd just like to have >this confirmed by *one* person since the LKM used to work fine for me >too, up until about a week or two ago. :-) I'll cvsup and try it. I use acroread and acl by loading the LKM, but I can live without either if it breaks. Robert Swindells ---------------------------------- Robert Swindells - GenRad Ltd. rjs@genrad.co.uk - Work rjs@fdy2.demon.co.uk - Home To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 09:17:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06849 for freebsd-stable-outgoing; Wed, 10 Jun 1998 09:17:36 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from SCIENCE-GUY.npt.nuwc.navy.mil (SCIENCE-GUY.NPT.NUWC.NAVY.MIL [129.190.139.47]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06672 for ; Wed, 10 Jun 1998 09:16:50 -0700 (PDT) (envelope-from tod@SCIENCE-GUY.npt.nuwc.navy.mil) Received: from SCIENCE-GUY.npt.nuwc.navy.mil (LOCALHOST [127.0.0.1]) by SCIENCE-GUY.npt.nuwc.navy.mil (8.8.8/8.8.7) with ESMTP id MAA01549 for ; Wed, 10 Jun 1998 12:19:16 -0400 (EDT) Message-Id: <199806101619.MAA01549@SCIENCE-GUY.npt.nuwc.navy.mil> To: stable@FreeBSD.ORG Subject: Re: Anyone know what this SCSI error is about? In-reply-to: Your message of "Tue, 09 Jun 1998 17:21:55 EDT." <00aa01bd93ec$a118bd80$02dd71d1@fargo.os.com> Date: Wed, 10 Jun 1998 12:19:15 -0400 From: Tod Luginbuhl Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Craig Shrimpton writes... >My stable system has been running great except for this incident. I have >all Adaptec options enabled and the system is barely loaded. The machine >ran for several months with no ahc options and no errors so I'm wondering if >this is a software issue. > >The error: > >Jun 6 03:32:57 orion /kernel: sd0(ahc0:0:0): SCB 0x1 - timed out in dataout >phase, SCSISIGI == 0xe6 >Jun 6 03:33:22 orion /kernel: SEQADDR = 0x127 SCSISEQ = 0x12 SSTAT0 = 0x2 >SSTAT1 = 0x13 >Jun 6 03:33:22 orion /kernel: Ordered Tag queued > I had the same problem happen to me yesterday. I had the CPU pegged crunching numbers, but the system wasn't doing anything else (I have a Pentium-Pro 200mhz machine with 128 mega of RAM). My Adaptec 2940UW board is "old" --- revision A. I don't have any ultra or wide SCSI devices attached to this card. I set the options AHC_TAGENABLE and AHC_SCBPAGING_ENABLE set in my kernel configuration file about a month ago, and this is the first problem I've seen (I had other problems with the 2940 over a year ago). I am going to search through the mail archives, because I recall seeing something about this. I added these two options after reading a mail message about them and some of their associated issues. I wasn't going to send a message to the list until I had exhausted the archives, but I thought I'd let you know your not alone. Tod -------------------------------------------------------------------------- Tod Luginbuhl email: t.e.luginbuhl@ieee.org Code 2121 luginbuhl@npt.nuwc.navy.mil Naval Undersea Warfare Center 1176 Howell Street Telephone: (401) 832-8241 Newport, Rhode Island FAX: (401) 841-7453 USA "Don't argue with drunks and fanatics!" -- Sun Wolf (Barbara Hambly) -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 09:22:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08084 for freebsd-stable-outgoing; Wed, 10 Jun 1998 09:22:58 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns11.rim.or.jp (root@ns11.rim.or.jp [202.247.130.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07944 for ; Wed, 10 Jun 1998 09:22:29 -0700 (PDT) (envelope-from motoyuki@snipe.rim.or.jp) Received: from rayearth.rim.or.jp (rayearth.rim.or.jp [202.247.130.242]) by ns11.rim.or.jp (8.8.5/3.5Wpl2-ns11/RIMNET-2) with ESMTP id BAA05312; Thu, 11 Jun 1998 01:22:18 +0900 (JST) Received: (from uucp@localhost) by rayearth.rim.or.jp (8.8.5/3.5Wpl2-uucp1/RIMNET) with UUCP id BAA16232; Thu, 11 Jun 1998 01:22:17 +0900 (JST) Received: from mserver.snipe.rim.or.jp (localhost.snipe.rim.or.jp [127.0.0.1]) by mserver.snipe.rim.or.jp (8.8.8/3.6W) with ESMTP id BAA21843; Thu, 11 Jun 1998 01:17:38 +0900 (JST) Message-Id: <199806101617.BAA21843@mserver.snipe.rim.or.jp> To: "Jordan K. Hubbard" Cc: Motoyuki Konno , freebsd-stable@FreeBSD.ORG Subject: Re: Where are 2.2.5 updates? X-Mailer: mh-e on Mule 2.3 / Emacs 19.28 Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit References: <18035.897484606@time.cdrom.com> In-reply-to: Message from jkh@time.cdrom.com of <18035.897484606@time.cdrom.com> Date: Thu, 11 Jun 1998 01:17:38 +0900 From: Motoyuki Konno Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, "Jordan K. Hubbard" wrote: > > Since /pub/FreeBSD/2.2.5-RELEASE directory was deleted from > > ftp.freebsd.org, users of 2.2.5-RELEASE can not get the patch now. > > Where are the update patches? > > http://ftpsearch.no is your friend! :-) I found at least 5 other sites > with the 2.2.5 bits up for FTP and grabbed the updates/ directory from > one of them. It's back on the ftp.freebsd.org site (see below for location). > > > I think the update patch files should place in > > ftp://ftp.freebsd.org/pub/FreeBSD/updates/X.X.X-RELEASE. > > I agree, done! I think Errata Notes in the FreeBSD WWW (www/data/releases/*/errata.sgml) also need to update the description of update patch files. --- ------------------------------------------------------------------------ Motoyuki Konno mkonno@res.yamanashi-med.ac.jp (Univ) motoyuki@snipe.rim.or.jp (Home) Yamanashi Medical University http://www.st.rim.or.jp/~motoyuki/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 09:44:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14235 for freebsd-stable-outgoing; Wed, 10 Jun 1998 09:44:18 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from obiwan.TerraNova.net (root@obiwan.TerraNova.net [205.152.191.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14124 for ; Wed, 10 Jun 1998 09:43:40 -0700 (PDT) (envelope-from bofh@terranova.net) Received: from guenhwyvar (tog@guenhwyvar.TerraNova.net [205.152.191.4]) by obiwan.TerraNova.net (8.8.8/TNN/3.1) with SMTP id MAA20316; Wed, 10 Jun 1998 12:43:43 -0400 (EDT) Message-ID: <357EB726.2F3F@terranova.net> Date: Wed, 10 Jun 1998 12:41:10 -0400 From: Travis Mikalson Organization: TerraNovaNet X-Mailer: Mozilla 3.04 (Win95; I) MIME-Version: 1.0 To: Greg Rowe CC: freebsd-stable@FreeBSD.ORG Subject: Re: Anyone know what this SCSI error is about? References: <00aa01bd93ec$a118bd80$02dd71d1@fargo.os.com> <9806101333.ZM16262@psv.oss.uswest.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Rowe wrote: > > There is a known problem with the Adaptec 2940UW's that report "rev 1". Justin > is trying to get info out of Adaptec as to what the real issues are. Check the > card, and the AIC chip should have a white label marking it as revision "E". > Either replace the card with a Revision "D" or lower or set the transfer rate > to the drives to 10MBS. That's the only option so far. There don't seem to be > many revision "E's" in the channels, so it shouldn't be hard to find a good > one. > > Greg Hmm how about this one (this machine is my playbox running -CURRENT so I'm guessing the rev output is a bit different than 2.2.x): ahc0: rev 0x01 int a irq 19 on pci0.11.0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16/255 SCBs That gives me those problems ONLY when I stress the drive to the absolute max with dd and silly benchmarks. Looks like rev 0x01 means I should exchange the card for a D. No mystery there. I've never ever seen the aborts and timeouts in the 155 days this one (also a -CURRENT box from.. well.. 156 days ago) has been up which is a lot more than I can say for the next box :( ahc0: rev 0x00 int a irq 10 on pci0.10.0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16/255 SCBs this is the last one with a 2940UW in it where there have been so many kernel messages (most of them from the SCSI timeouts, aborts, retries) that I can no longer see the beginning of the dmesg... I see it's a Rev C, not an E, but I still have the problems with this one that have been described earlier: sd1(ahc0:2:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x5 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Ordered Tag queued sd1(ahc0:2:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x4 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa sd1(ahc0:2:0): Queueing an Abort SCB sd1(ahc0:2:0): Abort Message Sent sd1(ahc0:2:0): SCB 6 - Abort Tag Completed. sd1(ahc0:2:0): no longer in timeout Ordered Tag sent This one's been up for 85 days and is running 2.2.6-BETA from mid-March but has had this problem since upgrading from 2.1.5 to 2.2.[1 I think] Same symptoms with three different cables and without the AHC_ options. All of these machines have all the AHC_ options enabled right now and no CAM. -T -- TerraNovaNet Internet Services - Key Largo, FL Voice: (305)453-4011 Fax: (305)451-5991 http://www.terranova.net/ ---------------------------------------------- And Jesus said unto them, "And whom do you say that I am?" They replied, "You are the eschatological manifestation of the ground of our being, the ontological foundation of the context of our very selfhood revealed." And Jesus replied, "What?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 09:47:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14881 for freebsd-stable-outgoing; Wed, 10 Jun 1998 09:47:13 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from lepton.nuc.net (root@lepton.nuc.net [204.49.61.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14753 for ; Wed, 10 Jun 1998 09:46:40 -0700 (PDT) (envelope-from wheelman@nuc.net) Received: from electron.nuc.net (dhcp3.nuc.net [204.49.61.51]) by lepton.nuc.net (8.8.8/8.7.3) with SMTP id LAA21516 for ; Wed, 10 Jun 1998 11:46:34 -0500 (CDT) From: "Jaime Bozza" To: Subject: Proftpd questions Date: Wed, 10 Jun 1998 11:44:07 -0500 Message-ID: <000101bd948e$fc18ea00$333d31cc@electron.nuc.net> 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 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm not sure if this is the most perfect place for this question, but it sort of relates to some possible updates to the stable branch. I noticed that the proftpd port is still set at 1.0.0, when a 1.0.3pl1 and a 1.1.3pre1 (development branch) are available. As I am using proftpd here I figured I'd just manually update. While 1.0.3pl1 compiled fine (with one new minor correction and using the 1.0.0 port patches as a base), 1.1.3pre1 is giving me some problem. It seems that as of 1.1.1 (I believe), proftpd is using the glob() function. Unfortunately, while they include glob.c and glob.h with proftpd, configure sees that FreeBSD already has the function (and include file), and tries to use it. The problem is that the glob.h (with proftpd) is dated 1997, while the FreeBSD one is dated 1993. (I'm using the copyright date at the top for reference) Looking through the code, it seems this function has changed a bit. What's the possibility of this being updated in stable? Is the new glob() function from gcc 2.8.x? Thanks for your help. Jaime Bozza Nucleus Communications, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 09:56:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17003 for freebsd-stable-outgoing; Wed, 10 Jun 1998 09:56:53 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [207.149.232.62] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16947 for ; Wed, 10 Jun 1998 09:56:21 -0700 (PDT) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.8/8.8.8) id JAA14423; Wed, 10 Jun 1998 09:55:24 -0700 (PDT) (envelope-from rgrimes) From: "Rodney W. Grimes" Message-Id: <199806101655.JAA14423@GndRsh.aac.dev.com> Subject: Re: Processor upgrade, minor problem. In-Reply-To: from Sean-Paul Rees at "Jun 9, 98 08:50:15 pm" To: sean@dreamfire.net (Sean-Paul Rees) Date: Wed, 10 Jun 1998 09:55:24 -0700 (PDT) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just upgraded from my Pentium 133, to the Evergreen MxPro > 200MHz MMX- and FreeBSD doesn't echo it's features like it did on the > P133. > This is what I get: > > FreeBSD 2.2.6-STABLE #0: Tue Jun 9 19:31:07 PDT 1998 > root@dreamer.dreamfire.net:/usr/src/sys/compile/DREAMER > CPU: Pentium (199.43-MHz 586-class CPU) > Origin = "CentaurHauls" Id = 0x540 ^^^^^^^^^^^^^ You most likely (reason I say ``most likely'' is below) have an IDT/Centaur CPU chip, which FreeBSD has not been updated to fully understand, and this does not print the Features values. One interesting thing about the IDT chips is that it is possible to reprogram the Origin string, and some one else may copy this miss feature in the future. If you do a yahoo search on the above ID string you'll find a few web sites that talk about this misfeature. > real memory = 100663296 (98304K bytes) > > instead of: > > FreeBSD 2.2.6-STABLE #0: Sat May 16 23:45:40 PDT 1998 > root@dreamer.dreamfire.net:/usr/src/sys/compile/DREAMER > CPU: Pentium (132.96-MHz 586-class CPU) > Origin = "GenuineIntel" Id = 0x52b Stepping=11 ^^^^^^^^^^^^^^ > Features=0x1bf > real memory = 100663296 (98304K bytes) > > Can anybody help? Hope you didn't pay Intel prices for an IDT chip... -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD http://www.aai.dnsmgr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 10:55:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28704 for freebsd-stable-outgoing; Wed, 10 Jun 1998 10:55:59 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dreamer.dreamfire.net (qmailr@dreamfire.net [209.160.21.220]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA28589 for ; Wed, 10 Jun 1998 10:55:25 -0700 (PDT) (envelope-from sean@dreamfire.net) Received: (qmail 915 invoked from network); 10 Jun 1998 17:55:15 -0000 Received: from dreamfire.net (HELO dreamer.dreamfire.net) (209.160.21.220) by dreamfire.net with SMTP; 10 Jun 1998 17:55:15 -0000 Date: Wed, 10 Jun 1998 10:55:15 -0700 (PDT) From: Sean-Paul Rees To: "Rodney W. Grimes" cc: freebsd-stable@FreeBSD.ORG Subject: Re: Processor upgrade, minor problem. In-Reply-To: <199806101655.JAA14423@GndRsh.aac.dev.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, 10 Jun 1998, Rodney W. Grimes wrote: > > You most likely (reason I say ``most likely'' is below) have > an IDT/Centaur CPU chip, which FreeBSD has not been updated > to fully understand, and this does not print the Features > values. > > One interesting thing about the IDT chips is that it is possible > to reprogram the Origin string, and some one else may copy this > miss feature in the future. If you do a yahoo search on the > above ID string you'll find a few web sites that talk about this > misfeature. > I'm no processor/software brainiac here, but will this affect performance of the chip in anyway? It does perform (so far) about 30& better than my Intel P133. > > real memory = 100663296 (98304K bytes) > > > > instead of: > > > > FreeBSD 2.2.6-STABLE #0: Sat May 16 23:45:40 PDT 1998 > > root@dreamer.dreamfire.net:/usr/src/sys/compile/DREAMER > > CPU: Pentium (132.96-MHz 586-class CPU) > > Origin = "GenuineIntel" Id = 0x52b Stepping=11 > ^^^^^^^^^^^^^^ > > Features=0x1bf > > real memory = 100663296 (98304K bytes) > > > > Can anybody help? > > Hope you didn't pay Intel prices for an IDT chip... > I didn't buy it =) I got it as a bday gift.... =) > > -- > Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.aac.dev.com > Accurate Automation, Inc. Reliable computers for FreeBSD > http://www.aai.dnsmgr.com > -Sean-Paul Rees sean@dreamfire.net, SR5176 =============================================== = Sean-Paul Rees = Dream Fire Networks = = sean@dreamfire.net = Dream Fire Consulting = = = = "Marking your achievements, and improving = = upon them is better than any award anybody = = will bestow." -Sean-Paul Rees = =============================================== sig updated: 5/20/1998 Type bits/keyID Date User ID pub 2047/EF18B3ED 1998/04/11 Sean-Paul Rees To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 11:34:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09318 for freebsd-stable-outgoing; Wed, 10 Jun 1998 11:34:20 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [207.149.232.62] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09169 for ; Wed, 10 Jun 1998 11:33:57 -0700 (PDT) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.8/8.8.8) id LAA14542; Wed, 10 Jun 1998 11:32:58 -0700 (PDT) (envelope-from rgrimes) From: "Rodney W. Grimes" Message-Id: <199806101832.LAA14542@GndRsh.aac.dev.com> Subject: Re: Processor upgrade, minor problem. In-Reply-To: from Sean-Paul Rees at "Jun 10, 98 10:55:15 am" To: sean@dreamfire.net (Sean-Paul Rees) Date: Wed, 10 Jun 1998 11:32:58 -0700 (PDT) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > You most likely (reason I say ``most likely'' is below) have > > an IDT/Centaur CPU chip, which FreeBSD has not been updated > > to fully understand, and this does not print the Features > > values. > > > > One interesting thing about the IDT chips is that it is possible > > to reprogram the Origin string, and some one else may copy this > > miss feature in the future. If you do a yahoo search on the > > above ID string you'll find a few web sites that talk about this > > misfeature. > > > > I'm no processor/software brainiac here, but will this affect performance > of the chip in anyway? It does perform (so far) about 30& better than my > Intel P133. Very hard to answer, given that we have not done any qualification testing of the IDT chips (nor do we plan to, we use either Intel or AMD products here, which we have qualified). If the IDT chip does a faithful duplication of the Pentium it should work, but if the chip has unknown bugs, well... it can bite! Do note that IDT is claiming support for Linux, Solaris and Unix in general, so at least they knew to test for more than just compatibility with Microsoft. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD http://www.aai.dnsmgr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 12:21:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19626 for freebsd-stable-outgoing; Wed, 10 Jun 1998 12:21:22 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19562 for ; Wed, 10 Jun 1998 12:20:59 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id VAA02644; Wed, 10 Jun 1998 21:15:08 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id UAA07427; Wed, 10 Jun 1998 20:51:38 +0200 (CEST) (envelope-from andreas) Message-ID: <19980610205138.A6701@klemm.gtn.com> Date: Wed, 10 Jun 1998 20:51:38 +0200 From: Andreas Klemm To: Cy Schubert - ITSD Open Systems Group Cc: Matthew Cashdollar , freebsd-stable@FreeBSD.ORG Subject: Re: bind 8 or 4 ? References: <19980607215916.A7507@klemm.gtn.com> <199806101520.IAA05119@cwsys.cwsent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199806101520.IAA05119@cwsys.cwsent.com>; from Cy Schubert - ITSD Open Systems Group on Wed, Jun 10, 1998 at 08:20:17AM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jun 10, 1998 at 08:20:17AM -0700, Cy Schubert - ITSD Open Systems Group wrote: > > On Thu, Jun 04, 1998 at 10:37:24AM -0500, Matthew Cashdollar wrote: > > > > > > Is stable going to be moving to bind 8? I am currently using 4 and > > > would like to upgrade, but if it is going to be in the base system > > > I'd rather wait instead of installing the port. > > > > I think FreeBSD-STABLE will stay at bind4. > > > > But where is the problem to use the bind8 port ? > > I installed it on one of my home machines to "experience" BIND 8, as > I'm pondering doing the same at work. The upgrade was trivial. Ok, fine then for you. > If BIND 8 was used in -stable, this would cause much of the same grief > that we've just experienced with the latest round of changes that > affected config and the previous changes to compatibility slices, > because of the varying degrees of experience of people administering > FreeBSD sites. I think that this type of upgrade should be left until > 3.0 comes out. Ok, but what do you whish ? I understood your question as asking for bind8 in stable.... > Even then a sysinstall should ask a question like "do > you wish to upgrade to BIND 8?", > then install the port and run the Perl script to convert > any BIND 4 named.boot files to BIND 8 named.conf > files. If you use systinstall to install a system, then usually you have a *fresh* installation, why do you need a conversion script then ? > Then in 3.1 make BIND 8 the default. This should give everyone > plenty of warning (though some may still not heed the warning and > complain, but I guess that's life). I think bind8 should not wait too long, since everybody in the ISP business needs it because of security and advantages (to bind it on one ethernet interface). Many people told positive results, so why wait in -current ? And if it turns out to be stable, then merge it in... -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 12:39:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23623 for freebsd-stable-outgoing; Wed, 10 Jun 1998 12:39:27 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.asahi-net.or.jp (pop.asahi-net.or.jp [202.224.39.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23498; Wed, 10 Jun 1998 12:38:52 -0700 (PDT) (envelope-from tfuruya@dilemma.tf.or.jp@ppp129162.asahi-net.or.jp) Received: from galois.tf.or.jp (ppp129162.asahi-net.or.jp [202.213.129.162]) by pop.asahi-net.or.jp (8.8.8/3.6W) with ESMTP id EAA37326; Thu, 11 Jun 1998 04:43:49 +0900 Received: from dilemma.tf.or.jp (dilemma.tf.or.jp [192.168.1.3]) by galois.tf.or.jp (8.8.8/3.6W-ht5t-fry@asahi-net-98042218) with ESMTP id EAA09238; Thu, 11 Jun 1998 04:38:15 +0900 (JST) Received: from dilemma.tf.or.jp (localhost [127.0.0.1]) by dilemma.tf.or.jp (8.8.8/3.6W-CF3.6W-dilemma-tf.or.jp-9806) with ESMTP id EAA11696; Thu, 11 Jun 1998 04:41:11 +0900 (JST) Message-Id: <199806101941.EAA11696@dilemma.tf.or.jp> To: mike@smith.net.au Cc: robinson@public.bta.net.cn, freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Tetsuro FURUYA Subject: Re: Bug in wd driver From: Tetsuro FURUYA Reply-To: Tetsuro FURUYA In-Reply-To: Your message of "Thu, 28 May 1998 12:57:14 -0700" References: <199805281957.MAA01309@dingo.cdrom.com> X-Mailer: Mew version 1.54 on Emacs 19.28.1, Mule 2.3 X-fingerprint: F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 X-URL: http://sodan.komaba.ecc.u-tokyo.ac.jp/~tfuruya/ Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg="pgp-md5"; boundary="--Security_Multipart(Thu_Jun_11_04:40:53_1998)--" Date: Thu, 11 Jun 1998 04:41:08 +0900 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----Security_Multipart(Thu_Jun_11_04:40:53_1998)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit I wrote, In Message-Id: <199805272026.FAA16850@dilemma.tf.or.jp> In Message-Id: <199805281508.AAA04056@dilemma.tf.or.jp> >I have been encountered at the same defaults in using Panasonic AL-N1, >and FreeBSD-2.2.2. >And bad144 was hangupped. >But I have found out how to manipulate bad144, or fsck , or badsect. >My kernel has kernel-debugger ddb(4) installed in it. > ^^^^^^ >So, listening to the hamming sound of wd0 drive, and when wd drive >is hangupped, invoke kernel-debugger by typing ctrl-alt-ESC keys. > ^^^^^^^^^^^^ >A while after stopping of disk access, type 'c' or 'continue', >and go back to bad144 or fsck. ^^^^^^^^ >Several attempts may complete the identification of bad clusters. >As for my machine, this was worked. And you pointed out that, > > In Message-ID: <199805272101.OAA01902@dingo.cdrom.com> > > Mike Smith worte: > > >fsck /usr > > >..... > > >wd0: interrupt timeout: > > >wd0: status 50 error 0 > > >wd0: interrupt timeout: > > >wd0: status 50 error 1 > > > > >===> hang up > > >===> type 'cntrl-alt-esc' > > This defers the interrupt timeout... > > > >db>wd0s1f: hard error reading fsbn 1152850 of 1152850-1152851(wd0s1 bn > > >1279826; cn 317 tn 26 sn 44) > > >wd0: status 59 error 40 > > ... but not the interrupt, which finally arrives and contains real > error information. Note that the interrupt timeouts in your case > *don't* have DRQ set. Are you running in multi-block mode? > > > As for wd.c source, I will try to experiment :) > > Please do. It looks like your information may lead to a result here. It seems too late for writing reply to mailing list. But, this seems important to note-users, so I dare to report the result of my experiment of patch to /usr/src/sys/i386/isa/wd.c which Mr. Mike Smith's stated, In Message-Id: <199805272101.OAA01902@dingo.cdrom.com> Mike Smith writes: >This would tend to imply that the timeout value is too short. > >Can you try increasing the timeout counter and provoking your disk? > >In sys/i386/isa/wd.c, in this section: > > /* > * Schedule wdtimeout() to wake up after a few seconds. Retrying > * unmarked bad blocks can take 3 seconds! Then it is not good that > * we retry 5 times. > * > * On the first try, we give it 10 seconds, for drives that may need > * to spin up. > * > * XXX wdtimeout() doesn't increment the error count so we may loop > * forever. More seriously, the loop isn't forever but causes a > * crash. > * > * TODO fix b_resid bug elsewhere (fd.c....). Fix short but positive > * counts being discarded after there is an error (in physio I > * think). Discarding them would be OK if the (special) file offset > * was not advanced. > */ > if (wdtab[ctrlr].b_errcnt == 0) > du->dk_timeout = 1 + 10; > else > du->dk_timeout = 1 + 3; <---- Only this line. > > >Increase the 10 and 3 values (first and subsequent timeouts). Try >raising them lots, then come down slowly. Unfortunately, my /usr/src/sys/i386/isa/wd.c is different from the above source code. There is just only the last line in the wd.c. So, I rewrite only this last line, and increased 3 to 50. ( Is this OK?) Up to now, I have not yet experienced any disk crash, nor cannot-mount-root problem, nor anything bad else. And, system comes back successfully from bad sector read. This time, error message is only as follows, >wd0s1f: hard error reading fsbn 1152850 of 1152850-1152851(wd0s1 bn >1279826; cn 317 tn 26 sn 44) >wd0: status 59 error 40 or, >Jun 8 12:17:03 dilemma pccardd[37]: pccardd started >Jun 8 12:30:59 dilemma /kernel: wd0s1f: hard error reading fsbn 1215577 of 1215576-1215579 (wd0s1 bn 1342553; cn 332 tn 62 sn 23) wd0: status 59 error 10 >Jun 8 12:31:08 dilemma /kernel: wd0s1f: hard error reading fsbn 1215577 of 1215576-1215579 (wd0s1 bn 1342553; cn 332 tn 62 sn 23) wd0: status 59 error 10 So, the bug of wd.c device driver seems to be removed ^^) The another problem of system lock after wd hungup seems to be related to indefinite wait of swap_pager.(This is serious for X.) But this defect does not appear when the wd device driver can recover from disk access error. You have written that >raising them lots, then come down slowly. Is there any inconvenience when du->dk_timeout value is very large ? What if du->dk_timeout value is too large ? What is this du->dk_timeout ? I've just tried 'cd /usr; badsect BAD 1152850 1215577' & 'fsck /dev/rwd0s1f', but 'bad144 -s -v /dev/wd0' should work fine. ( I had often used bad144. But now, my bad sectors of wd0 become too many for bad144 :( ) badsect & fsck don't take care of swap area, nevertheless they are working fine now :) So, Thank you Mr. Mike Smith ! ======================================================================== TEL: 048-852-3520 FAX: 048-858-1597 E-Mail: ht5t-fry@asahi-net.or.jp tfu@ff.iij4u.or.jp pgp-fingerprint: pub Tetsuro FURUYA Key fingerprint = F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 ========================================================================= ----Security_Multipart(Thu_Jun_11_04:40:53_1998)-- Content-Type: Application/Pgp-Signature Content-Transfer-Encoding: 7bit -----BEGIN PGP MESSAGE----- Version: 2.6.3i iQCVAwUANX7hSjzkiNBZ20qpAQGRfgP/Ws9puO32Jc4cxOZTE+TXDcYnBWhJV8vV DeOuhMrf4Pozd+Y6LPgQ1FFXJHPwdU9ZR4vxUSn1VmBN/Hps/cA/UAFu1MG9p2oB HfQqWrYFjE0zscm1Xja569jnICj2WVl5iPhmIDAXhvaCJrhLj1FF7ctcF8ZWeX0W Sna/x38TJ0s= =Zczd -----END PGP MESSAGE----- ----Security_Multipart(Thu_Jun_11_04:40:53_1998)---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 12:58:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28287 for freebsd-stable-outgoing; Wed, 10 Jun 1998 12:58:59 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from megaweapon.zigg.com (ip144.grand-rapids2.mi.pub-ip.psi.net [38.12.209.144]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27571 for ; Wed, 10 Jun 1998 12:56:15 -0700 (PDT) (envelope-from matt@megaweapon.zigg.com) Received: from megaweapon.zigg.com (megaweapon.zigg.com [192.168.1.1]) by megaweapon.zigg.com (8.8.8/8.8.8) with SMTP id PAA02228; Wed, 10 Jun 1998 15:55:45 -0400 (EDT) (envelope-from matt@megaweapon.zigg.com) Date: Wed, 10 Jun 1998 15:55:45 -0400 (EDT) From: Matt Behrens To: Cy Schubert - ITSD Open Systems Group cc: Andreas Klemm , Matthew Cashdollar , freebsd-stable@FreeBSD.ORG Subject: Re: bind 8 or 4 ? In-Reply-To: <199806101520.IAA05119@cwsys.cwsent.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 10 Jun 1998, Cy Schubert - ITSD Open Systems Group wrote: > script to convert any BIND 4 named.boot files to BIND 8 named.conf > files. Then in 3.1 make BIND 8 the default. This should give everyone > plenty of warning (though some may still not heed the warning and > complain, but I guess that's life). Pfft. BIND 8 can go in 3.0 just fine. I think everyone should know (and expect) that -STABLE stays bug-fixed and low-fallout and -CURRENT is essentially reinstall and reconfigure everything. Matt Behrens | http://www.zigg.com/ Network Operations, The Iserv Company | Proudly running FreeBSD; sworn MIS, Michigan Kenworth, Inc. | enemy of Linux, a free hack OS Chanop Script Coordinator, WWFIN | and Windows, a non-free hack OS! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 15:05:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA01930 for freebsd-stable-outgoing; Wed, 10 Jun 1998 15:05:24 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from couatl.uchicago.edu (couatl.uchicago.edu [128.135.21.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA01883 for ; Wed, 10 Jun 1998 15:05:04 -0700 (PDT) (envelope-from sfarrell@couatl.uchicago.edu) Received: (from sfarrell@localhost) by couatl.uchicago.edu (8.9.0/8.9.0) id RAA08186; Wed, 10 Jun 1998 17:04:53 -0500 (CDT) To: "Jordan K. Hubbard" Cc: stable@FreeBSD.ORG Subject: Re: Anyone running the linux emulation as an LKM under 2.2-stable? References: <18591.897488992@time.cdrom.com> From: stephen farrell Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: 10 Jun 1998 17:04:53 -0500 In-Reply-To: "Jordan K. Hubbard"'s message of "Wed, 10 Jun 1998 07:29:52 -0700" Message-ID: <877m2osyka.fsf@couatl.uchicago.edu> Lines: 33 X-Mailer: Gnus v5.6.9/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" writes: > So, can I infer from this that there are people who are _currently_ > using the Linux LKM, do not compile their kernels with COMPAT_LINUX, > and things are just fine with them in 2.2-stable? I'd just like to > have this confirmed by *one* person since the LKM used to work fine > for me too, up until about a week or two ago. :-) couatl# uname -a FreeBSD couatl.uchicago.edu 2.2.6-STABLE FreeBSD 2.2.6-STABLE #0: Mon Jun 8 21:58:37 CDT 1998 sfarrell@couatl.uchicago.edu:/usr/src/sys/compile/COUATL i386 couatl# grep COMPAT_LINUX /sys/i386/conf/COUATL couatl# make sure i'm running the latest linuxmod on my system... couatl# modunload -i 0 Linux emulator removed couatl# linux couatl# modstat Type Id Off Loadaddr Size Info Rev Module Name EXEC 0 4 f631f000 0020 f6326010 1 linux_mod run staroffice... yep I am all of these things... i'm running lkm's and kernel cvsupped June 8. (my world, other than lkm's, was last built may 24). -- Steve Farrell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 16:35:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20111 for freebsd-stable-outgoing; Wed, 10 Jun 1998 16:35:16 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20060; Wed, 10 Jun 1998 16:35:06 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id PAA00747; Wed, 10 Jun 1998 15:28:29 -0700 (PDT) Message-Id: <199806102228.PAA00747@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Tetsuro FURUYA cc: mike@smith.net.au, robinson@public.bta.net.cn, freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Tetsuro FURUYA Subject: Re: Bug in wd driver In-reply-to: Your message of "Thu, 11 Jun 1998 04:41:08 +0900." <199806101941.EAA11696@dilemma.tf.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Jun 1998 15:28:29 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > >fsck /usr > > > >..... > > > >wd0: interrupt timeout: > > > >wd0: status 50 error 0 > > > >wd0: interrupt timeout: > > > >wd0: status 50 error 1 > > > > > > >===> hang up > > > >===> type 'cntrl-alt-esc' > > > > This defers the interrupt timeout... > > > > > >db>wd0s1f: hard error reading fsbn 1152850 of 1152850-1152851(wd0s1 bn > > > >1279826; cn 317 tn 26 sn 44) > > > >wd0: status 59 error 40 > > > > ... but not the interrupt, which finally arrives and contains real > > error information. Note that the interrupt timeouts in your case > > *don't* have DRQ set. Are you running in multi-block mode? > > > > > As for wd.c source, I will try to experiment :) > > > > Please do. It looks like your information may lead to a result here. > > It seems too late for writing reply to mailing list. Not at all; better late than never! > But, this seems important to note-users, so I dare to report the result of > my experiment of patch to /usr/src/sys/i386/isa/wd.c > which Mr. Mike Smith's stated, ... > > if (wdtab[ctrlr].b_errcnt == 0) > > du->dk_timeout = 1 + 10; > > else > > du->dk_timeout = 1 + 3; <---- Only this line. > > > > > >Increase the 10 and 3 values (first and subsequent timeouts). Try > >raising them lots, then come down slowly. > > Unfortunately, my /usr/src/sys/i386/isa/wd.c is different > from the above source code. > There is just only the last line in the wd.c. > > So, I rewrite only this last line, and increased 3 to 50. ( Is this OK?) It's just a number, and you're in the best position to determine whether it's big enough. > Up to now, I have not yet experienced any disk crash, nor cannot-mount-root > problem, nor anything bad else. Excellent! And thanks for confirming this. I hope that the original plaintiff is in a position to try this themselves - I would be more than happy to be completely wrong about the situation. 8) > You have written that > >raising them lots, then come down slowly. > > Is there any inconvenience when du->dk_timeout value is > very large ? > What if du->dk_timeout value is too large ? The only inconvenience is in the case where the disk has truly failed to generate an interrupt, and the delay involved before reporting the failure. > What is this du->dk_timeout ? It determines how long a disk is allowed to take to complete a command. > I've just tried 'cd /usr; badsect BAD 1152850 1215577' & 'fsck /dev/rwd0s1f', > but 'bad144 -s -v /dev/wd0' should work fine. > ( I had often used bad144. But now, my bad sectors of wd0 become too many > for bad144 :( ) > badsect & fsck don't take care of swap area, > nevertheless they are working fine now :) > > So, Thank you Mr. Mike Smith ! No, definitely this time the thanks are for you. I'll look at increasing this timeout significantly for both -stable and -current, if someone doesn't beat me to it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 17:00:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25120 for freebsd-stable-outgoing; Wed, 10 Jun 1998 17:00:07 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from roguetrader.com (cold.org [206.81.134.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA25007 for ; Wed, 10 Jun 1998 16:59:58 -0700 (PDT) (envelope-from root@roguetrader.com) Received: (from root@localhost) by roguetrader.com (8.8.5/8.8.5) id SAA19779; Wed, 10 Jun 1998 18:00:03 -0600 (MDT) Date: Wed, 10 Jun 1998 18:00:03 -0600 (MDT) Message-Id: <199806110000.SAA19779@roguetrader.com> Subject: SECURITY NOTICE: FreeBSD 2.2.6-RELEASE From: freebsd-errata-update@roguetrader.com To: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ****************************************************************** ** THIS IS AN AUTOMATIC ERRATA UPDATE FOR FREEBSD 2.2.6-RELEASE ** ****************************************************************** You can retrieve the complete ERRATA from: ftp://ftp.freebsd.org/pub/FreeBSD/2.2.6-RELEASE/ERRATA.TXT The last update was sent: Mon May 11 22:15:30 1998 This update is sent: Wed Jun 10 18:00:03 1998 ------------------------------------------------------------------ ---- SECURITY ADVISORIES: See ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-98:0[2-5].* for full information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 10 17:42:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03403 for freebsd-stable-outgoing; Wed, 10 Jun 1998 17:42:36 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail1.realtime.net (mail1.realtime.net [205.238.128.217]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA03147 for ; Wed, 10 Jun 1998 17:41:16 -0700 (PDT) (envelope-from jktheowl@bga.com) Received: (qmail 32836 invoked from network); 11 Jun 1998 00:41:08 -0000 Received: from zoom.realtime.net (HELO zoom.bga.com) (root@205.238.128.40) by mail1.realtime.net with SMTP; 11 Jun 1998 00:41:08 -0000 Received: from barnowl (apm7-197.realtime.net [204.96.0.197]) by zoom.bga.com (8.6.12/8.6.12) with SMTP id TAA19546; Wed, 10 Jun 1998 19:41:04 -0500 Date: Wed, 10 Jun 1998 19:48:07 -0500 (CDT) From: John Kenagy X-Sender: jktheowl@barnowl To: Atipa cc: freebsd-stable@FreeBSD.ORG Subject: Re: NIS client maintenance script 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 Thanks! I'll give this a try in a day or so and post it with the tutorial as well. Or, would you rather I posted a link to the source file? Also, please send me your full name, etc. so I can credit you. (I know I've seen it but can't find it now, oops.) John On Tue, 9 Jun 1998, Atipa wrote: > > Oops! I posted the wrong script.. :( > Download the correct one from ftp://ftp.atipa.com/pub/FreeBSD/nis-client > > Kevin > > On Tue, 9 Jun 1998, Atipa wrote: > > > > > Everyone, > > > > You may find this script to be of use for NIS clients. It can be run from > > crontab every minute or so to make sure NIS connections are up and > > running. > > > > It disables NIS authentication during network failures, and > > resets and enables NIS if the connection is restored. > > > > Must be run as root. May work with /bin/sh, but I like bash better. > > > > WARNING!!! This may modify your /etc/master.password file. If you can not > > understand what it does, do not use it! :) > > > > Kevin > > > > > > ----- > > #!/usr/local/bin/bash > > > > # This script maintains NIS client connections on simple networks > > # Rev. 1.0, 05-09-98, Kevin McCarthy (kmcc@atipa.com) > > > > # It disables NIS authentication during network failures, and resets > > # and enables NIS if the connection is restored. > > > > # User defined variables > > nis_host="host.domain.tld" # required > > nis_domainname="freakazoid" # required > > ypbind_args="-s -ypsetme" # -s for security > > ypset_args="$nis_host" # "" for no ypset > > > > # Clearspace for readability > > echo " " > > > > # Find current state (bool) of NIS > > nis_state=`grep + /etc/master.passwd && ps ax |grep yp` > > if [ -n "$nis_state" ]; then > > echo NIS authentication is ON > > else > > echo NIS authentication is OFF > > fi > > > > # Set up NIS conditional functions > > function nis_down () { > > echo "Error: $nis_problem" > > > > if [ -n "$nis_state"]; then > > echo "Disabling NIS authentication" > > umask 077 > > grep -v + /etc/master.passwd > /root/mp.nonis > > mv /etc/master.passwd /etc/master.passwd.nis > > mv /root/mp.nonis /etc/master.passwd > > pwd_mkdb -p /etc/master.passwd > > else > > echo "NIS remaining disabled" > > fi > > > > exit 1 > > } > > > > function nis_reset () { > > if [ -n "$nis_problem"]; then > > echo "Error: $nis_problem" > > fi > > > > echo -n "Resetting NIS services... " > > killall ypbind >> /dev/null > > domainname $nis_domainname > > ypbind $ypbind_args > > if [ -n "$ypset_args"]; then > > ypset $ypset_args > > fi > > echo "Done" > > > > reset_done="true" > > } > > > > function nis_up () { > > if [ -z "$nis_state" ]; then > > echo "NIS services restored. Enabling NIS authentication" > > umask 077 > > mv /etc/master.passwd.nis /etc/master.passwd > > pwd_mkdb -p /etc/master.passwd > > fi > > > > nis_working="true" > > } > > > > echo -n "Network connecion to $nis_host is " > > up=`ping -c1 $nis_host | grep transmitted | awk -F, '{print $2}' \ > > | awk '{print $1}'` > > if [ "$up" = "1" ]; then > > echo ON > > else > > echo OFF > > nis_problem="host not reachable (ping failed)" > > nis_down > > fi > > > > while [ -z "$nis_working" ]; do > > # Check if NIS is bound > > nis_bound=`ypwhich` > > > > if [ "$nis_bound" = "$nis_host" ]; then > > echo NIS binding to $nis_bound is ON > > nis_up > > else > > if [ -z "$reset_done" ]; then > > nis_problem="NIS binding to $nis_host is OFF" > > nis_reset > > else > > echo "Reset Failed; disabling NIS services" > > nis_down > > fi > > fi > > done > > > > echo "Exiting" > > echo " " > > > > > > 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 Jun 10 20:48:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09590 for freebsd-stable-outgoing; Wed, 10 Jun 1998 20:48:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from router.home.com (root@ip-21-224.phx.primenet.com [206.165.21.224]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09478 for ; Wed, 10 Jun 1998 20:48:10 -0700 (PDT) (envelope-from fontenot@primenet.com) Received: from nt (nt.home.com [192.168.1.2]) by router.home.com (8.8.7/8.8.7) with SMTP id HAA12471 for ; Wed, 10 Jun 1998 07:41:21 -0700 From: "Paul Fontenot" To: Subject: 3COM 3C509 TPO Date: Wed, 10 Jun 1998 07:39:22 -0700 Message-ID: <01bd947d$8ec6ad90$0201a8c0@nt.home.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01BD9442.E267D590" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0006_01BD9442.E267D590 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have one of these cards in a Pentium 100 with 96M RAM and 2 Fujitsu = 1.6 GIG Drives. I also have the same setup running RH Linux 5.0. The = problem I have is when I try to initialize my ethernet card (ep0 = IRQ=3D10, IO=3D0x300) the system completely locks up. No switching VT's, = no CTRL+ALT+DEL, nothing. The only way out is to push the power button. = Any suggestions? -Paul P.S. Switch card to RH box to check it out and it works fine, also works = great for NT 4.0 ------=_NextPart_000_0006_01BD9442.E267D590 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I have one of these cards in a = Pentium 100 with=20 96M RAM and 2 Fujitsu 1.6 GIG Drives. I also have the same setup running = RH=20 Linux 5.0. The problem I have is when I try to initialize my ethernet = card (ep0=20 IRQ=3D10, IO=3D0x300) the system completely locks up. No switching VT's, = no=20 CTRL+ALT+DEL, nothing. The only way out is to push the power button. Any = suggestions?
 
-Paul
 
P.S. Switch card to RH box to check = it out and=20 it works fine, also works great for NT 4.0
------=_NextPart_000_0006_01BD9442.E267D590-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jun 11 06:24:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA11572 for freebsd-stable-outgoing; Thu, 11 Jun 1998 06:24:20 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from psv.oss.uswest.net (psv.oss.uswest.net [204.147.85.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA11556 for ; Thu, 11 Jun 1998 06:24:12 -0700 (PDT) (envelope-from greg@psv.oss.uswest.net) Received: (from greg@localhost) by psv.oss.uswest.net (8.8.8/8.8.5) id IAA22630; Thu, 11 Jun 1998 08:23:10 -0500 (CDT) From: "Greg Rowe" Message-Id: <9806111323.ZM22628@psv.oss.uswest.net> Date: Thu, 11 Jun 1998 13:23:09 +0000 In-Reply-To: Travis Mikalson "Re: Anyone know what this SCSI error is about?" (Jun 10, 12:41pm) References: <00aa01bd93ec$a118bd80$02dd71d1@fargo.os.com> <9806101333.ZM16262@psv.oss.uswest.net> <357EB726.2F3F@terranova.net> X-Mailer: Z-Mail (3.2.1 10apr95) To: Travis Mikalson Subject: Re: Anyone know what this SCSI error is about? Cc: 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 We have about 300 or so C's and D's in production with no problems at various release levels. We still have a couple E's in boxes with light loads and they run OK except for the occasional errors. We found that high user load or a couple bonnie or iozone runs can cause the systems to crash. Also, performance numbers under bonnie are terrible on the E cards. The E cards will also fail on our CAM test systems. All other Adaptec problems at the later FreeBSD releases can be traced to the usual drive/cable/termination problems. Greg > Hmm how about this one (this machine is my playbox running -CURRENT so > I'm guessing the rev output is a bit different than 2.2.x): > ahc0: rev 0x01 int a irq 19 on pci0.11.0 > ahc0: aic7880 Wide Channel, SCSI Id=7, 16/255 SCBs > > That gives me those problems ONLY when I stress the drive to the > absolute max with dd and silly benchmarks. Looks like rev 0x01 means > I should exchange the card for a D. No mystery there. > > I've never ever seen the aborts and timeouts in the 155 days this one > (also a -CURRENT box from.. well.. 156 days ago) has been up which is a > lot more than I can say for the next box :( > ahc0: rev 0x00 int a irq 10 on pci0.10.0 > ahc0: aic7880 Wide Channel, SCSI Id=7, 16/255 SCBs > > > this is the last one with a 2940UW in it where there have been so many > kernel messages (most of them from the SCSI timeouts, aborts, retries) > that I can no longer see the beginning of the dmesg... > I see it's a Rev C, not an E, but I still have the problems with this > one that have been described earlier: > sd1(ahc0:2:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR = 0x5 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa > Ordered Tag queued > sd1(ahc0:2:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR = 0x4 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa > sd1(ahc0:2:0): Queueing an Abort SCB > sd1(ahc0:2:0): Abort Message Sent > sd1(ahc0:2:0): SCB 6 - Abort Tag Completed. > sd1(ahc0:2:0): no longer in timeout > Ordered Tag sent > > This one's been up for 85 days and is running 2.2.6-BETA from mid-March > but has had this problem since upgrading from 2.1.5 to 2.2.[1 I think] > Same symptoms with three different cables and without the AHC_ options. > > All of these machines have all the AHC_ options enabled right now and no > CAM. -- Greg Rowe US WEST - !NTERACT Internet Services "To err is human, to really foul up requires the root password." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jun 11 08:12:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA04137 for freebsd-stable-outgoing; Thu, 11 Jun 1998 08:12:38 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA04119 for ; Thu, 11 Jun 1998 08:12:33 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id IAA02406; Thu, 11 Jun 1998 08:12:13 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: "Greg Rowe" cc: Travis Mikalson , freebsd-stable@FreeBSD.ORG Subject: Re: Anyone know what this SCSI error is about? In-reply-to: Your message of "Thu, 11 Jun 1998 13:23:09 -0000." <9806111323.ZM22628@psv.oss.uswest.net> Date: Thu, 11 Jun 1998 08:12:13 -0700 Message-ID: <2402.897577933@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We have about 300 or so C's and D's in production with no problems > at various release levels. We still have a couple E's in boxes with > light loads and they run OK except for the occasional errors. We > found that high user load or a couple bonnie or iozone runs can > cause the systems to crash. Also, performance numbers under bonnie > are terrible on the E cards. The E cards will also fail on our CAM > test systems. All other Adaptec problems at the later FreeBSD > releases can be traced to the usual drive/cable/termination > problems. Yow, that's pretty nasty! Do you think I could perhaps persuade you to put together a short paragraph describing the problems one might encounter with an E revision card and how to identify an E rev card in the field? Then I could put together a FAQ / HARDWARE.TXT entry for it since it seems worthy of such mention. Thanks! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jun 11 10:51:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12374 for freebsd-stable-outgoing; Thu, 11 Jun 1998 10:51:54 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from assurance (assurance.rstcorp.com [206.29.49.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12327 for ; Thu, 11 Jun 1998 10:51:37 -0700 (PDT) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance (8.7.5/8.6.9) id NAA13297; Thu, 11 Jun 1998 13:50:59 -0400 Received: from sandbox.rstcorp.com(206.29.49.63) by assurance.rstcorp.com via smap (V2.0) id xma013294; Thu, 11 Jun 98 13:50:27 -0400 Received: from fault.rstcorp.com (fault [206.29.49.18]) by sandbox.rstcorp.com (8.8.8/8.8.8) with ESMTP id NAA23271; Thu, 11 Jun 1998 13:50:21 -0400 (EDT) Received: (from vshah@localhost) by fault.rstcorp.com (8.8.8/8.8.8) id NAA08167; Thu, 11 Jun 1998 13:48:41 -0400 (EDT) Date: Thu, 11 Jun 1998 13:48:41 -0400 (EDT) Message-Id: <199806111748.NAA08167@fault.rstcorp.com> From: "Viren R. Shah" To: Wes Peters Cc: stable@FreeBSD.ORG Subject: Re: NFS server performance (was: NFS performance benchmarks?) In-Reply-To: <35814EA0.7847B26E@softweyr.com> References: <199806111217.IAA07801@fault.rstcorp.com> <35814EA0.7847B26E@softweyr.com> X-Mailer: VM 6.40 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Wes" == Wes Peters writes: Wes> Viren R. Shah wrote: >> >> Does anyone know if there are NFS performance benchmarks available? >> If not, what would be a good series of tests to run to compare >> relative NFS performance (FreeBSD NFS server vs. Solaris NFS server)? >> [I looked in /usr/ports/benchmarks, but there isn't anything NFS >> specific -- it all seems to be either network or CPU benchmarking] Wes> Are you the Viren Shah of NCWorld Magazine? Nope. Wes> I don't find any explicit NFS performance benchmarks, but have you Wes> tried running iozone or bonnie on an NFS mount? We tried iozone, and the results were bad (as shown below), which is why I was trying to see if there were other benchmarks that validated the iozone results, or not. We are trying to compare the relative performances of a solaris NFS server vs. a FreeBSD NFS server (running 2.2.6 late BETA): IOZONE: auto-test mode FreeBSD Server Solaris Server ====================== ================== MB reclen bytes/sec bytes/sec bytes/sec bytes/sec written read written read 1 512 51737 7117484 486685 7139923 1 1024 48598 11162427 472185 12754985 1 2048 53363 16469678 465276 19026272 1 4096 57415 25860745 492552 26323628 1 8192 56089 30133306 490601 33321942 2 512 52701 6225125 478547 7336163 2 1024 53642 10811569 483381 11907853 2 2048 46550 16377591 461267 18763777 2 4096 55467 22791909 489909 25800971 2 8192 52679 30147920 474295 22596409 4 512 51664 5246158 484840 6519525 Both the iozone tests were run from a SunOS NFS client. As you can see the write performance is an order of magnitude worse. The local iozone results for both servers were comparable (though the FreeBSD box had slightly worse performance) The FreeBSD server has: fxp0: flags=8843 mtu 1500 inet 206.29.49.78 netmask 0xffffff80 broadcast 206.29.49.127 ether 00:a0:c9:ce:ea:4a media: autoselect This was after we had problems with a 3COM 3c905 in 100Mbit mode (the box kept silently rebooting. At least with the Intel NIC, it works). Any ideas, anyone? Wes> Wes Peters Thanks Viren -- Viren R. Shah viren@rstcorp.com | "God made a few people perfect http://www.rstcorp.com/~vshah/ | --the rest He created right-handed" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jun 11 13:04:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13798 for freebsd-stable-outgoing; Thu, 11 Jun 1998 13:04:51 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from camel14.mindspring.com (camel14.mindspring.com [207.69.200.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13653 for ; Thu, 11 Jun 1998 13:04:21 -0700 (PDT) (envelope-from eternal@foci.net) Received: from et.foci.net (user-38lc37q.dialup.mindspring.com [209.86.12.250]) by camel14.mindspring.com (8.8.5/8.8.5) with SMTP id QAA24954 for ; Thu, 11 Jun 1998 16:04:12 -0400 (EDT) From: "Eternal" To: Subject: Network Ports Date: Thu, 11 Jun 1998 16:02:16 -0400 Message-ID: <01bd9573$d529b560$fa0c56d1@et.foci.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 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG telnetd: All network ports in use. How can I fix this error ? My maxusers is at 512, pty's at 64, and other options in the kernel set above normal levels. - Jeremy Blawn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jun 11 13:41:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22164 for freebsd-stable-outgoing; Thu, 11 Jun 1998 13:41:31 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from camel8.mindspring.com (camel8.mindspring.com [207.69.200.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22108 for ; Thu, 11 Jun 1998 13:41:06 -0700 (PDT) (envelope-from durkin@matter.net) Received: from gigantor.matter.net (user-38lcaio.dialup.mindspring.com [209.86.42.88]) by camel8.mindspring.com (8.8.5/8.8.5) with SMTP id QAA16353; Thu, 11 Jun 1998 16:39:40 -0400 (EDT) Date: Thu, 11 Jun 1998 16:39:39 -0400 (EDT) From: durkin Reply-To: durkin To: Cy Schubert - ITSD Open Systems Group cc: freebsd-stable@FreeBSD.ORG Subject: Re: rc.firewall and ipfw commands In-Reply-To: <199806101505.IAA05083@cwsys.cwsent.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 10 Jun 1998, Cy Schubert - ITSD Open Systems Group wrote: > In my firewall configurations I modify rc.firewall to recognize a > "user" firewall type (for user defined) and specify > firewall_type="user" in my rc.conf. The "user" firewall type executes > /usr/local/etc/rc.firewall.local instead of one of the predefined > firewall types in rc.firewall. This may be a handy feature in the > stock FreeBSD rc.firewall. If anyone wishes I can submit a PR to have > this included in the FreeBSD distribution. > Actually, FreeBSD's rc.firewall already has the ability to load ipfw commands contained within a file. Just specify the firewall type as the filename which contains the commands. Craig durkin@matter.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jun 11 14:31:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04832 for freebsd-stable-outgoing; Thu, 11 Jun 1998 14:31:23 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pn.wagsky.com (root@wagsky.vip.best.com [206.86.71.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04724 for ; Thu, 11 Jun 1998 14:30:50 -0700 (PDT) (envelope-from Jeff@Wagsky.com) Received: from [192.168.6.3] (mac.pn.wagsky.com [192.168.6.3]) by pn.wagsky.com (8.8.8/8.8.8) with ESMTP id OAA00680; Thu, 11 Jun 1998 14:29:58 -0700 (PDT) (envelope-from Jeff@Wagsky.com) X-Sender: mailman@mail.pn.wagsky.com Message-Id: In-Reply-To: References: <199806101505.IAA05083@cwsys.cwsent.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 11 Jun 1998 14:25:16 -0700 To: durkin From: Jeff Kletsky Subject: Re: rc.firewall and ipfw commands Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Wed, 10 Jun 1998, Cy Schubert - ITSD Open Systems Group wrote: > >> In my firewall configurations I modify rc.firewall to recognize a >> "user" firewall type (for user defined) and specify >> firewall_type="user" in my rc.conf. The "user" firewall type executes >> /usr/local/etc/rc.firewall.local instead of one of the predefined >> firewall types in rc.firewall. This may be a handy feature in the >> stock FreeBSD rc.firewall. If anyone wishes I can submit a PR to have >> this included in the FreeBSD distribution. >> > >Actually, FreeBSD's rc.firewall already has the ability to load ipfw >commands contained within a file. Just specify the firewall type as the >filename which contains the commands. Unfortunately, ipfw does not appear to allow a file of the form: -f flush add 1 count log tcp from any to any setup recv tun0 in . . . to permit reliable removal of the rules introduced by rc.firewall *before* the call for the "unknown" firewall is made: elif [ "${firewall_type}" != "UNKNOWN" -a -r "${firewall_type}" ]; then $fwcmd ${firewall_type} fi Mr. Schubert's approach allows greater flexibility and reliability for this critical function -- independent of changes in the distribution version of rc.firewall. Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jun 11 14:45:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07568 for freebsd-stable-outgoing; Thu, 11 Jun 1998 14:45:53 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from hobbes.saturn-tech.com (drussell@drussell.internode.net [198.161.228.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07498 for ; Thu, 11 Jun 1998 14:45:32 -0700 (PDT) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by hobbes.saturn-tech.com (8.8.4/8.8.2) with SMTP id PAA06334; Thu, 11 Jun 1998 15:44:52 -0600 (MDT) Date: Thu, 11 Jun 1998 15:44:52 -0600 (MDT) From: Doug Russell To: "Viren R. Shah" cc: stable@FreeBSD.ORG Subject: Re: NFS server performance (was: NFS performance benchmarks?) In-Reply-To: <199806111748.NAA08167@fault.rstcorp.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, 11 Jun 1998, Viren R. Shah wrote: > We tried iozone, and the results were bad (as shown below), which is > why I was trying to see if there were other benchmarks that validated > the iozone results, or not. > We are trying to compare the relative performances of a solaris NFS > server vs. a FreeBSD NFS server (running 2.2.6 late BETA): > > IOZONE: auto-test mode > > > FreeBSD Server Solaris Server > ====================== ================== > MB reclen bytes/sec bytes/sec bytes/sec bytes/sec > written read written read > 1 512 51737 7117484 486685 7139923 > 1 1024 48598 11162427 472185 12754985 > 1 2048 53363 16469678 465276 19026272 > 1 4096 57415 25860745 492552 26323628 > 1 8192 56089 30133306 490601 33321942 > 2 512 52701 6225125 478547 7336163 > 2 1024 53642 10811569 483381 11907853 > 2 2048 46550 16377591 461267 18763777 > 2 4096 55467 22791909 489909 25800971 > 2 8192 52679 30147920 474295 22596409 > 4 512 51664 5246158 484840 6519525 > > > Both the iozone tests were run from a SunOS NFS client. As you can see > the write performance is an order of magnitude worse. The local iozone > results for both servers were comparable (though the FreeBSD box had > slightly worse performance) There must be some time of flakiness occuring here. (Perhaps some strange incompatibility due to the SunOS client??) I have used iozone to test NFS performance before, but I did a quick test here to check that nothing has broken recently. With an AM486DX4/120 client running 2.2.6-STABLE from a couple weeks ago with an old NE2000 clone, mounting /usr from an AM5x86/150 running ancient 2.2-BETA with a 3c905 in 10 Mbps mode, I get: Writing the 20 Megabyte file, 'iozone.tmp'...46.320312 seconds Reading the file...25.390625 seconds IOZONE performance measurements: 452749 bytes/second for writing the file 825955 bytes/second for reading the file iozone auto results are similar, but when you get to the really small file sizes, various caches seem to speed things up abnormally, so this is probably a better result. Obviously my read speeds are limited due to the 10mbps link and NE2000, but this seems to be more the expected result. I may play with this a little later on some newer boxes and see what happens. I don't have any Sun boxes on my networks, and rather than drag one over from the other end of the building and reconfiguring it, perhaps someone else can shed some light on this? :) Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jun 11 14:50:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08614 for freebsd-stable-outgoing; Thu, 11 Jun 1998 14:50:44 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from passer.osg.gov.bc.ca (passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08565 for ; Thu, 11 Jun 1998 14:50:09 -0700 (PDT) (envelope-from cschuber@passer.osg.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.0/8.6.10) id OAA19467; Thu, 11 Jun 1998 14:38:48 -0700 (PDT) Message-Id: <199806112138.OAA19467@passer.osg.gov.bc.ca> Received: from localhost(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost, id smtpdaanEAa; Thu Jun 11 14:38:42 1998 X-Mailer: exmh version 2.0gamma 1/27/96 Reply-to: Cy Schubert - ITSD Open Systems Group X-Sender: cschuber To: Matt Behrens cc: Cy Schubert - ITSD Open Systems Group , Andreas Klemm , Matthew Cashdollar , freebsd-stable@FreeBSD.ORG Subject: Re: bind 8 or 4 ? In-reply-to: Your message of "Wed, 10 Jun 1998 15:55:45 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Jun 1998 14:37:06 -0700 From: Cy Schubert - ITSD Open Systems Group Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 10 Jun 1998, Cy Schubert - ITSD Open Systems Group wrote: > > > script to convert any BIND 4 named.boot files to BIND 8 named.conf > > files. Then in 3.1 make BIND 8 the default. This should give everyone > > plenty of warning (though some may still not heed the warning and > > complain, but I guess that's life). > > Pfft. BIND 8 can go in 3.0 just fine. I think everyone should know (and > expect) that -STABLE stays bug-fixed and low-fallout and -CURRENT is > essentially reinstall and reconfigure everything. That's a little more aggressive than my suggestion. That's O.K. too. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: cschuber@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Government of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jun 11 14:53:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09337 for freebsd-stable-outgoing; Thu, 11 Jun 1998 14:53:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from passer.osg.gov.bc.ca (passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09175 for ; Thu, 11 Jun 1998 14:52:47 -0700 (PDT) (envelope-from cschuber@passer.osg.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.0/8.6.10) id OAA16898; Thu, 11 Jun 1998 14:36:58 -0700 (PDT) Message-Id: <199806112136.OAA16898@passer.osg.gov.bc.ca> Received: from localhost(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost, id smtpdaabtFa; Thu Jun 11 14:36:48 1998 X-Mailer: exmh version 2.0gamma 1/27/96 Reply-to: Cy Schubert - ITSD Open Systems Group X-Sender: cschuber To: Andreas Klemm cc: Cy Schubert - ITSD Open Systems Group , Matthew Cashdollar , freebsd-stable@FreeBSD.ORG Subject: Re: bind 8 or 4 ? In-reply-to: Your message of "Wed, 10 Jun 1998 20:51:38 +0200." <19980610205138.A6701@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Jun 1998 14:35:52 -0700 From: Cy Schubert - ITSD Open Systems Group Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, Jun 10, 1998 at 08:20:17AM -0700, Cy Schubert - ITSD Open Systems Gro up wrote: > > > On Thu, Jun 04, 1998 at 10:37:24AM -0500, Matthew Cashdollar wrote: > > > > > > > > Is stable going to be moving to bind 8? I am currently using 4 and > > > > would like to upgrade, but if it is going to be in the base system > > > > I'd rather wait instead of installing the port. > > > > > > I think FreeBSD-STABLE will stay at bind4. > > > > > > But where is the problem to use the bind8 port ? > > > > I installed it on one of my home machines to "experience" BIND 8, as > > I'm pondering doing the same at work. The upgrade was trivial. > > Ok, fine then for you. > > > If BIND 8 was used in -stable, this would cause much of the same grief > > that we've just experienced with the latest round of changes that > > affected config and the previous changes to compatibility slices, > > because of the varying degrees of experience of people administering > > FreeBSD sites. I think that this type of upgrade should be left until > > 3.0 comes out. > > Ok, but what do you whish ? I understood your question as asking > for bind8 in stable.... Leave -stable alone and introduce BIND 8 in -current. > > > Even then a sysinstall should ask a question like "do > > you wish to upgrade to BIND 8?", > > then install the port and run the Perl script to convert > > any BIND 4 named.boot files to BIND 8 named.conf > > files. > > If you use systinstall to install a system, then usually you > have a *fresh* installation, why do you need a conversion script > then ? Sysinstall can be used for *upgrade* installs too! > > > Then in 3.1 make BIND 8 the default. This should give everyone > > plenty of warning (though some may still not heed the warning and > > complain, but I guess that's life). > > I think bind8 should not wait too long, since everybody in the > ISP business needs it because of security and advantages (to bind > it on one ethernet interface). Many people told positive results, > so why wait in -current ? And if it turns out to be stable, then > merge it in... If it is to be merged into -stable there needs to be an upgrade script and the option for administrators to choose to use BIND 4. The Perl script that comes with BIND 8 isn't smart enough to recognize include files and process them as well. Also, the Perl script may get the conversion wrong so it still needs to be eyeballed. On the other hand (taking the devil's advocate role and talking myself out of my position) any company or organization using a UNIX system without enough expertise should be hiring a contractor to do it right. Both opinions have valid points. It depends on what our priorities are. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: cschuber@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Government of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jun 11 14:59:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10284 for freebsd-stable-outgoing; Thu, 11 Jun 1998 14:59:11 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10142 for ; Thu, 11 Jun 1998 14:58:37 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id OAA02777; Thu, 11 Jun 1998 14:58:26 -0700 (PDT) (envelope-from jdp) Message-Id: <199806112158.OAA02777@austin.polstra.com> To: gibbs@narnia.plutotech.com Subject: Re: Anyone know what this SCSI error is about? In-Reply-To: <199806101527.JAA18289@narnia.plutotech.com> References: <199806101527.JAA18289@narnia.plutotech.com> Organization: Polstra & Co., Seattle, WA Cc: stable@FreeBSD.ORG Date: Thu, 11 Jun 1998 14:58:26 -0700 From: John Polstra Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199806101527.JAA18289@narnia.plutotech.com>, Justin T. Gibbs wrote: > > ahc0 rev 1 int a irq 10 on pci0:13:0 > > Your problem is that you are running a rev 1 aic7880 on a 440FX chipset. > This has known problems and I'm working with Adaptec to determine more > exactly what is going on and how the FreeBSD driver can work around it. I just had exactly the same problem with an on-board aic7880 that reports itself as "rev 0x00" under yesterday's -current. This is on one of those $800 Toshiba boxes from Insight that everybody was talking about a couple of weeks ago. Here's the dmesg output: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #1: Thu Jun 11 08:30:01 PDT 1998 jdp@blake.polstra.com:/usr/src/sys/compile/BLAKE Timecounter "i8254" frequency 1193182 Hz cost 3372 ns Timecounter "TSC" frequency 198665964 Hz cost 242 ns CPU: Pentium Pro (198.67-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xfbff real memory = 33554432 (32768K bytes) avail memory = 30470144 (29756K bytes) Probing for devices on PCI bus 0: Correcting Natoma config for non-SMP chip0: rev 0x02 on pci0.0.0 fxp0: rev 0x02 int a irq 11 on pci0.6. 0 fxp0: Ethernet address 00:a0:c9:49:74:bc chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 ahc0: rev 0x00 int a irq 11 on pci0.9. 0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16/255 SCBs ahc0: waiting for scsi devices to settle scbus0 at ahc0 bus 0 ahc0: target 0 Tagged Queuing Device sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 4340MB (8890029 512 byte sectors) vga0: rev 0x9a on pci0.15.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 not found at 0x1f0 wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, ovlap, dma, iordy wcd0: 2067Kb/sec, 256Kb cache, audio play, 255 volume levels, ejectable tray wcd0: no disc inside, unlocked npx0 on motherboard npx0: INT 16 interface changing root device to sd0s1a -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jun 11 15:39:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18599 for freebsd-stable-outgoing; Thu, 11 Jun 1998 15:39:43 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18516 for ; Thu, 11 Jun 1998 15:39:22 -0700 (PDT) (envelope-from danny@panda.hilink.com.au) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id IAA23762; Fri, 12 Jun 1998 08:38:59 +1000 (EST) Date: Fri, 12 Jun 1998 08:38:59 +1000 (EST) From: "Daniel O'Callaghan" To: Eternal cc: freebsd-stable@FreeBSD.ORG Subject: Re: Network Ports In-Reply-To: <01bd9573$d529b560$fa0c56d1@et.foci.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, 11 Jun 1998, Eternal wrote: > telnetd: All network ports in use. > > How can I fix this error ? My maxusers is at 512, pty's at 64, and other > options in the kernel set above normal levels. Use MAKEDEV to make more ptys. You have probably only got ttyp{0-v} - 32 ports. Danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jun 11 15:52:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21670 for freebsd-stable-outgoing; Thu, 11 Jun 1998 15:52:15 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA21534 for ; Thu, 11 Jun 1998 15:51:48 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0ykGC2-0006Og-00; Thu, 11 Jun 1998 15:51:38 -0700 Date: Thu, 11 Jun 1998 15:51:35 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: John Kenagy cc: Atipa , freebsd-stable@FreeBSD.ORG Subject: Re: NIS client maintenance script 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, 10 Jun 1998, John Kenagy wrote: > Thanks! > > I'll give this a try in a day or so and post it with the tutorial > as well. Or, would you rather I posted a link to the source file? > > Also, please send me your full name, etc. so I can credit you. > (I know I've seen it but can't find it now, oops.) > > John There are several problems with the script as attached. It assumes only one NIS server ($nis_host). You'd have to be mad to have only one NIS server in a production environment, especially since clients can automatically kick over to another if one fails. Since all the *pwnam fuctions (getpwnam, getpwent, etc) are flawed in that they can not return a temporary failure code, such functions should block until NIS services are back up. This is critical for systems running mail service, because you don't want all your users to disappear when NIS goes down. Tom > > > Everyone, > > > > > > You may find this script to be of use for NIS clients. It can be run from > > > crontab every minute or so to make sure NIS connections are up and > > > running. > > > > > > It disables NIS authentication during network failures, and > > > resets and enables NIS if the connection is restored. > > > > > > Must be run as root. May work with /bin/sh, but I like bash better. > > > > > > WARNING!!! This may modify your /etc/master.password file. If you can not > > > understand what it does, do not use it! :) > > > > > > Kevin > > > > > > > > > ----- > > > #!/usr/local/bin/bash > > > > > > # This script maintains NIS client connections on simple networks > > > # Rev. 1.0, 05-09-98, Kevin McCarthy (kmcc@atipa.com) > > > > > > # It disables NIS authentication during network failures, and resets > > > # and enables NIS if the connection is restored. > > > > > > # User defined variables > > > nis_host="host.domain.tld" # required > > > nis_domainname="freakazoid" # required > > > ypbind_args="-s -ypsetme" # -s for security > > > ypset_args="$nis_host" # "" for no ypset > > > > > > # Clearspace for readability > > > echo " " > > > > > > # Find current state (bool) of NIS > > > nis_state=`grep + /etc/master.passwd && ps ax |grep yp` > > > if [ -n "$nis_state" ]; then > > > echo NIS authentication is ON > > > else > > > echo NIS authentication is OFF > > > fi > > > > > > # Set up NIS conditional functions > > > function nis_down () { > > > echo "Error: $nis_problem" > > > > > > if [ -n "$nis_state"]; then > > > echo "Disabling NIS authentication" > > > umask 077 > > > grep -v + /etc/master.passwd > /root/mp.nonis > > > mv /etc/master.passwd /etc/master.passwd.nis > > > mv /root/mp.nonis /etc/master.passwd > > > pwd_mkdb -p /etc/master.passwd > > > else > > > echo "NIS remaining disabled" > > > fi > > > > > > exit 1 > > > } > > > > > > function nis_reset () { > > > if [ -n "$nis_problem"]; then > > > echo "Error: $nis_problem" > > > fi > > > > > > echo -n "Resetting NIS services... " > > > killall ypbind >> /dev/null > > > domainname $nis_domainname > > > ypbind $ypbind_args > > > if [ -n "$ypset_args"]; then > > > ypset $ypset_args > > > fi > > > echo "Done" > > > > > > reset_done="true" > > > } > > > > > > function nis_up () { > > > if [ -z "$nis_state" ]; then > > > echo "NIS services restored. Enabling NIS authentication" > > > umask 077 > > > mv /etc/master.passwd.nis /etc/master.passwd > > > pwd_mkdb -p /etc/master.passwd > > > fi > > > > > > nis_working="true" > > > } > > > > > > echo -n "Network connecion to $nis_host is " > > > up=`ping -c1 $nis_host | grep transmitted | awk -F, '{print $2}' \ > > > | awk '{print $1}'` > > > if [ "$up" = "1" ]; then > > > echo ON > > > else > > > echo OFF > > > nis_problem="host not reachable (ping failed)" > > > nis_down > > > fi > > > > > > while [ -z "$nis_working" ]; do > > > # Check if NIS is bound > > > nis_bound=`ypwhich` > > > > > > if [ "$nis_bound" = "$nis_host" ]; then > > > echo NIS binding to $nis_bound is ON > > > nis_up > > > else > > > if [ -z "$reset_done" ]; then > > > nis_problem="NIS binding to $nis_host is OFF" > > > nis_reset > > > else > > > echo "Reset Failed; disabling NIS services" > > > nis_down > > > fi > > > fi > > > done > > > > > > echo "Exiting" > > > echo " " > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jun 11 16:32:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29457 for freebsd-stable-outgoing; Thu, 11 Jun 1998 16:32:24 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.atipa.com (altrox.atipa.com [208.128.22.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA29441 for ; Thu, 11 Jun 1998 16:32:13 -0700 (PDT) (envelope-from freebsd@atipa.com) Received: (qmail 14687 invoked by uid 1017); 11 Jun 1998 22:29:10 -0000 Date: Thu, 11 Jun 1998 16:29:10 -0600 (MDT) From: Atipa To: Tom cc: John Kenagy , freebsd-stable@FreeBSD.ORG Subject: Re: NIS client maintenance script 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 > There are several problems with the script as attached. > > It assumes only one NIS server ($nis_host). You'd have to be mad to > have only one NIS server in a production environment, especially since > clients can automatically kick over to another if one fails. Correct. This script is not dynamic. I am using it primarily for machines w/o NIS servers on their network. Setting up slave servers would eliminate several problems. > Since all the *pwnam fuctions (getpwnam, getpwent, etc) are flawed in > that they can not return a temporary failure code, such functions should > block until NIS services are back up. This is critical for systems > running mail service, because you don't want all your users to disappear > when NIS goes down. But you don't want to have to wait 14 minutes (7 minutes each for user login, then su) to remedy problems. If no network services are available, your users will go away period, unless they are somehow cached (eg slave server). Suggestions? Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jun 11 16:45:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02793 for freebsd-stable-outgoing; Thu, 11 Jun 1998 16:45:00 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA02647 for ; Thu, 11 Jun 1998 16:44:33 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0ykH14-0000BP-00; Thu, 11 Jun 1998 16:44:22 -0700 Date: Thu, 11 Jun 1998 16:44:19 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Atipa cc: John Kenagy , freebsd-stable@FreeBSD.ORG Subject: Re: NIS client maintenance script 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, 11 Jun 1998, Atipa wrote: > > There are several problems with the script as attached. > > > > It assumes only one NIS server ($nis_host). You'd have to be mad to > > have only one NIS server in a production environment, especially since > > clients can automatically kick over to another if one fails. > > Correct. This script is not dynamic. I am using it primarily for machines > w/o NIS servers on their network. Setting up slave servers would eliminate > several problems. Yes, but the new ypbind has no problems handling multiple non-local servers. I'm hoping to see it committed before 2.2.7. > > Since all the *pwnam fuctions (getpwnam, getpwent, etc) are flawed in > > that they can not return a temporary failure code, such functions should > > block until NIS services are back up. This is critical for systems > > running mail service, because you don't want all your users to disappear > > when NIS goes down. > > But you don't want to have to wait 14 minutes (7 minutes each for user > login, then su) to remedy problems. Yes, but admin users should be listed in the system /etc/master.passwd so they can always login. The current yplib is bit broken in that it depends on YP even if all necessary info for login is in /etc. For example, if you only have a "+" in master.passwd, root should be able to login without delay, even if YP is down. > If no network services are available, your users will go away period, > unless they are somehow cached (eg slave server). For example, it is better that e-mail be delayed until YP is back up, rather than to bounce all e-mail as "user unknown" while YP is down. > Suggestions? > > Kevin Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jun 11 17:01:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06603 for freebsd-stable-outgoing; Thu, 11 Jun 1998 17:01:13 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mx.calweb.com (mx.calweb.com [208.131.56.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06576 for ; Thu, 11 Jun 1998 17:01:04 -0700 (PDT) (envelope-from rdugaue@calweb.com) Received: by mx.calweb.com (8.8.6/8.8.6) with SMTP id RAA20260; Thu, 11 Jun 1998 17:00:45 -0700 (PDT) X-SMTP: helo web2.calweb.com from rdugaue@calweb.com server rdugaue@web2.calweb.com ip 208.131.56.52 Date: Thu, 11 Jun 1998 17:00:44 -0700 (PDT) From: Robert Du Gaue Reply-To: Robert Du Gaue To: Doug Russell cc: "Viren R. Shah" , stable@FreeBSD.ORG Subject: Re: NFS server performance (was: NFS performance benchmarks?) 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 > Writing the 20 Megabyte file, 'iozone.tmp'...46.320312 seconds > Reading the file...25.390625 seconds > > IOZONE performance measurements: > 452749 bytes/second for writing the file > 825955 bytes/second for reading the file There's gotta be something screwy somewhere. Here's what I'm getting over NFS to a PPro-200 System with a SCSI-to-SCSI RAID (16MB cache) from Artecon: Writing the 50 Megabyte file, 'iozone.tmp'...23.679688 seconds Reading the file...18.742188 seconds IOZONE performance measurements: 2214083 bytes/second for writing the file 2797368 bytes/second for reading the file The NFS server is 100Base-T Full Duplex, the client I ran iozone on was 10-BaseT half duplex. Both are connected to an Intel 510T 10/100 switch. Running the same test on a client that is also 100Base-T Full Duplex on the same switch results in: Writing the 50 Megabyte file, 'iozone.tmp'...18.515625 seconds Reading the file...8.375000 seconds IOZONE performance measurements: 2831597 bytes/second for writing the file 6260155 bytes/second for reading the file I would look at your NIC cards, the HUB/Switch (if any), and cache in the RAID controller as possible bottlenecks. ----- For comparison... The Artecon is a pretty fast RAID system from what I can see. Doing an iozone local to the NFS on the RAID gets: Writing the 256 Megabyte file, 'iozone.tmp'...25.164062 seconds Reading the file...11.546875 seconds IOZONE performance measurements: 10667413 bytes/second for writing the file 23247454 bytes/second for reading the file -------------------------------------------------------------------------- Robert Du Gaue - rdugaue@calweb.com http://www.calweb.com President, CalWeb Internet Services Inc. (916) 641-9320 -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jun 11 18:00:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19729 for freebsd-stable-outgoing; Thu, 11 Jun 1998 18:00:36 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from passer.osg.gov.bc.ca (passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19616 for ; Thu, 11 Jun 1998 18:00:22 -0700 (PDT) (envelope-from cschuber@passer.osg.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.0/8.6.10) id SAA19961; Thu, 11 Jun 1998 18:00:08 -0700 (PDT) Message-Id: <199806120100.SAA19961@passer.osg.gov.bc.ca> Received: from localhost(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost, id smtpdaaurca; Thu Jun 11 18:00:05 1998 X-Mailer: exmh version 2.0gamma 1/27/96 Reply-to: Cy Schubert - ITSD Open Systems Group X-Sender: cschuber To: durkin cc: Cy Schubert - ITSD Open Systems Group , freebsd-stable@FreeBSD.ORG Subject: Re: rc.firewall and ipfw commands In-reply-to: Your message of "Thu, 11 Jun 1998 16:39:39 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Jun 1998 17:59:34 -0700 From: Cy Schubert - ITSD Open Systems Group Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > On Wed, 10 Jun 1998, Cy Schubert - ITSD Open Systems Group wrote: > > > In my firewall configurations I modify rc.firewall to recognize a > > "user" firewall type (for user defined) and specify > > firewall_type="user" in my rc.conf. The "user" firewall type executes > > /usr/local/etc/rc.firewall.local instead of one of the predefined > > firewall types in rc.firewall. This may be a handy feature in the > > stock FreeBSD rc.firewall. If anyone wishes I can submit a PR to have > > this included in the FreeBSD distribution. > > > > Actually, FreeBSD's rc.firewall already has the ability to load ipfw > commands contained within a file. Just specify the firewall type as the > filename which contains the commands. That is true, however one may wish to use a shell script to dynamically build a firewall based on various dynamic conditions. rc.firewall gets executed early enough in the boot that it may make my point moot, in which case rc.firewall would block everything, except DNS and NIS, then rc.local would open the firewall a bit, once applications are up using a more dynamic firewall setup script which would scan the system looking for ports to open up, and make the system useful again, e.g. open up ypserver port (which is dynamically assigned) only to NIS clients. You're probably right that no change to the existing rc scripts is required. I'll have to think about this a little more... Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: cschuber@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Government of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jun 11 20:43:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19746 for freebsd-stable-outgoing; Thu, 11 Jun 1998 20:43:03 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19717 for ; Thu, 11 Jun 1998 20:42:44 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id UAA07562; Thu, 11 Jun 1998 20:42:38 -0700 (PDT) (envelope-from jdp) Message-Id: <199806120342.UAA07562@austin.polstra.com> To: evanc@synapse.net Subject: Re: setuid on directory In-Reply-To: <004601bd9197$2666c340$c9252fce@cello.synapse.net> References: <004601bd9197$2666c340$c9252fce@cello.synapse.net> Organization: Polstra & Co., Seattle, WA Cc: stable@FreeBSD.ORG Date: Thu, 11 Jun 1998 20:42:38 -0700 From: John Polstra Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <004601bd9197$2666c340$c9252fce@cello.synapse.net>, Evan Champion wrote: > The manpage for chmod(1) says that if one sets the setuid bit on a > directory, files created within that directory will be owned by the owner of > the directory and not the uid of the current process. I suppose that pedantically speaking the man page is correct, since it goes on to say "if the underlying file system supports this feature: see chmod(2) and the suiddir option to mount(1)." Of course, no filesystems support this feature, and the suiddir option to mount(1) doesn't exist, as far as I can tell. :-) But speaking as a Man Of Reason, I have to agree with you that this is bogus. > A similar idea goes for the setgid bit. Actually, I don't see anything along those lines in chmod(1). -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jun 11 20:53:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21124 for freebsd-stable-outgoing; Thu, 11 Jun 1998 20:53:08 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA21117 for ; Thu, 11 Jun 1998 20:53:01 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id UAA07626; Thu, 11 Jun 1998 20:52:58 -0700 (PDT) (envelope-from jdp) Message-Id: <199806120352.UAA07626@austin.polstra.com> To: evanc@synapse.net Subject: Re: setuid on directory In-Reply-To: <004601bd9197$2666c340$c9252fce@cello.synapse.net> References: <004601bd9197$2666c340$c9252fce@cello.synapse.net> Organization: Polstra & Co., Seattle, WA Cc: stable@FreeBSD.ORG Date: Thu, 11 Jun 1998 20:52:58 -0700 From: John Polstra Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops. I wrote: > In article <004601bd9197$2666c340$c9252fce@cello.synapse.net>, > Evan Champion wrote: > > > The manpage for chmod(1) says that if one sets the setuid bit on a > > directory, files created within that directory will be owned by the owner of > > the directory and not the uid of the current process. > > I suppose that pedantically speaking the man page is correct, since it > goes on to say "if the underlying file system supports this feature: > see chmod(2) and the suiddir option to mount(1)." Of course, no > filesystems support this feature, and the suiddir option to mount(1) > doesn't exist, as far as I can tell. :-) I was wrong. It seems the "suiddir" option does exist after all. I don't know whether it works or not. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jun 11 20:56:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21724 for freebsd-stable-outgoing; Thu, 11 Jun 1998 20:56:12 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from conductor.synapse.net (conductor.synapse.net [199.84.54.18]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA21628 for ; Thu, 11 Jun 1998 20:55:55 -0700 (PDT) (envelope-from evanc@synapse.net) Received: (qmail 27939 invoked from network); 12 Jun 1998 03:55:52 -0000 Received: from localhost (HELO cello) (127.0.0.1) by localhost with SMTP; 12 Jun 1998 03:55:52 -0000 Message-ID: <00c501bd95b6$011ff520$c9252fce@cello.synapse.net> From: "Evan Champion" To: "John Polstra" Cc: Subject: Re: setuid on directory Date: Thu, 11 Jun 1998 23:55:55 -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 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >But speaking as a Man Of Reason, I have to agree with you that this >is bogus. :-) >> A similar idea goes for the setgid bit. > >Actually, I don't see anything along those lines in chmod(1). Ack, you're right, it doesn't. The sentences start so similarly that I didn't notice the one for setgid doesn't mention any effect on directories. Evan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jun 11 21:00:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22329 for freebsd-stable-outgoing; Thu, 11 Jun 1998 21:00:24 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from conductor.synapse.net (conductor.synapse.net [199.84.54.18]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA22219 for ; Thu, 11 Jun 1998 20:59:44 -0700 (PDT) (envelope-from evanc@synapse.net) Received: (qmail 28411 invoked from network); 12 Jun 1998 03:59:44 -0000 Received: from localhost (HELO cello) (127.0.0.1) by localhost with SMTP; 12 Jun 1998 03:59:44 -0000 Message-ID: <00cf01bd95b6$8ac08060$c9252fce@cello.synapse.net> From: "Evan Champion" To: "John Polstra" Cc: Subject: Re: setuid on directory Date: Thu, 11 Jun 1998 23:59:44 -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 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I was wrong. It seems the "suiddir" option does exist after all. I >don't know whether it works or not. Hum. I think I need my glasses cleaned :-) I could swear I read the manpage a few times and didn't see anything about special mount options. It's not that I'm really all that interested in trying it, it was just not something that I thought one could even do. Well, I'm sure I found at least one mistake in that manpage; it's mount(8) not mount(1) :-) Evan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jun 11 21:02:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22740 for freebsd-stable-outgoing; Thu, 11 Jun 1998 21:02:34 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22704 for ; Thu, 11 Jun 1998 21:02:24 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id VAA07758; Thu, 11 Jun 1998 21:02:19 -0700 (PDT) (envelope-from jdp) Message-Id: <199806120402.VAA07758@austin.polstra.com> To: "Evan Champion" cc: stable@FreeBSD.ORG Subject: Re: setuid on directory In-reply-to: Your message of "Thu, 11 Jun 1998 23:59:44 EDT." <00cf01bd95b6$8ac08060$c9252fce@cello.synapse.net> Date: Thu, 11 Jun 1998 21:02:18 -0700 From: John Polstra Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, I'm sure I found at least one mistake in that manpage; it's ) > mount(8 not mount(1) :- ) Heh, what difference does it make? The mount man page doesn't mention the suiddir option anyway. :-) I had to look in the sources to find it. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jun 11 21:09:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24031 for freebsd-stable-outgoing; Thu, 11 Jun 1998 21:09:59 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from conductor.synapse.net (conductor.synapse.net [199.84.54.18]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA24019 for ; Thu, 11 Jun 1998 21:09:49 -0700 (PDT) (envelope-from evanc@synapse.net) Received: (qmail 28980 invoked from network); 12 Jun 1998 04:09:46 -0000 Received: from localhost (HELO cello) (127.0.0.1) by localhost with SMTP; 12 Jun 1998 04:09:46 -0000 Message-ID: <010b01bd95b7$f0951da0$c9252fce@cello.synapse.net> From: "Evan Champion" To: "John Polstra" Cc: Subject: Re: setuid on directory Date: Fri, 12 Jun 1998 00:09:46 -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 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Heh, what difference does it make? The mount man page doesn't >mention the suiddir option anyway. :-) I had to look in the sources >to find it. Hum, it must have been precognition then; I sensed the man page wouldn't say anything and thus didn't bother to go look at it :-) I suppose if the feature is in the source, the manpage probably needs to be fixed then. Unless someone was hoping this feature would just disappear :-) Evan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jun 12 00:09:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA19784 for freebsd-stable-outgoing; Fri, 12 Jun 1998 00:09:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from softweyr.com ([204.68.178.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA19760 for ; Fri, 12 Jun 1998 00:09:42 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (zaphod.softweyr.com [204.68.178.35]) by softweyr.com (8.8.8/8.8.7) with ESMTP id BAA16989; Fri, 12 Jun 1998 01:09:10 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <358225EE.783ED931@softweyr.com> Date: Sat, 13 Jun 1998 01:10:38 -0600 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: Robert Du Gaue CC: Doug Russell , "Viren R. Shah" , stable@FreeBSD.ORG Subject: Re: NFS server performance (was: NFS performance benchmarks?) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Du Gaue wrote: > > > Writing the 20 Megabyte file, 'iozone.tmp'...46.320312 seconds > > Reading the file...25.390625 seconds > > > > IOZONE performance measurements: > > 452749 bytes/second for writing the file > > 825955 bytes/second for reading the file > > There's gotta be something screwy somewhere. Here's what I'm getting over > NFS to a PPro-200 System with a SCSI-to-SCSI RAID (16MB cache) from > Artecon: > > Writing the 50 Megabyte file, 'iozone.tmp'...23.679688 seconds > Reading the file...18.742188 seconds > > IOZONE performance measurements: > 2214083 bytes/second for writing the file > 2797368 bytes/second for reading the file I agree. Have you read the FAQs about NFS server with Sun clients? You may want to carefully specify NFS v2, for both clients and servers, at least on the client -> FreeBSD server link. To be fair, you should use whichever protocol version is fastest with the Solaris server, probably V3. If your client is SunOS older than 4.1.4, you probably don't have V3 support. By the way, I expect a Solaris server running on SMP hardware to out- perform a FreeBSD server; their threaded NFS server is quite fast. For the difference in price for the hardware, FreeBSD certainly provides acceptable performance. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jun 12 05:20:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA26799 for freebsd-stable-outgoing; Fri, 12 Jun 1998 05:20:23 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cesit1.unifi.it (cesit1.unifi.it [150.217.1.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA26650 for ; Fri, 12 Jun 1998 05:19:52 -0700 (PDT) (envelope-from ugo@dsi.UNIFI.IT) Received: from aguirre.dsi.unifi.it by CESIT1.UNIFI.IT (PMDF V5.1-10 #23168) with SMTP id <01IY5HDPQ1OQ0004W7@CESIT1.UNIFI.IT> for freebsd-stable@FreeBSD.ORG; Fri, 12 Jun 1998 14:19:40 MET Received: from dsi.unifi.it (ppp-firenze71-74.iol.it) by aguirre.dsi.unifi.it (4.1/SMI-4.1) id AA25159; Fri, 12 Jun 1998 14:19:01 +0200 Received: from pegasus.home.net (pegasus.home.net [192.168.1.3]) by dsi.unifi.it (8.8.8/8.8.8) with ESMTP id MAA03726; Fri, 12 Jun 1998 12:38:50 +0200 (MET DST envelope-from ugo) Received: (from ugo@localhost) by pegasus.home.net (8.8.8/8.8.8) id MAA03636; Fri, 12 Jun 1998 12:38:50 +0200 (MET DST envelope-from ugo) Date: Fri, 12 Jun 1998 12:38:50 +0200 (MET DST) From: Ugo Paternostro Subject: Re: PnP support for if_ed, and more... In-reply-to: <199806060121.SAA02536@dingo.cdrom.com> To: Mike Smith Cc: Luigi Rizzo , freebsd-stable@FreeBSD.ORG, eivind@yes.no (Eivind Eklund) Message-id: Organization: Not an organization MIME-version: 1.0 X-Mailer: XFMail 1.2 [p0] on FreeBSD Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Priority: 3 (Normal) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Jun-98 Mike Smith wrote about "Re: PnP support for if_ed, and more...": > and then work out a mechanism to scan the 'compatible device ID' > descriptors (0x1c) and pretend that the device is one of these if the > first pass (try for an exact match on the device ID) fails. The code is working here. I have a few questions: - I'm working on -stable, so someone else should take care of -current... [well this isn't really a question :-)] - I would like to MFC some code (mainly isa.c 1.103 -> 1.104), but I understand that I should avoid mixing the diffs togheter. What do you suggest? Should I reply to my own PR (i386/6792) with just the Compatible Device ID patch and open a new PR to backport that isa.c change? The problem is that I need to change both isa.c and pnp.c at the same time to let that MFC work, so at the end of the game I need to change pnp.c twice. - I used the same array for both Vendor IDs and Compatible Device IDs, like in: static struct edpnp_ids { u_long vend_id; char *id_str; } edpnp_ids[] = { { 0x1980635e, "WSC8019"}, { 0xd680d041, "NE2000 Compatible"}, { 0 } }; and it works: [...] Probing for PnP devices: CSN 1 Vendor ID: WSC9008 [0x0890635e] Serial 0xdea47218 Comp ID: PNP80d6 [0xd680 d041] ed1: address 00:20:18:72:a4:de, type NE2000 (16 bit) ed1 (edpnp sn 0xdea47218) at 0x280 irq 12 drq -1 flags 0x0 i d 14 Probing for devices on the ISA bus: [...] Should I fix/remove bogus/useless Vendor IDs from if_ed.c and sio.c? - I still would like to remove that structure definition (edpnp_ids) from sio.c and if_ed.c to put it into pnp.h - talking about sio.c, I don't have anymore the SupraExpress internal modem, so I don't know what its Compatible Device ID looks like. There are a lot of possible definitions in devids.txt (see PNP0500 -> PNP0502, plus PNPCxxx -> PNPDxxx). I would be glad to everyone that sends to me its pnpinfo output... > \\ Sometimes you're ahead, \\ Mike Smith Bye, UP To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jun 12 06:19:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA07359 for freebsd-stable-outgoing; Fri, 12 Jun 1998 06:19:45 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from assurance ([206.29.49.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA07347 for ; Fri, 12 Jun 1998 06:19:37 -0700 (PDT) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance (8.7.5/8.6.9) id JAA17445; Fri, 12 Jun 1998 09:19:04 -0400 Received: from sandbox.rstcorp.com(206.29.49.63) by assurance.rstcorp.com via smap (V2.0) id xma017439; Fri, 12 Jun 98 09:18:07 -0400 Received: from fault.rstcorp.com (fault [206.29.49.18]) by sandbox.rstcorp.com (8.8.8/8.8.8) with ESMTP id JAA08098; Fri, 12 Jun 1998 09:18:05 -0400 (EDT) Received: (from vshah@localhost) by fault.rstcorp.com (8.8.8/8.8.8) id JAA09212; Fri, 12 Jun 1998 09:16:20 -0400 (EDT) Date: Fri, 12 Jun 1998 09:16:20 -0400 (EDT) Message-Id: <199806121316.JAA09212@fault.rstcorp.com> From: "Viren R. Shah" To: Wes Peters Cc: freebsd-stable@FreeBSD.ORG, Robert Du Gaue , Doug Russell Subject: Re: NFS server performance (was: NFS performance benchmarks?) In-Reply-To: <358225EE.783ED931@softweyr.com> References: <358225EE.783ED931@softweyr.com> X-Mailer: VM 6.40 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Wes" == Wes Peters writes: [Thanks a lot for the responses.] Doug> There must be some time of flakiness occuring here. (Perhaps Doug> some strange incompatibility due to the SunOS client??) I have Doug> used iozone to test Robert> I would look at your NIC cards, the HUB/Switch (if any), Wes> I agree. Have you read the FAQs about NFS server with Sun clients? Yes. The FreeBSD Server only accepts NFSv2 mounts (using the -2 flag on mountd). NFSv3 was said to be too unstable to use in a production system. The system specs are as follows: PII-300 w/ 128M RAM Adaptec aic7880 Ultra SCSI host adapter Intel EtherExpress PRO/100+ card. 3COM hub The card is: fxp0: flags=8843 mtu 1500 inet 206.29.49.78 netmask 0xffffff80 broadcast 206.29.49.127 ether 00:a0:c9:ce:ea:4a media: autoselect The one problem seems to be: [vshah@hal] ~/extraspace> netstat -i | more Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll fxp0 1500 00.a0.c9.ce.ea.4a 43972311 183 43193398 2 1842570 fxp0 1500 206.29.49/25 hal.rstcorp.com 43972311 183 43193398 2 1842570 There seem to be a lot of collisions on the card. Is this indicative of anything? Should the NIC be forced into 100baseT/full-duplex mode? The 100Mb segment only has a couple of Ultras, the FreeBSD server and a couple of NT boxes on there (basically all the different server type boxen). Wes> By the way, I expect a Solaris server running on SMP hardware to out- Wes> perform a FreeBSD server; their threaded NFS server is quite fast. The Solaris server is an Ultra-1 without any RAID. Wes> Wes Peters Softweyr LLC Thanks Viren -- Viren R. Shah {viren @ rstcorp . com} Names : Vanadium(23) Iodine(53) RhEnium(75) Nitrogen(7) Density(g/mL): 5.8 4.92 21 0.0001251 Average Density: 7.93003 g/mL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jun 12 08:35:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00825 for freebsd-stable-outgoing; Fri, 12 Jun 1998 08:35:12 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00811 for ; Fri, 12 Jun 1998 08:35:03 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id PAA05007; Fri, 12 Jun 1998 15:35:01 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id RAA25166; Fri, 12 Jun 1998 17:35:01 +0200 (MET DST) Message-ID: <19980612173501.38618@follo.net> Date: Fri, 12 Jun 1998 17:35:01 +0200 From: Eivind Eklund To: Evan Champion , John Polstra Cc: stable@FreeBSD.ORG Subject: Re: setuid on directory References: <010b01bd95b7$f0951da0$c9252fce@cello.synapse.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <010b01bd95b7$f0951da0$c9252fce@cello.synapse.net>; from Evan Champion on Fri, Jun 12, 1998 at 12:09:46AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 12, 1998 at 12:09:46AM -0400, Evan Champion wrote: > >Heh, what difference does it make? The mount man page doesn't > >mention the suiddir option anyway. :-) I had to look in the sources > >to find it. > > > Hum, it must have been precognition then; I sensed the man page wouldn't say > anything and thus didn't bother to go look at it :-) > > I suppose if the feature is in the source, the manpage probably needs to be > fixed then. Unless someone was hoping this feature would just disappear :-) There was a fair bit of opposition to it when it was added. Personally, I hope it should stay, and probably become a default part of the compile (ie, not "options SUIDDIR" necessary). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jun 12 09:38:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17020 for freebsd-stable-outgoing; Fri, 12 Jun 1998 09:38:59 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from keaggy.canonware.com (canonware.com [206.184.206.112]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16858 for ; Fri, 12 Jun 1998 09:38:19 -0700 (PDT) (envelope-from jasone@canonware.com) Received: from localhost (jasone@localhost) by keaggy.canonware.com (8.8.8/8.8.7) with SMTP id JAA22182 for ; Fri, 12 Jun 1998 09:34:43 -0700 (PDT) (envelope-from jasone@canonware.com) Date: Fri, 12 Jun 1998 09:34:42 -0700 (PDT) From: Jason Evans To: freebsd-stable@FreeBSD.ORG Subject: fsck infinite loop 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 morning I finished up with a 'make world' and a new kernel installation to bring a system from 2.2.5 to -stable. When I rebooted I got the standard error unmounting file systems (apparently due to open nfs mounted files). I've had that happen many times before, with nothing more than a completely successful fsck. However, this morning, fsck went into an infinite loop with the following message: wd0s2e: soft error reading fsbn 132033 of 132032-132143 (wd0s2 bn 787393; cn 97 tn 82 sn 19) wd0; status 58 error 1 So, questions: 1) Is this a hardware or a software (logical disk corruption) error? 2) If it's a software error, what could cause fsck to loop infinitely? 3) Is there anything I can do to fix this short of re-installing, possibly on a new disk? Thanks, Jason Jason Evans Email: [jasone@canonware.com] Web: [http://www.canonware.com/~jasone] Home phone: [(650) 856-8204] Work phone: [(408) 774-8007] Quote: ["Invention is 1% inspiration and 99% perspiration" - Thomas Edison] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jun 12 11:01:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03150 for freebsd-stable-outgoing; Fri, 12 Jun 1998 11:01:57 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.atipa.com (altrox.atipa.com [208.128.22.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA03050 for ; Fri, 12 Jun 1998 11:01:20 -0700 (PDT) (envelope-from freebsd@atipa.com) Received: (qmail 17197 invoked by uid 1017); 12 Jun 1998 16:58:24 -0000 Date: Fri, 12 Jun 1998 10:58:24 -0600 (MDT) From: Atipa To: Tom cc: John Kenagy , freebsd-stable@FreeBSD.ORG Subject: Re: NIS client maintenance script 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 > > > It assumes only one NIS server ($nis_host). You'd have to be mad to > > > have only one NIS server in a production environment, especially since > > > clients can automatically kick over to another if one fails. > > > > Correct. This script is not dynamic. I am using it primarily for machines > > w/o NIS servers on their network. Setting up slave servers would eliminate > > several problems. > > Yes, but the new ypbind has no problems handling multiple non-local > servers. I'm hoping to see it committed before 2.2.7. Do you have diffs? I'd be happy to test in on -STABLE. Does it need any of -CURRENT's RPC stuff? > > > Since all the *pwnam fuctions (getpwnam, getpwent, etc) are flawed in > > > that they can not return a temporary failure code, such functions should > > > block until NIS services are back up. This is critical for systems > > > running mail service, because you don't want all your users to disappear > > > when NIS goes down. > > > > But you don't want to have to wait 14 minutes (7 minutes each for user > > login, then su) to remedy problems. > > Yes, but admin users should be listed in the system /etc/master.passwd > so they can always login. The current yplib is bit broken in that it > depends on YP even if all necessary info for login is in /etc. For > example, if you only have a "+" in master.passwd, root should be able to > login without delay, even if YP is down. No, I agree. I do not have any "wheeled" accounts on NIS (for that reason, and security), but if NIS authentication is enabled (any +'s) in /etc/master.passwd, and the domain is not bound, it _still_ takes 14 minutes to su. I thought that was standard behavior; is my setup wrong somehow? > > If no network services are available, your users will go away period, > > unless they are somehow cached (eg slave server). > > For example, it is better that e-mail be delayed until YP is back up, > rather than to bounce all e-mail as "user unknown" while YP is down. How would having +'s in your /etc/master.passwd postpone mail delivery? I think I must be missing a step here. In the case of NIS server being down, I have _no_ user lists at all, but I do have _serious_ delays authenticating users listed locally (wheels, etc.). That is why this script takes out all +'s if the domain is not bound. No, you can't get user info, but you couldn't anyway (w/o caching), and now you can log in w/o delays. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jun 12 11:07:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04477 for freebsd-stable-outgoing; Fri, 12 Jun 1998 11:07:44 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA04355 for ; Fri, 12 Jun 1998 11:07:13 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0ykYEB-0004lO-00; Fri, 12 Jun 1998 11:07:03 -0700 Date: Fri, 12 Jun 1998 11:07:01 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Atipa cc: John Kenagy , freebsd-stable@FreeBSD.ORG Subject: Re: NIS client maintenance script 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, 12 Jun 1998, Atipa wrote: > No, I agree. I do not have any "wheeled" accounts on NIS (for that reason, > and security), but if NIS authentication is enabled (any +'s) in > /etc/master.passwd, and the domain is not bound, it _still_ takes 14 > minutes to su. I thought that was standard behavior; is my setup wrong > somehow? It is standard broken behaviour. The FreeBSD yplib needs fixing, as delays for local accounts is completely unnecessary. It also means that YP is being referred to more often than necessary, meaning that there is some (albeit, perhaps very small) unnecessary YP load even when YP is working normally. > > > If no network services are available, your users will go away period, > > > unless they are somehow cached (eg slave server). > > > > For example, it is better that e-mail be delayed until YP is back up, > > rather than to bounce all e-mail as "user unknown" while YP is down. > > How would having +'s in your /etc/master.passwd postpone mail delivery? I Because YP calls take so long, that mail times out, at which point it is retried later. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jun 12 12:02:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16577 for freebsd-stable-outgoing; Fri, 12 Jun 1998 12:02:10 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA16373 for ; Fri, 12 Jun 1998 12:01:08 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0ykZ4P-0002KB-00; Fri, 12 Jun 1998 12:01:01 -0700 Date: Fri, 12 Jun 1998 12:00:59 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Jason Evans cc: freebsd-stable@FreeBSD.ORG Subject: Re: fsck infinite loop 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, 12 Jun 1998, Jason Evans wrote: > wd0s2e: soft error reading fsbn 132033 of 132032-132143 (wd0s2 bn 787393; > cn 97 tn 82 sn 19) wd0; status 58 error 1 > > So, questions: > > 1) Is this a hardware or a software (logical disk corruption) error? Hardware. > 2) If it's a software error, what could cause fsck to loop infinitely? fsck is not looping. The wd driver is looping because it is retrying again and again. > 3) Is there anything I can do to fix this short of re-installing, possibly > on a new disk? Try a couple of extended power cycles. You may get lucky and the disk may decide to behave, but you should plan a reinstall on a new disk. > Thanks, > Jason > > Jason Evans > Email: [jasone@canonware.com] > Web: [http://www.canonware.com/~jasone] > Home phone: [(650) 856-8204] > Work phone: [(408) 774-8007] > Quote: ["Invention is 1% inspiration and 99% perspiration" - Thomas Edison] Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jun 12 12:51:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27684 for freebsd-stable-outgoing; Fri, 12 Jun 1998 12:51:33 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from hobbes.saturn-tech.com (drussell@drussell.internode.net [198.161.228.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27643 for ; Fri, 12 Jun 1998 12:51:17 -0700 (PDT) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by hobbes.saturn-tech.com (8.8.4/8.8.2) with SMTP id NAA14437; Fri, 12 Jun 1998 13:50:34 -0600 (MDT) Date: Fri, 12 Jun 1998 13:50:33 -0600 (MDT) From: Doug Russell To: Evan Champion cc: John Polstra , stable@FreeBSD.ORG Subject: Re: setuid on directory In-Reply-To: <00cf01bd95b6$8ac08060$c9252fce@cello.synapse.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, 11 Jun 1998, Evan Champion wrote: > Hum. I think I need my glasses cleaned :-) I could swear I read the > manpage a few times and didn't see anything about special mount options. Everyone seems to be doing this. Perhaps we need to re-organize those paragraphs? :) Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jun 12 13:28:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07071 for freebsd-stable-outgoing; Fri, 12 Jun 1998 13:28:23 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from hobbes.saturn-tech.com (drussell@drussell.internode.net [198.161.228.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07052 for ; Fri, 12 Jun 1998 13:28:10 -0700 (PDT) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by hobbes.saturn-tech.com (8.8.4/8.8.2) with SMTP id OAA14748; Fri, 12 Jun 1998 14:27:30 -0600 (MDT) Date: Fri, 12 Jun 1998 14:27:30 -0600 (MDT) From: Doug Russell To: Robert Du Gaue cc: "Viren R. Shah" , stable@FreeBSD.ORG Subject: Re: NFS server performance (was: NFS performance benchmarks?) 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, 11 Jun 1998, Robert Du Gaue wrote: > > Writing the 20 Megabyte file, 'iozone.tmp'...46.320312 seconds > > Reading the file...25.390625 seconds > > > > IOZONE performance measurements: > > 452749 bytes/second for writing the file > > 825955 bytes/second for reading the file > > There's gotta be something screwy somewhere. Here's what I'm getting over Well, mine isn't screwy.... :) I figure 442K/sec and 806K/sec on a couple of 486es with IDE drives and an NE2000 client isn't bad. I can live with that. :) > IOZONE performance measurements: > 2214083 bytes/second for writing the file > 2797368 bytes/second for reading the file> > > The NFS server is 100Base-T Full Duplex, the client I ran iozone on was > 10-BaseT half duplex. Both are connected to an Intel 510T 10/100 switch. Wait a minute..... How can you get 2162 K/sec on a 10 Mbps link?? > The Artecon is a pretty fast RAID system from what I can see. Doing an > iozone local to the NFS on the RAID gets: > > Writing the 256 Megabyte file, 'iozone.tmp'...25.164062 seconds > Reading the file...11.546875 seconds > > IOZONE performance measurements: > 10667413 bytes/second for writing the file > 23247454 bytes/second for reading the file You are right, that IS fast. :) Want to know how pathetic the disk subsystem on the 486 NFS server from my first test above is? Writing the 32 Megabyte file, 'iozone.tmp'...20.031250 seconds Reading the file...10.273438 seconds IOZONE performance measurements: 1675104 bytes/second for writing the file 3266134 bytes/second for reading the file :) Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jun 12 15:06:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26514 for freebsd-stable-outgoing; Fri, 12 Jun 1998 15:06:33 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from csmd2.cs.uni-magdeburg.de (prinz-atm.cs.uni-magdeburg.de [141.44.30.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26482 for ; Fri, 12 Jun 1998 15:06:18 -0700 (PDT) (envelope-from jesse@prinz-atm.cs.Uni-Magdeburg.DE) Received: from pflaume.cs.uni-magdeburg.de (pflaume-atm [141.44.30.44]) by csmd2.cs.uni-magdeburg.de (8.8.8/8.8.8) with SMTP id OAA05894 for ; Fri, 12 Jun 1998 14:02:04 +0200 (MET DST) Received: by pflaume.cs.uni-magdeburg.de (SMI-8.6/SMI-SVR4) id OAA00682; Fri, 12 Jun 1998 14:02:04 +0200 Date: Fri, 12 Jun 1998 14:02:04 +0200 From: jesse@prinz-atm.cs.Uni-Magdeburg.DE (Roland Jesse) Message-Id: <199806121202.OAA00682@pflaume.cs.uni-magdeburg.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-stable@FreeBSD.ORG Subject: error when building kdebase-4.1b port X-Mailer: VM 6.32 under Emacs 19.34.1 Reply-To: Roland Jesse X-Organization: University of Magdeburg X-Pgp-Fingerprint: 5D 08 5A E3 B4 AA 68 C1 FF 67 06 29 62 DD 9A D7 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I am posting this to -stable and not to -ports because I do not think that the problem is related to the specific port but more to trouble in 2.2-stable. I cvsup'ed my stable sources early on June 10 and built a new world. When trying to make all in /usr/ports/x11/kdebase, I get: ------- begin quote ------- >> Checksum OK for kdebase-beta4-1.src.tar.bz2. ===> Building for kdebase-4.1b make all-recursive Making all in kfm Making all in kfmwarn Making all in client Making all in kioslave Making all in pics Making all in Desktop Making all in Templates Making all in kfmexec c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include -I/usr/X11R6/include/X11/qt -I/usr/X11R6/include -I/usr/local/include/giflib -O2 -m486 -pipe -c kfmgui.cpp In file included from root.h:8, from kfmgui.cpp:29: /usr/X11R6/include/X11/Xlib.h:1074: virtual memory exhausted cpp: output pipe has been closed *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. ------- end quote ------- At this point in time there is more than 200 MB of virtual memory free on my system. The specified line (1074) in Xlib.h is the last line of the typedef of XEDataObject. Honestly, I do not quite see the point of exhausting virtual memory at this point. I am using XFree 3.3.2. Any hints on what is going wrong and how to solve the problem are greatly appreciated. Roland -- "Well," said Trillian in a bright compassionate tone, "here's something to occupy you and keep your mind off things." "It won't work," droned Marvin, "I have an exceptionally large mind." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jun 13 06:49:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19060 for freebsd-stable-outgoing; Sat, 13 Jun 1998 06:49:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from csmd2.cs.uni-magdeburg.de (prinz-atm.cs.uni-magdeburg.de [141.44.30.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19050 for ; Sat, 13 Jun 1998 06:49:17 -0700 (PDT) (envelope-from jesse@prinz-atm.cs.Uni-Magdeburg.DE) Received: from pflaume.cs.uni-magdeburg.de (pflaume-atm [141.44.30.44]) by csmd2.cs.uni-magdeburg.de (8.8.8/8.8.8) with SMTP id PAA05200; Sat, 13 Jun 1998 15:49:17 +0200 (MET DST) Received: by pflaume.cs.uni-magdeburg.de (SMI-8.6/SMI-SVR4) id PAA03816; Sat, 13 Jun 1998 15:49:16 +0200 Date: Sat, 13 Jun 1998 15:49:16 +0200 From: jesse@prinz-atm.cs.Uni-Magdeburg.DE (Roland Jesse) Message-Id: <199806131349.PAA03816@pflaume.cs.uni-magdeburg.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Hans Petter Bieker Cc: freebsd-stable@FreeBSD.ORG Subject: Re: error when building kdebase-4.1b port In-Reply-To: References: <199806121202.OAA00682@pflaume.cs.uni-magdeburg.de> X-Mailer: VM 6.32 under Emacs 19.34.1 Reply-To: Roland Jesse X-Organization: University of Magdeburg X-Pgp-Fingerprint: 5D 08 5A E3 B4 AA 68 C1 FF 67 06 29 62 DD 9A D7 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hans Petter Bieker writes: > ar you running this as root? you should take a look on ulimit -a. I do get the error regardless to whether I am running it as root or ordinary user. ulimit -a is the same for both: cpu time (seconds) unlimited file size (blocks) unlimited data seg size (kbytes) 16384 stack size (kbytes) 8192 core file size (blocks) unlimited resident set size (kbytes) 30720 locked-in-memory size (kb) 10240 processes 64 file descriptors 64 But this should not be the problem as I get the error message even when I do not run any make processes but try to compile the file 'by hand': # cd /usr/ports/x11/kdebase/work/kdebase/kfm # c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include -I/usr/X11R6/include/X11/qt -I/usr/X11R6/include -I/usr/local/include/giflib -O2 -m486 -pipe -c kfmgui.cpp In file included from root.h:8, from kfmgui.cpp:29: /usr/X11R6/include/X11/Xlib.h:1074: virtual memory exhausted cpp: output pipe has been closed As I wrote before--there is definately enough virtual memory available on the system. Roland, still looking out for hints -- "Hey, Marvin kid," said Zaphod brightly, "how are you doing?" "Very badly I suspect," muttered Marvin. (TRATEOTU) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jun 13 07:05:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA21012 for freebsd-stable-outgoing; Sat, 13 Jun 1998 07:05:43 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from oslo17.or.uninett.no (hanspbie@oslo17.or.uninett.no [158.36.90.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20993 for ; Sat, 13 Jun 1998 07:05:37 -0700 (PDT) (envelope-from zerium@webindex.no) Received: from localhost (hanspbie@localhost) by oslo17.or.uninett.no (8.8.8/8.8.8) with SMTP id QAA00353; Sat, 13 Jun 1998 16:05:41 +0200 (CEST) (envelope-from zerium@webindex.no) X-Authentication-Warning: oslo17.or.uninett.no: hanspbie owned process doing -bs Date: Sat, 13 Jun 1998 16:05:40 +0200 (CEST) From: Hans Petter Bieker X-Sender: hanspbie@oslo17.or.uninett.no To: Roland Jesse cc: freebsd-stable@FreeBSD.ORG Subject: Re: error when building kdebase-4.1b port In-Reply-To: <199806131349.PAA03816@pflaume.cs.uni-magdeburg.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 13 Jun 1998, Roland Jesse wrote: > Hans Petter Bieker writes: > > ar you running this as root? you should take a look on ulimit -a. > I do get the error regardless to whether I am running it as root or > ordinary user. ulimit -a is the same for both: > > cpu time (seconds) unlimited > file size (blocks) unlimited > data seg size (kbytes) 16384 ^^^^^ > stack size (kbytes) 8192 ^^^^ > core file size (blocks) unlimited > resident set size (kbytes) 30720 > locked-in-memory size (kb) 10240 > processes 64 > file descriptors 64 just increase 'em in /etc/login.conf. -bieker- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jun 13 13:00:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29634 for freebsd-stable-outgoing; Sat, 13 Jun 1998 13:00:09 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles301.castles.com [208.214.167.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA29512 for ; Sat, 13 Jun 1998 12:59:56 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA00693; Sat, 13 Jun 1998 11:54:27 -0700 (PDT) Message-Id: <199806131854.LAA00693@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Ugo Paternostro cc: Mike Smith , Luigi Rizzo , freebsd-stable@FreeBSD.ORG, eivind@yes.no (Eivind Eklund) Subject: Re: PnP support for if_ed, and more... In-reply-to: Your message of "Fri, 12 Jun 1998 12:38:50 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 13 Jun 1998 11:54:27 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 06-Jun-98 Mike Smith wrote about "Re: PnP support for if_ed, and more...": > > and then work out a mechanism to scan the 'compatible device ID' > > descriptors (0x1c) and pretend that the device is one of these if the > > first pass (try for an exact match on the device ID) fails. > > The code is working here. I have a few questions: Qool! > - I'm working on -stable, so someone else should take care of -current... [well > this isn't really a question :-)] Sure; shouldn't be too bad. > - I would like to MFC some code (mainly isa.c 1.103 -> 1.104), but I understand > that I should avoid mixing the diffs togheter. What do you suggest? You're correct that the two should be separate. Luigi has commit access now I think, and failing that Eivind has practice in that area... > Should I > reply to my own PR (i386/6792) with just the Compatible Device ID patch and > open a new PR to backport that isa.c change? The problem is that I need to > change both isa.c and pnp.c at the same time to let that MFC work, so at the > end of the game I need to change pnp.c twice. You should submit your code as a PR stating that the diffs won't work until the changes in 1.104 are merged. > Should I fix/remove bogus/useless Vendor IDs from if_ed.c and sio.c? Yes. > - I still would like to remove that structure definition (edpnp_ids) from sio.c > and if_ed.c to put it into pnp.h This is the structure definition, or the initialisation? By all means move the definition. > - talking about sio.c, I don't have anymore the SupraExpress internal modem, so > I don't know what its Compatible Device ID looks like. There are a lot of > possible definitions in devids.txt (see PNP0500 -> PNP0502, plus PNPCxxx -> > PNPDxxx). I would be glad to everyone that sends to me its pnpinfo output... If you don't have it, err on the side of caution. (That's kinda obvious, really 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jun 13 15:40:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA17333 for freebsd-stable-outgoing; Sat, 13 Jun 1998 15:40:42 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA17256; Sat, 13 Jun 1998 15:40:30 -0700 (PDT) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE (8.8.8/8.8.8) with ESMTP id AAA25887; Sun, 14 Jun 1998 00:40:29 +0200 (MET DST) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.8.8/8.6.9) id AAA05119; Sun, 14 Jun 1998 00:38:04 +0200 (CEST) X-Face: " Date: Sun, 14 Jun 1998 00:38:04 +0200 From: Stefan Esser To: Roland Jesse , freebsd-stable@FreeBSD.ORG Cc: Stefan Esser Subject: Re: error when building kdebase-4.1b port References: <199806121202.OAA00682@pflaume.cs.uni-magdeburg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199806121202.OAA00682@pflaume.cs.uni-magdeburg.de>; from Roland Jesse on Fri, Jun 12, 1998 at 02:02:04PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1998-06-12 14:02 +0200, Roland Jesse wrote: > /usr/X11R6/include/X11/Xlib.h:1074: virtual memory exhausted > cpp: output pipe has been closed Either all (virtual) memory has been consumed, or you hit a resource limit (see /etc/login.conf and the output of the "limits" command). > At this point in time there is more than 200 MB of virtual memory free > on my system. The specified line (1074) in Xlib.h is the last line of > the typedef of XEDataObject. Honestly, I do not quite see the point of > exhausting virtual memory at this point. Just compile the single file that requires that much memory as "root" for higher resource limits. Or increase your limits (up to the hard limits) with the "limits" command. Or, as a third option, increase the login class limits of your account in /etc/login.conf ... Gruss, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message