From owner-freebsd-stable Sun Sep 21 00:03:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA18238 for stable-outgoing; Sun, 21 Sep 1997 00:03:05 -0700 (PDT) Received: from counterintelligence.ml.org ([209.76.130.180]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA18233 for ; Sun, 21 Sep 1997 00:03:01 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id XAA00272; Sat, 20 Sep 1997 23:53:50 -0700 (PDT) Date: Sat, 20 Sep 1997 23:53:50 -0700 (PDT) From: "Jamil J. Weatherbee" To: "Jordan K. Hubbard" cc: freebsd-stable@FreeBSD.ORG Subject: Re: pppd man page In-Reply-To: <973.874810628@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I think send-pr's are a pain in the ass, I did one once for the floppy driver about 6 months ago, but got a email back stating it wasn't ??specific?? enough, can't we just email our little bugs informally to some mailbox? Not to mention that I was annoyed enough about it I just let go of sending another send-pr and noone really paid attention to the bug until someone else stumbled upon it a few weeks ago (you've probably seen the numerous posts on that issue) > Jordan > > P.S. send-pr(1) or http://www.freebsd.org/send-pr.html - your choice. > From owner-freebsd-stable Sun Sep 21 00:27:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA19357 for stable-outgoing; Sun, 21 Sep 1997 00:27:52 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA19350 for ; Sun, 21 Sep 1997 00:27:49 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id AAA27096; Sun, 21 Sep 1997 00:28:08 -0700 (PDT) To: "Jamil J. Weatherbee" cc: freebsd-stable@FreeBSD.ORG Subject: Re: pppd man page In-reply-to: Your message of "Sat, 20 Sep 1997 23:53:50 PDT." Date: Sun, 21 Sep 1997 00:28:08 -0700 Message-ID: <27093.874826888@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I think send-pr's are a pain in the ass, I did one once for the floppy > driver about 6 months ago, but got a email back stating it wasn't > ??specific?? enough, can't we just email our little bugs informally to > some mailbox? Not to mention that I was annoyed enough about it I just No. Jordan From owner-freebsd-stable Sun Sep 21 01:14:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA21300 for stable-outgoing; Sun, 21 Sep 1997 01:14:00 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA21294 for ; Sun, 21 Sep 1997 01:13:57 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id RAA24163; Sun, 21 Sep 1997 17:51:39 +1000 Date: Sun, 21 Sep 1997 17:51:39 +1000 From: Bruce Evans Message-Id: <199709210751.RAA24163@godzilla.zeta.org.au> To: j@uriah.heep.sax.de, stable@freebsd.org Subject: Re: Another NFS bogon in 2.2-stable? Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Did anybody else notice that shutting down a 2.2-stable machine that >has NFS file systems mounted never yields a clean shutdown? My 2.2 I notice it in -current for a nfs-mounted /usr. It is caused by some daemons holding nfs files open and taking too long to die. I use `umount -Af -t nfs' before rebooting. This tends to kill the daemons early when their fd's go away. Bruce From owner-freebsd-stable Sun Sep 21 01:38:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA21965 for stable-outgoing; Sun, 21 Sep 1997 01:38:00 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA21959 for ; Sun, 21 Sep 1997 01:37:21 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id SAA29097; Sun, 21 Sep 1997 18:34:57 +1000 (EST) Date: Sun, 21 Sep 1997 18:34:56 +1000 (EST) From: "Daniel O'Callaghan" To: "Jamil J. Weatherbee" cc: freebsd-stable@FreeBSD.ORG Subject: Re: pppd man page In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 20 Sep 1997, Jamil J. Weatherbee wrote: > I think send-pr's are a pain in the ass, I did one once for the floppy > driver about 6 months ago, but got a email back stating it wasn't > ??specific?? enough, can't we just email our little bugs informally to Well, I can't say I found your recent e-mails to -hackers specific enough for me to know how you suggest the problems are solved. The man page of pppd refers to Linux. Hmm, that's probably because the program is an imported source and is designed to compile for Linux as well as *BSD. All you did was state a fact, rather than suggesting discussion on whether it was a problem. Danny From owner-freebsd-stable Sun Sep 21 01:49:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA22275 for stable-outgoing; Sun, 21 Sep 1997 01:49:58 -0700 (PDT) Received: from pegasus.com (pegasus.com [206.127.225.31]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA22265 for ; Sun, 21 Sep 1997 01:49:52 -0700 (PDT) Received: by pegasus.com (8.6.8/PEGASUS-2.2) id WAA09135; Sat, 20 Sep 1997 22:49:31 -1000 Date: Sat, 20 Sep 1997 22:49:31 -1000 From: richard@pegasus.com (Richard Foulk) Message-Id: <199709210849.WAA09135@pegasus.com> In-Reply-To: "Jamil J. Weatherbee" "Re: pppd man page" (Sep 20, 11:53pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: freebsd-stable@FreeBSD.ORG Subject: Re: pppd man page Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk } > } > P.S. send-pr(1) or http://www.freebsd.org/send-pr.html - your choice. } > } } I think send-pr's are a pain in the ass, I did one once for the floppy } driver about 6 months ago, but got a email back stating it wasn't } ??specific?? enough, can't we just email our little bugs informally to } some mailbox? Not to mention that I was annoyed enough about it I just } let go of sending another send-pr and noone really paid attention to the } bug until someone else stumbled upon it a few weeks ago (you've probably } seen the numerous posts on that issue) } Supporting FreeBSD is probably a `pain in the ass' sometimes for the folks that put so much into it for the rest of us. Especially when we don't give them a little help when we can. FreeBSD is a cooperative effort. When you find a bug, think of it as an opportunity to contribute. Try to provide as much information as you possibly can, to make it easier for someone to repeat the problem. FreeBSD is better than commercial software. And it is different. Don't expect service in the same way you would from a commercial vendor. It's not only unfair, it's inconsiderate, and kind of dumb. Service with FreeBSD is better, but it's like when you ask a friend to help you, not someone you've paid a large sum of money to. Let's not be pushy with our friends. Thanks Richard From owner-freebsd-stable Sun Sep 21 03:51:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA25570 for stable-outgoing; Sun, 21 Sep 1997 03:51:00 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id DAA25551; Sun, 21 Sep 1997 03:50:46 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA23812; Sun, 21 Sep 1997 12:50:44 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id MAA08389; Sun, 21 Sep 1997 12:26:11 +0200 (MET DST) Message-ID: <19970921122611.AG59280@uriah.heep.sax.de> Date: Sun, 21 Sep 1997 12:26:11 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: stable@freebsd.org Cc: current@freebsd.org Subject: Re: rc.shutdown [was: Another NFS bogon in 2.2-stable?] References: <199709210751.RAA24163@godzilla.zeta.org.au> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Bruce Evans wrote: > >Did anybody else notice that shutting down a 2.2-stable machine that > >has NFS file systems mounted never yields a clean shutdown? My 2.2 > > I notice it in -current for a nfs-mounted /usr. It is caused by > some daemons holding nfs files open and taking too long to die. > I use `umount -Af -t nfs' before rebooting. This tends to kill > the daemons early when their fd's go away. (Since you confirm it for -current, too, i've moved the discussion there. Please respect the reply-to.) In my case, it's probably the daemons running off the NFS-mounted /usr/local then. Should we ship an /etc/rc.shutdown by default, that kills off the daemons and unmounts NFS file systems? At least daemons that properly recorded their PID in /var/run/*pid could be killed easily. The following looks like a pretty good default rc.shutdown to me. The idea behind it is also that you can shutdown to single-user, and get an as clean as possible environment. (I didn't make up my mind about non-NFS filesystems, however. This might cause some LKMs to remain busy.) The mess to umount NFS filesystems could be replaced by `umount -Af -t nfs' in -current, but the -A option isn't available yet in 2.2-stable. Does -A correctly handle /etc/fstab reverse order, IOW, would it work if e.g. both /usr, and /usr/local were NFS-mounted? For some unknown reason, this script isn't really run on my 2.2 test machine when doing a `shutdown -h/-r', albeit it is run when doing a plain shutdown to single-user, as well as when typing Ctrl-Alt-Del. Looks like intention, but is IMHO bogus. If i type `shutdown -r', i expect it do perform a clean reboot. (This is the only way to do it when not sitting on the physical console.) Would anybody mind me committing the following script? #!/bin/sh stty status '^T' HOME=/; export HOME PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin export PATH echo -n "Stopping system daemons:" # # Stop by reverse PID order. Not ideal. for file in /var/run/*.pid; do if [ "$file" = "/var/run/*.pid" ]; then break fi pid=$(head -1 "$file") # sendmail needs head -1 name=$(expr "$file" : '/var/run/\(.*\)\.pid') pidlist="$pidlist$pid $name " done echo "$pidlist" | sort -n -r | while read pid name; do if [ "$pid" = "" ]; then break fi echo -n " $name" kill -TERM $pid && rm -f /var/run/$name.pid done echo '.' echo -n "Unloading kernel modules:" modstat | ( read junk # headline while read type id off loadaddr size info rev name; do echo -n " $name" modunload -i $id done ) echo '.' echo -n "Unmounting NFS filesystems:" nfslist=$( mount -t nfs | while read resource on mntpoint junk; do echo "$resource $mntpoint" done ) echo "$nfslist" | while read resource mntpoint; do if [ "$mntpoint" = ""]; then break fi echo -n " $resource" umount -f "$mntpoint" done echo '.' echo -n "Bringing down network interfaces:" ifconfig -a | while read line; do if iface=$(expr "$line" : '\([a-z][a-z]*[0-9][0-9]*\):'); then echo -n " $iface" ifconfig $iface down ifface="$iface" fi if ipaddr=$(expr "$line" : ' *inet \([0-9]*\.[0-9]*\.[0-9]*\.[0-9]*\)' then echo -n " $ipaddr" ifconfig $ifface $ipaddr delete fi done echo '.' -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-stable Sun Sep 21 04:21:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA26499 for stable-outgoing; Sun, 21 Sep 1997 04:21:58 -0700 (PDT) Received: from sinbin.demos.su (sinbin.demos.su [194.87.0.31]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id EAA26492 for ; Sun, 21 Sep 1997 04:21:51 -0700 (PDT) Received: by sinbin.demos.su id PAA20344; (8.6.12/D) Sun, 21 Sep 1997 15:21:05 +0400 From: bag@sinbin.demos.su (Alex G. Bulushev) Message-Id: <199709211121.PAA20344@sinbin.demos.su> Subject: Re: >8 char usernames going into 2.2.5? In-Reply-To: from "Tom" at "Sep 19, 97 03:48:01 pm" X-ELM-OSV: (Our standard violations) no-mime=1; no-hdr-encoding=1 To: tom@uniserve.com (Tom) Date: Sun, 21 Sep 1997 15:21:05 +0400 (MSD) Cc: Studded@dal.net, freebsd-stable@freebsd.org X-Mailer: ELM [version 2.4ME+ PL32 (25)] Content-Type: text Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > On Fri, 19 Sep 1997, Studded wrote: > > ... > > While I'm askin', it would be nice if some chars besides > > letters and numbers could sneak in there too. The one I would like > > most is - (the dash) but I know there are other requests. (And yes, I > > know about aliases. :) > > That is the foolish "adduser" imposing restrictions on you. "-" works > perfectly fine in userids. I use "-", and "_" in usernames regularly, but > I use a rather strange "adduser" that predates the one in FreeBSD. some problem exist to use "-" in the user names with rlogin rlogind check "-" ... but rlogin is not popular now ... slogin is :) Alex. > > "adduser" is in perl. Just fix it.. err... _modify_ it :) > > > Thanks for your input, > > > > Doug > > > > Do thou amend thy face, > > and I'll amend my life. > > -Shakespeare, "Henry V" > > > > > > Tom > > From owner-freebsd-stable Sun Sep 21 07:04:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA01715 for stable-outgoing; Sun, 21 Sep 1997 07:04:33 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA01693 for ; Sun, 21 Sep 1997 07:04:27 -0700 (PDT) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id PAA27908; Sun, 21 Sep 1997 15:00:46 +0100 (BST) Message-Id: <199709211400.PAA27908@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jamil J. Weatherbee" cc: "Jordan K. Hubbard" , freebsd-stable@FreeBSD.ORG Subject: Re: pppd man page In-reply-to: Your message of "Sat, 20 Sep 1997 23:53:50 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Sep 1997 15:00:46 +0100 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I think send-pr's are a pain in the ass, I did one once for the floppy > driver about 6 months ago, but got a email back stating it wasn't > ??specific?? enough, can't we just email our little bugs informally to > some mailbox? Not to mention that I was annoyed enough about it I just > let go of sending another send-pr and noone really paid attention to the > bug until someone else stumbled upon it a few weeks ago (you've probably > seen the numerous posts on that issue) The best you can do here, if you *know* who the maintainer for the piece of code with the problem is, is cc that person. Certainly, in my case, the cc'd mail will get into my inbox as distinct to the "bugs mailbox", and will get seen first :-) Of course not everyone that subscribes to freebsd-bugs will appreciate seeing the same piece of mail twice :-| -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-stable Sun Sep 21 07:44:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA02915 for stable-outgoing; Sun, 21 Sep 1997 07:44:54 -0700 (PDT) Received: from david.siemens.de (david.siemens.de [139.23.36.11]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA02909 for ; Sun, 21 Sep 1997 07:44:51 -0700 (PDT) Received: from salomon.mchp.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.8.7/8.8.5) with ESMTP id QAA00391 for ; Sun, 21 Sep 1997 16:44:38 +0200 (MDT) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by salomon.mchp.siemens.de (8.8.7/8.8.5) with ESMTP id QAA22026 for ; Sun, 21 Sep 1997 16:44:49 +0200 (MDT) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.7/8.8.7) id QAA14700 for ; Sun, 21 Sep 1997 16:44:48 +0200 (MET DST) From: Andre Albsmeier Message-Id: <199709211444.QAA28591@curry.mchp.siemens.de> Subject: Bug in wd.c when using devfs To: freebsd-stable@freebsd.org Date: Sun, 21 Sep 1997 16:44:40 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, when using devfs on 2.2-STABLE with 3 IDE drives, I saw that wd2 doesn't appear in /devs. Instead, when booting, the kernel prints a message that wd0 (yes, wd0) is already present. IMHO this is due to a bug in wd.c: When calling the devfs routines, the variable unit is passed instead of lunit. As far as I am correct, unit refers to the physical unit on the controller wdc which is 0 for wd2. And lunit refers to the logical unit which is 2 for wd2. So the kernel thinks, wd0 should be registered once more and complains. I have attached my changes to wd.c which makes it work. Please tell me if this is correct, and I send in a PR. Maybe, this applies to 2.1 and current, too. Thanks, -Andre *** wd.c.ORI Sun Sep 21 14:38:19 1997 --- wd.c Sun Sep 21 14:50:16 1997 *************** *** 478,492 **** wdtimeout(du); #ifdef DEVFS ! mynor = dkmakeminor(unit, WHOLE_DISK_SLICE, RAW_PART); du->dk_bdev = devfs_add_devswf(&wd_bdevsw, mynor, DV_BLK, UID_ROOT, GID_OPERATOR, 0640, ! "wd%d", unit); du->dk_cdev = devfs_add_devswf(&wd_cdevsw, mynor, DV_CHR, UID_ROOT, GID_OPERATOR, 0640, ! "rwd%d", unit); #endif if (dk_ndrive < DK_NDRIVE) { --- 478,492 ---- wdtimeout(du); #ifdef DEVFS ! mynor = dkmakeminor(lunit, WHOLE_DISK_SLICE, RAW_PART); du->dk_bdev = devfs_add_devswf(&wd_bdevsw, mynor, DV_BLK, UID_ROOT, GID_OPERATOR, 0640, ! "wd%d", lunit); du->dk_cdev = devfs_add_devswf(&wd_cdevsw, mynor, DV_CHR, UID_ROOT, GID_OPERATOR, 0640, ! "rwd%d", lunit); #endif if (dk_ndrive < DK_NDRIVE) { From owner-freebsd-stable Sun Sep 21 09:42:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA07090 for stable-outgoing; Sun, 21 Sep 1997 09:42:31 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA07084 for ; Sun, 21 Sep 1997 09:42:27 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id KAA05191; Sun, 21 Sep 1997 10:42:25 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA27169; Sun, 21 Sep 1997 10:42:23 -0600 (MDT) Date: Sun, 21 Sep 1997 10:42:23 -0600 (MDT) Message-Id: <199709211642.KAA27169@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: stable@freebsd.org Subject: Re: Another NFS bogon in 2.2-stable? In-Reply-To: <19970921083931.CS53038@uriah.heep.sax.de> References: <19970921083931.CS53038@uriah.heep.sax.de> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Did anybody else notice that shutting down a 2.2-stable machine that > has NFS file systems mounted never yields a clean shutdown? My 2.2 > scratchbox always jams with a `2 2 2 2 2 giving up' display, and comes > up again with the clean flag not set in the UFS filesystems. Hmm, all I can say is that it works for me. FreeBSD moth.mt.sri.com 2.2-STABLE FreeBSD 2.2-STABLE #15: Wed Sep 3 13:09:12 MDT 1997 The kernel is a bit out of date, but I just did an update and will be building a more recent one. The server is a Solaris 2.5 box, if that makes any difference. Nate From owner-freebsd-stable Sun Sep 21 09:57:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA07591 for stable-outgoing; Sun, 21 Sep 1997 09:57:04 -0700 (PDT) Received: from kelly.prima.ruhr.de (root@kelly.prima.ruhr.de [141.39.232.1]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA07586 for ; Sun, 21 Sep 1997 09:57:01 -0700 (PDT) Received: from chokepnt.prima.ruhr.de (DialPPP-1-207.rz.ruhr-uni-bochum.de [134.147.1.207]) by kelly.prima.ruhr.de (8.6.11/8.6.9) with SMTP id SAA23864; Sun, 21 Sep 1997 18:56:51 +0200 Message-ID: <341F198D.41C67EA6@prima.ruhr.de> Date: Wed, 17 Sep 1997 01:43:09 +0200 From: Philipp Reichmuth X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2-STABLE i386) MIME-Version: 1.0 To: Ollivier Robert CC: stable@freebsd.org Subject: Re: Fwd: K6 Linux Re-Compile Issue References: <199709131748.NAA09633@sabre.goldsword.com> <19970914024348.21276@keltia.freenix.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ollivier Robert wrote: > > According to John T. Farmer: > > When you get yours & verify that the problem is fixed, _please_ forward > > details such as rev. numbers & stepping so that we can be sure to get > > the new ones... > > AFAIK, K6 with a revision # higher than 9730 should be good. AFAIK it's 9731, but what the heck ;) I'm going to have mine swapped next week and see what happens. (I'm still down in the CTM 370's with my make worlds :( ) Philipp From owner-freebsd-stable Sun Sep 21 11:25:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA11144 for stable-outgoing; Sun, 21 Sep 1997 11:25:28 -0700 (PDT) Received: from dfw-ix11.ix.netcom.com (dfw-ix11.ix.netcom.com [206.214.98.11]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA11139 for ; Sun, 21 Sep 1997 11:25:25 -0700 (PDT) Received: (from smap@localhost) by dfw-ix11.ix.netcom.com (8.8.4/8.8.4) id NAA08415 for ; Sun, 21 Sep 1997 13:24:51 -0500 (CDT) Received: from stl-mo8-18.ix.netcom.com(205.187.206.82) by dfw-ix11.ix.netcom.com via smap (V1.3) id rma008394; Sun Sep 21 13:24:34 1997 Message-ID: <342520D9.6421CA77@ix.netcom.com> Date: Sun, 21 Sep 1997 13:27:53 +0000 From: Jerry Hicks Organization: Norml X-Mailer: Mozilla 4.02b7 [en] (X11; I; FreeBSD 2.2-STABLE i386) MIME-Version: 1.0 To: stable@FreeBSD.org Subject: Re: rc.shutdown [was: Another NFS bogon in 2.2-stable?] References: <199709210751.RAA24163@godzilla.zeta.org.au> <19970921122611.AG59280@uriah.heep.sax.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk shouldn't the file be removed unconditionally? As Joerg Wunsch wrote: > > kill -TERM $pid && rm -f /var/run/$name.pid From owner-freebsd-stable Sun Sep 21 13:46:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA16170 for stable-outgoing; Sun, 21 Sep 1997 13:46:54 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA16165 for ; Sun, 21 Sep 1997 13:46:46 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id NAA08555 for ; Sun, 21 Sep 1997 13:46:40 -0700 (PDT) Date: Sun, 21 Sep 1997 13:46:39 -0700 (PDT) From: "Jamil J. Weatherbee" To: freebsd-stable@freebsd.org Subject: Star Office Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I did a make on this port --- can someone explain what the deal with it is -- I was reading calderas web page, Is this a commercial procduct (or demo) is everything not supposed to work right or what? How did this get ported to freebsd in the first place -- is there a native port to be done as a commercial product? From owner-freebsd-stable Sun Sep 21 14:29:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA17682 for stable-outgoing; Sun, 21 Sep 1997 14:29:18 -0700 (PDT) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA17661 for ; Sun, 21 Sep 1997 14:29:10 -0700 (PDT) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xCtYj-0005Tp-00; Sun, 21 Sep 1997 14:28:53 -0700 Date: Sun, 21 Sep 1997 14:28:49 -0700 (PDT) From: Tom To: "Alex G. Bulushev" cc: Studded@dal.net, freebsd-stable@freebsd.org Subject: Re: >8 char usernames going into 2.2.5? In-Reply-To: <199709211121.PAA20344@sinbin.demos.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 21 Sep 1997, Alex G. Bulushev wrote: > > On Fri, 19 Sep 1997, Studded wrote: > > > > ... > > > While I'm askin', it would be nice if some chars besides > > > letters and numbers could sneak in there too. The one I would like > > > most is - (the dash) but I know there are other requests. (And yes, I > > > know about aliases. :) > > > > That is the foolish "adduser" imposing restrictions on you. "-" works > > perfectly fine in userids. I use "-", and "_" in usernames regularly, but > > I use a rather strange "adduser" that predates the one in FreeBSD. > > some problem exist to use "-" in the user names with rlogin > rlogind check "-" ... but rlogin is not popular now ... slogin is :) > > Alex. rlogind used to be too strict and not allow "-" at all, but I belive it now only fails if the first character is "-". Tom From owner-freebsd-stable Sun Sep 21 14:54:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA19916 for stable-outgoing; Sun, 21 Sep 1997 14:54:57 -0700 (PDT) Received: from usr03.primenet.com (root@usr03.primenet.com [206.165.6.203]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA19908 for ; Sun, 21 Sep 1997 14:54:53 -0700 (PDT) Received: from primenet.com (root@mailhost01.primenet.com [206.165.5.52]) by usr03.primenet.com (8.8.5/8.8.5) with ESMTP id OAA08417; Sun, 21 Sep 1997 14:54:37 -0700 (MST) Received: from foo.primenet.com (ip204.sjc.primenet.com [206.165.96.204]) by primenet.com (8.8.5/8.8.5) with ESMTP id OAA18809; Sun, 21 Sep 1997 14:54:35 -0700 (MST) Received: (from bkogawa@localhost) by foo.primenet.com (8.8.6/8.8.6) id PAA18877; Sun, 21 Sep 1997 15:01:08 -0700 (PDT) Date: Sun, 21 Sep 1997 15:01:08 -0700 (PDT) Message-Id: <199709212201.PAA18877@foo.primenet.com> To: jamil@counterintelligence.ml.org Subject: Re: Star Office Newsgroups: localhost.freebsd.stable References: From: "Bryan K. Ogawa" Cc: freebsd-stable@FreeBSD.ORG X-Newsreader: NN version 6.5.0 #1 (NOV) Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In localhost.freebsd.stable you write: >I did a make on this port --- can someone explain what the deal with it is >-- I was reading calderas web page, Is this a commercial procduct (or >demo) is everything not supposed to work right or what? How did this get >ported to freebsd in the first place -- is there a native port to be done >as a commercial product? Q: How did it get ported to FreeBSD? A. Unless we're talking about different versions of the software, it's Linux software, so it's running under the Linux emulation. If you mean "how did we get our hands on binaries", the educational/nonprofit/evaluation version is available via public FTP (look at the Makefile for where). Q: Is this a commercial product? A: Yes. Caldera carries it. Q: Is it available for free on the Internet? A: Yes. See above. If I have understood the license (I Am Not A Lawyer), you can use it if you're a non-profit or educational user, or evaluate it if you are a commercial or non-commercial user. If you are a commercial user, you can evaluate it for 90 days; if you are a non-commercial user, you can "evaluate" it as long as you want to. The literature seems to indicate that StarDivision fully expects individuals to take advantage of the unlimited evaluation period for it. Q: Is there a native port in the works? A: I heard some rumbling about this as part of a commercial FreeBSD offering, but nothing beyond that. Does anyone know the status of the whole commercial FreeBSD offering thing (with XAccel, etc.?)? -- bryan k ogawa http://www.primenet.com/~bkogawa/ From owner-freebsd-stable Sun Sep 21 15:30:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA21750 for stable-outgoing; Sun, 21 Sep 1997 15:30:57 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA21743 for ; Sun, 21 Sep 1997 15:30:52 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id PAA00192 for ; Sun, 21 Sep 1997 15:30:47 -0700 (PDT) Date: Sun, 21 Sep 1997 15:30:47 -0700 (PDT) From: "Jamil J. Weatherbee" To: freebsd-stable@freebsd.org Subject: Not A Problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Anyone else noticed problems with the console (like it not coming back) when closing down from X under heavy load (like while doing a make world), the machine will reboot via ctrl-alt-del, and I think you can log in remotely, so It seems like it is just a console thing. Is there a way to log in remotely and recover the console? From owner-freebsd-stable Sun Sep 21 18:03:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA29257 for stable-outgoing; Sun, 21 Sep 1997 18:03:43 -0700 (PDT) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA29252 for ; Sun, 21 Sep 1997 18:03:40 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with ESMTP id VAA29439; Sun, 21 Sep 1997 21:03:37 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPAN/970608) with ESMTP id VAA07192; Sun, 21 Sep 1997 21:03:37 -0400 (EDT) To: Tom cc: Rob Miracle , freebsd-stable@FreeBSD.ORG From: "Gary Palmer" Subject: Re: >8 char usernames going into 2.2.5? In-reply-to: Your message of "Fri, 19 Sep 1997 14:17:20 PDT." Date: Sun, 21 Sep 1997 21:03:36 -0400 Message-ID: <7190.874890216@orion.webspan.net> Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tom wrote in message ID : > Really useful? Like who has over 65,000 users in /etc/passwd anyhow? root@mail0:/# wc -l /etc/passwd 274200 /etc/passwd ahem Unfortunately not a FreeBSD box ... I don't think there are any PC's with the sort of hardware that machine needs (8 processors, 2gigs ram, etc) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-stable Sun Sep 21 18:06:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA29412 for stable-outgoing; Sun, 21 Sep 1997 18:06:52 -0700 (PDT) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA29404; Sun, 21 Sep 1997 18:06:42 -0700 (PDT) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xCwxJ-0006JK-00; Sun, 21 Sep 1997 18:06:29 -0700 Date: Sun, 21 Sep 1997 18:06:24 -0700 (PDT) From: Tom To: Gary Palmer cc: Rob Miracle , freebsd-stable@freebsd.org Subject: Re: >8 char usernames going into 2.2.5? In-Reply-To: <7190.874890216@orion.webspan.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 21 Sep 1997, Gary Palmer wrote: > Tom wrote in message ID > : > > Really useful? Like who has over 65,000 users in /etc/passwd anyhow? > > root@mail0:/# wc -l /etc/passwd > 274200 /etc/passwd > > ahem > > Unfortunately not a FreeBSD box ... I don't think there are any PC's > with the sort of hardware that machine needs (8 processors, 2gigs ram, > etc) And I really doubt that you're limited to 8 characters usernames on such a system. > Gary > -- > Gary Palmer FreeBSD Core Team Member > FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info > Tom From owner-freebsd-stable Sun Sep 21 18:51:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA01559 for stable-outgoing; Sun, 21 Sep 1997 18:51:07 -0700 (PDT) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA01553 for ; Sun, 21 Sep 1997 18:50:58 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with ESMTP id VAA07240; Sun, 21 Sep 1997 21:50:56 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPAN/970608) with ESMTP id VAA23207; Sun, 21 Sep 1997 21:50:56 -0400 (EDT) To: Tom cc: Rob Miracle , freebsd-stable@freebsd.org From: "Gary Palmer" Subject: Re: >8 char usernames going into 2.2.5? In-reply-to: Your message of "Sun, 21 Sep 1997 18:06:24 PDT." Date: Sun, 21 Sep 1997 21:50:56 -0400 Message-ID: <23205.874893056@orion.webspan.net> Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Tom wrote in message ID : > > root@mail0:/# wc -l /etc/passwd > > 274200 /etc/passwd > And I really doubt that you're limited to 8 characters usernames on such > a system. Our systems were not upgraded to handle more than 8 char logins until relatively recently (i.e. last month or so). What chanes were needed is unknown as I wasn't involved. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-stable Sun Sep 21 18:54:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA01687 for stable-outgoing; Sun, 21 Sep 1997 18:54:22 -0700 (PDT) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA01676 for ; Sun, 21 Sep 1997 18:54:15 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with ESMTP id VAA07775; Sun, 21 Sep 1997 21:54:13 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPAN/970608) with ESMTP id VAA24765; Sun, 21 Sep 1997 21:54:13 -0400 (EDT) To: John Robert LoVerso cc: Snob Art Genre , Tom , Studded , "freebsd-stable@freebsd.org" From: "Gary Palmer" Subject: Re: >8 char usernames going into 2.2.5 In-reply-to: Your message of "Sat, 20 Sep 1997 23:25:40 EDT." <199709210325.XAA14160@loverso.southborough.ma.us> Date: Sun, 21 Sep 1997 21:54:12 -0400 Message-ID: <24763.874893252@orion.webspan.net> Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk John Robert LoVerso wrote in message ID <199709210325.XAA14160@loverso.southborough.ma.us>: > The set of valid characters in usernames have nothing to do with what an > Internet RFC covers. It does have relevance if you want them to get mail, or other such useful functions. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-stable Sun Sep 21 22:10:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA12683 for stable-outgoing; Sun, 21 Sep 1997 22:10:04 -0700 (PDT) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA12676 for ; Sun, 21 Sep 1997 22:10:01 -0700 (PDT) Received: from localhost (spork@localhost) by super-g.inch.com (8.8.7/8.8.5) with SMTP id BAA21041; Mon, 22 Sep 1997 01:28:54 -0400 (EDT) Date: Mon, 22 Sep 1997 01:28:53 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: Joerg Wunsch cc: stable@FreeBSD.ORG Subject: Re: Another NFS bogon in 2.2-stable? In-Reply-To: <19970921083931.CS53038@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Is it just me or is there another bug involving 2 FBSD machines running -stable and nfsv2 or v3? In the above situation, if machine A is exporting a directory to machine B and machine A dies unexpectedly, you cannot umount the nfs-mounted directory; the command just hangs forever. "mount" will hang forever as well. Killing off any nfs processes will not help (brutal I thought, but worth a try). Remounting can be difficult, and sometimes a reboot is required. Am I doing something terribly wrong? I'm not doing anything out of the ordinary, I let the startup script do everything, and I'm only exporting one directory. Charles On Sun, 21 Sep 1997, J Wunsch wrote: > (Please drop me a Cc of this conversation, i'm not subscribed to this > list.) > > Did anybody else notice that shutting down a 2.2-stable machine that > has NFS file systems mounted never yields a clean shutdown? My 2.2 > scratchbox always jams with a `2 2 2 2 2 giving up' display, and comes > up again with the clean flag not set in the UFS filesystems. > > If i shutdown to single-user, manually umount the NFS filesystems, and > then type `halt', all works as expected. > > The machine is not the fastest on earth (386/40), maybe this is what > uncovers this problem? > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) > From owner-freebsd-stable Sun Sep 21 22:13:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA13020 for stable-outgoing; Sun, 21 Sep 1997 22:13:25 -0700 (PDT) Received: from shasta.wstein.com (joes@shasta.wstein.com [207.173.11.132]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA13010; Sun, 21 Sep 1997 22:13:21 -0700 (PDT) Received: (from joes@localhost) by shasta.wstein.com (8.8.7/8.8.7) id WAA00814; Sun, 21 Sep 1997 22:13:18 -0700 (PDT) From: Joseph Stein Message-Id: <199709220513.WAA00814@shasta.wstein.com> Subject: Help... Unexplained crashes under RELENG_2_2 (last message in syslog is from atrun) To: hackers@freebsd.org, stable@freebsd.org Date: Sun, 21 Sep 1997 22:13:18 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Over the course of the last four to six weeks, my system has been crashing unexpectedly (and of course, when I'm not home to coax it back to life). Today, it died, and rebooted itself, though not a soft reboot (like it used to do occasionally) -- it was a hard reboot... The last thing that is written to syslog() when it happens is messages like: Sep 21 17:00:00 shasta CRON[925]: (root) CMD (/usr/libexec/atrun) This system runs a plethora of daemons -- xntpd, named, sshd, httpd, ftpd, rwhod -- am I merely overloading it? Or is there some bug in at/atrun? I have coredumps enabled but have not yet seen anything in /var/run/crash from it. Should I just rebuild the world? (I'm going to anyway, and see if that helps). And, no, the power has not been out here today. (Other system is running just fine, and is identical except runs stock 2.1.7.) More information on request; not sure exactly what to send along with this. Here is some syslog() info; it has been edited to exclude the xntpd, named, and sendmail stuff. If you wish to examine the whole chunk from today, I'll have it available at ftp://shasta.wstein.com/pub/system/log.970921 (it's a *.* log so it's huge.) in short order (by the time you read this message.) Thanks for any help! Joe Stein ------------------- Syslog() stuff: Sep 21 17:00:00 shasta CRON[925]: (root) CMD (/usr/libexec/atrun) Sep 21 17:05:00 shasta CRON[931]: (root) CMD (/usr/libexec/atrun) Sep 21 17:10:00 shasta CRON[946]: (root) CMD (/usr/libexec/atrun) Sep 21 17:16:06 shasta /kernel: FreeBSD 2.2-STABLE #0: Sat Aug 23 20:00:30 PDT 1997 Sep 21 17:16:06 shasta /kernel: Features=0x1 Sep 21 17:16:07 shasta /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Sep 21 17:16:07 shasta /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Sep 21 17:16:08 shasta /kernel: sio1 not found at 0x3e8 Sep 21 17:16:08 shasta /kernel: sio2 at 0x2f8-0x2ff irq 3 on isa Sep 21 17:16:08 shasta /kernel: sio3 not found at 0x300 Sep 21 17:16:08 shasta /kernel: lpt0 at 0x378-0x37f irq 7 on isa Sep 21 17:16:09 shasta /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Sep 21 17:16:09 shasta /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa Sep 21 17:16:09 shasta /kernel: nca0 at 0x350-0x35f irq 5 on isa ... various CRON[xxx]: (root) CMD (/usr/libexec/atrun) every 5 minutes until I got home... Sep 21 21:51:52 shasta /kernel: FreeBSD 2.2-STABLE #0: Sat Aug 23 20:00:30 PDT 1997 Sep 21 21:51:53 shasta /kernel: Features=0x1 Sep 21 21:51:54 shasta /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Sep 21 21:51:54 shasta /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Sep 21 21:51:54 shasta /kernel: sio1 at 0x3e8-0x3ef irq 12 on isa Sep 21 21:51:55 shasta /kernel: sio2 at 0x2f8-0x2ff irq 3 on isa Sep 21 21:51:55 shasta /kernel: sio3 not found at 0x300 Sep 21 21:51:55 shasta /kernel: lpt0 at 0x378-0x37f irq 7 on isa Sep 21 21:51:55 shasta /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Sep 21 21:51:56 shasta /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa Sep 21 21:51:56 shasta /kernel: nca0 at 0x350-0x35f irq 5 on isa Output from dmesg(8): Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2-STABLE #0: Sat Aug 23 20:00:30 PDT 1997 root@shasta.wstein.com:/usr/src/sys/compile/S_ISDN CPU: AMD Enhanced Am486DX4 Write-Back (486-class CPU) Origin = "AuthenticAMD" Id = 0x494 Stepping=4 Features=0x1 real memory = 16777216 (16384K bytes) avail memory = 14848000 (14500K bytes) Probing for devices on PCI bus 0: chip0 rev 1 on pci0:16 chip1 rev 13 on pci0:18:0 pci0:18:1: UMC, device=0x673a, class=storage (ide) [no driver assigned] Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x3e8-0x3ef irq 12 on isa sio1: type 16550A sio2 at 0x2f8-0x2ff irq 3 on isa sio2: type 16550A sio3 not found at 0x300 lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 765 fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 3681MB (7539840 sectors), 7480 cyls, 16 heads, 63 S/T, 512 B/S nca0 at 0x350-0x35f irq 5 on isa nca0: type NCR-53C400 nca0 waiting for scsi devices to settle (nca0:2:0): "SANYO CRD-400I 1.32" type 5 removable SCSI 2 cd0(nca0:2:0): CD-ROM cd present [400000 x 2048 byte records] npx0 flags 0x1 on motherboard npx0: INT 16 interface From owner-freebsd-stable Sun Sep 21 23:12:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA17224 for stable-outgoing; Sun, 21 Sep 1997 23:12:11 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA17215 for ; Sun, 21 Sep 1997 23:12:07 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.71 #1) id 0xD1ip-0002rz-00; Sun, 21 Sep 1997 23:11:51 -0700 Date: Sun, 21 Sep 1997 23:11:51 -0700 (PDT) From: Tom To: Joseph Stein cc: stable@freebsd.org Subject: Re: Help... Unexplained crashes under RELENG_2_2 (last message in syslog is from atrun) In-Reply-To: <199709220513.WAA00814@shasta.wstein.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 21 Sep 1997, Joseph Stein wrote: > Over the course of the last four to six weeks, my system has been crashing > unexpectedly (and of course, when I'm not home to coax it back to life). > > Today, it died, and rebooted itself, though not a soft reboot (like it > used to do occasionally) -- it was a hard reboot... I don't understand. It rebooted itself, and it was a hard reboot? That isn't possible. Is a panic message displayed? > The last thing that is written to syslog() when it happens is messages like: > Sep 21 17:00:00 shasta CRON[925]: (root) CMD (/usr/libexec/atrun) Strange, cron messages are normally written to /var/cron/log. > This system runs a plethora of daemons -- xntpd, named, sshd, httpd, ftpd, > rwhod -- am I merely overloading it? Or is there some bug in at/atrun? atrun is an application, even if buggy it is not supposed to crash the system However, cron normally runs atrun every 5 minutes. It is probably _always_ the last log entry, because nothing else has happened yet. > I have coredumps enabled but have not yet seen anything in /var/run/crash > from it. > > Should I just rebuild the world? (I'm going to anyway, and see if that helps). > > And, no, the power has not been out here today. (Other system is running > just fine, and is identical except runs stock 2.1.7.) > > More information on request; not sure exactly what to send along with this. > > Here is some syslog() info; it has been edited to exclude the xntpd, named, and > sendmail stuff. If you wish to examine the whole chunk from today, I'll have > it available at > > ftp://shasta.wstein.com/pub/system/log.970921 (it's a *.* log so it's huge.) You put all the logs into one file? That is very odd, and definitely not how the default config works. > in short order (by the time you read this message.) > > Thanks for any help! Tom From owner-freebsd-stable Sun Sep 21 23:25:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA18195 for stable-outgoing; Sun, 21 Sep 1997 23:25:28 -0700 (PDT) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA18182; Sun, 21 Sep 1997 23:25:18 -0700 (PDT) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xD1vk-0007jm-00; Sun, 21 Sep 1997 23:25:12 -0700 Date: Sun, 21 Sep 1997 23:25:05 -0700 (PDT) From: Tom To: Gary Palmer cc: John Robert LoVerso , Snob Art Genre , Studded , "freebsd-stable@freebsd.org" Subject: Re: >8 char usernames going into 2.2.5 In-Reply-To: <24763.874893252@orion.webspan.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 21 Sep 1997, Gary Palmer wrote: > John Robert LoVerso wrote in message ID > <199709210325.XAA14160@loverso.southborough.ma.us>: > > The set of valid characters in usernames have nothing to do with what an > > Internet RFC covers. > > It does have relevance if you want them to get mail, or other such > useful functions. Hardly. The set of all possible legal unix usernames is only a small subset of the set of all possible RFC 821 local-parts. RFC 821 basically allows, given the right quoting, every possible ASCII character. So who want to allow whitepace in usernames? :) > Gary > -- > Gary Palmer FreeBSD Core Team Member > FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info > Tom From owner-freebsd-stable Mon Sep 22 00:18:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA21433 for stable-outgoing; Mon, 22 Sep 1997 00:18:27 -0700 (PDT) Received: from shasta.wstein.com (joes@shasta.wstein.com [207.173.11.132]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA21419 for ; Mon, 22 Sep 1997 00:18:22 -0700 (PDT) Received: (from joes@localhost) by shasta.wstein.com (8.8.7/8.8.7) id AAA00819; Mon, 22 Sep 1997 00:18:15 -0700 (PDT) From: Joseph Stein Message-Id: <199709220718.AAA00819@shasta.wstein.com> Subject: Re: Help... Unexplained crashes under RELENG_2_2 (last message in syslog is from atrun) In-Reply-To: from Tom at "Sep 21, 97 11:11:51 pm" To: tom@sdf.com (Tom) Date: Mon, 22 Sep 1997 00:18:15 -0700 (PDT) Cc: stable@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I don't understand. It rebooted itself, and it was a hard reboot? That > isn't possible. Is a panic message displayed? No panic message (that I know of). It may not have been a hard boot; but my PNP ISDN TA reset and was not probed when the system came back up. When I use 'reboot' or 'shutdown -r' that is not a problem -- the only time that I get that problem is when a hard boot occurs (and I'm not there to intervene with the DOS floppy... :( ) > > The last thing that is written to syslog() when it happens is messages like: > > Sep 21 17:00:00 shasta CRON[925]: (root) CMD (/usr/libexec/atrun) > > Strange, cron messages are normally written to /var/cron/log. And indeed they still are. I have a *.* /var/log/MASTER in my /etc/syslog.conf because when trying to figure out when or where something went "wrong" it's nice to get a big picture of what's happening on the whole system. > atrun is an application, even if buggy it is not supposed to crash the > system Yep. Like I said, the only two things that I know of are: o every time (except this most recent) the system locked up, the screen-saver (Daemon one) was frozen mid screen. o the atrun entry is the last one in the log file. > You put all the logs into one file? That is very odd, and definitely > not how the default config works. true enough. See response above. Thanks for your response, joe From owner-freebsd-stable Mon Sep 22 00:20:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA21634 for stable-outgoing; Mon, 22 Sep 1997 00:20:52 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA21628 for ; Mon, 22 Sep 1997 00:20:48 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA04983; Mon, 22 Sep 1997 09:20:44 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id JAA13849; Mon, 22 Sep 1997 09:02:36 +0200 (MET DST) Message-ID: <19970922090236.FF22331@uriah.heep.sax.de> Date: Mon, 22 Sep 1997 09:02:36 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: spork@super-g.com (spork) Cc: stable@FreeBSD.ORG Subject: Re: Another NFS bogon in 2.2-stable? References: <19970921083931.CS53038@uriah.heep.sax.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from spork on Sep 22, 1997 01:28:53 -0400 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As spork wrote: > Is it just me or is there another bug involving 2 FBSD machines running > -stable and nfsv2 or v3? > > In the above situation, if machine A is exporting a directory to machine B > and machine A dies unexpectedly, you cannot umount the nfs-mounted > directory; the command just hangs forever. That's normal if you told that the mount is `hard' (the default). It should however allow for umount -f nevertheless. I think this is a known problem. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-stable Mon Sep 22 03:26:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA04504 for stable-outgoing; Mon, 22 Sep 1997 03:26:34 -0700 (PDT) Received: from bunyip.cc.uq.edu.au (bunyip.cc.uq.edu.au [130.102.2.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA04496 for ; Mon, 22 Sep 1997 03:26:24 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.7/8.8.7) id UAA22851; Mon, 22 Sep 1997 20:25:49 +1000 Received: from troll.dtir.qld.gov.au (troll.dtir.qld.gov.au [167.123.8.1]) by ogre.dtir.qld.gov.au (8.8.7/8.8.7) with ESMTP id UAA02294; Mon, 22 Sep 1997 20:24:13 +1000 (EST) Received: from localhost (syssgm@localhost) by troll.dtir.qld.gov.au (8.8.5/8.8.5) with SMTP id UAA16455; Mon, 22 Sep 1997 20:27:09 +1000 (EST) Message-Id: <199709221027.UAA16455@troll.dtir.qld.gov.au> X-Authentication-Warning: troll.dtir.qld.gov.au: syssgm@localhost didn't use HELO protocol To: Snob Art Genre cc: freebsd-stable@FreeBSD.ORG, syssgm@dtir.qld.gov.au Subject: Re: No-go with read-only src tree References: In-Reply-To: from Snob Art Genre at "Fri, 19 Sep 1997 08:44:18 -0400" Date: Mon, 22 Sep 1997 20:27:08 +1000 From: Stephen McKay Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Friday, 19th September 1997, Snob Art Genre wrote: >It's trivial . . . just fix unionfs. :-) Unionfs will be a great toy some day. But for now, I don't need it to fix this problem. >On Fri, 19 Sep 1997, Stephen McKay wrote: > >> As the last step of the bootstrap, I see: >> >> /usr/obj/src/2.2-stable/usr.bin/lex created for /src/2.2-stable/usr.bin/lex >> >> but I DON'T see the expected lex/lib equivalent. Well, a bit of experimenting shows that this is caused by line 420 of the main Makefile: ${MAKE} ${MK_FLAGS} -DNOLIB all install ${CLEANDIR} ${OBJDIR} The -DNOLIB stuff says don't process the lib subdirectory. Unfortunately, when cleandir blows away the lex obj directory the lex/lib one goes too, and avoiding the lib subdirectory means that it doesn't get a replacement. My "fix" is to remove -DNOLIB. I've kicked off another read-only src build and will know how it went tomorrow morning. If this fixes all my problems, -DNOLIB will go. If not, I'll have to add a little extra cruft to specifically rebuild the lex/lib obj directory. If you know why there was a -DNOLIB there in the first place, speak up! Stephen. From owner-freebsd-stable Mon Sep 22 04:08:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA06212 for stable-outgoing; Mon, 22 Sep 1997 04:08:48 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA06207 for ; Mon, 22 Sep 1997 04:08:36 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id VAA09190; Mon, 22 Sep 1997 21:03:04 +1000 Date: Mon, 22 Sep 1997 21:03:04 +1000 From: Bruce Evans Message-Id: <199709221103.VAA09190@godzilla.zeta.org.au> To: benedict@echonyc.com, syssgm@dtir.qld.gov.au Subject: Re: No-go with read-only src tree Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >If this fixes all my problems, -DNOLIB will go. If not, I'll have to add a >little extra cruft to specifically rebuild the lex/lib obj directory. > >If you know why there was a -DNOLIB there in the first place, speak up! See the revision log. Bruce From owner-freebsd-stable Mon Sep 22 06:45:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA12807 for stable-outgoing; Mon, 22 Sep 1997 06:45:58 -0700 (PDT) Received: from dragon.awen.com (dragon.awen.com [207.33.155.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA12802 for ; Mon, 22 Sep 1997 06:45:53 -0700 (PDT) Received: from cmnsens (cmnsens.awen.com [207.33.155.2]) by dragon.awen.com (8.8.7/8.8.6) with SMTP id GAA03288 for ; Mon, 22 Sep 1997 06:45:27 -0700 (PDT) Message-Id: <199709221345.GAA03288@dragon.awen.com> From: "Mike Burgett" To: "freebsd-stable@freebsd.org" Date: Mon, 22 Sep 97 06:45:27 -0700 Reply-To: "Mike Burgett" Priority: Normal X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: -stable makeworld breakage (usr.sbin/ppp) Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It looks like /usr/src/usr.sbin/ppp has been broken in RELENG_2_2, main.c is using SetVariable, which is defined static in command.c, so the link fails. Thanks, Mike From owner-freebsd-stable Mon Sep 22 07:05:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA14216 for stable-outgoing; Mon, 22 Sep 1997 07:05:38 -0700 (PDT) Received: from bunyip.cc.uq.edu.au (daemon@bunyip.cc.uq.edu.au [130.102.2.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA14169; Mon, 22 Sep 1997 07:04:33 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.7/8.8.7) id AAA11981; Tue, 23 Sep 1997 00:04:13 +1000 Received: from troll.dtir.qld.gov.au (troll.dtir.qld.gov.au [167.123.8.1]) by ogre.dtir.qld.gov.au (8.8.7/8.8.7) with ESMTP id AAA07699; Tue, 23 Sep 1997 00:02:38 +1000 (EST) Received: from localhost (syssgm@localhost) by troll.dtir.qld.gov.au (8.8.5/8.8.5) with SMTP id AAA17411; Tue, 23 Sep 1997 00:05:32 +1000 (EST) Message-Id: <199709221405.AAA17411@troll.dtir.qld.gov.au> X-Authentication-Warning: troll.dtir.qld.gov.au: syssgm@localhost didn't use HELO protocol To: Bruce Evans cc: freebsd-stable@FreeBSD.ORG, syssgm@dtir.qld.gov.au, peter@FreeBSD.ORG Subject: Re: No-go with read-only src tree References: <199709221103.VAA09190@godzilla.zeta.org.au> In-Reply-To: <199709221103.VAA09190@godzilla.zeta.org.au> from Bruce Evans at "Mon, 22 Sep 1997 21:03:04 +1000" Date: Tue, 23 Sep 1997 00:05:32 +1000 From: Stephen McKay Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Monday, 22nd September 1997, Bruce Evans wrote: >>If this fixes all my problems, -DNOLIB will go. If not, I'll have to add a >>little extra cruft to specifically rebuild the lex/lib obj directory. >> >>If you know why there was a -DNOLIB there in the first place, speak up! > >See the revision log. I see you haven't become unnecessarily verbose, or succumbed to the temptation to spoon feed people. :-) Yes, I came to my senses shortly after posting, and read the log: >revision 1.6 >date: 1996/08/07 13:25:59; author: peter; state: Exp; lines: +3 -2 >Move tsort back to lib-tools where it belongs, and add a "specially >for bootstrap" tweak to the lex Makefile to stop it building the library >too early. > >This untangles things a bit more, it stops new bootstraps failing because >libl/libfl uses 'ld -O' before ld is updated. So, if we still care about 'make world' bootstrapping from 2.1.x, which I expect we do, then the -DNOLIB has to stay. I'll have to tweak around it since without -DNOLIB my compile breezed past the usual trouble spot to die messily with: /usr/src/lib/libc/i386/DEFS.h: No such file or directory But we know all about that one already. I'm thinking of adding a warning early in the build process. Just idle thinking. :-) Peter, if you have any insight you want to pass on, please chime in here. Stephen. From owner-freebsd-stable Mon Sep 22 07:59:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA17392 for stable-outgoing; Mon, 22 Sep 1997 07:59:03 -0700 (PDT) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA17382; Mon, 22 Sep 1997 07:58:17 -0700 (PDT) Received: from spinner.netplex.com.au (localhost.dialix.com.au [127.0.0.1]) by spinner.netplex.com.au with ESMTP id WAA25252; Mon, 22 Sep 1997 22:57:19 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199709221457.WAA25252@spinner.netplex.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Stephen McKay cc: Bruce Evans , freebsd-stable@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: No-go with read-only src tree In-reply-to: Your message of "Tue, 23 Sep 1997 00:05:32 +1000." <199709221405.AAA17411@troll.dtir.qld.gov.au> Date: Mon, 22 Sep 1997 22:57:18 +0800 From: Peter Wemm Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Stephen McKay wrote: > On Monday, 22nd September 1997, Bruce Evans wrote: > > >>If this fixes all my problems, -DNOLIB will go. If not, I'll have to add a > >>little extra cruft to specifically rebuild the lex/lib obj directory. > >> > >>If you know why there was a -DNOLIB there in the first place, speak up! > > > >See the revision log. > > I see you haven't become unnecessarily verbose, or succumbed to the temptatio n > to spoon feed people. :-) > > Yes, I came to my senses shortly after posting, and read the log: > > >revision 1.6 > >date: 1996/08/07 13:25:59; author: peter; state: Exp; lines: +3 -2 > >Move tsort back to lib-tools where it belongs, and add a "specially > >for bootstrap" tweak to the lex Makefile to stop it building the library > >too early. > > > >This untangles things a bit more, it stops new bootstraps failing because > >libl/libfl uses 'ld -O' before ld is updated. > > So, if we still care about 'make world' bootstrapping from 2.1.x, which > I expect we do, then the -DNOLIB has to stay. I'll have to tweak around > it since without -DNOLIB my compile breezed past the usual trouble spot > to die messily with: > > /usr/src/lib/libc/i386/DEFS.h: No such file or directory > > But we know all about that one already. I'm thinking of adding a warning > early in the build process. Just idle thinking. :-) > > Peter, if you have any insight you want to pass on, please chime in here. ``Urk''. Perhaps change: cd ${.CURDIR}/usr.bin/lex && ${MAKE} bootstrap && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} -DNOLIB all install ${CLEANDIR} ${OBJDIR} To something like: cd ${.CURDIR}/usr.bin/lex && ${MAKE} bootstrap && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} -DNOLIB all install ${CLEANDIR} .if !defined(NOOBJDIR) cd ${.CURDIR}/usr.bin/lex && ${MAKE} obj .endif Or even: cd ${.CURDIR}/usr.bin/lex && ${MAKE} bootstrap && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} -DNOLIB all install clean cleandepend One of those might do it. Otherwise, taking out the -DNOLIB makes lex descend into it's library, which causes ld -O to be used, and ld hasn't been built yet. (And, incidently, ld in binutils-2.8 uses lex during the build :-] /home/src/contrib/binutils/ld/ldlex.l ) > Stephen. Cheers, -Peter From owner-freebsd-stable Mon Sep 22 08:54:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA21531 for stable-outgoing; Mon, 22 Sep 1997 08:54:44 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA21517 for ; Mon, 22 Sep 1997 08:54:39 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id IAA15386; Mon, 22 Sep 1997 08:55:05 -0700 (PDT) To: "Mike Burgett" cc: "freebsd-stable@freebsd.org" Subject: Re: -stable makeworld breakage (usr.sbin/ppp) In-reply-to: Your message of "Mon, 22 Sep 1997 06:45:27 PDT." <199709221345.GAA03288@dragon.awen.com> Date: Mon, 22 Sep 1997 08:55:05 -0700 Message-ID: <15383.874943705@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Already fixed it. > It looks like /usr/src/usr.sbin/ppp has been broken in RELENG_2_2, > main.c is using SetVariable, which is defined static in command.c, so the lin k > fails. > > Thanks, > Mike > > From owner-freebsd-stable Mon Sep 22 08:59:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA21877 for stable-outgoing; Mon, 22 Sep 1997 08:59:12 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA21864 for ; Mon, 22 Sep 1997 08:59:05 -0700 (PDT) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id QAA14875; Mon, 22 Sep 1997 16:47:48 +0100 (BST) Message-Id: <199709221547.QAA14875@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Mike Burgett" cc: "freebsd-stable@freebsd.org" Subject: Re: -stable makeworld breakage (usr.sbin/ppp) In-reply-to: Your message of "Mon, 22 Sep 1997 06:45:27 PDT." <199709221345.GAA03288@dragon.awen.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Sep 1997 16:47:48 +0100 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > It looks like /usr/src/usr.sbin/ppp has been broken in RELENG_2_2, > main.c is using SetVariable, which is defined static in command.c, so the link > fails. My fault - sorry. Fixed by jordan :-) > Thanks, > Mike > > -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-stable Mon Sep 22 09:40:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA26106 for stable-outgoing; Mon, 22 Sep 1997 09:40:59 -0700 (PDT) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA26092 for ; Mon, 22 Sep 1997 09:40:40 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id SAA03613; Mon, 22 Sep 1997 18:39:49 +0200 (MET DST) Date: Mon, 22 Sep 1997 18:39:49 +0200 (MET DST) Message-Id: <199709221639.SAA03613@bitbox.follo.net> From: Eivind Eklund To: "Studded" CC: freebsd-stable@FreeBSD.ORG In-reply-to: "Studded"'s message of Sat, 20 Sep 97 17:43:53 -0700 Subject: Re: >8 char usernames going into 2.2.5? References: <199709210044.RAA18858@mail.san.rr.com> Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >Index: sys/sys/param.h > >========================================================= > >RCS file: /home/ncvs/src/sys/sys/param.h,v > > >-#define MAXLOGNAME 12 /* max login name length */ > >+#define MAXLOGNAME 17 /* max login name length */ > > >Index: include/utmp.h > >========================================================= > >RCS file: /home/ncvs/src/include/utmp.h,v > > >-#define UT_NAMESIZE 8 /* see MAXLOGNAME in */ > >+#define UT_NAMESIZE 16 /* see MAXLOGNAME in */ > > Ok, why is there a discrepancy here? If you told me that the change > was easy to make, and all I had to do was change the numbers in those two > files, the first thing I'd do is ask myself why they were already different, then > I'd make them both 16. Obviously I'd be wrong, but can someone explain to > a non-programmer why I want the value in param.h to be higher than the > one in utmp.h? Quick guess: MAXLOGNAME is supposed to include a zero terminator in the count (a single null character to indicate the end of the name), UT_NAMESIZE is just copied into a buffer with strncpy() and written to utmp, and strncpy() cut the terminator character if the string is too long for it. Eivind. From owner-freebsd-stable Mon Sep 22 09:42:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA26269 for stable-outgoing; Mon, 22 Sep 1997 09:42:35 -0700 (PDT) Received: from hawk.gnome.co.uk (gnome.gw.cerbernet.co.uk [193.243.224.22]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA26205 for ; Mon, 22 Sep 1997 09:42:26 -0700 (PDT) Received: from hawk.gnome.co.uk (localhost [127.0.0.1]) by hawk.gnome.co.uk (8.8.7/8.8.7) with ESMTP id RAA00380 for ; Mon, 22 Sep 1997 17:42:14 +0100 (BST) Message-Id: <199709221642.RAA00380@hawk.gnome.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: stable@freebsd.org Subject: ipfw logging problem Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Sep 1997 17:42:14 +0100 From: Chris Stenton Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have recently performed a "make world" updated rc.conf etc and rebuilt my kernel. However, I have found that logging has stopped working. Looking at the message log I find that on bootup I get:- Sep 22 17:33:22 hawk /kernel: changing root device to sd0a Sep 22 17:33:22 hawk /kernel: IP packet filtering initialized, divert disabled, logging limited to 50 packets/entry Sep 22 17:33:22 hawk /kernel: IP packet filtering initialized, divert disabled, logging disabled Anyone know why I am getting two messages with the second disabling logging? Chris From owner-freebsd-stable Mon Sep 22 10:49:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA03881 for stable-outgoing; Mon, 22 Sep 1997 10:49:16 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA03833; Mon, 22 Sep 1997 10:48:53 -0700 (PDT) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.6/8.8.4) with SMTP id UAA02711; Mon, 22 Sep 1997 20:48:36 +0300 (EEST) Date: Mon, 22 Sep 1997 20:48:36 +0300 (EEST) From: Narvi To: Tom cc: Gary Palmer , John Robert LoVerso , Snob Art Genre , Studded , "freebsd-stable@freebsd.org" Subject: Re: >8 char usernames going into 2.2.5 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 21 Sep 1997, Tom wrote: > > On Sun, 21 Sep 1997, Gary Palmer wrote: > > > John Robert LoVerso wrote in message ID > > <199709210325.XAA14160@loverso.southborough.ma.us>: > > > The set of valid characters in usernames have nothing to do with what an > > > Internet RFC covers. > > > > It does have relevance if you want them to get mail, or other such > > useful functions. > > Hardly. The set of all possible legal unix usernames is only a small > subset of the set of all possible RFC 821 local-parts. RFC 821 basically > allows, given the right quoting, every possible ASCII character. So who > want to allow whitepace in usernames? :) Whitespace in a username - what use could there except of confusing the heck out of the luser? That besides, I would expect it to require only very minor changes. Sander There is no love, no good, no happiness and no future - all these are just illusions. > > > Gary > > -- > > Gary Palmer FreeBSD Core Team Member > > FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info > > > > Tom > From owner-freebsd-stable Mon Sep 22 11:31:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA06984 for stable-outgoing; Mon, 22 Sep 1997 11:31:41 -0700 (PDT) Received: from mailhost3.BayNetworks.COM (ns4.BayNetworks.COM [192.32.253.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA06978 for ; Mon, 22 Sep 1997 11:31:36 -0700 (PDT) Received: from mailhost.BayNetworks.COM ([132.245.135.115] (may be forged)) by mailhost3.BayNetworks.COM (8.8.6/BNET-97/07/07-E) with ESMTP id OAA19865 Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.151.199]) by mailhost.BayNetworks.COM (8.8.6/BNET-97/07/07-I) with ESMTP id OAA15714 Posted-Date: Mon, 22 Sep 1997 14:30:59 -0400 (EDT) Received: from tuva.engeast.baynetworks.com (tuva [192.32.180.119]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id OAA27243; Mon, 22 Sep 1997 14:30:48 -0400 for Received: from tuva.engeast.baynetworks.com (localhost [127.0.0.1]) by tuva.engeast.baynetworks.com (8.8.3/8.8.3) with ESMTP id OAA21976; Mon, 22 Sep 1997 14:30:18 -0400 (EDT) Message-Id: <199709221830.OAA21976@tuva.engeast.baynetworks.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Nate Williams cc: "Jordan K. Hubbard" , Robert Withrow , freebsd-stable@freebsd.org Subject: Re: Minor problems with upcomming 2.2.5 In-reply-to: Your message of "Thu, 18 Sep 1997 23:20:35 MDT." <199709190520.XAA16476@rocky.mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Sep 1997 14:30:17 -0400 From: Robert Withrow Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk nate@mt.sri.com said: :- Actually, I think having more process slots is *a good thing* :- nowadays. Even on my (now ailing) lowly single-user 486/66 box with :- 16MB, I bump up maxusers. How many more? If you suggest a number I could try it and see if it fixes my problem, and then we'd at least have a datapoint in the argument for raising the number in GENERIC... -- Robert Withrow -- (+1 508 916 8256) BWithrow@BayNetworks.com From owner-freebsd-stable Mon Sep 22 11:36:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA07504 for stable-outgoing; Mon, 22 Sep 1997 11:36:12 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA07496 for ; Mon, 22 Sep 1997 11:36:09 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id MAA14201; Mon, 22 Sep 1997 12:36:01 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA01760; Mon, 22 Sep 1997 12:36:01 -0600 (MDT) Date: Mon, 22 Sep 1997 12:36:01 -0600 (MDT) Message-Id: <199709221836.MAA01760@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Robert Withrow Cc: Nate Williams , "Jordan K. Hubbard" , freebsd-stable@freebsd.org Subject: Re: Minor problems with upcomming 2.2.5 In-Reply-To: <199709221830.OAA21976@tuva.engeast.baynetworks.com> References: <199709190520.XAA16476@rocky.mt.sri.com> <199709221830.OAA21976@tuva.engeast.baynetworks.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Robert Withrow writes: > > nate@mt.sri.com said: > :- Actually, I think having more process slots is *a good thing* > :- nowadays. Even on my (now ailing) lowly single-user 486/66 box with > :- 16MB, I bump up maxusers. > > How many more? If you suggest a number I could try it and see > if it fixes my problem, and then we'd at least have a datapoint > in the argument for raising the number in GENERIC... I don't have the box handy (the disk is dying on it, and it's at home), but you could try 16 to see if it helps. Nate From owner-freebsd-stable Mon Sep 22 12:51:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA13649 for stable-outgoing; Mon, 22 Sep 1997 12:51:21 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA13618; Mon, 22 Sep 1997 12:51:11 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA12343; Mon, 22 Sep 1997 21:51:05 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id VAA15384; Mon, 22 Sep 1997 21:47:27 +0200 (MET DST) Message-ID: <19970922214727.WW10801@uriah.heep.sax.de> Date: Mon, 22 Sep 1997 21:47:27 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Cc: joes@seaport.net (Joseph Stein) Subject: Re: Help... Unexplained crashes under RELENG_2_2 (last message in syslog is from atrun) References: <199709220513.WAA00814@shasta.wstein.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709220513.WAA00814@shasta.wstein.com>; from Joseph Stein on Sep 21, 1997 22:13:18 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Joseph Stein wrote: > This system runs a plethora of daemons -- xntpd, named, sshd, httpd, ftpd, > rwhod -- am I merely overloading it? Or is there some bug in at/atrun? > > I have coredumps enabled but have not yet seen anything in /var/run/crash > from it. Do you have a dumpdev, too? The `savecore_enable' knob is history now (it was a bandaid only against savecore(8) not obeying its minfree file), but dumpdev remains a prerequisite for kernel core dumps. Can you run it on a serial console, with DDB enabled? (Maybe even over a modem line.) Does the machine provide NFS services, or act as a NFS client? I've seen a number of crashes on RELENG_2_2 lately that might be related to NFS. Is the CD-ROM regularly being used? I've seen another couple of crashes that might be related to a bug or two in the cd9660 f/s. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-stable Mon Sep 22 14:36:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA22633 for stable-outgoing; Mon, 22 Sep 1997 14:36:51 -0700 (PDT) Received: from ganymede.frii.com (ganymede.frii.com [208.146.240.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA22628 for ; Mon, 22 Sep 1997 14:36:48 -0700 (PDT) From: gnat@frii.com Received: from elara.frii.com (elara.frii.com [208.146.240.9]) by ganymede.frii.com (8.8.5/8.8.4) with ESMTP id PAA29586 for ; Mon, 22 Sep 1997 15:36:15 -0600 (MDT) Received: (from gnat@localhost) by elara.frii.com (8.8.5/8.6.9) id PAA02262; Mon, 22 Sep 1997 15:33:47 -0600 (MDT) Date: Mon, 22 Sep 1997 15:33:47 -0600 (MDT) Message-Id: <199709222133.PAA02262@elara.frii.com> To: stable@FreeBSD.ORG Subject: Dying -STABLE machine Mime-Version: 1.0 (generated by tm-edit 7.103) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I've got a 2.2-STABLE machine that keeps rebooting. It's our user machine, under a moderate but not heavy load. We see it rebooting every 6-12 hours. I see the message "page fault while in kernel mode". This machine is an NFS client, and runs sendmail (no httpd or ftpd). I've seen a lot of sendmail processes dying of signal 5 too, for what it's worth. Other machines kernels were built from the same code (but not config file) as the dying machine, and they are not dying. I want to track this problem down. What should I do? I've freed up a disk to use as a dumpdev, but don't know where to go from here. Thanks, Nat From owner-freebsd-stable Mon Sep 22 15:04:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA24542 for stable-outgoing; Mon, 22 Sep 1997 15:04:30 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA24537 for ; Mon, 22 Sep 1997 15:04:22 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id IAA08033; Tue, 23 Sep 1997 08:03:56 +1000 (EST) Date: Tue, 23 Sep 1997 08:03:55 +1000 (EST) From: "Daniel O'Callaghan" To: Chris Stenton cc: stable@FreeBSD.ORG Subject: Re: ipfw logging problem In-Reply-To: <199709221642.RAA00380@hawk.gnome.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Sep 1997, Chris Stenton wrote: > > I have recently performed a "make world" updated rc.conf etc and rebuilt my > kernel. However, I have found that logging has stopped working. Looking at the > message log I find that on bootup I get:- > > Sep 22 17:33:22 hawk /kernel: changing root device to sd0a > Sep 22 17:33:22 hawk /kernel: IP packet filtering initialized, divert > disabled, logging limited to 50 packets/entry > Sep 22 17:33:22 hawk /kernel: IP packet filtering initialized, divert > disabled, logging disabled > > Anyone know why I am getting two messages with the second disabling logging? Sorry, mea culpa. When you say firewall="YES" in rc.conf, rc.network will attempt to find the firewall code in kernel and if it is not there, will load the lkm. My test was broken, so the LKM was loaded even if firewalling was in the kernel. I've fixed it in -stable now. Patch below. regards, Danny --- rc.network.orig Thu Sep 18 15:48:31 1997 +++ rc.network Thu Sep 18 15:47:12 1997 @@ -58,7 +58,7 @@ # Initialize IP filtering using ipfw echo "" /sbin/ipfw -q flush > /dev/null 2>&1 - if [ $? ] ; then + if [ $? = 1 ] ; then firewall_in_kernel=0 else firewall_in_kernel=1 --- rc.firewall.orig Thu Sep 18 15:48:14 1997 +++ rc.firewall Thu Sep 18 15:47:10 1997 @@ -167,5 +167,5 @@ # Everything else is denied as default. elif [ "${firewall_type}" != "NONE" -a -r "${firewall_type}" ]; then - $fwcmd ${firewall} + $fwcmd ${firewall_type} fi From owner-freebsd-stable Mon Sep 22 16:26:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA29899 for stable-outgoing; Mon, 22 Sep 1997 16:26:45 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA29872; Mon, 22 Sep 1997 16:26:34 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id QAA01075; Mon, 22 Sep 1997 16:26:17 -0700 (PDT) Date: Mon, 22 Sep 1997 16:26:17 -0700 (PDT) From: "Jamil J. Weatherbee" To: freebsd-stable@freebsd.org cc: freebsd-hackers@freebsd.org Subject: Diskless Workstation -- Problems needing to be addressed Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I myself, am sold on the idea of diskless freebsd workstations, for my applications they greatly reduce the amount of maintenance that needs to be done aon a machine plus when stupid people panic and fluip the power switch there aren't any problems with drives being spammed -- one thing I have learned is that 100 base T networking is something you will definetely want to have for this --- with it there is no real difference in feeling between a machine with a hard drive and one without, I was able to set up a pentium 100 and a couple of nexgens 110s as some very suitable freebsd fully featured workstations/X stations (32MB) for about $800 a piece, and also by burning some eproms I dont need a floppy either, hell the only moving parts in the whole machine is the power supply which could be eliminated by using a centralized dc 12/5 power supply plus probably some filter capacitors at the endpointd due to the distance. Anyway having three of these disklesss workstations and one master server I just wanted to make my environment available for testing related things related to this, I have written some scripts that after a make world on a master server automatically mirror over things like /lkm /bin , and a kernel to each machines deirectory. I think there should be an option for easily setting up diskless workstations in the installation, because there are a different set of things that need to be done on the master server, also since a root directory is not as critical (in terms of having all the binaries needed to repair the system on a diskless machine I think a significant amount of reorganizing could be done to the diskless workstation directory structure there are other problems too for instance I have yet to figure out why when I have the /usr partition mounted read only from the master server and I run finger on the diskless machines as a regular user I get a finger: permission denied message? Are there some restrictions on things like running suid binaries on mounted volumes because of the obvious security hole if a user mounts a suid binary that would allow him to gain root priveledges etc. From owner-freebsd-stable Mon Sep 22 16:53:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA01511 for stable-outgoing; Mon, 22 Sep 1997 16:53:07 -0700 (PDT) Received: from pandora.hh.kew.com (root@kendra.ne.mediaone.net [24.128.53.73]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA01506 for ; Mon, 22 Sep 1997 16:53:04 -0700 (PDT) Received: from sonata (sonata.hh.kew.com [192.195.203.135]) by pandora.hh.kew.com (8.8.5/8.8.5) with ESMTP id TAA16399; Mon, 22 Sep 1997 19:52:33 -0400 (EDT) Message-ID: <342704C5.A242A097@kew.com> Date: Mon, 22 Sep 1997 19:52:37 -0400 From: Drew Derbyshire Organization: Kendra Electronic Wonderworks X-Mailer: Mozilla 4.01 [en]C-MOENE (WinNT; U) MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: "John T. Farmer" , tom@uniserve.com, freebsd-stable@FreeBSD.ORG, jfarmer@goldsword.com, Studded@dal.net Subject: Re: >8 char usernames going into 2.2.5? X-Priority: 3 (Normal) References: <27009.874760684@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard wrote: > Here, enjoy. :-) Okay, to further my enjoyment, two silly questions ... > diff -u -r1.15.2.2 param.h > --- param.h 1996/12/15 09:54:28 1.15.2.2 > +++ param.h 1997/09/20 13:04:06 > @@ -65,7 +65,7 @@ > -#define MAXLOGNAME 12 /* max login name length */ > +#define MAXLOGNAME 17 /* max login name length */ Why was this 12 and not 9? > diff -u -r1.2 utmp.h > --- utmp.h 1996/10/27 18:13:35 1.2 > +++ utmp.h 1997/09/20 13:03:42 > @@ -46,7 +46,7 @@ > #define _PATH_WTMP "/var/log/wtmp" > #define _PATH_LASTLOG "/var/log/lastlog" > > -#define UT_NAMESIZE 8 /* see MAXLOGNAME in */ > +#define UT_NAMESIZE 16 /* see MAXLOGNAME in */ Ummm, why isn't utmp.h using MAXLOGNAME+1 as a reasonable default? Morals require not including param.h? -- Internet: ahd@kew.com Voice: 781-279-9812 "Is a dream a lie if it don't come true, or is it something worse?" - Bruce Springsteen From owner-freebsd-stable Mon Sep 22 18:08:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA05572 for stable-outgoing; Mon, 22 Sep 1997 18:08:38 -0700 (PDT) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA05566 for ; Mon, 22 Sep 1997 18:08:33 -0700 (PDT) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xDJSk-00041b-00; Mon, 22 Sep 1997 18:08:26 -0700 Date: Mon, 22 Sep 1997 18:08:21 -0700 (PDT) From: Tom To: gnat@frii.com cc: stable@freebsd.org Subject: Re: Dying -STABLE machine In-Reply-To: <199709222133.PAA02262@elara.frii.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Sep 1997 gnat@frii.com wrote: > I've got a 2.2-STABLE machine that keeps rebooting. It's our user > machine, under a moderate but not heavy load. We see it rebooting > every 6-12 hours. I see the message "page fault while in kernel > mode". > > This machine is an NFS client, and runs sendmail (no httpd or ftpd). > I've seen a lot of sendmail processes dying of signal 5 too, for what > it's worth. Other machines kernels were built from the same code (but > not config file) as the dying machine, and they are not dying. > > I want to track this problem down. What should I do? I've freed up a > disk to use as a dumpdev, but don't know where to go from here. > > Thanks, > > Nat > Sounds like hardware. I bet you don't use parity memory do you? Tom From owner-freebsd-stable Mon Sep 22 21:22:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA14516 for stable-outgoing; Mon, 22 Sep 1997 21:22:36 -0700 (PDT) Received: from bunyip.cc.uq.edu.au (bunyip.cc.uq.edu.au [130.102.2.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA14481 for ; Mon, 22 Sep 1997 21:22:18 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.7/8.8.7) id OAA18229; Tue, 23 Sep 1997 14:20:22 +1000 Received: from troll.dtir.qld.gov.au (troll.dtir.qld.gov.au [167.123.8.1]) by ogre.dtir.qld.gov.au (8.8.7/8.8.7) with ESMTP id OAA16229; Tue, 23 Sep 1997 14:21:45 +1000 (EST) Received: from localhost (syssgm@localhost) by troll.dtir.qld.gov.au (8.8.5/8.8.5) with SMTP id OAA05113; Tue, 23 Sep 1997 14:21:41 +1000 (EST) Message-Id: <199709230421.OAA05113@troll.dtir.qld.gov.au> X-Authentication-Warning: troll.dtir.qld.gov.au: syssgm@localhost didn't use HELO protocol To: Peter Wemm cc: freebsd-stable@FreeBSD.ORG, syssgm@dtir.qld.gov.au Subject: Re: No-go with read-only src tree References: <199709221457.WAA25252@spinner.netplex.com.au> In-Reply-To: <199709221457.WAA25252@spinner.netplex.com.au> from Peter Wemm at "Mon, 22 Sep 1997 22:57:18 +0800" Date: Tue, 23 Sep 1997 14:21:41 +1000 From: Stephen McKay Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Monday, 22nd September 1997, Peter Wemm wrote: >Perhaps change: > cd ${.CURDIR}/usr.bin/lex && ${MAKE} bootstrap && ${MAKE} depend && \ > ${MAKE} ${MK_FLAGS} -DNOLIB all install ${CLEANDIR} ${OBJDIR} >To something like: > cd ${.CURDIR}/usr.bin/lex && ${MAKE} bootstrap && ${MAKE} depend && \ > ${MAKE} ${MK_FLAGS} -DNOLIB all install ${CLEANDIR} >.if !defined(NOOBJDIR) > cd ${.CURDIR}/usr.bin/lex && ${MAKE} obj >.endif > >Or even: > cd ${.CURDIR}/usr.bin/lex && ${MAKE} bootstrap && ${MAKE} depend && \ > ${MAKE} ${MK_FLAGS} -DNOLIB all install clean cleandepend > >One of those might do it. I came up with these two as well, but I prefer the first, though I'm finding it hard to produce convincing reasons. Either should do. I'm about to do another run from scratch with the first change in place. Oh, and you might have missed that I needed to do a make install in share/mk up front to get past building make. I'll fiddle/fix that too. And I'm hung up on the "cd /usr/src/share/info; ${MAKE} install" in bsd.info.mk too. Sigh. One thing at a time... Stephen. From owner-freebsd-stable Mon Sep 22 22:17:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA17947 for stable-outgoing; Mon, 22 Sep 1997 22:17:13 -0700 (PDT) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA17942 for ; Mon, 22 Sep 1997 22:17:11 -0700 (PDT) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id BAA24984; Tue, 23 Sep 1997 01:17:03 -0400 (EDT) Date: Tue, 23 Sep 1997 01:17:02 -0400 (EDT) From: Snob Art Genre To: Tim Tsai cc: Studded , "freebsd-stable@freebsd.org" Subject: Re: >8 char usernames going into 2.2.5? In-Reply-To: <19970919214620.01498@futuresouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Sep 1997, Tim Tsai wrote: > Having recently converted a garbage :-) bin full of Sun Solaris boxes > to FreeBSD, I am happy to report that "." works in most places. > > chown doesn't like it, obviously, but in those few cases I just use the > uid (but then again, there are users who has strictly numeric user > names!!!). Isn't that the point of the : separator for chown? Perhaps the . separator should start to go away? > Tim > Ben "You have your mind on computers, it seems." From owner-freebsd-stable Mon Sep 22 23:03:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA20555 for stable-outgoing; Mon, 22 Sep 1997 23:03:00 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA20535; Mon, 22 Sep 1997 23:02:48 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id GAA18356; Tue, 23 Sep 1997 06:49:18 +0200 From: Luigi Rizzo Message-Id: <199709230449.GAA18356@labinfo.iet.unipi.it> Subject: Re: Diskless Workstation -- Problems needing to be addressed To: jamil@counterintelligence.ml.org (Jamil J. Weatherbee) Date: Tue, 23 Sep 1997 06:49:18 +0200 (MET DST) Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Jamil J. Weatherbee" at Sep 22, 97 04:25:58 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Just curious, did you manage to boot from an eprom with 100Mbit cards ? Last time I tried this was only possible with 10Mbit cards, except the obvious option (one 10-mbit card with the boot rom, one 100-mbit which supports the real traffic). > easily setting up diskless workstations in the installation, because there > are a different set of things that need to be done on the master server, what I have is a script which clones the root partition by making a small set of changes and symlinks where needed. Cheers Luigi From owner-freebsd-stable Mon Sep 22 23:23:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA21861 for stable-outgoing; Mon, 22 Sep 1997 23:23:57 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA21810; Mon, 22 Sep 1997 23:23:30 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id XAA01385; Mon, 22 Sep 1997 23:18:29 -0700 (PDT) Date: Mon, 22 Sep 1997 23:18:29 -0700 (PDT) From: "Jamil J. Weatherbee" To: Luigi Rizzo cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Diskless Workstation -- Problems needing to be addressed In-Reply-To: <199709230449.GAA18356@labinfo.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk No only 10 megabit but I am going to get a linksys LNE100TX because I have a suspicion I may be able to hack it up and get it to work. There is some pci code in the netboot stuff (and also the boot rom sockets on other cards I've seen weren't the standard type I have the rom burner for) On Tue, 23 Sep 1997, Luigi Rizzo wrote: > Just curious, did you manage to boot from an eprom with 100Mbit > cards ? Last time I tried this was only possible with 10Mbit cards, > except the obvious option (one 10-mbit card with the boot rom, one > 100-mbit which supports the real traffic). > > > easily setting up diskless workstations in the installation, because there > > are a different set of things that need to be done on the master server, > > what I have is a script which clones the root partition by making a > small set of changes and symlinks where needed. > > Cheers > Luigi > From owner-freebsd-stable Tue Sep 23 00:48:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA26938 for stable-outgoing; Tue, 23 Sep 1997 00:48:41 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA26430; Tue, 23 Sep 1997 00:41:58 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id IAA18576; Tue, 23 Sep 1997 08:27:05 +0200 From: Luigi Rizzo Message-Id: <199709230627.IAA18576@labinfo.iet.unipi.it> Subject: Re: Diskless Workstation -- Problems needing to be addressed To: jamil@counterintelligence.ml.org (Jamil J. Weatherbee) Date: Tue, 23 Sep 1997 08:27:05 +0200 (MET DST) Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Jamil J. Weatherbee" at Sep 22, 97 11:18:10 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > No only 10 megabit but I am going to get a linksys LNE100TX because I have > a suspicion I may be able to hack it up and get it to work. There is some what is this suspicion based on, may I ask ? > pci code in the netboot stuff (and also the boot rom sockets on other I know, I wrote it :) but notices that different NE2000 clones behave differently with the PCI ROM (probably it is a property of the bios, not of the card). CHeers Luigi From owner-freebsd-stable Tue Sep 23 07:38:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA13999 for stable-outgoing; Tue, 23 Sep 1997 07:38:10 -0700 (PDT) Received: from as5200-port-254.no.neosoft.com (as5200-port-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA13993 for ; Tue, 23 Sep 1997 07:38:06 -0700 (PDT) Received: (from conrads@localhost) by as5200-port-254.no.neosoft.com (8.8.7/8.8.6) id JAA24684; Tue, 23 Sep 1997 09:38:29 -0500 (CDT) Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 23 Sep 1997 09:38:28 -0500 (CDT) Organization: NeoSoft, Inc. From: Conrad Sabatier To: "Jay M. Richmond" Subject: Re: anyone else ? atapi headaches? Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 18-Sep-97 "Jay M. Richmond" wrote: >is anyone else besides those I've talked to having problems with their >atapi cd-rom (input/output errors when mounting)...? or are there people >with cd-rom's that are working fine out there... Yes! root:/root# mount_cd9660 -v /dev/wcd0c /cdrom using starting sector 512 mount_cd9660: /dev/wcd0c: Invalid argument >i'm talking about a recently cvsup'ed 2.2-stable kernel... Same here. Just made update world and rebuilt kernel yesterday (9/22). Strangely, though, sysinstall (also rebuilt) mounts it just fine. -- Conrad Sabatier | FreeBSD -- UNIX for your PC http://www.neosoft.com/~conrads | Why settle for less than the best? Spambots, use this: biteme@f-u.org | http://www.freebsd.org From owner-freebsd-stable Tue Sep 23 09:47:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA20427 for stable-outgoing; Tue, 23 Sep 1997 09:47:20 -0700 (PDT) Received: from ganymede.frii.com (ganymede.frii.com [208.146.240.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA20408 for ; Tue, 23 Sep 1997 09:47:14 -0700 (PDT) From: gnat@frii.com Received: from elara.frii.com (elara.frii.com [208.146.240.9]) by ganymede.frii.com (8.8.5/8.8.4) with ESMTP id KAA22789; Tue, 23 Sep 1997 10:47:38 -0600 (MDT) Received: (from gnat@localhost) by elara.frii.com (8.8.5/8.6.9) id KAA15511; Tue, 23 Sep 1997 10:47:09 -0600 (MDT) Date: Tue, 23 Sep 1997 10:47:09 -0600 (MDT) Message-Id: <199709231647.KAA15511@elara.frii.com> To: Tom Cc: stable@FreeBSD.ORG Subject: Re: Dying -STABLE machine In-Reply-To: References: <199709222133.PAA02262@elara.frii.com> Mime-Version: 1.0 (generated by tm-edit 7.103) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tom writes: > Sounds like hardware. I bet you don't use parity memory do you? It turned out to be a dead power fan. It's replaced, but we're still getting the panics. Your question suggests you think the RAM is at fault. Is this a common thing? Nat From owner-freebsd-stable Tue Sep 23 12:48:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA00419 for stable-outgoing; Tue, 23 Sep 1997 12:48:39 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA00385; Tue, 23 Sep 1997 12:48:26 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id MAA00183; Tue, 23 Sep 1997 12:48:00 -0700 (PDT) Date: Tue, 23 Sep 1997 12:48:00 -0700 (PDT) From: "Jamil J. Weatherbee" To: Luigi Rizzo cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Diskless Workstation -- Problems needing to be addressed In-Reply-To: <199709230627.IAA18576@labinfo.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Last time I called Linksys they were reluctantly willing to give me some unusual info about the NE2000 cards we have, and possibly I could buy a boot rom off them and take a look at it :>) On Tue, 23 Sep 1997, Luigi Rizzo wrote: > > No only 10 megabit but I am going to get a linksys LNE100TX because I have > > a suspicion I may be able to hack it up and get it to work. There is some > > what is this suspicion based on, may I ask ? > > > pci code in the netboot stuff (and also the boot rom sockets on other > > I know, I wrote it :) but notices that different NE2000 clones behave > differently with the PCI ROM (probably it is a property of the bios, > not of the card). > > CHeers > Luigi > From owner-freebsd-stable Tue Sep 23 15:32:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA09576 for stable-outgoing; Tue, 23 Sep 1997 15:32:44 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA09531; Tue, 23 Sep 1997 15:32:35 -0700 (PDT) Received: from x14.mi.uni-koeln.de ([134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA18853 (5.67b/IDA-1.5); Wed, 24 Sep 1997 00:32:30 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.7/8.6.9) id AAA04311; Wed, 24 Sep 1997 00:03:03 +0200 (CEST) X-Face: " Date: Wed, 24 Sep 1997 00:03:03 +0200 From: Stefan Esser To: chro@ccca.nctu.edu.tw Cc: freebsd-stable@FreeBSD.ORG, Stefan Esser Subject: Re: About NCR Driver... References: <199709151758.RAA00313@avatar.dorm12.nctu.edu.tw> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199709151758.RAA00313@avatar.dorm12.nctu.edu.tw>; from Avatarf on Mon, Sep 15, 1997 at 05:58:21PM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sep 15, Avatarf wrote: > everytime after I reboot,a strange message appears to ncr0 (Takram DC-390F). > Here is the dmesg: > > ncr0 rev 3 int a irq 12 on pci0:11 > (ncr0:0:0): "IBM DCAS-32160W S65A" type 0 fixed SCSI 2 > sd0(ncr0:0:0): Direct-Access > sd0(ncr0:0:0): WIDE SCSI (16 bit) enabled > sd0(ncr0:0:0): 40.0 MB/s (50 ns, offset 15) > 2063MB (4226725 512 byte sectors) > (ncr0:1:0): "MICROP 4110-09NB_Nov18F TN0F" type 0 fixed SCSI 2 > sd1(ncr0:1:0): Direct-Access > sd1(ncr0:1:0): 10.0 MB/s (100 ns, offset 15) > 1002MB (2053880 512 byte sectors) > [deleted] > assertion "cp" failed: file "../../pci/ncr.c", line 6191 > assertion "cp" failed: file "../../pci/ncr.c", line 6191 > sd0(ncr0:0:0): COMMAND FAILED (4 28) @f0df7000. > > What did it mean? how to fix it? The message indicates that the drive did reject a tagged command and returned a QUEUE_FULL status. The IBM DORS is known to do this at times. It seems to support only a very limited number of tags (less than 4) in certain situations. There is not much that can be done about this in the NCR driver, but the new generic SCSI layer will provide support for adjusting the number of tags if QUEUE_FULL status is returned. > And when I run ncrcontrol. it shows the error message: > ncrcontrol: incompatible with kernel. Rebuild! > > but the program and kernel source are installed at the same time!! > (all 2.2-970913-RELENG) > > kernel config contains: > > controller ncr0 > controller scbus0 > device sd0 > options SCSI_NCR_DFLT_TAGS=8 > > How to fix it? thanks a lot for answer! The compilation of ncrcontrol does not know about your kernel config file. If you want to use a different default for the number of tags, you better just edit the line in ncr.c where SCSI_NCR_DFLT_TAGS is defined as "4". Regards, STefan From owner-freebsd-stable Tue Sep 23 19:30:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA23021 for stable-outgoing; Tue, 23 Sep 1997 19:30:34 -0700 (PDT) Received: from baklava.alt.net (root@baklava.alt.net [207.14.113.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA23016 for ; Tue, 23 Sep 1997 19:30:29 -0700 (PDT) Received: from baklava.alt.net (ccaputo@baklava.alt.net [207.14.113.9]) by baklava.alt.net (8.8.5/8.7.3) with SMTP id TAA05551; Tue, 23 Sep 1997 19:30:08 -0700 (PDT) Date: Tue, 23 Sep 1997 19:30:08 -0700 (PDT) From: Chris Caputo To: spork cc: Joerg Wunsch , stable@FreeBSD.ORG Subject: Re: Another NFS bogon in 2.2-stable? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk We are definitely seeing problems with nfsv2 and either tcp or udp connections. We have tried the -r=1024 fix for udp and that didn't help. We use the 2.2-stable box as an NFS client to a NetApp NFS server. After a little while, the FreeBSD box gets into a state where any command that causes NFS activity hangs, including a simple "df". Once in this state, the command can not be killed, even with "kill -9" from root. I am gonna start comparing the 2.2-stable sources with 3.0-current sources to see if there are any obvious fixes. If anyone has any other ideas, please let me know. We have an immediate desire to get beyond this. ;-) Chris On Mon, 22 Sep 1997, spork wrote: > Is it just me or is there another bug involving 2 FBSD machines running > -stable and nfsv2 or v3? > > In the above situation, if machine A is exporting a directory to machine B > and machine A dies unexpectedly, you cannot umount the nfs-mounted > directory; the command just hangs forever. "mount" will hang forever as > well. Killing off any nfs processes will not help (brutal I thought, but > worth a try). Remounting can be difficult, and sometimes a reboot is > required. > > Am I doing something terribly wrong? I'm not doing anything out of the > ordinary, I let the startup script do everything, and I'm only exporting > one directory. > > Charles > > On Sun, 21 Sep 1997, J Wunsch wrote: > > > (Please drop me a Cc of this conversation, i'm not subscribed to this > > list.) > > > > Did anybody else notice that shutting down a 2.2-stable machine that > > has NFS file systems mounted never yields a clean shutdown? My 2.2 > > scratchbox always jams with a `2 2 2 2 2 giving up' display, and comes > > up again with the clean flag not set in the UFS filesystems. > > > > If i shutdown to single-user, manually umount the NFS filesystems, and > > then type `halt', all works as expected. > > > > The machine is not the fastest on earth (386/40), maybe this is what > > uncovers this problem? > > > > -- > > cheers, J"org > > > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > > Never trust an operating system you don't have sources for. ;-) > > > From owner-freebsd-stable Tue Sep 23 22:24:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA01790 for stable-outgoing; Tue, 23 Sep 1997 22:24:23 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA01768; Tue, 23 Sep 1997 22:24:16 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id GAA20679; Wed, 24 Sep 1997 06:11:32 +0200 From: Luigi Rizzo Message-Id: <199709240411.GAA20679@labinfo.iet.unipi.it> Subject: Re: Diskless Workstation -- Problems needing to be addressed To: jamil@counterintelligence.ml.org (Jamil J. Weatherbee) Date: Wed, 24 Sep 1997 06:11:32 +0200 (MET DST) Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Jamil J. Weatherbee" at Sep 23, 97 12:47:41 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Last time I called Linksys they were reluctantly willing to give me some > unusual info about the NE2000 cards we have, and possibly I could buy a > boot rom off them and take a look at it :>) my experience on this: I looked at a boot rom for some other PCI ne200 clone. They only had code for novell, and internally the rom looked much different from what "PCI system architecture" says... My experience is that some BIOSes work fine with a normal ISA boot rom such as the one produced by netboot, and others (presumably old ones) seem not to like boot roms on PCI cards (the same card+rom on another system works fine) even if build the way PCI system architecture says. So my advice is to try the standard rom first... As a quick and dirty alternative, since I have some broken ISA network cards, at times I put there the card with the only purpose of acting as a boot rom socket. One more advanced option could be to update the flash bios to include the boot room, but this is a bit risky... As for 100 Mbit/s cards, remember they are quite different from ne2000, and that you will probably have to import a lot of code the controller (DEC 21x4x ?) they use. Unfortunately you cannot just link in say if_de.c , probably a lot of hand editing would be necessary (and a copy of the controller's data sheets). Luckily PCI cards tend to have only one chip so if you have those docs (often available from the manufacturer, e.g. www.dec.com or www.intel.com) you are in good shape... Cheers Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-stable Tue Sep 23 23:50:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA07946 for stable-outgoing; Tue, 23 Sep 1997 23:50:50 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA07923; Tue, 23 Sep 1997 23:50:44 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id XAA00997; Tue, 23 Sep 1997 23:49:52 -0700 (PDT) Date: Tue, 23 Sep 1997 23:49:52 -0700 (PDT) From: "Jamil J. Weatherbee" To: Luigi Rizzo cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Diskless Workstation -- Problems needing to be addressed In-Reply-To: <199709240411.GAA20679@labinfo.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I think in my situation since I am slowly transitioning from 10 base T to 100 baseT I can just put Two cards in each (I don't know what function this really serves since the bootp server is also sits betweens the networks and acts as a router?) but I'd much rather look at the specs and work it out (that will be the long term solution --- perhaps also educational). On Wed, 24 Sep 1997, Luigi Rizzo wrote: > > Last time I called Linksys they were reluctantly willing to give me some > > unusual info about the NE2000 cards we have, and possibly I could buy a > > boot rom off them and take a look at it :>) > > my experience on this: I looked at a boot rom for some other PCI > ne200 clone. They only had code for novell, and internally the rom > looked much different from what "PCI system architecture" says... > My experience is that some BIOSes work fine with a normal ISA boot > rom such as the one produced by netboot, and others (presumably > old ones) seem not to like boot roms on PCI cards (the same card+rom > on another system works fine) even if build the way PCI system > architecture says. So my advice is to try the standard rom first... > > As a quick and dirty alternative, since I have some broken ISA > network cards, at times I put there the card with the only purpose > of acting as a boot rom socket. > > One more advanced option could be to update the flash bios to > include the boot room, but this is a bit risky... > > As for 100 Mbit/s cards, remember they are quite different from ne2000, > and that you will probably have to import a lot of code the controller > (DEC 21x4x ?) they use. Unfortunately you cannot just link in say > if_de.c , probably a lot of hand editing would be necessary (and a copy > of the controller's data sheets). Luckily PCI cards tend to have only > one chip so if you have those docs (often available from the > manufacturer, e.g. www.dec.com or www.intel.com) you are in good > shape... > > Cheers > Luigi > -----------------------------+-------------------------------------- > Luigi Rizzo | Dip. di Ingegneria dell'Informazione > email: luigi@iet.unipi.it | Universita' di Pisa > tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) > fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ > _____________________________|______________________________________ > From owner-freebsd-stable Wed Sep 24 00:26:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA10697 for stable-outgoing; Wed, 24 Sep 1997 00:26:27 -0700 (PDT) Received: from home.shvetc.marka.net.ua (home.shvetc.marka.net.ua [193.193.219.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA10623 for ; Wed, 24 Sep 1997 00:24:35 -0700 (PDT) Received: from eugene.shvetc.marka.net.ua (eugene.shvetc.marka.net.ua [193.193.219.187]) by home.shvetc.marka.net.ua (8.8.5/8.8.5) with SMTP id KAA29277 for ; Wed, 24 Sep 1997 10:24:08 +0300 (EEST) Message-Id: <199709240724.KAA29277@home.shvetc.marka.net.ua> From: "Eugene Shvetc" To: Subject: slattach problems Date: Wed, 24 Sep 1997 10:24:07 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1008.3 X-MimeOle: Produced By Microsoft MimeOLE Engine V4.71.1008.3 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Does anybody know, does slattach -S option works correctly in latest FreeBSD-stable release? From owner-freebsd-stable Wed Sep 24 02:27:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA18121 for stable-outgoing; Wed, 24 Sep 1997 02:27:36 -0700 (PDT) Received: from sliphost37.uni-trier.de (root@sliphost37.uni-trier.de [136.199.240.37]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA18112 for ; Wed, 24 Sep 1997 02:27:29 -0700 (PDT) Received: (from blank@localhost) by sliphost37.uni-trier.de (8.8.7/8.8.7) id TAA24679 for freebsd-stable@freebsd.org; Tue, 23 Sep 1997 19:16:40 +0200 (CEST) From: Sascha Blank Message-Id: <199709231716.TAA24679@sliphost37.uni-trier.de> Subject: OPIE not activated in 2.2-STABLE To: freebsd-stable@freebsd.org Date: Tue, 23 Sep 1997 19:16:39 +0200 (CEST) Reply-To: blank@fox.uni-trier.de (Sascha Blank) X-Operating-System: FreeBSD 2.2-STABLE X-Mailer: ELM [version 2.4ME+ PL35 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I have noticed that the OPIE package has been introduced into the 2.2-STABLE source tree several months ago, but since then it has not been activated to be built during a make world. Is there any specific reason for this? -- Sascha Blank - mailto:blank@fox.uni-trier.de Student and System Administrator at the University of Trier, Germany Finger my account to receive my Public PGP key I don't speak for my employers, they don't pay me enough for that. From owner-freebsd-stable Wed Sep 24 06:11:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA27998 for stable-outgoing; Wed, 24 Sep 1997 06:11:59 -0700 (PDT) Received: from as5200-port-254.no.neosoft.com (as5200-port-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA27989 for ; Wed, 24 Sep 1997 06:11:55 -0700 (PDT) Received: (from conrads@localhost) by as5200-port-254.no.neosoft.com (8.8.7/8.8.6) id IAA12437; Wed, 24 Sep 1997 08:10:51 -0500 (CDT) Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <9709190656.AA11001@leech.mpg.uni-jena.de> Date: Wed, 24 Sep 1997 08:10:50 -0500 (CDT) Organization: NeoSoft, Inc. From: Conrad Sabatier To: Heiko Schafberg Subject: Re: Error message while cvsup'ing RELENG_2_2 Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 19-Sep-97 Heiko Schafberg wrote: >Hi folks > >One short question: What mean the option numbers 0, 1 ore 2 in the fstab? >It`s not the right place I know but it`s important. >Thank`s >From man 5 fstab: The fifth field, (fs_freq), is used for these filesystems by the dump(8) command to determine which filesystems need to be dumped. If the fifth field is not present, a value of zero is returned and dump will assume that the filesystem does not need to be dumped. The sixth field, (fs_passno), is used by the fsck(8) program to determine the order in which filesystem checks are done at reboot time. The root filesystem should be specified with a fs_passno of 1, and other filesystems should have a fs_passno of 2. Filesystems within a drive will be checked sequentially, but filesystems on different drives will be checked at the same time to utilize parallelism available in the hardware. If the sixth field is not present or zero, a value of zero is returned and fsck(8) will assume that the filesystem does not need to be checked. -- Conrad Sabatier | FreeBSD -- UNIX for your PC http://www.neosoft.com/~conrads | Why settle for less than the best? Spambots, use this: biteme@f-u.org | http://www.freebsd.org From owner-freebsd-stable Wed Sep 24 07:36:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA01795 for stable-outgoing; Wed, 24 Sep 1997 07:36:35 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA01779 for ; Wed, 24 Sep 1997 07:36:09 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id HAA00247 for ; Wed, 24 Sep 1997 07:35:32 -0700 (PDT) Date: Wed, 24 Sep 1997 07:35:32 -0700 (PDT) From: "Jamil J. Weatherbee" To: freebsd-stable@freebsd.org Subject: 2.2 Stable, Not so stable? In-Reply-To: <199709241008.DAA06292@dog.farm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Last night I cvsuped to stable after maybye a week. Recompiled kernel and rebooted and then started a make world, when I woke up this morning my machine was frozen up without a console (I run blank screensaver on it and that is exactly what it looked like), I don't believe this has ever happened before and I am pretty sure I didn't loose power. Anyway this apparently happened before make world was finished (which puts a significant load on the machine). I started a make world at about 2:30 this is all I have in my syslog: Sep 23 17:45:41 counterintelligence /kernel: sbmidi0 at 0x330 on isa Sep 23 17:45:41 counterintelligence /kernel: Sep 23 20:53:43 counterintelligence pppd[627]: Connect script failed Sep 23 21:14:22 counterintelligence /kernel: wcd0: i/o error, status=51, error=b5 Sep 23 21:14:24 counterintelligence /kernel: wcd0: i/o error, status=51, error=b5 Sep 23 21:22:52 counterintelligence pppd[700]: Connect script failed Sep 23 22:00:14 counterintelligence pppd[802]: Connect script failed Sep 23 22:15:56 counterintelligence pppd[828]: Connect script failed Sep 24 04:10:03 counterintelligence pppd[15467]: Connect script failed Sep 24 07:22:31 counterintelligence /kernel: Copyright (c) 1992-1997 FreeBSD Inc. Sep 24 07:22:31 counterintelligence /kernel: Copyright (c) 1982, 1986, 1989, 199 1 When I restarted the drives were pretty well spammed. This is very unusual for this system, It is usually on 24x7 and doesn't usually bomb without some reason. From owner-freebsd-stable Wed Sep 24 15:15:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA02271 for stable-outgoing; Wed, 24 Sep 1997 15:15:50 -0700 (PDT) Received: from pooh.cdrom.com (pooh.cdrom.com [204.216.28.222]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA02217; Wed, 24 Sep 1997 15:15:38 -0700 (PDT) Received: from localhost (murray@localhost) by pooh.cdrom.com (8.8.7/8.7.3) with SMTP id PAA17105; Wed, 24 Sep 1997 15:11:14 -0700 (PDT) Date: Wed, 24 Sep 1997 15:11:13 -0700 (PDT) From: Murray Stokely To: Luigi Rizzo cc: "Jamil J. Weatherbee" , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Diskless Workstation -- Problems needing to be addressed In-Reply-To: <199709230449.GAA18356@labinfo.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk SMC EtherPower II cards (10/100bt) have optional boot eproms for about $25. (the cards themselves are about $70). On Tue, 23 Sep 1997, Luigi Rizzo wrote: % Just curious, did you manage to boot from an eprom with 100Mbit % cards ? Last time I tried this was only possible with 10Mbit cards, % except the obvious option (one 10-mbit card with the boot rom, one % 100-mbit which supports the real traffic). % % > easily setting up diskless workstations in the installation, because there % > are a different set of things that need to be done on the master server, % % what I have is a script which clones the root partition by making a % small set of changes and symlinks where needed. Murray Stokely From owner-freebsd-stable Wed Sep 24 18:59:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA15828 for stable-outgoing; Wed, 24 Sep 1997 18:59:24 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA15801; Wed, 24 Sep 1997 18:59:14 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id SAA00759; Wed, 24 Sep 1997 18:56:36 -0700 (PDT) Date: Wed, 24 Sep 1997 18:56:36 -0700 (PDT) From: "Jamil J. Weatherbee" To: Murray Stokely cc: Luigi Rizzo , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Diskless Workstation -- Problems needing to be addressed In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Are these known to boot freebsd using bootp and tftp (i.e. have you tried it yourself or a close friend). I ask because most cards can do this just not with freebsd off the shelf. On Wed, 24 Sep 1997, Murray Stokely wrote: > SMC EtherPower II cards (10/100bt) have optional boot eproms for about > $25. (the cards themselves are about $70). > > On Tue, 23 Sep 1997, Luigi Rizzo wrote: > % Just curious, did you manage to boot from an eprom with 100Mbit > % cards ? Last time I tried this was only possible with 10Mbit cards, > % except the obvious option (one 10-mbit card with the boot rom, one > % 100-mbit which supports the real traffic). > % > % > easily setting up diskless workstations in the installation, because there > % > are a different set of things that need to be done on the master server, > % > % what I have is a script which clones the root partition by making a > % small set of changes and symlinks where needed. > > Murray Stokely > > From owner-freebsd-stable Wed Sep 24 21:42:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA24371 for stable-outgoing; Wed, 24 Sep 1997 21:42:58 -0700 (PDT) Received: from destiny.erols.com (root@destiny.erols.com [207.96.73.65]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA24342; Wed, 24 Sep 1997 21:42:46 -0700 (PDT) Received: from destiny.erols.com (someone@destiny.erols.com [207.96.73.65]) by destiny.erols.com (8.8.7/8.6.12) with SMTP id AAA27317; Thu, 25 Sep 1997 00:42:04 -0400 (EDT) Date: Thu, 25 Sep 1997 00:42:03 -0400 (EDT) From: John Dowdal To: "Jamil J. Weatherbee" cc: Murray Stokely , Luigi Rizzo , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Diskless Workstation -- Problems needing to be addressed In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Sep 1997, Jamil J. Weatherbee wrote: > > > Are these known to boot freebsd using bootp and tftp (i.e. have you tried > it yourself or a close friend). I ask because most cards can do this just > not with freebsd off the shelf. I'm currently doing this with a disposable NE2000 clone and the nb8390.com which is in /usr/mdec. There is also the .bin file which I haven't ever tried to burn into a rom; I'm netbooting this machine, because it has a 500MB hard drive which is dedicated to windoze. If you have specific quesitons I'll answer them. --------------------- John Dowdal jdowdal@destiny.erols.com I Want My/I Want My NetTV From owner-freebsd-stable Thu Sep 25 07:55:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA20530 for stable-outgoing; Thu, 25 Sep 1997 07:55:57 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA20500 for ; Thu, 25 Sep 1997 07:55:26 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id AAA04253; Fri, 26 Sep 1997 00:18:37 +0930 (CST) Message-Id: <199709251448.AAA04253@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Bryan K. Ogawa" cc: jamil@counterintelligence.ml.org, freebsd-stable@FreeBSD.ORG Subject: Re: Star Office In-reply-to: Your message of "Sun, 21 Sep 1997 15:01:08 MST." <199709212201.PAA18877@foo.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Sep 1997 00:18:36 +0930 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >I did a make on this port --- can someone explain what the deal with it is > >-- I was reading calderas web page, Is this a commercial procduct (or > >demo) is everything not supposed to work right or what? How did this get > >ported to freebsd in the first place -- is there a native port to be done > >as a commercial product? Eep. You show remarkably practiced ignorance and a stunning ability to ignore documentation my friend. > Q: Is this a commercial product? > > A: Yes. Caldera carries it. Actually, StarDivision "carries" it, and sells it commercially for a not inconsiderable number of platforms. They have an active internal Linux community that are responsible for the Linux port, which currently lags their fully commercial release considerably. It's also markedly less stable, but improving. > The literature seems to indicate that StarDivision fully expects > individuals to take advantage of the unlimited evaluation period for > it. Yes. They are very keen to be taken seriously as a provider of a multiplatform office suite, and the Linux version seems to be seen as good publicity. > Q: Is there a native port in the works? > > A: I heard some rumbling about this as part of a commercial FreeBSD > offering, but nothing beyond that. Not to the best of my knowledge. Conversations with the friendly people at StarDivision have indicated that they are extremely strained for resources as things stand, and as such the best goal to aim for is a Linux version that is compatible with the ABI emulation. They have indicated that they're willing to work with us to ensure that this state of affairs can be maintained. In reality, their system interface is likely to be fairly conservative, as their code has to build on a very wide range of platforms. ie. unless some functionality is available on Solaris, Irix, Sinix, AIX, etc. they're not going to stress over it. > Does anyone know the status of the > whole commercial FreeBSD offering thing (with XAccel, etc.?)? There are rumblings, yes. mike From owner-freebsd-stable Thu Sep 25 08:24:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA22089 for stable-outgoing; Thu, 25 Sep 1997 08:24:16 -0700 (PDT) Received: from dragon.awen.com (dragon.awen.com [207.33.155.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA22082 for ; Thu, 25 Sep 1997 08:24:12 -0700 (PDT) Received: from cmnsens (cmnsens.awen.com [207.33.155.2]) by dragon.awen.com (8.8.7/8.8.7) with SMTP id IAA20826 for ; Thu, 25 Sep 1997 08:24:05 -0700 (PDT) Message-Id: <199709251524.IAA20826@dragon.awen.com> From: "Mike Burgett" To: "freebsd-stable@freebsd.org" Date: Thu, 25 Sep 97 08:24:04 -0700 Reply-To: "Mike Burgett" Priority: Normal X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: [Q] 2.2.5 bind release Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Will 2.2.5 ship with the 4.9.6 or 8.1.1 BIND release? --Mike From owner-freebsd-stable Thu Sep 25 10:15:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA29549 for stable-outgoing; Thu, 25 Sep 1997 10:15:04 -0700 (PDT) Received: from zigg.com (tcgr-65.dialup.alliance.net [207.74.43.65]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA29532 for ; Thu, 25 Sep 1997 10:14:50 -0700 (PDT) Received: from localhost (matt@localhost) by zigg.com (8.8.7/8.8.5) with SMTP id NAA19988; Thu, 25 Sep 1997 13:15:45 -0400 (EDT) Date: Thu, 25 Sep 1997 13:15:44 -0400 (EDT) From: Matt Behrens To: Mike Burgett cc: "freebsd-stable@freebsd.org" Subject: Re: [Q] 2.2.5 bind release In-Reply-To: <199709251524.IAA20826@dragon.awen.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 25 Sep 1997, Mike Burgett wrote: > Will 2.2.5 ship with the 4.9.6 or 8.1.1 BIND release? I'm 99.9% sure it'll be 4.9.6. 8.1.1 has the strongest nameserver but its resolver library is sorely lacking and would probably cause many packages to break. Matt Behrens | matt@zigg.com MST3K #85995 | http://www.zigg.com/ From owner-freebsd-stable Thu Sep 25 15:13:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA17136 for stable-outgoing; Thu, 25 Sep 1997 15:13:29 -0700 (PDT) Received: from stoner.sinet.com ([204.233.141.228]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA16930 for ; Thu, 25 Sep 1997 15:09:26 -0700 (PDT) Received: from wang ([169.147.153.126]) by stoner.sinet.com with esmtp id m0xEMQB-0003cWC (Debian Smail-3.2 1996-Jul-4 #2); Thu, 25 Sep 1997 17:30:07 -0500 (CDT) Message-Id: From: "Lester P. Wang" To: Subject: amanda and archive 4586 npr Date: Thu, 25 Sep 1997 17:04:49 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello all, I have just bought an Archive 4586 NPR autoloading DAT tape drive. I am new to FreeBSD and have mostly used Linux. I can not get this DAT tape drive and AMANDA to work with Linux for the sake of me. I'd like to try FreeBSD. I have a DX4133 with an Adaptec VL bus adapter. Has anybody gotten AMANDA to work with this DAT drive? Any help in this matter is greatly appreciated. Thanks Lester From owner-freebsd-stable Thu Sep 25 17:25:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA24488 for stable-outgoing; Thu, 25 Sep 1997 17:25:48 -0700 (PDT) Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA24483 for ; Thu, 25 Sep 1997 17:25:43 -0700 (PDT) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.4/8.8.4) with ESMTP id RAA10211; Thu, 25 Sep 1997 17:24:35 -0700 (PDT) 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 RAA12068; Thu, 25 Sep 1997 17:24:34 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id RAA19181; Thu, 25 Sep 1997 17:24:32 -0700 (PDT) From: Don Lewis Message-Id: <199709260024.RAA19181@salsa.gv.tsc.tdk.com> Date: Thu, 25 Sep 1997 17:24:31 -0700 In-Reply-To: Matt Behrens "Re: [Q] 2.2.5 bind release" (Sep 25, 1:15pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Matt Behrens , Mike Burgett Subject: Re: [Q] 2.2.5 bind release Cc: "freebsd-stable@freebsd.org" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sep 25, 1:15pm, Matt Behrens wrote: } Subject: Re: [Q] 2.2.5 bind release } On Thu, 25 Sep 1997, Mike Burgett wrote: } } > Will 2.2.5 ship with the 4.9.6 or 8.1.1 BIND release? } } I'm 99.9% sure it'll be 4.9.6. 8.1.1 has the strongest nameserver but its } resolver library is sorely lacking and would probably cause many packages } to break. I'd recommend staying with 4.9.6 for now. There are a couple of bits of functionality that were changed in or eliminated from the 8.1.1 server. One change is the secure zone stuff. In 4.9.x you can put TXT RRs in the zone file to limit who is allowed to query the zone. In 8.1.1 this is done in the config file, so if you upgrade a server to 8.1.1 and you were relying on this feature, you have to manually add this to the config file of each server for the zone. The biggest feature that was removed was the automatic sorting of A RRs that the server did for local clients. If you mount a filesystem from a multi-homed NFS server, this feature would put the local network address of the NFS server first in the DNS response. Recent resolvers have this functionality built in, but if you have any clients using old and non-upgradable servers, you may be SOL if you upgrade your server to 8.1.1. I've got a patch to add this feature back to 8.1.1, but I don't know if it will be integrated into the official source tree. From owner-freebsd-stable Thu Sep 25 18:23:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA27106 for stable-outgoing; Thu, 25 Sep 1997 18:23:16 -0700 (PDT) Received: from pooh.cdrom.com (pooh.cdrom.com [204.216.28.222]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA27101 for ; Thu, 25 Sep 1997 18:23:12 -0700 (PDT) Received: from localhost (murray@localhost) by pooh.cdrom.com (8.8.7/8.7.3) with SMTP id SAA29465; Thu, 25 Sep 1997 18:20:05 -0700 (PDT) Date: Thu, 25 Sep 1997 18:20:04 -0700 (PDT) From: Murray Stokely To: "Lester P. Wang" cc: freebsd-stable@FreeBSD.ORG Subject: Re: amanda and archive 4586 npr In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 25 Sep 1997, Lester P. Wang wrote: % I have just bought an Archive 4586 NPR autoloading DAT tape drive. I am % new to FreeBSD and have mostly used Linux. I can not get this DAT tape % drive and AMANDA to work with Linux for the sake of me. I'd like to try % FreeBSD. I have a DX4133 with an Adaptec VL bus adapter. Has anybody % gotten AMANDA to work with this DAT drive? Any help in this matter is % greatly appreciated. AMANDA should work with any tape drive that the operating system supports? I've never used any form of autoloader with FreeBSD, but I've had good luck getting obscure tape drives to work. When you add the 'st' driver to your system and try to issue commands like 'mt erase' what happens? Does FreeBSD detect the drive correctly at startup? You're posting in the wrong group, by the way. freebsd-questions is where you should direct inquiries like this. Murray Stokely From owner-freebsd-stable Thu Sep 25 23:19:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA11944 for stable-outgoing; Thu, 25 Sep 1997 23:19:37 -0700 (PDT) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA11939 for ; Thu, 25 Sep 1997 23:19:35 -0700 (PDT) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xETkD-00073e-00; Thu, 25 Sep 1997 23:19:17 -0700 Date: Thu, 25 Sep 1997 23:19:11 -0700 (PDT) From: Tom To: Matt Behrens cc: Mike Burgett , "freebsd-stable@freebsd.org" Subject: Re: [Q] 2.2.5 bind release In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 25 Sep 1997, Matt Behrens wrote: > On Thu, 25 Sep 1997, Mike Burgett wrote: > > > Will 2.2.5 ship with the 4.9.6 or 8.1.1 BIND release? > > I'm 99.9% sure it'll be 4.9.6. 8.1.1 has the strongest nameserver but its > resolver library is sorely lacking and would probably cause many packages > to break. Has FreeBSD ever use the BIND resolver library? It seems to me that the FreeBSD resolver is whole mix of different things, and is not 4.9.6 either. Besides the BIND resolver is mainly for systems that come with such a useless/broken resolver that anything is better (ex SunOS 4.1). > Matt Behrens | matt@zigg.com > MST3K #85995 | http://www.zigg.com/ > > Tom From owner-freebsd-stable Thu Sep 25 23:29:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA12530 for stable-outgoing; Thu, 25 Sep 1997 23:29:47 -0700 (PDT) Received: from bunyip.cc.uq.edu.au (daemon@bunyip.cc.uq.edu.au [130.102.2.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA12505; Thu, 25 Sep 1997 23:29:12 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.7/8.8.7) id QAA15687; Fri, 26 Sep 1997 16:29:00 +1000 Received: from troll.dtir.qld.gov.au (troll.dtir.qld.gov.au [167.123.8.1]) by ogre.dtir.qld.gov.au (8.8.7/8.8.7) with ESMTP id QAA09202; Fri, 26 Sep 1997 16:30:07 +1000 (EST) Received: from localhost (syssgm@localhost) by troll.dtir.qld.gov.au (8.8.5/8.8.5) with SMTP id QAA10015; Fri, 26 Sep 1997 16:30:03 +1000 (EST) Message-Id: <199709260630.QAA10015@troll.dtir.qld.gov.au> X-Authentication-Warning: troll.dtir.qld.gov.au: syssgm@localhost didn't use HELO protocol To: freebsd-stable@freebsd.org cc: asami@freebsd.org, syssgm@dtir.qld.gov.au Subject: Read-only src tree solution for review Date: Fri, 26 Sep 1997 16:30:02 +1000 From: Stephen McKay Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk After the lex lib obj problem (fix to be committed probably tomorrow), the other main problem was a failure building make. I solved this by changing line 188 of Makefile from: IBMAKE= ${BMAKEENV} ${MAKE} DESTDIR=${WORLDTMP} to IBMAKE= ${BMAKEENV} MAKEOBJDIR=/tmp ${MAKE} DESTDIR=${WORLDTMP} IBMAKE is only used when building make for the first time, and MAKEOBJDIR=/tmp puts the objects in /tmp. Without this, the old make will put the objects in the source directory. With this fix (plus the lex/lib one) a read only source tree will build 2.2-stable from a 2.1.5 box. While this seems the simplest way to fix things, some people might like something other than /tmp. Perhaps ${WORLDTMP}, or even something else. It was not immediately obvious to me how to put make's object files in its real object area. (Think about people NOT using read-only source, and NOT using a separate object tree.) So, what do people think? I want to commit a fix tomorrow some time. If nobody speaks up, it will be either /tmp or ${WORLDTMP} for this tweak. Then I should update the handbook with some "How to upgrade from source" doco covering the other surprises (like group mail and group network and /usr/src/share/info ...) Stephen. Oh bugger! I've just been told that there's a power shutdown here this weekend. Everything should be up by the afternoon. From owner-freebsd-stable Thu Sep 25 23:43:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA13505 for stable-outgoing; Thu, 25 Sep 1997 23:43:14 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA13486 for ; Thu, 25 Sep 1997 23:43:01 -0700 (PDT) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.8.7/8.8.7) id IAA09099; Fri, 26 Sep 1997 08:42:27 +0200 (SAT) From: John Hay Message-Id: <199709260642.IAA09099@zibbi.mikom.csir.co.za> Subject: Re: [Q] 2.2.5 bind release In-Reply-To: from Tom at "Sep 25, 97 11:19:11 pm" To: tom@uniserve.com (Tom) Date: Fri, 26 Sep 1997 08:42:26 +0200 (SAT) Cc: freebsd-stable@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > > Will 2.2.5 ship with the 4.9.6 or 8.1.1 BIND release? > > > > I'm 99.9% sure it'll be 4.9.6. 8.1.1 has the strongest nameserver but its > > resolver library is sorely lacking and would probably cause many packages > > to break. > > Has FreeBSD ever use the BIND resolver library? It seems to me that the > FreeBSD resolver is whole mix of different things, and is not 4.9.6 > either. > While FreeBSD does not have a seperate resolver library, the resolver code in libc does come from bind. Here is a piece of the cvs log of src/lib/libc/net/gethostbydns.c ---------------------------- revision 1.22 date: 1997/06/27 08:22:01; author: peter; state: Exp; lines: +25 -9 Merge in bind-4.9.6 resolver changes. Note that they resolve the overflow problem differently. ---------------------------- John -- John Hay -- John.Hay@mikom.csir.co.za From owner-freebsd-stable Thu Sep 25 23:55:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA14428 for stable-outgoing; Thu, 25 Sep 1997 23:55:07 -0700 (PDT) Received: from gate.mgt.msk.ru (mgtrep.24h.dialup.ru [194.87.18.139]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA14362; Thu, 25 Sep 1997 23:54:44 -0700 (PDT) Received: from asteroid.mgt.msk.ru (asteroid.mgt.msk.ru [192.168.133.145]) by gate.mgt.msk.ru (8.8.6/8.8.6) with ESMTP id KAA06887; Fri, 26 Sep 1997 10:54:14 +0400 (MSD) Received: from asteroid.mgt.msk.ru (localhost.mgt.msk.ru [127.0.0.1]) by asteroid.mgt.msk.ru (8.8.7/8.8.6) with ESMTP id KAA06908; Fri, 26 Sep 1997 10:54:00 +0400 (MSD) Message-Id: <199709260654.KAA06908@asteroid.mgt.msk.ru> To: hackers@freebsd.org cc: stable@freebsd.org Reply-To: tarkhil@mgt.msk.ru Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Sep 1997 10:53:59 +0400 From: "Alexander B. Povolotsky" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello! I'm running FreeBSD-2.2.2-stable on P-133, with EtherExpress card (fxp0 interface). Sometimes (about 3-4 times per week) I'm getting troubles with IP. 127.0.0.1 pings ok, and my fxp0's address as well, but no other computer can see me, and I can't see any others. Putting fxp0 in promiscous mode heals the trouble in several seconds, but shutdown (without reboot) doesn't help. Routing tables remains unchanged. It happened at both day and night, the only program that could receive something thry TCP/IP was sendmail. make world and kernel recompilatin didn't help. Any other suggestions? Alex. From owner-freebsd-stable Fri Sep 26 00:00:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA14908 for stable-outgoing; Fri, 26 Sep 1997 00:00:25 -0700 (PDT) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA14899 for ; Fri, 26 Sep 1997 00:00:16 -0700 (PDT) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xEUNT-0007E8-00; Thu, 25 Sep 1997 23:59:51 -0700 Date: Thu, 25 Sep 1997 23:59:44 -0700 (PDT) From: Tom To: John Hay cc: freebsd-stable@freebsd.org Subject: Re: [Q] 2.2.5 bind release In-Reply-To: <199709260642.IAA09099@zibbi.mikom.csir.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 26 Sep 1997, John Hay wrote: > > > > Will 2.2.5 ship with the 4.9.6 or 8.1.1 BIND release? > > > > > > I'm 99.9% sure it'll be 4.9.6. 8.1.1 has the strongest nameserver but its > > > resolver library is sorely lacking and would probably cause many packages > > > to break. > > > > Has FreeBSD ever use the BIND resolver library? It seems to me that the > > FreeBSD resolver is whole mix of different things, and is not 4.9.6 > > either. > > > > While FreeBSD does not have a seperate resolver library, the resolver > code in libc does come from bind. Here is a piece of the cvs log of > src/lib/libc/net/gethostbydns.c > > ---------------------------- > revision 1.22 > date: 1997/06/27 08:22:01; author: peter; state: Exp; lines: +25 -9 > Merge in bind-4.9.6 resolver changes. Note that they resolve the > overflow problem differently. > ---------------------------- That is a just a merge of some 4.9.6 fixes, not a complete import. 4.9.6 resolver does not use /etc/host.conf or /etc/hosts, yet the FreeBSD resolver does. The FreeBSD resolver is also capable of using NIS host maps. The FreeBSD resolver seems to similar to resolv+ with various other addons bolted on it (NIS host maps for one, as resolv+ as DNS-only). > John > -- > John Hay -- John.Hay@mikom.csir.co.za > Tom From owner-freebsd-stable Fri Sep 26 00:19:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA16038 for stable-outgoing; Fri, 26 Sep 1997 00:19:55 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA16032 for ; Fri, 26 Sep 1997 00:19:51 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id QAA00314; Fri, 26 Sep 1997 16:46:51 +0930 (CST) Message-Id: <199709260716.QAA00314@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Tom cc: Matt Behrens , Mike Burgett , "freebsd-stable@freebsd.org" Subject: Re: [Q] 2.2.5 bind release In-reply-to: Your message of "Thu, 25 Sep 1997 23:19:11 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Sep 1997 16:46:51 +0930 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I'm 99.9% sure it'll be 4.9.6. 8.1.1 has the strongest nameserver but its > > resolver library is sorely lacking and would probably cause many packages > > to break. > > Has FreeBSD ever use the BIND resolver library? It seems to me that the > FreeBSD resolver is whole mix of different things, and is not 4.9.6 > either. What sort of dopey question is this? Have a look at src/contrib/bind and decide for yourself what FreeBSD uses. > Besides the BIND resolver is mainly for systems that come with such a > useless/broken resolver that anything is better (ex SunOS 4.1). Not by half. mike From owner-freebsd-stable Fri Sep 26 00:57:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA18700 for stable-outgoing; Fri, 26 Sep 1997 00:57:19 -0700 (PDT) Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [194.93.177.113]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA18664; Fri, 26 Sep 1997 00:56:47 -0700 (PDT) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.8.7/8.8.7) id KAA01057; Fri, 26 Sep 1997 10:53:42 +0300 (EEST) From: Ruslan Ermilov Message-Id: <199709260753.KAA01057@relay.ucb.crimea.ua> Subject: Re: your mail In-Reply-To: <199709260654.KAA06908@asteroid.mgt.msk.ru> from "Alexander B. Povolotsky" at "Sep 26, 97 10:53:59 am" To: tarkhil@mgt.msk.ru Date: Fri, 26 Sep 1997 10:53:42 +0300 (EEST) Cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG X-My-Interests: Unix,Oracle,Networking 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 X-Loop: FreeBSD.org Precedence: bulk Once Alexander B. Povolotsky wrote: > Hello! > > I'm running FreeBSD-2.2.2-stable on P-133, with EtherExpress card (fxp0 interface). Sometimes (about 3-4 times per week) I'm getting troubles with IP. 127.0.0.1 pings ok, and my fxp0's address as well, but no other computer can see me, and I can't see any others. > > Putting fxp0 in promiscous mode heals the trouble in several seconds, but shutdown (without reboot) doesn't help. Routing tables remains unchanged. It happened at both day and night, the only program that could receive something thry TCP/IP was sendmail. > > make world and kernel recompilatin didn't help. > > Any other suggestions? > > Alex. > The same problems. I'm using 3 EtherExpress cards: fxp0 rev 2 int a irq 10 on pci0:10 fxp0: Ethernet address 00:a0:c9:55:13:22 fxp1 rev 1 int a irq 9 on pci0:12 fxp1: Ethernet address 00:a0:c9:10:68:a0, 10Mbps fxp2 rev 1 int a irq 9 on pci0:14 fxp2: Ethernet address 00:a0:c9:5a:51:f9, 10Mbps Sometimes, ~ 1/2 per week, my fxp0, which is revision 2 card, silently freezes. When I `ifconfig down delete fxp0' and then ifconfig it up, the situation resolves. ;-( -- Ruslan A. Ermilov System Administrator ru@ucb.crimea.ua United Commercial Bank +380-652-247647 Simferopol, Crimea 2426679 ICQ Network, UIN From owner-freebsd-stable Fri Sep 26 01:20:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA20139 for stable-outgoing; Fri, 26 Sep 1997 01:20:34 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA20129; Fri, 26 Sep 1997 01:20:31 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id BAA18077; Fri, 26 Sep 1997 01:20:20 -0700 (MST) From: Terry Lambert Message-Id: <199709260820.BAA18077@usr04.primenet.com> Subject: Re: Alexander B. Povol's mail To: tarkhil@mgt.msk.ru Date: Fri, 26 Sep 1997 08:20:19 +0000 (GMT) Cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: <199709260654.KAA06908@asteroid.mgt.msk.ru> from "Alexander B. Povolotsky" at Sep 26, 97 10:53:59 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'm running FreeBSD-2.2.2-stable on P-133, with EtherExpress card > (fxp0 interface). Sometimes (about 3-4 times per week) I'm getting > troubles with IP. 127.0.0.1 pings ok, and my fxp0's address as well, > but no other computer can see me, and I can't see any others. 127.0.0.1 is the loopback address. You aren't ifconfig'ing the card to actually have that address, are you? > Putting fxp0 in promiscous mode heals the trouble in several seconds, > but shutdown (without reboot) doesn't help. Routing tables remains > unchanged. The 127.0.0.1 is not normally something that has anything at all to do with the card driver. Instead, it is internally looped back; it is a simulated interface. I don't see how shoving the interface into promiscuous mode would help. Perhaps you are RIP'ing out that your address is 127.0.0.1? This should give the arp tables on all the machines that are listening a fit. If you ever get a RIP back, you are probably screwed. Also, all loopback traffic on those machines (depending on how their routing code is written) would be bounced through your machine. I truly hope you aren't using it for the card address. 8-). > It happened at both day and night, the only program that > could receive something thry TCP/IP was sendmail. Sendmail specifically avoids domain suffixing on lookup, among other things; many programs don't, so it's probably working because of that; that's what made me think you might be using 127.0.0.1 as a real interface address, above. PS: use a subject line so you can recognize a reply, and break your lines at 80 columns so it's easier break out relevent lines when someone sends you a reply. PPS: if you still have problems, it would be useful for you to provide the output of the following network control functions: netstat -r arp -a ifconfig -a If DNS is clobbered, you may need to use the '-n' option to get real output instead of hanging forever waiting on a host lookup. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-stable Fri Sep 26 01:36:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA21168 for stable-outgoing; Fri, 26 Sep 1997 01:36:17 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA21163 for ; Fri, 26 Sep 1997 01:36:14 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id BAA08492 for ; Fri, 26 Sep 1997 01:35:56 -0700 (PDT) To: stable@freebsd.org Subject: 2nd Notice: 4 days to code freeze in RELENG_2_2 branch. Date: Fri, 26 Sep 1997 01:35:55 -0700 Message-ID: <8488.875262955@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just FYI, so nobody can say "but.. but you didn't give me any warning!" when the time comes. ;) This will be the usual FreeBSD style code-freeze: New features and radical changes not allowed, bug fixes and cleanup permitted. Jordan From owner-freebsd-stable Fri Sep 26 01:42:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA21550 for stable-outgoing; Fri, 26 Sep 1997 01:42:08 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA21541; Fri, 26 Sep 1997 01:42:03 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id BAA22393; Fri, 26 Sep 1997 01:43:43 -0700 (PDT) Message-Id: <199709260843.BAA22393@implode.root.com> To: tarkhil@mgt.msk.ru cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG In-reply-to: Your message of "Fri, 26 Sep 1997 10:53:59 +0400." <199709260654.KAA06908@asteroid.mgt.msk.ru> From: David Greenman Reply-To: dg@root.com Date: Fri, 26 Sep 1997 01:43:43 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I'm running FreeBSD-2.2.2-stable on P-133, with EtherExpress card (fxp0 > interface). Sometimes (about 3-4 times per week) I'm getting troubles > with IP. 127.0.0.1 pings ok, and my fxp0's address as well, but no other > computer can see me, and I can't see any others. > >Putting fxp0 in promiscous mode heals the trouble in several seconds, but > shutdown (without reboot) doesn't help. Routing tables remains unchanged. > It happened at both day and night, the only program that could receive > something thry TCP/IP was sendmail. Sounds like you have a "rev 1" chip on the board and the ethernet you're attaching it to has noise problems which are triggering a bug in the chip that causes the receiver to lock up. The problem is especially acute when the interface is in 10Mbps mode. The best solution: find out why your network has garbage on it and fix it. Some hubs will filter out the garbage, so using a different hub might also fix the problem. Another solution: replace the card with a newer one that has the fixed NIC ("rev 2"). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-stable Fri Sep 26 02:17:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA23677 for stable-outgoing; Fri, 26 Sep 1997 02:17:28 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA23670; Fri, 26 Sep 1997 02:17:20 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id SAA00775; Fri, 26 Sep 1997 18:43:19 +0930 (CST) Message-Id: <199709260913.SAA00775@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-reply-to: Your message of "Fri, 26 Sep 1997 08:20:19 GMT." <199709260820.BAA18077@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Sep 1997 18:43:16 +0930 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I'm running FreeBSD-2.2.2-stable on P-133, with EtherExpress card > > (fxp0 interface). Sometimes (about 3-4 times per week) I'm getting > > troubles with IP. 127.0.0.1 pings ok, and my fxp0's address as well, > > but no other computer can see me, and I can't see any others. > > 127.0.0.1 is the loopback address. You aren't ifconfig'ing the card > to actually have that address, are you? (I have removed the term "peanut" from the following response. Feel free to reinsert it at an appropriate point to achieve the original tone.) No. He's reporting the "fxp driver dies occasionally" problem that's been seen off and on for the last few months. Pinging the loopback address is a simple confidence test in at least a little of the network code. See the section in the above paragraph where he uses English well enough to make it clear that 127.0.0.1 is *not* the address attachd to fxp0. > The 127.0.0.1 is not normally something that has anything at all to > do with the card driver. Instead, it is internally looped back; it > is a simulated interface. I don't see how shoving the interface > into promiscuous mode would help. Putting the fxp driver into promiscuous mode involves poking at bits of the interface hardware. This appears to fix whatever it is that's going wrong. If this problem hasn't already been dealt with in the -current/-stable drivers, I hope DG is looking at it. mike From owner-freebsd-stable Fri Sep 26 02:28:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA24241 for stable-outgoing; Fri, 26 Sep 1997 02:28:00 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA24236; Fri, 26 Sep 1997 02:27:56 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id CAA22718; Fri, 26 Sep 1997 02:28:52 -0700 (PDT) Message-Id: <199709260928.CAA22718@implode.root.com> To: Ruslan Ermilov cc: tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: your mail In-reply-to: Your message of "Fri, 26 Sep 1997 10:53:42 +0300." <199709260753.KAA01057@relay.ucb.crimea.ua> From: David Greenman Reply-To: dg@root.com Date: Fri, 26 Sep 1997 02:28:52 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I'm using 3 EtherExpress cards: > >fxp0 rev 2 int a irq 10 on pci0:10 >fxp0: Ethernet address 00:a0:c9:55:13:22 >fxp1 rev 1 int a irq 9 on pci0:12 >fxp1: Ethernet address 00:a0:c9:10:68:a0, 10Mbps >fxp2 rev 1 int a irq 9 on pci0:14 >fxp2: Ethernet address 00:a0:c9:5a:51:f9, 10Mbps > >Sometimes, ~ 1/2 per week, my fxp0, which is revision 2 card, silently freezes. >When I `ifconfig down delete fxp0' and then ifconfig it up, the situation >resolves. If this is true, then Intel has apparantly lied to me about fixing the problem in the "next stepping" of the chip. The lock up should only occur when garbage bits occur in the preamble of a packet. It's not supposed to happen in 100Mbps mode (only 10Mbps), but since I've personnally been able to get it to happen in 100Mbps, I don't believe it. I can reproduce the problem only under special circumstance like power-cycling the hub. You might try using the "link0 link1 -link2" flags on the 100Mbps link to force it to stay in 100/half...this might prevent the lock up from occuring (but I've not tested this myself). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-stable Fri Sep 26 03:15:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA26709 for stable-outgoing; Fri, 26 Sep 1997 03:15:23 -0700 (PDT) Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA26704 for ; Fri, 26 Sep 1997 03:15:17 -0700 (PDT) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.4/8.8.4) with ESMTP id DAA13003; Fri, 26 Sep 1997 03:14:12 -0700 (PDT) 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 DAA20774; Fri, 26 Sep 1997 03:14:11 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id DAA20428; Fri, 26 Sep 1997 03:14:09 -0700 (PDT) From: Don Lewis Message-Id: <199709261014.DAA20428@salsa.gv.tsc.tdk.com> Date: Fri, 26 Sep 1997 03:14:08 -0700 In-Reply-To: Tom "Re: [Q] 2.2.5 bind release" (Sep 25, 11:59pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Tom , John Hay Subject: Re: [Q] 2.2.5 bind release Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sep 25, 11:59pm, Tom wrote: } Subject: Re: [Q] 2.2.5 bind release } 4.9.6 resolver does not use /etc/host.conf or /etc/hosts, yet the } FreeBSD resolver does. The FreeBSD resolver is also capable of using } NIS host maps. The FreeBSD resolver seems to similar to resolv+ } with various other addons bolted on it (NIS host maps for one, as resolv+ } as DNS-only). I think the BIND 8.1.1 resolver has this stuff as well. I haven't had the time to examine it closely. From owner-freebsd-stable Fri Sep 26 04:32:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA29576 for stable-outgoing; Fri, 26 Sep 1997 04:32:37 -0700 (PDT) Received: from usr09.primenet.com (tlambert@usr09.primenet.com [206.165.6.209]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA29565; Fri, 26 Sep 1997 04:32:34 -0700 (PDT) Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id EAA19446; Fri, 26 Sep 1997 04:31:46 -0700 (MST) From: Terry Lambert Message-Id: <199709261131.EAA19446@usr09.primenet.com> Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) To: mike@smith.net.au (Mike Smith) Date: Fri, 26 Sep 1997 11:31:45 +0000 (GMT) Cc: tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: <199709260913.SAA00775@word.smith.net.au> from "Mike Smith" at Sep 26, 97 06:43:16 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > The 127.0.0.1 is not normally something that has anything at all to > > do with the card driver. Instead, it is internally looped back; it > > is a simulated interface. I don't see how shoving the interface > > into promiscuous mode would help. > > Putting the fxp driver into promiscuous mode involves poking at bits > of the interface hardware. This appears to fix whatever it is that's > going wrong. If this problem hasn't already been dealt with in the > -current/-stable drivers, I hope DG is looking at it. So how the heck can pinging the loopback *ever* fail because of an unrelated driver? The only think I can think of is a screwed routing table or a screwed arp table. Yet he says neither of these change when the problem is manifest. Or.... his ethernet card is denial-of-service attacking him?!? Maybe the mbufs are all allocated, so he can't get any for the loopback ping? This could point to a bad driver assumption, like you can transmit when a receive is pending, but the hardware has one queue for both sets of operations, or something eqully idiotic. Or it may be bad code. I still don't see how putting the card into a mode where it will see yet more packets could fix it. There is som suspicious code about preemptively freeing mbufs in som bad cases surrounded by #ifdef's for the BPF. But to trigger, the BPF would have to actually be in the process of being used (ifp->if_bpf != NULL). Hmmm. If this theory is true, then it's likely that what's holding the mbufs is fixed by the fxp_stop() at the top of fxp_init() when the mode is changed. Technically, the SIOCSIFFLAGS case in fxp_ioctl() should fix this with a standard ifconfig down then up. Let's see... This is an interesting problem... I'm going to provide some possible hacks. Normally I don't hack drivers for cards that I don't have available for test and have nop documentation for, but with the wedges you are seeing, these are what I'd try for myself. 8-). *DON'T* mix these patches!!! First, try this patch: ---------------------------------------------------------------------------- Index: if_fxp.c =================================================================== RCS file: /b/cvstree/ncvs/src/sys/pci/if_fxp.c,v retrieving revision 1.39 diff -c -r1.39 if_fxp.c *** 1.39 1997/09/05 10:23:54 --- if_fxp.c 1997/09/26 10:24:47 *************** *** 1241,1247 **** cbp->tno_int = 0; /* (disable) tx not okay interrupt */ cbp->ci_int = 0; /* interrupt on CU not active */ cbp->save_bf = prm; /* save bad frames */ ! cbp->disc_short_rx = !prm; /* discard short packets */ cbp->underrun_retry = 1; /* retry mode (1) on DMA underrun */ cbp->mediatype = !sc->phy_10Mbps_only; /* interface mode */ cbp->nsai = 1; /* (don't) disable source addr insert */ --- 1241,1247 ---- cbp->tno_int = 0; /* (disable) tx not okay interrupt */ cbp->ci_int = 0; /* interrupt on CU not active */ cbp->save_bf = prm; /* save bad frames */ ! cbp->disc_short_rx = 0; /* discard short packets */ cbp->underrun_retry = 1; /* retry mode (1) on DMA underrun */ cbp->mediatype = !sc->phy_10Mbps_only; /* interface mode */ cbp->nsai = 1; /* (don't) disable source addr insert */ *************** *** 1253,1259 **** cbp->promiscuous = prm; /* promiscuous mode */ cbp->bcast_disable = 0; /* (don't) disable broadcasts */ cbp->crscdt = 0; /* (CRS only) */ ! cbp->stripping = !prm; /* truncate rx packet to byte count */ cbp->padding = 1; /* (do) pad short tx packets */ cbp->rcv_crc_xfer = 0; /* (don't) xfer CRC to host */ cbp->force_fdx = 0; /* (don't) force full duplex */ --- 1253,1259 ---- cbp->promiscuous = prm; /* promiscuous mode */ cbp->bcast_disable = 0; /* (don't) disable broadcasts */ cbp->crscdt = 0; /* (CRS only) */ ! cbp->stripping = 0; /* truncate rx packet to byte count */ cbp->padding = 1; /* (do) pad short tx packets */ cbp->rcv_crc_xfer = 0; /* (don't) xfer CRC to host */ cbp->force_fdx = 0; /* (don't) force full duplex */ ---------------------------------------------------------------------------- This patch will work if the hardware has a bug that depends on one of these two bits. If this doesn't fix the problem, and you can't reset it by ifconfiging it down and up, but promiscuous mode still works, then there is a bug in fxp_intr() that causes leaks. Most likely, it's an error condition that results in bad packets that's not being caught by the driver. This could be a hardware bug where non-local packets are "leaking", or it could be an otherwise unsignalled bad status. I believe this patch *may* catch these cases (I don't have a hardware manual to check it's correctness, or if the fields hold true out of promiscuous mode: ---------------------------------------------------------------------------- Index: if_fxp.c =================================================================== RCS file: /b/cvstree/ncvs/src/sys/pci/if_fxp.c,v retrieving revision 1.39 diff -c -r1.39 if_fxp.c *** 1.39 1997/09/05 10:23:54 --- if_fxp.c 1997/09/26 11:22:40 *************** *** 989,1009 **** bpf_tap(FXP_BPFTAP_ARG(ifp), mtod(m, caddr_t), total_len); - /* - * Only pass this packet up - * if it is for us. - */ - if ((ifp->if_flags & - IFF_PROMISC) && - (rfa->rfa_status & - FXP_RFA_STATUS_IAMATCH) && - (eh->ether_dhost[0] & 1) - == 0) { - m_freem(m); - goto rcvloop; - } } #endif /* NBPFILTER > 0 */ m->m_data += sizeof(struct ether_header); ether_input(ifp, eh, m); --- 989,1013 ---- bpf_tap(FXP_BPFTAP_ARG(ifp), mtod(m, caddr_t), total_len); } #endif /* NBPFILTER > 0 */ + /* + * Only pass this packet up + * if it is for us. + */ + if ( + /* + * XXX remove the next two lines + * XXX and this comment if your + * XXX interface goes away entirely + * XXX with this patch + */ + (rfa->rfa_status & + FXP_RFA_STATUS_IAMATCH) && + (eh->ether_dhost[0] & 1) == 0) { + m_freem(m); + goto rcvloop; + } m->m_data += sizeof(struct ether_header); ether_input(ifp, eh, m); ---------------------------------------------------------------------------- Note the funny thing about this: the old code assumes PROMISC mode, so it *may* be the culprit, *IF* the BPF is present *AND* active, and thus the reason setting PROMISC fixes it. The FXP_RFA_STATUS_IAMATCH may not happen out of PROMISC mode (see comment). If all this fails, then you have an mbuf leak (this should cover the soft reset case, the transmit buffer release, and the realloc/reinit receive buffers, since fxp_stop() does all this and is called on a down then up. If you have an mbuf leak, then its a driver logic bug, and I don't know the hardware well enough to find one of those very easily. On the other hand, if a down-then-up fixes it, then one of the three stops is the unwedger. If it's the card reset, then the hardware is screwed. If it's one of the other, then the code is at fault. It may be that the thing has a single queue, and can't transmit while a recieve is outstanding, or vice versa. Maybe they studdied under the "multidrop" serial board vendors, or at the VMS academy of terminal driver writing both have the one queue problem). If the hardware is screwed, and it is truly pounding on the control bits that gets you back, then *maybe* this patch will fix you; it's a hell of a kludge, but... it pounds the control bits the same way you do manually: ---------------------------------------------------------------------------- Index: if_fxp.c =================================================================== RCS file: /b/cvstree/ncvs/src/sys/pci/if_fxp.c,v retrieving revision 1.39 diff -c -r1.39 if_fxp.c *** 1.39 1997/09/05 10:23:54 --- if_fxp.c 1997/09/26 11:02:09 *************** *** 1167,1172 **** --- 1167,1176 ---- log(LOG_ERR, FXP_FORMAT ": device timeout\n", FXP_ARGS(sc)); ifp->if_oerrors++; + /* bletcherous hack to pound bits to unwedge card*/ + ifp->if_flags ^= IFF_PROMISC; /* toggle it*/ + fxp_init(sc); + ifp->if_flags ^= IFF_PROMISC; /* toggle it back*/ fxp_init(sc); } ---------------------------------------------------------------------------- The real pain with this is that (1) it assumes the watchdog is being called (ie: transmits are actually failing), (2) It's take a "long" time... maybe enough for you to feel the hiccup (but nothing you can do about that if the chip is broken), and (3) you're going to get some packets which aren't meant for you in a tiny (but annoying) window. A better fix would call the watchdog when you've been waiting a "long time" for an ACK, so it wouldn't depend on the transmit not functioning; for all I know, it is. 8-( Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-stable Fri Sep 26 07:25:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA06986 for stable-outgoing; Fri, 26 Sep 1997 07:25:43 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA06980; Fri, 26 Sep 1997 07:25:38 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id HAA25055; Fri, 26 Sep 1997 07:26:28 -0700 (PDT) Message-Id: <199709261426.HAA25055@implode.root.com> To: Mike Smith cc: tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-reply-to: Your message of "Fri, 26 Sep 1997 18:43:16 +0930." <199709260913.SAA00775@word.smith.net.au> From: David Greenman Reply-To: dg@root.com Date: Fri, 26 Sep 1997 07:26:27 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Putting the fxp driver into promiscuous mode involves poking at bits >of the interface hardware. This appears to fix whatever it is that's >going wrong. If this problem hasn't already been dealt with in the >-current/-stable drivers, I hope DG is looking at it. The card doesn't need to be put into promiscuous mode. Doing that has the side effect of resetting the chip, which is all that is really needed. This can be accomplished by doing a simple "ifconfig fxp0 up". There isn't anything wrong with the driver and working around the bug in the hardware is difficult since there are no symptoms other than packets not coming in anymore. The problem is well known and is covered in the errata for the 82557 chip. Let me say again that this bug should only show itself when there is something wrong on the network and usually only when the card is in 10Mbps mode. I haven't seen a failure in the 9+ months that I've used the Pro/100B in wcarchive, it's never happened here locally under regular usage (I use these cards in about 5 machines), and in fact I've only seen it occur myself when I've killed the power on my hub. Yahoo was having this occur whenever the ISP power cycled the switch that the machines were connected to, and I think they worked around it with some sort of ping/ifconfig cron job. One of these days I'll conjure up some sort of hack to fix the problem. Intel recommends reprogramming the multicast filter (!) if no packets are received for some number of seconds. This is difficult to implement in the current design of the driver. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-stable Fri Sep 26 07:30:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA07329 for stable-outgoing; Fri, 26 Sep 1997 07:30:31 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA07324; Fri, 26 Sep 1997 07:30:28 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id HAA25105; Fri, 26 Sep 1997 07:31:43 -0700 (PDT) Message-Id: <199709261431.HAA25105@implode.root.com> To: Terry Lambert cc: tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-reply-to: Your message of "Fri, 26 Sep 1997 11:31:45 -0000." <199709261131.EAA19446@usr09.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Fri, 26 Sep 1997 07:31:43 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >This is an interesting problem... I'm going to provide some possible >hacks. Normally I don't hack drivers for cards that I don't have Wrong on all accounts. Let's not cloud the issue with irrelevant information and wrong patches. It's difficult enough for me to provide accurate information without having to battle misinformation. Thanks. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-stable Fri Sep 26 08:55:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA12171 for stable-outgoing; Fri, 26 Sep 1997 08:55:37 -0700 (PDT) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA12165; Fri, 26 Sep 1997 08:55:34 -0700 (PDT) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id IAA02046; Fri, 26 Sep 1997 08:56:42 -0700 (PDT) Date: Fri, 26 Sep 1997 08:56:42 -0700 (PDT) From: Jim Shankland Message-Id: <199709261556.IAA02046@biggusdiskus.flyingfox.com> To: tarkhil@mgt.msk.ru Subject: fxp driver problem? Cc: hackers@freebsd.org, stable@freebsd.org Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Re Alex Povolotsky's problem (fxp driver becomes unresponsive, putting it into promiscuous mode briefly makes it work again): I am getting sporadic reports of a similar (or the same) problem with the fxp driver running on a hacked-up (by me) version of the 2.2.2-RELEASE kernel. In our case, the fxp driver becomes unresponsive, bringing the interface down and back up again with ifconfig brings it back to life. I will likely be putting some effort into tracking this one down. This is complicated by the fact that the failure happens only on a heavily used interface on a production system, and happens maybe once a month at most. If anyone (dg?) has ideas on what to instrument to figure out what's going on, I'm all ears :-). Jim Shankland Flying Fox Computer Systems, Inc. From owner-freebsd-stable Fri Sep 26 09:16:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA13452 for stable-outgoing; Fri, 26 Sep 1997 09:16:34 -0700 (PDT) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA13447; Fri, 26 Sep 1997 09:16:29 -0700 (PDT) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id JAA02310; Fri, 26 Sep 1997 09:17:32 -0700 (PDT) Date: Fri, 26 Sep 1997 09:17:32 -0700 (PDT) From: Jim Shankland Message-Id: <199709261617.JAA02310@biggusdiskus.flyingfox.com> To: dg@root.com Subject: Re: fxp driver/chip problems Cc: hackers@freebsd.org, stable@freebsd.org Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks for the information, David. OK, I won't go off hunting for a bug in the fxp driver :-). As another data point, in my case, it's the rev 1 card, and it's in 10 Mb mode. Unfortunately, I have no control over the hub being used, so I'll need to either upgrade to a rev 2 card, and hope that "Intel (rev 2) inside" fixes it, or (sigh) write a little "ping daemon" that resets the interface after several lost ping packets to the gateway on the wire. The things I stoop to :-)! Jim Shankland Flying Fox Computer Systems, Inc. From owner-freebsd-stable Fri Sep 26 11:24:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA20330 for stable-outgoing; Fri, 26 Sep 1997 11:24:01 -0700 (PDT) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA20306 for ; Fri, 26 Sep 1997 11:23:57 -0700 (PDT) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xEf3G-0001EJ-00; Fri, 26 Sep 1997 11:23:42 -0700 Date: Fri, 26 Sep 1997 11:23:39 -0700 (PDT) From: Tom To: Mike Smith cc: Matt Behrens , Mike Burgett , "freebsd-stable@freebsd.org" Subject: Re: [Q] 2.2.5 bind release In-Reply-To: <199709260716.QAA00314@word.smith.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 26 Sep 1997, Mike Smith wrote: > > > I'm 99.9% sure it'll be 4.9.6. 8.1.1 has the strongest nameserver but its > > > resolver library is sorely lacking and would probably cause many packages > > > to break. > > > > Has FreeBSD ever use the BIND resolver library? It seems to me that the > > FreeBSD resolver is whole mix of different things, and is not 4.9.6 > > either. > > What sort of dopey question is this? Have a look at src/contrib/bind > and decide for yourself what FreeBSD uses. Just for named, nslookup, etc. The 4.9.6 resolver has no support for /etc/host.conf, and yet the FreeBSD resolver does... Please refrain from derogatory comments. They are unprofessional, and don't belong on the list. > > Besides the BIND resolver is mainly for systems that come with such a > > useless/broken resolver that anything is better (ex SunOS 4.1). > > Not by half. Really? The 4.9.6 resolver has no support for /etc/host.conf and /etc/hosts. Nearly everybody has hacked their own goodies into the resolver, and so has FreeBSD. > mike Tom From owner-freebsd-stable Fri Sep 26 11:26:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA20514 for stable-outgoing; Fri, 26 Sep 1997 11:26:26 -0700 (PDT) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA20508 for ; Fri, 26 Sep 1997 11:26:22 -0700 (PDT) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xEf5P-0001En-00; Fri, 26 Sep 1997 11:25:55 -0700 Date: Fri, 26 Sep 1997 11:25:52 -0700 (PDT) From: Tom To: Don Lewis cc: John Hay , freebsd-stable@freebsd.org Subject: Re: [Q] 2.2.5 bind release In-Reply-To: <199709261014.DAA20428@salsa.gv.tsc.tdk.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 26 Sep 1997, Don Lewis wrote: > On Sep 25, 11:59pm, Tom wrote: > } Subject: Re: [Q] 2.2.5 bind release > > } 4.9.6 resolver does not use /etc/host.conf or /etc/hosts, yet the > } FreeBSD resolver does. The FreeBSD resolver is also capable of using > } NIS host maps. The FreeBSD resolver seems to similar to resolv+ > } with various other addons bolted on it (NIS host maps for one, as resolv+ > } as DNS-only). > > I think the BIND 8.1.1 resolver has this stuff as well. I haven't had > the time to examine it closely. Perhaps, but not the 4.9.x resolver certainly didn't. Paul Vixie wanted the resolver library to clean and simple in 4.9.x Tom From owner-freebsd-stable Fri Sep 26 14:08:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA27831 for stable-outgoing; Fri, 26 Sep 1997 14:08:34 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA27811; Fri, 26 Sep 1997 14:08:21 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id OAA13493; Fri, 26 Sep 1997 14:07:32 -0700 (MST) From: Terry Lambert Message-Id: <199709262107.OAA13493@usr08.primenet.com> Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) To: dg@root.com Date: Fri, 26 Sep 1997 21:07:31 +0000 (GMT) Cc: tlambert@primenet.com, tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: <199709261431.HAA25105@implode.root.com> from "David Greenman" at Sep 26, 97 07:31:43 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >This is an interesting problem... I'm going to provide some possible > >hacks. Normally I don't hack drivers for cards that I don't have > > Wrong on all accounts. Let's not cloud the issue with irrelevant > information and wrong patches. It's difficult enough for me to provide > accurate information without having to battle misinformation. Thanks. This seemed like an issue that simply hadn't been addresssed, but which was well known, according to early postings. Subsequent traffic (which occurred *after* my posting makes it clear that up/downing the interface will fix it as well. Clearly, the very last suggestion, coupled with the suggested receive idle timer, will work, though it is not pretty. Playing with the control bits, as well, may very well "resolve" the deadlock. As far as mbuf denial, it's clearly not the problem, but it could be *a* problem. I should have suggested "vmstat -m | grep mbuf" first, though. 8-). I'm not sure why that status bit is not checked in all cases, though if ether_input() isn't puked, all it should do is result in bogus packets coming further up the stack than they should. 8-(. Anyway, it's still an interesting problem: how to deal with broken hardware. Sounds like a job for a high resoloution timer... ;-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-stable Fri Sep 26 14:34:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA29375 for stable-outgoing; Fri, 26 Sep 1997 14:34:54 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA29370; Fri, 26 Sep 1997 14:34:51 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id OAA14622; Fri, 26 Sep 1997 14:34:01 -0700 (MST) From: Terry Lambert Message-Id: <199709262134.OAA14622@usr08.primenet.com> Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) To: dg@root.com Date: Fri, 26 Sep 1997 21:34:01 +0000 (GMT) Cc: mike@smith.net.au, tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: <199709261426.HAA25055@implode.root.com> from "David Greenman" at Sep 26, 97 07:26:27 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > One of these days I'll conjure up some sort of hack to fix the problem. > Intel recommends reprogramming the multicast filter (!) if no packets are > received for some number of seconds. This is difficult to implement in the > current design of the driver. Plus it leaves your butt hanging in the wind for several seconds on a *supposedly* 100Mbit card. Pretty frigging ugly. I guess the errata don't say what causes the bug (like a collision? That would explain the 100Mbit being more robust...), like the macrocell for the chip is actually mask programmed and the unused bit sets aren't specifically disallowed, or a header collision can't be dealt with because the header accumulation buffer isn't cleared, or something dumb like that? Do we know that the "cron ping soloution" actually works? If it does, can we set up a bogus gateway route to avoid getting a packet back for one sent to see if it's the packet out or the packet back that does it? I'm betting out at this point... If this works, then a timer set to bogusly send a packet to ourselves would not bother anyone else on the network who wasn't in promiscuous mode and running a network monitor, and it would be filterable there. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-stable Fri Sep 26 18:00:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA11434 for stable-outgoing; Fri, 26 Sep 1997 18:00:33 -0700 (PDT) Received: from tok.qiv.com (uucp@[204.214.141.211]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA11417 for ; Fri, 26 Sep 1997 18:00:29 -0700 (PDT) Received: (from uucp@localhost) by tok.qiv.com (8.8.6/8.8.5) with UUCP id UAA09576 for stable@freebsd.org; Fri, 26 Sep 1997 20:00:25 -0500 (CDT) Received: from localhost (jdn@localhost) by acp.qiv.com (8.8.6/8.8.5) with SMTP id TAA00259 for ; Fri, 26 Sep 1997 19:59:00 -0500 (CDT) X-Authentication-Warning: acp.qiv.com: jdn owned process doing -bs Date: Fri, 26 Sep 1997 19:59:00 -0500 (CDT) From: "Jay D. Nelson" To: stable@freebsd.org Subject: Re: 2nd Notice: 4 days to code freeze in RELENG_2_2 branch. In-Reply-To: <8488.875262955@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Would it be possible to uncomment the HDB capabilities in UUCP for the next release? Even though UUCP died years ago, I'm converting more older Unix systems than ever. Most sites don't need the extra capabilities of Taylor, and if HDB capability came out of the box, it would save those of us who have to do this some headaches. (I know about uuconv -- but that's not the issue. If the client doesn't need Taylor, HDB is simpler to maintain.) I think the increase in binary size is worth the price. Thanks -- Jay From owner-freebsd-stable Fri Sep 26 18:09:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA11893 for stable-outgoing; Fri, 26 Sep 1997 18:09:07 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA11886; Fri, 26 Sep 1997 18:09:03 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id SAA01062; Fri, 26 Sep 1997 18:10:48 -0700 (PDT) Message-Id: <199709270110.SAA01062@implode.root.com> To: Terry Lambert cc: tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-reply-to: Your message of "Fri, 26 Sep 1997 21:34:01 -0000." <199709262134.OAA14622@usr08.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Fri, 26 Sep 1997 18:10:48 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> One of these days I'll conjure up some sort of hack to fix the problem. >> Intel recommends reprogramming the multicast filter (!) if no packets are >> received for some number of seconds. This is difficult to implement in the >> current design of the driver. > >Plus it leaves your butt hanging in the wind for several seconds on >a *supposedly* 100Mbit card. Pretty frigging ugly. Uh, well, as far as I can tell, for 100Mbps, the problem only occurs when the link transitions to 10Mbps first and then sees garbage. Since the link speed is autodetected, it's easy to see how this might happen when someone power cycles a hub or something. It's less clear how it could occur in normal use at 10Mbps. Perhaps the problem doesn't occur with some hubs due to the hub/switch regeneration of the synch bits (which many hubs apparantly will do). >I guess the errata don't say what causes the bug (like a collision? >That would explain the 100Mbit being more robust...), It has something to do with the synchronization bits that preceed the packet data, but I can't find the errata right now (I recall that is was quite vague in any case). >Do we know that the "cron ping soloution" actually works? If it >does, can we set up a bogus gateway route to avoid getting a packet >back for one sent to see if it's the packet out or the packet back >that does it? I'm betting out at this point... The problem is that the receiver circuitry in the chip locks up, so you stop getting the echo response; the card continues to transmit, however. For whatever reason, reprogramming the multicast filter or resetting the entire chip corrects the condition. (The multicast filter is part of the receiver circuit, and it is apparantly selectively reset when the multicast filter is reprogrammed). >If this works, then a timer set to bogusly send a packet to ourselves >would not bother anyone else on the network who wasn't in promiscuous >mode and running a network monitor, and it would be filterable there. You can't send a packet to yourself under normal circumstances (ethernet is a simplex device). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-stable Fri Sep 26 18:32:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA13266 for stable-outgoing; Fri, 26 Sep 1997 18:32:13 -0700 (PDT) Received: from ns.NL.net (ns.NL.net [193.78.240.1]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA13249 for ; Fri, 26 Sep 1997 18:32:06 -0700 (PDT) Received: from stuyts by ns.NL.net (5.65b/NLnet1.3) id AA11267; Sat, 27 Sep 1997 03:22:16 +0200 Received: from daneel.stuyts.nl (daneel.stuyts.nl [193.78.231.7]) by terminus.stuyts.nl (8.8.7/8.8.5) with ESMTP id DAA03060; Sat, 27 Sep 1997 03:19:43 +0200 (MET DST) Received: (from benst@localhost) by daneel.stuyts.nl (8.8.5/8.8.5) id DAA22457; Sat, 27 Sep 1997 03:19:30 +0200 (MET DST) Message-Id: <199709270119.DAA22457@daneel.stuyts.nl> Content-Type: text/plain Mime-Version: 1.0 (NeXT Mail 3.3 v118.2) In-Reply-To: <8488.875262955@time.cdrom.com> X-Nextstep-Mailer: Mail 3.3 (Enhance 1.2) Received: by NeXT.Mailer (1.118.2) From: Ben Stuyts Date: Sat, 27 Sep 97 03:19:27 +0200 To: "Jordan K. Hubbard" Subject: Re: 2nd Notice: 4 days to code freeze in RELENG_2_2 branch. Cc: stable@FreeBSD.ORG, joerg_wunsch@uriah.heep.sax.de Reply-To: ben@stuyts.nl References: <8488.875262955@time.cdrom.com> Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello, On Fri, 26 Sep 1997, "Jordan K. Hubbard" wrote: > This will be the usual FreeBSD style code-freeze: New features > and radical changes not allowed, bug fixes and cleanup permitted. I just found out that the problem with fixating cdr's are still present in RELENG_2_2. (cvsupped two days ago): [terminus.stuyts.nl src/worm]167: sudo ./burncd /var/tmp/cd Place CD in the worm drive now and press return: 510966 kilobytes, 1693 seconds 1021932+0 records in 25548+1 records out 523229184 bytes transferred in 1706.858504 secs (306545 bytes/sec) /var/log/messages says after writing, but before finishing, so probably during fixating: Sep 27 02:56:24 terminus /kernel: worm0(ahc0:5:0): MEDIUM ERROR info:0x80000082 asc:34,0 I tried a suggestion posted by J"org here, but that doesn't seem to work: %scsi -f /dev/rworm0.ctl -s 3600 -c "e9 0 0 0 0 0 0 0 1 0" SCIOCCOMMAND ioctl: Command accepted. return status 3 (Sense Returned) host adapter status 2 Command out (10 of 10): e9 00 00 00 00 00 00 00 01 00 Error code is "current errors" Segment number is 00 Sense key is "Illegal request" The Information field is 80000002 (-2147483646). The Command Specific Information field is 00000000 (0). Additional sense code: 82 Additional sense code qualifier: 00 sense (32 of 48): f0 00 05 80 00 00 02 0a 00 00 00 00 82 00 00 00 00 00 00 ff 74 bf 3a 00 00 00 00 00 00 00 00 00 %scsi -f /dev/rworm0.ctl -s 3600 -c "35 0 0 0 0 0 0 0 0 0" SCIOCCOMMAND ioctl: Command accepted. return status 3 (Sense Returned) host adapter status 2 Command out (10 of 10): 35 00 00 00 00 00 00 00 00 00 Error code is "current errors" Segment number is 00 Sense key is "Illegal request" The Information field is 80000000 (-2147483648). The Command Specific Information field is 00000000 (0). Additional sense code: 2c Additional sense code qualifier: 00 sense (32 of 48): f0 00 05 80 00 00 00 0a 00 00 00 00 2c 00 00 00 00 00 00 ff 74 bf 3a 00 00 00 00 00 00 00 00 00 %scsi -f /dev/rworm0.ctl -s 3600 -c "e9 0 0 0 0 0 0 0 1 0" SCIOCCOMMAND ioctl: Command accepted. return status 3 (Sense Returned) host adapter status 2 Command out (10 of 10): e9 00 00 00 00 00 00 00 01 00 Error code is "current errors" Segment number is 00 Sense key is "Illegal request" The Information field is 80000002 (-2147483646). The Command Specific Information field is 00000000 (0). Additional sense code: 82 Additional sense code qualifier: 00 sense (32 of 48): f0 00 05 80 00 00 02 0a 00 00 00 00 82 00 00 00 00 00 00 ff 74 bf 3a 00 00 00 00 00 00 00 00 00 This is with a Philips CDD2600 drive. Mounting the same cd after all this did work though. Checked it, and it verified fine. If there's anything I can do or check, please let me know. With kind regards, Ben Stuyts From owner-freebsd-stable Fri Sep 26 19:53:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA18572 for stable-outgoing; Fri, 26 Sep 1997 19:53:34 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA18567; Fri, 26 Sep 1997 19:53:31 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id TAA02076; Fri, 26 Sep 1997 19:53:12 -0700 (MST) From: Terry Lambert Message-Id: <199709270253.TAA02076@usr08.primenet.com> Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) To: dg@root.com Date: Sat, 27 Sep 1997 02:53:12 +0000 (GMT) Cc: tlambert@primenet.com, tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: <199709270110.SAA01062@implode.root.com> from "David Greenman" at Sep 26, 97 06:10:48 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >If this works, then a timer set to bogusly send a packet to ourselves > >would not bother anyone else on the network who wasn't in promiscuous > >mode and running a network monitor, and it would be filterable there. > > You can't send a packet to yourself under normal circumstances (ethernet > is a simplex device). I meant "send it addressed to my own address"... from what you say, though, the "ping soloutoin" probably is just a conicidence, so it's a non-starter. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-stable Fri Sep 26 22:24:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA27383 for stable-outgoing; Fri, 26 Sep 1997 22:24:19 -0700 (PDT) Received: from kelly.prima.ruhr.de (root@kelly.prima.ruhr.de [141.39.232.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA27328; Fri, 26 Sep 1997 22:24:05 -0700 (PDT) Received: from chokepnt.prima.ruhr.de (DialPPP-1-83.rz.ruhr-uni-bochum.de [134.147.1.83]) by kelly.prima.ruhr.de (8.8.7/8.6.9) with SMTP id HAA22380; Sat, 27 Sep 1997 07:24:09 +0200 Message-ID: <342A79F5.41C67EA6@prima.ruhr.de> Date: Thu, 25 Sep 1997 16:49:25 +0200 From: Philipp Reichmuth X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2-STABLE i386) MIME-Version: 1.0 To: stable@freebsd.org CC: hardware@freebsd.org Subject: K6 Update & AMD Statement Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi folks! Good news for the K6: I just got mine swapped by my dealer; it was a revision 9721 chip, and he swapped it for a 9735 chip. It now works fine. I'll redo the make world for a couple of times the next weeks and see what I'll get. Second good news: I wrote to AMD about it, and they seem genuinely concerned with it, or so I gather from their mail. Here's what they wrote (follows) Philipp ==================> begin AMD mail <============ Dear Philipp, 1. We believe you are encountering Erratum 2.6.2 that is fully documented in the AMD-K6 MMX Enhanced Processor Revision Guide posted on our website, www.amd.com. Due to the long list of rare conditions necessary for this erratum to occur, the issue does not effect general users in a DOS or Windows environment. It appears to be limited to a special cases as in the Linux kernal re-compile. 2. A design change that fixes the erratum has been identified and is currently being implemented in a future revision of the AMD-K6 processor. 3. AMD stands behind its products and wants you to be fully satisfied with your choice. To this end, we are offering to replace your processor as the new revision becomes available. 4 To replace your processor we need the following information. We will contact you in about 3 weeks with more specifics on when and how the processor will be replaced. - Name - Address - Phone Number - Type of System or Motherboard - Processor Frequency Kind Regards Tvrtko AMD Hotline / Technical Support. =========================> End AMD Stuff <========================= (but please don't post all this into the wide world - it's a bit touchy with personal email) From owner-freebsd-stable Fri Sep 26 23:12:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA00832 for stable-outgoing; Fri, 26 Sep 1997 23:12:20 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241] (may be forged)) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA00826; Fri, 26 Sep 1997 23:12:17 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id XAA19592; Fri, 26 Sep 1997 23:10:25 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199709270610.XAA19592@GndRsh.aac.dev.com> Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-Reply-To: <199709270110.SAA01062@implode.root.com> from David Greenman at "Sep 26, 97 06:10:48 pm" To: dg@root.com Date: Fri, 26 Sep 1997 23:10:25 -0700 (PDT) Cc: tlambert@primenet.com, tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > You can't send a packet to yourself under normal circumstances (ethernet > is a simplex device). Only broken NIC chips are simplex, even the 82586 is actually capable of hering itself talk on the wire, though most drives do not set the chip into this mode. Either way ``ethernet is _not_ a simplex device''. Infact the 82586 has the ability to due cource grain TDR (Time Domain Reflectonmetry) for finding bad coax (thick or thin). -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-stable Sat Sep 27 01:14:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA08786 for stable-outgoing; Sat, 27 Sep 1997 01:14:38 -0700 (PDT) Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA08781; Sat, 27 Sep 1997 01:14:36 -0700 (PDT) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.4/8.8.4) with ESMTP id BAA23841; Sat, 27 Sep 1997 01:11:53 -0700 (PDT) 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 BAA10855; Sat, 27 Sep 1997 01:11:52 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id BAA00487; Sat, 27 Sep 1997 01:11:51 -0700 (PDT) From: Don Lewis Message-Id: <199709270811.BAA00487@salsa.gv.tsc.tdk.com> Date: Sat, 27 Sep 1997 01:11:51 -0700 In-Reply-To: "Rodney W. Grimes" "Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail)" (Sep 26, 11:10pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: "Rodney W. Grimes" , dg@root.com Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) Cc: tlambert@primenet.com, tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sep 26, 11:10pm, "Rodney W. Grimes" wrote: } Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's m } > You can't send a packet to yourself under normal circumstances (ethernet } > is a simplex device). } } Only broken NIC chips are simplex, even the 82586 is actually capable } of hering itself talk on the wire, though most drives do not set } the chip into this mode. Either way ``ethernet is _not_ a simplex } device''. That's only true of coaxial media. Over twisted pair, if you see data start arriving on the receive pair while your transmitting then you have to assume that the data is being sent by another station and you've got a collision situation. However, you may have the option to loop back your transmitted data to your receiver after the receiver stage where collision sensing is done. I believe this is known as natural loopback. I don't think it's commonly used. From owner-freebsd-stable Sat Sep 27 01:23:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA09357 for stable-outgoing; Sat, 27 Sep 1997 01:23:57 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA09352 for ; Sat, 27 Sep 1997 01:23:53 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA17803; Sat, 27 Sep 1997 10:23:42 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id KAA16028; Sat, 27 Sep 1997 10:16:31 +0200 (MET DST) Message-ID: <19970927101631.VO25657@uriah.heep.sax.de> Date: Sat, 27 Sep 1997 10:16:31 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: ben@stuyts.nl Cc: jkh@time.cdrom.com (Jordan K. Hubbard), stable@FreeBSD.ORG Subject: Re: 2nd Notice: 4 days to code freeze in RELENG_2_2 branch. References: <8488.875262955@time.cdrom.com> <199709270119.DAA22457@daneel.stuyts.nl> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709270119.DAA22457@daneel.stuyts.nl>; from Ben Stuyts on Sep 27, 1997 03:19:27 +0200 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Ben Stuyts wrote: > I just found out that the problem with fixating cdr's are still present in > RELENG_2_2. (cvsupped two days ago): Try to see whether your problems are solved if you omit the call to `foo_prepare_track()' from within `foo_finalize_track()'. Jean-Marc put it there in order to re-adjust the blocksize setting of the drive. Apparently, sending mode page 0x21 to the drive isn't something the drive loves very much if no write data are following. I've got a patch from Jean-Marc that reduces this call to a plain MODE SELECT with just a buffer header, and no actual page. I haven't been able to test this patch yet, however. It is likely that the same things are broken in -current, btw., but apparently nobody is using CD-Rs with a -current machine. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-stable Sat Sep 27 04:42:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA19904 for stable-outgoing; Sat, 27 Sep 1997 04:42:50 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA19899; Sat, 27 Sep 1997 04:42:41 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id EAA24360; Sat, 27 Sep 1997 04:42:15 -0700 (MST) From: Terry Lambert Message-Id: <199709271142.EAA24360@usr04.primenet.com> Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) To: Don.Lewis@tsc.tdk.com (Don Lewis) Date: Sat, 27 Sep 1997 11:42:14 +0000 (GMT) Cc: rgrimes@GndRsh.aac.dev.com, dg@root.com, tlambert@primenet.com, tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: <199709270811.BAA00487@salsa.gv.tsc.tdk.com> from "Don Lewis" at Sep 27, 97 01:11:51 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > } Only broken NIC chips are simplex, even the 82586 is actually capable > } of hering itself talk on the wire, though most drives do not set > } the chip into this mode. Either way ``ethernet is _not_ a simplex > } device''. > > That's only true of coaxial media. Over twisted pair, if you see > data start arriving on the receive pair while your transmitting then > you have to assume that the data is being sent by another station > and you've got a collision situation. Isn't this the hub's responsibility to distinguish and prevent? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-stable Sat Sep 27 05:39:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA21521 for stable-outgoing; Sat, 27 Sep 1997 05:39:55 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA21511 for ; Sat, 27 Sep 1997 05:39:49 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 17059 invoked by uid 1001); 27 Sep 1997 12:39:45 +0000 (GMT) To: tlambert@primenet.com Cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-Reply-To: Your message of "Sat, 27 Sep 1997 11:42:14 +0000 (GMT)" References: <199709271142.EAA24360@usr04.primenet.com> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 27 Sep 1997 14:39:45 +0200 Message-ID: <17057.875363985@verdi.nethelp.no> Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > That's only true of coaxial media. Over twisted pair, if you see > > data start arriving on the receive pair while your transmitting then > > you have to assume that the data is being sent by another station > > and you've got a collision situation. > > Isn't this the hub's responsibility to distinguish and prevent? Nope. A hub doesn't do anything with collisions - it just propagates them bit by bit. The NICs sense the collision. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-stable Sat Sep 27 06:15:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA22725 for stable-outgoing; Sat, 27 Sep 1997 06:15:27 -0700 (PDT) Received: from phoenix.its.rpi.edu (phoenix.its.rpi.edu [128.113.161.45]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA22720; Sat, 27 Sep 1997 06:15:20 -0700 (PDT) Received: from localhost (dec@localhost) by phoenix.its.rpi.edu (8.8.7/8.8.7) with SMTP id JAA25094; Sat, 27 Sep 1997 09:16:17 -0400 (EDT) Date: Sat, 27 Sep 1997 09:16:17 -0400 (EDT) From: "David E. Cross" To: sthaug@nethelp.no cc: tlambert@primenet.com, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-Reply-To: <17057.875363985@verdi.nethelp.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 27 Sep 1997 sthaug@nethelp.no wrote: > > > That's only true of coaxial media. Over twisted pair, if you see > > > data start arriving on the receive pair while your transmitting then > > > you have to assume that the data is being sent by another station > > > and you've got a collision situation. > > > > Isn't this the hub's responsibility to distinguish and prevent? > > Nope. A hub doesn't do anything with collisions - it just propagates > them bit by bit. The NICs sense the collision. > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no Technically this is not even a colission situation. Many new NICs and Hubs (both must support it to work) support full-duplex 10BaseT, allowing 20MBits/sec. I am not sure what happens when it gets into the hub and needs to be propogated to other ports though *shrug*. Anyway... multiple packets being transmitted at the same time is detected by the NIC, and the NIC then sends a jamming signal which stops all transmissions on the network for a random time (each card that was transmitting durring this time sets a ranom timer for how long to wait, and they all try to re-transmit, using exponential backoff if there are additional collisions). This jamming signal is the actual 'collision', and is what shows up as a colision light on hubs/external transcievers. Excellent and page-turning reading that 802.* ;) -- David Cross From owner-freebsd-stable Sat Sep 27 08:11:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA26427 for stable-outgoing; Sat, 27 Sep 1997 08:11:10 -0700 (PDT) Received: from sabre.goldsword.com (sabre.goldsword.com [199.170.202.32]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA26413; Sat, 27 Sep 1997 08:10:54 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.8.7/8.7.3) id LAA17620; Sat, 27 Sep 1997 11:13:40 -0400 (EDT) Date: Sat, 27 Sep 1997 11:13:40 -0400 (EDT) From: "John T. Farmer" Message-Id: <199709271513.LAA17620@sabre.goldsword.com> To: chokepnt@prima.ruhr.de, stable@FreeBSD.ORG Subject: Re: K6 Update & AMD Statement Cc: hardware@FreeBSD.ORG, jfarmer@goldsword.com Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk That is good news! It also fits in with what I've been hearing for several other sources. I'm very interested in your results on the make world testing... John ------------------------------------------------------------------------- John T. Farmer Proprietor, GoldSword Systems jfarmer@goldsword.com Public Internet Access in East Tennessee dial-in (423)470-9953 for info, e-mail to info@goldsword.com Network Design, Internet Services & Servers, Consulting From owner-freebsd-stable Sat Sep 27 09:06:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA29247 for stable-outgoing; Sat, 27 Sep 1997 09:06:14 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA29203; Sat, 27 Sep 1997 09:05:56 -0700 (PDT) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id SAA05824; Sat, 27 Sep 1997 18:04:54 +0200 (CEST) To: "John T. Farmer" cc: chokepnt@prima.ruhr.de, stable@FreeBSD.ORG, hardware@FreeBSD.ORG, jfarmer@goldsword.com Subject: Re: K6 Update & AMD Statement In-reply-to: Your message of "Sat, 27 Sep 1997 11:13:40 EDT." <199709271513.LAA17620@sabre.goldsword.com> Date: Sat, 27 Sep 1997 18:04:53 +0200 Message-ID: <5817.875376293@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199709271513.LAA17620@sabre.goldsword.com>, "John T. Farmer" writes : >That is good news! It also fits in with what I've been hearing for several >other sources. I'm very interested in your results on the make world >testing... I have a K6/233 here which has by now completed 50 or more make worlds, no complaints. It is marked: AMD-K6-233ANR 3.2V CORE / 3.3V I/O B 9731EJBW -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-stable Sat Sep 27 09:20:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA29942 for stable-outgoing; Sat, 27 Sep 1997 09:20:46 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241] (may be forged)) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA29934; Sat, 27 Sep 1997 09:20:34 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id JAA20171; Sat, 27 Sep 1997 09:16:35 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199709271616.JAA20171@GndRsh.aac.dev.com> Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-Reply-To: <199709270811.BAA00487@salsa.gv.tsc.tdk.com> from Don Lewis at "Sep 27, 97 01:11:51 am" To: Don.Lewis@tsc.tdk.com (Don Lewis) Date: Sat, 27 Sep 1997 09:16:35 -0700 (PDT) Cc: dg@root.com, tlambert@primenet.com, tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Sep 26, 11:10pm, "Rodney W. Grimes" wrote: > } Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's m > } > You can't send a packet to yourself under normal circumstances (ethernet > } > is a simplex device). > } > } Only broken NIC chips are simplex, even the 82586 is actually capable > } of hering itself talk on the wire, though most drives do not set > } the chip into this mode. Either way ``ethernet is _not_ a simplex > } device''. > > That's only true of coaxial media. Over twisted pair, if you see > data start arriving on the receive pair while your transmitting then > you have to assume that the data is being sent by another station > and you've got a collision situation. Add ``in half duplex mode'' and the above holds water. But not for full duplex mode. My statement still holds true ``ethernet is _NOT_ a simplex device''. Why do you the the driver flag ``SIMPLEX'' exists, to deal with the fact that some ethernet interfaces on some systems do infact actuall here them selves talk, infact that use to be pretty much the norm back in the days of VAXEN. Here is another one to think about.... ``If you see data arriving on the receive pair _AND_ the mac source address is not yours you have a collision, or if you are talking to a full duplex port in full duplex mode you are using it.'' These types of designs preclude the use of the cheap TP<->AUI converter chips that just trash a 10Mhz signal onto CD when they see RD go active with XMTD active. Does Intel buy chance use something as stupid as the old 82503 or 82506 for the 10Mb TP interface? > However, you may have the option > to loop back your transmitted data to your receiver after the receiver > stage where collision sensing is done. I believe this is known as > natural loopback. I don't think it's commonly used. More common that looping it after the TP interface chip, and often implemented right in the NIC chip itself. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-stable Sat Sep 27 09:35:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA00795 for stable-outgoing; Sat, 27 Sep 1997 09:35:39 -0700 (PDT) Received: from sabre.goldsword.com (sabre.goldsword.com [199.170.202.32]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA00790; Sat, 27 Sep 1997 09:35:33 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.8.7/8.7.3) id MAA17779; Sat, 27 Sep 1997 12:13:14 -0400 (EDT) Date: Sat, 27 Sep 1997 12:13:14 -0400 (EDT) From: "John T. Farmer" Message-Id: <199709271613.MAA17779@sabre.goldsword.com> To: hackers@FreeBSD.ORG, stable@FreeBSD.ORG, tlambert@primenet.com Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) Cc: dg@root.com, jfarmer@goldsword.com, rgrimes@GndRsh.aac.dev.com, tarkhil@mgt.msk.ru Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 27 Sep 1997 11:42:14 +0000 (GMT) Terry Lambert said: [somebody else...] >> } Only broken NIC chips are simplex, even the 82586 is actually capable >> } of hering itself talk on the wire, though most drives do not set >> } the chip into this mode. Either way ``ethernet is _not_ a simplex >> } device''. >> >> That's only true of coaxial media. Over twisted pair, if you see >> data start arriving on the receive pair while your transmitting then >> you have to assume that the data is being sent by another station >> and you've got a collision situation. > >Isn't this the hub's responsibility to distinguish and prevent? > A hub that does this is usually called a "switch" :^> However, a hub that supports full-duplex links _must_ deal with some of the collision issues but a simpler level than a switch does. John ------------------------------------------------------------------------- John T. Farmer Proprietor, GoldSword Systems jfarmer@goldsword.com Public Internet Access in East Tennessee dial-in (423)470-9953 for info, e-mail to info@goldsword.com Network Design, Internet Services & Servers, Consulting From owner-freebsd-stable Sat Sep 27 09:41:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA01070 for stable-outgoing; Sat, 27 Sep 1997 09:41:03 -0700 (PDT) Received: from sabre.goldsword.com (sabre.goldsword.com [199.170.202.32]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA01062; Sat, 27 Sep 1997 09:40:55 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.8.7/8.7.3) id MAA17859; Sat, 27 Sep 1997 12:43:35 -0400 (EDT) Date: Sat, 27 Sep 1997 12:43:35 -0400 (EDT) From: "John T. Farmer" Message-Id: <199709271643.MAA17859@sabre.goldsword.com> To: phk@critter.freebsd.dk Subject: Re: K6 Update & AMD Statement Cc: chokepnt@prima.ruhr.de, hardware@FreeBSD.ORG, jfarmer@goldsword.com, stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 27 Sep 1997 18:04:53 +0200 Poul-Henning Kamp said: >I have a K6/233 here which has by now completed 50 or more make worlds, >no complaints. > >It is marked: > AMD-K6-233ANR > 3.2V CORE / 3.3V I/O > B 9731EJBW ^^^^^^^^ This is what I'm told is the important part. The stepping must be 9731 or later. I've got a Cyrix 686MX-P200+ coming for testing. I suppose it's time to order a K6-XXX... John ------------------------------------------------------------------------- John T. Farmer Proprietor, GoldSword Systems jfarmer@goldsword.com Public Internet Access in East Tennessee dial-in (423)470-9953 for info, e-mail to info@goldsword.com Network Design, Internet Services & Servers, Consulting From owner-freebsd-stable Sat Sep 27 09:48:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA01351 for stable-outgoing; Sat, 27 Sep 1997 09:48:10 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241] (may be forged)) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA01346; Sat, 27 Sep 1997 09:48:05 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id JAA20293; Sat, 27 Sep 1997 09:47:15 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199709271647.JAA20293@GndRsh.aac.dev.com> Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-Reply-To: <17057.875363985@verdi.nethelp.no> from "sthaug@nethelp.no" at "Sep 27, 97 02:39:45 pm" To: sthaug@nethelp.no Date: Sat, 27 Sep 1997 09:47:15 -0700 (PDT) Cc: tlambert@primenet.com, hackers@FreeBSD.ORG, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > That's only true of coaxial media. Over twisted pair, if you see > > > data start arriving on the receive pair while your transmitting then > > > you have to assume that the data is being sent by another station > > > and you've got a collision situation. > > > > Isn't this the hub's responsibility to distinguish and prevent? > > Nope. A hub doesn't do anything with collisions - it just propagates > them bit by bit. The NICs sense the collision. Better go think so more about that... it depends on the hub! Some hubs that have partitioning ability will automagically partition out someone who starts to transmit if the hub is sending data out that port, this is called autopartitioning and is used to stop baligerant (sp) mau's or Jabberers(sp). If you want something that really tries to ``prevent'' this you want a switch and not a hub, and you want full-duplex non-simplex NIC cards in every box connected to that switch, and no I'm not just talking about 100Base stuff here, it applies to both 10 and 100Base ethernet over TP. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-stable Sat Sep 27 10:03:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA02182 for stable-outgoing; Sat, 27 Sep 1997 10:03:07 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA02173 for ; Sat, 27 Sep 1997 10:03:01 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.71 #1) id 0xF0Fp-0004IR-00; Sat, 27 Sep 1997 10:02:05 -0700 Date: Sat, 27 Sep 1997 10:02:04 -0700 (PDT) From: Tom To: "David E. Cross" cc: sthaug@nethelp.no, tlambert@primenet.com, stable@freebsd.org Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 27 Sep 1997, David E. Cross wrote: > Technically this is not even a colission situation. Many new NICs and > Hubs (both must support it to work) support full-duplex 10BaseT, allowing > 20MBits/sec. I am not sure what happens when it gets into the hub and > needs to be propogated to other ports though *shrug*. That is an etherswitch. Etherswitches learn which ports are using what MAC addresses, and only direct traffic to the right ports. Etherswitches are basically bridges with lots of ports. They even support bridging protocols like 802.1d to support networks with lots of interconnected switches. A hub is just a repeater. It may detect some kinds of errrors, but probably just jabber errors. Tom From owner-freebsd-stable Sat Sep 27 10:05:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA02422 for stable-outgoing; Sat, 27 Sep 1997 10:05:51 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA02412 for ; Sat, 27 Sep 1997 10:05:39 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 18014 invoked by uid 1001); 27 Sep 1997 17:05:01 +0000 (GMT) To: rgrimes@GndRsh.aac.dev.com Cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-Reply-To: Your message of "Sat, 27 Sep 1997 09:47:15 -0700 (PDT)" References: <199709271647.JAA20293@GndRsh.aac.dev.com> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 27 Sep 1997 19:05:01 +0200 Message-ID: <18012.875379901@verdi.nethelp.no> Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Nope. A hub doesn't do anything with collisions - it just propagates > > them bit by bit. The NICs sense the collision. > > Better go think so more about that... it depends on the hub! Some hubs > that have partitioning ability will automagically partition out someone > who starts to transmit if the hub is sending data out that port, this > is called autopartitioning and is used to stop baligerant (sp) mau's > or Jabberers(sp). Sure - I agree it depends on the hub. But the basic task of the hub is to propagate everything bit by bit - including collisions. And if you buy a noname cheapie hub, it won't do much more than that. > If you want something that really tries to ``prevent'' this you want > a switch and not a hub, and you want full-duplex non-simplex NIC cards > in every box connected to that switch, and no I'm not just talking > about 100Base stuff here, it applies to both 10 and 100Base ethernet > over TP. Yup. But for normal, half-duplex Ethernet you *don't* want to prevent collisions :-) Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-stable Sat Sep 27 10:06:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA02506 for stable-outgoing; Sat, 27 Sep 1997 10:06:43 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA02484 for ; Sat, 27 Sep 1997 10:06:37 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 18026 invoked by uid 1001); 27 Sep 1997 17:06:31 +0000 (GMT) To: dec@phoenix.its.rpi.edu Cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-Reply-To: Your message of "Sat, 27 Sep 1997 09:16:17 -0400 (EDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 27 Sep 1997 19:06:31 +0200 Message-ID: <18024.875379991@verdi.nethelp.no> Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Nope. A hub doesn't do anything with collisions - it just propagates > > them bit by bit. The NICs sense the collision. > > Technically this is not even a colission situation. Many new NICs and > Hubs (both must support it to work) support full-duplex 10BaseT, allowing > 20MBits/sec. I am not sure what happens when it gets into the hub and > needs to be propogated to other ports though *shrug*. If a "hub" supports full duplex then it is by definition a switch - at least in my language. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-stable Sat Sep 27 13:12:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA10918 for stable-outgoing; Sat, 27 Sep 1997 13:12:39 -0700 (PDT) Received: from baklava.alt.net (root@baklava.alt.net [207.14.113.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA10911 for ; Sat, 27 Sep 1997 13:12:36 -0700 (PDT) Received: from baklava.alt.net (ccaputo@baklava.alt.net [207.14.113.9]) by baklava.alt.net (8.8.5/8.7.3) with SMTP id NAA29367; Sat, 27 Sep 1997 13:12:28 -0700 (PDT) Date: Sat, 27 Sep 1997 13:12:28 -0700 (PDT) From: Chris Caputo To: spork cc: Joerg Wunsch , stable@FreeBSD.ORG Subject: Re: Another NFS bogon in 2.2-stable? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk We reverted back to 2.1-STABLE and this bug is not present. Chris On Tue, 23 Sep 1997, Chris Caputo wrote: > We are definitely seeing problems with nfsv2 and either tcp or udp > connections. We have tried the -r=1024 fix for udp and that didn't help. > > We use the 2.2-stable box as an NFS client to a NetApp NFS server. After > a little while, the FreeBSD box gets into a state where any command that > causes NFS activity hangs, including a simple "df". Once in this state, > the command can not be killed, even with "kill -9" from root. > > I am gonna start comparing the 2.2-stable sources with 3.0-current sources > to see if there are any obvious fixes. If anyone has any other ideas, > please let me know. We have an immediate desire to get beyond this. ;-) > > Chris > > On Mon, 22 Sep 1997, spork wrote: > > Is it just me or is there another bug involving 2 FBSD machines running > > -stable and nfsv2 or v3? > > > > In the above situation, if machine A is exporting a directory to machine B > > and machine A dies unexpectedly, you cannot umount the nfs-mounted > > directory; the command just hangs forever. "mount" will hang forever as > > well. Killing off any nfs processes will not help (brutal I thought, but > > worth a try). Remounting can be difficult, and sometimes a reboot is > > required. > > > > Am I doing something terribly wrong? I'm not doing anything out of the > > ordinary, I let the startup script do everything, and I'm only exporting > > one directory. > > > > Charles > > > > On Sun, 21 Sep 1997, J Wunsch wrote: > > > > > (Please drop me a Cc of this conversation, i'm not subscribed to this > > > list.) > > > > > > Did anybody else notice that shutting down a 2.2-stable machine that > > > has NFS file systems mounted never yields a clean shutdown? My 2.2 > > > scratchbox always jams with a `2 2 2 2 2 giving up' display, and comes > > > up again with the clean flag not set in the UFS filesystems. > > > > > > If i shutdown to single-user, manually umount the NFS filesystems, and > > > then type `halt', all works as expected. > > > > > > The machine is not the fastest on earth (386/40), maybe this is what > > > uncovers this problem? > > > > > > -- > > > cheers, J"org > > > > > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > > > Never trust an operating system you don't have sources for. ;-) > > > > > > From owner-freebsd-stable Sat Sep 27 14:53:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA14839 for stable-outgoing; Sat, 27 Sep 1997 14:53:51 -0700 (PDT) Received: from xmission.xmission.com (softweyr@xmission.xmission.com [198.60.22.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA14834 for ; Sat, 27 Sep 1997 14:53:46 -0700 (PDT) Received: (from softweyr@localhost) by xmission.xmission.com (8.8.5/8.7.5) id PAA20526; Sat, 27 Sep 1997 15:53:30 -0600 (MDT) From: Wes Peters - Softweyr LLC Message-Id: <199709272153.PAA20526@xmission.xmission.com> Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) To: tom@sdf.com (Tom) Date: Sat, 27 Sep 1997 15:53:29 -0600 (MDT) Cc: stable@freebsd.org In-Reply-To: from "Tom" at Sep 27, 97 10:02:04 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David E. Cross informed us: % Technically this is not even a colission situation. Many new NICs and % Hubs (both must support it to work) support full-duplex 10BaseT, allowing % 20MBits/sec. I am not sure what happens when it gets into the hub and % needs to be propogated to other ports though *shrug*. Tom replied: > That is an etherswitch. Etherswitches learn which ports are using what > MAC addresses, and only direct traffic to the right ports. Etherswitches > are basically bridges with lots of ports. They even support bridging > protocols like 802.1d to support networks with lots of interconnected > switches. > > A hub is just a repeater. It may detect some kinds of errrors, but > probably just jabber errors. Apparently, Tom, you've never heard of a "smart hub." There are 10-Base hubs will will "autopartition" and lock out a port *before* it can generate a collision. Yes, there really is a difference between $80 hubs and $200 hubs! -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.xmission.com/~softweyr softweyr@xmission.com From owner-freebsd-stable Sat Sep 27 15:28:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA16278 for stable-outgoing; Sat, 27 Sep 1997 15:28:40 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA16272; Sat, 27 Sep 1997 15:28:36 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id PAA14163; Sat, 27 Sep 1997 15:28:24 -0700 (MST) From: Terry Lambert Message-Id: <199709272228.PAA14163@usr08.primenet.com> Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes) Date: Sat, 27 Sep 1997 22:28:24 +0000 (GMT) Cc: sthaug@nethelp.no, tlambert@primenet.com, hackers@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: <199709271647.JAA20293@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Sep 27, 97 09:47:15 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > If you want something that really tries to ``prevent'' this you want > a switch and not a hub, and you want full-duplex non-simplex NIC cards > in every box connected to that switch, and no I'm not just talking > about 100Base stuff here, it applies to both 10 and 100Base ethernet > over TP. While you are in the process emptying your wallet into a fire, you may want to consider buying good cards instead, and avoiding the problem altogether... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-stable Sat Sep 27 17:43:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA23571 for stable-outgoing; Sat, 27 Sep 1997 17:43:22 -0700 (PDT) Received: from proxy3.ba.best.com (root@proxy3.ba.best.com [206.184.139.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA23566 for ; Sat, 27 Sep 1997 17:43:16 -0700 (PDT) Received: from shellx.best.com (shellx.best.com [206.86.0.11]) by proxy3.ba.best.com (8.8.7/8.8.BEST) with ESMTP id RAA29206 for ; Sat, 27 Sep 1997 17:42:43 -0700 (PDT) Received: from localhost (mdean@localhost) by shellx.best.com (8.8.6/8.8.3) with SMTP id RAA29551 for ; Sat, 27 Sep 1997 17:42:41 -0700 (PDT) Date: Sat, 27 Sep 1997 17:42:40 -0700 (PDT) From: mdean To: freebsd-stable@freebsd.org Subject: bad144 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've looked through the freebsd mail archive about this but can't find any reported bugs. Should bad144 fail on 4.0 gig ide drives or what? It is failing about at the middle of mine but the drive is detected fine on startup and I ran a test with the utilities that came with it (western digital) and it can't find any bad sectors---- should I ignore bad144 or is this a sign that it may be broken once I install --- my bios fully supports drives of this size (it is a fairly new ppro) From owner-freebsd-stable Sat Sep 27 18:50:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA26468 for stable-outgoing; Sat, 27 Sep 1997 18:50:48 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA26460 for ; Sat, 27 Sep 1997 18:50:41 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id LAA03271; Sun, 28 Sep 1997 11:18:12 +0930 (CST) Message-Id: <199709280148.LAA03271@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: mdean cc: freebsd-stable@freebsd.org Subject: Re: bad144 In-reply-to: Your message of "Sat, 27 Sep 1997 17:42:40 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Sep 1997 11:18:11 +0930 From: Mike Smith Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I've looked through the freebsd mail archive about this but can't find any > reported bugs. Should bad144 fail on 4.0 gig ide drives or what? It is I'm fairly sure that bad144 suffers on extents larger than 2GB, although I haven't actually tried it to see. > digital) and it can't find any bad sectors---- should I ignore bad144 or is > this a sign that it may be broken once I install --- my bios fully supports > drives of this size (it is a fairly new ppro) There's little point in using it unless you're sure your disk doesn't do bad sector forwarding. mike From owner-freebsd-stable Sat Sep 27 20:57:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA04176 for stable-outgoing; Sat, 27 Sep 1997 20:57:28 -0700 (PDT) Received: from proxy3.ba.best.com (root@proxy3.ba.best.com [206.184.139.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA04171 for ; Sat, 27 Sep 1997 20:57:25 -0700 (PDT) Received: from shellx.best.com (shellx.best.com [206.86.0.11]) by proxy3.ba.best.com (8.8.7/8.8.BEST) with ESMTP id UAA00180; Sat, 27 Sep 1997 20:56:26 -0700 (PDT) Received: from localhost (mdean@localhost) by shellx.best.com (8.8.6/8.8.3) with SMTP id UAA10357; Sat, 27 Sep 1997 20:56:25 -0700 (PDT) Date: Sat, 27 Sep 1997 20:56:25 -0700 (PDT) From: mdean To: "John T. Farmer" cc: freebsd-stable@FreeBSD.ORG, jfarmer@goldsword.com Subject: Re: bad144 In-Reply-To: <199709280337.XAA18951@sabre.goldsword.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I am not really worried what bad144 thinks, I worried that if it returns errors so will freebsd in general since it does run under freebsd and uses freebsd system calls I assume. On Sat, 27 Sep 1997, John T. Farmer wrote: > > On Sat, 27 Sep 1997 17:42:40 -0700 (PDT) mdean said: > >I've looked through the freebsd mail archive about this but can't find any > >reported bugs. Should bad144 fail on 4.0 gig ide drives or what? It is > >failing about at the middle of mine but the drive is detected fine on > >startup and I ran a test with the utilities that came with it (western > >digital) and it can't find any bad sectors---- should I ignore bad144 or is > >this a sign that it may be broken once I install --- my bios fully supports > >drives of this size (it is a fairly new ppro) > > > > Why use bad144 at all? It's a relic left over from the VAX/PDP-11 days... > Search the archives, this has come up several times. It the drive checks > good with the vendors utilities (for IDE and SCSI) then it's good. > > bad144 had it's day when drives _didn't_ do automatic bad block > replacement. > > John (Yes, I'm old enought to have had to deal with such beasts. > My first Unix box was a PDP-11/34 with Version 6.... And > _big_ RK-05 drives, all of 2.5mb each...) > > ------------------------------------------------------------------------- > John T. Farmer Proprietor, GoldSword Systems > jfarmer@goldsword.com Public Internet Access in East Tennessee > dial-in (423)470-9953 for info, e-mail to info@goldsword.com > Network Design, Internet Services & Servers, Consulting > From owner-freebsd-stable Sat Sep 27 21:14:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA05071 for stable-outgoing; Sat, 27 Sep 1997 21:14:17 -0700 (PDT) Received: from obie.softweyr.ml.org ([199.104.124.49]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA05066 for ; Sat, 27 Sep 1997 21:14:12 -0700 (PDT) Received: (from wes@localhost) by obie.softweyr.ml.org (8.7.5/8.6.12) id WAA21096; Sat, 27 Sep 1997 22:23:18 -0600 (MDT) Date: Sat, 27 Sep 1997 22:23:18 -0600 (MDT) Message-Id: <199709280423.WAA21096@obie.softweyr.ml.org> From: Wes Peters To: stable@freebsd.org Subject: Re: K6 Update & AMD Statement In-Reply-To: <5817.875376293@critter.freebsd.dk> from "Poul-Henning Kamp" at Sep 27, 97 06:04:53 pm Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp reported: > I have a K6/233 here which has by now completed 50 or more make worlds, > no complaints. > > It is marked: > AMD-K6-233ANR > 3.2V CORE / 3.3V I/O > B 9731EJBW Ah, yes, 9731, a fine vintage. ;^) The latest I heard was all steppings after 9729 should work fine. BTW, for anyone else who wishes to test this, remember the bug only occurs with more than 32M physical RAM in the system. Please include your RAM configuration in your report. (Still K6-less, but now only for another month or so. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.xmission.com/~softweyr softweyr@xmission.com From owner-freebsd-stable Sat Sep 27 21:31:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA05602 for stable-outgoing; Sat, 27 Sep 1997 21:31:03 -0700 (PDT) Received: from sabre.goldsword.com (sabre.goldsword.com [199.170.202.32]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA05595 for ; Sat, 27 Sep 1997 21:30:52 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.8.7/8.7.3) id XAA18951; Sat, 27 Sep 1997 23:37:08 -0400 (EDT) Date: Sat, 27 Sep 1997 23:37:08 -0400 (EDT) From: "John T. Farmer" Message-Id: <199709280337.XAA18951@sabre.goldsword.com> To: freebsd-stable@FreeBSD.ORG, mdean@best.com Subject: Re: bad144 Cc: jfarmer@goldsword.com Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 27 Sep 1997 17:42:40 -0700 (PDT) mdean said: >I've looked through the freebsd mail archive about this but can't find any >reported bugs. Should bad144 fail on 4.0 gig ide drives or what? It is >failing about at the middle of mine but the drive is detected fine on >startup and I ran a test with the utilities that came with it (western >digital) and it can't find any bad sectors---- should I ignore bad144 or is >this a sign that it may be broken once I install --- my bios fully supports >drives of this size (it is a fairly new ppro) > Why use bad144 at all? It's a relic left over from the VAX/PDP-11 days... Search the archives, this has come up several times. It the drive checks good with the vendors utilities (for IDE and SCSI) then it's good. bad144 had it's day when drives _didn't_ do automatic bad block replacement. John (Yes, I'm old enought to have had to deal with such beasts. My first Unix box was a PDP-11/34 with Version 6.... And _big_ RK-05 drives, all of 2.5mb each...) ------------------------------------------------------------------------- John T. Farmer Proprietor, GoldSword Systems jfarmer@goldsword.com Public Internet Access in East Tennessee dial-in (423)470-9953 for info, e-mail to info@goldsword.com Network Design, Internet Services & Servers, Consulting From owner-freebsd-stable Sat Sep 27 23:21:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA10469 for stable-outgoing; Sat, 27 Sep 1997 23:21:13 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA10464 for ; Sat, 27 Sep 1997 23:21:10 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id XAA01604; Sat, 27 Sep 1997 23:21:00 -0700 (PDT) Date: Sat, 27 Sep 1997 23:21:00 -0700 (PDT) From: "Jamil J. Weatherbee" To: "Jordan K. Hubbard" cc: stable@FreeBSD.ORG Subject: Re: 2nd Notice: 4 days to code freeze in RELENG_2_2 branch. In-Reply-To: <8488.875262955@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Have the floppy driver problems been repaired?? From owner-freebsd-stable Sat Sep 27 23:25:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA10681 for stable-outgoing; Sat, 27 Sep 1997 23:25:24 -0700 (PDT) Received: from aurora.rose-hulman.edu (SYSTEM@aurora.rose-hulman.edu [137.112.8.16]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA10657; Sat, 27 Sep 1997 23:25:17 -0700 (PDT) Received: from richmojm.laptop.rose-hulman.edu ("port 1163"@richmojm.laptop.rose-hulman.edu) by RoseVC.Rose-Hulman.Edu (PMDF V5.1-10 #17642) with SMTP id <01IO5PIHMGR08X1ORL@RoseVC.Rose-Hulman.Edu>; Sun, 28 Sep 1997 01:27:24 EST Date: Sun, 28 Sep 1997 01:28:35 -0500 From: Jay Richmond Subject: booting new kernel... problems To: freebsd-questions@freebsd.org Cc: freebsd-stable@freebsd.org Message-id: <01IO5PIHPMPQ8X1ORL@RoseVC.Rose-Hulman.Edu> MIME-version: 1.0 X-Mailer: Microsoft Outlook Express 4.71.1008.3 Content-type: multipart/alternative; boundary="----=_NextPart_000_0000_01BCCBAD.D6ED7C00" X-MSMail-Priority: Normal X-MimeOle: Produced By Microsoft MimeOLE Engine V4.71.1008.3 X-Priority: 3 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0000_01BCCBAD.D6ED7C00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello-- I built a new 2.2-stable kernel as of today and everything compiled = fine... Then when I tried to reboot, I got the following messages: Boot: dosdev=3D 80, biosdrive =3D 0, unit =3D 0, maj =3D 4 Invalid format! after that it goes in a countinuous loop... have I done something wrong = here? or is there something I should be doing? i can boot the old = kernel just fine by using /kernel.old iused the same config file that i = used for the old kernel (which was also a recent 2.2-stable kernel). any help would be appreciated... thanks for your time, jay ------=_NextPart_000_0000_01BCCBAD.D6ED7C00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

 Hello--

I built a new = 2.2-stable kernel=20 as of today and everything compiled fine... Then when I tried to reboot, = I got=20 the following messages:

Boot:

dosdev=3D 80, biosdrive =3D 0, unit =3D = 0, maj =3D 4

Invalid format!

after that it goes in a countinuous = loop... have I=20 done something wrong here? or is there something I should be = doing?  i can=20 boot the old kernel just fine by using /kernel.old  iused the same = config=20 file that i used for the old kernel (which was also a recent 2.2-stable=20 kernel).

any help would be appreciated...

thanks for your time,

jay

  ------=_NextPart_000_0000_01BCCBAD.D6ED7C00-- From owner-freebsd-stable Sat Sep 27 23:58:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA12494 for stable-outgoing; Sat, 27 Sep 1997 23:58:12 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA12489; Sat, 27 Sep 1997 23:58:08 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id XAA20941; Sat, 27 Sep 1997 23:56:53 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199709280656.XAA20941@GndRsh.aac.dev.com> Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-Reply-To: <199709272228.PAA14163@usr08.primenet.com> from Terry Lambert at "Sep 27, 97 10:28:24 pm" To: tlambert@primenet.com (Terry Lambert) Date: Sat, 27 Sep 1997 23:56:53 -0700 (PDT) Cc: sthaug@nethelp.no, tlambert@primenet.com, hackers@FreeBSD.ORG, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > If you want something that really tries to ``prevent'' this you want > > a switch and not a hub, and you want full-duplex non-simplex NIC cards > > in every box connected to that switch, and no I'm not just talking > > about 100Base stuff here, it applies to both 10 and 100Base ethernet > > over TP. > > While you are in the process emptying your wallet into a fire, you > may want to consider buying good cards instead, and avoiding the > problem altogether... Ah, Terry, do you realize who you quoted above? Please reread what I wrote, I don't think you can find a NIC that meets my spec without getting a ``good one''. I was also ``preventing'' the collisions, something some major corps have paid me good money to go in and do. How about a 50 node HP7000/J200 cluster using Catalyst 5000 switches. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD