From owner-freebsd-stable Sun Feb 22 01:59:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA10590 for freebsd-stable-outgoing; Sun, 22 Feb 1998 01:59:47 -0800 (PST) (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 BAA10582; Sun, 22 Feb 1998 01:59:40 -0800 (PST) (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.7/8.8.7) with ESMTP id KAA13285; Sun, 22 Feb 1998 10:59:37 +0100 (MET) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.8.8/8.6.9) id JAA00772; Sun, 22 Feb 1998 09:56:26 +0100 (CET) X-Face: " Date: Sun, 22 Feb 1998 09:56:26 +0100 From: Stefan Esser To: Castor Fu , freebsd-stable@FreeBSD.ORG Cc: Stefan Esser Subject: Re: ncr0 hangs with freebsd-stable References: <199802220322.TAA09638@geo.geocast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199802220322.TAA09638@geo.geocast.net>; from Castor Fu on Sat, Feb 21, 1998 at 07:22:26PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On 1998-02-21 19:22 -0800, Castor Fu wrote: > After cvsup'ing to the latest version of FreebSD-2.2.5-STABLE today, > when booting the generic kernel I cannot mount the hard disk attached > to my ASUS SC-200 SCSI controller. The process executing the mount appears > to simply hang. > > Here's what dmesg says about the scsi controller on the working kernel. > > ncr0 rev 2 int a irq 9 on pci0:13 > ncr0 waiting for scsi devices to settle > (ncr0:0:0): "CONNER CFP2107E 2.14GB 1524" type 0 fixed SCSI 2 > sd0(ncr0:0:0): Direct-Access > sd0(ncr0:0:0): 10.0 MB/s (100 ns, offset 8) > 2048MB (4194304 512 byte sectors) > > > I suppose it's possible that it's a cabling problem, but I can switch > between the 2.2.5-stable (from about Jan 1 1998) and today's > version and reliably reproduce the hang. > > Today (Feb 21) I cvsup'd the latest version of FreeBSD-2.2.5-STABLE and > did "make buildworld" and "make installworld". > > Any clues about what might be wrong? Sorry, none from my side. The last commit to the NCR driver in stable has been on December, 12, 1998, and it just made MAX_START (the number of commands active at a time for this controller) to a constant 32. Even with 7 drives and 4 tags each you are not going to hit that limit, and of course not from within the mount when going multi-user ... There have been a few changes in FreeBSD recently, and one of them may hurt you. Perhaps you've got LKMs that are no longer compatible with a recent kernel ? Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Feb 22 13:05:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11193 for freebsd-stable-outgoing; Sun, 22 Feb 1998 13:05:59 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11177 for ; Sun, 22 Feb 1998 13:05:48 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.8/8.8.8) with SMTP id NAA15715; Sun, 22 Feb 1998 13:04:42 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Date: Sun, 22 Feb 1998 13:04:42 -0800 (PST) From: Chris Timmons To: "Jordan K. Hubbard" cc: Warner Losh , John Kelly , Greg Lehey , stable@FreeBSD.ORG Subject: pppd merge from -current to -stable In-Reply-To: <24762.888125282@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I use pppd extensively and ever since about 2.0.5 (or whenever the panic problem was fixed) it has been completely stable for me. I will ascertain what would be gained from a merge (first), and whether my rather limited hacking skills are up to it (second.) -Chris On Sat, 21 Feb 1998, Jordan K. Hubbard wrote: > > Ooops. I just read this more closely. The PPP in -stable is very > > close to -current, but the PPPD may well be very old. > > Anyone care to merge it? I don't even use pppd nor have I a ready-made > setup for testing it (e.g. an existing link which uses pppd) or I'd be > more inclined to do it myself. > > Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Feb 22 13:12:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12639 for freebsd-stable-outgoing; Sun, 22 Feb 1998 13:12:16 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns2.cetlink.net (root@ns2.cetlink.net [209.54.54.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12585 for ; Sun, 22 Feb 1998 13:12:09 -0800 (PST) (envelope-from jak@cetlink.net) Received: from exit1.i485.net (ts2-cltnc-95.cetlink.net [209.54.58.95]) by ns2.cetlink.net (8.8.5/8.8.5) with SMTP id QAA04325; Sun, 22 Feb 1998 16:10:49 -0500 (EST) From: jak@cetlink.net (John Kelly) To: Chris Timmons Cc: "Jordan K. Hubbard" , Warner Losh , Greg Lehey , stable@FreeBSD.ORG Subject: Re: pppd merge from -current to -stable Date: Sun, 22 Feb 1998 22:11:16 GMT Message-ID: <34f3a1c4.34222174@mail.cetlink.net> References: In-Reply-To: X-Mailer: Forte Agent 1.01/16.397 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id NAA12594 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Sun, 22 Feb 1998 13:04:42 -0800 (PST), Chris Timmons wrote: >I use pppd extensively and ever since about 2.0.5 (or whenever the panic >problem was fixed) it has been completely stable for me. > >I will ascertain what would be gained from a merge (first), and whether my >rather limited hacking skills are up to it (second.) There are some new features worthwhile to have. If you give it a go, how about getting the latest version from the maintainer's FTP site to put into -current first? We're already several releases behind, even in -current. I will help in this effort if there's anything I can do. -- The day of the proprietary OS is over. Long live free software. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Feb 22 18:05:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24656 for freebsd-stable-outgoing; Sun, 22 Feb 1998 18:05:03 -0800 (PST) (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 SAA24620; Sun, 22 Feb 1998 18:04:57 -0800 (PST) (envelope-from cy@cschuber.net.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.8.8/8.6.10) id SAA21413; Sun, 22 Feb 1998 18:04:47 -0800 (PST) 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 smtpdaacoia; Sun Feb 22 18:04:41 1998 Received: (from uucp@localhost) by cwsys.cwsent.com (8.8.8/8.6.10) id LAA13152; Sun, 22 Feb 1998 11:54:49 -0800 (PST) Message-Id: <199802221954.LAA13152@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpd013117; Sun Feb 22 19:54:09 1998 X-Mailer: exmh version 2.0.1 12/23/97 Reply-to: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: cy To: "Daniel O'Callaghan" cc: freebsd-hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: /etc/crontab In-reply-to: Your message of "Sun, 22 Feb 1998 09:50:11 +1100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Feb 1998 11:54:07 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > It was written that /etc/daily is run twice or not at all during DST changes. > I said it was a bug in cron(8); Archie Cobbs said it wasn't. > > HP-UX seems to have it sorted out.... Solaris and DUNIX did sort it out as well. > > Can anyone suggest an algorithm for implementing the HP-UX cron(8) behavior? > > Danny > > ---------- Forwarded message ---------- > Date: Tue, 8 Apr 1997 14:09:07 +1000 (EST) > From: Darren Reed > To: Warner Losh > Cc: thompson@squirrel.tgsoft.com, hackers@freebsd.com > Subject: Re: crontab nit? > > HP-UX man page for cron: > Notes > On the days of daylight savings (summer) time transition (in time > zones and countries where daylight savings time applies), cron > schedules commands differently than normal. > > In the following description, an ambiguous time refers to an hour and > minute that occurs twice in the same day because of a daylight savings > time transition (usually on a day during the Autumn season). A non- > existent time refers to an hour and minute that does not occur because > of a daylight savings time transition (usually on a day during the > Spring season). DST-shift refers to the offset that is applied to > standard time to result in daylight savings time. This is normally > one hour, but can be any combination of hours and minutes up to 23 > hours and 59 minutes (see tztab(4)). > > When a command is specified to run at an ambiguous time, the command > is executed only once at the first occurrence of the ambiguous time. > > When a command is specified to run a non-existent time, the command is > executed after the specified time by an amount of time equal to the > DST-shift. When such an adjustment would conflict with another time > specified to run the command, the command is run only once rather than > running the command twice at the same time. > > For commands that are scheduled to run during all hours by specifying > a * in the hour field of the crontab entry, the command is scheduled > without any adjustment. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 UNIX Support OV/VM: BCSC02(CSCHUBER) ITSD BITNET: CSCHUBER@BCSC02.BITNET Government of BC Internet: cschuber@uumail.gov.bc.ca Cy.Schubert@gems8.gov.bc.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Feb 22 18:05:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24711 for freebsd-stable-outgoing; Sun, 22 Feb 1998 18:05:09 -0800 (PST) (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 SAA24626; Sun, 22 Feb 1998 18:04:59 -0800 (PST) (envelope-from cy@cschuber.net.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.8.8/8.6.10) id SAA17280; Sun, 22 Feb 1998 18:04:57 -0800 (PST) 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 smtpdaavfla; Sun Feb 22 17:57:23 1998 Received: (from uucp@localhost) by cwsys.cwsent.com (8.8.8/8.6.10) id LAA13152; Sun, 22 Feb 1998 11:54:49 -0800 (PST) Message-Id: <199802221954.LAA13152@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpd013117; Sun Feb 22 19:54:09 1998 X-Mailer: exmh version 2.0.1 12/23/97 Reply-to: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: cy To: "Daniel O'Callaghan" cc: freebsd-hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: /etc/crontab In-reply-to: Your message of "Sun, 22 Feb 1998 09:50:11 +1100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Feb 1998 11:54:07 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > It was written that /etc/daily is run twice or not at all during DST changes. > I said it was a bug in cron(8); Archie Cobbs said it wasn't. > > HP-UX seems to have it sorted out.... Solaris and DUNIX did sort it out as well. > > Can anyone suggest an algorithm for implementing the HP-UX cron(8) behavior? > > Danny > > ---------- Forwarded message ---------- > Date: Tue, 8 Apr 1997 14:09:07 +1000 (EST) > From: Darren Reed > To: Warner Losh > Cc: thompson@squirrel.tgsoft.com, hackers@freebsd.com > Subject: Re: crontab nit? > > HP-UX man page for cron: > Notes > On the days of daylight savings (summer) time transition (in time > zones and countries where daylight savings time applies), cron > schedules commands differently than normal. > > In the following description, an ambiguous time refers to an hour and > minute that occurs twice in the same day because of a daylight savings > time transition (usually on a day during the Autumn season). A non- > existent time refers to an hour and minute that does not occur because > of a daylight savings time transition (usually on a day during the > Spring season). DST-shift refers to the offset that is applied to > standard time to result in daylight savings time. This is normally > one hour, but can be any combination of hours and minutes up to 23 > hours and 59 minutes (see tztab(4)). > > When a command is specified to run at an ambiguous time, the command > is executed only once at the first occurrence of the ambiguous time. > > When a command is specified to run a non-existent time, the command is > executed after the specified time by an amount of time equal to the > DST-shift. When such an adjustment would conflict with another time > specified to run the command, the command is run only once rather than > running the command twice at the same time. > > For commands that are scheduled to run during all hours by specifying > a * in the hour field of the crontab entry, the command is scheduled > without any adjustment. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 UNIX Support OV/VM: BCSC02(CSCHUBER) ITSD BITNET: CSCHUBER@BCSC02.BITNET Government of BC Internet: cschuber@uumail.gov.bc.ca Cy.Schubert@gems8.gov.bc.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Feb 23 11:17:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18539 for freebsd-stable-outgoing; Mon, 23 Feb 1998 11:17:50 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from noao.edu (noao.edu [140.252.1.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18493; Mon, 23 Feb 1998 11:17:27 -0800 (PST) (envelope-from grandi@noao.edu) Received: from mirfak.tuc.noao.edu (grandi@mirfak.tuc.noao.edu [140.252.1.9]) by noao.edu (8.8.8/8.8.7/SAG-02Dec97) with SMTP id MAA18362; Mon, 23 Feb 1998 12:17:25 -0700 (MST) (envelope-from grandi@noao.edu) Date: Mon, 23 Feb 1998 12:17:24 -0700 (MST) From: Steve Grandi X-Sender: grandi@mirfak.tuc.noao.edu To: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: I need a strategy for making my STABLE installation stable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk A progress report.... First, I have sent this to both questions and stable (where I started this thread a week ago). If this is bad form, please rap my knuckles gently. >From last week: > My STABLE system hasn't been very stable: I've been averaging one system > crash a day for the past week or so. The frequency of crashes is > increasing with perhaps one crash a week averaged the past 3 months. I > need some help in devising a strategy to make things stable... > > The hardware: PentiumPro-200 (Venus Motherboard), 128 MB of RAM, Adaptec > 2940 Ultra-Wide SCSI controller, two Seagate ST32155W 2GB disks, a > Micropolis 3391WS 9GB disk, Plextor SCSI CD-ROM, Intel EtherExpress Pro > 10/100B Ethernet card. > > The System: FreeBSD 2.2.5-STABLE kept up-to-date via CVSUP > > What's the system doing: DNS server, Sendmail server, FTP server, Net News > server. > > Ever since I upgraded to 2.2.5-RELEASE in late November, I've seen far too > many system crashes. About half the time, the crash would be followed by > a reboot. The other half of the time the system would just hang with no > response from the console keyboard or active rlogin sessions (but > sometimes the system would still answer PINGs). Crashes seemed to follow > heavy disk I/O and/or paging (usually soon after an INN expire with a > 200MB+ history file). > So what strategy should I follow to make the system stable and make the Users > happy again? I received several very good pieces of advice and tried them out: unfortunately the crashes continued. I have replaced the motherboard and P6-200, memory (putting in parity memory with ECC enabled in the motherboard BIOS), the SCSI disk controller, the Ethernet card and the video card. All that remains from the original system is the power-supply, the keyboard and the three disks. I have also turned off Ultra SCSI speed in the Adaptec card's BIOS. Two of the crashes in the past week have generated dumps; the rest were hard hangs. Stack traces of these follow. I have since realized that I need to generate a "debug" kernel so that variable names show up in the dumps; next time! # strings kernel.0 | grep STABLE 2.2.5-STABLE @(#)FreeBSD 2.2.5-STABLE #0: Tue Feb 17 08:44:04 MST 1998 # gdb -k kernel.0 vmcore.0 Copyright 1996 Free Software Foundation, Inc...(no debugging symbols found)... IdlePTD 20c000 current pcb at 1ef358 panic: page fault #0 0xf01126f3 in boot () (kgdb) where #0 0xf01126f3 in boot () #1 0xf01129b2 in panic () #2 0xf01b7526 in trap_fatal () #3 0xf01b7014 in trap_pfault () #4 0xf01b6cef in trap () #5 0xf01b36f1 in pmap_qenter () #6 0xf012d15e in allocbuf () #7 0xf012caf8 in getblk () #8 0xf0196f15 in ffs_sbupdate () #9 0xf01969df in ffs_sync () #10 0xf01324e7 in sync () #11 0xf012d70f in vfs_update () #12 0xf010921a in kproc_start () #13 0xf01091b8 in main () # strings kernel.1 | grep STABLE 2.2.5-STABLE @(#)FreeBSD 2.2.5-STABLE #0: Tue Feb 17 08:44:04 MST 1998 # gdb -k kernel.1 vmcore.1 Copyright 1996 Free Software Foundation, Inc...(no debugging symbols found)... IdlePTD 20c000 current pcb at 1ef358 panic: vm_fork: u_map allocation failed #0 0xf01126f3 in boot () (kgdb) where #0 0xf01126f3 in boot () #1 0xf01129b2 in panic () #2 0xf01b387d in pmap_new_proc () #3 0xf01a2017 in vm_fork () #4 0xf010d76a in fork1 () #5 0xf010d2b0 in fork () #6 0xf01b7763 in syscall () #7 0x100482d5 in ?? () #8 0x1095 in ?? () This last panic was a "killer:" the 9GB /var/spool/news partition was toasted beyond recovery (defined as a case where fsck -y runs for half an hour and looks like it will run forever...). This happened before and the interesting thing is that the system stopped crashing while /var/spool/news filled up again! Indeed, the system hasn't crashed in the three days since this last "killer" crash while the mean-time-to-crash in the prior week was less than a day. Based on all of this, I have made two suppositions: 1) I have a software problem and not a hardware problem. 2) Something about a "fully loaded" inn netnews system (7 GB of articles, a history file exceeding 120 MB, etc.) tickles a bug in FreeBSD that causes the observed hangs and panics. Hence, I expect that my system will run fine for another few days until netnews fills up a good fraction of /var/spool/news. My plan is to do the following: 1) Wait for the next crash and capture a crash dump against the debug kernel. 2) After capturing said crash dump; install on the machine an old kernel "borrowed" from another machine: FreeBSD 2.2-970422-RELENG. Since my memory tells me that when this pre-2.2.2 system was running on the machine in question, the system stayed up for months despite a fully loaded inn. Can anyone think of other things to try or a useful strategy to follow? Steve Grandi, National Optical Astronomy Observatories, Tucson, Arizona USA Internet: grandi@noao.edu Voice: +1 520 318-8228 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Feb 23 11:28:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20746 for freebsd-stable-outgoing; Mon, 23 Feb 1998 11:28:02 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20696; Mon, 23 Feb 1998 11:27:55 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id OAA01501; Mon, 23 Feb 1998 14:27:50 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199802231927.OAA01501@dyson.iquest.net> Subject: Re: I need a strategy for making my STABLE installation stable In-Reply-To: from Steve Grandi at "Feb 23, 98 12:17:24 pm" To: grandi@noao.edu (Steve Grandi) Date: Mon, 23 Feb 1998 14:27:50 -0500 (EST) Cc: freebsd-stable@FreeBSD.ORG, freebsd-questions@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 Steve Grandi said: > A progress report.... > > First, I have sent this to both questions and stable (where I started this > thread a week ago). If this is bad form, please rap my knuckles gently. > I suggest disabling swapping (paging will still work.) The errors that you are getting are wierd (those are the worst kind :-(). If swapping is enabled, and there are subtile problems with the system, the UPAGES being messed up can cause the kernel stack to be corrupt. options "NO_SWAPPING" This is a "stab in the dark", but I will try to watch your progress and bug reports. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Feb 23 12:24:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05919 for freebsd-stable-outgoing; Mon, 23 Feb 1998 12:24:56 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from bsd3.nyct.net (bsd3.nyct.net [204.141.86.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05784; Mon, 23 Feb 1998 12:24:14 -0800 (PST) (envelope-from myj@bsd3.nyct.net) Received: (from myj@localhost) by bsd3.nyct.net (8.8.8/8.8.5) id PAA26109; Mon, 23 Feb 1998 15:24:01 -0500 (EST) Date: Mon, 23 Feb 1998 15:24:01 -0500 (EST) From: Paul Sandys To: Steve Grandi cc: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: I need a strategy for making my STABLE installation stable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Mon, 23 Feb 1998, Steve Grandi wrote: > Date: Mon, 23 Feb 1998 12:17:24 -0700 (MST) > From: Steve Grandi > To: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG > Subject: Re: I need a strategy for making my STABLE installation stable > > A progress report.... > > First, I have sent this to both questions and stable (where I started this > thread a week ago). If this is bad form, please rap my knuckles gently. > > >From last week: > > > My STABLE system hasn't been very stable: I've been averaging one system > > crash a day for the past week or so. The frequency of crashes is > > increasing with perhaps one crash a week averaged the past 3 months. I > > need some help in devising a strategy to make things stable... > > > > The hardware: PentiumPro-200 (Venus Motherboard), 128 MB of RAM, Adaptec > > 2940 Ultra-Wide SCSI controller, two Seagate ST32155W 2GB disks, a > > Micropolis 3391WS 9GB disk, Plextor SCSI CD-ROM, Intel EtherExpress Pro > > 10/100B Ethernet card. > > > > The System: FreeBSD 2.2.5-STABLE kept up-to-date via CVSUP > > > > What's the system doing: DNS server, Sendmail server, FTP server, Net News > > server. > > > > Ever since I upgraded to 2.2.5-RELEASE in late November, I've seen far too > > many system crashes. About half the time, the crash would be followed by > > a reboot. The other half of the time the system would just hang with no > > response from the console keyboard or active rlogin sessions (but > > sometimes the system would still answer PINGs). Crashes seemed to follow > > heavy disk I/O and/or paging (usually soon after an INN expire with a > > 200MB+ history file). > > > So what strategy should I follow to make the system stable and make the Users > > happy again? > > I received several very good pieces of advice and tried them out: > unfortunately the crashes continued. I have replaced the motherboard and > P6-200, memory (putting in parity memory with ECC enabled in the motherboard > BIOS), the SCSI disk controller, the Ethernet card and the video card. All > that remains from the original system is the power-supply, the keyboard and > the three disks. I have also turned off Ultra SCSI speed in the Adaptec card's > BIOS. I suggest you try different power supply. I also spent 3 months replacing parts in one FreeBSD server with random crashes, and it ended up being the SCSI cable, which worked for 2 years straight before ..... > > Two of the crashes in the past week have generated dumps; the rest were hard > hangs. Stack traces of these follow. I have since realized that I need to > generate a "debug" kernel so that variable names show up in the dumps; next > time! > > # strings kernel.0 | grep STABLE > 2.2.5-STABLE > @(#)FreeBSD 2.2.5-STABLE #0: Tue Feb 17 08:44:04 MST 1998 > > # gdb -k kernel.0 vmcore.0 > Copyright 1996 Free Software Foundation, Inc...(no debugging symbols found)... > IdlePTD 20c000 > current pcb at 1ef358 > panic: page fault > #0 0xf01126f3 in boot () > (kgdb) where > #0 0xf01126f3 in boot () > #1 0xf01129b2 in panic () > #2 0xf01b7526 in trap_fatal () > #3 0xf01b7014 in trap_pfault () > #4 0xf01b6cef in trap () > #5 0xf01b36f1 in pmap_qenter () > #6 0xf012d15e in allocbuf () > #7 0xf012caf8 in getblk () > #8 0xf0196f15 in ffs_sbupdate () > #9 0xf01969df in ffs_sync () > #10 0xf01324e7 in sync () > #11 0xf012d70f in vfs_update () > #12 0xf010921a in kproc_start () > #13 0xf01091b8 in main () > > > # strings kernel.1 | grep STABLE > 2.2.5-STABLE > @(#)FreeBSD 2.2.5-STABLE #0: Tue Feb 17 08:44:04 MST 1998 > > # gdb -k kernel.1 vmcore.1 > Copyright 1996 Free Software Foundation, Inc...(no debugging symbols found)... > IdlePTD 20c000 > current pcb at 1ef358 > panic: vm_fork: u_map allocation failed > #0 0xf01126f3 in boot () > (kgdb) where > #0 0xf01126f3 in boot () > #1 0xf01129b2 in panic () > #2 0xf01b387d in pmap_new_proc () > #3 0xf01a2017 in vm_fork () > #4 0xf010d76a in fork1 () > #5 0xf010d2b0 in fork () > #6 0xf01b7763 in syscall () > #7 0x100482d5 in ?? () > #8 0x1095 in ?? () > > This last panic was a "killer:" the 9GB /var/spool/news partition was > toasted beyond recovery (defined as a case where fsck -y runs for half > an hour and looks like it will run forever...). This happened before > and the interesting thing is that the system stopped crashing while > /var/spool/news filled up again! Indeed, the system hasn't crashed in the > three days since this last "killer" crash while the mean-time-to-crash > in the prior week was less than a day. > > Based on all of this, I have made two suppositions: > > 1) I have a software problem and not a hardware problem. > > 2) Something about a "fully loaded" inn netnews system (7 GB of articles, a > history file exceeding 120 MB, etc.) tickles a bug in FreeBSD that causes the > observed hangs and panics. > > Hence, I expect that my system will run fine for another few days until > netnews fills up a good fraction of /var/spool/news. > > My plan is to do the following: > > 1) Wait for the next crash and capture a crash dump against the debug kernel. > > 2) After capturing said crash dump; install on the machine an old kernel > "borrowed" from another machine: FreeBSD 2.2-970422-RELENG. Since my > memory tells me that when this pre-2.2.2 system was running on the machine > in question, the system stayed up for months despite a fully loaded inn. > > Can anyone think of other things to try or a useful strategy to follow? > > Steve Grandi, National Optical Astronomy Observatories, Tucson, Arizona USA > Internet: grandi@noao.edu Voice: +1 520 318-8228 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > P. <-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-> < myj@nyct.net Paul Sandys | New York Connect http://www.nyct.net > < network operations manager | Total Solution provider > <-------------------------------------------------------------------------> < " BRINGING NEW YORK THE INTERNET SERVICES IT DESERVES " > <-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Feb 23 13:48:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19766 for freebsd-stable-outgoing; Mon, 23 Feb 1998 13:48:30 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from noao.edu (noao.edu [140.252.1.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19729; Mon, 23 Feb 1998 13:48:14 -0800 (PST) (envelope-from grandi@noao.edu) Received: from mirfak.tuc.noao.edu (grandi@mirfak.tuc.noao.edu [140.252.1.9]) by noao.edu (8.8.8/8.8.7/SAG-02Dec97) with SMTP id OAA08925; Mon, 23 Feb 1998 14:47:30 -0700 (MST) (envelope-from grandi@noao.edu) Date: Mon, 23 Feb 1998 14:47:29 -0700 (MST) From: Steve Grandi X-Sender: grandi@mirfak.tuc.noao.edu To: "John S. Dyson" cc: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: I need a strategy for making my STABLE installation stable In-Reply-To: <199802231927.OAA01501@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I will get this option a try and report back... Steve Grandi, National Optical Astronomy Observatories, Tucson, Arizona USA Internet: grandi@noao.edu Voice: +1 520 318-8228 On Mon, 23 Feb 1998, John S. Dyson wrote: > Steve Grandi said: > > A progress report.... > > > > First, I have sent this to both questions and stable (where I started this > > thread a week ago). If this is bad form, please rap my knuckles gently. > > > I suggest disabling swapping (paging will still work.) The errors that > you are getting are wierd (those are the worst kind :-(). If swapping > is enabled, and there are subtile problems with the system, the UPAGES > being messed up can cause the kernel stack to be corrupt. > > options "NO_SWAPPING" > > This is a "stab in the dark", but I will try to watch your progress and > bug reports. > > -- > John | Never try to teach a pig to sing, > dyson@freebsd.org | it just makes you look stupid, > jdyson@nc.com | and it irritates the pig. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Feb 23 13:57:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21187 for freebsd-stable-outgoing; Mon, 23 Feb 1998 13:57:32 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from noao.edu (noao.edu [140.252.1.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21151; Mon, 23 Feb 1998 13:57:19 -0800 (PST) (envelope-from grandi@noao.edu) Received: from mirfak.tuc.noao.edu (grandi@mirfak.tuc.noao.edu [140.252.1.9]) by noao.edu (8.8.8/8.8.7/SAG-02Dec97) with SMTP id OAA09627; Mon, 23 Feb 1998 14:51:33 -0700 (MST) (envelope-from grandi@noao.edu) Date: Mon, 23 Feb 1998 14:51:33 -0700 (MST) From: Steve Grandi X-Sender: grandi@mirfak.tuc.noao.edu To: Paul Sandys cc: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: I need a strategy for making my STABLE installation stable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk An excellent suggestion: I have just ordered a replacement internal SCSI cable as well! Steve Grandi, National Optical Astronomy Observatories, Tucson, Arizona USA Internet: grandi@noao.edu Voice: +1 520 318-8228 On Mon, 23 Feb 1998, Paul Sandys wrote: > > I suggest you try different power supply. I also spent 3 months > replacing parts in one FreeBSD server with random crashes, and it ended up > being the SCSI cable, which worked for 2 years straight before ..... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Feb 23 14:52:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02688 for freebsd-stable-outgoing; Mon, 23 Feb 1998 14:52:06 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02375 for ; Mon, 23 Feb 1998 14:51:37 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.8/8.8.8) with SMTP id OAA28092; Mon, 23 Feb 1998 14:48:29 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Date: Mon, 23 Feb 1998 14:48:29 -0800 (PST) From: Chris Timmons To: John Kelly cc: "Jordan K. Hubbard" , Warner Losh , Greg Lehey , stable@FreeBSD.ORG Subject: Re: pppd merge from -current to -stable In-Reply-To: <34f3a1c4.34222174@mail.cetlink.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I'll look into this some evening this week. Since it is a kernel interface, I am queasy about doing anything to -stable before the release. Current on the other hand... :) -c On Sun, 22 Feb 1998, John Kelly wrote: > On Sun, 22 Feb 1998 13:04:42 -0800 (PST), Chris Timmons > wrote: > > >I use pppd extensively and ever since about 2.0.5 (or whenever the panic > >problem was fixed) it has been completely stable for me. > > > >I will ascertain what would be gained from a merge (first), and whether my > >rather limited hacking skills are up to it (second.) > > There are some new features worthwhile to have. If you give it a go, > how about getting the latest version from the maintainer's FTP site to > put into -current first? We're already several releases behind, even > in -current. > > I will help in this effort if there's anything I can do. > > -- > The day of the proprietary OS is over. Long live free software. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Feb 23 18:34:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18601 for freebsd-stable-outgoing; Mon, 23 Feb 1998 18:34:58 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18592 for ; Mon, 23 Feb 1998 18:34:54 -0800 (PST) (envelope-from mark@vnode.vmunix.com) Received: (from mark@localhost) by vnode.vmunix.com (8.8.8/8.8.8) id VAA02395; Mon, 23 Feb 1998 21:43:15 -0500 (EST) (envelope-from mark) Message-ID: <19980223214315.08888@vmunix.com> Date: Mon, 23 Feb 1998 21:43:15 -0500 From: Mark Mayo To: Steve Grandi , Paul Sandys Cc: freebsd-stable@FreeBSD.ORG Subject: Re: I need a strategy for making my STABLE installation stable References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Steve Grandi on Mon, Feb 23, 1998 at 02:51:33PM -0700 X-Operating-System: FreeBSD 2.2.5-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Mon, Feb 23, 1998 at 02:51:33PM -0700, Steve Grandi wrote: > An excellent suggestion: I have just ordered a replacement internal SCSI > cable as well! I agree - SCSI cables can be finicky(sp?), and I have had the personal experience in the past of a crappy power supply causing all sorts of crap. Or more specifically, an overloaded power-suply.. Since you've replaced just about everything else in your system, that's all I can think of :) Another interesting thing about the Adaptec 2940UW - I have a PPro200 that I was using with some strange motherboard that a systems contract produced -- it would not work reliably at all with "ultra" turned on. Worked fine with ultra turned off. I swapped motherboards for a nice Asus P65UP5 and it has worked perfectly with the exact same hardware and Ultra turned ON... So there are lots of factors at work when trying to squeeze the most out of PC hardware. :-( Just my $.02, -Mark > > Steve Grandi, National Optical Astronomy Observatories, Tucson, Arizona USA > Internet: grandi@noao.edu Voice: +1 520 318-8228 > > > On Mon, 23 Feb 1998, Paul Sandys wrote: > > > > > I suggest you try different power supply. I also spent 3 months > > replacing parts in one FreeBSD server with random crashes, and it ended up > > being the SCSI cable, which worked for 2 years straight before ..... > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ "The problem is how do you build tools that understand your programs at a deeper semantic level." - James Gosling To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Feb 23 19:28:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26357 for freebsd-stable-outgoing; Mon, 23 Feb 1998 19:28:03 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail-gw.pacbell.net (mail-gw.pacbell.net [206.13.28.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26242 for ; Mon, 23 Feb 1998 19:27:51 -0800 (PST) (envelope-from oski@pacbell.net) Received: from pacbell.net (ppp-207-215-86-72.scrm01.pacbell.net [207.215.86.72]) by mail-gw.pacbell.net (8.8.8/8.7.1+antispam) with ESMTP id TAA17496; Mon, 23 Feb 1998 19:27:12 -0800 (PST) Message-ID: <34F23D89.6440660A@pacbell.net> Date: Mon, 23 Feb 1998 19:24:57 -0800 From: Michael Oski X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: Mark Mayo CC: Steve Grandi , Paul Sandys , freebsd-stable@FreeBSD.ORG Subject: Re: I need a strategy for making my STABLE installation stable References: <19980223214315.08888@vmunix.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk OK, I'll throw a couple of penny's too - quick; duck! I've been running stable on a piece of crap motherboard (one of the $59.95 jobs) with a 2940UW in "ultra" mode for months. It doesn't do too much heavy duty work, mostly IP gateway and DNS stuff. I have never had a problem with this controller or the Seagate drives connected to it (of course, I probably will immediately following the send of this message ;-)) I'm interested in seeing the results of your next dump... Good luck! Mark Mayo wrote: > On Mon, Feb 23, 1998 at 02:51:33PM -0700, Steve Grandi wrote: > > An excellent suggestion: I have just ordered a replacement internal SCSI > > cable as well! > > I agree - SCSI cables can be finicky(sp?), and I have had the > personal experience in the past of a crappy power supply causing all > sorts of crap. Or more specifically, an overloaded power-suply.. > Since you've replaced just about everything else in your system, > that's all I can think of :) > > Another interesting thing about the Adaptec 2940UW - I have a PPro200 > that I was using with some strange motherboard that a systems contract > produced -- it would not work reliably at all with "ultra" turned on. > Worked fine with ultra turned off. I swapped motherboards for a nice > Asus P65UP5 and it has worked perfectly with the exact same hardware > and Ultra turned ON... So there are lots of factors at work when > trying to squeeze the most out of PC hardware. :-( > > Just my $.02, > -Mark > > > > > Steve Grandi, National Optical Astronomy Observatories, Tucson, Arizona USA > > Internet: grandi@noao.edu Voice: +1 520 318-8228 > > > > > > On Mon, 23 Feb 1998, Paul Sandys wrote: > > > > > > > > I suggest you try different power supply. I also spent 3 months > > > replacing parts in one FreeBSD server with random crashes, and it ended up > > > being the SCSI cable, which worked for 2 years straight before ..... > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > -- > ------------------------------------------------------------------------ > Mark Mayo mark@vmunix.com > RingZero Comp. http://www.vmunix.com/mark > > finger mark@vmunix.com for my PGP key and GCS code > ------------------------------------------------------------------------ > "The problem is how do you build tools that understand your programs > at a deeper semantic level." - James Gosling > > 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 Feb 23 21:44:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09287 for freebsd-stable-outgoing; Mon, 23 Feb 1998 21:44:25 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from firewall.scitec.com.au (firewall-user@fgate.scitec.com.au [203.17.180.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA09278 for ; Mon, 23 Feb 1998 21:44:07 -0800 (PST) (envelope-from john.saunders@scitec.com.au) Received: by firewall.scitec.com.au; id QAA09665; Tue, 24 Feb 1998 16:43:59 +1100 (EST) Received: from mailhub.scitec.com.au(203.17.180.131) by fgate.scitec.com.au via smap (3.2) id xma009641; Tue, 24 Feb 98 16:43:41 +1100 Received: from hydra.scitec.com.au (hydra.scitec.com.au [203.17.182.101]) by mailhub.scitec.com.au (8.6.12/8.6.9) with ESMTP id QAA23711 for ; Tue, 24 Feb 1998 16:43:35 +1100 Received: from scitec.com.au (saruman.scitec.com.au) by hydra.scitec.com.au with ESMTP (1.40.112.8/16.2) id AA276959013; Tue, 24 Feb 1998 16:43:34 +1100 Message-Id: <34F25BC6.13E2F7A8@scitec.com.au> Date: Tue, 24 Feb 1998 16:33:58 +1100 From: John Saunders Organization: SCITEC LIMITED X-Mailer: Mozilla 4.04 [en] (WinNT; I) Mime-Version: 1.0 Newsgroups: comp.unix.bsd.freebsd.misc To: freebsd-stable@FreeBSD.ORG Subject: stable branch funnies Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I've been wanting to track -stable and I think I've managed to get on top of how to keep up using cvsup. But then I got a surprise yesterday. I installed the source from my 2.2.5 CD and did a make world on it which went OK. Machine still boots and works OK. Then I read up on cvsup and I'm using it with a RELENG_2_2 tag to suck updates from cvsup.au.freebsd.org (If anybody else does this remember to unblock ports 5999 and 5998, if you firewall, as it helps a lot :-) I got the cvsup-stable file from the web handbook. I did my first cvsup a few days ago and I got a nice log file of deltas being applied and files checked out (for example the game boggle seemed to be a totally new game). I didn't do a build after this due to time constraints. Then yesterday I had time to do a build but decided to run cvsup and get the latest and greatest before doing the build. What was strange is that I noticed the boggle game being deleted but didn't think anything more than "gee I would have liked to play it once". I then tried a build which failed due to a problem in libg++. I now have a number of possibilities for this failure and I'm not sure how to proceed. 1) -stable is very volatile and whole programs coming and going, and failed builds, is a part of life. (I can't really believe this). 2) Somehow cvsup managed to reverse the sup it did a few days ago and removed things it shouldn't have (evidence boggle going). Or maybe it just went plain bonkers :-) 3) Who knows? Reading up on the cvsup man page it says that it maintains a file(s) so it knows what versions it has of each file. I have yet to locate these files and after 2 runs of cvsup I would have expected these files to be created. Is these missing files somehow confusing cvsup about what versions it has and what it needs? If anybody has some clues or tips I would be glad of some help. Thanks. -- +------------------------------------------------------------+ . | John Saunders mailto:John.Saunders@scitec.com.au (Work) | ,--_|\ | mailto:john@nlc.net.au (Home) | / Oz \ | http://www.nlc.net.au/~john/ | \_,--\_/ | SCITEC LIMITED Phone +61 2 9428 9563 Fax +61 2 9428 9933 | v | "By the time you make ends meet, they move the ends." | +------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Feb 23 22:00:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA12080 for freebsd-stable-outgoing; Mon, 23 Feb 1998 22:00:40 -0800 (PST) (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 WAA12070 for ; Mon, 23 Feb 1998 22:00:25 -0800 (PST) (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.6.9) with ESMTP id VAA04983; Mon, 23 Feb 1998 21:59:49 -0800 (PST) To: Mark Mayo cc: Steve Grandi , Paul Sandys , freebsd-stable@FreeBSD.ORG Subject: Re: I need a strategy for making my STABLE installation stable In-reply-to: Your message of "Mon, 23 Feb 1998 21:43:15 EST." <19980223214315.08888@vmunix.com> Date: Mon, 23 Feb 1998 21:59:49 -0800 Message-ID: <4979.888299989@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > and Ultra turned ON... So there are lots of factors at work when > trying to squeeze the most out of PC hardware. :-( Yes, did I also mention that 90% of PC hardware is crap and will jump up and bite you on various sensitive body parts if you give it any chance at all to do so? And did I mention that 90% is a very very charitable estimate? :-) I'm not saying that FreeBSD hasn't been found to contain bugs, simply that if I had a buck for every time I'd gone chasing someone's "FreeBSD problem" only to find it was some hardware Heisenbug all along, well, I'd be quite wealthy now. :-) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Feb 23 23:12:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19245 for freebsd-stable-outgoing; Mon, 23 Feb 1998 23:12:47 -0800 (PST) (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 XAA19238 for ; Mon, 23 Feb 1998 23:12:40 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.73 #1) id 0y7EXW-0006vG-00; Mon, 23 Feb 1998 23:12:30 -0800 Date: Mon, 23 Feb 1998 23:12:26 -0800 (PST) From: Tom To: John Saunders cc: freebsd-stable@FreeBSD.ORG Subject: Re: stable branch funnies In-Reply-To: <34F25BC6.13E2F7A8@scitec.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Tue, 24 Feb 1998, John Saunders wrote: > 1) -stable is very volatile and whole programs coming and going, and > failed builds, is a part of life. (I can't really believe this). When you installed the original source, you probably did not install the source for games. But your cvsupfile has an entry for games, so cvsup would have downloaded the source for the games. However, boggle was recently removed because it violates a trademark. ... > Reading up on the cvsup man page it says that it maintains a file(s) > so it knows what versions it has of each file. I have yet to locate ... In /usr/sup directory normally. Also, your build problems with g++ are probably completely unreleated. Most likely you have done some funny things to your tree. Try a "make clean", before doing a "make buildworld". Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Feb 24 01:25:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA04311 for freebsd-stable-outgoing; Tue, 24 Feb 1998 01:25:09 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from fw.tue.le (p402321.S.dip.t-online.de [193.159.35.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA04299 for ; Tue, 24 Feb 1998 01:25:03 -0800 (PST) (envelope-from thz@Lennartz-Electronic.DE) Received: from mezcal.tue.le (mezcal.tue.le [192.168.201.20]) by fw.tue.le (8.8.8/8.8.8) with ESMTP id KAA07954; Tue, 24 Feb 1998 10:24:38 +0100 (CET) (envelope-from thz@mezcal.tue.le) Received: (from thz@localhost) by mezcal.tue.le (8.8.5/8.8.8) id KAA22366; Tue, 24 Feb 1998 10:24:38 +0100 (MET) (envelope-from thz) Message-ID: <19980224102438.62250@tue.le> Date: Tue, 24 Feb 1998 10:24:38 +0100 From: Thomas Zenker To: Steve Grandi Cc: freebsd-stable@FreeBSD.ORG Subject: Re: I need a strategy for making my STABLE installation stable References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Steve Grandi on Mon, Feb 23, 1998 at 02:51:33PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Mon, Feb 23, 1998 at 02:51:33PM -0700, Steve Grandi wrote: > On Mon, 23 Feb 1998, Paul Sandys wrote: > > I suggest you try different power supply. I also spent 3 months > > replacing parts in one FreeBSD server with random crashes, and it ended up > > being the SCSI cable, which worked for 2 years straight before ..... > I had similar experiences about a year ago... it turned out to be the power supply which has become weak months after change of the harddisks to once, which rotate at 7200 rpm. During heavy seeks on the news partitions, the system crashed randomly, making me think of software bugs. --------------------------------------------------------------------------- Thomas Zenker at work thz@lennartz-electronic.de private thz@tuebingen.netsurf.de --------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Feb 24 04:01:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA23633 for freebsd-stable-outgoing; Tue, 24 Feb 1998 04:01:03 -0800 (PST) (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 EAA23621 for ; Tue, 24 Feb 1998 04:00:58 -0800 (PST) (envelope-from evanc@synapse.net) Received: (qmail 20582 invoked from network); 24 Feb 1998 12:00:57 -0000 Received: from cpu1970.adsl.bellglobal.com (HELO cello) (206.47.37.201) by conductor.synapse.net with SMTP; 24 Feb 1998 12:00:57 -0000 Message-ID: <007001bd411b$e6673d90$c9252fce@cello.synapse.net> From: "Evan Champion" To: "John Saunders" , Subject: Re: stable branch funnies Date: Tue, 24 Feb 1998 07:01:10 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk >1) -stable is very volatile and whole programs coming and going, and > failed builds, is a part of life. (I can't really believe this). Right now it is slightly volitile because people are moving large amounts of stable stuff from -current in to -stable in preparation for the imminent 2.2.6 release. I don't think there have been that many mistakes, and they were quickly corrected. jkh and co. have done a pretty good job considering how many patches have been put in. In general, however, stable is basically stagnant change-wise, with maybe a few patches each day to non-critical components. If you look at what is being patched, almost none of the patches are to critical components like the kernel or libc. Most are to bring applications up to date with -current (from your perspective, upgrading a stock 2.2.5 system, you might see a huge number of patches, but that's because you're 6 months behind -stable :-) The only thing that -stable consistently seems to break is make -j, however this has been reported a few times. The problem is that it seems none of the commiters use -j so there isn't much incentive for them to make sure things still work after they commit... Unless you have a multiprocessor machine or are compiling over a relatively high-delay channel (ie: NFS) there isn't any advantage to make -j, and -stable doesn't support SMP anyway so there goes one of the two reasons to use it :-) [Of course, I do compile over NFS, so I'd certainly appreciate it if people stopped breaking it :-)] >2) Somehow cvsup managed to reverse the sup it did a few days ago > and removed things it shouldn't have (evidence boggle going). Or > maybe it just went plain bonkers :-) It was very intentional that boggle went. See the huge discussion that just happened in the freebsd-current and cvs-all... I won't rehash it here as everyone has had enough of it, but it had to do with trademark infringement. Evan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Feb 24 06:33:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12678 for freebsd-stable-outgoing; Tue, 24 Feb 1998 06:33:12 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from versa.eng.comsat.com (root@versa.eng.comsat.com [134.133.169.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12666 for ; Tue, 24 Feb 1998 06:32:53 -0800 (PST) (envelope-from marc@versa.eng.comsat.com) Received: (from marc@localhost) by versa.eng.comsat.com (8.8.5/8.7.3) id JAA05189 for freebsd-stable@FreeBSD.ORG; Tue, 24 Feb 1998 09:32:43 -0500 (EST) Date: Tue, 24 Feb 1998 09:32:43 -0500 (EST) From: Marc Giannoni Message-Id: <199802241432.JAA05189@versa.eng.comsat.com> To: freebsd-stable@FreeBSD.ORG Subject: Installation Problem 2.2.5-stable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I tried to 'upgrade' a 2.2-stable system with a stock 2.2.5-stable cdrom. There was some form of problem with the '/mnt' file system because everything was installing into the root partition. I have two 'slices' wd0s1 for DOS and wd0s2 for FreeBSD. The installation floppy mounted three file systems, but the root file system used '/dev/wd0a' unlike '/dev/wd0s1e' for var and '/dev/wd0s2f' for usr. I think I'll try upgrading with an old 2.2.1 floppy, these seem to work OK. Anybody remember (or heard of this) problem? marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Feb 24 08:14:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24330 for freebsd-stable-outgoing; Tue, 24 Feb 1998 08:14:41 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from relay.rhein-main.de (root@hermes.rhein-main.de [195.37.8.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24318 for ; Tue, 24 Feb 1998 08:14:28 -0800 (PST) (envelope-from nyx.rhein-main.de!tobias@odb.rhein-main.de) Received: from odb.rhein-main.de (odb.rhein-main.de [195.37.8.4]) by relay.rhein-main.de (8.8.7/8.8.7) with SMTP id RAA13308 for ; Tue, 24 Feb 1998 17:12:35 +0100 Received: by odb.rhein-main.de (Smail3.2 #4) id m0y7MwT-0007RqC; Tue, 24 Feb 1998 17:10:49 +0100 (MET) Received: (from tobias@localhost) by nyx.rhein-main.de (8.8.3/8.8.3) id RAA20169 for freebsd-stable@FreeBSD.ORG; Tue, 24 Feb 1998 17:15:19 +0100 Date: Tue, 24 Feb 1998 17:15:19 +0100 From: Tobias Pfeil Message-Id: <199802241615.RAA20169@nyx.rhein-main.de> To: freebsd-stable@FreeBSD.ORG Subject: lost v consoles Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I'm using 2.2.2 on a Toshiba laptop and every now and then I'm loosing all odd numbered virtual consoles. (ttyv1/ttyv3/...) all gone. Then filename completion in zsh ceases in the active console. All of this comes and goes without any noticeable regularity. I recompiled the (pretty standard) PAO kernel and raised the maxusers to 25 but the problem persists. Anybody else seen that kind of behave? --Tobias To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Feb 24 10:17:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11796 for freebsd-stable-outgoing; Tue, 24 Feb 1998 10:17:47 -0800 (PST) (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 KAA11732 for ; Tue, 24 Feb 1998 10:17:42 -0800 (PST) (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.6.9) with ESMTP id KAA08852; Tue, 24 Feb 1998 10:17:07 -0800 (PST) To: Marc Giannoni cc: freebsd-stable@FreeBSD.ORG Subject: Re: Installation Problem 2.2.5-stable In-reply-to: Your message of "Tue, 24 Feb 1998 09:32:43 EST." <199802241432.JAA05189@versa.eng.comsat.com> Date: Tue, 24 Feb 1998 10:17:07 -0800 Message-ID: <8849.888344227@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > wd0s1 for DOS and wd0s2 for FreeBSD. The installation floppy mounted > three file systems, but the root file system used '/dev/wd0a' unlike > '/dev/wd0s1e' for var and '/dev/wd0s2f' for usr. I think I'll try That's a feature, not a bug - the boot blocks don't support slice name parsing yet. :( Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Feb 24 15:41:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07734 for freebsd-stable-outgoing; Tue, 24 Feb 1998 15:41:44 -0800 (PST) (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 PAA07709 for ; Tue, 24 Feb 1998 15:41:22 -0800 (PST) (envelope-from jfieber@indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.7/8.8.7) with SMTP id SAA13075 for ; Tue, 24 Feb 1998 18:41:18 -0500 (EST) Date: Tue, 24 Feb 1998 18:41:18 -0500 (EST) From: John Fieber To: stable@FreeBSD.ORG Subject: grops eats disk Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Okay, I'm puzzled. I run groff, then get an error /: write failed, file system is full Hmm... must be filling up /tmp. I've got about 5 megabytes free on / and I can't imagine why groff would need all that but anyway...I suspend groff and sure enough, df shows that that / is indeed full, but there is nothing unusual in /tmp. In fact I can't find *anything* on the root partition eating up space, yet the space disappears. To make a long story short, rummaging around with fstat and lsof shows: COMMAND PID USER FD TYPE DEVICE SIZE/OFF INODE NAME grops 13016 jfieber 4u VREG 4,0 2596864 1002 / (/dev/sd0a) Sure enough, the SIZE field grows until the root partition is full. Can anyone explain this to me? How is it possible that an ordinary users process can fill up a partition without using the single writable directory (/tmp) on that disk? I'm running 2.2.5-RELEASE plus a couple security patches. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Feb 24 15:53:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09308 for freebsd-stable-outgoing; Tue, 24 Feb 1998 15:53:57 -0800 (PST) (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 PAA09264 for ; Tue, 24 Feb 1998 15:53:43 -0800 (PST) (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 PAA17125; Tue, 24 Feb 1998 15:51:32 -0800 (PST) Message-Id: <199802242351.PAA17125@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: John Fieber cc: stable@FreeBSD.ORG Subject: Re: grops eats disk In-reply-to: Your message of "Tue, 24 Feb 1998 18:41:18 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Feb 1998 15:51:31 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > Okay, I'm puzzled. I run groff, then get an error > > /: write failed, file system is full > > Hmm... must be filling up /tmp. I've got about 5 megabytes free > on / and I can't imagine why groff would need all that but > anyway...I suspend groff and sure enough, df shows that that / is > indeed full, but there is nothing unusual in /tmp. In fact I > can't find *anything* on the root partition eating up space, yet > the space disappears. This is the traditional "invisible temporary file" trick, I suspect. The file has been deleted, but because it's still open, it still exists. If you kill groff, the space will be freed again. Groff just nukes the file to minimise the chances of temporary file collision, and to ensure that even if it crashes horribly you're not left with temporary files lying around. -- \\ 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 Tue Feb 24 16:01:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10585 for freebsd-stable-outgoing; Tue, 24 Feb 1998 16:01:55 -0800 (PST) (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 QAA10578 for ; Tue, 24 Feb 1998 16:01:44 -0800 (PST) (envelope-from jfieber@indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.7/8.8.7) with SMTP id TAA13141; Tue, 24 Feb 1998 19:01:35 -0500 (EST) Date: Tue, 24 Feb 1998 19:01:35 -0500 (EST) From: John Fieber To: Mike Smith cc: stable@FreeBSD.ORG Subject: Re: grops eats disk In-Reply-To: <199802242351.PAA17125@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Tue, 24 Feb 1998, Mike Smith wrote: > This is the traditional "invisible temporary file" trick, I suspect. Mmm... that makes sense. Thanks. Now to figure out how to tell groff to put its temp files somewhere else... -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Feb 24 16:07:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12108 for freebsd-stable-outgoing; Tue, 24 Feb 1998 16:07:39 -0800 (PST) (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 QAA12094 for ; Tue, 24 Feb 1998 16:07:32 -0800 (PST) (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 QAA17179; Tue, 24 Feb 1998 16:04:43 -0800 (PST) Message-Id: <199802250004.QAA17179@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: John Fieber cc: Mike Smith , stable@FreeBSD.ORG Subject: Re: grops eats disk In-reply-to: Your message of "Tue, 24 Feb 1998 19:01:35 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Feb 1998 16:04:42 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > On Tue, 24 Feb 1998, Mike Smith wrote: > > > This is the traditional "invisible temporary file" trick, I suspect. > > Mmm... that makes sense. Thanks. Now to figure out how to tell > groff to put its temp files somewhere else... A quick run of # strings `which grops` suggests GROFF_TMPDIR and TMPDIR are worth trying. -- \\ 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 Tue Feb 24 18:02:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03135 for freebsd-stable-outgoing; Tue, 24 Feb 1998 18:02:36 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from megaweapon.zigg.com (tcgr2-77.dialup.alliance.net [207.74.43.77]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03117 for ; Tue, 24 Feb 1998 18:02:26 -0800 (PST) (envelope-from matt@zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.8.8/8.8.8) with SMTP id VAA10348 for ; Tue, 24 Feb 1998 21:02:44 -0500 (EST) (envelope-from matt@megaweapon.zigg.com) Date: Tue, 24 Feb 1998 21:02:43 -0500 (EST) From: Matt Behrens To: stable@FreeBSD.ORG Subject: Bringing 2.1.6-RELEASE up to 2.2.5-STABLE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I have a 2.1.6-RELEASE CD that I want to donate to a poor friend. Can she subsequently use cvsup to bring her system up to 2.2.5-STABLE, and if so, does anyone remember all the extra steps involved? (That file that I suggested awhile back, in the root of the CVS repos, that noted important changes would be real helpful now) :) Matt Behrens | "Separation of church and state is http://www.zigg.com/ | absolutely essential," they say. Chanop Script Coordinator | Why, then, do they make America's World-Wide FreeNet IRC Network | state religion atheism? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Feb 24 19:06:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13632 for freebsd-stable-outgoing; Tue, 24 Feb 1998 19:06:38 -0800 (PST) (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 TAA13602 for ; Tue, 24 Feb 1998 19:06:26 -0800 (PST) (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 TAA19009; Tue, 24 Feb 1998 19:05:45 -0800 (PST) (envelope-from jdp) Message-Id: <199802250305.TAA19009@austin.polstra.com> To: john.saunders@scitec.com.au Subject: Re: stable branch funnies In-Reply-To: <34F25BC6.13E2F7A8@scitec.com.au> References: <34F25BC6.13E2F7A8@scitec.com.au> Organization: Polstra & Co., Seattle, WA Cc: stable@FreeBSD.ORG Date: Tue, 24 Feb 1998 19:05:45 -0800 From: John Polstra Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk In article <34F25BC6.13E2F7A8@scitec.com.au>, John Saunders wrote: > Then I read up on cvsup and [...] > Reading up on the cvsup man page [...] First let me say that it's heartwarming to find somebody who has read the man page. :-) > it says that it maintains a file(s) so it knows what versions it > has of each file. I have yet to locate these files and after 2 runs > of cvsup I would have expected these files to be created. Is these > missing files somehow confusing cvsup about what versions it has and > what it needs? As somebody already answered, they're in subdirectories of /usr/sup if you use the "/usr/share/examples/cvsup/stable-supfile" supfile. I'm sure they're being created, because cvsup would complain if it couldn't make the files. In short, everything's working the way it's supposed to. :-) -- 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 Feb 24 19:11:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14352 for freebsd-stable-outgoing; Tue, 24 Feb 1998 19:11:03 -0800 (PST) (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 TAA14282 for ; Tue, 24 Feb 1998 19:10:43 -0800 (PST) (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 TAA19041; Tue, 24 Feb 1998 19:10:21 -0800 (PST) (envelope-from jdp) Message-Id: <199802250310.TAA19041@austin.polstra.com> To: matt@zigg.com Subject: Re: Bringing 2.1.6-RELEASE up to 2.2.5-STABLE In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: stable@FreeBSD.ORG Date: Tue, 24 Feb 1998 19:10:21 -0800 From: John Polstra Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk In article , Matt Behrens wrote: > I have a 2.1.6-RELEASE CD that I want to donate to a poor friend. Can she > subsequently use cvsup to bring her system up to 2.2.5-STABLE, and if so, > does anyone remember all the extra steps involved? It should probably work. One thing you'll need to do is add the line: network:*:69: to your /etc/group file before doing the make world. There may be other things necessary as well, but I don't remember any. If there are, you'll find out. :-) -- 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 Feb 24 19:46:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA19408 for freebsd-stable-outgoing; Tue, 24 Feb 1998 19:46:55 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mikey.nofear.com (mikey.nofear.com [199.106.6.190]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA19396 for ; Tue, 24 Feb 1998 19:46:45 -0800 (PST) (envelope-from mvh@nofear.com) Received: (from mvh@localhost) by mikey.nofear.com (8.8.8/8.8.8) id TAA12543; Tue, 24 Feb 1998 19:46:41 -0800 (PST) (envelope-from mvh) Date: Tue, 24 Feb 1998 19:46:41 -0800 (PST) Message-Id: <199802250346.TAA12543@mikey.nofear.com> From: "Michael V. Harding" To: freebsd-stable@FreeBSD.ORG Subject: Netcom blocked? Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I can't seem to send mail to the stable group from netcom - is this domain blocked? If so, it's sort of harsh - I can't even unsubscribe! Mike Harding To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Feb 24 21:04:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01136 for freebsd-stable-outgoing; Tue, 24 Feb 1998 21:04:46 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from netmug.org (perl@netmug.org [207.88.43.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA01131 for ; Tue, 24 Feb 1998 21:04:42 -0800 (PST) (envelope-from perl@netmug.org) Received: from localhost (perl@localhost) by netmug.org (8.8.8/NetMUG_1.0.0) with SMTP id VAA17407; Tue, 24 Feb 1998 21:03:37 -0800 (PST) Date: Tue, 24 Feb 1998 21:03:37 -0800 (PST) From: Michael Haro To: John Polstra cc: matt@zigg.com, stable@FreeBSD.ORG Subject: Re: Bringing 2.1.6-RELEASE up to 2.2.5-STABLE In-Reply-To: <199802250310.TAA19041@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk You will also need to add a /etc/login.conf file Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Feb 24 22:11:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15521 for freebsd-stable-outgoing; Tue, 24 Feb 1998 22:11:16 -0800 (PST) (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 WAA15410 for ; Tue, 24 Feb 1998 22:11:08 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #3) id 0y7a3R-0000SX-00; Tue, 24 Feb 1998 22:10:53 -0800 Date: Tue, 24 Feb 1998 22:10:49 -0800 (PST) From: Tom To: "Michael V. Harding" cc: freebsd-stable@FreeBSD.ORG Subject: Re: Netcom blocked? In-Reply-To: <199802250346.TAA12543@mikey.nofear.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Tue, 24 Feb 1998, Michael V. Harding wrote: > I can't seem to send mail to the stable group from netcom - is this > domain blocked? If so, it's sort of harsh - I can't even unsubscribe! > > Mike Harding Some netcom servers have been in out of the RBL lately. Netcom thinks that is it really cool to allow unrestricted relaying. Any site that uses RBL will simply refuse mail mail from RBL listed sites. I heard that the President of Netcom called Paul Vixie personally to negotiate how to get off the RBL. See http://maps.vix.com for RBL info. I'm not sure if any FreeBSD servers use RBL, but I think they should. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Feb 24 23:26:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28666 for freebsd-stable-outgoing; Tue, 24 Feb 1998 23:26:08 -0800 (PST) (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 XAA28649 for ; Tue, 24 Feb 1998 23:25:59 -0800 (PST) (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.6.9) with ESMTP id XAA15575; Tue, 24 Feb 1998 23:25:36 -0800 (PST) To: Tom cc: "Michael V. Harding" , freebsd-stable@FreeBSD.ORG Subject: Re: Netcom blocked? In-reply-to: Your message of "Tue, 24 Feb 1998 22:10:49 PST." Date: Tue, 24 Feb 1998 23:25:36 -0800 Message-ID: <15572.888391536@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > I'm not sure if any FreeBSD servers use RBL, but I think they should. They do, as do cdrom.com's. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 00:46:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09039 for freebsd-stable-outgoing; Wed, 25 Feb 1998 00:46:56 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gothik.net (beav@[203.33.252.176]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09030 for ; Wed, 25 Feb 1998 00:46:38 -0800 (PST) (envelope-from beav@gothik.net) Received: (from beav@localhost) by gothik.net (8.8.8/8.8.7) id QAA07122 for freebsd-stable@freebsd.org; Wed, 25 Feb 1998 16:45:13 +0800 (WST) (envelope-from beav) Date: Wed, 25 Feb 1998 16:45:13 +0800 (WST) From: beav@nw.com.au Message-Id: <199802250845.QAA07122@gothik.net> To: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Hi... I'm running 2.2.5-STABLE on my PPro180, and have had lots of problems when trying to "make world" from /usr/src, here's the end snippet of the log.. ===> share/examples [...] install -C -o bin -g bin -m 644 etc/README.examples /usr/share/examples/etc/README.examples install -C -o bin -g bin -m 644 etc/bsd-style-copyright /usr/share/examples/etc/bsd-style-copyright install -C -o bin -g bin -m 644 etc/skey.access /usr/share/examples/etc/skey.access install -C -o bin -g bin -m 644 etc/README.examples,v /usr/share/examples/etc/README.examples,v install -C -o bin -g bin -m 644 etc/Attic/aliases,v /usr/share/examples/etc/Attic/aliases,v install: mkstemp: /usr/share/examples/etc/Attic for /usr/share/examples/etc/Attic/aliases,v: No such file or directory *** Error code 71 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. [===] that's it. Any ideas? Thanks, = beav. beav@nw.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 01:24:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13345 for freebsd-stable-outgoing; Wed, 25 Feb 1998 01:24:28 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from solaris.matti.ee (root@solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA13310 for ; Wed, 25 Feb 1998 01:24:08 -0800 (PST) (envelope-from vallo@matti.ee) Received: from localhost (vallo@localhost [127.0.0.1]) by solaris.matti.ee (8.8.8/8.8.8.s) with SMTP id LAA03288; Wed, 25 Feb 1998 11:23:19 +0200 (EET) Date: Wed, 25 Feb 1998 11:23:18 +0200 (EET) From: Vallo Kallaste X-Sender: vallo@solaris To: John Polstra cc: matt@zigg.com, stable@FreeBSD.ORG Subject: Re: Bringing 2.1.6-RELEASE up to 2.2.5-STABLE In-Reply-To: <199802250310.TAA19041@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Tue, 24 Feb 1998, John Polstra wrote: > It should probably work. > > One thing you'll need to do is add the line: > > network:*:69: > > to your /etc/group file before doing the make world. There may be > other things necessary as well, but I don't remember any. If there > are, you'll find out. :-) *** If I remember, there are also one more missing line in /etc/group ppp:*:1002: Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 05:34:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA09927 for freebsd-stable-outgoing; Wed, 25 Feb 1998 05:34:51 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from tyree.iii.co.uk ([195.89.149.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA09918 for ; Wed, 25 Feb 1998 05:34:31 -0800 (PST) (envelope-from nik@iii.co.uk) From: nik@iii.co.uk Received: from carrig.strand.iii.co.uk (carrig.strand.iii.co.uk [192.168.7.25]) by tyree.iii.co.uk (8.8.8/8.8.8) with ESMTP id KAA10093; Wed, 25 Feb 1998 10:21:38 GMT Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.7/8.8.7) id KAA03012; Wed, 25 Feb 1998 10:26:56 GMT Message-ID: <19980225102655.59596@iii.co.uk> Date: Wed, 25 Feb 1998 10:26:55 +0000 To: Matt Behrens Cc: stable@FreeBSD.ORG Subject: Re: Bringing 2.1.6-RELEASE up to 2.2.5-STABLE References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e In-Reply-To: ; from Matt Behrens on Tue, Feb 24, 1998 at 09:02:43PM -0500 Organization: interactive investor Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Tue, Feb 24, 1998 at 09:02:43PM -0500, Matt Behrens wrote: > I have a 2.1.6-RELEASE CD that I want to donate to a poor friend. Can she > subsequently use cvsup to bring her system up to 2.2.5-STABLE, and if so, > does anyone remember all the extra steps involved? The tutorial at http://www.nothing-going-on.demon.co.uk/FreeBSD/make-world/make-world.html *should* cover all the necessary steps, including things like the addition of extra groups. If she's got the patience I'd appreciate her working through the tutorial and getting back to me with any comments or suggestions for improvements she has afterwards. N -- --+==[ Nik Clayton is Just Another Perl Hacker at Interactive Investor ]==+-- . . . and relax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 05:54:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA11782 for freebsd-stable-outgoing; Wed, 25 Feb 1998 05:54:03 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pandora.hh.kew.com (root@kendra.ne.mediaone.net [24.128.94.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA11747 for ; Wed, 25 Feb 1998 05:53:39 -0800 (PST) (envelope-from ahd@pandora.hh.kew.com) Received: (from root@localhost) by pandora.hh.kew.com (8.8.5/8.8.5) id IAA00561 for stable@FreeBSD.ORG; Wed, 25 Feb 1998 08:53:35 -0500 (EST) Date: Wed, 25 Feb 1998 08:53:35 -0500 (EST) From: Drew Derbyshire Message-Id: <199802251353.IAA00561@pandora.hh.kew.com> To: stable@FreeBSD.ORG Subject: BIND 8.* and STABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Any reason I can't take the BIND port in the CURRENT ports collection and install it on -STABLE? I know the thing builds, but that doesn't say I won't cripple my system when the resolver library gets replaced. I also notice the install seems dummied out in the BIND makefile, any idea why? -ahd- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 06:30:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20760 for freebsd-stable-outgoing; Wed, 25 Feb 1998 06:30:22 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20676; Wed, 25 Feb 1998 06:30:01 -0800 (PST) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199802251430.GAA20676@hub.freebsd.org> Subject: Re: Netcom blocked? In-Reply-To: <199802250346.TAA12543@mikey.nofear.com> from "Michael V. Harding" at "Feb 24, 98 07:46:41 pm" To: mvh@nofear.com (Michael V. Harding) Date: Wed, 25 Feb 1998 06:30:01 -0800 (PST) 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 Michael V. Harding wrote: > > I can't seem to send mail to the stable group from netcom - is this > domain blocked? If so, it's sort of harsh - I can't even unsubscribe! > > Mike Harding no...netcom is not, and never has been blocked. i do not see a "*harding*@netcom*" subscribed to any of the lists. neither does an address at "*nofear*". please send me an email from the lists, complete with headers. i will remove you from the lists if that is what you want. but i need to know the address that you subscribed. ;) jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 06:37:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23625 for freebsd-stable-outgoing; Wed, 25 Feb 1998 06:37:51 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mikey.nofear.com (mikey.nofear.com [199.106.6.190]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23399; Wed, 25 Feb 1998 06:37:23 -0800 (PST) (envelope-from mvh@nofear.com) Received: (from mvh@localhost) by mikey.nofear.com (8.8.8/8.8.8) id GAA16136; Wed, 25 Feb 1998 06:37:18 -0800 (PST) (envelope-from mvh) Date: Wed, 25 Feb 1998 06:37:18 -0800 (PST) Message-Id: <199802251437.GAA16136@mikey.nofear.com> From: "Michael V. Harding" To: jmb@FreeBSD.ORG CC: freebsd-stable@FreeBSD.ORG In-reply-to: <199802251430.GAA20676@hub.freebsd.org> (jmb@FreeBSD.ORG) Subject: Re: Netcom blocked? References: <199802251430.GAA20676@hub.freebsd.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I don't want to unsubscribe - I was just pointing out that I can't. Netcom is not in the RBL - I set up the mail server I'm using now to use the RBL, and it doesn't block email. Possibly my setup is causing a problem - I don't use Netcom's mail server, I use my own via 'squid', so the 'helo' may appear flakey, thought the domain should be good. I telneted into hub.freeebsd.org directly, and was decidedly bounced. Also, netcom's shell mail servers still appear to allow relaying... Hopefully this will get hashed out soon... From: "Jonathan M. Bresler" Date: Wed, 25 Feb 1998 06:30:01 -0800 (PST) Cc: freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset=US-ASCII Michael V. Harding wrote: > > I can't seem to send mail to the stable group from netcom - is this > domain blocked? If so, it's sort of harsh - I can't even unsubscribe! > > Mike Harding no...netcom is not, and never has been blocked. i do not see a "*harding*@netcom*" subscribed to any of the lists. neither does an address at "*nofear*". please send me an email from the lists, complete with headers. i will remove you from the lists if that is what you want. but i need to know the address that you subscribed. ;) jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 06:38:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23783 for freebsd-stable-outgoing; Wed, 25 Feb 1998 06:38:22 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23714; Wed, 25 Feb 1998 06:38:00 -0800 (PST) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199802251438.GAA23714@hub.freebsd.org> Subject: Re: Netcom blocked? In-Reply-To: from Tom at "Feb 24, 98 10:10:49 pm" To: tom@uniserve.com (Tom) Date: Wed, 25 Feb 1998 06:37:59 -0800 (PST) Cc: mvh@nofear.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 Tom wrote: > > On Tue, 24 Feb 1998, Michael V. Harding wrote: > > > I can't seem to send mail to the stable group from netcom - is this > > domain blocked? If so, it's sort of harsh - I can't even unsubscribe! > > > > Mike Harding > > Some netcom servers have been in out of the RBL lately. Netcom thinks > that is it really cool to allow unrestricted relaying. Any site that uses > RBL will simply refuse mail mail from RBL listed sites. I heard that the > President of Netcom called Paul Vixie personally to negotiate how to get > off the RBL. > > See http://maps.vix.com for RBL info. > > I'm not sure if any FreeBSD servers use RBL, but I think they should. we certainly do use the RBL. if netcom managed to get themselves blacklisted, well its not surprising given the amount of spam that they enable others to relay through them. i found your subscriptions: (i should have tried "mvh" first) freebsd-stable:mvh@netcom.com stable:mvh@netcom.com jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 06:52:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA27810 for freebsd-stable-outgoing; Wed, 25 Feb 1998 06:52:10 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mikey.nofear.com (mikey.nofear.com [199.106.6.190]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA27770; Wed, 25 Feb 1998 06:51:51 -0800 (PST) (envelope-from mvh@nofear.com) Received: (from mvh@localhost) by mikey.nofear.com (8.8.8/8.8.8) id GAA16242; Wed, 25 Feb 1998 06:51:46 -0800 (PST) (envelope-from mvh) Date: Wed, 25 Feb 1998 06:51:46 -0800 (PST) Message-Id: <199802251451.GAA16242@mikey.nofear.com> From: "Michael V. Harding" To: jmb@FreeBSD.ORG CC: tom@uniserve.com, freebsd-stable@FreeBSD.ORG In-reply-to: <199802251438.GAA23714@hub.freebsd.org> (jmb@freebsd.org) Subject: Re: Netcom blocked? References: <199802251438.GAA23714@hub.freebsd.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Mystery solved. After doing a 'make' in /etc/mail, I find NETCOM.COM listed in 'domains.txt'. I don't know who maintains this list, but hopefully netcom will turn off relaying and stop this BS. I installed anti-relaying myself - they should be able to handle this - they are running sendmail 8.8.8... From: "Jonathan M. Bresler" Date: Wed, 25 Feb 1998 06:37:59 -0800 (PST) Cc: mvh@nofear.com, freebsd-stable@freebsd.org Content-Type: text/plain; charset=US-ASCII Tom wrote: > > On Tue, 24 Feb 1998, Michael V. Harding wrote: > > > I can't seem to send mail to the stable group from netcom - is this > > domain blocked? If so, it's sort of harsh - I can't even unsubscribe! > > > > Mike Harding > > Some netcom servers have been in out of the RBL lately. Netcom thinks > that is it really cool to allow unrestricted relaying. Any site that uses > RBL will simply refuse mail mail from RBL listed sites. I heard that the > President of Netcom called Paul Vixie personally to negotiate how to get > off the RBL. > > See http://maps.vix.com for RBL info. > > I'm not sure if any FreeBSD servers use RBL, but I think they should. we certainly do use the RBL. if netcom managed to get themselves blacklisted, well its not surprising given the amount of spam that they enable others to relay through them. i found your subscriptions: (i should have tried "mvh" first) freebsd-stable:mvh@netcom.com stable:mvh@netcom.com jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 07:13:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02136 for freebsd-stable-outgoing; Wed, 25 Feb 1998 07:13:32 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mx3.cso.uiuc.edu (mx3.cso.uiuc.edu [128.174.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02097; Wed, 25 Feb 1998 07:13:05 -0800 (PST) (envelope-from igor@alecto.physics.uiuc.edu) Received: from alecto.physics.uiuc.edu (alecto.physics.uiuc.edu [130.126.8.20]) by mx3.cso.uiuc.edu (8.8.8/8.8.8) with SMTP id JAA20834; Wed, 25 Feb 1998 09:12:19 -0600 (CST) Received: by alecto.physics.uiuc.edu (940816.SGI.8.6.9/940406.SGI) id JAA18076; Wed, 25 Feb 1998 09:08:21 -0600 From: igor@alecto.physics.uiuc.edu (Igor Roshchin) Message-Id: <199802251508.JAA18076@alecto.physics.uiuc.edu> Subject: apache for stable To: stable@FreeBSD.ORG, ports@FreeBSD.ORG Date: Wed, 25 Feb 1998 09:08:20 -0600 (CST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Hello! apache for 2.2.5 does not have corresponding distfile. Makefile wnats to use 1.2.4 version. www.apache.org has just 1.2.3.* and 1.2.5 ftp.freebsd.org/pub/FreeBSD/distfiles has versions below 1.2.3 Thanks! IgoR To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 07:19:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04119 for freebsd-stable-outgoing; Wed, 25 Feb 1998 07:19:19 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from exchange.fse.com (exchange.fse.com [199.165.143.127]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA03976 for ; Wed, 25 Feb 1998 07:18:55 -0800 (PST) (envelope-from Mark@FutureSoft.com) Received: by exchange.fse.com with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52) id <01BD41CE.618841B0@exchange.fse.com>; Wed, 25 Feb 1998 09:18:49 -0600 Message-ID: From: "Trefney, Mark" To: "'Freebsd-stable@freebsd.org'" Date: Wed, 25 Feb 1998 09:18:47 -0600 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk UNSUBSCRIBE FREEBSD-STABLE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 07:38:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07395 for freebsd-stable-outgoing; Wed, 25 Feb 1998 07:38:32 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from solaric.UkrCard.Kiev.UA (ukrcard-gu.gu.net [194.93.170.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA07305; Wed, 25 Feb 1998 07:38:05 -0800 (PST) (envelope-from alex@solaric.UkrCard.Kiev.UA) Received: from localhost (alex@localhost) by solaric.UkrCard.Kiev.UA (8.8.8/8.8.7) with SMTP id RAA15576; Wed, 25 Feb 1998 17:37:41 +0200 (EET) (envelope-from alex@solaric.UkrCard.Kiev.UA) Date: Wed, 25 Feb 1998 17:37:39 +0200 (EET) From: Alexander Tatmaniants To: Igor Roshchin cc: stable@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: apache for stable In-Reply-To: <199802251508.JAA18076@alecto.physics.uiuc.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Wed, 25 Feb 1998, Igor Roshchin wrote: > Hello! > > apache for 2.2.5 does not have corresponding distfile. > Makefile wnats to use 1.2.4 version. > www.apache.org has just 1.2.3.* and 1.2.5 > ftp.freebsd.org/pub/FreeBSD/distfiles has versions below 1.2.3 apache (actualy apache-1.2.5) from ports-current perfectly work for me at my -stable box > > Thanks! > > IgoR > > 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 Feb 25 08:29:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15512 for freebsd-stable-outgoing; Wed, 25 Feb 1998 08:29:58 -0800 (PST) (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 IAA15400 for ; Wed, 25 Feb 1998 08:29:34 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from gnipahellir.ifi.uio.no (2602@gnipahellir.ifi.uio.no [129.240.64.86]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id RAA07458; Wed, 25 Feb 1998 17:29:04 +0100 (MET) Received: (from dag-erli@localhost) by gnipahellir.ifi.uio.no ; Wed, 25 Feb 1998 17:29:03 +0100 (MET) To: John Fieber Cc: stable@FreeBSD.ORG Subject: Re: grops eats disk References: Organization: Gutteklubben Terrasse / KRST X-url: http://www.ifi.uio.no/~dag-erli/ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit From: dag-erli@ifi.uio.no (Dag-Erling Coidan Smørgrav) Date: 25 Feb 1998 17:29:02 +0100 In-Reply-To: John Fieber's message of "Tue, 24 Feb 1998 18:41:18 -0500 (EST)" Message-ID: Lines: 13 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk John Fieber writes: > Okay, I'm puzzled. I run groff, then get an error > > /: write failed, file system is full Knee-jerk reaction: # echo 'TMPDIR=/usr/tmp ; export TMPDIR' >> /etc/profile IMHO this should be in FreeBSD's default /etc/profile. -- "I have a closed mind. It helps keeping the rain out." (Michael Press on a.s.r) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 08:38:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17711 for freebsd-stable-outgoing; Wed, 25 Feb 1998 08:38:49 -0800 (PST) (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 IAA17691 for ; Wed, 25 Feb 1998 08:38:23 -0800 (PST) (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 IAA23921; Wed, 25 Feb 1998 08:38:16 -0800 (PST) (envelope-from jdp) Message-Id: <199802251638.IAA23921@austin.polstra.com> To: Vallo Kallaste cc: stable@FreeBSD.ORG Subject: Re: Bringing 2.1.6-RELEASE up to 2.2.5-STABLE In-reply-to: Your message of "Wed, 25 Feb 1998 11:23:18 +0200." Date: Wed, 25 Feb 1998 08:38:15 -0800 From: John Polstra Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > If I remember, there are also one more missing line in /etc/group > > ppp:*:1002: No, not in -stable or -current. I think there might have been a "ppp" group at one time, but not any more. -- 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 Wed Feb 25 08:41:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18058 for freebsd-stable-outgoing; Wed, 25 Feb 1998 08:41:16 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17942 for ; Wed, 25 Feb 1998 08:40:36 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.8.8/8.8.7) with SMTP id LAA11524 for ; Wed, 25 Feb 1998 11:40:41 -0500 (EST) Date: Wed, 25 Feb 1998 11:40:41 -0500 (EST) From: jack To: freebsd-stable@FreeBSD.ORG Subject: Re: Netcom blocked? In-Reply-To: <199802251437.GAA16136@mikey.nofear.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Wed, 25 Feb 1998, Michael V. Harding wrote: > Netcom is not in the RBL - I set up the mail server I'm using now to > use the RBL, and it doesn't block email. Seems they've sweet talked Paul into taking them off the list, claiming that they will close their open relays by the end of February. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 08:43:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18670 for freebsd-stable-outgoing; Wed, 25 Feb 1998 08:43:58 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18544 for ; Wed, 25 Feb 1998 08:43:18 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id IAA29855; Wed, 25 Feb 1998 08:43:03 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id IAA23092; Wed, 25 Feb 1998 08:43:02 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id IAA27775; Wed, 25 Feb 1998 08:43:01 -0800 (PST) From: Don Lewis Message-Id: <199802251643.IAA27775@salsa.gv.tsc.tdk.com> Date: Wed, 25 Feb 1998 08:43:00 -0800 In-Reply-To: dag-erli@ifi.uio.no (Dag-Erling Coidan Smørgrav) "Re: grops eats disk" (Feb 25, 5:29pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: dag-erli@ifi.uio.no (Dag-Erling Coidan Smørgrav), John Fieber Subject: Re: grops eats disk Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Feb 25, 5:29pm, Dag-Erling Coidan Smørgrav wrote: } Subject: Re: grops eats disk } Knee-jerk reaction: } } # echo 'TMPDIR=/usr/tmp ; export TMPDIR' >> /etc/profile } } IMHO this should be in FreeBSD's default /etc/profile. Not for those of us who use a nice big MFS partition for /tmp and don't want our /var/tmp clogged up with files that can be safely disposed of by a reboot. I want to save room in /var/tmp for things that should be preserved across reboots, like editor temporaries. --- Truck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 08:51:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20227 for freebsd-stable-outgoing; Wed, 25 Feb 1998 08:51:53 -0800 (PST) (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 IAA19863 for ; Wed, 25 Feb 1998 08:49:39 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from gnipahellir.ifi.uio.no (2602@gnipahellir.ifi.uio.no [129.240.64.86]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id RAA09697; Wed, 25 Feb 1998 17:49:11 +0100 (MET) Received: (from dag-erli@localhost) by gnipahellir.ifi.uio.no ; Wed, 25 Feb 1998 17:49:11 +0100 (MET) To: John Polstra Cc: matt@zigg.com, stable@FreeBSD.ORG Subject: Re: Bringing 2.1.6-RELEASE up to 2.2.5-STABLE References: <199802250310.TAA19041@austin.polstra.com> Organization: Gutteklubben Terrasse / KRST X-url: http://www.ifi.uio.no/~dag-erli/ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit From: dag-erli@ifi.uio.no (Dag-Erling Coidan Smørgrav) Date: 25 Feb 1998 17:49:10 +0100 In-Reply-To: John Polstra's message of "Tue, 24 Feb 1998 19:10:21 -0800" Message-ID: Lines: 43 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk John Polstra writes: > In article , > Matt Behrens wrote: > > I have a 2.1.6-RELEASE CD that I want to donate to a poor friend. Can she > > subsequently use cvsup to bring her system up to 2.2.5-STABLE, and if so, > > does anyone remember all the extra steps involved? > > It should probably work. > > One thing you'll need to do is add the line: > > network:*:69: > > to your /etc/group file before doing the make world. There may be > other things necessary as well, but I don't remember any. If there > are, you'll find out. :-) Been there, done that (nearly). I recommend the following procedure: - install a bare-bones 2.1.6R and the bare minimum of packages (bash, less, lynx, ncftp, cvsup-nogui) - fetch the complete 2.2.5-STABLE sources using cvsup - copy /usr/src/etc/make.conf to /etc/make.conf, and edit it - make buildworld - rename /etc to /oldetc and copy over crucial files (pwd.db, groups, perhaps one or two others) - 'cd /usr/src/etc ; make distribution DESTDIR=/'. - make installworld - build a kernel - reboot - remove all packages and replace with newer versions from ftp.*.freebsd.org - customize /etc/rc.conf etc. - install X and other cruft Note that I've never done this on 2.1.6R (only on 2.2.1R and 2.2.2R), so YMMV. Also note that fiddling with /etc/make.conf can significantly speed up this process. -- "I have a closed mind. It helps keeping the rain out." (Michael Press on a.s.r) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 09:22:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27755 for freebsd-stable-outgoing; Wed, 25 Feb 1998 09:22:06 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27577; Wed, 25 Feb 1998 09:21:11 -0800 (PST) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199802251721.JAA27577@hub.freebsd.org> Subject: Re: Netcom blocked? In-Reply-To: <199802251451.GAA16242@mikey.nofear.com> from "Michael V. Harding" at "Feb 25, 98 06:51:46 am" To: mvh@nofear.com (Michael V. Harding) Date: Wed, 25 Feb 1998 09:21:07 -0800 (PST) Cc: jmb@FreeBSD.ORG, tom@uniserve.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 Michael V. Harding wrote: > > Mystery solved. After doing a 'make' in /etc/mail, I find NETCOM.COM > listed in 'domains.txt'. I don't know who maintains this list, but > hopefully netcom will turn off relaying and stop this BS. I installed > anti-relaying myself - they should be able to handle this - they are > running sendmail 8.8.8... i have removed NETCOM.COM from the /etc/mail/domains.txt on hub.freebsd.org and recreated the database (make install) you should be able to send mail to the lists now. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 09:22:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27779 for freebsd-stable-outgoing; Wed, 25 Feb 1998 09:22:10 -0800 (PST) (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 JAA27558 for ; Wed, 25 Feb 1998 09:21:02 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from gnipahellir.ifi.uio.no (2602@gnipahellir.ifi.uio.no [129.240.64.86]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id SAA13832; Wed, 25 Feb 1998 18:20:50 +0100 (MET) Received: (from dag-erli@localhost) by gnipahellir.ifi.uio.no ; Wed, 25 Feb 1998 18:20:50 +0100 (MET) To: Don Lewis Cc: John Fieber , stable@FreeBSD.ORG Subject: Re: grops eats disk References: <199802251643.IAA27775@salsa.gv.tsc.tdk.com> Organization: Gutteklubben Terrasse / KRST X-url: http://www.ifi.uio.no/~dag-erli/ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit From: dag-erli@ifi.uio.no (Dag-Erling Coidan Smørgrav) Date: 25 Feb 1998 18:20:49 +0100 In-Reply-To: Don Lewis's message of "Wed, 25 Feb 1998 08:43:00 -0800" Message-ID: Lines: 15 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Don Lewis writes: > On Feb 25, 5:29pm, Dag-Erling Coidan Smørgrav wrote: > } # echo 'TMPDIR=/usr/tmp ; export TMPDIR' >> /etc/profile > } > } IMHO this should be in FreeBSD's default /etc/profile. > > Not for those of us who use a nice big MFS partition for /tmp and don't > want our /var/tmp clogged up with files that can be safely disposed of > by a reboot. I want to save room in /var/tmp for things that should > be preserved across reboots, like editor temporaries. I wrote /usr/tmp, not /var/tmp. -- "I have a closed mind. It helps keeping the rain out." (Michael Press on a.s.r) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 09:26:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29020 for freebsd-stable-outgoing; Wed, 25 Feb 1998 09:26:52 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA28917 for ; Wed, 25 Feb 1998 09:26:08 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id JAA00822; Wed, 25 Feb 1998 09:25:57 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id JAA23941; Wed, 25 Feb 1998 09:25:56 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id JAA28263; Wed, 25 Feb 1998 09:25:55 -0800 (PST) From: Don Lewis Message-Id: <199802251725.JAA28263@salsa.gv.tsc.tdk.com> Date: Wed, 25 Feb 1998 09:25:55 -0800 In-Reply-To: dag-erli@ifi.uio.no (Dag-Erling Coidan Smørgrav) "Re: grops eats disk" (Feb 25, 6:20pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: dag-erli@ifi.uio.no (Dag-Erling Coidan Smørgrav), Don Lewis Subject: Re: grops eats disk Cc: John Fieber , stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Feb 25, 6:20pm, Dag-Erling Coidan Smørgrav wrote: } Subject: Re: grops eats disk } Don Lewis writes: } > On Feb 25, 5:29pm, Dag-Erling Coidan Smørgrav wrote: } > } # echo 'TMPDIR=/usr/tmp ; export TMPDIR' >> /etc/profile } > } } > } IMHO this should be in FreeBSD's default /etc/profile. } > } > Not for those of us who use a nice big MFS partition for /tmp and don't } > want our /var/tmp clogged up with files that can be safely disposed of } > by a reboot. I want to save room in /var/tmp for things that should } > be preserved across reboots, like editor temporaries. } } I wrote /usr/tmp, not /var/tmp. Wouldn't work for me. news: {1362} ls -l /usr/tmp ls: /usr/tmp: No such file or directory news: {1363} df /usr Filesystem 512-blocks Used Avail Capacity Mounted on /dev/sd0s1f 196958 166260 14942 92% /usr I'm also allergic to having world writeable directories in the same partition as setuid executables or even any executables. I prefer to have world writeable directories mounted nodev,noexec. --- Truck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 10:48:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16993 for freebsd-stable-outgoing; Wed, 25 Feb 1998 10:48:21 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from bigbrother (bigbrother.rstcorp.com [206.29.49.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA16871 for ; Wed, 25 Feb 1998 10:48:12 -0800 (PST) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by bigbrother (8.6.12/8.6.9) id OAA24770 for ; Wed, 25 Feb 1998 14:42:21 -0500 Received: from fault.rstcorp.com(206.29.49.18) by bigbrother.rstcorp.com via smap (V2.0) id xma024768; Wed, 25 Feb 98 14:41:53 -0500 Received: (from vshah@localhost) by rstcorp.com (8.8.1/8.8.1) id NAA05311; Wed, 25 Feb 1998 13:46:54 -0500 (EST) Date: Wed, 25 Feb 1998 13:46:54 -0500 (EST) Message-Id: <199802251846.NAA05311@rstcorp.com> From: "Viren R. Shah" To: freebsd-stable@FreeBSD.ORG Subject: 2.2.6 for NFS server 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 We just got a server in that will be acting as our main NFS server. We intend to run 2.2.x on it. Couple of questions: 1. Is 2.2.6 close enough that we should put off installing 2.2-STABLE for a few days? Or in other terms, are there enough stability improvements in 2.2.6 that we should definitely wait for it. 2. I've seen a few mentions of NFS problems on 2.2.5. Are there any big gotchas wrt using a 2.2.x box as an NFS server? Thanks Viren -- Viren R. Shah "Creeping featurism is a disease, fatal if not treated promptly" -- Don Norman in _The Design of Everyday Things_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 10:55:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18905 for freebsd-stable-outgoing; Wed, 25 Feb 1998 10:55:19 -0800 (PST) (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 KAA18879 for ; Wed, 25 Feb 1998 10:54:53 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #3) id 0y7lyd-0006dJ-00; Wed, 25 Feb 1998 10:54:43 -0800 Date: Wed, 25 Feb 1998 10:54:40 -0800 (PST) From: Tom To: "Viren R. Shah" cc: freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.6 for NFS server In-Reply-To: <199802251846.NAA05311@rstcorp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Wed, 25 Feb 1998, Viren R. Shah wrote: > > We just got a server in that will be acting as our main NFS server. We > intend to run 2.2.x on it. Couple of questions: > > 1. Is 2.2.6 close enough that we should put off installing 2.2-STABLE > for a few days? Or in other terms, are there enough stability > improvements in 2.2.6 that we should definitely wait for it. Probably best to install now, and begin testing. If you need 2.2.6, it is just a "make world" away. > 2. I've seen a few mentions of NFS problems on 2.2.5. Are there any > big gotchas wrt using a 2.2.x box as an NFS server? Most NFS comments have been about freebsd-current. Best thing is to test first. > Thanks > Viren > -- > Viren R. Shah > "Creeping featurism is a disease, fatal if not treated promptly" > -- Don Norman in _The Design of Everyday Things_ Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 12:52:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14246 for freebsd-stable-outgoing; Wed, 25 Feb 1998 12:52:12 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from geo.geocast.net (geo.geocast.net [128.177.240.120]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14150 for ; Wed, 25 Feb 1998 12:51:55 -0800 (PST) (envelope-from castor@geocast.net) Received: (from castor@localhost) by geo.geocast.net (8.8.8/8.8.8) id MAA11625 for freebsd-stable@freebsd.org; Wed, 25 Feb 1998 12:51:43 -0800 (PST) Date: Wed, 25 Feb 1998 12:51:43 -0800 (PST) From: Castor Fu Message-Id: <199802252051.MAA11625@geo.geocast.net> To: freebsd-stable@FreeBSD.ORG Subject: Re: NCR53c810 problems and FreeBSD2.2-STABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I have narrowed down the source of my problems with the NCR SCSI controller which I reported earlier with 2.2-STABLE Attempts to use the drive hang if the probe for the uha driver is enabled. The GENERIC kernel tries to find the uha controller at port 0x330. I believe that this port number is used by my Yamaha OPL-3 sound interface. However, the GENERIC kernel doesn't contain support for sound cards, and furthermore, it doesn't seem like the Ultrastor driver should stomp on the NCR one just from probing things. I'm happy because I'm up and running, but if someone wants to look further into this, I'd be happy to try other tests. -castor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 13:06:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17491 for freebsd-stable-outgoing; Wed, 25 Feb 1998 13:06:34 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from infowest.com (infowest.com [204.17.177.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17460 for ; Wed, 25 Feb 1998 13:06:20 -0800 (PST) (envelope-from agifford@infowest.com) Received: from infowest.com (dialup5-18.infowest.net [207.49.60.121]) by infowest.com (8.8.8/8.8.5) with ESMTP id OAA24657 for ; Wed, 25 Feb 1998 14:05:48 -0700 (MST) Message-ID: <34F48785.343D8C39@infowest.com> Date: Wed, 25 Feb 1998 21:05:09 +0000 From: "Aaron D. Gifford" X-Mailer: Mozilla 4.03 [en] (X11; U; FreeBSD 2.2.5-STABLE i386) MIME-Version: 1.0 To: stable@FreeBSD.ORG Subject: Re: BIND 8.* and STABLE References: <199802251353.IAA00561@pandora.hh.kew.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Drew Derbyshire wrote: > > Any reason I can't take the BIND port in the CURRENT ports collection > and install it on -STABLE? I know the thing builds, but that > doesn't say I won't cripple my system when the resolver library > gets replaced. > > I also notice the install seems dummied out in the BIND makefile, > any idea why? > > -ahd- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message I would LOVE to see BIND 8 make its way into -STABLE. That way I won't have to keep reinstalling BIND 8 after every "make world" overwrites it with the older version. :) Aaron out. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 13:21:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22462 for freebsd-stable-outgoing; Wed, 25 Feb 1998 13:21:29 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pandora.hh.kew.com (ahd@kendra.ne.mediaone.net [24.128.94.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22356 for ; Wed, 25 Feb 1998 13:20:55 -0800 (PST) (envelope-from ahd@pandora.hh.kew.com) Received: (from ahd@localhost) by pandora.hh.kew.com (8.8.5/8.8.5) id QAA01606; Wed, 25 Feb 1998 16:20:34 -0500 (EST) Date: Wed, 25 Feb 1998 16:20:34 -0500 (EST) From: Drew Derbyshire Message-Id: <199802252120.QAA01606@pandora.hh.kew.com> To: agifford@infowest.com, stable@FreeBSD.ORG Subject: Re: BIND 8.* and STABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > Date: Wed, 25 Feb 1998 21:05:09 +0000 > From: "Aaron D. Gifford" > I would LOVE to see BIND 8 make its way into -STABLE. That way I won't > have to keep reinstalling BIND 8 after every "make world" overwrites it > with the older version. :) Well, at least I can take that as 'it works'. :-) When I last saw the topic visited many months ago, one of the issues was the revamped boot file. Now, I didn't have a problem running the conversion utility, but some will. Since the current BIND works, I can see why many would prefer it be left the current STABLE resolver, and leave BIND 8.* for CURRENT. Aaron, you doing anything else besides simple reinstall? > Drew Derbyshire wrote: > > I also notice the install seems dummied out in the BIND makefile, > > any idea why? Any answer for this? -ahd- -- Drew Derbyshire Internet: ahd@kew.com Kendra Electronic Wonderworks Telephone: 781-279-9812 "I don't ask for much, I only want trust and you know it don't come easy . . ." - Ringo Starr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 13:21:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22540 for freebsd-stable-outgoing; Wed, 25 Feb 1998 13:21:56 -0800 (PST) (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 NAA22387 for ; Wed, 25 Feb 1998 13:21:01 -0800 (PST) (envelope-from hometeam@techpower.net) Received: from localhost (hometeam@localhost) by techpower.net (8.8.8/8.8.5) with SMTP id QAA20031; Wed, 25 Feb 1998 16:19:43 -0500 (EST) Date: Wed, 25 Feb 1998 16:19:43 -0500 (EST) From: Jt To: "Aaron D. Gifford" cc: stable@FreeBSD.ORG Subject: Re: BIND 8.* and STABLE In-Reply-To: <34F48785.343D8C39@infowest.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk You have my vote.... TJ hometeam@techpower.net --We cannot all be masters, nor all masters Cannot be truly follow'd-- -----BEGIN PGP MESSAGE----- Version: 2.6.2 owEBqwBU/4kAlQMFADRCxNWhsddKSTR+6QEBelED/jzeC3btZfqSdIfrNoCgwUJJ iNQ33UQoMyJ2ygkfl72xP5J79yml/F4P73GnNaDVbaMOmOG2NNAi5ElE73wRh54U 17kH+n5XnYeqekV8T2TG2Q6ex3UotXPyZ1vvrCrSxapOz6a4hh0GQeA55rcwLy2W ROHwxfvaVsrX5iVOkRoerBFiC21lc3NhZ2UudHh0AAAAAA== =jCvF -----END PGP MESSAGE----- On Wed, 25 Feb 1998, Aaron D. Gifford wrote: > Drew Derbyshire wrote: > > > > Any reason I can't take the BIND port in the CURRENT ports collection > > and install it on -STABLE? I know the thing builds, but that > > doesn't say I won't cripple my system when the resolver library > > gets replaced. > > > > I also notice the install seems dummied out in the BIND makefile, > > any idea why? > > > > -ahd- > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > I would LOVE to see BIND 8 make its way into -STABLE. That way I won't > have to keep reinstalling BIND 8 after every "make world" overwrites it > with the older version. :) > > Aaron out. > > 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 Feb 25 13:51:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02675 for freebsd-stable-outgoing; Wed, 25 Feb 1998 13:51:25 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from proxyb1.san.rr.com (proxyb1-atm.san.rr.com [204.210.0.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02613 for ; Wed, 25 Feb 1998 13:51:06 -0800 (PST) (envelope-from Studded@san.rr.com) Received: from san.rr.com (dt050ndd.san.rr.com [204.210.31.221]) by proxyb1.san.rr.com (8.8.7/8.8.8) with ESMTP id NAA19484; Wed, 25 Feb 1998 13:49:39 -0800 (PST) Message-ID: <34F491F1.18915C4D@san.rr.com> Date: Wed, 25 Feb 1998 13:49:37 -0800 From: Studded Organization: Triborough Bridge and Tunnel Authority X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-STABLE-0223 i386) MIME-Version: 1.0 To: Drew Derbyshire CC: stable@FreeBSD.ORG Subject: Re: BIND 8.* and STABLE References: <199802251353.IAA00561@pandora.hh.kew.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Drew Derbyshire wrote: > > Any reason I can't take the BIND port in the CURRENT ports collection > and install it on -STABLE? I know the thing builds, but that > doesn't say I won't cripple my system when the resolver library > gets replaced. The default for 8.1.1 install is to put the libs and such in /usr/local, and leave the resolver library you have in place intact. As far as I can see the patches just enforce this policy and make the appropriate changes for freebsd-style man pages. I run an 8.1.1 nameserver on a -Stable machine and haven't had a problem. > I also notice the install seems dummied out in the BIND makefile, > any idea why? I don't know what you mean here. Hope this helps, Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 5,328 clients and still growing. *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 14:18:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09732 for freebsd-stable-outgoing; Wed, 25 Feb 1998 14:18:36 -0800 (PST) (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 OAA09724 for ; Wed, 25 Feb 1998 14:18:25 -0800 (PST) (envelope-from jfieber@indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.7/8.8.7) with SMTP id RAA03529; Wed, 25 Feb 1998 17:17:55 -0500 (EST) Date: Wed, 25 Feb 1998 17:17:55 -0500 (EST) From: John Fieber To: "Viren R. Shah" cc: freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.6 for NFS server In-Reply-To: <199802251846.NAA05311@rstcorp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Wed, 25 Feb 1998, Viren R. Shah wrote: > 1. Is 2.2.6 close enough that we should put off installing 2.2-STABLE > for a few days? Or in other terms, are there enough stability > improvements in 2.2.6 that we should definitely wait for it. > > 2. I've seen a few mentions of NFS problems on 2.2.5. Are there any > big gotchas wrt using a 2.2.x box as an NFS server? Depends on your clients. For 2.2.5, I can confirm that Solaris and Digital Unix clients do NOT work using nfs v3. Digital Unix works fine if you specify v2 when mounting. Telling FreeBSD mountd to only accept v2 does not seem to allow mounts from Solaris clients using their automounter (I'm not the admin of the Solaris boxes in question so I can't do much more investigation.) In other words: Try it out. The most obvious symptom of the v3 problems with Solaris and Digital Unix are with large directories--listings will be incomplete. For example if you have 200 files in a directory, it may take three or four rm * commands to actually remove everything. I have not been paying much attention to the 2.2.5 to 2.2.6 changes. A fix for this v3 incompatibility would be most welcome (but far beyond my hacking skills). -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 14:53:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16147 for freebsd-stable-outgoing; Wed, 25 Feb 1998 14:53:53 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from as5200-port-254.no.neosoft.com (as5200-port-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16116 for ; Wed, 25 Feb 1998 14:53:21 -0800 (PST) (envelope-from conrads@as5200-port-254.no.neosoft.com) Received: (from conrads@localhost) by as5200-port-254.no.neosoft.com (8.8.8/8.8.5) id QAA13828; Wed, 25 Feb 1998 16:51:20 GMT Date: Wed, 25 Feb 1998 16:51:20 GMT From: Conrad Sabatier Message-Id: <199802251651.QAA13828@as5200-port-254.no.neosoft.com> To: stable@FreeBSD.ORG X-Also-Posted-To: comp.unix.bsd.freebsd.misc Subject: Kudos on stable make world (2/24/98) Reply-To: conrads@neosoft.com Organization: NeoSoft, Inc. X-Newsreader: trn 4.0-test60 (5 October 1997) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Hadn't done this in a while (a wee bit leery due to some occasional problems in the past), but yesterday I cvsupped my stable sources and did a make world. Everything ran flawlessly to completion. Just thought the developers deserved a bit of applause for a fine piece of work (clap-clap). :-) A confirmed FreeBSD addict -- Conrad Sabatier | FreeBSD -- UNIX for your PC | Why settle for less than the best? http://www.neosoft.com/~conrads | http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 15:04:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18899 for freebsd-stable-outgoing; Wed, 25 Feb 1998 15:04:06 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from prefetch.san.rr.com (ns1.san.rr.com [204.210.0.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18845 for ; Wed, 25 Feb 1998 15:03:52 -0800 (PST) (envelope-from Studded@san.rr.com) Received: from san.rr.com (dt050ndd.san.rr.com [204.210.31.221]) by prefetch.san.rr.com (8.8.7/8.8.8) with ESMTP id PAA01789; Wed, 25 Feb 1998 15:02:45 -0800 (PST) Message-ID: <34F4A312.9BE41FC4@san.rr.com> Date: Wed, 25 Feb 1998 15:02:42 -0800 From: Studded Organization: Triborough Bridge and Tunnel Authority X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-STABLE-0223 i386) MIME-Version: 1.0 To: "Aaron D. Gifford" CC: stable@FreeBSD.ORG Subject: Re: BIND 8.* and STABLE References: <199802251353.IAA00561@pandora.hh.kew.com> <34F48785.343D8C39@infowest.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Aaron D. Gifford wrote: > I would LOVE to see BIND 8 make its way into -STABLE. That way I won't > have to keep reinstalling BIND 8 after every "make world" overwrites it > with the older version. :) BIND 8 is not ready for -Stable. The BIND people will tell you that. You can avoid rebuilding named by editing /usr/src/usr.sbin/Makefile. If you rebuild often, try copying Makefile to makefile and editing makefile. It will supersede the Makefile in the same directory. I use this technique often to avoid building various aspects of the tree. FWIW, I would really like to see this as a /usr/src/Makefile option. The problem being which elements of BIND do you not rebuild? You want the 4.9.6 resolver libraries and includes, even if you build and use the 8.1.1 stuff for certain applications (you have to link it specifically, it's not included in anything otherwise). The binaries like dig, nslookup, etc. should be exempted with a -DNOBIND option, however in the end it's easier to just rebuild 8.1.1, especially now that there is a port. Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 5,328 clients and still growing. *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 15:27:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23837 for freebsd-stable-outgoing; Wed, 25 Feb 1998 15:27:13 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from xmission.xmission.com (softweyr@xmission.xmission.com [198.60.22.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23700 for ; Wed, 25 Feb 1998 15:26:59 -0800 (PST) (envelope-from softweyr@xmission.xmission.com) Received: (from softweyr@localhost) by xmission.xmission.com (8.8.7/8.7.5) id QAA17514; Wed, 25 Feb 1998 16:26:43 -0700 (MST) From: Wes Peters - Softweyr LLC Message-Id: <199802252326.QAA17514@xmission.xmission.com> Subject: Re: 2.2.6 for NFS server To: jfieber@indiana.edu (John Fieber) Date: Wed, 25 Feb 1998 16:26:42 -0700 (MST) Cc: stable@FreeBSD.ORG In-Reply-To: from "John Fieber" at Feb 25, 98 05:17:55 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > Depends on your clients. For 2.2.5, I can confirm that Solaris > and Digital Unix clients do NOT work using nfs v3. Digital Unix > works fine if you specify v2 when mounting. Telling FreeBSD > mountd to only accept v2 does not seem to allow mounts from > Solaris clients using their automounter (I'm not the admin of the > Solaris boxes in question so I can't do much more investigation.) You can probably take care of this problem for the Solaris clients by specifying vers=2 in the mount options. > In other words: Try it out. Always a good suggestion. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.xmission.com/~softweyr softweyr@xmission.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 16:27:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07661 for freebsd-stable-outgoing; Wed, 25 Feb 1998 16:27:51 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from netcom1.netcom.com (mvh@netcom20.netcom.com [192.100.81.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07604 for ; Wed, 25 Feb 1998 16:27:32 -0800 (PST) (envelope-from mvh@netcom.com) Received: (from mvh@localhost) by netcom1.netcom.com (8.8.8/8.8.8) id QAA02724; Wed, 25 Feb 1998 16:27:24 -0800 (PST) (envelope-from mvh) Date: Wed, 25 Feb 1998 16:27:24 -0800 (PST) Message-Id: <199802260027.QAA02724@netcom1.netcom.com> From: "Michael V. Harding" To: freebsd-stable@FreeBSD.ORG Subject: A 'make world' suggestion... Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk The following occurred to me while after doing a 'make -DNOCLEAN buildworld' on a populated /usr/obj with only one file change: for my system, (K6 200, IDE) the timing goes as follows for a 'make buildworld': 1. ~2.5 hrs: a regular 'make buildworld' 2. ~1.5 hrs: 'make -DNOCLEAN buildworld' with an empty /usr/src/obj tree, including (parallel) removal of the old /usr/src/obj data. 3. ~1.0 hrs: 'make buildworld' with a populated /usr/src/obj Option 2 is all I use - it saves an hour and does a complete build. Option 3 is 'risky' and not worth the extra half hour. Option 1 provides no benefit over option 2. Could we codify option 2 with a -DQUICKCLEAN flag or something, where the steps I do by hand are incorporated into the makefile? The only difference would be that a 'rm -rf /usr/src' would get done at the beginning, and the rest would work like a -DNOCLEAN. Also, could the following line be done at the END of installworld, or of buildworld, so that it's possible to remove the object tree with a simple 'rm -rf /usr/src/obj/*' ? chflags -R noschg ${WORLDTMP}/ The flags could be set in 'installworld' rather than 'buildworld', and reset after the install... Thanks, Mike Harding To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 16:33:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA08639 for freebsd-stable-outgoing; Wed, 25 Feb 1998 16:33:02 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from netcom1.netcom.com (mvh@netcom20.netcom.com [192.100.81.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA08588 for ; Wed, 25 Feb 1998 16:32:44 -0800 (PST) (envelope-from mvh@netcom.com) Received: (from mvh@localhost) by netcom1.netcom.com (8.8.8/8.8.8) id QAA02852; Wed, 25 Feb 1998 16:32:14 -0800 (PST) (envelope-from mvh) Date: Wed, 25 Feb 1998 16:32:14 -0800 (PST) Message-Id: <199802260032.QAA02852@netcom1.netcom.com> From: "Michael V. Harding" To: agifford@infowest.com CC: stable@FreeBSD.ORG In-reply-to: <34F48785.343D8C39@infowest.com> (agifford@infowest.com) Subject: Re: BIND 8.* and STABLE References: <199802251353.IAA00561@pandora.hh.kew.com> <34F48785.343D8C39@infowest.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Bind 8 has some significant advantages as well, and some neat configuration options that don't exist on 4.9.6, like being able to use access control. No new code changes are going into 4.9.x - why not make the leap? The data files can be the same, and there is a conversion script for the configuration file. Date: Wed, 25 Feb 1998 21:05:09 +0000 From: "Aaron D. Gifford" Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG X-UIDL: 8ef23f6953a1a5540657c5855804ae8b Drew Derbyshire wrote: > > Any reason I can't take the BIND port in the CURRENT ports collection > and install it on -STABLE? I know the thing builds, but that > doesn't say I won't cripple my system when the resolver library > gets replaced. > > I also notice the install seems dummied out in the BIND makefile, > any idea why? > > -ahd- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message I would LOVE to see BIND 8 make its way into -STABLE. That way I won't have to keep reinstalling BIND 8 after every "make world" overwrites it with the older version. :) Aaron out. 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 Feb 25 16:52:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14061 for freebsd-stable-outgoing; Wed, 25 Feb 1998 16:52:31 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail-relay1.yahoo.com (mail-relay1.yahoo.com [206.251.17.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13976 for ; Wed, 25 Feb 1998 16:52:00 -0800 (PST) (envelope-from serge@yahoo-inc.com) Received: from borogove.yahoo.com (borogove.yahoo.com [205.216.162.65]) by mail-relay1.yahoo.com (8.8.7/8.8.8) with ESMTP id QAA04676; Wed, 25 Feb 1998 16:51:49 -0800 (PST) Received: from serge.yahoo.com (serge.yahoo.com [205.216.162.201]) by borogove.yahoo.com (8.8.7/8.8.8) with SMTP id QAA27150; Wed, 25 Feb 1998 16:51:15 -0800 (PST) Date: Wed, 25 Feb 1998 16:51:22 -0800 (PST) From: Sergiy Zhuk X-Sender: serge@serge.yahoo.com To: "Michael V. Harding" cc: agifford@infowest.com, stable@FreeBSD.ORG Subject: Re: BIND 8.* and STABLE In-Reply-To: <199802260032.QAA02852@netcom1.netcom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk hi On Wed, 25 Feb 1998, Michael V. Harding wrote: > Bind 8 has some significant advantages as well, and some neat > configuration options that don't exist on 4.9.6, like being able to > use access control. No new code changes are going into 4.9.x - why 4.9.6 has access control, althought the syntax is different: 8.1: allow-transfer {/;} 4.9: xfrnets & anyway, 8.1 *is* better... -- rgds, serge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 17:12:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17608 for freebsd-stable-outgoing; Wed, 25 Feb 1998 17:12:39 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from firewall.scitec.com.au (firewall-user@fgate.scitec.com.au [203.17.180.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17569 for ; Wed, 25 Feb 1998 17:12:03 -0800 (PST) (envelope-from john.saunders@scitec.com.au) Received: by firewall.scitec.com.au; id MAA10824; Thu, 26 Feb 1998 12:11:58 +1100 (EST) Received: from mailhub.scitec.com.au(203.17.180.131) by fgate.scitec.com.au via smap (3.2) id xma010817; Thu, 26 Feb 98 12:11:35 +1100 Received: from hydra.scitec.com.au (hydra.scitec.com.au [203.17.182.101]) by mailhub.scitec.com.au (8.6.12/8.6.9) with ESMTP id MAA13187 for ; Thu, 26 Feb 1998 12:11:34 +1100 Received: from scitec.com.au (saruman.scitec.com.au) by hydra.scitec.com.au with ESMTP (1.40.112.8/16.2) id AA205045493; Thu, 26 Feb 1998 12:11:33 +1100 Message-Id: <34F4C11D.DD3E9820@scitec.com.au> Date: Thu, 26 Feb 1998 12:10:53 +1100 From: John Saunders Organization: SCITEC LIMITED X-Mailer: Mozilla 4.04 [en] (WinNT; I) Mime-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Re: stable branch funnies Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk John Saunders wrote: > I then tried a build which failed due to a problem in libg++. After several more attempts at building, all resulting in failed compiles of ACG.cc in libg++, I blew away my cvsup'ed source and re-installed 2.2.5-RELEASE from CD. Then I found out that the source that built 1 week ago (I have the timestamps to prove it) doesn't build anymore! Still failing in ACG.cc (although when building that file by had it compiles). The build fails reminded me of problem in Linux with signal 11 caused by bad memory/cache/mb. So i pulled out my memory, cleaned the edge connectors with alcohol, and plugged 'em back in. Result, sucessfull build! I cvsup'ed -stable and got a perfect build again! The only thing that has happened to the system between then and now is I took it to a friends place (by car) to play network games. So I think this has disturbed the SIMM connectors somehow. So sorry for wasting peoples time with this. And congrats to core on providing a good OS that really builds perfectly! :^) P.S. Something to consider, a "make diff" in the etc directory would be cool to check out what has changed. I knocked up a little script to generate a diff of all files so I could merge in changes. With Squid I have the following proceedure on upgrades... 1) diff squid.config.default squid.config >local.diff 2) build + install squid 3) cp squid.config.default squid.config 4) patch -s -p0 Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22893 for freebsd-stable-outgoing; Wed, 25 Feb 1998 17:42:50 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pandora.hh.kew.com (ahd@kendra.ne.mediaone.net [24.128.94.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22874 for ; Wed, 25 Feb 1998 17:42:38 -0800 (PST) (envelope-from ahd@pandora.hh.kew.com) Received: (from ahd@localhost) by pandora.hh.kew.com (8.8.5/8.8.5) id UAA02378; Wed, 25 Feb 1998 20:42:28 -0500 (EST) Date: Wed, 25 Feb 1998 20:42:28 -0500 (EST) From: Drew Derbyshire Message-Id: <199802260142.UAA02378@pandora.hh.kew.com> To: mvh@netcom.com, serge@yahoo-inc.com Subject: Re: BIND 8.* and STABLE Cc: agifford@infowest.com, stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I never was able to get xfernets to work, I dunno why ... > From owner-freebsd-stable@freebsd.org Wed Feb 25 20:22:41 1998 > Date: Wed, 25 Feb 1998 16:51:22 -0800 (PST) > From: Sergiy Zhuk > To: "Michael V. Harding" > cc: agifford@infowest.com, stable@freebsd.org > Subject: Re: BIND 8.* and STABLE > > hi > > On Wed, 25 Feb 1998, Michael V. Harding wrote: > > > Bind 8 has some significant advantages as well, and some neat > > configuration options that don't exist on 4.9.6, like being able to > > use access control. No new code changes are going into 4.9.x - why > > 4.9.6 has access control, althought the syntax is different: > > 8.1: allow-transfer {/;} > 4.9: xfrnets & > > anyway, 8.1 *is* better... > > -- > rgds, > serge > > > 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 Feb 25 18:04:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27067 for freebsd-stable-outgoing; Wed, 25 Feb 1998 18:04:51 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail-relay1.yahoo.com (mail-relay1.yahoo.com [206.251.17.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27044 for ; Wed, 25 Feb 1998 18:04:25 -0800 (PST) (envelope-from serge@yahoo-inc.com) Received: from borogove.yahoo.com (borogove.yahoo.com [205.216.162.65]) by mail-relay1.yahoo.com (8.8.7/8.8.8) with ESMTP id SAA13921; Wed, 25 Feb 1998 18:04:19 -0800 (PST) Received: from serge.yahoo.com (serge.yahoo.com [205.216.162.201]) by borogove.yahoo.com (8.8.7/8.8.8) with SMTP id SAA02441; Wed, 25 Feb 1998 18:03:48 -0800 (PST) Date: Wed, 25 Feb 1998 18:03:56 -0800 (PST) From: Sergiy Zhuk X-Sender: serge@serge.yahoo.com To: Drew Derbyshire cc: stable@FreeBSD.ORG Subject: Re: BIND 8.* and STABLE In-Reply-To: <199802260142.UAA02378@pandora.hh.kew.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk hi On Wed, 25 Feb 1998, Drew Derbyshire wrote: > I never was able to get xfernets to work, I dunno why ... works fine for me... you've probably misconfigured named or compiled it wrong, read the sources -- rgds, serge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 20:06:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA26175 for freebsd-stable-outgoing; Wed, 25 Feb 1998 20:06:00 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from as5200-port-254.no.neosoft.com (as5200-port-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA25899 for ; Wed, 25 Feb 1998 20:05:23 -0800 (PST) (envelope-from conrads@as5200-port-254.no.neosoft.com) Received: (from conrads@localhost) by as5200-port-254.no.neosoft.com (8.8.8/8.8.5) id WAA26929; Wed, 25 Feb 1998 22:03:22 GMT Date: Wed, 25 Feb 1998 22:03:22 GMT From: Conrad Sabatier Message-Id: <199802252203.WAA26929@as5200-port-254.no.neosoft.com> To: stable@FreeBSD.ORG X-Also-Posted-To: comp.unix.bsd.freebsd.misc References: <6d1i69$dgq$1@dolphin.neosoft.com> <34F4A7BD.4A7B7C1D@FreeBSD.org> Reply-To: conrads@neosoft.com Organization: NeoSoft, Inc. Subject: Re: Kudos on stable make world (2/24/98) X-Newsreader: trn 4.0-test60 (5 October 1997) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk In article <34F4A7BD.4A7B7C1D@FreeBSD.org>, Jordan K. Hubbard wrote: >Conrad Sabatier wrote: >> >> Hadn't done this in a while (a wee bit leery due to some occasional >> problems in the past), but yesterday I cvsupped my stable sources >> and did a make world. Everything ran flawlessly to completion. Just >> thought the developers deserved a bit of applause for a fine piece of >> work (clap-clap). :-) > >Thanks! People generally only tell us when things break. :) Most welcome. Seriously, I am continuously in awe of what the FreeBSD development team has succeeded in accomplishing: taking the "raw" BSD sources and turning them into a not only eminently viable, but downright *desirable* operating system for the PC platform, whilst all the while maintaining the "open" (or "freeware", if you will) philosophy as well, not to mention keeping abreast of the latest hardware/security/etc. Thou art truly the most noble of gentlemen! :-) -- Conrad Sabatier | FreeBSD -- UNIX for your PC | Why settle for less than the best? http://www.neosoft.com/~conrads | http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 25 22:48:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02291 for freebsd-stable-outgoing; Wed, 25 Feb 1998 22:48:38 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from xpert.com (xpert.com [199.203.132.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02275 for ; Wed, 25 Feb 1998 22:48:29 -0800 (PST) (envelope-from yuri@xpert.com) Received: from localhost (yuri@localhost) by xpert.com (8.8.5/8.8.5) with SMTP id IAA30757; Thu, 26 Feb 1998 08:48:14 +0200 Date: Thu, 26 Feb 1998 08:48:14 +0200 (IST) From: Yuri Gindin To: John Fieber cc: "Viren R. Shah" , freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.6 for NFS server In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Wed, 25 Feb 1998, John Fieber wrote: John, > Depends on your clients. For 2.2.5, I can confirm that Solaris > and Digital Unix clients do NOT work using nfs v3. Digital Unix > works fine if you specify v2 when mounting. Telling FreeBSD > mountd to only accept v2 does not seem to allow mounts from > Solaris clients using their automounter (I'm not the admin of the > Solaris boxes in question so I can't do much more investigation.) > Don't know about Dunix but solaris-2.6 works. I had some problems with programs requiring locks, such as top, lsof, netscape but after I started rpc.lockd on FreeBSD everything went fine even with NFSv3. > > The most obvious symptom of the v3 problems with Solaris and > Digital Unix are with large directories--listings will be > incomplete. For example if you have 200 files in a directory, it > may take three or four rm * commands to actually remove > everything. Just checked this and everything worked fine. I'm on 2.2.5-stable. --Yuri Gindin Xpert UNIX Systems Ltd. Work phone: +972-3-6181118 Mobile phone: +972-50-982113 Home phone: +972-3-6735883 PGP Key fingerprint = 5D 56 0B 88 F1 51 4B F7 52 FE 62 28 76 0A 18 77 PGP public key available via http://pgp5.ai.mit.edu/pks-commands.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 26 02:57:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA29098 for freebsd-stable-outgoing; Thu, 26 Feb 1998 02:57:18 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from helix.mdy.univie.ac.at (helix.mdy.univie.ac.at [131.130.40.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA29088 for ; Thu, 26 Feb 1998 02:57:12 -0800 (PST) (envelope-from stefan@mdy.univie.ac.at) Received: from alpha.mdy.univie.ac.at (alpha.mdy.univie.ac.at [131.130.40.3]) by helix.mdy.univie.ac.at (8.8.8/8.8.8) with ESMTP id LAA22728 for ; Thu, 26 Feb 1998 11:57:06 +0100 (MET) From: Stefan Boresch Received: (from stefan@localhost) by alpha.mdy.univie.ac.at (8.8.8/8.8.8) id MAA11236 for freebsd-stable@freebsd.org; Thu, 26 Feb 1998 12:00:31 +0100 (MEZ) Message-Id: <199802261100.MAA11236@alpha.mdy.univie.ac.at> Subject: Re: 2.2.6 for NFS server To: freebsd-stable@FreeBSD.ORG Date: Thu, 26 Feb 98 12:00:30 MEZ Reply-To: stefan@mdy.univie.ac.at Mailer: Elm [revision: 70.85] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Hmh, with regard to 2.2-stable as an NFS-server: I have encountered severe performance problems between IRIX 5.3 (and 6.1) as clients and a 2.2.5 box as server (last made world made around the end of January). When I simply mount from the IRIX boxes, files get truncated. One can avoid that by specifying a block-size for read/write of 1024 when mounting. However, then the performance is lousy 20k/sec. (Compare this to the reversed roles, FreeBSD as the client, IRIX as the server, where I see 1MB/sec!) I have posted this previously, but got no reply. (I believe the issue mentioned for Digital UNIX and Solaris is in the official bug-database). Just in case anyone is interested: This is a typical error message from the IRIX side (6.1) when files get truncated during an NFS write Dec 15 16:03:05 2A:octopus unix: NFS write error 5 on host server1 Dec 15 16:03:07 2A:octopus unix: xdr_bytes: bad size FAILED Dec 15 16:03:07 2A:octopus unix: NFS2 write failed for server server1: Can't encode arguments No apparent error messages on the FreeBSD side. Helpful hints are certainly appreciated! Stefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 26 05:09:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA14737 for freebsd-stable-outgoing; Thu, 26 Feb 1998 05:09:54 -0800 (PST) (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 FAA14712 for ; Thu, 26 Feb 1998 05:09:51 -0800 (PST) (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.6.9) with ESMTP id FAA24555; Thu, 26 Feb 1998 05:09:32 -0800 (PST) To: stefan@mdy.univie.ac.at cc: freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.6 for NFS server In-reply-to: Your message of "Thu, 26 Feb 1998 12:00:30 EST." <199802261100.MAA11236@alpha.mdy.univie.ac.at> Date: Thu, 26 Feb 1998 05:09:32 -0800 Message-ID: <24551.888498572@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > I have posted this previously, but got no reply. (I believe > the issue mentioned for Digital UNIX and Solaris is in the > official bug-database). Just in case anyone is interested: > This is a typical error message from the IRIX side (6.1) when > files get truncated during an NFS write And can you tell us whether this is with NFS v3 or v2? I know that there are some serious problems with v3 at the moment and it should probably not be used in heterogenous NFS environments. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 26 05:21:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17115 for freebsd-stable-outgoing; Thu, 26 Feb 1998 05:21:05 -0800 (PST) (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 FAA17108 for ; Thu, 26 Feb 1998 05:21:01 -0800 (PST) (envelope-from jfieber@indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.7/8.8.7) with SMTP id IAA05765; Thu, 26 Feb 1998 08:20:37 -0500 (EST) Date: Thu, 26 Feb 1998 08:20:37 -0500 (EST) From: John Fieber To: Yuri Gindin cc: "Viren R. Shah" , freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.6 for NFS server In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Thu, 26 Feb 1998, Yuri Gindin wrote: > On Wed, 25 Feb 1998, John Fieber wrote: > > Depends on your clients. For 2.2.5, I can confirm that Solaris > > and Digital Unix clients do NOT work using nfs v3. Digital Unix > > works fine if you specify v2 when mounting. Telling FreeBSD > > mountd to only accept v2 does not seem to allow mounts from > > Solaris clients using their automounter (I'm not the admin of the > > Solaris boxes in question so I can't do much more investigation.) > > > Don't know about Dunix but solaris-2.6 works. ...version check...The solaris boxes I have trouble with are 2.5.1. The DEC boxes with trouble report "OSF1 zinc V4.0 564 alpha". -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 26 05:38:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19444 for freebsd-stable-outgoing; Thu, 26 Feb 1998 05:38:20 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA19342 for ; Thu, 26 Feb 1998 05:37:11 -0800 (PST) (envelope-from werner@btp1da.phy.uni-bayreuth.de) Received: (from werner@localhost) by btp1da.phy.uni-bayreuth.de (8.8.8/8.7.3) id OAA00420; Thu, 26 Feb 1998 14:36:41 +0100 (MET) Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 26 Feb 1998 14:36:41 +0100 (MET) Organization: university of bayreuth From: Werner Griessl To: John Fieber Subject: Re: 2.2.6 for NFS server Cc: freebsd-stable@FreeBSD.ORG, "Viren R. Shah" , Yuri Gindin Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On 26-Feb-98 John Fieber wrote: > On Thu, 26 Feb 1998, Yuri Gindin wrote: > >> On Wed, 25 Feb 1998, John Fieber wrote: >> > Depends on your clients. For 2.2.5, I can confirm that Solaris >> > and Digital Unix clients do NOT work using nfs v3. Digital Unix >> > works fine if you specify v2 when mounting. Telling FreeBSD >> > mountd to only accept v2 does not seem to allow mounts from >> > Solaris clients using their automounter (I'm not the admin of the >> > Solaris boxes in question so I can't do much more investigation.) >> > >> Don't know about Dunix but solaris-2.6 works. > > ...version check...The solaris boxes I have trouble with are > 2.5.1. The DEC boxes with trouble report "OSF1 zinc V4.0 564 > alpha". > > -john > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message ---------------------------------- E-Mail: Werner Griessl Date: 26-Feb-98 Time: 14:33:49 This message was sent by XFMail ---------------------------------- Have no problem here with "OSF1 V4.0 564.32 alpha" and nfs v2, but nfs v3 is not stable ! Werner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 26 06:14:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22901 for freebsd-stable-outgoing; Thu, 26 Feb 1998 06:14:08 -0800 (PST) (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 GAA22852 for ; Thu, 26 Feb 1998 06:13:22 -0800 (PST) (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.7/8.8.6) with ESMTP id PAA15326; Thu, 26 Feb 1998 15:12:03 +0100 (CET) Received: (from tg@localhost) by ghpc6.ihf.rwth-aachen.de (8.8.8/8.8.5) id PAA01742; Thu, 26 Feb 1998 15:12:02 +0100 (CET) To: John Fieber Cc: Yuri Gindin , "Viren R. Shah" , freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.6 for NFS server References: From: Thomas Gellekum Date: 26 Feb 1998 15:12:01 +0100 In-Reply-To: John Fieber's message of Thu, 26 Feb 1998 08:20:37 -0500 (EST) Message-ID: <87pvka4fri.fsf@ghpc6.ihf.rwth-aachen.de> Lines: 37 X-Mailer: Gnus v5.4.37/XEmacs 19.16 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk John Fieber writes: > On Thu, 26 Feb 1998, Yuri Gindin wrote: > > > On Wed, 25 Feb 1998, John Fieber wrote: > > > Depends on your clients. For 2.2.5, I can confirm that Solaris > > > and Digital Unix clients do NOT work using nfs v3. Digital Unix > > > works fine if you specify v2 when mounting. Telling FreeBSD > > > mountd to only accept v2 does not seem to allow mounts from > > > Solaris clients using their automounter (I'm not the admin of the > > > Solaris boxes in question so I can't do much more investigation.) > > > > > Don't know about Dunix but solaris-2.6 works. > > ...version check...The solaris boxes I have trouble with are > 2.5.1. The DEC boxes with trouble report "OSF1 zinc V4.0 564 > alpha". I never investigated further because it didn't bother me, but when I read this thread... ;-) Sample output (client FreeBSD-2.2.5-stable, server Solaris-2.5.1): root:129# mount bert:/claudia /mnt nfs: can't access /claudia: Permission denied root:130# mount -o -2 bert:/claudia /mnt nfs: can't access /claudia: Permission denied root:131# mount -o -3 bert:/claudia /mnt nfs: can't access /claudia: Permission denied root:132# mount -o resvport bert:/claudia /mnt nfs: can't access /claudia: Permission denied root:133# mount -o resvport,nfsv2 bert:/claudia /mnt nfs: can't access /claudia: Permission denied No obvious jokes here, please; I didn't choose the names. ;-) tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 26 06:30:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24741 for freebsd-stable-outgoing; Thu, 26 Feb 1998 06:30:02 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA24681 for ; Thu, 26 Feb 1998 06:29:57 -0800 (PST) (envelope-from werner@btp1da.phy.uni-bayreuth.de) Received: (from werner@localhost) by btp1da.phy.uni-bayreuth.de (8.8.8/8.7.3) id PAA06191; Thu, 26 Feb 1998 15:29:06 +0100 (MET) Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <87pvka4fri.fsf@ghpc6.ihf.rwth-aachen.de> Date: Thu, 26 Feb 1998 15:29:05 +0100 (MET) Organization: university of bayreuth From: Werner Griessl To: Thomas Gellekum Subject: Re: 2.2.6 for NFS server Cc: freebsd-stable@FreeBSD.ORG, "Viren R. Shah" , Yuri Gindin , John Fieber Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On 26-Feb-98 Thomas Gellekum wrote: > John Fieber writes: > >> On Thu, 26 Feb 1998, Yuri Gindin wrote: >> >> > On Wed, 25 Feb 1998, John Fieber wrote: >> > > Depends on your clients. For 2.2.5, I can confirm that Solaris >> > > and Digital Unix clients do NOT work using nfs v3. Digital Unix >> > > works fine if you specify v2 when mounting. Telling FreeBSD >> > > mountd to only accept v2 does not seem to allow mounts from >> > > Solaris clients using their automounter (I'm not the admin of the >> > > Solaris boxes in question so I can't do much more investigation.) >> > > >> > Don't know about Dunix but solaris-2.6 works. >> >> ...version check...The solaris boxes I have trouble with are >> 2.5.1. The DEC boxes with trouble report "OSF1 zinc V4.0 564 >> alpha". > > I never investigated further because it didn't bother me, but when I > read this thread... ;-) > > Sample output (client FreeBSD-2.2.5-stable, server Solaris-2.5.1): > > root:129# mount bert:/claudia /mnt > nfs: can't access /claudia: Permission denied > root:130# mount -o -2 bert:/claudia /mnt > nfs: can't access /claudia: Permission denied > root:131# mount -o -3 bert:/claudia /mnt > nfs: can't access /claudia: Permission denied > root:132# mount -o resvport bert:/claudia /mnt > nfs: can't access /claudia: Permission denied > root:133# mount -o resvport,nfsv2 bert:/claudia /mnt > nfs: can't access /claudia: Permission denied > > No obvious jokes here, please; I didn't choose the names. ;-) > > tg > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message ---------------------------------- E-Mail: Werner Griessl Date: 26-Feb-98 Time: 15:27:50 This message was sent by XFMail ---------------------------------- Are you sure, that the client is in the exports-file of the server ? Werner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 26 06:43:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA27772 for freebsd-stable-outgoing; Thu, 26 Feb 1998 06:43:39 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from bigbrother (bigbrother.rstcorp.com [206.29.49.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA27759 for ; Thu, 26 Feb 1998 06:43:26 -0800 (PST) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by bigbrother (8.6.12/8.6.9) id KAA31328; Thu, 26 Feb 1998 10:36:18 -0500 Received: from fault.rstcorp.com(206.29.49.18) by bigbrother.rstcorp.com via smap (V2.0) id xma031325; Thu, 26 Feb 98 10:35:31 -0500 Received: (from vshah@localhost) by rstcorp.com (8.8.1/8.8.1) id JAA06335; Thu, 26 Feb 1998 09:40:27 -0500 (EST) Date: Thu, 26 Feb 1998 09:40:27 -0500 (EST) Message-Id: <199802261440.JAA06335@rstcorp.com> From: "Viren R. Shah" To: Wes Peters - Softweyr LLC Cc: stable@FreeBSD.ORG Subject: Re: 2.2.6 for NFS server In-Reply-To: <199802252326.QAA17514@xmission.xmission.com> References: <199802252326.QAA17514@xmission.xmission.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 >>>>> "Wes" == Wes Peters <- Softweyr LLC > writes: >> Depends on your clients. For 2.2.5, I can confirm that Solaris >> and Digital Unix clients do NOT work using nfs v3. Digital Unix >> works fine if you specify v2 when mounting. Telling FreeBSD >> mountd to only accept v2 does not seem to allow mounts from >> Solaris clients using their automounter (I'm not the admin of the >> Solaris boxes in question so I can't do much more investigation.) Wes> You can probably take care of this problem for the Solaris clients Wes> by specifying vers=2 in the mount options. So, from all the feedback I've been getting, it seems that the best approach is to make sure that the FreeBSD server uses only NFS version 2. And for solaris clients, make sure they try to mount with "vers=2". Any other gotchas? Anyone know whether -current is better with NFS? (I realize that this is the wrong list). Especially considering that we have every major UNIX represented here as a NFS client? Thanks for all the feedback. Any other suggestions? I'll report back on how -stable worked as a NFS server with the other unices. Wes> Wes Peters Thanks Viren -- Viren R. Shah, {viren@rstcorp.com} "You are about as sharp as a sack of wet mice" -- Foghorn Leghorn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 26 07:03:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA00340 for freebsd-stable-outgoing; Thu, 26 Feb 1998 07:03:03 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from netcom1.netcom.com (mvh@netcom6.netcom.com [192.100.81.114]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA00332 for ; Thu, 26 Feb 1998 07:02:58 -0800 (PST) (envelope-from mvh@netcom.com) Received: (from mvh@localhost) by netcom1.netcom.com (8.8.8/8.8.8) id HAA00344; Thu, 26 Feb 1998 07:02:47 -0800 (PST) (envelope-from mvh) Date: Thu, 26 Feb 1998 07:02:47 -0800 (PST) Message-Id: <199802261502.HAA00344@netcom1.netcom.com> From: "Michael V. Harding" To: mvh@netcom.com CC: freebsd-stable@FreeBSD.ORG In-reply-to: <199802260027.QAA02724@netcom1.netcom.com> (mvh@netcom.com) Subject: Re: A 'make world' suggestion... References: <199802260027.QAA02724@netcom1.netcom.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Whoops! Of course I meant 'rm -rf /usr/obj' below... -- mvh Date: Wed, 25 Feb 1998 16:27:24 -0800 (PST) From: "Michael V. Harding" Sender: owner-freebsd-stable@FreeBSD.ORG X-UIDL: 6ce24729da61409608f3ef9f9d9f8cfb The following occurred to me while after doing a 'make -DNOCLEAN buildworld' on a populated /usr/obj with only one file change: for my system, (K6 200, IDE) the timing goes as follows for a 'make buildworld': 1. ~2.5 hrs: a regular 'make buildworld' 2. ~1.5 hrs: 'make -DNOCLEAN buildworld' with an empty /usr/src/obj tree, including (parallel) removal of the old /usr/src/obj data. 3. ~1.0 hrs: 'make buildworld' with a populated /usr/src/obj Option 2 is all I use - it saves an hour and does a complete build. Option 3 is 'risky' and not worth the extra half hour. Option 1 provides no benefit over option 2. Could we codify option 2 with a -DQUICKCLEAN flag or something, where the steps I do by hand are incorporated into the makefile? The only difference would be that a 'rm -rf /usr/src' would get done at the beginning, and the rest would work like a -DNOCLEAN. Also, could the following line be done at the END of installworld, or of buildworld, so that it's possible to remove the object tree with a simple 'rm -rf /usr/src/obj/*' ? chflags -R noschg ${WORLDTMP}/ The flags could be set in 'installworld' rather than 'buildworld', and reset after the install... Thanks, Mike Harding 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 Feb 26 07:19:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02758 for freebsd-stable-outgoing; Thu, 26 Feb 1998 07:19:41 -0800 (PST) (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 HAA02598 for ; Thu, 26 Feb 1998 07:19:22 -0800 (PST) (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.7/8.8.6) with ESMTP id QAA15430; Thu, 26 Feb 1998 16:19:01 +0100 (CET) Received: (from tg@localhost) by ghpc6.ihf.rwth-aachen.de (8.8.8/8.8.5) id QAA02605; Thu, 26 Feb 1998 16:19:00 +0100 (CET) To: Werner Griessl Cc: freebsd-stable@FreeBSD.ORG, "Viren R. Shah" , Yuri Gindin , John Fieber Subject: Re: 2.2.6 for NFS server References: From: Thomas Gellekum Date: 26 Feb 1998 16:18:59 +0100 In-Reply-To: Werner Griessl's message of Thu, 26 Feb 1998 15:29:05 +0100 (MET) Message-ID: <87ogzu4cnw.fsf@ghpc6.ihf.rwth-aachen.de> Lines: 12 X-Mailer: Gnus v5.4.37/XEmacs 19.16 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Werner Griessl writes: > Are you sure, that the client is in the exports-file of the server ? > Werner tg:230) showmount -e bert Exports list on bert: /claudia ghpc6 ghpc6 is the FreeBSD client. tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 26 08:35:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11832 for freebsd-stable-outgoing; Thu, 26 Feb 1998 08:35:25 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ms7.accmail.com.tw (ms7.accmail.com.tw [210.68.148.43]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA11792; Thu, 26 Feb 1998 08:35:11 -0800 (PST) (envelope-from darkangel@ms7.accmail.com.tw) Message-Id: <199802261635.IAA11792@hub.freebsd.org> Received: from default ([202.145.226.10]) by AccSMTP Gateway for AccMail (v4.00.05/k3.10) [210.68.148.43]; Fri, 27 Feb 1998 00:35:14 +0800 From: "DARKANGEL" To: Cc: Subject: =?BIG5?B?vdCw3S4uLi4uLi4uLi4uLi4uLi4uLi4uLj8=?= Date: Fri, 27 Feb 1998 00:30:09 +0800 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 MIME-Version: 1.0 Content-Type: text/plain; charset=BIG5 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk ½Ð°Ý¦³ÃöFreeBSDªº«ü¥O±Ô­z±q¦ó³B¥i¥H¨ú±o¬ÛÃö¸ê®Æ p.s ¾Ç®Õ­n§Ú­Ì½ĶFreeBSDªº«ü¥O¤Î»yªk........ ½Ð±Nµª®×(ºô¯¸¦ì¸m)E-MAIL¦Ü DARKANGEL@ACCMAIL.COM.TW ©Î JENTEH@HOTMAIL.COM ÁÂÁÂ...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 26 08:44:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14029 for freebsd-stable-outgoing; Thu, 26 Feb 1998 08:44:27 -0800 (PST) (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 IAA14021 for ; Thu, 26 Feb 1998 08:44:20 -0800 (PST) (envelope-from evanc@synapse.net) Received: (qmail 26893 invoked from network); 26 Feb 1998 16:44:16 -0000 Received: from cpu1970.adsl.bellglobal.com (HELO cello) (206.47.37.201) by conductor.synapse.net with SMTP; 26 Feb 1998 16:44:16 -0000 Message-ID: <008401bd42d5$d07a1190$c9252fce@cello.synapse.net> From: "Evan Champion" To: "Michael V. Harding" Cc: Subject: Re: A 'make world' suggestion... Date: Thu, 26 Feb 1998 11:44:32 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk >Whoops! Of course I meant 'rm -rf /usr/obj' below... That would not be good for the case where /usr/obj is the root of a mounted filesystem (ie: in my case, /usr/src and /usr/obj are NFS mounted). Perhaps rm -rf /usr/obj/* would be better. Either way, you're right; it's much faster to toast /usr/obj in advance. Evan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 26 10:32:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29295 for freebsd-stable-outgoing; Thu, 26 Feb 1998 10:32:06 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c243.moon.jic.com [206.156.18.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29145; Thu, 26 Feb 1998 10:31:48 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id NAA00581; Thu, 26 Feb 1998 13:31:30 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: "Michael V. Harding" cc: jmb@FreeBSD.ORG, tom@uniserve.com, freebsd-stable@FreeBSD.ORG From: "Gary Palmer" Subject: Re: Netcom blocked? In-reply-to: Your message of "Wed, 25 Feb 1998 06:51:46 PST." <199802251451.GAA16242@mikey.nofear.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 26 Feb 1998 13:31:30 -0500 Message-ID: <577.888517890@gjp.erols.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk "Michael V. Harding" wrote in message ID <199802251451.GAA16242@mikey.nofear.com>: > > Mystery solved. After doing a 'make' in /etc/mail, I find NETCOM.COM > listed in 'domains.txt'. I don't know who maintains this list, but > hopefully netcom will turn off relaying and stop this BS. I installed > anti-relaying myself - they should be able to handle this - they are > running sendmail 8.8.8... The reason I heard that they are finding it difficult to refuse relaying is that they allow roaming (i.e. using your account through someone elses dialup). And they most definately were on the rbl for a while ... I think news.com may have an article on it. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 26 11:41:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07299 for freebsd-stable-outgoing; Thu, 26 Feb 1998 11:41:00 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from itsdsv1.enc.edu (fw1.enc.edu [207.95.42.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07290 for ; Thu, 26 Feb 1998 11:40:51 -0800 (PST) (envelope-from owensc@enc.edu) Received: from itsdsv2.enc.edu (itsdsv2.enc.edu [10.1.1.9]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id OAA23146 for ; Thu, 26 Feb 1998 14:39:05 -0500 (EST) Date: Thu, 26 Feb 1998 14:39:04 -0500 (EST) From: Charles Owens To: FreeBSD Stable List Subject: cvs update fails Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Ummm... anyone ever seen this? Doing an update of my releng_2_2 source tree: setenv CVSROOT /usr/cvs #pointing at my local CVS repository cd /usr/bigsrc/RELENG_2_2 cvs update # Runs fine for quite a while ... cvs update: Updating src/usr.sbin/pcvt/vttest cvs update: Updating src/usr.sbin/periodic cvs update: Updating src/usr.sbin/pkg_install assertion "rev == NULL || isdigit (*rev)" failed: file "/usr/bigsrc/RELENG_2_2/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/src/rcs.c", line 2861 Abort (core dumped) I ran it again and it died in the same spot... Any ideas? Thanks, --- ------------------------------------------------------------------------- Charles N. Owens Email: owensc@enc.edu http://www.enc.edu/~owensc Network & Systems Administrator Information Technology Services "Outside of a dog, a book is a man's Eastern Nazarene College best friend. Inside of a dog it's too dark to read." - Groucho Marx ------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 26 11:46:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08951 for freebsd-stable-outgoing; Thu, 26 Feb 1998 11:46:09 -0800 (PST) (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 LAA08716 for ; Thu, 26 Feb 1998 11:45:34 -0800 (PST) (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.6.9) with ESMTP id LAA26118; Thu, 26 Feb 1998 11:45:20 -0800 (PST) To: Charles Owens cc: FreeBSD Stable List Subject: Re: cvs update fails In-reply-to: Your message of "Thu, 26 Feb 1998 14:39:04 EST." Date: Thu, 26 Feb 1998 11:45:20 -0800 Message-ID: <26115.888522320@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > Ummm... anyone ever seen this? Yes, once when my CVS repository was corrupted. Are you sure yours is kosher? You might try removing src/contrib/cvs/src/rcs.c and re-cvsuping it just to make sure. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 26 12:17:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16463 for freebsd-stable-outgoing; Thu, 26 Feb 1998 12:17:35 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from itsdsv1.enc.edu (fw1.enc.edu [207.95.42.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16455 for ; Thu, 26 Feb 1998 12:17:31 -0800 (PST) (envelope-from owensc@enc.edu) Received: from itsdsv2.enc.edu (itsdsv2.enc.edu [10.1.1.9]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id PAA24453; Thu, 26 Feb 1998 15:15:10 -0500 (EST) Date: Thu, 26 Feb 1998 15:15:10 -0500 (EST) From: Charles Owens To: "Jordan K. Hubbard" cc: FreeBSD Stable List Subject: Re: cvs update fails In-Reply-To: <26115.888522320@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Thu, 26 Feb 1998, Jordan K. Hubbard wrote: > > Ummm... anyone ever seen this? > > Yes, once when my CVS repository was corrupted. Are you sure yours is > kosher? You might try removing src/contrib/cvs/src/rcs.c and > re-cvsuping it just to make sure. Hmmm... I might suspect this, but I can do a cvs update on another box from the same repository without any trouble. Here's how things are set up: Two systems: Delta - runs 2.2-970618-RELENG (currently up for 191 days!) /usr/cvs - master CVS repository, updated nightly via cvsup /usr/bigstuff/src local tree of RELENG_2_2 Dingo - runs 2.2.5-STABLE (a few days old) /usr/cvs - NFS mount of delta:/usr/cvs /usr/bigstuff/RELENG_2_2/src local tree of RELENG_2_2 It is on dingo where I'm having 'cvs update' die today. I just now ran 'cvs update' on delta with no trouble, which would seem to say that there's no problem with the repository. The only difference that I can see is that dingo NFS-mounts the repository and that it is running a newer OS version (neither of which I'd expect to be a problem). I've had no problem running 'cvs update' and 'make world' on dingo serveral times this month. Weird... --- ------------------------------------------------------------------------- Charles N. Owens Email: owensc@enc.edu http://www.enc.edu/~owensc Network & Systems Administrator Information Technology Services "Outside of a dog, a book is a man's Eastern Nazarene College best friend. Inside of a dog it's too dark to read." - Groucho Marx ------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 26 13:05:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24383 for freebsd-stable-outgoing; Thu, 26 Feb 1998 13:05:37 -0800 (PST) (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 NAA24270 for ; Thu, 26 Feb 1998 13:05:25 -0800 (PST) (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.6.9) with ESMTP id NAA26597; Thu, 26 Feb 1998 13:05:11 -0800 (PST) To: Charles Owens cc: FreeBSD Stable List Subject: Re: cvs update fails In-reply-to: Your message of "Thu, 26 Feb 1998 15:15:10 EST." Date: Thu, 26 Feb 1998 13:05:11 -0800 Message-ID: <26594.888527111@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > Hmmm... I might suspect this, but I can do a cvs update on another box > from the same repository without any trouble. Hmmm. Sounds like an NFS bogon to me then. V2 or V3 mounts? Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 26 13:20:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26886 for freebsd-stable-outgoing; Thu, 26 Feb 1998 13:20:18 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail-relay1.yahoo.com (mail-relay1.yahoo.com [206.251.17.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26688 for ; Thu, 26 Feb 1998 13:19:14 -0800 (PST) (envelope-from serge@yahoo-inc.com) Received: from borogove.yahoo.com (borogove.yahoo.com [205.216.162.65]) by mail-relay1.yahoo.com (8.8.7/8.8.8) with ESMTP id NAA00283; Thu, 26 Feb 1998 13:18:01 -0800 (PST) Received: from serge.yahoo.com (serge.yahoo.com [205.216.162.201]) by borogove.yahoo.com (8.8.7/8.8.8) with SMTP id NAA05520; Thu, 26 Feb 1998 13:17:29 -0800 (PST) Date: Thu, 26 Feb 1998 13:17:34 -0800 (PST) From: Sergiy Zhuk X-Sender: serge@serge.yahoo.com To: Thomas Gellekum cc: Werner Griessl , freebsd-stable@FreeBSD.ORG, "Viren R. Shah" , Yuri Gindin , John Fieber Subject: Re: 2.2.6 for NFS server In-Reply-To: <87ogzu4cnw.fsf@ghpc6.ihf.rwth-aachen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk hi On 26 Feb 1998, Thomas Gellekum wrote: > > Are you sure, that the client is in the exports-file of the server ? > > Werner > > tg:230) showmount -e bert > Exports list on bert: > /claudia ghpc6 > > ghpc6 is the FreeBSD client. check your name resolution and make sure your client is ghpc6 ;) login to 'bert' and use 'who' or 'w' to lookup your client's host name... client works perfect (except for nfsv3.tcp) with solaris and netapp at least. -- rgds, serge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 26 13:35:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29477 for freebsd-stable-outgoing; Thu, 26 Feb 1998 13:35:17 -0800 (PST) (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 NAA29428 for ; Thu, 26 Feb 1998 13:35:02 -0800 (PST) (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 NAA09350 for ; Thu, 26 Feb 1998 13:35:01 -0800 (PST) (envelope-from jdp) Message-Id: <199802262135.NAA09350@austin.polstra.com> To: stable@FreeBSD.ORG Subject: Re: A 'make world' suggestion... In-Reply-To: <008401bd42d5$d07a1190$c9252fce@cello.synapse.net> References: <008401bd42d5$d07a1190$c9252fce@cello.synapse.net> Organization: Polstra & Co., Seattle, WA Date: Thu, 26 Feb 1998 13:35:01 -0800 From: John Polstra Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > >Whoops! Of course I meant 'rm -rf /usr/obj' below... > > > That would not be good for the case where /usr/obj is the root of a mounted > filesystem (ie: in my case, /usr/src and /usr/obj are NFS mounted). Perhaps > rm -rf /usr/obj/* would be better. Either way, you're right; it's much > faster to toast /usr/obj in advance. There's an even faster way. Put /usr/obj alone in its own filesystem, and replace the "rm -rf" with a umount - newfs - mount sequence. Newfs is the fastest version of "rm -rf" in the world. -- 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 Feb 26 16:07:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29730 for freebsd-stable-outgoing; Thu, 26 Feb 1998 16:07:57 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gaia.coppe.ufrj.br (cisigw.coppe.ufrj.br [146.164.5.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29700 for ; Thu, 26 Feb 1998 16:07:42 -0800 (PST) (envelope-from jonny@coppe.ufrj.br) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.8/8.8.8) id WAA17130; Thu, 26 Feb 1998 22:07:34 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199802270007.WAA17130@gaia.coppe.ufrj.br> Subject: Re: 2.2.6 for NFS server In-Reply-To: <199802251846.NAA05311@rstcorp.com> from "Viren R. Shah" at "Feb 25, 98 01:46:54 pm" To: viren@rstcorp.com Date: Thu, 26 Feb 1998 22:07:34 -0200 (EDT) 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 #define quoting(Viren R. Shah) // We just got a server in that will be acting as our main NFS server. We // intend to run 2.2.x on it. Couple of questions: // // 1. Is 2.2.6 close enough that we should put off installing 2.2-STABLE // for a few days? Or in other terms, are there enough stability // improvements in 2.2.6 that we should definitely wait for it. Install it, and do a cvsup/make world after. :) // 2. I've seen a few mentions of NFS problems on 2.2.5. Are there any // big gotchas wrt using a 2.2.x box as an NFS server? I have some problems with NFS that I could not yet track down the source. If I try to use NFS in a full 100Mbps network, some time the client locks up completely, and I have to reboot. The problem seens to have diminished a lot when I upgraded the server's CPU from P90 to P200, so I think it's some kind of performance feature. Somebody said the problem is my network card, 3c905, that is a bad performing one, but this is not an excuse for a locking up NFS client. A big problem you'll find with FreeBSD as a NFS server is that its rpc.lockd is a fake. It'll always answer "Ok" to requesting clients, but it'll never make a real file lock. This is specially bad if you plan to mount your mail directory over NFS. Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 jonny@coppe.ufrj.br Universidade Federal do Rio de Janeiro UFRJ/COPPE/CISI PGP fingerprint: 29 C0 50 B9 B6 3E 58 F2 83 5F E3 26 BF 0F EA 67 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 26 17:04:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11995 for freebsd-stable-outgoing; Thu, 26 Feb 1998 17:04:15 -0800 (PST) (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 RAA11951 for ; Thu, 26 Feb 1998 17:03:59 -0800 (PST) (envelope-from evanc@synapse.net) Received: (qmail 6210 invoked from network); 27 Feb 1998 01:03:58 -0000 Received: from cpu1970.adsl.bellglobal.com (HELO cello) (206.47.37.201) by conductor.synapse.net with SMTP; 27 Feb 1998 01:03:58 -0000 Message-ID: <002401bd431b$9e9d7860$c9252fce@cello.synapse.net> From: "Evan Champion" To: "Joao Carlos Mendes Luis" , Cc: Subject: Re: 2.2.6 for NFS server Date: Thu, 26 Feb 1998 20:04:13 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk >A big problem you'll find with FreeBSD as a NFS server is that its >rpc.lockd is a fake. It'll always answer "Ok" to requesting clients, >but it'll never make a real file lock. This is specially bad if you >plan to mount your mail directory over NFS. Run qmail with maildirs; then even if you can't lock, delivering mail over NFS is safe. Evan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 26 17:09:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA12867 for freebsd-stable-outgoing; Thu, 26 Feb 1998 17:09:46 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from shell.futuresouth.com (shell.futuresouth.com [207.141.254.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA12850 for ; Thu, 26 Feb 1998 17:09:34 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: from shell.futuresouth.com (mail.futuresouth.com [207.141.254.21]) by shell.futuresouth.com (8.8.8/8.8.8) with SMTP id TAA01548; Thu, 26 Feb 1998 19:09:22 -0600 (CST) Date: Thu, 26 Feb 1998 19:09:22 -0600 (CST) From: "Matthew D. Fuller" To: Joao Carlos Mendes Luis cc: viren@rstcorp.com, freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.6 for NFS server In-Reply-To: <199802270007.WAA17130@gaia.coppe.ufrj.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Thu, 26 Feb 1998, Joao Carlos Mendes Luis wrote: > I have some problems with NFS that I could not yet track down the source. > If I try to use NFS in a full 100Mbps network, some time the client locks > up completely, and I have to reboot. The problem seens to have diminished > a lot when I upgraded the server's CPU from P90 to P200, so I think it's > some kind of performance feature. Somebody said the problem is my network > card, 3c905, that is a bad performing one, but this is not an excuse for > a locking up NFS client. I do believe that's right. I have a 905 too, but I only use it in 10 Mbps mode. IIRC, it only has 4k cache, split between transmit and recieve, so when there's heavy traffic, it goes nuts and drags the system down with it. Blame 3Com, not the OS. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | FreeBSD; the way computers were meant to be | * "The only reason I'm burning my candle at both ends, is * | that I haven't figured out how to light the middle yet."| * fullermd@futuresouth.com :-} MAtthew Fuller * | http://keystone.westminster.edu/~fullermd | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 26 18:50:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02330 for freebsd-stable-outgoing; Thu, 26 Feb 1998 18:50:49 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from itsdsv1.enc.edu (fw1.enc.edu [207.95.42.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02312 for ; Thu, 26 Feb 1998 18:50:38 -0800 (PST) (envelope-from owensc@enc.edu) Received: from itsdsv2.enc.edu (itsdsv2.enc.edu [10.1.1.9]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id VAA06679; Thu, 26 Feb 1998 21:48:20 -0500 (EST) Date: Thu, 26 Feb 1998 21:48:20 -0500 (EST) From: Charles Owens To: "Jordan K. Hubbard" cc: FreeBSD Stable List Subject: Re: cvs update fails In-Reply-To: <26594.888527111@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Thu, 26 Feb 1998, Jordan K. Hubbard wrote: > > Hmmm... I might suspect this, but I can do a cvs update on another box > > from the same repository without any trouble. > > Hmmm. Sounds like an NFS bogon to me then. V2 or V3 mounts? Was using V3. I just remounted it using V2 and tried again: same problem... cvs dumps core while chewing on .../src/usr.sbin/pkg_install. Next I did this: cd .../src/usr.sbin cvs release pkg_install # similar core dumping of cvs ensues, message like "cannot # release module pkg_install". Grrrrr: rm -r pkg_install cvs checkout pkg_install # success! cvs update # update .../src/usr.sbin -> success! cd .. cvs update # update all source -> success! Apparantly somewhere along the way something in the pkg_install source files got corrupted enough to choke cvs. No way of doing more than guessing as to the root cause... Assuming I get both boxes running -STABLE, should I in general trust nfs V3? Folks have been saying that there can be problems in heterogeneous environments, but it is thought that V3 is working well between FreeBSD boxes, correct? Thanks! --- ------------------------------------------------------------------------- Charles N. Owens Email: owensc@enc.edu http://www.enc.edu/~owensc Network & Systems Administrator Information Technology Services "Outside of a dog, a book is a man's Eastern Nazarene College best friend. Inside of a dog it's too dark to read." - Groucho Marx ------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 26 20:34:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA13838 for freebsd-stable-outgoing; Thu, 26 Feb 1998 20:34:11 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.sat.t.u-tokyo.ac.jp (dryad.sat.t.u-tokyo.ac.jp [133.11.156.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13685 for ; Thu, 26 Feb 1998 20:32:55 -0800 (PST) (envelope-from hideyuki@sat.t.u-tokyo.ac.jp) Received: by mail.sat.t.u-tokyo.ac.jp (8.8.6/3.4Wbeta6-SAT1.0) with ESMTP id NAA29632; Fri, 27 Feb 1998 13:32:47 +0900 (JST) Received: from localhost by vienas.sat.t.u-tokyo.ac.jp (8.8.8/sat-V0.6) id NAA27459; Fri, 27 Feb 1998 13:32:46 +0900 (JST) To: owensc@enc.edu Cc: jkh@time.cdrom.com, stable@FreeBSD.ORG Subject: Re: cvs update fails In-Reply-To: Your message of "27 Feb 1998 11:48:20 +0900" References: Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980227133246E.hideyuki@sat.t.u-tokyo.ac.jp> Date: Fri, 27 Feb 1998 13:32:46 +0900 From: Hideyuki Suzuki X-Dispatcher: imput version 980128 Lines: 40 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk From: Charles Owens Subject: Re: cvs update fails Date: 27 Feb 1998 11:48:20 +0900 > On Thu, 26 Feb 1998, Jordan K. Hubbard wrote: > > > > Hmmm... I might suspect this, but I can do a cvs update on another box > > > from the same repository without any trouble. > > > > Hmmm. Sounds like an NFS bogon to me then. V2 or V3 mounts? > > Was using V3. I just remounted it using V2 and tried again: same > problem... cvs dumps core while chewing on .../src/usr.sbin/pkg_install. > Next I did this: > > cd .../src/usr.sbin > cvs release pkg_install > # similar core dumping of cvs ensues, message like "cannot > # release module pkg_install". Grrrrr: > > rm -r pkg_install > cvs checkout pkg_install > # success! > cvs update # update .../src/usr.sbin -> success! > cd .. > cvs update # update all source -> success! > > Apparantly somewhere along the way something in the pkg_install source > files got corrupted enough to choke cvs. No way of doing more than > guessing as to the root cause... Yesterday, I saw cvs dumped core in src/usr.sbin/pkg_install while updating all source. Since the problem went away after another checkout, I just thought I've mistakenly broke something. But the same problem at the same place... In my case, both the repository and the source are on the local disk. -- Hideyuki Suzuki Department of Mathematical Engineering, the University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 26 23:49:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14188 for freebsd-stable-outgoing; Thu, 26 Feb 1998 23:49:57 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from uranus.planet-three.com (homer.duff-beer.com [194.207.51.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14183 for ; Thu, 26 Feb 1998 23:49:54 -0800 (PST) (envelope-from scot@poptart.org) Received: from localhost (scot@localhost) by uranus.planet-three.com (8.8.8/8.8.5) with SMTP id HAA12253 for ; Fri, 27 Feb 1998 07:49:51 GMT Date: Fri, 27 Feb 1998 07:49:50 +0000 (GMT) From: Scot Elliott To: freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.6 for NFS server In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Thu, 26 Feb 1998, Matthew D. Fuller wrote: > I have a 905 too, but I only use it in 10 Mbps mode. IIRC, it only has 4k > cache, split between transmit and recieve, so when there's heavy traffic, > it goes nuts and drags the system down with it. > Blame 3Com, not the OS. Hmm... well I've always avoided 3com cards in FreeBSD because of the rather discouraging comments in LINT: # el: 3Com 3C501 (slow!) # ep: 3Com 3C509 (buggy) Does anyone know if this is still true - or do these actually work OK? I'm not convinced you can say it's the card's fault that the machine comes down when the network is under heavy load. Even if the OS spits loads of errors about the card, there's obviously a buggy driver if the kernel crashes. Scot. ----------------------------------------------------------------------------- Scot Elliott (scot@poptart.org) | Work: +44 (0)1344 899401 PGP fingerprint: FCAE9ED3A234FEB59F8C7F9DDD112D | Home: +44 (0)181 8961019 ----------------------------------------------------------------------------- Public key available by finger at: finger scot@poptart.org or at: http://www.poptart.org/pgpkey.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 27 00:01:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA15865 for freebsd-stable-outgoing; Fri, 27 Feb 1998 00:01:14 -0800 (PST) (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 AAA15839 for ; Fri, 27 Feb 1998 00:01:09 -0800 (PST) (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 XAA26898; Thu, 26 Feb 1998 23:59:23 -0800 (PST) Message-Id: <199802270759.XAA26898@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Scot Elliott cc: freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.6 for NFS server In-reply-to: Your message of "Fri, 27 Feb 1998 07:49:50 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 26 Feb 1998 23:59:22 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > I have a 905 too, but I only use it in 10 Mbps mode. IIRC, it only has 4k > > cache, split between transmit and recieve, so when there's heavy traffic, > > it goes nuts and drags the system down with it. > > Blame 3Com, not the OS. This is not fair. The current driver for these cards runs them in a backwards-compatible mode that does not take advantage of their more advanced features. This *is* an OS issue. The recent 3com supporter indicated that he would be writing improved support, and that's thoroughly wonderful. I'm certainly keen to see it happen. > Hmm... well I've always avoided 3com cards in FreeBSD because of the > rather discouraging comments in LINT: > > # el: 3Com 3C501 (slow!) > # ep: 3Com 3C509 (buggy) > > Does anyone know if this is still true - or do these actually work OK? The 501 is an atrocious piece of junk, and we should probably stop even pretending to support it. The 509 has caused many people grief, but basically the card works quite OK when properly configured. It's not a stellar performer, but it's quite functional. -- \\ 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 Fri Feb 27 03:34:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA06958 for freebsd-stable-outgoing; Fri, 27 Feb 1998 03:34:19 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from tyree.iii.co.uk ([195.89.149.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA06953 for ; Fri, 27 Feb 1998 03:34:15 -0800 (PST) (envelope-from nik@iii.co.uk) From: nik@iii.co.uk Received: from carrig.strand.iii.co.uk (carrig.strand.iii.co.uk [192.168.7.25]) by tyree.iii.co.uk (8.8.8/8.8.8) with ESMTP id LAA15700; Fri, 27 Feb 1998 11:28:29 GMT Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.7/8.8.7) id LAA02927; Fri, 27 Feb 1998 11:33:48 GMT Message-ID: <19980227113347.35288@iii.co.uk> Date: Fri, 27 Feb 1998 11:33:47 +0000 To: Charles Owens Cc: FreeBSD Stable List Subject: Re: cvs update fails References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e In-Reply-To: ; from Charles Owens on Thu, Feb 26, 1998 at 02:39:04PM -0500 Organization: interactive investor Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Thu, Feb 26, 1998 at 02:39:04PM -0500, Charles Owens wrote: > setenv CVSROOT /usr/cvs #pointing at my local CVS repository > cd /usr/bigsrc/RELENG_2_2 > cvs update cvs update -Pd It won't fix the problem you're having, but it's a good idea anyway. N -- Work: nik@iii.co.uk | FreeBSD + Perl + Apache Rest: nik@nothing-going-on.demon.co.uk | Remind me again why we need Play: nik@freebsd.org | Microsoft? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 27 04:18:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA12991 for freebsd-stable-outgoing; Fri, 27 Feb 1998 04:18:47 -0800 (PST) (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 EAA12982 for ; Fri, 27 Feb 1998 04:18:41 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id MAA27529; Fri, 27 Feb 1998 12:18:39 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id NAA04652; Fri, 27 Feb 1998 13:18:14 +0100 (MET) Message-ID: <19980227131814.17813@follo.net> Date: Fri, 27 Feb 1998 13:18:14 +0100 From: Eivind Eklund To: nik@iii.co.uk, Charles Owens Cc: FreeBSD Stable List Subject: Re: cvs update fails References: <19980227113347.35288@iii.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980227113347.35288@iii.co.uk>; from nik@iii.co.uk on Fri, Feb 27, 1998 at 11:33:47AM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Fri, Feb 27, 1998 at 11:33:47AM +0000, nik@iii.co.uk wrote: > On Thu, Feb 26, 1998 at 02:39:04PM -0500, Charles Owens wrote: > > setenv CVSROOT /usr/cvs #pointing at my local CVS repository > > cd /usr/bigsrc/RELENG_2_2 > > cvs update > > cvs update -Pd > > It won't fix the problem you're having, but it's a good idea anyway. .cvsrc It won't fix the problem you're having, but it's a good idea anyway. (Translation: The -Pd options should usually be specified in the .cvsrc file of the user, so 'cvs update' should be the correct thing to do.) Eivind, in a slightly malicious mood. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 27 07:25:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02606 for freebsd-stable-outgoing; Fri, 27 Feb 1998 07:25:08 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from helix.mdy.univie.ac.at (helix.mdy.univie.ac.at [131.130.40.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02600 for ; Fri, 27 Feb 1998 07:25:04 -0800 (PST) (envelope-from stefan@mdy.univie.ac.at) Received: from alpha.mdy.univie.ac.at (alpha.mdy.univie.ac.at [131.130.40.3]) by helix.mdy.univie.ac.at (8.8.8/8.8.8) with ESMTP id QAA24798 for ; Fri, 27 Feb 1998 16:24:56 +0100 (MET) From: Stefan Boresch Received: (from stefan@localhost) by alpha.mdy.univie.ac.at (8.8.8/8.8.8) id QAA00611 for freebsd-stable@FreeBSD.ORG; Fri, 27 Feb 1998 16:29:59 +0100 (MEZ) Message-Id: <199802271529.QAA00611@alpha.mdy.univie.ac.at> Subject: Re: 2.2.6 for NFS server To: freebsd-stable@FreeBSD.ORG Date: Fri, 27 Feb 98 16:29:58 MEZ Reply-To: stefan@mdy.univie.ac.at Mailer: Elm [revision: 70.85] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I briefly contributed to this thread by mentioning that I was/am encountering severe (performance) problems between a FreeBSD server (2.2-stable machine, last make world around end of January) and SGIs running IRIX 5.3 and 6.1 as the client. In return the question came up whether this happens using NFSv3 or NFSv2. It turns out that this is a good question. I sort of 'inherited' the administration of these SGIs and have little expertise in IRIX 5.3 and 6.1. I don't find in the manpages any option to choose between NFSv3 and NFSv2. I believe, however, that 5.3 doesn't even support v3. Further, doesn't mounting with mount -t nfs -o wsize=1024 server1:/temp_data /tmp_mnt/data (or a larger size for wsize) imply NFSv2. The wsize option is irrelevant for v3, isn't it. I frequently have to mount as specified above as omitting the wsize statement leads to file truncation errors. BTW, the syslog entry on IRIX 6.1 specifically mentions NFS2 (I cut it out wrong in my last posting) |||| Feb 27 13:28:12 2A:octopus unix: NFS2 write failed for server server1: Can't encode arguments Feb 27 13:28:12 2A:octopus unix: NFS write error 5 on host server1 Feb 27 13:28:18 2A:octopus unix: xdr_bytes: bad size FAILED My main gripe is truly the performance, 20kB/sec isn't usable for anything practical! (It can't be my network since FreeBSD as a NFS client easily does 1MB/sec (this is a switched 10MBit EThernet installation), for ftp even slightly better!) I am happy to test and follow suggestion. Thanks, Stefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 27 07:34:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA03972 for freebsd-stable-outgoing; Fri, 27 Feb 1998 07:34:37 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA03958 for ; Fri, 27 Feb 1998 07:34:28 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.8.8/8.8.7) with SMTP id KAA00453 for ; Fri, 27 Feb 1998 10:34:25 -0500 (EST) Date: Fri, 27 Feb 1998 10:34:25 -0500 (EST) From: jack To: stable@FreeBSD.ORG Subject: BOOT_HD_BIAS broken in RELENG_2_2 ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Attempts to compile in /sys/i386/boot/biosboot with BOOT_HD_BIAS set to either 1 or 2 fall over with `boot2 is too big'. Compiles fine without that option. I've gotten the same results on three different 2.2-STABLE boxes one cvsup'ed last night, one a few days ago, and one a few weeks ago. 2.2.1-RELEASE compiles it cleanly. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 27 07:51:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06123 for freebsd-stable-outgoing; Fri, 27 Feb 1998 07:51:22 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from msp-ln05.dgii.com (msp-ln05.dgii.com [204.221.110.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06096 for ; Fri, 27 Feb 1998 07:51:13 -0800 (PST) (envelope-from Robert_Wagner@dgii.com) Received: from Lotus Notes (PU Serial #1839) by msp-ln05.dgii.com (PostalUnion/SMTP(tm) v2.1.9f for Windows NT(tm)) id AA-1998Feb27.084618.1839.2208950; Fri, 27 Feb 1998 09:49:21 -0600 From: Robert_Wagner@dgii.com (Robert Wagner) To: stable@FreeBSD.ORG (stable) Message-ID: <1998Feb27.084618.1839.2208950@msp-ln05.dgii.com> X-Conversion-ID: X-Mailer: Lotus Notes via PostalUnion/SMTP for Windows NT Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Organization: Digi International Date: Fri, 27 Feb 1998 09:49:21 -0600 Subject: make buildworld Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk When doing a make on the SRC tree I get ".depend", line 497: Need an operator I ran make in debug mode with all messages and the previous 2 lines reads Searching for .depend...in '.' Global:MAKEFILE = .depend The following line to the error is make : fatal errors encountered -- cannot continue This is happening in the gnu/usr.bin/rcs/lib directory. Any ideas on how to correct this problem? Which make file is it in ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 27 08:45:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16584 for freebsd-stable-outgoing; Fri, 27 Feb 1998 08:45:25 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16500; Fri, 27 Feb 1998 08:45:17 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id JAA27422; Fri, 27 Feb 1998 09:19:56 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA04116; Fri, 27 Feb 1998 09:19:55 -0700 Date: Fri, 27 Feb 1998 09:19:55 -0700 Message-Id: <199802271619.JAA04116@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Eivind Eklund Cc: cvs-committers@FreeBSD.ORG, FreeBSD Stable List Subject: Re: cvs update fails In-Reply-To: <19980227131814.17813@follo.net> References: <19980227113347.35288@iii.co.uk> <19980227131814.17813@follo.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Eivind Eklund writes: > On Fri, Feb 27, 1998 at 11:33:47AM +0000, nik@iii.co.uk wrote: > > On Thu, Feb 26, 1998 at 02:39:04PM -0500, Charles Owens wrote: > > > setenv CVSROOT /usr/cvs #pointing at my local CVS repository > > > cd /usr/bigsrc/RELENG_2_2 > > > cvs update > > > > cvs update -Pd > > > > It won't fix the problem you're having, but it's a good idea anyway. > > .cvsrc > > It won't fix the problem you're having, but it's a good idea anyway. > > (Translation: The -Pd options should usually be specified in the > .cvsrc file of the user, so 'cvs update' should be the correct thing > to do.) FWIW, CVS has recently been fixed to 'Do The Right Thing' when checking out new directories on branches when -d is given. As many know already, previously it would check out the directory on the HEAD (even if the directory above was a 'sticky branch'. It now checks out directories that only exist on the branch. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 27 09:04:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20038 for freebsd-stable-outgoing; Fri, 27 Feb 1998 09:04:39 -0800 (PST) (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 JAA20030 for ; Fri, 27 Feb 1998 09:04:32 -0800 (PST) (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 IAA16226; Fri, 27 Feb 1998 08:54:42 -0800 (PST) (envelope-from jdp) Message-Id: <199802271654.IAA16226@austin.polstra.com> To: Robert_Wagner@dgii.com Subject: Re: make buildworld In-Reply-To: <1998Feb27.084618.1839.2208950@msp-ln05.dgii.com> References: <1998Feb27.084618.1839.2208950@msp-ln05.dgii.com> Organization: Polstra & Co., Seattle, WA Cc: stable@FreeBSD.ORG Date: Fri, 27 Feb 1998 08:54:42 -0800 From: John Polstra Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk In article <1998Feb27.084618.1839.2208950@msp-ln05.dgii.com>, Robert Wagner wrote: > When doing a make on the SRC tree I get > > ".depend", line 497: Need an operator [...] > This is happening in the gnu/usr.bin/rcs/lib directory. Any ideas on how to > correct this problem? Which make file is it in ? It looks like the ".depend" file in the corresponding /usr/obj subdirectory is corrupted. The easiest way to fix it is: cd /usr/src/gnu/usr.bin/rcs/lib make cleandepend make depend John -- 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 Fri Feb 27 11:07:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04441 for freebsd-stable-outgoing; Fri, 27 Feb 1998 11:07:43 -0800 (PST) (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 LAA04427 for ; Fri, 27 Feb 1998 11:07:35 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id NAA16952; Fri, 27 Feb 1998 13:07:25 -0600 (CST) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <199802271619.JAA04116@mt.sri.com> References: <19980227131814.17813@follo.net> <19980227113347.35288@iii.co.uk> <19980227131814.17813@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 27 Feb 1998 13:04:53 -0600 To: Nate Williams From: Richard Wackerbarth Subject: Re: cvs update fails Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk At 10:19 AM -0600 2/27/98, Nate Williams wrote: >FWIW, CVS has recently been fixed to 'Do The Right Thing' when checking >out new directories on branches when -d is given. As many know already, >previously it would check out the directory on the HEAD (even if the >directory above was a 'sticky branch'. It now checks out directories >that only exist on the branch. I presume that you mean "It checks out only those directories that exist on the branch". A directory that is added to both the head and the branch would also get checked out. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 27 11:34:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11171 for freebsd-stable-outgoing; Fri, 27 Feb 1998 11:34:10 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dt050ndd.san.rr.com (dougdougdougdoug@dt050ndd.san.rr.com [204.210.31.221]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11137; Fri, 27 Feb 1998 11:33:50 -0800 (PST) (envelope-from Studded@dal.net) Received: from localhost (dougdougdougdoug@localhost) by dt050ndd.san.rr.com (8.8.8/8.8.8) with SMTP id TAA00321; Fri, 27 Feb 1998 19:33:41 GMT (envelope-from Studded@dal.net) Date: Fri, 27 Feb 1998 11:33:40 -0800 (PST) From: Studded X-Sender: dougdougdougdoug@dt050ndd.san.rr.com To: freebsd-stable@FreeBSD.ORG cc: alex@FreeBSD.ORG Subject: ipfw not setting rules Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk With no changes to any of my ipfw rules, I noticed on reboot last night (after a 2/23 cvsup and make world) that ipfw was giving an error message instead of setting rules. So I cvsup'ed early this morning (around 12:30 PST) make the world, made a new kernel and got the same error, always about the supposedly missing 'to'. Here is an example: 4# ipfw add 65534 allow ip from any to any ipfw: error: missing ``to'' usage: ipfw [options] etc. I have the following ipfw options in my kernel: options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets options "IPFIREWALL_VERBOSE_LIMIT=1000" #limit verbosity options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default These are also unchanged from pre 2/23 which used to work. Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 5,328 clients and still growing. *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 27 12:40:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24862 for freebsd-stable-outgoing; Fri, 27 Feb 1998 12:40:01 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24811 for ; Fri, 27 Feb 1998 12:39:59 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id NAA29082; Fri, 27 Feb 1998 13:39:57 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA05657; Fri, 27 Feb 1998 13:39:56 -0700 Date: Fri, 27 Feb 1998 13:39:56 -0700 Message-Id: <199802272039.NAA05657@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Richard Wackerbarth Cc: Nate Williams , stable@FreeBSD.ORG Subject: Re: cvs update fails In-Reply-To: References: <19980227131814.17813@follo.net> <19980227113347.35288@iii.co.uk> <199802271619.JAA04116@mt.sri.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > >FWIW, CVS has recently been fixed to 'Do The Right Thing' when checking > >out new directories on branches when -d is given. As many know already, > >previously it would check out the directory on the HEAD (even if the > >directory above was a 'sticky branch'. It now checks out directories > >that only exist on the branch. > > I presume that you mean "It checks out only those directories that > exist on the branch". A directory that is added to both the head and > the branch would also get checked out. Yes, but those files would be checked on with the versions that are on the branch. Like I said, it now 'Does the Right Thing'. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 27 13:03:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29932 for freebsd-stable-outgoing; Fri, 27 Feb 1998 13:03:18 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA29907 for ; Fri, 27 Feb 1998 13:02:57 -0800 (PST) (envelope-from nash@Jupiter.Mcs.Net) Received: from Jupiter.Mcs.Net (nash@Jupiter.mcs.net [192.160.127.88]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id PAA29982; Fri, 27 Feb 1998 15:02:53 -0600 (CST) Received: from localhost (nash@localhost) by Jupiter.Mcs.Net (8.8.7/8.8.2) with SMTP id PAA28095; Fri, 27 Feb 1998 15:02:52 -0600 (CST) Date: Fri, 27 Feb 1998 15:02:52 -0600 (CST) From: Alex Nash To: Studded cc: freebsd-stable@FreeBSD.ORG Subject: Re: ipfw not setting rules In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Fri, 27 Feb 1998, Studded wrote: > With no changes to any of my ipfw rules, I noticed on reboot last > night (after a 2/23 cvsup and make world) that ipfw was giving an error > message instead of setting rules. So I cvsup'ed early this morning (around > 12:30 PST) make the world, made a new kernel and got the same error, > always about the supposedly missing 'to'. Here is an example: > > 4# ipfw add 65534 allow ip from any to any > ipfw: error: missing ``to'' Thanks for the report, Doug. I tried to duplicate this here using a slightly older 2.2.5 (approx. early January) and an updated ipfw, but the above command works fine for me. I'll make another attempt to duplicate this tomorrow morning after I get an up-to-date 2.2.5 built. For reference purposes, can you give me the output of: ident /usr/src/sbin/ipfw/ipfw.c /sys/netinet/ip_fw* Does anyone else see this problem? Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 27 14:42:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15603 for freebsd-stable-outgoing; Fri, 27 Feb 1998 14:42:58 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from hol.virtual-pc.com (hol.virtual-pc.com [195.11.18.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15582 for ; Fri, 27 Feb 1998 14:42:44 -0800 (PST) (envelope-from hol@homes-on-line.com) Received: from spod (ae162.du.pipex.com [193.130.244.162]) by hol.virtual-pc.com (8.8.7/8.8.7) with ESMTP id WAA03237 for ; Fri, 27 Feb 1998 22:58:18 GMT Message-ID: <34CFB3A8.5FF0FFC3@homes-on-line.com> Date: Wed, 28 Jan 1998 22:39:36 +0000 From: hol user X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: subscribe X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 27 14:59:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17817 for freebsd-stable-outgoing; Fri, 27 Feb 1998 14:59:30 -0800 (PST) (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 OAA17804 for ; Fri, 27 Feb 1998 14:59:19 -0800 (PST) (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 OAA29280; Fri, 27 Feb 1998 14:57:27 -0800 (PST) Message-Id: <199802272257.OAA29280@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: jack cc: stable@FreeBSD.ORG Subject: Re: BOOT_HD_BIAS broken in RELENG_2_2 ? In-reply-to: Your message of "Fri, 27 Feb 1998 10:34:25 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Feb 1998 14:57:24 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > Attempts to compile in /sys/i386/boot/biosboot with BOOT_HD_BIAS > set to either 1 or 2 fall over with `boot2 is too big'. > Compiles fine without that option. I've gotten the same results > on three different 2.2-STABLE boxes one cvsup'ed last night, one > a few days ago, and one a few weeks ago. 2.2.1-RELEASE compiles > it cleanly. There was some extra functionality added recently that bloated it out again. I've merged one of the size reductions from -current to get it back down again; you should be OK now. -- \\ 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 Fri Feb 27 17:19:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13431 for freebsd-stable-outgoing; Fri, 27 Feb 1998 17:19:16 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from shell.futuresouth.com (shell.futuresouth.com [207.141.254.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA13424 for ; Fri, 27 Feb 1998 17:19:06 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: from shell.futuresouth.com (mail.futuresouth.com [207.141.254.21]) by shell.futuresouth.com (8.8.8/8.8.8) with SMTP id TAA00819; Fri, 27 Feb 1998 19:18:37 -0600 (CST) Date: Fri, 27 Feb 1998 19:18:37 -0600 (CST) From: "Matthew D. Fuller" To: Mike Smith cc: Scot Elliott , freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.6 for NFS server In-Reply-To: <199802270759.XAA26898@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Thu, 26 Feb 1998, Mike Smith wrote: > > > I have a 905 too, but I only use it in 10 Mbps mode. IIRC, it only has 4k > > > cache, split between transmit and recieve, so when there's heavy traffic, > > > it goes nuts and drags the system down with it. > > > Blame 3Com, not the OS. > > This is not fair. The current driver for these cards runs them in a > backwards-compatible mode that does not take advantage of their more > advanced features. This *is* an OS issue. The recent 3com supporter > indicated that he would be writing improved support, and that's > thoroughly wonderful. I'm certainly keen to see it happen. *cringe* OK, maybe I was a bit hasty. Let me clarify that a bit: The card is, in many ways, a bit crappy, IMO. It SHOULD not, however, take the OS down with it. And I suspect an updated driver would helps loads. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | FreeBSD; the way computers were meant to be | * "The only reason I'm burning my candle at both ends, is * | that I haven't figured out how to light the middle yet."| * fullermd@futuresouth.com :-} MAtthew Fuller * | http://keystone.westminster.edu/~fullermd | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 27 19:23:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03530 for freebsd-stable-outgoing; Fri, 27 Feb 1998 19:23:12 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03479 for ; Fri, 27 Feb 1998 19:22:58 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.8.8/8.8.7) with SMTP id WAA00243; Fri, 27 Feb 1998 22:22:17 -0500 (EST) Date: Fri, 27 Feb 1998 22:22:17 -0500 (EST) From: jack To: Mike Smith cc: stable@FreeBSD.ORG Subject: Re: BOOT_HD_BIAS broken in RELENG_2_2 ? In-Reply-To: <199802272257.OAA29280@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Fri, 27 Feb 1998, Mike Smith wrote: > There was some extra functionality added recently that bloated it out > again. I've merged one of the size reductions from -current to get it > back down again; you should be OK now. Thanks Mike. That did it. One more SCSI drive, and a cable with enough connectors, and these IDEs can slide down the food chain. :) -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 27 19:59:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA11512 for freebsd-stable-outgoing; Fri, 27 Feb 1998 19:59:04 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA11468 for ; Fri, 27 Feb 1998 19:58:50 -0800 (PST) (envelope-from mark@vnode.vmunix.com) Received: (from mark@localhost) by vnode.vmunix.com (8.8.8/8.8.8) id XAA18355; Fri, 27 Feb 1998 23:08:08 -0500 (EST) (envelope-from mark) Message-ID: <19980227230807.57951@vmunix.com> Date: Fri, 27 Feb 1998 23:08:07 -0500 From: Mark Mayo To: John Saunders , freebsd-stable@FreeBSD.ORG Subject: Re: stable branch funnies References: <34F4C11D.DD3E9820@scitec.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <34F4C11D.DD3E9820@scitec.com.au>; from John Saunders on Thu, Feb 26, 1998 at 12:10:53PM +1100 X-Operating-System: FreeBSD 2.2.5-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Thu, Feb 26, 1998 at 12:10:53PM +1100, John Saunders wrote: > John Saunders wrote: > > I then tried a build which failed due to a problem in libg++. > > After several more attempts at building, all resulting in failed > compiles of ACG.cc in libg++, I blew away my cvsup'ed source and > re-installed 2.2.5-RELEASE from CD. FWIW, I generally blow away the source that came off the CD before I do a CVSup of the RELENG_2_2 tree - I remember in the past that someone mentioned that if you don't, cvs might thing that it doesn't own the files it's trying to delete, and you'll run into problems. I don't know if this is still the case... But yeah, I've had much better luck with 'rm -r /usr/src/*' before my initial cvsup on a freshly installed RELEASE. -Mark > > Cheers. > -- +------------------------------------------------------------+ > . | John Saunders mailto:John.Saunders@scitec.com.au (Work) | > ,--_|\ | mailto:john@nlc.net.au (Home) | > / Oz \ | http://www.nlc.net.au/~john/ | > \_,--\_/ | SCITEC LIMITED Phone +61 2 9428 9563 Fax +61 2 9428 9933 | > v | "By the time you make ends meet, they move the ends." | > +------------------------------------------------------------+ -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ "The problem is how do you build tools that understand your programs at a deeper semantic level." - James Gosling To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 27 23:55:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09041 for freebsd-stable-outgoing; Fri, 27 Feb 1998 23:55:31 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from const. (willow7.verinet.com [199.45.181.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA09014 for ; Fri, 27 Feb 1998 23:55:23 -0800 (PST) (envelope-from allenc@verinet.com) Received: (from allenc@localhost) by const. (8.8.8/8.8.8) id AAA00364 for stable@freebsd.org; Sat, 28 Feb 1998 00:55:19 -0700 (MST) (envelope-from allenc) Date: Sat, 28 Feb 1998 00:55:19 -0700 (MST) From: allen campbell Message-Id: <199802280755.AAA00364@const.> To: stable@FreeBSD.ORG Subject: schg flag in /usr/obj Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk While preparing to make world (RELENG_2_2), I found the schg (immutable) flag set on two files under /usr/obj, apparently left over from the last make world. /usr/obj/usr/src/tmp/usr/lib/lib.so.3.0 /usr/obj/usr/src/tmp/usr/libexec/ld.so Nothing unexpected happened during the last make world. I have no reason to suspect anything has been corrupted on this host. I cleared the flags and removed the files. This seemed a bit strange so I thought I'd report it. Allen Campbell allenc@verinet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 28 20:51:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09136 for freebsd-stable-outgoing; Sat, 28 Feb 1998 20:51:57 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09125 for ; Sat, 28 Feb 1998 20:51:44 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt1-92.HiWAAY.net [208.147.147.92]) by fly.HiWAAY.net (8.8.8/8.8.6) with ESMTP id WAA23639 for ; Sat, 28 Feb 1998 22:51:36 -0600 (CST) Received: from nospam.hiwaay.net (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.4) with ESMTP id WAA25777 for ; Sat, 28 Feb 1998 22:51:35 -0600 (CST) Message-Id: <199803010451.WAA25777@nospam.hiwaay.net> X-Mailer: exmh version 2.0.1 12/23/97 To: freebsd-stable@FreeBSD.ORG Subject: Tonight's cvsup'ed -stable fails "make buildword" From: David Kelly Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Feb 1998 22:51:34 -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Am not sure if this is operator error on my part or what. Had some cvsup problems earlier this (or last) week. Wonder if I got my sources hosed? If so, thought cvsup was supposed to detect that and fix my source tree? As an attempt to cure I have "make clean", "make cleandepend", "rm -rf /usr/obj/*", and finally "rm /usr/src/include/*" followed by a cvsup. That last one is compiling right now. ===> libscsi cc -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libscsi/scsi.c -o scsi.o building standard scsi library ranlib libscsi.a cc -fpic -DPIC -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libscsi/scsi.c -o scsi.so building shared scsi library (version 2.0) ===> libskey cc -pipe -DPERMIT_CONSOLE -D_SKEY_INTERNAL -I/usr/src/lib/libskey -W -Wall -Werror -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libskey/skeyaccess.c -o skeyaccess.o cc1: warnings being treated as errors /usr/obj/usr/src/tmp/usr/include/stdio.h:366: warning: `__sputc' defined but not used /usr/obj/usr/src/tmp/usr/include/ctype.h:143: warning: `__istype' defined but not used /usr/obj/usr/src/tmp/usr/include/ctype.h:157: warning: `__toupper' defined but not used /usr/obj/usr/src/tmp/usr/include/ctype.h:164: warning: `__tolower' defined but not used *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 28 21:28:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14053 for freebsd-stable-outgoing; Sat, 28 Feb 1998 21:28:26 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from emu.sourcee.com (emu.sourcee.com [199.201.159.173]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14033 for ; Sat, 28 Feb 1998 21:28:05 -0800 (PST) (envelope-from nrice@emu.sourcee.com) Received: (from nrice@localhost) by emu.sourcee.com (8.8.8/8.8.3) id AAA25665; Sun, 1 Mar 1998 00:26:26 -0500 (EST) Message-ID: <19980301002625.29916@emu.sourcee.com> Date: Sun, 1 Mar 1998 00:26:25 -0500 From: Norman C Rice To: David Kelly Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Tonight's cvsup'ed -stable fails "make buildword" References: <199803010451.WAA25777@nospam.hiwaay.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199803010451.WAA25777@nospam.hiwaay.net>; from David Kelly on Sat, Feb 28, 1998 at 10:51:34PM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Sat, Feb 28, 1998 at 10:51:34PM -0600, David Kelly wrote: > Am not sure if this is operator error on my part or what. Had some > cvsup problems earlier this (or last) week. Wonder if I got my sources > hosed? If so, thought cvsup was supposed to detect that and fix my > source tree? > > As an attempt to cure I have "make clean", "make cleandepend", > "rm -rf /usr/obj/*", and finally "rm /usr/src/include/*" followed by a > cvsup. That last one is compiling right now. > > ===> libscsi > cc -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libscsi/scsi.c -o scsi.o > building standard scsi library > ranlib libscsi.a > cc -fpic -DPIC -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libscsi/scsi.c -o scsi.so > building shared scsi library (version 2.0) > ===> libskey > cc -pipe -DPERMIT_CONSOLE -D_SKEY_INTERNAL -I/usr/src/lib/libskey -W -Wall -Werror ^^^^^^^ The `-Werror' option is causing the compiler to abort just because some macros were defined but not used. IMO, this seems a little too stringent; even for stable/secure code. I am not sure why it's being used, but I believe if you get rid of the option, the compiler will get by this. -- Regards, Norman C. Rice, Jr. > -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libskey/skeyaccess.c -o skeyaccess.o > cc1: warnings being treated as errors > /usr/obj/usr/src/tmp/usr/include/stdio.h:366: warning: `__sputc' defined but not used > /usr/obj/usr/src/tmp/usr/include/ctype.h:143: warning: `__istype' defined but not used > /usr/obj/usr/src/tmp/usr/include/ctype.h:157: warning: `__toupper' defined but not used > /usr/obj/usr/src/tmp/usr/include/ctype.h:164: warning: `__tolower' defined but not used > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > > > > -- > David Kelly N4HHE, dkelly@nospam.hiwaay.net > ===================================================================== > The human mind ordinarily operates at only ten percent of its > capacity -- the rest is overhead for the operating system. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 28 21:40:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16897 for freebsd-stable-outgoing; Sat, 28 Feb 1998 21:40:50 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16840; Sat, 28 Feb 1998 21:40:43 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA32286; Sun, 1 Mar 1998 16:36:42 +1100 Date: Sun, 1 Mar 1998 16:36:42 +1100 From: Bruce Evans Message-Id: <199803010536.QAA32286@godzilla.zeta.org.au> To: dkelly@HiWAAY.net, freebsd-stable@FreeBSD.ORG Subject: Re: Tonight's cvsup'ed -stable fails "make buildword" Cc: pst@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk >===> libscsi >cc -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libscsi/scsi.c -o scsi.o >building standard scsi library >ranlib libscsi.a >cc -fpic -DPIC -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libscsi/scsi.c -o scsi.so >building shared scsi library (version 2.0) >===> libskey >cc -pipe -DPERMIT_CONSOLE -D_SKEY_INTERNAL -I/usr/src/lib/libskey -W -Wall -Werror -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libskey/skeyaccess.c -o skeyaccess.o >cc1: warnings being treated as errors >/usr/obj/usr/src/tmp/usr/include/stdio.h:366: warning: `__sputc' defined but not used >/usr/obj/usr/src/tmp/usr/include/ctype.h:143: warning: `__istype' defined but not used >/usr/obj/usr/src/tmp/usr/include/ctype.h:157: warning: `__toupper' defined but not used >/usr/obj/usr/src/tmp/usr/include/ctype.h:164: warning: `__tolower' defined but not used >*** Error code 1 This is caused by dubious configuration: 1) you don't have -O in CFLAGS for some reason (it looks like you have -pipe without -O in /etc/make.conf). 2) libskey/Makefile now puts -W in CFLAGS. In combination with (1), this causes gcc t emit a warning for every static inline declaration in every header file that it parses. 3) libskey now puts -Werror in CFLAGS. This makes the combination of (1) and (2) fatal. In other words, libskey is now broken even in -stable if -O isn't in CFLAGS. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 28 22:16:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA25384 for freebsd-stable-outgoing; Sat, 28 Feb 1998 22:16:53 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from emu.sourcee.com (emu.sourcee.com [199.201.159.173]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25125; Sat, 28 Feb 1998 22:16:16 -0800 (PST) (envelope-from nrice@emu.sourcee.com) Received: (from nrice@localhost) by emu.sourcee.com (8.8.8/8.8.3) id BAA25861; Sun, 1 Mar 1998 01:15:01 -0500 (EST) Message-ID: <19980301011501.02816@emu.sourcee.com> Date: Sun, 1 Mar 1998 01:15:01 -0500 From: Norman C Rice To: Bruce Evans Cc: dkelly@HiWAAY.net, freebsd-stable@FreeBSD.ORG, pst@FreeBSD.ORG Subject: Re: Tonight's cvsup'ed -stable fails "make buildword" References: <199803010536.QAA32286@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199803010536.QAA32286@godzilla.zeta.org.au>; from Bruce Evans on Sun, Mar 01, 1998 at 04:36:42PM +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Sun, Mar 01, 1998 at 04:36:42PM +1100, Bruce Evans wrote: > >===> libscsi > >cc -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libscsi/scsi.c -o scsi.o > >building standard scsi library > >ranlib libscsi.a > >cc -fpic -DPIC -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libscsi/scsi.c -o scsi.so > >building shared scsi library (version 2.0) > >===> libskey > >cc -pipe -DPERMIT_CONSOLE -D_SKEY_INTERNAL -I/usr/src/lib/libskey -W -Wall -Werror -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libskey/skeyaccess.c -o skeyaccess.o > >cc1: warnings being treated as errors > >/usr/obj/usr/src/tmp/usr/include/stdio.h:366: warning: `__sputc' defined but not used > >/usr/obj/usr/src/tmp/usr/include/ctype.h:143: warning: `__istype' defined but not used > >/usr/obj/usr/src/tmp/usr/include/ctype.h:157: warning: `__toupper' defined but not used > >/usr/obj/usr/src/tmp/usr/include/ctype.h:164: warning: `__tolower' defined but not used > >*** Error code 1 > > This is caused by dubious configuration: > 1) you don't have -O in CFLAGS for some reason (it looks like you have > -pipe without -O in /etc/make.conf). > 2) libskey/Makefile now puts -W in CFLAGS. In combination with (1), this > causes gcc t emit a warning for every static inline declaration in > every header file that it parses. > 3) libskey now puts -Werror in CFLAGS. This makes the combination of > (1) and (2) fatal. > > In other words, libskey is now broken even in -stable if -O isn't in CFLAGS. It also appears that `lpr' is broken for similar reasons. -- Regards, Norman C. Rice, Jr. > > Bruce > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 28 23:06:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02629 for freebsd-stable-outgoing; Sat, 28 Feb 1998 23:06:35 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA02621; Sat, 28 Feb 1998 23:06:26 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id SAA02404; Sun, 1 Mar 1998 18:00:45 +1100 Date: Sun, 1 Mar 1998 18:00:45 +1100 From: Bruce Evans Message-Id: <199803010700.SAA02404@godzilla.zeta.org.au> To: bde@zeta.org.au, nrice@emu.sourcee.com Subject: Re: Tonight's cvsup'ed -stable fails "make buildword" Cc: dkelly@HiWAAY.net, freebsd-stable@FreeBSD.ORG, pst@FreeBSD.ORG, wollman@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk >> >cc1: warnings being treated as errors >> >/usr/obj/usr/src/tmp/usr/include/stdio.h:366: warning: `__sputc' defined but not used >> ... >> In other words, libskey is now broken even in -stable if -O isn't in CFLAGS. > >It also appears that `lpr' is broken for similar reasons. Yes, lpr doesn't put -W in CFLAGS (this in combination with -Werror would break lpr in CFLAGS because of warnings about sign mismatches), but the "defined but not used warnings" are actually enabled by -Wunused and -Wall, and lpr puts -Wall in CFLAGS. Unused statics in "standard" headers are never reported, but buildworld installs the standard headers in nonstandard places, and gcc's test for standardness is simplistic. The warning can be prevented by declaring all possibly-unused static functions and objects in headers as having attribute __unused: #include static __inline int __sputc(int _c, FILE *_p) __unused; static __inline int __sputc(int _c, FILE *_p) { ... } I don't know how to attach the attribute to the function definition here. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message