From owner-freebsd-current Sun Jan 31 01:46:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA04801 for freebsd-current-outgoing; Sun, 31 Jan 1999 01:46:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [209.244.238.132] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA04794 for ; Sun, 31 Jan 1999 01:46:53 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id EAA21245; Sun, 31 Jan 1999 04:40:59 -0500 (EST) From: Peter Dufault Message-Id: <199901310940.EAA21245@hda.hda.com> Subject: Re: LINUX clone? sched_yield? In-Reply-To: <199901310414.PAA15601@godzilla.zeta.org.au> from Bruce Evans at "Jan 31, 99 03:14:18 pm" To: bde@zeta.org.au (Bruce Evans) Date: Sun, 31 Jan 1999 04:40:58 -0500 (EST) Cc: dufault@hda.com, wollman@khavrinen.lcs.mit.edu, freebsd-current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There's a yield() syscall that is enabled permanently. Is there any > harm in untangling it from the POSIX sched_yield()? :-) I've got a synch_yield() in kern_synch and a call into it from yield() in kern_thread that duplicates the yield() behavior for the non-RTPRIO, non-sched_yield() condition. synch_yield() also KASSERTS that p == curproc since nothing else makes sense. However, I've woken up to a gcc SIG 11 during my world build. This is from yesterday AM sources and is the first crash for my crash box. Though I doubt it is my patches I'll look a bit to convince myself. Prior to this that system has been running a week with a patched world. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 01:47:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA04826 for freebsd-current-outgoing; Sun, 31 Jan 1999 01:47:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.use-net.co.jp (gw-ns.use-net.co.jp [203.141.207.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA04818 for ; Sun, 31 Jan 1999 01:47:12 -0800 (PST) (envelope-from asa@use-net.co.jp) Received: from beta (use177.use-net.co.jp [203.141.207.177]) by ns.use-net.co.jp (8.9.1/3.7W) with SMTP id SAA36687 for ; Sun, 31 Jan 1999 18:46:24 +0900 (JST) Date: Sun, 31 Jan 1999 18:46:30 +0900 From: Tomoyoshi ASANO To: freebsd-current@FreeBSD.ORG Subject: About /usr/mdec/cdboot Message-Id: <36B42676158.488EASA@mail.use-net.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver 1.24.13 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm using DELL's OptiPlex Gn+. This machine is supported CD-ROM Booting from ATAPI CD-ROM. In 3.0-stable and -cureent, I created CD-R disc with /usr/mdec/cdboot using mkisofs and cdrecord. When CD booting, some error messages is displayed. And I tested other machines supported atapi-cdrom booting. > (In /usr/sys/i386/boot/cdboot/boot.c) > Your BIOS int 0x13 extensions seem to be disabled. > It's impossible to boot a CD-ROM without them. > (BIOS int 0x13 fn 0x4b01 yielded error ?) I'm sorry I don't know 0x13 extensions. Is /usr/mdec/cdrom supported atapi-cdrom booting ? -- Tomoyoshi ASANO To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 02:21:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA06857 for freebsd-current-outgoing; Sun, 31 Jan 1999 02:21:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA06840; Sun, 31 Jan 1999 02:21:43 -0800 (PST) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Sisyphos.MI.Uni-Koeln.DE (8.8.7/8.8.7) with ESMTP id LAA20746; Sun, 31 Jan 1999 11:21:39 +0100 (MET) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.9.2/8.6.9) id KAA00926; Sat, 30 Jan 1999 10:49:58 +0100 (CET) Date: Sat, 30 Jan 1999 10:49:57 +0100 From: Stefan Esser To: Christopher Masto Cc: hardware@FreeBSD.ORG, current@FreeBSD.ORG, Stefan Esser Subject: Re: Network/ARP problem? Maybe pn driver? Message-ID: <19990130104957.B660@dialup124.mi.uni-koeln.de> Reply-To: se@FreeBSD.ORG Mail-Followup-To: Christopher Masto , hardware@FreeBSD.ORG, current@FreeBSD.ORG References: <19990129173922.A29551@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19990129173922.A29551@netmonger.net>; from Christopher Masto on Fri, Jan 29, 1999 at 05:39:22PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yust a wild guess: You could have blocked reception of ARP requests / ARP replies in your IPFW rules on one of the systems involved. Just try again with a completely open configuration (a pass all as rule 1 should work). That would explain that other systems can learn the ARP address as soon as they have received IP packets, but they can't get at the ARP address by querying for it ... Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 02:27:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA07335 for freebsd-current-outgoing; Sun, 31 Jan 1999 02:27:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [209.244.238.132] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA07330 for ; Sun, 31 Jan 1999 02:27:46 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id FAA21322; Sun, 31 Jan 1999 05:22:03 -0500 (EST) From: Peter Dufault Message-Id: <199901311022.FAA21322@hda.hda.com> Subject: more about yield() versus sched_yield() To: current@FreeBSD.ORG Date: Sun, 31 Jan 1999 05:22:03 -0500 (EST) Cc: bde@zeta.org.au 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've got a synch_yield() in kern_synch and a call into it from yield() > in kern_thread that duplicates the yield() behavior for the non-RTPRIO, > non-sched_yield() condition. synch_yield() also KASSERTS > that p == curproc since nothing else makes sense. While we're discussing yield here's a question. The difference between yield() and sched_yield() is that yield unconditionally yields while sched_yield() won't if you are the highest priority process and the only process in your run queue. Does anyone know the reuirements on yield() and would it continue to function for us if it worked the same as sched_yield()? Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 02:33:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA08172 for freebsd-current-outgoing; Sun, 31 Jan 1999 02:33:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA08159 for ; Sun, 31 Jan 1999 02:33:49 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id VAA01602; Sun, 31 Jan 1999 21:34:47 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199901311034.VAA01602@cimlogic.com.au> Subject: Re: more about yield() versus sched_yield() In-Reply-To: <199901311022.FAA21322@hda.hda.com> from Peter Dufault at "Jan 31, 1999 5:22: 3 am" To: dufault@hda.com (Peter Dufault) Date: Sun, 31 Jan 1999 21:34:45 +1100 (EST) Cc: current@FreeBSD.ORG, bde@zeta.org.au X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Dufault wrote: > > I've got a synch_yield() in kern_synch and a call into it from yield() > > in kern_thread that duplicates the yield() behavior for the non-RTPRIO, > > non-sched_yield() condition. synch_yield() also KASSERTS > > that p == curproc since nothing else makes sense. > > While we're discussing yield here's a question. > > The difference between yield() and sched_yield() is that yield unconditionally > yields while sched_yield() won't if you are the highest priority process > and the only process in your run queue. Does anyone know the > reuirements on yield() and would it continue to function for us if > it worked the same as sched_yield()? FWIW, the yield syscall is _not_ built into libc, so I doubt there will be anything that actually uses it. I think you should just keep sched_yield(). -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 02:49:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA09027 for freebsd-current-outgoing; Sun, 31 Jan 1999 02:49:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA09019 for ; Sun, 31 Jan 1999 02:49:16 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id CAA72454; Sun, 31 Jan 1999 02:49:14 -0800 (PST) (envelope-from obrien) Date: Sun, 31 Jan 1999 02:49:14 -0800 From: "David O'Brien" To: "Jordan K. Hubbard" Cc: obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: Even more interesting NFS problems.. Message-ID: <19990131024914.C67786@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19990130200958.B66257@relay.nuxi.com> <10965.917762686@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <10965.917762686@zippy.cdrom.com>; from Jordan K. Hubbard on Sat, Jan 30, 1999 at 10:04:46PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Yes, to be consistent with the state of world WRT NFS. Or at least with > > the leader -- Solaris. This has been the default in 3.0-C since the > > am-utils import. > > Yeah, well, amd is a whole other ball of wax. That's clearly broken > in both 3.0-stable and 4.0-current Why is it clearly broken? proto=tcp,vers=3 is what is in 3.0-RELEASE, Amd in 3.0 works for many. I won't defend that the new Amd works the best with us, but then neither did the old Amd. > and we're going to have to revert the last set of changes fairly soon, > it's on my TODO list of things to deal with. I think we need to do more testing in the environments Amd currently gives trouble to determine if the problem is with using TCP or version 3 of NFS. I still question if there still are problems in our NFS (even with hard mounts) implementation. Also, is the problem FreeBSD between two FreeBSD boxes, or a FreeBSD and say Solaris box. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 02:57:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA09943 for freebsd-current-outgoing; Sun, 31 Jan 1999 02:57:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA09930 for ; Sun, 31 Jan 1999 02:57:09 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA08719; Sun, 31 Jan 1999 21:57:07 +1100 Date: Sun, 31 Jan 1999 21:57:07 +1100 From: Bruce Evans Message-Id: <199901311057.VAA08719@godzilla.zeta.org.au> To: current@FreeBSD.ORG, dufault@hda.com Subject: Re: more about yield() versus sched_yield() Cc: bde@zeta.org.au Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >While we're discussing yield here's a question. > >The difference between yield() and sched_yield() is that yield unconditionally >yields while sched_yield() won't if you are the highest priority process >and the only process in your run queue. Does anyone know the >reuirements on yield() and would it continue to function for us if >it worked the same as sched_yield()? AFAIK (not far), yield() is not used, so there are no requirements on it. It is certainly missing from libc (except as sycall(321)) and undocumented in FreeBSD. Another difference is that it correctly counts context switches as voluntary. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 03:13:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA12888 for freebsd-current-outgoing; Sun, 31 Jan 1999 03:13:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA12837 for ; Sun, 31 Jan 1999 03:13:40 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id MAA07128 for freebsd-current@FreeBSD.ORG; Sun, 31 Jan 1999 12:13:38 +0100 (CET) (envelope-from olli) Date: Sun, 31 Jan 1999 12:13:38 +0100 (CET) From: Oliver Fromme Message-Id: <199901311113.MAA07128@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: 3.0-STABLE and 4.0-CURRENT snapshots Newsgroups: list.freebsd-current Organization: Administration Heim 3 Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Roman V. Palaginwrote in list.freebsd-current: > Where I can find snapshot for -stable & -current? I've tried > current.freebsd.org, but 'cd /pub/FreeBSD' says 'Permission denied'. > And there is nothing at > ftp://ftp.freebsd.org/pub/FreeBSD/release/snapshots/i386 You might give ftp7.de.freebsd.org a try... Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 03:27:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA13792 for freebsd-current-outgoing; Sun, 31 Jan 1999 03:27:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nagual.pp.ru (nagual.pp.ru [193.125.27.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA13783 for ; Sun, 31 Jan 1999 03:27:20 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.2/8.9.2) id OAA21688 for current@freebsd.org; Sun, 31 Jan 1999 14:27:18 +0300 (MSK) (envelope-from ache) Date: Sun, 31 Jan 1999 14:27:17 +0300 From: "Andrey A. Chernov" To: current@FreeBSD.ORG Subject: Latest VM changes cause panic: page fault Message-ID: <19990131142716.A21218@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It happens with plain UFS, I have no NFS. Pre-new-VM kernel not cause page fault -- Andrey A. Chernov ache@null.net MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 03:34:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA15522 for freebsd-current-outgoing; Sun, 31 Jan 1999 03:34:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nagual.pp.ru (nagual.pp.ru [193.125.27.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA15516 for ; Sun, 31 Jan 1999 03:34:44 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.2/8.9.2) id OAA23326; Sun, 31 Jan 1999 14:34:42 +0300 (MSK) (envelope-from ache) Date: Sun, 31 Jan 1999 14:34:41 +0300 From: "Andrey A. Chernov" To: current@FreeBSD.ORG Cc: fenner@parc.xerox.com Subject: New socket code hits again! (was: Latest VM changes cause panic: page fault) Message-ID: <19990131143441.A22367@nagual.pp.ru> References: <19990131142716.A21218@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990131142716.A21218@nagual.pp.ru>; from ache@nagual.pp.ru on Sun, Jan 31, 1999 at 02:27:17PM +0300 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 31, 1999 at 02:27:17PM +0300, Andrey A. Chernov wrote: > Pre-new-VM kernel not cause page fault Sorry for false alarm - it seems that new socket code hits again and not new VM: #4 0xf019cc3e in trap () #5 0xf013aa20 in soclose () #6 0xf01314e2 in soo_close () #7 0xf011c456 in closef () #8 0xf011ba8f in close () #9 0xf019d4fc in syscall () #10 0xf019456c in Xint0x80_syscall () -- Andrey A. Chernov ache@null.net MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 03:35:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA15578 for freebsd-current-outgoing; Sun, 31 Jan 1999 03:35:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA15551 for ; Sun, 31 Jan 1999 03:35:01 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id UAA05029; Sun, 31 Jan 1999 20:34:57 +0900 (JST) Message-ID: <36B43FC5.7348076F@newsguy.com> Date: Sun, 31 Jan 1999 20:34:29 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Medium priority tasks... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey, are you REALLY sure this is a medium priority task? From the handbook: 3.Full LKM based driver support/Configuration Manager. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com Would you mind not shooting at the thermonuclear weapons? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 03:38:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA15954 for freebsd-current-outgoing; Sun, 31 Jan 1999 03:38:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA15947; Sun, 31 Jan 1999 03:38:34 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id WAA28140; Sat, 30 Jan 1999 22:17:29 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.2/8.9.2) with ESMTP id WAA57236; Sat, 30 Jan 1999 22:13:08 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199901302213.WAA57236@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: Warner Losh , Matthew Dillon , Bruce Evans , current@FreeBSD.ORG, nate@FreeBSD.ORG, julian@FreeBSD.ORG Subject: Re: c_caddr_t (etc) In-reply-to: Your message of "Fri, 29 Jan 1999 20:27:04 PST." <86830.917670424@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 30 Jan 1999 22:13:08 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > To put it in a somewhat larger context, none of the things which have > seen people blow up recently have been all that important, and to get > people freaking out in my mailbox over the -Wall changes or a change > to style(9) is pretty damned silly. This is one aspect to John > Birrell's accusation that our heads have gotten firmly stuck up a > certain orifice that I have to agree with. We should certainly > continue to be conservative when it comes to making major > architectural changes, but this constant griping over cosmetic stuff > isn't serving anyone's purposes at all. The general impression I get out of what's been happening lately is that (overall) people are trying to shout ``don't jump in with both feet if you're likely to either stomp all over someone elses stuff or to do something that the project as a whole doesn't necessarily agree with''. The pre-4.0 clobbering got everyone on edge. Matts -Wall changes are ultimately good, but should probably have been mentioned/discussed first. This is probably a bit ``cheeky'' for a relatively new committer (despite his established reputation). As soon as he made a mistake, that was kind of an excuse for a slap on the wrist. Julians style(9) suggestion brings up the fact that there are a lot of different coding styles running around. People tend to stay quiet about it as they really don't want to change their existing code. So everyone jumps to agree that something should change (Nate wants to revise the whole thing, but that's probably a bit radical :). Bruce objects (pretty strongly), but there's too much ``wow, something may change'' momentum...... IMHO, this is all mostly the result of having lots of new committers and a very small settling down period. Nobody's got the hang of the status quo and lots of the new committers are pretty strong players from previous lives. >From my point of view, leaving the problem alone is the best approach. When Matt wants to -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes the code, he'll probably mention it on -current/-hackers first (and Nate'll probably make sure it's reviewed and will help etc). When Julian wants braces on a line of their own (only joking) he'll talk to bde first and the end result will be that he's better off making DEVFS the default.... It's probably a good idea to go easy on the new committers for now though. > - Jordan -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 03:39:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16006 for freebsd-current-outgoing; Sun, 31 Jan 1999 03:39:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [209.244.238.132] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA16000 for ; Sun, 31 Jan 1999 03:39:36 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id GAA21441; Sun, 31 Jan 1999 06:33:41 -0500 (EST) From: Peter Dufault Message-Id: <199901311133.GAA21441@hda.hda.com> Subject: Re: more about yield() versus sched_yield() In-Reply-To: <199901311057.VAA08719@godzilla.zeta.org.au> from Bruce Evans at "Jan 31, 99 09:57:07 pm" To: bde@zeta.org.au (Bruce Evans) Date: Sun, 31 Jan 1999 06:33:40 -0500 (EST) Cc: current@FreeBSD.ORG, dufault@hda.com, bde@zeta.org.au 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Another difference is that it correctly counts context switches as voluntary. Good point. The patched version calls maybe_resched(), and I'm adding the line at "<<<". (This also will let people who haven't looked at that code complain about the function interface - it doesn't bother me, macros could come later.) /* * prioritize: Compute a priority based on the type of scheduler. */ static priority_type prioritize(struct proc *p) { priority_type priority; int class = RTP_PRIO_BASE(p->p_rtprio.type); if (class == RTP_PRIO_NORMAL) { priority = (RTP_PRIO_NORMAL << 8) | (p->p_priority / PPQ); } else priority = (class << 8) | p->p_rtprio.prio; return priority; } /* * curpriority_set: Set the current process priority to that of the process * in the call. */ void curpriority_set(struct proc *p) { newcurpriority = prioritize(p); } /* * curpriority_cmp: Compare the priorities. Return: * <0: p < curpriority * 0: p == curpriority * >0: p > curpriority */ static int curpriority_cmp(struct proc *p) { priority_type prio = prioritize(p); return prio - newcurpriority; } /* * maybe_resched: Decide if you need to reschedule or not, * taking the priorities and schedulers into account. * * This function needs to be call AFTER chk->p_priority has * been updated. */ static void maybe_resched(struct proc *chk) { if (curproc == 0) need_resched(); else if (chk == curproc) { /* * If chk is curproc, we may need to preempt if * we're making our priority less favorable. */ if (curpriority_cmp(chk) > 0) { chk->p_stats->p_ru.ru_nvcsw++; /* <<< Adding */ need_resched(); } } /* * If chk is not the curproc, we want to preempt if chk has * a more favorable priority than curproc. * * We shouldn't preempt the current process because of the * priority of a sleeping or stopped process. * */ else if ((chk->p_flag & P_INMEM) && chk->p_stat == SRUN && curpriority_cmp(chk) < 0) { need_resched(); } } -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 03:47:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16390 for freebsd-current-outgoing; Sun, 31 Jan 1999 03:47:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA16371 for ; Sun, 31 Jan 1999 03:47:41 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id UAA06215; Sun, 31 Jan 1999 20:47:38 +0900 (JST) Message-ID: <36B442BD.33F544E@newsguy.com> Date: Sun, 31 Jan 1999 20:47:09 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: More on The Handbook Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The section "24.1. The FreeBSD Booting Process" might be misleading... With our new three stage boot loader, people are bound to hit that link thinking it will explain how does boot[012]/loader works, what's a BTX, etc... :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com Would you mind not shooting at the thermonuclear weapons? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 04:17:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA21925 for freebsd-current-outgoing; Sun, 31 Jan 1999 04:17:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA21920 for ; Sun, 31 Jan 1999 04:17:41 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.2) with ESMTP id EAA01376; Sun, 31 Jan 1999 04:18:25 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: obrien@NUXI.com cc: current@FreeBSD.ORG Subject: Re: Even more interesting NFS problems.. In-reply-to: Your message of "Sun, 31 Jan 1999 02:49:14 PST." <19990131024914.C67786@relay.nuxi.com> Date: Sun, 31 Jan 1999 04:18:25 -0800 Message-ID: <1374.917785105@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why is it clearly broken? proto=tcp,vers=3 is what is in 3.0-RELEASE, > Amd in 3.0 works for many. I won't defend that the new Amd works the > best with us, but then neither did the old Amd. Erm, I haven't tried it between 3.0 and 3.0 boxes because all my test environments currently involve one of each (4.0 and 3.0), but I can certainly say that in none of these test environments does amd work at all. On freefall, for example, it's really simple to demonstrate the error. First, we start amd: # amd -a /net -c 1800 -k i386 -d freebsd.org -l syslog /host /etc/amd.map # ps ax | grep amd 9127 ?? Is 0:00.01 amd -a /net -c 1800 -k i386 -d freebsd.org -l syslog # cat /etc/amd.map /defaults type:=host;fs:=${autodir}/${rhost};rhost:=${key} * opts:=rw,grpid,resvport,vers=2,proto=udp,nosuid,nodev,intr # df .. pid9127@freefall:/host 0 0 0 100% /host # ls /host/hub ls: /host/hub: No such file or directory # ls /host/bento ls: /host/bento: No such file or directory But no workee at all. Any ideas? Using only FreeBSD boxes and udp/ver2 mounts, amd fails to function as far as I can tell. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 04:36:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA24170 for freebsd-current-outgoing; Sun, 31 Jan 1999 04:36:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA24143 for ; Sun, 31 Jan 1999 04:36:01 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id XAA15248; Sun, 31 Jan 1999 23:35:53 +1100 Date: Sun, 31 Jan 1999 23:35:53 +1100 From: Bruce Evans Message-Id: <199901311235.XAA15248@godzilla.zeta.org.au> To: bde@zeta.org.au, dufault@hda.com Subject: Re: more about yield() versus sched_yield() Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Another difference is that it correctly counts context switches as voluntary. > >Good point. The patched version calls maybe_resched(), and I'm >adding the line at "<<<". This counts context switches twice (once as voluntary here, once as involuntary when switch is done on return from the syscall). You could frob the count of involuntary switches here, but the uglyness of that shows that things aren't being done right. A direct switch as in yield() seems best. >(This also will let people who haven't looked at that code >complain about the function interface - it doesn't bother me, >macros could come later.) I might complain about style bugs, and typedefs named priority_type, and magic conversions between priority_type and int. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 04:41:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA24456 for freebsd-current-outgoing; Sun, 31 Jan 1999 04:41:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [209.244.238.132] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA24448 for ; Sun, 31 Jan 1999 04:41:07 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id HAA21617; Sun, 31 Jan 1999 07:35:15 -0500 (EST) From: Peter Dufault Message-Id: <199901311235.HAA21617@hda.hda.com> Subject: Re: more about yield() versus sched_yield() In-Reply-To: <199901311235.XAA15248@godzilla.zeta.org.au> from Bruce Evans at "Jan 31, 99 11:35:53 pm" To: bde@zeta.org.au (Bruce Evans) Date: Sun, 31 Jan 1999 07:35:14 -0500 (EST) Cc: bde@zeta.org.au, dufault@hda.com, current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >(This also will let people who haven't looked at that code > >complain about the function interface - it doesn't bother me, > >macros could come later.) > > I might complain about style bugs, and typedefs named priority_type, > and magic conversions between priority_type and int. Or you might gently suggest improvements. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 05:46:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA29859 for freebsd-current-outgoing; Sun, 31 Jan 1999 05:46:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA29853 for ; Sun, 31 Jan 1999 05:46:01 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id VAA03611; Sun, 31 Jan 1999 21:45:37 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901311345.VAA03611@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: Even more interesting NFS problems.. In-reply-to: Your message of "Sun, 31 Jan 1999 04:18:25 PST." <1374.917785105@zippy.cdrom.com> Date: Sun, 31 Jan 1999 21:45:37 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > Why is it clearly broken? proto=tcp,vers=3 is what is in 3.0-RELEASE, > > Amd in 3.0 works for many. I won't defend that the new Amd works the > > best with us, but then neither did the old Amd. > > Erm, I haven't tried it between 3.0 and 3.0 boxes because all my test > environments currently involve one of each (4.0 and 3.0), but I can > certainly say that in none of these test environments does amd work at > all. On freefall, for example, it's really simple to demonstrate the > error. First, we start amd: > > # amd -a /net -c 1800 -k i386 -d freebsd.org -l syslog /host /etc/amd.map > # ps ax | grep amd > 9127 ?? Is 0:00.01 amd -a /net -c 1800 -k i386 -d freebsd.org -l syslo g > > # cat /etc/amd.map > /defaults type:=host;fs:=${autodir}/${rhost};rhost:=${key} > * opts:=rw,grpid,resvport,vers=2,proto=udp,nosuid,nodev,intr > I added the vers=2 and proto=udp, "just in case", but it wouldn't work either way. At one point there was: fs:=${autodir}/${rhost}/host, but that didn't work either (as /host/hub or /host/hub/host). > # ls /host/bento > ls: /host/bento: No such file or directory > > But no workee at all. Any ideas? Using only FreeBSD boxes and > udp/ver2 mounts, amd fails to function as far as I can tell. It would appear the the NFS interface between the kernel and amd is working otherwise the accesses to /host would hang. But beyond that I don't know. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 07:06:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08267 for freebsd-current-outgoing; Sun, 31 Jan 1999 07:06:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles216.castles.com [208.214.165.216]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08262 for ; Sun, 31 Jan 1999 07:06:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id HAA06566; Sun, 31 Jan 1999 07:02:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901311502.HAA06566@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Patrick Hartling cc: freebsd-current@FreeBSD.ORG Subject: Re: Reading a text file with BTX In-reply-to: Your message of "Thu, 28 Jan 1999 10:10:20 CST." <199901281610.KAA04600@friley-184-92.res.iastate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 31 Jan 1999 07:02:43 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there a way to view the contents of a text file (specifically, > /boot/loader.rc) with BTX? Now that there are all these nifty new modules, > my kernel is a lot smaller and my /boot/loader.rc is a lot longer. The way > I have my /boot/loader.rc setup is such that it unloads everythin > automatically loaded if I drop to the BTX prompt instead of autobooting. > This is fairly convenient except when I want to boot an alternate kernel but > still load all the same modules that I use in my default kernel. If there > isn't such a feature, it would be really nice if there were a 'cat' command > or something along those lines so that I could read the contents of > /boot/loader.rc and get everything properly reloaded by hand. Could it be > added or could I just make my own somehow? Thanks a bunch. Perhaps try something like: @set kernelname=kernel @read -t 5 -p "Enter kernel name [kernel] : " kernelname @load $kernelname @include /boot/modules.default -include /boot/modules.$kernelname @autoboot 5 The 'include' commands make it easier to keep your module sets organised, should you want to do that. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 07:41:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10970 for freebsd-current-outgoing; Sun, 31 Jan 1999 07:41:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10965 for ; Sun, 31 Jan 1999 07:41:01 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.2/8.9.1) id JAA51513; Sun, 31 Jan 1999 09:40:29 -0600 (CST) (envelope-from dick) Date: Sun, 31 Jan 1999 09:40:29 -0600 From: "Richard Seaman, Jr." To: Peter Dufault Cc: John Birrell , current@FreeBSD.ORG, bde@zeta.org.au Subject: Re: more about yield() versus sched_yield() Message-ID: <19990131094029.D29670@tar.com> References: <199901311022.FAA21322@hda.hda.com> <199901311034.VAA01602@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199901311034.VAA01602@cimlogic.com.au>; from John Birrell on Sun, Jan 31, 1999 at 09:34:45PM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 31, 1999 at 09:34:45PM +1100, John Birrell wrote: > Peter Dufault wrote: > > > I've got a synch_yield() in kern_synch and a call into it from yield() > > > in kern_thread that duplicates the yield() behavior for the non-RTPRIO, > > > non-sched_yield() condition. synch_yield() also KASSERTS > > > that p == curproc since nothing else makes sense. > > > > While we're discussing yield here's a question. > > > > The difference between yield() and sched_yield() is that yield unconditionally > > yields while sched_yield() won't if you are the highest priority process > > and the only process in your run queue. Does anyone know the > > reuirements on yield() and would it continue to function for us if > > it worked the same as sched_yield()? > > FWIW, the yield syscall is _not_ built into libc, so I doubt there will > be anything that actually uses it. I think you should just keep > sched_yield(). FWIW, there was sample code posted to -current by John Dyson that used the syscall yield, as well as the undocumented (and absent from libc) syscalls thr_sleep and thr_wakeup. The implication of his comments was that he used the code, or something like it, in some production application. As I indicated to you several weeks ago, I think it is possible to have a priority inversion problem in spinlocks that spin on sched_yield. The yield call, as implemented, partly addresses the issue. However, as you commented to me, it does so poorly. If the consensus is to drop or modify SYS_yield, my vote would be to give consideration to changing the call to more correctly address the priority inversion issue. Possibly a yield (pid_t pid) where the pid passed in is the pid of the thread (process) holding a lock. The system could then check the credentials of the pid to see if there is permission (eg. its a kernel thread of the same process) and if so, raise the priority of pid to that of the calling process for one time slice so pid has a chance to execute and free the lock. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 08:01:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13198 for freebsd-current-outgoing; Sun, 31 Jan 1999 08:01:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13193 for ; Sun, 31 Jan 1999 08:01:28 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id BAA08770; Mon, 1 Feb 1999 01:01:26 +0900 (JST) Message-ID: <36B47C1B.C509042A@newsguy.com> Date: Mon, 01 Feb 1999 00:51:55 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: vn and 4.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is vn safe right now on -current? And does current's msdos fs support fat-32? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com Would you mind not shooting at the thermonuclear weapons? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 08:02:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13335 for freebsd-current-outgoing; Sun, 31 Jan 1999 08:02:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13329 for ; Sun, 31 Jan 1999 08:02:05 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id BAA08762; Mon, 1 Feb 1999 01:01:22 +0900 (JST) Message-ID: <36B47BA6.AA940054@newsguy.com> Date: Mon, 01 Feb 1999 00:49:58 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Mike Smith CC: Patrick Hartling , freebsd-current@FreeBSD.ORG Subject: Re: Reading a text file with BTX References: <199901311502.HAA06566@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd like to suggest that nobody depends on the exact syntax below. Using "@" at the beginning of the lines is EVIL, and has to go away. Well, for *this* purpose, at least. Likewise, - at the beginning of the line is also very evil. Very, very evil. I have now, at last, a fully working version of "include" for forth source code. With that, we are finally able to actually *use* ficl in loader.rc and the likes. The down side, of course, is that we ought to stop treating things included as special cases of "builtin only" with special semantics. We get more power, but a few concessions must be mude. Specifically, "@", "#" and "-". Mike Smith wrote: > > Perhaps try something like: > > @set kernelname=kernel > @read -t 5 -p "Enter kernel name [kernel] : " kernelname > @load $kernelname > @include /boot/modules.default > -include /boot/modules.$kernelname > @autoboot 5 > > The 'include' commands make it easier to keep your module sets > organised, should you want to do that. And include is also recursive. Or, at least, it should be. :-) There is something smelly with the way errors are being treated, though it might not show up in the current version because it's recursive chain doesn't include bf_run(). Anyway, the above could be coded like this in my current version of loader: \ loader.rc \ <-- This is the new character for comments set kernelname=kernel \ Don't echo is now default read -t 5 -p "Enter kernel name [kernel] : " kernelname load ${kernelname} \ I thought {} was required include /boot/modules.default ~ include /boot/modules.$kernelname \ And this is the new way \ of ignoring errors autoboot 5 But the bottom line is that @#- are evil and must go away. :-) I even thought of preemptively removing then from loader.help, so nobody would get used to them... :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com Would you mind not shooting at the thermonuclear weapons? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 09:07:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20820 for freebsd-current-outgoing; Sun, 31 Jan 1999 09:07:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA20810 for ; Sun, 31 Jan 1999 09:07:48 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id MAA01425; Sun, 31 Jan 1999 12:14:33 -0500 From: Bill Paul Message-Id: <199901311714.MAA01425@skynet.ctr.columbia.edu> Subject: Re: Even more interesting NFS problems.. To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Sun, 31 Jan 1999 12:14:32 -0500 (EST) Cc: current@FreeBSD.ORG, obrien@nuxi.com In-Reply-To: <1374.917785105@zippy.cdrom.com> from "Jordan K. Hubbard" at Jan 31, 99 04:18:25 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Jordan K. Hubbard had to walk into mine and say: > > Why is it clearly broken? proto=tcp,vers=3 is what is in 3.0-RELEASE, > > Amd in 3.0 works for many. I won't defend that the new Amd works the > > best with us, but then neither did the old Amd. > > Erm, I haven't tried it between 3.0 and 3.0 boxes because all my test > environments currently involve one of each (4.0 and 3.0), but I can > certainly say that in none of these test environments does amd work at > all. On freefall, for example, it's really simple to demonstrate the > error. First, we start amd: > > # amd -a /net -c 1800 -k i386 -d freebsd.org -l syslog /host /etc/amd.map Err.... On all of the machines where I use amd, I don't use -l syslog. I use -l /tmp/.automsg (or some other filename that lusers aren't likely to trip over). You get _MUCH_ more information this way. I strongly suggest trying this and observing the results when you try to automount something. I've found that am-utils is much more verbose than previous versions of amd so you may not want to leave it that way permanently, but you can't beat it for troubleshooting. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 09:13:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21827 for freebsd-current-outgoing; Sun, 31 Jan 1999 09:13:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley-184-92.res.iastate.edu (friley-184-92.res.iastate.edu [129.186.184.92]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21819 for ; Sun, 31 Jan 1999 09:13:45 -0800 (PST) (envelope-from mystify@friley-184-92.res.iastate.edu) Received: from friley-184-92.res.iastate.edu (localhost.res.iastate.edu [127.0.0.1]) by friley-184-92.res.iastate.edu (8.9.2/8.9.1) with ESMTP id LAA06495; Sun, 31 Jan 1999 11:13:34 -0600 (CST) (envelope-from mystify@friley-184-92.res.iastate.edu) Message-Id: <199901311713.LAA06495@friley-184-92.res.iastate.edu> To: Mike Smith cc: freebsd-current@FreeBSD.ORG Subject: Re: Reading a text file with BTX In-reply-to: Message from Mike Smith of "Sun, 31 Jan 1999 07:02:43 PST." <199901311502.HAA06566@dingo.cdrom.com> Date: Sun, 31 Jan 1999 11:13:34 -0600 From: Patrick Hartling Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: } > Is there a way to view the contents of a text file (specifically, } > /boot/loader.rc) with BTX? Now that there are all these nifty new modules, } > my kernel is a lot smaller and my /boot/loader.rc is a lot longer. The way } > I have my /boot/loader.rc setup is such that it unloads everythin } > automatically loaded if I drop to the BTX prompt instead of autobooting. } > This is fairly convenient except when I want to boot an alternate kernel but } > still load all the same modules that I use in my default kernel. If there } > isn't such a feature, it would be really nice if there were a 'cat' command } > or something along those lines so that I could read the contents of } > /boot/loader.rc and get everything properly reloaded by hand. Could it be } > added or could I just make my own somehow? Thanks a bunch. } } Perhaps try something like: } } @set kernelname=kernel } @read -t 5 -p "Enter kernel name [kernel] : " kernelname } @load $kernelname } @include /boot/modules.default } -include /boot/modules.$kernelname } @autoboot 5 } } The 'include' commands make it easier to keep your module sets } organised, should you want to do that. That looks great to me. I was thinking that something like the above would probably be necessary, but I haven't learned Forth yet. This should be just what I need though. Thanks! -Patrick Patrick L. Hartling | Research Assistant, ICEMT mystify@friley-184-92.res.iastate.edu | Carver Lab - 0095E Black Engineering http://www.public.iastate.edu/~oz/ | http://www.icemt.iastate.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 09:36:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24537 for freebsd-current-outgoing; Sun, 31 Jan 1999 09:36:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24531 for ; Sun, 31 Jan 1999 09:36:43 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id MAA06899 for ; Sun, 31 Jan 1999 12:36:41 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA03433; Sun, 31 Jan 1999 12:36:40 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id MAA00522 for freebsd-current@freebsd.org; Sun, 31 Jan 1999 12:36:40 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199901311736.MAA00522@bb01f39.unx.sas.com> Subject: Re: Scsi chatty'ness can be good.. To: freebsd-current@FreeBSD.ORG Date: Sun, 31 Jan 1999 12:36:40 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, Well, to add a positive vote to this issue.... I run alot of ccd arrays... When I put one together last week, those messages alerted me to a bad drive.... One drive in the array immediately went from 64 available opennings down to about 30. None of the other drives exhibitted this behaviour (nor have I seen it before on my other arrays). Just my 0.02 cents. Thanks! John > On Fri, Jan 29, 1999 at 08:26:49PM -0800, Matthew Jacob wrote: > > > > I've always felt this was too chatty, but the authors disagree.... > > Add my vote for 'too chatty'. Silence it. I agree too. > Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 10:40:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02169 for freebsd-current-outgoing; Sun, 31 Jan 1999 10:40:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02158 for ; Sun, 31 Jan 1999 10:40:10 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA17836; Mon, 1 Feb 1999 03:39:47 +0900 (JST) Message-ID: <36B49315.545D0814@newsguy.com> Date: Mon, 01 Feb 1999 02:29:57 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Patrick Hartling CC: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: Reading a text file with BTX References: <199901311713.LAA06495@friley-184-92.res.iastate.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Patrick Hartling wrote: > > } @set kernelname=kernel > } @read -t 5 -p "Enter kernel name [kernel] : " kernelname > } @load $kernelname > } @include /boot/modules.default > } -include /boot/modules.$kernelname > } @autoboot 5 > > That looks great to me. I was thinking that something like the above would > probably be necessary, but I haven't learned Forth yet. This should be just > what I need though. Thanks! As it happens, none of the above include forth... :-) "Include" hasn't been taught forth yet. Well, not on -current, anyway. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com Would you mind not shooting at the thermonuclear weapons? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 10:57:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04583 for freebsd-current-outgoing; Sun, 31 Jan 1999 10:57:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04549; Sun, 31 Jan 1999 10:57:11 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id QAA02576; Sun, 31 Jan 1999 16:39:00 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.2/8.9.2) with ESMTP id OAA91236; Sun, 31 Jan 1999 14:41:04 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199901311441.OAA91236@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Somers cc: "Jordan K. Hubbard" , Warner Losh , Matthew Dillon , Bruce Evans , current@FreeBSD.ORG, nate@FreeBSD.ORG, julian@FreeBSD.ORG Subject: Re: c_caddr_t (etc) In-reply-to: Your message of "Sat, 30 Jan 1999 22:13:08 GMT." <199901302213.WAA57236@keep.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 31 Jan 1999 14:41:03 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > It's probably a good idea to go easy on the new committers for now > though. Oops, I meant ``to go easy on the *introduction of* new committers''. > > - Jordan > > -- > Brian > > Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 11:35:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10070 for freebsd-current-outgoing; Sun, 31 Jan 1999 11:35:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10047 for ; Sun, 31 Jan 1999 11:35:04 -0800 (PST) (envelope-from fanf@demon.net) Received: by server.noc.demon.net; id TAA10311; Sun, 31 Jan 1999 19:35:02 GMT Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xmab10309; Sun, 31 Jan 99 19:34:55 GMT Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 1072dy-0004z3-00; Sun, 31 Jan 1999 19:34:54 +0000 To: current@FreeBSD.ORG From: Tony Finch Subject: Re: btokup().. patch to STYLE(9) (fwd) In-Reply-To: References: <92584.917604304@axl.noc.iafrica.com> Message-Id: Date: Sun, 31 Jan 1999 19:34:54 +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: >On Fri, 29 Jan 1999, Sheldon Hearn wrote: >> >> The reason I'm interested in this (now tiresome) thread is that I'd much >> rather have to read >> >> /* >> * Bail out if the time left to next transaction is less than >> * the duration of the previous transaction. >> */ >> if (t % u - n % u < d % u) { >> >> than >> >> if (((t % u) - (n % u)) < (d % u)) { > >This is a strawman. The original expression is perfectly fine (by my >rules). One could make a case for: > > if ((t % u) - (n % u) < d % u) Am I a heretic for suggesting this? if (t%u - n%u < d%u) Grouping without brackets! Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 12:00:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12898 for freebsd-current-outgoing; Sun, 31 Jan 1999 12:00:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12891 for ; Sun, 31 Jan 1999 12:00:03 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id LAA63553; Sun, 31 Jan 1999 11:59:49 -0800 (PST) (envelope-from obrien) Date: Sun, 31 Jan 1999 11:59:49 -0800 From: "David O'Brien" To: Bill Paul Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: Even more interesting NFS problems.. Message-ID: <19990131115949.A50177@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <1374.917785105@zippy.cdrom.com> <199901311714.MAA01425@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199901311714.MAA01425@skynet.ctr.columbia.edu>; from Bill Paul on Sun, Jan 31, 1999 at 12:14:32PM -0500 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I use -l /tmp/.automsg (or some other filename that lusers aren't likely ..snip.. > I've found that am-utils is much more verbose than previous versions of > amd so you may not want to leave it that way permanently ... /var/log/amd.log and add it to /etc/newsyslog.conf. Since this is what I use, I've considered makeing this the default rather than "-l syslog". -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 12:13:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14600 for freebsd-current-outgoing; Sun, 31 Jan 1999 12:13:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14595 for ; Sun, 31 Jan 1999 12:13:55 -0800 (PST) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.2/8.9.1) with ESMTP id XAA00403 for ; Sun, 31 Jan 1999 23:11:28 +0300 (MSK) (envelope-from osa@etrust.ru) Date: Sun, 31 Jan 1999 23:11:28 +0300 (MSK) From: oZZ!!! To: current@FreeBSD.ORG Subject: Have a problems with SLIP under 4.0-current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! My system is 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sun Jan 31 22:42:09 MSK 1999 Have a following problem: $ ifconfig sl0 % ifconfig sl0 sl0: flags=c013 mtu 296 inet X.Y.Z.116 --> X.Y.Z.115 netmask 0xfffffff0 broadcast X.Y.Z.115 Does it right? Rgdz, ïÓÏËÉÎ óĊÒÇĊÊ aka oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 12:38:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17802 for freebsd-current-outgoing; Sun, 31 Jan 1999 12:38:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hoflink.com (hoflink.com [199.173.65.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17763 for ; Sun, 31 Jan 1999 12:38:01 -0800 (PST) (envelope-from mikeg@hoflink.com) Received: from hoflink.com (ppp34.hoflink.com [199.173.65.134]) by hoflink.com (8.8.5/8.6.12) with ESMTP id PAA11147 for ; Sun, 31 Jan 1999 15:38:31 -0500 (EST) Message-ID: <36B479AD.3888BEE1@hoflink.com> Date: Sun, 31 Jan 1999 15:41:34 +0000 From: Michael Graziano X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Persistent files under /usr/obj Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I went to remove everything from my /usr/obj directory this morning in preparation to do a make world, and found that two files (/usr/obj/usr/src/tmp/usr/lib/libc.so.3 and /usr/obj/usr/src/tmp/usr/lib/libc_r.so.3) can't be deleted. Am I missing something, or are these two files just hanging out for no reason? -Mike "All we are are monkeys with car keys." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 12:40:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18296 for freebsd-current-outgoing; Sun, 31 Jan 1999 12:40:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from proxy.vvm.com (proxy.vvm.com [204.71.94.238]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18291 for ; Sun, 31 Jan 1999 12:40:52 -0800 (PST) (envelope-from sbarron@abalonesoft.com) Received: from ns.vvm.com (ns.vvm.com [204.71.94.1]) by proxy.vvm.com (8.9.1/8.9.1) with ESMTP id OAA14752; Sun, 31 Jan 1999 14:44:36 -0600 Received: from avalon.com (ta09-093.vvm.com [206.97.173.93]) by ns.vvm.com (8.8.7/8.9.1) with ESMTP id OAA26703; Sun, 31 Jan 1999 14:40:48 -0600 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <36B479AD.3888BEE1@hoflink.com> Date: Sun, 31 Jan 1999 14:41:39 -0600 (CST) From: "Scott A. Barron" To: Michael Graziano Subject: RE: Persistent files under /usr/obj Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG do a chflags -R noschg /usr/obj before you rm it -Scott On 31-Jan-99 Michael Graziano wrote: > I went to remove everything from my /usr/obj directory this morning in > preparation to do a make world, and found that two files > (/usr/obj/usr/src/tmp/usr/lib/libc.so.3 and > /usr/obj/usr/src/tmp/usr/lib/libc_r.so.3) can't be deleted. Am I > missing something, or are these two files just hanging out for no > reason? > > -Mike > "All we are are monkeys with car keys." > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 12:46:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19097 for freebsd-current-outgoing; Sun, 31 Jan 1999 12:46:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19092 for ; Sun, 31 Jan 1999 12:46:21 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id PAA53656; Sun, 31 Jan 1999 15:52:48 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sun, 31 Jan 1999 15:52:48 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: "Scott A. Barron" cc: Michael Graziano , current@FreeBSD.ORG Subject: RE: Persistent files under /usr/obj In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 31 Jan 1999, Scott A. Barron wrote: > On 31-Jan-99 Michael Graziano wrote: > > I went to remove everything from my /usr/obj directory this morning in > > preparation to do a make world, and found that two files > > (/usr/obj/usr/src/tmp/usr/lib/libc.so.3 and > > /usr/obj/usr/src/tmp/usr/lib/libc_r.so.3) can't be deleted. Am I > > missing something, or are these two files just hanging out for no > > reason? > > do a > chflags -R noschg /usr/obj > before you rm it if you don't want to sit there for a long time try: rm -rf /usr/obj/* chflags -R noschg /usr/obj/* rm -rf /usr/obj/* it's substantially faster. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 4.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 14:18:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01260 for freebsd-current-outgoing; Sun, 31 Jan 1999 14:18:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cidaut4.eis.uva.es (cidaut4.eis.uva.es [157.88.142.104]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01251 for ; Sun, 31 Jan 1999 14:18:56 -0800 (PST) (envelope-from sanper@pcfa.es.eu.org) Received: (from uucp@localhost) by cidaut4.eis.uva.es (8.8.5/8.8.5) with UUCP id XAA09599 for current@freebsd.org; Sun, 31 Jan 1999 23:20:49 +0100 (CET) Received: from localhost (sanper@localhost) by ergopc.pcfa.es.eu.org (8.8.8/8.8.8) with SMTP id XAA15964 for ; Sun, 31 Jan 1999 23:17:32 +0100 (CET) (envelope-from sanper@ergopc.pcfa.es.eu.org) Date: Sun, 31 Jan 1999 23:17:31 +0100 (CET) From: "Santiago Perez-Cacho Jr." Reply-To: "Santiago Perez-Cacho Jr." To: current@FreeBSD.ORG Subject: Can't boot from 1st disk on 2nd IDE controller Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello!! I'm running 4.0-CURRENT cvsupped last Friday. I've tried to move my installation from a partition on the first disk of the first IDE controller to a new disk that I've placed as master of the second IDE controller. Everything looks fine until the system tries to mount the root partition and can't find it, so it panics. I've tried breaking the boot process and setting num_ide_disks and rootdev to no avail. Here is the dmesg and error messages: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #2: Sun Jan 31 15:50:25 CET 1999 root@parches.pcfa.es.eu.org:/usr/src/sys/compile/PARCHES Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 200455493 Hz CPU: Pentium/P55C (200.46-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping=3 Features=0x8001bf real memory = 67108864 (65536K bytes) config> quit avail memory = 62464000 (61000K bytes) Preloaded elf kernel "kernel" at 0xf02be000. Probing for devices on PCI bus 0: chip0: rev 0x01 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip2: rev 0x01 on pci0.7.3 vga0: rev 0x01 int a irq 10 on pci0.10.0 ncr0: rev 0x12 int a irq 9 on pci0.11.0 ed1: rev 0x00 int a irq 11 on pci0.12.0 ed1: address 00:40:05:64:67:f2, type NE2000 (16 bit) Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> pcm0 at 0x220 irq 5 drq 1 flags 0x15 on isa atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 2445MB (5008752 sectors), 4969 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (atapi): , removable, intr, iordis acd0: drive speed 689KB/sec, 128KB cache acd0: supported read types: acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): wd2: 1669MB (3419010 sectors), 3618 cyls, 15 heads, 63 S/T, 512 B/S vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Intel Pentium detected, installing workaround for F00F bug Waiting 2 seconds for SCSI devices to settle changing root device to wd1s1a ^^^^^^ changing root device to wd1a ^^^^ error 6: panic : cannot mount root (2) It doesn't matter what I set as num_ide_disks and rootdev, the system always tries to mount partitions on wd1. Is this a known issue or am I doing something wrong? Thanks in advance!! --------------------- Santiago Perez-Cacho sanper@pcfa.es.eu.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 14:48:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05052 for freebsd-current-outgoing; Sun, 31 Jan 1999 14:48:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA05024 for ; Sun, 31 Jan 1999 14:48:34 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id RAA01895 for current@freebsd.org; Sun, 31 Jan 1999 17:55:24 -0500 From: Bill Paul Message-Id: <199901312255.RAA01895@skynet.ctr.columbia.edu> Subject: SIOCADDMULTI doesn't work, proposed fix To: current@FreeBSD.ORG Date: Sun, 31 Jan 1999 17:55:22 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After experimenting some more, I've come to the conclusion that trying to manually add a non-IP ethernet multicast address doesn't work properly. The ether_resolvemulti() assumes that addresses will be specified as either AF_LINK or AF_INET; if the family is AF_LINK, it assumes that a struct sockaddr_dl will be used. However, the user is supposed to pass the address using a struct ifreq, and struct ifreq uses struct sockaddr, not struct sockaddr_dl. The original code in 2.2.x expected a struct sockaddr with a family of AF_UNSPEC. This no longer works in 3.0, which breaks compatibility. Among other things, the Columbia Appletalk port doesn't work because of this. As an aside, the equal() macro in /sys/net/if.c does a bcmp() using sa_len as the length of the data to check, but doesn't account for the possibility of sa_len being 0 (this makes it always return true, which can yield false positives). The patches included with this post change /sys/net/if.c and /sys/net/if_ethersubr.c so that adding a mutlicast address with SIOCADDMULTI using a struct sockaddr and AF_UNSPEC works again. I would like Those Who Know More Than I (tm) to review these changes and offer criticisms and comments. These patches are against 3.0-RELEASE but should apply to -current and -stable as well. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= *** if.c.orig Sun Jan 31 17:13:01 1999 --- if.c Sun Jan 31 17:10:36 1999 *************** *** 186,192 **** register struct ifaddr *ifa; #define equal(a1, a2) \ ! (bcmp((caddr_t)(a1), (caddr_t)(a2), ((struct sockaddr *)(a1))->sa_len) == 0) for (ifp = ifnet.tqh_first; ifp; ifp = ifp->if_link.tqe_next) for (ifa = ifp->if_addrhead.tqh_first; ifa; ifa = ifa->ifa_link.tqe_next) { --- 186,193 ---- register struct ifaddr *ifa; #define equal(a1, a2) \ ! (((struct sockaddr *)(a1))->sa_len && \ ! bcmp((caddr_t)(a1), (caddr_t)(a2), ((struct sockaddr *)(a1))->sa_len) == 0) for (ifp = ifnet.tqh_first; ifp; ifp = ifp->if_link.tqe_next) for (ifa = ifp->if_addrhead.tqh_first; ifa; ifa = ifa->ifa_link.tqe_next) { *************** *** 636,642 **** return EOPNOTSUPP; /* Don't let users screw up protocols' entries. */ ! if (ifr->ifr_addr.sa_family != AF_LINK) return EINVAL; if (cmd == SIOCADDMULTI) { --- 637,644 ---- return EOPNOTSUPP; /* Don't let users screw up protocols' entries. */ ! if (ifr->ifr_addr.sa_family != AF_LINK && ! ifr->ifr_addr.sa_family != AF_UNSPEC) return EINVAL; if (cmd == SIOCADDMULTI) { *** if_ethersubr.c.orig Sun Jan 31 17:13:07 1999 --- if_ethersubr.c Sun Jan 31 17:00:54 1999 *************** *** 778,783 **** --- 778,800 ---- u_char *e_addr; switch(sa->sa_family) { + case AF_UNSPEC: + e_addr = (u_char *)&sa->sa_data; + if ((e_addr[0] & 1) != 1) + return EADDRNOTAVAIL; + MALLOC(sdl, struct sockaddr_dl *, sizeof *sdl, M_IFMADDR, + M_WAITOK); + sdl->sdl_len = sizeof *sdl; + sdl->sdl_family = AF_LINK; + sdl->sdl_index = ifp->if_index; + sdl->sdl_type = IFT_ETHER; + sdl->sdl_nlen = 0; + sdl->sdl_alen = ETHER_ADDR_LEN; + sdl->sdl_slen = 0; + e_addr = LLADDR(sdl); + bcopy((char *)&sa->sa_data, (char *)e_addr, ETHER_ADDR_LEN); + *llsa = (struct sockaddr *)sdl; + return 0; case AF_LINK: /* * No mapping needed. Just check that it's a valid MC address. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 14:50:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05254 for freebsd-current-outgoing; Sun, 31 Jan 1999 14:50:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05162 for ; Sun, 31 Jan 1999 14:49:43 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id JAA22576; Mon, 1 Feb 1999 09:19:36 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA26288; Mon, 1 Feb 1999 09:19:35 +1030 Date: Mon, 1 Feb 1999 09:19:35 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: "Daniel C. Sobral" Cc: current@FreeBSD.ORG Subject: Re: vn and 4.0 In-Reply-To: <36B47C1B.C509042A@newsguy.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 1 Feb 1999, Daniel C. Sobral wrote: > Is vn safe right now on -current? It's broken for me without Matt's patch posted the other day (not yet checked in). I can send you a copy if you missed it. > And does current's msdos fs > support fat-32? Don't know, but I think so. Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 15:05:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07041 for freebsd-current-outgoing; Sun, 31 Jan 1999 15:05:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sand2.sentex.ca (sand2.sentex.ca [209.167.248.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07033; Sun, 31 Jan 1999 15:05:33 -0800 (PST) (envelope-from mike@sentex.net) Received: from gravel (ospf-wat.sentex.net [209.167.248.81]) by sand2.sentex.ca (8.8.8/8.8.8) with SMTP id SAA09232; Sun, 31 Jan 1999 18:05:31 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.1.19990131181107.04928040@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 31 Jan 1999 18:11:53 -0500 To: stable@FreeBSD.ORG From: Mike Tancsa Subject: current.freebsd.org backup and then back down :-( Cc: current@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Connected to usw2.freebsd.org. 220 usw2.freebsd.org FTP server (Version 6.00) ready. Name (current.freebsd.org:mdtancsa): ftp 331 Guest login ok, send your email address as password. Password: 550 Can't set guest privileges. ftp: Login failed. Remote system type is UNIX. Using binary mode to transfer files. ftp> ---Mike ********************************************************************** Mike Tancsa, Network Admin * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 01.519.651.3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 15:11:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08144 for freebsd-current-outgoing; Sun, 31 Jan 1999 15:11:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from post.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08139 for ; Sun, 31 Jan 1999 15:11:23 -0800 (PST) (envelope-from bsdcurrent@scratch.demon.co.uk) Received: from [212.228.22.156] (helo=scratch.demon.co.uk) by post.mail.demon.net with smtp (Exim 2.11 #1) id 10761J-0007e6-00 for current@FreeBSD.ORG; Sun, 31 Jan 1999 23:11:16 +0000 Message-ID: Date: Sun, 31 Jan 1999 23:10:17 +0000 To: current@FreeBSD.ORG From: Tim Preece Subject: Kernel wont compile MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain;charset=iso-8859-1 X-Mailer: Turnpike (32) Version 4.00 <2bL8TQCIEWg0B+1EtXWvseZtDP> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Iv'e CVSupped on Friday 29/1/99 and proceeded to make world seemed to go OK but when I tried to compile the kernel I got this.... Script started on Sat Jan 30 00:27:14 1999 [2]root@scratch1/usr/src/sys/ compile/SCRATCH1# make depend cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes - Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat- extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h ../../i386/i386/genassym.c In file included from ../../sys/types.h:48, from ../../sys/param.h:56, from ../../i386/i386/genassym.c:45: ../../sys/inttypes.h:11: parse error before `int8_t' ../../sys/inttypes.h:11: warning: data definition has no type or storage class ../../sys/inttypes.h:12: parse error before `int16_t' ../../sys/inttypes.h:12: warning: data definition has no type or storage class ../../sys/inttypes.h:13: parse error before `int32_t' ../../sys/inttypes.h:13: warning: data definition has no type or storage class ../../sys/inttypes.h:16: parse error before `uint8_t' ../../sys/inttypes.h:16: warning: data definition has no type or storage class ../../sys/inttypes.h:17: parse error before `uint16_t' ../../sys/inttypes.h:17: warning: data definition has no type or storage class ../../sys/inttypes.h:18: parse error before `uint32_t' ../../sys/inttypes.h:18: warning: data definition has no type or storage class ../../sys/inttypes.h:21: parse error before `intptr_t' ../../sys/inttypes.h:21: warning: data definition has no type or storage class ../../sys/inttypes.h:22: parse error before `uintptr_t' ../../sys/inttypes.h:22: warning: data definition has no type or storage class In file included from ../../sys/types.h:49, from ../../sys/param.h:56, from ../../i386/i386/genassym.c:45: machine/types.h:59: `int8_t' redeclared as different kind of symbol ../../sys/inttypes.h:11: previous declaration of `int8_t' machine/types.h:59: warning: `int8_t' was declared `extern' and later `static' machine/types.h:61: `int16_t' redeclared as different kind of symbol ../../sys/inttypes.h:12: previous declaration of `int16_t' machine/types.h:61: warning: `int16_t' was declared `extern' and later `static' machine/types.h:63: `int32_t' redeclared as different kind of symbol ../../sys/inttypes.h:13: previous declaration of `int32_t' machine/types.h:63: warning: `int32_t' was declared `extern' and later `static' machine/types.h:65: redefinition of `int64_t' ../../sys/inttypes.h:14: `int64_t' previously declared here machine/types.h:75: `intptr_t' redeclared as different kind of symbol ../../sys/inttypes.h:21: previous declaration of `intptr_t' machine/types.h:75: warning: `intptr_t' was declared `extern' and later `static' machine/types.h:76: `uintptr_t' redeclared as different kind of symbol ../../sys/inttypes.h:22: previous declaration of `uintptr_t' machine/types.h:76: warning: `uintptr_t' was declared `extern' and later `static' In file included from ../../sys/param.h:56, from ../../i386/i386/genassym.c:45: ../../sys/types.h:60: syntax error before `u_int8_t' ../../sys/types.h:60: warning: useless keyword or type name in empty declaration ../../sys/types.h:60: warning: empty declaration ../../sys/types.h:61: syntax error before `u_int16_t' ../../sys/types.h:61: warning: useless keyword or type name in empty declaration ../../sys/types.h:61: warning: empty declaration ../../sys/types.h:62: syntax error before `u_int32_t' ../../sys/types.h:62: warning: useless keyword or type name in empty declaration ../../sys/types.h:62: warning: empty declaration ../../sys/types.h:63: redefinition of `u_int64_t' machine/types.h:66: `u_int64_t' previously declared here ../../sys/types.h:90: redefinition of `ufs_daddr_t' machine/types.h:70: `ufs_daddr_t' previously declared here ../../sys/types.h:95: redefinition of `uoff_t' machine/types.h:77: `uoff_t' previously declared here *** Error code 1 Stop. [2]root@scratch1/usr/src/sys/compile/SCRATCH1# exit exit Script done on Sat Jan 30 00:27:26 1999 What should I do, re-CVSup, make clean or other ? Please help Thanks -- Tim Preece To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 15:14:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08554 for freebsd-current-outgoing; Sun, 31 Jan 1999 15:14:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08547 for ; Sun, 31 Jan 1999 15:14:01 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id SAA06802; Sun, 31 Jan 1999 18:13:52 -0500 (EST) Date: Sun, 31 Jan 1999 18:13:52 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Kris Kennaway cc: "Daniel C. Sobral" , current@FreeBSD.ORG Subject: Re: vn and 4.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 1 Feb 1999, Kris Kennaway wrote: > On Mon, 1 Feb 1999, Daniel C. Sobral wrote: > > > Is vn safe right now on -current? > > It's broken for me without Matt's patch posted the other day (not yet checked > in). I can send you a copy if you missed it. > > > And does current's msdos fs > > support fat-32? > > Don't know, but I think so. FAT32 has been supported for quite a while now, along with FAT12/FAT16 and the VFAT extension (long file names). In fact, we've just about got a read only NTFS now too. > > Kris > > ----- > (ASP) Microsoft Corporation (MSFT) announced today that the release of its > productivity suite, Office 2000, will be delayed until the first quarter > of 1901. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 15:37:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12093 for freebsd-current-outgoing; Sun, 31 Jan 1999 15:37:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from servo.ccr.org (servo.ccr.org [198.3.0.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12082 for ; Sun, 31 Jan 1999 15:37:44 -0800 (PST) (envelope-from mo@servo.ccr.org) Received: (from mo@localhost) by servo.ccr.org (8.9.2/8.9.2) id SAA02589 for freebsd-current@freebsd.org; Sun, 31 Jan 1999 18:37:43 -0500 (EST) (envelope-from mo) Date: Sun, 31 Jan 1999 18:37:43 -0500 (EST) From: "Mike O'Dell" Message-Id: <199901312337.SAA02589@servo.ccr.org> To: freebsd-current@FreeBSD.ORG Subject: a nit, however.... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG any reason why the kernel "config" program shouldn't be changed to dramatically reduce the requirement for the silling quoting of option values??? if an option needs embedded whitespace, but other than that, is there any reason other than historical for the silliness about nubmers, etc?? -mo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 16:13:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18214 for freebsd-current-outgoing; Sun, 31 Jan 1999 16:13:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18185 for ; Sun, 31 Jan 1999 16:13:17 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id TAA09893; Sun, 31 Jan 1999 19:13:10 -0500 (EST) Date: Sun, 31 Jan 1999 19:13:10 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: "Mike O'Dell" cc: freebsd-current@FreeBSD.ORG Subject: Re: a nit, however.... In-Reply-To: <199901312337.SAA02589@servo.ccr.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 31 Jan 1999, Mike O'Dell wrote: > > any reason why the kernel "config" program shouldn't > be changed to dramatically reduce the requirement for > the silling quoting of option values??? if an option > needs embedded whitespace, but other than that, > is there any reason other than historical for > the silliness about nubmers, etc?? Actually, as I understand it config(8) was never meant to allow the LACK of quotation marks. It's simply we've grown accustomed to not using them, I suppose, that we don't. I, for one, have every option quoted in my kernel configuration file. The right thing would be to not allow lack of quotes at all, I believe, but that would be disastrous now with current config files, and release scripts. > > -mo > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 16:21:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19272 for freebsd-current-outgoing; Sun, 31 Jan 1999 16:21:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA19267 for ; Sun, 31 Jan 1999 16:21:06 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.2) with ESMTP id QAA79810; Sun, 31 Jan 1999 16:21:42 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Bill Paul cc: current@FreeBSD.ORG, obrien@nuxi.com Subject: Re: Even more interesting NFS problems.. In-reply-to: Your message of "Sun, 31 Jan 1999 12:14:32 EST." <199901311714.MAA01425@skynet.ctr.columbia.edu> Date: Sun, 31 Jan 1999 16:21:41 -0800 Message-ID: <79808.917828501@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Err.... On all of the machines where I use amd, I don't use -l syslog. > I use -l /tmp/.automsg (or some other filename that lusers aren't likely You're right, that does produce more information. Unfortunatly, not enough to help diagnose the problem. :( I think something more fundamental is broken here since it doesn't even log the requests you make of it. All you get are the startup messages, then silence forever more. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 16:51:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22115 for freebsd-current-outgoing; Sun, 31 Jan 1999 16:51:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from jason03.u.washington.edu (jason03.u.washington.edu [140.142.77.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA22106 for ; Sun, 31 Jan 1999 16:51:22 -0800 (PST) (envelope-from jcwells@u.washington.edu) Received: from saul7.u.washington.edu (root@saul7.u.washington.edu [140.142.82.2]) by jason03.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA11108; Sun, 31 Jan 1999 16:51:21 -0800 Received: from S8-37-26.student.washington.edu (S8-37-26.student.washington.edu [128.208.37.26]) by saul7.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA13870; Sun, 31 Jan 1999 16:51:20 -0800 (PST) Date: Mon, 1 Feb 1999 00:50:48 +0000 (GMT) From: "Jason C. Wells" X-Sender: jason@s8-37-26.student.washington.edu Reply-To: "Jason C. Wells" To: Michael Graziano cc: current@FreeBSD.ORG Subject: Re: Persistent files under /usr/obj In-Reply-To: <36B479AD.3888BEE1@hoflink.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 31 Jan 1999, Michael Graziano wrote: >I went to remove everything from my /usr/obj directory this morning in >preparation to do a make world, and found that two files >(/usr/obj/usr/src/tmp/usr/lib/libc.so.3 and >/usr/obj/usr/src/tmp/usr/lib/libc_r.so.3) can't be deleted. Am I >missing something, or are these two files just hanging out for no >reason? chflags -R noschg Research that before you use it. My memory fails me on the syntax. Catchya Later, | Give me UNIX or give me a typewriter. Jason Wells | http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 17:09:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24334 for freebsd-current-outgoing; Sun, 31 Jan 1999 17:09:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24327 for ; Sun, 31 Jan 1999 17:09:15 -0800 (PST) (envelope-from gnb@itga.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id MAA02960; Mon, 1 Feb 1999 12:09:10 +1100 (EST) Received: from lightning.itga.com.au(192.168.71.20) via SMTP by fw.bby.com.au, id smtpd002958; Mon Feb 1 01:09:03 1999 Received: from lightning (lightning [192.168.71.20]) by lightning.itga.com.au (8.9.1a/8.9.1) with ESMTP id MAA03424; Mon, 1 Feb 1999 12:09:02 +1100 (EST) Message-Id: <199902010109.MAA03424@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: Brian Feldman Cc: Christopher Masto , current@FreeBSD.ORG Subject: Re: btokup().. patch to STYLE(9) (fwd) In-reply-to: Your message of Fri, 29 Jan 1999 11:29:29 -0500. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 01 Feb 1999 12:09:02 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I seem to remember there once was a comment in a well-known body of code, which > went something like: > "You are not supposed to understand this." It was (IIRC) the process switching magic at the heart of fork() in V7 (and earlier, I assume). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 17:17:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26036 for freebsd-current-outgoing; Sun, 31 Jan 1999 17:17:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.kersur.net (mail.kersur.net [199.79.199.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26031 for ; Sun, 31 Jan 1999 17:17:53 -0800 (PST) (envelope-from dswartz@druber.com) Received: from manticore (manticore.druber.com [207.180.95.108]) by mail.kersur.net (8.9.1/8.9.1) with SMTP id UAA15969; Sun, 31 Jan 1999 20:20:21 -0500 (EST) Message-Id: <3.0.5.32.19990131201731.009da5f0@mail.kersur.net> X-Sender: druber@mail.kersur.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Sun, 31 Jan 1999 20:17:31 -0500 To: Gregory Bond From: Dan Swartzendruber Subject: Re: btokup().. patch to STYLE(9) (fwd) Cc: Brian Feldman , Christopher Masto , current@FreeBSD.ORG In-Reply-To: <199902010109.MAA03424@lightning.itga.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:09 PM 2/1/99 +1100, Gregory Bond wrote: >> I seem to remember there once was a comment in a well-known body of code, which >> went something like: >> "You are not supposed to understand this." > >It was (IIRC) the process switching magic at the heart of fork() in V7 (and >earlier, I assume). If I remember right, it referred to the non-local goto juju where if the forked processed was swapped out, the label jumped was changed to yet another place. Unfortunately, my annotated V6 listing is not accessible right now... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 17:21:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26509 for freebsd-current-outgoing; Sun, 31 Jan 1999 17:21:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from servo.ccr.org (servo.ccr.org [198.3.0.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26501 for ; Sun, 31 Jan 1999 17:21:34 -0800 (PST) (envelope-from mo@servo.ccr.org) Received: from servo.ccr.org (localhost [127.0.0.1]) by servo.ccr.org (8.9.2/8.9.2) with ESMTP id UAA03978; Sun, 31 Jan 1999 20:21:31 -0500 (EST) (envelope-from mo@servo.ccr.org) Message-Id: <199902010121.UAA03978@servo.ccr.org> To: Brian Feldman cc: freebsd-current@FreeBSD.ORG, mo@servo.ccr.org Subject: Re: a nit, however.... In-reply-to: Your message of "Sun, 31 Jan 1999 19:13:10 EST." Date: Sun, 31 Jan 1999 20:21:31 -0500 From: "Mike O'Dell" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG actually, i was there when Sam Leffler first wrote "config" and that was never the intention, and that proposed fix would be astoundingly silly -mo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 17:25:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26964 for freebsd-current-outgoing; Sun, 31 Jan 1999 17:25:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fep1-orange.clear.net.nz (fep1-orange.clear.net.nz [203.97.32.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26952 for ; Sun, 31 Jan 1999 17:25:16 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep1-orange.clear.net.nz (1.5/1.11) with ESMTP id OAA02348; Mon, 1 Feb 1999 14:25:07 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.2/8.9.1) id OAA50584; Mon, 1 Feb 1999 14:25:07 +1300 (NZDT) (envelope-from jabley) Date: Mon, 1 Feb 1999 14:25:03 +1300 From: Joe Abley To: "Jordan K. Hubbard" Cc: obrien@NUXI.com, current@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: Even more interesting NFS problems.. Message-ID: <19990201142503.B50525@clear.co.nz> References: <19990131024914.C67786@relay.nuxi.com> <1374.917785105@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <1374.917785105@zippy.cdrom.com>; from Jordan K. Hubbard on Sun, Jan 31, 1999 at 04:18:25AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been using amd on bleeding-edge current for the past year or so with no problems - the servers in my case are Solaris 2.5.1 boxes. I remember becoming extremely confused when I configured my first amd map file, since there was no coherent documentation to be found at the time, but I ended up with this (and have kept it ever since): % grep amd /etc/rc.conf amd_enable="YES" # Run amd service with $amd_flags (or NO). amd_flags="-a /a -c 1800 -k i386 -d clear.net.nz -l syslog /home /etc/amd.home.map /net /etc/amd.net.map" amd_map_program="NO" # Can be set to "ypcat -k amd.master" % % cat /etc/amd.home.map # auto-mount home directories /defaults type:=nfs;rfs=/export/${path};rhost:=oms jabley rhost:=intdev * opts:=rw,resvport % % cat /etc/amd.net.map # automount /net hierarchies /defaults opts:=rw,grpid,resvport,nosuid buddha type:=link;fs=/ * type:=host;rhost:=${key} buddha is the local machine; intdev is where my home directory happens to be (everybody else's is mounted off oms). Never had a problem with it. Just to confirm that amd is not hideously broken beyond the point where _some_ people can use it just fine. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 18:17:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02973 for freebsd-current-outgoing; Sun, 31 Jan 1999 18:17:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02967 for ; Sun, 31 Jan 1999 18:17:18 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id VAA17157; Sun, 31 Jan 1999 21:17:10 -0500 (EST) Message-ID: <19990131211710.B12496@netmonger.net> Date: Sun, 31 Jan 1999 21:17:10 -0500 From: Christopher Masto To: Bill Paul Cc: current@FreeBSD.ORG Subject: Re: Network/ARP problem? Maybe pn driver? References: <19990129180612.C3237@netmonger.net> <199901292328.SAA26781@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199901292328.SAA26781@skynet.ctr.columbia.edu>; from Bill Paul on Fri, Jan 29, 1999 at 06:28:46PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 29, 1999 at 06:28:46PM -0500, Bill Paul wrote: > - Change the if() clause so that it looks like this: > > if (sc->pn_promisc_war /*&& ifp->if_flags & IFF_PROMISC*/) { > > (In other words, comment out the test for the IFF_PROMISC flag.) > > This will enable the workaround all the time and allow the receiver bug > to be detected and handled properly. > > Compile a new kernel with this change and see if the problem persists. > Report back your findings (one way or the other) so that I'll know if > I should modify the code in the repository. I'm sad to say, this didn't solve the problem. It still happens exactly as before, and still goes away immediately if I run a tcpdump on another console (but not if I do tcpdump -p). I did add a printf when pn_promisc_war is set to 1 just to make sure that it was being properly detected and turned on, and it is.. but enabling the workaround all the time doesn't seem to help. -- Christopher Masto Director of Operations NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net "Good tools allow users to do stupid things." -- Clay Shirky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 18:41:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05236 for freebsd-current-outgoing; Sun, 31 Jan 1999 18:41:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.atl.bellsouth.net (mail.atl.bellsouth.net [205.152.0.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05231 for ; Sun, 31 Jan 1999 18:41:44 -0800 (PST) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-65-117.atl.bellsouth.net [209.214.65.117]) by mail.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id VAA28938; Sun, 31 Jan 1999 21:41:42 -0500 (EST) Received: from wghicks (localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.2/8.9.2) with ESMTP id VAA00534; Sun, 31 Jan 1999 21:58:33 -0500 (EST) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199902010258.VAA00534@bellsouth.net> To: "Scott A. Barron" cc: Michael Graziano , current@FreeBSD.ORG, wghicks@wghicks.bellsouth.net Subject: Re: Persistent files under /usr/obj In-reply-to: Your message of "Sun, 31 Jan 1999 14:41:39 CST." Date: Sun, 31 Jan 1999 21:58:32 -0500 From: W Gerald Hicks Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >do a >chflags -R noschg /usr/obj >before you rm it Uh no... do the 'rm' first, tolerate the few warnings, _then_ do the chflags and then another 'rm'. It's faster on my stopwatch anyway :) Cheers, Jerry Hicks wghicks@bellsouth.net > >-Scott > >On 31-Jan-99 Michael Graziano wrote: >> I went to remove everything from my /usr/obj directory this morning in >> preparation to do a make world, and found that two files >> (/usr/obj/usr/src/tmp/usr/lib/libc.so.3 and >> /usr/obj/usr/src/tmp/usr/lib/libc_r.so.3) can't be deleted. Am I >> missing something, or are these two files just hanging out for no >> reason? >> >> -Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 20:08:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA13670 for freebsd-current-outgoing; Sun, 31 Jan 1999 20:08:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail2.rochester.rr.com (mail2-1.twcny.rr.com [24.92.226.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13664 for ; Sun, 31 Jan 1999 20:08:55 -0800 (PST) (envelope-from leisner@rochester.rr.com) Received: from rochester.rr.com ([24.93.25.38]) by mail2.rochester.rr.com (Post.Office MTA v3.5.2 release 221 ID# 0-53939U80000L80000S0V35) with ESMTP id com; Sun, 31 Jan 1999 23:10:17 -0500 Received: from dw.home (leisner@localhost [127.0.0.1]) by rochester.rr.com (8.8.7/8.8.5) with ESMTP id XAA01185; Sun, 31 Jan 1999 23:08:50 -0500 Message-Id: <199902010408.XAA01185@rochester.rr.com> X-Mailer: exmh version 2.0.2 Reply-to: leisner@rochester.rr.com To: Sheldon Hearn cc: Mikhail Teterin , current@FreeBSD.ORG Subject: Re: btokup().. patch to STYLE(9) (fwd) In-reply-to: Your message of "Fri, 29 Jan 1999 10:27:00 +0200." <88592.917598420@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 31 Jan 1999 23:08:50 -0500 From: "Marty Leisner" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > On Fri, 29 Jan 1999 00:55:21 EST, Mikhail Teterin wrote: > > > Everybody's goal is to keep/make code readable (accusations of "trying > > to obfuscate" are silly). You, people, are just not agreeing what > > "readable" means. Hoping to aid in the ending of this thread(s), > > Thank you very much. This is _exactly_ the point here. > > As far as I see it, there are a lot of people who are saying > > "I want to use parens to improve readability" > > when what they really mean is > > "I want to use parens to obviate the need to learn operator precedence." > > I can't imagine how unnecessary parens are going to improve > "readability" for anyone who knows his/her operator precedence. What > it does is allow folks who aren't sure about what they're doing to get > around doing things properly. > > Ciao, > Sheldon. > If you use paranthesis, you don't have to memorize the operator precedence. People are not compilers, unnecessary parenthesis/braces is usally a good idea where there could be some confusion. In our work place we have a policy of extra braces around single line ifs...the idea is people often add lines in maintaince, and forget to add the braces...I think its a good argument for maintability... Marty Leisner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 20:30:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15922 for freebsd-current-outgoing; Sun, 31 Jan 1999 20:30:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA15909 for ; Sun, 31 Jan 1999 20:30:23 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id XAA14690; Sun, 31 Jan 1999 23:30:19 -0500 (EST) (envelope-from wollman) Date: Sun, 31 Jan 1999 23:30:19 -0500 (EST) From: Garrett Wollman Message-Id: <199902010430.XAA14690@khavrinen.lcs.mit.edu> To: "Jordan K. Hubbard" Cc: obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: Even more interesting NFS problems.. In-Reply-To: <1374.917785105@zippy.cdrom.com> References: <19990131024914.C67786@relay.nuxi.com> <1374.917785105@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Erm, I haven't tried it between 3.0 and 3.0 boxes because all my test > environments currently involve one of each (4.0 and 3.0), but I can > certainly say that in none of these test environments does amd work at > all. Works just fine on a somewhat older 3.0 (which is still running the new amd). Believe me, I would have screamed like hell if both my home directory and my Web server stopped working... So, clearly, the kernel <-> amd part works, and so does NFSv2 to a SunOS machine (see below). wollman@khavrinen$ ps alwwx | fgrep amd 0 138 1 0 2 0 1004 468 select Ss ?? 4:18.35 amd -p -x noinfo /net /etc/amd.net /home /etc/amd.home 12369 14676 14668 4 -6 0 932 484 piperd S+ p2 0:00.01 fgrep amd wollman@khavrinen$ cat /etc/amd.net /defaults type:=host;fs:=${autodir}/root/${rhost};rhost:=${key} * opts:=rw,grpid,noexec,nosuid wollman@khavrinen$ cat /etc/amd.home /defaults sublink:=${key};opts:=rw,soft,intr * type:=linkx;fs:=/homes wollman@khavrinen$ ls -l /home total 2 lrwxrwxrwx 1 root wheel 15 Jan 31 23:25 postgres@ -> /homes/postgres lrwxrwxrwx 1 root wheel 14 Jan 31 22:23 wollman@ -> /homes/wollman lrwxrwxrwx 1 root wheel 10 Jan 31 23:25 www@ -> /homes/www wollman@khavrinen$ cd /net/tower wollman@khavrinen$ ls cdrom/ pcfs/ wollman@khavrinen$ cd pcfs wollman@khavrinen$ mount /dev/wd0s1a on / (local, writes: sync 195 async 6628) /dev/wd0s1d on /var (local, writes: sync 26599 async 47055) /dev/wd0s1e on /usr (local, writes: sync 69 async 5534) /dev/wd0s1f on /usr/local (NFS exported, local, writes: sync 1325 async 3876) /dev/wd0s1g on /homes (local, writes: sync 114203 async 287246) /dev/wd0s1h on /usr/obj (asynchronous, NFS exported, local, noatime, writes: sync 2 async 0) /dev/sd0s1d on /usr/src (NFS exported, local, writes: sync 26974 async 33971) /dev/sd0s1e on /usr/ports (NFS exported, local, writes: sync 14951 async 56478) procfs on /proc (local) pid138@khavrinen:/home on /home pid138@khavrinen:/net on /net tower:/cdrom on /a/root/tower/cdrom (noexec, nosuid) tower:/pcfs on /a/root/tower/pcfs (noexec, nosuid) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 20:58:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19485 for freebsd-current-outgoing; Sun, 31 Jan 1999 20:58:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19480 for ; Sun, 31 Jan 1999 20:58:45 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id XAA14745; Sun, 31 Jan 1999 23:58:31 -0500 (EST) (envelope-from wollman) Date: Sun, 31 Jan 1999 23:58:31 -0500 (EST) From: Garrett Wollman Message-Id: <199902010458.XAA14745@khavrinen.lcs.mit.edu> To: Bill Paul Cc: current@FreeBSD.ORG Subject: SIOCADDMULTI doesn't work, proposed fix In-Reply-To: <199901312255.RAA01895@skynet.ctr.columbia.edu> References: <199901312255.RAA01895@skynet.ctr.columbia.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > a struct sockaddr_dl will be used. However, the user is supposed to > pass the address using a struct ifreq, and struct ifreq uses struct > sockaddr, not struct sockaddr_dl. This is called ``poor man's inheritance''. I believe it is an error for any code to use AF_UNSPEC for any purpose other than masks (where it makes sense since the address family is normally not included in the mask). A `sockaddr_dl', while by default longer than a `sockaddr', in this case will fit withing the structure allotted. In the future, I fully expect that `sockaddr' will be of maximal length (we need this for IPv6). > The patches included with this post change /sys/net/if.c and > /sys/net/if_ethersubr.c so that adding a mutlicast address with > SIOCADDMULTI using a struct sockaddr and AF_UNSPEC works again. I would > like Those Who Know More Than I (tm) to review these changes and offer > criticisms and comments. There are two things which should be done here. First, the kernel AppleTalk code should be fixed to join the necessary multicast groups when an interface is first configured for AppleTalk. (By preference the AARP implementation should be entirely in the kernel as well, but that's more of a challenge.) Second, the generic ether_resolvemulti function should be enhanced to know about AppleTalk multicast addresses. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 21:21:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21753 for freebsd-current-outgoing; Sun, 31 Jan 1999 21:21:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles313.castles.com [208.214.167.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21735 for ; Sun, 31 Jan 1999 21:21:18 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA10261; Sun, 31 Jan 1999 21:17:20 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902010517.VAA10261@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Santiago Perez-Cacho Jr." cc: current@FreeBSD.ORG Subject: Re: Can't boot from 1st disk on 2nd IDE controller In-reply-to: Your message of "Sun, 31 Jan 1999 23:17:31 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 31 Jan 1999 21:17:20 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG set root_disk_unit=2 > Hello!! > I'm running 4.0-CURRENT cvsupped last Friday. I've tried to move my > installation from a partition on the first disk of the first IDE > controller to a new disk that I've placed as master of the second IDE > controller. Everything looks fine until the system tries to mount the > root partition and can't find it, so it panics. I've tried breaking the > boot process and setting num_ide_disks and rootdev to no avail. > > Here is the dmesg and error messages: > > Copyright (c) 1992-1999 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 4.0-CURRENT #2: Sun Jan 31 15:50:25 CET 1999 > root@parches.pcfa.es.eu.org:/usr/src/sys/compile/PARCHES > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 200455493 Hz > CPU: Pentium/P55C (200.46-MHz 586-class CPU) > Origin = "GenuineIntel" Id = 0x543 Stepping=3 > Features=0x8001bf > real memory = 67108864 (65536K bytes) > config> quit > avail memory = 62464000 (61000K bytes) > Preloaded elf kernel "kernel" at 0xf02be000. > Probing for devices on PCI bus 0: > chip0: rev 0x01 on pci0.0.0 > chip1: rev 0x01 on pci0.7.0 > ide_pci0: rev 0x01 on pci0.7.1 > chip2: rev 0x01 on pci0.7.3 > vga0: rev 0x01 int a irq 10 on pci0.10.0 > ncr0: rev 0x12 int a irq 9 on pci0.11.0 > ed1: rev 0x00 int a irq 11 on pci0.12.0 > ed1: address 00:40:05:64:67:f2, type NE2000 (16 bit) > Probing for PnP devices: > Probing for devices on the ISA bus: > sc0 on isa > sc0: VGA color <16 virtual consoles, flags=0x0> > pcm0 at 0x220 irq 5 drq 1 flags 0x15 on isa > atkbdc0 at 0x60-0x6f on motherboard > atkbd0 irq 1 on isa > sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > sio0: type 16550A > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > lpt0 at 0x378-0x37f irq 7 on isa > lpt0: Interrupt-driven port > lp0: TCP/IP capable interface > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: FIFO enabled, 8 bytes threshold > fd0: 1.44MB 3.5in > wdc0 at 0x1f0-0x1f7 irq 14 on isa > wdc0: unit 0 (wd0): > wd0: 2445MB (5008752 sectors), 4969 cyls, 16 heads, 63 S/T, 512 B/S > wdc0: unit 1 (atapi): , removable, intr, iordis > acd0: drive speed 689KB/sec, 128KB cache > acd0: supported read types: > acd0: Audio: play, 255 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: no/blank disc inside, unlocked > wdc1 at 0x170-0x177 irq 15 on isa > wdc1: unit 0 (wd2): > wd2: 1669MB (3419010 sectors), 3618 cyls, 15 heads, 63 S/T, 512 B/S > vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa > npx0 on motherboard > npx0: INT 16 interface > Intel Pentium detected, installing workaround for F00F bug > Waiting 2 seconds for SCSI devices to settle > changing root device to wd1s1a > ^^^^^^ > changing root device to wd1a > ^^^^ > error 6: panic : cannot mount root (2) > > It doesn't matter what I set as num_ide_disks and rootdev, the system > always tries to mount partitions on wd1. Is this a known issue or am I > doing something wrong? > > Thanks in advance!! > > --------------------- > Santiago Perez-Cacho > sanper@pcfa.es.eu.org > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 21:49:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25282 for freebsd-current-outgoing; Sun, 31 Jan 1999 21:49:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25276 for ; Sun, 31 Jan 1999 21:49:12 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id VAA27831; Sun, 31 Jan 1999 21:48:40 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id VAA09450; Sun, 31 Jan 1999 21:48:39 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id VAA07713; Sun, 31 Jan 1999 21:48:36 -0800 (PST) From: Don Lewis Message-Id: <199902010548.VAA07713@salsa.gv.tsc.tdk.com> Date: Sun, 31 Jan 1999 21:48:36 -0800 In-Reply-To: Sheldon Hearn "Re: btokup().. patch to STYLE(9) (fwd)" (Jan 29, 12:05pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Sheldon Hearn , Greg Lehey Subject: Re: btokup().. patch to STYLE(9) (fwd) Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jan 29, 12:05pm, Sheldon Hearn wrote: } Subject: Re: btokup().. patch to STYLE(9) (fwd) } The reason I'm interested in this (now tiresome) thread is that I'd much } rather have to read } } /* } * Bail out if the time left to next transaction is less than } * the duration of the previous transaction. } */ } if (t % u - n % u < d % u) { } } than } } if (((t % u) - (n % u)) < (d % u)) { } } Giving folks the go-ahead to use parens as a form of documentation is } misguided and will end in tears. MHO. This is a fairly trivial example, but I find the second version slightly easier to read at a glance. I do think it's overly parenthesized, though. I prefer if ((t % u - n % u) < (d % u)) { or if ((t % u - n % u) < d % u) { because they are less cluttered. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 22:06:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA27322 for freebsd-current-outgoing; Sun, 31 Jan 1999 22:05:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA27314 for ; Sun, 31 Jan 1999 22:05:15 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id WAA27908; Sun, 31 Jan 1999 22:00:11 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id WAA09611; Sun, 31 Jan 1999 22:00:10 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id WAA07742; Sun, 31 Jan 1999 22:00:09 -0800 (PST) From: Don Lewis Message-Id: <199902010600.WAA07742@salsa.gv.tsc.tdk.com> Date: Sun, 31 Jan 1999 22:00:09 -0800 In-Reply-To: Poul-Henning Kamp "Re: btokup().. patch to STYLE(9) (fwd)" (Jan 29, 9:13am) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: btokup().. patch to STYLE(9) (fwd) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jan 29, 9:13am, Poul-Henning Kamp wrote: } Subject: Re: btokup().. patch to STYLE(9) (fwd) } } On the other hand style(9) should still firmly outlaw stuff like: } } /* wait 10 ms */ } if (((error = tsleep((caddr_t)dev, PPBPRI | PCATCH, } "ppbpoll", hz/100)) != EWOULDBLOCK) != 0) { } return (error); } } The "!= 0" is obviously bogus, but what about: if ((error = tsleep((caddr_t)dev, PPBPRI | PCATCH, "ppbpoll", hz/100)) != EWOULDBLOCK) { return (error); } It would be better if the "!=" fit on the previous line. What if the expression fit on one 80 character line? BTW, something I like that I picked up from Paul Vixie's code is indenting all the arguments to a function by the same amount. Forcing an unneccesary line wrap: if ((error = tsleep((caddr_t)dev, PPBPRI | PCATCH, "ppbpoll", hz/100)) != EWOULDBLOCK) { return (error); } which isn't real clean because of the trailing "!= EWOULDBLOCK". The downside of this style is that some arguments won't fit in the available space or the argument list will occupy quite a few lines if the arguments start too far to the right. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 22:30:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA00203 for freebsd-current-outgoing; Sun, 31 Jan 1999 22:30:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA00196 for ; Sun, 31 Jan 1999 22:30:08 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id WAA28055; Sun, 31 Jan 1999 22:29:15 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id WAA09960; Sun, 31 Jan 1999 22:29:13 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id WAA07789; Sun, 31 Jan 1999 22:29:11 -0800 (PST) From: Don Lewis Message-Id: <199902010629.WAA07789@salsa.gv.tsc.tdk.com> Date: Sun, 31 Jan 1999 22:29:11 -0800 In-Reply-To: Brian Somers "Re: btokup().. patch to STYLE(9) (fwd)" (Jan 29, 8:34am) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Brian Somers , Andrew Kenneth Milton Subject: Re: btokup().. patch to STYLE(9) (fwd) Cc: julian@whistle.com (Julian Elischer), mike@smith.net.au, dillon@apollo.backplane.com, archie@whistle.com, nate@mt.sri.com, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jan 29, 8:34am, Brian Somers wrote: } Subject: Re: btokup().. patch to STYLE(9) (fwd) } } My argument is that this sort of thing gets out of hand. I've seen } things such as } } if (((a == b) || (c == d))) } } where a, b, c & d are just simple variables - there are so many } redundant brackets that you have to double-check that there isn't } some weird grouping.... You can pretty clearly dump the outer parens, since it makes no sense to write "(expression)" instead of "expression". In general, "a OP b" should not be parenthesized if both "a" and "b" are atoms unless the context requires it. In general my preferred style doesn't use parentheses in expressions using "+-*/" according to their naturual precedence rules. I might drop the whitespace around "*", just like you'd write "2n" in mathematics. Likewise, I don't use parentheses in logical expressions or bitwise expressions where the terms are atoms. Expressions used as terms in logical expressions or comparision expressions might be parenthesized if they are complicated so I can find the extent of the expression by using '%' in vi. I always parenthesize the interfaces between bitwise and other expressions, since K&R admits that C botched the precedence of the bitwise operators and this seems to be one common place for bugs to occur. In general, I always parenthesize non-atomic arguments to the shift and ternary operators. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 22:37:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA00560 for freebsd-current-outgoing; Sun, 31 Jan 1999 22:37:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA00554 for ; Sun, 31 Jan 1999 22:37:02 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id WAA20572; Sun, 31 Jan 1999 22:35:58 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma020567; Sun, 31 Jan 99 22:35:52 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id WAA25806; Sun, 31 Jan 1999 22:35:52 -0800 (PST) From: Archie Cobbs Message-Id: <199902010635.WAA25806@bubba.whistle.com> Subject: Re: a nit, however.... In-Reply-To: from Brian Feldman at "Jan 31, 99 07:13:10 pm" To: green@unixhelp.org (Brian Feldman) Date: Sun, 31 Jan 1999 22:35:52 -0800 (PST) Cc: mo@servo.ccr.org, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman writes: > > any reason why the kernel "config" program shouldn't > > be changed to dramatically reduce the requirement for > > the silling quoting of option values??? if an option > > needs embedded whitespace, but other than that, > > is there any reason other than historical for > > the silliness about nubmers, etc?? > > Actually, as I understand it config(8) was never meant to allow the LACK > of quotation marks. It's simply we've grown accustomed to not using them, > I suppose, that we don't. I, for one, have every option quoted in my kernel > configuration file. The right thing would be to not allow lack of quotes > at all, I believe, but that would be disastrous now with current config > files, and release scripts. Why would that be the "right thing"? Seems to me that not requiring quotes would be more "right" with today's usage. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 22:52:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02126 for freebsd-current-outgoing; Sun, 31 Jan 1999 22:52:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02093; Sun, 31 Jan 1999 22:51:59 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id WAA20661; Sun, 31 Jan 1999 22:51:58 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma020659; Sun, 31 Jan 99 22:51:37 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id WAA25847; Sun, 31 Jan 1999 22:51:37 -0800 (PST) From: Archie Cobbs Message-Id: <199902010651.WAA25847@bubba.whistle.com> Subject: Re: Network/ARP problem? Maybe pn driver? In-Reply-To: <19990130104957.B660@dialup124.mi.uni-koeln.de> from Stefan Esser at "Jan 30, 99 10:49:57 am" To: se@FreeBSD.ORG Date: Sun, 31 Jan 1999 22:51:37 -0800 (PST) Cc: chris@netmonger.net, hardware@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stefan Esser writes: > You could have blocked reception of ARP requests / ARP replies in your IPFW > rules on one of the systems involved. Just try again with a completely open FYI- There's no way to block ARP packets with ipfw... it only deals with IP packets. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 31 22:56:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02461 for freebsd-current-outgoing; Sun, 31 Jan 1999 22:56:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA02452 for ; Sun, 31 Jan 1999 22:55:55 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id CAA02576; Mon, 1 Feb 1999 02:02:50 -0500 From: Bill Paul Message-Id: <199902010702.CAA02576@skynet.ctr.columbia.edu> Subject: Re: SIOCADDMULTI doesn't work, proposed fix To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Mon, 1 Feb 1999 02:02:48 -0500 (EST) Cc: current@FreeBSD.ORG In-Reply-To: <199902010458.XAA14745@khavrinen.lcs.mit.edu> from "Garrett Wollman" at Jan 31, 99 11:58:31 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Garrett Wollman had to walk into mine and say: > < said: > > > a struct sockaddr_dl will be used. However, the user is supposed to > > pass the address using a struct ifreq, and struct ifreq uses struct > > sockaddr, not struct sockaddr_dl. > > This is called ``poor man's inheritance''. > > I believe it is an error for any code to use AF_UNSPEC for any purpose > other than masks (where it makes sense since the address family is > normally not included in the mask). A `sockaddr_dl', while by default > longer than a `sockaddr', in this case will fit withing the structure > allotted. > > In the future, I fully expect that `sockaddr' will be of maximal > length (we need this for IPv6). There's still one small problem: the code as it stands now can return success and still not update the multicast filter. If you pass a structure with AF_LINK as the family but with the length set to 0, if_addmulti() falsely detects that the entry already matches an existing one and returns success (it the equal() macro equates to a bcmp(), which tries to compare 0 bytes worth of data and returns success). In my opinion, this is a bug: either the equal() macro should return false, or the zero length field should be detected by a sanity check and the function should return EINVAL. > > The patches included with this post change /sys/net/if.c and > > /sys/net/if_ethersubr.c so that adding a mutlicast address with > > SIOCADDMULTI using a struct sockaddr and AF_UNSPEC works again. I would > > like Those Who Know More Than I (tm) to review these changes and offer > > criticisms and comments. > > There are two things which should be done here. > > First, the kernel AppleTalk code should be fixed to join the necessary > multicast groups when an interface is first configured for AppleTalk. > (By preference the AARP implementation should be entirely in the > kernel as well, but that's more of a challenge.) Second, the generic > ether_resolvemulti function should be enhanced to know about AppleTalk > multicast addresses. The Columbia Appletalk code is not the same as netatalk: it's implemented entirely in user space and uses BPF as well as manually joining multicast groups. The existing Columbia Appletalk port, which works on 2.2.x, uses SIOCADDMULTI with a family of AF_UNSPEC. I rifled through a bunch of man pages in 3.0-RELEASE trying to find the Right Way To Do This (tm) but came up empty. If the right way to do this is to cast the struct sockaddr to a struct sockaddr_dl and use AF_LINK, then this should be documented somewhere. (If it is documented and I missed it, feel free to slap me around and point me in the right direction.) -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 00:19:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA11087 for freebsd-current-outgoing; Mon, 1 Feb 1999 00:19:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA11080; Mon, 1 Feb 1999 00:19:06 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id HAA19979; Mon, 1 Feb 1999 07:06:56 +0100 From: Luigi Rizzo Message-Id: <199902010606.HAA19979@labinfo.iet.unipi.it> Subject: Re: Network/ARP problem? Maybe pn driver? To: archie@whistle.com (Archie Cobbs) Date: Mon, 1 Feb 1999 07:06:56 +0100 (MET) Cc: se@FreeBSD.ORG, chris@netmonger.net, hardware@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199902010651.WAA25847@bubba.whistle.com> from "Archie Cobbs" at Jan 31, 99 10:51:18 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Stefan Esser writes: > > You could have blocked reception of ARP requests / ARP replies in your IPFW > > rules on one of the systems involved. Just try again with a completely open > > FYI- > There's no way to block ARP packets with ipfw... it only > deals with IP packets. er... if you use bridging and enable ipfw on bridged packets (net.link.ether.bridge_ipfw=1) then you can block non-ip packets if you don't use an open firewall. I don't think the original poster is in this situation that's why i did not spoke before. cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO . EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 00:21:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA11477 for freebsd-current-outgoing; Mon, 1 Feb 1999 00:21:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from coiib.es ([195.76.52.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA11322; Mon, 1 Feb 1999 00:20:34 -0800 (PST) (envelope-from janet9981@yahoo.com) From: janet9981@yahoo.com Received: from mirentxu.coiib.es by coiib.es (SMI-8.6/SMI-SVR4) id KAA03948; Mon, 1 Feb 1999 10:14:59 -0100 Message-Id: <199902011114.KAA03948@coiib.es> To: adsrtc@mtyisrot.com Date: Sun, 31 Jan 99 23:41:37 EST Subject: Maximize your website's traffic! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maximize your website's traffic. INCREASE YOUR SEARCH ENGINE RANK! If your Web site isn't getting the traffic it should, it's likely that it's not ranked well on the major Internet search engines. According to recent Internet E-commerce studies, over 90% of consumers find the Web sites they visit by using eight major search engines, which are Yahoo!, Excite, AltaVista, Infoseek, Lycos, Web Crawler, HotBot, and Northern Light. If your website isn't located in the top-30 listings of these engines, chances are your site will never be seen. The single most important thing you can do to increase your Web site's traffic is to increase your search engine ranking. ------------- "PUT YOUR NAME IN LIGHTS -- List your business with search engines to make sure potential customers can find it." -- BIZ Excite, PC Computing magazine, November 1998 ------------- THE BASICS: HOW SEARCH ENGINES RANK YOUR SITE When you submit your website to a search engine to be indexed in its database, it sends a "robot" to scan your page. Using complex algorithms to rank your page for keyword relevance, the "robot" determines whether you'll be ranked number 1 or 1,000,000 when potential visitors conduct a search looking for sites like yours. Because the search engines are constantly changing their algorithms to provide users with the best possible search results, there's only one true solution to high search engine placement--us. In short, submission alone isn't enough. *Good search engine ranking* is critical to your site's success. ------------- HERE'S WHAT WE DO -- A UNIQUE, SUCCESSFUL APPROACH In order to counter the ever-changing search engine algorithms, we create an entire series of "entry pages" that are optimized for the search engines--one for every keyword (or keyword phrase) that you provide. Each entry page is optimized for a different set of algorithm variables. In other words, instead of having only *one* page struggling to rank well on all engines, we create separate, search engine-specific entry pages for each keyword. As a result, your pages rank well because they contain information relevant to search queries that are related to your industry. ------------- HOW ENTRY PAGES AFFECT YOUR WEB SITE'S CURRENT STRUCTURE Put simply, they don't. When creating entry pages we *do not* make any changes to the existing structure, content, or functionality of your current site. The entry pages act as a welcome screen for your Web site when people enter from your highly ranked link on the search engine. The pages will say a few introductory words about your site, which are keyword and/or keyword phrase rich, and then provide a link that asks the visitor to "Click Here To Enter," which moves them directly to your current homepage. ------------ HERE'S WHAT WE DON'T *EVER* DO TO HELP YOUR SEARCH ENGINE RANK We *will not* build pages for irrelevant--yet "popular"--keywords. Also, we will *never* "spamdex" pages. "Spamdexing" is "stuffing" a Web page full of words for the search engine's robots. You may have seen spamdexing, which is placing many words in the same text color as a background onto a Web page. Spamdexing will actually get your pages "kicked" from search engine indexes. What we *will* do is simply present very relevant keywords for your site to the search engines in the way that they "like" to see it. ------------- "It's simple: If they can't find you on the search engines, they can't buy from you." -- J. LeRoss, Internet Sales Consultant ------------ HOW WELL DOES THE SERVICE WORK? We'll send you a detailed report of your current search engine ranking on "The Big Six" engines before we begin. Then, once your new entry pages have been indexed, we'll send you a second report showing how they've ranked. Here's a sampling of some results we've acheived for previous clients. (These examples are for competitive keywords--not just obscure words on which no one is conducting searches.) <> 6 top-10 rankings on Infoseek for different relevant keywords <> 18 top-10 rankings across the major search engines <> 3 top-10 rankings on Alta Vista for one keyword <> 16 total *number one* rankings <> 40 top-30 rankings, spread across the different engines. <> 1 to 2 hits per week increased to 500 per day <> 45,000 hits per month grew to 108,000. ------------ HOW MUCH DOES YOUR SERVICE COST? Our basic services start at only $385. The basic package includes: <> Construction of optimized entry pages for up to 20 keywords -- This gives you good "coverage" in your industry <> Submission of the keyword-dense entry pages to the "Big Six" search engines When you contact us, ask about other services we provide that may be able to help your Internet initiatives succeed. We have special services that can be tailored for your specific Internet marketing needs. ------------ HOW DO I GET STARTED? <> Call us--we'll answer any questions you may have and provide a no-cost initial consultation. (310) 859-4659 <> Submit your keywords and/or keyword phrases (up to 20) to us ------------ COMMENTS FROM CLIENTS "Frankly, I'm impressed with the foregoing. So many solicitations from email sources turn out to be a phone line that hooks up to a voice mail system that is designed to give the impression of size, and people who never return phone calls/messages. . . So its a pleasant surprise to find that someone at the other end is really operating as a business!!!" --Alan B. "Incredible! Our site is now receiving more hits in a day than we used to get in an entire month. [My boss] is still eating his words." -- Bob W. "I knew the search engines were a fantastic marketing tool, but my company simply didn't have the time to devote to search engine placement. It has proven to be the best money we've ever spent on marketing." -- Shelley H. "I worked for weeks to get good search engine placement, but I could never crack the top 80 . . . my site was deserted. Within a month [after using your service], I'd had more hits than I'd had in the last year. I wouldn't believe it if it hadn't happened to me." -- Chris L. ------------ OUR JOB: INCREASE YOUR WEB SITE'S RANKING. We can't guarantee that better ranking will increase the number of visitors that "surf" to your Web site. Some highly-ranked websites still don't get much traffic--much depends on your particular industry and choice of keywords. However, high rankings, in most cases, do mean increased Web site traffic. And, we have never failed to increase a client's ranking. Ever. ------------ CONTACT A REPRESENTATIVE: Search Engine Success Group - Call us at: (310) 859-4659 ----------------------- If you've received this message in error--and are not interested in our services--please click reply or call, (888)-248-2236, and we'll remove you from our list. Maximize your website's traffic. INCREASE YOUR SEARCH ENGINE RANK! If your Web site isn't getting the traffic it should, it's likely that it's not ranked well on the major Internet search engines. According to recent Internet E-commerce studies, over 90% of consumers find the Web sites they visit by using eight major search engines, which are Yahoo!, Excite, AltaVista, Infoseek, Lycos, Web Crawler, HotBot, and Northern Light. If your website isn't located in the top-30 listings of these engines, chances are your site will never be seen. The single most important thing you can do to increase your Web site's traffic is to increase your search engine ranking. ------------- "PUT YOUR NAME IN LIGHTS -- List your business with search engines to make sure potential customers can find it." -- BIZ Excite, PC Computing magazine, November 1998 ------------- THE BASICS: HOW SEARCH ENGINES RANK YOUR SITE When you submit your website to a search engine to be indexed in its database, it sends a "robot" to scan your page. Using complex algorithms to rank your page for keyword relevance, the "robot" determines whether you'll be ranked number 1 or 1,000,000 when potential visitors conduct a search looking for sites like yours. Because the search engines are constantly changing their algorithms to provide users with the best possible search results, there's only one true solution to high search engine placement--us. In short, submission alone isn't enough. *Good search engine ranking* is critical to your site's success. ------------- HERE'S WHAT WE DO -- A UNIQUE, SUCCESSFUL APPROACH In order to counter the ever-changing search engine algorithms, we create an entire series of "entry pages" that are optimized for the search engines--one for every keyword (or keyword phrase) that you provide. Each entry page is optimized for a different set of algorithm variables. In other words, instead of having only *one* page struggling to rank well on all engines, we create separate, search engine-specific entry pages for each keyword. As a result, your pages rank well because they contain information relevant to search queries that are related to your industry. ------------- HOW ENTRY PAGES AFFECT YOUR WEB SITE'S CURRENT STRUCTURE Put simply, they don't. When creating entry pages we *do not* make any changes to the existing structure, content, or functionality of your current site. The entry pages act as a welcome screen for your Web site when people enter from your highly ranked link on the search engine. The pages will say a few introductory words about your site, which are keyword and/or keyword phrase rich, and then provide a link that asks the visitor to "Click Here To Enter," which moves them directly to your current homepage. ------------ HERE'S WHAT WE DON'T *EVER* DO TO HELP YOUR SEARCH ENGINE RANK We *will not* build pages for irrelevant--yet "popular"--keywords. Also, we will *never* "spamdex" pages. "Spamdexing" is "stuffing" a Web page full of words for the search engine's robots. You may have seen spamdexing, which is placing many words in the same text color as a background onto a Web page. Spamdexing will actually get your pages "kicked" from search engine indexes. What we *will* do is simply present very relevant keywords for your site to the search engines in the way that they "like" to see it. ------------- "It's simple: If they can't find you on the search engines, they can't buy from you." -- J. LeRoss, Internet Sales Consultant ------------ HOW WELL DOES THE SERVICE WORK? We'll send you a detailed report of your current search engine ranking on "The Big Six" engines before we begin. Then, once your new entry pages have been indexed, we'll send you a second report showing how they've ranked. Here's a sampling of some results we've acheived for previous clients. (These examples are for competitive keywords--not just obscure words on which no one is conducting searches.) <> 6 top-10 rankings on Infoseek for different relevant keywords <> 18 top-10 rankings across the major search engines <> 3 top-10 rankings on Alta Vista for one keyword <> 16 total *number one* rankings <> 40 top-30 rankings, spread across the different engines. <> 1 to 2 hits per week increased to 500 per day <> 45,000 hits per month grew to 108,000. ------------ HOW MUCH DOES YOUR SERVICE COST? Our basic services start at only $385. The basic package includes: <> Construction of optimized entry pages for up to 20 keywords -- This gives you good "coverage" in your industry <> Submission of the keyword-dense entry pages to the "Big Six" search engines When you contact us, ask about other services we provide that may be able to help your Internet initiatives succeed. We have special services that can be tailored for your specific Internet marketing needs. ------------ HOW DO I GET STARTED? <> Call us--we'll answer any questions you may have and provide a no-cost initial consultation. (888) 283-2050 <> Submit your keywords and/or keyword phrases (up to 20) to us ------------ COMMENTS FROM CLIENTS "Frankly, I'm impressed with the foregoing. So many solicitations from email sources turn out to be a phone line that hooks up to a voice mail system that is designed to give the impression of size, and people who never return phone calls/messages. . . So its a pleasant surprise to find that someone at the other end is really operating as a business!!!" --Alan B. "Incredible! Our site is now receiving more hits in a day than we used to get in an entire month. [My boss] is still eating his words." -- Bob W. "I knew the search engines were a fantastic marketing tool, but my company simply didn't have the time to devote to search engine placement. It has proven to be the best money we've ever spent on marketing." -- Shelley H. "I worked for weeks to get good search engine placement, but I could never crack the top 80 . . . my site was deserted. Within a month [after using your service], I'd had more hits than I'd had in the last year. I wouldn't believe it if it hadn't happened to me." -- Chris L. ------------ OUR JOB: INCREASE YOUR WEB SITE'S RANKING. We can't guarantee that better ranking will increase the number of visitors that "surf" to your Web site. Some highly-ranked websites still don't get much traffic--much depends on your particular industry and choice of keywords. However, high rankings, in most cases, do mean increased Web site traffic. And, we have never failed to increase a client's ranking. Ever. ------------ CONTACT A REPRESENTATIVE: Search Engine Success Group - Call us at: (888) 283-2050 ----------------------- If you've received this message in error--and are not interested in our services--please click reply or call, (888)-248-2236, and we'll remove you from our list. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 00:37:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA13937 for freebsd-current-outgoing; Mon, 1 Feb 1999 00:37:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA13924 for ; Mon, 1 Feb 1999 00:37:54 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id AAA02272; Mon, 1 Feb 1999 00:37:52 -0800 (PST) (envelope-from dillon) Date: Mon, 1 Feb 1999 00:37:52 -0800 (PST) From: Matthew Dillon Message-Id: <199902010837.AAA02272@apollo.backplane.com> To: "Daniel C. Sobral" Cc: current@FreeBSD.ORG Subject: Re: vn and 4.0 References: <36B47C1B.C509042A@newsguy.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Is vn safe right now on -current? And does current's msdos fs :support fat-32? : :-- :Daniel C. Sobral (8-DCS) :dcs@newsguy.com With that most recent patch ( which I am just committing now ) ... maybe. In -4.x, the alternate B_PAGING path in vn.c's vnstrategy() code is used for VM faults as well as swap I/O. In -3.x that path was only used for swap I/O. It is possible that there are more bugs in this section of vn.c. I would say it is 'probably' ok, but it will take more people testing the vn device under -4.x to be able to say that it is safe. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 01:52:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23785 for freebsd-current-outgoing; Mon, 1 Feb 1999 01:52:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nhj.nlc.net.au (nhj.nlc.net.au [203.24.133.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA23780 for ; Mon, 1 Feb 1999 01:52:50 -0800 (PST) (envelope-from john.saunders@nlc.net.au) Received: (qmail 24006 invoked by uid 1000); 1 Feb 1999 20:52:45 +1100 Date: 1 Feb 1999 20:52:45 +1100 Message-ID: <19990201095245.24005.qmail@nhj.nlc.net.au> From: "John Saunders" To: freebsd-current@FreeBSD.ORG Cc: Dan Swartzendruber Subject: Re: btokup().. patch to STYLE(9) (fwd) X-Newsgroups: nlc.lists.freebsd-current In-Reply-To: <3.0.5.32.19990131201731.009da5f0@mail.kersur.net> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (Linux/2.0.36 (i686)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In nlc.lists.freebsd-current you wrote: > At 12:09 PM 2/1/99 +1100, Gregory Bond wrote: >>> "You are not supposed to understand this." "You are not expected to understand this." >>It was (IIRC) the process switching magic at the heart of fork() in V7 (and >>earlier, I assume). > If I remember right, it referred to the non-local goto juju where if the > forked processed was swapped out, the label jumped was changed to yet > another place. Unfortunately, my annotated V6 listing is not accessible > right now... It's inside the swtch() function call. Just having a quick look now. Inside expand(), where core is allocated for a process, if no core is available the process is swapped out with a call to xswap(), then switched out with a call to swtch(). When core becomes available and the process image is read in from swap, the process will be selected by swtch() to become runnable. However with the current context, swtch() would return and the tail end of the expand() function would execute. So inside expand() a call is made to save the stack state so that when swtch() restores this state, the return skips over the expand() function entirely. Cheers. -- +------------------------------------------------------------+ . | John Saunders - mailto:john@nlc.net.au (EMail) | ,--_|\ | - http://www.nlc.net.au/ (WWW) | / Oz \ | - 02-9489-4932 or 041-822-3814 (Phone) | \_,--\_/ | NHJ NORTHLINK COMMUNICATIONS - Supplying a professional, | v | and above all friendly, internet connection service. | +------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 02:08:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA25071 for freebsd-current-outgoing; Mon, 1 Feb 1999 02:08:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from titan.metropolitan.at ([195.212.98.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA25065 for ; Mon, 1 Feb 1999 02:08:31 -0800 (PST) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id <1CLHRB30>; Mon, 1 Feb 1999 11:10:36 +0100 Message-ID: <97A8CA5BF490D211A94F0000F6C2E55D09752A@s-lmh-wi-900.corpnet.at> From: Ladavac Marino To: "'John Saunders'" , freebsd-current@FreeBSD.ORG Cc: Dan Swartzendruber Subject: RE: btokup().. patch to STYLE(9) (fwd) Date: Mon, 1 Feb 1999 11:06:48 +0100 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: John Saunders [SMTP:john.saunders@nlc.net.au] > Sent: Monday, February 01, 1999 10:53 AM > To: freebsd-current@FreeBSD.ORG > Cc: Dan Swartzendruber > Subject: Re: btokup().. patch to STYLE(9) (fwd) > > In nlc.lists.freebsd-current you wrote: > > At 12:09 PM 2/1/99 +1100, Gregory Bond wrote: > >>> "You are not supposed to understand this." > > "You are not expected to understand this." > > > It's inside the swtch() function call. Just having a quick look now. > > Inside expand(), where core is allocated for a process, if no core is > available the process is swapped out with a call to xswap(), then > switched out with a call to swtch(). When core becomes available and > the process image is read in from swap, the process will be selected > by swtch() to become runnable. However with the current context, > swtch() > would return and the tail end of the expand() function would execute. > So inside expand() a call is made to save the stack state so that when > swtch() restores this state, the return skips over the expand() > function > entirely. > [ML] I don't understand that. But, then again, I am not supposed to :) P.S I did understand it, but it was too good an opportunitiy to miss. /Marino To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 03:46:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA05714 for freebsd-current-outgoing; Mon, 1 Feb 1999 03:46:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA05704 for ; Mon, 1 Feb 1999 03:46:55 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id UAA02848; Mon, 1 Feb 1999 20:46:12 +0900 (JST) Message-ID: <36B52198.40908ABC@newsguy.com> Date: Mon, 01 Feb 1999 12:38:00 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Santiago Perez-Cacho Jr." CC: current@FreeBSD.ORG Subject: Re: Can't boot from 1st disk on 2nd IDE controller References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Santiago Perez-Cacho Jr." wrote: > > changing root device to wd1s1a > ^^^^^^ > changing root device to wd1a > ^^^^ > error 6: panic : cannot mount root (2) > > It doesn't matter what I set as num_ide_disks and rootdev, the system > always tries to mount partitions on wd1. Is this a known issue or am I > doing something wrong? Someone here had the same problem, and modified the source code to deal with it. The easiest solution is simply to use wd1. Instead of configuring your second IDE as wd2, configure it as wd1. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com She just looked at him over the rotating pencil like, how slow can a mammal be and still have respiratory functions? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 05:31:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA20632 for freebsd-current-outgoing; Mon, 1 Feb 1999 05:31:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.238.120.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA20612 for ; Mon, 1 Feb 1999 05:31:24 -0800 (PST) (envelope-from paulo@nlink.com.br) Received: from localhost (paulo@localhost) by mirage.nlink.com.br (8.9.1a/8.9.1) with SMTP id KAA07417; Mon, 1 Feb 1999 10:30:52 -0300 (EST) Date: Mon, 1 Feb 1999 10:30:52 -0300 (EST) From: Paulo Fragoso To: "Richard Seaman, Jr." cc: freebsd-current@FreeBSD.ORG Subject: Re: LINUX clone? sched_yield? In-Reply-To: <19990130140620.A29670@tar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Sat, 30 Jan 1999, Richard Seaman, Jr. wrote: > You need to: > > 1) Upgrade your source tree to Jan 28 or later for 3.X or Jan 26 > or later for 4.0 current, and "make world" and config and remake > and install a new kernel, > That's ok now :-). Thanks, Paulo. ------ " ... Overall we've found FreeBSD to excel in performace, stability, technical support, and of course price. Two years after discovering FreeBSD, we have yet to find a reason why we switch to anything else" -David Filo, Yahoo! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 08:11:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09599 for freebsd-current-outgoing; Mon, 1 Feb 1999 08:11:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09594 for ; Mon, 1 Feb 1999 08:11:56 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id LAA16234; Mon, 1 Feb 1999 11:11:47 -0500 (EST) (envelope-from wollman) Date: Mon, 1 Feb 1999 11:11:47 -0500 (EST) From: Garrett Wollman Message-Id: <199902011611.LAA16234@khavrinen.lcs.mit.edu> To: Bill Paul Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), current@FreeBSD.ORG Subject: Re: SIOCADDMULTI doesn't work, proposed fix In-Reply-To: <199902010702.CAA02576@skynet.ctr.columbia.edu> References: <199902010458.XAA14745@khavrinen.lcs.mit.edu> <199902010702.CAA02576@skynet.ctr.columbia.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > to compare 0 bytes worth of data and returns success). In my opinion, > this is a bug: either the equal() macro should return false, or the > zero length field should be detected by a sanity check and the function > should return EINVAL. OK, I'll agree that this is a bug. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 10:31:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25135 for freebsd-current-outgoing; Mon, 1 Feb 1999 10:31:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25118; Mon, 1 Feb 1999 10:31:12 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id KAA07335; Mon, 1 Feb 1999 10:30:57 -0800 (PST) (envelope-from dillon) Date: Mon, 1 Feb 1999 10:30:57 -0800 (PST) From: Matthew Dillon Message-Id: <199902011830.KAA07335@apollo.backplane.com> To: Bjoern Fischer Cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: nuts'n'bolts in vfs_bio References: <19990129094616.A555@frolic.no-support.loc> <199901290923.BAA75985@apollo.backplane.com> <19990129211554.A349@broccoli.no-support.loc> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hello Matthew, : :thank you for reviewing vfs_bio.c. Your patch seems to :solve the problem with NFS writes remaining uncommitted. :At the time I can't see any NFS related data corruption. : :But when shutting down the server it still panics complaining :about dirty bufs. (happens in 9 out of 10 times). : : Bjoern I haven't been able to reproduce this one yet. I can see how there might be dirty buffers on the client, but there shouldn't be dirty buffers on the server. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 10:55:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28218 for freebsd-current-outgoing; Mon, 1 Feb 1999 10:55:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28205; Mon, 1 Feb 1999 10:55:21 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id KAA13162; Mon, 1 Feb 1999 10:54:47 -0800 Date: Mon, 1 Feb 1999 10:54:47 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Matthew Dillon cc: Bjoern Fischer , freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: nuts'n'bolts in vfs_bio In-Reply-To: <199902011830.KAA07335@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've seen this for a non-NFS case. On Mon, 1 Feb 1999, Matthew Dillon wrote: > > :Hello Matthew, > : > :thank you for reviewing vfs_bio.c. Your patch seems to > :solve the problem with NFS writes remaining uncommitted. > :At the time I can't see any NFS related data corruption. > : > :But when shutting down the server it still panics complaining > :about dirty bufs. (happens in 9 out of 10 times). > : > : Bjoern > > I haven't been able to reproduce this one yet. I can see how there > might be dirty buffers on the client, but there shouldn't be dirty buffers > on the server. > > -Matt > Matthew Dillon > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 11:31:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04078 for freebsd-current-outgoing; Mon, 1 Feb 1999 11:31:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04061 for ; Mon, 1 Feb 1999 11:31:12 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.152]) by smtp03.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA2C87; Mon, 1 Feb 1999 20:31:10 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 01 Feb 1999 20:40:01 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Tim Preece Subject: RE: Kernel wont compile Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 31-Jan-99 Tim Preece wrote: > In file included from ../../sys/types.h:48, > from ../../sys/param.h:56, > from ../../i386/i386/genassym.c:45: > ../../sys/inttypes.h:11: parse error before `int8_t' > ../../sys/inttypes.h:11: warning: data definition has no type or storage > class Parse error? Mmmm, I believe I once had such a problem which I fixed by first rebuilding lex and yacc. Try it and let us know =) --- Jeroen Ruigrok van der Werven It's a Dance of Energy, asmodai(at)wxs.nl when the Mind goes Binary... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 11:39:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05505 for freebsd-current-outgoing; Mon, 1 Feb 1999 11:39:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA05495 for ; Mon, 1 Feb 1999 11:39:38 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id SAA21495; Mon, 1 Feb 1999 18:30:40 +0100 From: Luigi Rizzo Message-Id: <199902011730.SAA21495@labinfo.iet.unipi.it> Subject: how to run a cvs server ? To: current@FreeBSD.ORG Date: Mon, 1 Feb 1999 18:30:40 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry if this is not 100% freebsd related... i wonder what should i use to run a local cvs server (to understand, something i can access setting CVSROOT=:pserver:user@host:/pathname) i haven't found anything obvious with man -k cvs or man -k pserver... thanks luigi -----------------------------------+------------------------------------- Luigi RIZZO . EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 11:51:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06729 for freebsd-current-outgoing; Mon, 1 Feb 1999 11:51:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.symmetron.com (mail.symmetron.com [206.239.186.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06716 for ; Mon, 1 Feb 1999 11:51:00 -0800 (PST) (envelope-from FreeBSD.lists@symmetron.com) Received: from mail (mail.symmetron.com [127.0.0.1]) by mail.symmetron.com (Netscape Mail Server v2.02) with SMTP id AAA314; Mon, 1 Feb 1999 14:57:23 -0500 Reply-To: From: FreeBSD.lists@symmetron.com (Symmetron's FreeBSD Mailing Lists) To: "Luigi Rizzo" , Subject: RE: how to run a cvs server ? Date: Mon, 1 Feb 1999 14:57:23 -0500 Keywords: FreeBSDemail Message-ID: <000601be4e1d$15a97dc0$02baefce@mail.symmetron.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: <199902011730.SAA21495@labinfo.iet.unipi.it> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG check out http://www.cyclic.com/ (makers of CVS) or my favorite cvs manual at: http://www.loria.fr/~molli/cvs/doc/cvs_toc.html The section of the online manual that talks about how to set up a pserver is at: http://www.loria.fr/~molli/cvs/doc/cvs_2.html#SEC30 -john -----Original Message----- From: owner-freebsd-current@FreeBSD.ORG [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Luigi Rizzo Sent: Monday, February 01, 1999 12:31 PM To: current@FreeBSD.ORG Subject: how to run a cvs server ? Sorry if this is not 100% freebsd related... i wonder what should i use to run a local cvs server (to understand, something i can access setting CVSROOT=:pserver:user@host:/pathname) i haven't found anything obvious with man -k cvs or man -k pserver... thanks luigi -----------------------------------+------------------------------------- Luigi RIZZO . EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 12:11:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09993 for freebsd-current-outgoing; Mon, 1 Feb 1999 12:11:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09975 for ; Mon, 1 Feb 1999 12:11:24 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40330>; Tue, 2 Feb 1999 07:01:21 +1100 Date: Tue, 2 Feb 1999 07:11:06 +1100 From: Peter Jeremy Subject: Re: btokup().. patch to STYLE(9) (fwd) To: current@FreeBSD.ORG Message-Id: <99Feb2.070121est.40330@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Someone wrote: > "You are not supposed to understand this." I'd suggest that there's a vast difference in the intended audience of the code containing the above comment and FreeBSD. Not to mention a 20+ year gap in time. Whilst the official codebase may be under the control of a select group of committers, the code should be capable of being understood by anyone who is reasonably proficient with C. If understanding the kernel requires that you be a guru-level expert in C, then people won't bother. FreeBSD will wind up being a small collection of people trying to outdo each other in obtuseness. Whenever someone suggests adding something new, there's usually a chorus of `where are the patches'. People can't write patches if they can't understand the code they want to modify. BTW, anyone looking further afield from the above comment might notice code like: register *foo; foo = u.u_area; foo->p_xyzzy =+ n; There aren't may C compilers left that can handle this sort of code... Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 12:25:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11211 for freebsd-current-outgoing; Mon, 1 Feb 1999 12:25:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11206 for ; Mon, 1 Feb 1999 12:25:06 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40330>; Tue, 2 Feb 1999 07:15:09 +1100 Date: Tue, 2 Feb 1999 07:24:55 +1100 From: Peter Jeremy Subject: Re: Can't boot from 1st disk on 2nd IDE controller To: "Santiago Perez-Cacho Jr." Cc: current@FreeBSD.ORG, dcs@newsguy.com Message-Id: <99Feb2.071509est.40330@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" wrote: >"Santiago Perez-Cacho Jr." wrote: >> >> changing root device to wd1s1a >> ^^^^^^ >> changing root device to wd1a >> ^^^^ >> error 6: panic : cannot mount root (2) >> >> It doesn't matter what I set as num_ide_disks and rootdev, the system >> always tries to mount partitions on wd1. Is this a known issue or am I >> doing something wrong? It is a known problem and was discussed here last month. The issue is basically that BIOS uses a different algorithm to the kernel to count disks. For various reasons, it's not practical for the kernel to use the same algorithm as the BIOS. Someone (I think it's Mike Smith) is looking at a reasonably general kludge to resolve the problem. >Someone here had the same problem, and modified the source code to >deal with it. I wrote the following kludge. This treats an IDE disk number supplied by the BIOS as the Nth IDE disk found by the kernel probe. You'll have to read the original thread for reasons why this solution may not work in all cases. Index: i386/i386/autoconf.c =================================================================== RCS file: /home/CVSROOT/./src/sys/i386/i386/autoconf.c,v retrieving revision 1.110 diff -b -u -r1.110 autoconf.c --- autoconf.c 1998/10/26 07:05:34 1.110 +++ autoconf.c 1999/01/21 23:18:18 @@ -433,6 +433,10 @@ #define FDMAJOR 2 #define FDUNITSHIFT 6 +/* KLUDGE for bios handling of multiple devices */ +#define WDMAJOR 0 +int wd_mask = 0; /* mask of WD devices found during probe */ + /* * Attempt to find the device from which we were booted. * If we can do so, and not instructed not to do so, @@ -467,6 +471,18 @@ slice = COMPATIBILITY_SLICE; part = RAW_PART; mindev = unit << FDUNITSHIFT; + } else if (majdev == WDMAJOR) { + /* + * XXX kludge to handle holes in numbering + */ + for (part = 0, mindev = unit; part < 32 && mindev >= 0; part++) + if (wd_mask & (1 << part)) + mindev--; + if (mindev == -1) + unit = part - 1; + + part = B_PARTITION(bootdev); + mindev = dkmakeminor(unit, slice, part); } else { part = B_PARTITION(bootdev); mindev = dkmakeminor(unit, slice, part); Index: i386/isa/wd.c =================================================================== RCS file: /home/CVSROOT/./src/sys/i386/isa/wd.c,v retrieving revision 1.186 diff -b -u -r1.186 wd.c --- wd.c 1999/01/17 05:46:24 1.186 +++ wd.c 1999/01/21 23:18:18 @@ -223,6 +223,8 @@ static struct buf rwdbuf[NWD]; /* buffers for raw IO */ #endif +extern int wd_mask; /* This is a KLUDGE */ + static int wdprobe(struct isa_device *dvp); static int wdattach(struct isa_device *dvp); static void wdustart(struct disk *du); @@ -551,6 +553,8 @@ DEVSTAT_NO_ORDERED_TAGS, DEVSTAT_TYPE_DIRECT | DEVSTAT_TYPE_IF_IDE); + /* KLUDGE: mark drive as present */ + wd_mask |= 1 << lunit; } else { free(du, M_TEMP); wddrives[lunit] = NULL; Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 12:45:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13827 for freebsd-current-outgoing; Mon, 1 Feb 1999 12:45:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13820 for ; Mon, 1 Feb 1999 12:45:14 -0800 (PST) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.1/8.9.1) id PAA28495 for current@freebsd.org; Mon, 1 Feb 1999 15:41:20 -0500 (EST) (envelope-from mi) From: Mikhail Teterin Message-Id: <199902012041.PAA28495@misha.cisco.com> Subject: Re: btokup().. patch to STYLE(9) (fwd) In-Reply-To: <99Feb2.070121est.40330@border.alcanet.com.au> from Peter Jeremy at "Feb 2, 1999 07:11:06 am" To: current@FreeBSD.ORG Date: Mon, 1 Feb 1999 15:41:20 -0500 (EST) Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG =Whilst the official codebase may be under the control of a select =group of committers, the code should be capable of being understood by =anyone who is reasonably proficient with C. Depends on your definition of "reasonably", Mr. Special Counselor... That's what is being tirelessly debated for the last several days. -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 14:01:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23408 for freebsd-current-outgoing; Mon, 1 Feb 1999 14:01:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from PaLaDiN7.ml.org (PaLaDiN7.ml.org [208.132.240.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23403 for ; Mon, 1 Feb 1999 14:01:18 -0800 (PST) (envelope-from pal@PaLaDiN7.ml.org) Received: from localhost (localhost.my.domain [127.0.0.1]) by PaLaDiN7.ml.org (8.9.2/8.9.2) with ESMTP id RAA23412 for ; Mon, 1 Feb 1999 17:03:06 -0500 (EST) Date: Mon, 1 Feb 1999 17:03:04 -0500 (EST) From: pal To: freebsd-current@FreeBSD.ORG Subject: NAT Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Is there any limit for open NAT connections? If it is where it can be set/change? Thanks, -pal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 14:22:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25892 for freebsd-current-outgoing; Mon, 1 Feb 1999 14:22:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25807 for ; Mon, 1 Feb 1999 14:21:59 -0800 (PST) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.2/8.9.1) with ESMTP id BAA00707 for ; Tue, 2 Feb 1999 01:18:25 +0300 (MSK) (envelope-from osa@etrust.ru) Date: Tue, 2 Feb 1999 01:18:25 +0300 (MSK) From: oZZ!!! To: freebsd-current@FreeBSD.ORG Subject: Problems with SLIP under 4.0-current... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! % uname -a ......4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sun Jan 31 22:42:09 MSK 1999.... % ifconfig sl0 sl0: flags=c013 mtu 296 inet 195.2.84.116 --> 195.2.84.115 netmask 0xfffffff0 broadcast 195.2.84.115 i can't connect to my 195.2.84.115 FreeBSD box... Whats wrong? Rgdz, ïÓÏËÉÎ óĊÒÇĊÊ aka oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 14:30:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27183 for freebsd-current-outgoing; Mon, 1 Feb 1999 14:30:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cidaut4.eis.uva.es (cidaut4.eis.uva.es [157.88.142.104]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27177 for ; Mon, 1 Feb 1999 14:30:52 -0800 (PST) (envelope-from sanper@pcfa.es.eu.org) Received: (from uucp@localhost) by cidaut4.eis.uva.es (8.8.5/8.8.5) with UUCP id XAA12442; Mon, 1 Feb 1999 23:33:25 +0100 (CET) Received: from localhost (sanper@localhost) by ergopc.pcfa.es.eu.org (8.8.8/8.8.8) with SMTP id XAA01151; Mon, 1 Feb 1999 23:21:34 +0100 (CET) (envelope-from sanper@ergopc.pcfa.es.eu.org) Date: Mon, 1 Feb 1999 23:21:33 +0100 (CET) From: "Santiago Perez-Cacho Jr." Reply-To: "Santiago Perez-Cacho Jr." To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: Can't boot from 1st disk on 2nd IDE controller In-Reply-To: <199902010517.VAA10261@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 31 Jan 1999, Mike Smith wrote: > > set root_disk_unit=2 > That did it!!! FreeBSD 4.0-CURRENT is now happily running on the master disk of the second IDE controller. > > Hello!! > > I'm running 4.0-CURRENT cvsupped last Friday. I've tried to move my > > installation from a partition on the first disk of the first IDE > > controller to a new disk that I've placed as master of the second IDE > > controller. Everything looks fine until the system tries to mount the > > root partition and can't find it, so it panics. I've tried breaking the > > boot process and setting num_ide_disks and rootdev to no avail. > > > > Here is the dmesg and error messages: > > [snip] > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > Thanks to all that answered! --------------------- Santiago Perez-Cacho sanper@pcfa.es.eu.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 14:40:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28135 for freebsd-current-outgoing; Mon, 1 Feb 1999 14:40:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28120 for ; Mon, 1 Feb 1999 14:40:15 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.1/8.9.1) id OAA12444 for freebsd-current@freebsd.org; Mon, 1 Feb 1999 14:39:04 -0800 (PST) (envelope-from dhw) Date: Mon, 1 Feb 1999 14:39:04 -0800 (PST) From: David Wolfskill Message-Id: <199902012239.OAA12444@pau-amma.whistle.com> To: freebsd-current@FreeBSD.ORG Subject: Re: Even more interesting NFS problems.. In-Reply-To: <19990201142503.B50525@clear.co.nz> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Mon, 1 Feb 1999 14:25:03 +1300 >From: Joe Abley >Never had a problem with it. Just to confirm that amd is not hideously >broken beyond the point where _some_ people can use it just fine. Likewise, though nearly all of our NFS activity is among FreeBSD boxen. And we use NIS for the amd maps: pau-amma[1] grep amd /etc/rc.conf amd_enable="YES" # Run amd service with $amd_flags (or NO). amd_flags="-nr -k i386 -l syslog -x all" amd_map_program="ypcat -k amd.master" Such as pau-amma[2] ypcat -k amd.n * host!=${key};os==freebsd3;type:=host;fs:=${autodir}/${rhost}/root;opts:=vers=2,proto=udp,nosuid,grpid,soft,intr host!=${key};os!=freebsd3;type:=host;fs:=${autodir}/${rhost}/root;opts:=nfsv2,noconn,nosuid,grpid,soft,intr host==${key};type:=link;fs:=/ /defaults rhost:=${key} Urrgh... That's a little ugly. Reformatted: * host!=${key};os==freebsd3;type:=host;fs:=${autodir}/${rhost}/root;\ opts:=vers=2,proto=udp,nosuid,grpid,soft,intr host!=${key};os!=freebsd3;type:=host;fs:=${autodir}/${rhost}/root;\ opts:=nfsv2,noconn,nosuid,grpid,soft,intr host==${key};type:=link;fs:=/ /defaults rhost:=${key} Basically: if this is the host in question, don't even use NFS; let amd simulate a symlink. Otherwise, use the release-specific incantation to force the use of NFS V2/UDP. And "amd.n" is the map we use for the equivalent of the Sun automounter "/hosts" map. Putting the "release-specific incantation" stuff in there managed to shut am-util's whining about "nfsv2" up. And using the rel. 1.2 of contrib/amd/libamu/mount_fs.c made it quit spitting out silly messages about "noconn". (Yes, I also sent a copy of that patch to the am-utils maintainer.) david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 14:48:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29362 for freebsd-current-outgoing; Mon, 1 Feb 1999 14:48:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from crap.31337.net (node1484.a2000.nl [62.108.20.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29344 for ; Mon, 1 Feb 1999 14:48:29 -0800 (PST) (envelope-from alexlh@funk.org) Received: from p.funk.org (p.funk.org [194.109.86.229]) by crap.31337.net (8.9.1/8.9.1) with ESMTP id XAA28828 for ; Mon, 1 Feb 1999 23:10:45 GMT (envelope-from alexlh@funk.org) Received: from funk.org (localhost [127.0.0.1]) by p.funk.org (8.9.2/8.9.2) with ESMTP id XAA47591 for ; Mon, 1 Feb 1999 23:48:35 +0100 (CET) (envelope-from alexlh@funk.org) Message-ID: <36B62F43.AF3E6DAC@funk.org> Date: Mon, 01 Feb 1999 23:48:35 +0100 From: Alex Le Heux X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: 3c589 doesn't work? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Is there any reason why the 3c589 in my laptop stopped working after I upgraded it to -current? During boot it now only tells me: > Initializing PC-card drivers: ed Instead of 3.0-RELEASE, which says: > Initializing PC-card drivers: ed ep Any ideas? Alex -- Gezeur. Ik heb gewoon al lekker met mijn zoon achter de pjoeter gezeten en hem M$ Publisher uitgelegd. Hij vond het heel interessant. Marcel en Erin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 15:02:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA01234 for freebsd-current-outgoing; Mon, 1 Feb 1999 15:02:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA01220 for ; Mon, 1 Feb 1999 15:02:50 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA20244; Tue, 2 Feb 1999 09:32:47 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id JAA73667; Tue, 2 Feb 1999 09:32:46 +1030 (CST) Date: Tue, 2 Feb 1999 09:32:46 +1030 From: Greg Lehey To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Obutuse code (was: btokup().. patch to STYLE(9) (fwd)) Message-ID: <19990202093246.M71384@freebie.lemis.com> References: <99Feb2.070121est.40330@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <99Feb2.070121est.40330@border.alcanet.com.au>; from Peter Jeremy on Tue, Feb 02, 1999 at 07:11:06AM +1100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 2 February 1999 at 7:11:06 +1100, Peter Jeremy wrote: > > BTW, anyone looking further afield from the above comment might notice > code like: > > register *foo; > > foo = u.u_area; > foo->p_xyzzy =+ n; > > There aren't may C compilers left that can handle this sort of code... Ah, but there's better: #define PS 0177776 struct { int integ; }; sleep(chan, pri) { int s; register *rp; s = PS->integ; Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 15:03:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA01347 for freebsd-current-outgoing; Mon, 1 Feb 1999 15:03:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mnw.eas.slu.edu (mnw.eas.slu.edu [165.134.8.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA01342 for ; Mon, 1 Feb 1999 15:03:57 -0800 (PST) (envelope-from ejh@mnw.eas.slu.edu) Received: (from ejh@localhost) by mnw.eas.slu.edu (8.8.8/8.8.8) id RAA29987 for freebsd-current@freebsd.org; Mon, 1 Feb 1999 17:03:55 -0600 (CST) Date: Mon, 1 Feb 1999 17:03:55 -0600 (CST) From: Eric Haug Message-Id: <199902012303.RAA29987@mnw.eas.slu.edu> To: freebsd-current@FreeBSD.ORG Subject: Re: style 9 pet annoyance Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, You should run vi with set tabstop=3 and shiftwidth=3 and see what you think of the 4 spaces that are IMHO now making the code look really bad. I think that the spaces stuff should be eliminated in favor of only tabs. Yes, i just deal with it. eric haug Saint Louis Univ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 15:04:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA01502 for freebsd-current-outgoing; Mon, 1 Feb 1999 15:04:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA01454 for ; Mon, 1 Feb 1999 15:04:23 -0800 (PST) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.2/8.9.1) with ESMTP id CAA00525 for ; Tue, 2 Feb 1999 02:03:32 +0300 (MSK) (envelope-from osa@etrust.ru) Date: Tue, 2 Feb 1999 02:03:32 +0300 (MSK) From: oZZ!!! To: freebsd-current@FreeBSD.ORG Subject: Fix problems with SLIP under 4.0-current... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Here is a patch for SLIP under 4.0-current... After make it, i recompile kernel & SLIP work. --- if_sl.c Tue Feb 2 01:42:35 1999 +++ if_sl.c.orig Tue Feb 2 01:56:41 1999 @@ -222,8 +222,7 @@ #ifdef SLIP_IFF_OPTS SLIP_IFF_OPTS; #else -/* IFF_BROADCAST | IFF_POINTOPOINT | SC_AUTOCOMP | IFF_MULTICAST; */ - IFF_POINTOPOINT | SC_AUTOCOMP | IFF_MULTICAST; + IFF_BROADCAST | IFF_POINTOPOINT | SC_AUTOCOMP | IFF_MULTICAST; #endif sc->sc_if.if_type = IFT_SLIP; sc->sc_if.if_ioctl = slioctl; Plz fix it. Rgdz, Sergey A. Osokin osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 15:21:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03808 for freebsd-current-outgoing; Mon, 1 Feb 1999 15:21:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03797 for ; Mon, 1 Feb 1999 15:21:54 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA20358; Tue, 2 Feb 1999 09:51:51 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id JAA73865; Tue, 2 Feb 1999 09:51:50 +1030 (CST) Date: Tue, 2 Feb 1999 09:51:50 +1030 From: Greg Lehey To: Eric Haug Cc: freebsd-current@FreeBSD.ORG Subject: Re: style 9 pet annoyance Message-ID: <19990202095150.T71384@freebie.lemis.com> References: <199902012303.RAA29987@mnw.eas.slu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199902012303.RAA29987@mnw.eas.slu.edu>; from Eric Haug on Mon, Feb 01, 1999 at 05:03:55PM -0600 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 1 February 1999 at 17:03:55 -0600, Eric Haug wrote: > > Hi All, > You should run vi with set tabstop=3 and shiftwidth=3 > and see what you think of the 4 spaces that are IMHO > now making the code look really bad. If that's the case, maybe we shouldn't. > I think that the spaces stuff should be eliminated > in favor of only tabs. I don't think that will meet with general agreement. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 15:39:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA06319 for freebsd-current-outgoing; Mon, 1 Feb 1999 15:39:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from daytona.hkstar.com (daytona.hkstar.com [202.82.3.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06312 for ; Mon, 1 Feb 1999 15:39:31 -0800 (PST) (envelope-from c5666305@ursa.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by daytona.hkstar.com (8.9.1/8.9.1) with ESMTP id HAA13955 for ; Tue, 2 Feb 1999 07:40:06 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8+Sun/8.8.8) id HAA14024 for freebsd-current@freebsd.org; Tue, 2 Feb 1999 07:39:26 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199902012339.HAA14024@b1.hkstar.com> Subject: how to record audio from the casstte thru pci128 audio in To: freebsd-current@FreeBSD.ORG Date: Tue, 2 Feb 1999 07:39:25 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I would like to know if there exist some software which can allow the user to record the audio from the cassette through the pci128 audio in. If so, would you please show me yours steps. Thanks. Clarence To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 16:27:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12573 for freebsd-current-outgoing; Mon, 1 Feb 1999 16:27:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12568 for ; Mon, 1 Feb 1999 16:27:44 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id QAA27798; Mon, 1 Feb 1999 16:27:30 -0800 (PST) (envelope-from dillon) Date: Mon, 1 Feb 1999 16:27:30 -0800 (PST) From: Matthew Dillon Message-Id: <199902020027.QAA27798@apollo.backplane.com> To: oZZ!!! Cc: freebsd-current@FreeBSD.ORG Subject: Re: Fix problems with SLIP under 4.0-current... References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hello! :Here is a patch for SLIP under 4.0-current... :After make it, i recompile kernel & SLIP work. : :--- if_sl.c Tue Feb 2 01:42:35 1999 :+++ if_sl.c.orig Tue Feb 2 01:56:41 1999 :@@ -222,8 +222,7 @@ : #ifdef SLIP_IFF_OPTS : SLIP_IFF_OPTS; : #else :-/* IFF_BROADCAST | IFF_POINTOPOINT | SC_AUTOCOMP | IFF_MULTICAST; */ :- IFF_POINTOPOINT | SC_AUTOCOMP | IFF_MULTICAST; :+ IFF_BROADCAST | IFF_POINTOPOINT | SC_AUTOCOMP | IFF_MULTICAST; : #endif : :Plz fix it. : :Rgdz, :Sergey A. Osokin :osa@etrust.ru Ach. I forgot to restore the original IFF_ options when I added SLIP_IFF_OPTS. I am presuming that you actually mean 'remove IFF_BROADCAST from the default options'. I'll commit a fix. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 17:06:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16767 for freebsd-current-outgoing; Mon, 1 Feb 1999 17:06:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16761 for ; Mon, 1 Feb 1999 17:06:36 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id RAA23946 for ; Mon, 1 Feb 1999 17:05:02 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdo23935; Tue Feb 2 01:04:58 1999 Message-ID: <36B64F35.237C228A@whistle.com> Date: Mon, 01 Feb 1999 17:04:53 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: KLD confusion.. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Take the following scenario: compiled in: module A kldstat -v shows module 'A' kldload A damned thing succeeds. e.g. [phaser.whistle.com] 516 kldstat -v Id Refs Address Size Name 1 2 0xf0100000 1c8198 kernel.try Contains modules: Id Name 1 rootbus 2 netgraph [...] 2 1 0xf07f0000 4000 netgraph.ko Contains modules: Id Name 31 netgraph this is handleable by just not loading 'A' but what about the following: kldload 'B' where B is defined to have a dependency on 'A' and 'A' is already loaded.. A get's loaded again.. leading to REALLY strange behaviour if the kernel is talking to one copy of A and B is talking to the other. I saw a suggestion from Peter to do something to change this, but I didn't understand it at the time. Now I think I saw what he was talking about. can whatever he was suggesting be done? as it is I can't win.. If I don't declare a dependency between A and B then I need to have A compiled in for B to load, but if A is loaded instead of compiled, B can't find it. If I DO declare a dependency, then if I load B it will ALWAYS load A even if it's already compiled in. as a result, the only way I can make it work is if either both A and B are compiled in or A and B are both loaded. Unfortunatly, I have some node that need to be compiled in as the infrastructure is not quite ready for them to be loaded yet, (e.g. interrupt hooking etc.) so ALL ofthe nodes need to be compiled in. Effectively, this is the same as not having KLDs. If I can't use them, what good are they? I've had a look at the code, but I think this would be a 20 minute thing for the right person, rather than a 2 day thing for me... julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 17:20:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17785 for freebsd-current-outgoing; Mon, 1 Feb 1999 17:20:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17780 for ; Mon, 1 Feb 1999 17:20:20 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id UAA10186 for ; Mon, 1 Feb 1999 20:20:13 -0500 (EST) Date: Mon, 1 Feb 1999 20:20:13 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: current@FreeBSD.ORG Subject: swap_page_getswapspace failed (don't do stupid things with /dev/mem) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So, never do stupid things as root; that's always my moto. Well, so I did something stupid as root, but it wasn't inherrently *that* stupid, at least not stupid enough to require a hard boot :). Below is the source code for the beginnings of an audit daemon--all it does is disable auditing on its own process, then read from /dev/audit. My goal was simply to make sure that data was going back and forth via the device correctly. Except I decided to test that feature that overrides the device filename (normally /dev/audit). Instead, I chose /dev/mem. Don't do that (ouch). The machine began to churn -- ok, so the buffer expands as necessary without limit, which is something that will go away once I actually write the daemon. But it kept churning, and gradually I lost control of things--my keyboard, eventually my mouse, and eventually the system just hung. Retrying it after a hard boot (and let me tell you that the off switch did not work on my IBM 560E notebook for a few tries :), I tried again on the console. The system is reduced to an endlessly printed: swap_pager_getswapspace: failed from the kernel. And needless to say, it loops fairly tightly and we don't get much in the way of key-pressing. Clearly, this is not something you should do with /dev/mem, but how was I to know :). Perhaps someone could determine if there is a race condition/etc that allows this condition to be entered, and instead default to killing the process or something. My kernel code is a few days old on the 4.0-CURRENT branch. Source: auditd.c (just disable auditing stuff to make it compile). Invoke as auditd /dev/mem. /*- * Copyright (c) 1999 Robert Watson * All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * * THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * * $Id: $ */ /* * User-land audit daemon * Listens on /dev/audit reading out records, and dropping them into * /var/log/audit. * Disables its own auditing to prevent nasties. */ #include #include #include #include #include #include #include #include "auditd.h" void usage(void) { fprintf(stderr, "auditd [-d] [-f auditdevice]\n"); exit(-1); } void main(int argc, char *argv[]) { int i, fd, size, bufsize, not_daemon; char ch, *buf, *devfile=AUDIT_DEVICE; not_daemon = 0; while ((ch = getopt(argc, argv, "df:")) != -1) { switch(ch) { case 'd': not_daemon = 1; break; case 'f': devfile = optarg; break; default: /* warnx("unknown flag -%c ignored", optopt); */ usage(); } } buf = (char *) malloc(AUDIT_DEF_BUF_SIZE * sizeof(char)); if (!buf) { fprintf(stderr, "auditd: unable to malloc buffer\n"); exit(-1); } bufsize = AUDIT_DEF_BUF_SIZE; i = aud_switch(AUD_STATE_OFF); if (i == -1) { perror("auditd: aud_switch"); exit(-1); } fd = open(devfile, O_RDONLY); if (fd == -1) { perror("auditd: open: audit device"); exit(-1); } if (!not_daemon) { i = daemon(1, 1); if (i == -1) { perror("auditd: daemon"); exit(-1); } } while (1) { /* read the size of the next block */ i = read(fd, &size, sizeof(size)); if (i == sizeof(size)) { if (size > bufsize) { free(buf); bufsize = size; buf = NULL; while (buf == NULL) { buf = (char *) malloc(bufsize * sizeof(char)); } i = read(fd, buf, bufsize); fprintf(stderr, "got stuff (%d/%d)\n", i, bufsize); } } } } Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 18:06:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21807 for freebsd-current-outgoing; Mon, 1 Feb 1999 18:06:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21799 for ; Mon, 1 Feb 1999 18:06:11 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA03687; Mon, 1 Feb 1999 21:04:50 -0500 (EST) Date: Mon, 1 Feb 1999 21:04:50 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Greg Lehey cc: Eric Haug , freebsd-current@FreeBSD.ORG Subject: Re: style 9 pet annoyance In-Reply-To: <19990202095150.T71384@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 2 Feb 1999, Greg Lehey wrote: > On Monday, 1 February 1999 at 17:03:55 -0600, Eric Haug wrote: > > > > Hi All, > > You should run vi with set tabstop=3 and shiftwidth=3 > > and see what you think of the 4 spaces that are IMHO > > now making the code look really bad. > > If that's the case, maybe we shouldn't. Having 4 (not 3) spaces would be a better idea. Many people do this. > > > I think that the spaces stuff should be eliminated > > in favor of only tabs. > > I don't think that will meet with general agreement. I don't see why it shouldn't, except people like to be stuck in their ways. If everyone could just echo "set ts=4 sw=4" > .exrc, we wouldn't have these tab/space arguments. That's probably way too much to ask, of course. > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 19:08:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27369 for freebsd-current-outgoing; Mon, 1 Feb 1999 19:08:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27350 for ; Mon, 1 Feb 1999 19:07:58 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id WAA06200 for ; Mon, 1 Feb 1999 22:07:54 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA16314; Mon, 1 Feb 1999 22:07:54 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id WAA39720 for freebsd-current@freebsd.org; Mon, 1 Feb 1999 22:07:53 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199902020307.WAA39720@bb01f39.unx.sas.com> Subject: Make world failure in lpr.c To: freebsd-current@FreeBSD.ORG Date: Mon, 1 Feb 1999 22:07:53 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, 4.0-current sources current as of 9pm EST. Is anyone else seeing this problem? Version 1.28 (wollman) seems to have broken this... The relevant pieces being: +static char *Uflag; /* user name specified with -U flag */ + uflag = optarg; uflag = optarg; looks like it should be Uflag. Thanks, John ===> usr.sbin/lpr/lpr cc -nostdinc -O -pipe -I/usr/src/usr.sbin/lpr/lpr/../common_source -Wall -Wnested-externs -Wmissing-prototypes -Wno-unused -Wredundant-decls -Wstrict-prototypes -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/lpr/lpr/lpr.c /usr/src/usr.sbin/lpr/lpr/lpr.c: In function `main': /usr/src/usr.sbin/lpr/lpr/lpr.c:192: `uflag' undeclared (first use this function) /usr/src/usr.sbin/lpr/lpr/lpr.c:192: (Each undeclared identifier is reported only once /usr/src/usr.sbin/lpr/lpr/lpr.c:192: for each function it appears in.) *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 19:44:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01405 for freebsd-current-outgoing; Mon, 1 Feb 1999 19:44:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01400 for ; Mon, 1 Feb 1999 19:44:47 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id WAA09767 for ; Mon, 1 Feb 1999 22:44:45 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA19265; Mon, 1 Feb 1999 22:44:44 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id WAA39884 for freebsd-current@freebsd.org; Mon, 1 Feb 1999 22:44:44 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199902020344.WAA39884@bb01f39.unx.sas.com> Subject: lpr.c problem (never mind) To: freebsd-current@FreeBSD.ORG Date: Mon, 1 Feb 1999 22:44:44 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I see 1.29 (the fix) as of 10:30 EST... Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 19:49:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02182 for freebsd-current-outgoing; Mon, 1 Feb 1999 19:49:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cantor.boolean.net (cantor.boolean.net [209.133.111.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02175 for ; Mon, 1 Feb 1999 19:49:40 -0800 (PST) (envelope-from Kurt@OpenLDAP.Org) Received: from gypsy (localhost [127.0.0.1]) by cantor.boolean.net (8.9.1/8.9.1) with SMTP id DAA54841 for ; Tue, 2 Feb 1999 03:49:08 GMT (envelope-from Kurt@OpenLDAP.Org) Message-Id: <3.0.5.32.19990201194542.00992710@localhost> X-Sender: kurt@localhost (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 01 Feb 1999 19:45:42 -0800 To: current@FreeBSD.ORG From: "Kurt D. Zeilenga" Subject: 3.0-current(12/98) -> RELENG_3 problems Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had a hoard of problems upgrading a 3.0-current a.out system circa ~12/7/98 to RELENG_3. After CVSuping, running make aout-to-elf-build would complain about OBJFORMAT previously being set in /etc/make.conf (which I don't think it was) and suggested I override it. Setting OBJFORMAT to elf, the aout-to-elf would fail unable to find make. Setting OBJFORMAT to aout, cause a nasty warning about a.out not being supported. I tried a few combinations and could not get aout-to-elf to build. However, I was around this by: setenv OBJFORMAT aout setenv REALLY_WANT_DEPRECIATED_AOUT 1 make buildworld mergemaster make installworld reboot make upgrade Kurt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 20:19:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05369 for freebsd-current-outgoing; Mon, 1 Feb 1999 20:19:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05361 for ; Mon, 1 Feb 1999 20:19:45 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id UAA31702; Mon, 1 Feb 1999 20:19:32 -0800 (PST) (envelope-from dillon) Date: Mon, 1 Feb 1999 20:19:32 -0800 (PST) From: Matthew Dillon Message-Id: <199902020419.UAA31702@apollo.backplane.com> To: Robert Watson Cc: current@FreeBSD.ORG Subject: Re: swap_page_getswapspace failed (don't do stupid things with /dev/mem) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :So, never do stupid things as root; that's always my moto. Well, so I did :something stupid as root, but it wasn't inherrently *that* stupid, at :least not stupid enough to require a hard boot :). Below is the source :... :Except I decided to test that feature that overrides the device filename :(normally /dev/audit). Instead, I chose /dev/mem. Don't do that (ouch). :The machine began to churn -- ok, so the buffer expands as necessary :without limit, which is something that will go away once I actually write :... :swap_pager_getswapspace: failed : :from the kernel. And needless to say, it loops fairly tightly and we :... Uh. Mmmmmm...... Hmmmmmm :-) i = read(fd, &size, sizeof(size)); ... malloc(bufsize * sizeof(char)) i = read(fd, buf, bufsize); When you are reading /dev/mem, 'size' can turn out to be anything. You are then allocating 'size' bytes ( which could be some insane value ). Finally, you try to read() from /dev/mem into the buffer the same insane value. The system is almost certainly trying to kill this process, but it can't because the process is stuck in an uninterruptable system read() of an insane amount of data. I don't think there is anything to 'fix' here. The system is making the best of a bad situation. Perhaps, though, we could test for signal 9 within the insanely huge read() loops and pop out. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 20:26:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06048 for freebsd-current-outgoing; Mon, 1 Feb 1999 20:26:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA06041 for ; Mon, 1 Feb 1999 20:26:02 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id XAA11018; Mon, 1 Feb 1999 23:25:52 -0500 (EST) Date: Mon, 1 Feb 1999 23:25:52 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Matthew Dillon cc: current@FreeBSD.ORG Subject: Re: swap_page_getswapspace failed (don't do stupid things with /dev/mem) In-Reply-To: <199902020419.UAA31702@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 1 Feb 1999, Matthew Dillon wrote: > Uh. Mmmmmm...... Hmmmmmm :-) > > i = read(fd, &size, sizeof(size)); > ... malloc(bufsize * sizeof(char)) > i = read(fd, buf, bufsize); > > When you are reading /dev/mem, 'size' can turn out to be anything. > You are then allocating 'size' bytes ( which could be some insane > value ). Finally, you try to read() from /dev/mem into the buffer > the same insane value. > > The system is almost certainly trying to kill this process, but it > can't because the process is stuck in an uninterruptable system read() > of an insane amount of data. > > I don't think there is anything to 'fix' here. The system is making > the best of a bad situation. Perhaps, though, we could test for signal > 9 within the insanely huge read() loops and pop out. So this probably works for non-root users on files like /dev/zero that can produce as much data as you might be interested in, suggesting a fun denial of service attack for the bored and/or insane. Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 20:34:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07121 for freebsd-current-outgoing; Mon, 1 Feb 1999 20:34:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07115 for ; Mon, 1 Feb 1999 20:34:27 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id UAA31836; Mon, 1 Feb 1999 20:34:24 -0800 (PST) (envelope-from dillon) Date: Mon, 1 Feb 1999 20:34:24 -0800 (PST) From: Matthew Dillon Message-Id: <199902020434.UAA31836@apollo.backplane.com> To: Robert Watson Cc: current@FreeBSD.ORG Subject: Re: swap_page_getswapspace failed (don't do stupid things with /dev/mem) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :So this probably works for non-root users on files like /dev/zero that can :produce as much data as you might be interested in, suggesting a fun :denial of service attack for the bored and/or insane. : : Robert N Watson : :Carnegie Mellon University http://www.cmu.edu/ :TIS Labs at Network Associates, Inc. http://www.tis.com/ :SafePort Network Services http://www.safeport.com/ Presumably the datasize limit can be used restrict the size of the process. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 21:51:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15197 for freebsd-current-outgoing; Mon, 1 Feb 1999 21:51:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15183 for ; Mon, 1 Feb 1999 21:51:17 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id QAA07849; Tue, 2 Feb 1999 16:21:11 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA27488; Tue, 2 Feb 1999 16:20:40 +1030 Date: Tue, 2 Feb 1999 16:20:40 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Robert Watson Cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: swap_page_getswapspace failed (don't do stupid things with /dev/mem) In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 1 Feb 1999, Robert Watson wrote: > On Mon, 1 Feb 1999, Matthew Dillon wrote: > > > Uh. Mmmmmm...... Hmmmmmm :-) > > > > i = read(fd, &size, sizeof(size)); > > ... malloc(bufsize * sizeof(char)) > > i = read(fd, buf, bufsize); > > > > When you are reading /dev/mem, 'size' can turn out to be anything. > > You are then allocating 'size' bytes ( which could be some insane > > value ). Finally, you try to read() from /dev/mem into the buffer > > the same insane value. > > > > The system is almost certainly trying to kill this process, but it > > can't because the process is stuck in an uninterruptable system read() > > of an insane amount of data. > > > > I don't think there is anything to 'fix' here. The system is making > > the best of a bad situation. Perhaps, though, we could test for signal > > 9 within the insanely huge read() loops and pop out. > > So this probably works for non-root users on files like /dev/zero that can > produce as much data as you might be interested in, suggesting a fun > denial of service attack for the bored and/or insane. /dev/zero isn't too bad DoS-wise. /dev/urandom is much worse - this was raised a month or so ago (it's probably been one of those repeating problems people periodically notice but which hadn't ever been fixed). bde posted this to -security last week: >From bde@zeta.org.au Tue Feb 2 16:16:18 1999 Date: Wed, 27 Jan 1999 23:35:01 +1100 From: Bruce Evans To: security@freebsd.org Subject: Re: signal handling in urandom can cause lockup I finally "finished" my fix for this. The problem has very little to do with signal handling, at least under FreeBSD. It is a general problem with slow devices that can transfer large amounts of data without blocking. E.g., dd if=/dev/urandom of=/dev/null bs=10m count=1 runs at about 1MB per 3.8 seconds on a P5/133, so the read() syscall for 10MB spends about 38 seconds in the kernel without blocking. My fix blocks most i/o hog processes in uiomove() and associated functions if they would be rescheduled if they were running in user mode. Unfortunately, signals can't be handled at this level since it would be surprising if disk i/o could be aborted by a signal. My fix only checks for signals for /dev/urandom. I don't know of any other devices that need it. Bruce diff -c2 src/sys/alpha/include/cpu.h~ src/sys/alpha/include/cpu.h *** src/sys/alpha/include/cpu.h~ Wed Oct 7 21:32:44 1998 --- src/sys/alpha/include/cpu.h Tue Jan 26 00:14:30 1999 *************** *** 76,80 **** * or after the current trap/syscall if in system mode. */ ! #define need_resched() { want_resched = 1; aston(); } /* --- 76,82 ---- * or after the current trap/syscall if in system mode. */ ! #define need_resched() do { want_resched = 1; aston(); } while (0) ! ! #define resched_wanted() want_resched /* diff -c2 src/sys/i386/include/cpu.h~ src/sys/i386/include/cpu.h *** src/sys/i386/include/cpu.h~ Tue Sep 1 15:54:52 1998 --- src/sys/i386/include/cpu.h Tue Jan 26 00:13:47 1999 *************** *** 84,88 **** * or after the current trap/syscall if in system mode. */ ! #define need_resched() { want_resched = 1; aston(); } /* --- 84,90 ---- * or after the current trap/syscall if in system mode. */ ! #define need_resched() do { want_resched = 1; aston(); } while (0) ! ! #define resched_wanted() want_resched /* diff -c2 src/sys/kern/kern_subr.c~ src/sys/kern/kern_subr.c *** src/sys/kern/kern_subr.c~ Mon Jan 11 03:15:05 1999 --- src/sys/kern/kern_subr.c Tue Jan 26 00:41:50 1999 *************** *** 45,48 **** --- 45,49 ---- #include #include + #include #include *************** *** 52,55 **** --- 53,60 ---- #include + #include + + static int uio_yield __P((void)); + int uiomove(cp, n, uio) *************** *** 82,85 **** --- 87,92 ---- case UIO_USERSPACE: case UIO_USERISPACE: + if (resched_wanted()) + uio_yield(); if (uio->uio_rw == UIO_READ) error = copyout(cp, iov->iov_base, cnt); *************** *** 140,143 **** --- 147,152 ---- case UIO_USERSPACE: case UIO_USERISPACE: + if (resched_wanted()) + uio_yield(); if (uio->uio_rw == UIO_READ) { if (vfs_ioopt && ((cnt & PAGE_MASK) == 0) && *************** *** 215,218 **** --- 224,229 ---- cnt &= ~PAGE_MASK; + if (resched_wanted()) + uio_yield(); error = vm_uiomove(&curproc->p_vmspace->vm_map, obj, uio->uio_offset, cnt, *************** *** 389,391 **** --- 400,417 ---- *nentries = hashsize; return (hashtbl); + } + + static int + uio_yield() + { + struct proc *p; + int s; + + p = curproc; + s = splhigh(); + setrunqueue(p); + p->p_stats->p_ru.ru_nivcsw++; + mi_switch(); + splx(s); + return (0); } diff -c2 src/sys/i386/i386/mem.c~ src/sys/i386/i386/mem.c *** src/sys/i386/i386/mem.c~ Mon Nov 9 16:34:49 1998 --- src/sys/i386/i386/mem.c Wed Jan 27 23:04:33 1999 *************** *** 60,63 **** --- 60,64 ---- #include #include + #include #include *************** *** 287,290 **** --- 288,301 ---- c = iov->iov_len; break; + } + if (CURSIG(curproc) != 0) { + /* + * Use tsleep() to get the error code right. + * It should return immediately. + */ + error = tsleep(&random_softc[0], + PZERO | PCATCH, "urand", 1); + if (error != 0 && error != EWOULDBLOCK) + continue; } if (buf == NULL) >From owner-freebsd-bugs@FreeBSD.ORG Thu Dec 31 13:12:07 1998 >Return-Path: >Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) > by godzilla.zeta.org.au (8.8.7/8.8.7) with SMTP id NAA23413 > for ; Thu, 31 Dec 1998 13:12:06 +1100 >Received: (qmail 7350 invoked from network); 31 Dec 1998 02:12:04 -0000 >Received: from hub.freebsd.org (204.216.27.18) > by gidora.zeta.org.au with SMTP; 31 Dec 1998 02:12:04 -0000 >Received: from localhost (daemon@localhost) > by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA02579; > Wed, 30 Dec 1998 17:56:31 -0800 (PST) > (envelope-from owner-freebsd-bugs) >Received: by hub.freebsd.org (bulk_mailer v1.6); Wed, 30 Dec 1998 17:56:17 -0800 >Received: (from majordom@localhost) > by hub.freebsd.org (8.8.8/8.8.8) id RAA02486 > for freebsd-bugs-outgoing; Wed, 30 Dec 1998 17:56:17 -0800 (PST) > (envelope-from owner-freebsd-bugs@FreeBSD.ORG) >Received: from ouch.Oof.NET (ouch.Oof.NET [208.212.72.34]) > by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA02481 > for ; Wed, 30 Dec 1998 17:56:13 -0800 (PST) > (envelope-from sdjames@research.poc.net) >Received: from localhost (sdj@localhost) > by ouch.Oof.NET (POC/Oof) with ESMTP id UAA17346; > Wed, 30 Dec 1998 20:55:14 -0500 (EST) >Date: Wed, 30 Dec 1998 20:55:14 -0500 (EST) >From: Steven Ji >To: freebsd-bugs@FreeBSD.ORG >Subject: signal handling in urandom can cause lockup >Message-ID: >MIME-Version: 1.0 >Content-Type: TEXT/PLAIN; charset=US-ASCII >Sender: owner-freebsd-bugs@FreeBSD.ORG >X-Loop: FreeBSD.org >Status: RO > >dd if=/dev/urandom of=/dev/null bs=100000k count=20000 > >I just tried this on -stable (12/2/98), and the machine seemed to >completely lock up. > >Box is a P6@200MHz x 2. > >---------- Forwarded message ---------- >Date: Sun, 27 Dec 1998 20:40:32 +0100 >From: Andrea Arcangeli >To: BUGTRAQ@netspace.org >Subject: [patch] fix for urandom read(2) not interruptible > >After having read phrak54 about Linux /dev/u?random (and this is the reason >I am CCing also to bugtraq ;), I was playing a bit >with the random driver it and I noticed that was difficult to kill `dd >if=/dev/urandom of=/dev/null bs=100000k count=20000' once started ;)). The >machine was eavily loaded and the process was unkillable and I the fastest >thing to restore the system is been a reset... > >It's a bug in random.c that doesn' t check for signal pending inside the >read(2) code, so you have no chance to kill the process via signals until >the read(2) syscall is finished, and it could take a lot of time before >return, if the buffer given to the read syscall is very big... > >Here the fix against 2.1.132: > >Index: linux/drivers/char/random.c >diff -u linux/drivers/char/random.c:1.1.1.1 linux/drivers/char/random.c:1.1.1.1.2.3 >--- linux/drivers/char/random.c:1.1.1.1 Fri Nov 20 00:02:25 1998 >+++ linux/drivers/char/random.c Sun Dec 27 20:19:16 1998 >@@ -232,6 +232,11 @@ > * Eastlake, Steve Crocker, and Jeff Schiller. > */ > >+/* >+ * Added a check for signal pending in the extract_entropy() loop to allow >+ * the read(2) syscall to be interrupted. Copyright (C) 1998 Andrea Arcangeli >+ */ >+ > #include > #include > #include >@@ -1269,7 +1274,14 @@ > buf += i; > add_timer_randomness(r, &extract_timer_state, nbytes); > if (to_user && current->need_resched) >+ { >+ if (signal_pending(current)) >+ { >+ ret = -EINTR; >+ break; >+ } > schedule(); >+ } > } > > /* Wipe data just returned from memory */ > > >And here a fix against 2.0.36: > >--- linux/drivers/char/random.c.orig Sun Dec 27 20:22:53 1998 >+++ linux/drivers/char/random.c Sun Dec 27 20:24:17 1998 >@@ -226,6 +226,11 @@ > * Eastlake, Steve Crocker, and Jeff Schiller. > */ > >+/* >+ * Added a check for signal pending in the extract_entropy() loop to allow >+ * the read(2) syscall to be interrupted. Copyright (C) 1998 Andrea Arcangeli >+ */ >+ > #include /* CONFIG_RST_COOKIES and CONFIG_SYN_COOKIES */ > #include > #include >@@ -1004,7 +1009,14 @@ > buf += i; > add_timer_randomness(r, &extract_timer_state, nbytes); > if (to_user && need_resched) >+ { >+ if (signal_pending(current)) >+ { >+ ret = -EINTR; >+ break; >+ } > schedule(); >+ } > } > > /* Wipe data from memory */ > >Andrea Arcangeli > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-bugs" in the body of the message > Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 23:22:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26497 for freebsd-current-outgoing; Mon, 1 Feb 1999 23:22:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news2.du.gtn.com (news2.du.gtn.com [194.77.9.57] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26485 for ; Mon, 1 Feb 1999 23:22:31 -0800 (PST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely.de [194.231.9.142]) by news2.du.gtn.com (8.8.6/8.8.6) with ESMTP id IAA17988 for ; Tue, 2 Feb 1999 08:22:12 +0100 (MET) Received: (from ticso@localhost) by cicely7.cicely.de (8.9.0/8.9.0) id IAA66577; Tue, 2 Feb 1999 08:22:20 +0100 (CET) Message-ID: <19990202082220.64600@cicely.de> Date: Tue, 2 Feb 1999 08:22:20 +0100 From: Bernd Walter To: freebsd-current@FreeBSD.ORG Subject: Dual console don't work Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I use -h -D in /boot.config Today I wanted to boot with monitor and keyboard. All I got was the first stage of the news boot loader on vga and seriel. The prompt itself goes only on seriel so there wasn't a chance to switch the console back to vga without a terminal. -- B.Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 1 23:47:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01180 for freebsd-current-outgoing; Mon, 1 Feb 1999 23:47:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01166 for ; Mon, 1 Feb 1999 23:46:56 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.11 #1) id 107aWC-000Mkm-00; Tue, 2 Feb 1999 09:45:08 +0200 From: Sheldon Hearn To: Luigi Rizzo cc: current@FreeBSD.ORG Subject: Re: how to run a cvs server ? In-reply-to: Your message of "Mon, 01 Feb 1999 18:30:40 +0100." <199902011730.SAA21495@labinfo.iet.unipi.it> Date: Tue, 02 Feb 1999 09:45:08 +0200 Message-ID: <87465.917941508@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 01 Feb 1999 18:30:40 +0100, Luigi Rizzo wrote: > i wonder what should i use to run a local cvs server (to understand, > something i can access setting CVSROOT=:pserver:user@host:/pathname) > > i haven't found anything obvious with man -k cvs or man -k pserver... Hi Luigi, There is a lot of documnetation available in the FreeBSD info distribution. The FreeBSD Handbook does make reference to the info files. Try ``info cvs'' at the shell prompt. For help on navigating the info system, try ``info info''. If you find info(1) difficult to use, try installing tkinfo from the ports tree or packages. Suggestions should obviously be typed without the quotes. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 01:16:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13756 for freebsd-current-outgoing; Tue, 2 Feb 1999 01:16:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-55-dbn.dial-up.net [196.34.155.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA13747 for ; Tue, 2 Feb 1999 01:16:19 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id LAA00389; Tue, 2 Feb 1999 11:15:12 +0200 (SAT) From: Robert Nordier Message-Id: <199902020915.LAA00389@ceia.nordier.com> Subject: Re: Dual console don't work In-Reply-To: <19990202082220.64600@cicely.de> from Bernd Walter at "Feb 2, 99 08:22:20 am" To: ticso@cicely.de (Bernd Walter) Date: Tue, 2 Feb 1999 11:15:09 +0200 (SAT) Cc: freebsd-current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bernd Walter wrote: > I use -h -D in /boot.config > Today I wanted to boot with monitor and keyboard. > All I got was the first stage of the news boot loader on vga and seriel. > The prompt itself goes only on seriel so there wasn't a chance to switch > the console back to vga without a terminal. This is deliberate, FWIW. The old bootblocks privately define RB_DUAL, and you won't find it in with the other flags like RB_SINGLE, RB_SERIAL, etc. For compatibility, the new bootblocks honor the -D option, as far as their own behavior goes. But they don't pass RB_DUAL, as one of the "howto" flags, on to either the kernel or /boot/loader. So -D is preserved only as a backward-compatibility option (and therefore applies only to stage two of the bootstrap), and /boot/loader knows nothing about it. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 01:32:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA15226 for freebsd-current-outgoing; Tue, 2 Feb 1999 01:32:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from titan.metropolitan.at ([195.212.98.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA15215 for ; Tue, 2 Feb 1999 01:32:27 -0800 (PST) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id <1CLHRCV9>; Tue, 2 Feb 1999 10:34:33 +0100 Message-ID: <97A8CA5BF490D211A94F0000F6C2E55D09752E@s-lmh-wi-900.corpnet.at> From: Ladavac Marino To: "'mi@aldan.algebra.com'" , current@FreeBSD.ORG Subject: RE: btokup().. patch to STYLE(9) (fwd) Date: Tue, 2 Feb 1999 10:30:43 +0100 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Mikhail Teterin [SMTP:mi@misha.cisco.com] > Sent: Monday, February 01, 1999 9:41 PM > To: current@FreeBSD.ORG > Subject: Re: btokup().. patch to STYLE(9) (fwd) > > =Whilst the official codebase may be under the control of a select > =group of committers, the code should be capable of being understood > by > =anyone who is reasonably proficient with C. > > Depends on your definition of "reasonably", Mr. Special Counselor... [ML] I see no cause for name calling. A "Reasonably Proficient" programmer is the one who writes correct code. The one who writes maintainable correct code is "Very Proficient". The one who writes well-documented maintainable correct code is a target for a marriage proposal :) Sadly, few proficient programmers program exclusively in C/C++. Most of us have bills to pay and switch on a drop of a hat from C to PL/I to COBOL to VisualBASIC to Perl to FORTRAN to YouNameIt to ... And, guess what, none of these languages have the same operator precedence as C/C++. But they all have parentheses. Knowledge of operator precedence as a metric of programming proficience--ludicrous. My brain would turn to pretzel if I had to know all the precedence rules in all the languages that I daily have to use. So, yes, I do use parentheses relying on assocciativity only around addition/multiplication. Logical expressions are handled differently in every language--some of them do not even have short-circuiting logical operators--thus, they will be parenthesized. An example that was being thrown around would look like this in my code: /* the reason for branching */ if ( (a * b - c * d) < (e / f) ) { true_part(); } else { false_part(); more_false_part(); } You will have noticed that I put braces around single statements. This has no performance penalty--a reasonable compiler will not create a stack frame--and helps in maintenance. /* copy null-terminated b to a */ for (pa = a, pb = b; (*pa = *pb) != 0; ++pa, ++pb) { /* NOTHING */ } Same thing here--okay, so it is a bit more verbose than absolutely neccessary. The advantage is that the people who are not absolutely acquainted with the syntactical finesse of the language *can* read it and can actually *modify* it without undue hassle. > That's what is being tirelessly debated for the last several days. > [ML] Hopefully we will come to agreement about a reasonable metric for programmer proficiency (and when I am at that, I can also hope for a jackpot in lottery :) /Marino > -mi > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 03:01:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA24648 for freebsd-current-outgoing; Tue, 2 Feb 1999 03:01:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ipt2.iptelecom.net.ua ([212.42.68.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA24639 for ; Tue, 2 Feb 1999 03:01:52 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega. ([212.42.68.146]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id NAA25082 for ; Tue, 2 Feb 1999 13:01:56 +0200 (EET) (envelope-from sobomax@altavista.net) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id NAA31978 for ; Tue, 2 Feb 1999 13:00:18 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <36B6DAC2.2567BA77@altavista.net> Date: Tue, 02 Feb 1999 13:00:18 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Misterious message... Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running recent 4.0 (updated today) and when booting have an message: lo0 XXX: driver didn't set ifq_maxlen Is it dangerous or not? Sincerely, Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 03:58:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA29841 for freebsd-current-outgoing; Tue, 2 Feb 1999 03:58:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bryggen.bgnett.no (bryggen.bgnett.no [194.54.96.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA29825 for ; Tue, 2 Feb 1999 03:58:30 -0800 (PST) (envelope-from erik@habatech.no) Received: from HABAWKS (4pogc-gw.online.no [194.248.199.142]) by bryggen.bgnett.no (8.8.8/8.8.5/brage2.1) with SMTP id LAA28547 for ; Tue, 2 Feb 1999 11:58:15 GMT Message-ID: <009501be4ea3$409e8940$8101a8c0@HABAWKS> From: "Erik H. Bakke" To: "FreeBSD Current" Subject: Re: Persistent files under /usr/obj Date: Tue, 2 Feb 1999 12:53:02 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.0707.2700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0707.2700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>do a >>chflags -R noschg /usr/obj >>before you rm it > >Uh no... do the 'rm' first, tolerate the few warnings, _then_ >do the chflags and then another 'rm'. > >It's faster on my stopwatch anyway :) > /* Flamebait mode on: */ Now, shouldn't we really have a target in our makefile for this, like: make REALLYCLEAN /* Flamebait mode off: */ Due to a harddisk crash I may not have received all the mails in this thread, and may therefore have missed someone else asking this question and getting a real good answer. --- Erik H. Bakke Habatech AS erik@habatech.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 05:12:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA12098 for freebsd-current-outgoing; Tue, 2 Feb 1999 05:12:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA12090 for ; Tue, 2 Feb 1999 05:12:15 -0800 (PST) (envelope-from fanf@demon.net) Received: by server.noc.demon.net; id NAA28224; Tue, 2 Feb 1999 13:12:12 GMT Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xmaa28195; Tue, 2 Feb 99 13:12:03 GMT Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 107fcY-0006IY-00; Tue, 2 Feb 1999 13:12:02 +0000 To: current@FreeBSD.ORG From: Tony Finch Subject: Re: btokup().. patch to STYLE(9) (fwd) In-Reply-To: <99Feb2.070121est.40330@border.alcanet.com.au> Message-Id: Date: Tue, 2 Feb 1999 13:12:02 +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy wrote: >Someone wrote: >> >> "You are not supposed to understand this." > >I'd suggest that there's a vast difference in the intended audience >of the code containing the above comment and FreeBSD. Not to mention >a 20+ year gap in time. > >Whilst the official codebase may be under the control of a select >group of committers, the code should be capable of being understood by >anyone who is reasonably proficient with C. If understanding the >kernel requires that you be a guru-level expert in C, then people >won't bother. FreeBSD will wind up being a small collection of >people trying to outdo each other in obtuseness. Don't be silly. FreeBSD is much more complicated than V6 for a whole lot of reasons that are independent of who gets to read the code and who gets to change it. Just as a starting point, the kernel has about a million lines of code compared to V6's ten thousand lines; Lions' comment about 10000 lines being a comfortable amount of code for one person to understand comes to mind. The x86 architecture is vastly more complicated and baroque than the PDP11. We now have paging and networking and SMP and a whole lot of other sophisticated stuff that were completely beyond V6. The magic of swtch() is written in assembler, not C. On the other hand, what we have that the early Unix community didn't have is the Internet. We can collaborate with email, we can browse the code history with CVS, and generally benefit from a far greater level of support. Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 05:19:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA13007 for freebsd-current-outgoing; Tue, 2 Feb 1999 05:19:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vision.vc3.com (vision.vc3.com [209.12.161.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA12899 for ; Tue, 2 Feb 1999 05:19:28 -0800 (PST) (envelope-from tatemj@vision.vc3.com) Received: from localhost (tatemj@localhost) by vision.vc3.com (8.9.1/8.9.1) with ESMTP id IAA02046; Tue, 2 Feb 1999 08:07:12 -0500 Date: Tue, 2 Feb 1999 08:07:12 -0500 (EST) From: Jason Tatem To: Alex Le Heux cc: freebsd-current@FreeBSD.ORG Subject: Re: 3c589 doesn't work? In-Reply-To: <36B62F43.AF3E6DAC@funk.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm using a 3c589C in a Fujitsu Lifebook 765dx, went from -release to -current about a week ago, no problem here. Aren't you supposed to use the zp driver for the 3c589 series? That's what I'm using at least. ----------------------------------------------------------------- Jason Tatem "What you want is irrelevant. VC3, Inc. What you have chosen is at hand!" tatemj@vc3.com --Spock, Star Trek VI ----------------------------------------------------------------- On Mon, 1 Feb 1999, Alex Le Heux wrote: > Hi, > > Is there any reason why the 3c589 in my laptop stopped working after I > upgraded it to -current? > > During boot it now only tells me: > > > Initializing PC-card drivers: ed > > Instead of 3.0-RELEASE, which says: > > > Initializing PC-card drivers: ed ep > > Any ideas? > > Alex > > -- > Gezeur. Ik heb gewoon al lekker met mijn zoon achter de pjoeter gezeten > en > hem M$ Publisher uitgelegd. Hij vond het heel interessant. > > Marcel en Erin > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 05:39:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA14499 for freebsd-current-outgoing; Tue, 2 Feb 1999 05:39:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.128.29.136]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA14485 for ; Tue, 2 Feb 1999 05:39:17 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id IAA20839; Tue, 2 Feb 1999 08:38:41 -0500 (EST) From: Mikhail Teterin Message-Id: <199902021338.IAA20839@kot.ne.mediaone.net> Subject: Re: btokup().. patch to STYLE(9) (fwd) In-Reply-To: <97A8CA5BF490D211A94F0000F6C2E55D09752E@s-lmh-wi-900.corpnet.at> from Ladavac Marino at "Feb 2, 1999 10:30:43 am" To: mladavac@metropolitan.at (Ladavac Marino) Date: Tue, 2 Feb 1999 08:38:41 -0500 (EST) Cc: current@FreeBSD.ORG X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" =Whilst the official codebase may be under the control of a select => =group of committers, the code should be capable of being understood => by => =anyone who is reasonably proficient with C. => => Depends on your definition of "reasonably", Mr. Special Counselor... = [ML] = I see no cause for name calling. I'm sorry, I did not mean "name calling". I was making a joke refering to the America's infamous senior public official talking to a certain Special Counsel (or Independent Counsel). = And, guess what, none of these languages have the same = operator precedence as C/C++. But they all have = parentheses. Knowledge of operator precedence as a = metric of programming proficience--ludicrous. My brain = would turn to pretzel if I had to know all the precedence = rules in all the languages that I daily have to use. I must admit, that this is the first reasonable argument I observe in a few days of this Battle of Giants. Mostly it looks like: -- I think, the code must be readable, therefore, we must allow for X. -- No, I think, the readability is very important, therefore X should be disallowed. = /* the reason for branching */ = if ( (a * b - c * d) < (e / f) ) { = true_part(); = } = else { = false_part(); = more_false_part(); = } = You will have noticed that I put braces around single = statements. This has no performance penalty--a reasonable = compiler will not create a stack frame--and helps in = maintenance. I'd say, I do not like this :) My first move is to remove the un-needed braces or put `else' onto the same line as the closing brace before it (I program in TCL a lot). But we all 've read enough of this already. The discussion is no longer interesting because of its subject, but rather because of its style. And this is a whole different branch of science... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 05:39:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA14520 for freebsd-current-outgoing; Tue, 2 Feb 1999 05:39:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA14487 for ; Tue, 2 Feb 1999 05:39:18 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id IAA15727 for ; Tue, 2 Feb 1999 08:39:16 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA16393; Tue, 2 Feb 1999 08:39:16 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id IAA48630 for freebsd-current@freebsd.org; Tue, 2 Feb 1999 08:39:15 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199902021339.IAA48630@bb01f39.unx.sas.com> Subject: make world failure (2 days in a row) To: freebsd-current@FreeBSD.ORG Date: Tue, 2 Feb 1999 08:39:15 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, The following says it all... Thanks, John ===> ru cd /usr/doc/ru ; make afterdistribute DESTDIR=/R/stage/trees/bin ===> ru/FAQ cd /usr/doc/ru/FAQ ; make install DESTDIR=/R/stage/trees/doc SHARED=copies install -c -o root -g wheel -m 444 FAQ*.html /R/stage/trees/doc/usr/share/doc/ru/FAQ if [ -f /usr/doc/ru/FAQ/FAQ.ln ]; then (cd /R/stage/trees/doc/usr/share/doc/ru/FAQ; sh /usr/doc/ru/FAQ/FAQ.ln); fi install -c -o root -g wheel -m 444 FAQ.roff /R/stage/trees/doc/usr/share/doc/ru/FAQ ===> zh cd /usr/doc/zh ; make afterdistribute DESTDIR=/R/stage/trees/bin ===> zh/FAQ cd /usr/doc/zh/FAQ ; make install DESTDIR=/R/stage/trees/doc SHARED=copies install -c -o root -g wheel -m 444 FAQ*.html /R/stage/trees/doc/FAQ usage: install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-g group] [-m mode] [-o owner] directory ... *** Error code 64 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 07:05:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA23559 for freebsd-current-outgoing; Tue, 2 Feb 1999 07:05:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from maild.telia.com (maild.telia.com [194.22.190.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA23548 for ; Tue, 2 Feb 1999 07:05:22 -0800 (PST) (envelope-from khaled@mailbox.telia.net) Received: from mailbox.telia.net (khaled@mailbox.telia.net [194.237.170.234]) by maild.telia.com (8.8.8/8.8.8) with ESMTP id QAA20669; Tue, 2 Feb 1999 16:05:15 +0100 (CET) Received: from localhost (khaled@localhost) by mailbox.telia.net (8.9.1/8.8.5) with SMTP id QAA28080; Tue, 2 Feb 1999 16:05:08 +0100 (CET) Date: Tue, 2 Feb 1999 16:05:08 +0100 (CET) From: Khaled Daham To: Jason Tatem cc: Alex Le Heux , freebsd-current@FreeBSD.ORG Subject: Re: 3c589 doesn't work? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 2 Feb 1999, Jason Tatem wrote: > I'm using a 3c589C in a Fujitsu Lifebook 765dx, went from -release to > -current about a week ago, no problem here. Aren't you supposed to use > the zp driver for the 3c589 series? That's what I'm using at least. pccard (compiled in the kernel, without zp) uses ep for 3c589 cards.. without pccard zp is used. And well my 3c589D works both ways. Though I could not get a 3c589B card working , but that was with 2.2.5 & PAO dont know if that card still doesnt work.. /Khaled, Telia Network Services Mail: khaled@telia.net Cell: 070-6785492 Work: 08-4567281 :hacker: /n./ [originally, someone who makes furniture with an axe] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 07:08:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA23804 for freebsd-current-outgoing; Tue, 2 Feb 1999 07:08:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oreo.adsu.bellsouth.com (host-209-214-72-80.atl.bellsouth.net [209.214.72.80]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA23796 for ; Tue, 2 Feb 1999 07:08:52 -0800 (PST) (envelope-from ck@oreo.adsu.bellsouth.com) Received: (from ck@localhost) by oreo.adsu.bellsouth.com (8.9.1/8.9.1) id KAA01368; Tue, 2 Feb 1999 10:08:02 -0500 (EST) (envelope-from ck) Date: Tue, 2 Feb 1999 10:08:00 -0500 From: Christian Kuhtz To: Jason Tatem Cc: Alex Le Heux , freebsd-current@FreeBSD.ORG Subject: Re: 3c589 doesn't work? Message-ID: <19990202100759.E298@oreo.adsu.bellsouth.com> References: <36B62F43.AF3E6DAC@funk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Jason Tatem on Tue, Feb 02, 1999 at 08:07:12AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, you should use the pccard driver. The zp doesn't support multicast and a couple of other things aren't as clean. Used to work fine over here, although I haven't tried it recently. Cheers, Chris On Tue, Feb 02, 1999 at 08:07:12AM -0500, Jason Tatem wrote: > I'm using a 3c589C in a Fujitsu Lifebook 765dx, went from -release to > -current about a week ago, no problem here. Aren't you supposed to use > the zp driver for the 3c589 series? That's what I'm using at least. -- "Be careful of reading health books, you might die of a misprint." -- Mark Twain [Disclaimer: I speak for myself and my views are my own and not in any way to be construed as the views of BellSouth Corporation. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 07:28:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26003 for freebsd-current-outgoing; Tue, 2 Feb 1999 07:28:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from agnes.stthom.edu ([209.184.165.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25992 for ; Tue, 2 Feb 1999 07:28:13 -0800 (PST) (envelope-from jim@agnes.stthom.edu) Received: from localhost (jim@localhost) by agnes.stthom.edu (8.7.6/8.7.3) with SMTP id JAA10567 for ; Tue, 2 Feb 1999 09:23:45 -0600 Date: Tue, 2 Feb 1999 09:23:44 -0600 (CST) From: "Jim C. Joseph" To: current@FreeBSD.ORG Subject: GUI for cdrecord Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG does anybody know of a decent GUI for cdrecord that works on -current? XCDRoast is pretty hardcoded for linux. ---------------------------------- Jim Joseph Email: jcj@phoenix.net The rule is, jam to-morrow and jam yesterday, but never jam today. -- Lewis Carroll To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 07:30:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26450 for freebsd-current-outgoing; Tue, 2 Feb 1999 07:30:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vision.vc3.com (vision.vc3.com [209.12.161.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26445 for ; Tue, 2 Feb 1999 07:30:47 -0800 (PST) (envelope-from tatemj@vision.vc3.com) Received: from localhost (tatemj@localhost) by vision.vc3.com (8.9.1/8.9.1) with ESMTP id KAA05419; Tue, 2 Feb 1999 10:29:46 -0500 Date: Tue, 2 Feb 1999 10:29:46 -0500 (EST) From: Jason Tatem To: Christian Kuhtz cc: Jason Tatem , Alex Le Heux , freebsd-current@FreeBSD.ORG Subject: Re: 3c589 doesn't work? In-Reply-To: <19990202100759.E298@oreo.adsu.bellsouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I loaded the generic pccard support + ep driver, and that works fine so far using -current from about middle of last week. ----------------------------------------------------------------- Jason Tatem "What you want is irrelevant. VC3, Inc. What you have chosen is at hand!" tatemj@vc3.com --Spock, Star Trek VI ----------------------------------------------------------------- On Tue, 2 Feb 1999, Christian Kuhtz wrote: > > Actually, you should use the pccard driver. The zp doesn't support multicast > and a couple of other things aren't as clean. > > Used to work fine over here, although I haven't tried it recently. > > Cheers, > Chris > > On Tue, Feb 02, 1999 at 08:07:12AM -0500, Jason Tatem wrote: > > I'm using a 3c589C in a Fujitsu Lifebook 765dx, went from -release to > > -current about a week ago, no problem here. Aren't you supposed to use > > the zp driver for the 3c589 series? That's what I'm using at least. > > -- > "Be careful of reading health books, you might die of a misprint." > -- Mark Twain > > [Disclaimer: I speak for myself and my views are my own and not in any way to > be construed as the views of BellSouth Corporation. ] > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 08:12:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00826 for freebsd-current-outgoing; Tue, 2 Feb 1999 08:12:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00818 for ; Tue, 2 Feb 1999 08:12:09 -0800 (PST) (envelope-from geoffb@gti.noc.demon.net) Received: by server.noc.demon.net; id QAA18724; Tue, 2 Feb 1999 16:12:03 GMT Received: from gti.noc.demon.net(195.11.55.101) by inside.noc.demon.net via smap (3.2) id xma018705; Tue, 2 Feb 99 16:11:48 GMT Received: (from geoffb@localhost) by gti.noc.demon.net (8.8.8/8.8.8) id QAA10337; Tue, 2 Feb 1999 16:11:45 GMT Message-ID: <19990202161144.C5815@gti.noc.demon.net> Date: Tue, 2 Feb 1999 16:11:45 +0000 From: Geoff Buckingham To: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: Scsi chatty'ness can be good.. Reply-To: Geoff Buckingham References: <199901311736.MAA00522@bb01f39.unx.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199901311736.MAA00522@bb01f39.unx.sas.com>; from John W. DeBoskey on Sun, Jan 31, 1999 at 12:36:40PM -0500 Organisation: Demon Internet Ltd Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hopefully this isn't becoming a democracy, but just in case, the verbose reporting is a valued feature here. -- Geoff Buckingham Demon Internet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 08:18:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01407 for freebsd-current-outgoing; Tue, 2 Feb 1999 08:16:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01398 for ; Tue, 2 Feb 1999 08:16:13 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id LAA00695; Tue, 2 Feb 1999 11:15:49 -0500 (EST) Date: Tue, 2 Feb 1999 11:15:48 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Matthew Dillon cc: Robert Watson , current@FreeBSD.ORG Subject: Re: swap_page_getswapspace failed (don't do stupid things with /dev/mem) In-Reply-To: <199902020419.UAA31702@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 1 Feb 1999, Matthew Dillon wrote: > :So, never do stupid things as root; that's always my moto. Well, so I did > :something stupid as root, but it wasn't inherrently *that* stupid, at > :least not stupid enough to require a hard boot :). Below is the source > :... > :Except I decided to test that feature that overrides the device filename > :(normally /dev/audit). Instead, I chose /dev/mem. Don't do that (ouch). > :The machine began to churn -- ok, so the buffer expands as necessary > :without limit, which is something that will go away once I actually write > :... > :swap_pager_getswapspace: failed > : > :from the kernel. And needless to say, it loops fairly tightly and we > :... > > Uh. Mmmmmm...... Hmmmmmm :-) > > i = read(fd, &size, sizeof(size)); > ... malloc(bufsize * sizeof(char)) > i = read(fd, buf, bufsize); > > When you are reading /dev/mem, 'size' can turn out to be anything. > You are then allocating 'size' bytes ( which could be some insane > value ). Finally, you try to read() from /dev/mem into the buffer > the same insane value. > > The system is almost certainly trying to kill this process, but it > can't because the process is stuck in an uninterruptable system read() > of an insane amount of data. > > I don't think there is anything to 'fix' here. The system is making > the best of a bad situation. Perhaps, though, we could test for signal > 9 within the insanely huge read() loops and pop out. I did a signal test inside /dev/urandom (probably yet to be committed, but Bruce said he was going to.) There's no reason we can't do one here, but we may have to break read()s of /dev/mem to smaller chunks to allow for this. Maybe there is a better way to break out of a running system call, and have it return immediately, but I haven't seen one. > > -Matt > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 08:39:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03638 for freebsd-current-outgoing; Tue, 2 Feb 1999 08:39:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03633 for ; Tue, 2 Feb 1999 08:39:09 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id LAA13781; Tue, 2 Feb 1999 11:39:01 -0500 (EST) Date: Tue, 2 Feb 1999 11:39:01 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Matthew Dillon cc: current@FreeBSD.ORG Subject: Re: swap_page_getswapspace failed (don't do stupid things with /dev/mem) In-Reply-To: <199902020434.UAA31836@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 1 Feb 1999, Matthew Dillon wrote: > :So this probably works for non-root users on files like /dev/zero that can > :produce as much data as you might be interested in, suggesting a fun > :denial of service attack for the bored and/or insane. > > Presumably the datasize limit can be used restrict the size > of the process. Matt, Does datasize limit the number of backed pages, or the amount of address space used by a process? I.e., can I grow myself a large chunk of address space using mmap to the same region of a file, and then read into that large chunk (presumably larger than the cache size if I want to be nasty)? If datasize only affects backed pages, then we can still do nasty large copies; if it affects address space, then nasty large copies are limited to the size of the writable address space (if using readv) or the size of the largest contiguous writable space (if using read). Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 09:06:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07042 for freebsd-current-outgoing; Tue, 2 Feb 1999 09:06:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07036 for ; Tue, 2 Feb 1999 09:06:43 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id JAA36791; Tue, 2 Feb 1999 09:06:37 -0800 (PST) (envelope-from dillon) Date: Tue, 2 Feb 1999 09:06:37 -0800 (PST) From: Matthew Dillon Message-Id: <199902021706.JAA36791@apollo.backplane.com> To: Robert Watson Cc: current@FreeBSD.ORG Subject: Re: swap_page_getswapspace failed (don't do stupid things with /dev/mem) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Matt, : :Does datasize limit the number of backed pages, or the amount of address :space used by a process? I.e., can I grow myself a large chunk of address :space using mmap to the same region of a file, and then read into that :large chunk (presumably larger than the cache size if I want to be nasty)? :If datasize only affects backed pages, then we can still do nasty large :copies; if it affects address space, then nasty large copies are limited :to the size of the writable address space (if using readv) or the size of :the largest contiguous writable space (if using read). : : Robert N Watson : :robert@fledge.watson.org http://www.watson.org/~robert/ :PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C The 'datasize' limit does not effect mmap(), only brk/sbrk. So, in fact, I believe you can bypass the datasize limit by allocating anonymous memory using mmap(). This is probably a bug. We should either limit the mmap()able space to about the same size as the data segment limit, or keep track of the amount of anonymous mapped memory and count that in the datasize limit. Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 09:13:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07717 for freebsd-current-outgoing; Tue, 2 Feb 1999 09:13:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07708 for ; Tue, 2 Feb 1999 09:13:03 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id JAA36862; Tue, 2 Feb 1999 09:12:40 -0800 (PST) (envelope-from dillon) Date: Tue, 2 Feb 1999 09:12:40 -0800 (PST) From: Matthew Dillon Message-Id: <199902021712.JAA36862@apollo.backplane.com> To: Robert Nordier Cc: ticso@cicely.de (Bernd Walter), freebsd-current@FreeBSD.ORG Subject: Re: Dual console don't work References: <199902020915.LAA00389@ceia.nordier.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Bernd Walter wrote: : :> I use -h -D in /boot.config :> Today I wanted to boot with monitor and keyboard. :> All I got was the first stage of the news boot loader on vga and seriel. :> The prompt itself goes only on seriel so there wasn't a chance to switch :> the console back to vga without a terminal. : :This is deliberate, FWIW. The old bootblocks privately define :RB_DUAL, and you won't find it in with the other :flags like RB_SINGLE, RB_SERIAL, etc. : :For compatibility, the new bootblocks honor the -D option, as far :as their own behavior goes. But they don't pass RB_DUAL, as one :of the "howto" flags, on to either the kernel or /boot/loader. : :So -D is preserved only as a backward-compatibility option (and :therefore applies only to stage two of the bootstrap), and /boot/loader :knows nothing about it. : :-- :Robert Nordier Is there a replacement for this functionality with the new bootloader? I was trying to get duel consoles working on a rack mount machine a week or two ago and met with utter failure. It was quite annoying. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 09:27:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09314 for freebsd-current-outgoing; Tue, 2 Feb 1999 09:27:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09307 for ; Tue, 2 Feb 1999 09:27:48 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.2/8.9.2) with ESMTP id RAA98587; Tue, 2 Feb 1999 17:27:13 GMT Message-ID: <36B73570.17B6E341@tdx.co.uk> Date: Tue, 02 Feb 1999 17:27:12 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Geoff Buckingham CC: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: Scsi chatty'ness can be good.. References: <199901311736.MAA00522@bb01f39.unx.sas.com> <19990202161144.C5815@gti.noc.demon.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Geoff Buckingham wrote: > Hopefully this isn't becoming a democracy, but just in case, the verbose > reporting is a valued feature here. I'm pretty sure it's never going to go... The worst that seems to be threatened is that it's made an option (which is fine by me, I'd leave it turned on... All the time )... I think one of the major advantages of *nix / linux is that it is so verbose... Maybe a new topic for -chat? -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 09:30:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09780 for freebsd-current-outgoing; Tue, 2 Feb 1999 09:30:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09769 for ; Tue, 2 Feb 1999 09:30:47 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id JAA18143; Tue, 2 Feb 1999 09:30:31 -0800 Date: Tue, 2 Feb 1999 09:30:31 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Karl Pielorz cc: freebsd-current@FreeBSD.ORG Subject: Re: Scsi chatty'ness can be good.. In-Reply-To: <36B73570.17B6E341@tdx.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I think one of the major advantages of *nix / linux is that it is so > verbose... Maybe a new topic for -chat? NT is just as verbose (when using the Checked build) if not more- you just don't see it because it's being dumped out a debug serial port. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 10:27:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15186 for freebsd-current-outgoing; Tue, 2 Feb 1999 10:27:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from genius.cirx.org (r00t.m1.ntu.edu.tw [140.112.240.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15181 for ; Tue, 2 Feb 1999 10:27:13 -0800 (PST) (envelope-from clkao@CirX.ORG) Received: (from clkao@localhost) by genius.cirx.org (8.9.2/8.9.1) id CAA00553; Wed, 3 Feb 1999 02:26:52 +0800 (CST) (envelope-from clkao@CirX.ORG) Date: Wed, 3 Feb 1999 02:26:52 +0800 (CST) Message-Id: <199902021826.CAA00553@genius.cirx.org> X-Authentication-Warning: genius.cirx.org: clkao set sender to clkao@CirX.ORG using -f From: Chia-liang Kao To: freebsd-current@FreeBSD.ORG Subject: problem with vr0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have problem with my newly bought D-link DFE530TX on my -current (which is very new). I have tested my NIC using the master/slave mode program came with my NIC with my room mate. And the results show the NIC work correctly. The most strange thing is that I can see the ethernet address of the other ip, see the following infomation. But I can't get the interface to work at all. Also, I tested replacing my de0 (which connects the outside world) with vr0. It doesn't work at all, but I can still get the ethernet address of other nodes shown in the routing table. Here are some output which might be useful to determine the problem. # dmesg | grep vr0 vr0: rev 0x06 int a irq 12 on pci0.19.0 vr0: Ethernet address: 00:80:c8:ef:82:09 vr0: autoneg complete, link status good (half-duplex, 10Mbps) vr0: selecting MII, 10Mbps, half duplex # ifconfig vr0 vr0: flags=8843 mtu 1500 inet 192.168.100.2 netmask 0xffffff00 broadcast 192.168.100.255 ether 00:80:c8:ef:82:09 media: 10baseT/UTP (10baseT/UTP ) supported media: autoselect 100baseTX 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 10baseT/UTP # netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 140.112.240.254 UGSc 10 0 de0 127.0.0.1 127.0.0.1 UH 1 120 lo0 140.112.240/24 link#1 UC 0 0 de0 140.112.240.59 0:80:c8:46:1e:d4 UHLW 5 1359 lo0 140.112.240.60 0:80:c8:69:96:3c UHLW 5 178 de0 1114 140.112.240.254 0:0:1d:ce:d3:7d UHLW 11 0 de0 839 140.112.240.255 ff:ff:ff:ff:ff:ff UHLWb 0 1 de0 192.168.100 link#2 UC 0 0 vr0 192.168.100.1 0:80:c8:ef:3c:3f UHLW 0 15 vr0 1158 ^^^^^^^^^^^^^^^^ 192.168.100.2 0:80:c8:ef:82:9 UHLW 0 3 lo0 192.168.100.255 ff:ff:ff:ff:ff:ff UHLWb 0 1 vr0 # ipfw list ipfw: getsockopt(IP_FW_GET): Protocol not available To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 10:29:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15384 for freebsd-current-outgoing; Tue, 2 Feb 1999 10:29:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-59-dbn.dial-up.net [196.34.155.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15362 for ; Tue, 2 Feb 1999 10:29:27 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id UAA04458; Tue, 2 Feb 1999 20:28:27 +0200 (SAT) From: Robert Nordier Message-Id: <199902021828.UAA04458@ceia.nordier.com> Subject: Re: Dual console don't work In-Reply-To: <199902021712.JAA36862@apollo.backplane.com> from Matthew Dillon at "Feb 2, 99 09:12:40 am" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Tue, 2 Feb 1999 20:28:24 +0200 (SAT) Cc: rnordier@nordier.com, ticso@cicely.de, freebsd-current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > :Bernd Walter wrote: > : > :> I use -h -D in /boot.config > :> Today I wanted to boot with monitor and keyboard. > :> All I got was the first stage of the news boot loader on vga and seriel. > :> The prompt itself goes only on seriel so there wasn't a chance to switch > :> the console back to vga without a terminal. > : > :This is deliberate, FWIW. The old bootblocks privately define > :RB_DUAL, and you won't find it in with the other > :flags like RB_SINGLE, RB_SERIAL, etc. > : > :For compatibility, the new bootblocks honor the -D option, as far > :as their own behavior goes. But they don't pass RB_DUAL, as one > :of the "howto" flags, on to either the kernel or /boot/loader. > : > :So -D is preserved only as a backward-compatibility option (and > :therefore applies only to stage two of the bootstrap), and /boot/loader > :knows nothing about it. > : > :-- > :Robert Nordier > > Is there a replacement for this functionality with the new bootloader? > I was trying to get duel consoles working on a rack mount machine a week > or two ago and met with utter failure. It was quite annoying. > Support for multiple consoles in /boot/loader is planned but not implemented yet. Mike should be able to put a timeframe on this. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 11:13:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19617 for freebsd-current-outgoing; Tue, 2 Feb 1999 11:13:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA19605 for ; Tue, 2 Feb 1999 11:13:30 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id OAA05271; Tue, 2 Feb 1999 14:20:13 -0500 From: Bill Paul Message-Id: <199902021920.OAA05271@skynet.ctr.columbia.edu> Subject: Re: problem with vr0 To: clkao@CirX.ORG (Chia-liang Kao) Date: Tue, 2 Feb 1999 14:20:11 -0500 (EST) Cc: current@FreeBSD.ORG In-Reply-To: <199902021826.CAA00553@genius.cirx.org> from "Chia-liang Kao" at Feb 3, 99 02:26:52 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Chia-liang Kao had to walk into mine and say: > > I have problem with my newly bought D-link DFE530TX on my -current > (which is very new). > > I have tested my NIC using the master/slave mode program came with my > NIC with my room mate. And the results show the NIC work correctly. > > The most strange thing is that I can see the ethernet address of the > other ip, see the following infomation. But I can't get the interface > to work at all. ARRRRGHHHH!!! I really don't want to get mad at you personally, but this is really starting to annoy me. Virtually every time anybody reports a problem, the only thing they ever say is "it doesn't work." WHAT DOESN'T WORK EXACTLY!?! Describe the problem(s)!! Show us examples!! Show us error messages!! Does it catch fire?! Does it spit pea soup at you and speak in tongues?! Does it lie around the house all day and refuse to cut its hair and get a job!? WHAT!! You have not explained exactly what is going wrong. You have not explained what it is that you're trying to do which isn't working. You have not explained how you came to the conclusion that the card "isn't working." Show us what happens if you type 'ping 192.168.100.1'. Don't attempt to paraphrase the error messages: quote them exactly. Does ping not illustrate the problem accurately? Fine: choose another example and show us the results. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 11:32:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21513 for freebsd-current-outgoing; Tue, 2 Feb 1999 11:32:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Vorlon.odc.net (Vorlon.odc.net [207.137.42.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21508 for ; Tue, 2 Feb 1999 11:32:52 -0800 (PST) (envelope-from nwestfal@Vorlon.odc.net) Received: from localhost (nwestfal@localhost) by Vorlon.odc.net (8.8.7/8.8.7) with ESMTP id LAA10036 for ; Tue, 2 Feb 1999 11:32:44 -0800 Date: Tue, 2 Feb 1999 11:32:44 -0800 (PST) From: Neal Westfall To: current@FreeBSD.ORG Subject: de0 XXX: driver didn't set ifq_maxlen Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just built a kernel from code cvsup'd last night. I get the following messages now during boot: de0 XXX: driver didn't set ifq_maxlen lo0 XXX: driver didn't set ifq_maxlen Everything otherwise seems to be working. Are these messages indicative of a problem? Thanks -- Neal Westfall mailto:nwestfal@odc.net http://www.odc.net/~nwestfal/ FreeBSD: The Power To Serve! http://www.freebsd.org/ $Id: dot.signature,v 1.2 1998/12/30 08:23:13 nwestfal Exp nwestfal $ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 11:42:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22461 for freebsd-current-outgoing; Tue, 2 Feb 1999 11:42:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22452 for ; Tue, 2 Feb 1999 11:42:14 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id UAA21563; Tue, 2 Feb 1999 20:40:57 +0100 (CET) To: Neal Westfall cc: current@FreeBSD.ORG Subject: Re: de0 XXX: driver didn't set ifq_maxlen In-reply-to: Your message of "Tue, 02 Feb 1999 11:32:44 PST." Date: Tue, 02 Feb 1999 20:40:54 +0100 Message-ID: <21561.917984454@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Neal Westf all writes: >Just built a kernel from code cvsup'd last night. I get the following >messages now during boot: > >de0 XXX: driver didn't set ifq_maxlen >lo0 XXX: driver didn't set ifq_maxlen > >Everything otherwise seems to be working. Are these messages >indicative of a problem? No, the "XXX:" in general means "Somebody should do something about this, but it is probably not a problem". The maintainers for the respective drivers will hopefully take notice and fix this buglet soon. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 11:43:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22812 for freebsd-current-outgoing; Tue, 2 Feb 1999 11:43:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from csla.csl.sri.com (csla.csl.sri.com [192.12.33.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22802 for ; Tue, 2 Feb 1999 11:43:51 -0800 (PST) (envelope-from gilham@csl.sri.com) Received: from csl.sri.com (snapdragon.csl.sri.com [130.107.18.20]) by csla.csl.sri.com (8.9.1/8.9.1) with ESMTP id LAA10324 for ; Tue, 2 Feb 1999 11:43:47 -0800 (PST) Message-Id: <199902021943.LAA10324@csla.csl.sri.com> To: current@FreeBSD.ORG Subject: Re: btokup().. patch to STYLE(9) (fwd) In-reply-to: Your message of "Thu, 28 Jan 1999 21:43:41 PST." Date: Tue, 02 Feb 1999 11:43:47 -0800 From: Fred Gilham Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer writes: > > Now if I'm working on some piece of code and feel that it could do with > some parens then surely KNF should be flexible enough to allow them.. > > I don't know how many bugs have ben revealed by adding parens and braces.. > I know that one of the first things I do when looking for a bug is add as > many as I can in parts of the code that are suspect. > > It's amazing how often it shows up the problem. > As someone who has made one (1) contribution to the FreeBSD kernel, I say, go ahead and use parentheses to your heart's content. My one contribution was a patch to the kernel and Linux emulator to allow the Linux version of Allegro Common Lisp 4.3 to run under FreeBSD. :-) :-) -Fred Gilham gilham@csl.sri.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 12:55:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01294 for freebsd-current-outgoing; Tue, 2 Feb 1999 12:55:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01279 for ; Tue, 2 Feb 1999 12:55:29 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id MAA28615; Tue, 2 Feb 1999 12:55:27 -0800 (PST) Date: Tue, 2 Feb 1999 12:55:30 -0800 (PST) From: Tom Bartol To: current@FreeBSD.ORG cc: Joel Stiles Subject: 4GB of RAM?! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Has anyone yet tried running -current on a Xeon with 4GB RAM installed? We're about to place an order for a Quad Xeon and would like to have 4GB of RAM installed if it is feasible and/or possible to make this work with -current. Thanks for the help, Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 13:16:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05129 for freebsd-current-outgoing; Tue, 2 Feb 1999 13:16:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.hq.tis.com (relay.hq.tis.com [192.94.214.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05122 for ; Tue, 2 Feb 1999 13:16:14 -0800 (PST) (envelope-from stevek@tis.com) Received: by relay.hq.tis.com; id QAA03580; Tue, 2 Feb 1999 16:23:42 -0500 (EST) Received: from clipper.hq.tis.com(10.33.1.2) by relay.hq.tis.com via smap (4.1) id xma003555; Tue, 2 Feb 99 16:22:49 -0500 Received: from mufasa.va.tis.com (mufasa.va.tis.com [192.168.10.18]) by clipper.hq.tis.com (8.9.1/8.9.1) with ESMTP id QAA14738 for ; Tue, 2 Feb 1999 16:13:41 -0500 (EST) Received: from localhost (stevek@localhost) by mufasa.va.tis.com (8.8.7/8.8.7) with SMTP id QAA10979 for ; Tue, 2 Feb 1999 16:25:06 -0500 (EST) (envelope-from stevek@mufasa.va.tis.com) Date: Tue, 2 Feb 1999 16:25:06 -0500 (EST) From: Steve Kiernan To: freebsd-current@FreeBSD.ORG Subject: New boot blocks not installed on 3.0-STABLE (02/01/1999 snap) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, I did an update install with 3.0-STABLE (the snap from yesterday), but the new boot blocks weren't installed, so the old boot loader keeps complaining that the kernel is the wrong format (obviously, bootloader, it's an ELF kernel). Any way to get the new boot blocks onto the drive from the kernel/mfs root disks or the fixit floppy? Thanks, Stephen Kiernan stevek@tis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 13:52:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09893 for freebsd-current-outgoing; Tue, 2 Feb 1999 13:52:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09884 for ; Tue, 2 Feb 1999 13:52:29 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA01122; Tue, 2 Feb 1999 13:46:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902022146.NAA01122@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Robert Nordier cc: dillon@apollo.backplane.com (Matthew Dillon), ticso@cicely.de, freebsd-current@FreeBSD.ORG Subject: Re: Dual console don't work In-reply-to: Your message of "Sat, 02 Feb 1999 20:28:24 +0200." <199902021828.UAA04458@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Feb 1999 13:46:32 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is there a replacement for this functionality with the new bootloader? > > I was trying to get duel consoles working on a rack mount machine a week > > or two ago and met with utter failure. It was quite annoying. > > > > Support for multiple consoles in /boot/loader is planned but not > implemented yet. Mike should be able to put a timeframe on this. It requires a few minutes worth of code work, support for RB_DUAL as a "real" boot option, and a test environment. Please contact me if you're serious about this (I've had about four flakes so far). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 16:03:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01102 for freebsd-current-outgoing; Tue, 2 Feb 1999 16:03:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ganymede.or.intel.com (ganymede.or.intel.com [134.134.248.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01078 for ; Tue, 2 Feb 1999 16:02:52 -0800 (PST) (envelope-from jkastens@iwa.dp.intel.com) Received: from fs001.dp.intel.com (fs001.dp.intel.com [172.24.108.1]) by ganymede.or.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id AAA14778 for ; Wed, 3 Feb 1999 00:02:51 GMT Received: from md6ws267 (md6ws267.dp.intel.com [172.24.108.46]) by fs001.dp.intel.com (8.8.8/8.8.8) with SMTP id QAA02396 for ; Tue, 2 Feb 1999 16:02:50 -0800 (PST) Reply-To: From: "Jayson Kastens" To: Date: Tue, 2 Feb 1999 16:02:47 -0800 Message-ID: <000001be4f08$8999c000$2e6c18ac@md6ws267.dp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 16:26:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06929 for freebsd-current-outgoing; Tue, 2 Feb 1999 16:26:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from liberty.bulinfo.net (liberty.bulinfo.net [195.10.36.71]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA06848 for ; Tue, 2 Feb 1999 16:26:22 -0800 (PST) (envelope-from ian@bulinfo.net) Received: (qmail 21897 invoked from network); 3 Feb 1999 00:25:57 -0000 Received: from gate.bulinfo.net (195.10.36.66) by liberty.bulinfo.net with SMTP; 3 Feb 1999 00:25:57 -0000 Received: (qmail 11968 invoked from network); 3 Feb 1999 00:25:53 -0000 Received: from ppp48.bulinfo.net (HELO cserv.oksys.bg) (195.10.36.93) by gate.bulinfo.net with SMTP; 3 Feb 1999 00:25:53 -0000 Received: from bulinfo.net (ian@cserv.oksys.bg [192.72.180.21]) by cserv.oksys.bg (8.8.8/8.8.8) with ESMTP id CAA22773; Wed, 3 Feb 1999 02:25:53 +0200 (EET) (envelope-from ian@bulinfo.net) Message-ID: <36B79791.7C5562D2@bulinfo.net> Date: Wed, 03 Feb 1999 02:25:53 +0200 From: Iani Brankov Organization: ok systems X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.8-STABLE i386) X-Accept-Language: bg, en MIME-Version: 1.0 To: jkastens@iwa.dp.intel.com, freebsd-current@FreeBSD.ORG Subject: Re: References: <000001be4f08$8999c000$2e6c18ac@md6ws267.dp.intel.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jayson Kastens wrote: > > subscribe freebsd-current > mailto:majordomo@freebsd.org?body=subscribe freebsd-current :) -- When the people talk about troubles, the word Microsoft is the most frequently used one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 16:27:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07072 for freebsd-current-outgoing; Tue, 2 Feb 1999 16:27:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07043 for ; Tue, 2 Feb 1999 16:27:50 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id JAA27357; Wed, 3 Feb 1999 09:27:44 +0900 (JST) Message-ID: <36B795A1.50AC4775@newsguy.com> Date: Wed, 03 Feb 1999 09:17:37 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Steve Kiernan CC: freebsd-current@FreeBSD.ORG Subject: Re: New boot blocks not installed on 3.0-STABLE (02/01/1999 snap) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Kiernan wrote: > > Okay, I did an update install with 3.0-STABLE (the snap from yesterday), > but the new boot blocks weren't installed, so the old boot loader keeps > complaining that the kernel is the wrong format (obviously, bootloader, > it's an ELF kernel). Any way to get the new boot blocks onto the drive > from the kernel/mfs root disks or the fixit floppy? No need to. Pass /boot/loader to your old boot blocks, and it will boot normally. Then install your new bootblocks. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com She just looked at him over the rotating pencil like, how slow can a mammal be and still have respiratory functions? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 16:28:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07267 for freebsd-current-outgoing; Tue, 2 Feb 1999 16:28:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from liberty.bulinfo.net (liberty.bulinfo.net [195.10.36.71]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA07223 for ; Tue, 2 Feb 1999 16:28:17 -0800 (PST) (envelope-from ian@bulinfo.net) Received: (qmail 21915 invoked from network); 3 Feb 1999 00:28:07 -0000 Received: from gate.bulinfo.net (195.10.36.66) by liberty.bulinfo.net with SMTP; 3 Feb 1999 00:28:07 -0000 Received: (qmail 12024 invoked from network); 3 Feb 1999 00:28:03 -0000 Received: from ppp48.bulinfo.net (HELO cserv.oksys.bg) (195.10.36.93) by gate.bulinfo.net with SMTP; 3 Feb 1999 00:28:03 -0000 Received: from bulinfo.net (ian@cserv.oksys.bg [192.72.180.21]) by cserv.oksys.bg (8.8.8/8.8.8) with ESMTP id CAA23078; Wed, 3 Feb 1999 02:28:03 +0200 (EET) (envelope-from ian@bulinfo.net) Message-ID: <36B79813.8828962C@bulinfo.net> Date: Wed, 03 Feb 1999 02:28:03 +0200 From: Iani Brankov Organization: ok systems X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.8-STABLE i386) X-Accept-Language: bg, en MIME-Version: 1.0 To: jkastens@iwa.dp.intel.com, freebsd-current@FreeBSD.ORG Subject: Re: References: <000001be4f08$8999c000$2e6c18ac@md6ws267.dp.intel.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jayson Kastens wrote: > > subscribe freebsd-current > mailto:majordomo@freebsd.org?body='subscribe freebsd-current' :) -- When the people talk about troubles, the word Microsoft is the most frequently used one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 16:41:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09079 for freebsd-current-outgoing; Tue, 2 Feb 1999 16:41:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09074 for ; Tue, 2 Feb 1999 16:41:28 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id TAA25452 for ; Tue, 2 Feb 1999 19:41:24 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA18039; Tue, 2 Feb 1999 19:41:23 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id TAA51965 for freebsd-current@freebsd.org; Tue, 2 Feb 1999 19:41:23 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199902030041.TAA51965@bb01f39.unx.sas.com> Subject: 4.0-19990130-SNAP - ld.so not installed To: freebsd-current@FreeBSD.ORG Date: Tue, 2 Feb 1999 19:41:23 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I just installed the 0130 snap. The install process did not install /usr/libexec/ld.so ... I ran a make world which built and installed correctly: -------------------------------------------------------------- >>> Installing legacy rtld -------------------------------------------------------------- cd /usr/src/libexec/rtld-aout; /usr/obj/usr/src/tmp/usr/bin/make -DNOMAN install install -c -s -o root -g wheel -m 555 -fschg -C ld.so /usr/libexec So I back-tracked to where the snap is generated. The make release process is correctly building and installing this into the snap area: /snap/release/usr/libexec/ld.so /snap/release/usr/obj/aout/usr/src/libexec/rtld-aout/ld.so but it doesn't appear to make it into the /snap/release/R/ftp area. Is this the expected/correct behavior? or am I missing something? Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 17:47:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18095 for freebsd-current-outgoing; Tue, 2 Feb 1999 17:47:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18090 for ; Tue, 2 Feb 1999 17:47:01 -0800 (PST) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.2/8.8.8) with SMTP id JAA26933 for ; Wed, 3 Feb 1999 09:46:45 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id JAA18991; Wed, 3 Feb 1999 09:46:45 +0800 Message-Id: <199902030146.JAA18991@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Linux devel doesn't work with glibc libs Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Feb 1999 09:46:45 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When trying to link, it complains about libc.os.6 vs libc.so.5. This makes life rather difficult when trying to test glide programs against my version of the /dev/3dfx driver. Can someone commit the RedHat dev system (mmmm. egcs mmmm)? Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 18:10:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21435 for freebsd-current-outgoing; Tue, 2 Feb 1999 18:10:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21429 for ; Tue, 2 Feb 1999 18:10:22 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA02590 for ; Tue, 2 Feb 1999 18:06:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902030206.SAA02590@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Overview of the FreeBSD boot process, 3.1 and later Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Feb 1999 18:06:32 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm in the process of preparing a document describing the FreeBSD boot process in the new age. At the moment, there's some emphasis on the loader, and probably an uneven level of detail elsewhere. Commentary is invited. http://www.freebsd.org/~msmith/FTL/bootstrap.txt -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 18:17:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22675 for freebsd-current-outgoing; Tue, 2 Feb 1999 18:17:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ww183.netaddress.usa.net (ww183.netaddress.usa.net [204.68.24.83]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA22660 for ; Tue, 2 Feb 1999 18:17:51 -0800 (PST) (envelope-from slpalmer@netscape.net) Received: (qmail 24794 invoked by uid 60001); 3 Feb 1999 02:15:39 -0000 Message-ID: <19990203021539.24793.qmail@ww183.netaddress.usa.net> Received: from 204.68.24.83 by ww183 via web-mailer(R2.6) on Wed Feb 3 02:15:39 GMT 1999 Date: 3 Feb 99 02:15:39 America/Fort_Wayne From: Stephen Palmer To: Subject: ppbus0: MEDIA CPIA_1-20 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id SAA22668 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While looking at the output from dmesg, I noticed the following which I don't remember having seen before. (Of course I might not have had the camera hooked up to this system while running FreeBSD before ;-) Probing for PnP devices on ppbus0: ppbus0: MEDIA CPIA_1-20 This is actualy a "Zoom/Video Cam PPC" which I use under Win98 from time to time. Any chance of getting working images from this device under FreeBSD-current? How would I go about this? This system is not currently very current (Jan 14, 1999 / no pun intended) but I'm cvsup'ing as I type this... Stephen L. Palmer slpalmer@netscape.net ____________________________________________________________________ More than just email--Get your FREE Netscape WebMail account today at http://home.netscape.com/netcenter/mail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 20:37:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA13161 for freebsd-current-outgoing; Tue, 2 Feb 1999 20:37:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13149 for ; Tue, 2 Feb 1999 20:37:13 -0800 (PST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from dsto-ms2.dsto.defence.gov.au (dsto-ms2.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id PAA21497 for ; Wed, 3 Feb 1999 15:04:09 +1030 (CST) Received: from exchsa1.dsto.defence.gov.au (unverified [131.185.2.94]) by dsto-ms2.dsto.defence.gov.au (Integralis SMTPRS 2.0.15) with ESMTP id for ; Wed, 03 Feb 1999 14:55:15 +1030 Received: from fang.dsto.defence.gov.au ([131.185.2.5]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id 1CHAA5JD; Wed, 3 Feb 1999 14:51:41 +1030 Received: from dsto.defence.gov.au (fuzz.dsto.defence.gov.au [131.185.75.229]) by fang.dsto.defence.gov.au (8.8.5/8.8.5) with ESMTP id OAA20730 for ; Wed, 3 Feb 1999 14:51:39 +1030 (CST) Message-Id: <36B7CED1.96D4B369@dsto.defence.gov.au> Date: Wed, 03 Feb 1999 14:51:37 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: How do I query system temperature probes ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I seem to have all the hardware required for querying the temperature probes in the system (At least I can do it from the BIOS). How can I query this info ? I assume I need "controller smbus0" and "controller intpm0" in my kernel. But do I also need "device smb0 at smbus?" and/or any of the following: # ic i2c network interface # iic i2c standard io # iicsmb i2c to smb bridge. Allow i2c i/o with smb commands. Once I have all this stuff in my kernel, what commands do I use to query the probes ?? My system is FreeBSD 4.0-CURRENT (of CTM 3722 - but will soon be really -CURRENT) Extract from dmesg: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x01 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip3: rev 0x01 on pci0.7.3 -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 21:01:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA17930 for freebsd-current-outgoing; Tue, 2 Feb 1999 21:01:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from genius.cirx.org (r00t.m1.ntu.edu.tw [140.112.240.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA17859 for ; Tue, 2 Feb 1999 21:00:44 -0800 (PST) (envelope-from clkao@CirX.ORG) Received: (from clkao@localhost) by genius.cirx.org (8.9.2/8.9.1) id MAA01559; Wed, 3 Feb 1999 12:42:01 +0800 (CST) (envelope-from clkao@CirX.ORG) Date: Wed, 3 Feb 1999 12:42:01 +0800 (CST) Message-Id: <199902030442.MAA01559@genius.cirx.org> X-Authentication-Warning: genius.cirx.org: clkao set sender to clkao@CirX.ORG using -f From: Chia-liang Kao To: wpaul@skynet.ctr.columbia.edu CC: current@FreeBSD.ORG In-reply-to: <199902021920.OAA05271@skynet.ctr.columbia.edu> (message from Bill Paul on Tue, 2 Feb 1999 14:20:11 -0500 (EST)) Subject: Re: problem with vr0 References: <199902021920.OAA05271@skynet.ctr.columbia.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm really sorry about this, Bill. I'll be very careful and make a recheck before sending out problem report next time. And really thank you for shouting at me instead of leaving my problem along. I did a `ping 192.168.100.1', and there is no response and no messages at all. I think the most interesting part of this is that I can see both of the lights on the hub blinking when I ping 192.168.100.1; while only the light of the other side blinks when he pings me. So we're starting to doubt the problem is the receiving function of my side. And we test again with `trafshow'. Then I found he does receive my packet and replies when I ping him, while I can only see the packets I sent out but no packets from his side. But sometimes it works for a tiny second, like the following: # traceroute i1 traceroute to i1 (192.168.100.1), 30 hops max, 40 byte packets 1 i1 (192.168.100.1) 0.720 ms * * * From: Bill Paul * Date: Tue, 2 Feb 1999 14:20:11 -0500 (EST) * * You have not explained exactly what is going wrong. You have not * explained what it is that you're trying to do which isn't working. * You have not explained how you came to the conclusion that the card * "isn't working." Show us what happens if you type 'ping 192.168.100.1'. * Don't attempt to paraphrase the error messages: quote them exactly. * Does ping not illustrate the problem accurately? Fine: choose another * example and show us the results. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 21:02:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18162 for freebsd-current-outgoing; Tue, 2 Feb 1999 21:02:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18146; Tue, 2 Feb 1999 21:02:24 -0800 (PST) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.sci.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id NAA19395; Wed, 3 Feb 1999 13:53:28 +0900 (JST) Message-Id: <199902030453.NAA19395@shidahara1.planet.sci.kobe-u.ac.jp> To: Matthew Thyer , dillon@FreeBSD.ORG cc: current@FreeBSD.ORG Subject: Re: How do I query system temperature probes ? In-reply-to: Your message of "Wed, 03 Feb 1999 14:51:37 +1030" References: <36B7CED1.96D4B369@dsto.defence.gov.au> Date: Wed, 03 Feb 1999 13:53:27 +0900 From: Takanori Watanabe Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <36B7CED1.96D4B369@dsto.defence.gov.au>, Matthew Thyer wrote: > >Extract from dmesg: > >chip0: rev 0x03 on >pci0.0.0 >chip1: rev 0x03 on >pci0.1.0 >chip2: rev 0x01 on pci0.7.0 >ide_pci0: rev 0x01 on pci0.7.1 >chip3: rev 0x01 on pci0.7.3 Commited code on pcisupport.c from 1.88 to 1.89 will break it. If "intpm.h" is not included,chipset probe code is used instead of the driver probe code. Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A P.S I have forgotten to enclose unused variable in #undef ENABLE_ALART with #ifdef ENABLE_ALART - #endif ,so the variable may deleted when it was commited. And currently ENABLE_ALART code will not work properly. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 21:15:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20583 for freebsd-current-outgoing; Tue, 2 Feb 1999 21:15:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20578 for ; Tue, 2 Feb 1999 21:15:45 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id VAA43044; Tue, 2 Feb 1999 21:15:44 -0800 (PST) (envelope-from dillon) Date: Tue, 2 Feb 1999 21:15:44 -0800 (PST) From: Matthew Dillon Message-Id: <199902030515.VAA43044@apollo.backplane.com> To: current@FreeBSD.ORG Subject: Heads up: comitted optimization to vm_map_insert() Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've comitted an optimization to vm_map_insert() after initial tests seemed to indicate that it works. Basically it allows OBJT_SWAP objects to be optimized in addition to OBJT_DEFAULT objects already optimized in certain specific cases. However, a followup test that I had never run before had a temporary seg-fault ( i.e. it didn't repeat when I re-ran the test ). I think the seg fault may have revealed a new bug and is not related to the optimization I comitted, so I haven't backed out the commit. I am not 100% sure though, and I am testing this now. If anyone notices weird seg-faulting that didn't occur before tonight, please notify me! -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 21:17:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21028 for freebsd-current-outgoing; Tue, 2 Feb 1999 21:17:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA21012 for ; Tue, 2 Feb 1999 21:17:37 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id AAA06011; Wed, 3 Feb 1999 00:24:28 -0500 From: Bill Paul Message-Id: <199902030524.AAA06011@skynet.ctr.columbia.edu> Subject: Re: problem with vr0 To: clkao@CirX.ORG (Chia-liang Kao) Date: Wed, 3 Feb 1999 00:24:27 -0500 (EST) Cc: current@FreeBSD.ORG In-Reply-To: <199902030442.MAA01559@genius.cirx.org> from "Chia-liang Kao" at Feb 3, 99 12:42:01 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Chia-liang Kao had to walk into mine and say: > I'm really sorry about this, Bill. I'll be very careful and make a > recheck before sending out problem report next time. And really thank > you for shouting at me instead of leaving my problem along. Shouting is my specialty. I get a lot of practice. > I did a `ping 192.168.100.1', and there is no response and no messages > at all. I think the most interesting part of this is that I can see > both of the lights on the hub blinking when I ping 192.168.100.1; > while only the light of the other side blinks when he pings me. What kind of hub is this? > So we're starting to doubt the problem is the receiving function of my > side. And we test again with `trafshow'. Then I found he does receive > my packet and replies when I ping him, while I can only see the > packets I sent out but no packets from his side. > > But sometimes it works for a tiny second, like the following: > > # traceroute i1 > traceroute to i1 (192.168.100.1), 30 hops max, 40 byte packets > 1 i1 (192.168.100.1) 0.720 ms * * Are you using any unusual networking tricks, like network address translation or firewalling or IP aliasing? People tend to forget to mention things like that. There are some things I'm curious about: - What does netstat -in show? Are there any input errors? Are there any input packets? (If the input packet counter keeps incrementing then it has to be receiving something.) - Do you see any suspicious messages when you do a dmesg to look at the kernel message buffer? The vr driver should report receive errors if it encounters any. - If you run tcpdump on the vr0 interface (tcpdump -n -e -i vr0) can you see the traffic from the other host? Try the following: # arp -d 192.168.100.1 # tcpdump -n -e -i vr0 & # ping -c 5 192.168.100.1 Show us the output. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 22:49:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA07743 for freebsd-current-outgoing; Tue, 2 Feb 1999 22:49:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from genius.cirx.org (r00t.m1.ntu.edu.tw [140.112.240.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA07673 for ; Tue, 2 Feb 1999 22:49:03 -0800 (PST) (envelope-from clkao@CirX.ORG) Received: (from clkao@localhost) by genius.cirx.org (8.9.2/8.9.1) id OAA01948; Wed, 3 Feb 1999 14:47:45 +0800 (CST) (envelope-from clkao@CirX.ORG) Date: Wed, 3 Feb 1999 14:47:45 +0800 (CST) Message-Id: <199902030647.OAA01948@genius.cirx.org> X-Authentication-Warning: genius.cirx.org: clkao set sender to clkao@CirX.ORG using -f From: Chia-liang Kao To: wpaul@skynet.ctr.columbia.edu CC: current@FreeBSD.ORG In-reply-to: <199902030524.AAA06011@skynet.ctr.columbia.edu> (message from Bill Paul on Wed, 3 Feb 1999 00:24:27 -0500 (EST)) Subject: Re: problem with vr0 References: <199902030524.AAA06011@skynet.ctr.columbia.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Bill Paul * Date: Wed, 3 Feb 1999 00:24:27 -0500 (EST) * * > I did a `ping 192.168.100.1', and there is no response and no messages * > at all. I think the most interesting part of this is that I can see * > both of the lights on the hub blinking when I ping 192.168.100.1; * > while only the light of the other side blinks when he pings me. * * What kind of hub is this? It's a nonaccredited 5-port 10Bast-T hub which we used to connect outside world via another interface (my de0 and his ed0). And when we're trying to use this hub for internal connection only via both of our newly bought dfe530s, we're in trouble. * Are you using any unusual networking tricks, like network address * translation or firewalling or IP aliasing? People tend to forget to * mention things like that. There are some things I'm curious about: No, that's why I typed a `ipfw list' in the very first mail which indicates I have no firewall configuration in my kernel at all. * - What does netstat -in show? Are there any input errors? Are there * any input packets? (If the input packet counter keeps incrementing * then it has to be receiving something.) * There are some Ipkts but very few as you can see in the following. # netstat -in Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll de0 1500 00.80.c8.46.1e.d4 313987 34111 18717 185 2651 de0 1500 140.112.240/2 140.112.240.59 313987 34111 18717 185 2651 vr0 1500 00.80.c8.ef.82.09 16 0 15804 0 0 vr0 1500 192.168.100 192.168.100.2 16 0 15804 0 0 * - Do you see any suspicious messages when you do a dmesg to look at the * kernel message buffer? The vr driver should report receive errors if * it encounters any. Not at all, only `vr0: promiscuous mode enabled' when starting tcpdump. * - If you run tcpdump on the vr0 interface (tcpdump -n -e -i vr0) can * you see the traffic from the other host? Try the following: * * # arp -d 192.168.100.1 * # tcpdump -n -e -i vr0 & * # ping -c 5 192.168.100.1 * * Show us the output. PING 192.168.100.1 (192.168.100.1): 56 data bytes 14:32:35.481753 0:80:c8:ef:82:9 ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.1 tell 192.168.100.2 14:32:36.486348 0:80:c8:ef:82:9 ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.1 tell 192.168.100.2 14:32:36.486561 0:80:c8:ef:3c:3f 0:80:c8:ef:82:9 0806 60: arp reply 192.168.100.1 is-at 0:80:c8:ef:3c:3f 14:32:36.486625 0:80:c8:ef:82:9 0:80:c8:ef:3c:3f 0800 98: 192.168.100.2 > 192.168.100.1: icmp: echo request 14:32:37.496739 0:80:c8:ef:82:9 0:80:c8:ef:3c:3f 0800 98: 192.168.100.2 > 192.168.100.1: icmp: echo request 14:32:38.506383 0:80:c8:ef:82:9 0:80:c8:ef:3c:3f 0800 98: 192.168.100.2 > 192.168.100.1: icmp: echo request 14:32:39.516717 0:80:c8:ef:82:9 0:80:c8:ef:3c:3f 0800 98: 192.168.100.2 > 192.168.100.1: icmp: echo request --- 192.168.100.1 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss and here is the result of the same test done on 192.168.100.1 (with the target changed to 192.168.100.2): ping -c 5 192.168.100.2 PING 192.168.100.2 (192.168.100.2): 56 data bytes 14:36:01.999162 0:80:c8:ef:3c:3f ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.2 tell 192.168.100.1 14:36:03.008614 0:80:c8:ef:3c:3f ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.2 tell 192.168.100.1 14:36:04.018622 0:80:c8:ef:3c:3f ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.2 tell 192.168.100.1 14:36:05.028656 0:80:c8:ef:3c:3f ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.2 tell 192.168.100.1 14:36:06.038664 0:80:c8:ef:3c:3f ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.2 tell 192.168.100.1 14:36:14.106056 0:80:c8:ef:3c:3f ff:ff:ff:ff:ff:ff 0800 142: 192.168.100.1.1090> 192.168.100.255.111: udp 100 14:36:14.106075 0:80:c8:ef:3c:3f ff:ff:ff:ff:ff:ff 0800 142: 192.168.100.1.1090> 192.168.100.255.111: udp 100 --- 192.168.100.2 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 2 23:23:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14580 for freebsd-current-outgoing; Tue, 2 Feb 1999 23:23:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles138.castles.com [208.214.165.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14564 for ; Tue, 2 Feb 1999 23:23:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id XAA00601; Tue, 2 Feb 1999 23:19:52 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902030719.XAA00601@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: KLD confusion.. In-reply-to: Your message of "Mon, 01 Feb 1999 17:04:53 PST." <36B64F35.237C228A@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Feb 1999 23:19:52 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Take the following scenario: > > compiled in: module A > > kldstat -v shows module 'A' > > kldload A > damned thing succeeds. That's correct. There's a fundamental problem here in that there's a confusion between file names and module names. This is a basic flaw in the way that KLD was implemented (no offense to Doug; it was initially meant to be a better LKM, not necessarily a whole new ball of wax). I've taken about four different runs at a "right" way of doing this subsequently. I think that, with some help and advice from Doug and Peter, I'm on the right track now, but there's no hope of it being ready for 3.1. > this is handleable by just not loading 'A' > but what about the following: > > kldload 'B' where B is defined to have a dependency on 'A' > and 'A' is already loaded.. > > A get's loaded again.. leading to REALLY strange behaviour > if the kernel is talking to one copy of A and B is talking > to the other. That's definitely not correct behaviour, but again it's because the dependancy is implemented as a NEEDED reference to a *file*, not a module. > I've had a look at the code, but > I think this would be a 20 minute thing for the right person, > rather than a 2 day thing for me... It's been about 2 months for me so far, so I guess either I'm not the right person, or it's not that easy. I can't see a "right" way of fixing it short of completely separating "files" and "modules". Here's another scenario guaranteed to flummox the current code; link A and B together in a single file, name it after A. Then have C, which depends on B, and try to load that. It's going to look for a file named after B... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 01:12:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29247 for freebsd-current-outgoing; Wed, 3 Feb 1999 01:12:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from buffy.tpgi.com.au (buffy.tpgi.com.au [203.12.160.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29240 for ; Wed, 3 Feb 1999 01:12:05 -0800 (PST) (envelope-from eirvine@tpgi.com.au) Received: (from smtpd@localhost) by buffy.tpgi.com.au (8.8.7/8.8.7) id UAA29868 for ; Wed, 3 Feb 1999 20:12:09 +1100 Received: from kmidc71-133.ecopost.com.au(203.28.71.133), claiming to be "tpgi.com.au" via SMTP by buffy.tpgi.com.au, id smtpda29741; Wed Feb 3 20:11:56 1999 Message-ID: <36B812EC.9D2279A5@tpgi.com.au> Date: Wed, 03 Feb 1999 20:12:12 +1100 From: Eddie Irvine X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: buildworld fails on 3.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I've cvsupped a number of times over the last week, zapped /usr/obj/* , made the includes, and keep getting exactly the same problem: my cvsup tag=RLENG_3 (or something like that) cd /usr/src make includes ----- this is OK make clean ----- this is OK nohup make buildworld 2>&1 -------- this is not so OK -------- The first appearance occurs on line 23914 of nohup.out: gzip -cn /usr/src/sbin/i386/nextboot/nextboot.8 > nextboot.8.gz ===> share ===> share/dict ===> share/doc ===> share/doc/psd ===> share/doc/psd/title touch _stamp.extraobjs (cd /usr/src/share/doc/psd/title; groff -mtty-char -Tascii -ms -o1- /usr/src/sha re/doc/psd/title/Title) | gzip -cn > Title.ascii.gz groff: can't find `DESC' file ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ groff:fatal error: invalid device `ascii' ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ===> share/doc/psd/contents touch _stamp.extraobjs (cd /usr/src/share/doc/psd/contents; groff -mtty-char -Tascii -ms -o1- /usr/src/ share/doc/psd/contents/contents.ms) | gzip -cn > contents.ascii.gz groff: can't find `DESC' file groff:fatal error: invalid device `ascii' ---------- and it karks it around line 24128 ===> share/doc/usd/13.viref sed -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(vi.ref\)$:\1/usr/src/share/doc/usd/13.vire f/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(ex.cmd.roff\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contrib/nvi/d ocs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(ref.so\)$:\1/usr/s rc/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ ' s:\(\.so[\ \ ][\ \ ]*\)\(set.opt.roff\)$:\1/usr/src/share/doc/usd/13.viref/ ../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(vi.cmd.roff\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contrib/nvi/d ocs/USD.doc/vi.ref/\2:' -e 's:^\.so index.so$::' /usr/src/share/doc/usd/13.viref /../../../../contrib/nvi/docs/USD.doc/vi.ref/vi.ref | groff -mtty-char -Tascii -t -s -me -o1- > /dev/null groff: can't find `DESC' file ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ groff:fatal error: invalid device `ascii' ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ *** Error code 3 Stop. *** Error code 1 What do I do? should I zap the /usr/share/doc/* and re-cvsup? Eddie. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 01:17:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29980 for freebsd-current-outgoing; Wed, 3 Feb 1999 01:17:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29971 for ; Wed, 3 Feb 1999 01:17:07 -0800 (PST) (envelope-from netchild@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.2/1999010400) with ESMTP id KAA13602; Wed, 3 Feb 1999 10:16:41 +0100 (CET) Received: from wurzelausix (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.2/1999010400) with ESMTP id KAA13921; Wed, 3 Feb 1999 10:16:40 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (IDENT:GjyLxTf3RuLMMIh9yWJHPrgTxlrhC4QL@localhost [127.0.0.1]) by wurzelausix (8.9.1/wjp/19980821) with ESMTP id KAA23750; Wed, 3 Feb 1999 10:16:36 +0100 (CET) Message-Id: <199902030916.KAA23750@wurzelausix> Date: Wed, 3 Feb 1999 10:16:34 +0100 (CET) From: Alexander Leidinger Subject: Re: buildworld fails on 3.0 To: eirvine@tpgi.com.au cc: freebsd-current@FreeBSD.ORG In-Reply-To: <36B812EC.9D2279A5@tpgi.com.au> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 3 Feb, Eddie Irvine wrote: > re/doc/psd/title/Title) | gzip -cn > Title.ascii.gz > groff: can't find `DESC' file > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > groff:fatal error: invalid device `ascii' > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > ===> share/doc/psd/contents > touch _stamp.extraobjs > (cd /usr/src/share/doc/psd/contents; groff -mtty-char -Tascii -ms -o1- > /usr/src/ > share/doc/psd/contents/contents.ms) | gzip -cn > contents.ascii.gz > groff: can't find `DESC' file > groff:fatal error: invalid device `ascii' > What do I do? should I zap the /usr/share/doc/* and re-cvsup? > Eddie. Do you compile with "-O3" (make.conf)? -> try again with "-O2" or less. Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 02:40:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA09356 for freebsd-current-outgoing; Wed, 3 Feb 1999 02:40:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from k6n1.znh.org ([207.109.235.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA09280 for ; Wed, 3 Feb 1999 02:39:58 -0800 (PST) (envelope-from zach@uffdaonline.net) Received: (from zach@localhost) by k6n1.znh.org (8.9.2/8.9.1) id KAA07331; Wed, 3 Feb 1999 10:40:45 GMT (envelope-from zach) Message-ID: <19990203044045.A7108@znh.org> Date: Wed, 3 Feb 1999 04:40:45 -0600 From: Zach Heilig To: Chia-liang Kao , wpaul@skynet.ctr.columbia.edu Cc: current@FreeBSD.ORG Subject: Re: problem with vr0 References: <199902021920.OAA05271@skynet.ctr.columbia.edu> <199902030442.MAA01559@genius.cirx.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199902030442.MAA01559@genius.cirx.org>; from Chia-liang Kao on Wed, Feb 03, 1999 at 12:42:01PM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 03, 1999 at 12:42:01PM +0800, Chia-liang Kao wrote: > I did a `ping 192.168.100.1', and there is no response and no messages > at all. I think the most interesting part of this is that I can see > both of the lights on the hub blinking when I ping 192.168.100.1; > while only the light of the other side blinks when he pings me. ... I use this driver as well, and have had conversations with Bill Paul before on this. It is now working well enough for my needs (but not anywhere resembling perfect -- transfers either direction have to be initiated from a different host). Maybe your machine and my machine that flakes out are similar: [excerpts from dmesg] CPU: AMD Am5x86 Write-Back (486-class CPU) Origin = "AuthenticAMD" Id = 0x4f4 Stepping=4 Features=0x1 real memory = 67108864 (65536K bytes) chip0: rev 0x31 on pci0.5.0 vr0: rev 0x06 int a irq 9 on pci0.13.0 vr0: Ethernet address: 00:a0:0c:c0:03:c1 vr0: autoneg complete, link status good (half-duplex, 10Mbps) The best conclusion I could come up with is that particular PCI chipset is flakey [maybe the entire chipset]. Only one pci card I have tried in that system has worked properly, and that was a display adapter -- this is out of about 6 different PCI cards of various types. -- Zach Heilig / Zach Heilig "Americans are sensitive about their money, and since this was the first major change in the greenback in nearly 70 years, a radical redesign might have been too much for consumers to comprehend" -- John Iddings [COINage, Feb. 1999]. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 02:45:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA09812 for freebsd-current-outgoing; Wed, 3 Feb 1999 02:45:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA09806 for ; Wed, 3 Feb 1999 02:45:06 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from guppy.dons.net.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.2/8.9.1) with ESMTP id VAA05751; Wed, 3 Feb 1999 21:14:44 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199902030146.JAA18991@ariadne.tensor.pgs.com> Date: Wed, 03 Feb 1999 21:12:47 +1030 (CST) From: "Daniel J. O'Connor" To: Stephen Hocking-Senior Programmer PGS Tensor Perth Subject: RE: Linux devel doesn't work with glibc libs Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Feb-99 Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > When trying to link, it complains about libc.os.6 vs libc.so.5. This makes > life rather difficult when trying to test glide programs against my version > the /dev/3dfx driver. Can someone commit the RedHat dev system (mmmm. egcs > mmmm)? Ahh... This would explain a few things :-/ Damn I can't rebuild a copy of qkHacklib, or Mesa.. ARGH! --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 03:49:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16865 for freebsd-current-outgoing; Wed, 3 Feb 1999 03:49:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oskar.nanoteq.co.za (oskar.nanoteq.co.za [196.37.91.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA16852 for ; Wed, 3 Feb 1999 03:49:20 -0800 (PST) (envelope-from rbezuide@oskar.nanoteq.co.za) Received: (from rbezuide@localhost) by oskar.nanoteq.co.za (8.9.0/8.9.0) id NAA26926 for freebsd-current@freeBSD.org; Wed, 3 Feb 1999 13:49:16 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199902031149.NAA26926@oskar.nanoteq.co.za> Subject: make port and bsd.port.mk To: freebsd-current@FreeBSD.ORG Date: Wed, 3 Feb 1999 13:49:13 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ... I recently upgraded from 3.0-current to 3.0-STABLE ... When running 3.0-current I was able to build ports without a problem. In the new system ... I get the following error : "/usr/share/mk/bsd.port.mk", line 2: Could not find /usr/ports/Mk/bsd.port.mk make: fatal errors encountered -- cannot continue There is no /usr/ports/Mk directory on my machine (I did a make buildworld and a installworld ) Where can I find these files or is it a bug ?? Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 03:56:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA17476 for freebsd-current-outgoing; Wed, 3 Feb 1999 03:56:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA17434 for ; Wed, 3 Feb 1999 03:56:43 -0800 (PST) (envelope-from steveo@iol.ie) Received: from pooh.elsevier.nl (localhost [127.0.0.1]) by pooh.elsevier.nl (8.9.2/8.9.2) with ESMTP id LAA97041; Wed, 3 Feb 1999 11:52:59 GMT (envelope-from steveo@iol.ie) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199902031149.NAA26926@oskar.nanoteq.co.za> Date: Wed, 03 Feb 1999 11:52:58 -0000 (GMT) From: "Steve O'Hara-Smith" To: Reinier Bezuidenhout Subject: RE: make port and bsd.port.mk Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Feb-99 Reinier Bezuidenhout wrote: > Hi ... > > There is no /usr/ports/Mk directory on my machine > Where can I find these files or is it a bug ?? cvsup your ports and all will be well. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 05:22:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA04469 for freebsd-current-outgoing; Wed, 3 Feb 1999 05:22:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA04436 for ; Wed, 3 Feb 1999 05:22:44 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id XAA23622; Wed, 3 Feb 1999 23:52:37 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA06565; Wed, 3 Feb 1999 23:52:33 +1030 Date: Wed, 3 Feb 1999 23:52:33 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: "Steve O'Hara-Smith" Cc: Reinier Bezuidenhout , freebsd-current@FreeBSD.ORG Subject: RE: make port and bsd.port.mk In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 3 Feb 1999, Steve O'Hara-Smith wrote: > On 03-Feb-99 Reinier Bezuidenhout wrote: > > Hi ... > > > > There is no /usr/ports/Mk directory on my machine > > Where can I find these files or is it a bug ?? > > cvsup your ports and all will be well. And make sure you're grabbing the ports-base collection (either explicitly or part of ports-all). Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 06:20:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA11976 for freebsd-current-outgoing; Wed, 3 Feb 1999 06:20:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA11826 for ; Wed, 3 Feb 1999 06:19:45 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id JAA06705; Wed, 3 Feb 1999 09:26:26 -0500 From: Bill Paul Message-Id: <199902031426.JAA06705@skynet.ctr.columbia.edu> Subject: Re: problem with vr0 To: clkao@CirX.ORG (Chia-liang Kao) Date: Wed, 3 Feb 1999 09:26:24 -0500 (EST) Cc: current@FreeBSD.ORG In-Reply-To: <199902030647.OAA01948@genius.cirx.org> from "Chia-liang Kao" at Feb 3, 99 02:47:45 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Chia-liang Kao had to walk into mine and say: > * From: Bill Paul > * Date: Wed, 3 Feb 1999 00:24:27 -0500 (EST) > * > * > I did a `ping 192.168.100.1', and there is no response and no messages > * > at all. I think the most interesting part of this is that I can see > * > both of the lights on the hub blinking when I ping 192.168.100.1; > * > while only the light of the other side blinks when he pings me. > * > * What kind of hub is this? > > It's a nonaccredited 5-port 10Bast-T hub which we used to connect > outside world via another interface (my de0 and his ed0). And when > we're trying to use this hub for internal connection only via both of > our newly bought dfe530s, we're in trouble. Whoa whoa. Wait a minute; stop right there. Let me see if I understand this. You have a 5 port hub. One port has the connection that links you to the outside world (it goes to your router/switch/whatever). Another second port connects to your machine at de0. A third port connects to your roommate's machine on his ed0. And you have your vr0 interface and your roommate's vr0 interface both connected to this _same_ hub as well? (See, this is why I yell: I can see how somebody might try this and not think that it might cause problems. If I was right there looking at your systems I could probably spot this immediately, but it was only blind luck that you happened to mention it now, otherwise I could have spent months going back and forth with you via e-mail before finally dragging this piece of information out of you.) Uhm. I dunno. That doesn't seem right somehow. It adds another variable that has to be accounted for. The problem here is that when one of you sends a packet, it will end up a) delivered to _two_ interfaces on the target host and b) it will be echoed back to the other interface on the source host. Remember: an ordinary hub just retransmits whatever it hears on one port to every otgher port. Given that you don't seem to be experiencing any transmit or receive errors on the vr0 interface, I get the feeling that this configuration may be contributing to the problem somehow. You need to do one of three things to test to see if this is your problem: - Obtain (purchase/borrow/steal) a second hub, and connect all the 192.168.100 interfaces to it all by themselves. - Connect your vr0 interface to your roommate's vr0 interface directly using a crossover cable. (A crossover cable has the transmit and receive pairs reversed on one end.) - Temporarily unplug your de0 interface and his ed0 interface from the hub and leave just the vr0 interfaces plugged in. Use arp -d to remove each others' ARP entries from your respective ARP caches so that we start fresh. If you can successfully ping each other via the 192.168.100 interfaces and exchange traffic, then you have found the problem. (This is the easiest test, and it doesn't cost anything. :) If you had a _switch_ instead of a hub, then your configuration would probably work because a switch will only deliver traffic to one port (the port where the interface with the destination ethernet address is attached) instead of all ports. (Except for broadcasts and multicasts, without extra configuration.) At least, that's my suspicion. > * - What does netstat -in show? Are there any input errors? Are there > * any input packets? (If the input packet counter keeps incrementing > * then it has to be receiving something.) > * > > There are some Ipkts but very few as you can see in the following. > > # netstat -in > Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll > de0 1500 00.80.c8.46.1e.d4 313987 34111 18717 185 2651 > de0 1500 140.112.240/2 140.112.240.59 313987 34111 18717 185 2651 > vr0 1500 00.80.c8.ef.82.09 16 0 15804 0 0 > vr0 1500 192.168.100 192.168.100.2 16 0 15804 0 0 Hm... No transmit or receive errors. I wonder what all the output traffic is though. > * - If you run tcpdump on the vr0 interface (tcpdump -n -e -i vr0) can > * you see the traffic from the other host? Try the following: > * > * # arp -d 192.168.100.1 > * # tcpdump -n -e -i vr0 & > * # ping -c 5 192.168.100.1 > * > * Show us the output. > > PING 192.168.100.1 (192.168.100.1): 56 data bytes > 14:32:35.481753 0:80:c8:ef:82:9 ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.1 tell 192.168.100.2 > 14:32:36.486348 0:80:c8:ef:82:9 ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.1 tell 192.168.100.2 > 14:32:36.486561 0:80:c8:ef:3c:3f 0:80:c8:ef:82:9 0806 60: arp reply 192.168.100.1 is-at 0:80:c8:ef:3c:3f > 14:32:36.486625 0:80:c8:ef:82:9 0:80:c8:ef:3c:3f 0800 98: 192.168.100.2 > 192.168.100.1: icmp: echo request > 14:32:37.496739 0:80:c8:ef:82:9 0:80:c8:ef:3c:3f 0800 98: 192.168.100.2 > 192.168.100.1: icmp: echo request > 14:32:38.506383 0:80:c8:ef:82:9 0:80:c8:ef:3c:3f 0800 98: 192.168.100.2 > 192.168.100.1: icmp: echo request > 14:32:39.516717 0:80:c8:ef:82:9 0:80:c8:ef:3c:3f 0800 98: 192.168.100.2 > 192.168.100.1: icmp: echo request > --- 192.168.100.1 ping statistics --- > 5 packets transmitted, 0 packets received, 100% packet loss Hm. Okay. Here's a slightly different test: # tcpdump -n -e -i vr0 & # arp -d 192.168.100.1 # ping -c 192.168.100.1 # arp -d 192.168.100.1 # ping -c 192.168.100.1 One possibility is that the receiver is getting stuck and has to be reset; running tcpdump to put the interface in promiscuous mode implicity reinitializes and resets the card (it happens that that's how the driver works). In the above example, we initialize the card once and then leave it alone, then run the arp -d/ping test twice. If you see the same exact results both times (i.e. the chip receives at least one frame) then the receiver is not getting wedged, since it would be receiving at least two frames correctly without having to be reset. Anyway, to sum up: I think the problem has something to do with having both interfaces on both machines attached to the same hub at the same time. If you have ever tried the same configuration before and seen it work (with different cards) then I might be inclined to think the problem is somewhere else. On the other hand, if you and your roommate were just sitting around one day and said "Gee, maybe we can use those two empty ports on the hub to connect our machines together using a private ethernet link!" then you may want to prepare yourselves to be disappointed. :) -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 07:01:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19082 for freebsd-current-outgoing; Wed, 3 Feb 1999 07:01:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from genius.cirx.org (r00t.m1.ntu.edu.tw [140.112.240.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA18439 for ; Wed, 3 Feb 1999 06:58:45 -0800 (PST) (envelope-from clkao@CirX.ORG) Received: (from clkao@localhost) by genius.cirx.org (8.9.2/8.9.1) id WAA43061; Wed, 3 Feb 1999 22:52:43 +0800 (CST) (envelope-from clkao@CirX.ORG) Date: Wed, 3 Feb 1999 22:52:43 +0800 (CST) Message-Id: <199902031452.WAA43061@genius.cirx.org> X-Authentication-Warning: genius.cirx.org: clkao set sender to clkao@CirX.ORG using -f From: Chia-liang Kao To: wpaul@skynet.ctr.columbia.edu CC: current@FreeBSD.ORG In-reply-to: <199902031426.JAA06705@skynet.ctr.columbia.edu> (message from Bill Paul on Wed, 3 Feb 1999 09:26:24 -0500 (EST)) Subject: Re: problem with vr0 References: <199902031426.JAA06705@skynet.ctr.columbia.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Bill Paul * Date: Wed, 3 Feb 1999 09:26:24 -0500 (EST) * * And you have your vr0 interface and your roommate's vr0 interface both * connected to this _same_ hub as well? (See, this is why I yell: I can see * how somebody might try this and not think that it might cause problems. * If I was right there looking at your systems I could probably spot this * immediately, but it was only blind luck that you happened to mention * it now, otherwise I could have spent months going back and forth with * you via e-mail before finally dragging this piece of information out * of you.) Certainly not, sorry that I didn't specify precisely. I meant we used the hub very well connecting us and the outside world, and then we decided to use the hub for internal connection only. So the hub is now connecting our vr0's and nothing else. (Of course, the power adapter is connected. :) * - Obtain (purchase/borrow/steal) a second hub, and connect all the * 192.168.100 interfaces to it all by themselves. * * - Connect your vr0 interface to your roommate's vr0 interface directly * using a crossover cable. (A crossover cable has the transmit and receive * pairs reversed on one end.) * * - Temporarily unplug your de0 interface and his ed0 interface from the * hub and leave just the vr0 interfaces plugged in. Use arp -d to remove * each others' ARP entries from your respective ARP caches so that we * start fresh. If you can successfully ping each other via the * 192.168.100 interfaces and exchange traffic, then you have found the * problem. (This is the easiest test, and it doesn't cost anything. :) We are poor students, so the easiest test has been performed right after we can't get the vr0s to work. (actually it's mine, his works very fine) We even swapped our cards and the result (the ping/trafshow test) is the same. Also, the vr0 currently on my box was originally his, and he used the card to connect outside world in the past. Shouldn't be a kernel issue, since I have tried to get it right by booting his kernel. Anyway, I'll try the first two tests tomorrow. (Ya, you know it, I'll steal one.) * > vr0 1500 00.80.c8.ef.82.09 16 0 15804 0 0 * > vr0 1500 192.168.100 192.168.100.2 16 0 15804 0 0 * * Hm... No transmit or receive errors. I wonder what all the output traffic is * though. When I ping him, he can receive my packets and replies, while I can't get his reply. I think that's where th output packet came from. (ie the icmp outgoing packets when I ping him). And `netstat -in' on his box shows the input and output packets on vr0 are nearly identical. * Hm. Okay. Here's a slightly different test: * * # tcpdump -n -e -i vr0 & * # arp -d 192.168.100.1 * # ping -c 192.168.100.1 * # arp -d 192.168.100.1 * # ping -c 192.168.100.1 * * One possibility is that the receiver is getting stuck and has to be reset; * running tcpdump to put the interface in promiscuous mode implicity * reinitializes and resets the card (it happens that that's how the driver * works). In the above example, we initialize the card once and then leave * it alone, then run the arp -d/ping test twice. If you see the same exact * results both times (i.e. the chip receives at least one frame) then the * receiver is not getting wedged, since it would be receiving at least * two frames correctly without having to be reset. The difference of the above two arp -d/ping are: the first one have 3 `arp who-has' message and 1 arp reply and 3 icmp echo the second one have 5 `arp who-has' and 1 arp reply and 1 icmp echo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 08:06:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00789 for freebsd-current-outgoing; Wed, 3 Feb 1999 08:06:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA00770 for ; Wed, 3 Feb 1999 08:06:17 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id LAA06847; Wed, 3 Feb 1999 11:13:01 -0500 From: Bill Paul Message-Id: <199902031613.LAA06847@skynet.ctr.columbia.edu> Subject: Re: problem with vr0 To: clkao@CirX.ORG (Chia-liang Kao) Date: Wed, 3 Feb 1999 11:12:59 -0500 (EST) Cc: current@FreeBSD.ORG In-Reply-To: <199902031452.WAA43061@genius.cirx.org> from "Chia-liang Kao" at Feb 3, 99 10:52:43 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Chia-liang Kao had to walk into mine and say: > * And you have your vr0 interface and your roommate's vr0 interface both > * connected to this _same_ hub as well? (See, this is why I yell: I can see > * how somebody might try this and not think that it might cause problems. > * If I was right there looking at your systems I could probably spot this > * immediately, but it was only blind luck that you happened to mention > * it now, otherwise I could have spent months going back and forth with > * you via e-mail before finally dragging this piece of information out > * of you.) > > Certainly not, sorry that I didn't specify precisely. I meant we used > the hub very well connecting us and the outside world, and then we > decided to use the hub for internal connection only. So the hub is now > connecting our vr0's and nothing else. (Of course, the power adapter > is connected. :) Ah, okay. My bad. It sure looked like you were saying you had everything attached to the same hub. > We even swapped our cards and the result (the ping/trafshow test) is the same. > > Also, the vr0 currently on my box was originally his, and he used the > card to connect outside world in the past. Shouldn't be a kernel > issue, since I have tried to get it right by booting his kernel. What kind of machine/CPU does your friend have? > Anyway, I'll try the first two tests tomorrow. (Ya, you know it, I'll > steal one.) > > * > vr0 1500 00.80.c8.ef.82.09 16 0 15804 0 0 > * > vr0 1500 192.168.100 192.168.100.2 16 0 15804 0 0 > * > * Hm... No transmit or receive errors. I wonder what all the output traffic is > * though. > > When I ping him, he can receive my packets and replies, while I can't > get his reply. I think that's where th output packet came from. (ie > the icmp outgoing packets when I ping him). And `netstat -in' on his box > shows the input and output packets on vr0 are nearly identical. Hm. I have some more questions: - In your first posting, you mentioned this: vr0: rev 0x06 int a irq 12 on pci0.19.0 IRQ 12 is normally used by the mouse (if you have a PS/2 mouse). Do you have a mouse or PS/2 mouse port on this machine? (I suspect you don't but I have to ask.) - How many PCI bus slots does your machine have? - Have you tried putting the vr0 card in a different slot? Have you tried putting it in the slot where the de0 card is now? - What PCI chipset do you have? The test machine in which I currently have my sample VIA Rhine card installed is an Intel Pentium 200 system that says the following: chip0 rev 1 on pci0:0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 [...] vr0 rev 6 int a irq 9 on pci0:15:0 vr0: Ethernet address: 00:a0:0c:c0:01:e7 vr0: autoneg complete, no carrier - Can you show me the output of the following: pciconf -r pci0:19:0 0xc I want to see what the latency timer setting looks like. This may be something do to with your particular PCI chipset or motherboard; unfortunately, I have only Intel systems here so it's hard to duplicate your exact setup. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 09:01:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10724 for freebsd-current-outgoing; Wed, 3 Feb 1999 09:01:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from genius.cirx.org (r00t.m1.ntu.edu.tw [140.112.240.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10712 for ; Wed, 3 Feb 1999 09:01:23 -0800 (PST) (envelope-from clkao@CirX.ORG) Received: (from clkao@localhost) by genius.cirx.org (8.9.2/8.9.1) id AAA43583; Thu, 4 Feb 1999 00:23:47 +0800 (CST) (envelope-from clkao@CirX.ORG) Date: Thu, 4 Feb 1999 00:23:47 +0800 (CST) Message-Id: <199902031623.AAA43583@genius.cirx.org> X-Authentication-Warning: genius.cirx.org: clkao set sender to clkao@CirX.ORG using -f From: Chia-liang Kao To: wpaul@skynet.ctr.columbia.edu CC: current@FreeBSD.ORG In-reply-to: <199902031613.LAA06847@skynet.ctr.columbia.edu> (message from Bill Paul on Wed, 3 Feb 1999 11:12:59 -0500 (EST)) Subject: Re: problem with vr0 References: <199902031613.LAA06847@skynet.ctr.columbia.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Bill Paul * Date: Wed, 3 Feb 1999 11:12:59 -0500 (EST) * * What kind of machine/CPU does your friend have? my friend's: CPU: Pentium II (233.86-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x634 Stepping=4 Features=0x80f9ff chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x01 on pci0.4.0 ide_pci0: rev 0x01 on pci0.4.1 chip3: rev 0x01 on pci0.4.3 vr0: rev 0x06 int a irq 10 on pci0.11.0 vr0: Ethernet address: 00:80:c8:ef:3c:3f vr0: autoneg complete, link status good (half-duplex, 10Mbps) Mine: CPU: Pentium/P54C (133.64-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf chip0: rev 0x01 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 vr0: rev 0x06 int a irq 12 on pci0.19.0 vr0: Ethernet address: 00:80:c8:ef:82:09 vr0: autoneg complete, link status good (half-duplex, 10Mbps) * Hm. I have some more questions: * * - In your first posting, you mentioned this: * vr0: rev 0x06 int a irq 12 on pci0.19.0 * IRQ 12 is normally used by the mouse (if you have a PS/2 mouse). Do you * have a mouse or PS/2 mouse port on this machine? (I suspect you don't but * I have to ask.) No, I use a mouse connected to com port. Actually we thought of the problem caused by irq conflicts, and we made sure it wasn't happening. It is very strange that when I used the incorporated diagnose program, I can connect to my friend's dfe530, running the same program. * - How many PCI bus slots does your machine have? I have 3 PCI bus slots. It's quite an old machine. * - Have you tried putting the vr0 card in a different slot? Have you tried * putting it in the slot where the de0 card is now? Yes, I had previously done exactly the same test you mentioned. * - What PCI chipset do you have? The test machine in which I currently have * my sample VIA Rhine card installed is an Intel Pentium 200 system that * says the following: As you can see in the top of this mail, my chipset configuration seemed to be identical as yours. * - Can you show me the output of the following: * * pciconf -r pci0:19:0 0xc * * I want to see what the latency timer setting looks like. It shows `0x00002008' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 09:11:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12581 for freebsd-current-outgoing; Wed, 3 Feb 1999 09:11:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12539 for ; Wed, 3 Feb 1999 09:10:50 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.2/8.9.2) with ESMTP id RAA04184 for ; Wed, 3 Feb 1999 17:10:39 GMT Message-ID: <36B8830E.A9BDD32D@tdx.co.uk> Date: Wed, 03 Feb 1999 17:10:38 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: LD problems... (Pilot error no doubt) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a 4.0-current system which has been upgraded from 3.0-current... I keep getting errors such as: /usr/libexec/ld-elf.so.1: Shared object "libmysqlclient.so.5.2" not found (There are numerous other ones for other libraries)... This stops anything that's in '/etc/rc.d' from starting (e.g. Apache, Samba, Squid etc.) If I manually run the /etc/rc.d/ contents after the machine has come up it all works fine... I'm guessing I've missed something - but I can't figure what? - As far as I can see ldconfig has no config file on FreeBSd, and it's confusing me (doesn't take much)... If I run 'ldconfig -elf -R -v' I get no output... If I run 'ldconfig -aout -R -v' I get a stream of all the libraries it found... Any help gratefuly received (as always :-) -Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 09:48:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18220 for freebsd-current-outgoing; Wed, 3 Feb 1999 09:48:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18206 for ; Wed, 3 Feb 1999 09:48:19 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id MAA25858; Wed, 3 Feb 1999 12:48:13 -0500 (EST) Date: Wed, 3 Feb 1999 12:48:13 -0500 (EST) Message-Id: <199902031748.MAA25858@highwind.com> From: HighWind Software Information To: current@FreeBSD.ORG Subject: 3.0 vs 4.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can someone summarize the difference and locations between all these things? I've heard of: 2.2.8-stable 3.0-stable 3.0-current 3.0-release 4.0-current Where are all these things? Some in source? Some in binary? I've just been grabbing the things in "pub/FreeBSD" on current.freebsd.org. I assume those are daily builds of 3.0-stable. Is it still true that "2.2.8" is the thing that folks get when they go to the www.freebsd.org website and grab the "the latest stable thing"? I've been on this list for a while and there doesn't seem to be a document anywhere saying what any of this is. It is quite confusing. An explanation would be incredibly appreciated. -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 09:57:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19831 for freebsd-current-outgoing; Wed, 3 Feb 1999 09:57:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net ([207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19824 for ; Wed, 3 Feb 1999 09:57:19 -0800 (PST) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id JAA14012; Wed, 3 Feb 1999 09:57:18 -0800 (PST) Date: Wed, 3 Feb 1999 09:57:18 -0800 (PST) From: "Steven P. Donegan" To: current@FreeBSD.ORG Subject: Location of 4.0-current? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Where might I find 4.0 - I've got another development machine available for some thrashing. TIA. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 10:24:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25050 for freebsd-current-outgoing; Wed, 3 Feb 1999 10:24:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25043 for ; Wed, 3 Feb 1999 10:24:40 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id KAA18864 for ; Wed, 3 Feb 1999 10:24:39 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id KAA17077 for current@freebsd.org; Wed, 3 Feb 1999 10:24:38 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 03 Feb 1999 10:24:38 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: current@FreeBSD.ORG Subject: OBJLINK=yes breaks make buildworld Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Make buildworld is broken for the OBJLINK=yes case, and it may have been broken for quite some time. When the a.out legacy libraries are built, the object files end up in the source tree, because the "obj" links no longer point to the right place. Furthermore, these object files don't get removed when you do a make clean or a make cleandir. I don't have a fix. I never use OBJLINK. As far as I'm concerned, a suitable fix would be to eliminate that option altogether. This is the cause of one kind of libpam build failure, namely the one that ends like this: /usr/src/lib/libpam/libpam/../modules/pam_cleartext_pass_ok/libpam_cleartext_pas s_ok.a: object /usr/src/lib/libpam/libpam/../mo dules/pam_cleartext_pass_ok/libpam_cleartext_pass_ok.a(pam_cleartext_pass_ok.o) in archive is not object *** Error code 1 Thanks to Jon Hamilton for suggesting the OBJLINK connection. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 10:41:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27674 for freebsd-current-outgoing; Wed, 3 Feb 1999 10:41:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27669 for ; Wed, 3 Feb 1999 10:40:59 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id KAA18945; Wed, 3 Feb 1999 10:40:51 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id KAA17142; Wed, 3 Feb 1999 10:40:51 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 03 Feb 1999 10:40:51 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: current@FreeBSD.ORG Subject: libpam related buildworld failures Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There have been some reports of builds failing in libpam. With help from Jon Hamilton, I've narrowed down the causes. There are at least two different failure modes, but the solution is the same in either case. * Don't define OBJLINK. It is badly broken, and a libpam build failure happens to be the first symptom you're likely to see. * Don't define NOCLEAN. * Scan your entire source tree and make sure there are no symbolic links named "obj" there. Remove any that you find. * Scan your source tree under "/usr/src/lib/libpam" and make sure there are no symbolic links at all. Remove any that you find. * Scan your source tree under "/usr/src/lib/libpam" and make sure there are no files with names matching "*.[oa]" or "*.?o" there. Remove any that you find. Don't assume that a "make clean" or "make cleandir" will remove the files above. Check manually using "find". Once your source tree is cleaned up, if you avoid using OBJLINK, it will stay clean. Note, these problems have nothing to do with libpam. It's just the thing that's getting clobbered by polluted source trees resulting from unrelated breakage. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 10:53:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00317 for freebsd-current-outgoing; Wed, 3 Feb 1999 10:53:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00268 for ; Wed, 3 Feb 1999 10:53:42 -0800 (PST) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id NAA47768; Wed, 3 Feb 1999 13:53:28 -0500 (EST) Date: Wed, 3 Feb 1999 13:53:28 -0500 (EST) From: John Fieber To: HighWind Software Information cc: current@FreeBSD.ORG Subject: Re: 3.0 vs 4.0 In-Reply-To: <199902031748.MAA25858@highwind.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 3 Feb 1999, HighWind Software Information wrote: > Can someone summarize the difference and locations between all these > things? Think of it as a tree where the trunk is -current and branches are -stable. There is only one -current but potentally many -stables. Each release with a new major version number creates a new branch. Old branches, starved for light, eventually wither and die. current | | | stable | | | 3.1 | | stable | / | | / 2.2.8 | / | |/ 2.2.7 | 3.0 | | 2.2.6 | | | \ | 2.1 \ | \ | \| 2.0 | | 2.2.8-release is (supposedly) the end of the line for the 2.2 branch of FreeBSD but critical bugs continue to be fixed and they show up in the 2.2.8-stable branch. You can get binary "snapshots" of this branch to pick up the bug fixes, or you can get the source and "make world" to get them. Call 2.2.8-stable the "trailing edge". 3.0-stable is is the actively maintained stable branch from which the next release (3.1) will come. The primary activity on this--or any stable branch--is bug fixes rather than new features, although new features will appear over time. Call 3.0-stable the "cutting edge". There is only one -current at any given time and the version number just indicates what the next major release will be. Since there is only one, it is usually just called "-current" and this is where exciting new features and bugs are introduced to FreeBSD. Call -current the "bleeding edge". > Is it still true that "2.2.8" is the thing that folks get when they go > to the www.freebsd.org website and grab the "the latest stable thing"? Speaking only for myself, I'd say that is correct. Once 3.1 comes out, then I would say 3.1 is "the latest stable thing". I'm not sure that *any* dot zero release should be considered stable. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 11:28:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06982 for freebsd-current-outgoing; Wed, 3 Feb 1999 11:28:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06970 for ; Wed, 3 Feb 1999 11:28:52 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id LAA19192 for ; Wed, 3 Feb 1999 11:28:50 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id LAA17206 for current@freebsd.org; Wed, 3 Feb 1999 11:28:49 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 03 Feb 1999 11:28:49 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: current@FreeBSD.ORG Subject: Quick vm_map_insert() question Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hopefully somebody who knows the VM system better than I do can answer this easily. In "sys/kern/imgact_elf.c", vm_map_insert() is used to map the segments of an ELF file. In all of the calls, the address of the mapping is specified explicitly. I'd like to experiment with letting the system choose the address itself for the ELF dynamic linker. In other words, I want it to be mapped just as if a userland call to mmap(0, ...) had been done. Can somebody tell me how to do that? Thanks, John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 11:32:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07834 for freebsd-current-outgoing; Wed, 3 Feb 1999 11:32:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07815 for ; Wed, 3 Feb 1999 11:32:32 -0800 (PST) (envelope-from brdean@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id OAA06224 for ; Wed, 3 Feb 1999 14:32:26 -0500 (EST) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA13564; Wed, 3 Feb 1999 14:32:24 -0500 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.1/8.9.1) id OAA01903; Wed, 3 Feb 1999 14:32:24 -0500 (EST) (envelope-from brdean) From: Brian Dean Message-Id: <199902031932.OAA01903@dean.pc.sas.com> Subject: aio_read panics SMP kernel To: freebsd-current@FreeBSD.ORG Date: Wed, 3 Feb 1999 14:32:24 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm using a dual 350MHz Dell Precision 410 with 4.0-19990130-SNAP (SMP enabled) to prototype a program that uses asynchronous read and write (aio_read() and aio_write()), and found that the following simple and not very useful program (it's for demonstration purposes only!) causes the system to do one of three things: 1) panic - "page fault in the kernel" ... I don't have any other specifics, I will follow up with the details provided by the console as soon as I can make this occur again (I should have written it down the first time). 2) reset - no panic or anything, just a system reset and subsequent reboot 3) hang - everything totally unresponsive, machine does not respond to pings or anything else, no keyboard response. Below, please find the output of 'mptable' for the SMP experts and the program that I used to cause the panic. Any help on fixing this and/or suggestions on what I might be doing wrong are much appreciated. Thanks, -Brian -- Brian Dean Process Engineering brdean@unx.sas.com Following is the output of 'mpinfo' on this machine: [root@mrose]:/brdean- mptable =============================================================================== MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000fe710 signature: '_MP_' length: 16 bytes version: 1.4 checksum: 0x91 mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f0000 signature: 'PCMP' base table length: 468 version: 1.4 checksum: 0x33 OEM ID: 'DELL ' Product ID: 'WS 410 ' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 50 local APIC address: 0xfee00000 extended table length: 0 extended table checksum: 0 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 0 0x11 BSP, usable 6 5 2 0x183fbff 1 0x11 AP, usable 6 5 2 0x183fbff -- Bus: Bus ID Type 0 PCI 1 PCI 2 PCI 3 ISA -- I/O APICs: APIC ID Version State Address 2 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT active-hi edge 3 0 2 0 INT conforms conforms 3 1 2 1 INT conforms conforms 3 0 2 2 INT conforms conforms 3 3 2 3 INT conforms conforms 3 4 2 4 INT conforms conforms 3 5 2 5 INT conforms conforms 3 6 2 6 INT conforms conforms 3 7 2 7 INT conforms conforms 3 8 2 8 INT conforms conforms 3 9 2 9 INT conforms conforms 3 10 2 10 INT conforms conforms 3 11 2 11 INT conforms conforms 3 12 2 12 INT conforms conforms 3 14 2 14 INT conforms conforms 3 15 2 15 INT conforms conforms 0 13:A 2 16 INT conforms conforms 0 14:D 2 16 INT conforms conforms 0 16:B 2 16 INT conforms conforms 1 0:A 2 16 INT conforms conforms 2 6:C 2 16 INT conforms conforms 2 9:D 2 16 INT conforms conforms 0 13:B 2 17 INT conforms conforms 0 14:A 2 17 INT conforms conforms 0 16:C 2 17 INT conforms conforms 1 0:B 2 17 INT conforms conforms 2 6:D 2 17 INT conforms conforms 2 9:A 2 17 INT conforms conforms 0 13:C 2 18 INT conforms conforms 0 14:B 2 18 INT conforms conforms 0 16:D 2 18 INT conforms conforms 2 6:A 2 18 INT conforms conforms 2 9:B 2 18 INT conforms conforms 2 10:A 2 18 INT conforms conforms 2 14:A 2 18 INT conforms conforms 0 7:D 2 19 INT conforms conforms 0 13:D 2 19 INT conforms conforms 0 14:C 2 19 INT conforms conforms 0 16:A 2 19 INT conforms conforms 0 17:A 2 19 INT conforms conforms 2 6:B 2 19 INT conforms conforms 2 9:C 2 19 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT active-hi edge 3 0 255 0 NMI active-hi edge 3 0 255 1 ------------------------------------------------------------------------------- # SMP kernel config file options: # Required: options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional (built-in defaults will work in most cases): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=41 # number of INTs =============================================================================== And here is the simple program to demonstrate the panic: #include #include #include #include #include #include #define BUFLEN 4096 char * progname; int main ( int argc, char * argv [] ) { int rc, fd; char buf [ BUFLEN ]; char * fname; int done; aiocb_t cb = { 0 }; long long unsigned int pollcount; progname = rindex ( argv[0], '/' ); if (progname == NULL) progname = argv[0]; else progname++; if (argc != 2) { fprintf ( stderr, "Usage: %s InputFile\n", progname ); exit(1); } fname = argv[1]; fd = open ( fname, O_RDONLY ); if (fd < 0) { fprintf ( stderr, "%s: can't open %s for reading: %s\n", progname, fname, strerror(errno) ); exit(1); } cb.aio_fildes = fd; cb.aio_offset = 0; cb.aio_buf = buf; cb.aio_nbytes = BUFLEN; done = 0; while (!done) { rc = aio_read ( &cb ); if (rc) { fprintf ( stderr, "%s: aio_read(): %s\n", progname, strerror(errno) ); exit(1); } fprintf ( stderr, "%s: aio_read() OK, polling for completion ...\n", progname ); pollcount = 0; while (aio_error(&cb)==EINPROGRESS) pollcount++; fprintf ( stderr, "%s: polling completed, count = %qu\n", progname, pollcount ); rc = aio_return ( &cb ); if (rc < 0) { fprintf ( stderr, "%s: aio_return([read]): %s\n", progname, strerror(errno) ); exit(1); } else if (rc == 0) { done = 1; } else { cb.aio_offset += rc; } } return 0; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 12:32:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17533 for freebsd-current-outgoing; Wed, 3 Feb 1999 12:30:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17523 for ; Wed, 3 Feb 1999 12:30:46 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id MAA00912; Wed, 3 Feb 1999 12:29:55 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma000908; Wed, 3 Feb 99 12:29:34 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id MAA25871; Wed, 3 Feb 1999 12:29:34 -0800 (PST) From: Archie Cobbs Message-Id: <199902032029.MAA25871@bubba.whistle.com> Subject: Re: KLD confusion.. In-Reply-To: <199902030719.XAA00601@dingo.cdrom.com> from Mike Smith at "Feb 2, 99 11:19:52 pm" To: mike@smith.net.au (Mike Smith) Date: Wed, 3 Feb 1999 12:29:34 -0800 (PST) Cc: julian@whistle.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > > Take the following scenario: > > > > compiled in: module A > > > > kldstat -v shows module 'A' > > > > kldload A > > damned thing succeeds. > > That's correct. There's a fundamental problem here in that there's a > confusion between file names and module names. This is a basic flaw in > the way that KLD was implemented (no offense to Doug; it was initially > meant to be a better LKM, not necessarily a whole new ball of wax). > > I've taken about four different runs at a "right" way of doing this > subsequently. I think that, with some help and advice from Doug and > Peter, I'm on the right track now, but there's no hope of it being > ready for 3.1. This may be oversimplifying, but why wouldn't this work: just do everything at the module level: - All dependencies are inter-*module* dependencies. - Only one *module* with the same name can be loaded at one time. - KLD files (eg, foo.ko) are simply containers for one or more modules. We'd take the conservative stance on loading: if you tried to kldload foo.ko, it would fail unless *all* the modules in it were successfully able to link & load. It seems if you just make consistent what the atomic unit of linking is (is it a file?? it is a module??) then all will be well. We just have to make sure we have unique names for all modules as we do now for files. Now, there remains the problem of how do you find the file foo.ko containing module "bar", eg, if you want to auto-load dependencies? For starters, we could just assert that only module "foo" can be found this way. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 12:32:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17715 for freebsd-current-outgoing; Wed, 3 Feb 1999 12:32:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17708 for ; Wed, 3 Feb 1999 12:32:53 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id MAA00973; Wed, 3 Feb 1999 12:31:55 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma000969; Wed, 3 Feb 99 12:31:53 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id MAA25882; Wed, 3 Feb 1999 12:31:53 -0800 (PST) From: Archie Cobbs Message-Id: <199902032031.MAA25882@bubba.whistle.com> Subject: Re: make port and bsd.port.mk In-Reply-To: from Steve O'Hara-Smith at "Feb 3, 99 11:52:58 am" To: steveo@iol.ie (Steve O'Hara-Smith) Date: Wed, 3 Feb 1999 12:31:53 -0800 (PST) Cc: rbezuide@oskar.nanoteq.co.za, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve O'Hara-Smith writes: > > There is no /usr/ports/Mk directory on my machine > > Where can I find these files or is it a bug ?? > > cvsup your ports and all will be well. I'm curious what the reason for moving the includes to /usr/ports/Mk was.. is this to insure better consistency? That would make sense. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 12:50:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20099 for freebsd-current-outgoing; Wed, 3 Feb 1999 12:50:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20070 for ; Wed, 3 Feb 1999 12:50:14 -0800 (PST) (envelope-from brooks@one-eyed-alien.net) From: brooks@one-eyed-alien.net Received: from localhost (brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) with ESMTP id MAA27018; Wed, 3 Feb 1999 12:49:21 -0800 (PST) X-Authentication-Warning: orion.ac.hmc.edu: brdavis owned process doing -bs Date: Wed, 3 Feb 1999 12:49:21 -0800 (PST) X-Sender: brdavis@orion.ac.hmc.edu To: Archie Cobbs cc: "Steve O'Hara-Smith" , rbezuide@oskar.nanoteq.co.za, freebsd-current@FreeBSD.ORG Subject: Re: make port and bsd.port.mk In-Reply-To: <199902032031.MAA25882@bubba.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 3 Feb 1999, Archie Cobbs wrote: > Steve O'Hara-Smith writes: > > > There is no /usr/ports/Mk directory on my machine > > > Where can I find these files or is it a bug ?? > > > > cvsup your ports and all will be well. > > I'm curious what the reason for moving the includes to /usr/ports/Mk > was.. is this to insure better consistency? That would make sense. It makes since to me, but I'm a little confused about the timing of this change. It was rather annoying to update my 2.2.8-STABLE machine a day or two after being told that cvsuping ports on a 2.2 machine might cause breakage (re: the no more 2.2 support announcement) to find that *not* cvsuping ports broke my ports collection because the makefiles moved to /usr/ports/Mk. Don't get me wrong, I like the change, but the timing seems less the perfect. -- Brooks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 12:54:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20847 for freebsd-current-outgoing; Wed, 3 Feb 1999 12:54:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20837 for ; Wed, 3 Feb 1999 12:54:11 -0800 (PST) (envelope-from alc@cs.rice.edu) Received: from nonpc.cs.rice.edu (nonpc.cs.rice.edu [128.42.1.219]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id OAA23358; Wed, 3 Feb 1999 14:54:04 -0600 (CST) Received: (from alc@localhost) by nonpc.cs.rice.edu (8.9.2/8.7.3) id OAA06592; Wed, 3 Feb 1999 14:54:04 -0600 (CST) Date: Wed, 3 Feb 1999 14:54:04 -0600 From: Alan Cox To: jdp@polstra.com Cc: current@FreeBSD.ORG Subject: Re: Quick vm_map_insert() question Message-ID: <19990203145404.D3714@nonpc.cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Look at vm_map_find. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 13:15:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23680 for freebsd-current-outgoing; Wed, 3 Feb 1999 13:15:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from h24-64-221-247.gv.wave.shaw.ca ([24.64.221.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23612 for ; Wed, 3 Feb 1999 13:15:14 -0800 (PST) (envelope-from jake@h24-64-221-247.gv.wave.shaw.ca) Received: from h24-64-221-247.gv.wave.shaw.ca (localhost [127.0.0.1]) by h24-64-221-247.gv.wave.shaw.ca (8.9.2/8.9.2) with ESMTP id NAA73189 for ; Wed, 3 Feb 1999 13:15:05 -0800 (PST) (envelope-from jake@h24-64-221-247.gv.wave.shaw.ca) Message-Id: <199902032115.NAA73189@h24-64-221-247.gv.wave.shaw.ca> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: rc.conf needs updating Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Feb 1999 13:15:04 -0800 From: Jake Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a note that rc.conf needs updating. --- rc.conf.orig Wed Feb 3 13:10:46 1999 +++ rc.conf Wed Feb 3 13:12:54 1999 @@ -195,7 +195,7 @@ kern_securelevel_enable="NO" # kernel security level (see init(8)), kern_securelevel="-1" # range: -1..3 ; `-1' is the most insecure update_motd="YES" # update version info in /etc/motd (or NO) -vinum_slices="" # put in names of vinum slices to enable vinum +vinum_drives="" # put in names of vinum drives to enable vinum ############################################################## ### Allow local configuration override at the very end here ## Cheers! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 13:30:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26235 for freebsd-current-outgoing; Wed, 3 Feb 1999 13:30:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA26228 for ; Wed, 3 Feb 1999 13:30:33 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id QAA07284; Wed, 3 Feb 1999 16:37:16 -0500 From: Bill Paul Message-Id: <199902032137.QAA07284@skynet.ctr.columbia.edu> Subject: Re: problem with vr0 To: clkao@CirX.ORG (Chia-liang Kao) Date: Wed, 3 Feb 1999 16:37:14 -0500 (EST) Cc: current@FreeBSD.ORG In-Reply-To: <199902031623.AAA43583@genius.cirx.org> from "Chia-liang Kao" at Feb 4, 99 00:23:47 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Chia-liang Kao had to walk into mine and say: [chop] > * - Can you show me the output of the following: > * > * pciconf -r pci0:19:0 0xc > * > * I want to see what the latency timer setting looks like. > It shows `0x00002008' Hmm... Alright, I have a patch I'd like you to try. I don't know that this will really have an effect, but I'm curious to see what it does. If this doesn't work, then the only other thing I can think of is if you can give me login access to your machine so that I can try some experiments. Anyway, to apply the patch, do the following: - Save this message to /tmp/vr.patch (or something similar). - Become root. - Type the following: # cd /sys/pci # patch < /tmp/vr.patch - Compile a new kernel and boot it. Let me know if this has any effect on the card's behavior. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= *** ../CVSWORK/sys_pci/if_vr.c Mon Feb 1 16:25:52 1999 --- if_vr.c Wed Feb 3 16:11:24 1999 *************** *** 899,905 **** vm_offset_t pbase, vbase; #endif u_char eaddr[ETHER_ADDR_LEN]; ! u_int32_t command; struct vr_softc *sc; struct ifnet *ifp; int media = IFM_ETHER|IFM_100_TX|IFM_FDX; --- 899,905 ---- vm_offset_t pbase, vbase; #endif u_char eaddr[ETHER_ADDR_LEN]; ! u_int32_t command, lat; struct vr_softc *sc; struct ifnet *ifp; int media = IFM_ETHER|IFM_100_TX|IFM_FDX; *************** *** 988,993 **** --- 988,1002 ---- goto fail; } + /* bump up the latency timer a little */ + command = pci_conf_read(config_id, VR_PCI_LATENCY_TIMER); + lat = (command & 0x0000FF00) >> 8; + if (lat < 64) { + command &= 0xFFFF00FF; + command |= 0x00004000; + pci_conf_write(config_id, VR_PCI_LATENCY_TIMER, command); + } + /* Reset the adapter. */ vr_reset(sc); *************** *** 1675,1680 **** --- 1684,1692 ---- VR_CLRBIT(sc, VR_TXCFG, VR_TXCFG_TX_THRESH); VR_SETBIT(sc, VR_TXCFG, VR_TXTHRESH_STORENFWD); + + /* Adjust configuration a little */ + CSR_WRITE_2(sc, VR_BCR0, 0x0006); /* Init circular RX list. */ if (vr_list_rx_init(sc) == ENOBUFS) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 14:00:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00875 for freebsd-current-outgoing; Wed, 3 Feb 1999 14:00:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00864 for ; Wed, 3 Feb 1999 14:00:22 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id XAA17661; Wed, 3 Feb 1999 23:00:06 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.2/8.9.1) id UAA01297; Wed, 3 Feb 1999 20:31:33 +0100 (CET) (envelope-from son) Message-ID: <19990203203133.12975@breizh.prism.uvsq.fr> Date: Wed, 3 Feb 1999 20:31:33 +0100 From: Nicolas Souchu To: Matthew Thyer Cc: current@FreeBSD.ORG Subject: Re: How do I query system temperature probes ? References: <36B7CED1.96D4B369@dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <36B7CED1.96D4B369@dsto.defence.gov.au>; from Matthew Thyer on Wed, Feb 03, 1999 at 02:51:37PM +1030 X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 03, 1999 at 02:51:37PM +1030, Matthew Thyer wrote: > >I seem to have all the hardware required for querying the temperature >probes in the system (At least I can do it from the BIOS). > >How can I query this info ? > >I assume I need "controller smbus0" and "controller intpm0" in my >kernel. But do I also need "device smb0 at smbus?" and/or any >of the following: > ># ic i2c network interface ># iic i2c standard io ># iicsmb i2c to smb bridge. Allow i2c i/o with smb commands. You need: controller intpm0 # the PIIX4 interface controller smbus0 # the SMBus system device smb0 at smbus? # user access to the SMBus > > >Once I have all this stuff in my kernel, what commands do I use to >query the probes ?? Takanori Watanabe as example code to do this. > >My system is FreeBSD 4.0-CURRENT (of CTM 3722 - but will soon be really >-CURRENT) > > >Extract from dmesg: > >chip0: rev 0x03 on >pci0.0.0 >chip1: rev 0x03 on >pci0.1.0 >chip2: rev 0x01 on pci0.7.0 >ide_pci0: rev 0x01 on pci0.7.1 >chip3: rev 0x01 on pci0.7.3 >-- > Matthew Thyer Phone: +61 8 8259 7249 > Corporate Information Systems Fax: +61 8 8259 5537 > Defence Science and Technology Organisation, Salisbury > PO Box 1500 Salisbury South Australia 5108 > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 14:00:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00932 for freebsd-current-outgoing; Wed, 3 Feb 1999 14:00:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00927 for ; Wed, 3 Feb 1999 14:00:34 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id XAA25876; Wed, 3 Feb 1999 23:00:12 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.2/8.9.1) id UAA01239; Wed, 3 Feb 1999 20:17:56 +0100 (CET) (envelope-from son) Message-ID: <19990203201756.60738@breizh.prism.uvsq.fr> Date: Wed, 3 Feb 1999 20:17:56 +0100 From: Nicolas Souchu To: Stephen Palmer Cc: freebsd-current@FreeBSD.ORG Subject: Re: ppbus0: MEDIA CPIA_1-20 References: <19990203021539.24793.qmail@ww183.netaddress.usa.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <19990203021539.24793.qmail@ww183.netaddress.usa.net>; from Stephen Palmer on Wed, Feb 03, 1999 at 02:15:39AM +0000 X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 03, 1999 at 02:15:39AM +0000, Stephen Palmer wrote: > >While looking at the output from dmesg, I noticed the following >which I don't remember having seen before. (Of course I might >not have had the camera hooked up to this system while running >FreeBSD before ;-) Sure, this is really new. > >Probing for PnP devices on ppbus0: >ppbus0: MEDIA CPIA_1-20 What it means: the parallel port bus system - ppbus - probes the parallel port in order to detect eventually an IEEE1284 (parallel port standard released in 1994) compliant device. So your camera is IEEE1284 compliant because ppbus could enter the NIBBLE-get_device_id mode and retrieve PnP info from it. The line before tells you something like "IEEE1284 device found..." with the available IEEE1284 modes supported by your device. > >This is actualy a "Zoom/Video Cam PPC" which I use under Win98 >from time to time. Any chance of getting working images from >this device under FreeBSD-current? How would I go about this? The link protocol is supported by FreeBSD, this is what the IEEE1284 stuff is for. But you'll also need info about higher protocols of the device to drive it correctly. (1) The device is really simple and a 'cat' from the parallel port in any of the supported modes is enough. That would suppose the camera dumps pictures to the port as they are captured. Of course, you should guess the format. This is the case with printers supporting IEEE1284: cat /dev/lpt0 gives printer info (READY, OUT OF PAPER...). If NIBBLE mode is supported by your device, which is not certain if I remember well your logs, you can try cat /dev/lpt0. Otherwise we'll have to hack ppi(4) to give it a try.. (2) The device is more complicated and an analyser under windows may give you the magic sequence to enter plain reverse mode to retrieve pictures as they are captured. > >This system is not currently very current (Jan 14, 1999 / no pun >intended) but I'm cvsup'ing as I type this... > >Stephen L. Palmer >slpalmer@netscape.net > Nicholas. > >____________________________________________________________________ >More than just email--Get your FREE Netscape WebMail account today at http://home.netscape.com/netcenter/mail > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 14:26:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05636 for freebsd-current-outgoing; Wed, 3 Feb 1999 14:26:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (pm3-13.ppp.wenet.net [206.15.85.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05587 for ; Wed, 3 Feb 1999 14:26:14 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.2/8.9.1) with ESMTP id OAA01911; Wed, 3 Feb 1999 14:23:08 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Wed, 3 Feb 1999 14:23:08 -0800 (PST) From: Alex Zepeda To: John Polstra cc: current@FreeBSD.ORG Subject: Re: libpam related buildworld failures In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Speaking of pam, when will it be fixed to support all the various service types? Or is that a do it yourself project? - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 14:34:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06866 for freebsd-current-outgoing; Wed, 3 Feb 1999 14:34:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA06857 for ; Wed, 3 Feb 1999 14:34:44 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id OAA20227; Wed, 3 Feb 1999 14:34:42 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id OAA17656; Wed, 3 Feb 1999 14:34:42 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 03 Feb 1999 14:34:42 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Alex Zepeda Subject: Re: libpam related buildworld failures Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Zepeda wrote: > Speaking of pam, when will it be fixed to support all the various service > types? Or is that a do it yourself project? As you know, questions of the form "when will X happen" rarely get useful answers around here. So here's my useless answer: "When it's finished." :-) I'm working on it as fast as my available time permits. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 14:37:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07285 for freebsd-current-outgoing; Wed, 3 Feb 1999 14:37:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (pm3-13.ppp.wenet.net [206.15.85.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07277 for ; Wed, 3 Feb 1999 14:37:44 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.2/8.9.1) with ESMTP id OAA02222; Wed, 3 Feb 1999 14:34:47 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Wed, 3 Feb 1999 14:34:47 -0800 (PST) From: Alex Zepeda To: John Polstra cc: current@FreeBSD.ORG Subject: Re: libpam related buildworld failures In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 3 Feb 1999, John Polstra wrote: > Alex Zepeda wrote: > > Speaking of pam, when will it be fixed to support all the various service > > types? Or is that a do it yourself project? > > As you know, questions of the form "when will X happen" rarely get > useful answers around here. So here's my useless answer: "When it's > finished." :-) I'm working on it as fast as my available time permits. Well I should have rephrased that. I was curious if anyone knew about it or was working on it. What exactly needs to be done here (I know next to nothing about pam)? - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 14:43:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08519 for freebsd-current-outgoing; Wed, 3 Feb 1999 14:43:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08513 for ; Wed, 3 Feb 1999 14:43:17 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.2) with ESMTP id OAA13459; Wed, 3 Feb 1999 14:43:55 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: John Polstra cc: current@FreeBSD.ORG Subject: Re: OBJLINK=yes breaks make buildworld In-reply-to: Your message of "Wed, 03 Feb 1999 10:24:38 PST." Date: Wed, 03 Feb 1999 14:43:55 -0800 Message-ID: <13455.918081835@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Make buildworld is broken for the OBJLINK=yes case, and it may have > been broken for quite some time. When the a.out legacy libraries are > built, the object files end up in the source tree, because the "obj" > links no longer point to the right place. Furthermore, these object > files don't get removed when you do a make clean or a make cleandir. > > I don't have a fix. I never use OBJLINK. As far as I'm concerned, a > suitable fix would be to eliminate that option altogether. As far as I'm concerned, and speaking as the author of that hack, I agree with you! :-) Kill it. Kill it dead. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 14:50:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09012 for freebsd-current-outgoing; Wed, 3 Feb 1999 14:48:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09005 for ; Wed, 3 Feb 1999 14:48:05 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id OAA20307; Wed, 3 Feb 1999 14:48:04 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id OAA17704; Wed, 3 Feb 1999 14:48:03 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 03 Feb 1999 14:48:03 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Alex Zepeda Subject: Re: libpam related buildworld failures Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Zepeda wrote: > > Well I should have rephrased that. I was curious if anyone knew about it > or was working on it. What exactly needs to be done here (I know next to > nothing about pam)? Well, if by "service types" you meant login, ftp, telnet, etc., then what needs to be done is to convert ftpd, telnetd, etc. to use PAM instead of doing their own authentication. For ftpd that will require a few relatively minor PAM module fixes having to do with the fact that FTP as viewed from the server is sort of an event-driven machine rather than an interactive conversation. That's what my near-term focus is on. If you instead meant things like support for RADIUS accounting, that's just waiting for somebody to come along and implement the necessary support in libradius and the corresponding PAM module. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 14:53:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09726 for freebsd-current-outgoing; Wed, 3 Feb 1999 14:53:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (pm3-13.ppp.wenet.net [206.15.85.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09709 for ; Wed, 3 Feb 1999 14:53:17 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.2/8.9.1) with ESMTP id OAA02414; Wed, 3 Feb 1999 14:50:20 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Wed, 3 Feb 1999 14:50:20 -0800 (PST) From: Alex Zepeda To: John Polstra cc: current@FreeBSD.ORG Subject: Re: libpam related buildworld failures In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No I meant service as in authentication types or tasks whatever ya call it. From the man page: PAM separates the tasks of authentication into four inde- pendent management groups: account management; authentica- tion management; password management; and session manage- ment. (We highlight the abbreviations used for these groups in the configuration file.) authentication works.. but everything else gives unresolved (or defined) symbols... so kdm, xdm, and samba don't work with pam on FreeBSD (well those are the ones I've tried). - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 15:00:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10825 for freebsd-current-outgoing; Wed, 3 Feb 1999 15:00:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10808 for ; Wed, 3 Feb 1999 15:00:06 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id PAA20372; Wed, 3 Feb 1999 15:00:04 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id PAA17752; Wed, 3 Feb 1999 15:00:02 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 03 Feb 1999 15:00:02 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Alex Zepeda Subject: Re: libpam related buildworld failures Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Zepeda wrote: > No I meant service as in authentication types or tasks whatever ya call > it. From the man page: Well, "service type" is a specific term in PAM that refers to things like "login", "ftp", "ppp", and so forth. > PAM separates the tasks of authentication into four inde- > pendent management groups: account management; authentica- > tion management; password management; and session manage- > ment. (We highlight the abbreviations used for these > groups in the configuration file.) > > > authentication works.. but everything else gives unresolved (or defined) > symbols... so kdm, xdm, and samba don't work with pam on FreeBSD (well > those are the ones I've tried). That's what I meant by: If you instead meant things like support for RADIUS accounting, that's just waiting for somebody to come along and implement the necessary support in libradius and the corresponding PAM module. I'm going to work now. Gotta keep food on the table. Bye! :-) John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 15:02:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11093 for freebsd-current-outgoing; Wed, 3 Feb 1999 15:02:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [206.205.41.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA11061 for ; Wed, 3 Feb 1999 15:02:02 -0800 (PST) (envelope-from adrian@lorax.ubergeeks.com) Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [206.205.41.241]) by lorax.ubergeeks.com (8.8.8/8.8.8) with SMTP id SAA04100; Wed, 3 Feb 1999 18:02:06 -0500 (EST) (envelope-from adrian@lorax.ubergeeks.com) Date: Wed, 3 Feb 1999 18:02:06 -0500 (EST) From: ADRIAN Filipi-Martin Reply-To: Adrian Filipi-Martin To: Tomoyoshi ASANO cc: freebsd-current@FreeBSD.ORG Subject: Re: About /usr/mdec/cdboot In-Reply-To: <36B42676158.488EASA@mail.use-net.co.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 31 Jan 1999, Tomoyoshi ASANO wrote: > When CD booting, some error messages is displayed. > And I tested other machines supported atapi-cdrom booting. > > > (In /usr/sys/i386/boot/cdboot/boot.c) > > Your BIOS int 0x13 extensions seem to be disabled. > > It's impossible to boot a CD-ROM without them. > > (BIOS int 0x13 fn 0x4b01 yielded error ?) > > I'm sorry I don't know 0x13 extensions. > Is /usr/mdec/cdrom supported atapi-cdrom booting ? Check that your BIOS is enabled. It's talking about hooking into the BIOS disk IO routines such that they can access the SCSI device. If you can boot from a hard disk on this controller, then you should be able to boot from a CD-ROM on the same controller, if it supports CD-ROM booting at all. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 15:09:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12113 for freebsd-current-outgoing; Wed, 3 Feb 1999 15:09:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (pm3-13.ppp.wenet.net [206.15.85.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12096 for ; Wed, 3 Feb 1999 15:09:00 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.2/8.9.1) with ESMTP id PAA02557; Wed, 3 Feb 1999 15:05:58 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Wed, 3 Feb 1999 15:05:58 -0800 (PST) From: Alex Zepeda To: John Polstra cc: current@FreeBSD.ORG Subject: Re: libpam related buildworld failures In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 3 Feb 1999, John Polstra wrote: > That's what I meant by: > > If you instead meant things like support for RADIUS accounting, > that's just waiting for somebody to come along and implement the > necessary support in libradius and the corresponding PAM module. No. I don't want/need radious support. kdm and samba only do password authentication AFAIK, why they don't use the "auth" method (or whatever) I don't know. They work without Radius and without Pam.. but that doesn't fix the underlying problem.... > I'm going to work now. Gotta keep food on the table. Bye! :-) Have fun! ;) - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 15:26:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15523 for freebsd-current-outgoing; Wed, 3 Feb 1999 15:26:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mta2.iol.it (mta2.iol.it [195.210.91.152]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA14885 for ; Wed, 3 Feb 1999 15:23:20 -0800 (PST) (envelope-from ugo@dsi.unifi.it) Received: from dsi.unifi.it ([212.52.71.243]) by mta2.iol.it (Netscape Messaging Server 3.6) with ESMTP id AAA1414 for ; Thu, 4 Feb 1999 00:22:29 +0100 Received: from pegasus.home.net (pegasus.home.net [192.168.1.3]) by dsi.unifi.it (8.9.2/8.9.2) with ESMTP id SAA07420; Wed, 3 Feb 1999 18:45:04 +0100 (CET) (envelope-from ugo) Received: (from ugo@localhost) by pegasus.home.net (8.9.2/8.9.2) id SAA39598; Wed, 3 Feb 1999 18:45:04 +0100 (CET) (envelope-from ugo) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <199901301728.TAA00662@ceia.nordier.com> Date: Wed, 03 Feb 1999 18:45:04 +0100 (CET) Organization: Not an organization From: Ugo Paternostro To: Robert Nordier Subject: Re: Reading a text file with BTX Cc: freebsd-current@FreeBSD.ORG, (Daniel C. Sobral) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Jan-99 Robert Nordier wrote about "Re: Reading a text file with BTX": > Daniel C. Sobral wrote: >> Robert Nordier wrote: >> > >> > Daniel C. Sobral wrote: >> > > >> > > Y'know, in my computer that F5 is "Drive 0", and the system will not >> > > boot unless I select it first. Selecting it, makes the OSes boot and >> > > F5 disappear. >> >> Right on the mark. BTW, my BIOS is set so the cd drive is searched >> before the hd on boot. Could that be the cause? > > Seems a reasonable assumption, but I don't know for sure. It is. > Robert Nordier Bye, UP To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 15:27:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15699 for freebsd-current-outgoing; Wed, 3 Feb 1999 15:27:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kong.dorms.spbu.ru (kong.dorms.spbu.ru [195.19.252.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15693 for ; Wed, 3 Feb 1999 15:26:58 -0800 (PST) (envelope-from kong@kong.dorms.spbu.ru) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.9.2/0.0.1/kong) with ESMTP id CAA63768 for ; Thu, 4 Feb 1999 02:26:27 +0300 (MSK) (envelope-from kong@kong.dorms.spbu.ru) Date: Thu, 4 Feb 1999 02:26:27 +0300 (MSK) From: Hostas Red To: current@FreeBSD.ORG Subject: make world: fail Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! At least for a week now i can't make world with following message: ===> sys/modules/syscons/logo make: don't know how to make /usr/src/sys/modules/syscons/logo/@/i386/isa/videoio.h. Stop *** Error code 2 Stop. *** Error code 1 ... What i'm getting wrong? Maybe i've missed something? Adios, /KONG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 15:41:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18185 for freebsd-current-outgoing; Wed, 3 Feb 1999 15:41:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.kar.net (n181.cdialup.kar.net [195.178.130.181]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18161 for ; Wed, 3 Feb 1999 15:41:02 -0800 (PST) (envelope-from kushn@mail.kar.net) Received: from localhost (volodya@localhost) by mail.kar.net (8.9.2/8.8.8) with ESMTP id BAA62863; Thu, 4 Feb 1999 01:39:46 +0200 (EET) (envelope-from kushn@mail.kar.net) Date: Thu, 4 Feb 1999 01:39:45 +0200 (EET) From: Vladimir Kushnir X-Sender: volodya@kushnir.kiev.ua To: Hostas Red cc: current@FreeBSD.ORG Subject: Re: make world: fail In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 4 Feb 1999, Hostas Red wrote: > Hi! > > At least for a week now i can't make world with following message: > > ===> sys/modules/syscons/logo > make: don't know how to make > /usr/src/sys/modules/syscons/logo/@/i386/isa/videoio.h. Stop > *** Error code 2 > > Stop. > *** Error code 1 > > ... > > What i'm getting wrong? Maybe i've missed something? cd /usr/src/sys/modules/syscons/logo make cleandepend Did you compile this module before? That's the remnants. > > Adios, > /KONG > Regards, Vladimir ===========================|======================= Vladimir Kushnir | kushn@mail.kar.net, | Powered by FreeBSD kushnir@ap3.bitp.kiev.ua | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 16:21:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27450 for freebsd-current-outgoing; Wed, 3 Feb 1999 16:21:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-60-dbn.dial-up.net [196.34.155.124]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27439 for ; Wed, 3 Feb 1999 16:21:16 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id CAA20072; Thu, 4 Feb 1999 02:20:09 +0200 (SAT) From: Robert Nordier Message-Id: <199902040020.CAA20072@ceia.nordier.com> Subject: Re: Reading a text file with BTX In-Reply-To: from Ugo Paternostro at "Feb 3, 99 06:45:04 pm" To: paterno@dsi.unifi.it (Ugo Paternostro) Date: Thu, 4 Feb 1999 02:20:06 +0200 (SAT) Cc: rnordier@nordier.com, freebsd-current@FreeBSD.ORG, dcs@newsguy.com 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ugo Paternostro wrote: > On 30-Jan-99 Robert Nordier wrote about "Re: Reading a text file with BTX": > > Daniel C. Sobral wrote: > >> Robert Nordier wrote: > >> > > >> > Daniel C. Sobral wrote: > >> > > > >> > > Y'know, in my computer that F5 is "Drive 0", and the system will not > >> > > boot unless I select it first. Selecting it, makes the OSes boot and > >> > > F5 disappear. > >> > >> Right on the mark. BTW, my BIOS is set so the cd drive is searched > >> before the hd on boot. Could that be the cause? > > > > Seems a reasonable assumption, but I don't know for sure. > > It is. Proof? -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 16:25:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28042 for freebsd-current-outgoing; Wed, 3 Feb 1999 16:25:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28002 for ; Wed, 3 Feb 1999 16:25:01 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA02534; Thu, 4 Feb 1999 10:54:57 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id KAA63774; Thu, 4 Feb 1999 10:54:55 +1030 (CST) Date: Thu, 4 Feb 1999 10:54:55 +1030 From: Greg Lehey To: Jake Cc: current@FreeBSD.ORG Subject: Re: rc.conf needs updating Message-ID: <19990204105455.S1179@freebie.lemis.com> References: <199902032115.NAA73189@h24-64-221-247.gv.wave.shaw.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199902032115.NAA73189@h24-64-221-247.gv.wave.shaw.ca>; from Jake on Wed, Feb 03, 1999 at 01:15:04PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 3 February 1999 at 13:15:04 -0800, Jake wrote: > Just a note that rc.conf needs updating. > > --- rc.conf.orig Wed Feb 3 13:10:46 1999 > +++ rc.conf Wed Feb 3 13:12:54 1999 > @@ -195,7 +195,7 @@ > kern_securelevel_enable="NO" # kernel security level (see init(8)), > kern_securelevel="-1" # range: -1..3 ; `-1' is the most insecure > update_motd="YES" # update version info in /etc/motd (or NO) > -vinum_slices="" # put in names of vinum slices to enable vinum > +vinum_drives="" # put in names of vinum drives to enable vinum > > ############################################################## > ### Allow local configuration override at the very end here ## Oops. Thanks for prodding me. It's done now. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 17:17:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04850 for freebsd-current-outgoing; Wed, 3 Feb 1999 17:17:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA04840 for ; Wed, 3 Feb 1999 17:17:52 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id UAA06455; Wed, 3 Feb 1999 20:17:48 -0500 (EST) Date: Wed, 3 Feb 1999 20:17:48 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Matthew Dillon cc: current@FreeBSD.ORG Subject: Re: Heads up: comitted optimization to vm_map_insert() In-Reply-To: <199902030515.VAA43044@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 2 Feb 1999, Matthew Dillon wrote: > I've comitted an optimization to vm_map_insert() after initial > tests seemed to indicate that it works. Basically it allows > OBJT_SWAP objects to be optimized in addition to OBJT_DEFAULT > objects already optimized in certain specific cases. > > However, a followup test that I had never run before had a > temporary seg-fault ( i.e. it didn't repeat when I re-ran > the test ). I think the seg fault may have revealed a new > bug and is not related to the optimization I comitted, so I > haven't backed out the commit. I am not 100% sure though, > and I am testing this now. What test? If we had this exact test, it could be exploiting the exact bug, could it not? I'll let you know of any weird crashes in previously stable programs. > > If anyone notices weird seg-faulting that didn't occur before > tonight, please notify me! Will do! CPU_WT_ALLOC actually seemed to have caused instability before... > > -Matt > Matthew Dillon > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 17:20:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05292 for freebsd-current-outgoing; Wed, 3 Feb 1999 17:20:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from speed.rcc.on.ca (radio163.mipps.net [205.189.197.163] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA05285 for ; Wed, 3 Feb 1999 17:20:25 -0800 (PST) (envelope-from oscentral@usa.net) Received: from a20.my.intranet ([207.164.233.98]) by speed.rcc.on.ca (8.6.12/8.6.9) with SMTP id VAA15630 for ; Wed, 3 Feb 1999 21:30:35 -0500 From: Rod Taylor To: freebsd-current@FreeBSD.ORG Subject: Network Cards Date: Wed, 3 Feb 1999 20:19:07 -0500 X-Mailer: KMail [version 1.0.9] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99020320193400.08377@a20.my.intranet> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've often wondered this, but why is it that every network card has a different 'name'. xl0, rl0, vr0, ed0, etc. etc. etc I tried simlinking them to a common name (I have xl0, rl0, and ed0 active in my current machine). linked to eth0, eth1, eth2 (didn't work). However, it would be nice if they all had a common name to the end user.. Primarily, me.. Especially when you rip out one card, install another, then the name changes on you... -- Rod Taylor Proud Member of Team OS/2 User of FreeBSD & KDE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 17:40:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08122 for freebsd-current-outgoing; Wed, 3 Feb 1999 17:40:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08078 for ; Wed, 3 Feb 1999 17:40:01 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id RAA06551 for freebsd-current@freebsd.org; Wed, 3 Feb 1999 17:40:00 -0800 (PST) From: Archie Cobbs Message-Id: <199902040140.RAA06551@bubba.whistle.com> Subject: Boot block problem To: freebsd-current@FreeBSD.ORG Date: Wed, 3 Feb 1999 17:39:59 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just upgraded to 3.0-stable snapshot circa 2/1 and noticed that the new "booteasy" does not seem to remember the selection from the previous time. Eg., I need to press F5 to get to disk 2 but it always defaults to F2 (which is FreeBSD slice containing only a swap partition). This means my box won't reboot automatically anymore, e.g., if the power goes out. Is this a new bug or a new feature? :-) Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 17:55:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10193 for freebsd-current-outgoing; Wed, 3 Feb 1999 17:55:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10179 for ; Wed, 3 Feb 1999 17:55:18 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id UAA09674; Wed, 3 Feb 1999 20:59:38 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Wed, 3 Feb 1999 20:59:38 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Rod Taylor cc: freebsd-current@FreeBSD.ORG Subject: Re: Network Cards In-Reply-To: <99020320193400.08377@a20.my.intranet> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 3 Feb 1999, Rod Taylor wrote: > I've often wondered this, but why is it that every network card has a different > 'name'. > > xl0, rl0, vr0, ed0, etc. etc. etc > > I tried simlinking them to a common name (I have xl0, rl0, and ed0 active in my > current machine). linked to eth0, eth1, eth2 (didn't work). look at /etc/rc* , try to formulate something like rc.conf where you define internet interfaces like: eth0 = "xl0" look at rc.firewall for better examples. > However, it would be nice if they all had a common name to the end user.. > Primarily, me.. Especially when you rip out one card, install another, then > the name changes on you... ifconfig -a Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 4.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 18:50:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20697 for freebsd-current-outgoing; Wed, 3 Feb 1999 18:50:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20675 for ; Wed, 3 Feb 1999 18:50:27 -0800 (PST) (envelope-from rock@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.2/1999010400) with ESMTP id DAA18474 for ; Thu, 4 Feb 1999 03:50:23 +0100 (CET) Received: from wurzelausix (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.2/1999010400) with ESMTP id DAA24816 for ; Thu, 4 Feb 1999 03:50:22 +0100 (CET) Received: from vodix.aremorika (vodix [134.96.247.43]) by wurzelausix (8.9.1/wjp/19980821) with ESMTP id DAA22709 for ; Thu, 4 Feb 1999 03:50:22 +0100 (CET) From: "D. Rock" Received: by vodix.aremorika; Thu, 4 Feb 1999 03:50:21 +0100 (MET) Date: Thu, 4 Feb 1999 03:50:21 +0100 (MET) Message-Id: <199902040250.DAA01966@vodix.aremorika> To: current@FreeBSD.ORG Subject: locale errors Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While browsing through some directories I noticed an annoying error in locale based sorting. My LANG is set to de_DE.ISO_8859-1 Sorting treats "ss" as a single character instead of two. This leads to some interesting (at least) errors in displaying sorted output. My locale is set do de_DE.ISO_8859-1, not de_DE.ASCII If I type 2 characters ss, I mean 2 characters ss. If I type ß I mean the single character ß. This sorting behaviour is just wrong. Not every apperence of "ss" even in pure ASCII does mean "ß". I suggest removing any multi character definition out of the collate files. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 18:52:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20988 for freebsd-current-outgoing; Wed, 3 Feb 1999 18:52:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20928 for ; Wed, 3 Feb 1999 18:51:53 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA12241 for ; Wed, 3 Feb 1999 21:51:56 -0500 (EST) Date: Wed, 3 Feb 1999 21:51:56 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@FreeBSD.ORG Subject: various -CURRENT nits Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got a few patches today; let's see: The TCB hash check is broken, because ffs() returns offsets starting at 1, not 0. Some of VoxWare doesn't compile. In addition, if anyone thinks it should be done, should I make PQ_L[12]_SIZE config(8) tuneable (individually, not via PQ_FOOCACHE)? I use different values because I have a K6-2 (8+8 pages L1) that does not match PQ_L1_SIZE. I'd also like to readd the comment that CPU_WT_ALLOC might not be stable on a K6-2, because it actually _doesn't_ seem to be stable here. The fixes to the two problems follow. Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ --- src/sys/netinet/tcp_subr.c.orig Wed Feb 3 21:40:42 1999 +++ src/sys/netinet/tcp_subr.c Wed Feb 3 21:42:17 1999 @@ -136,8 +136,8 @@ tcbinfo.listhead = &tcb; if (!(getenv_int("net.inet.tcp.tcbhashsize", &hashsize))) hashsize = TCBHASHSIZE; - if ((1 << ffs(hashsize)) != hashsize) { - printf("WARNING: TCB hash size not a power of 2\n"); + if ((1 << (ffs(hashsize) - 1)) != hashsize) { + printf("WARNING: TCB hash size (%d) not a power of 2\n", hashsize); hashsize = 512; /* safe default */ } tcbinfo.hashbase = hashinit(hashsize, M_PCB, &tcbinfo.hashmask); --- src/sys/i386/isa/sound/os.h.orig Wed Feb 3 20:51:52 1999 +++ src/sys/i386/isa/sound/os.h Wed Feb 3 20:51:47 1999 @@ -18,6 +18,7 @@ #include #include #include +#include #include To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 19:04:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA23523 for freebsd-current-outgoing; Wed, 3 Feb 1999 19:04:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nagual.pp.ru (nagual.pp.ru [193.125.27.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA23401; Wed, 3 Feb 1999 19:03:55 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.2/8.9.2) id GAA41316; Thu, 4 Feb 1999 06:03:50 +0300 (MSK) (envelope-from ache) Date: Thu, 4 Feb 1999 06:03:49 +0300 From: "Andrey A. Chernov" To: "D. Rock" Cc: current@FreeBSD.ORG, joerg@FreeBSD.ORG Subject: Re: locale errors Message-ID: <19990204060349.A40565@nagual.pp.ru> References: <199902040250.DAA01966@vodix.aremorika> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.1i In-Reply-To: <199902040250.DAA01966@vodix.aremorika>; from rock@wurzelausix.CS.Uni-SB.DE on Thu, Feb 04, 1999 at 03:50:21AM +0100 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 04, 1999 at 03:50:21AM +0100, D. Rock wrote: > Sorting treats "ss" as a single character instead of two. This leads > to some interesting (at least) errors in displaying sorted output. > > My locale is set do de_DE.ISO_8859-1, not de_DE.ASCII > If I type 2 characters ss, I mean 2 characters ss. If I type ß I > mean the single character ß. > This sorting behaviour is just wrong. Not every apperence of "ss" > even in pure ASCII does mean "ß". > > I suggest removing any multi character definition out of the collate > files. It was Joerg initiative, I don't know DE enough to judge here. Please resolve this problem with him (CC'ed). -- Andrey A. Chernov ache@null.net MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 19:23:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27127 for freebsd-current-outgoing; Wed, 3 Feb 1999 19:23:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles240.castles.com [208.214.165.240]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27114 for ; Wed, 3 Feb 1999 19:23:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id TAA10987; Wed, 3 Feb 1999 19:19:35 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902040319.TAA10987@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Archie Cobbs cc: freebsd-current@FreeBSD.ORG Subject: Re: Boot block problem In-reply-to: Your message of "Wed, 03 Feb 1999 17:39:59 PST." <199902040140.RAA06551@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Feb 1999 19:19:34 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just upgraded to 3.0-stable snapshot circa 2/1 and noticed that > the new "booteasy" does not seem to remember the selection from > the previous time. Eg., I need to press F5 to get to disk 2 but > it always defaults to F2 (which is FreeBSD slice containing > only a swap partition). > > This means my box won't reboot automatically anymore, e.g., if > the power goes out. > > Is this a new bug or a new feature? :-) It's supposed to work, and it does for me here. Check you haven't got your BIOS 'boot virus protection' stuff enabled, then talk to Robert Nordier (in that order 8). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 19:53:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03116 for freebsd-current-outgoing; Wed, 3 Feb 1999 19:53:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley-185-205.res.iastate.edu (friley-185-205.res.iastate.edu [129.186.185.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03102 for ; Wed, 3 Feb 1999 19:53:08 -0800 (PST) (envelope-from ccsanady@friley-185-205.res.iastate.edu) Received: from friley-185-205.res.iastate.edu (localhost.res.iastate.edu [127.0.0.1]) by friley-185-205.res.iastate.edu (Postfix) with ESMTP id EEA306 for ; Wed, 3 Feb 1999 21:53:05 -0600 (CST) X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: How many people use VI? This is unbelievable.. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Feb 1999 21:53:05 -0600 From: Chris Csanady Message-Id: <19990204035306.EEA306@friley-185-205.res.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I unfortunately have a lot of data to type in, and to my surprise the keypad is unuseable in vi. It doesn't even work in vim. Thank god it works on Irix--I thought I would be using ee. Anyways, here is what happens when I type the digits 1-9 on the keypad while in insert mode.. y x w v u t s r q Chris Csanady To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 20:02:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05165 for freebsd-current-outgoing; Wed, 3 Feb 1999 20:02:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from veda.is (veda.is [193.4.230.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05158 for ; Wed, 3 Feb 1999 20:02:25 -0800 (PST) (envelope-from adam@veda.is) Received: (from adam@localhost) by veda.is (8.9.0/8.9.0) id EAA23386 for freebsd-current@freebsd.org; Thu, 4 Feb 1999 04:02:23 GMT From: Adam David Message-Id: <199902040402.EAA23386@veda.is> Subject: clock / timer running very slow? To: freebsd-current@FreeBSD.ORG Date: Thu, 4 Feb 1999 04:02:22 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After upgrading 3.0-RELEASE to -stable I noticed various time related things have been acting strange. Obviously one of the timers is running extremely slow, since effects have been observed such as: reported ping times are about 35 times shorter than actual values. 'date' increments at a rate of one or two seconds per minute. 'shutdown -r now' announces the shutdown about a minute later and 'reboot' seems to hang indefinitely requiring Ctrl-Alt-Del to sync the disks. So I tried upgrading to 4.0-current and it still misbehaves in this way. Is this a known problem? Any ideas? This is an AMD K5-PR90 with VIA chipset, world compiled -O2 and kernel compiled -O without options MATH_EMULATE or FAILSAFE if that makes any difference. -- Adam David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 20:11:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06730 for freebsd-current-outgoing; Wed, 3 Feb 1999 20:11:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA06703 for ; Wed, 3 Feb 1999 20:11:21 -0800 (PST) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.9.1a/8.9.1) id PAA10065; Thu, 4 Feb 1999 15:11:02 +1100 (EST) Message-ID: <19990204151101.K28430@rf900.physics.usyd.edu.au> Date: Thu, 4 Feb 1999 15:11:01 +1100 From: David Dawes To: Chris Csanady , freebsd-current@FreeBSD.ORG Subject: Re: How many people use VI? This is unbelievable.. References: <19990204035306.EEA306@friley-185-205.res.iastate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990204035306.EEA306@friley-185-205.res.iastate.edu>; from Chris Csanady on Wed, Feb 03, 1999 at 09:53:05PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 03, 1999 at 09:53:05PM -0600, Chris Csanady wrote: >I unfortunately have a lot of data to type in, and to my surprise >the keypad is unuseable in vi. It doesn't even work in vim. Thank >god it works on Irix--I thought I would be using ee. > >Anyways, here is what happens when I type the digits 1-9 on the >keypad while in insert mode.. > >y >x >w >v >u >t >s >r >q You don't say what terminal emulator you're using, but with xterm, the "application keypad" option gets enabled when entering vi, which prevents the keypad from generating numbers. You can change it once in vi with the +left-button menu. I haven't looked into this sufficiently to know the direct cause of this behaviour. Maybe it could be avoided by tuning the termcap entry? Maybe 'vi' (as the application) should interpret the sequences in the correct way? David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 20:15:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07262 for freebsd-current-outgoing; Wed, 3 Feb 1999 20:15:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07245 for ; Wed, 3 Feb 1999 20:15:24 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.1a/8.9.1) id WAA12066; Wed, 3 Feb 1999 22:15:16 -0600 (CST) Message-ID: <19990203221516.T16540@futuresouth.com> Date: Wed, 3 Feb 1999 22:15:16 -0600 From: "Matthew D. Fuller" To: Chris Csanady , freebsd-current@FreeBSD.ORG Subject: Re: How many people use VI? This is unbelievable.. References: <19990204035306.EEA306@friley-185-205.res.iastate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990204035306.EEA306@friley-185-205.res.iastate.edu>; from Chris Csanady on Wed, Feb 03, 1999 at 09:53:05PM -0600 X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 03, 1999 at 09:53:05PM -0600, a little birdie told me that Chris Csanady remarked > I unfortunately have a lot of data to type in, and to my surprise > the keypad is unuseable in vi. It doesn't even work in vim. Thank > god it works on Irix--I thought I would be using ee. > > Anyways, here is what happens when I type the digits 1-9 on the > keypad while in insert mode.. That's not a function of vi, that's a function of your terminal. Lemme guess; xterm, right? If I start vi in console mode, works fine. >From a raw xterm, no dice. I haven't tracked down what precisely is causing it to roll over and start twitching under X because it doesn't bug me that much, but it may you. --- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller http://www.over-yonder.net/~fullermd | * fullermd@futuresouth.com fullermd@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | "The only reason I'm burning my candle at both ends, | * is because I haven't figured out how to light the * | middle yet" | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 20:16:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07505 for freebsd-current-outgoing; Wed, 3 Feb 1999 20:16:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07463 for ; Wed, 3 Feb 1999 20:16:16 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id PAA14815; Thu, 4 Feb 1999 15:18:43 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199902040418.PAA14815@cimlogic.com.au> Subject: Re: How many people use VI? This is unbelievable.. In-Reply-To: <19990204035306.EEA306@friley-185-205.res.iastate.edu> from Chris Csanady at "Feb 3, 1999 9:53: 5 pm" To: ccsanady@friley-185-205.res.iastate.edu (Chris Csanady) Date: Thu, 4 Feb 1999 15:18:42 +1100 (EST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Csanady wrote: > I unfortunately have a lot of data to type in, and to my surprise > the keypad is unuseable in vi. It doesn't even work in vim. Thank > god it works on Irix--I thought I would be using ee. > > Anyways, here is what happens when I type the digits 1-9 on the > keypad while in insert mode.. FWIW, this message is being edited with vi on a 2.2.8-STABLE machine rlogged in from a dxterm running on an OSF/1 box. The keyboard is one of DEC's LK401 things with the funny "Do" keys etc from back when VAX was just a twinkle in PDP's eye. I have TERM=vt100 in my FreeBSD environment, dxterm configured with the "Numeric Keypad" option checked and vt100 emulation, so keypad keys are 0.123456789, just like you'd expect. It's not vi that's the problem, just your termcap setting doesn't match the keyboard. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 20:20:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08479 for freebsd-current-outgoing; Wed, 3 Feb 1999 20:20:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08452 for ; Wed, 3 Feb 1999 20:20:51 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id OAA03565; Thu, 4 Feb 1999 14:50:44 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id OAA65295; Thu, 4 Feb 1999 14:50:43 +1030 (CST) Date: Thu, 4 Feb 1999 14:50:43 +1030 From: Greg Lehey To: John Birrell Cc: Chris Csanady , freebsd-current@FreeBSD.ORG Subject: Re: How many people use VI? This is unbelievable.. Message-ID: <19990204145043.H1179@freebie.lemis.com> References: <19990204035306.EEA306@friley-185-205.res.iastate.edu> <199902040418.PAA14815@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199902040418.PAA14815@cimlogic.com.au>; from John Birrell on Thu, Feb 04, 1999 at 03:18:42PM +1100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 4 February 1999 at 15:18:42 +1100, John Birrell wrote: > Chris Csanady wrote: >> I unfortunately have a lot of data to type in, and to my surprise >> the keypad is unuseable in vi. It doesn't even work in vim. Thank >> god it works on Irix--I thought I would be using ee. >> >> Anyways, here is what happens when I type the digits 1-9 on the >> keypad while in insert mode.. > > FWIW, this message is being edited with vi on a 2.2.8-STABLE machine > rlogged in from a dxterm running on an OSF/1 box. The keyboard is one > of DEC's LK401 things with the funny "Do" keys etc from back when VAX > was just a twinkle in PDP's eye. I have TERM=vt100 in my FreeBSD > environment, dxterm configured with the "Numeric Keypad" option checked > and vt100 emulation, so keypad keys are 0.123456789, just like you'd > expect. It's not vi that's the problem, just your termcap setting doesn't > match the keyboard. Correct, and he doesn't say what he's using, but I see that I have problems with both vi and terminal Emacs when using an xterm. Emacs goes crazy: it's obviously interpreting the keypad entries as commands. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 20:22:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08839 for freebsd-current-outgoing; Wed, 3 Feb 1999 20:22:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08827 for ; Wed, 3 Feb 1999 20:22:31 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id UAA82246; Wed, 3 Feb 1999 20:22:28 -0800 (PST) (envelope-from dillon) Date: Wed, 3 Feb 1999 20:22:28 -0800 (PST) From: Matthew Dillon Message-Id: <199902040422.UAA82246@apollo.backplane.com> To: Brian Feldman Cc: current@FreeBSD.ORG Subject: Re: Heads up: comitted optimization to vm_map_insert() References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> the test ). I think the seg fault may have revealed a new :> bug and is not related to the optimization I comitted, so I :> haven't backed out the commit. I am not 100% sure though, :> and I am testing this now. : : What test? If we had this exact test, it could be exploiting the exact bug, :could it not? I'll let you know of any weird crashes in previously stable :programs. My "do lots of things that force the machine to page up the wazoo and try to make it crash" test :-) -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 20:27:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09787 for freebsd-current-outgoing; Wed, 3 Feb 1999 20:27:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley-185-205.res.iastate.edu (friley-185-205.res.iastate.edu [129.186.185.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09776 for ; Wed, 3 Feb 1999 20:27:17 -0800 (PST) (envelope-from ccsanady@friley-185-205.res.iastate.edu) Received: from friley-185-205.res.iastate.edu (localhost.res.iastate.edu [127.0.0.1]) by friley-185-205.res.iastate.edu (Postfix) with ESMTP id 8C4E76; Wed, 3 Feb 1999 22:27:15 -0600 (CST) X-Mailer: exmh version 2.0.2 2/24/98 To: David Dawes Cc: freebsd-current@FreeBSD.ORG Subject: Re: How many people use VI? This is unbelievable.. In-reply-to: Your message of "Thu, 04 Feb 1999 15:11:01 +1100." <19990204151101.K28430@rf900.physics.usyd.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Feb 1999 22:27:15 -0600 From: Chris Csanady Message-Id: <19990204042715.8C4E76@friley-185-205.res.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Wed, Feb 03, 1999 at 09:53:05PM -0600, Chris Csanady wrote: >>I unfortunately have a lot of data to type in, and to my surprise >>the keypad is unuseable in vi. It doesn't even work in vim. Thank >>god it works on Irix--I thought I would be using ee. >> >>Anyways, here is what happens when I type the digits 1-9 on the >>keypad while in insert mode.. >> >>y >>x >>w >>v >>u >>t >>s >>r >>q > >You don't say what terminal emulator you're using, but with xterm, the >"application keypad" option gets enabled when entering vi, which prevents >the keypad from generating numbers. You can change it once in vi with >the +left-button menu. I haven't looked into this sufficiently >to know the direct cause of this behaviour. Maybe it could be avoided >by tuning the termcap entry? Maybe 'vi' (as the application) should >interpret the sequences in the correct way? This was using the xterm termcap entry. Although when I login to other machines running DU4.0 or Irix6, vi works without touching anything. Regardless, I would be inclined to blame this on our vi. I don't understand much about tercap entries, but this certainly violates POLA. :( So does this mean that the default xterm entry should be different? Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 20:55:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA13904 for freebsd-current-outgoing; Wed, 3 Feb 1999 20:55:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13858 for ; Wed, 3 Feb 1999 20:54:48 -0800 (PST) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.9.1a/8.9.1) id PAA10340; Thu, 4 Feb 1999 15:54:37 +1100 (EST) Message-ID: <19990204155437.N28430@rf900.physics.usyd.edu.au> Date: Thu, 4 Feb 1999 15:54:37 +1100 From: David Dawes To: Chris Csanady Cc: freebsd-current@FreeBSD.ORG Subject: Re: How many people use VI? This is unbelievable.. References: <19990204151101.K28430@rf900.physics.usyd.edu.au> <19990204042715.8C4E76@friley-185-205.res.iastate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990204042715.8C4E76@friley-185-205.res.iastate.edu>; from Chris Csanady on Wed, Feb 03, 1999 at 10:27:15PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 03, 1999 at 10:27:15PM -0600, Chris Csanady wrote: > >>On Wed, Feb 03, 1999 at 09:53:05PM -0600, Chris Csanady wrote: >>>I unfortunately have a lot of data to type in, and to my surprise >>>the keypad is unuseable in vi. It doesn't even work in vim. Thank >>>god it works on Irix--I thought I would be using ee. >>> >>>Anyways, here is what happens when I type the digits 1-9 on the >>>keypad while in insert mode.. >>> >>>y >>>x >>>w >>>v >>>u >>>t >>>s >>>r >>>q >> >>You don't say what terminal emulator you're using, but with xterm, the >>"application keypad" option gets enabled when entering vi, which prevents >>the keypad from generating numbers. You can change it once in vi with >>the +left-button menu. I haven't looked into this sufficiently >>to know the direct cause of this behaviour. Maybe it could be avoided >>by tuning the termcap entry? Maybe 'vi' (as the application) should >>interpret the sequences in the correct way? > >This was using the xterm termcap entry. Although when I login to other >machines running DU4.0 or Irix6, vi works without touching anything. >Regardless, I would be inclined to blame this on our vi. I don't >understand much about tercap entries, but this certainly violates POLA. :( > >So does this mean that the default xterm entry should be different? OK, I've looked into it a little now. It is the ks sequence, which is defined to set the cursor keys and the keypad to "application" mode in both the FreeBSD (3.0-stable as of a week ago) and XFree86 3.3.3.1 versions of the xterm termcap entries. In the FreeBSD case, it ends up falling back to the vt100 entry for this. Here are the definitions: ks=\E[?1h\E=:ke=\E[?1l\E>: \E[?1h sets the cursor keys to application mode \E= sets the keypad to application mode Maybe xterm could use a "keksInhibit" resource like the titeInhibit resource? David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 21:47:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19471 for freebsd-current-outgoing; Wed, 3 Feb 1999 21:47:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19464 for ; Wed, 3 Feb 1999 21:47:50 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id VAA03576; Wed, 3 Feb 1999 21:46:11 -0800 (PST) From: Archie Cobbs Message-Id: <199902040546.VAA03576@bubba.whistle.com> Subject: Re: make port and bsd.port.mk In-Reply-To: <199902031149.NAA26926@oskar.nanoteq.co.za> from Reinier Bezuidenhout at "Feb 3, 99 01:49:13 pm" To: rbezuide@oskar.nanoteq.co.za (Reinier Bezuidenhout) Date: Wed, 3 Feb 1999 21:46:11 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Reinier Bezuidenhout writes: > In the new system ... I get the following error : > > "/usr/share/mk/bsd.port.mk", line 2: Could not find /usr/ports/Mk/bsd.port.mk > make: fatal errors encountered -- cannot continue You just need to update or install /usr/ports/Mk, which contains the current ports stuff. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 22:06:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21151 for freebsd-current-outgoing; Wed, 3 Feb 1999 22:06:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21140 for ; Wed, 3 Feb 1999 22:06:38 -0800 (PST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from dsto-ms2.dsto.defence.gov.au (dsto-ms2.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id QAA13231 for ; Thu, 4 Feb 1999 16:33:42 +1030 (CST) Received: from exchsa1.dsto.defence.gov.au (unverified [131.185.2.94]) by dsto-ms2.dsto.defence.gov.au (Integralis SMTPRS 2.0.15) with ESMTP id ; Thu, 04 Feb 1999 16:10:58 +1030 Received: from fang.dsto.defence.gov.au ([131.185.2.5]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id 1CHABH9G; Thu, 4 Feb 1999 11:01:28 +1030 Received: from dsto.defence.gov.au (fuzz.dsto.defence.gov.au [131.185.75.229]) by fang.dsto.defence.gov.au (8.8.5/8.8.5) with ESMTP id LAA29828; Thu, 4 Feb 1999 11:00:44 +1030 (CST) Message-Id: <36B8EA32.D5105294@dsto.defence.gov.au> Date: Thu, 04 Feb 1999 11:00:42 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Nicolas Souchu , Takanori Watanabe Cc: current@FreeBSD.ORG Subject: Re: How do I query system temperature probes ? References: <36B7CED1.96D4B369@dsto.defence.gov.au> <19990203203133.12975@breizh.prism.uvsq.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks, Takanori, are you going to commit your example code in say /usr/src/share/examples/smbus ? If not can you send me a copy please ? Nicolas Souchu wrote: > > On Wed, Feb 03, 1999 at 02:51:37PM +1030, Matthew Thyer wrote: > > > >I seem to have all the hardware required for querying the temperature > >probes in the system (At least I can do it from the BIOS). > > > >How can I query this info ? > > > >I assume I need "controller smbus0" and "controller intpm0" in my > >kernel. But do I also need "device smb0 at smbus?" and/or any > >of the following: > > > ># ic i2c network interface > ># iic i2c standard io > ># iicsmb i2c to smb bridge. Allow i2c i/o with smb commands. > > You need: > > controller intpm0 # the PIIX4 interface > controller smbus0 # the SMBus system > device smb0 at smbus? # user access to the SMBus > > > > > > >Once I have all this stuff in my kernel, what commands do I use to > >query the probes ?? > > Takanori Watanabe as example > code to do this. > > > > >My system is FreeBSD 4.0-CURRENT (of CTM 3722 - but will soon be really > >-CURRENT) > > > > > >Extract from dmesg: > > > >chip0: rev 0x03 on > >pci0.0.0 > >chip1: rev 0x03 on > >pci0.1.0 > >chip2: rev 0x01 on pci0.7.0 > >ide_pci0: rev 0x01 on pci0.7.1 > >chip3: rev 0x01 on pci0.7.3 > >-- > > Matthew Thyer Phone: +61 8 8259 7249 > > Corporate Information Systems Fax: +61 8 8259 5537 > > Defence Science and Technology Organisation, Salisbury > > PO Box 1500 Salisbury South Australia 5108 > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-current" in the body of the message > > > > -- > nsouch@teaser.fr / nsouch@freebsd.org > FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 22:43:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24793 for freebsd-current-outgoing; Wed, 3 Feb 1999 22:43:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24784 for ; Wed, 3 Feb 1999 22:43:10 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id HAA12620; Thu, 4 Feb 1999 07:43:03 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id HAA06996; Thu, 4 Feb 1999 07:38:13 +0100 (MET) (envelope-from j) Message-ID: <19990204073812.49101@uriah.heep.sax.de> Date: Thu, 4 Feb 1999 07:38:12 +0100 From: J Wunsch To: "Andrey A. Chernov" Cc: "D. Rock" , current@FreeBSD.ORG Subject: Re: locale errors Reply-To: Joerg Wunsch References: <199902040250.DAA01966@vodix.aremorika> <19990204060349.A40565@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.88 In-Reply-To: <19990204060349.A40565@nagual.pp.ru>; from Andrey A. Chernov on Thu, Feb 04, 1999 at 06:03:49AM +0300 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 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Andrey A. Chernov wrote: > > I suggest removing any multi character definition out of the collate > > files. > > It was Joerg initiative, I don't know DE enough to judge here. Please > resolve this problem with him (CC'ed). Well, not completely. :) For testing, i've restored the file from before my change, and it missorts similarly. I'm probably too stupid to understand all of this collate stuff. So far, i haven't been able to come up with any locale definition that does the right thing for every input. To make matters worse, German doesn't even have a single collate defintion at all. There are at least two dissenting definitions: one is the phonebook sorting order, and the other one (certainly more widely accepted and thus should be the base of our collate definition) the `Duden' (German dictionary). According to my Duden, the following words Maße Maßeinheit Masse Massaua Massel should be sorted like: Massaua Maße Masse Maßeinheit Massel If anybody could come up with a set of collate definition files that does this, it probably would be the right thing. ;) Maybe it's simply impossible to express using the current collate stuff? -- 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. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 23:10:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26016 for freebsd-current-outgoing; Wed, 3 Feb 1999 22:51:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26007 for ; Wed, 3 Feb 1999 22:51:22 -0800 (PST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (IDENT:MHJwv3+x1CYP5k4+0XH4UjdxQm1iY1eu@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id IAA98458 for ; Thu, 4 Feb 1999 08:51:13 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (IDENT:07Em86cRp9x+SJJI7Qjw5E52enhF9GWh@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id IAA19226 for ; Thu, 4 Feb 1999 08:51:12 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Message-Id: <199902040651.IAA19226@greenpeace.grondar.za> To: current@freebsd.org Subject: config(8) putting (null) into config files Date: Thu, 04 Feb 1999 08:51:10 +0200 From: Mark Murray Sender: owner-freebsd-current@freebsd.org Precedence: bulk X-Loop: FreeBSD.ORG Hi I am trying to get my laptop's config file as clean as possible and one of the lines I experimented with is: controller fdc0 at isa? disable port ? bio (notice the lack of an "irq" and the wildcarding of "at isa"). This results in a line in ioconf.c of: { 10, &fdcdriver, (null), 0, -1, C 0x00000, 0, 0, 0, 0x0000, 0, 0, 0, 0, 0, 0, 0 }, Notice the "(null)". I want the line in my config file to be like that as I do not use the floppy drive very often, and I am quite content for it to be kicked into action by pccardd when I plug it in. So my config line above is just a device placeholder. The "(null)" causes a compile failure, which is fixed by the kluge below. Is there a better way of doing this, or is this OK to commit? (WARNING! Cut 'n Paste alert!) Index: mkioconf.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/config/mkioconf.c,v retrieving revision 1.45 diff -u -d -r1.45 mkioconf.c --- mkioconf.c 1998/11/15 18:07:35 1.45 +++ mkioconf.c 1999/02/04 06:38:37 @@ -721,7 +721,7 @@ mp == TO_NEXUS || !eq(mp->d_name, table)) continue; fprintf(fp, "{ -1, &%3sdriver, %8s,", - mp->d_name, mp->d_port); + mp->d_name, mp->d_port ? mp->d_port : "0"); fprintf(fp, "%6s, %2d, C 0x%05X, %5d, 0, %3d, 0x%04X, %5d, 0, 0, 0, %6d, %8d, 0 },\n", sirq(mp->d_irq), mp->d_drq, mp->d_maddr, mp->d_msize, dp->d_unit, -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 23:14:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28111 for freebsd-current-outgoing; Wed, 3 Feb 1999 23:14:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA28085 for ; Wed, 3 Feb 1999 23:14:52 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 108Izy-0003Iq-00; Thu, 4 Feb 1999 00:14:50 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.2/8.8.3) with ESMTP id AAA74143; Thu, 4 Feb 1999 00:14:55 -0700 (MST) Message-Id: <199902040714.AAA74143@harmony.village.org> To: HighWind Software Information Subject: Re: 3.0 vs 4.0 Cc: current@FreeBSD.ORG In-reply-to: Your message of "Wed, 03 Feb 1999 12:48:13 EST." <199902031748.MAA25858@highwind.com> References: <199902031748.MAA25858@highwind.com> Date: Thu, 04 Feb 1999 00:14:55 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199902031748.MAA25858@highwind.com> HighWind Software Information writes: : Can someone summarize the difference and locations between all these : things? : : I've heard of: : 2.2.8-stable : 3.0-stable : 3.0-current : 3.0-release : 4.0-current : : Where are all these things? Some in source? Some in binary? I've just : been grabbing the things in "pub/FreeBSD" on current.freebsd.org. I : assume those are daily builds of 3.0-stable. 2.2.8-stable is the current name of the 2.2 "branch" of FreeBSD. It was created some time ago. This is the branch that all the 2.2.x releases came from. 2.2.8-stable means that you are on teh 2.2 branch sometime after the 2.2.8 release. 3.0-stable is the name of the 3.x branch of FreeBSD. All 3.x based releases will be based on this, except for 3.0-release. 3.0-release was based on a pre-branch version of this code. 3.0-stable is more stable than 3.0-release in many ways and is currently marching along towards a 3.1 release slated for later this month. 3.0-current is the old name for the bleeding edge. It was until recently the most up to date copy of FreeBSD that you could get. This was both good and bad depending on the day since minor problems crop up and bugs are fixed. 4.0-current is the new name for the bleeding edge. Here's an approximate graphical picture of the branches in the CVS tree: ------+- 3.0-current -----*----+#------------------------ 4.0-current \ \ \ \ 3.0 stable banch ----------------- \ \ --1--2-5-6-7-8- 2.2 stable branch [*] in the above picture is where 3.0 was release (and hence is 3.0-release). [#] in the above is where the main trunk changed its name from 3.0-current to 4.0-current. [1-8] on the 2.2 stable branch above are release points for 2.2.1R, 2.2.2R, etc. I say approximate because I've hand waved the earlier 2.x releases and the exact point that the branch was made for 2.2. It is enough to understand what is going on. The 2.2 stable branch is coming to its end of life. It is becoming more than just stable, it is effectively frozen with very few bug fixes being propigated back to it now. : Is it still true that "2.2.8" is the thing that folks get when they go : to the www.freebsd.org website and grab the "the latest stable thing"? Yes. 3.0 release had some problems, and 3.1 isn't ready. When 3.1 comes out, I'd say go for that. If it is for your personal machine, I'd be tempted to install 3.0 but be prepared to back off to 2.2.8 if there are major problems. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 3 23:31:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00523 for freebsd-current-outgoing; Wed, 3 Feb 1999 23:31:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nagual.pp.ru (nagual.pp.ru [193.125.27.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00517 for ; Wed, 3 Feb 1999 23:30:58 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.2/8.9.2) id KAA23771; Thu, 4 Feb 1999 10:30:39 +0300 (MSK) (envelope-from ache) Date: Thu, 4 Feb 1999 10:30:39 +0300 From: "Andrey A. Chernov" To: Joerg Wunsch Cc: "D. Rock" , current@FreeBSD.ORG Subject: Re: locale errors Message-ID: <19990204103038.A19952@nagual.pp.ru> References: <199902040250.DAA01966@vodix.aremorika> <19990204060349.A40565@nagual.pp.ru> <19990204073812.49101@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990204073812.49101@uriah.heep.sax.de>; from j@uriah.heep.sax.de on Thu, Feb 04, 1999 at 07:38:12AM +0100 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 04, 1999 at 07:38:12AM +0100, J Wunsch wrote: > Well, not completely. :) For testing, i've restored the file from > before my change, and it missorts similarly. I'm probably too stupid > to understand all of this collate stuff. So far, i haven't been able > to come up with any locale definition that does the right thing for > every input. I mean no particular commit but whole idea how to sort doubled letters - it comes from you, I can't invent this. Collating scheme is very simple - we have two sorting orders - primary and secondary (f.e. Posix have four levels for Unicode). If two strings are the same by primary order, they compare using secondary one. That's all. I will apreciate your any decision regarding to DE locale, fixing, backing out etc. since I even can't display characters you use in your example, nor have strong desire to dig in DE language area starting from zero background. -- Andrey A. Chernov ache@null.net MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 00:12:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA05613 for freebsd-current-outgoing; Thu, 4 Feb 1999 00:12:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05415 for ; Thu, 4 Feb 1999 00:12:12 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA30783; Thu, 4 Feb 1999 19:12:09 +1100 Date: Thu, 4 Feb 1999 19:12:09 +1100 From: Bruce Evans Message-Id: <199902040812.TAA30783@godzilla.zeta.org.au> To: current@FreeBSD.ORG, mark@grondar.za Subject: Re: config(8) putting (null) into config files Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I am trying to get my laptop's config file as clean as possible >and one of the lines I experimented with is: > >controller fdc0 at isa? disable port ? bio > >(notice the lack of an "irq" and the wildcarding of "at isa"). > >This results in a line in ioconf.c of: > >{ 10, &fdcdriver, (null), 0, -1, C 0x00000, 0, 0, 0, 0x0000, 0, 0, 0, 0, 0, 0, 0 }, > >Notice the "(null)". I want the line in my config file to be like that >as I do not use the floppy drive very often, and I am quite content for >it to be kicked into action by pccardd when I plug it in. So my config >line above is just a device placeholder. The "(null)" causes a compile >failure, which is fixed by the kluge below. Is there a better way of >doing this, or is this OK to commit? There is a better way. Copy the correct code for printing d_port and d_portn from isa_devtab() to isa_biotab(), and while your're there, check for other lossage in isa_biotab(). The current code also screws up cases where the token following "port" is a number. Only the case where it is a macro name works. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 01:35:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16252 for freebsd-current-outgoing; Thu, 4 Feb 1999 01:35:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16223 for ; Thu, 4 Feb 1999 01:35:35 -0800 (PST) (envelope-from rock@cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.2/1999010400) with ESMTP id KAA19557; Thu, 4 Feb 1999 10:35:28 +0100 (CET) Received: from cs.uni-sb.de (maxtnt-192.telip.uni-sb.de [134.96.71.63]) by cs.uni-sb.de (8.9.2/1999010400) with ESMTP id KAA27168; Thu, 4 Feb 1999 10:35:25 +0100 (CET) Message-ID: <36B969FF.D244FCC4@cs.uni-sb.de> Date: Thu, 04 Feb 1999 10:35:59 +0100 From: "D. Rock" X-Mailer: Mozilla 4.5 [de] (WinNT; U) X-Accept-Language: de MIME-Version: 1.0 To: Joerg Wunsch CC: "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: locale errors References: <199902040250.DAA01966@vodix.aremorika> <19990204060349.A40565@nagual.pp.ru> <19990204073812.49101@uriah.heep.sax.de> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG J Wunsch schrieb: > > As Andrey A. Chernov wrote: > > > > I suggest removing any multi character definition out of the collate > > > files. > > > > It was Joerg initiative, I don't know DE enough to judge here. Please > > resolve this problem with him (CC'ed). > > Well, not completely. :) For testing, i've restored the file from > before my change, and it missorts similarly. I'm probably too stupid > to understand all of this collate stuff. So far, i haven't been able > to come up with any locale definition that does the right thing for > every input. > > To make matters worse, German doesn't even have a single collate > defintion at all. There are at least two dissenting definitions: one > is the phonebook sorting order, and the other one (certainly more > widely accepted and thus should be the base of our collate definition) > the `Duden' (German dictionary). According to my Duden, the following > words > > Maße > Maßeinheit > Masse > Massaua > Massel > > should be sorted like: > > Massaua > Maße > Masse > Maßeinheit > Massel > > If anybody could come up with a set of collate definition files that > does this, it probably would be the right thing. ;) Maybe it's simply > impossible to express using the current collate stuff? It is impossible. The collate couldn't detect concatenated words, which sould sort the usual way: aussetzen austreiben (just a simple example) I noticed the difference while looking into the /R/dist/src directory during a "make release". ssys.XX was sorted behind susrbin.XX in ls output. I suggest just backing out the stuff with multi character locale settings because it is bogus. We should just use the simple phonebook sorting, because it is easier to implement, and the people are more familiar with it. Duden isn't always right (very true since last year for some parts in northern Germany) Daniel P.S. Solaris does sorting the easy way (at least for LC_COLLATE=de.ISO8859-15 and LC_COLLATE=de) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 01:53:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA17933 for freebsd-current-outgoing; Thu, 4 Feb 1999 01:53:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA17921 for ; Thu, 4 Feb 1999 01:53:18 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA06486; Thu, 4 Feb 1999 20:53:15 +1100 Date: Thu, 4 Feb 1999 20:53:15 +1100 From: Bruce Evans Message-Id: <199902040953.UAA06486@godzilla.zeta.org.au> To: jdp@polstra.com, jkh@zippy.cdrom.com Subject: Re: OBJLINK=yes breaks make buildworld Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I don't have a fix. I never use OBJLINK. As far as I'm concerned, a >> suitable fix would be to eliminate that option altogether. > >As far as I'm concerned, and speaking as the author of that hack, >I agree with you! :-) Kill it. Kill it dead. I use it a lot for working in individual directories. It shouldn't be killed until the separate object tree is killed. `make's search path should be set on the command line (default ".") so that obj subdirectories, obj links, and /usr/obj/ can be ignored. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 01:57:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA18484 for freebsd-current-outgoing; Thu, 4 Feb 1999 01:57:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA18477 for ; Thu, 4 Feb 1999 01:57:38 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id EAA03436; Thu, 4 Feb 1999 04:57:46 -0500 (EST) Date: Thu, 4 Feb 1999 04:57:46 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Matthew Dillon cc: current@FreeBSD.ORG Subject: Re: Heads up: comitted optimization to vm_map_insert() In-Reply-To: <199902040422.UAA82246@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 3 Feb 1999, Matthew Dillon wrote: > :> the test ). I think the seg fault may have revealed a new > :> bug and is not related to the optimization I comitted, so I > :> haven't backed out the commit. I am not 100% sure though, > :> and I am testing this now. > : > : What test? If we had this exact test, it could be exploiting the exact bug, > :could it not? I'll let you know of any weird crashes in previously stable > :programs. > > My "do lots of things that force the machine to page up the wazoo and > try to make it crash" test :-) So do you run Netscape, or do you run StarOffice? ;) > > -Matt > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 02:14:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA20101 for freebsd-current-outgoing; Thu, 4 Feb 1999 02:14:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from titan.metropolitan.at ([195.212.98.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA20093 for ; Thu, 4 Feb 1999 02:14:12 -0800 (PST) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id <1CLHRFN5>; Thu, 4 Feb 1999 11:16:20 +0100 Message-ID: <97A8CA5BF490D211A94F0000F6C2E55D097532@s-lmh-wi-900.corpnet.at> From: Ladavac Marino To: "'D. Rock'" , Joerg Wunsch Cc: "Andrey A. Chernov" , current@FreeBSD.ORG Subject: RE: locale errors Date: Thu, 4 Feb 1999 11:12:25 +0100 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id CAA20095 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: D. Rock [SMTP:rock@cs.uni-sb.de] > Sent: Thursday, February 04, 1999 10:36 AM > To: Joerg Wunsch > Cc: Andrey A. Chernov; current@FreeBSD.ORG > Subject: Re: locale errors > > > It is impossible. The collate couldn't detect concatenated words, > which sould sort the usual way: > > aussetzen > austreiben > > (just a simple example) > [ML] Shouldn't ß (scharfes-s, sz) be collated as SZ which it really is? /Marino > I noticed the difference while looking into the /R/dist/src directory > during > a "make release". ssys.XX was sorted behind susrbin.XX in ls output. > > I suggest just backing out the stuff with multi character locale > settings > because it is bogus. We should just use the simple phonebook sorting, > because > it is easier to implement, and the people are more familiar with it. > > Duden isn't always right (very true since last year for some parts in > northern Germany) > > Daniel > > P.S. Solaris does sorting the easy way (at least for > LC_COLLATE=de.ISO8859-15 > and LC_COLLATE=de) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 02:30:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA21505 for freebsd-current-outgoing; Thu, 4 Feb 1999 02:30:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA21408 for ; Thu, 4 Feb 1999 02:29:59 -0800 (PST) (envelope-from rock@cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.2/1999010400) with ESMTP id LAA19857; Thu, 4 Feb 1999 11:29:52 +0100 (CET) Received: from cs.uni-sb.de (maxtnt-203.telip.uni-sb.de [134.96.71.74]) by cs.uni-sb.de (8.9.2/1999010400) with ESMTP id LAA27747; Thu, 4 Feb 1999 11:29:51 +0100 (CET) Message-ID: <36B976C9.F5DF96DB@cs.uni-sb.de> Date: Thu, 04 Feb 1999 11:30:33 +0100 From: "D. Rock" X-Mailer: Mozilla 4.5 [de] (WinNT; U) X-Accept-Language: de MIME-Version: 1.0 To: Ladavac Marino CC: Joerg Wunsch , current@FreeBSD.ORG Subject: Re: locale errors References: <97A8CA5BF490D211A94F0000F6C2E55D097532@s-lmh-wi-900.corpnet.at> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ladavac Marino schrieb: > > > -----Original Message----- > > From: D. Rock [SMTP:rock@cs.uni-sb.de] > > Sent: Thursday, February 04, 1999 10:36 AM > > To: Joerg Wunsch > > Cc: Andrey A. Chernov; current@FreeBSD.ORG > > Subject: Re: locale errors > > > > > > It is impossible. The collate couldn't detect concatenated words, > > which sould sort the usual way: > > > > aussetzen > > austreiben > > > > (just a simple example) > > > [ML] Shouldn't ß (scharfes-s, sz) be collated as SZ which > it really is? > > /Marino You will still get into the same problem (Auszeit) Also Duden explicitly states, sz should be only used as a last resort, to avoid misinterpretation. But the original example shows that Duden suggests treating "ss" and "ß" equal in sorting. Introducing "sz" just produces additional confusion. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 02:39:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA22352 for freebsd-current-outgoing; Thu, 4 Feb 1999 02:39:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-26-dbn.dial-up.net [196.34.155.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA22343 for ; Thu, 4 Feb 1999 02:39:43 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id MAA22256; Thu, 4 Feb 1999 12:37:47 +0200 (SAT) From: Robert Nordier Message-Id: <199902041037.MAA22256@ceia.nordier.com> Subject: Re: Boot block problem In-Reply-To: <199902040319.TAA10987@dingo.cdrom.com> from Mike Smith at "Feb 3, 99 07:19:34 pm" To: archie@whistle.com (Archie Cobbs) Date: Thu, 4 Feb 1999 12:37:45 +0200 (SAT) Cc: mike@smith.net.au, freebsd-current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > [Archie Cobbs wrote:] > > Just upgraded to 3.0-stable snapshot circa 2/1 and noticed that > > the new "booteasy" does not seem to remember the selection from > > the previous time. Eg., I need to press F5 to get to disk 2 but > > it always defaults to F2 (which is FreeBSD slice containing > > only a swap partition). > > > > This means my box won't reboot automatically anymore, e.g., if > > the power goes out. > > > > Is this a new bug or a new feature? :-) > > It's supposed to work, and it does for me here. Check you haven't got > your BIOS 'boot virus protection' stuff enabled, then talk to Robert > Nordier (in that order 8). No need to talk to me: I'll talk to you instead. :) The new boot manager remembers "last slice selected" rather than "last menu option selected" on each drive. I think I prefer this behavior myself, but I'll change it for compatibility with booteasy. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 02:41:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA22581 for freebsd-current-outgoing; Thu, 4 Feb 1999 02:41:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA22570 for ; Thu, 4 Feb 1999 02:41:41 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id TAA25791; Thu, 4 Feb 1999 19:41:35 +0900 (JST) Message-ID: <36B9717C.EBDE13@newsguy.com> Date: Thu, 04 Feb 1999 19:07:56 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Rod Taylor CC: freebsd-current@FreeBSD.ORG Subject: Re: Network Cards References: <99020320193400.08377@a20.my.intranet> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rod Taylor wrote: > > I've often wondered this, but why is it that every network card has a different > 'name'. > > xl0, rl0, vr0, ed0, etc. etc. etc > > I tried simlinking them to a common name (I have xl0, rl0, and ed0 active in my > current machine). linked to eth0, eth1, eth2 (didn't work). > > However, it would be nice if they all had a common name to the end user.. > Primarily, me.. Especially when you rip out one card, install another, then > the name changes on you... Suppose you have "xl" and "vr" in your computer. They are named eth0 and eth1, respectively. You then replace your "vr" by a "ed". Mark with an X the correct option: ( ) the names for "vr" and "ed" will be eth0 and eth1, respectively. ( ) the names for "vr" and "ed" will be eth1 and eth0, respectively. ( ) none of the above Can you see what I'm getting at here? :-) The best solution would be hardwiring the names, but in that case it doesn't matter what are the default names. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com She just looked at him over the rotating pencil like, how slow can a mammal be and still have respiratory functions? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 03:03:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA24899 for freebsd-current-outgoing; Thu, 4 Feb 1999 03:03:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from speed.rcc.on.ca (radio163.mipps.net [205.189.197.163] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA24894 for ; Thu, 4 Feb 1999 03:03:01 -0800 (PST) (envelope-from oscentral@usa.net) Received: from a20.my.intranet ([207.164.233.98]) by speed.rcc.on.ca (8.6.12/8.6.9) with SMTP id HAA16452 for ; Thu, 4 Feb 1999 07:13:18 -0500 From: Rod Taylor To: freebsd-current@FreeBSD.ORG Subject: Re: Network Cards Date: Thu, 4 Feb 1999 06:01:52 -0500 X-Mailer: KMail [version 1.0.9] Content-Type: text/plain References: <36B9717C.EBDE13@newsguy.com> MIME-Version: 1.0 Message-Id: <99020406025800.09173@a20.my.intranet> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG But then if I added another say ed0, it wouldn't get eth2 :) But yeah, I understand where you're going... >> However, it would be nice if they all had a common name to the end user.. >> Primarily, me.. Especially when you rip out one card, install another, then >> the name changes on you... > >Suppose you have "xl" and "vr" in your computer. They are named eth0 >and eth1, respectively. You then replace your "vr" by a "ed". Mark >with an X the correct option: > >( ) the names for "vr" and "ed" will be eth0 and eth1, respectively. >( ) the names for "vr" and "ed" will be eth1 and eth0, respectively. >( ) none of the above > >Can you see what I'm getting at here? :-) > >The best solution would be hardwiring the names, but in that case it >doesn't matter what are the default names. > >-- >Daniel C. Sobral (8-DCS) >dcs@newsguy.com > > She just looked at him over the rotating pencil like, how slow can >a mammal be and still have respiratory functions? > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message -- Rod Taylor Proud Member of Team OS/2 User of FreeBSD & KDE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 04:36:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA08390 for freebsd-current-outgoing; Thu, 4 Feb 1999 04:36:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nomad.dataplex.net (nomad.dataplex.net [208.2.87.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA08371 for ; Thu, 4 Feb 1999 04:36:52 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from localhost (rkw@localhost) by nomad.dataplex.net (8.9.1/8.9.1) with ESMTP id GAA66607; Thu, 4 Feb 1999 06:36:45 -0600 (CST) (envelope-from rkw@dataplex.net) Date: Thu, 4 Feb 1999 06:36:45 -0600 (CST) From: Richard Wackerbarth To: "Daniel C. Sobral" cc: Rod Taylor , freebsd-current@FreeBSD.ORG Subject: Re: Network Cards In-Reply-To: <36B9717C.EBDE13@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 4 Feb 1999, Daniel C. Sobral wrote: > Rod Taylor wrote: > > I've often wondered this, but why is it that every network card has a different > > 'name'. > > xl0, rl0, vr0, ed0, etc. etc. etc > The best solution would be hardwiring the names, but in that case it > doesn't matter what are the default names. Yes. Hardwiring is the only appropriate solution. It should be done as a part of the loader kernel configuration. Perhaps it should work somewhat like the SCSI disk partitions. Unspecified interfaces get the next available slot. However, and this is the important point, it is very useful to be able to assign an identifier to the logical interface and have that identifier appear in EVERY reference to the interface. I would like to hardwire 00:aa:bb:cc:dd:ee which uses the vr driver to eth23 and have ifconfig accept and report the device as 'eth23'. The actual driver is parenthetical. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 05:01:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA10834 for freebsd-current-outgoing; Thu, 4 Feb 1999 05:01:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA10819 for ; Thu, 4 Feb 1999 05:01:33 -0800 (PST) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id XAA11758; Thu, 4 Feb 1999 23:00:33 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (3.2) id xma011755; Thu, 4 Feb 99 23:00:14 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id XAA28476 for ; Thu, 4 Feb 1999 23:00:14 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id XAA09072 for ; Thu, 4 Feb 1999 23:00:13 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id XAA10590; Thu, 4 Feb 1999 23:00:11 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199902041300.XAA10590@nymph.detir.qld.gov.au> To: freebsd-current@FreeBSD.ORG cc: syssgm@detir.qld.gov.au Subject: panic: vm_object_qcollapse(): object mismatch Date: Thu, 04 Feb 1999 23:00:11 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hardware: 486DX2/66 16Mb ram, aha1542CF, 2x1Gb SCSI disks Software: 4.0-current 1-2 days old, softupdates (vm_map.c is at rev 1.146, for example) I was running 'make -j5 buildworld'. It swaps like crazy when I do this. :-) Here's what gdb -k tells me: ... #9 0xf01425e0 in panic ( fmt=0xf0225c1f "vm_object_qcollapse(): object mismatch") at ../../kern/kern_shutdown.c:446 #10 0xf01e0772 in vm_object_qcollapse (object=0xf2f001d0) at ../../vm/vm_object.c:1011 #11 0xf01e08d6 in vm_object_collapse (object=0xf2f001d0) at ../../vm/vm_object.c:1102 #12 0xf01ddae2 in vm_map_copy_entry (src_map=0xf2f4aa00, dst_map=0xf2f4ad00, src_entry=0xf2ed0e10, dst_entry=0xf2f8edc0) at ../../vm/vm_map.c:2284 #13 0xf01ddd73 in vmspace_fork (vm1=0xf2f4aa00) at ../../vm/vm_map.c:2411 #14 0xf01da833 in vm_fork (p1=0xf2f7db20, p2=0xf2d751e0, flags=20) at ../../vm/vm_glue.c:231 #15 0xf013d4f0 in fork1 (p1=0xf2f7db20, flags=20) at ../../kern/kern_fork.c:447 #16 0xf013ce65 in fork (p=0xf2f7db20, uap=0xf3021f94) at ../../kern/kern_fork.c:99 #17 0xf01fe783 in syscall (frame={tf_es = 134807599, tf_ds = -272695249, tf_edi = 134750909, tf_esi = 134935201, tf_ebp = -272643652, tf_isp = -217964572, tf_ebx = 4, tf_edx = 672250004, tf_ecx = 19, tf_eax = 2, tf_trapno = 12, tf_err = 2, tf_eip = 671826564, tf_cs = 31, tf_eflags = 662, tf_esp = -272651296, tf_ss = 47}) at ../../i386/i386/trap.c:1100 #18 0xf01f4e9c in Xint0x80_syscall () ... (kgdb) p *p $1 = {pageq = {tqe_next = 0xf02c5240, tqe_prev = 0xf02e4e00}, hnext = 0x0, listq = {tqe_next = 0xf02e59d0, tqe_prev = 0xf2f69cc8}, object = 0xf2f69cb0, pindex = 30, phys_addr = 15065088, queue = 4, flags = 1, pc = 0, wire_count = 0, hold_count = 0, act_count = 27 '\e', busy = 0 '\000', valid = 255 '˙', dirty = 255 '˙'} (kgdb) p object $2 = (struct vm_object *) 0xf2f001d0 (kgdb) p *object $3 = {object_list = {tqe_next = 0xf2fdc2b8, tqe_prev = 0xf2f69c3c}, shadow_head = {tqh_first = 0x0, tqh_last = 0xf2f001d8}, shadow_list = { tqe_next = 0x0, tqe_prev = 0xf2f69cb8}, memq = {tqh_first = 0xf02dbcb0, tqh_last = 0xf02cc86c}, generation = 11690, type = OBJT_DEFAULT, size = 32, ref_count = 2, shadow_count = 0, pg_color = 0, hash_rand = -136756254, flags = 8576, paging_in_progress = 0, behavior = 0, resident_page_count = 6, cache_count = 0, wire_count = 0, backing_object = 0xf2f69cb0, backing_object_offset = 0x0000000000000000, last_read = 0, pager_object_list = {tqe_next = 0xf2f69000, tqe_prev = 0xf0252f10}, handle = 0x0, un_pager = {vnp = { vnp_size = 0x0000000000000000}, devp = {devp_pglist = {tqh_first = 0x0, tqh_last = 0x0}}, swp = {swp_bcount = 0}}} (kgdb) p *(p->object) $4 = {object_list = {tqe_next = 0xf2f915e4, tqe_prev = 0xf30fd0e8}, shadow_head = {tqh_first = 0xf2f001d0, tqh_last = 0xf2f001e0}, shadow_list = {tqe_next = 0x0, tqe_prev = 0xf30fef04}, memq = { tqh_first = 0xf02e7170, tqh_last = 0xf02cff5c}, generation = 10219, type = OBJT_SWAP, size = 32, ref_count = 3, shadow_count = 1, pg_color = 0, hash_rand = -136000830, flags = 384, paging_in_progress = 0, behavior = 0, resident_page_count = 4, cache_count = 1, wire_count = 0, backing_object = 0x0, backing_object_offset = 0x0000000000000000, last_read = 29, pager_object_list = {tqe_next = 0xf30fad24, tqe_prev = 0xf30f0814}, handle = 0x0, un_pager = {vnp = { vnp_size = 0x0000000000000001}, devp = {devp_pglist = {tqh_first = 0x1, tqh_last = 0x0}}, swp = {swp_bcount = 1}}} I'll keep this dump around. What other details do people want? I'm not likely to even get to look at this let alone solve it. Bummer. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 05:12:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA12237 for freebsd-current-outgoing; Thu, 4 Feb 1999 05:12:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA12230 for ; Thu, 4 Feb 1999 05:12:14 -0800 (PST) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.sci.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id WAA28989 for ; Thu, 4 Feb 1999 22:03:25 +0900 (JST) Message-Id: <199902041303.WAA28989@shidahara1.planet.sci.kobe-u.ac.jp> To: current@FreeBSD.ORG Subject: Re: How do I query system temperature probes ? In-reply-to: Your message of "Thu, 04 Feb 1999 11:00:42 +1030" References: <36B7CED1.96D4B369@dsto.defence.gov.au> <19990203203133.12975@breizh.prism.uvsq.fr> <36B8EA32.D5105294@dsto.defence.gov.au> Date: Thu, 04 Feb 1999 22:03:25 +0900 From: Takanori Watanabe Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <36B8EA32.D5105294@dsto.defence.gov.au>, Matthew Thyer wrote: >Thanks, > >Takanori, are you going to commit your example code in >say /usr/src/share/examples/smbus ? > >If not can you send me a copy please ? I'll announce about it in current list also. I'm sorry if you see this twice. Message-Id: <199901251651.BAA27916@shidahara1.planet.sci.kobe-u.ac.jp> To: hackers@FreeBSD.ORG Subject: Some SMBus Stuffs. Date: Tue, 26 Jan 1999 01:51:13 +0900 From: Takanori Watanabe The driver for SMBus on Intel PIIX4 Power Management Controller has been commited. Now, I have some examples for SMBus application. It is available at http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/examples/ . (snip) Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 06:32:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22611 for freebsd-current-outgoing; Thu, 4 Feb 1999 06:32:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA22475 for ; Thu, 4 Feb 1999 06:30:46 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:rbtkdinzGzOXkaaZAmkpFRv7zOTSdCod@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id XAA01513 for ; Thu, 4 Feb 1999 23:30:38 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id XAA15337; Thu, 4 Feb 1999 23:33:24 +0900 (JST) Message-Id: <199902041433.XAA15337@zodiac.mech.utsunomiya-u.ac.jp> To: current@FreeBSD.ORG cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: CALL FOR REVIEW: man page update Date: Thu, 04 Feb 1999 23:33:07 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In order to reflect the recent changes regarding syscons, keyboard and video drivers, I wrote the following new man pages and update for a couple of existing ones. They are rudimentary, but better than nothing. http://www.freebsd.org/~yokota/man4update.tar.gz New pages: atkbd.4 atkbdc.4 splash.4 (screensaver.4) vga.4 Updated pages: pcvt.4 psm.4 (The tar.gz file includes doc-syms.diff, which should be applied to /usr/share/tmac/mdoc/doc-syms too.) Would you please, please review these man pages and correct my poor English. Please send me any suggestions and addition for them too. I would like to finish them in time for 3.1-RELEASE. I appreciate your help. Thank you. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 07:52:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04676 for freebsd-current-outgoing; Thu, 4 Feb 1999 07:52:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.nerds4rent.com (ns2.freedomnet.com [198.240.104.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04665 for ; Thu, 4 Feb 1999 07:52:11 -0800 (PST) (envelope-from kbyanc@freedomnet.com) Received: from freedomnet.com (tech.nerds4rent.com [198.240.104.20]) by mail.nerds4rent.com (8.8.8/8.8.8/antispam) with ESMTP id KAA18653 for ; Thu, 4 Feb 1999 10:58:39 -0500 (EST) X-Envelope-To: Message-ID: <36B9BEC2.B6303CA@freedomnet.com> Date: Thu, 04 Feb 1999 10:37:38 -0500 From: Kelly Yancey Organization: FreedomNet - http://www.freedomnet.com/ X-Mailer: Mozilla 4.5 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Snapshots and Netscape Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just FYI, I don't know if anyone else has experienced this problem or if it was only with 3.0-19990128-SNAP. I found that if you use sysinstall to install a snapshot then you can't build Netscape 4..08 or 4.5 (Communicator or standalone). It dies in vreg (also when trying to start Netscape withoutt having run vreg) looking for ld.so. I cvsup'ed to 3.0-STABLE as of last night and everything worked. Kelly -- Kelly Yancey "Bill Gates is only a white Persian cat and ~kbyanc@freedomnet.com~ a monocle away from being the villain in a James Bond movie" - comedian Dennis Miller To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 08:02:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA05864 for freebsd-current-outgoing; Thu, 4 Feb 1999 08:02:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ent.freebsd.org.pl (ent.freebsd.org.pl [195.117.238.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05791 for ; Thu, 4 Feb 1999 08:01:41 -0800 (PST) (envelope-from jarekb@freebsd.org.pl) Received: from localhost (jarekb@localhost) by ent.freebsd.org.pl (8.9.2/8.9.1) with ESMTP id SAA00201 for ; Thu, 4 Feb 1999 18:10:58 GMT (envelope-from jarekb@ent.freebsd.org.pl) Date: Thu, 4 Feb 1999 18:10:58 +0000 (GMT) From: Jaroslaw Bazydlo To: current@FreeBSD.ORG Subject: ifq_maxlen problem... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After yesterdays 'make world' I am having such warnings: FreeBSD 4.0-CURRENT #0: Thu Feb 4 17:19:09 GMT 1999 jarekb@ent.freebsd.org.pl:/usr/src/sys/compile/ENT [...] ep0 at 0x300-0x30f irq 10 on isa ep0: utp/bnc[*UTP*] address 00:60:08:65:d6:8d [...] ep0 XXX: driver didn't set ifq_maxlen lo0 XXX: driver didn't set ifq_maxlen ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The system itself seems to work fine (for last 24 hrs). What do those messages mean??? Does anyone of you noticed similar messages??? The NIC is 3com 3c509B. Greetings -- Jaroslaw Bazydlo | mailto:jarekb@freebsd.org.pl | http://www.freebsd.org.pl/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 08:18:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08546 for freebsd-current-outgoing; Thu, 4 Feb 1999 08:18:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles233.castles.com [208.214.165.233]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA08530 for ; Thu, 4 Feb 1999 08:18:43 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA15035; Thu, 4 Feb 1999 08:14:13 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902041614.IAA15035@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Robert Nordier cc: archie@whistle.com (Archie Cobbs), mike@smith.net.au, freebsd-current@FreeBSD.ORG Subject: Re: Boot block problem In-reply-to: Your message of "Sat, 04 Feb 1999 12:37:45 +0200." <199902041037.MAA22256@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Feb 1999 08:14:12 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The new boot manager remembers "last slice selected" rather than > "last menu option selected" on each drive. > > I think I prefer this behavior myself, but I'll change it for > compatibility with booteasy. In the case where the last action was to chain to another disk, that's definitely preferable... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 08:26:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10132 for freebsd-current-outgoing; Thu, 4 Feb 1999 08:26:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles233.castles.com [208.214.165.233]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10121 for ; Thu, 4 Feb 1999 08:26:28 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA15091; Thu, 4 Feb 1999 08:22:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902041622.IAA15091@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" cc: Rod Taylor , freebsd-current@FreeBSD.ORG Subject: Re: Network Cards In-reply-to: Your message of "Thu, 04 Feb 1999 19:07:56 +0900." <36B9717C.EBDE13@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Feb 1999 08:22:11 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Rod Taylor wrote: > > > > I've often wondered this, but why is it that every network card has a different > > 'name'. > > > > xl0, rl0, vr0, ed0, etc. etc. etc > > > > I tried simlinking them to a common name (I have xl0, rl0, and ed0 active in my > > current machine). linked to eth0, eth1, eth2 (didn't work). > > > > However, it would be nice if they all had a common name to the end user.. > > Primarily, me.. Especially when you rip out one card, install another, then > > the name changes on you... > > Suppose you have "xl" and "vr" in your computer. They are named eth0 > and eth1, respectively. You then replace your "vr" by a "ed". Mark > with an X the correct option: > > ( ) the names for "vr" and "ed" will be eth0 and eth1, respectively. > ( ) the names for "vr" and "ed" will be eth1 and eth0, respectively. > ( ) none of the above > > Can you see what I'm getting at here? :-) > > The best solution would be hardwiring the names, but in that case it > doesn't matter what are the default names. Actually, this is just a pathalogical case of: You have de0 and de1 in your computer. You replace one with another 'de' card/rearrange cards/whatever. Mark with an X the correct option ( ) de0 remains de0, de1 remains de1 ( ) de0 becomes de1, de1 becomes de0 ( ) you discover a new device, de-1 Having a single linear namespace for interfaces would, actually, make life somewhat easier for the administrator. You can simulate it buy only buying one type of ethernet card. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 08:30:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10880 for freebsd-current-outgoing; Thu, 4 Feb 1999 08:30:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.WorldMediaCo.com ([207.252.121.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10873 for ; Thu, 4 Feb 1999 08:30:10 -0800 (PST) (envelope-from opsys@open-systems.net) Received: from freebsd.omaha.com ([207.252.122.220]) by mail1.WorldMediaCo.com (Post.Office MTA v3.5.3 release 223 ID# 0-55573U2500L250S0V35) with SMTP id com; Thu, 4 Feb 1999 10:23:47 -0600 Date: Thu, 4 Feb 1999 10:30:05 +0000 (GMT) From: "Open Systems Inc." X-Sender: opsys@freebsd.omaha.com To: Jaroslaw Bazydlo cc: current@FreeBSD.ORG Subject: Re: ifq_maxlen problem... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 4 Feb 1999, Jaroslaw Bazydlo wrote: > After yesterdays 'make world' I am having such warnings: > ep0 XXX: driver didn't set ifq_maxlen > lo0 XXX: driver didn't set ifq_maxlen > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > The system itself seems to work fine (for last 24 hrs). What do those > messages mean??? Does anyone of you noticed similar messages??? I get the same thing for my kingston DEC based 10/100 card and lo0. The card still works though so the chance of this being life threatening are low :-) I'm sure its pretty harmless. Chris -- "Join Team-FreeBSD on cracking RC5-64! grab you client now and HELP OUT! http://www.distributed.net/cgi/select.cgi" ===================================| Open Systems FreeBSD Consulting. FreeBSD 2.2.8 is available now! | Phone: 402-573-9124 -----------------------------------| 3335 N. 103 Plaza #14, Omaha, NE 68134 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting, Network Engineering, Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 08:32:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11245 for freebsd-current-outgoing; Thu, 4 Feb 1999 08:32:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles233.castles.com [208.214.165.233]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11236 for ; Thu, 4 Feb 1999 08:32:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA15129; Thu, 4 Feb 1999 08:28:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902041628.IAA15129@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Richard Wackerbarth cc: "Daniel C. Sobral" , Rod Taylor , freebsd-current@FreeBSD.ORG Subject: Re: Network Cards In-reply-to: Your message of "Thu, 04 Feb 1999 06:36:45 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Feb 1999 08:28:07 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 4 Feb 1999, Daniel C. Sobral wrote: > > Rod Taylor wrote: > > > I've often wondered this, but why is it that every network card has a different > > > 'name'. > > > xl0, rl0, vr0, ed0, etc. etc. etc > > The best solution would be hardwiring the names, but in that case it > > doesn't matter what are the default names. > > Yes. Hardwiring is the only appropriate solution. Hardwiring is nonappropriate in a non-static environment. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 08:40:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12242 for freebsd-current-outgoing; Thu, 4 Feb 1999 08:40:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from darkstar.psa.at (darkstar.psa.at [194.152.163.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12106 for ; Thu, 4 Feb 1999 08:40:00 -0800 (PST) (envelope-from root@frag.quake.at) Received: from unet2-127.univie.ac.at ([131.130.232.127] helo=entropy.quake.at) by darkstar.psa.at with esmtp (Exim 2.10 #2) id 108Rry-00074U-00; Thu, 4 Feb 1999 17:43:10 +0100 Received: from root by entropy.quake.at with local (Exim 2.10 #2) id 108IG0-0000mA-00; Thu, 4 Feb 1999 07:27:20 +0100 To: John Birrell , current@FreeBSD.ORG Subject: Re: How many people use VI? This is unbelievable.. References: <199902040418.PAA14815@cimlogic.com.au> From: as@psa.at (Alexander Sanda) In-Reply-To: John Birrell's message of "Thu, 4 Feb 1999 15:18:42 +1100 (EST)" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: 04 Feb 1999 07:27:20 +0100 Message-ID: Lines: 22 User-Agent: Gnus/5.070075 (Pterodactyl Gnus v0.75) XEmacs/21.2(beta8) (Artemis) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Birrell writes: > FWIW, this message is being edited with vi on a 2.2.8-STABLE machine > rlogged in from a dxterm running on an OSF/1 box. The keyboard is one > of DEC's LK401 things with the funny "Do" keys etc from back when VAX > was just a twinkle in PDP's eye. I have TERM=vt100 in my FreeBSD > environment, dxterm configured with the "Numeric Keypad" option checked > and vt100 emulation, so keypad keys are 0.123456789, just like you'd > expect. It's not vi that's the problem, just your termcap setting doesn't > match the keyboard. But why is it only vi ? I see the same behaviour here (-current, Eterm, TERM=xterm). The numeric keypad works for XEmacs forced to use term instead of X, pico, mcedit (midnight commanders builtin editor), shell - everywhere else, but not for vi. -- # /AS/ http://privat.schlund.de/entropy/ # # According to rumours, MS finally decided to delay the release of the # # long-awaited Windows 2000 until the first quarter of 1901. -unknown # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 08:54:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14565 for freebsd-current-outgoing; Thu, 4 Feb 1999 08:54:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from seawall.ninthwave.com (ninthwave.com [209.31.6.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14520 for ; Thu, 4 Feb 1999 08:53:49 -0800 (PST) (envelope-from jdi@ninthwave.com) Received: from ninthwave.com (kuta.ninthwave.com [10.0.0.2]) by seawall.ninthwave.com (8.9.2/8.9.1) with ESMTP id IAA18967; Thu, 4 Feb 1999 08:53:24 -0800 (PST) (envelope-from jdi@ninthwave.com) Message-ID: <36B9D1BC.D2409BB5@ninthwave.com> Date: Thu, 04 Feb 1999 08:58:36 -0800 From: John Irwin X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm CC: "Eric J. Schwertfeger" , current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad References: <199812292011.EAA82011@spinner.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Eric J. Schwertfeger" wrote: > > There's two areas that IPFILTER seems to work better than IPFW, and both > > are NAT-related. > > I've been discussing this with various folks. > > What I see as the "best" solution to overcome the problem of a poorly > maintained (and old) copy in the tree is to make a port out of it and > remove the bulk of the code from the tree. Any chance of this happening (preferrably in 3.0-stable)? I need to run the newest version of IPFilter, and it's a bitch trying to hack out the old/hack in the new. Thanks, -- John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 08:55:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14962 for freebsd-current-outgoing; Thu, 4 Feb 1999 08:55:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14841 for ; Thu, 4 Feb 1999 08:55:02 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (tiburon [158.227.6.111]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id RAA12214 for ; Thu, 4 Feb 1999 17:54:40 +0100 (MET) Message-ID: <36B9D0CF.8EB9BC65@we.lc.ehu.es> Date: Thu, 04 Feb 1999 17:54:39 +0100 From: "Jose M. Alcaide" Organization: Universidad del Pais Vasco - Dept. de Electricidad y Electronica X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 3.0-STABLE i386) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: boot0 does not remember F5 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have just installed the new boot0 boot manager on a machine which has two IDE disks attached to the same IDE bus. The first disk (wd0) is entirely dedicated to Windoze (ugh!) and the second one (wd1) to FreeBSD (aahhh...). Boot0 does its job, so I can choose between the two disks pressing F1 or F5. However, the default option is _always_ F1, despite of being F5 the last choice. Is this a bug or a "feature" :-) ? -- JMA ----------------------------------------------------------------------- José MŞ Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@es.FreeBSD.ORG Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 09:23:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19908 for freebsd-current-outgoing; Thu, 4 Feb 1999 09:23:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19898 for ; Thu, 4 Feb 1999 09:23:50 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from daniel.sobral by peach.ocn.ne.jp (8.9.1a/OCN) id CAA25387; Fri, 5 Feb 1999 02:23:44 +0900 (JST) Received: (from dcs@localhost) by daniel.sobral (8.9.1/8.9.2) id CAA00600 for current@freebsd.org; Fri, 5 Feb 1999 02:23:13 +0900 (JST) (envelope-from dcs) From: "Daniel C. Sobral" Message-Id: <199902041723.CAA00600@daniel.sobral> Subject: HEADS UP: loader has changed To: current@FreeBSD.ORG Date: Fri, 5 Feb 1999 02:23:13 +0900 (JST) Disclaimer: Klaatu Barada Nikto! X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just committed patches to make "include" work with source code. Previously, it only processed builtins, greatly diminishing both ficl and include's usefulness. As a result of this change, the special behavior of the chacters @, # and - at the beginning of script lines is lost. They have been replaced as follow: @ Lines will *not* be echoed anymore by default. Thus, lines with "@" can simply remove it. If one wants to echo a line, use the character "$", with a space after it. # Use "\" followed by a space. - Use "%" followed by a space. Examples: \ This is a comment load dont.echo $ load echo % load ignore.errors Since the new "characters" are forth words, they can be used anywhere in the line. So you can add comments *after* the command, for example. They can also be used together: % $ load /kernel.experimental I apologize for the inconvenience this may cause, but the previous way is highly incompatible with forth. -- Daniel C. Sobral (8-DCS) dcs@gns.com.br The trouble with eating Italian food is that five or six days later you're hungry again. -- George Miller To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 09:28:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20239 for freebsd-current-outgoing; Thu, 4 Feb 1999 09:26:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20232 for ; Thu, 4 Feb 1999 09:26:17 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id JAA88650; Thu, 4 Feb 1999 09:26:07 -0800 (PST) (envelope-from dillon) Date: Thu, 4 Feb 1999 09:26:07 -0800 (PST) From: Matthew Dillon Message-Id: <199902041726.JAA88650@apollo.backplane.com> To: Stephen McKay Cc: freebsd-current@FreeBSD.ORG, syssgm@detir.qld.gov.au Subject: Re: panic: vm_object_qcollapse(): object mismatch References: <199902041300.XAA10590@nymph.detir.qld.gov.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmmm. This looks like an out-an-out bug to me. The assertion is wrong. It's scanning the backing_object and asserting that the pages in the backing object are associated with object rather then backing_object. This section of code only runs when paging is in progress on a collapseable object AND there are also idle pages in that object. The collapse condition is probably due to an exiting process ( typical in a buildworld ). ( from vm/vm_object.c ) /* * busy the page and move it from the backing store to the * parent object. */ vm_page_busy(p); KASSERT(p->object == object, ("vm_object_qcollapse(): object mismatch")); ^^^^^^^^^^ should be 'backing_object' There is also an interrupt race. Since paging can be in progress, pages in the object can be ripped out from under it so we have to run at splbio() in the loop. I will commit the fix. -Matt Matthew Dillon :Hardware: 486DX2/66 16Mb ram, aha1542CF, 2x1Gb SCSI disks :Software: 4.0-current 1-2 days old, softupdates : (vm_map.c is at rev 1.146, for example) : :I was running 'make -j5 buildworld'. It swaps like crazy when I do this. :-) : :Here's what gdb -k tells me: : :... :#9 0xf01425e0 in panic ( : fmt=0xf0225c1f "vm_object_qcollapse(): object mismatch") : at ../../kern/kern_shutdown.c:446 :#10 0xf01e0772 in vm_object_qcollapse (object=0xf2f001d0) : at ../../vm/vm_object.c:1011 :#11 0xf01e08d6 in vm_object_collapse (object=0xf2f001d0) : at ../../vm/vm_object.c:1102 :#12 0xf01ddae2 in vm_map_copy_entry (src_map=0xf2f4aa00, dst_map=0xf2f4ad00, : src_entry=0xf2ed0e10, dst_entry=0xf2f8edc0) at ../../vm/vm_map.c:2284 :#13 0xf01ddd73 in vmspace_fork (vm1=0xf2f4aa00) at ../../vm/vm_map.c:2411 :#14 0xf01da833 in vm_fork (p1=0xf2f7db20, p2=0xf2d751e0, flags=20) : at ../../vm/vm_glue.c:231 :#15 0xf013d4f0 in fork1 (p1=0xf2f7db20, flags=20) at ../../kern/kern_fork.c:447 :#16 0xf013ce65 in fork (p=0xf2f7db20, uap=0xf3021f94) : at ../../kern/kern_fork.c:99 :#17 0xf01fe783 in syscall (frame={tf_es = 134807599, tf_ds = -272695249, : tf_edi = 134750909, tf_esi = 134935201, tf_ebp = -272643652, : tf_isp = -217964572, tf_ebx = 4, tf_edx = 672250004, tf_ecx = 19, : tf_eax = 2, tf_trapno = 12, tf_err = 2, tf_eip = 671826564, tf_cs = 31, : tf_eflags = 662, tf_esp = -272651296, tf_ss = 47}) : at ../../i386/i386/trap.c:1100 :#18 0xf01f4e9c in Xint0x80_syscall () :... :(kgdb) p *p :$1 = {pageq = {tqe_next = 0xf02c5240, tqe_prev = 0xf02e4e00}, hnext = 0x0, : listq = {tqe_next = 0xf02e59d0, tqe_prev = 0xf2f69cc8}, object = 0xf2f69cb0, : pindex = 30, phys_addr = 15065088, queue = 4, flags = 1, pc = 0, : wire_count = 0, hold_count = 0, act_count = 27 '\e', busy = 0 '\000', : valid = 255 '˙', dirty = 255 '˙'} :(kgdb) p object :$2 = (struct vm_object *) 0xf2f001d0 :(kgdb) p *object :$3 = {object_list = {tqe_next = 0xf2fdc2b8, tqe_prev = 0xf2f69c3c}, : shadow_head = {tqh_first = 0x0, tqh_last = 0xf2f001d8}, shadow_list = { : tqe_next = 0x0, tqe_prev = 0xf2f69cb8}, memq = {tqh_first = 0xf02dbcb0, : tqh_last = 0xf02cc86c}, generation = 11690, type = OBJT_DEFAULT, : size = 32, ref_count = 2, shadow_count = 0, pg_color = 0, : hash_rand = -136756254, flags = 8576, paging_in_progress = 0, behavior = 0, : resident_page_count = 6, cache_count = 0, wire_count = 0, : backing_object = 0xf2f69cb0, backing_object_offset = 0x0000000000000000, : last_read = 0, pager_object_list = {tqe_next = 0xf2f69000, : tqe_prev = 0xf0252f10}, handle = 0x0, un_pager = {vnp = { : vnp_size = 0x0000000000000000}, devp = {devp_pglist = {tqh_first = 0x0, : tqh_last = 0x0}}, swp = {swp_bcount = 0}}} :(kgdb) p *(p->object) :$4 = {object_list = {tqe_next = 0xf2f915e4, tqe_prev = 0xf30fd0e8}, : shadow_head = {tqh_first = 0xf2f001d0, tqh_last = 0xf2f001e0}, : shadow_list = {tqe_next = 0x0, tqe_prev = 0xf30fef04}, memq = { : tqh_first = 0xf02e7170, tqh_last = 0xf02cff5c}, generation = 10219, : type = OBJT_SWAP, size = 32, ref_count = 3, shadow_count = 1, pg_color = 0, : hash_rand = -136000830, flags = 384, paging_in_progress = 0, behavior = 0, : resident_page_count = 4, cache_count = 1, wire_count = 0, : backing_object = 0x0, backing_object_offset = 0x0000000000000000, : last_read = 29, pager_object_list = {tqe_next = 0xf30fad24, : tqe_prev = 0xf30f0814}, handle = 0x0, un_pager = {vnp = { : vnp_size = 0x0000000000000001}, devp = {devp_pglist = {tqh_first = 0x1, : tqh_last = 0x0}}, swp = {swp_bcount = 1}}} : :I'll keep this dump around. What other details do people want? : :I'm not likely to even get to look at this let alone solve it. Bummer. : :Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 09:49:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23174 for freebsd-current-outgoing; Thu, 4 Feb 1999 09:49:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23168 for ; Thu, 4 Feb 1999 09:49:54 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id JAA89484; Thu, 4 Feb 1999 09:49:50 -0800 (PST) (envelope-from dillon) Date: Thu, 4 Feb 1999 09:49:50 -0800 (PST) From: Matthew Dillon Message-Id: <199902041749.JAA89484@apollo.backplane.com> To: Matthew Dillon Cc: Stephen McKay , freebsd-current@FreeBSD.ORG, syssgm@detir.qld.gov.au Subject: Re: panic: vm_object_qcollapse(): object mismatch References: <199902041300.XAA10590@nymph.detir.qld.gov.au> <199902041726.JAA88650@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I introduced this bug in 1.139 when I added the KASSERT(). Bleh. However, the code still needs to be protected at splbio(). And so I've committed. -Matt : Hmmm. This looks like an out-an-out bug to me. The assertion is wrong. : It's scanning the backing_object and asserting that the pages in the : backing object are associated with object rather then backing_object. : : This section of code only runs when paging is in progress on a : collapseable object AND there are also idle pages in that object. : The collapse condition is probably due to an exiting process ( typical : in a buildworld ). : : ( from vm/vm_object.c ) : /* : * busy the page and move it from the backing store to the : * parent object. : */ : : vm_page_busy(p); : : KASSERT(p->object == object, ("vm_object_qcollapse(): object mismatch")); : ^^^^^^^^^^ : should be 'backing_object' : : There is also an interrupt race. Since paging can be in progress, : pages in the object can be ripped out from under it so we have to : run at splbio() in the loop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 09:57:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24469 for freebsd-current-outgoing; Thu, 4 Feb 1999 09:57:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24459 for ; Thu, 4 Feb 1999 09:57:53 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id CAA26914; Fri, 5 Feb 1999 02:57:46 +0900 (JST) Message-ID: <36B9DE6B.A6A1071C@newsguy.com> Date: Fri, 05 Feb 1999 02:52:43 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: HEADS UP: loader has changed References: <199902041723.CAA00600@daniel.sobral> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" wrote: > > I just committed patches to make "include" work with source code. ^^^^^^ That should have been _forth_ source code. > Previously, it only processed builtins, greatly diminishing both > ficl and include's usefulness. > > As a result of this change, the special behavior of the chacters @, > # and - at the beginning of script lines is lost. They have been > replaced as follow: > > @ Lines will *not* be echoed anymore by default. Thus, lines > with "@" can simply remove it. If one wants to echo a line, > use the character "$", with a space after it. > > # Use "\" followed by a space. > > - Use "%" followed by a space. > > Examples: > > \ This is a comment > load dont.echo > $ load echo > % load ignore.errors > > Since the new "characters" are forth words, they can be used anywhere in > the line. So you can add comments *after* the command, for example. They > can also be used together: > > % $ load /kernel.experimental > > I apologize for the inconvenience this may cause, but the previous way > is highly incompatible with forth. > > -- > Daniel C. Sobral (8-DCS) > dcs@gns.com.br > > The trouble with eating Italian food is that > five or six days later you're hungry again. > -- George Miller > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Daniel C. Sobral (8-DCS) dcs@newsguy.com She just looked at him over the rotating pencil like, how slow can a mammal be and still have respiratory functions? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 10:03:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25152 for freebsd-current-outgoing; Thu, 4 Feb 1999 10:03:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-8-dbn.dial-up.net [196.34.155.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25144 for ; Thu, 4 Feb 1999 10:03:07 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id UAA26086; Thu, 4 Feb 1999 20:01:18 +0200 (SAT) From: Robert Nordier Message-Id: <199902041801.UAA26086@ceia.nordier.com> Subject: Re: boot0 does not remember F5 In-Reply-To: <36B9D0CF.8EB9BC65@we.lc.ehu.es> from "Jose M. Alcaide" at "Feb 4, 99 05:54:39 pm" To: jose@we.lc.ehu.es (Jose M. Alcaide) Date: Thu, 4 Feb 1999 20:01:15 +0200 (SAT) Cc: freebsd-current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jose M. Alcaide wrote: > Boot0 does its job, so I can choose between the two disks pressing > F1 or F5. However, the default option is _always_ F1, despite > of being F5 the last choice. Is this a bug or a "feature" :-) ? This issue has already been discussed today (see the thread "Boot block problem" a few messages back). -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 10:31:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29230 for freebsd-current-outgoing; Thu, 4 Feb 1999 10:31:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29224 for ; Thu, 4 Feb 1999 10:31:57 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id KAA05942; Thu, 4 Feb 1999 10:30:52 -0800 (PST) From: Archie Cobbs Message-Id: <199902041830.KAA05942@bubba.whistle.com> Subject: Re: Boot block problem In-Reply-To: <199902041614.IAA15035@dingo.cdrom.com> from Mike Smith at "Feb 4, 99 08:14:12 am" To: mike@smith.net.au (Mike Smith) Date: Thu, 4 Feb 1999 10:30:52 -0800 (PST) Cc: rnordier@nordier.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > > The new boot manager remembers "last slice selected" rather than > > "last menu option selected" on each drive. > > > > I think I prefer this behavior myself, but I'll change it for > > compatibility with booteasy. > > In the case where the last action was to chain to another disk, that's > definitely preferable... Ah yes, that's what is happening to me, as I need to remember "F5". Please let me know how I can get the necessary changes and whether you want me to test them. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 10:53:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01772 for freebsd-current-outgoing; Thu, 4 Feb 1999 10:53:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oreo.adsu.bellsouth.com (oreo.adsu.bellsouth.com [205.152.173.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01763 for ; Thu, 4 Feb 1999 10:53:24 -0800 (PST) (envelope-from ck@oreo.adsu.bellsouth.com) Received: (from ck@localhost) by oreo.adsu.bellsouth.com (8.9.1/8.9.1) id IAA51602 for freebsd-current@freebsd.org; Thu, 4 Feb 1999 08:30:13 -0500 (EST) (envelope-from ck) Date: Thu, 4 Feb 1999 08:30:13 -0500 From: Christian Kuhtz To: freebsd-current@FreeBSD.ORG Subject: make release failure Message-ID: <19990204083013.N600@oreo.adsu.bellsouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just tried a make release late last night eastern time, and it blew up in this stage. ===> Verifying install for /usr/local/share/sgml/iso8879/catalog in /usr/ports/textproc/iso8879 make: argument list too long *** Error code 2 1 error -- "Be careful of reading health books, you might die of a misprint." -- Mark Twain [Disclaimer: I speak for myself and my views are my own and not in any way to be construed as the views of BellSouth Corporation. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 11:05:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03802 for freebsd-current-outgoing; Thu, 4 Feb 1999 11:05:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail11.digital.com (mail11.digital.com [192.208.46.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03775 for ; Thu, 4 Feb 1999 11:05:19 -0800 (PST) (envelope-from perry@zso.dec.com) Received: from yakko.zso.dec.com (yakko.zso.dec.com [16.64.16.191]) by mail11.digital.com (8.9.1a/8.9.1/WV2.0d) with ESMTP id OAA21990; Thu, 4 Feb 1999 14:05:16 -0500 (EST) Received: from localhost (perry@localhost) by yakko.zso.dec.com (8.9.1/8.9.1) with SMTP id LAA10608; Thu, 4 Feb 1999 11:05:04 -0800 (PST) Message-Id: <199902041905.LAA10608@yakko.zso.dec.com> X-Authentication-Warning: yakko.zso.dec.com: perry@localhost didn't use HELO protocol To: Alfred Perlstein cc: "Reginald S. Perry" , Jeroen Ruigrok/Asmodai , Andrew Gordon , current@FreeBSD.ORG, Matthew Dillon Reply-To: perry@zso.dec.com Subject: Re: 4.0-Current, netscape halts system In-reply-to: Message from Alfred Perlstein of "Tue, 26 Jan 1999 03:07:33 EST." Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Thu, 04 Feb 1999 11:04:59 -0800 From: "Reginald S. Perry" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I finally got everything set up as far as having my vt220 being my console and being able to drop into DDB by hitting the break key. It turns out that as part of my setup I was using MFS for /tmp. When I did a CVSup and make world on the 29th, I decided to comment out the MFS mount point. I have not had a hang since then. So the question is are there known problems with MFS? -Reggie >"Alfred" == Alfred Perlstein writes: > On Mon, 25 Jan 1999, Reginald S. Perry wrote: I have been having > these X lockups with the linux netscape 4.5 running. I may have > exacerbated it when I installed the linux realplayer and macromedia > flash plugins. > > I would like to have a methodology to help debug this, but I have > just this one system to use as the debug system. I do also have a > vt220 which I could set up if that would help. > > The key here is that for me it locks the system up completely. I > cannot telnet in remotely and the ctrl-alt-esc key sequence does not > work so its unclear to me how to debug this. Tell me what I would > need to help debug it, and I will try to be of some help. Ill attach > my dmesg output. > > -Reggie > > options DDB options BREAK_TO_DEBUGGER #a BREAK on a comconsole goes > to options INVARIANTS options INVARIANT_SUPPORT > device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device > sio1 at isa? port "IO_COM2" flags 0x30 tty irq 3 vector siointr > my 'sio2' is setup with special flags to make it always be the > consol. look in lint for more hints. > when the machine locks: send a break: if on vt220: F5 using tip/cu: > ~% > take a look at 'ps' and copy it down to see what's up. > you may also want to enable crash dumps, look in rc.conf and set > your 'dumpdevice' to your swap partition. then you can type 'panic' > and get a core image of the system to look at. > on the next reboot you can 'kdb' the kernel and then type 'bt' to > get a backtrace. > i have a vt320 for vanity purposes :), but i suggest you use a > serial line into an xterm on another box if you can, ddb isn't the > nicest interface and being able to cut and paste in and out of ddb > in an xterm is nice. > -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 11:32:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07850 for freebsd-current-outgoing; Thu, 4 Feb 1999 11:32:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA07819 for ; Thu, 4 Feb 1999 11:32:19 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA14447 (5.67b/IDA-1.5); Thu, 4 Feb 1999 20:18:17 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id TAA00914; Thu, 4 Feb 1999 19:34:40 +0100 (CET) From: Wilko Bulte Message-Id: <199902041834.TAA00914@yedi.iaf.nl> Subject: Re: ifq_maxlen problem... In-Reply-To: from "Open Systems Inc." at "Feb 4, 99 10:30:05 am" To: opsys@open-systems.net (Open Systems Inc.) Date: Thu, 4 Feb 1999 19:34:40 +0100 (CET) Cc: jarekb@freebsd.org.pl, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Open Systems Inc. wrote... > On Thu, 4 Feb 1999, Jaroslaw Bazydlo wrote: > > > After yesterdays 'make world' I am having such warnings: > > > ep0 XXX: driver didn't set ifq_maxlen > > lo0 XXX: driver didn't set ifq_maxlen > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > The system itself seems to work fine (for last 24 hrs). What do those > > messages mean??? Does anyone of you noticed similar messages??? > > I get the same thing for my kingston DEC based 10/100 card and lo0. > The card still works though so the chance of this being life threatening > are low :-) Interesting. I have the same Kingston 10/100 and I've never seen it. YMMV obviously. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 13:48:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26247 for freebsd-current-outgoing; Thu, 4 Feb 1999 13:48:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26230 for ; Thu, 4 Feb 1999 13:48:02 -0800 (PST) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id TAA21532; Thu, 4 Feb 1999 19:47:46 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199902042147.TAA21532@roma.coe.ufrj.br> Subject: Re: Overview of the FreeBSD boot process, 3.1 and later In-Reply-To: <199902030206.SAA02590@dingo.cdrom.com> from Mike Smith at "Feb 2, 1999 6: 6:32 pm" To: mike@smith.net.au (Mike Smith) Date: Thu, 4 Feb 1999 19:47:46 -0200 (EDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG #define quoting(Mike Smith) // I'm in the process of preparing a document describing the FreeBSD boot // process in the new age. At the moment, there's some emphasis on the // loader, and probably an uneven level of detail elsewhere. Commentary // is invited. // // http://www.freebsd.org/~msmith/FTL/bootstrap.txt Cool !!! We really needed such a documentation... My sugestions: 1) Explain a bit more how boot0 works, and which consequences could this behavior have on another operating systems installed. For example, say that it remembers the last booted slice by rewriting itself. BTW: Can this be disabled ? Sometimes this is not needed/wanted, and the only current solution is to use os-bs. 2) Update it for the last changes in /boot/loader by Daniel Sobral. IIRC: @, # and - are gone. BTW: If variables were identified by a $ sign, and the $ sign is now an "echo on execute" command, how will variables be identified now ? Or have I misunderstood something ? 3) Give more real examples in the load -t section. I'd include mfs_root and splash_image_data, for example. Or, at least, send the reader to some reference elsewhere. Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 13:52:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26948 for freebsd-current-outgoing; Thu, 4 Feb 1999 13:52:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26926 for ; Thu, 4 Feb 1999 13:52:33 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id WAA64476; Thu, 4 Feb 1999 22:22:18 +0100 (CET) (envelope-from des) To: Brian Feldman Cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: Heads up: comitted optimization to vm_map_insert() References: From: Dag-Erling Smorgrav Date: 04 Feb 1999 22:22:16 +0100 In-Reply-To: Brian Feldman's message of "Thu, 4 Feb 1999 04:57:46 -0500 (EST)" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman writes: > On Wed, 3 Feb 1999, Matthew Dillon wrote: > > My "do lots of things that force the machine to page up the wazoo and > > try to make it crash" test :-) > So do you run Netscape, or do you run StarOffice? ;) Just trying to compile Applix should be enough. Ask Mike ;) DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 14:19:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00623 for freebsd-current-outgoing; Thu, 4 Feb 1999 14:19:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00611 for ; Thu, 4 Feb 1999 14:19:55 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id OAA90785; Thu, 4 Feb 1999 14:19:54 -0800 (PST) (envelope-from dillon) Date: Thu, 4 Feb 1999 14:19:54 -0800 (PST) From: Matthew Dillon Message-Id: <199902042219.OAA90785@apollo.backplane.com> To: current@FreeBSD.ORG Subject: Bug in piperd Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ha. I've been slowly reducing MAXMEM on my test box to force it to swap more heavily running buildworld and found a race in the kern/sys_pipe.c module. My buildworld froze up... i.e. just stopped running. Everything else on the box was fine. ps showed an 'as' command stuck in 'piperd'. The problem is simple (pseudo code fragment): pipe read: ... * check for EOF * check for waiting writers * lock the pipe * check for waiting writers * check for non-blocking I/O * sleep in 'piperd' The problem, of course, is that if 'lock the pipe' blocks, it is possible for the writer side to close the pipe. Since EOF is not checked for after the pipe has been locked, the reader enters a 'piperd' state and never gets woken up again. I am testing a fix now and will then commit it. If anyone sees anything obviously wrong with this patch, please email me. -Matt Matthew Dillon Index: sys_pipe.c =================================================================== RCS file: /home/ncvs/src/sys/kern/sys_pipe.c,v retrieving revision 1.49 diff -u -r1.49 sys_pipe.c --- sys_pipe.c 1999/01/28 00:57:47 1.49 +++ sys_pipe.c 1999/02/04 22:14:58 @@ -381,12 +381,32 @@ #endif } else { /* + * If there is no more to read in the pipe, reset + * its pointers to the beginning. This improves + * cache hit stats. + * + * We get this over with now because it may block + * and cause the state to change out from under us, + * rather then have to re-test the state both before + * and after this fragment. + */ + + if ((error = pipelock(rpipe,1)) == 0) { + if (rpipe->pipe_buffer.cnt == 0) { + rpipe->pipe_buffer.in = 0; + rpipe->pipe_buffer.out = 0; + } + pipeunlock(rpipe); + } + + /* * detect EOF condition */ if (rpipe->pipe_state & PIPE_EOF) { /* XXX error = ? */ break; } + /* * If the "write-side" has been blocked, wake it up now. */ @@ -394,34 +414,26 @@ rpipe->pipe_state &= ~PIPE_WANTW; wakeup(rpipe); } - if (nread > 0) + + /* + * break if error (signal via pipelock), or if some + * data was read + */ + if (error || nread > 0) break; + /* + * Handle non-blocking mode operation + */ + if (fp->f_flag & FNONBLOCK) { error = EAGAIN; break; } /* - * If there is no more to read in the pipe, reset - * its pointers to the beginning. This improves - * cache hit stats. + * Wait for more data */ - - if ((error = pipelock(rpipe,1)) == 0) { - if (rpipe->pipe_buffer.cnt == 0) { - rpipe->pipe_buffer.in = 0; - rpipe->pipe_buffer.out = 0; - } - pipeunlock(rpipe); - } else { - break; - } - - if (rpipe->pipe_state & PIPE_WANTW) { - rpipe->pipe_state &= ~PIPE_WANTW; - wakeup(rpipe); - } rpipe->pipe_state |= PIPE_WANTR; if ((error = tsleep(rpipe, PRIBIO|PCATCH, "piperd", 0)) != 0) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 14:30:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02462 for freebsd-current-outgoing; Thu, 4 Feb 1999 14:30:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02451 for ; Thu, 4 Feb 1999 14:30:26 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id OAA90906; Thu, 4 Feb 1999 14:30:26 -0800 (PST) (envelope-from dillon) Date: Thu, 4 Feb 1999 14:30:26 -0800 (PST) From: Matthew Dillon Message-Id: <199902042230.OAA90906@apollo.backplane.com> To: current@FreeBSD.ORG Subject: Re: Bug in piperd References: <199902042219.OAA90785@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Updated patch - one must also check to see if any new data has entered the pipe after locking it in case the lock blocked. ( this patch FYI only, the problem occurs unoften enough that you can afford to wait until I commit it ). -Matt Index: sys_pipe.c =================================================================== RCS file: /home/ncvs/src/sys/kern/sys_pipe.c,v retrieving revision 1.49 diff -u -r1.49 sys_pipe.c --- sys_pipe.c 1999/01/28 00:57:47 1.49 +++ sys_pipe.c 1999/02/04 22:24:42 @@ -381,12 +381,39 @@ #endif } else { /* + * If there is no more to read in the pipe, reset + * its pointers to the beginning. This improves + * cache hit stats. + * + * We get this over with now because it may block + * and cause the state to change out from under us, + * rather then have to re-test the state both before + * and after this fragment. + */ + + if ((error = pipelock(rpipe,1)) == 0) { + if (rpipe->pipe_buffer.cnt == 0) { + rpipe->pipe_buffer.in = 0; + rpipe->pipe_buffer.out = 0; + } + pipeunlock(rpipe); + + /* + * If pipe filled up due to pipelock + * blocking, loop back up. + */ + if (rpipe->pipe_buffer.cnt > 0) + continue; + } + + /* * detect EOF condition */ if (rpipe->pipe_state & PIPE_EOF) { /* XXX error = ? */ break; } + /* * If the "write-side" has been blocked, wake it up now. */ @@ -394,34 +421,26 @@ rpipe->pipe_state &= ~PIPE_WANTW; wakeup(rpipe); } - if (nread > 0) + + /* + * break if error (signal via pipelock), or if some + * data was read + */ + if (error || nread > 0) break; + /* + * Handle non-blocking mode operation + */ + if (fp->f_flag & FNONBLOCK) { error = EAGAIN; break; } /* - * If there is no more to read in the pipe, reset - * its pointers to the beginning. This improves - * cache hit stats. + * Wait for more data */ - - if ((error = pipelock(rpipe,1)) == 0) { - if (rpipe->pipe_buffer.cnt == 0) { - rpipe->pipe_buffer.in = 0; - rpipe->pipe_buffer.out = 0; - } - pipeunlock(rpipe); - } else { - break; - } - - if (rpipe->pipe_state & PIPE_WANTW) { - rpipe->pipe_state &= ~PIPE_WANTW; - wakeup(rpipe); - } rpipe->pipe_state |= PIPE_WANTR; if ((error = tsleep(rpipe, PRIBIO|PCATCH, "piperd", 0)) != 0) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 14:34:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03361 for freebsd-current-outgoing; Thu, 4 Feb 1999 14:34:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-33-dbn.dial-up.net [196.34.155.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03346 for ; Thu, 4 Feb 1999 14:34:16 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id AAA29549; Fri, 5 Feb 1999 00:32:36 +0200 (SAT) From: Robert Nordier Message-Id: <199902042232.AAA29549@ceia.nordier.com> Subject: Re: Overview of the FreeBSD boot process, 3.1 and later In-Reply-To: <199902042147.TAA21532@roma.coe.ufrj.br> from Joao Carlos Mendes Luis at "Feb 4, 99 07:47:46 pm" To: jonny@jonny.eng.br (Joao Carlos Mendes Luis) Date: Fri, 5 Feb 1999 00:32:24 +0200 (SAT) Cc: mike@smith.net.au, current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joao Carlos Mendes Luis wrote: > 1) Explain a bit more how boot0 works, and which consequences could > this behavior have on another operating systems installed. For > example, say that it remembers the last booted slice by rewriting > itself. BTW: Can this be disabled ? Sometimes this is not > needed/wanted, and the only current solution is to use os-bs. I think the best place to deal in detail with boot0 would be in a boot0(8) man page, similar in approach to the present boot(8). I'll try to get around to this in the next few days. It's useful that Mike's document touches on boot[012], but the loader is a big subject in it's own right -- and the one most people will want to read up on -- whereas boot0 is not even FreeBSD-specific, beyond being included in the distribution. To answer your question: yes, updates can be disabled. The easiest method at present is to define B0FLAGS (in the Makefile) as having bit 6 (0x40) set. Though a utility for installing and configuring the boot manager from the command line is in progress. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 14:37:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03780 for freebsd-current-outgoing; Thu, 4 Feb 1999 14:37:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03774 for ; Thu, 4 Feb 1999 14:37:07 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id OAA90952; Thu, 4 Feb 1999 14:37:03 -0800 (PST) (envelope-from dillon) Date: Thu, 4 Feb 1999 14:37:03 -0800 (PST) From: Matthew Dillon Message-Id: <199902042237.OAA90952@apollo.backplane.com> To: Dag-Erling Smorgrav Cc: Brian Feldman , current@FreeBSD.ORG Subject: Re: Heads up: comitted optimization to vm_map_insert() References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Brian Feldman writes: :> On Wed, 3 Feb 1999, Matthew Dillon wrote: :> > My "do lots of things that force the machine to page up the wazoo and :> > try to make it crash" test :-) :> So do you run Netscape, or do you run StarOffice? ;) : :Just trying to compile Applix should be enough. Ask Mike ;) : :DES :-- :Dag-Erling Smorgrav - des@flood.ping.uio.no At the moment I'm doing -j16 buildworlds with MFS mounted /usr/obj, NFS swap, NFS mounted /usr/src, and artificially limited main memory (32MB). The machine goes totally nuts compiling the perl stuff, paging in and paging out simultaniously at > 1 MByte/sec in each direction. But it slogs through it. Pretty soon I'm going to start experimenting with NFS-file-backed VN-mounted filesystems & combo NFS and IDE swap to better test the swap and vnode pagers under extreme load conditions. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 15:22:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09869 for freebsd-current-outgoing; Thu, 4 Feb 1999 15:22:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09863 for ; Thu, 4 Feb 1999 15:22:16 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id PAA29097; Thu, 4 Feb 1999 15:21:57 -0800 Date: Thu, 4 Feb 1999 15:21:57 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Dan Strick cc: freebsd-current@FreeBSD.ORG Subject: Re: /dev/nrsa0 file mark handling In-Reply-To: <199812240434.UAA10299@math.berkeley.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > "control open" - Already on my list. > > > > "mt_fileno/mt_blkno" - I'm mulling that one. Yes, I think I will, but > > it'll take a lot of work because there are (now) a large number of > > conditions that invalidate and make completely unknown those > > relative positions (EOD, hard block locating). > > > > "current state" - Interesting notion. > > My motivation for wanting these things is that I have a program >.... All three items are to be integrated today. There will be a control open device that allows you to open the device to retrieve stats (even if another application has the device open). You can (try) and set block size and density and compression via the control device open, but you'll pin (interruptibly) waiting for access to the device if another application has it open. There already is an Error Stats ioctl that is different from the regular MTIOCGET. The mt_fileno/mt_blkno will go in. Hopefully I'll have caught all the spots, but I will document in the man page that this information is not definitive. The only definitive information about tape position is BOT, End of Recorded Media and hardware block position (if supported by the drive). Current state will now be loaded int mt_dsreg. There will be some FreeBSD specific defines as to what the tape driver thinks that it is doing. mt(1) will be modified to print out the latter two items. After this point I plan to start development on using the HP TapeAlert initiative's rulesets for new tape behaviour. That should leverage FreeBSD into a number of markets. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 16:23:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20116 for freebsd-current-outgoing; Thu, 4 Feb 1999 16:23:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20109 for ; Thu, 4 Feb 1999 16:23:18 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id TAA22986; Thu, 4 Feb 1999 19:23:15 -0500 (EST) Date: Thu, 4 Feb 1999 19:23:14 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Dag-Erling Smorgrav cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: Heads up: comitted optimization to vm_map_insert() In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 4 Feb 1999, Dag-Erling Smorgrav wrote: > Brian Feldman writes: > > On Wed, 3 Feb 1999, Matthew Dillon wrote: > > > My "do lots of things that force the machine to page up the wazoo and > > > try to make it crash" test :-) > > So do you run Netscape, or do you run StarOffice? ;) > > Just trying to compile Applix should be enough. Ask Mike ;) Hah, I remember when I tried compiling (old-school) Mozilla, and ld was over 100mb ;) People need more RAM like in Jordan's home box, or wcarchive for that matter! This summer, hope I'll get my 512mb, and say goodbye to wd[03]s1b =) Let's ask Mr. VM if the fixes he did today were the culprits for his sig11, shall we? > > DES > -- > Dag-Erling Smorgrav - des@flood.ping.uio.no > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 16:32:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21189 for freebsd-current-outgoing; Thu, 4 Feb 1999 16:32:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA21180 for ; Thu, 4 Feb 1999 16:32:33 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA11097; Thu, 4 Feb 1999 16:30:56 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdP11061; Fri Feb 5 00:30:52 1999 Message-ID: <36BA3B93.2781E494@whistle.com> Date: Thu, 04 Feb 1999 16:30:11 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: Matthew Dillon CC: current@FreeBSD.ORG Subject: Re: Bug in piperd References: <199902042219.OAA90785@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been seeng lockups in 3.0 where as is in piperd, but the stack trace has always looked as if the problem was in soft updates or the syncer daemon.. Matthew Dillon wrote: > > Ha. I've been slowly reducing MAXMEM on my test box to force it to > swap more heavily running buildworld and found a race in the > kern/sys_pipe.c module. > > My buildworld froze up... i.e. just stopped running. Everything else > on the box was fine. ps showed an 'as' command stuck in 'piperd'. > > The problem is simple (pseudo code fragment): > > pipe read: > ... > * check for EOF > * check for waiting writers > * lock the pipe > * check for waiting writers > * check for non-blocking I/O > * sleep in 'piperd' > > The problem, of course, is that if 'lock the pipe' blocks, it is possible > for the writer side to close the pipe. Since EOF is not checked for > after the pipe has been locked, the reader enters a 'piperd' state > and never gets woken up again. > > I am testing a fix now and will then commit it. > > If anyone sees anything obviously wrong with this patch, please email me. > > -Matt > Matthew Dillon > > > Index: sys_pipe.c > =================================================================== > RCS file: /home/ncvs/src/sys/kern/sys_pipe.c,v > retrieving revision 1.49 > diff -u -r1.49 sys_pipe.c > --- sys_pipe.c 1999/01/28 00:57:47 1.49 > +++ sys_pipe.c 1999/02/04 22:14:58 > @@ -381,12 +381,32 @@ > #endif > } else { > /* > + * If there is no more to read in the pipe, reset > + * its pointers to the beginning. This improves > + * cache hit stats. > + * > + * We get this over with now because it may block > + * and cause the state to change out from under us, > + * rather then have to re-test the state both before > + * and after this fragment. > + */ > + > + if ((error = pipelock(rpipe,1)) == 0) { > + if (rpipe->pipe_buffer.cnt == 0) { > + rpipe->pipe_buffer.in = 0; > + rpipe->pipe_buffer.out = 0; > + } > + pipeunlock(rpipe); > + } > + > + /* > * detect EOF condition > */ > if (rpipe->pipe_state & PIPE_EOF) { > /* XXX error = ? */ > break; > } > + > /* > * If the "write-side" has been blocked, wake it up now. > */ > @@ -394,34 +414,26 @@ > rpipe->pipe_state &= ~PIPE_WANTW; > wakeup(rpipe); > } > - if (nread > 0) > + > + /* > + * break if error (signal via pipelock), or if some > + * data was read > + */ > + if (error || nread > 0) > break; > > + /* > + * Handle non-blocking mode operation > + */ > + > if (fp->f_flag & FNONBLOCK) { > error = EAGAIN; > break; > } > > /* > - * If there is no more to read in the pipe, reset > - * its pointers to the beginning. This improves > - * cache hit stats. > + * Wait for more data > */ > - > - if ((error = pipelock(rpipe,1)) == 0) { > - if (rpipe->pipe_buffer.cnt == 0) { > - rpipe->pipe_buffer.in = 0; > - rpipe->pipe_buffer.out = 0; > - } > - pipeunlock(rpipe); > - } else { > - break; > - } > - > - if (rpipe->pipe_state & PIPE_WANTW) { > - rpipe->pipe_state &= ~PIPE_WANTW; > - wakeup(rpipe); > - } > > rpipe->pipe_state |= PIPE_WANTR; > if ((error = tsleep(rpipe, PRIBIO|PCATCH, "piperd", 0)) != 0) { > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 16:37:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21764 for freebsd-current-outgoing; Thu, 4 Feb 1999 16:37:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA21759 for ; Thu, 4 Feb 1999 16:37:22 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id QAA91805; Thu, 4 Feb 1999 16:37:20 -0800 (PST) (envelope-from dillon) Date: Thu, 4 Feb 1999 16:37:20 -0800 (PST) From: Matthew Dillon Message-Id: <199902050037.QAA91805@apollo.backplane.com> To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: Bug in piperd References: <199902042219.OAA90785@apollo.backplane.com> <36BA3B93.2781E494@whistle.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :I've been seeng lockups in 3.0 where as is in piperd, :but the stack trace has always looked as if the problem was in soft :updates or the syncer daemon.. : It's quite possible for as to be in 'piperd' when some other unassociated crash occurs, since it is typically waiting for input from cc1. What is not typical, however, is if as is stuck 'piperd' and the other end of the pipe has been closed. The particular piperd bug I found cannot crash the system - at worst it will block a process forever. And you can still kill the process. 3.0's lockups could be very well due to a number of low-memory interlock situations that typically occur when heavy paging is going on, if that is how you are running 3.0. I suspect it is too late to get my getpbuf() changes into 3.1, which might mitigate that somewhat. -Matt Matthew Dillon :> The problem is simple (pseudo code fragment): :> :> pipe read: :> ... :> * check for EOF :> * check for waiting writers :> * lock the pipe :> * check for waiting writers :> * check for non-blocking I/O :> * sleep in 'piperd' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 16:51:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23608 for freebsd-current-outgoing; Thu, 4 Feb 1999 16:51:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23603 for ; Thu, 4 Feb 1999 16:51:34 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA12291; Thu, 4 Feb 1999 16:47:08 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdp12278; Fri Feb 5 00:46:58 1999 Message-ID: <36BA3F7D.15FB7483@whistle.com> Date: Thu, 04 Feb 1999 16:46:53 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: Matthew Dillon CC: current@FreeBSD.ORG Subject: Re: Bug in piperd References: <199902042219.OAA90785@apollo.backplane.com> <36BA3B93.2781E494@whistle.com> <199902050037.QAA91805@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > : > :I've been seeng lockups in 3.0 where as is in piperd, > :but the stack trace has always looked as if the problem was in soft > :updates or the syncer daemon.. > : > > It's quite possible for as to be in 'piperd' when some other unassociated > crash occurs, since it is typically waiting for input from cc1. What > is not typical, however, is if as is stuck 'piperd' and the other end of > the pipe has been closed. > > The particular piperd bug I found cannot crash the system - at worst it > will block a process forever. And you can still kill the process. > > 3.0's lockups could be very well due to a number of low-memory interlock > situations that typically occur when heavy paging is going on, if that is > how you are running 3.0. I suspect it is too late to get my getpbuf() > changes into 3.1, which might mitigate that somewhat. the lockups are in a 2 day old SNAP of 3.x To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 16:52:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23681 for freebsd-current-outgoing; Thu, 4 Feb 1999 16:52:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles146.castles.com [208.214.165.146]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23664 for ; Thu, 4 Feb 1999 16:52:03 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA17840; Thu, 4 Feb 1999 16:47:52 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902050047.QAA17840@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: Bug in piperd In-reply-to: Your message of "Thu, 04 Feb 1999 16:37:20 PST." <199902050037.QAA91805@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Feb 1999 16:47:51 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 3.0's lockups could be very well due to a number of low-memory interlock > situations that typically occur when heavy paging is going on, if that is > how you are running 3.0. I suspect it is too late to get my getpbuf() > changes into 3.1, which might mitigate that somewhat. If you can demonstrate that they work and have the desired effect, you could make a good case for this. If you have the time, a lot of people would appreciate the effort. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 17:31:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28239 for freebsd-current-outgoing; Thu, 4 Feb 1999 17:31:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mta2.iol.it (mta2.iol.it [195.210.91.152]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28233 for ; Thu, 4 Feb 1999 17:31:41 -0800 (PST) (envelope-from ugo@dsi.unifi.it) Received: from dsi.unifi.it ([212.52.70.31]) by mta2.iol.it (Netscape Messaging Server 3.6) with ESMTP id AAA736A for ; Fri, 5 Feb 1999 02:31:37 +0100 Received: from pegasus.home.net (pegasus.home.net [192.168.1.3]) by dsi.unifi.it (8.9.2/8.9.2) with ESMTP id CAA00455; Fri, 5 Feb 1999 02:03:41 +0100 (CET) (envelope-from ugo) Received: (from ugo@localhost) by pegasus.home.net (8.9.2/8.9.2) id CAA06507; Fri, 5 Feb 1999 02:03:40 +0100 (CET) (envelope-from ugo) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <199902040020.CAA20072@ceia.nordier.com> Date: Fri, 05 Feb 1999 02:03:39 +0100 (CET) Organization: Not an organization From: Ugo Paternostro To: Robert Nordier Subject: Re: Reading a text file with BTX Cc: dcs@newsguy.com, freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Feb-99 Robert Nordier wrote about "Re: Reading a text file with BTX": >> >> Right on the mark. BTW, my BIOS is set so the cd drive is searched >> >> before the hd on boot. Could that be the cause? >> > >> > Seems a reasonable assumption, but I don't know for sure. >> >> It is. > > Proof? I simply meant that it happened to me once on a 586 FX M/B: it disappeared when I selected "C/CDROM/A" as the drive to boot from in the BIOS. I cannot remember the version of the BootManager I tried, if that means anything. > Robert Nordier Bye, UP To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 18:00:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02980 for freebsd-current-outgoing; Thu, 4 Feb 1999 18:00:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from as5200-01-254.no.neosoft.com (as5200-01-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02971 for ; Thu, 4 Feb 1999 18:00:25 -0800 (PST) (envelope-from conrads@as5200-01-254.no.neosoft.com) Received: (from conrads@localhost) by as5200-01-254.no.neosoft.com (8.9.2/8.8.7) id TAA01583 for current@FreeBSD.ORG; Thu, 4 Feb 1999 19:20:23 -0600 (CST) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 04 Feb 1999 19:20:23 -0600 (CST) Reply-To: conrads@neosoft.com From: Conrad Sabatier To: current@FreeBSD.ORG Subject: Re: ifq_maxlen problem... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Feb-99 Jaroslaw Bazydlo wrote: > After yesterdays 'make world' I am having such warnings: > > FreeBSD 4.0-CURRENT #0: Thu Feb 4 17:19:09 GMT 1999 > jarekb@ent.freebsd.org.pl:/usr/src/sys/compile/ENT > [...] > ep0 at 0x300-0x30f irq 10 on isa > ep0: utp/bnc[*UTP*] address 00:60:08:65:d6:8d > [...] > ep0 XXX: driver didn't set ifq_maxlen > lo0 XXX: driver didn't set ifq_maxlen > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > The system itself seems to work fine (for last 24 hrs). What do those > messages mean??? Does anyone of you noticed similar messages??? > > The NIC is 3com 3c509B. Just cvsup'ed, made world and kernel today (Thursday, 2/4), and am seeing the same thing at bootup (on lo0; I have no network interfaces installed). No idea what it means or what's causing it, but it seems pretty harmless. -- Conrad Sabatier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 18:43:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09127 for freebsd-current-outgoing; Thu, 4 Feb 1999 18:43:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailin.hkstar.com (cygnus.hkstar.com [202.82.3.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09114 for ; Thu, 4 Feb 1999 18:43:46 -0800 (PST) (envelope-from c5666305@ursa.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by mailin.hkstar.com (8.8.8/8.8.5) with ESMTP id KAA28124 for ; Fri, 5 Feb 1999 10:43:43 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8+Sun/8.8.8) id KAA05621 for freebsd-current@freebsd.org; Fri, 5 Feb 1999 10:43:47 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199902050243.KAA05621@b1.hkstar.com> Subject: which star office 5.0 works with -current To: freebsd-current@FreeBSD.ORG Date: Fri, 5 Feb 1999 10:43:46 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I had checked ftp.stardiv.com and found that there are several star office 5.0 under the directory /pub/so5. I would like to know which one works with -current. 1. so50_01.tar Nov 5 2. so50_33.tar Dec18 3. so50_39.tar Dec18 4. so50_49.tar Nov 5 cheers.. Clarence To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 18:56:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11413 for freebsd-current-outgoing; Thu, 4 Feb 1999 18:56:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11388 for ; Thu, 4 Feb 1999 18:56:38 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id SAA31885; Thu, 4 Feb 1999 18:55:57 -0800 (PST) From: Archie Cobbs Message-Id: <199902050255.SAA31885@bubba.whistle.com> Subject: Re: CALL FOR REVIEW: man page update In-Reply-To: <199902041433.XAA15337@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Feb 4, 99 11:33:07 pm" To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Thu, 4 Feb 1999 18:55:57 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA writes: > In order to reflect the recent changes regarding syscons, keyboard and > video drivers, I wrote the following new man pages and update for a > couple of existing ones. They are rudimentary, but better than > nothing. > > http://www.freebsd.org/~yokota/man4update.tar.gz I've added a couple of tweaks. For some reason the ".Fx" macro doesn't work on my terminal (using "nroff -man foo.4"), it just replaces the O/S version with nothing.. so I used ".Tn" instead which is what the pnpinfo(8) man page uses. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com diff -ur old/atkbd.4 new/atkbd.4 --- old/atkbd.4 Thu Feb 4 05:45:09 1999 +++ new/atkbd.4 Thu Feb 4 18:41:41 1999 @@ -69,7 +69,8 @@ The .Nm driver first appeared in -.Fx 3.1 . +.Tn FreeBSD +3.1. .Sh AUTHORS The .Nm diff -ur old/atkbdc.4 new/atkbdc.4 --- old/atkbdc.4 Thu Feb 4 05:45:10 1999 +++ new/atkbdc.4 Thu Feb 4 18:43:06 1999 @@ -77,9 +77,11 @@ The .Nm driver first appeared in -.Fx 3.1 . +.Tn FreeBSD +3.1. It is based on the kbdio module in -.Fx 2.2 . +.Tn FreeBSD +2.2. .Sh AUTHORS The kbdio module and the .Nm diff -ur old/splash.4 new/splash.4 --- old/splash.4 Thu Feb 4 05:45:15 1999 +++ new/splash.4 Thu Feb 4 18:48:38 1999 @@ -30,8 +30,8 @@ .Fl c or .Fl v -boot option when loading kernel, the splash image won't appear. -(But is still loaded and can be used as a screen saver later; see below.) +boot option when loading kernel, the splash image won't appear +(though it is still loaded and can be used as a screen saver later; see below). .Pp In order to display the bitmap, the bitmap file itself and matching splash image decoder must be loaded by the boot loader. @@ -41,7 +41,7 @@ .It splash_bmp.ko W*ndows BMP file decoder. While the BMP file format allows various depth of colors, this decoder -can handle 256 color bitmaps only. +can only handle 256 color bitmaps. Other color depth won't work. .El .Pp @@ -122,11 +122,11 @@ The screen saver won't run if the current screen is not in the text mode. .Sh SPLASH SCREEN AS A SCREEN SAVER -If you load splash image but don't load a screen saver, +If you load a splash image but don't load a screen saver, you can continue using the splash module as a screen saver. Specify the screen blanking interval as explained in the .Sx SCREEN SAVER -section above, then +section above, and the splash screen image will come back after the specified time. .\".Sh DRIVER CONFIGURATION .Sh FILES @@ -188,7 +188,7 @@ .Xr pcvt 4 . .Sh BUGS If you load a screen saver while another screen saver has already -been loaded, the first screen saver won't be automatically unloaed +been loaded, the first screen saver won't be automatically unloaded and remain in memory, wasting kernel memory space. .Sh SEE ALSO .Xr vidcontrol 1 , @@ -197,12 +197,13 @@ .Xr loader.rc 5 , .Xr rc.conf 5 , .Xr kldload 8 , -.Xr kldunload 8 , +.Xr kldunload 8 . .Sh HISTORY The .Nm driver first appeared in -.Fx 3.1 . +.Tn FreeBSD +3.1. .Sh AUTHORS The .Nm diff -ur old/vga.4 new/vga.4 --- old/vga.4 Thu Feb 4 05:45:18 1999 +++ new/vga.4 Thu Feb 4 18:52:40 1999 @@ -50,7 +50,7 @@ option is required in the kernel configuration file in this case too. .Sh DRIVER CONFIGURATION .Ss Kernel Configuration Options -There are following kernel configuration options to control the +The following kernel configuration options control the .Nm driver. They may be set in the kernel configuration file @@ -81,7 +81,7 @@ option. .It Em VESA_DEBUG=N Set the VESA support debug level to N. -The default value is zero and all debugging output is suppressed. +The default value is zero (all debugging output is suppressed). .El .Pp The following options will remove some features from the @@ -128,14 +128,18 @@ .Sh SEE ALSO .Xr syscons 4 , .Xr kldload 8 , -.Xr kldunload 8 +.Xr kldunload 8 . .Sh STANDARD -``VESA BIOS Extension (VBE)'', Video Electronics Standards Association. +.Rs +.%T "VESA BIOS Extension (VBE)" +.%A Video Electronics Standards Association +.Re .Sh HISTORY The .Nm driver first appeared in -.Fx 3.1 . +.Tn FreeBSD +3.1. .Sh AUTHORS The .Nm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 19:06:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA12757 for freebsd-current-outgoing; Thu, 4 Feb 1999 19:06:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA12747 for ; Thu, 4 Feb 1999 19:06:11 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 27075 invoked from network); 5 Feb 1999 03:05:30 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 5 Feb 1999 03:05:30 -0000 Received: (from root@localhost) by y.dyson.net (8.9.1/8.9.1) id WAA00818; Thu, 4 Feb 1999 22:05:28 -0500 (EST) Message-Id: <199902050305.WAA00818@y.dyson.net> Subject: Re: aio_read panics SMP kernel In-Reply-To: <199902031932.OAA01903@dean.pc.sas.com> from Brian Dean at "Feb 3, 99 02:32:24 pm" To: brdean@unx.sas.com (Brian Dean) Date: Thu, 4 Feb 1999 22:05:28 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Dean said: > > I'm using a dual 350MHz Dell Precision 410 with 4.0-19990130-SNAP (SMP > enabled) to prototype a program that uses asynchronous read and write > (aio_read() and aio_write()), and found that the following simple and > not very useful program (it's for demonstration purposes only!) causes > the system to do one of three things: > The VM code needs to be upgraded to support proper threading and shared address space operations under SMP. That is a major missing feature, and probably something that should be higher priority than it currently is. I have experimental work to support it (and alot of other interesting things), but it will probably be quite a while before those who are currently working on the code will be able to add the capability. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 19:09:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13240 for freebsd-current-outgoing; Thu, 4 Feb 1999 19:09:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA13233 for ; Thu, 4 Feb 1999 19:09:50 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 2980 invoked from network); 5 Feb 1999 03:09:46 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 5 Feb 1999 03:09:46 -0000 Received: (from root@localhost) by y.dyson.net (8.9.1/8.9.1) id WAA00824; Thu, 4 Feb 1999 22:09:36 -0500 (EST) Message-Id: <199902050309.WAA00824@y.dyson.net> Subject: Re: more about yield() versus sched_yield() In-Reply-To: <19990131094029.D29670@tar.com> from "Richard Seaman, Jr." at "Jan 31, 99 09:40:29 am" To: dick@tar.com (Richard Seaman, Jr.) Date: Thu, 4 Feb 1999 22:09:36 -0500 (EST) Cc: dufault@hda.com, jb@cimlogic.com.au, current@FreeBSD.ORG, bde@zeta.org.au From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Seaman, Jr. said: > > As I indicated to you several weeks ago, I think it is possible to have > a priority inversion problem in spinlocks that spin on sched_yield. > The yield call, as implemented, partly addresses the issue. However, > as you commented to me, it does so poorly. > > If the consensus is to drop or modify SYS_yield, my vote would be to > give consideration to changing the call to more correctly address the > priority inversion issue. Possibly a yield (pid_t pid) where the > pid passed in is the pid of the thread (process) holding a lock. The > system could then check the credentials of the pid to see if there > is permission (eg. its a kernel thread of the same process) and if > so, raise the priority of pid to that of the calling process for one > time slice so pid has a chance to execute and free the lock. > I didn't add the system call to the library (yet), because wasn't sure if it was working the way that I wanted. I do suggest that there be only one (yield) type system call, and if special behavior is desired, then give an argument describing the special behavior. I suggest that the yield that is kept should be the one where there is a current maintainer for it :-). -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 19:15:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14113 for freebsd-current-outgoing; Thu, 4 Feb 1999 19:15:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA14107 for ; Thu, 4 Feb 1999 19:15:31 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 10624 invoked from network); 5 Feb 1999 03:15:26 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 5 Feb 1999 03:15:26 -0000 Received: (from root@localhost) by y.dyson.net (8.9.1/8.9.1) id WAA00836; Thu, 4 Feb 1999 22:15:16 -0500 (EST) Message-Id: <199902050315.WAA00836@y.dyson.net> Subject: Re: swap_page_getswapspace failed (don't do stupid things with /dev/mem) In-Reply-To: <199902021706.JAA36791@apollo.backplane.com> from Matthew Dillon at "Feb 2, 99 09:06:37 am" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Thu, 4 Feb 1999 22:15:16 -0500 (EST) Cc: robert@cyrus.watson.org, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon said: > :Matt, > : > :Does datasize limit the number of backed pages, or the amount of address > :space used by a process? I.e., can I grow myself a large chunk of address > :space using mmap to the same region of a file, and then read into that > :large chunk (presumably larger than the cache size if I want to be nasty)? > :If datasize only affects backed pages, then we can still do nasty large > :copies; if it affects address space, then nasty large copies are limited > :to the size of the writable address space (if using readv) or the size of > :the largest contiguous writable space (if using read). > : > : Robert N Watson > : > :robert@fledge.watson.org http://www.watson.org/~robert/ > :PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C > > The 'datasize' limit does not effect mmap(), only brk/sbrk. So, > in fact, I believe you can bypass the datasize limit by allocating > anonymous memory using mmap(). > > This is probably a bug. We should either limit the mmap()able space to > about the same size as the data segment limit, or keep track of the > amount of anonymous mapped memory and count that in the datasize > limit. > FYI, the information that provides the virtual space used by a map (process) is in the vm_map data structure (so you don't need to reinvent it.) It is now used by PS also. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 19:53:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA19175 for freebsd-current-outgoing; Thu, 4 Feb 1999 19:53:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from blue.bad.bris.ac.uk (blue.bad.bris.ac.uk [137.222.132.60]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA19162 for ; Thu, 4 Feb 1999 19:52:58 -0800 (PST) (envelope-from matt@blue.bad.bris.ac.uk) Received: (qmail 10493 invoked by uid 58871); 5 Feb 1999 03:52:56 -0000 Date: Fri, 5 Feb 1999 03:52:56 +0000 (GMT) From: Matt Hamilton Reply-To: matt.hamilton@etherworks.net To: freebsd-current@FreeBSD.ORG Subject: mmap() raw device Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it possible somehow to mmap() a raw device such as /dev/rda0s2b? I am writing a program that needs very fast access to raw data, it almost creates its own filesystem in its own right. I'd much rather be able to mmap() the raw drive rather than having to go through the filesystem. -Matt ------------------------------[ Matt Hamilton ]-------------------------------- System Administrator System Administrator Badock Hall Clintondale Aviation Bristol University, UK Clifton Park, NY, USA http://www.bad.bris.ac.uk http://www.clintondale.com matt@bad.bris.ac.uk matt@clintondale.com ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 20:18:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21698 for freebsd-current-outgoing; Thu, 4 Feb 1999 20:18:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA21691 for ; Thu, 4 Feb 1999 20:18:23 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id XAA08106 for ; Thu, 4 Feb 1999 23:18:25 -0500 (EST) Date: Thu, 4 Feb 1999 23:18:24 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@FreeBSD.ORG Subject: swapper BIG problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, here's the situation: I've got an old program from when I was first learning C lying around, and I converted it to be a very rudimentary memory tester. #include #include #include #define SIZE 1024*1024 void main(void) { int count, yep = 0; void *stfu[SIZE]; void *mem; for (count = 0; count < SIZE; count++) { if ((mem = stfu[count] = malloc(1024))) { int where; printf("%p (%i) malloc'd\n", stfu[count], count); for (where = 0; where < (1024 / sizeof(unsigned)); where++) ((unsigned *)mem)[where] = 0xdeadbeef; yep++; } else break; } for (count = 0; count < yep; count++) { int where; mem = stfu[count]; for (where = 0; where < (1024 / sizeof(unsigned)); where++) if (((unsigned *)mem)[where] != 0xdeadbeef) { fprintf(stderr, "memory check failed at %i of %i\n", count, yep); exit(2); } free(stfu[count]); printf("%i free'd\n", count); } if (yep != SIZE) { printf("mallocs failed at %i\n", yep); exit (1); } else exit (0); } It succeeds as per allocating the memory until the swap is full. But, when it starts the reading/freeing, the swapins cause hundreds of swap_pager_getswapspace: failed This will put the system in a deadlock if, for instance, this program is run in an xterm and an X server is running locally, and it's too swapped out to be used, but the memory program displays things to the term (catch-22). What I see this as is (but I'm just guessing, I'm not a real kernel hacker yet): The mallocations fail where the swap runs out. Fine, whatever. The printf's in the free routines call malloc() after free()ing the kilobyte, but malloc does not have the memory for it (or does but complains) and so complains a LOT. The printfs work so it _SEEMS_ to be that the only thing bringing the system to a halt is the printfs is the kernel itself, most likely the printf's. Does this seem correct? If it's actually the kernel printf that's hanging the system, what's the solution? What if it's not? Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 20:46:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA24509 for freebsd-current-outgoing; Thu, 4 Feb 1999 20:46:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA24500 for ; Thu, 4 Feb 1999 20:46:21 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id XAA09667 for ; Thu, 4 Feb 1999 23:46:27 -0500 (EST) Date: Thu, 4 Feb 1999 23:46:27 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@FreeBSD.ORG Subject: Re: swapper BIG problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If I do a little --- swap_pager.c.orig Thu Feb 4 23:30:43 1999 +++ swap_pager.c Thu Feb 4 23:31:22 1999 @@ -203,8 +203,10 @@ swp_sizecheck() { if (vm_swap_size < nswap_lowat) { +/* if (swap_pager_full == 0) printf("swap_pager: out of swap space\n"); +*/ swap_pager_full = 1; } else if (vm_swap_size > nswap_hiwat) { swap_pager_full = 0; @@ -442,9 +444,7 @@ { daddr_t blk; - if ((blk = blist_alloc(swapblist, npages)) == SWAPBLK_NONE) { - printf("swap_pager_getswapspace: failed\n"); - } else { + if ((blk = blist_alloc(swapblist, npages)) != SWAPBLK_NONE) { vm_swap_size -= npages; swp_sizecheck(); } My system survives through the run quite well. It does in fact seem I was correct in my educated guess, but if anyone knows differently, (Matt, John Dyson) please let me know! Right now it seems the printf()s can cause the deadlock. Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 21:57:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA00408 for freebsd-current-outgoing; Thu, 4 Feb 1999 21:57:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nhj.nlc.net.au (nhj.nlc.net.au [203.24.133.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA00403 for ; Thu, 4 Feb 1999 21:56:59 -0800 (PST) (envelope-from john.saunders@nlc.net.au) Received: (qmail 18209 invoked by uid 1000); 5 Feb 1999 16:56:55 +1100 Date: 5 Feb 1999 16:56:55 +1100 Message-ID: <19990205055655.18199.qmail@nhj.nlc.net.au> From: "John Saunders" To: Brian Feldman Cc: freebsd-current@FreeBSD.ORG Subject: Re: swapper BIG problems X-Newsgroups: nlc.lists.freebsd-current In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (Linux/2.0.37 (i686)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In nlc.lists.freebsd-current you wrote: > It succeeds as per allocating the memory until the swap is full. But, when Malloc's don't cause swap space allocation. Theoretically a process can malloc all of it's virtual address space so long as it doesn't touch the pages. > it starts the reading/freeing, the swapins cause hundreds of > swap_pager_getswapspace: failed Once you actually start touching the pages does swap space (or real memory) get allocated. However by now you have malloc'ed more data than exists in physical swap space, and the swapper can't do anything about it except throw away your dirty pages without saving them. > This will put the system in a deadlock if, for instance, this program is run > in an xterm and an X server is running locally, and it's too swapped out to > be used, but the memory program displays things to the term (catch-22). This is a problem. Possibly the print commands should be rate limited. If they go to the console how do they end up in an xterm? Possibly your syslog.conf, or you run xconsole. Cheers. -- +------------------------------------------------------------+ . | John Saunders - mailto:john@nlc.net.au (EMail) | ,--_|\ | - http://www.nlc.net.au/ (WWW) | / Oz \ | - 02-9489-4932 or 041-822-3814 (Phone) | \_,--\_/ | NHJ NORTHLINK COMMUNICATIONS - Supplying a professional, | v | and above all friendly, internet connection service. | +------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 4 23:33:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09489 for freebsd-current-outgoing; Thu, 4 Feb 1999 23:33:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA09481 for ; Thu, 4 Feb 1999 23:33:42 -0800 (PST) (envelope-from Michael.Schuster@Germany.Sun.COM) Received: from Germany.Sun.COM ([129.157.168.5]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id XAA16914 for ; Thu, 4 Feb 1999 23:33:41 -0800 Received: from emuc05-home by Germany.Sun.COM (SMI-8.6/SMI-SVR4-sd.fkk205) id IAA01282; Fri, 5 Feb 1999 08:33:38 +0100 Received: from Germany.Sun.com by emuc05-home (SMI-8.6/SMI-SVR4-se.fkk202) id IAA07729; Fri, 5 Feb 1999 08:33:39 +0100 Message-ID: <36BA9EC2.5AE608DF@Germany.Sun.com> Date: Fri, 05 Feb 1999 08:33:22 +0100 From: michael schuster Organization: Sun Microsystems X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: locale errors Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id XAA09485 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My locale is set do de_DE.ISO_8859-1, not de_DE.ASCII > If I type 2 characters ss, I mean 2 characters ss. If I type ß I > mean the single character ß. > This sorting behaviour is just wrong. Not every apperence of "ss" > even in pure ASCII does mean "ß". I suggest you set LC_COLLATE to C, then it sorts in the good old fashioned way its meant to be. (like this on Solaris 7: Assel aSS asen ass asse assel assen aß aßen ) and so: Grüße Michael -- Michael.Schuster@germany.sun.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 01:06:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19225 for freebsd-current-outgoing; Fri, 5 Feb 1999 01:06:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19216 for ; Fri, 5 Feb 1999 01:06:21 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id BAA25424; Fri, 5 Feb 1999 01:06:17 -0800 (PST) (envelope-from obrien) Date: Fri, 5 Feb 1999 01:06:17 -0800 From: "David O'Brien" To: Chan Yiu Wah Cc: freebsd-current@FreeBSD.ORG Subject: Re: which star office 5.0 works with -current Message-ID: <19990205010617.A25357@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <199902050243.KAA05621@b1.hkstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199902050243.KAA05621@b1.hkstar.com>; from Chan Yiu Wah on Fri, Feb 05, 1999 at 10:43:46AM +0800 X-Operating-System: FreeBSD 3.0-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I had checked ftp.stardiv.com and found that there are several star office 5.0 > under the directory /pub/so5. I would like to know which one works with > -current. The different "versions" are really different languages. "01" is English. Others are German, French, and ______. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 01:58:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23431 for freebsd-current-outgoing; Fri, 5 Feb 1999 01:58:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23417 for ; Fri, 5 Feb 1999 01:58:44 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id KAA02363; Fri, 5 Feb 1999 10:57:22 +0100 (CET) To: conrads@neosoft.com cc: current@FreeBSD.ORG Subject: Re: ifq_maxlen problem... In-reply-to: Your message of "Thu, 04 Feb 1999 19:20:23 CST." Date: Fri, 05 Feb 1999 10:57:22 +0100 Message-ID: <2361.918208642@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Conrad Sabatier writes: > >On 04-Feb-99 Jaroslaw Bazydlo wrote: >> After yesterdays 'make world' I am having such warnings: >> >> FreeBSD 4.0-CURRENT #0: Thu Feb 4 17:19:09 GMT 1999 >> jarekb@ent.freebsd.org.pl:/usr/src/sys/compile/ENT >> [...] >> ep0 at 0x300-0x30f irq 10 on isa >> ep0: utp/bnc[*UTP*] address 00:60:08:65:d6:8d >> [...] >> ep0 XXX: driver didn't set ifq_maxlen >> lo0 XXX: driver didn't set ifq_maxlen >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> The system itself seems to work fine (for last 24 hrs). What do those >> messages mean??? Does anyone of you noticed similar messages??? >> >> The NIC is 3com 3c509B. > >Just cvsup'ed, made world and kernel today (Thursday, 2/4), and am seeing >the same thing at bootup (on lo0; I have no network interfaces installed). >No idea what it means or what's causing it, but it seems pretty harmless. I've already answered once: this is a note to driver developers. I would also point out that stuff like this can be easily found with grep over the kernel sources and examination of the cvs log message would explain it in more detail. I mean, you guys are not running -current without reading committ messages, right ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 02:46:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA28616 for freebsd-current-outgoing; Fri, 5 Feb 1999 02:46:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA28595 for ; Fri, 5 Feb 1999 02:46:46 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id TAA11110; Fri, 5 Feb 1999 19:46:25 +0900 (JST) Message-ID: <36BAB573.A56889B9@newsguy.com> Date: Fri, 05 Feb 1999 18:10:11 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Joao Carlos Mendes Luis CC: Mike Smith , current@FreeBSD.ORG Subject: Re: Overview of the FreeBSD boot process, 3.1 and later References: <199902042147.TAA21532@roma.coe.ufrj.br> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joao Carlos Mendes Luis wrote: > > 2) Update it for the last changes in /boot/loader by Daniel Sobral. > IIRC: @, # and - are gone. BTW: If variables were identified by > a $ sign, and the $ sign is now an "echo on execute" command, how will > variables be identified now ? Or have I misunderstood something ? So, it seems Mike do really have a point... I missed the potential for confusion when I choose $. Worse yet, I mislead people when I said that "\" could be used anywhere on the line. The "builtin" commands have very special semantics, that need to be understood. When interpreted (ie, the normal use), *everything* to the right of a builtin is taken as a parameter to the builtin. So, "\" wouldn't work on the right side of a builtin. Also, the special meaning of "$" when refering to variables only applies to builtin parameters. Actually, everything about special parsing only apply as builtin parameters. So, if $ or \ is on the right side of a builtin, it receives the special parsing behavior. On the left side, it is a normal forth word (or part of one). -- Daniel C. Sobral (8-DCS) dcs@newsguy.com Well, as a computer geek, I have to believe in the binary universe. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 04:58:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA12749 for freebsd-current-outgoing; Fri, 5 Feb 1999 04:58:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA12744 for ; Fri, 5 Feb 1999 04:58:22 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id HAA01137; Fri, 5 Feb 1999 07:58:16 -0500 (EST) Date: Fri, 5 Feb 1999 07:58:15 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: John Saunders cc: freebsd-current@FreeBSD.ORG Subject: Re: swapper BIG problems In-Reply-To: <19990205055655.18199.qmail@nhj.nlc.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 5 Feb 1999, John Saunders wrote: > In nlc.lists.freebsd-current you wrote: > > It succeeds as per allocating the memory until the swap is full. But, when > > Malloc's don't cause swap space allocation. Theoretically a process can > malloc all of it's virtual address space so long as it doesn't touch > the pages. If you looked at the "prgram" (term used loosely) it touches every bit of memory it allocates. > > > it starts the reading/freeing, the swapins cause hundreds of > > swap_pager_getswapspace: failed > Once you actually start touching the pages does swap space (or real > memory) get allocated. However by now you have malloc'ed more data > than exists in physical swap space, and the swapper can't do anything > about it except throw away your dirty pages without saving them. The pages were already touched and in swap. After each page was read in by the pager, the printf() tried to malloc but generated the error (as it seems to me). > > > This will put the system in a deadlock if, for instance, this program is run > > in an xterm and an X server is running locally, and it's too swapped out to > > be used, but the memory program displays things to the term (catch-22). > > This is a problem. Possibly the print commands should be rate limited. > If they go to the console how do they end up in an xterm? Possibly your > syslog.conf, or you run xconsole. The problem is, the commands were going to the console, not even the xterm. I found out by looking at /var/log/messages after poking reset. > > Cheers. > -- +------------------------------------------------------------+ > . | John Saunders - mailto:john@nlc.net.au (EMail) | > ,--_|\ | - http://www.nlc.net.au/ (WWW) | > / Oz \ | - 02-9489-4932 or 041-822-3814 (Phone) | > \_,--\_/ | NHJ NORTHLINK COMMUNICATIONS - Supplying a professional, | > v | and above all friendly, internet connection service. | > +------------------------------------------------------------+ > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 06:35:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA25030 for freebsd-current-outgoing; Fri, 5 Feb 1999 06:35:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.238.120.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA24619 for ; Fri, 5 Feb 1999 06:33:34 -0800 (PST) (envelope-from paulo@nlink.com.br) Received: from localhost (paulo@localhost) by mirage.nlink.com.br (8.9.1a/8.9.1) with SMTP id LAA05608; Fri, 5 Feb 1999 11:32:39 -0300 (EST) Date: Fri, 5 Feb 1999 11:32:39 -0300 (EST) From: Paulo Fragoso To: "Richard Seaman, Jr." cc: freebsd-current@FreeBSD.ORG Subject: Re: LINUX clone? sched_yield? In-Reply-To: <19990130140620.A29670@tar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Sat, 30 Jan 1999, Richard Seaman, Jr. wrote: > You need to: > > 1) Upgrade your source tree to Jan 28 or later for 3.X or Jan 26 > or later for 4.0 current, and "make world" and config and remake > and install a new kernel, > > or > > 2) Take your existing source and add -DCOMPAT_LINUX_THREADS to > CFLAGS and COPTFLAGS in /etc/make.conf and make world and > remake and install your kernel. > > Also, you need to add the posix priority extensions to your > kernel (see LINT). Why "/net" option in StarOffice 5.0 don't work? I make one install under Linux RedHat 5.0 with "setup /net" and I was sucessfull but in my FBSD 3.0-Stable (30Jan1999) it don't work. Are there any schedule to make work linux clone in SMP kernel? I'm using dual PII motherboard. Many Thanks, Paulo. ------ " ... Overall we've found FreeBSD to excel in performace, stability, technical support, and of course price. Two years after discovering FreeBSD, we have yet to find a reason why we switch to anything else" -David Filo, Yahoo! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 08:15:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA06551 for freebsd-current-outgoing; Fri, 5 Feb 1999 08:15:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cadaverene.neptho.net (neptho.net [207.88.23.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA06540 for ; Fri, 5 Feb 1999 08:15:03 -0800 (PST) (envelope-from bright@cadaverene.neptho.net) Received: from localhost (bright@localhost) by cadaverene.neptho.net (8.9.1a/8.9.1) with ESMTP id IAA10526 for ; Fri, 5 Feb 1999 08:15:02 -0800 (PST) Date: Fri, 5 Feb 1999 08:15:01 -0800 (PST) From: notso To: current@FreeBSD.ORG Subject: i don't have a /mnt and "/mnt: optimization changed from SPACE to TIME" message appeared. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG just curious... anything i could look at? i'm almost done with make-release and this message popped up: Feb 5 11:07:55 bright /kernel: /mnt: optimization changed from SPACE to TIME i know what that means, however: ~ % mount /dev/wd0s1a on / (local, soft-updates, writes: sync 3 async 15144) /dev/wd0s1f on /usr (NFS exported, local, soft-updates, writes: sync 10 async 104158) /dev/wd0s1e on /var (local, soft-updates, writes: sync 121 async 22721) /dev/wd0s1g on /usr/home (local, soft-updates, writes: sync 830 async 18655) procfs on /proc (local) /dev/da0a on /scsi (local, soft-updates, writes: sync 2 async 574) /dev/wd1s1e on /spare (NFS exported, local, soft-updates, writes: sync 3700 async 319664) .(11:08:36)(perlsta@bright.reserved) ~ % ? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 08:42:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09814 for freebsd-current-outgoing; Fri, 5 Feb 1999 08:42:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09809 for ; Fri, 5 Feb 1999 08:42:54 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (pm3a-6.cybcon.com [205.147.75.135]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id IAA15313 for ; Fri, 5 Feb 1999 08:42:52 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 05 Feb 1999 08:42:21 -0800 (PST) Reply-To: wwoods@cybcon.com From: William Woods To: FreeBSD Current Subject: StarOffice 5.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it correct to assume that StarOffice 5.0 works with current now? ---------------------------------- E-Mail: William Woods Date: 05-Feb-99 / Time: 08:40:59 FreeBSD 4.0 -Current ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 09:07:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12121 for freebsd-current-outgoing; Fri, 5 Feb 1999 09:07:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12115 for ; Fri, 5 Feb 1999 09:07:57 -0800 (PST) (envelope-from rock@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.2/1999010400) with ESMTP id SAA29152; Fri, 5 Feb 1999 18:07:39 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.2/1999010400) with ESMTP id SAA14814; Fri, 5 Feb 1999 18:07:38 +0100 (CET) Received: (from rock@localhost) by wurzelausix.cs.uni-sb.de (8.9.1/wjp/19980821) id SAA18017; Fri, 5 Feb 1999 18:07:38 +0100 (CET) Date: Fri, 5 Feb 1999 18:07:38 +0100 (CET) From: "D. Rock" Message-Id: <199902051707.SAA18017@wurzelausix.cs.uni-sb.de> To: Michael.Schuster@Germany.Sun.COM, current@FreeBSD.ORG Subject: Re: locale errors Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > My locale is set do de_DE.ISO_8859-1, not de_DE.ASCII > > If I type 2 characters ss, I mean 2 characters ss. If I type ß I > > mean the single character ß. > > This sorting behaviour is just wrong. Not every apperence of "ss" > > even in pure ASCII does mean "ß". > > I suggest you set LC_COLLATE to C, then it sorts in the good old > fashioned way its meant to be. > (like this on Solaris 7: > Assel > aSS > asen > ass > asse > assel > assen > aß > aßen > ) The locales were introduced to be used. I want words with umlauts to be sorted the right way, not somewhere at the end of the section/file. Solaris isn't the problem. FreeBSD treats two character strings special, which is wrong IMHO. I want FreeBSD to sort the same way as Solaris: No special interpretation of "ss", which would be right on some cases, wrong on other (wrong on all cases if we use phone book sorting) The only LC_ variable which is not set to de (de_DE.ISO_8859-1 on FreeBSD) is LC_NUMERIC. I don't want to convert all awk scripts... Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 09:22:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13882 for freebsd-current-outgoing; Fri, 5 Feb 1999 09:22:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13877 for ; Fri, 5 Feb 1999 09:22:07 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id JAA01426; Fri, 5 Feb 1999 09:22:06 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id JAA22531; Fri, 5 Feb 1999 09:22:05 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 5 Feb 1999 09:22:05 -0800 (PST) Message-Id: <199902051722.JAA22531@vashon.polstra.com> To: bright@neptho.net Subject: Re: i don't have a /mnt and "/mnt: optimization changed from SPACE to TIME" message appeared. Newsgroups: polstra.freebsd.current In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , notso wrote: > > just curious... > > anything i could look at? > > i'm almost done with make-release and this message popped up: > > Feb 5 11:07:55 bright /kernel: /mnt: optimization changed from SPACE to > TIME > > i know what that means, however: > > ~ % mount > /dev/wd0s1a on / (local, soft-updates, writes: sync 3 async 15144) > /dev/wd0s1f on /usr (NFS exported, local, soft-updates, writes: sync 10 > async 104158) > /dev/wd0s1e on /var (local, soft-updates, writes: sync 121 async 22721) > /dev/wd0s1g on /usr/home (local, soft-updates, writes: sync 830 async > 18655) > procfs on /proc (local) > /dev/da0a on /scsi (local, soft-updates, writes: sync 2 async 574) > /dev/wd1s1e on /spare (NFS exported, local, soft-updates, writes: sync > 3700 async 319664) > .(11:08:36)(perlsta@bright.reserved) > ~ % The make release process operates in a chroot environment. At certain points it makes a directory "/mnt" (in the chroot area) and mounts filesystems there temporarily. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 09:25:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16107 for freebsd-current-outgoing; Fri, 5 Feb 1999 09:25:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nhj.nlc.net.au (nhj.nlc.net.au [203.24.133.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA16094 for ; Fri, 5 Feb 1999 09:25:21 -0800 (PST) (envelope-from john.saunders@nlc.net.au) Received: (qmail 15777 invoked by uid 1000); 6 Feb 1999 04:25:14 +1100 Date: 6 Feb 1999 04:25:14 +1100 Message-ID: <19990205172514.15774.qmail@nhj.nlc.net.au> From: "John Saunders" To: Brian Feldman Cc: freebsd-current@FreeBSD.ORG Subject: Re: swapper BIG problems X-Newsgroups: nlc.lists.freebsd-current In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (Linux/2.0.37 (i686)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In nlc.lists.freebsd-current you wrote: > If you looked at the "prgram" (term used loosely) it touches every bit of > memory it allocates. I seemed to have overlooked the bit where you wrote deadbeef. I took a closer look. What I think is happening is that as the blocks are allocated and then touched, physical RAM is allocated. As you continue the oldest touched blocks get allocated to swap to make RAM available for touching new pages. You will reach a stage where you fill all of swap _and_ all of the free RAM pages. It's very likely that some part of your code hasn't been paged into RAM yet. But when it does need to there are no free RAM pages. When the swapper tries to make some free RAM pages by swapping out, guess what no swap available. > The pages were already touched and in swap. After each page was read in by > the pager, the printf() tried to malloc but generated the error (as it seems > to me). Maybe not tried to malloc, but simply for the shared library or some part of your code to be paged in for execution. This is a hard problem to fix reliably. However try limiting the max memory size (ulimit -m xxx). I believe this should limit the resident set size (RSS) for the process, therefore it will fail to allocate more memory before all of available RAM is allocated. Cheers. -- +------------------------------------------------------------+ . | John Saunders - mailto:john@nlc.net.au (EMail) | ,--_|\ | - http://www.nlc.net.au/ (WWW) | / Oz \ | - 02-9489-4932 or 041-822-3814 (Phone) | \_,--\_/ | NHJ NORTHLINK COMMUNICATIONS - Supplying a professional, | v | and above all friendly, internet connection service. | +------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 09:46:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18266 for freebsd-current-outgoing; Fri, 5 Feb 1999 09:46:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18258 for ; Fri, 5 Feb 1999 09:46:04 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id JAA33026; Fri, 5 Feb 1999 09:45:58 -0800 (PST) (envelope-from obrien) Date: Fri, 5 Feb 1999 09:45:58 -0800 From: "David O'Brien" To: brooks@one-eyed-alien.net Cc: freebsd-current@FreeBSD.ORG Subject: Re: make port and bsd.port.mk Message-ID: <19990205094558.B25357@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <199902032031.MAA25882@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from brooks@one-eyed-alien.net on Wed, Feb 03, 1999 at 12:49:21PM -0800 X-Operating-System: FreeBSD 3.0-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It was rather annoying to update my 2.2.8-STABLE machine a day or two > after being told that cvsuping ports on a 2.2 machine might cause > breakage (re: the no more 2.2 support announcement) to find that *not* Generally, you shouldn't be CVSup'ing in that case. Rather visit www.freebsd.org/ports and get an upgrade kit. Problem is in this case, the upgrade kit for 22-stable that includes these changes hasn't been built yet. You could gently nudge asami@freebsd.org to update it. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 12:44:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27893 for freebsd-current-outgoing; Fri, 5 Feb 1999 12:44:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27884 for ; Fri, 5 Feb 1999 12:44:02 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id MAA98966; Fri, 5 Feb 1999 12:22:44 -0800 (PST) (envelope-from dillon) Date: Fri, 5 Feb 1999 12:22:44 -0800 (PST) From: Matthew Dillon Message-Id: <199902052022.MAA98966@apollo.backplane.com> To: current@FreeBSD.ORG Subject: More on Seeing NFS saturation 'loop' when installworld'ing to NFS / and /usr Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's more. I seem to be getting stale NFS handle replies on the NFS-V3 commits and writes. I am guessing that the problem is due, somehow, to install's writing or renaming over of the original file, probably after stat'ing the original file. doing a mount -u -o acdirmin=0,acdirmax=0,acregmin=0,acregmax=0 ... on my / and /usr NFS mounts does not fix the problem. I am not ripping these files up from under the client .. the client is the only machine messing with these files. -Matt : This is very odd. This is the approximate backtrace that I get : when I throw my test machine into DDB: : : --- interrupt, ... : nfs_* routines.... : cluster_wbuild : vfs_bio_awrite : flushdirtybuffers : bdwrite : nfs_write : vn_write : write : syscall : : What is happening is that I am doing a 'make installworld' on my : test machine with / and /usr NFS V3 mounted R+W. : : The install goes well, but four times so far an 'install' command has : gotten 'stuck' in 'R'un state and the network has gone into saturation. : It seems to be repreating the same NFS I/O over the network over and : over again as far as I can tell. It is very odd. : : The network stays in saturation ( at 8 MBytes/sec ) until I kill -STOP :... : nfs_* routines.... : cluster_wbuild : vfs_bio_awrite : flushdirtybuffers : bdwrite ( I think ) : ffs_update : : It is very odd. I don't suppose very many people try to make install :... 12:11:51.065802 209.157.86.12.287646691 > 209.157.86.2.2049: 132 commit fh 0,7/2006718018 65536 bytes @ 0 12:11:51.066276 209.157.86.12.287646692 > 209.157.86.2.2049: 1472 write fh 0,7/2006718018 8192 bytes @ 0 (frag 54615:1480@0+) 12:11:51.066417 209.157.86.12 > 209.157.86.2: (frag 54615:1480@1480+) 12:11:51.066558 209.157.86.12 > 209.157.86.2: (frag 54615:1480@2960+) 12:11:51.066698 209.157.86.12 > 209.157.86.2: (frag 54615:1480@4440+) 12:11:51.066839 209.157.86.12 > 209.157.86.2: (frag 54615:1480@5920+) 12:11:51.066930 209.157.86.12 > 209.157.86.2: (frag 54615:940@7400) 12:11:51.067842 209.157.86.2.2049 > 209.157.86.12.287646691: reply ok 36 commit ERROR: Stale NFS file handle 12:11:51.067938 209.157.86.2.2049 > 209.157.86.12.287646692: reply ok 36 write ERROR: Stale NFS file handle 12:11:51.068038 209.157.86.12.287646693 > 209.157.86.2.2049: 132 commit fh 0,7/2006718018 16384 bytes @ 65536 12:11:51.068185 209.157.86.2.2049 > 209.157.86.12.287646693: reply ok 36 commit ERROR: Stale NFS file handle 12:11:51.068512 209.157.86.12.287646694 > 209.157.86.2.2049: 1472 write fh 0,7/2006718018 8192 bytes @ 0 (frag 54617:1480@0+) 12:11:51.068654 209.157.86.12 > 209.157.86.2: (frag 54617:1480@1480+) 12:11:51.068796 209.157.86.12 > 209.157.86.2: (frag 54617:1480@2960+) 12:11:51.068932 209.157.86.12 > 209.157.86.2: (frag 54617:1480@4440+) 12:11:51.069072 209.157.86.12 > 209.157.86.2: (frag 54617:1480@5920+) 12:11:51.069161 209.157.86.12 > 209.157.86.2: (frag 54617:940@7400) 12:11:51.069188 209.157.86.12.287646695 > 209.157.86.2.2049: 132 commit fh 0,7/2006718018 57344 bytes @ 0 12:11:51.069374 209.157.86.12.287646696 > 209.157.86.2.2049: 1472 write fh 0,7/2006718018 8192 bytes @ 65536 (frag 54619:1480@0+) 12:11:51.069512 209.157.86.12 > 209.157.86.2: (frag 54619:1480@1480+) 12:11:51.069652 209.157.86.12 > 209.157.86.2: (frag 54619:1480@2960+) 12:11:51.069688 209.157.86.2.2049 > 209.157.86.12.287646694: reply ok 36 write ERROR: Stale NFS file handle 12:11:51.069793 209.157.86.12 > 209.157.86.2: (frag 54619:1480@4440+) 12:11:51.069832 209.157.86.2.2049 > 209.157.86.12.287646695: reply ok 36 commit ERROR: Stale NFS file handle 12:11:51.069940 209.157.86.12 > 209.157.86.2: (frag 54619:1480@5920+) 12:11:51.070030 209.157.86.12 > 209.157.86.2: (frag 54619:940@7400) 12:11:51.070215 209.157.86.12.287646697 > 209.157.86.2.2049: 132 commit fh 0,7/2006718018 24576 bytes @ 0 12:11:51.070603 209.157.86.12.287646698 > 209.157.86.2.2049: 1472 write fh 0,7/2006718018 8192 bytes @ 0 (frag 54621:1480@0+) 12:11:51.070743 209.157.86.12 > 209.157.86.2: (frag 54621:1480@1480+) 12:11:51.070777 209.157.86.2.2049 > 209.157.86.12.287646696: reply ok 36 write ERROR: Stale NFS file handle 12:11:51.070889 209.157.86.12 > 209.157.86.2: (frag 54621:1480@2960+) 12:11:51.070922 209.157.86.2.2049 > 209.157.86.12.287646697: reply ok 36 commit ERROR: Stale NFS file handle 12:11:51.071034 209.157.86.12 > 209.157.86.2: (frag 54621:1480@4440+) 12:11:51.071176 209.157.86.12 > 209.157.86.2: (frag 54621:1480@5920+) 12:11:51.071267 209.157.86.12 > 209.157.86.2: (frag 54621:940@7400) 12:11:51.071456 209.157.86.12.287646699 > 209.157.86.2.2049: 132 commit fh 0,7/2006718018 49152 bytes @ 0 12:11:51.071729 209.157.86.12.287646700 > 209.157.86.2.2049: 1472 write fh 0,7/2006718018 8192 bytes @ 0 (frag 54623:1480@0+) 12:11:51.071871 209.157.86.12 > 209.157.86.2: (frag 54623:1480@1480+) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 12:44:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27903 for freebsd-current-outgoing; Fri, 5 Feb 1999 12:44:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27888 for ; Fri, 5 Feb 1999 12:44:03 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id LAA98698; Fri, 5 Feb 1999 11:47:05 -0800 (PST) (envelope-from dillon) Date: Fri, 5 Feb 1999 11:47:05 -0800 (PST) From: Matthew Dillon Message-Id: <199902051947.LAA98698@apollo.backplane.com> To: current@FreeBSD.ORG Subject: Seeing NFS saturation 'loop' when installworld'ing to NFS / and /usr Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is very odd. This is the approximate backtrace that I get when I throw my test machine into DDB: --- interrupt, ... nfs_* routines.... cluster_wbuild vfs_bio_awrite flushdirtybuffers bdwrite nfs_write vn_write write syscall What is happening is that I am doing a 'make installworld' on my test machine with / and /usr NFS V3 mounted R+W. The install goes well, but four times so far an 'install' command has gotten 'stuck' in 'R'un state and the network has gone into saturation. It seems to be repreating the same NFS I/O over the network over and over again as far as I can tell. It is very odd. The network stays in saturation ( at 8 MBytes/sec ) until I kill -STOP the install. It usually takes about a minute for the kill -STOP to take effect ( which is also very odd ). If I then kill -CONT the install program, the install resumes normally, finishes its write(), and continues on normally. The system is not locked up when this situation occurs. As far as I can tell, it is some sort of weird interaction with the flushdirtybuffers() routine and cluster_wbuild(), but I haven't a clue as to what is causing the problem. Sometimes when I break into DDB and do a backtrace, flushdirtybuffers() is being called from a non-NFS element such as ffs_update(), so the sequence looks like: nfs_* routines.... cluster_wbuild vfs_bio_awrite flushdirtybuffers bdwrite ( I think ) ffs_update It is very odd. I don't suppose very many people try to make install over NFS ( it works, you just have to chflags -R noschg the destination on the NFS server before you run make install on the NFS client ). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 12:48:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28445 for freebsd-current-outgoing; Fri, 5 Feb 1999 12:48:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28421 for ; Fri, 5 Feb 1999 12:48:08 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (pm3a-13.cybcon.com [205.147.75.142]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id LAA26298 for ; Fri, 5 Feb 1999 11:20:51 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 05 Feb 1999 11:20:19 -0800 (PST) Reply-To: wwoods@cybcon.com From: William Woods To: FreeBSD Current Subject: STAROFFICE 5.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I ubderstand that StarOffice 5.0 now works with FreeBSD 4.0-current. Where would I find the instructions for implementing this? ---------------------------------- E-Mail: William Woods Date: 05-Feb-99 / Time: 11:19:15 FreeBSD 4.0 -Current ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 12:48:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28451 for freebsd-current-outgoing; Fri, 5 Feb 1999 12:48:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28416; Fri, 5 Feb 1999 12:48:05 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (pm3a-13.cybcon.com [205.147.75.142]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id LAA27932; Fri, 5 Feb 1999 11:48:58 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 05 Feb 1999 11:48:25 -0800 (PST) Reply-To: wwoods@cybcon.com From: William Woods To: FreeBSD Questions To: FreeBSD Questions , FreeBSD Current , FreeBSD Stable Subject: test............ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG test......... ---------------------------------- E-Mail: William Woods Date: 05-Feb-99 / Time: 11:48:00 FreeBSD 4.0 -Current ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 12:59:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00380 for freebsd-current-outgoing; Fri, 5 Feb 1999 12:59:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from asteroid.svib.ru (asteroid.svib.ru [195.151.166.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00375; Fri, 5 Feb 1999 12:59:05 -0800 (PST) (envelope-from tarkhil@asteroid.svib.ru) Received: from shuttle.svib.ru (shuttle.svib.ru [195.151.166.144]) by asteroid.svib.ru (8.9.1a/8.9.1) with ESMTP id VAA23167; Fri, 5 Feb 1999 21:26:03 +0300 (MSK) Received: from shuttle.svib.ru (minas-tirith.pol.ru [127.0.0.1]) by shuttle.svib.ru (8.8.8/8.8.8) with ESMTP id VAA06615; Fri, 5 Feb 1999 21:27:13 +0300 (MSK) (envelope-from tarkhil@shuttle.svib.ru) Message-Id: <199902051827.VAA06615@shuttle.svib.ru> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG cc: questions@FreeBSD.ORG Reply-To: tarkhil@asteroid.svib.ru Subject: Cyrillic is broken in XFree86 3.3.3.1? X-URL: http://freebsd.svib.ru Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Date: Fri, 05 Feb 1999 21:27:12 +0300 From: Alex Povolotsky Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I've recently fetched and built XFree86 3.3.3.1, and some programs (most notably xterm and xemacs 20.4, built from ports also) fails to input Russian letters, using either locale or .xmodmap method. What should I set up? I've tried config file from my (_working_) XFree 3.3.3, but it didn't help :-( Alex. -- Alexander B. Povolotsky [ICQ 18277558] [2:5020/145] [http://freebsd.svib.ru] [tarkhil@asteroid.svib.ru] [Urgent messages: 234-9696 ÁÂ.#35442 or tarkhil@pager.express.ru] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 13:03:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01152 for freebsd-current-outgoing; Fri, 5 Feb 1999 13:03:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA01134 for ; Fri, 5 Feb 1999 13:03:36 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from boole.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 5 Feb 99 21:03:35 +0000 (GMT) To: freebsd-current@FreeBSD.ORG Subject: Lots of "panic: vrele: negative ref cnt" Date: Fri, 05 Feb 1999 21:03:34 +0000 From: David Malone Message-ID: <9902052103.aa20667@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We're getting lots of negative reference counts for 3.0-STABLE. We've been getting them since long before Christmas. We have 3 SMP machines, all heavy NFS clients, which are dieing about 1 per day with this panic. Several of these hangs have been provoked by me logging out - you can see the ^D in the xterm - but everything dies before the window goes away. In the trace below the it is closing my tty I think. We have also seen this happen with a write process trying to write to someones tty. Does anyone have any suggestions on how we can procede from here. We also have kernel dumps from this and several other crashes. David. #0 boot (howto=256) at ../../kern/kern_shutdown.c:285 #1 0xf014aef1 in panic (fmt=0xf0234f30 "vrele: negative ref cnt") at ../../kern/kern_shutdown.c:446 #2 0xf016f616 in vrele (vp=0xfbe1b480) at ../../kern/vfs_subr.c:1338 #3 0xf0143cad in fdfree (p=0xfb7d5b80) at ../../kern/kern_descrip.c:980 #4 0xf014510b in exit1 (p=0xfb7d5b80, rv=0) at ../../kern/kern_exit.c:199 #5 0xf0144f74 in exit1 (p=0xfb7d5b80, rv=-74600556) at ../../kern/kern_exit.c:104 #6 0xf0211347 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 1, tf_esi = 0, tf_ebp = -272640964, tf_isp = -74600476, tf_ebx = 135084552, tf_edx = 48, tf_ecx = 134813076, tf_eax = 1, tf_trapno = 12, tf_err = 2, tf_eip = 671963896, tf_cs = 31, tf_eflags = 582, tf_esp = -272640980, tf_ss = 39}) at ../../i386/i386/trap.c:1100 #7 0xf0200d6c in Xint0x80_syscall () cannot read proc at 0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 13:23:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04466 for freebsd-current-outgoing; Fri, 5 Feb 1999 13:23:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from liquid.tpb.net (drum-n-bass.party-animals.com [194.134.94.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04458 for ; Fri, 5 Feb 1999 13:23:32 -0800 (PST) (envelope-from niels@bakker.net) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.1a/8.8.8/Debian/GNU) with SMTP id WAA18561; Fri, 5 Feb 1999 22:23:09 +0100 Date: Fri, 5 Feb 1999 22:23:08 +0100 (CET) From: N To: Matthew Dillon cc: current@FreeBSD.ORG Subject: Re: Seeing NFS saturation 'loop' when installworld'ing to NFS / and /usr In-Reply-To: <199902051947.LAA98698@apollo.backplane.com> Message-ID: <990205221457.18464A-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth Matt Dillon: [make world over nfs breakage] > It is very odd. I don't suppose very many people try to make install > over NFS ( it works, you just have to chflags -R noschg the destination > on the NFS server before you run make install on the NFS client ). Actually, I did, this broke somewhere at the end of January in 3.0-STABLE. Unfortunately I first built a kernel, rebooted with that, and tried to build the world, but /usr/bin/ps was the wrong version so I couldn't easily see where processes were hanging. (Can you say Catch-22 - downgrade kernel so ps works but the bug didn't expose itself.) A kernel from Jan 27 works, but one dated Feb 2 doesn't. Symptoms include a "hanging" in a random command, be it cc or install. ^Z / fg doesn't work. /usr/src and /usr/obj both mounted via NFS. I resolved the issue by keeping /usr/obj local (with -DNOGAMES -DNOINFO this remained just under 200 MB which was basically what I have available). Since it's quite irritating to find a hanging build process in the morning (a '486 is a terrible thing to waste, isn't it? :) I didn't peruse it any further. If anyone can point me at documentation on how to configure the diuerse boot loaders that stuff gets sent to a serial port during booting, a kernel debugger is available (either via console or serial port) but reboots after panics still happen without user intervention I'd be happy to try to reproduce this. On a totally unrelated note, su(1) never works if you're not in group wheel, Kerberos or no Kerberos, as far as I can tell. -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 14:56:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15901 for freebsd-current-outgoing; Fri, 5 Feb 1999 14:56:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15896 for ; Fri, 5 Feb 1999 14:56:45 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.2) with ESMTP id OAA00510 for ; Fri, 5 Feb 1999 14:56:45 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: current@FreeBSD.ORG Subject: Heads up on new sysinstall changes. Date: Fri, 05 Feb 1999 14:56:45 -0800 Message-ID: <506.918255405@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 1. Userconfig parameter saving should work again, albeit somewhat differently than before. Rather than having a program (dset) pound bits directly into your kernel, a /boot/kernel.conf file is written out by sysinstall, along with a set of /boot/loader.rc file entries to make use of it. If you've already got a loader.rc file, sysinstall won't touch it but will instead instruct you on what to add. This is not to say that you can boot -c any time and have your parameters saved entirely like in the old days. This is (for the time being) solely a feature of sysinstall, not the rc scripts, and good only for initial install/upgrade time. 2. Sysinstall no longer writes customizations into /etc/rc.conf, reserving that file as a "template" of config data. Sysinstall's customizations are written into /etc/rc.conf.site, the /etc/rc.conf.local file remaining free for site-specific use as always. This makes the task of keeping /etc up to date that much easier since you can just copy over a new rc.conf at any time if your /etc starts getting stale. The Feb 6th snapshot (for both 4.0 and 3.0S) should contain these changes. Please test them out as they do represent some fairly sweeping internal changes to sysinstall. Thanks! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 15:25:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18744 for freebsd-current-outgoing; Fri, 5 Feb 1999 15:25:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18739 for ; Fri, 5 Feb 1999 15:25:17 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id PAA00308; Fri, 5 Feb 1999 15:25:12 -0800 (PST) (envelope-from dillon) Date: Fri, 5 Feb 1999 15:25:12 -0800 (PST) From: Matthew Dillon Message-Id: <199902052325.PAA00308@apollo.backplane.com> To: N Cc: current@FreeBSD.ORG Subject: Re: Seeing NFS saturation 'loop' when installworld'ing to NFS / and /usr References: <990205221457.18464A-100000@liquid.tpb.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> on the NFS server before you run make install on the NFS client ). : :Actually, I did, this broke somewhere at the end of January in 3.0-STABLE. :Unfortunately I first built a kernel, rebooted with that, and tried to :build the world, but /usr/bin/ps was the wrong version so I couldn't :easily see where processes were hanging. (Can you say Catch-22 - downgrade :kernel so ps works but the bug didn't expose itself.) : :A kernel from Jan 27 works, but one dated Feb 2 doesn't. Symptoms include :a "hanging" in a random command, be it cc or install. ^Z / fg doesn't Is the Jan 27 kernel a -3.0 kernel also? How old was the CVS tree you built from the Jan 27 kernel from ? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 16:19:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27459 for freebsd-current-outgoing; Fri, 5 Feb 1999 16:19:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27454 for ; Fri, 5 Feb 1999 16:19:49 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id QAA00659; Fri, 5 Feb 1999 16:19:48 -0800 (PST) (envelope-from dillon) Date: Fri, 5 Feb 1999 16:19:48 -0800 (PST) From: Matthew Dillon Message-Id: <199902060019.QAA00659@apollo.backplane.com> To: current@FreeBSD.ORG Subject: Re: More on Seeing NFS saturation 'loop' when installworld'ing to NFS / and /usr Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think I've found the general area where the problem is occuring. It appears to some sort of weird write()/remove() interaction. In the make install, the problem appears to only occurs when install -s ( install and strip binary ) is used. This causes an NFS file to be written, copied, and then removed. I think what is going on is that the dirty bp's associated with the file being removed are not being cleared out prior to the NFS setattr call that removes the actual file. Then a flushdirtyblks() call comes along and tries to vfs_bio_awrite()'s the B_INVALID|B_DELWRI buffers. I still can't figure out where exactly in the code the problem is occuring, though. It's definitely related to a just-written file via NFS getting remove()'d, and then a later flushdirtyblks() call doing something that causes the blocks to be written out to the server ( and thus returning a 'Stale file' error ). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 17:01:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03223 for freebsd-current-outgoing; Fri, 5 Feb 1999 17:01:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA03217 for ; Fri, 5 Feb 1999 17:01:45 -0800 (PST) (envelope-from rock@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.2/1999010400) with ESMTP id CAA01262; Sat, 6 Feb 1999 02:01:38 +0100 (CET) Received: from wurzelausix (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.2/1999010400) with ESMTP id CAA18835; Sat, 6 Feb 1999 02:01:37 +0100 (CET) Received: from vodix.aremorika (vodix [134.96.247.43]) by wurzelausix (8.9.1/wjp/19980821) with ESMTP id CAA20903; Sat, 6 Feb 1999 02:01:37 +0100 (CET) From: "D. Rock" Received: by vodix.aremorika; Sat, 6 Feb 1999 02:01:36 +0100 (MET) Date: Sat, 6 Feb 1999 02:01:36 +0100 (MET) Message-Id: <199902060101.CAA04062@vodix.aremorika> To: current@FreeBSD.ORG, dillon@apollo.backplane.com Subject: Re: Seeing NFS saturation 'loop' when installworld'ing to NFS / and /usr Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt wrote: > This is very odd. This is the approximate backtrace that I get > when I throw my test machine into DDB: [..] > What is happening is that I am doing a 'make installworld' on my > test machine with / and /usr NFS V3 mounted R+W. I also have come to the conclusion that NFSv3 is badly broken. I switched all my R/W mounts back to NFSv2 and I am happy again. I can do a full "make relase" with an NFS mounted chroot directory with no problems, while I have seen many problems with v3 mounts. One thing to lock up the system (probably only the filesystem code, I can still switch virtual screens with Alt+Fx, but getty cannot start /usr/bin/login) if I mount NFSv3 with the -l flag. I tried to track down some of the problems doing a network snoop and noticed something interesting: NFSv3 seems to produce more than twice the packets during file write than NFSv2 Is this true. There are many more getattr() calls with NFSv3 than with NFSv2. Since my NFS server exports one filesystem exclusively to one FreeBSD machine (which is a little short on disk space), I also tried some tricks for speedup. I just mounted one big file, vnconfig'd, newfs'd it and mounted it via UFS. But unfortunately the machine panic'd really fast during filesystem activity. My tests on this are 3-4 months old though, I will give it another try. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 17:58:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09711 for freebsd-current-outgoing; Fri, 5 Feb 1999 17:58:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09704 for ; Fri, 5 Feb 1999 17:58:40 -0800 (PST) (envelope-from mike@sentex.net) Received: from ospf-wat.sentex.net (ospf-wat.sentex.net [209.167.248.81]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id UAA26550 for ; Fri, 5 Feb 1999 20:58:36 -0500 (EST) From: mike@sentex.net (Mike Tancsa) To: current@FreeBSD.ORG Subject: Re: SKIP on 3.0 ? lkm vs kld = SOL ? Date: Sat, 06 Feb 1999 02:05:47 GMT Message-ID: <36bba2d1.455362426@mail.sentex.net> References: In-Reply-To: X-Mailer: Forte Agent .99e/32.227 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 5 Feb 1999 17:19:44 -0500, in sentex.lists.freebsd.misc you wrote: > >I was trying to install SKIP on a 3.0 STABLE box and I am having problems >getting it to boot up. The port compliles cleanly, but when I reboot, I >get the following > >ruby# /usr/local/etc/rc.d/skip.sh > skipld: /kernel: malformed input file (not rel or archive) >modload: /usr/bin/ld: return code 1 > >skip: failed to load driver >skip: perhaps too many drivers are loaded? > > >I have LKM support in my ELF kernel, but it does not seem to make a >difference. OK, looking back at some of the threads, it seems I am hosed since the ELF cannot load klds ? Is that correct ? Are there any other options for VPN on the 3.0 branch ? SKIP wasnt/isnt the greatest, but I had decent luck with it on the 2.2 branch of things... ---Mike Mike Tancsa (mdtancsa@sentex.net) Sentex Communications Corp, Waterloo, Ontario, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 18:03:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10299 for freebsd-current-outgoing; Fri, 5 Feb 1999 18:03:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa17-15.ix.netcom.com [207.93.156.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10291 for ; Fri, 5 Feb 1999 18:03:37 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.2/8.8.8) id SAA00439; Fri, 5 Feb 1999 18:03:35 -0800 (PST) (envelope-from tomdean) Date: Fri, 5 Feb 1999 18:03:35 -0800 (PST) Message-Id: <199902060203.SAA00439@ix.netcom.com> From: Thomas Dean To: current@FreeBSD.ORG Subject: Reboot and Message Logging Problems Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry for the long lines, I want to show garbled/split messages. I am running an SMP kernel, -current as of last night. I can look through logs back to early April, 1998, if necessary. If I use reboot or shutdown -r, the top part of dmesg does not appear in /var/log/messages. The amount of dmesg that gets into the log file seems to vary. If I use shutdown -h, all of dmesg gets into the log file. Some messages get garbled. All su's do not get logged. All of these, except the su problem, are minor. I will supply the entire message file, if anyone wants it. Refer to the list attached: su not logged Feb 5 17:15:07 I used reboot Feb 5 17:06:08 I used shutdown -h Feb 5 17:08:41 I used shutdown -r Feb 5 17:15:07 Garbled messages: Feb 5 17:07:12 only the last part of the chip 0 message Feb 5 17:10:01 the chip 1 message split Start point in dmesg varies Feb 5 17:07:12 started at memory controller Feb 5 17:10:01 started at the top Feb 5 17:16:10 started with kernel address tomdean ==== from /var/log/messages ====================================== Feb 5 17:00:00 celebris newsyslog[293]: logfile turned over Feb 5 17:01:38 celebris su: tomdean to root on /dev/ttyp0 Feb 5 17:06:08 celebris reboot: rebooted by tomdean Feb 5 17:06:08 celebris syslogd: exiting on signal 15 Feb 5 17:07:12 celebris /kernel: e memory controller> rev 0x11 on pci0.0.0 Feb 5 17:07:12 celebris /kernel: ncr0: rev 0x02 int a irq 11 on pci0.1.0 Feb 5 17:07:12 celebris /kernel: chip1: rev 0x88 on pci0.2.0 Feb 5 17:07:12 celebris /kernel: vga0: rev 0x01 int a irq 9 on pci0.6.0 Feb 5 17:07:12 celebris /kernel: de0: rev 0x11 int a irq 10 on pci0.8.0 Feb 5 17:07:12 celebris /kernel: de0: DEC DE450-CA 21041 [10Mb/s] pass 1.1 Feb 5 17:07:12 celebris /kernel: de0: address 00:00:f8:02:76:db Feb 5 17:07:12 celebris /kernel: Probing for devices on the ISA bus: Feb 5 17:07:12 celebris /kernel: sc0 on isa Feb 5 17:07:12 celebris /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Feb 5 17:07:12 celebris /kernel: atkbdc0 at 0x60-0x6f on motherboard Feb 5 17:07:12 celebris /kernel: atkbd0 irq 1 on isa Feb 5 17:07:12 celebris /kernel: psm0 irq 12 on isa Feb 5 17:07:12 celebris /kernel: psm0: model Generic PS/2 mouse, device ID 0 Feb 5 17:07:12 celebris /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Feb 5 17:07:12 celebris /kernel: sio0: type 16550A Feb 5 17:08:27 celebris su: tomdean to root on /dev/ttyp0 Feb 5 17:08:41 celebris shutdown: halt by tomdean: Feb 5 17:08:43 celebris syslogd: exiting on signal 15 Feb 5 17:10:01 celebris /kernel: Copyright (c) 1992-1999 FreeBSD Inc. Feb 5 17:10:01 celebris /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Feb 5 17:10:01 celebris /kernel: The Regents of the University of California. All rights reserved. Feb 5 17:10:01 celebris /kernel: FreeBSD 4.0-CURRENT #6: Fri Feb 5 17:05:47 PST 1999 Feb 5 17:10:01 celebris /kernel: tomdean@celebris:/usr/src/sys/compile/CELEBRIS-SMP Feb 5 17:10:01 celebris /kernel: Timecounter-tdd "i8254" frequency 1193182 Hz cost 2540 ns Feb 5 17:10:01 celebris /kernel: CPU: Pentium/P54C (586-class CPU) Feb 5 17:10:01 celebris /kernel: Origin = "GenuineIntel" Id = 0x525 Stepping=5 Feb 5 17:10:01 celebris /kernel: Features=0x3bf Feb 5 17:10:01 celebris /kernel: real memory = 100663296 (98304K bytes) Feb 5 17:10:01 celebris /kernel: avail memory = 95076352 (92848K bytes) Feb 5 17:10:01 celebris /kernel: Programming 16 pins in IOAPIC #0 Feb 5 17:10:01 celebris /kernel: FreeBSD/SMP: Multiprocessor motherboard Feb 5 17:10:01 celebris /kernel: cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 Feb 5 17:10:01 celebris /kernel: cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 Feb 5 17:10:01 celebris /kernel: io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec00000 Feb 5 17:10:01 celebris /kernel: Preloaded elf kernel "kernel" at 0xf02ab000. Feb 5 17:10:01 celebris /kernel: Probing for devices on PCI bus 0: Feb 5 17:10:01 celebris /kernel: chip0: rev 0x11 on pci0.0.0 Feb 5 17:10:01 celebris /kernel: ncr0: rev 0x02 int a irq 11 on pci0.1.0 Feb 5 17:10:01 celebris /kernel: chip1: rev 0x88 on pci0.2.0 Feb 5 17:10:01 celebris /kernel: vga0: rev 0x01 int a irq 9 on pci0.6.0 Feb 5 17:10:01 celebris /kernel: de0: rev 0x11 int a irq 10 on pci0.8.0 Feb 5 17:10:01 celebris /kernel: de0: DEC DE450-CA 21041 [10Mb/s] pass 1.1 Feb 5 17:10:01 celebris /kernel: de0: address 00:00:f8:02:76:db Feb 5 17:10:01 celebris /kernel: Probing for devices on the ISA bus: Feb 5 17:10:01 celebris /kernel: sc0 on isa Feb 5 17:10:01 celebris /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Feb 5 17:10:01 celebris /kernel: atkbdc0 at 0x60-0x6f on motherboard Feb 5 17:10:01 celebris /kernel: atkbd0 irq 1 on isa Feb 5 17:10:01 celebris /kernel: psm0 irq 12 on isa Feb 5 17:10:01 celebris /kernel: psm0: model Generic PS/2 mouse, device ID 0 Feb 5 17:10:04 celebris lpd[157]: restarted Feb 5 17:10:14 celebris /kernel: (da1:ncr0:0:1:0): tagged openings now 8 Feb 5 17:15:07 celebris shutdown: reboot by tomdean: Feb 5 17:15:10 celebris syslogd: exiting on signal 15 Feb 5 17:16:10 celebris /kernel: "kernel" at 0xf02ab000. Feb 5 17:16:10 celebris /kernel: Probing for devices on PCI bus 0: Feb 5 17:16:10 celebris /kernel: chip0: rev 0x11 on pci0.0.0 Feb 5 17:16:10 celebris /kernel: ncr0: rev 0x02 int a irq 11 on pci0.1.0 Feb 5 17:16:10 celebris /kernel: chip1: rev 0x88 on pci0.2.0 Feb 5 17:16:10 celebris /kernel: vga0: rev 0x01 int a irq 9 on pci0.6.0 Feb 5 17:16:10 celebris /kernel: de0: rev 0x11 int a irq 10 on pci0.8.0 Feb 5 17:16:10 celebris /kernel: de0: DEC DE450-CA 21041 [10Mb/s] pass 1.1 Feb 5 17:16:10 celebris /kernel: de0: address 00:00:f8:02:76:db Feb 5 17:16:10 celebris /kernel: Probing for devices on the ISA bus: Feb 5 17:16:10 celebris /kernel: sc0 on isa Feb 5 17:16:10 celebris /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Feb 5 17:16:10 celebris /kernel: atkbdc0 at 0x60-0x6f on motherboard Feb 5 17:16:10 celebris /kernel: atkbd0 irq 1 on isa Feb 5 17:16:10 celebris /kernel: psm0 irq 12 on isa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 18:14:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10830 for freebsd-current-outgoing; Fri, 5 Feb 1999 18:14:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10825 for ; Fri, 5 Feb 1999 18:14:04 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id SAA01635; Fri, 5 Feb 1999 18:03:46 -0800 (PST) (envelope-from dillon) Date: Fri, 5 Feb 1999 18:03:46 -0800 (PST) From: Matthew Dillon Message-Id: <199902060203.SAA01635@apollo.backplane.com> To: "D. Rock" , N Cc: current@FreeBSD.ORG Subject: Re: Seeing NFS saturation 'loop' when installworld'ing to NFS / and /usr References: <199902060101.CAA04062@vodix.aremorika> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, I think I found the problem. I believe what is going on is that dirty buffers are being held across an nfs_rename() call under NFS V3. Under NFS V2, most such buffers are written synchronously. Under NFS V3, however, it appears to work differently. One of the following two sequences is causing the problem: * write A * rename A B * delete B or * write B * rename A B * delete B I can't tell which. The dirty buffers stay in the buffer cache until after the rename, and then flushdirtybuffers() comes along and tries to flush them. The buffers being flushed get an NFS 'Stale file Handle' error. Not only that, but due to the error the buffer remains dirty and gets flushed out again by flushdirtybuffers(). This occurs add-nausium until some other event comes along and clears enough buffers such that flushdirtybuffers() will exit its loop. This could also be responsible or partially responsible for the NFS-based dirty-buffers panic on shutdown. -- I would appreciate it if people experiencing either problem try this patch. It is rather important that we test this patch big-time because we will want to get it into -3.1 if it turns out to fix some of the problems. Even if this fixes some things, we still have a potential stale-file looping condition in flushdirtybufs() that must be addressed. If the stale file handle error is a fatal error under NFS, we should generate a system log message and eradicate the buffer(s) in question rather then leave them sitting around in the buffer cache. -Matt Matthew Dillon Index: nfs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_vnops.c,v retrieving revision 1.119 diff -u -r1.119 nfs_vnops.c --- nfs_vnops.c 1999/01/27 22:45:49 1.119 +++ nfs_vnops.c 1999/02/06 01:56:23 @@ -1567,6 +1567,19 @@ } /* + * We have to flush B_DELWRI data prior to renaming + * the file. If we don't, the delayed-write buffers + * can be flushed out later after the file has gone stale + * under NFSV3. NFSV2 does not have this problem because + * ( as far as I can tell ) it flushes dirty buffers more + * often. + */ + + VOP_FSYNC(fvp, fcnp->cn_cred, MNT_WAIT, fcnp->cn_proc); + if (tvp) + VOP_FSYNC(tvp, tcnp->cn_cred, MNT_WAIT, tcnp->cn_proc); + + /* * If the tvp exists and is in use, sillyrename it before doing the * rename of the new file over it. * XXX Can't sillyrename a directory. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 18:36:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12657 for freebsd-current-outgoing; Fri, 5 Feb 1999 18:36:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA12650 for ; Fri, 5 Feb 1999 18:36:06 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (pm3a-35.cybcon.com [205.147.75.164]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id SAA23037 for ; Fri, 5 Feb 1999 18:36:04 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 05 Feb 1999 18:35:30 -0800 (PST) Reply-To: wwoods@cybcon.com From: William Woods To: FreeBSD Current Subject: Problem with "top" on current ? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Running 4.0 -Current build as of a few miniutesd ago, I go to run top and I get......... top: cannot read *swapblist: kvm_read: Bad address top: cannot read blmeta_t: kvm_read: Bad address Floating point exception ---------------------------------- E-Mail: William Woods Date: 05-Feb-99 / Time: 18:34:17 FreeBSD 4.0 -Current ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 18:39:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13221 for freebsd-current-outgoing; Fri, 5 Feb 1999 18:39:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13214 for ; Fri, 5 Feb 1999 18:39:53 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA16750; Fri, 5 Feb 1999 21:39:53 -0500 (EST) Date: Fri, 5 Feb 1999 21:39:52 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: William Woods cc: FreeBSD Current Subject: Re: Problem with "top" on current ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 5 Feb 1999, William Woods wrote: > Running 4.0 -Current build as of a few miniutesd ago, I go to run top and I > get......... > > top: cannot read *swapblist: kvm_read: Bad address > top: cannot read blmeta_t: kvm_read: Bad address > Floating point exception Try "kvm_mkdb" yet? > > ---------------------------------- > E-Mail: William Woods > Date: 05-Feb-99 / Time: 18:34:17 > FreeBSD 4.0 -Current > ---------------------------------- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 20:10:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20257 for freebsd-current-outgoing; Fri, 5 Feb 1999 20:10:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20252 for ; Fri, 5 Feb 1999 20:10:39 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (usr1-12.cybcon.com [205.147.76.13]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id UAA28330 for ; Fri, 5 Feb 1999 20:10:38 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 05 Feb 1999 20:10:04 -0800 (PST) Reply-To: wwoods@cybcon.com From: William Woods To: FreeBSD Current Subject: Top not working in -Current?? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To go along with my other message about the top problem, When I try to run top in a current box, compiled a few moments ago I get: top: cannot read *swapblist: kvm_read: Bad address top: cannot read blmeta_t: kvm_read: Bad address Floating point exception And, in /var/log/messages I see: Feb 5 20:06:08 freebsd /kernel: pid 96162 (kikbd), uid 1000: exited on signal 11 Feb 5 20:09:20 freebsd /kernel: pid 97284 (top), uid 1000: exited on signal 8 Any ideas? ---------------------------------- E-Mail: William Woods Date: 05-Feb-99 / Time: 20:08:30 FreeBSD 4.0 -Current ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 20:10:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20287 for freebsd-current-outgoing; Fri, 5 Feb 1999 20:10:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20277 for ; Fri, 5 Feb 1999 20:10:43 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (usr1-12.cybcon.com [205.147.76.13]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id UAA28337; Fri, 5 Feb 1999 20:10:40 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 05 Feb 1999 20:10:06 -0800 (PST) Reply-To: wwoods@cybcon.com From: William Woods To: Brian Feldman Subject: Re: Problem with "top" on current ? Cc: FreeBSD Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ahhh...not sure what you mean here....... On 06-Feb-99 Brian Feldman wrote: > On Fri, 5 Feb 1999, William Woods wrote: > >> Running 4.0 -Current build as of a few miniutesd ago, I go to run top and I >> get......... >> >> top: cannot read *swapblist: kvm_read: Bad address >> top: cannot read blmeta_t: kvm_read: Bad address >> Floating point exception > > Try "kvm_mkdb" yet? > >> >> ---------------------------------- >> E-Mail: William Woods >> Date: 05-Feb-99 / Time: 18:34:17 >> FreeBSD 4.0 -Current >> ---------------------------------- >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-current" in the body of the message >> > > Brian Feldman _ __ ___ ___ ___ > green@unixhelp.org _ __ ___ | _ ) __| \ > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ ---------------------------------- E-Mail: William Woods Date: 05-Feb-99 / Time: 20:07:41 FreeBSD 4.0 -Current ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 20:18:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20974 for freebsd-current-outgoing; Fri, 5 Feb 1999 20:18:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20969 for ; Fri, 5 Feb 1999 20:18:30 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id UAA02533; Fri, 5 Feb 1999 20:18:23 -0800 (PST) (envelope-from dillon) Date: Fri, 5 Feb 1999 20:18:23 -0800 (PST) From: Matthew Dillon Message-Id: <199902060418.UAA02533@apollo.backplane.com> To: William Woods Cc: Brian Feldman , FreeBSD Current Subject: Re: Problem with "top" on current ? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Ahhh...not sure what you mean here....... : :On 06-Feb-99 Brian Feldman wrote: :> On Fri, 5 Feb 1999, William Woods wrote: :>> Floating point exception :... :> :> Try "kvm_mkdb" yet? :> :---------------------------------- :E-Mail: William Woods Try this: cd /usr/src/lib/libkvm make; make install; make clean cd /usr/src/usr.bin/top make; make install; make clean kvm_mkdb -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 20:23:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21321 for freebsd-current-outgoing; Fri, 5 Feb 1999 20:23:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA21314 for ; Fri, 5 Feb 1999 20:23:56 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (usr1-12.cybcon.com [205.147.76.13]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id UAA29058; Fri, 5 Feb 1999 20:23:53 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199902060418.UAA02533@apollo.backplane.com> Date: Fri, 05 Feb 1999 20:23:19 -0800 (PST) Reply-To: wwoods@cybcon.com From: William Woods To: Matthew Dillon Subject: Re: Problem with "top" on current ? Cc: FreeBSD Current , Brian Feldman Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just tried that, same error..... On 06-Feb-99 Matthew Dillon wrote: > >: >:Ahhh...not sure what you mean here....... >: >:On 06-Feb-99 Brian Feldman wrote: >:> On Fri, 5 Feb 1999, William Woods wrote: >:>> Floating point exception >:... >:> >:> Try "kvm_mkdb" yet? >:> >:---------------------------------- >:E-Mail: William Woods > > Try this: > > cd /usr/src/lib/libkvm > make; make install; make clean > cd /usr/src/usr.bin/top > make; make install; make clean > kvm_mkdb > > > -Matt > > Matthew Dillon > ---------------------------------- E-Mail: William Woods Date: 05-Feb-99 / Time: 20:22:51 FreeBSD 4.0 -Current ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 20:33:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22125 for freebsd-current-outgoing; Fri, 5 Feb 1999 20:33:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22112; Fri, 5 Feb 1999 20:32:57 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id PAA06324; Sat, 6 Feb 1999 15:32:53 +1100 Date: Sat, 6 Feb 1999 15:32:53 +1100 From: Bruce Evans Message-Id: <199902060432.PAA06324@godzilla.zeta.org.au> To: current@FreeBSD.ORG, wwoods@cybcon.com Subject: Re: Top not working in -Current?? Cc: dillon@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >When I try to run top in a current box, compiled a few moments ago I get: > >top: cannot read *swapblist: kvm_read: Bad address >top: cannot read blmeta_t: kvm_read: Bad address >Floating point exception kvm_getswapinfo() is broken when there is no swap. It falls into its own compatibility cruft and attempts to read the old swap variables which don't exist. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 20:37:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22365 for freebsd-current-outgoing; Fri, 5 Feb 1999 20:37:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22355; Fri, 5 Feb 1999 20:37:20 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (usr1-12.cybcon.com [205.147.76.13]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id UAA29890; Fri, 5 Feb 1999 20:37:06 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199902060432.PAA06324@godzilla.zeta.org.au> Date: Fri, 05 Feb 1999 20:36:32 -0800 (PST) Reply-To: wwoods@cybcon.com From: William Woods To: Bruce Evans Subject: Re: Top not working in -Current?? Cc: dillon@FreeBSD.ORG, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmmm...I have a swap, although it is mounted /tmp as mfs, here is my fstab: # Device Mountpoint FStype Options Dump Pass# /dev/wd0s1b /tmp mfs rw 0 0 #/dev/wd0s1b none swap sw 0 0 /dev/wd0s1a / ufs rw 1 1 /dev/wd0s1f /usr ufs rw 2 2 /dev/wd1s1e /usr/local ufs rw 2 2 /dev/wd0s1e /var ufs rw 2 2 proc /proc procfs rw 0 0 /dev/wcd0c /cdrom cd9660 ro,noauto 0 0 On 06-Feb-99 Bruce Evans wrote: >>When I try to run top in a current box, compiled a few moments ago I get: >> >>top: cannot read *swapblist: kvm_read: Bad address >>top: cannot read blmeta_t: kvm_read: Bad address >>Floating point exception > > kvm_getswapinfo() is broken when there is no swap. It falls into its > own compatibility cruft and attempts to read the old swap variables > which don't exist. > > Bruce ---------------------------------- E-Mail: William Woods Date: 05-Feb-99 / Time: 20:35:23 FreeBSD 4.0 -Current ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 20:39:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22624 for freebsd-current-outgoing; Fri, 5 Feb 1999 20:39:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22614; Fri, 5 Feb 1999 20:39:03 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id UAA02692; Fri, 5 Feb 1999 20:38:52 -0800 (PST) (envelope-from dillon) Date: Fri, 5 Feb 1999 20:38:52 -0800 (PST) From: Matthew Dillon Message-Id: <199902060438.UAA02692@apollo.backplane.com> To: Bruce Evans Cc: current@FreeBSD.ORG, wwoods@cybcon.com, dillon@FreeBSD.ORG Subject: Re: Top not working in -Current?? References: <199902060432.PAA06324@godzilla.zeta.org.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :>When I try to run top in a current box, compiled a few moments ago I get: :> :>top: cannot read *swapblist: kvm_read: Bad address :>top: cannot read blmeta_t: kvm_read: Bad address :>Floating point exception : :kvm_getswapinfo() is broken when there is no swap. It falls into its :own compatibility cruft and attempts to read the old swap variables :which don't exist. : :Bruce Ahhhhhhhhhhh. Easy to fix. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 20:40:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22793 for freebsd-current-outgoing; Fri, 5 Feb 1999 20:40:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22783; Fri, 5 Feb 1999 20:40:15 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (usr1-12.cybcon.com [205.147.76.13]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id UAA00211; Fri, 5 Feb 1999 20:40:12 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199902060438.UAA02692@apollo.backplane.com> Date: Fri, 05 Feb 1999 20:39:38 -0800 (PST) Reply-To: wwoods@cybcon.com From: William Woods To: Matthew Dillon Subject: Re: Top not working in -Current?? Cc: dillon@FreeBSD.ORG, current@FreeBSD.ORG, Bruce Evans Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And the fix is..... On 06-Feb-99 Matthew Dillon wrote: > >:>When I try to run top in a current box, compiled a few moments ago I get: >:> >:>top: cannot read *swapblist: kvm_read: Bad address >:>top: cannot read blmeta_t: kvm_read: Bad address >:>Floating point exception >: >:kvm_getswapinfo() is broken when there is no swap. It falls into its >:own compatibility cruft and attempts to read the old swap variables >:which don't exist. >: >:Bruce > > Ahhhhhhhhhhh. Easy to fix. > > -Matt > Matthew Dillon > ---------------------------------- E-Mail: William Woods Date: 05-Feb-99 / Time: 20:39:17 FreeBSD 4.0 -Current ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 20:50:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23226 for freebsd-current-outgoing; Fri, 5 Feb 1999 20:50:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23221 for ; Fri, 5 Feb 1999 20:50:23 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id UAA03021; Fri, 5 Feb 1999 20:50:16 -0800 (PST) (envelope-from dillon) Date: Fri, 5 Feb 1999 20:50:16 -0800 (PST) From: Matthew Dillon Message-Id: <199902060450.UAA03021@apollo.backplane.com> To: William Woods Cc: current@FreeBSD.ORG, Bruce Evans Subject: Re: Top not working in -Current?? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :And the fix is..... : :On 06-Feb-99 Matthew Dillon wrote: :> :>: :>:Bruce :> :> Ahhhhhhhhhhh. Easy to fix. :> : This this patch to /usr/src/lib/libkvm/kvm_getswapinfo.c. Then recompile libkvm and try top and pstat -s again. -Matt Matthew Dillon Index: kvm_getswapinfo.c =================================================================== RCS file: /home/ncvs/src/lib/libkvm/kvm_getswapinfo.c,v retrieving revision 1.4 diff -u -r1.4 kvm_getswapinfo.c --- kvm_getswapinfo.c 1999/01/27 11:29:15 1.4 +++ kvm_getswapinfo.c 1999/02/06 04:46:48 @@ -127,10 +127,10 @@ KGET(NL_NSWDEV, nswdev); KGET(NL_DMMAX, dmmax); - if (kvm_swap_nl[NL_SWAPLIST].n_value) + if (kvm_swap_nl[NL_SWAPLIST].n_type != N_UNDF) type = 1; - if (kvm_swap_nl[NL_SWAPBLIST].n_value) + if (kvm_swap_nl[NL_SWAPBLIST].n_type != N_UNDF) type = 2; /* @@ -406,6 +406,13 @@ struct blist blcopy = { 0 }; KGET(NL_SWAPBLIST, swapblist); + + if (swapblist == NULL) { + if (flags & SWIF_DUMP_TREE) + printf("radix tree: NULL - no swap in system\n"); + return; + } + KGET2(swapblist, &blcopy, sizeof(blcopy), "*swapblist"); if (flags & SWIF_DUMP_TREE) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 20:55:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23629 for freebsd-current-outgoing; Fri, 5 Feb 1999 20:55:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23624 for ; Fri, 5 Feb 1999 20:55:45 -0800 (PST) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id CAA02875; Sat, 6 Feb 1999 02:55:38 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199902060455.CAA02875@roma.coe.ufrj.br> Subject: Re: SKIP on 3.0 ? lkm vs kld = SOL ? In-Reply-To: <36bba2d1.455362426@mail.sentex.net> from Mike Tancsa at "Feb 6, 1999 2: 5:47 am" To: mike@sentex.net (Mike Tancsa) Date: Sat, 6 Feb 1999 02:55:38 -0200 (EDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG #define quoting(Mike Tancsa) // Are there any other options for VPN on the 3.0 branch ? SKIP wasnt/isnt // the greatest, but I had decent luck with it on the 2.2 branch of things... Have you tried the ssh+ppp combo ? IIRC, there's a small example in the file /etc/ppp/ppp.conf.sample. Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 20:57:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23761 for freebsd-current-outgoing; Fri, 5 Feb 1999 20:57:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23756 for ; Fri, 5 Feb 1999 20:57:21 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (usr1-12.cybcon.com [205.147.76.13]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id UAA01124; Fri, 5 Feb 1999 20:57:13 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199902060450.UAA03021@apollo.backplane.com> Date: Fri, 05 Feb 1999 20:56:40 -0800 (PST) Reply-To: wwoods@cybcon.com From: William Woods To: Matthew Dillon Subject: Re: Top not working in -Current?? Cc: Bruce Evans , current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ahh.....and exactly how do I use this? On 06-Feb-99 Matthew Dillon wrote: >:And the fix is..... >: >:On 06-Feb-99 Matthew Dillon wrote: >:> >:>: >:>:Bruce >:> >:> Ahhhhhhhhhhh. Easy to fix. >:> >: > > This this patch to /usr/src/lib/libkvm/kvm_getswapinfo.c. Then > recompile libkvm and try top and pstat -s again. > > -Matt > > Matthew Dillon > > > > Index: kvm_getswapinfo.c > =================================================================== > RCS file: /home/ncvs/src/lib/libkvm/kvm_getswapinfo.c,v > retrieving revision 1.4 > diff -u -r1.4 kvm_getswapinfo.c > --- kvm_getswapinfo.c 1999/01/27 11:29:15 1.4 > +++ kvm_getswapinfo.c 1999/02/06 04:46:48 > @@ -127,10 +127,10 @@ > KGET(NL_NSWDEV, nswdev); > KGET(NL_DMMAX, dmmax); > > - if (kvm_swap_nl[NL_SWAPLIST].n_value) > + if (kvm_swap_nl[NL_SWAPLIST].n_type != N_UNDF) > type = 1; > > - if (kvm_swap_nl[NL_SWAPBLIST].n_value) > + if (kvm_swap_nl[NL_SWAPBLIST].n_type != N_UNDF) > type = 2; > > /* > @@ -406,6 +406,13 @@ > struct blist blcopy = { 0 }; > > KGET(NL_SWAPBLIST, swapblist); > + > + if (swapblist == NULL) { > + if (flags & SWIF_DUMP_TREE) > + printf("radix tree: NULL - no swap in system\n"); > + return; > + } > + > KGET2(swapblist, &blcopy, sizeof(blcopy), "*swapblist"); > > if (flags & SWIF_DUMP_TREE) { ---------------------------------- E-Mail: William Woods Date: 05-Feb-99 / Time: 20:56:18 FreeBSD 4.0 -Current ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 21:04:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24212 for freebsd-current-outgoing; Fri, 5 Feb 1999 21:04:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24202; Fri, 5 Feb 1999 21:04:23 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA08567; Sat, 6 Feb 1999 16:04:21 +1100 Date: Sat, 6 Feb 1999 16:04:21 +1100 From: Bruce Evans Message-Id: <199902060504.QAA08567@godzilla.zeta.org.au> To: bde@zeta.org.au, wwoods@cybcon.com Subject: Re: Top not working in -Current?? Cc: current@FreeBSD.ORG, dillon@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Hmmm...I have a swap, although it is mounted /tmp as mfs, here is my fstab: You have swap commented out. mfs isn't swap. > ># Device Mountpoint FStype Options Dump Pass# >/dev/wd0s1b /tmp mfs rw 0 0 >#/dev/wd0s1b none swap sw 0 0 ^^^ Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 21:26:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25747 for freebsd-current-outgoing; Fri, 5 Feb 1999 21:26:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25742 for ; Fri, 5 Feb 1999 21:26:20 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA10052; Sat, 6 Feb 1999 16:26:17 +1100 Date: Sat, 6 Feb 1999 16:26:17 +1100 From: Bruce Evans Message-Id: <199902060526.QAA10052@godzilla.zeta.org.au> To: dillon@apollo.backplane.com, wwoods@cybcon.com Subject: Re: Top not working in -Current?? Cc: bde@zeta.org.au, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This this patch to /usr/src/lib/libkvm/kvm_getswapinfo.c. Then > recompile libkvm and try top and pstat -s again. >Index: kvm_getswapinfo.c >=================================================================== >RCS file: /home/ncvs/src/lib/libkvm/kvm_getswapinfo.c,v >retrieving revision 1.4 >diff -u -r1.4 kvm_getswapinfo.c >--- kvm_getswapinfo.c 1999/01/27 11:29:15 1.4 >+++ kvm_getswapinfo.c 1999/02/06 04:46:48 >@@ -127,10 +127,10 @@ > KGET(NL_NSWDEV, nswdev); > KGET(NL_DMMAX, dmmax); > >- if (kvm_swap_nl[NL_SWAPLIST].n_value) >+ if (kvm_swap_nl[NL_SWAPLIST].n_type != N_UNDF) > type = 1; > >- if (kvm_swap_nl[NL_SWAPBLIST].n_value) >+ if (kvm_swap_nl[NL_SWAPBLIST].n_type != N_UNDF) > type = 2; > > /* >@@ -406,6 +406,13 @@ > struct blist blcopy = { 0 }; > > KGET(NL_SWAPBLIST, swapblist); >+ >+ if (swapblist == NULL) { >+ if (flags & SWIF_DUMP_TREE) >+ printf("radix tree: NULL - no swap in system\n"); >+ return; >+ } >+ > KGET2(swapblist, &blcopy, sizeof(blcopy), "*swapblist"); > > if (flags & SWIF_DUMP_TREE) { This needs more work - library routines shouldn't print to stdout or stderr, especially when there is a function like kvm_geterr() for reporting errors. - no swap is not an error. - top still gets a SIGFPE (the bug is in top -- it divides by swpary[0].ksw_total which may be 0). - pstat and systat have the same bug as top. - libkvm is still bloated with support for old swapping methods, despite more important parts of libkvm not working with kernels more than a few days old because the proc struct changed significantly. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 23:04:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03411 for freebsd-current-outgoing; Fri, 5 Feb 1999 23:04:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03406 for ; Fri, 5 Feb 1999 23:04:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id XAA06756; Fri, 5 Feb 1999 23:04:24 -0800 (PST) (envelope-from dillon) Date: Fri, 5 Feb 1999 23:04:24 -0800 (PST) From: Matthew Dillon Message-Id: <199902060704.XAA06756@apollo.backplane.com> To: Bruce Evans Cc: wwoods@cybcon.com, bde@zeta.org.au, current@FreeBSD.ORG Subject: Re: Top not working in -Current?? References: <199902060526.QAA10052@godzilla.zeta.org.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yah yah. I had to get a machine up without any configured swap, it took a little while. Fixes have been comitted. SWIF_DUMP_TREE is not used for error reporting. It's used to dump the radix tree. While one could argue that printf()'s should not exist in libkvm, I am not going to spend another bunch of hours separating the radix tree dump code into another library. It wouldn't be appropriate anyway. The support for the original swap configuration will eventually be removed, but not until we decide somewhere down the line ( in a few months.. NOT NOW! ) whether to backport the new swapper to -3.x or not. If we do, I'll want that legacy support in for at least one release. -Matt : :>Index: kvm_getswapinfo.c :>=================================================================== :>RCS file: /home/ncvs/src/lib/libkvm/kvm_getswapinfo.c,v :>retrieving revision 1.4 :>diff -u -r1.4 kvm_getswapinfo.c :>--- kvm_getswapinfo.c 1999/01/27 11:29:15 1.4 :>+++ kvm_getswapinfo.c 1999/02/06 04:46:48 :>@@ -127,10 +127,10 @@ :> KGET(NL_NSWDEV, nswdev); :> KGET(NL_DMMAX, dmmax); :> :>- if (kvm_swap_nl[NL_SWAPLIST].n_value) :>+ if (kvm_swap_nl[NL_SWAPLIST].n_type != N_UNDF) :> type = 1; :> :>- if (kvm_swap_nl[NL_SWAPBLIST].n_value) :>+ if (kvm_swap_nl[NL_SWAPBLIST].n_type != N_UNDF) :> type = 2; :> :> /* :>@@ -406,6 +406,13 @@ :> struct blist blcopy = { 0 }; :> :> KGET(NL_SWAPBLIST, swapblist); :>+ :>+ if (swapblist == NULL) { :>+ if (flags & SWIF_DUMP_TREE) :>+ printf("radix tree: NULL - no swap in system\n"); :>+ return; :>+ } :>+ :> KGET2(swapblist, &blcopy, sizeof(blcopy), "*swapblist"); :> :> if (flags & SWIF_DUMP_TREE) { : : :This needs more work :- library routines shouldn't print to stdout or stderr, especially when : there is a function like kvm_geterr() for reporting errors. :- no swap is not an error. :- top still gets a SIGFPE (the bug is in top -- it divides by : swpary[0].ksw_total which may be 0). :- pstat and systat have the same bug as top. :- libkvm is still bloated with support for old swapping methods, despite : more important parts of libkvm not working with kernels more than a : few days old because the proc struct changed significantly. : :Bruce : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 5 23:06:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03649 for freebsd-current-outgoing; Fri, 5 Feb 1999 23:06:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03644 for ; Fri, 5 Feb 1999 23:06:26 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id CAA07659; Sat, 6 Feb 1999 02:05:49 -0500 (EST) From: Mikhail Teterin Message-Id: <199902060705.CAA07659@kot.ne.mediaone.net> Subject: Re: SKIP on 3.0 ? lkm vs kld = SOL ? In-Reply-To: <36bba2d1.455362426@mail.sentex.net> from Mike Tancsa at "Feb 6, 1999 02:05:47 am" To: mike@sentex.net (Mike Tancsa) Date: Sat, 6 Feb 1999 02:05:49 -0500 (EST) Cc: current@FreeBSD.ORG X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA06883 for freebsd-current-outgoing; Fri, 5 Feb 1999 23:47:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06869 for ; Fri, 5 Feb 1999 23:47:11 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id XAA07130; Fri, 5 Feb 1999 23:47:10 -0800 (PST) (envelope-from dillon) Date: Fri, 5 Feb 1999 23:47:10 -0800 (PST) From: Matthew Dillon Message-Id: <199902060747.XAA07130@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: nfs hack to nfs_rename() committed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I was able to successfully 'make buildworld' and 'make installworld' on an NFS-V3 mounted / and /usr with this patch in place, so I am going to commit it to -4.x in liu of an NFS hacker figuring out what exactly was going on with delayed-write buffers. I think it's pretty important that we commit a fix to -3.x too -- either this patch, or the 'correct' fix depending on what the NFS gurus come up with. I don't think this particular patch will fix the vrele ref count bug reported today, but it should fix the problem I reported in regards to make installworld and it *might* have an impact on the dirty-buffer- panic-on-shutdown problem. -Matt Matthew Dillon Index: nfs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_vnops.c,v retrieving revision 1.119 diff -u -r1.119 nfs_vnops.c --- nfs_vnops.c 1999/01/27 22:45:49 1.119 +++ nfs_vnops.c 1999/02/06 07:40:26 @@ -1567,6 +1567,19 @@ } /* + * We have to flush B_DELWRI data prior to renaming + * the file. If we don't, the delayed-write buffers + * can be flushed out later after the file has gone stale + * under NFSV3. NFSV2 does not have this problem because + * ( as far as I can tell ) it flushes dirty buffers more + * often. + */ + + VOP_FSYNC(fvp, fcnp->cn_cred, MNT_WAIT, fcnp->cn_proc); + if (tvp) + VOP_FSYNC(tvp, tcnp->cn_cred, MNT_WAIT, tcnp->cn_proc); + + /* * If the tvp exists and is in use, sillyrename it before doing the * rename of the new file over it. * XXX Can't sillyrename a directory. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 00:28:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA10092 for freebsd-current-outgoing; Sat, 6 Feb 1999 00:28:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from poboxer.pobox.com ([208.141.230.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA10087 for ; Sat, 6 Feb 1999 00:28:42 -0800 (PST) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.2/8.9.1) id CAA00467; Sat, 6 Feb 1999 02:28:38 -0600 (CST) (envelope-from alk) From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 6 Feb 1999 02:28:38 -0600 (CST) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: current@FreeBSD.ORG Subject: imgact_shell.c ENOEXEC X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14011.64749.572752.41299@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the file of the subject, I notice this: /* * Don't allow a shell script to be the shell for a shell * script. :-) */ if (imgp->interpreted) return(ENOEXEC); Why not? I'd like to. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 02:19:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA19963 for freebsd-current-outgoing; Sat, 6 Feb 1999 02:19:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA19958 for ; Sat, 6 Feb 1999 02:19:55 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id TAA13296; Sat, 6 Feb 1999 19:19:45 +0900 (JST) Message-ID: <36BC1233.77541AAC@newsguy.com> Date: Sat, 06 Feb 1999 18:58:11 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: N CC: Matthew Dillon , current@FreeBSD.ORG Subject: Re: Seeing NFS saturation 'loop' when installworld'ing to NFS / and /usr References: <990205221457.18464A-100000@liquid.tpb.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG N wrote: > > On a totally unrelated note, su(1) never works if you're not in group > wheel, Kerberos or no Kerberos, as far as I can tell. Standard BSD behavior. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org Well, as a computer geek, I have to believe in the binary universe. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 03:11:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA24526 for freebsd-current-outgoing; Sat, 6 Feb 1999 03:11:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from stade.demon.co.uk (stade.demon.co.uk [158.152.29.164]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA24521 for ; Sat, 6 Feb 1999 03:11:05 -0800 (PST) (envelope-from aw1@stade.co.uk) Received: (from aw1@localhost) by stade.demon.co.uk (8.9.2/8.9.1) id KAA17679 for current@freebsd.org; Sat, 6 Feb 1999 10:24:08 GMT (envelope-from aw1) Date: Sat, 6 Feb 1999 10:24:08 +0000 From: Adrian Wontroba To: current@FreeBSD.ORG Subject: 4.0 sysinstall - dmenu.c fails to compile Message-ID: <19990206102408.B56231@titus.stade.co.uk> Reply-To: aw1@stade.co.uk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i X-Operating-System: FreeBSD 4.0-CURRENT Organization: Yes, I need some of that. X-Phone: +(44) 121 681 6677 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With a recently cvsupped current, make all in /usr/src/release/sysinstall fails: cc -O -pipe -Wall -I/d3p2/FreeBSD-3.0/src/release/sysinstall/../../gnu/lib/libdialog -I/d3p2/FreeBSD-3.0/src/release/sysinstall -I/d3p2/FreeBSD-3.0/src/release/sysinstall/../../sys -DUC_PRIVATE -DKERN_NO_SYMBOLS -c dmenu.c dmenu.c: In function `dmenuSetVariable': dmenu.c:91: invalid operands to binary != *** Error code 1 Stop. Looks like this is the culprit: revision 1.39 date: 1999/02/05 22:25:13; author: jkh; state: Exp; lines: +5 -5 Add one more "escape" for marking internal variables. -- Adrian Wontroba To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 04:04:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA02717 for freebsd-current-outgoing; Sat, 6 Feb 1999 04:04:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA02707 for ; Sat, 6 Feb 1999 04:04:06 -0800 (PST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (IDENT:Io+mqfhq0kiVfeCUQwt2qFW1AwTeR4LC@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id OAA06995; Sat, 6 Feb 1999 14:03:56 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (IDENT:06hGB0OiS864I8w1A7DGyCD6kaWgnDj/@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id OAA30687; Sat, 6 Feb 1999 14:03:53 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Message-Id: <199902061203.OAA30687@greenpeace.grondar.za> To: "Daniel C. Sobral" cc: N , Matthew Dillon , current@FreeBSD.ORG Subject: Re: Seeing NFS saturation 'loop' when installworld'ing to NFS / and /usr In-Reply-To: Your message of " Sat, 06 Feb 1999 18:58:11 +0900." <36BC1233.77541AAC@newsguy.com> References: <990205221457.18464A-100000@liquid.tpb.net> <36BC1233.77541AAC@newsguy.com> Date: Sat, 06 Feb 1999 14:03:51 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" wrote: > N wrote: > > > > On a totally unrelated note, su(1) never works if you're not in group > > wheel, Kerberos or no Kerberos, as far as I can tell. > > Standard BSD behavior. Hmm... for Kerberos, this ought to be relaxed, really. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 04:28:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA04183 for freebsd-current-outgoing; Sat, 6 Feb 1999 04:28:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA04177 for ; Sat, 6 Feb 1999 04:28:06 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.2) with ESMTP id EAA06482; Sat, 6 Feb 1999 04:27:55 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: aw1@stade.co.uk cc: current@FreeBSD.ORG Subject: Re: 4.0 sysinstall - dmenu.c fails to compile In-reply-to: Your message of "Sat, 06 Feb 1999 10:24:08 GMT." <19990206102408.B56231@titus.stade.co.uk> Date: Sat, 06 Feb 1999 04:27:55 -0800 Message-ID: <6478.918304075@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Already fixed, please re-cvsup. > With a recently cvsupped current, make all in /usr/src/release/sysinstall > fails: > > cc -O -pipe -Wall -I/d3p2/FreeBSD-3.0/src/release/sysinstall/../../gnu/lib/li bdialog -I/d3p2/FreeBSD-3.0/src/release/sysinstall -I/d3p2/FreeBSD-3.0/src/rele ase/sysinstall/../../sys -DUC_PRIVATE -DKERN_NO_SYMBOLS -c dmenu.c > dmenu.c: In function `dmenuSetVariable': > dmenu.c:91: invalid operands to binary != > *** Error code 1 > > Stop. > > Looks like this is the culprit: > > revision 1.39 > date: 1999/02/05 22:25:13; author: jkh; state: Exp; lines: +5 -5 > Add one more "escape" for marking internal variables. > > -- > Adrian Wontroba > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 05:38:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA10969 for freebsd-current-outgoing; Sat, 6 Feb 1999 05:38:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA10959 for ; Sat, 6 Feb 1999 05:38:35 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id AAA18505 for ; Sun, 7 Feb 1999 00:08:29 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA10345; Sun, 7 Feb 1999 00:08:28 +1030 Date: Sun, 7 Feb 1999 00:08:28 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: current@FreeBSD.ORG Subject: pseudo-device gzip Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are there any plans to make this work with ELF binaries? Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 06:36:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA14804 for freebsd-current-outgoing; Sat, 6 Feb 1999 06:36:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA14799 for ; Sat, 6 Feb 1999 06:36:19 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id JAA22645; Sat, 6 Feb 1999 09:36:09 -0500 (EST) Date: Sat, 6 Feb 1999 09:36:08 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Matthew Dillon cc: William Woods , FreeBSD Current Subject: Re: Problem with "top" on current ? In-Reply-To: <199902060418.UAA02533@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 5 Feb 1999, Matthew Dillon wrote: > > : > :Ahhh...not sure what you mean here....... > : > :On 06-Feb-99 Brian Feldman wrote: > :> On Fri, 5 Feb 1999, William Woods wrote: > :>> Floating point exception > :... > :> > :> Try "kvm_mkdb" yet? > :> > :---------------------------------- > :E-Mail: William Woods > > Try this: > > cd /usr/src/lib/libkvm > make; make install; make clean > cd /usr/src/usr.bin/top > make; make install; make clean > kvm_mkdb > In case anyone wants to rebuild everything with a kvm dependency, I made a little something (maybe it's a time for a make kvmdepend target, or something) #cd /usr/src cd lib/libkvm make all install clean cd - for dir in bin sbin usr.bin usr.sbin; do cd $dir for file in *; do if [ -f $file/Makefile ] && grep lkvm $file/Makefile; then (cd $file; make all install clean) fi done cd .. done > > -Matt > > Matthew Dillon > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 09:20:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29862 for freebsd-current-outgoing; Sat, 6 Feb 1999 09:20:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from k6n1.znh.org ([207.109.235.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29854 for ; Sat, 6 Feb 1999 09:20:07 -0800 (PST) (envelope-from zach@uffdaonline.net) Received: (from zach@localhost) by k6n1.znh.org (8.9.2/8.9.1) id RAA27274; Sat, 6 Feb 1999 17:22:46 GMT (envelope-from zach) Message-ID: <19990206112246.A26991@znh.org> Date: Sat, 6 Feb 1999 11:22:46 -0600 From: Zach Heilig To: alk@pobox.com, current@FreeBSD.ORG Subject: Re: imgact_shell.c ENOEXEC References: <14011.64749.572752.41299@avalon.east> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <14011.64749.572752.41299@avalon.east>; from Tony Kimball on Sat, Feb 06, 1999 at 02:28:38AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Feb 06, 1999 at 02:28:38AM -0600, Tony Kimball wrote: > In the file of the subject, I notice this: > /* > * Don't allow a shell script to be the shell for a shell > * script. :-) > */ > if (imgp->interpreted) > return(ENOEXEC); > Why not? I'd like to. Imagine this: $ file /tmp/test.sh /tmp/test.sh: a /tmp/test.sh script text $ /tmp/test.sh ... -- Zach Heilig / Zach Heilig "Americans are sensitive about their money, and since this was the first major change in the greenback in nearly 70 years, a radical redesign might have been too much for consumers to comprehend" -- John Iddings [COINage, Feb. 1999]. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 09:58:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03857 for freebsd-current-outgoing; Sat, 6 Feb 1999 09:58:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from post.mail.demon.net (post-20.mail.demon.net [194.217.242.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03852 for ; Sat, 6 Feb 1999 09:58:50 -0800 (PST) (envelope-from dom@myrddin.demon.co.uk) Received: from [158.152.54.180] (helo=myrddin.demon.co.uk) by post.mail.demon.net with esmtp (Exim 2.10 #2) id 109C0F-0007YR-00; Sat, 6 Feb 1999 17:58:47 +0000 Received: from localhost (myrddin.demon.co.uk) [127.0.0.1] by myrddin.demon.co.uk with esmtp (Exim 1.92 #1) id 109Bzb-0000L4-00; Sat, 6 Feb 1999 17:58:07 +0000 To: David Malone Cc: freebsd-current@FreeBSD.ORG Subject: Re: Lots of "panic: vrele: negative ref cnt" References: <9902052103.aa20667@salmon.maths.tcd.ie> From: Dom Mitchell In-Reply-To: David Malone's message of "Fri, 05 Feb 1999 21:03:34 +0000" X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Date: Sat, 06 Feb 1999 17:58:07 +0000 Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Malone writes: > We're getting lots of negative reference counts for 3.0-STABLE. We've been > getting them since long before Christmas. We have 3 SMP machines, all heavy > NFS clients, which are dieing about 1 per day with this panic. > > Several of these hangs have been provoked by me logging out - you can see > the ^D in the xterm - but everything dies before the window goes away. In > the trace below the it is closing my tty I think. > > We have also seen this happen with a write process trying to write to > someones tty. I've seen identical panics when using nmh's spost command to send mail. Instant panic saying "negative ref cnt". This is using an NFS mounted home directory (containing the draft mail to be sent). Unfortunately, I didn't have time to investigate further, so I just switched over to using SMTP instead. I'll try again on Monday to see if it's still doing it for me. -- When I said "we", officer, I was referring to myself, the four young ladies, and, of course, the goat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 10:01:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04085 for freebsd-current-outgoing; Sat, 6 Feb 1999 10:01:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA04080 for ; Sat, 6 Feb 1999 10:01:52 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 6 Feb 99 18:01:50 +0000 (GMT) To: Dom Mitchell cc: David Malone , freebsd-current@FreeBSD.ORG Subject: Re: Lots of "panic: vrele: negative ref cnt" In-reply-to: Your message of "Sat, 06 Feb 1999 17:58:07 GMT." Date: Sat, 06 Feb 1999 18:01:50 +0000 From: David Malone Message-ID: <9902061801.aa26680@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've seen identical panics when using nmh's spost command to send > mail. Instant panic saying "negative ref cnt". This is using an NFS > mounted home directory (containing the draft mail to be sent). > Unfortunately, I didn't have time to investigate further, so I just > switched over to using SMTP instead. Interesting. I've just had our only 3.0-STABLE non-SMP box die with the same problem - so it isn't SMP related by the looks of things. If we can make it reproducable then maybe we can get Matt to look at it ;-) David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 10:53:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10393 for freebsd-current-outgoing; Sat, 6 Feb 1999 10:53:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from poboxer.pobox.com ([208.149.16.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10379 for ; Sat, 6 Feb 1999 10:53:27 -0800 (PST) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.2/8.9.1) id MAA06195; Sat, 6 Feb 1999 12:40:01 -0600 (CST) (envelope-from alk) From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 6 Feb 1999 12:39:21 -0600 (CST) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: zach@uffdaonline.net Cc: current@FreeBSD.ORG Subject: Re: imgact_shell.c ENOEXEC References: <14011.64749.572752.41299@avalon.east> <19990206112246.A26991@znh.org> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14012.34942.338695.378661@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth Zach Heilig on Sat, 6 February: : On Sat, Feb 06, 1999 at 02:28:38AM -0600, Tony Kimball wrote: : > In the file of the subject, I notice this: : : > /* : > * Don't allow a shell script to be the shell for a shell : > * script. :-) : > */ : > if (imgp->interpreted) : > return(ENOEXEC); : : > Why not? I'd like to. : : Imagine this: : : $ file /tmp/test.sh : /tmp/test.sh: a /tmp/test.sh script text : $ /tmp/test.sh : Won't this just fail when the recursion level is such that the command length exceeds stringspace? Ah, I see the difference: /* * Copy to end of token. No need to watch stringspace * because this is at the front of the string buffer * and the maximum shell command length is tiny. */ Very bogus. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 11:19:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13245 for freebsd-current-outgoing; Sat, 6 Feb 1999 11:19:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13240 for ; Sat, 6 Feb 1999 11:19:17 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (pm3a-9.cybcon.com [205.147.75.138]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id LAA05746 for ; Sat, 6 Feb 1999 11:19:15 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 06 Feb 1999 11:18:41 -0800 (PST) Reply-To: wwoods@cybcon.com From: William Woods To: FreeBSD Current Subject: Floppy Tape Driver..... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just finished looking in LINT for "ft" the floppy tape device. Now I remember some discussion of this being removed a while ago, but I do not remember the outcome of this. I am running a -curent system and was wondering what I sue for a floppy tape driver. ---------------------------------- E-Mail: William Woods Date: 06-Feb-99 / Time: 11:17:08 FreeBSD 4.0 -Current ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 11:28:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13645 for freebsd-current-outgoing; Sat, 6 Feb 1999 11:28:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13639 for ; Sat, 6 Feb 1999 11:28:07 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id UAA43136; Sat, 6 Feb 1999 20:27:14 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: wwoods@cybcon.com cc: FreeBSD Current Subject: Re: Floppy Tape Driver..... In-reply-to: Your message of "Sat, 06 Feb 1999 11:18:41 PST." Date: Sat, 06 Feb 1999 20:27:14 +0100 Message-ID: <43133.918329234@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , William Woods writes: >I just finished looking in LINT for "ft" the floppy tape device. Now I remember >some discussion of this being removed a while ago, but I do not remember the >outcome of this. I am running a -curent system and was wondering what I sue for >a floppy tape driver. Save yourself the worry and trouble and buy an atapi tape instead... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 11:47:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15327 for freebsd-current-outgoing; Sat, 6 Feb 1999 11:47:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA15322 for ; Sat, 6 Feb 1999 11:47:22 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA17790; Sat, 6 Feb 1999 11:39:16 -0800 (PST) Received: from s204m82.isp.whistle.com(207.76.204.82) via SMTP by alpo.whistle.com, id smtpdo17782; Sat Feb 6 19:39:14 1999 Date: Sat, 6 Feb 1999 11:39:14 -0800 (PST) From: Julian Elischer X-Sender: julian@s204m82.isp.whistle.com To: Poul-Henning Kamp cc: wwoods@cybcon.com, FreeBSD Current Subject: Re: Floppy Tape Driver..... In-Reply-To: <43133.918329234@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OR, get teh changes needed (that were removed) from the fd driver.. (you can find them using the CVS web-pages) and the correct files, and get it all working again.. One of the problems was that there was no-one that the intersecting set of developers who could maintain the driver, and people who had and used these devices was a null set. If this were to change (i.e. there wa an active maintainer, and users) then it could possibly be re-introduced, or at least made into a supported patch set.) julian On Sat, 6 Feb 1999, Poul-Henning Kamp wrote: > In message , William Woods writes: > > >I just finished looking in LINT for "ft" the floppy tape device. Now I remember > >some discussion of this being removed a while ago, but I do not remember the > >outcome of this. I am running a -curent system and was wondering what I sue for > >a floppy tape driver. > > Save yourself the worry and trouble and buy an atapi tape instead... > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 11:49:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15726 for freebsd-current-outgoing; Sat, 6 Feb 1999 11:49:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA15719 for ; Sat, 6 Feb 1999 11:49:45 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (usr1-39.cybcon.com [205.147.76.40]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id LAA07113; Sat, 6 Feb 1999 11:49:41 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 06 Feb 1999 11:49:08 -0800 (PST) Reply-To: wwoods@cybcon.com From: William Woods To: Julian Elischer Subject: Re: Floppy Tape Driver..... Cc: FreeBSD Current Cc: FreeBSD Current , Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So, basically I am screwed? On 06-Feb-99 Julian Elischer wrote: > OR, > > get teh changes needed (that were removed) from the fd driver.. > (you can find them using the CVS web-pages) > and the correct files, and get it all working again.. > > One of the problems was that there was no-one that the intersecting set of > developers who could maintain the driver, and people who had and used > these devices was a null set. > > If this were to change (i.e. there wa an active maintainer, and users) > then it could possibly be re-introduced, or at least made into a supported > patch set.) > > julian > > > On Sat, 6 Feb 1999, Poul-Henning Kamp wrote: > >> In message , William Woods writes: >> >> >I just finished looking in LINT for "ft" the floppy tape device. Now I >> >remember >> >some discussion of this being removed a while ago, but I do not remember >> >the >> >outcome of this. I am running a -curent system and was wondering what I sue >> >for >> >a floppy tape driver. >> >> Save yourself the worry and trouble and buy an atapi tape instead... >> >> -- >> Poul-Henning Kamp FreeBSD coreteam member >> phk@FreeBSD.ORG "Real hackers run -current on their laptop." >> FreeBSD -- It will take a long time before progress goes too far! >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-current" in the body of the message >> ---------------------------------- E-Mail: William Woods Date: 06-Feb-99 / Time: 11:48:34 FreeBSD 4.0 -Current ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 11:53:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16048 for freebsd-current-outgoing; Sat, 6 Feb 1999 11:53:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16037 for ; Sat, 6 Feb 1999 11:53:18 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (usr1-39.cybcon.com [205.147.76.40]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id LAA07055; Sat, 6 Feb 1999 11:48:14 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <43133.918329234@critter.freebsd.dk> Date: Sat, 06 Feb 1999 11:47:40 -0800 (PST) Reply-To: wwoods@cybcon.com From: William Woods To: Poul-Henning Kamp Subject: Re: Floppy Tape Driver..... Cc: FreeBSD Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yea yea, I know......but this was a gifyt for Christmass and I really dont have any extra $$ right now////so where is the floppy tape driver? On 06-Feb-99 Poul-Henning Kamp wrote: > In message , William Woods writes: > >>I just finished looking in LINT for "ft" the floppy tape device. Now I >>remember >>some discussion of this being removed a while ago, but I do not remember the >>outcome of this. I am running a -curent system and was wondering what I sue >>for >>a floppy tape driver. > > Save yourself the worry and trouble and buy an atapi tape instead... > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! ---------------------------------- E-Mail: William Woods Date: 06-Feb-99 / Time: 11:46:00 FreeBSD 4.0 -Current ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 12:01:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16660 for freebsd-current-outgoing; Sat, 6 Feb 1999 12:01:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16648 for ; Sat, 6 Feb 1999 12:01:07 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id VAA65416; Sat, 6 Feb 1999 21:00:27 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: wwoods@cybcon.com cc: Julian Elischer , FreeBSD Current Subject: Re: Floppy Tape Driver..... In-reply-to: Your message of "Sat, 06 Feb 1999 11:49:08 PST." Date: Sat, 06 Feb 1999 21:00:27 +0100 Message-ID: <65414.918331227@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , William Woods writes: >So, basically I am screwed? Run 2.2.8 ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 12:07:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17188 for freebsd-current-outgoing; Sat, 6 Feb 1999 12:07:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17182 for ; Sat, 6 Feb 1999 12:07:00 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id VAA70867; Sat, 6 Feb 1999 21:06:23 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: wwoods@cybcon.com cc: FreeBSD Current Subject: Re: Floppy Tape Driver..... In-reply-to: Your message of "Sat, 06 Feb 1999 11:47:40 PST." Date: Sat, 06 Feb 1999 21:06:23 +0100 Message-ID: <70862.918331583@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , William Woods writes: >Yea yea, I know......but this was a gifyt for Christmass and I really dont have >any extra $$ right now////so where is the floppy tape driver? Btw, if this is a new device, it is unlikely that the ft driver will support it anyway, I don't think it ever came above the 80Mbyte tapes... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 12:15:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18432 for freebsd-current-outgoing; Sat, 6 Feb 1999 12:15:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18421 for ; Sat, 6 Feb 1999 12:15:46 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (usr1-39.cybcon.com [205.147.76.40]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id MAA08149; Sat, 6 Feb 1999 12:10:42 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <70862.918331583@critter.freebsd.dk> Date: Sat, 06 Feb 1999 12:10:08 -0800 (PST) Reply-To: wwoods@cybcon.com From: William Woods To: Poul-Henning Kamp Subject: Re: Floppy Tape Driver..... Cc: FreeBSD Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm...it is an Iomega gig internal............any ideas for me then? On 06-Feb-99 Poul-Henning Kamp wrote: > In message , William Woods writes: > >>Yea yea, I know......but this was a gifyt for Christmass and I really dont >>have >>any extra $$ right now////so where is the floppy tape driver? > > Btw, if this is a new device, it is unlikely that the ft driver will support > it anyway, I don't think it ever came above the 80Mbyte tapes... > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! ---------------------------------- E-Mail: William Woods Date: 06-Feb-99 / Time: 12:09:20 FreeBSD 4.0 -Current ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 12:21:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19147 for freebsd-current-outgoing; Sat, 6 Feb 1999 12:21:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from phluffy.fks.bt (net25-cust199.pdx.wantweb.net [24.236.25.199]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19141 for ; Sat, 6 Feb 1999 12:21:52 -0800 (PST) (envelope-from myke@ees.com) Received: from localhost (myke@localhost) by phluffy.fks.bt (8.8.8/8.8.8) with ESMTP id MAA16388; Sat, 6 Feb 1999 12:18:36 -0800 (PST) (envelope-from myke@ees.com) Date: Sat, 6 Feb 1999 12:18:35 -0800 (PST) From: Mike Holling X-Sender: myke@phluffy.fks.bt To: Poul-Henning Kamp cc: wwoods@cybcon.com, FreeBSD Current Subject: Re: Floppy Tape Driver..... In-Reply-To: <70862.918331583@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Btw, if this is a new device, it is unlikely that the ft driver will support > it anyway, I don't think it ever came above the 80Mbyte tapes... I have a 2.2.x machine with a 120M device. I believe someone on this list stated that they had it working with a 250M device as well. - Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 12:24:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19382 for freebsd-current-outgoing; Sat, 6 Feb 1999 12:24:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19377 for ; Sat, 6 Feb 1999 12:24:44 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id PAA11341 for ; Sat, 6 Feb 1999 15:24:36 -0500 (EST) Date: Sat, 6 Feb 1999 15:24:36 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@FreeBSD.ORG Subject: msdosfs/vn trouble, doscmd "nicety", fd trouble Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id MAA19378 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, I've got three separate problems today: Doscmd is really only useable with X, and running doscmd -bx with a local X server generates tons of "trap 25 with interrupts disabled". I don't recall this being the case many moons ago... When I mount a floppy image (msdos, using the vn device), I soon get: panic: zone: entry not free syncing disks... 152 47 44 38 31 24 17 1 done dumping to dev 30001, offset 73728 dump 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:287 287 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:287 #1 0xf0136fed in panic (fmt=0xf0213774 "zone: entry not free") at ../../kern/kern_shutdown.c:448 #2 0xf01afed3 in zerror (error=1) at ../../vm/vm_zone.c:455 #3 0xf015a650 in namei (ndp=0xf78f9f08) at ../../vm/vm_zone.h:91 #4 0xf0161238 in rename (p=0xf73731e0, uap=0xf78f9f84) at ../../kern/vfs_syscalls.c:2461 #5 0xf01d9a2b in syscall (frame={tf_es = 47, tf_ds = 47, tf_edi = 134828010, tf_esi = 134934656, tf_ebp = -272657172, tf_isp = -141582380, tf_ebx = 134931436, tf_edx = -272640240, tf_ecx = 14, tf_eax = 128, tf_trapno = 7, tf_err = 2, tf_eip = 672138692, tf_cs = 31, tf_eflags = 582, tf_esp = -272657192, tf_ss = 47}) at ../../i386/i386/trap.c:1100 #6 0xf01cc4fc in Xint0x80_syscall () #7 0x8050ec1 in ?? () #8 0x8050703 in ?? () #9 0x80516cc in ?? () #10 0x8052ae0 in ?? () #11 0x8052b90 in ?? () #12 0x804e43d in ?? () #13 0x8068ebc in ?? () #14 0x804a491 in ?? () (kgdb) (kgdb) frame 3 #3 0xf015a650 in namei (ndp=0xf78f9f08) at ../../vm/vm_zone.h:91 91 zerror(ZONE_ERROR_NOTFREE); (kgdb) print *ndp $1 = {ni_dirp = 0x80af080 ".new.GraphBuil", ni_segflg = UIO_USERSPACE, ni_startdir = 0xf78f9f30, ni_rootdir = 0xf012e469, ni_vp = 0xf05a0e00, ni_dvp = 0xf73731e0, ni_pathlen = 4147589600, ni_next = 0x5e9
, ni_loopcnt = 0, ni_cnd = { cn_nameiop = 2, cn_flags = 4112, cn_proc = 0xf73731e0, cn_cred = 0xf133c200, cn_pnbuf = 0xf73731e0 "à\022\221÷", cn_nameptr = 0x80000000
, cn_namelen = 0, cn_hash = 134828010, cn_consume = -266186924}} I'll try do some more testing on this... I really don't know if it's a problem with msdosfs or vn. It will only show p (like this) with INVARIANTS on. I also notice I can't seem to use my flopy drive anymore. The BIOS and BTX can both use it, the kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in fd0: 1.44MB 3.5in and I can hear the drive click-whir-buzz like normal, but if I try to use the drive ({,r}fd0, etc), all I get is fd0: recal failed ST0 70 cyl 0 fd0: recal failed ST0 70 cyl 0 fd0: recal failed ST0 70 cyl 0 fd0: recal failed ST0 78 cyl 0 fd0c: hard error reading fsbn 0 of 0-3 (No status) With this, I'm wondering if everyone's floppy drives work fine and if their drives work fine on an AcerLabs socket 7 motherboard. If so, maybe I can scrounge up a different floppy drive and try it out, but it really seems to not be a hardware problem. Thanks in advance. Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 12:27:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19688 for freebsd-current-outgoing; Sat, 6 Feb 1999 12:27:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19619 for ; Sat, 6 Feb 1999 12:26:17 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id VAA87720; Sat, 6 Feb 1999 21:25:33 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: wwoods@cybcon.com cc: FreeBSD Current Subject: Re: Floppy Tape Driver..... In-reply-to: Your message of "Sat, 06 Feb 1999 12:10:08 PST." Date: Sat, 06 Feb 1999 21:25:33 +0100 Message-ID: <87718.918332733@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 4:1 that the ft driver will not do anything with it... In message , William Woods writes: >Hmm...it is an Iomega gig internal............any ideas for me then? > >On 06-Feb-99 Poul-Henning Kamp wrote: >> In message , William Woods writes: >> >>>Yea yea, I know......but this was a gifyt for Christmass and I really dont >>>have >>>any extra $$ right now////so where is the floppy tape driver? >> >> Btw, if this is a new device, it is unlikely that the ft driver will support >> it anyway, I don't think it ever came above the 80Mbyte tapes... >> >> -- >> Poul-Henning Kamp FreeBSD coreteam member >> phk@FreeBSD.ORG "Real hackers run -current on their laptop." >> FreeBSD -- It will take a long time before progress goes too far! > > >---------------------------------- >E-Mail: William Woods >Date: 06-Feb-99 / Time: 12:09:20 >FreeBSD 4.0 -Current >---------------------------------- > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 12:37:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20520 for freebsd-current-outgoing; Sat, 6 Feb 1999 12:37:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cx757770-a.fed1.sdca.home.com (cx757770-a.fed1.sdca.home.com [24.0.167.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20515 for ; Sat, 6 Feb 1999 12:37:52 -0800 (PST) (envelope-from daren@sefcik.cc) Received: from localhost (daren@localhost) by cx757770-a.fed1.sdca.home.com (8.9.1/8.9.1) with ESMTP id MAA03844 for ; Sat, 6 Feb 1999 12:55:17 -0800 (PST) Date: Sat, 6 Feb 1999 12:55:16 -0800 (PST) From: Daren Sefcik X-Sender: daren@cx757770-a.fed1.sdca.home.com To: freebsd-current@FreeBSD.ORG Subject: low level format--how?? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it possible to do a low level format of a scsi disk..I do not see a utility to do so. thanks in advance Daren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 12:46:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21024 for freebsd-current-outgoing; Sat, 6 Feb 1999 12:46:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21019 for ; Sat, 6 Feb 1999 12:46:12 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (jbloom.ne.mediaone.net [24.128.100.196]) by chmls06.mediaone.net (8.8.7/8.8.7) with ESMTP id PAA22610; Sat, 6 Feb 1999 15:46:10 -0500 (EST) Message-ID: <36BCAA15.4CBB2C0F@acm.org> Date: Sat, 06 Feb 1999 15:46:13 -0500 From: Jim Bloom X-Mailer: Mozilla 4.5 [en]C-MOENE (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD Current CC: wwoods@cybcon.com Subject: Re: Floppy Tape Driver..... References: <70862.918331583@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I used to run a 250Mb with extended length tapes (350Mb). That is still far short of the size of newer tape drives. Jim Bloom bloom@acm.org Poul-Henning Kamp wrote: > > In message , William Woods writes: > > >Yea yea, I know......but this was a gifyt for Christmass and I really dont have > >any extra $$ right now////so where is the floppy tape driver? > > Btw, if this is a new device, it is unlikely that the ft driver will support > it anyway, I don't think it ever came above the 80Mbyte tapes... > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 12:46:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21264 for freebsd-current-outgoing; Sat, 6 Feb 1999 12:46:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pinhead.parag.codegen.com ([207.44.235.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21257 for ; Sat, 6 Feb 1999 12:46:50 -0800 (PST) (envelope-from parag@cgt.com) Received: from pinhead.parag.codegen.com (parag@localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.2/8.8.8) with ESMTP id MAA29155; Sat, 6 Feb 1999 12:46:40 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199902062046.MAA29155@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman cc: current@FreeBSD.ORG Subject: Re: msdosfs/vn trouble, doscmd "nicety", fd trouble In-Reply-To: Message from Brian Feldman of "Sat, 06 Feb 1999 15:24:36 EST." X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Sat, 06 Feb 1999 12:46:40 -0800 From: Parag Patel Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id MAA21260 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Doscmd is really only useable with X, and running doscmd -bx with a local X > server generates tons of "trap 25 with interrupts disabled". I don't recall > this being the case many moons ago... Yeah, me too. I was told this is a bug in doscmd and the owner needs to fix it. I don't understand the inner parts of DOS VM86 as it relates to the x86 architecture or I'd take a crack at it. Instead, I hacked as follows to silence this specific error. This is not a good thing to do in general, but it lets me use doscmd to program EPROMs. I just use cvs instead of cvsup to update my working source tree so I don't lose this (and other) local mods. Don't know about the panic though - I haven't seen anything like it. I've never used vn to access the floppy under DOS. Instead I just point it to a 1.44Mb floppy image on the filesystem and a 10Mb hard-drive image on the filesystem, and it works fine for me. -- Parag Patel =================================================================== # my ~/.doscmdrc assign A: /u/parag/dos/1.44M 1440 assign B: /dev/rfd0 1440 assign C: /u/parag/dos/10M 306 4 17 assign D: /cgt/src/bin/of/ppc assign E: /u/parag/tmp #assign lpt1: direct /dev/lpt0 # map in the parallel port for the EMP-10 portmap 0x378 8 boot c: =================================================================== Index: trap.c =================================================================== RCS file: /src/freebsd/src/sys/i386/i386/trap.c,v retrieving revision 1.133 diff -c -r1.133 trap.c *** trap.c 1999/01/06 23:05:36 1.133 --- trap.c 1999/01/16 18:32:46 *************** *** 234,240 **** printf( "pid %ld (%s): trap %d with interrupts disabled\n", (long)curproc->p_pid, curproc->p_comm, type); ! else if (type != T_BPTFLT && type != T_TRCTRAP) /* * XXX not quite right, since this may be for a * multiple fault in user mode. --- 234,240 ---- printf( "pid %ld (%s): trap %d with interrupts disabled\n", (long)curproc->p_pid, curproc->p_comm, type); ! else if (type != T_BPTFLT && type != T_TRCTRAP && type != T_TSSFLT) /* * XXX not quite right, since this may be for a * multiple fault in user mode. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 12:47:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21291 for freebsd-current-outgoing; Sat, 6 Feb 1999 12:47:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from superior.mooseriver.com (superior.mooseriver.com [208.138.31.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21284 for ; Sat, 6 Feb 1999 12:46:58 -0800 (PST) (envelope-from jgrosch@superior.mooseriver.com) Received: (from jgrosch@localhost) by superior.mooseriver.com (8.8.8/8.8.8) id MAA06643; Sat, 6 Feb 1999 12:46:56 -0800 (PST) (envelope-from jgrosch) Message-ID: <19990206124656.A6621@mooseriver.com> Date: Sat, 6 Feb 1999 12:46:56 -0800 From: Josef Grosch To: Daren Sefcik , freebsd-current@FreeBSD.ORG Subject: Re: low level format--how?? Reply-To: jgrosch@mooseriver.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Daren Sefcik on Sat, Feb 06, 1999 at 12:55:16PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Feb 06, 1999 at 12:55:16PM -0800, Daren Sefcik wrote: > Is it possible to do a low level format > of a scsi disk..I do not see a utility > to do so. If you are using an Adaptec controller card, like a 2940, there is a low-level format in the card-bios. You can get into the card-bios utilities by watching the system as it is coming up and hitting control-a. Your mileage may vary. Josef -- Josef Grosch | Another day closer to a | FreeBSD 3.0 jgrosch@MooseRiver.com | Micro$oft free world | UNIX for the masses To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 12:52:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21895 for freebsd-current-outgoing; Sat, 6 Feb 1999 12:52:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21890 for ; Sat, 6 Feb 1999 12:52:38 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id PAA11317; Sat, 6 Feb 1999 15:51:40 -0500 (EST) From: Mikhail Teterin Message-Id: <199902062051.PAA11317@kot.ne.mediaone.net> Subject: Re: low level format--how?? In-Reply-To: from Daren Sefcik at "Feb 6, 1999 12:55:16 pm" To: daren@sefcik.cc (Daren Sefcik) Date: Sat, 6 Feb 1999 15:51:40 -0500 (EST) Cc: current@FreeBSD.ORG X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21968 for freebsd-current-outgoing; Sat, 6 Feb 1999 12:53:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cx757770-a.fed1.sdca.home.com (cx757770-a.fed1.sdca.home.com [24.0.167.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21963 for ; Sat, 6 Feb 1999 12:53:12 -0800 (PST) (envelope-from daren@sefcik.cc) Received: from localhost (daren@localhost) by cx757770-a.fed1.sdca.home.com (8.9.1/8.9.1) with ESMTP id NAA03940; Sat, 6 Feb 1999 13:10:35 -0800 (PST) Date: Sat, 6 Feb 1999 13:10:34 -0800 (PST) From: Daren Sefcik X-Sender: daren@cx757770-a.fed1.sdca.home.com To: Josef Grosch cc: freebsd-current@FreeBSD.ORG Subject: Re: low level format--how?? In-Reply-To: <19990206124656.A6621@mooseriver.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No..it's an HP generic and it has no BIOS... I tried using SCSI ToolBox on my windows machine but it just hangs. The disk was formatted for freebsd and I used the newfs_msdos command on it and now it is hosed..I can't seem to get it back. Disklabel gives me a "disk not configured" error argghh..any ideas/help..?? Daren On Sat, 6 Feb 1999, Josef Grosch wrote: > On Sat, Feb 06, 1999 at 12:55:16PM -0800, Daren Sefcik wrote: > > Is it possible to do a low level format > > of a scsi disk..I do not see a utility > > to do so. > > If you are using an Adaptec controller card, like a 2940, there is a > low-level format in the card-bios. You can get into the card-bios utilities > by watching the system as it is coming up and hitting control-a. > > Your mileage may vary. > > > Josef > > -- > Josef Grosch | Another day closer to a | FreeBSD 3.0 > jgrosch@MooseRiver.com | Micro$oft free world | UNIX for the masses > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 12:55:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22163 for freebsd-current-outgoing; Sat, 6 Feb 1999 12:55:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cx757770-a.fed1.sdca.home.com (cx757770-a.fed1.sdca.home.com [24.0.167.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22158 for ; Sat, 6 Feb 1999 12:55:57 -0800 (PST) (envelope-from daren@sefcik.cc) Received: from localhost (daren@localhost) by cx757770-a.fed1.sdca.home.com (8.9.1/8.9.1) with ESMTP id NAA03963; Sat, 6 Feb 1999 13:13:11 -0800 (PST) Date: Sat, 6 Feb 1999 13:13:10 -0800 (PST) From: Daren Sefcik X-Sender: daren@cx757770-a.fed1.sdca.home.com To: Mikhail Teterin cc: current@FreeBSD.ORG Subject: Re: low level format--how?? In-Reply-To: <199902062051.PAA11317@kot.ne.mediaone.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > =Is it possible to do a low level format of a scsi disk..I do not see a > =utility to do so. > > scsiformat(8) > > -mi rover >man scsiformat No manual entry for scsiformat rover > rover >uname -a FreeBSD rover.sefcik.cc 4.0-CURRENT FreeBSD 4.0-CURRENT #2: Sat Jan 30 09:17:12 PST 1999 daren@rover.sefcik.cc:/usr/src/sys/compile/ROVER i386 rover > Didn't find it or scsi... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 12:59:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22495 for freebsd-current-outgoing; Sat, 6 Feb 1999 12:59:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22488 for ; Sat, 6 Feb 1999 12:59:05 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id PAA13240; Sat, 6 Feb 1999 15:58:48 -0500 (EST) Date: Sat, 6 Feb 1999 15:58:48 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Daren Sefcik cc: Josef Grosch , freebsd-current@FreeBSD.ORG Subject: Re: low level format--how?? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 6 Feb 1999, Daren Sefcik wrote: > No..it's an HP generic and it has no BIOS... > I tried using SCSI ToolBox on my windows > machine but it just hangs. > The disk was formatted for freebsd and I used > the newfs_msdos command on it and now it > is hosed..I can't seem to get it back. > Disklabel gives me a "disk not configured" error Have you tried dd if=/dev/zero of=/dev/rsd# count=100? > > argghh..any ideas/help..?? > > Daren > > On Sat, 6 Feb 1999, Josef Grosch wrote: > > > On Sat, Feb 06, 1999 at 12:55:16PM -0800, Daren Sefcik wrote: > > > Is it possible to do a low level format > > > of a scsi disk..I do not see a utility > > > to do so. > > > > If you are using an Adaptec controller card, like a 2940, there is a > > low-level format in the card-bios. You can get into the card-bios utilities > > by watching the system as it is coming up and hitting control-a. > > > > Your mileage may vary. > > > > > > Josef > > > > -- > > Josef Grosch | Another day closer to a | FreeBSD 3.0 > > jgrosch@MooseRiver.com | Micro$oft free world | UNIX for the masses > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 13:01:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22738 for freebsd-current-outgoing; Sat, 6 Feb 1999 13:01:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cx757770-a.fed1.sdca.home.com (cx757770-a.fed1.sdca.home.com [24.0.167.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22733 for ; Sat, 6 Feb 1999 13:01:02 -0800 (PST) (envelope-from daren@sefcik.cc) Received: from localhost (daren@localhost) by cx757770-a.fed1.sdca.home.com (8.9.1/8.9.1) with ESMTP id NAA04027; Sat, 6 Feb 1999 13:18:22 -0800 (PST) Date: Sat, 6 Feb 1999 13:18:21 -0800 (PST) From: Daren Sefcik X-Sender: daren@cx757770-a.fed1.sdca.home.com To: Brian Feldman cc: Josef Grosch , freebsd-current@FreeBSD.ORG Subject: Re: low level format--how?? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Have you tried dd if=/dev/zero of=/dev/rsd# count=100? > rover# dd if=/dev/zero of=/dev/rda0 count=100 dd: /dev/rda0: Device not configured rover# yeah.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 13:04:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22931 for freebsd-current-outgoing; Sat, 6 Feb 1999 13:04:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (pm3-19.ppp.wenet.net [206.15.85.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22926 for ; Sat, 6 Feb 1999 13:04:08 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.2/8.9.1) with ESMTP id NAA09792; Sat, 6 Feb 1999 13:00:59 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Sat, 6 Feb 1999 13:00:59 -0800 (PST) From: Alex Zepeda To: Brian Feldman cc: current@FreeBSD.ORG Subject: Re: msdosfs/vn trouble, doscmd "nicety", fd trouble In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 6 Feb 1999, Brian Feldman wrote: > When I mount a floppy image (msdos, using the vn device), I soon get: > panic: zone: entry not free When I needed to copy some stuff onto a "boot disk", this worked fine with my Feb 1 kernel. Installing Win95 on Bochs OTOH and mounting the resulting disk image (was a pain, didn't work).... > I'll try do some more testing on this... I really don't know if it's a problem > with msdosfs or vn. It will only show p (like this) with INVARIANTS on. As I said above... it was rather weird that the hdd image I was using wouldn't mount when I vnconfig'd it and mount -tmsdosfs'd it.. it claimed the bpb was invalid.. Win95 under Bochs grok'd it.. > With this, I'm wondering if everyone's floppy drives work fine and if their > drives work fine on an AcerLabs socket 7 motherboard. If so, maybe I can > scrounge up a different floppy drive and try it out, but it really seems > to not be a hardware problem. The only floppy oddity I've noticed of late was when I tried making disk images of 1.68mb disks. dd if=/dev/fd0.1720.. worked fine and generated disk images fine.. but generated a LOT of error messages towards the end like: fd0c: hard error reading fsbn 3360 of 3360-3363 (ST0 40 ST1 4 ST2 0 cyl 80 hd 0 sec 1) fd0c: hard error reading fsbn 3364 of 3364-3367 (ST0 40 ST1 4 ST2 0 cyl 80 hd 0 sec 5) fd0c: hard error reading fsbn 3360 of 3360-3363 (ST0 40 ST1 4 ST2 10 cyl 80 hd 0 sec 1) fd0c: hard error reading fsbn 3360 of 3360-3363 (ST0 40 ST1 4 ST2 10 cyl 80 hd 0 sec 1) fd0c: hard error reading fsbn 3364 of 3364-3367 (ST0 40 ST1 4 ST2 10 cyl 80 hd 0 sec 5) fd0c: hard error reading fsbn 3360 of 3360-3363 (ST0 40 ST1 4 ST2 0 cyl 80 hd 0 sec 1) fd0c: hard error reading fsbn 3360 of 3360-3363 (ST0 40 ST1 4 ST2 0 cyl 80 hd 0 sec 1) fd0c: hard error reading fsbn 3364 of 3364-3367 (ST0 40 ST1 4 ST2 0 cyl 80 hd 0 sec 5) fd0c: hard error reading fsbn 3360 of 3360-3363 (ST0 40 ST1 4 ST2 0 cyl 80 hd 0 sec 1) fd0c: hard error reading fsbn 3360 of 3360-3363 (ST0 40 ST1 4 ST2 0 cyl 80 hd 0 sec 1) fd0c: hard error reading fsbn 3364 of 3364-3367 (ST0 40 ST1 4 ST2 0 cyl 80 hd 0 sec 5) - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 13:04:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22950 for freebsd-current-outgoing; Sat, 6 Feb 1999 13:04:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cx757770-a.fed1.sdca.home.com (cx757770-a.fed1.sdca.home.com [24.0.167.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22943 for ; Sat, 6 Feb 1999 13:04:20 -0800 (PST) (envelope-from daren@sefcik.cc) Received: from localhost (daren@localhost) by cx757770-a.fed1.sdca.home.com (8.9.1/8.9.1) with ESMTP id NAA04045; Sat, 6 Feb 1999 13:21:36 -0800 (PST) Date: Sat, 6 Feb 1999 13:21:35 -0800 (PST) From: Daren Sefcik X-Sender: daren@cx757770-a.fed1.sdca.home.com To: Mikhail Teterin cc: freebsd-current@FreeBSD.ORG Subject: Re: low level format--howto?? In-Reply-To: <199902062058.PAA11390@kot.ne.mediaone.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You are, probably, using a wrong device name. First, check the file > /var/run/dmesg.boot to find out exactly how the drive was found -- > what is the device number (da? something). >From dmesg.boot: (da0:adv0:0:1:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:adv0:0:1:0): MEDIUM ERROR asc:31,0 (da0:adv0:0:1:0): Medium format corrupted field replaceable unit: 9 (da0:adv0:0:1:0): fatal error, failed to attach to device (da0:adv0:0:1:0): lost device (da0:adv0:0:1:0): removing device entry It worked fine until I used newfs_msdos...then it was hosed. Daren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 13:06:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23166 for freebsd-current-outgoing; Sat, 6 Feb 1999 13:06:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23161 for ; Sat, 6 Feb 1999 13:06:07 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id QAA11438; Sat, 6 Feb 1999 16:05:22 -0500 (EST) From: Mikhail Teterin Message-Id: <199902062105.QAA11438@kot.ne.mediaone.net> Subject: Re: low level format--how?? In-Reply-To: from Daren Sefcik at "Feb 6, 1999 01:13:10 pm" To: daren@sefcik.cc (Daren Sefcik) Date: Sat, 6 Feb 1999 16:05:21 -0500 (EST) Cc: current@FreeBSD.ORG X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" =Is it possible to do a low level format of a scsi disk..I do not see a => =utility to do so. => => scsiformat(8) =rover >man scsiformat =No manual entry for scsiformat =rover > Khmm... My man-page is dated August 19, so it was in -current back then... I used this once on a 2.2.7 machine... Is there ``/sbin/scsiformat''? Or may be you have to use camcontrol now? I guess, scsi(8) and scsiformat(8) are now stale, and I should remove them... Someone more knowledgeable has to step in now. -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 13:12:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23488 for freebsd-current-outgoing; Sat, 6 Feb 1999 13:12:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cx757770-a.fed1.sdca.home.com (cx757770-a.fed1.sdca.home.com [24.0.167.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23483 for ; Sat, 6 Feb 1999 13:12:43 -0800 (PST) (envelope-from daren@sefcik.cc) Received: from sefcik.cc (rover.sefcik.cc [10.0.0.9]) by cx757770-a.fed1.sdca.home.com (8.9.1/8.9.1) with ESMTP id NAA04102; Sat, 6 Feb 1999 13:30:03 -0800 (PST) Message-ID: <36BCB4B8.C8728AAD@sefcik.cc> Date: Sat, 06 Feb 1999 13:31:36 -0800 From: Daren Sefcik X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: Mikhail Teterin CC: current@FreeBSD.ORG Subject: Re: low level format--how?? References: <199902062105.QAA11438@kot.ne.mediaone.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin wrote: > > Daren Sefcik once stated: > > => =Is it possible to do a low level format of a scsi disk..I do not see a > => =utility to do so. > => > => scsiformat(8) > > > > Is there ``/sbin/scsiformat''? Or may be you have to use camcontrol now? rover# camcontrol defects -f da0 camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed cam_lookup_pass: No such file or directory cam_lookup_pass: either the pass driver isn't in your kernel cam_lookup_pass: or da0 doesn't exist rover# camcontrol defects -f /dev/da0 camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed cam_lookup_pass: No such file or directory cam_lookup_pass: either the pass driver isn't in your kernel cam_lookup_pass: or da0 doesn't exist rover# arrgghh...do I need to add something to the kernel..?? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 13:37:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25354 for freebsd-current-outgoing; Sat, 6 Feb 1999 13:37:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley-184-92.res.iastate.edu (friley-184-92.res.iastate.edu [129.186.184.92]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25348 for ; Sat, 6 Feb 1999 13:37:35 -0800 (PST) (envelope-from mystify@friley-184-92.res.iastate.edu) Received: from friley-184-92.res.iastate.edu (localhost.res.iastate.edu [127.0.0.1]) by friley-184-92.res.iastate.edu (8.9.2/8.9.1) with ESMTP id PAA01705 for ; Sat, 6 Feb 1999 15:37:33 -0600 (CST) (envelope-from mystify@friley-184-92.res.iastate.edu) Message-Id: <199902062137.PAA01705@friley-184-92.res.iastate.edu> To: freebsd-current@FreeBSD.ORG Subject: Incorrect idle times Date: Sat, 06 Feb 1999 15:37:33 -0600 From: Patrick Hartling Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm getting some weird/wrong idle times with newly opened windows. For example, this is from a few minutes ago: > w 3:27PM up 13 mins, 6 users, load averages: 0.21, 0.18, 0.13 USER TTY FROM LOGIN@ IDLE WHAT [...] mystify p3 :0.0 3:17PM 1:00 ssh friley-185-206.res [...] mystify p5 :0.0 3:26PM 2:03 ssh -l patrick crunche mystify p6 :0.0 3:27PM 28:41 ssh -l patrick crunche These are in xterms that I just opened and in which I have done nothing (including type in a password thanks to ssh). This is on a freshly built 4.0-current system running XFree86 3.3.3.1. I saw this before rebuilding this afternoon but didn't pay attention to the conditions under which it happened. It's easily repeatable by simply opening a new xterm and not typing anything in it. If I close the xterm on ttyp6 by logging out and then open a new one, the idle time is at zero. If I close it by clicking on the window manager's close button, the idle time picks up where it left off. It's not a problem or even an annoyance. It's just a little strange since it seems as though idle times are being "recycled" in a way. -Patrick Patrick L. Hartling | Research Assistant, ICEMT mystify@friley-184-92.res.iastate.edu | Carver Lab - 0095E Black Engineering http://www.public.iastate.edu/~oz/ | http://www.icemt.iastate.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 14:07:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28379 for freebsd-current-outgoing; Sat, 6 Feb 1999 14:07:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28372 for ; Sat, 6 Feb 1999 14:07:31 -0800 (PST) (envelope-from mike@sentex.net) Received: from ospf-wat.sentex.net (ospf-wat.sentex.net [209.167.248.81]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id RAA02533 for ; Sat, 6 Feb 1999 17:07:25 -0500 (EST) From: mike@sentex.net (Mike Tancsa) To: current@FreeBSD.ORG Subject: Re: SKIP on 3.0 ? lkm vs kld = SOL ? Date: Sat, 06 Feb 1999 22:14:43 GMT Message-ID: <36bcbe77.527975678@mail.sentex.net> References: <36bba2d1.455362426@mail.sentex.net> In-Reply-To: X-Mailer: Forte Agent .99e/32.227 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 5 Feb 1999 23:56:04 -0500, in sentex.lists.freebsd.current you wrote: >#define quoting(Mike Tancsa) >// Are there any other options for VPN on the 3.0 branch ? SKIP wasnt/isnt >// the greatest, but I had decent luck with it on the 2.2 branch of things... > >Have you tried the ssh+ppp combo ? IIRC, there's a small example in >the file /etc/ppp/ppp.conf.sample. Thanks, I will have a look. I also looked at the IPSEC stuff, but it seems too much of a moving target still to place into production. Does anyone have any experiences with ssh and ppp ? Should I stick with 2.2.x machines and SKIP for now instead ? ---Mike Mike Tancsa (mdtancsa@sentex.net) Sentex Communications Corp, Waterloo, Ontario, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 14:34:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00959 for freebsd-current-outgoing; Sat, 6 Feb 1999 14:34:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles103.castles.com [208.214.165.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00954 for ; Sat, 6 Feb 1999 14:34:28 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA01262; Sat, 6 Feb 1999 14:30:13 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902062230.OAA01262@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "D. Rock" cc: current@FreeBSD.ORG, dillon@apollo.backplane.com Subject: Re: Seeing NFS saturation 'loop' when installworld'ing to NFS / and /usr In-reply-to: Your message of "Sat, 06 Feb 1999 02:01:36 +0100." <199902060101.CAA04062@vodix.aremorika> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 06 Feb 1999 14:30:13 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I tried to track down some of the problems doing a network snoop and noticed > something interesting: > NFSv3 seems to produce more than twice the packets during file write than NFSv2 > Is this true. There are many more getattr() calls with NFSv3 than with NFSv2. You may mean "ACCESS", not "GETATTR" here. > Since my NFS server exports one filesystem exclusively to one FreeBSD machine > (which is a little short on disk space), I also tried some tricks for speedup. > I just mounted one big file, vnconfig'd, newfs'd it and mounted it via UFS. > But unfortunately the machine panic'd really fast during filesystem activity. > My tests on this are 3-4 months old though, I will give it another try. Definitely, since we cache ACCESS RPC results now. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 16:06:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09983 for freebsd-current-outgoing; Sat, 6 Feb 1999 16:06:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from locus.dml.com (locus.dml.com [198.49.1.49] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09912 for ; Sat, 6 Feb 1999 16:06:21 -0800 (PST) (envelope-from rose@dml.com) Received: from localhost (rose@localhost) by locus.dml.com (8.8.5/8.8.5) with ESMTP id QAA18920 for ; Sat, 6 Feb 1999 16:06:17 -0800 (PST) Date: Sat, 6 Feb 1999 16:06:17 -0800 (PST) From: Stephen Rose To: current@FreeBSD.ORG Subject: Silo overflow messages with 3.0 Release Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I didn't get a response from the questions list, so let's try here. I've been getting my server ready to switch from FreeBSD 2.2.2 to 3.0 Release. Everything was going well until I tried to bring my kernel ppp link up to my isp. I get many silo overflow messages when there's any activity on the line. The connection doesn't seem very responsive either. This machine is a dual pentium pro. I've built an smp kernel which seems to work fine otherwise. I've arranged to build the new system on another disk so I can easily switch between the 2.2.2 system and the 3.0 system. Everything works fine with 2.2.2. I've seen many messages in the archive about silo overflows, but there doesn't seem to be a real solution in them. Is this ever likely to work or should I just wait for 3.1? Steve Rose To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 17:16:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17295 for freebsd-current-outgoing; Sat, 6 Feb 1999 17:16:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cx757770-a.fed1.sdca.home.com (cx757770-a.fed1.sdca.home.com [24.0.167.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17279; Sat, 6 Feb 1999 17:16:31 -0800 (PST) (envelope-from daren@sefcik.cc) Received: from rover.fed1.sdca.home.com (rover.sefcik.cc [10.0.0.9]) by cx757770-a.fed1.sdca.home.com (8.9.1/8.9.1) with SMTP id RAA04392; Sat, 6 Feb 1999 17:33:43 -0800 (PST) Date: Sat, 6 Feb 1999 17:35:03 -0800 (Pacific Standard Time) From: "Daren R. Sefcik" To: "David O'Brien" cc: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: low level format--how?? In-Reply-To: <19990206151129.A66591@relay.nuxi.com> Message-ID: X-X-Sender: daren@sefcik.cc MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks..I ended up just pulling my old Atari out of the closet and doing the format on it...that seemed to work and I am now up and running. I would still like to know how to do it under FreeBSD. Daren On Sat, 6 Feb 1999, David O'Brien wrote: > You will get more mileage by discussing this type of thing on > freebsd-scsi@freebsd.org > > > > > Is there ``/sbin/scsiformat''? Or may be you have to use camcontrol now? > > > > rover# camcontrol defects -f da0 > > camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed > > cam_lookup_pass: No such file or directory > > cam_lookup_pass: either the pass driver isn't in your kernel > > cam_lookup_pass: or da0 doesn't exist > > rover# camcontrol defects -f /dev/da0 > > camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed > > cam_lookup_pass: No such file or directory > > cam_lookup_pass: either the pass driver isn't in your kernel > > cam_lookup_pass: or da0 doesn't exist > > rover# > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 17:44:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19448 for freebsd-current-outgoing; Sat, 6 Feb 1999 17:44:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19432 for ; Sat, 6 Feb 1999 17:44:27 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id UAA28426 for ; Sat, 6 Feb 1999 20:44:27 -0500 (EST) Date: Sat, 6 Feb 1999 20:44:26 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@FreeBSD.ORG Subject: Re: msdosfs/vn trouble, doscmd "nicety", fd trouble In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The panic() I'm getting is not what appears to be the fault of vn(4). I can vnconfig, newfs, and mount_ufs a filesystem to my heart's content, even running my nice file-system-beater-upper (TM). The problem only occurs when I try to use msdosfs, and then occurs when: I chdir into the msdosfs, then when I try to chdir out. On the second chdir, I get the lovely panic. With INVARIANTS on, this is easily reproducible. Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 19:15:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25710 for freebsd-current-outgoing; Sat, 6 Feb 1999 19:15:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25603 for ; Sat, 6 Feb 1999 19:14:08 -0800 (PST) (envelope-from tcobb@staff.circle.net) From: tcobb@staff.circle.net Received: by freya.circle.net with Internet Mail Service (5.5.2232.9) id <1H4AT203>; Sat, 6 Feb 1999 22:13:08 -0500 Message-ID: To: freebsd-current@FreeBSD.ORG Cc: wpaul@ctr.columbia.edu Subject: 3c905B stops responding during ifconfig alias Date: Sat, 6 Feb 1999 22:13:06 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This happens in -current and -stable. Machine: CPU: Pentium II (quarter-micron) (350.80-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183fbff> real memory = 402653184 (393216K bytes) config> quit avail memory = 388808704 (379696K bytes ... xl0: <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 0x30 int a irq 9 on pci0.18.0 ... During an ifconfig xl0 alias, the xl0 interface drops packets. It does NOT generate errors (netstat -in). In fact, on several occasions I've seen it go completely unresponsive (not responding to arp requests) until kicked back to life by outbound packets. This does NOT happen on the: xl0: <3Com 3c905 Fast Etherlink XL 10/100BaseTX> rev 0x00 int a irq 10 on pci0.1 8.0 Here's a quick test program that I use: #!/usr/bin/perl # call this as just_alias.pl class_c num_ips $ip_base=$ARGV[0] || "209.95.67."; $num=$ARGV[1] || 250; for (1..$num) { print "aliasing for $ip_base".$_."\n"; system ("ifconfig xl0 alias $ip_base".$_." netmask 255.255.255.255"); # the sleep command allows us to see the problem more # clearly, though it does happen w/o the sleep here... sleep 1; } -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 20:15:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00254 for freebsd-current-outgoing; Sat, 6 Feb 1999 20:15:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA00237; Sat, 6 Feb 1999 20:15:52 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id VAA61198; Sat, 6 Feb 1999 21:14:01 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902070414.VAA61198@panzer.plutotech.com> Subject: Re: low level format--how?? In-Reply-To: from "Daren R. Sefcik" at "Feb 6, 1999 5:35: 3 pm" To: daren@sefcik.cc (Daren R. Sefcik) Date: Sat, 6 Feb 1999 21:14:01 -0700 (MST) Cc: obrien@NUXI.com, freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daren R. Sefcik wrote... > Thanks..I ended up just pulling my old Atari out of the closet and doing > the format on it...that seemed to work and I am now up and running. I > would still like to know how to do it under FreeBSD. First off, someone (can't tell who, because the attributions were deleted) doesn't have the pass driver in their kernel. You won't be able to use camcontrol for most things without it. Second, someone hasn't read the camcontrol man page. The -f option to the defects command is to specify the defect list format. To format a disk, you would do something like this: camcontrol cmd -n da -u 0 -t 3600 -v -c "4 0 0 0 0 0" The -t argument sets the timeout in seconds, you may need more time, depending on what kind of drive you have. > On Sat, 6 Feb 1999, David O'Brien wrote: > > > You will get more mileage by discussing this type of thing on > > freebsd-scsi@freebsd.org > > > > > > > > Is there ``/sbin/scsiformat''? Or may be you have to use camcontrol now? > > > > > > rover# camcontrol defects -f da0 > > > camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed > > > cam_lookup_pass: No such file or directory > > > cam_lookup_pass: either the pass driver isn't in your kernel > > > cam_lookup_pass: or da0 doesn't exist > > > rover# camcontrol defects -f /dev/da0 > > > camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed > > > cam_lookup_pass: No such file or directory > > > cam_lookup_pass: either the pass driver isn't in your kernel > > > cam_lookup_pass: or da0 doesn't exist > > > rover# > > > > -- > > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) > > Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 20:22:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01056 for freebsd-current-outgoing; Sat, 6 Feb 1999 20:22:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA01051 for ; Sat, 6 Feb 1999 20:22:46 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id VAA61234; Sat, 6 Feb 1999 21:21:15 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902070421.VAA61234@panzer.plutotech.com> Subject: Re: low level format--howto?? In-Reply-To: from Daren Sefcik at "Feb 6, 1999 1:21:35 pm" To: daren@sefcik.cc (Daren Sefcik) Date: Sat, 6 Feb 1999 21:21:15 -0700 (MST) Cc: mi@kot.ne.mediaone.net, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daren Sefcik wrote... > > You are, probably, using a wrong device name. First, check the file > > /var/run/dmesg.boot to find out exactly how the drive was found -- > > what is the device number (da? something). > > >From dmesg.boot: > > (da0:adv0:0:1:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (da0:adv0:0:1:0): MEDIUM ERROR asc:31,0 > (da0:adv0:0:1:0): Medium format corrupted field replaceable unit: 9 > (da0:adv0:0:1:0): fatal error, failed to attach to device > (da0:adv0:0:1:0): lost device > (da0:adv0:0:1:0): removing device entry > > > It worked fine until I used newfs_msdos...then it was hosed. Looks like the disk has lost its brain. If you've got the pass driver configured in your kernel, do the following: camcontrol devlist Find out which pass driver corresponds to your hard disk. Then, low-level format it like this: camcontrol cmd -n pass -u 0 -t 7200 -v -c "4 0 0 0 0 0" If the hard disk is on pass2 or something instead of pass0, just use -u 2 above. The -t argument sets the timeout in seconds. You may need to set it to something longer, depending on the disk. Generally, with errors like the one you have above, the disk can be brought back with a low-level format. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 20:25:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01229 for freebsd-current-outgoing; Sat, 6 Feb 1999 20:25:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA01193; Sat, 6 Feb 1999 20:24:57 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id VAA61254; Sat, 6 Feb 1999 21:23:32 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902070423.VAA61254@panzer.plutotech.com> Subject: Re: low level format--how?? In-Reply-To: <199902070414.VAA61198@panzer.plutotech.com> from "Kenneth D. Merry" at "Feb 6, 1999 9:14: 1 pm" To: ken@plutotech.com (Kenneth D. Merry) Date: Sat, 6 Feb 1999 21:23:32 -0700 (MST) Cc: daren@sefcik.cc, obrien@NUXI.com, freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth D. Merry wrote... > Daren R. Sefcik wrote... > > Thanks..I ended up just pulling my old Atari out of the closet and doing > > the format on it...that seemed to work and I am now up and running. I > > would still like to know how to do it under FreeBSD. > > > First off, someone (can't tell who, because the attributions were deleted) > doesn't have the pass driver in their kernel. > > You won't be able to use camcontrol for most things without it. Sorry to respond to myself, but as the error message below indicates, it is either because the pass driver isn't in the kernel, or because da0 doesn't exist. In your case, it's the latter. That's because the da driver couldn't attach because of the fatal error it got back from the read capacity command. > > On Sat, 6 Feb 1999, David O'Brien wrote: > > > > > You will get more mileage by discussing this type of thing on > > > freebsd-scsi@freebsd.org > > > > > > > > > > > Is there ``/sbin/scsiformat''? Or may be you have to use camcontrol now? > > > > > > > > rover# camcontrol defects -f da0 > > > > camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed > > > > cam_lookup_pass: No such file or directory > > > > cam_lookup_pass: either the pass driver isn't in your kernel > > > > cam_lookup_pass: or da0 doesn't exist > > > > rover# camcontrol defects -f /dev/da0 > > > > camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed > > > > cam_lookup_pass: No such file or directory > > > > cam_lookup_pass: either the pass driver isn't in your kernel > > > > cam_lookup_pass: or da0 doesn't exist > > > > rover# > > > > > > -- > > > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) > > > Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 20:29:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01945 for freebsd-current-outgoing; Sat, 6 Feb 1999 20:29:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA01564 for ; Sat, 6 Feb 1999 20:26:55 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id XAA12491; Sat, 6 Feb 1999 23:26:08 -0500 (EST) From: Mikhail Teterin Message-Id: <199902070426.XAA12491@kot.ne.mediaone.net> Subject: Re: low level format--how?? In-Reply-To: <199902070414.VAA61198@panzer.plutotech.com> from "Kenneth D. Merry" at "Feb 6, 1999 09:14:01 pm" To: ken@plutotech.com (Kenneth D. Merry) Date: Sat, 6 Feb 1999 23:26:08 -0500 (EST) Cc: current@FreeBSD.ORG X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05152 for freebsd-current-outgoing; Sat, 6 Feb 1999 20:58:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04870 for ; Sat, 6 Feb 1999 20:54:49 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id VAA61394; Sat, 6 Feb 1999 21:54:38 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902070454.VAA61394@panzer.plutotech.com> Subject: Re: low level format--how?? In-Reply-To: <199902070426.XAA12491@kot.ne.mediaone.net> from Mikhail Teterin at "Feb 6, 1999 11:26: 8 pm" To: mi@kot.ne.mediaone.net (Mikhail Teterin) Date: Sat, 6 Feb 1999 21:54:38 -0700 (MST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin wrote... > Kenneth D. Merry once stated: > > =To format a disk, you would do something like this: > = > =camcontrol cmd -n da -u 0 -t 3600 -v -c "4 0 0 0 0 0" > > Yep, this similar to what the scsiformat(8) script was doing using > the scsi(8) command. > > IMHO, it is very bad, the scsi(8) did not survive the switch to CAM as > a backward-compatability interface... Or, at least, the nice scsiformat > should be re-introduced, using the camcontrol as a back-end. I've been planning on doing a 'camcontrol format' subcommand. That's why the scsiformat(8) utility hasn't reappeared. At some point, I'll probably also do a port of Joerg Schilling's sformat utility. It has far more functionality than will probably ever go into camcontrol. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 21:10:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06123 for freebsd-current-outgoing; Sat, 6 Feb 1999 21:10:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06117 for ; Sat, 6 Feb 1999 21:10:17 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.2) with ESMTP id VAA21445; Sat, 6 Feb 1999 21:09:08 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: wwoods@cybcon.com cc: Julian Elischer , FreeBSD Current , Poul-Henning Kamp Subject: Re: Floppy Tape Driver..... In-reply-to: Your message of "Sat, 06 Feb 1999 11:49:08 PST." Date: Sat, 06 Feb 1999 21:09:08 -0800 Message-ID: <21441.918364148@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So, basically I am screwed? Not at all - get busy on maintaining this thing and ft is all yours again. How do you think stuff like this happens around here? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 21:16:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06695 for freebsd-current-outgoing; Sat, 6 Feb 1999 21:16:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06690 for ; Sat, 6 Feb 1999 21:16:39 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id AAA16576; Sun, 7 Feb 1999 00:16:23 -0500 (EST) Message-ID: <19990207001623.A14051@netmonger.net> Date: Sun, 7 Feb 1999 00:16:23 -0500 From: Christopher Masto To: current@FreeBSD.ORG Subject: Re: Floppy Tape Driver..... References: <87718.918332733@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <87718.918332733@critter.freebsd.dk>; from Poul-Henning Kamp on Sat, Feb 06, 1999 at 09:25:33PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have an Exabyte Eagle TR-3 drive, and I had a look at the floppy tape situation a while back. The driver is.. well.. inadequate. It makes a lot of assumptions that are quite a few years incorrect. But they're probably still needed if someone has those old drives. New drives come in all sorts of configurations and can be queried for the correct parameters, among other differences. Also, it's weirdly split into kernel and user-level parts, and makes no attempt whatsoever to pretend to be a "proper" Unix tape. I was going to fix all of this a while back, and I still have the pile of documentation on how floppy tape works. I think I planned to write a standard QIC header at the beginning of the tape and fake up SCSI-like behavior (end of file marks, etc.). Hackers have bizzare motivations sometimes, and my motivation for this project was to back up my machine so I could install it anew. Unfortunately, it's now been so long that I really have to reinstall _before_ I'd want to start on such a thing. And I'm not sure I care anymore. I certainly don't have the free time for some time to come. -- Christopher Masto Director of Operations NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net "Good tools allow users to do stupid things." -- Clay Shirky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 21:23:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA07104 for freebsd-current-outgoing; Sat, 6 Feb 1999 21:23:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA07099 for ; Sat, 6 Feb 1999 21:22:58 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (usr1-3.cybcon.com [205.147.76.4]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id VAA05526; Sat, 6 Feb 1999 21:17:47 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <21441.918364148@zippy.cdrom.com> Date: Sat, 06 Feb 1999 21:17:18 -0800 (PST) Reply-To: wwoods@cybcon.com From: William Woods To: "Jordan K. Hubbard" Subject: Re: Floppy Tape Driver..... Cc: Poul-Henning Kamp Cc: Poul-Henning Kamp , FreeBSD Current , Julian Elischer Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I need to learn a little about programming first, so where do you reccomend I begin learning? On 07-Feb-99 Jordan K. Hubbard wrote: >> So, basically I am screwed? > > Not at all - get busy on maintaining this thing and ft is all yours > again. How do you think stuff like this happens around here? > > - Jordan ---------------------------------- E-Mail: William Woods Date: 06-Feb-99 / Time: 21:16:31 FreeBSD 4.0 -Current ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 21:37:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA08427 for freebsd-current-outgoing; Sat, 6 Feb 1999 21:37:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebase.sitaranetworks.com (freebase.sitaranetworks.com [199.103.141.181]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA08422 for ; Sat, 6 Feb 1999 21:36:59 -0800 (PST) (envelope-from john@loverso.southborough.ma.us) Received: from loverso.southborough.ma.us (loverso.sitaranetworks.com [199.103.141.107]) by freebase.sitaranetworks.com (8.8.8/8.8.8) with ESMTP id AAA29562; Sun, 7 Feb 1999 00:36:56 -0500 (EST) Received: from loverso.southborough.ma.us (localhost [127.0.0.1]) by loverso.southborough.ma.us (8.8.8/8.6.9) with ESMTP id AAA16159; Sun, 7 Feb 1999 00:36:19 -0500 (EST) Message-Id: <199902070536.AAA16159@loverso.southborough.ma.us> To: wwoods@cybcon.com Cc: FreeBSD Current Subject: Re: Floppy Tape Driver..... In-reply-to: Message from William Woods . X-Face: "UZ!}1W2N?eJdN(`1%|/OOPqJ).Idk?UyvWw'W-%`Gto8^IkEm>.g1O$[.;~}8E=Ire0|lO .o>:NlJS1@vO9bVmswRoq3j DdX9YGSeJ5a(mfX[1u>Z63G5_^+'8LVqjqvn X-Url: http://surf.to/loverso Date: Sun, 07 Feb 1999 00:36:18 -0500 From: John Robert LoVerso Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, I need to learn a little about programming first, so where do you > reccomend I begin learning? > E-Mail: William Woods > FreeBSD 4.0 -Current If you don't know about programming, then you just shouldn't be running -current. Step back to 2.2.8R and enjoy the Floppy Tape support there. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 22:07:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10896 for freebsd-current-outgoing; Sat, 6 Feb 1999 22:07:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10888 for ; Sat, 6 Feb 1999 22:07:25 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.57.47]) by smtp05.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAAC3C for ; Fri, 5 Feb 1999 20:30:25 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 05 Feb 1999 20:39:11 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Current Subject: Netscape, again Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, found another reproducable coredumper: whenever I click a mailto: HREF it inadvertly dumps core. Now, am I wrong or did Netscape code their mailer in Java? (btw, Netscape 4.5 Communicator) --- Jeroen Ruigrok van der Werven It's a Dance of Energy, asmodai(at)wxs.nl when the Mind goes Binary... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 22:07:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11146 for freebsd-current-outgoing; Sat, 6 Feb 1999 22:07:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11141 for ; Sat, 6 Feb 1999 22:07:36 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id BAA12328 for ; Sun, 7 Feb 1999 01:07:35 -0500 (EST) Date: Sun, 7 Feb 1999 01:07:35 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@FreeBSD.ORG Subject: msdosfs is dead, Jim. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How am I supposed to find the maintainer of a certain part of the kernel, anyway? The basic problem is that msdosfs panic()s quite easily with a "zone not free" error (INVARIANTS is /ON/ in the kernel), when I attempt to do a rw mount of a FAT16. I don't know what else it affects, but it's easily and consistently reproducible. This is not in relation to vn(4), which it was originally tested with, as vn(4) works flawlessly. Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 22:21:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA12193 for freebsd-current-outgoing; Sat, 6 Feb 1999 22:21:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA12188 for ; Sat, 6 Feb 1999 22:21:51 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 16360 invoked from network); 7 Feb 1999 06:15:09 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 7 Feb 1999 06:15:09 -0000 Received: (from root@localhost) by y.dyson.net (8.9.1/8.9.1) id BAA00269 for current@freebsd.org; Sun, 7 Feb 1999 01:15:07 -0500 (EST) Message-Id: <199902070615.BAA00269@y.dyson.net> Subject: Significant page coloring improvement To: current@FreeBSD.ORG Date: Sun, 7 Feb 1999 01:15:07 -0500 (EST) From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM918368107-256-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ELM918368107-256-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit When reviewing the VM code regarding another issue (another significant VM contributor had found an interesting anomoly), I noticed that the coloring wasn't as complete as it should be. Attached is a patch that appears to make a reasonable improvement in performance, when using both my slightly more advanced VM kernel, and also the stuff in -current. I seem to see a fork() only performance improvement of about 10% on a 2 processor SMP PPro, using lmbench. On vfork (which isn't completely implemented on a PPro, but is still faster than fork), the improvement appears to be about 5%. Of course, any page coloring improvement is dependent on alot of factors, but the missing object coloring handling is a problem... -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. --ELM918368107-256-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=vm.diff Content-Description: vm.diff Content-Transfer-Encoding: 7bit Index: vm/vm_object.c =================================================================== RCS file: /local/home/ncvs/src/sys/vm/vm_object.c,v retrieving revision 1.144 diff -r1.144 vm_object.c 215a216 > kmem_object->pg_color = (kernel_object->pg_color + PQ_L2_SIZE/4) & PQ_L2_MASK; 945a947 > result->pg_color = (source->pg_color + OFF_TO_IDX(*offset)) & PQ_L2_MASK; --ELM918368107-256-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 6 23:44:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA18683 for freebsd-current-outgoing; Sat, 6 Feb 1999 23:44:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peacock.tci.com (coral.tci.com [198.178.8.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA18669 for ; Sat, 6 Feb 1999 23:43:59 -0800 (PST) (envelope-from chris@tci.com) Received: from oreo.tci.com (co-chris-pc01.tci.com [172.18.27.65]) by peacock.tci.com (8.9.0/8.9.0) with ESMTP id AAA19716; Sun, 7 Feb 1999 00:43:51 -0700 (MST) Received: from tci.com (localhost [127.0.0.1]) by oreo.tci.com (8.9.1b+Sun/8.9.1) with ESMTP id AAA22779; Sun, 7 Feb 1999 00:43:43 -0700 (MST) Message-ID: <36BD442E.3140A32F@tci.com> Date: Sun, 07 Feb 1999 00:43:42 -0700 From: Chris Tubutis Organization: Tele-Communications, Inc. X-Mailer: Mozilla 4.5 [en] (X11; U; SunOS 5.7 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: Jeroen Ruigrok/Asmodai CC: FreeBSD Current Subject: Re: Netscape, again References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok/Asmodai wrote: > > OK, > > found another reproducable coredumper: > > whenever I click a mailto: HREF it inadvertly dumps core. Does it truly dump core, or does it merely go away? It's a known problem with Communicrasher 4.5 on UNIX platforms that trying to use any of the mail stuff (including mailto links in web pages) without first starting up the mail client will cause it to generate a Bus Error and and rather abruptly die. (Check the "Communicator for UNIX News group on the secnews.netscape.com News server.) The simple workaround is to first open up the mail client thing, *then* try to use the web browser part. ct To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message