From owner-freebsd-hackers Sun Nov 14 6:26:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 6855014CFB; Sun, 14 Nov 1999 06:26:33 -0800 (PST) (envelope-from mb@imp.ch) Received: from mephisto.imp.ch (mb@mephisto.imp.ch [157.161.1.22]) by mail.imp.ch (8.9.3/8.9.3) with ESMTP id PAA01575; Sun, 14 Nov 1999 15:26:24 +0100 (MET) Received: from localhost (mb@localhost) by mephisto.imp.ch (8.9.3/8.9.3) with ESMTP id PAA18125; Sun, 14 Nov 1999 15:26:17 +0100 (MEZ) Date: Sun, 14 Nov 1999 15:26:16 +0100 From: Martin Blapp To: current@freebsd.org Cc: hackers@freebsd.org Subject: Call for objections Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi everbody, I had a concept to solve some bad implemented NFS part: The client unmount notification of the NFS server. There seems to be different understanding if the programm rpc.umntall should be started at shutdown, startup or both. Can you please vote for or against these three possibilitys ? Someone also had the idea to use a counter 'n' for trying only 'n' times to send a unmount request to the server and then to delete the entry. If we start rpc.umntall at startup-time as the RFC 1813 proposes, we have to save/store all nfs mounts in a list. This may also be some point to discuss. To get an idea you'll have to read the following URL's. my announcement: ---------------- http://docs.FreeBSD.org/cgi/getmsg.cgi?fetch=243597+0+archive/1999/freebsd-hackers/19991114.freebsd-hackers the patches/programm itself: ---------------------------- http://www.attic.ch/patches/rpc.umntall/ this PR: -------- http://www.freebsd.org/cgi/query-pr.cgi?pr=14709 Thank you very much Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 14 7:15:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from massive.geek.edu (massive.geek.edu [216.73.11.10]) by hub.freebsd.org (Postfix) with ESMTP id 3B8B214CFF for ; Sun, 14 Nov 1999 07:15:33 -0800 (PST) (envelope-from jontow@massive.geek.edu) Received: (from jontow@localhost) by massive.geek.edu (8.9.3/8.9.2) id KAA22673; Sun, 14 Nov 1999 10:16:51 -0500 (EST) (envelope-from jontow) Date: Sun, 14 Nov 1999 10:16:51 -0500 From: Jonathan Towne To: Thierry Herbelot Cc: freebsd-hackers@freebsd.org Subject: Re: Thinkpad 750 Message-ID: <19991114101650.A22661@massve.geek.edu> References: <19991113210357.A20018@massve.geek.edu> <382E6BA2.83A1BF48@cybercable.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <382E6BA2.83A1BF48@cybercable.fr>; from Thierry Herbelot on Sun, Nov 14, 1999 at 08:58:26AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There was a time where you had to have at least 12 megs of RAM to > install FreeBSD. You may check the errata and release notes for 3.3 to > find out if you can install with only 8 megs. Not so, that was for an FTP installation over PPP.. that, i'm quite sure, is not the problem.. it doesn't get to a point where i could even begin to install, sysinstall isn't fully started. -- Jonathan Towne jontow@massive.geek.edu/wrongway@slic.com Systems Administrator http://massive.geek.edu/ -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GU d- s: a--- C+++ UB++++ P L- E--- W--- N++ o K w--- O-- M V- PS PE Y-- PGP- t+ 5 X+ R+ tv- b+ DI+ D++ G e- h-- r-- y ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 14 16:45:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 23B0715309 for ; Sun, 14 Nov 1999 16:45:29 -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.3/8.9.3) with ESMTP id QAA02839; Sun, 14 Nov 1999 16:45:28 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id QAA18717; Sun, 14 Nov 1999 16:45:27 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sun, 14 Nov 1999 16:45:27 -0800 (PST) Message-Id: <199911150045.QAA18717@vashon.polstra.com> To: nmh@dialup.nacamar.de Subject: Re: Missing symbols in LIBC ??? In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Nils M Holm wrote: > > Hello! > > I am currently porting my compiler to the release 3.3. My RT lib depends > on /usr/lib/libc.a. When attempting to link a program, I get messages about > unresolved externals (it DOES work on release 2.x). > > I have seen that the C compiler no longer generates underscores on > symbols by default and consequently, '_printf' in /usr/lib/libc.a has > become simply 'printf'. There seem to exist kind of 'compatibility > entries' for some functions, though. > > However, (at least) the symbols _creat, _lseek, and _memmove are not > defined in /usr/lib/libc.a. (creat, lseek, and memove are defined.) > > Is this a bug or a feature? Will underscores vanish totally in the > future? Do I have to create a workaround for the 3.x branch?? Yes, the underscores are gone permanently because we switched from a.out to ELF as the object file format. You can test for it at compile time with #ifdef __ELF__. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 14 17:13:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tamserver.jfk1.gctr.net (tamserver.jfk1.gctr.net [206.41.7.82]) by hub.freebsd.org (Postfix) with ESMTP id DBA4614C99 for ; Sun, 14 Nov 1999 17:13:52 -0800 (PST) (envelope-from sec@finary.com) Received: from localhost (sec@localhost) by tamserver.jfk1.gctr.net (8.9.3/8.9.2) with ESMTP id UAA25683; Sun, 14 Nov 1999 20:23:12 -0500 (EST) (envelope-from sec@finary.com) Date: Sun, 14 Nov 1999 20:23:11 -0500 (EST) From: sec X-Sender: sec@tamserver.jfk1.gctr.net To: Jonathan Towne Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Thinkpad 750 In-Reply-To: <19991113210357.A20018@massve.geek.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG yep i have an 600E 350Mhz, 128m or RAM. The same thing happens as it hits 'Probing devices' The machine just hangs and becomes totally un-responsive. Heck can't even turn the machine off by hitting the power off button, have to take out the Battery, have tried this with 2.2.8-REL, 3.1-REL et cetera. On Sat, 13 Nov 1999, Jonathan Towne wrote: > I've got a Thinkpad 750, 2 pc card slots, no cdrom, only a mere > 486SL/33 CPU, and 8meg of RAM, and i'm trying to install a copy > of 3.3-RELEASE on it to replace win3.11. Since the thinkpad > uses an odd keyboard of some sort, i give syscons the 0x2 flag, > which fixed the keyboard one time (the only time i got it to > boot correctly). Anyways, i've tried the standard installation > floppies, and the pccard floppies, neither would get past the > "Probing devices, please wait (...)" dialog, it just hangs there, > and will not accept any keyboard commands or anything like that. > This problem previously happened to me on a set of installation > floppies that didn't have FPU emulation in the kernel on my > 486sx/25, but, 3.3-RELEASE is supposed to have it, so, I'm sure > that can't be the problem, any answers would be greatly > appreciated.. :) > > -- > Jonathan Towne jontow@massive.geek.edu/wrongway@slic.com > Systems Administrator http://massive.geek.edu/ > > -----BEGIN GEEK CODE BLOCK----- > Version: 3.1 > GU d- s: a--- C+++ UB++++ P L- E--- W--- N++ o K w--- > O-- M V- PS PE Y-- PGP- t+ 5 X+ R+ tv- b+ DI+ D++ > G e- h-- r-- y > ------END GEEK CODE BLOCK------ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 14 17:17: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 1DEDA14C99 for ; Sun, 14 Nov 1999 17:17:00 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id SAA12713; Sun, 14 Nov 1999 18:16:52 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id SAA26166; Sun, 14 Nov 1999 18:16:51 -0700 Date: Sun, 14 Nov 1999 18:16:51 -0700 Message-Id: <199911150116.SAA26166@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: sec Cc: Jonathan Towne , freebsd-hackers@FreeBSD.ORG Subject: Re: Thinkpad 750 In-Reply-To: References: <19991113210357.A20018@massve.geek.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > yep i have an 600E 350Mhz, 128m or RAM. The same thing happens as it hits > 'Probing devices' The machine just hangs and becomes totally > un-responsive. Go back and read the mobile mailing lists for your 600E fixes. It's discussed greatly there, and is in no way related to the 750 problems. The 750 problems are probably exactly *opposite* related, in that his box doesn't have enough memory. :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 14 19:13:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id 402F614D50 for ; Sun, 14 Nov 1999 19:13:45 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.3/8.9.1) id TAA61507 for hackers@freebsd.org; Sun, 14 Nov 1999 19:14:12 -0800 (PST) (envelope-from ulf) Date: Sun, 14 Nov 1999 19:14:12 -0800 From: Ulf Zimmermann To: hackers@freebsd.org Subject: Support for USB floppies like Y-E Data FlashBuster-u ? Message-ID: <19991114191412.B46290@PacHell.TelcoSucks.org> Reply-To: ulf@Alameda.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.2-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone working on such support yet ? This drive came with the Sony Vaio Z505R. -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 15 8: 3:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id A6DF51509E for ; Mon, 15 Nov 1999 08:03:12 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id LAA11327 for ; Mon, 15 Nov 1999 11:03:06 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id LAA13052 for ; Mon, 15 Nov 1999 11:03:05 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id LAA04493 for freebsd-hackers@freebsd.org; Mon, 15 Nov 1999 11:03:04 -0500 (EST) Date: Mon, 15 Nov 1999 11:03:04 -0500 (EST) From: Thomas David Rivers Message-Id: <199911151603.LAA04493@lakes.dignus.com> To: freebsd-hackers@freebsd.org Subject: Kernel debug assistance? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to track down a problem in 3.3-RELEASE (which I _think_ might be a linux emu bug that's crashing the kernel.) Anyway - I thought I might ask here for some kernel debugging assistance... I've got a debuggable kernel, with DDB. When the panic occurs (which I can readily reproduce) I drop down into DDB... Which is great - right? But - IP is 0x0 (or, sometimes 0x80000000) - so the trace command in DDB (to show the stack traceback) doesn't seem to work - all I get is the Trap 12 message. Does anyone have any sage words of advice on how to proceed with tracking this down? At least some neat trick for determining where the bad branch is taken? - Thanks - - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 15 10:56:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id 8F0CD15011 for ; Mon, 15 Nov 1999 10:56:10 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id FAA21300; Tue, 16 Nov 1999 05:25:53 +1030 (CST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991115135516.21972@mojave.sitaranetworks.com> Date: Mon, 15 Nov 1999 13:55:16 -0500 From: Greg Lehey To: Clinton Xavier Berni , freebsd-hackers@FreeBSD.ORG Subject: Re: upcall Reply-To: Greg Lehey References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from Clinton Xavier Berni on Sat, Nov 13, 1999 at 04:14:02PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 13 November 1999 at 16:14:02 -0500, Clinton Xavier Berni wrote: > > Hello, > > How do I access a user level data structure from the kernel. In general, you don't, unless the user wants you to. > Are there any Upcalls that I could use? No. What are you trying to do? The only way to get data is to have it passed. You can then use copyin() to move it to the kernel. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 15 11:31:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 8B4DE14D6C for ; Mon, 15 Nov 1999 11:31:54 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (loot.cs.rpi.edu [128.213.16.22]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id OAA80206 for ; Mon, 15 Nov 1999 14:31:54 -0500 (EST) Message-Id: <199911151931.OAA80206@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: 3.3-STABLE panic Date: Mon, 15 Nov 1999 14:24:43 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I received the following panic() on our primary user fileserver. Note that this is the first panic we have received in well over 80 days. Below is a backtrace obtained from a kernel with debugging symbols: IdlePTD 2977792 initial pcb at 264d38 panicstr: softdep_lock: locking against myself panic messages: --- panic: allocdirect_check: old 0 != new 1225576 || lbn 13 >= 12 syncing disks... panic: softdep_lock: locking against myself dumping to dev 30001, offset 851968 dump 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 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=260) at ../../kern/kern_shutdown.c:285 285 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=260) at ../../kern/kern_shutdown.c:285 #1 0xc014f429 in panic (fmt=0xc023bd04 "softdep_lock: locking against myself") at ../../kern/kern_shutdown.c:446 #2 0xc01dc3bd in acquire_lock (lk=0xc0258214) at ../../ufs/ffs/ffs_softdep.c:266 #3 0xc01dfd71 in softdep_update_inodeblock (ip=0xc0d9ed00, bp=0xc2befa00, waitfor=0) at ../../ufs/ffs/ffs_softdep.c:3447 #4 0xc01db40c in ffs_update (vp=0xc6700f40, waitfor=0) at ../../ufs/ffs/ffs_inode.c:105 #5 0xc01e2e2c in ffs_sync (mp=0xc0cedc00, waitfor=2, cred=0xc0690300, p=0xc027ce0c) at ../../ufs/ffs/ffs_vfsops.c:1001 #6 0xc0175ff7 in sync (p=0xc027ce0c, uap=0x0) at ../../kern/vfs_syscalls.c:549 #7 0xc014efd1 in boot (howto=256) at ../../kern/kern_shutdown.c:203 #8 0xc014f429 in panic ( fmt=0xc023c124 "allocdirect_check: old %d != new %d || lbn %ld >= %d") at ../../kern/kern_shutdown.c:446 #9 0xc01dd373 in allocdirect_merge (adphead=0xc10761c4, newadp=0xc10b5980, oldadp=0xc10bdb00) at ../../ufs/ffs/ffs_softdep.c:1238 #10 0xc01dff45 in merge_inode_lists (inodedep=0xc1076180) at ../../ufs/ffs/ffs_softdep.c:3523 #11 0xc01dfe03 in softdep_update_inodeblock (ip=0xc0e31100, bp=0xc2c562b8, waitfor=1) at ../../ufs/ffs/ffs_softdep.c:3471 #12 0xc01db40c in ffs_update (vp=0xc68ebd80, waitfor=1) at ../../ufs/ffs/ffs_inode.c:105 #13 0xc01e40cb in ffs_write (ap=0xc6708c7c) at ../../ufs/ufs/ufs_readwrite.c:508 #14 0xc01a8775 in nfsrv_write (nfsd=0xc1017100, slp=0xc0cf7300, procp=0xc66beb20, mrq=0xc6708e34) at vnode_if.h:331 #15 0xc01be8a6 in nfssvc_nfsd (nsd=0xc6708e94, argp=0x8071f04 "", p=0xc66beb20) at ../../nfs/nfs_syscalls.c:656 #16 0xc01be1c1 in nfssvc (p=0xc66beb20, uap=0xc6708f94) at ../../nfs/nfs_syscalls.c:342 #17 0xc0213c0b in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 8, tf_esi = 0, tf_ebp = -1077944892, tf_isp = -965701660, tf_ebx = 0, tf_edx = -1077945288, tf_ecx = 0, tf_eax = 155, tf_trapno = 12, tf_err = 2, tf_eip = 134518972, tf_cs = 31, tf_eflags = 642, tf_esp = -1077945280, tf_ss = 39}) at ../../i386/i386/trap.c:1100 #18 0xc0208e7c in Xint0x80_syscall () #19 0x80480e9 in ?? () -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 15 12:19:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pak2.texar.com (pak2.texar.com [216.208.160.130]) by hub.freebsd.org (Postfix) with ESMTP id 5048B152DC for ; Mon, 15 Nov 1999 12:19:38 -0800 (PST) (envelope-from dseg@pak2.texar.com) Received: from localhost (dseg@localhost) by pak2.texar.com (8.9.2/8.8.3) with ESMTP id PAA48567 for ; Mon, 15 Nov 1999 15:19:38 -0500 (EST) Date: Mon, 15 Nov 1999 15:19:38 -0500 (EST) From: Dan Seguin To: FreeBSD Hackers Subject: Vnodes and Pathnames Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Gurus, Is there any way of getting filepath information from a vnode? What I'm looking for is pathname info for VDIR and VREG types, sort of a reverse namei(). Thanks! -------------------------------------------------------------------------------- Dan Seguin Texar Software, Corporation. The trouble with doing something right the first time is that nobody appreciates how difficult it was. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 15 12:33:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 2C84A14C04 for ; Mon, 15 Nov 1999 12:33:48 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id MAA25364; Mon, 15 Nov 1999 12:59:28 -0800 (PST) Date: Mon, 15 Nov 1999 12:59:28 -0800 (PST) From: Alfred Perlstein To: Dan Seguin Cc: FreeBSD Hackers Subject: Re: Vnodes and Pathnames In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 15 Nov 1999, Dan Seguin wrote: > > > Hello Gurus, > > > Is there any way of getting filepath information from a vnode? What I'm > looking for is pathname info for VDIR and VREG types, sort of a reverse > namei(). It's really not possible since a file may have mutiple parent directories. There were some discussions on the lists in the last 30 days that went into greater detail. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 15 12:38:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 76228150F0 for ; Mon, 15 Nov 1999 12:38:20 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id MAA14432; Mon, 15 Nov 1999 12:38:11 -0800 (PST) Date: Mon, 15 Nov 1999 12:38:10 -0800 (PST) From: Julian Elischer To: Dan Seguin Cc: FreeBSD Hackers Subject: Re: Vnodes and Pathnames In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG you can for VDIR as the getcwd call does so, but not for VREG becasue you don't know the directory entry that you used to get to it. (You could look in the name cache using a reverse lookup, but I don't know that you are guaranteed of success.) PHK may have more to say on this topic. On Mon, 15 Nov 1999, Dan Seguin wrote: > > > Hello Gurus, > > > Is there any way of getting filepath information from a vnode? What I'm > looking for is pathname info for VDIR and VREG types, sort of a reverse > namei(). > > Thanks! > > > > -------------------------------------------------------------------------------- > Dan Seguin Texar Software, Corporation. > > The trouble with doing something right the first time is that nobody > appreciates how difficult it was. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 15 12:47:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pak2.texar.com (pak2.texar.com [216.208.160.130]) by hub.freebsd.org (Postfix) with ESMTP id 16818150F0 for ; Mon, 15 Nov 1999 12:47:26 -0800 (PST) (envelope-from dseg@pak2.texar.com) Received: from localhost (dseg@localhost) by pak2.texar.com (8.9.2/8.8.3) with ESMTP id PAA49706; Mon, 15 Nov 1999 15:47:25 -0500 (EST) Date: Mon, 15 Nov 1999 15:47:25 -0500 (EST) From: Dan Seguin To: Julian Elischer Cc: FreeBSD Hackers Subject: Re: Vnodes and Pathnames In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for your response. Both you and Alfred have answered my questions. All I really needed was VDIR, since I can get to the filename from the process-context call to open. I thought I'd ask about VREG anyway. My search of the archives was fragged and I didn't find anything (I did upon restarting my browser. grrrr). Dan On Mon, 15 Nov 1999, Julian Elischer wrote: > you can for VDIR as the getcwd call does so, but not for VREG becasue you > don't know the directory entry that you used to get to it. > (You could look in the name cache using a reverse lookup, but I don't know > that you are guaranteed of success.) PHK may have more to say on this > topic. > > > On Mon, 15 Nov 1999, Dan Seguin wrote: > > > > > > > Hello Gurus, > > > > > > Is there any way of getting filepath information from a vnode? What I'm > > looking for is pathname info for VDIR and VREG types, sort of a reverse > > namei(). > > > > Thanks! > > -------------------------------------------------------------------------------- Dan Seguin Texar Software, Corporation. The trouble with doing something right the first time is that nobody appreciates how difficult it was. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 15 13:38:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 3AAC914BD5 for ; Mon, 15 Nov 1999 13:38:24 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id QAA00299 for ; Mon, 15 Nov 1999 16:38:23 -0500 (EST) Date: Mon, 15 Nov 1999 15:25:54 -0500 (EST) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: Set the baud rate on remote debugging Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have set up a remote debugging environment. But I think default 9600 bps is slow. I can use "set remotebaud 19200" on the debugging machine side. How can I set the baud rate on the target machine that is running the debugged kernel? (I press CTRL+ESC+ALT to drop to DDB mode and find no command to set the baud rate). Any help is appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 15 14:14:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 6C01414BC2 for ; Mon, 15 Nov 1999 14:14:09 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA58051; Mon, 15 Nov 1999 15:13:53 -0700 (MST) (envelope-from ken) Message-Id: <199911152213.PAA58051@panzer.kdm.org> Subject: Re: Set the baud rate on remote debugging In-Reply-To: from Zhihui Zhang at "Nov 15, 1999 03:25:54 pm" To: zzhang@cs.binghamton.edu (Zhihui Zhang) Date: Mon, 15 Nov 1999 15:13:53 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Zhihui Zhang wrote... > > I have set up a remote debugging environment. But I think default 9600 > bps is slow. I can use "set remotebaud 19200" on the debugging machine > side. How can I set the baud rate on the target machine that is running > the debugged kernel? (I press CTRL+ESC+ALT to drop to DDB mode and find > no command to set the baud rate). > > Any help is appreciated. Use the CONSPEED option in the kernel config file on the target machine. e.g.: options CONSPEED=115200 Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 15 14:33:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id 2BC6614A2A for ; Mon, 15 Nov 1999 14:33:06 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id JAA21488; Tue, 16 Nov 1999 09:02:50 +1030 (CST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991115173216.19303@mojave.sitaranetworks.com> Date: Mon, 15 Nov 1999 17:32:16 -0500 From: Greg Lehey To: Thomas David Rivers , freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel debug assistance? Reply-To: Greg Lehey References: <199911151603.LAA04493@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <199911151603.LAA04493@lakes.dignus.com>; from Thomas David Rivers on Mon, Nov 15, 1999 at 11:03:04AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 15 November 1999 at 11:03:04 -0500, Thomas David Rivers wrote: > > I'm trying to track down a problem in 3.3-RELEASE > (which I _think_ might be a linux emu bug that's > crashing the kernel.) > > Anyway - I thought I might ask here for some > kernel debugging assistance... > > I've got a debuggable kernel, with DDB. > > When the panic occurs (which I can readily reproduce) > I drop down into DDB... > > Which is great - right? > > But - IP is 0x0 (or, sometimes 0x80000000) - so the > trace command in DDB (to show the stack traceback) > doesn't seem to work - all I get is the Trap 12 message. That in itself doesn't mean you can't do a backtrace. I'm currently fighting this one: (kgdb) bt #0 0x0 in ?? () #1 0xc0184494 in spec_close (ap=0xc5f9de58) at ../../miscfs/specfs/spec_vnops.c:673 #2 0xc01f804e in ufsspec_close (ap=0xc5f9de58) at ../../ufs/ufs/ufs_vnops.c:1872 #3 0xc01f8521 in ufs_vnoperatespec (ap=0xc5f9de58) at ../../ufs/ufs/ufs_vnops.c:2317 (etc). > Does anyone have any sage words of advice on how to proceed with > tracking this down? At least some neat trick for determining where > the bad branch is taken? The real problem is that you have probably trashed your stack. I'd recommend using remote serial gdb; few people are happy with the level of support provided by ddb. Then you need to guess where it's happening, and set some breakpoints round likely places. It's not easy. The first thing to do would be to establish whether you're in process or interrupt context. If you're in a process context, you can at least find what process it is, and the macros in /usr/src/sys/modules/vinum/.gdbinit.kernel should help you determine what it's doing (sorry, the only documentation on these macros is the source code, including the gdb 'help user' command). Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 15 14:53:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id 4102B14A2A for ; Mon, 15 Nov 1999 14:53:44 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id JAA21505; Tue, 16 Nov 1999 09:23:38 +1030 (CST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991115175303.59865@mojave.sitaranetworks.com> Date: Mon, 15 Nov 1999 17:53:03 -0500 From: Greg Lehey To: "Kenneth D. Merry" , Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Set the baud rate on remote debugging Reply-To: Greg Lehey References: <199911152213.PAA58051@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <199911152213.PAA58051@panzer.kdm.org>; from Kenneth D. Merry on Mon, Nov 15, 1999 at 03:13:53PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 15 November 1999 at 15:13:53 -0700, Kenneth D. Merry wrote: > Zhihui Zhang wrote... >> >> I have set up a remote debugging environment. But I think default 9600 >> bps is slow. I can use "set remotebaud 19200" on the debugging machine >> side. How can I set the baud rate on the target machine that is running >> the debugged kernel? (I press CTRL+ESC+ALT to drop to DDB mode and find >> no command to set the baud rate). >> >> Any help is appreciated. > > Use the CONSPEED option in the kernel config file on the target machine. > e.g.: > > options CONSPEED=115200 I'm planning to modify ddb to specify the bit rate as a parameter to the gdb command: db> gdb 19200 Next trap will enter GDB remote protocol mode at 19200 bps Comments? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 15 14:59:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id C1ACB15189 for ; Mon, 15 Nov 1999 14:59:37 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id RAA08807; Mon, 15 Nov 1999 17:59:17 -0500 (EST) Date: Mon, 15 Nov 1999 16:46:50 -0500 (EST) From: Zhihui Zhang To: Greg Lehey Cc: "Kenneth D. Merry" , freebsd-hackers@FreeBSD.ORG Subject: Re: Set the baud rate on remote debugging In-Reply-To: <19991115175303.59865@mojave.sitaranetworks.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 15 Nov 1999, Greg Lehey wrote: > On Monday, 15 November 1999 at 15:13:53 -0700, Kenneth D. Merry wrote: > > Zhihui Zhang wrote... > >> > >> I have set up a remote debugging environment. But I think default 9600 > >> bps is slow. I can use "set remotebaud 19200" on the debugging machine > >> side. How can I set the baud rate on the target machine that is running > >> the debugged kernel? (I press CTRL+ESC+ALT to drop to DDB mode and find > >> no command to set the baud rate). > >> > >> Any help is appreciated. > > > > Use the CONSPEED option in the kernel config file on the target machine. > > e.g.: > > > > options CONSPEED=115200 > > I'm planning to modify ddb to specify the bit rate as a parameter to > the gdb command: > > db> gdb 19200 > Next trap will enter GDB remote protocol mode at 19200 bps > > Comments? > That will be useful. I have just found out that I can use sysctl -w machdep.conspeed=19200 to achieve this. But I can not go higher than 19200. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 15 15: 0:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id C13481518A for ; Mon, 15 Nov 1999 15:00:44 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA58590; Mon, 15 Nov 1999 16:00:31 -0700 (MST) (envelope-from ken) Message-Id: <199911152300.QAA58590@panzer.kdm.org> Subject: Re: Set the baud rate on remote debugging In-Reply-To: <19991115175303.59865@mojave.sitaranetworks.com> from Greg Lehey at "Nov 15, 1999 05:53:03 pm" To: grog@lemis.com (Greg Lehey) Date: Mon, 15 Nov 1999 16:00:31 -0700 (MST) Cc: zzhang@cs.binghamton.edu (Zhihui Zhang), freebsd-hackers@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote... > On Monday, 15 November 1999 at 15:13:53 -0700, Kenneth D. Merry wrote: > > Zhihui Zhang wrote... > >> > >> I have set up a remote debugging environment. But I think default 9600 > >> bps is slow. I can use "set remotebaud 19200" on the debugging machine > >> side. How can I set the baud rate on the target machine that is running > >> the debugged kernel? (I press CTRL+ESC+ALT to drop to DDB mode and find > >> no command to set the baud rate). > >> > >> Any help is appreciated. > > > > Use the CONSPEED option in the kernel config file on the target machine. > > e.g.: > > > > options CONSPEED=115200 > > I'm planning to modify ddb to specify the bit rate as a parameter to > the gdb command: > > db> gdb 19200 > Next trap will enter GDB remote protocol mode at 19200 bps > > Comments? It might also be nice to have it tuneable as a kernel variable from the loader and a sysctl variable. Oh, I see it's already available as the 'machdep.conspeed' sysctl variable. Obviously, specifying the baud rate at the ddb prompt should override any previous baud rate setting. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 15 17:31: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 916F415191 for ; Mon, 15 Nov 1999 17:31:00 -0800 (PST) (envelope-from hibma@skylink.it) Received: from skylink.it (va-173.skylink.it [194.185.55.173]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id CAA23658; Tue, 16 Nov 1999 02:31:22 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with SMTP id PAA00569; Mon, 15 Nov 1999 15:56:21 +0100 (CET) (envelope-from hibma@skylink.it) Date: Mon, 15 Nov 1999 15:56:21 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@henny.plazza.it Reply-To: Nick Hibma To: Ulf Zimmermann Cc: hackers@FreeBSD.org Subject: Re: Support for USB floppies like Y-E Data FlashBuster-u ? In-Reply-To: <19991114191412.B46290@PacHell.TelcoSucks.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Anyone working on such support yet ? This drive came with the Sony > Vaio Z505R. If you ask the 3 IDE disks and ethernet hub that have gone pop this weekend, they would say no, but myself I was pretty firm that I was going to do something about it this weekend. Bastard things, they should be shot and they will be. All is well now, so maybe this week, maybe next, top of the prioritised list in any case. And it would be great if by the time something is working I could count on a few people with machines that can boot from USB floppies to give me a hand in getting booting and installing on those machines to work. Cheers, Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 15 19:30: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id D617D14C9C for ; Mon, 15 Nov 1999 19:30:07 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id WAA92082 for ; Mon, 15 Nov 1999 22:29:57 -0500 (EST) Message-Id: <199911160329.WAA92082@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: vmpfw in pine via NFS Date: Mon, 15 Nov 1999 22:29:57 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am noticing a large number of pine (and only pine) procs stuck in disk-wait. All of the are in the WCHAN "vmpfw". Any ideas what this may mean? -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 15 20:55:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 40BEA14E5B for ; Mon, 15 Nov 1999 20:55:13 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id XAA74824 for ; Mon, 15 Nov 1999 23:55:12 -0500 (EST) Date: Mon, 15 Nov 1999 23:55:12 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: freebsd-hackers@freebsd.org Subject: Portable way to compare struct stat's? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a portable method for determining if the contents of two struct stat's are identical? I believe there is not. The problem is that while Posix defines a base set of fields for the stat structure, it appears that most implementations (including FreeBSD's) extend the structure with additional fields. Comparing all of the Posix fields will only determine the relationship between the Posix subset of the structures. My first inclination was to do a memcmp() which in theory should work across all stat structure definitions. But being that my development box runs FreeBSD, I quickly discovered that at least on FreeBSD, memcmp won't work. The reason? Because the FreeBSD struct stat defines 2 spare fields: st_lspare and st_qspare. The kernel never initializes the values of these fields when returning structures back to userland. So the values are more or less random contents that were on the kernel stack. Besides the possible security implications of passing random kernel stack contents into userland (I am no security expert, so there may not be any problem with this, it just doesn't seem right), there is the nasty side effect the memcmp cannot be used to compare 2 stat structures for equality. I have made a small set of changes to my local kernel source which addresses the problem by bzero'ing the struct stat memory in the kernel before filling it (which ensures that the spare fields get reset to a known state). I've attached the patches below (they need to be applied in the /sys/kern directory). So, back to my original question: is there a better way for comparing stat structures? Or, should memcmp work on other platforms (as well as FreeBSD given the attached patch)? -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Director of Technical Services, ALC Communications http://www.alcnet.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ --- kern_descrip.c.orig Mon Nov 15 22:11:57 1999 +++ kern_descrip.c Mon Nov 15 22:27:43 1999 @@ -548,9 +548,11 @@ panic("ofstat"); /*NOTREACHED*/ } - cvtstat(&ub, &oub); - if (error == 0) + if (error == 0) { + bzero(&oub, sizeof (oub)); + cvtstat(&ub, &oub); error = copyout((caddr_t)&oub, (caddr_t)uap->sb, sizeof (oub)); + } return (error); } #endif /* COMPAT_43 || COMPAT_SUNOS */ @@ -578,6 +580,7 @@ if ((unsigned)uap->fd >= fdp->fd_nfiles || (fp = fdp->fd_ofiles[uap->fd]) == NULL) return (EBADF); + bzero(&ub, sizeof (ub)); switch (fp->f_type) { case DTYPE_FIFO: @@ -646,6 +649,7 @@ /*NOTREACHED*/ } if (error == 0) { + bzero(&nub, sizeof (nub)); cvtnstat(&ub, &nub); error = copyout((caddr_t)&nub, (caddr_t)uap->sb, sizeof (nub)); } --- vfs_syscalls.c.orig Mon Nov 15 23:25:48 1999 +++ vfs_syscalls.c Mon Nov 15 23:29:08 1999 @@ -1514,6 +1514,7 @@ vput(nd.ni_vp); if (error) return (error); + bzero(&osb, sizeof (osb)); cvtstat(&sb, &osb); error = copyout((caddr_t)&osb, (caddr_t)SCARG(uap, ub), sizeof (osb)); return (error); @@ -1552,6 +1553,7 @@ vput(vp); if (error) return (error); + bzero(&osb, sizeof (osb)); cvtstat(&sb, &osb); error = copyout((caddr_t)&osb, (caddr_t)SCARG(uap, ub), sizeof (osb)); return (error); @@ -1613,6 +1615,7 @@ SCARG(uap, path), p); if (error = namei(&nd)) return (error); + bzero(&sb, sizeof (sb)); error = vn_stat(nd.ni_vp, &sb, p); vput(nd.ni_vp); if (error) @@ -1648,6 +1651,7 @@ SCARG(uap, path), p); if (error = namei(&nd)) return (error); + bzero(&sb, sizeof (sb)); vp = nd.ni_vp; error = vn_stat(vp, &sb, p); vput(vp); @@ -1707,6 +1711,7 @@ vput(nd.ni_vp); if (error) return (error); + bzero(&nsb, sizeof (nsb)); cvtnstat(&sb, &nsb); error = copyout((caddr_t)&nsb, (caddr_t)SCARG(uap, ub), sizeof (nsb)); return (error); @@ -1745,6 +1750,7 @@ vput(vp); if (error) return (error); + bzero(&nsb, sizeof (nsb)); cvtnstat(&sb, &nsb); error = copyout((caddr_t)&nsb, (caddr_t)SCARG(uap, ub), sizeof (nsb)); return (error); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 15 22:22:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 432D514D83 for ; Mon, 15 Nov 1999 22:22:52 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id WAA02931; Mon, 15 Nov 1999 22:22:20 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id WAA24026; Mon, 15 Nov 1999 22:22:19 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA09384; Mon, 15 Nov 99 22:22:08 PST Message-Id: <3830F80F.6456DC5@softweyr.com> Date: Mon, 15 Nov 1999 23:22:07 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Kelly Yancey Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kelly Yancey wrote: > > Is there a portable method for determining if the contents of two struct > stat's are identical? On a single system, if st_dev and st_ino are equal, you must be referring to the same object. If not, I'd like to hear about it. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 0:40:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from clifford.inch.com (clifford.inch.com [207.240.140.163]) by hub.freebsd.org (Postfix) with ESMTP id C068014CB8 for ; Tue, 16 Nov 1999 00:40:28 -0800 (PST) (envelope-from omar@clifford.inch.com) Received: (from omar@localhost) by clifford.inch.com (8.9.3/8.8.5) id CAA31593 for hackers@FreeBSD.ORG; Tue, 16 Nov 1999 02:57:50 -0500 Message-ID: <19991116025749.A31559@clifford.inch.com> Date: Tue, 16 Nov 1999 02:57:50 -0500 From: Omar Thameen To: hackers@FreeBSD.ORG Subject: panic: page fault - need help with diagnosis Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, We have a server running 3.2-RELEASE #2 (see dmesg below) which crashed during a period of light activity. It's a dedicated server hosting one large web site (Apache 1.3.4 with php) and a half dozen smaller sites. There's a mysql server as well, though the main db work is done by a separate machine. The server became remotely unresponsive (couldn't ping, couldn't console in) and had nothing in the logs. It was locked with the following on the screen, which I transcribed. I had to hit the reset switch to bring it back. Can anyone offer any insight as to what happened and if there are any problems? Thanks much, Omar ------------------------- Begin included text ------------------------- panic: free: multiple pfrees syncing disks... Fatal trap 12: page fault while in kernel mode fault virtual address = 0xb8 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01492eb stack pointer = 0x10:0xc01ef2cc frame pointer = 0x10:0xc01ef2e0 code segment = base 0x0, limit 0xfffff, type 0x1b = TPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = idle interrupt mask = net tty bio cam trap number = 12 panic: page fault -------------------------- End included text -------------------------- dmesg output: ------------------------- Begin included text ------------------------- Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.2-RELEASE #2: Mon Aug 2 12:23:54 EDT 1999 spork@:/usr/src/sys/compile/LOCAL_KERN Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 350797746 Hz CPU: Pentium II/Xeon/Celeron (350.80-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183f9ff> real memory = 536870912 (524288K bytes) avail memory = 519847936 (507664K bytes) Preloaded elf kernel "kernel" at 0xc0255000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc025509c. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.1.0 chip2: rev 0x02 on pci0.4.0 chip3: rev 0x02 on pci0.4.3 ahc0: rev 0x00 int a irq 10 on pci0.6.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs fxp0: rev 0x05 int a irq 11 on pci0.7.0 fxp0: Ethernet address 00:e0:18:90:ad:51 vga0: rev 0xd3 int a irq 10 on pci0.9.0 Probing for devices on PCI bus 1: Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> 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 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Waiting 2 seconds for SCSI devices to settle changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da0: 4357MB (8923136 512 byte sectors: 255H 63S/T 555C) da1 at ahc0 bus 0 target 0 lun 1 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da1: 8715MB (17848320 512 byte sectors: 255H 63S/T 1111C) WARNING: / was not properly dismounted -------------------------- End included text -------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 1:26:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 6892E14CB7 for ; Tue, 16 Nov 1999 01:26:15 -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 3.040 #1) id 11nery-000DXu-00; Tue, 16 Nov 1999 11:25:46 +0200 From: Sheldon Hearn Reply-To: chat@FreeBSD.org To: Nick Hibma Cc: Ulf Zimmermann , hackers@FreeBSD.org Subject: Re: Support for USB floppies like Y-E Data FlashBuster-u ? In-reply-to: Your message of "Mon, 15 Nov 1999 15:56:21 +0100." Date: Tue, 16 Nov 1999 11:25:46 +0200 Message-ID: <52073.942744346@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 15 Nov 1999 15:56:21 +0100, Nick Hibma wrote: > If you ask the 3 IDE disks and ethernet hub that have gone pop this > weekend, they would say no, but myself I was pretty firm that I was > going to do something about it this weekend. Bastard things, they should > be shot and they will be. Be careful about shooting hard drives. Specifically, get your angle right such that you _do_ actually fracture the casing. The alternatives are all unfortunate and mostly painful. We wouldn't want you hurting yourself, no matter how funny the story might be. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 3:42:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from techpower.net (techpower.net [205.133.231.1]) by hub.freebsd.org (Postfix) with ESMTP id 43FE114D59 for ; Tue, 16 Nov 1999 03:42:26 -0800 (PST) (envelope-from fragment@techpower.net) Received: from localhost (fragment@localhost) by techpower.net (8.9.3/8.9.3) with ESMTP id HAA34006 for ; Tue, 16 Nov 1999 07:46:03 GMT (envelope-from fragment@techpower.net) Date: Tue, 16 Nov 1999 07:46:03 +0000 (GMT) From: fragmented To: freebsd-hackers@freebsd.org Subject: ppp-2.3.10 In-Reply-To: <3.0.5.32.19991114115851.0094b280@pop.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Subject: ppp-2.3.10 > > > > > > > > > > Anyone successfully compiled ppp-2.3.10 under 3.3-Stable ? > > I get an error messages unblanced #endif in sys-bsd.c if I removed > > this it compiles and works except the wtmp does not log whois on the > > system under pppd on dialups. > > Any help would be appreciated. Also I am not on this list would you please mail me direct. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 4:53:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cequrux.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id 8E41E14C93 for ; Tue, 16 Nov 1999 04:53:30 -0800 (PST) (envelope-from gram@cequrux.com) Received: (from nobody@localhost) by citadel.cequrux.com (8.9.3/8.9.3) id OAA29641 for ; Tue, 16 Nov 1999 14:53:27 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 29573; Tue Nov 16 14:53:06 1999 From: Graham Wheeler To: hackers@freebsd.org Subject: Missing core dumps Date: Tue, 16 Nov 1999 14:45:26 +0200 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <9911161453040F.23105@cequrux.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Howdy all I have a program that occasionally catches a SEGV signal, but it doesn't dump core. And I really could use that core file, as I can't replicate the problem under controlled conditions. The program is invoked from inetd. It is owned by user nobody and has group mail. When it starts up, it calls setuid and setgid to set the user and group to be nobody and mail respectively. It then chroots to a directory which is owned by bin and has group mail. This directory has owner and group read, write and execute permissions on. The program can create and destroy temporary files in this directory without any problem. It doesn't catch SEGV signals in its own handler, and it has no obvious file size limits. From my reading of Stevens APITUE, there are no reasons why the core file shouldn't be created. Am I missing something? (This is on 2.2.7 and 2.2.8 systems, although I suspect the behaviour will be unchanged under 3.x) TIA gram -- Dr Graham Wheeler E-mail: gram@cequrux.com Cequrux Technologies Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data/Network Security Specialists WWW: http://www.cequrux.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 5:28:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cequrux.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id 2B88214CBE for ; Tue, 16 Nov 1999 05:28:15 -0800 (PST) (envelope-from gram@cequrux.com) Received: (from nobody@localhost) by citadel.cequrux.com (8.9.3/8.9.3) id PAA02047 for ; Tue, 16 Nov 1999 15:28:14 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 2044; Tue Nov 16 15:27:39 1999 From: Graham Wheeler To: hackers@freebsd.org Subject: Re: Missing core files Date: Tue, 16 Nov 1999 15:26:26 +0200 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <9911161527380G.23105@cequrux.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ignore my last message; having trolled through the kernel source I see that if setgid/setuid are called at all (even if there is no actual change as a result), then no core files will be created. Seems Stevens was wrong on this one... -- Dr Graham Wheeler E-mail: gram@cequrux.com Cequrux Technologies Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data/Network Security Specialists WWW: http://www.cequrux.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 7:39:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 6898515219 for ; Tue, 16 Nov 1999 07:39:25 -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.9.3/8.9.3) with SMTP id KAA07073; Tue, 16 Nov 1999 10:38:42 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Tue, 16 Nov 1999 10:38:42 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Wes Peters Cc: Kelly Yancey , freebsd-hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? In-Reply-To: <3830F80F.6456DC5@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 15 Nov 1999, Wes Peters wrote: > Kelly Yancey wrote: > > > > Is there a portable method for determining if the contents of two struct > > stat's are identical? > > On a single system, if st_dev and st_ino are equal, you must be referring > to the same object. If not, I'd like to hear about it. This assumption has always caused lots of pain and suffering for distributed file system people -- in a distributed file system, the requirement that you can generate a unique 32 bit number for each file or directory visible in the FS is a fairly arduous one. Either the number is assigned locally, or it is assigned globally--if locally, you have to dynamically allocate and track the use of so-called inode numbers, and their mappings to files. That's extremely expensive in terms of memory, processor, et al, to maintain the guise of having an inode number where one doesn't exist. If you go for the global option, you have to manage synchronization if you have replication or weak consistency, etc. Very messy. :-) The only real uniqueness guarantee, in my view, should be the uniqueness of the vnode pointer in the kernel -- that is sufficient to distinguish references to files only where relevant (i.e., for whatever reason, there is a vnode reference to the object in kernel). This comes up in AFS and Coda a lot, especially in operating systems where the kernel requires the uniqueness of a given inode number on a device (Linux)--in Coda/AFS, there is indeed a globally unique fid for each file/directory, only it's 96-bit, which in my book doesn't guarantee unique mapping onto the 16 bit dev number and 32 bit inode. This means a hash is required, and collisions are possibly. When a collision occurs on the hash under Linux, all hell breaks loose :-). In Coda, the fid of a file/directory can change, as if you're running disconnected, you allocate out of a local fid space. When you reconnect, you acquire a global fid for the file based on volume number and file number in the volume. But it's still the same file object. Unique inode number makes even less space if you have a web file system, wherein URLs identify files, but you trying to generate a unique inode num per referenced URLs would be a mess. Unique file numbers really only make sense when you have an inode-based file system, or something like that--sure, somewhere there will be a value uniquely identifying the file (unless fs lookups are queries :-), but it may not easily be mappable onto the inode number namespace, and it may not be possible to do so in a way consistent with inode number behavior, a common assumption in tools like tar that try to use inode numbers to detect hard links. Rant rant rant. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 10: 3:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id EB76515239 for ; Tue, 16 Nov 1999 10:03:09 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id KAA02088; Tue, 16 Nov 1999 10:03:07 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 16 Nov 1999 10:03:07 -0800 (PST) From: Doug White To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vmpfw in pine via NFS In-Reply-To: <199911160329.WAA92082@cs.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 15 Nov 1999, David E. Cross wrote: > I am noticing a large number of pine (and only pine) procs stuck in disk-wait. > All of the are in the WCHAN "vmpfw". Any ideas what this may mean? Is the mail spool pine accessing on this NFS volume, or just the binary? If so you're breaking the cardinal rule of NFS: Never serve mail spools via NFS. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 10: 4:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id 348F215239 for ; Tue, 16 Nov 1999 10:04:43 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id EAA22596; Wed, 17 Nov 1999 04:34:14 +1030 (CST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991116130339.17641@mojave.sitaranetworks.com> Date: Tue, 16 Nov 1999 13:03:39 -0500 From: Greg Lehey To: Graham Wheeler , hackers@FreeBSD.ORG Subject: Re: Missing core dumps Reply-To: Greg Lehey References: <9911161453040F.23105@cequrux.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <9911161453040F.23105@cequrux.com>; from Graham Wheeler on Tue, Nov 16, 1999 at 02:45:26PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 16 November 1999 at 14:45:26 +0200, Graham Wheeler wrote: > Howdy all > > I have a program that occasionally catches a SEGV signal, but it doesn't dump > core. And I really could use that core file, as I can't replicate the problem > under controlled conditions. > > The program is invoked from inetd. It is owned by user nobody and has group > mail. When it starts up, it calls setuid and setgid to set the user and group > to be nobody and mail respectively. It then chroots to a directory which is > owned by bin and has group mail. This directory has owner and group read, > write and execute permissions on. The program can create and destroy temporary > files in this directory without any problem. > > It doesn't catch SEGV signals in its own handler, and it has no obvious file > size limits. > > From my reading of Stevens APITUE, there are no reasons why the core file > shouldn't be created. Am I missing something? (This is on 2.2.7 and 2.2.8 > systems, although I suspect the behaviour will be unchanged under 3.x) For security reasons, you normally can't get a core dump of a setuid program. You could use it to break security. To change this behaviour, set the sysctl sugid.coredump: # sysctl -w sugid.coredump=1 BTW, this knob isn't mentioned in the man page. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 10:16:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A0E7B14D98 for ; Tue, 16 Nov 1999 10:16:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA53317; Tue, 16 Nov 1999 10:16:30 -0800 (PST) (envelope-from dillon) Date: Tue, 16 Nov 1999 10:16:30 -0800 (PST) From: Matthew Dillon Message-Id: <199911161816.KAA53317@apollo.backplane.com> To: Doug White Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: vmpfw in pine via NFS References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Mon, 15 Nov 1999, David E. Cross wrote: : :> I am noticing a large number of pine (and only pine) procs stuck in disk-wait. :> All of the are in the WCHAN "vmpfw". Any ideas what this may mean? : :Is the mail spool pine accessing on this NFS volume, or just the binary? : :If so you're breaking the cardinal rule of NFS: Never serve mail spools :via NFS. : :Doug White | FreeBSD: The Power to Serve :dwhite@resnet.uoregon.edu | www.FreeBSD.org Which FreeBSD release is being used here? What kind of NFS mount is being used (localhost mount?) -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 10:19:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 6A3981533F; Tue, 16 Nov 1999 10:19:11 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id NAA00441; Tue, 16 Nov 1999 13:19:04 -0500 (EST) Date: Tue, 16 Nov 1999 12:06:37 -0500 (EST) From: Zhihui Zhang Reply-To: Zhihui Zhang To: freebsd-hackers@freebsd.org, freebsd-fs@freebsd.org Subject: On-the-fly defragmentation of FFS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After studying the code of ffs_reallocblks() for a while, it occurs to me that the on-the-fly defragmentation of a FFS file (It does this on a per file basis) only takes place at the end of a file and only when the previous logical blocks have all been laid out contiguously on the disk (see also cluster_write()). This seems to me a lot of limitations to the FFS defragger. I wonder if the file was not allocated contiguously when it was first created, how can it find contiguous space later unless we delete a lot of files in between? I hope someone can confirm or correct my understanding. It would be even better if someone can suggest a way to improve defragmentation if the FFS defragger is not very efficient. BTW, if I copy all files from a filesystem to a new filesystem, will the files be stored more contiguously? Why? Any help or suggestion is appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 10:46:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from marcy.nas.nasa.gov (marcy.nas.nasa.gov [129.99.113.17]) by hub.freebsd.org (Postfix) with ESMTP id ECCA314E20 for ; Tue, 16 Nov 1999 10:46:38 -0800 (PST) (envelope-from wrstuden@marcy.nas.nasa.gov) Received: from localhost (wrstuden@localhost) by marcy.nas.nasa.gov (8.9.3/NAS8.8.7n) with SMTP id KAA07787; Tue, 16 Nov 1999 10:46:26 -0800 (PST) Date: Tue, 16 Nov 1999 10:46:26 -0800 (PST) From: Bill Studenmund To: Kelly Yancey Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 15 Nov 1999, Kelly Yancey wrote: > > Is there a portable method for determining if the contents of two struct > stat's are identical? I believe there is not. The problem is that while What exactly are you trying to do? i.e. why are you comparing the struct stat's? Take care, Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 10:47:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 7D09514D91 for ; Tue, 16 Nov 1999 10:47:41 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id NAA07576; Tue, 16 Nov 1999 13:47:34 -0500 (EST) Message-Id: <199911161847.NAA07576@cs.rpi.edu> To: Matthew Dillon Cc: Doug White , "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: vmpfw in pine via NFS In-Reply-To: Message from Matthew Dillon of "Tue, 16 Nov 1999 10:16:30 PST." <199911161816.KAA53317@apollo.backplane.com> Date: Tue, 16 Nov 1999 13:47:34 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :> I am noticing a large number of pine (and only pine) procs stuck in disk-wait. > :> All of the are in the WCHAN "vmpfw". Any ideas what this may mean? > : > :Is the mail spool pine accessing on this NFS volume, or just the binary? > : > :If so you're breaking the cardinal rule of NFS: Never serve mail spools > :via NFS. > : > > Which FreeBSD release is being used here? What kind of NFS mount is > being used (localhost mount?) Ok, I have some additional details, as I was able to mostly resolve the issue. Yes, mail is nfs exported, but that does not appear to be the issue in this case. pine is run from nfs mounted "/usr/local" pine would hang every time a user would go to send a composed message and wind up in "vmpfw". The "fix" was to go to the NFS server for /usr/local and do "mv pine pine.old; cp pine.old pine". This would (obviously) not affect any of the old pine's, it would however allow any new pines to run w/o problems. Note that any access to /usr/local/bin/pine.old on the client machine would result in a hang. Specifically "file /usr/local/bin/pine.old" resulted in "vmpfw" as did "cmp" and a couple of others. All of these worked just fine on the NFS server. The release in question is 3.3-STABLE from this past Friday (Nov. 12). -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 10:51:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from moo.sysabend.org (moo.sysabend.org [209.0.55.68]) by hub.freebsd.org (Postfix) with ESMTP id 7DC14152BA for ; Tue, 16 Nov 1999 10:51:26 -0800 (PST) (envelope-from ragnar@sysabend.org) Received: by moo.sysabend.org (Postfix, from userid 1004) id E7B8A754D; Tue, 16 Nov 1999 10:51:42 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by moo.sysabend.org (Postfix) with ESMTP id C65BC1D84; Tue, 16 Nov 1999 10:51:42 -0800 (PST) Date: Tue, 16 Nov 1999 10:51:42 -0800 (PST) From: Jamie Bowden To: Doug White Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: vmpfw in pine via NFS In-Reply-To: Message-ID: Approved: yep X-representing: Only myself. X-badge: We don't need no stinking badges. X-obligatory-profanity: Fuck X-moo: Moo. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 16 Nov 1999, Doug White wrote: :If so you're breaking the cardinal rule of NFS: Never serve mail spools :via NFS. Correction: Never mount mail splls via NFS on platforms without NFS locking. I mount mail spools via NFS all the time in SunOS, Solaris, and Irix. Have been for years. Never had a problem. Jamie Bowden -- If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 11:24: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (Postfix) with ESMTP id 6933D14EB1; Tue, 16 Nov 1999 11:23:57 -0800 (PST) (envelope-from roger@cs.strath.ac.uk) Received: from cs.strath.ac.uk (roger@telford-01.cs.strath.ac.uk [130.159.172.1]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with ESMTP id TAA04032 Tue, 16 Nov 1999 19:23:56 GMT Message-ID: <3831AF4C.5DB28281@cs.strath.ac.uk> Date: Tue, 16 Nov 1999 19:23:56 +0000 From: Roger Hardiman Organization: Department of Computer Science, University of Strathclyde X-Mailer: Mozilla 4.61 [en] (X11; I; SunOS 5.5.1 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org, hackers@freebsd.org, Russell Cattelan Subject: HEADS UP: ES1371/1373 sound card support in -stable Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've just committed Russell Cattelan's patch for ES1371/ES1373 PCI Audio sound cards (which includes the new Creative Labs SoundBlaster 16, 64 and 128). This HEADS up is to explain that the code committed to -stable has not been committed to -current. This is because in 4.x-current, the PCM driver has been totally rewritten and so, the -stable driver and the -current driver are very very different. A commit to -current and an MFC are not applicable. If anyone experiences any problems with ES1370 sound cards or the new 1371 / 1373 support, please email Russell Cattelan or Roger Hardiman Thanks Roger -- Roger Hardiman roger@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 11:44:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from usc.edu (usc.edu [128.125.253.136]) by hub.freebsd.org (Postfix) with ESMTP id 5CE1D14D9C for ; Tue, 16 Nov 1999 11:44:14 -0800 (PST) (envelope-from walker@usc.edu) Received: from skat.usc.edu (walker@skat.usc.edu [128.125.253.131]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id LAA04749 for ; Tue, 16 Nov 1999 11:44:13 -0800 (PST) Received: from localhost (walker@localhost) by skat.usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id LAA19170 for ; Tue, 16 Nov 1999 11:44:12 -0800 (PST) Date: Tue, 16 Nov 1999 11:44:12 -0800 (PST) From: Mike Walker To: freebsd-hackers@FreeBSD.ORG Subject: Re: vmpfw in pine via NFS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I am noticing a large number of pine (and only pine) procs stuck in >> disk-wait. All of the are in the WCHAN "vmpfw". Any ideas what >> this may mean? > Is the mail spool pine accessing on this NFS volume, or just the > binary? > > If so you're breaking the cardinal rule of NFS: Never serve mail > spools via NFS. > > Doug White | FreeBSD: The Power to Serve > dwhite@resnet.uoregon.edu | www.FreeBSD.org Why is this a cardinal rule? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 11:48:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from vitoria.ddsecurity.com.br (vitoria.ddsecurity.com.br [200.18.130.93]) by hub.freebsd.org (Postfix) with SMTP id D226814D9C for ; Tue, 16 Nov 1999 11:47:48 -0800 (PST) (envelope-from grios@ddsecurity.com.br) Received: (qmail 89029 invoked by uid 1001); 16 Nov 1999 19:45:55 -0000 From: "Gustavo Rios" Date: Tue, 16 Nov 1999 17:45:55 -0200 (EDT) To: Mike Walker Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vmpfw in pine via NFS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 16 Nov 1999, Mike Walker wrote: > >> I am noticing a large number of pine (and only pine) procs stuck in > >> disk-wait. All of the are in the WCHAN "vmpfw". Any ideas what > >> this may mean? > > > Is the mail spool pine accessing on this NFS volume, or just the > > binary? > > > > If so you're breaking the cardinal rule of NFS: Never serve mail > > spools via NFS. And what about maildir with qmail ? Isn't it safe via NFS ? > > Doug White | FreeBSD: The Power to Serve > > dwhite@resnet.uoregon.edu | www.FreeBSD.org > > Why is this a cardinal rule? > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 11:49:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 754A514D9C for ; Tue, 16 Nov 1999 11:49:43 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-3.enteract.com (dscheidt@shell-3.enteract.com [207.229.143.42]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id NAA49442; Tue, 16 Nov 1999 13:49:39 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Tue, 16 Nov 1999 13:49:39 -0600 (CST) From: David Scheidt To: Mike Walker Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vmpfw in pine via NFS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 16 Nov 1999, Mike Walker wrote: > > If so you're breaking the cardinal rule of NFS: Never serve mail > > spools via NFS. > Why is this a cardinal rule? FreeBSD doesn't support locking over NFS, so you will get corruption of mailboxes if there are attempts at concurrent access of the mail spools. Maildir solves this problem. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 12: 6: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id C87CD14D2A for ; Tue, 16 Nov 1999 12:05:53 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id PAA87182; Tue, 16 Nov 1999 15:05:45 -0500 (EST) Date: Tue, 16 Nov 1999 15:05:45 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: Wes Peters Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? In-Reply-To: <3830F80F.6456DC5@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 15 Nov 1999, Wes Peters wrote: > Kelly Yancey wrote: > > > > Is there a portable method for determining if the contents of two struct > > stat's are identical? > > On a single system, if st_dev and st_ino are equal, you must be referring > to the same object. If not, I'd like to hear about it. > The problem is that I need to be able to determine if the file's metadata has changed, not necessarily if two paths refer to the same file. I would use the st_ctime field except that not all file systems implement it. Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Director of Technical Services, ALC Communications http://www.alcnet.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 12:40:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id D336B14DC5 for ; Tue, 16 Nov 1999 12:40:45 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id PAA87906; Tue, 16 Nov 1999 15:40:43 -0500 (EST) Date: Tue, 16 Nov 1999 15:40:43 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: Bill Studenmund Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 16 Nov 1999, Bill Studenmund wrote: > On Mon, 15 Nov 1999, Kelly Yancey wrote: > > > > > Is there a portable method for determining if the contents of two struct > > stat's are identical? I believe there is not. The problem is that while > > What exactly are you trying to do? i.e. why are you comparing the struct > stat's? > Basically just determine whether any field of the structure has changed (ie, if any of the file's metadata has changed). But the tricks are that a) not all file systems implement a ctime value b) even on systems that do implement ctime fields, Posix only requires 1 second resolution (unlike FreeBSD which was smart enough to use timespecs for nanosecond resolution :) ) c) the method has to work on all (or most) operating systems that implement the stat, fstat, and lstat calls. I thought memcmp() to be the correct solution except that spare fields in the structure are filled with garbage (kernel stack contents), and who knows what values might be stored in the padding between fields for alignment. Using memcmp yields false positives then. Unfortunately, a quick perusal of the OpenBSD source tree indicates that it (and most likely NetBSD) also have the problem. Which leads to the dillema, how to tell with any reasonable accuracy whether 2 stat structures are the same on a given OS. I'm beginning to think that the only way is a kludge: one routine per OS which only checks the fields defined on that OS. This will greatly limit portability due to the cost of maintainability :( I'm hoping that someone knows a better way. For the list: while I was checking OpenBSD's kern_descrip.c to see whether they zeroed the memory first, I noticed that they had the following check that my 3.3-stable system does not: [ ... ] /* Don't let non-root see generation numbers (for NFS security) */ if (suser(p->p_ucred, &p->p_acflag)) ub.st_gen = 0; [ perform copyout ... ] Is this a legitimate concern or paranoia? I see that we don't bother in -current with it either. Thanks, Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Director of Technical Services, ALC Communications http://www.alcnet.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 14:35:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id F0CC214CA7 for ; Tue, 16 Nov 1999 14:35:08 -0800 (PST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id XAA03300 for ; Tue, 16 Nov 1999 23:34:58 +0100 (CET) (envelope-from leifn@neland.dk) Date: Tue, 16 Nov 1999 23:34:58 +0100 (CET) From: Leif Neland To: freebsd-hackers@freebsd.org Subject: making users modem dial from webpage Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been asked if this is possible: Having a webserver running a database of some sort. User clicks a button on a form, a cgi-script runs, determines the ip of the user, and sends a command to "something" on the users pc, which then sends commands to a modem, making it dial a number. So our salespeople can dial directly from the database. This "something", could this be a java-applet, or should it be an active-x? Or something completely different? I probably could install Back Orifice, and send commands to that :-) Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 14:45:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id D4CA9151CA for ; Tue, 16 Nov 1999 14:45:44 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id RAA90423; Tue, 16 Nov 1999 17:45:41 -0500 (EST) Date: Tue, 16 Nov 1999 17:45:41 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: Leif Neland Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: making users modem dial from webpage In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 16 Nov 1999, Leif Neland wrote: > I've been asked if this is possible: > > Having a webserver running a database of some sort. > User clicks a button on a form, a cgi-script runs, determines the ip of > the user, and sends a command to "something" on the users pc, which then > sends commands to a modem, making it dial a number. > > So our salespeople can dial directly from the database. > > This "something", could this be a java-applet, or should it be an > active-x? Or something completely different? > > I probably could install Back Orifice, and send commands to that :-) > > Leif > I think that the security settings in most browsers would prevent an object embedded in a page (such as a java applet or activeX control) from this amount of system access. Just think of the implications otherwise: maliscious people could put applets/activeX controls on a web page which racked up long distance charges to some eastern European country. But that doesn't rule java out (if you are a java fan). Basically, you just need some custom application running on each salesperson's workstation which listens to a given TCP port. You can write that application in C, or Java, or god forbid, visual basic. Oh, and make sure you traffic on this port from outside your firewall. :) Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Director of Technical Services, ALC Communications http://www.alcnet.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 15:49:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 60C4814EC2 for ; Tue, 16 Nov 1999 15:49:40 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id KAA09934; Wed, 17 Nov 1999 10:18:59 +1030 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199911162348.KAA09934@gizmo.internode.com.au> Subject: Re: HEADS UP: ES1371/1373 sound card support in -stable To: roger@cs.strath.ac.uk (Roger Hardiman) Date: Wed, 17 Nov 1999 10:18:59 +1030 (CST) Cc: hackers@freebsd.org In-Reply-To: <3831AF4C.5DB28281@cs.strath.ac.uk> from "Roger Hardiman" at Nov 16, 99 07:23:56 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Roger Hardiman wrote: > This is because in 4.x-current, the PCM driver has been totally > rewritten and so, the -stable driver and the -current driver are very very > different. A commit to -current and an MFC are not applicable. That'd be an MTC rather than an MFC, wouldn't it? :-) - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 16:34:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A481C14E46 for ; Tue, 16 Nov 1999 16:34:37 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA55836; Tue, 16 Nov 1999 16:34:31 -0800 (PST) (envelope-from dillon) Date: Tue, 16 Nov 1999 16:34:31 -0800 (PST) From: Matthew Dillon Message-Id: <199911170034.QAA55836@apollo.backplane.com> To: Kelly Yancey Cc: Leif Neland , freebsd-hackers@FreeBSD.ORG Subject: Re: making users modem dial from webpage References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : I think that the security settings in most browsers would prevent an :object embedded in a page (such as a java applet or activeX control) from :this amount of system access. Just think of the implications otherwise: Not for activeX. If you enable activeX, your system is wide-open. For Java you theoretically have a sandbox, certainly better then activeX, but it isn't assured. -Matt Matthew Dillon :maliscious people could put applets/activeX controls on a web page which :racked up long distance charges to some eastern European country. : But that doesn't rule java out (if you are a java fan). Basically, you :just need some custom application running on each salesperson's :workstation which listens to a given TCP port. You can write that :application in C, or Java, or god forbid, visual basic. Oh, and make sure :you traffic on this port from outside your firewall. :) : : Kelly : :-- :Kelly Yancey - kbyanc@posi.net - Richmond, VA :Director of Technical Services, ALC Communications http://www.alcnet.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 17:28:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 6BAE214E2D for ; Tue, 16 Nov 1999 17:28:50 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id RAA64713 for ; Tue, 16 Nov 1999 17:28:49 -0800 (PST) Date: Tue, 16 Nov 1999 17:28:48 -0800 (PST) From: Julian Elischer To: hackers@freebsd.org Subject: netgraph into -stable. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I admit that it doesn't seem a minor addition, but I'd like ot get netgraph down -nto 3.x now that it has been shaken down a bit in 4.x reasons: 1/ DSL in Canada is now switching rapidly to PPPoE. 2/ PPP will start using it soon (other than with pppoe) and we'd like ONE version not 2 for Brian to maintain. 3/ ISPs who may wan tto use the PPPOE server side are generally running 3.x, not 4.x Supporting facts: Netgraph is written to generally be non intrusive. No code is changed in the non "options NETGRAPH" case and only minor changes are made in normal code paths in the NETGRAPH case. (with the exception of the if_sr and if_ar drivers) I might hold off on some of the more intrusive of those changes (e.g. no real need to add it to netstat immediatly) which will not really effect the functionality. And last but not least: We are actually developing Netgraph under 3.3 so we are already keeping two source trees in sync, 3.3. and 4.0 so we might as well let others get at it. Anyone violently object? Julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 17:31: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id C0B4A14F9B for ; Tue, 16 Nov 1999 17:30:58 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id RAA09215; Tue, 16 Nov 1999 17:31:30 -0800 Date: Tue, 16 Nov 1999 17:31:29 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Julian Elischer Cc: hackers@FreeBSD.ORG Subject: Re: netgraph into -stable. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What's the potential breakage? On Tue, 16 Nov 1999, Julian Elischer wrote: > > I admit that it doesn't seem a minor addition, but > I'd like ot get netgraph down -nto 3.x now that it has been shaken down a > bit in 4.x > > reasons: > 1/ DSL in Canada is now switching rapidly to PPPoE. > 2/ PPP will start using it soon (other than with pppoe) > and we'd like ONE version not 2 for Brian to maintain. > 3/ ISPs who may wan tto use the PPPOE server side are generally running > 3.x, not 4.x > > > Supporting facts: > Netgraph is written to generally be non intrusive. > No code is changed in the non "options NETGRAPH" case and only minor > changes are made in normal code paths in the NETGRAPH case. > (with the exception of the if_sr and if_ar drivers) > > I might hold off on some of the more intrusive of those > changes (e.g. no real need to add it to netstat immediatly) > which will not really effect the functionality. > > > And last but not least: > We are actually developing Netgraph under 3.3 so we are already keeping > two source trees in sync, 3.3. and 4.0 so we might as well let others get > at it. > > Anyone violently object? > > Julian > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 17:33:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id C7663150A9 for ; Tue, 16 Nov 1999 17:33:26 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id RAA64855; Tue, 16 Nov 1999 17:33:23 -0800 (PST) Date: Tue, 16 Nov 1999 17:33:21 -0800 (PST) From: Julian Elischer To: Matthew Jacob Cc: hackers@FreeBSD.ORG Subject: Re: netgraph into -stable. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 16 Nov 1999, Matthew Jacob wrote: > > What's the potential breakage? None that I know of.. if you don't use it, it can't break.. > > > On Tue, 16 Nov 1999, Julian Elischer wrote: > > > > > I admit that it doesn't seem a minor addition, but > > I'd like ot get netgraph down -nto 3.x now that it has been shaken down a > > bit in 4.x > > > > reasons: > > 1/ DSL in Canada is now switching rapidly to PPPoE. > > 2/ PPP will start using it soon (other than with pppoe) > > and we'd like ONE version not 2 for Brian to maintain. > > 3/ ISPs who may wan tto use the PPPOE server side are generally running > > 3.x, not 4.x > > > > > > Supporting facts: > > Netgraph is written to generally be non intrusive. > > No code is changed in the non "options NETGRAPH" case and only minor > > changes are made in normal code paths in the NETGRAPH case. > > (with the exception of the if_sr and if_ar drivers) > > > > I might hold off on some of the more intrusive of those > > changes (e.g. no real need to add it to netstat immediatly) > > which will not really effect the functionality. > > > > > > And last but not least: > > We are actually developing Netgraph under 3.3 so we are already keeping > > two source trees in sync, 3.3. and 4.0 so we might as well let others get > > at it. > > > > Anyone violently object? > > > > Julian > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 17:45: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from awfulhak.org (dynamic-112.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.240]) by hub.freebsd.org (Postfix) with ESMTP id 726ED14E3C for ; Tue, 16 Nov 1999 17:44:58 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA36430; Tue, 16 Nov 1999 23:19:30 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA04673; Tue, 16 Nov 1999 23:23:52 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199911162323.XAA04673@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Leif Neland Cc: freebsd-hackers@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: making users modem dial from webpage In-Reply-To: Message from Leif Neland of "Tue, 16 Nov 1999 23:34:58 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 16 Nov 1999 23:23:51 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've been asked if this is possible: > > Having a webserver running a database of some sort. > User clicks a button on a form, a cgi-script runs, determines the ip of > the user, and sends a command to "something" on the users pc, which then > sends commands to a modem, making it dial a number. > > So our salespeople can dial directly from the database. > > This "something", could this be a java-applet, or should it be an > active-x? Or something completely different? It could be a pppctl(8) command. [.....] -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 19:20: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from f434.n5020.z2.fidonet.org (host5.mtelecom.ru [212.44.147.5]) by hub.freebsd.org (Postfix) with ESMTP id 3C27514A16 for ; Tue, 16 Nov 1999 19:19:37 -0800 (PST) (envelope-from seva@mtelecom.ru) Received: from mtelecom.ru (p1 [192.168.44.37]) by f434.n5020.z2.fidonet.org (8.8.8/8.8.8) with ESMTP id GAA20032 for ; Wed, 17 Nov 1999 06:21:27 +0300 (MSK) (envelope-from seva@mtelecom.ru) Message-ID: <383222DF.164E86DB@mtelecom.ru> Date: Wed, 17 Nov 1999 06:37:12 +0300 From: Seva "Semenov" X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: fifo's select in 3.3 RELEASE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSD 3.3 and 3.2 RELEASE. fifo has nothing to read, why select(2) return > 0 without timeout? in freeBSD 2.2.X select(2) return 0 (timeout) as expected. # mkfifo fifo # cat readfifo.c #include #include #include #include #include #include #include #include int main() { int fd; fprintf(stderr,"opening fifo\n"); if((fd=open("fifo",O_RDONLY|O_NONBLOCK))<0) err(errno,"can't open fifo"); fprintf(stderr,"fifo opend\n"); for(;;){ fd_set fds; int r; struct timeval tv; size_t s; char b[64]; tv.tv_sec=5; tv.tv_usec=0; FD_ZERO(&fds); FD_SET(fd,&fds); r=select(FD_SETSIZE,&fds,NULL,NULL,&tv); if(r<0) err(errno,"select return %d ",r); if(r==0){ perror("timeout"); continue; } fprintf(stderr,"start reading\n"); s=read(fd,b,63); if(s<0) err(errno,"read fifo return %d",s); if(!s){ perror("read null bites"); continue; } puts(b); } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 20:41:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from orange.kame.net (orange.kame.net [203.178.141.194]) by hub.freebsd.org (Postfix) with ESMTP id 59BFE14FF7; Tue, 16 Nov 1999 20:41:05 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from localhost (kame209.kame.net [203.178.141.209]) by orange.kame.net (8.9.1+3.1W/3.7W) with ESMTP id NAA17591; Wed, 17 Nov 1999 13:40:43 +0900 (JST) To: phk@critter.freebsd.dk Cc: beyssac@enst.fr Cc: freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Should jail treat ip-number? In-Reply-To: <19991110025853X.shin@nd.net.fujitsu.co.jp> References: <19991110022852N.shin@nd.net.fujitsu.co.jp> <24337.942169052@critter.freebsd.dk> <19991110025853X.shin@nd.net.fujitsu.co.jp> <19991110013913.A5181@enst.fr> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991117134132S.shin@nd.net.fujitsu.co.jp> Date: Wed, 17 Nov 1999 13:41:32 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 59 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm not against adding IPv6 functionality to jail(2), my point is > > merely that until somebody who has sufficient time & ability to > > fiddle with it does it, it's not going to happen. > > > > The usual rule applies: > > > > "Great idea, why don't you send me patches which does this ?" > > OK, then I'll try making patches and send you. > My current Idea is that adding a new member, a pointer to > sockaddr to the jail structure, and leave current ip_number > member for backward compatibility. > (Also with associated changes in kernel and the jail command) > There's been a discussion a few weeks ago on freebsd-security on > this very matter. See attached mail below. > > The conclusion was that jail(2) should be fixed to use a sockaddr > instead of a 32 bit int to specify the address. > > That seems to be the first logical step, even before making jail(2) > IPv6-compliant. In implementing jail sockaddr extension trial, I found some problems, and now have an possible solution. problems: -Any process in a jail might want to use several protocol families at the same time. So jail(2) need to specify every adress of those possible address families. (AF_INET, AF_INET6, AF_IPX, AF_APPLETALK, and so on) To do this, jail structure need to have not only a sockaddr but several sockaddrs list, and they are specified via jail(2). But I don't like such a extension, because, -It is complicated. Error checking will be diffcult. -User interface will also become complicated, and difficult to use. -As already commented, checking those addresses which already specified by other jail'ed processes is necessary. solution: Don't specify addresses via jail(2), and let kernel select any non binded address. Loop in_ifaddr list and try in_pcblookup_hash() for each of addresses, just as in_pcbbind does it to search for non binded port. A weak point of this solution is that processes in a same jail won't be necessariliy binded to a same address, but does it matters? Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 21:21: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 8E6EF1520D for ; Tue, 16 Nov 1999 21:20:59 -0800 (PST) (envelope-from partha@cs.duke.edu) Received: from rodgers.cs.duke.edu (rodgers.cs.duke.edu [152.3.140.40]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id AAA11803 for ; Wed, 17 Nov 1999 00:20:57 -0500 (EST) Received: from localhost (partha@localhost) by rodgers.cs.duke.edu (8.8.5/8.6.9) with ESMTP id AAA03313 for ; Wed, 17 Nov 1999 00:20:57 -0500 (EST) X-Authentication-Warning: rodgers.cs.duke.edu: partha owned process doing -bs Date: Wed, 17 Nov 1999 00:20:57 -0500 (EST) From: "Parthasarathy M. Aji" To: freebsd-hackers@FreeBSD.ORG Subject: Ip _ fw.c In-Reply-To: <19991113204833.6CC121FCC@io.yi.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey, i want to do packet filtering and redirection through the kernel. Specifically, My application will be on an intermediate node, through which, I want to redirect every packet that comes through me to a different server. Would you know what files I might want to look into this( like ip_fw.c for eg) etc..? .. Partha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 21:58:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 7D97C14DCF; Tue, 16 Nov 1999 21: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.3/8.9.2) with ESMTP id GAA28860; Wed, 17 Nov 1999 06:58:16 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Yoshinobu Inoue Cc: beyssac@enst.fr, freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Should jail treat ip-number? In-reply-to: Your message of "Wed, 17 Nov 1999 13:41:32 +0900." <19991117134132S.shin@nd.net.fujitsu.co.jp> Date: Wed, 17 Nov 1999 06:58:16 +0100 Message-ID: <28858.942818296@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991117134132S.shin@nd.net.fujitsu.co.jp>, Yoshinobu Inoue writes: >solution: > Don't specify addresses via jail(2), and let kernel select > any non binded address. No, that doesn't work. People want to run servers so they want to know their IP for DNS. >A weak point of this solution is that processes in a same jail >won't be necessariliy binded to a same address, but does it >matters? Yes, that also matters, this is a administrative facility. -- 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-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 21:59:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id BDE90152B2 for ; Tue, 16 Nov 1999 21:59:16 -0800 (PST) (envelope-from julian@whistle.com) Received: from home.elischer.org (home.elischer.org [207.76.204.203]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id VAA70242; Tue, 16 Nov 1999 21:59:12 -0800 (PST) Date: Tue, 16 Nov 1999 21:59:17 -0800 (PST) From: Julian Elischer X-Sender: julian@home.elischer.org To: "Parthasarathy M. Aji" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Ip _ fw.c In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You can use the ipfw "fwd" command (man 8 ipfw) you need to also run ipfw 'fwd' commands on the servers otherwise they will send the packet back to it's original destination. alternatively you could have no real machine with that address but set a loopback interface to the target address on each machine so that each machine would accept the packet when it arrived. if you want to actually CHANGE the packet then I believe natd can do that but I've not done it. julian (p.s. tell more about your set-up and maybe I can be more specific) On Wed, 17 Nov 1999, Parthasarathy M. Aji wrote: > Hey, > i want to do packet filtering and redirection through the > kernel. Specifically, My application will be on an intermediate node, > through which, I want to redirect every packet that comes through me to a > different server. Would you know what files I might want to look into > this( like ip_fw.c for eg) etc..? .. > > Partha > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 22:12:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from orange.kame.net (orange.kame.net [203.178.141.194]) by hub.freebsd.org (Postfix) with ESMTP id 6D46314A2D; Tue, 16 Nov 1999 22:12:30 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from localhost (kame209.kame.net [203.178.141.209]) by orange.kame.net (8.9.1+3.1W/3.7W) with ESMTP id PAA18229; Wed, 17 Nov 1999 15:12:21 +0900 (JST) To: phk@critter.freebsd.dk Cc: beyssac@enst.fr, freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Should jail treat ip-number? In-Reply-To: <28858.942818296@critter.freebsd.dk> References: <19991117134132S.shin@nd.net.fujitsu.co.jp> <28858.942818296@critter.freebsd.dk> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991117151309T.shin@nd.net.fujitsu.co.jp> Date: Wed, 17 Nov 1999 15:13:09 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 12 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >solution: > > Don't specify addresses via jail(2), and let kernel select > > any non binded address. > > No, that doesn't work. People want to run servers so they want > to know their IP for DNS. Hmmm, I wish if I could just let jail(2) pass DNS name into the kernel, but the implementation in the kernel won't be easy nor clean.... Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 16 22:30:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from orange.kame.net (orange.kame.net [203.178.141.194]) by hub.freebsd.org (Postfix) with ESMTP id 8C3C014ECE; Tue, 16 Nov 1999 22:30:51 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from localhost (kame209.kame.net [203.178.141.209]) by orange.kame.net (8.9.1+3.1W/3.7W) with ESMTP id PAA18369; Wed, 17 Nov 1999 15:30:38 +0900 (JST) To: phk@critter.freebsd.dk Cc: beyssac@enst.fr, freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Should jail treat ip-number? In-Reply-To: <19991117151309T.shin@nd.net.fujitsu.co.jp> References: <19991117134132S.shin@nd.net.fujitsu.co.jp> <28858.942818296@critter.freebsd.dk> <19991117151309T.shin@nd.net.fujitsu.co.jp> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991117153126C.shin@nd.net.fujitsu.co.jp> Date: Wed, 17 Nov 1999 15:31:26 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 30 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Don't specify addresses via jail(2), and let kernel select > > > any non binded address. > > No, that doesn't work. People want to run servers so they want > > to know their IP for DNS. > Hmmm, I wish if I could just let jail(2) pass DNS name into > the kernel, but the implementation in the kernel won't be easy > nor clean.... Then I have a new proposal which might not be so clean but I think it is somewhat practical. -Only think about inet and inet6. Forget about other protocol family and sockaddr. (Just as current jail only think about inet.) -Just add an in6_addr structure(IPv6 address) member "ip6_number" into the jail structure. -Jail(2) specify "ip_number" and/or "ip6_number" into the kernel. -Kernel treat "ip6_number" as just a same kind of extension for IPv6 as "ip_number" for IPv4. -Jail(8) command can also accept DNS name, and then it resolve the name internally and, if A record is obtained, specify its address into "ip_number". if AAAA record is obtained, also specify its address into "ip6_number". Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 1:20:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id BFF9714C0B for ; Wed, 17 Nov 1999 01:20:08 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 752838 invoked from network); 17 Nov 1999 09:20:07 -0000 Received: from d125.paris-38.cybercable.fr (HELO cybercable.fr) ([212.198.38.125]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 17 Nov 1999 09:20:07 -0000 Message-ID: <38326564.E2784C42@cybercable.fr> Date: Wed, 17 Nov 1999 09:20:52 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer Cc: hackers@freebsd.org Subject: Re: netgraph into -stable. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > > I admit that it doesn't seem a minor addition, but > I'd like ot get netgraph down -nto 3.x now that it has been shaken down a > bit in 4.x > > reasons: > 1/ DSL in Canada is now switching rapidly to PPPoE. > 2/ PPP will start using it soon (other than with pppoe) > and we'd like ONE version not 2 for Brian to maintain. > 3/ ISPs who may wan tto use the PPPOE server side are generally running > 3.x, not 4.x Is there any doc on how to implement ISP-side PPPoE ? (or is it PPP over ATM, on the PVCs terminating the ADSL connections ?) TfH > > Supporting facts: > Netgraph is written to generally be non intrusive. > No code is changed in the non "options NETGRAPH" case and only minor > changes are made in normal code paths in the NETGRAPH case. > (with the exception of the if_sr and if_ar drivers) > > I might hold off on some of the more intrusive of those > changes (e.g. no real need to add it to netstat immediatly) > which will not really effect the functionality. > > And last but not least: > We are actually developing Netgraph under 3.3 so we are already keeping > two source trees in sync, 3.3. and 4.0 so we might as well let others get > at it. > > Anyone violently object? > > Julian > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 3: 7:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id C3B1214C5A for ; Wed, 17 Nov 1999 03:07:29 -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 3.040 #1) id 11o2vd-000Pzy-00; Wed, 17 Nov 1999 13:07:09 +0200 From: Sheldon Hearn To: Ollivier Robert Cc: hackers@freebsd.org Subject: Re: mode_perl DSO works on STABLE, not CURRENT In-reply-to: Your message of "Thu, 11 Nov 1999 00:45:52 +0100." <19991111004552.B44926@keltia.freenix.fr> Date: Wed, 17 Nov 1999 13:07:09 +0200 Message-ID: <99941.942836829@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 11 Nov 1999 00:45:52 +0100, Ollivier Robert wrote: > Your Perl binary is compiled without '-Wl,-E' (or > '-Wl,--export-dynamic'). Without this option the Perl binary doesn't > expoert its symbols thus preventing any dynamically loaded module to > use anything from the binary. Hi Ollivier, Thanks for your reply. I appreciate that this is a sticky one to get mixed up in. The thing is that the libperl.a which is compiled as part of the mod_perl installation _is_ linked with -E. So I'm not sure what else to look at. I've submitted PR 14924 with the details and a precise How-To-Repeat, so if you have any further suggestions, your feedback copied to freebsd-gnats-submit would be greatly appreciated. Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 3:34:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gw-nl4.philips.com (gw-nl4.philips.com [192.68.44.36]) by hub.freebsd.org (Postfix) with ESMTP id CE12714C38 for ; Wed, 17 Nov 1999 03:34:26 -0800 (PST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl4.philips.com with ESMTP id MAA18044 for ; Wed, 17 Nov 1999 12:34:24 +0100 (MET) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl4.philips.com via mwrap (4.0a) id xma018041; Wed, 17 Nov 99 12:34:25 +0100 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with SMTP id MAA28081 for ; Wed, 17 Nov 1999 12:34:23 +0100 (MET) Received: (qmail 70770 invoked by uid 666); 17 Nov 1999 11:34:45 -0000 Date: Wed, 17 Nov 1999 12:34:45 +0100 From: Jos Backus To: freebsd-hackers@FreeBSD.ORG Subject: Re: vmpfw in pine via NFS Message-ID: <19991117123445.B62132@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <199911160329.WAA92082@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from dwhite@resnet.uoregon.edu on Tue, Nov 16, 1999 at 10:03:07AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 16, 1999 at 10:03:07AM -0800, Doug White wrote: > If so you're breaking the cardinal rule of NFS: Never serve mail spools > via NFS. ...unless you're using the Maildir mailbox format and delivery protocol: http://cr.yp.to/proto/maildir.html -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 3:44:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from vitoria.ddsecurity.com.br (vitoria.ddsecurity.com.br [200.18.130.93]) by hub.freebsd.org (Postfix) with SMTP id F0CE714C38 for ; Wed, 17 Nov 1999 03:44:05 -0800 (PST) (envelope-from grios@ddsecurity.com.br) Received: (qmail 2121 invoked by uid 1001); 17 Nov 1999 11:42:13 -0000 From: "Gustavo Rios" Date: Wed, 17 Nov 1999 09:42:13 -0200 (EDT) To: freebsd-hackers@freebsd.org Subject: Included file errors Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am trying to compile a C source, but i get some strange error. In file included from stats.c:15: /usr/include/sys/socket.h:139: parse error before `u_char' /usr/include/sys/socket.h:139: warning: no semicolon at end of struct or union /usr/include/sys/socket.h:140: warning: data definition has no type or storage class /usr/include/sys/socket.h:142: parse error before `}' /usr/include/sys/socket.h:150: parse error before `u_short' /usr/include/sys/socket.h:150: warning: no semicolon at end of struct or union /usr/include/sys/socket.h:151: warning: data definition has no type or storage class /usr/include/sys/socket.h:266: parse error before `caddr_t' /usr/include/sys/socket.h:266: warning: no semicolon at end of struct or union /usr/include/sys/socket.h:267: warning: data definition has no type or storage class /usr/include/sys/socket.h:269: parse error before `msg_iovlen' /usr/include/sys/socket.h:269: warning: data definition has no type or storage class /usr/include/sys/socket.h:270: parse error before `msg_control' /usr/include/sys/socket.h:270: warning: data definition has no type or storage class /usr/include/sys/socket.h:271: parse error before `msg_controllen' /usr/include/sys/socket.h:271: warning: data definition has no type or storage class /usr/include/sys/socket.h:273: parse error before `}' /usr/include/sys/socket.h:293: parse error before `u_int' /usr/include/sys/socket.h:293: warning: no semicolon at end of struct or union /usr/include/sys/socket.h:297: parse error before `}' /usr/include/sys/socket.h:314: parse error before `pid_t' /usr/include/sys/socket.h:314: warning: no semicolon at end of struct or union /usr/include/sys/socket.h:315: warning: data definition has no type or storage class /usr/include/sys/socket.h:316: parse error before `cmcred_euid' /usr/include/sys/socket.h:316: warning: data definition has no type or storage class /usr/include/sys/socket.h:317: parse error before `cmcred_gid' /usr/include/sys/socket.h:317: warning: data definition has no type or storage class /usr/include/sys/socket.h:319: parse error before `cmcred_groups' /usr/include/sys/socket.h:319: warning: data definition has no type or storage class /usr/include/sys/socket.h:320: parse error before `}' /usr/include/sys/socket.h:343: parse error before `u_short' /usr/include/sys/socket.h:343: warning: no semicolon at end of struct or union /usr/include/sys/socket.h:345: parse error before `}' /usr/include/sys/socket.h:351: parse error before `caddr_t' /usr/include/sys/socket.h:351: warning: no semicolon at end of struct or union /usr/include/sys/socket.h:355: parse error before `msg_accrights' /usr/include/sys/socket.h:355: warning: data definition has no type or storage class /usr/include/sys/socket.h:357: parse error before `}' /usr/include/sys/socket.h:388: parse error before `recv' /usr/include/sys/socket.h:388: warning: data definition has no type or storage class /usr/include/sys/socket.h:389: parse error before `recvfrom' /usr/include/sys/socket.h:389: warning: data definition has no type or storage class /usr/include/sys/socket.h:390: parse error before `recvmsg' /usr/include/sys/socket.h:390: warning: data definition has no type or storage class ... ... ... In file included from stats.c:16: /usr/include/arpa/inet.h:89: warning: parameter has incomplete type /usr/include/arpa/inet.h:92: warning: parameter has incomplete type /usr/include/arpa/inet.h:96: warning: parameter has incomplete type BTW, i am running 3.3Stable. -- ADA, n.: Something you need only know the name of to be an Expert in Computing. Useful in sentences like, "We had better develop an ADA awareness." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 3:50: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id 44C6914FF3 for ; Wed, 17 Nov 1999 03:50:02 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id GAA05115; Wed, 17 Nov 1999 06:49:59 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id GAA16979; Wed, 17 Nov 1999 06:49:58 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id GAA01584; Wed, 17 Nov 1999 06:49:58 -0500 (EST) Date: Wed, 17 Nov 1999 06:49:58 -0500 (EST) From: Thomas David Rivers Message-Id: <199911171149.GAA01584@lakes.dignus.com> To: freebsd-hackers@FreeBSD.ORG, grios@ddsecurity.com.br Subject: Re: Included file errors In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You're missing a #include of - Dave R. - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 5:53:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 7053014D3B for ; Wed, 17 Nov 1999 05:53:34 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id CC1E51C6D; Wed, 17 Nov 1999 21:53:31 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Kelly Yancey Cc: Bill Studenmund , freebsd-hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? In-reply-to: Your message of "Tue, 16 Nov 1999 15:40:43 EST." Date: Wed, 17 Nov 1999 21:53:31 +0800 From: Peter Wemm Message-Id: <19991117135331.CC1E51C6D@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kelly Yancey wrote: [..] > For the list: while I was checking OpenBSD's kern_descrip.c to see > whether they zeroed the memory first, I noticed that they had the > following check that my 3.3-stable system does not: > > [ ... ] > /* Don't let non-root see generation numbers (for NFS security) */ > if (suser(p->p_ucred, &p->p_acflag)) ub.st_gen = 0; > [ perform copyout ... ] > > Is this a legitimate concern or paranoia? I see that we don't bother in > -current with it either. We do this too, but elsewhere... int vn_stat(vp, sb, p) { ... if (suser_xxx(p->p_ucred, 0, 0)) sb->st_gen = 0; else sb->st_gen = vap->va_gen; ... } Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 6:38:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 5078914A15 for ; Wed, 17 Nov 1999 06:38:42 -0800 (PST) (envelope-from babolo@links.ru) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id RAA18760; Wed, 17 Nov 1999 17:40:11 +0300 (MSK) Message-Id: <199911171440.RAA18760@aaz.links.ru> Subject: Re: making users modem dial from webpage In-Reply-To: from "Kelly Yancey" at "Nov 16, 99 05:45:41 pm" To: kbyanc@posi.net (Kelly Yancey) Date: Wed, 17 Nov 1999 17:40:11 +0300 (MSK) Cc: leifn@neland.dk, freebsd-hackers@FreeBSD.ORG From: "Aleksandr A.Babaylov" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kelly Yancey writes: > On Tue, 16 Nov 1999, Leif Neland wrote: > > I've been asked if this is possible: > > > > Having a webserver running a database of some sort. > > User clicks a button on a form, a cgi-script runs, determines the ip of > > the user, and sends a command to "something" on the users pc, which then > > sends commands to a modem, making it dial a number. > > > > So our salespeople can dial directly from the database. > > > > This "something", could this be a java-applet, or should it be an > > active-x? Or something completely different? > > I think that the security settings in most browsers would prevent an > object embedded in a page (such as a java applet or activeX control) from > this amount of system access. Just think of the implications otherwise: > maliscious people could put applets/activeX controls on a web page which > racked up long distance charges to some eastern European country. It is very easy: create file on server side with content-type x-application/x-dialout for example and dial information in it. configure helpers to start program 'dialout' for type x-application/x-dialout and write script 'dialout' which use dialing information from x-application/x-dialout files. All names are examples and can be changed as you want. But be careful when choose name for content-type Sorry bad English. I can to detaile if need (I am using similar methods sometimes) -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 6:53:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wally.eecs.harvard.edu (wally.eecs.harvard.edu [140.247.60.30]) by hub.freebsd.org (Postfix) with ESMTP id 352D51533A for ; Wed, 17 Nov 1999 06:53:20 -0800 (PST) (envelope-from stein@eecs.harvard.edu) Received: from localhost (stein@localhost) by wally.eecs.harvard.edu (8.8.6/8.8.6) with ESMTP id JAA17447 for ; Wed, 17 Nov 1999 09:53:19 -0500 (EST) Date: Wed, 17 Nov 1999 09:53:19 -0500 (EST) From: Christopher Stein To: freebsd-hackers@freebsd.org Subject: bdevsw ?? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could someone please tell me why bdevsw has disappeared from FreeBSD-current and what I should use for the block device switch. Thanks Chris Stein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 7:24:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id DD0FA1529C for ; Wed, 17 Nov 1999 07:24:46 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id BAA23659; Thu, 18 Nov 1999 01:54:34 +1030 (CST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991116205031.07184@mojave.sitaranetworks.com> Date: Tue, 16 Nov 1999 20:50:31 -0500 From: Greg Lehey To: Zhihui Zhang Cc: "Kenneth D. Merry" , freebsd-hackers@FreeBSD.ORG Subject: Re: Set the baud rate on remote debugging Reply-To: Greg Lehey References: <19991115175303.59865@mojave.sitaranetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from Zhihui Zhang on Mon, Nov 15, 1999 at 04:46:50PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 15 November 1999 at 16:46:50 -0500, Zhihui Zhang wrote: > > On Mon, 15 Nov 1999, Greg Lehey wrote: > >> On Monday, 15 November 1999 at 15:13:53 -0700, Kenneth D. Merry wrote: >>> Zhihui Zhang wrote... >>>> >>>> I have set up a remote debugging environment. But I think default 9600 >>>> bps is slow. I can use "set remotebaud 19200" on the debugging machine >>>> side. How can I set the baud rate on the target machine that is running >>>> the debugged kernel? (I press CTRL+ESC+ALT to drop to DDB mode and find >>>> no command to set the baud rate). >>>> >>>> Any help is appreciated. >>> >>> Use the CONSPEED option in the kernel config file on the target machine. >>> e.g.: >>> >>> options CONSPEED=115200 >> >> I'm planning to modify ddb to specify the bit rate as a parameter to >> the gdb command: >> >> db> gdb 19200 >> Next trap will enter GDB remote protocol mode at 19200 bps >> >> Comments? >> > > That will be useful. I have just found out that I can use sysctl -w > machdep.conspeed=19200 to achieve this. But I can not go higher than > 19200. I set 38400 today, but it ran very badly. I think 19200 is probably as high as you want to go, at least until somebody fixes the buffering in the UARTs. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 7:36:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 44CE214E09; Wed, 17 Nov 1999 07:36:41 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id IAA00291; Wed, 17 Nov 1999 08:59:04 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Yoshinobu Inoue Cc: beyssac@enst.fr, freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Should jail treat ip-number? In-reply-to: Your message of "Wed, 17 Nov 1999 15:31:26 +0900." <19991117153126C.shin@nd.net.fujitsu.co.jp> Date: Wed, 17 Nov 1999 08:59:03 +0100 Message-ID: <289.942825543@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991117153126C.shin@nd.net.fujitsu.co.jp>, Yoshinobu Inoue writes: >-Only think about inet and inet6. Forget about other protocol > family and sockaddr. > (Just as current jail only think about inet.) This has basically been the policy until now: Don't worry about a protocol until somebody needs it. >-Just add an in6_addr structure(IPv6 address) member > "ip6_number" into the jail structure. > >-Jail(2) specify "ip_number" and/or "ip6_number" into the kernel. Well, I guess we want it to be "and", right ? Will people want to bind both a IPv4 and IPv6 address (does it make sense to do so ?) or will people only need to bind one of them ? >-Kernel treat "ip6_number" as just a same kind of extension > for IPv6 as "ip_number" for IPv4. I'm not against them being sockaddr's. >-Jail(8) command can also accept DNS name, and then it resolve > the name internally and, > if A record is obtained, specify its address into "ip_number". > if AAAA record is obtained, also specify its address into "ip6_number". Sure, this is trivial to do. -- 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-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 7:54: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 1D63914EB0 for ; Wed, 17 Nov 1999 07:54:06 -0800 (PST) (envelope-from julian@whistle.com) Received: from home.elischer.org (home.elischer.org [207.76.204.203]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id HAA79720; Wed, 17 Nov 1999 07:53:59 -0800 (PST) Date: Wed, 17 Nov 1999 07:54:04 -0800 (PST) From: Julian Elischer X-Sender: julian@home.elischer.org To: Thierry Herbelot Cc: hackers@freebsd.org Subject: Re: netgraph into -stable. In-Reply-To: <38326564.E2784C42@cybercable.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 17 Nov 1999, Thierry Herbelot wrote: > Is there any doc on how to implement ISP-side PPPoE ? (or is it PPP over > ATM, on the PVCs terminating the ADSL connections ?) > > TfH Documenttion is on its way. The present pppoe man page will give some help but it is not complete yet. Brian is writing a pppoed to do the server side. Its not complete yet either. Julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 7:57:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id 604FD15346; Wed, 17 Nov 1999 07:57:04 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id CAA23775; Thu, 18 Nov 1999 02:26:59 +1030 (CST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991117105626.30085@mojave.sitaranetworks.com> Date: Wed, 17 Nov 1999 10:56:26 -0500 From: Greg Lehey To: Christopher Stein , FreeBSD current users Subject: Re: bdevsw ?? Reply-To: Greg Lehey References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from Christopher Stein on Wed, Nov 17, 1999 at 09:53:19AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [redirected to -CURRENT] Repeat after me: If I am running -CURRENT, I should be subscribed to -CURRENT, and that's where I should send my messages about -CURRENT. On Wednesday, 17 November 1999 at 9:53:19 -0500, Christopher Stein wrote: > > Could someone please tell me why bdevsw has disappeared > from FreeBSD-current Block devices are going away. > and what I should use for the block device switch. Probably nothing. It depends on what you want a block device switch for. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 9:51: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cx47987-b.escnd1.sdca.home.com (cx47987-b.escnd1.sdca.home.com [24.0.175.250]) by hub.freebsd.org (Postfix) with ESMTP id 60B7015267 for ; Wed, 17 Nov 1999 09:50:56 -0800 (PST) (envelope-from lomion@cx47987-b.escnd1.sdca.home.com) Received: from cx47987-c (cx47987-c.escnd1.sdca.home.com [24.0.175.251]) by cx47987-b.escnd1.sdca.home.com (8.9.3/8.9.3) with ESMTP id JAA55770 for ; Wed, 17 Nov 1999 09:40:47 -0800 (PST) (envelope-from lomion@cx47987-b.escnd1.sdca.home.com) Message-Id: <4.2.2.19991117095040.00ba9f00@mail.anais-nin.org> X-Sender: lomion@mail.anais-nin.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Wed, 17 Nov 1999 09:52:40 -0800 To: freebsd-hackers@FreeBSD.ORG From: lomion Subject: Re: making users modem dial from webpage In-Reply-To: <199911171440.RAA18760@aaz.links.ru> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05:40 PM 11/17/99 +0300, Aleksandr A.Babaylov wrote: >Kelly Yancey writes: > > On Tue, 16 Nov 1999, Leif Neland wrote: > > > I've been asked if this is possible: > > > > > > Having a webserver running a database of some sort. > > > User clicks a button on a form, a cgi-script runs, determines the ip of > > > the user, and sends a command to "something" on the users pc, which then > > > sends commands to a modem, making it dial a number. If they are dialed into an ISP how are they going to be able to dial otherwise? Or is this for internal use only? > > > > > > So our salespeople can dial directly from the database. > > > > > > This "something", could this be a java-applet, or should it be an > > > active-x? Or something completely different? you could do it with active X, but that limits your platform > > > > I think that the security settings in most browsers would prevent an > > object embedded in a page (such as a java applet or activeX control) from > > this amount of system access. Just think of the implications otherwise: > > maliscious people could put applets/activeX controls on a web page which > > racked up long distance charges to some eastern European country. This can be configured. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 9:55: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 04D5A14F47 for ; Wed, 17 Nov 1999 09:54:46 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id MAA09056; Wed, 17 Nov 1999 12:53:31 -0500 (EST) Message-Id: <199911171753.MAA09056@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Wed, 17 Nov 1999 12:50:09 -0500 To: Andrey Simonenko , hackers@FreeBSD.ORG From: Dennis Subject: Re: UNILOAD v.1.2 In-Reply-To: <37F23AED.586E8304@comsys.ntu-kpi.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG regarding loading over 1024 cylinder...does this work? Can someone provide a pointer? The URL previously provided on this list does not work. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 10:30:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id D46DE15288 for ; Wed, 17 Nov 1999 10:30:41 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com ([210.163.200.123]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id DAA24854; Thu, 18 Nov 1999 03:30:32 +0900 (JST) Message-ID: <3832E1AE.97FFFEF7@newsguy.com> Date: Thu, 18 Nov 1999 02:11:10 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Jos Backus Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vmpfw in pine via NFS References: <199911160329.WAA92082@cs.rpi.edu> <19991117123445.B62132@hal.mpn.cp.philips.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jos Backus wrote: > > On Tue, Nov 16, 1999 at 10:03:07AM -0800, Doug White wrote: > > If so you're breaking the cardinal rule of NFS: Never serve mail spools > > via NFS. > > ...unless you're using the Maildir mailbox format and delivery protocol: > > http://cr.yp.to/proto/maildir.html /me shivers at the thought of my (easily) 500+ new messages a day and hundreds of thousands of messages being stored one file for each message... -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Then again maybe not going to heaven would be a blessing. Relkin liked a certain amount of peace and harmony, since there'd been a pronounced shortage of them in his own life; however, nothing but peace and harmony, forever and forever? He wasn't sure about that. And no beer? Very dubious proposition." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 10:31:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 883F815047; Wed, 17 Nov 1999 10:31:23 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com ([210.163.200.123]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id DAA24919; Thu, 18 Nov 1999 03:30:48 +0900 (JST) Message-ID: <3832F11A.6D206BEC@newsguy.com> Date: Thu, 18 Nov 1999 03:16:58 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Yoshinobu Inoue Cc: phk@critter.freebsd.dk, beyssac@enst.fr, freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Should jail treat ip-number? References: <19991110022852N.shin@nd.net.fujitsu.co.jp> <24337.942169052@critter.freebsd.dk> <19991110025853X.shin@nd.net.fujitsu.co.jp> <19991110013913.A5181@enst.fr> <19991117134132S.shin@nd.net.fujitsu.co.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yoshinobu Inoue wrote: > > -As already commented, checking those addresses which > already specified by other jail'ed processes is necessary. I disagree. The address is specified by the admin of the machine. Letting him shoot himself in the foot is not particular bad, and the test can be performed by the userland tools used to manage the machine. > solution: > Don't specify addresses via jail(2), and let kernel select > any non binded address. > Loop in_ifaddr list and try in_pcblookup_hash() for each > of addresses, just as in_pcbbind does it to search for non > binded port. > > A weak point of this solution is that processes in a same jail > won't be necessariliy binded to a same address, but does it > matters? Ok, question: I "buy" a virtual server on the machine to run an internet daemon of mine. I need the IP to that server to access the daemon. How do the admin of the machine ensures that _my_ jail will have the fixed IP assigned to me always with your solution? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Then again maybe not going to heaven would be a blessing. Relkin liked a certain amount of peace and harmony, since there'd been a pronounced shortage of them in his own life; however, nothing but peace and harmony, forever and forever? He wasn't sure about that. And no beer? Very dubious proposition." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 11:18:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id CE7CF14EB7; Wed, 17 Nov 1999 11:18:42 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id UAA02423; Wed, 17 Nov 1999 20:18:42 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Date: Wed, 17 Nov 1999 20:18:41 +0100 Message-ID: <2417.942866321.1@critter.freebsd.dk> From: Poul-Henning Kamp Subject: Bumping libstdc++ version number MIME-Version: 1.0 Content-Type: multipart/digest; boundary="----- =_aaaaaaaaaa" Content-Description: Blind Carbon Copy Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------- =_aaaaaaaaaa Content-Type: message/rfc822 Content-Description: Original Message To: committer@freebsd.org Subject: Bumping libstdc++ version number From: Poul-Henning Kamp Date: Wed, 17 Nov 1999 20:18:41 +0100 Message-ID: <2417.942866321@critter.freebsd.dk> Sender: phk@critter.freebsd.dk MIME-Version: 1.0 The core team has discussed the issue of bumping the libstdc++ version numer because of the compiler upgrade: Yes, we do have a rule saying ``only one bump per release'', and that rules still stands. But no rule without exception: Clearly what we're looking at here deserves a version number bump, and therefore -core hereby gives David O'Brien permission to do so. for -core, Poul-Henning Kamp -- 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! ------- =_aaaaaaaaaa-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 11:36:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from spirit.jaded.net (spirit.jaded.net [216.94.113.12]) by hub.freebsd.org (Postfix) with ESMTP id 48BE314A24 for ; Wed, 17 Nov 1999 11:36:48 -0800 (PST) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id OAA03140 for hackers@freebsd.org; Wed, 17 Nov 1999 14:38:00 -0500 (EST) Date: Wed, 17 Nov 1999 14:37:59 -0500 From: Dan Moschuk To: hackers@freebsd.org Subject: VAIO F270, ep0 and -current Message-ID: <19991117143759.A3011@spirit.jaded.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, I have been in light contact with Warner over the course of the last couple of weeks, and I am still at wits end with this one. Currently, my laptop (VAIO F270 with a 3Com 589E pcmcia nic card) runs 3.3-REL with the PAO hacks, and works near-perfect. However, I would love to use this machine as a development box, which means I should really be running current on it. Now, everything but pccard works, which fails with ENOTTY on the following ioctl() call: usr.sbin/pccard/pccardd/cardd.c, line 590: if (ioctl(sp->fd, PIOCSDRV, &drv)) { This is now the only thing holding me back. Anyone had a similar experience? Relevant configuration follows. pccard.conf -- io 0x240-0x360 irq 3 5 10 11 13 15 memory 0xd4000 96k card "3Com" "Megahertz 589E" config 0x1 "ep0" ? insert echo 3Com Megahertz Ethernet card inserted insert /etc/pccard_ether ep0 remove echo 3Com Megahertz Ethernet card removed remove /sbin/ifconfig ep0 delete the kernel config is a chopped down PCCARD Cheers, -- Dan Moschuk (TFreak!dan@freebsd.org) "Cure for global warming: One giant heatsink and dual fans!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 12:52:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 2DE0914DB4 for ; Wed, 17 Nov 1999 12:52:28 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id VAA26208; Wed, 17 Nov 1999 21:39:49 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA01866; Wed, 17 Nov 1999 20:43:46 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199911171943.UAA01866@yedi.iaf.nl> Subject: Re: vmpfw in pine via NFS In-Reply-To: <3832E1AE.97FFFEF7@newsguy.com> from "Daniel C. Sobral" at "Nov 18, 1999 2:11:10 am" To: dcs@newsguy.com (Daniel C. Sobral) Date: Wed, 17 Nov 1999 20:43:46 +0100 (CET) Cc: Jos.Backus@nl.origin-it.com, freebsd-hackers@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+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Daniel C. Sobral wrote ... > Jos Backus wrote: > > > > On Tue, Nov 16, 1999 at 10:03:07AM -0800, Doug White wrote: > > > If so you're breaking the cardinal rule of NFS: Never serve mail spools > > > via NFS. > > > > ...unless you're using the Maildir mailbox format and delivery protocol: > > > > http://cr.yp.to/proto/maildir.html > > /me shivers at the thought of my (easily) 500+ new messages a day > and hundreds of thousands of messages being stored one file for each > message... It's been done. It's called MS Exchange................. -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 13: 0:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id DC3A014F8C for ; Wed, 17 Nov 1999 13:00:31 -0800 (PST) (envelope-from hibma@skylink.it) Received: from skylink.it (va-185.skylink.it [194.185.55.185]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id WAA09013; Wed, 17 Nov 1999 22:01:05 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with SMTP id UAA00502; Wed, 17 Nov 1999 20:43:48 +0100 (CET) (envelope-from hibma@skylink.it) Date: Wed, 17 Nov 1999 20:43:48 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@henny.jrc.it Reply-To: Nick Hibma To: Greg Lehey Cc: "Kenneth D. Merry" , Zhihui Zhang , freebsd-hackers@FreeBSD.org Subject: Re: Set the baud rate on remote debugging In-Reply-To: <19991115175303.59865@mojave.sitaranetworks.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > db> gdb 19200 > Next trap will enter GDB remote protocol mode at 19200 bps > > Comments? Yes: Please do. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 13: 8:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 66DE914E05 for ; Wed, 17 Nov 1999 13:08:37 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id VAA01297; Wed, 17 Nov 1999 21:10:58 GMT (envelope-from dfr@nlsystems.com) Date: Wed, 17 Nov 1999 21:10:58 +0000 (GMT) From: Doug Rabson To: Greg Lehey Cc: Zhihui Zhang , "Kenneth D. Merry" , freebsd-hackers@freebsd.org Subject: Re: Set the baud rate on remote debugging In-Reply-To: <19991116205031.07184@mojave.sitaranetworks.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 16 Nov 1999, Greg Lehey wrote: > On Monday, 15 November 1999 at 16:46:50 -0500, Zhihui Zhang wrote: > > > > On Mon, 15 Nov 1999, Greg Lehey wrote: > > > >> On Monday, 15 November 1999 at 15:13:53 -0700, Kenneth D. Merry wrote: > >>> Zhihui Zhang wrote... > >>>> > >>>> I have set up a remote debugging environment. But I think default 9600 > >>>> bps is slow. I can use "set remotebaud 19200" on the debugging machine > >>>> side. How can I set the baud rate on the target machine that is running > >>>> the debugged kernel? (I press CTRL+ESC+ALT to drop to DDB mode and find > >>>> no command to set the baud rate). > >>>> > >>>> Any help is appreciated. > >>> > >>> Use the CONSPEED option in the kernel config file on the target machine. > >>> e.g.: > >>> > >>> options CONSPEED=115200 > >> > >> I'm planning to modify ddb to specify the bit rate as a parameter to > >> the gdb command: > >> > >> db> gdb 19200 > >> Next trap will enter GDB remote protocol mode at 19200 bps > >> > >> Comments? > >> > > > > That will be useful. I have just found out that I can use sysctl -w > > machdep.conspeed=19200 to achieve this. But I can not go higher than > > 19200. > > I set 38400 today, but it ran very badly. I think 19200 is probably > as high as you want to go, at least until somebody fixes the buffering > in the UARTs. I've always used 57600 and it seems to work fine... -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 13:25:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id D882A14FED for ; Wed, 17 Nov 1999 13:25:07 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id HAA24064; Thu, 18 Nov 1999 07:54:49 +1030 (CST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991117162411.27609@mojave.sitaranetworks.com> Date: Wed, 17 Nov 1999 16:24:11 -0500 From: Greg Lehey To: Doug Rabson Cc: Zhihui Zhang , "Kenneth D. Merry" , freebsd-hackers@freebsd.org Subject: Re: Set the baud rate on remote debugging Reply-To: Greg Lehey References: <19991116205031.07184@mojave.sitaranetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from Doug Rabson on Wed, Nov 17, 1999 at 09:10:58PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 17 November 1999 at 21:10:58 +0000, Doug Rabson wrote: > On Tue, 16 Nov 1999, Greg Lehey wrote: > >> On Monday, 15 November 1999 at 16:46:50 -0500, Zhihui Zhang wrote: >>> >>> On Mon, 15 Nov 1999, Greg Lehey wrote: >>> >>>> On Monday, 15 November 1999 at 15:13:53 -0700, Kenneth D. Merry wrote: >>>>> Zhihui Zhang wrote... >>>>>> >>>>>> I have set up a remote debugging environment. But I think default 9600 >>>>>> bps is slow. I can use "set remotebaud 19200" on the debugging machine >>>>>> side. How can I set the baud rate on the target machine that is running >>>>>> the debugged kernel? (I press CTRL+ESC+ALT to drop to DDB mode and find >>>>>> no command to set the baud rate). >>>>>> >>>>>> Any help is appreciated. >>>>> >>>>> Use the CONSPEED option in the kernel config file on the target machine. >>>>> e.g.: >>>>> >>>>> options CONSPEED=115200 >>>> >>>> I'm planning to modify ddb to specify the bit rate as a parameter to >>>> the gdb command: >>>> >>>> db> gdb 19200 >>>> Next trap will enter GDB remote protocol mode at 19200 bps >>>> >>>> Comments? >>>> >>> >>> That will be useful. I have just found out that I can use sysctl -w >>> machdep.conspeed=19200 to achieve this. But I can not go higher than >>> 19200. >> >> I set 38400 today, but it ran very badly. I think 19200 is probably >> as high as you want to go, at least until somebody fixes the buffering >> in the UARTs. > > I've always used 57600 and it seems to work fine... I think it depends on your UART hardware. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 13:30:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D31A11523C for ; Wed, 17 Nov 1999 13:30:11 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA08337; Wed, 17 Nov 1999 14:30:09 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA19083; Wed, 17 Nov 1999 14:30:22 -0700 (MST) Message-Id: <199911172130.OAA19083@harmony.village.org> To: Dennis Subject: Re: UNILOAD v.1.2 Cc: Andrey Simonenko , hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 17 Nov 1999 12:50:09 EST." <199911171753.MAA09056@etinc.com> References: <199911171753.MAA09056@etinc.com> Date: Wed, 17 Nov 1999 14:30:22 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911171753.MAA09056@etinc.com> Dennis writes: : regarding loading over 1024 cylinder...does this work? even w/o uniload, I've managed to get my FreeBSD partition to work on my Sony VAIO laptop. It starts at cylnder 2193... It all depends on the BIOS that you are using... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 13:32:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7067614F65 for ; Wed, 17 Nov 1999 13:32:14 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA08346; Wed, 17 Nov 1999 14:32:11 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA19103; Wed, 17 Nov 1999 14:32:28 -0700 (MST) Message-Id: <199911172132.OAA19103@harmony.village.org> To: Doug Rabson Subject: Re: Set the baud rate on remote debugging Cc: Greg Lehey , Zhihui Zhang , "Kenneth D. Merry" , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 17 Nov 1999 21:10:58 GMT." References: Date: Wed, 17 Nov 1999 14:32:28 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Doug Rabson writes: : I've always used 57600 and it seems to work fine... On some carefully hand picked machines, I run at 115200 w/o problems... Don't try this if your mcahines don't have good UARTs and can service the interrupts fast enough... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 13:52:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id CAD96152D0 for ; Wed, 17 Nov 1999 13:52:33 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id QAA01333; Wed, 17 Nov 1999 16:52:24 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <199911172152.QAA01333@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Wilko Bulte Cc: dcs@newsguy.com (Daniel C. Sobral), Jos.Backus@nl.origin-it.com, freebsd-hackers@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: vmpfw in pine via NFS References: <199911171943.UAA01866@yedi.iaf.nl> In-reply-to: Your message of "Wed, 17 Nov 1999 20:43:46 +0100." <199911171943.UAA01866@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Nov 1999 16:52:24 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > /me shivers at the thought of my (easily) 500+ new messages a day > > and hundreds of thousands of messages being stored one file for each > > message... > > It's been done. It's called MS Exchange................. You don't have to use vile language in public :-) MH has been storing mail in it's folders like this for years/decades. While it might be a little hard on the file system, it works great for the user. Sorta like emacs. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 15:26:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from schuimpje.snt.utwente.nl (schuimpje.snt.utwente.nl [130.89.238.4]) by hub.freebsd.org (Postfix) with ESMTP id 1C1D414C1D; Wed, 17 Nov 1999 15:26:50 -0800 (PST) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (wit395301.student.utwente.nl [130.89.235.121]) by schuimpje.snt.utwente.nl (Postfix) with ESMTP id D806628B2; Thu, 18 Nov 1999 00:26:49 +0100 (CET) Message-ID: <38333989.9C4A0383@vangelderen.org> Date: Thu, 18 Nov 1999 00:26:01 +0100 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.61 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp Cc: Yoshinobu Inoue , beyssac@enst.fr, freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Should jail treat ip-number? References: <289.942825543@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > >-Jail(2) specify "ip_number" and/or "ip6_number" into the kernel. > > Well, I guess we want it to be "and", right ? Will people want to > bind both a IPv4 and IPv6 address (does it make sense to do so ?) > or will people only need to bind one of them ? What about multiple IPv6 or IPv4 addresses per jail? It might be a good idea while Inoue-san is at it. Or is this an incredibly stupid question? Cheers, Jeroen -- Jeroen C. van Gelderen - jeroen@vangelderen.org Interesting read: http://www.vcnet.com/bms/ JLF To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 15:43:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id DB49B1523B; Wed, 17 Nov 1999 15:43:12 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id PAA23345; Wed, 17 Nov 1999 15:40:49 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199911172340.PAA23345@gndrsh.dnsmgr.net> Subject: Re: Should jail treat ip-number? In-Reply-To: <38333989.9C4A0383@vangelderen.org> from "Jeroen C. van Gelderen" at "Nov 18, 1999 00:26:01 am" To: jeroen@vangelderen.org (Jeroen C. van Gelderen) Date: Wed, 17 Nov 1999 15:40:49 -0800 (PST) Cc: phk@critter.freebsd.dk (Poul-Henning Kamp), shin@nd.net.fujitsu.co.jp (Yoshinobu Inoue), beyssac@enst.fr, freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Poul-Henning Kamp wrote: > > >-Jail(2) specify "ip_number" and/or "ip6_number" into the kernel. > > > > Well, I guess we want it to be "and", right ? Will people want to > > bind both a IPv4 and IPv6 address (does it make sense to do so ?) > > or will people only need to bind one of them ? > > What about multiple IPv6 or IPv4 addresses per jail? It might be a > good idea while Inoue-san is at it. Or is this an incredibly stupid > question? I don't know how technically difficult it would be to allow multiple IPv4 and IPv6 addresses per jail, but I can think of a few very good things to do with it. I spend a fair amount of time playing with routing protocols and it would be wonderful to be able to create jailed version of gated/zebra/rodscode on the same box and watch them interact. It would probably cut the size of my hardware lab used for this now in half or maybe even quarter it! -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 16:55: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 4F0EA1501E for ; Wed, 17 Nov 1999 16:54:59 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (loot.cs.rpi.edu [128.213.16.22]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id TAA48910; Wed, 17 Nov 1999 19:54:57 -0500 (EST) Message-Id: <199911180054.TAA48910@cs.rpi.edu> To: freebsd-hackers@freebsd.org Cc: crossd@cs.rpi.edu Subject: AMD wedging Date: Wed, 17 Nov 1999 19:47:41 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been noticing of late a disturbing trend of AMD wedging and eventually taking the entire system down. The WCHAN that it is locked in is "sbwait". I now have the luxury of having this happen on a non-critical system with DDB compiled in (the system is the one I am typing on now). How would I go about finding exactly what it is stuck on so I may correct the bug in the kernel or amd? -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 18:21: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 8AA1D1501B; Wed, 17 Nov 1999 18:20:58 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX9911-Fujitsu Gateway) id LAA20291; Thu, 18 Nov 1999 11:20:56 +0900 (JST) Received: from chisato.nd.net.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-9910-Fujitsu Domain Master) id LAA18211; Thu, 18 Nov 1999 11:20:56 +0900 (JST) Received: from localhost (dhcp7186.nd.net.fujitsu.co.jp [10.18.7.186]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id LAA21665; Thu, 18 Nov 1999 11:20:55 +0900 (JST) To: phk@critter.freebsd.dk Cc: beyssac@enst.fr, freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Should jail treat ip-number? In-Reply-To: <289.942825543@critter.freebsd.dk> References: <19991117153126C.shin@nd.net.fujitsu.co.jp> <289.942825543@critter.freebsd.dk> <199911172340.PAA23345@gndrsh.dnsmgr.net> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991118042404X.shin@nd.net.fujitsu.co.jp> Date: Thu, 18 Nov 1999 04:24:04 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 63 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >-Jail(2) specify "ip_number" and/or "ip6_number" into the kernel. > > Well, I guess we want it to be "and", right ? Will people want to > bind both a IPv4 and IPv6 address (does it make sense to do so ?) > or will people only need to bind one of them ? I also think it is "and", but maybe some time some application just use one of them and specify another familiy's addr as null. So I used "and/or". > > What about multiple IPv6 or IPv4 addresses per jail? It might be a > > good idea while Inoue-san is at it. Or is this an incredibly stupid > > question? > > I don't know how technically difficult it would be to allow multiple > IPv4 and IPv6 addresses per jail, but I can think of a few very good > things to do with it. I spend a fair amount of time playing with > routing protocols and it would be wonderful to be able to create > jailed version of gated/zebra/rodscode on the same box and watch > them interact. It would probably cut the size of my hardware lab > used for this now in half or maybe even quarter it! I'm not sure if multiple addrs for each address familiy will be useful or not. But at least, I think several other change(e.g. kernel routing table implementation change, or prepare several virtual ones on user-land) will also be necessary for several instances of each routing protocol implementation to operate on a system. > >-Kernel treat "ip6_number" as just a same kind of extension > > for IPv6 as "ip_number" for IPv4. > > I'm not against them being sockaddr's. I think it depends on if we allow multiple addrs per address family. If we don't allow it, I think sockaddr is not better, because, -Need to explicitely forbid multiple same families specification(e.g. either of sockaddr is AF_INET) as API. -Kernel side also need to check (1) case, and do some additional work. (return error, or prefer the former or the latter) -When more sockaddr's are added in the future, things will be more complicated. If we allow it(multiple addrs per address family), then I think sockaddr list pointer member, and total sockaddr's number member should be added, and they are searched in prison_ip(), prison_ip6() or such like that in kernel. But again, I'm not sure how multiple addrs per address family is useful. If explicit needs for "multiple addrs per address family" are not clear now, I would like to try to implement just adding ip6_number member for this time. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 20:17:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id A19D315060; Wed, 17 Nov 1999 20:17:09 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id UAA23680; Wed, 17 Nov 1999 20:16:48 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199911180416.UAA23680@gndrsh.dnsmgr.net> Subject: Re: Should jail treat ip-number? In-Reply-To: <19991118042404X.shin@nd.net.fujitsu.co.jp> from Yoshinobu Inoue at "Nov 18, 1999 04:24:04 am" To: shin@nd.net.fujitsu.co.jp (Yoshinobu Inoue) Date: Wed, 17 Nov 1999 20:16:48 -0800 (PST) Cc: phk@critter.freebsd.dk, beyssac@enst.fr, freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >-Jail(2) specify "ip_number" and/or "ip6_number" into the kernel. > > > > Well, I guess we want it to be "and", right ? Will people want to > > bind both a IPv4 and IPv6 address (does it make sense to do so ?) > > or will people only need to bind one of them ? > > I also think it is "and", but maybe some time some application > just use one of them and specify another familiy's addr as > null. So I used "and/or". > > > > What about multiple IPv6 or IPv4 addresses per jail? It might be a > > > good idea while Inoue-san is at it. Or is this an incredibly stupid > > > question? > > > > I don't know how technically difficult it would be to allow multiple > > IPv4 and IPv6 addresses per jail, but I can think of a few very good > > things to do with it. I spend a fair amount of time playing with > > routing protocols and it would be wonderful to be able to create > > jailed version of gated/zebra/rodscode on the same box and watch > > them interact. It would probably cut the size of my hardware lab > > used for this now in half or maybe even quarter it! > > I'm not sure if multiple addrs for each address familiy will > be useful or not. Just about anything usefull in a non jailed world is useful in a jailed world. Other applications for this would be a jailed NAT router, ability to jail our dual homed DNS and web services where everything is fully redundant right down to dual nics in every box, dual switches and 2 IP's on seperate blocks with DNS running on 2 boxes at 4 IP's. We do things for Telco's and they are really big into redundancy by dualality, and that means 2 IP's inside a jail, or 2 jails. > > But at least, I think several other change(e.g. kernel routing > table implementation change, or prepare several virtual ones > on user-land) will also be necessary for several instances of > each routing protocol implementation to operate on a system. Your correct, I had not taken that thought far enough to think about the fact that the kernel routing table is a shared resouce. Is it protected from modification by a jailed process? > > > >-Kernel treat "ip6_number" as just a same kind of extension > > > for IPv6 as "ip_number" for IPv4. > > > > I'm not against them being sockaddr's. > > I think it depends on if we allow multiple addrs per address > family. > > If we don't allow it, I think sockaddr is not better, because, > > -Need to explicitely forbid multiple same families > specification(e.g. either of sockaddr is AF_INET) as API. > > -Kernel side also need to check (1) case, and do some > additional work. > (return error, or prefer the former or the latter) > > -When more sockaddr's are added in the future, things will > be more complicated. > > If we allow it(multiple addrs per address family), then I > think sockaddr list pointer member, and total sockaddr's > number member should be added, and they are searched in > prison_ip(), prison_ip6() or such like that in kernel. > > But again, I'm not sure how multiple addrs per address family > is useful. > > If explicit needs for "multiple addrs per address family" are > not clear now, I would like to try to implement just adding > ip6_number member for this time. I think that this is probably the best path at this time. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 20:24: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 25A6C150EA for ; Wed, 17 Nov 1999 20:23:40 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id FAA21981 for freebsd-hackers@FreeBSD.ORG; Thu, 18 Nov 1999 05:23:29 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id C3CA38864; Thu, 18 Nov 1999 00:50:30 +0100 (CET) Date: Thu, 18 Nov 1999 00:50:30 +0100 From: Ollivier Robert To: freebsd-hackers@FreeBSD.ORG Subject: Re: vmpfw in pine via NFS Message-ID: <19991118005030.A33224@keltia.freenix.fr> Mail-Followup-To: freebsd-hackers@FreeBSD.ORG References: <3832E1AE.97FFFEF7@newsguy.com> <199911171943.UAA01866@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <199911171943.UAA01866@yedi.iaf.nl> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Wilko Bulte: > It's been done. It's called MS Exchange................. AFAIK, it is the opposite. M-Sexchange use one unique database for all mailboxes, making recovery of a lost message an "interesting" challenge. It is worse than the mbox format... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 22:13:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D478014A1F for ; Wed, 17 Nov 1999 22:13:48 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA09843; Wed, 17 Nov 1999 23:13:47 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA21369; Wed, 17 Nov 1999 23:14:08 -0700 (MST) Message-Id: <199911180614.XAA21369@harmony.village.org> To: "David E. Cross" Subject: Re: AMD wedging Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 17 Nov 1999 19:47:41 EST." <199911180054.TAA48910@cs.rpi.edu> References: <199911180054.TAA48910@cs.rpi.edu> Date: Wed, 17 Nov 1999 23:14:08 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911180054.TAA48910@cs.rpi.edu> "David E. Cross" writes: : I have been noticing of late a disturbing trend of AMD wedging and : eventually taking the entire system down. The WCHAN that it is locked in is : "sbwait". I now have the luxury of having this happen on a non-critical : system with DDB compiled in (the system is the one I am typing on now). : How would I go about finding exactly what it is stuck on so I may correct : the bug in the kernel or amd? -stable or -current? If -stable, then there is a well known bug that prevents AMD from NFS mounting local file systems. I have a kludge that is gross beyond words that I came up with, but haven't had a time to made it any less gross. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 22:46:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id C3C7C15320 for ; Wed, 17 Nov 1999 22:46:08 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id BAA57262; Thu, 18 Nov 1999 01:46:03 -0500 (EST) Message-Id: <199911180646.BAA57262@cs.rpi.edu> To: Warner Losh Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: AMD wedging In-Reply-To: Message from Warner Losh of "Wed, 17 Nov 1999 23:14:08 MST." <199911180614.XAA21369@harmony.village.org> Date: Thu, 18 Nov 1999 01:46:03 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199911180054.TAA48910@cs.rpi.edu> "David E. Cross" writes: > : I have been noticing of late a disturbing trend of AMD wedging and > : eventually taking the entire system down. The WCHAN that it is locked in is > : "sbwait". I now have the luxury of having this happen on a non-critical > : system with DDB compiled in (the system is the one I am typing on now). > : How would I go about finding exactly what it is stuck on so I may correct > : the bug in the kernel or amd? > > -stable or -current? If -stable, then there is a well known bug that > prevents AMD from NFS mounting local file systems. I have a kludge > that is gross beyond words that I came up with, but haven't had a time This is indeed -stable, but I do not believe that this is the bug. For one the machine does not have any NFS exports. Another is that we have 'host==' and 'host!=' entries in our amd maps, host!= are NFS mounts, host== are sym-links. Strangely enough on this system it came back by itself. I just needed to wait 30 minutes and *poof*, the problem went away. Any ideas? -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 22:50:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A8146152F8 for ; Wed, 17 Nov 1999 22:50:44 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA09960; Wed, 17 Nov 1999 23:50:44 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA22901; Wed, 17 Nov 1999 23:51:05 -0700 (MST) Message-Id: <199911180651.XAA22901@harmony.village.org> To: "David E. Cross" Subject: Re: AMD wedging Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 18 Nov 1999 01:46:03 EST." <199911180646.BAA57262@cs.rpi.edu> References: <199911180646.BAA57262@cs.rpi.edu> Date: Wed, 17 Nov 1999 23:51:05 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911180646.BAA57262@cs.rpi.edu> "David E. Cross" writes: : 30 minutes and *poof*, the problem went away. Any ideas? Contact Matt Dillon :-). The specific case that I hit he was able to help me with, but it is very definitely NFS client/server on the same machine only. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 23:42: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 3D142151C4 for ; Wed, 17 Nov 1999 23:42:04 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA78627; Wed, 17 Nov 1999 23:41:57 -0800 (PST) (envelope-from dillon) Date: Wed, 17 Nov 1999 23:41:57 -0800 (PST) From: Matthew Dillon Message-Id: <199911180741.XAA78627@apollo.backplane.com> To: Warner Losh Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: AMD wedging References: <199911180646.BAA57262@cs.rpi.edu> <199911180651.XAA22901@harmony.village.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :In message <199911180646.BAA57262@cs.rpi.edu> "David E. Cross" writes: :: 30 minutes and *poof*, the problem went away. Any ideas? : :Contact Matt Dillon :-). The specific case that I hit he was able to :help me with, but it is very definitely NFS client/server on the same :machine only. : :Warner In the cases where the kernel might be at fault you will see one or more processes stuck in an NFS wait state or a VM wait state. For example, stuck nfsd's or nfsiod's. If you don't see anything like that happening, then there is a good chance that the bug is in AMD itself. I think we've fixed most of the protocol hangs... there may still be problems with 'intr' mounts -- I recommend using only hard mounts. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 17 23:59:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 062AB151C4 for ; Wed, 17 Nov 1999 23:59:47 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA78788; Wed, 17 Nov 1999 23:59:46 -0800 (PST) (envelope-from dillon) Date: Wed, 17 Nov 1999 23:59:46 -0800 (PST) From: Matthew Dillon Message-Id: <199911180759.XAA78788@apollo.backplane.com> To: "David E. Cross" Cc: Doug White , "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: vmpfw in pine via NFS References: <199911161847.NAA07576@cs.rpi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> : :> :> Which FreeBSD release is being used here? What kind of NFS mount is :> being used (localhost mount?) : :Ok, I have some additional details, as I was able to mostly resolve the issue. : :Yes, mail is nfs exported, but that does not appear to be the issue in this :case. pine is run from nfs mounted "/usr/local" pine would hang every time :a user would go to send a composed message and wind up in "vmpfw". The "fix" :was to go to the NFS server for /usr/local and do "mv pine pine.old; cp :pine.old pine". This would (obviously) not affect any of the old pine's, it :would however allow any new pines to run w/o problems. Note that any access :to /usr/local/bin/pine.old on the client machine would result in a hang. :Specifically "file /usr/local/bin/pine.old" resulted in "vmpfw" as did "cmp" :and a couple of others. All of these worked just fine on the NFS server. :The release in question is 3.3-STABLE from this past Friday (Nov. 12). : :-- :David Cross | email: crossd@cs.rpi.edu pine does some really *bad* things with mmap(), as I recall. I'm trying to remember what the bug was. The thing to do is to run a debug kernel, and when you hit the problem do a 'ps axl' and locate all the processes that are 'stuck' in a state that they shouldn't be stuck in. It's almost certainly a deadlock somewhere. There should be more then one. Once you have identified the processes you can gdb the running kernel and get a backtrace of each stuck process: gdb -k kernel.debug /dev/mem proc XXX back proc YYY back ... I think the problem is related to pine's use of MAP_PRIVATE mmap's of mail files, and then going through and modifying every page as it scans the map. This causes a large number of write faults to occur and even though the copy-on-write's are creating private pages, vm_fault still winds up locking the underlying file. This can cause a deadlock to occur somewhere - I'm not exactly sure where. I recall that there are some VM-related situations where NFS can get into a deadlock due to side effects, but I don't recall it well enough to figure it out without some backtraces to work with. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 4: 1:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wit395301.student.utwente.nl (wit395301.student.utwente.nl [130.89.235.121]) by hub.freebsd.org (Postfix) with ESMTP id A2D9515105; Thu, 18 Nov 1999 04:01:53 -0800 (PST) (envelope-from jeroen@vangelderen.org) Received: from [10.235.121.14] (helo=vangelderen.org) by wit395301.student.utwente.nl with esmtp (Exim 2.05 #1) id 11oQCc-00056Q-00; Thu, 18 Nov 1999 12:58:14 +0100 Message-ID: <3833E9AB.13864ECA@vangelderen.org> Date: Thu, 18 Nov 1999 12:57:31 +0100 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.61 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Yoshinobu Inoue Cc: phk@critter.freebsd.dk, beyssac@enst.fr, freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Should jail treat ip-number? References: <19991117153126C.shin@nd.net.fujitsu.co.jp> <289.942825543@critter.freebsd.dk> <199911172340.PAA23345@gndrsh.dnsmgr.net> <19991118042404X.shin@nd.net.fujitsu.co.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yoshinobu Inoue wrote: > If explicit needs for "multiple addrs per address family" are > not clear now, I would like to try to implement just adding > ip6_number member for this time. I think sockaddrs are better because it allows you to change to multiple IP-support without changing the interface again. Or you can add IPX (whatever) support without disturbing existing applications... I'd say (but I'm not a real hacker) make jail accept a list of sockaddrs and -for now- disallow anything except a single IPv4 and a single IPv6 address in that list. I'm now pretty sure multiple IPs per jail is a good idea, but you can easily defer implementation to some point in the future... Cheers, Jeroen -- Jeroen C. van Gelderen - jeroen@vangelderen.org Interesting read: http://www.vcnet.com/bms/ JLF To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 6:53:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id D8F4D14CCD for ; Thu, 18 Nov 1999 06:53:11 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id JAA23579; Thu, 18 Nov 1999 09:52:56 -0500 (EST) Date: Thu, 18 Nov 1999 09:52:55 -0500 (EST) From: Bosko Milekic To: Julian Elischer Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf wait code (revisited) -- review? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Although I've presently received little feedback on this... I found a potential problem with the patch, so I am taking the following approach to bypass it. I have a feeling that there's another way, though (perhaps better, conceptually). Consider a case where there are 40 instances of tsleep all waiting for an mbuf to be freed. Consider a single mbuf beeing freed, this would awake _all_ the sleepers, the first one "queued" would succeed in the [retried] MGET whereas the other 39 will fail and return NULL (not necessarily having waited the designated mbuf_wait time). I am replacing the wakeup() in the wakeup procedure with a wakeup_one and adding an extra 'check' to the sleep procedures themselves. Thus, when the 'free' macro is used, the wakeup procedure is called, one sleep (the first one) is woken up, it tries the MGET, hopefully succeeds, and if it does, checks whether or not there are more free mbufs -- if that's the case, then another wakeup_one is done, etc. Note that the statement to zero out the number of 'waiting' instances in the wakeup function would be replaced by a decrement of that count. This approach adds some overhead (not much, though). Anybody know of a different [better] way? On Fri, 12 Nov 1999, Julian Elischer wrote: !>It looks pretty thorough but needs more examination that I have given it !>yet. !> !>On Fri, 12 Nov 1999, Bosko Milekic wrote: !> !>> !>> Hi, !>> !>> Attached are some diffs that provide a couple of wait routines in the !>> out-of-mbuf and/or out-of-mbuf-cluster case(s). The attached diffs are for -STABLE !>> and I would be greatful if somebody could review them/give feedback. I have diffs for !>> -CURRENT but am not posting them because I haven't had too much of a chance to test !>[...] !> !> !> !>To Unsubscribe: send mail to majordomo@FreeBSD.org !>with "unsubscribe freebsd-hackers" in the body of the message !> -- Bosko Milekic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 6:55:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 6E0D314CCD for ; Thu, 18 Nov 1999 06:55:28 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p12-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.141]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id XAA12524; Thu, 18 Nov 1999 23:55:00 +0900 (JST) Message-ID: <383412B5.142F74A3@newsguy.com> Date: Thu, 18 Nov 1999 23:52:37 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: "Louis A. Mamakos" Cc: Wilko Bulte , Jos.Backus@nl.origin-it.com, freebsd-hackers@FreeBSD.ORG Subject: Re: vmpfw in pine via NFS References: <199911171943.UAA01866@yedi.iaf.nl> <199911172152.QAA01333@whizzo.transsys.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Louis A. Mamakos" wrote: > > You don't have to use vile language in public :-) > > MH has been storing mail in it's folders like this for years/decades. While > it might be a little hard on the file system, it works great for the user. Works great? Seriously, how long does it take to open a folder with over a hundred thousand messages? I *do* have some folders like that. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Then again maybe not going to heaven would be a blessing. Relkin liked a certain amount of peace and harmony, since there'd been a pronounced shortage of them in his own life; however, nothing but peace and harmony, forever and forever? He wasn't sure about that. And no beer? Very dubious proposition." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 7:16: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gw0.boostworks.com (gw0.boostworks.com [194.167.81.213]) by hub.freebsd.org (Postfix) with ESMTP id 7CC86153FE for ; Thu, 18 Nov 1999 07:15:42 -0800 (PST) (envelope-from root@synx.com) Received: from synx.com (root@rn.synx.com [192.1.1.241]) by gw0.boostworks.com (8.9.1/8.9.1) with ESMTP id QAA38881; Thu, 18 Nov 1999 16:13:28 +0100 (CET) Message-Id: <199911181513.QAA38881@gw0.boostworks.com> Date: Thu, 18 Nov 1999 16:13:25 +0100 (CET) From: Remy Nonnenmacher Reply-To: remy@synx.com Subject: Re: mbuf wait code (revisited) -- review? To: bmilekic@dsuper.net Cc: julian@whistle.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18 Nov, Bosko Milekic wrote: > > Although I've presently received little feedback on this... > > I found a potential problem with the patch, so I am taking the following > approach to bypass it. I have a feeling that there's another way, though > (perhaps better, conceptually). > > Consider a case where there are 40 instances of tsleep all waiting for an mbuf > to be freed. Consider a single mbuf beeing freed, this would awake _all_ the > sleepers, the first one "queued" would succeed in the [retried] MGET whereas the > other 39 will fail and return NULL (not necessarily having waited the designated > mbuf_wait time). > > I am replacing the wakeup() in the wakeup procedure with a wakeup_one and adding >...... Another place where a wakeup_one would be of great interest is the point where multiple processes are select()ing on a listen socket. Every incoming connection wakes every process to have them returning to user mode, have one succeeding in accept() and N-1 failling and returning to select(). It have been identified as a key improvement for, eg Apache, but, AFAIK, there where no proposal to provide a solving feature (sysctl-ized) in FBSD (Some work have been done in Linux, since a well-known comparative benchmark offense). Would be even more usefull in SMP context. RN. IaM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 7:42:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 5932415098 for ; Thu, 18 Nov 1999 07:42:39 -0800 (PST) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id HAA15679; Thu, 18 Nov 1999 07:35:54 -0800 (PST) Message-Id: <199911181535.HAA15679@implode.root.com> To: remy@synx.com Cc: bmilekic@dsuper.net, julian@whistle.com, freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf wait code (revisited) -- review? In-reply-to: Your message of "Thu, 18 Nov 1999 16:13:25 +0100." <199911181513.QAA38881@gw0.boostworks.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 18 Nov 1999 07:35:54 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On 18 Nov, Bosko Milekic wrote: >> >> Although I've presently received little feedback on this... >> >> I found a potential problem with the patch, so I am taking the following >> approach to bypass it. I have a feeling that there's another way, though >> (perhaps better, conceptually). >> >> Consider a case where there are 40 instances of tsleep all waiting for an mbuf >> to be freed. Consider a single mbuf beeing freed, this would awake _all_ the >> sleepers, the first one "queued" would succeed in the [retried] MGET whereas the >> other 39 will fail and return NULL (not necessarily having waited the designated >> mbuf_wait time). >> >> I am replacing the wakeup() in the wakeup procedure with a wakeup_one and adding >>...... > >Another place where a wakeup_one would be of great interest is the >point where multiple processes are select()ing on a listen socket. Every >incoming connection wakes every process to have them returning to user >mode, have one succeeding in accept() and N-1 failling and returning to >select(). It have been identified as a key improvement for, eg Apache, >but, AFAIK, there where no proposal to provide a solving feature >(sysctl-ized) in FBSD (Some work have been done in Linux, since a >well-known comparative benchmark offense). Would be even more usefull >in SMP context. FreeBSD has used wakeup_one() for this purpose since I wrote wakeup_one(). In fact, it was the main reason I wrote it. Shortly after doing this the Apache Group changed to using file locking to coordinate access to the socket and we ended up back at square one in terms of the thundering herd. Someone needs to modify the file locking to use wakeup_one(), but that is not as trivial as it might first seem (think shared/exclusive locks and priority inversion). -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 7:42:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 620E815441 for ; Thu, 18 Nov 1999 07:42:55 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-3.enteract.com (dscheidt@shell-3.enteract.com [207.229.143.42]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id JAA54957; Thu, 18 Nov 1999 09:42:31 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Thu, 18 Nov 1999 09:42:31 -0600 (CST) From: David Scheidt To: "Daniel C. Sobral" Cc: "Louis A. Mamakos" , Wilko Bulte , Jos.Backus@nl.origin-it.com, freebsd-hackers@FreeBSD.ORG Subject: Re: vmpfw in pine via NFS In-Reply-To: <383412B5.142F74A3@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 18 Nov 1999, Daniel C. Sobral wrote: > "Louis A. Mamakos" wrote: > > > > You don't have to use vile language in public :-) > > > > MH has been storing mail in it's folders like this for years/decades. While > > it might be a little hard on the file system, it works great for the user. > > Works great? Seriously, how long does it take to open a folder with > over a hundred thousand messages? I *do* have some folders like > that. Ouch. Don't do that. The upside of MH and maildir format is that deleting an arbitrary message is much faster. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 8:22:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id BDBDE15460 for ; Thu, 18 Nov 1999 08:22:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id IAA85547; Thu, 18 Nov 1999 08:22:28 -0800 (PST) (envelope-from dillon) Date: Thu, 18 Nov 1999 08:22:28 -0800 (PST) From: Matthew Dillon Message-Id: <199911181622.IAA85547@apollo.backplane.com> To: David Greenman Cc: remy@synx.com, bmilekic@dsuper.net, julian@whistle.com, freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf wait code (revisited) -- review? References: <199911181535.HAA15679@implode.root.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG wakeup_one is really a very dangerous routine to use if you aren't careful. If the one process that is woken up does not do the correct thing (call wakeup_one again if it cannot immediately get the resource it was waiting on) you can lockup the system. I would not recommend using wakeup_one in anything but an integrated manner. That is, for example, if you were to encapsulate the mbuf wait-for-free and mbuf freeing code into their own routines you could then safely implement use of wakeup_one within those routines. But if you try to implement wakeup_one in all the myrid places where the mbuf code might interact in this manner, you create serious instability in the codebase. -Matt Matthew Dillon : :>On 18 Nov, Bosko Milekic wrote: :>> :>> Although I've presently received little feedback on this... :>> :>> I found a potential problem with the patch, so I am taking the following :>> approach to bypass it. I have a feeling that there's another way, though :>> (perhaps better, conceptually). :>> :>> Consider a case where there are 40 instances of tsleep all waiting for an mbuf :>> to be freed. Consider a single mbuf beeing freed, this would awake _all_ the :>> sleepers, the first one "queued" would succeed in the [retried] MGET whereas the :>> other 39 will fail and return NULL (not necessarily having waited the designated :>> mbuf_wait time). :>> :>> I am replacing the wakeup() in the wakeup procedure with a wakeup_one and adding :>>...... :> :>Another place where a wakeup_one would be of great interest is the :>point where multiple processes are select()ing on a listen socket. Every :>incoming connection wakes every process to have them returning to user :>mode, have one succeeding in accept() and N-1 failling and returning to :>select(). It have been identified as a key improvement for, eg Apache, :>but, AFAIK, there where no proposal to provide a solving feature :>(sysctl-ized) in FBSD (Some work have been done in Linux, since a :>well-known comparative benchmark offense). Would be even more usefull :>in SMP context. : : FreeBSD has used wakeup_one() for this purpose since I wrote wakeup_one(). :In fact, it was the main reason I wrote it. Shortly after doing this the Apache :Group changed to using file locking to coordinate access to the socket and :we ended up back at square one in terms of the thundering herd. Someone needs :to modify the file locking to use wakeup_one(), but that is not as trivial :as it might first seem (think shared/exclusive locks and priority inversion). : :-DG : :David Greenman :Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org :Creator of high-performance Internet servers - http://www.terasolutions.com :Pave the road of life with opportunities. : : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 8:49:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from devserv.devel.redhat.com (devserv.devel.redhat.com [207.175.42.156]) by hub.freebsd.org (Postfix) with ESMTP id 4434615167 for ; Thu, 18 Nov 1999 08:49:17 -0800 (PST) (envelope-from zab@zabbo.net) Received: from localhost (zab@localhost) by devserv.devel.redhat.com (8.8.7/8.8.7) with SMTP id LAA21863 for ; Thu, 18 Nov 1999 11:49:07 -0500 X-Authentication-Warning: devserv.devel.redhat.com: zab owned process doing -bs Date: Thu, 18 Nov 1999 11:49:07 -0500 (EST) From: Zach Brown X-Sender: zab@devserv.devel.redhat.com To: freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf wait code (revisited) -- review? In-Reply-To: <199911181535.HAA15679@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >(sysctl-ized) in FBSD (Some work have been done in Linux, since a > >well-known comparative benchmark offense). Would be even more usefull > >in SMP context. I don't think the wake-many problem was ever the cause of the poor numbers that comparitve benchmark unearthed. This is only a problem if you have a whole slew of children sitting around waiting for new connections, rather than doing real work. this sure isn't the environment a heavily loaded server is under :) If you're still curious, check out http://www.kegel.com/mindcraft_redux.html specifically http://kernelnotes.org/lnxlists/linux-kernel/lk_9906_04/msg01100.html -- zach - - - - - - 007 373 5963 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 9: 0:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9FADC15432 for ; Thu, 18 Nov 1999 09:00:08 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA85880; Thu, 18 Nov 1999 09:00:07 -0800 (PST) (envelope-from dillon) Date: Thu, 18 Nov 1999 09:00:07 -0800 (PST) From: Matthew Dillon Message-Id: <199911181700.JAA85880@apollo.backplane.com> To: Zach Brown Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf wait code (revisited) -- review? References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> >(sysctl-ized) in FBSD (Some work have been done in Linux, since a :> >well-known comparative benchmark offense). Would be even more usefull :> >in SMP context. : :I don't think the wake-many problem was ever the cause of the poor numbers :that comparitve benchmark unearthed. This is only a problem if you have a :whole slew of children sitting around waiting for new connections, rather :than doing real work. this sure isn't the environment a heavily loaded :server is under :) If you're still curious, check out : :http://www.kegel.com/mindcraft_redux.html : :specifically : :http://kernelnotes.org/lnxlists/linux-kernel/lk_9906_04/msg01100.html : :-- zach Well, the wake-many problem hit me several times at BEST both with Apache and with the WWW server I wrote. We had the problem under both FreeBSD and IRIX. These were heavily loaded web servers and the wakeup issue turned into an O(N^2) problem. Every time a connection was accepted it woke up N processes where N effectively scaled to the connection rate. For example, shellx (the IRIX box) was getting 40 connections/second and had over 600 active connections at any given moment. There would perhaps be 200 processes waiting to accept a new connection. Without a fix the result was 200x40 = 8000 wakeups/second which is significant. Not only that, but the wakeup's themselves were O(N) resulting in O(2*N^2) operation. All sorts of scaling problems occured inside the kernel! The solution Apache takes is to surround the accept() with a file lock so only one process blocks in accept() at any given point (the file lock uses wakeup_one and is safe). The solution that I took with BestWWWD was to have just one process accept all the connections and then have it dole the descriptor out to the appropriate sub-processes over a unix-domain socket. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 9: 2:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id CC23C153CF for ; Thu, 18 Nov 1999 09:02:27 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id JAA24804; Thu, 18 Nov 1999 09:01:39 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Thu, 18 Nov 1999 09:01:38 -0800 Date: Thu, 18 Nov 1999 09:01:38 -0800 (PST) From: Kip Macy X-Sender: kip@luna To: David Greenman Cc: remy@synx.com, bmilekic@dsuper.net, julian@whistle.com, freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf wait code (revisited) -- review? In-Reply-To: <199911181535.HAA15679@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: dg@root.com,remy@synx.com,bmilekic@dsuper.net,julian@whistle.com,freebsd-hackers@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > FreeBSD has used wakeup_one() for this purpose since I wrote wakeup_one(). > In fact, it was the main reason I wrote it. Shortly after doing this the Apache > Group changed to using file locking to coordinate access to the socket and It may not be understanding the dialog correctly, but it seems like optimizing FreeBSD for a poorly architected web server, however widely used, is a sub-optimal allocation of effort. -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 9:12:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from devserv.devel.redhat.com (devserv.devel.redhat.com [207.175.42.156]) by hub.freebsd.org (Postfix) with ESMTP id 6E5B21544C for ; Thu, 18 Nov 1999 09:12:07 -0800 (PST) (envelope-from zab@zabbo.net) Received: from localhost (zab@localhost) by devserv.devel.redhat.com (8.8.7/8.8.7) with SMTP id MAA22976 for ; Thu, 18 Nov 1999 12:12:06 -0500 X-Authentication-Warning: devserv.devel.redhat.com: zab owned process doing -bs Date: Thu, 18 Nov 1999 12:12:06 -0500 (EST) From: Zach Brown X-Sender: zab@devserv.devel.redhat.com To: freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf wait code (revisited) -- review? In-Reply-To: <199911181700.JAA85880@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, the wake-many problem hit me several times at BEST both with > Apache and with the WWW server I wrote. We had the problem under both > FreeBSD and IRIX. These were heavily loaded web servers and the wakeup > issue turned into an O(N^2) problem. Every time a connection was > accepted it woke up N processes where N effectively scaled to the > connection rate. For example, shellx (the IRIX box) was getting oh, I don't doubt that it can be a problem, just that it wasn't on the linux box I was playing with at the ZD retest of the mindcraft test. We didn't see the run queue go nuts, we just had plenty of proeccesses trying to do work. And they all were stuck waiting around for the single threaded tcp lock that was being highly contested with the 4 100mb interfaces going full steam with teeny httpd requests.. > The solution that I took with BestWWWD was to have just one process > accept all the connections and then have it dole the descriptor out to the > appropriate sub-processes over a unix-domain socket. *nod* I'd be interested in seeing bestwwwd, is the source available anywhere? phhttpd does this by changing who the sigio signal for incoming accepts gets delivered too.. after each accept it is handed to the next thread. -- zach - - - - - - 007 373 5963 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 9:43:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id A5BC015459 for ; Thu, 18 Nov 1999 09:43:38 -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.3/8.9.3) with ESMTP id JAA24159; Thu, 18 Nov 1999 09:43:35 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA02952; Thu, 18 Nov 1999 09:43:34 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 18 Nov 1999 09:43:34 -0800 (PST) Message-Id: <199911181743.JAA02952@vashon.polstra.com> To: sepotvin@videotron.ca Subject: Re: gas pseudo-ops In-Reply-To: <000001bf260d$837c8770$0100000a@stephanep.bishop> References: <000001bf260d$837c8770$0100000a@stephanep.bishop> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <000001bf260d$837c8770$0100000a@stephanep.bishop>, Stephane Potvin wrote: > > Do you think it would be possible to change the > .type ,@object > for > .type ,object > in gensetdef? By looking in the gas code I found that the assembler just > ignores the @ character. I think it would be much better to remove all of the platform-specific asm statements from gensetdefs and put them into a header . Gensetdefs would then emit an include of that header to get the needed definitions. This isn't very high on my personal priority list, though. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 10:31: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 754C5154DA for ; Thu, 18 Nov 1999 10:30:56 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA86634; Thu, 18 Nov 1999 10:30:54 -0800 (PST) (envelope-from dillon) Date: Thu, 18 Nov 1999 10:30:54 -0800 (PST) From: Matthew Dillon Message-Id: <199911181830.KAA86634@apollo.backplane.com> To: Zach Brown Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf wait code (revisited) -- review? References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :phhttpd does this by changing who the sigio signal for incoming accepts :gets delivered too.. after each accept it is handed to the next thread. : :-- zach Ugh. SIGIO is evil and should never be used. I tried using SIGIO for tty I/O many years ago and it was a total disaster - it used an unbelievable amount of cpu due to the signal overhead :-) I theoretically own the rights to BestWWWD if only I could find the piece of paper. It shouldn't be an issue any longer with Best/Verio, I'll see what can be done. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 10:35: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from devserv.devel.redhat.com (devserv.devel.redhat.com [207.175.42.156]) by hub.freebsd.org (Postfix) with ESMTP id 968AE154A8 for ; Thu, 18 Nov 1999 10:34:49 -0800 (PST) (envelope-from zab@zabbo.net) Received: from localhost (zab@localhost) by devserv.devel.redhat.com (8.8.7/8.8.7) with SMTP id NAA26505 for ; Thu, 18 Nov 1999 13:34:27 -0500 X-Authentication-Warning: devserv.devel.redhat.com: zab owned process doing -bs Date: Thu, 18 Nov 1999 13:34:27 -0500 (EST) From: Zach Brown X-Sender: zab@devserv.devel.redhat.com To: freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf wait code (revisited) -- review? In-Reply-To: <199911181830.KAA86634@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ugh. SIGIO is evil and should never be used. I tried using SIGIO for > tty I/O many years ago and it was a total disaster - it used an > unbelievable amount of cpu due to the signal overhead :-) blocked, queued real-time sigio with siginfo goop slurped sync via sigwaitinfo().. i think we've covered this :) > > I theoretically own the rights to BestWWWD if only I could find the piece > of paper. It shouldn't be an issue any longer with Best/Verio, I'll see > what can be done. I'm interested. -- zach - - - - - - 007 373 5963 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 10:39:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gw0.boostworks.com (gw0.boostworks.com [194.167.81.213]) by hub.freebsd.org (Postfix) with ESMTP id F39A915485 for ; Thu, 18 Nov 1999 10:39:44 -0800 (PST) (envelope-from root@synx.com) Received: from synx.com (root@rn.synx.com [192.1.1.241]) by gw0.boostworks.com (8.9.1/8.9.1) with ESMTP id TAA39896; Thu, 18 Nov 1999 19:39:29 +0100 (CET) Message-Id: <199911181839.TAA39896@gw0.boostworks.com> Date: Thu, 18 Nov 1999 19:39:26 +0100 (CET) From: Remy Nonnenmacher Reply-To: remy@synx.com Subject: Re: mbuf wait code (revisited) -- review? To: zab@zabbo.net Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18 Nov, Zach Brown wrote: > >> >(sysctl-ized) in FBSD (Some work have been done in Linux, since a >> >well-known comparative benchmark offense). Would be even more usefull >> >in SMP context. > > I don't think the wake-many problem was ever the cause of the poor numbers > that comparitve benchmark unearthed. This is only a problem if you have a > whole slew of children sitting around waiting for new connections, rather > than doing real work. this sure isn't the environment a heavily loaded > server is under :) If you're still curious, check out > > http://www.kegel.com/mindcraft_redux.html > > specifically > > http://kernelnotes.org/lnxlists/linux-kernel/lk_9906_04/msg01100.html > I agree that it is not the sole problem (as, for exemple, the discussions in the MC-redux shows that topics quickly went past the thundering herd) but it's a recurrent irritating (for mind) thing. Also, as the processes in a select/acccept loop will go user-mode, this means BGL contention in SMP, reducing the processing capacity to a single processor. I noticed that system activity tend to grow more quickly than user activity and these un-necessary wakeups are part of it. Am I wrong ? RN. IeM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 10:41:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 9BF2415490 for ; Thu, 18 Nov 1999 10:41:18 -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.3/8.9.3) with ESMTP id KAA24422; Thu, 18 Nov 1999 10:41:01 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA03119; Thu, 18 Nov 1999 10:40:59 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 18 Nov 1999 10:40:59 -0800 (PST) Message-Id: <199911181840.KAA03119@vashon.polstra.com> To: robert+freebsd@cyrus.watson.org Subject: Re: Portable way to compare struct stat's? In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Robert Watson wrote: > On Mon, 15 Nov 1999, Wes Peters wrote: > > > On a single system, if st_dev and st_ino are equal, you must be > > referring to the same object. If not, I'd like to hear about it. > > This assumption has always caused lots of pain and suffering for > distributed file system people -- in a distributed file system, the > requirement that you can generate a unique 32 bit number for each > file or directory visible in the FS is a fairly arduous one. I don't dispute that point, but it is worth mentioning that POSIX specifically guarantees that st_dev and st_ino "taken together uniquely identify the file within the system." So it is OK for applications to rely on that. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 11: 9:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 1A31F15654 for ; Thu, 18 Nov 1999 11:09:25 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id OAA07174; Thu, 18 Nov 1999 14:09:15 -0500 (EST) Date: Thu, 18 Nov 1999 14:09:13 -0500 (EST) From: Bosko Milekic To: Matthew Dillon Cc: David Greenman , remy@synx.com, julian@whistle.com, freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf wait code (revisited) -- review? In-Reply-To: <199911181622.IAA85547@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 18 Nov 1999, Matthew Dillon wrote: !> wakeup_one is really a very dangerous routine to use if you !> aren't careful. If the one process that is woken up does not !> do the correct thing (call wakeup_one again if it cannot !> immediately get the resource it was waiting on) you can lockup !> the system. !> !> I would not recommend using wakeup_one in anything but an !> integrated manner. That is, for example, if you were to !> encapsulate the mbuf wait-for-free and mbuf freeing code !> into their own routines you could then safely implement use !> of wakeup_one within those routines. But if you try to implement !> wakeup_one in all the myrid places where the mbuf code !> might interact in this manner, you create serious instability !> in the codebase. I'm not sure if you have read the [original] patch that I had posted about a week ago. Both the mbuf-wait and mbuf-cluster-wait routines (as well as their "wakeup" routines) are just that, separate routines. The sleep routines are called through the MGET, MGETHDR, and MCLALLOC macros, depending of course whether the sleep is for an mbuf or mbuf cluster. The place where wakeup() was originally called was also a routine that I defined in kern/uipc_mbuf.c and that was invoked through the macros that freed an mbuf or an mbuf chain (along with the mbuf clusters). The plan is to fiddle with those _new_ routines. !> !> -Matt !> Matthew Dillon !> !> -- Bosko Milekic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 11:13:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 37DCD154A2 for ; Thu, 18 Nov 1999 11:10:51 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id WAA55774; Wed, 17 Nov 1999 22:41:47 GMT (envelope-from nik) Date: Wed, 17 Nov 1999 22:41:47 +0000 From: Nik Clayton To: Julian Elischer Cc: hackers@freebsd.org Subject: Re: netgraph into -stable. Message-ID: <19991117224146.A55401@catkin.nothing-going-on.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Julian Elischer on Tue, Nov 16, 1999 at 05:28:48PM -0800 Organization: FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian (or anyone else on -hackers who can assist) On Tue, Nov 16, 1999 at 05:28:48PM -0800, Julian Elischer wrote: > I admit that it doesn't seem a minor addition, but > I'd like ot get netgraph down -nto 3.x now that it has been shaken down a > bit in 4.x Assuming this does go in, in time for 3.4, I'd like to mention this fact in a write up I'll be doing for Slashdot. Unfortunately, I'm hampered by not knowing what on Earth the netgraph code does? I know it was donated by Whistle, but that's about it. Could you give me a (150 - 200 words) overview of what this is, and why it's useful? Thanks, N -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 11:23:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id 2854815496; Thu, 18 Nov 1999 11:23:43 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id TAA86292; Thu, 18 Nov 1999 19:23:38 GMT (envelope-from joe) Date: Thu, 18 Nov 1999 19:23:38 +0000 From: Josef Karthauser To: Dan Moschuk Cc: hackers@FreeBSD.ORG Subject: Re: VAIO F270, ep0 and -current Message-ID: <19991118192338.D55314@florence.pavilion.net> References: <19991117143759.A3011@spirit.jaded.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19991117143759.A3011@spirit.jaded.net> X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got problems with F290 and ep0 and 'zzz' :) I've running a kernel from 20th Oct (FreeBSDCon ;) to solve it. It may be fixed more recently, but last week's kernel didn't solve it. Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 11:33:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id 83BE914E2C for ; Thu, 18 Nov 1999 11:32:53 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.3/8.9.1) id GAA23277; Fri, 19 Nov 1999 06:10:48 +1100 (EST) (envelope-from jb) Date: Fri, 19 Nov 1999 06:10:48 +1100 From: John Birrell To: John Polstra Cc: sepotvin@videotron.ca, hackers@FreeBSD.ORG Subject: Re: gas pseudo-ops Message-ID: <19991119061048.F13376@freebsd1.cimlogic.com.au> References: <000001bf260d$837c8770$0100000a@stephanep.bishop> <199911181743.JAA02952@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <199911181743.JAA02952@vashon.polstra.com>; from John Polstra on Thu, Nov 18, 1999 at 09:43:34AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 18, 1999 at 09:43:34AM -0800, John Polstra wrote: > In article <000001bf260d$837c8770$0100000a@stephanep.bishop>, > Stephane Potvin wrote: > > > > Do you think it would be possible to change the > > .type ,@object > > for > > .type ,object > > in gensetdef? By looking in the gas code I found that the assembler just > > ignores the @ character. > > I think it would be much better to remove all of the platform-specific > asm statements from gensetdefs and put them into a header > . Gensetdefs would then emit an include of that > header to get the needed definitions. gensetdefs also needs to act according to the machine and endian type it sees in the elf header, not the ones it was compiled for. Then it can be used as a cross-tool. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ john.birrell@cai.com john.birrell@opendirectory.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 12:29:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from awfulhak.org (dynamic-18.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.146]) by hub.freebsd.org (Postfix) with ESMTP id 97A25150E5; Thu, 18 Nov 1999 12:29:39 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id UAA02356; Thu, 18 Nov 1999 20:24:46 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id SAA00361; Thu, 18 Nov 1999 18:53:50 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199911181853.SAA00361@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Dan Moschuk Cc: hackers@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: VAIO F270, ep0 and -current In-Reply-To: Message from Dan Moschuk of "Wed, 17 Nov 1999 14:37:59 EST." <19991117143759.A3011@spirit.jaded.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Nov 1999 18:53:50 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > io 0x240-0x360 > irq 3 5 10 11 13 15 > memory 0xd4000 96k > card "3Com" "Megahertz 589E" > config 0x1 "ep0" ? [.....] FWIW, I've got: io 0x240-0x360 irq 10 11 13 memory 0xc0000 96k card "3Com Corporation" "3C589" config 0x1 "ep0" 11 [.....] so we don't share the same card..... but, I'd advise disabling your IrDA port - the default is to use irq3, which may conflict with your setup. I've also got device pcic0 at isa? irq 10 device pcic1 at isa? controller card0 in my kenrel config and get pcic-pci0: at device 10.0 on pci0 pcic-pci1: at device 10.1 on pci0 pcic0: at irq 10 on isa0 at boot time. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 12:59: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from spirit.jaded.net (spirit.jaded.net [216.94.113.12]) by hub.freebsd.org (Postfix) with ESMTP id BEE6E14C82 for ; Thu, 18 Nov 1999 12:59:07 -0800 (PST) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id QAA10120 for hackers@freebsd.org; Thu, 18 Nov 1999 16:00:21 -0500 (EST) Date: Thu, 18 Nov 1999 16:00:21 -0500 From: Dan Moschuk To: hackers@freebsd.org Subject: Re: VAIO F270, ep0 and -current Message-ID: <19991118160021.C8467@spirit.jaded.net> References: <19991117143759.A3011@spirit.jaded.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991117143759.A3011@spirit.jaded.net>; from dan@FreeBSD.ORG on Wed, Nov 17, 1999 at 02:37:59PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | Greetings, [snip] | usr.sbin/pccard/pccardd/cardd.c, line 590: | if (ioctl(sp->fd, PIOCSDRV, &drv)) { | | This is now the only thing holding me back. Anyone had a similar experience? | Relevant configuration follows. It's worth nothing that the problem is not ep0 specific. My 56k modem card (3COm 3CC156 B) also fails with the exact error message. -- Dan Moschuk (TFreak!dan@freebsd.org) "Cure for global warming: One giant heatsink and dual fans!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 13:33:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 4C5F5154EA; Thu, 18 Nov 1999 13:33:26 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 3AB311CD625; Thu, 18 Nov 1999 13:33:25 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Thu, 18 Nov 1999 13:33:25 -0800 (PST) From: Kris Kennaway To: Nik Clayton Cc: Julian Elischer , hackers@freebsd.org Subject: Re: netgraph into -stable. In-Reply-To: <19991117224146.A55401@catkin.nothing-going-on.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 17 Nov 1999, Nik Clayton wrote: > Assuming this does go in, in time for 3.4, I'd like to mention this fact > in a write up I'll be doing for Slashdot. Check ftp://ftp.whistle.com/pub/archie/netgraph/index.html - that should give you the information you need. Kris ---- Cthulhu for President! For when you're tired of choosing the _lesser_ of two evils.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 13:34:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A26A7154D0; Thu, 18 Nov 1999 13:34:40 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA12433; Thu, 18 Nov 1999 14:34:38 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA28043; Thu, 18 Nov 1999 14:35:07 -0700 (MST) Message-Id: <199911182135.OAA28043@harmony.village.org> To: Josef Karthauser Subject: Re: VAIO F270, ep0 and -current Cc: Dan Moschuk , hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 18 Nov 1999 19:23:38 GMT." <19991118192338.D55314@florence.pavilion.net> References: <19991118192338.D55314@florence.pavilion.net> <19991117143759.A3011@spirit.jaded.net> Date: Thu, 18 Nov 1999 14:35:07 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991118192338.D55314@florence.pavilion.net> Josef Karthauser writes: : I've got problems with F290 and ep0 and 'zzz' :) : I've running a kernel from 20th Oct (FreeBSDCon ;) to solve it. : : It may be fixed more recently, but last week's kernel didn't solve it. The suspend/card eject problem is still there. I've not found the time, energy or motivation to fix it. No body else has sent me patches either. I also don't have my laptop, but I could work around that if I were motivated to work on the old stuff. :-(. I'm bad, I like working on the new stuff more. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 13:36: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0DE6B154F0; Thu, 18 Nov 1999 13:36:04 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA12445; Thu, 18 Nov 1999 14:36:03 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA28063; Thu, 18 Nov 1999 14:36:32 -0700 (MST) Message-Id: <199911182136.OAA28063@harmony.village.org> To: Dan Moschuk Subject: Re: VAIO F270, ep0 and -current Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 18 Nov 1999 16:00:21 EST." <19991118160021.C8467@spirit.jaded.net> References: <19991118160021.C8467@spirit.jaded.net> <19991117143759.A3011@spirit.jaded.net> Date: Thu, 18 Nov 1999 14:36:32 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991118160021.C8467@spirit.jaded.net> Dan Moschuk writes: : | if (ioctl(sp->fd, PIOCSDRV, &drv)) { Do you have any cards that work? Are you 100% positive that your kernel and pccardd match? ENOTTY is returned only when the pccard driver doesn't know about the ioctl. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 13:53:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 419311518D; Thu, 18 Nov 1999 13:53:37 -0800 (PST) From: "Jonathan M. Bresler" To: dillon@apollo.backplane.com Cc: zab@zabbo.net, freebsd-hackers@FreeBSD.ORG In-reply-to: <199911181700.JAA85880@apollo.backplane.com> (message from Matthew Dillon on Thu, 18 Nov 1999 09:00:07 -0800 (PST)) Subject: Re: mbuf wait code (revisited) -- review? Message-Id: <19991118215337.419311518D@hub.freebsd.org> Date: Thu, 18 Nov 1999 13:53:37 -0800 (PST) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The solution that I took with BestWWWD was to have just one process > accept all the connections and then have it dole the descriptor out to the > appropriate sub-processes over a unix-domain socket. > > -Matt > yes. clearly, thats the way to go, to use the ability to pass a file descriptor over a unix-domain socket. one socket per handler (web server), and the process doing the accept doles out the work as each handler (web server) finishes a task and is ready to accept another task. in my memory, i can almost see the description of this problem and its resolution in a book on threads (i think). could it have been the addison-wesley swoosh book on threads by behlendorf? sigh...gotta get better memory installed. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 13:59: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 2D4A5154B7; Thu, 18 Nov 1999 13:58:59 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id NAA28127; Thu, 18 Nov 1999 13:58:59 -0800 (PST) Date: Thu, 18 Nov 1999 13:58:59 -0800 (PST) From: Julian Elischer To: Nik Clayton Cc: hackers@freebsd.org Subject: Re: netgraph into -stable. In-Reply-To: <19991117224146.A55401@catkin.nothing-going-on.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 17 Nov 1999, Nik Clayton wrote: > Assuming this does go in, in time for 3.4, I'd like to mention this fact > in a write up I'll be doing for Slashdot. It's in 3.x and being cleaned up. Not being compiled by default yet. > Unfortunately, I'm hampered by not knowing what on Earth the netgraph > code does? I know it was donated by Whistle, but that's about it. Could > you give me a (150 - 200 words) overview of what this is, and why it's > useful? for info on what it is, see: ftp://ftp.whistle.com/pub/archie/netgraph/index.html or in an http form: http://www.elischer.org/netgraph/index.html > > > Thanks, > > N > -- julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 14: 1:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from spirit.jaded.net (spirit.jaded.net [216.94.113.12]) by hub.freebsd.org (Postfix) with ESMTP id B6148154C2; Thu, 18 Nov 1999 14:01:17 -0800 (PST) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id RAA00602; Thu, 18 Nov 1999 17:02:34 -0500 (EST) Date: Thu, 18 Nov 1999 17:02:34 -0500 From: Dan Moschuk To: Warner Losh Cc: Dan Moschuk , hackers@FreeBSD.ORG Subject: Re: VAIO F270, ep0 and -current Message-ID: <19991118170234.B290@spirit.jaded.net> References: <19991118160021.C8467@spirit.jaded.net> <19991117143759.A3011@spirit.jaded.net> <19991118160021.C8467@spirit.jaded.net> <199911182136.OAA28063@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199911182136.OAA28063@harmony.village.org>; from imp@village.org on Thu, Nov 18, 1999 at 02:36:32PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | : | if (ioctl(sp->fd, PIOCSDRV, &drv)) { | | Do you have any cards that work? Are you 100% positive that your | kernel and pccardd match? ENOTTY is returned only when the pccard | driver doesn't know about the ioctl. | | Warner The steps I take are as follows: i) cvsup ii) make/make install usr.sbin/pccard iii) copy new pccard.conf into place iv) build and reboot new kernel If I've forgotten a step, please let me know. Thanks, -- Dan Moschuk (TFreak!dan@freebsd.org) "Cure for global warming: One giant heatsink and dual fans!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 14:17:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9A94715183; Thu, 18 Nov 1999 14:17:38 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA12599; Thu, 18 Nov 1999 15:17:37 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA28371; Thu, 18 Nov 1999 15:18:06 -0700 (MST) Message-Id: <199911182218.PAA28371@harmony.village.org> To: Dan Moschuk Subject: Re: VAIO F270, ep0 and -current Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 18 Nov 1999 17:02:34 EST." <19991118170234.B290@spirit.jaded.net> References: <19991118170234.B290@spirit.jaded.net> <19991118160021.C8467@spirit.jaded.net> <19991117143759.A3011@spirit.jaded.net> <19991118160021.C8467@spirit.jaded.net> <199911182136.OAA28063@harmony.village.org> Date: Thu, 18 Nov 1999 15:18:06 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991118170234.B290@spirit.jaded.net> Dan Moschuk writes: : The steps I take are as follows: : i) cvsup ia) make includes in src : ii) make/make install usr.sbin/pccard : iii) copy new pccard.conf into place : iv) build and reboot new kernel You need to make sure that you are compiling against the right kernel headers. Not that I'm saying that you are, just making sure. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 15:13:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id 8BD4B14A05 for ; Thu, 18 Nov 1999 15:13:26 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from videotron.ca ([207.253.0.113]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.07.30.00.05.p8) with ESMTP id <0FLF002621JBS4@falla.videotron.net> for hackers@freebsd.org; Thu, 18 Nov 1999 18:06:50 -0500 (EST) Date: Thu, 18 Nov 1999 17:06:30 -0500 From: "Stephane E. Potvin" Subject: Re: gas pseudo-ops To: John Polstra Cc: hackers@freebsd.org Message-id: <38347865.66F9D39@videotron.ca> MIME-version: 1.0 X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 4.0-CURRENT i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en References: <000001bf260d$837c8770$0100000a@stephanep.bishop> <199911181743.JAA02952@vashon.polstra.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > > In article <000001bf260d$837c8770$0100000a@stephanep.bishop>, > Stephane Potvin wrote: > > > > Do you think it would be possible to change the > > .type ,@object > > for > > .type ,object > > in gensetdef? By looking in the gas code I found that the assembler just > > ignores the @ character. > > I think it would be much better to remove all of the platform-specific > asm statements from gensetdefs and put them into a header > . Gensetdefs would then emit an include of that > header to get the needed definitions. > > This isn't very high on my personal priority list, though. Fair enough. Anyway, I'm currently using a local gensetdefs for the arm part as is done with the alpha instead of the default gensetdefs. So far it's working pretty well so I'll let it that way for the time being. Thanks for the answer though. Steph -- Stephane E. Potvin InnoMediaLogic Inc. - http://www.multichassis.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 15:25:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from spirit.jaded.net (spirit.jaded.net [216.94.113.12]) by hub.freebsd.org (Postfix) with ESMTP id 95A8A15463; Thu, 18 Nov 1999 15:25:12 -0800 (PST) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id SAA00289; Thu, 18 Nov 1999 18:25:54 -0500 (EST) Date: Thu, 18 Nov 1999 18:25:46 -0500 From: Dan Moschuk To: Warner Losh Cc: Dan Moschuk , hackers@FreeBSD.ORG Subject: Re: VAIO F270, ep0 and -current Message-ID: <19991118182546.A276@spirit.jaded.net> References: <19991118170234.B290@spirit.jaded.net> <19991118160021.C8467@spirit.jaded.net> <19991117143759.A3011@spirit.jaded.net> <19991118160021.C8467@spirit.jaded.net> <199911182136.OAA28063@harmony.village.org> <19991118170234.B290@spirit.jaded.net> <199911182218.PAA28371@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199911182218.PAA28371@harmony.village.org>; from imp@village.org on Thu, Nov 18, 1999 at 03:18:06PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | You need to make sure that you are compiling against the right kernel | headers. Not that I'm saying that you are, just making sure. | | Warner Doh! Are my cheeks red. After rebuilding /usr/include, and recompiling pccard all is well. Thanks! -- Dan Moschuk (TFreak!dan@freebsd.org) "Cure for global warming: One giant heatsink and dual fans!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 15:35: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from excalibur.lps.ens.fr (excalibur.lps.ens.fr [129.199.120.3]) by hub.freebsd.org (Postfix) with ESMTP id C95BD1553D; Thu, 18 Nov 1999 15:34:55 -0800 (PST) (envelope-from Thierry.Besancon@lps.ens.fr) Received: by excalibur.lps.ens.fr (8.9.3/jtpda-5.3.1) id AAA25614 ; Fri, 19 Nov 1999 00:34:53 +0100 (MET) Message-Id: <199911182334.AAA25614@excalibur.lps.ens.fr> From: Thierry.Besancon@lps.ens.fr (Thierry Besancon) Date: Fri, 19 Nov 1999 00:34:53 +0000 X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: freebsd-fs@freebsd.org, freebsd-hackers@freebsd.org Subject: crash in ffs_vptofh on diskless workstation Cc: dillon@freebsd.org, Ollivier.Robert@eurocontrol.fr, besancon@lps.ens.fr, Joel.Marchand@polytechnique.fr, Pierre.David@prism.uvsq.fr Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello I'm trying to build new X terminals for my lab. To do so I use FreeBSD 3.3-RELEASE. The X terminal is a diskless PC with 64 Mo of ram. It perfectly boots and I can launch the X server perfectly. Everything just runs fine. Except for one little piece of thing. As i wanted to make use of the floppy drive, I gave a look at floppyd part of mtools package. It implements what I want. While running the daemon, I encountered a problem. So I went debugging the C code of it. And so i found a bug in FreeBSD (?!). Here's the df of the diskless X terminal (i kept the ssh port in order to remotely connect and be able to look at the problem of floppyd) : Filesystem 1K-blocks Used Avail Capacity Mounted on 129.199.120.250:/ 127023 31651 85211 27% / mfs:29 959 668 215 76% /conf/etc /conf/etc 959 668 215 76% /etc 129.199.120.250:/usr 190543 153042 22258 87% /usr 129.199.120.250:/usr/local 2846396 1958786 659899 75% /usr/local mfs:61 3935 1431 2190 40% /var /var/tmp 3935 1431 2190 40% /tmp mfs:91 1511 47 1344 3% /dev It's the classical way FreeBSD 3.3 seems to make diskless run. The root filesystem is mounted through NFS and memory filesystems are created to store the live logs of the system. The mounts are read-only. The X terminal runs without any swap. /etc/rc.sysctl confirms it as well : sysctl -w vm.swap_enabled=0 The bug is just that when launching any executable residing in my mfs /tmp, it justs hangs the kernel. # cp /bin/ls /tmp # df /tmp/. Filesystem 1K-blocks Used Avail Capacity Mounted on /var/tmp 3935 1432 2189 40% /tmp # /tmp/ls (workstation freezes) Here's the panic : Fatal trap 12 : page fault while in kernel mode fault virtual address = 0x3e fault code = supervisor read, page not present instruction pointer = 0x8:0xc022bf14 stack pointer = 0x10:0xc4546bc8 frame pointer = 0x10:0xc4546ca4 code segment = base 0x0, list 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 precessor eflags = interrupt disabled, resume, IOPL = 0 current process = 355 (csh) interrupt mask = net tty bio cam kernel : type 12 trap, code = 0 Stopped at ffs_vptofh+0xfe0: cmpw $0x2,0x3e(%edx) and the trace : db> trace ffs_vptofh(c4546d5c,c4514300,1000,0,c4546cf4) at ffs_vptofh+0xfe0 end(c4546d5c) at 0xc087c485 vnode_pager_freepage(c4559a2c,c4546db8,1,0,c4546df8) at vnode_pager_freepage+0x556 vm_pager_get_pages(c4559a2c,c4546db8,1,0,c4546f18) at vm_pager_get_pages+0x1f exec_map_first_page(c4546e94,c44c55a8,c02fe464,0,4) at exec_map_first_page+0xba execve(c44c55a0,c4546f94,80922e0,80940000,8085000) at execve+0x19e syscall(27,27,8085000,8094000,bfbffbb0) at syscall+0x187 Xint0x80_syscall() at Xint0x80_syscall+0x2c (not too deep) Given I have no swap, it is not easy to supply vmcore. But I can provide any help as I can reproduce the crash at will. If someone has a clue on how to fix that... Thierry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 16:43:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id B646415567 for ; Thu, 18 Nov 1999 16:43:16 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id TAA73766; Thu, 18 Nov 1999 19:42:38 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <199911181840.KAA03119@vashon.polstra.com> References: <199911181840.KAA03119@vashon.polstra.com> Date: Thu, 18 Nov 1999 19:44:07 -0500 To: John Polstra , robert+freebsd@cyrus.watson.org From: Garance A Drosihn Subject: Re: Portable way to compare struct stat's? Cc: hackers@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:40 AM -0800 11/18/99, John Polstra wrote: >I don't dispute that point, but it is worth mentioning that POSIX >specifically guarantees that st_dev and st_ino "taken together >uniquely identify the file within the system." So it is OK for >applications to rely on that. Given how many people have files mounted from foreign file systems, I would think that applications should not rely on that. Sure, it's a nice guarantee for a completely stand-alone system, but a "general purpose" application should consider that it may be dealing with files in NFS, AFS, or some other file system, and plan accordingly. (here at RPI we have a lot of files in AFS space, and I've certainly seen problems because some application depended on that POSIX promise, but that POSIX promise is pretty meaningless in our real world. I would not want to encourage any programmer to depend on that, unless they are pretty much certain that the program will not have to deal with files from external file systems.) If the program is only for you in your organization, then the POSIX promise is helpful. If you're sending the code off to "the world", then you should not rely on that posix promise. Just my own opinion, of course. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 16:49:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 4B06E15705; Thu, 18 Nov 1999 16:48:45 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id QAA33477; Thu, 18 Nov 1999 16:48:41 -0800 (PST) Date: Thu, 18 Nov 1999 16:48:41 -0800 (PST) From: Julian Elischer To: stable@freebsd.org Cc: hackers@freebsd.org Subject: HEADS UP -stable Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You should do a 'config' again before making a kernel from -stable sources. No code changes will result but a new options file "opt_netgraph.h" will be required by if_ethersubr.c. an alternative is to do touch opt_netgraph.h in /sys/compile/MYKERNEL This will build an empty version of this file which will do just fine. (it would probably be empty anyhow). Julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 17: 2:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7988715018 for ; Thu, 18 Nov 1999 17:02:33 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA88661; Thu, 18 Nov 1999 17:02:28 -0800 (PST) (envelope-from dillon) Date: Thu, 18 Nov 1999 17:02:28 -0800 (PST) From: Matthew Dillon Message-Id: <199911190102.RAA88661@apollo.backplane.com> To: Bosko Milekic Cc: David Greenman , remy@synx.com, julian@whistle.com, freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf wait code (revisited) -- review? References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : I'm not sure if you have read the [original] patch that I had posted :about a week ago. Both the mbuf-wait and mbuf-cluster-wait routines (as well :as their "wakeup" routines) are just that, separate routines. The sleep :routines are called through the MGET, MGETHDR, and MCLALLOC macros, :depending of course whether the sleep is for an mbuf or mbuf cluster. : The place where wakeup() was originally called was also a routine :that I defined in kern/uipc_mbuf.c and that was invoked through the macros :that freed an mbuf or an mbuf chain (along with the mbuf clusters). : The plan is to fiddle with those _new_ routines. Sounds like a reasonable plan. I wonder if we should consider getting rid of the mbuf macros entirely and simply proceduralizing them. Then everything could be collected together into a single file. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 18:56:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 4B05C1558A for ; Thu, 18 Nov 1999 18:56:14 -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.3/8.9.3) with ESMTP id SAA26447; Thu, 18 Nov 1999 18:56:12 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id SAA04873; Thu, 18 Nov 1999 18:56:11 -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: Thu, 18 Nov 1999 18:56:11 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Garance A Drosihn Subject: Re: Portable way to compare struct stat's? Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garance A Drosihn wrote: > At 10:40 AM -0800 11/18/99, John Polstra wrote: >>I don't dispute that point, but it is worth mentioning that POSIX >>specifically guarantees that st_dev and st_ino "taken together >>uniquely identify the file within the system." So it is OK for >>applications to rely on that. > > Given how many people have files mounted from foreign file systems, > I would think that applications should not rely on that. Sure, it's > a nice guarantee for a completely stand-alone system, but a "general > purpose" application should consider that it may be dealing with > files in NFS, AFS, or some other file system, and plan accordingly. We must be interpreting the requirement differently, because it doesn't seem onerous at all to me. The st_dev value needn't be the same on two different hosts which both mount the same filesystem. I also doubt that the requirement has to hold across remounts. Under that interpretation, it's simple to meet the requirement. Just create a locally-unique st_dev value whenever you mount a filesystem, and if the filesystem is remote then record a mapping between (remote hostname, remote host's idea of the "device") and the local st_dev value. (I've never used AFS, so I may be missing something crucial here.) > If the program is only for you in your organization, then the > POSIX promise is helpful. If you're sending the code off to "the > world", then you should not rely on that posix promise. Just my own > opinion, of course. Well, the POSIX requirement isn't optional. If a system doesn't meet it then it is not POSIX-compliant. So any application that is targeted toward POSIX systems is perfectly within its rights to rely on the requirement. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 19:16:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id E3DC4155B6 for ; Thu, 18 Nov 1999 19:16:39 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id WAA09726; Thu, 18 Nov 1999 22:16:37 -0500 (EST) Date: Thu, 18 Nov 1999 22:16:37 -0500 (EST) From: Bosko Milekic To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf wait code (revisited) -- review? In-Reply-To: <199911190102.RAA88661@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 18 Nov 1999, Matthew Dillon wrote: !> !> Sounds like a reasonable plan. I wonder if we should consider getting !> rid of the mbuf macros entirely and simply proceduralizing them. Then !> everything could be collected together into a single file. !> !> -Matt !> Matthew Dillon !> !> Well, the macros are there, as commented in uipc_mbuf.c, "for critical paths." Ultimately, having them available as macros reduces some overhead. They are also, however, available as procedures (defined in uipc_mbuf.c). The procedures actually almost act as 'wrappers' for the macros because they really just end up running these macros. On what I believe emphasis should be placed upon is making sure that ALL the code using either the macros of the procedures doesn't automatically 'assume' that they will succeed, even if the call is made with M_WAIT. If the [new] diffs that I have sitting here are committed, then that should become the focus. There still seems to be plenty of code, especially around sys/nfs that 'assumes' this 'guaranteed success,' and because of that, problems arise. Bosko. -- Bosko Milekic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 22:26:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 89F57151BD for ; Thu, 18 Nov 1999 22:26:46 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id WAA26623 for ; Thu, 18 Nov 1999 22:26:46 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id WAA01876; Thu, 18 Nov 1999 22:26:45 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA19534; Thu, 18 Nov 99 22:26:41 PST Message-Id: <3834EDA0.4C0E0EF7@softweyr.com> Date: Thu, 18 Nov 1999 23:26:40 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: hackers@freebsd.org Subject: Making a port kit Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, so I finally got around to crafting up a port kit for my obliterate program, since it's been getting some notice once again. I have one little problem left. When I "make install" I get the following snivels: root@homer# make install ===> Installing for obliterate-0.3 install -c -s -o root -g wheel -m 555 obliterate /usr/local/bin install -c -o root -g wheel -m 444 obliterate.8.gz /usr/local/man8 ===> Generating temporary packing list ===> Compressing manual pages for obliterate-0.3 /usr/local/man//man8/obliterate.8: No such file or directory *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Oops. My Makefile is pretty trivial, borrowed from another simple port. It contains: CFLAGS= -g PROG= obliterate SRCS= obliterate.c MAN8= obliterate.8 BINDIR= ${PREFIX}/bin MANDIR= ${PREFIX}/man .include This is the Makefile in the work directory. Any help? This is the last stumble before committing this and getting several people off my back. Also, how do I go about adding the source archive to the FreeBSD collection, rather than leaving it on my ftp server? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 22:30:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 3F2C6151BD for ; Thu, 18 Nov 1999 22:30:41 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id RAA18042; Fri, 19 Nov 1999 17:00:25 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [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: <3834EDA0.4C0E0EF7@softweyr.com> Date: Fri, 19 Nov 1999 17:00:25 +1030 (CST) From: "Daniel O'Connor" To: Wes Peters Subject: RE: Making a port kit Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Nov-99 Wes Peters wrote: > install -c -o root -g wheel -m 444 obliterate.8.gz /usr/local/man8 This should install to /usr/local/man/man8 > /usr/local/man//man8/obliterate.8: No such file or directory --- 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-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 18 23:33:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from beebite.ugh.net.au (beebite.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id E827314DCB for ; Thu, 18 Nov 1999 23:33:24 -0800 (PST) (envelope-from andrew@ugh.net.au) Received: by beebite.ugh.net.au (Postfix, from userid 1000) id 083D41DA; Fri, 19 Nov 1999 18:33:23 +1100 (EST) Received: from localhost (localhost [127.0.0.1]) by beebite.ugh.net.au (Postfix) with ESMTP id E4EBE195; Fri, 19 Nov 1999 17:33:23 +1000 (EST) Date: Fri, 19 Nov 1999 17:33:23 +1000 (EST) From: andrew@ugh.net.au To: Daniel O'Connor Cc: Wes Peters , hackers@freebsd.org Subject: RE: Making a port kit In-Reply-To: Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 19 Nov 1999, Daniel O'Connor wrote: > On 19-Nov-99 Wes Peters wrote: > > install -c -o root -g wheel -m 444 obliterate.8.gz /usr/local/man8 > > This should install to /usr/local/man/man8 ..and if the page is compressed already you need to set: MANCOMPRESSED= yes Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 19 8:13:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 208271565D for ; Fri, 19 Nov 1999 08:13:46 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id IAA01325; Fri, 19 Nov 1999 08:12:46 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id IAA26632; Fri, 19 Nov 1999 08:12:46 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA16760; Fri, 19 Nov 99 08:12:26 PST Message-Id: <383576E9.CD5A32D2@softweyr.com> Date: Fri, 19 Nov 1999 09:12:25 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: andrew@ugh.net.au Cc: "Daniel O'Connor" , hackers@freebsd.org Subject: Re: Making a port kit References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG andrew@ugh.net.au wrote: > > On Fri, 19 Nov 1999, Daniel O'Connor wrote: > > > On 19-Nov-99 Wes Peters wrote: > > > install -c -o root -g wheel -m 444 obliterate.8.gz /usr/local/man8 > > > > This should install to /usr/local/man/man8 > > ..and if the page is compressed already you need to set: > > MANCOMPRESSED= yes Actually, taking the MAN8= line out of the port Makefile fixed the problem. Thanks for the hints. I'll go commit this now, after checking with the Ports Wraith. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 19 8:30: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bomber.avantgo.com (ws1.avantgo.com [207.214.200.194]) by hub.freebsd.org (Postfix) with ESMTP id 0BD1215666 for ; Fri, 19 Nov 1999 08:29:57 -0800 (PST) (envelope-from scott@avantgo.com) Received: from river ([10.0.128.30]) by bomber.avantgo.com (Netscape Messaging Server 3.5) with SMTP id 377 for ; Fri, 19 Nov 1999 08:25:47 -0800 Message-ID: <030f01bf32ab$2d2c5620$1e80000a@avantgo.com> From: "Scott Hess" To: Subject: EINTR problems with multithreaded programs. Date: Fri, 19 Nov 1999 08:28:56 -0800 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_030C_01BF3268.1EFCBA10" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_030C_01BF3268.1EFCBA10 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit When using -pthread on FreeBSD3.3 to build a multithreaded program, I find that signals are delivered to all threads (see attached program). Specifically, if multiple threads are in blocking read calls, and a signal is handled, they will all receive -1 from the read and EINTR in errno. We're running MYSQL with a large number of connections (>1000), many of which are idle at any given time (in a blocking read), and MYSQL uses alarm signals in many places (it appears to be on a per-handled-query basis, but I've not been able to pin this down quite yet). The net result is that with many idle connections and many active connections, the idle connections get a _lot_ of EINTR. By default, MYSQL takes 10 EINTR in a row before dropping the connection - I've modified that upwards, but then substantial amounts of CPU time are spent catching the EINTR and throwing the thread back into the read (it's a relatively cheap operation - but might happen a couple hundred thousand times a second). I've tried using sigaction() in hopes of letting the system know that it can restart the interrupted read(), but that doesn't seem to do the trick in the attached program. Any other options? [Right now I'm seriously considering adding small sleeps to the EINTR case in MYSQL. At least then all the threads won't wake up on every signal. I know, I know, I should fix the use of signals, too, but that's going to take a couple more weeks of becoming one with the code.] Thanks, scott ------=_NextPart_000_030C_01BF3268.1EFCBA10 Content-Type: application/octet-stream; name="thread_EINTR.c" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="thread_EINTR.c" #include =0A= #include =0A= #include =0A= #include =0A= =0A= static void *reader( void *arg)=0A= {=0A= char buf[ 1024];=0A= int cc;=0A= int fd=3D(int)arg;=0A= =0A= while(1) {=0A= printf( "%p waiting for data\n", pthread_self());=0A= cc=3Dread( fd, buf, sizeof( buf));=0A= if( cc>=3D0) {=0A= printf( "%p got %d bytes\n", pthread_self(), cc);=0A= } else {=0A= printf( "%p saw errno=3D=3D%d/%s\n", pthread_self(), errno, = strerror( errno));=0A= }=0A= }=0A= return NULL;=0A= }=0A= =0A= static void signal_handler( int sig)=0A= {=0A= printf( "Got signal %d\n", sig);=0A= }=0A= =0A= void main( void)=0A= {=0A= int ii, cc=3D10;=0A= pthread_t child;=0A= =0A= #if 0=0A= signal( SIGUSR1, signal_handler);=0A= #else=0A= {=0A= struct sigaction sa=3D{ signal_handler, 0, SA_RESTART};=0A= sigaction( SIGUSR1, &sa, NULL);=0A= }=0A= #endif=0A= =0A= for( ii=3D0; ii To: Warner Losh Cc: Dan Moschuk , hackers@FreeBSD.ORG Subject: Re: VAIO F270, ep0 and -current Message-ID: <19991119172025.A97321@florence.pavilion.net> References: <19991118192338.D55314@florence.pavilion.net> <19991117143759.A3011@spirit.jaded.net> <19991118192338.D55314@florence.pavilion.net> <199911182135.OAA28043@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199911182135.OAA28043@harmony.village.org> X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 18, 1999 at 02:35:07PM -0700, Warner Losh wrote: > In message <19991118192338.D55314@florence.pavilion.net> Josef Karthauser writes: > : I've got problems with F290 and ep0 and 'zzz' :) > : I've running a kernel from 20th Oct (FreeBSDCon ;) to solve it. > : > : It may be fixed more recently, but last week's kernel didn't solve it. > > The suspend/card eject problem is still there. I've not found the > time, energy or motivation to fix it. No body else has sent me > patches either. I also don't have my laptop, but I could work around > that if I were motivated to work on the old stuff. :-(. I'm bad, I > like working on the new stuff more. > > Warner If you can give me some clues I'll work on it. I've got zero familiarity with the code :(. Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 19 9:39:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id BCF5D14CE0; Fri, 19 Nov 1999 09:39:41 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA15908; Fri, 19 Nov 1999 10:39:40 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA33661; Fri, 19 Nov 1999 10:40:19 -0700 (MST) Message-Id: <199911191740.KAA33661@harmony.village.org> To: Josef Karthauser Subject: Re: VAIO F270, ep0 and -current Cc: Dan Moschuk , hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 19 Nov 1999 17:20:25 GMT." <19991119172025.A97321@florence.pavilion.net> References: <19991119172025.A97321@florence.pavilion.net> <19991118192338.D55314@florence.pavilion.net> <19991117143759.A3011@spirit.jaded.net> <19991118192338.D55314@florence.pavilion.net> <199911182135.OAA28043@harmony.village.org> Date: Fri, 19 Nov 1999 10:40:19 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991119172025.A97321@florence.pavilion.net> Josef Karthauser writes: : If you can give me some clues I'll work on it. I've got zero familiarity : with the code :(. Sure. I posted this once to -mobile, so you might want to look in the archives there as well as here. The basic problem is that it appears that detach may be called AFTER the power is removed from the card generating an interrupt causing the interrupt routine to be called when the card is no longer there, which leads to an instant hang. Either that, or the act of removing the card causes an interupt to the card, then on the pcic which pulls the rug out from under the card and then it just hangs. I'm not completely sure and don't have a machine to test this on extenstively right now, so here goes at an off the cuff analysis. Looking at pcicintr in sys/pccard/pcic.c we see that the card_inserted event gets called (pccard_event in sys/pccard/pccard.c). This calls disable_slot and sets the state of the slot to empty and wakes up the pccardd proces. Looking at code it appears that we go ahead and delete the child in disable_slot (which should really be delayed until spl has been lowered via a timeout) which should be right. We then wait 1/2 second and power off the slot. Looks like we call the controllers disable routine for the slot (which is pcic_disable in pcic.c) where we turn off the card at the bridge chip. It is when we power the card off that we hang in the cards interrupt routine. Given this sequence of events, we should be safe. For the ep card we if_down, teardown the interrupt and free the resources and print unload. Somewhere in the above, something goes wrong :-(. Maybe it is the first parenthetical statement about waiting for the spl to be lowered, which would be something like: /* * disable_slot - Disables the slot by removing * the power and unmapping the I/O */ static void real_disable_slot(struct slot *slt); static void disable_slot(struct slot *slt) { slt->poff_ch = timeout(real_disable_slot, (caddr_t) slot, 0); } static void real_disable_slot(struct slot *slt) { // guts of the old disable_slot goes here } but there may be some more complicated book keeping needed... Lemme know if this helps... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 19 9:48: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.249.195.3]) by hub.freebsd.org (Postfix) with SMTP id 7E3E814D0A for ; Fri, 19 Nov 1999 09:47:44 -0800 (PST) (envelope-from paulo@nlink.com.br) Received: (qmail 36387 invoked by uid 501); 19 Nov 1999 17:47:42 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 19 Nov 1999 17:47:42 -0000 Date: Fri, 19 Nov 1999 15:47:42 -0200 (EDT) From: Paulo Fragoso To: hackers@freebsd.org Subject: Tunning Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Is there any HOWTO for to tune havy load web servers using FBSD 3.x? For FreeBSD 2.x I knew some items for kernel, like: options "NMBCLUSTERS=1024" options "CHILD_MAX=512" options "OPEN_MAX=512" but about FBSD 3.x I didn't. Can anyone help me? Thanks, Paulo. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 19 10:14:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 5AA4C156AD for ; Fri, 19 Nov 1999 10:14:07 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id NAA02164; Fri, 19 Nov 1999 13:14:09 -0500 (EST) Date: Fri, 19 Nov 1999 13:14:09 -0500 (EST) From: Daniel Eischen Message-Id: <199911191814.NAA02164@pcnet1.pcnet.com> To: freebsd-hackers@FreeBSD.ORG, scott@avantgo.com Subject: Re: EINTR problems with multithreaded programs. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > When using -pthread on FreeBSD3.3 to build a multithreaded program, I find > that signals are delivered to all threads (see attached program). > Specifically, if multiple threads are in blocking read calls, and a signal > is handled, they will all receive -1 from the read and EINTR in errno. If you don't want all threads to see the signal(s), then you have to block the signal(s) in each thread. > We're running MYSQL with a large number of connections (>1000), many of > which are idle at any given time (in a blocking read), and MYSQL uses alarm > signals in many places (it appears to be on a per-handled-query basis, but > I've not been able to pin this down quite yet). The net result is that > with many idle connections and many active connections, the idle > connections get a _lot_ of EINTR. By default, MYSQL takes 10 EINTR in a > row before dropping the connection - I've modified that upwards, but then > substantial amounts of CPU time are spent catching the EINTR and throwing > the thread back into the read (it's a relatively cheap operation - but > might happen a couple hundred thousand times a second). It sounds like MySQL isn't making sure that SIGALRM is blocked in all its threads. > I've tried using sigaction() in hopes of letting the system know that it > can restart the interrupted read(), but that doesn't seem to do the trick > in the attached program. Any other options? > > [Right now I'm seriously considering adding small sleeps to the EINTR case > in MYSQL. At least then all the threads won't wake up on every signal. I > know, I know, I should fix the use of signals, too, but that's going to > take a couple more weeks of becoming one with the code.] See /usr/src/lib/libc_r/test/sigwait/sigwait.c. FreeBSD delivers signals to each thread that has the signal unblocked. I believe this is part of the POSIX specified semantics for threads. You can use pthread_sigmask or sigprocmask within each thread to block each uninteresting signal. I have the POSIX standard at home, and I'll check to ensure we are handling signals in threaded programs correctly. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 19 10:15:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 51B7F1569A for ; Fri, 19 Nov 1999 10:15:30 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id NAA04652 for ; Fri, 19 Nov 1999 13:15:28 -0500 (EST) Date: Fri, 19 Nov 1999 12:02:52 -0500 (EST) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: What are short read and short write? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can anyone explain for me what are short read and short write? Under what circumstances will they happen and how FreeBSD deals with them? I come to this question while looking at code in file ufs/ufs_readwrite.c. Any help is appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 19 10:18:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id D62BD14E03 for ; Fri, 19 Nov 1999 10:18:38 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id KAA04030; Fri, 19 Nov 1999 10:18:21 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Fri, 19 Nov 1999 10:18:21 -0800 Date: Fri, 19 Nov 1999 10:18:21 -0800 (PST) From: Kip Macy X-Sender: kip@luna To: Daniel Eischen Cc: freebsd-hackers@FreeBSD.ORG, scott@avantgo.com Subject: Re: EINTR problems with multithreaded programs. In-Reply-To: <199911191814.NAA02164@pcnet1.pcnet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: eischen@vigrid.com,freebsd-hackers@FreeBSD.ORG,scott@avantgo.com X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That is not the way that Solaris or Windows NT handles it. However, delivering the signal to all threads offers a lot more design flexibility. -Kip On Fri, 19 Nov 1999, Daniel Eischen wrote: > > When using -pthread on FreeBSD3.3 to build a multithreaded program, I find > > that signals are delivered to all threads (see attached program). > > Specifically, if multiple threads are in blocking read calls, and a signal > > is handled, they will all receive -1 from the read and EINTR in errno. > > If you don't want all threads to see the signal(s), then you > have to block the signal(s) in each thread. > > > We're running MYSQL with a large number of connections (>1000), many of > > which are idle at any given time (in a blocking read), and MYSQL uses alarm > > signals in many places (it appears to be on a per-handled-query basis, but > > I've not been able to pin this down quite yet). The net result is that > > with many idle connections and many active connections, the idle > > connections get a _lot_ of EINTR. By default, MYSQL takes 10 EINTR in a > > row before dropping the connection - I've modified that upwards, but then > > substantial amounts of CPU time are spent catching the EINTR and throwing > > the thread back into the read (it's a relatively cheap operation - but > > might happen a couple hundred thousand times a second). > > It sounds like MySQL isn't making sure that SIGALRM is blocked in > all its threads. > > > I've tried using sigaction() in hopes of letting the system know that it > > can restart the interrupted read(), but that doesn't seem to do the trick > > in the attached program. Any other options? > > > > [Right now I'm seriously considering adding small sleeps to the EINTR case > > in MYSQL. At least then all the threads won't wake up on every signal. I > > know, I know, I should fix the use of signals, too, but that's going to > > take a couple more weeks of becoming one with the code.] > > See /usr/src/lib/libc_r/test/sigwait/sigwait.c. FreeBSD delivers signals > to each thread that has the signal unblocked. I believe this is part of > the POSIX specified semantics for threads. You can use pthread_sigmask > or sigprocmask within each thread to block each uninteresting signal. > > I have the POSIX standard at home, and I'll check to ensure we are > handling signals in threaded programs correctly. > > Dan Eischen > eischen@vigrid.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 19 10:19:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bomber.avantgo.com (ws1.avantgo.com [207.214.200.194]) by hub.freebsd.org (Postfix) with ESMTP id 4A6FF14E24 for ; Fri, 19 Nov 1999 10:19:23 -0800 (PST) (envelope-from scott@avantgo.com) Received: from river ([10.0.128.30]) by bomber.avantgo.com (Netscape Messaging Server 3.5) with SMTP id 369; Fri, 19 Nov 1999 10:15:13 -0800 Message-ID: <03e501bf32ba$76d83550$1e80000a@avantgo.com> From: "Scott Hess" To: "Daniel Eischen" , References: <199911191814.NAA02164@pcnet1.pcnet.com> Subject: Re: EINTR problems with multithreaded programs. Date: Fri, 19 Nov 1999 10:18:22 -0800 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_03E2_01BF3277.68A11F30" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_03E2_01BF3277.68A11F30 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Daniel Eischen wrote: >Scott Hess mailto:scott@avantgo.com wrote: > > When using -pthread on FreeBSD3.3 to build a multithreaded program, I find > > that signals are delivered to all threads (see attached program). > > Specifically, if multiple threads are in blocking read calls, and a signal > > is handled, they will all receive -1 from the read and EINTR in errno. > > If you don't want all threads to see the signal(s), then you > have to block the signal(s) in each thread. I've checked further, and found that FreeBSD correctly handles blocking signals on a per-thread basis. _But_, all threads still get EINTR when a signal happens while they're in a blocking read. I've attached the updated program that shows the correct delivery of the signals, with system calls still being interrupted. [Sorry about the attachment, but that seems the safest way to go about getting the file delivered in usable fashion.] Thanks, scott ------=_NextPart_000_03E2_01BF3277.68A11F30 Content-Type: application/octet-stream; name="thread_EINTR.c" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="thread_EINTR.c" #include =0A= #include =0A= #include =0A= #include =0A= =0A= static void signal_handler( int sig)=0A= {=0A= printf( "%p Got signal %d\n", pthread_self(), sig);=0A= }=0A= =0A= static void *reader( void *arg)=0A= {=0A= char buf[ 1024];=0A= int cc;=0A= int ii=3D(int)arg;=0A= int fd=3Ddup( 0);=0A= sigset_t set;=0A= =0A= sigemptyset( &set);=0A= if( (ii%3)=3D=3D0 || (ii%3)=3D=3D1) {=0A= sigaddset( &set, SIGUSR1);=0A= }=0A= if( (ii%3)=3D=3D0 || (ii%3)=3D=3D2) {=0A= sigaddset( &set, SIGUSR2);=0A= }=0A= pthread_sigmask( SIG_BLOCK, &set, NULL);=0A= =0A= {=0A= struct sigaction sa_usr1=3D{ signal_handler, 0, SA_RESTART};=0A= struct sigaction sa_usr2=3D{ signal_handler, 0, SA_RESTART};=0A= sigaction( SIGUSR1, &sa_usr1, NULL);=0A= sigaction( SIGUSR2, &sa_usr2, NULL);=0A= }=0A= =0A= printf( "%p/%d waiting for data\n", pthread_self(), ii);=0A= while(1) {=0A= cc=3Dread( fd, buf, sizeof( buf));=0A= if( cc>=3D0) {=0A= printf( "%p got %d bytes\n", pthread_self(), cc);=0A= } else {=0A= printf( "%p saw errno=3D=3D%d/%s\n", pthread_self(), errno, = strerror( errno));=0A= }=0A= }=0A= return NULL;=0A= }=0A= =0A= void main( void)=0A= {=0A= int ii, cc=3D9;=0A= pthread_t child;=0A= =0A= #if 0=0A= signal( SIGUSR1, signal_handler);=0A= #else=0A= {=0A= struct sigaction sa_usr1=3D{ signal_handler, 0, SA_RESTART};=0A= struct sigaction sa_usr2=3D{ signal_handler, 0, SA_RESTART};=0A= sigaction( SIGUSR1, &sa_usr1, NULL);=0A= sigaction( SIGUSR2, &sa_usr2, NULL);=0A= }=0A= #endif=0A= =0A= for( ii=3D0; ii; Fri, 19 Nov 1999 10:43:29 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id NAA05320; Fri, 19 Nov 1999 13:43:30 -0500 (EST) Date: Fri, 19 Nov 1999 13:43:29 -0500 (EST) From: Daniel Eischen To: Scott Hess Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: EINTR problems with multithreaded programs. In-Reply-To: <03e501bf32ba$76d83550$1e80000a@avantgo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 19 Nov 1999, Scott Hess wrote: > Daniel Eischen wrote: > >Scott Hess mailto:scott@avantgo.com wrote: > > > When using -pthread on FreeBSD3.3 to build a multithreaded program, I > find > > > that signals are delivered to all threads (see attached program). > > > Specifically, if multiple threads are in blocking read calls, and a > signal > > > is handled, they will all receive -1 from the read and EINTR in errno. > > > > If you don't want all threads to see the signal(s), then you > > have to block the signal(s) in each thread. > > I've checked further, and found that FreeBSD correctly handles blocking > signals on a per-thread basis. _But_, all threads still get EINTR when a > signal happens while they're in a blocking read. > > I've attached the updated program that shows the correct delivery of the > signals, with system calls still being interrupted. [Sorry about the > attachment, but that seems the safest way to go about getting the file > delivered in usable fashion.] Well, that is wrong and should be fixed. I'll commit a fix to -current this weekend. Here's an untested patch to libc_r/uthread/uthread_sig.c: *** uthread_sig.c.orig Fri Nov 19 13:36:53 1999 --- uthread_sig.c Fri Nov 19 13:38:06 1999 *************** *** 323,330 **** case PS_POLL_WAIT: case PS_SLEEP_WAIT: case PS_SELECT_WAIT: ! if (sig != SIGCHLD || ! _thread_sigact[sig - 1].sa_handler != SIG_DFL) { /* Flag the operation as interrupted: */ pthread->interrupted = 1; --- 323,330 ---- case PS_POLL_WAIT: case PS_SLEEP_WAIT: case PS_SELECT_WAIT: ! if (!sigismember(&pthread->sigmask, sig) && (sig != SIGCHLD || ! _thread_sigact[sig - 1].sa_handler != SIG_DFL)) { /* Flag the operation as interrupted: */ pthread->interrupted = 1; Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 19 13:18: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id D35E914F3C for ; Fri, 19 Nov 1999 13:17:27 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (loot.cs.rpi.edu [128.213.16.22]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA05349; Fri, 19 Nov 1999 16:17:19 -0500 (EST) Message-Id: <199911192117.QAA05349@cs.rpi.edu> To: Warner Losh Cc: freebsd-hackers@freebsd.org, "David E. Cross" Subject: Re: AMD wedging In-Reply-To: Message from Warner Losh of "Thu, 18 Nov 1999 12:21:10 MST." <199911181921.MAA27386@harmony.village.org> Date: Fri, 19 Nov 1999 16:10:00 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does this give any indications to anyone? loot# gdb -k /kernel /dev/mem GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... (no debugging symbols found)... IdlePTD 2932736 initial pcb at 1118000 panic messages: --- --- #0 0xc0136a39 in mi_switch () (kgdb) proc 17399 (kgdb) bt #0 0xfdf0 in ?? () error reading /proc/17399/mem (kgdb) quit loot# cat /proc/17399/mem cat: /proc/17399/mem: Bad address -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 19 14:32:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id 9279E14CF8 for ; Fri, 19 Nov 1999 14:30:54 -0800 (PST) (envelope-from freebsd@b0rg.net) Received: from cr717730b ([24.112.177.211]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with SMTP id <19991119222740.VUFJ7575.mail.rdc3.on.home.com@cr717730b> for ; Fri, 19 Nov 1999 14:27:40 -0800 Message-ID: <001701bf32dd$4f76a500$d3b17018@wlfdle1.on.wave.home.com> From: "Jason Craig" To: Subject: Compile new kernel with MCA support Date: Fri, 19 Nov 1999 17:27:15 -0500 Organization: Resistance is Futile MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I have a few FreeBSD machines that I am playing around with now, and have come across a nice old IBM PC Server 320 with dual P90 processors and 64MB of RAM i would also like to utilize. I am currently using 4.0-19991113-CURRENT generic kernel, and things are working great. However, I tried to compile a custom kernel to weed out any unwanted devices, and to enable SMP and have have run into a problem. After compiling the kernel using the standard procedure, I rebooted it, and it panic'd after doing the kernel config. I tried removing most of the entries from /boot/kernel.conf, only to find it still panics saying something about the MCA bus. Am I missing something? Your help would be appreciated. Thanks, Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 19 14:37:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id 20DEC157C3 for ; Fri, 19 Nov 1999 14:36:17 -0800 (PST) (envelope-from nemesys@home.com) Received: from cr717730b ([24.112.177.211]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with SMTP id <19991119223242.VWMR7575.mail.rdc3.on.home.com@cr717730b> for ; Fri, 19 Nov 1999 14:32:42 -0800 Message-ID: <003001bf32de$02ffa4a0$d3b17018@wlfdle1.on.wave.home.com> From: "Jason Craig" To: Subject: Compiling a new kernel with MCA Date: Fri, 19 Nov 1999 17:32:20 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I have a few FreeBSD machines that I am playing around with now, and have come across a nice old IBM PC Server 320 with dual P90 processors and 64MB of RAM i would also like to utilize. I am currently using 4.0-19991113-CURRENT generic kernel, and things are working great. However, I tried to compile a custom kernel to weed out any unwanted devices, and to enable SMP and have have run into a problem. After compiling the kernel using the standard procedure, I rebooted it, and it panic'd after doing the kernel config. I tried removing most of the entries from /boot/kernel.conf, only to find it still panics saying something about the MCA bus. Am I missing something? Your help would be appreciated. Thanks, Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 19 14:40:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.ny.verio.net (listserv.ny.verio.net [199.1.22.70]) by hub.freebsd.org (Postfix) with ESMTP id E5CEF14E7F for ; Fri, 19 Nov 1999 14:40:11 -0800 (PST) (envelope-from jcraig@servtech.com) Received: from servtech.com (mail.ny.verio.net [199.1.22.31]) by mailhub.ny.verio.net (8.8.8/8.8.8) with ESMTP id WAA26001 for ; Fri, 19 Nov 1999 22:40:01 GMT Received: from cr717730b (cr717730-b.wlfdle1.on.wave.home.com [24.112.177.211]) by servtech.com (8.8.8/8.8.8) with SMTP id WAA24261 for ; Fri, 19 Nov 1999 22:39:47 GMT Message-ID: <003601bf32de$c3a0ff60$d3b17018@wlfdle1.on.wave.home.com> From: "Jason" To: Subject: Compiling a new kernel with MCA Date: Fri, 19 Nov 1999 17:38:07 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I have a few FreeBSD machines that I am playing around with now, and have come across a nice old IBM PC Server 320 with dual P90 processors and 64MB of RAM i would also like to utilize. I am currently using 4.0-19991113-CURRENT generic kernel, and things are working great. However, I tried to compile a custom kernel to weed out any unwanted devices, and to enable SMP and have have run into a problem. After compiling the kernel using the standard procedure, I rebooted it, and it panic'd after doing the kernel config. I tried removing most of the entries from /boot/kernel.conf, only to find it still panics saying something about the MCA bus. Am I missing something? Your help would be appreciated. Thanks, Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 19 15: 4:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id 59F1614F3E; Fri, 19 Nov 1999 15:04:08 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991119180320.65386@mojave.sitaranetworks.com> Date: Fri, 19 Nov 1999 18:03:20 -0500 From: Greg Lehey To: Jason Craig , Jason Craig , Jason Cc: FreeBSD current users Subject: Re: Compile new kernel with MCA support Reply-To: Greg Lehey References: <001701bf32dd$4f76a500$d3b17018@wlfdle1.on.wave.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <001701bf32dd$4f76a500$d3b17018@wlfdle1.on.wave.home.com>; from Jason Craig on Fri, Nov 19, 1999 at 05:27:15PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [moved to -current] On Friday, 19 November 1999 at 17:27:15 -0500, Jason Craig wrote: On Friday, 19 November 1999 at 17:32:20 -0500, Jason Craig wrote: On Friday, 19 November 1999 at 17:38:07 -0500, Jason wrote: > Hello all, > > I have a few FreeBSD machines that I am playing around with now, and have > come across a nice old IBM PC Server 320 with dual P90 processors and 64MB > of RAM i would also like to utilize. > > I am currently using 4.0-19991113-CURRENT generic kernel, and things are > working great. > > However, I tried to compile a custom kernel to weed out any unwanted > devices, and to enable SMP and have have run into a problem. After > compiling the kernel using the standard procedure, I rebooted it, and it > panic'd after doing the kernel config. > > I tried removing most of the entries from /boot/kernel.conf, only to find it > still panics saying something about the MCA bus. > > Am I missing something? Yes, probably http://www.lemis.com/questions.html. To quote: Should I ask -questions or -hackers? Two mailing lists handle general questions about FreeBSD, FreeBSD-questions and FreeBSD-hackers. In some cases, it's not really clear which group you should ask. The following criteria should help for 99% of all questions, however: If the question is of a general nature, ask FreeBSD-questions. Examples might be questions about intstalling FreeBSD or the use of a particular UNIX utility. If you think the question relates to a bug, but you're not sure, or you don't know how to look for it, send the message to FreeBSD-questions. 6. Specify as much information as possible. This is a difficult area, and we need to expand on what information you need to submit, but here's a start: In nearly every case, it's important to know the version of FreeBSD you're running. This is particularly the case for FreeBSD-CURRENT, where you should also specify the date of the sources, though of course you shouldn't be sending questions about -CURRENT to FreeBSD-questions (...) If your system panics, don't say ``My system panicked'', say (for example) ``my system panicked with the message 'free vnode isn't'''. 7. If you do all this, and you still don't get an answer, there could be other reasons. For example, the problem is so complicated that nobody knows the answer, or the person who does know the answer was offline. If you don't get an answer after, say, a week, it might help to re-send the message. If you don't get an answer to your second message, though, you're probably not going to get one from this forum. Resending the same message again and again will only make you unpopular. One that's not in there: if you're running -CURRENT, come with some *clever* questions. -CURRENT isn't for beginners. In your case, you sent three messages in 11 minues. That's a good way to make yourself unpopular, especially when you're running exotic hardware which not many people know. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 19 15:13: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 4207214E3E; Fri, 19 Nov 1999 15:13:00 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 33A1A1CD73D; Fri, 19 Nov 1999 15:13:00 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Fri, 19 Nov 1999 15:13:00 -0800 (PST) From: Kris Kennaway To: Wes Peters Cc: andrew@ugh.net.au, Daniel O'Connor , hackers@freebsd.org Subject: Re: Making a port kit In-Reply-To: <383576E9.CD5A32D2@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 19 Nov 1999, Wes Peters wrote: > Actually, taking the MAN8= line out of the port Makefile fixed the problem. > Thanks for the hints. You need to have manpages referenced by MAN? variables instead of just installed directly: the reason is that they may or may not be compressed at the time the package is deinstalled, and so you get left with manpage turds in the filesystem. Didn't someone already point out your problem was just a mistyped path? Kris ---- Cthulhu for President! For when you're tired of choosing the _lesser_ of two evils.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 19 17:56:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 168FD1532A for ; Fri, 19 Nov 1999 17:56:17 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id UAA08261; Fri, 19 Nov 1999 20:56:10 -0500 (EST) Date: Fri, 19 Nov 1999 20:56:10 -0500 (EST) From: "Matthew N. Dodd" To: Jason Craig Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Compile new kernel with MCA support In-Reply-To: <001701bf32dd$4f76a500$d3b17018@wlfdle1.on.wave.home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 19 Nov 1999, Jason Craig wrote: > I have a few FreeBSD machines that I am playing around with now, and > have come across a nice old IBM PC Server 320 with dual P90 processors > and 64MB of RAM i would also like to utilize. > > I am currently using 4.0-19991113-CURRENT generic kernel, and things are > working great. > > However, I tried to compile a custom kernel to weed out any unwanted > devices, and to enable SMP and have have run into a problem. After > compiling the kernel using the standard procedure, I rebooted it, and > it panic'd after doing the kernel config. > > I tried removing most of the entries from /boot/kernel.conf, only to > find it still panics saying something about the MCA bus. Using the serial console, capture the boot messages and attach them to the reply to this message. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 0:16: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id C40E714C44 for ; Sat, 20 Nov 1999 00:16:05 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id AAA60453; Sat, 20 Nov 1999 00:16:03 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Sat, 20 Nov 1999 00:16:03 -0800 (PST) From: Doug White To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: What are short read and short write? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 19 Nov 1999, Zhihui Zhang wrote: > > Can anyone explain for me what are short read and short write? Under what > circumstances will they happen and how FreeBSD deals with them? I come > to this question while looking at code in file ufs/ufs_readwrite.c. A ``short read'' or ``short write'' are when the read() and write() system calls return less data than requested. For example, if you had the read call read(fd, &buf, 1024) and read could pull only 512 bytes from the file descriptor, read() would return 512 and that would be a short read. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 0:19:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 8BD9014D1F; Sat, 20 Nov 1999 00:19:44 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id AAA17895; Sat, 20 Nov 1999 00:03:22 GMT (envelope-from nik) Date: Sat, 20 Nov 1999 00:03:21 +0000 From: Nik Clayton To: Julian Elischer Cc: Nik Clayton , hackers@freebsd.org Subject: Re: netgraph into -stable. Message-ID: <19991120000321.A17758@catkin.nothing-going-on.org> References: <19991117224146.A55401@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Julian Elischer on Thu, Nov 18, 1999 at 01:58:59PM -0800 Organization: FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 18, 1999 at 01:58:59PM -0800, Julian Elischer wrote: > for info on what it is, > see: > ftp://ftp.whistle.com/pub/archie/netgraph/index.html > or in an http form: > http://www.elischer.org/netgraph/index.html Thanks a lot. Very interesting reading. N -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 0:20:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id CAC1414CAD for ; Sat, 20 Nov 1999 00:20:21 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id AAA62047; Sat, 20 Nov 1999 00:20:07 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Sat, 20 Nov 1999 00:20:07 -0800 (PST) From: Doug White To: Paulo Fragoso Cc: hackers@FreeBSD.ORG Subject: Re: Tunning In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 19 Nov 1999, Paulo Fragoso wrote: > Is there any HOWTO for to tune havy load web servers using FBSD 3.x? > > For FreeBSD 2.x I knew some items for kernel, like: > > options "NMBCLUSTERS=1024" > options "CHILD_MAX=512" > options "OPEN_MAX=512" > > but about FBSD 3.x I didn't. Tweak `maxusers' first. Maxusers is a general scaling constant that affects multiple tables, including the ones formerly controlled by CHILD_MAX and OPEN_MAX. I recommend at least 64 for most server systems, 128 being a good median. If you need an insane number of mbufs, set NMBCLUSTERS independently, but use 'netstat -m' to make sure you don't reduce the number of mbufs. I wouldn't touch NMBCLUSTERS independently unless you have information/experience otherwise. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 6:18:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id 5B4A414D40; Sat, 20 Nov 1999 06:18:08 -0800 (PST) (envelope-from freebsd@b0rg.net) Received: from cr717730b ([24.112.177.211]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with SMTP id <19991120141610.LKQU7575.mail.rdc3.on.home.com@cr717730b>; Sat, 20 Nov 1999 06:16:10 -0800 Message-ID: <008f01bf3361$cb5d5900$d3b17018@wlfdle1.on.wave.home.com> From: "Jason Craig" To: "Greg Lehey" Cc: "FreeBSD Current" , "FreeBSD Hackers" References: <001701bf32dd$4f76a500$d3b17018@wlfdle1.on.wave.home.com> <19991119180320.65386@mojave.sitaranetworks.com> Subject: Re: Compile new kernel with MCA support Date: Sat, 20 Nov 1999 09:16:10 -0500 Organization: Resistance is Futile MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry about the multiple posts. I have @home to thank for this. The mail server said the connection was timing out. Apparently not. I am quite well aware of the mailing list etiquette. I read through many of them frequently. The question itself should remain in the hackers list. Support for Micro channel is not only fairly new from what I read, but a direct modification to the kernel to support the old architecture. That's why I am running current on said machine. A beginner to FreeBSD, I am not... I am a beginner to making MCA work on BSD. Anyways... Thank you Matthew for replying to my message. I'll get the boot messages this morning. Jason ----- Original Message ----- From: Greg Lehey To: Jason Craig ; Jason Craig ; Jason Cc: FreeBSD current users Sent: Friday, November 19, 1999 6:03 PM Subject: Re: Compile new kernel with MCA support > [moved to -current] > > On Friday, 19 November 1999 at 17:27:15 -0500, Jason Craig wrote: > On Friday, 19 November 1999 at 17:32:20 -0500, Jason Craig wrote: > On Friday, 19 November 1999 at 17:38:07 -0500, Jason wrote: > > Hello all, > > > > I have a few FreeBSD machines that I am playing around with now, and have > > come across a nice old IBM PC Server 320 with dual P90 processors and 64MB > > of RAM i would also like to utilize. > > > > I am currently using 4.0-19991113-CURRENT generic kernel, and things are > > working great. > > > > However, I tried to compile a custom kernel to weed out any unwanted > > devices, and to enable SMP and have have run into a problem. After > > compiling the kernel using the standard procedure, I rebooted it, and it > > panic'd after doing the kernel config. > > > > I tried removing most of the entries from /boot/kernel.conf, only to find it > > still panics saying something about the MCA bus. > > > > Am I missing something? > > Yes, probably http://www.lemis.com/questions.html. To quote: > > Should I ask -questions or -hackers? > > Two mailing lists handle general questions about FreeBSD, > FreeBSD-questions and FreeBSD-hackers. In some cases, it's not really > clear which group you should ask. The following criteria should help > for 99% of all questions, however: > > If the question is of a general nature, ask > FreeBSD-questions. Examples might be questions about intstalling > FreeBSD or the use of a particular UNIX utility. > > If you think the question relates to a bug, but you're not sure, > or you don't know how to look for it, send the message to > FreeBSD-questions. > > 6. Specify as much information as possible. This is a difficult area, > and we need to expand on what information you need to submit, but > here's a start: > > In nearly every case, it's important to know the version of > FreeBSD you're running. This is particularly the case for > FreeBSD-CURRENT, where you should also specify the date of the > sources, though of course you shouldn't be sending questions about > -CURRENT to FreeBSD-questions > > (...) > > If your system panics, don't say ``My system panicked'', say (for > example) ``my system panicked with the message 'free vnode > isn't'''. > > 7. If you do all this, and you still don't get an answer, there could > be other reasons. For example, the problem is so complicated that > nobody knows the answer, or the person who does know the answer > was offline. If you don't get an answer after, say, a week, it > might help to re-send the message. If you don't get an answer to > your second message, though, you're probably not going to get one > from this forum. Resending the same message again and again will > only make you unpopular. > > One that's not in there: if you're running -CURRENT, come with some > *clever* questions. -CURRENT isn't for beginners. > > In your case, you sent three messages in 11 minues. That's a good way > to make yourself unpopular, especially when you're running exotic > hardware which not many people know. > > Greg > -- > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 10: 7:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 464D61577C for ; Sat, 20 Nov 1999 10:07:12 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p11-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.140]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id DAA04648; Sun, 21 Nov 1999 03:06:59 +0900 (JST) Message-ID: <3836DF98.9A84EC44@newsguy.com> Date: Sun, 21 Nov 1999 02:51:20 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: John Polstra Cc: Garance A Drosihn , hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > > We must be interpreting the requirement differently, because it > doesn't seem onerous at all to me. The st_dev value needn't be the > same on two different hosts which both mount the same filesystem. I > also doubt that the requirement has to hold across remounts. Under > that interpretation, it's simple to meet the requirement. Just create > a locally-unique st_dev value whenever you mount a filesystem, and > if the filesystem is remote then record a mapping between (remote > hostname, remote host's idea of the "device") and the local st_dev > value. (I've never used AFS, so I may be missing something crucial > here.) You are assuming the fs is local to some place. It is not. It is distributed. Files might even migrate. So, the fs is at the same time local and foreign to all hosts mounting it. Anyway, st_dev+st_ino just don't give enough bits for a unique identifier. The example of AFS (?), where a globally unique identifier has 80 bits, is a good one. > Well, the POSIX requirement isn't optional. If a system doesn't > meet it then it is not POSIX-compliant. So any application that is > targeted toward POSIX systems is perfectly within its rights to rely > on the requirement. It was stated before that FreeBSD complies with POSIX except where POSIX is broken. Well, it's broken here. st_dev+st_ino *can't* work with modern, distributed filesystems (without undue overhead). -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Then again maybe not going to heaven would be a blessing. Relkin liked a certain amount of peace and harmony, since there'd been a pronounced shortage of them in his own life; however, nothing but peace and harmony, forever and forever? He wasn't sure about that. And no beer? Very dubious proposition." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 11: 6:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id 1845814D1C for ; Sat, 20 Nov 1999 11:06:13 -0800 (PST) (envelope-from nemesys@home.com) Received: from cr717730b ([24.112.177.211]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with SMTP id <19991120190414.QEPC7575.mail.rdc3.on.home.com@cr717730b>; Sat, 20 Nov 1999 11:04:14 -0800 Message-ID: <00b701bf338a$06d096a0$d3b17018@wlfdle1.on.wave.home.com> From: "Jason Craig" To: "Matthew N. Dodd" Cc: "FreeBSD Hackers" References: Subject: Re: Compile new kernel with MCA support Date: Sat, 20 Nov 1999 14:04:10 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Mathew, Thanks for replying! Here's what I see when I boot with the kernel I compiled a few days ago: Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-19991113-CURRENT #0: Fri Nov 19 08:00:49 GMT 1999 root@cr717730-d.wlfdle1.on.wave.home.com:/usr/src/sys/compile/KERNEL.1119199 9 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P54C (89.96-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping = 5 Features=0x3bf real memory = 67108864 (65536K bytes) avail memory = 62033920 (60580K bytes) panic: unknown bus type: 'MCA' mp_lock = 00000004; cpuid = 0; lapic.id = 00000000 Boom... Locked up. When I created the custom kernel config for this machine I did removed devices that were not present in my system (as usual), and enabled SMP. # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs A little lower I noticed that there were no entries for MCA, should there be one? controller isa0 controller pnp0 # PnP support for ISA controller eisa0 controller pci0 Thans in advance, Jason ----- Original Message ----- From: Matthew N. Dodd To: Jason Craig Cc: Sent: Friday, November 19, 1999 8:56 PM Subject: Re: Compile new kernel with MCA support > On Fri, 19 Nov 1999, Jason Craig wrote: > > I have a few FreeBSD machines that I am playing around with now, and > > have come across a nice old IBM PC Server 320 with dual P90 processors > > and 64MB of RAM i would also like to utilize. > > > > I am currently using 4.0-19991113-CURRENT generic kernel, and things are > > working great. > > > > However, I tried to compile a custom kernel to weed out any unwanted > > devices, and to enable SMP and have have run into a problem. After > > compiling the kernel using the standard procedure, I rebooted it, and > > it panic'd after doing the kernel config. > > > > I tried removing most of the entries from /boot/kernel.conf, only to > > find it still panics saying something about the MCA bus. > > Using the serial console, capture the boot messages and attach them to the > reply to this message. > > -- > | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | > | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | > | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 11:29:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 4CF9415084; Sat, 20 Nov 1999 11:29:12 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id LAA15346; Sat, 20 Nov 1999 11:29:06 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id LAA14904; Sat, 20 Nov 1999 11:29:05 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA02583; Sat, 20 Nov 99 11:28:56 PST Message-Id: <3836F676.CB4D2D9F@softweyr.com> Date: Sat, 20 Nov 1999 12:28:54 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Kris Kennaway Cc: andrew@ugh.net.au, "Daniel O'Connor" , hackers@freebsd.org Subject: Re: Making a port kit References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > On Fri, 19 Nov 1999, Wes Peters wrote: > > > Actually, taking the MAN8= line out of the port Makefile fixed the problem. > > Thanks for the hints. > > You need to have manpages referenced by MAN? variables instead of just > installed directly: the reason is that they may or may not be compressed > at the time the package is deinstalled, and so you get left with manpage > turds in the filesystem. > > Didn't someone already point out your problem was just a mistyped path? Nope, and it seems difficult to have a mistyped path when you don't have any paths anywhere. The only paths are in the obliterate makefile: ~~~~~~~~~~~~~~~ snip ~~~~~~~~~~~~~~~~ CFLAGS= -g PROG= obliterate SRCS= obliterate.c MAN8= obliterate.8 BINDIR= ${PREFIX}/bin MANDIR= ${PREFIX}/man .include ~~~~~~~~~~~~~~~ snip ~~~~~~~~~~~~~~~~ Which part of MANDIR did I misspell, the "m", "a", or "n"? The real problem came from having MAN8= sections in BOTH Makefiles, the one in the obliterate tarball and the port Makefile. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 11:39:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 25C5314C1F for ; Sat, 20 Nov 1999 11:39:14 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id LAA15383; Sat, 20 Nov 1999 11:37:32 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id LAA15018; Sat, 20 Nov 1999 11:37:32 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA02933; Sat, 20 Nov 99 11:37:24 PST Message-Id: <3836F873.D3B989FE@softweyr.com> Date: Sat, 20 Nov 1999 12:37:23 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: "Daniel C. Sobral" Cc: John Polstra , Garance A Drosihn , hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? References: <3836DF98.9A84EC44@newsguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" wrote: > > John Polstra wrote: > > > > Well, the POSIX requirement isn't optional. If a system doesn't > > meet it then it is not POSIX-compliant. So any application that is > > targeted toward POSIX systems is perfectly within its rights to rely > > on the requirement. > > It was stated before that FreeBSD complies with POSIX except where > POSIX is broken. Well, it's broken here. st_dev+st_ino *can't* work > with modern, distributed filesystems (without undue overhead). It's not broken in this case. 2^16 (st_dev) is certainly enough to uniquely indentify all mounted filesystems, and 2^32 is (by definition) enough to uniquely indentify each of the files on a filesystem. Discussions (with strong, valid reasons) about expanding the size of ino_t should be carried out on -arch. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 11:45:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id BBC1F1508B for ; Sat, 20 Nov 1999 11:44:57 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id OAA19595 for ; Sat, 20 Nov 1999 14:44:58 -0500 (EST) Message-Id: <199911201944.OAA19595@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 20 Nov 1999 14:41:27 -0500 To: hackers@freebsd.org From: Dennis Subject: PCI DMA lockups in 3.2 (3.3 maybe?) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've run into a situation where, with heavy PCI bus traffic, freebsd 3.2 systems lock up. I havent tried it on 3.3 yet. The same scenarios do not cause the problem on the exact machine in both FreeBSD 2.2.8 and LINUX so it doesnt seem to be a hardware problem. The problem can be duplicated regularly by passing 80Mb/s of traffic through ethernet and serial devices and then doing a "find" to create excessive disk access. The 2.2.8 and LINUX systems continue to run normally while FreeBSD 3.2 hangs regularly. I'll test this in 3.3 shortly...has anything been done in this area? It seems to happen on passive backplace systems (although its more likely the chipsets used on SBCs)...my acer MB doesnt lock up with the same test. This problem has been duplicated on more than 1 system with completely different hardware. Any ideas? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 12: 9:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 816DD14C41 for ; Sat, 20 Nov 1999 12:08:51 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p11-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.140]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id FAA04911; Sun, 21 Nov 1999 05:08:26 +0900 (JST) Message-ID: <3836FF29.3D918C08@newsguy.com> Date: Sun, 21 Nov 1999 05:06:01 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Wes Peters Cc: John Polstra , Garance A Drosihn , hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? References: <3836DF98.9A84EC44@newsguy.com> <3836F873.D3B989FE@softweyr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters wrote: > > It's not broken in this case. 2^16 (st_dev) is certainly enough to uniquely > indentify all mounted filesystems, and 2^32 is (by definition) enough to > uniquely indentify each of the files on a filesystem. Discussions (with > strong, valid reasons) about expanding the size of ino_t should be carried > out on -arch. Well, the whole argument was preceeded by a disclaimer that the "by definition" of inode depended on... the very concept of inode, which is not universal. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Then again maybe not going to heaven would be a blessing. Relkin liked a certain amount of peace and harmony, since there'd been a pronounced shortage of them in his own life; however, nothing but peace and harmony, forever and forever? He wasn't sure about that. And no beer? Very dubious proposition." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 12:10:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 2149A1573C for ; Sat, 20 Nov 1999 12:10:03 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p11-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.140]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id FAA05476; Sun, 21 Nov 1999 05:09:50 +0900 (JST) Message-ID: <3836FF7C.2D8236AE@newsguy.com> Date: Sun, 21 Nov 1999 05:07:24 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Wes Peters Cc: John Polstra , Garance A Drosihn , hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? References: <3836DF98.9A84EC44@newsguy.com> <3836F873.D3B989FE@softweyr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters wrote: > > It's not broken in this case. 2^16 (st_dev) is certainly enough to uniquely > indentify all mounted filesystems, and 2^32 is (by definition) enough to > uniquely indentify each of the files on a filesystem. Discussions (with > strong, valid reasons) about expanding the size of ino_t should be carried > out on -arch. Just to expand a little bit more, some distributed filesystems *do not* have a unique identifier like the inode. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Then again maybe not going to heaven would be a blessing. Relkin liked a certain amount of peace and harmony, since there'd been a pronounced shortage of them in his own life; however, nothing but peace and harmony, forever and forever? He wasn't sure about that. And no beer? Very dubious proposition." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 12:14:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 8546314C41 for ; Sat, 20 Nov 1999 12:14:13 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id PAA133582; Sat, 20 Nov 1999 15:14:06 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Sat, 20 Nov 1999 15:15:40 -0500 To: John Polstra From: Garance A Drosihn Subject: Re: Portable way to compare struct stat's? Cc: hackers@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 6:56 PM -0800 11/18/99, John Polstra wrote: >Garance A Drosihn wrote: > > At 10:40 AM -0800 11/18/99, John Polstra wrote: > >>I don't dispute that point, but it is worth mentioning that POSIX > >>specifically guarantees that st_dev and st_ino "taken together > >>uniquely identify the file within the system." So it is OK for > >>applications to rely on that. > > > > Given how many people have files mounted from foreign file systems, > > I would think that applications should not rely on that. Sure, it's > > a nice guarantee for a completely stand-alone system, but a "general > > purpose" application should consider that it may be dealing with > > files in NFS, AFS, or some other file system, and plan accordingly. > >We must be interpreting the requirement differently, because it >doesn't seem onerous at all to me. The st_dev value needn't be the >same on two different hosts which both mount the same filesystem. I >also doubt that the requirement has to hold across remounts. Under >that interpretation, it's simple to meet the requirement. Hmm. My guess is that we're talking about different aspects of this issue. I believe I agree 100% with what you're saying here, but I don't see how your comments apply to what I was saying. That might mean I am just missing some important detail, so... From an operating-system point of view, I think the POSIX requirement is a good thing. Operating system developers should do everything they can do to make sure that those two fields will "uniquely identify the file within the system". (what exactly is meant by "in the system" here? I'm assuming it means all locally-attached hard drives...). I certainly do not think that is an onerous request to make of operating system developers. From the application side of things (ie, a person writing a generic program), I'm saying it is a fact that those two numbers will not always "uniquely identify a file", mainly because of distributed file systems (NFS-mounted, or AFS, or whatever). I am stating a fact of the real world, and am saying that "application developers should plan accordingly". Example: it is a fact that if your system is using NFS to mount filesystems exported from AIX boxes, then you can not depend on those numbers. Two different processes (say, 'lpr' running as a generic user, and 'lpd' running as root) will get DIFFERENT values for those numbers, when stat()-ing the exact same file on the exact same machine using the exact same path at the same time. I'm not even trying to compare two different paths to see if they point to the "same inode", I'm saying these two numbers do not even identify the file, never mind "uniquely" identify it. It might be that freebsd does things which fix this behavior, but that only helps if the application developer knows that their application will only run on FreeBSD. The problem, as I understand it, is in the way AIX *exports* the file systems. Now, maybe your point is that AIX hasn't done it's homework here, and that would be a good point. However, that does not change the behavior an application developer will actually see, and there is nothing the application developer can do to avoid the consequences of that behavior. That's one NFS-based example that's on my mind because I recently tripped over it. I'm pretty sure there are specific AFS-based examples too, but I can't think of one at the moment. Probably issues with mounting the same volume at multiple points within the AFS hierarchy. Perhaps it's just the sheer number of files one can find in the entire hierarchy of AFS is too many to uniquely identify them all in "such a small field" as 'st_dev + st_ino'. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 13:12:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id A7EFF14A28 for ; Sat, 20 Nov 1999 13:12:09 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id QAA03193; Sat, 20 Nov 1999 16:12:08 -0500 (EST) Date: Sat, 20 Nov 1999 16:12:07 -0500 (EST) From: "Matthew N. Dodd" To: Jason Craig Cc: FreeBSD Hackers Subject: Re: Compile new kernel with MCA support In-Reply-To: <00b701bf338a$06d096a0$d3b17018@wlfdle1.on.wave.home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 20 Nov 1999, Jason Craig wrote: > Here's what I see when I boot with the kernel I compiled a few days ago: Humm... I see where the problem is. I'd like you to compile a kernel without SMP support but with MCA support. Add: controller mca0 I'm working on the SMP angle. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 4.0-19991113-CURRENT #0: Fri Nov 19 08:00:49 GMT 1999 > > root@cr717730-d.wlfdle1.on.wave.home.com:/usr/src/sys/compile/KERNEL.1119199 > 9 > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium/P54C (89.96-MHz 586-class CPU) > Origin = "GenuineIntel" Id = 0x525 Stepping = 5 > Features=0x3bf > real memory = 67108864 (65536K bytes) > avail memory = 62033920 (60580K bytes) > panic: unknown bus type: 'MCA' > mp_lock = 00000004; cpuid = 0; lapic.id = 00000000 > > Boom... Locked up. > > When I created the custom kernel config for this machine I did removed > devices that were not present in my system (as usual), and enabled SMP. > > # To make an SMP kernel, the next two are needed > options SMP # Symmetric MultiProcessor Kernel > options APIC_IO # Symmetric (APIC) I/O > # Optionally these may need tweaked, (defaults shown): > options NCPU=2 # number of CPUs > #options NBUS=4 # number of busses > #options NAPIC=1 # number of IO APICs > #options NINTR=24 # number of INTs > > A little lower I noticed that there were no entries for MCA, should there be > one? > > controller isa0 > controller pnp0 # PnP support for ISA > controller eisa0 > controller pci0 > > Thans in advance, > > Jason > > > > > ----- Original Message ----- > From: Matthew N. Dodd > To: Jason Craig > Cc: > Sent: Friday, November 19, 1999 8:56 PM > Subject: Re: Compile new kernel with MCA support > > > > On Fri, 19 Nov 1999, Jason Craig wrote: > > > I have a few FreeBSD machines that I am playing around with now, and > > > have come across a nice old IBM PC Server 320 with dual P90 processors > > > and 64MB of RAM i would also like to utilize. > > > > > > I am currently using 4.0-19991113-CURRENT generic kernel, and things are > > > working great. > > > > > > However, I tried to compile a custom kernel to weed out any unwanted > > > devices, and to enable SMP and have have run into a problem. After > > > compiling the kernel using the standard procedure, I rebooted it, and > > > it panic'd after doing the kernel config. > > > > > > I tried removing most of the entries from /boot/kernel.conf, only to > > > find it still panics saying something about the MCA bus. > > > > Using the serial console, capture the boot messages and attach them to the > > reply to this message. > > > > -- > > | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | > > | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | > > | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 13:29:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 99F5F14C83 for ; Sat, 20 Nov 1999 13:29:43 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id QAA03485; Sat, 20 Nov 1999 16:29:41 -0500 (EST) Date: Sat, 20 Nov 1999 16:29:41 -0500 (EST) From: "Matthew N. Dodd" To: Jason Craig Cc: FreeBSD Hackers Subject: Re: Compile new kernel with MCA support In-Reply-To: <00b701bf338a$06d096a0$d3b17018@wlfdle1.on.wave.home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 20 Nov 1999, Jason Craig wrote: > panic: unknown bus type: 'MCA' > mp_lock = 00000004; cpuid = 0; lapic.id = 00000000 Apply this patch: ftp://ftp.jurai.net/users/winter/patches/mca_mp.patch And let me know what happens. Thanks. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 13:41:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id DA85614C83 for ; Sat, 20 Nov 1999 13:41:51 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA39144; Sat, 20 Nov 1999 16:41:29 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <3836F873.D3B989FE@softweyr.com> References: <3836DF98.9A84EC44@newsguy.com> <3836F873.D3B989FE@softweyr.com> Date: Sat, 20 Nov 1999 16:43:04 -0500 To: Wes Peters , "Daniel C. Sobral" From: Garance A Drosihn Subject: Re: Portable way to compare struct stat's? Cc: John Polstra , hackers@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:37 PM -0700 11/20/99, Wes Peters wrote: >"Daniel C. Sobral" wrote: > > It was stated before that FreeBSD complies with POSIX except where > > POSIX is broken. Well, it's broken here. st_dev+st_ino *can't* work > > with modern, distributed filesystems (without undue overhead). > >It's not broken in this case. 2^16 (st_dev) is certainly enough to uniquely >indentify all mounted filesystems, and 2^32 is (by definition) enough to >uniquely indentify each of the files on a filesystem. Hmm, I'm not so sure. In AFS land we have 162 different cells "in AFS". Those cells are made up of 394 different machines which are exporting files. AFS exports "volumes", not bsd-style file systems. If you use st_dev to indicate the "cell", you will run into problems because a given volume can be mounted at multiple spots in the same cell. You can't use st_dev to indicate the server-machine being used either, because a volume can be replicated across multiple servers. It can also move from one server to another, without the AFS client ever seeing any event. So, st_dev pretty much has to be related to the AFS volume. I don't know the maximum number of volumes that a single AFS cell can have, but at RPI there's at least one volume for every userid (say, 10,000 volumes there), plus one backup-volume for every userid (so, 20,000 volumes), plus at least a few thousand more volumes for things unrelated to userids. Home directories are not replicated volumes, but many of the remaining volumes are replicated. Each replicated volume would have to be considered two separate volumes as far as this check is concerned. The "read-write" volume, and the "read-only" volume. My guess is that we (RPI) have over 32,000 volumes, and we're certainly not the largest AFS cell. It is perhaps useful to note that the "AFS volume ID" for my home directory is 536874209, although I am certainly not implying that we have that many different volumes in our cell. Given that there are over 160 cells, I'm pretty sure st_dev is simply not up to the task of giving a unique identifier for each volume which is mounted on a given AFS client machine. It is probably true that any one volume can not have more than 2^32 files in it. It is also probably true that you can not assume that the per-volume max-count of unique files is significantly smaller than 2^32 either. It's got to be at least 2^16, I would think. >Discussions (with strong, valid reasons) about expanding >the size of ino_t should be carried out on -arch. Mind you, I don't know what to suggest as a solution to this, so I don't have anything to send to -arch... --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 13:45:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id B544F14C83; Sat, 20 Nov 1999 13:45:47 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.0.4] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.092 #1) id 11pGfh-000JQ8-00; Sat, 20 Nov 1999 19:59:45 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.092 #1) id 11pGfh-0000Ai-00; Sat, 20 Nov 1999 19:59:45 +0000 Date: Sat, 20 Nov 1999 19:59:45 +0000 From: Ben Smithurst To: Wes Peters Cc: Kris Kennaway , andrew@ugh.net.au, Daniel O'Connor , hackers@freebsd.org Subject: Re: Making a port kit Message-ID: <19991120195945.B621@strontium.scientia.demon.co.uk> References: <3836F676.CB4D2D9F@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3836F676.CB4D2D9F@softweyr.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters wrote: > Nope, and it seems difficult to have a mistyped path when you don't have > any paths anywhere. The only paths are in the obliterate makefile: > > ~~~~~~~~~~~~~~~ snip ~~~~~~~~~~~~~~~~ > CFLAGS= -g > PROG= obliterate > SRCS= obliterate.c > MAN8= obliterate.8 > BINDIR= ${PREFIX}/bin > MANDIR= ${PREFIX}/man > > .include > ~~~~~~~~~~~~~~~ snip ~~~~~~~~~~~~~~~~ > > Which part of MANDIR did I misspell, the "m", "a", or "n"? I think it should be ${PREFIX}/man/man, I don't know why, but it should be from what I can tell. MAN8 should be in both Makefiles, with MANCOMPRESSED=yes set in the port Makefile as someone else suggested so the installation procedure doesn't try to compress them when they are already compressed. -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 16: 1:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from foo.sics.se (foo.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id D6E0714C84 for ; Sat, 20 Nov 1999 16:01:22 -0800 (PST) (envelope-from assar@foo.sics.se) Received: (from assar@localhost) by foo.sics.se (8.9.3/8.9.3) id BAA00832; Sun, 21 Nov 1999 01:01:29 +0100 (CET) (envelope-from assar) To: Garance A Drosihn Cc: hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? References: <3836DF98.9A84EC44@newsguy.com> <3836F873.D3B989FE@softweyr.com> From: Assar Westerlund Date: 21 Nov 1999 01:01:29 +0100 In-Reply-To: Garance A Drosihn's message of "Sat, 20 Nov 1999 16:43:04 -0500" Message-ID: <5l1z9kn25i.fsf@foo.sics.se> Lines: 17 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garance A Drosihn writes: > At 12:37 PM -0700 11/20/99, Wes Peters wrote: > >It's not broken in this case. 2^16 (st_dev) is certainly enough to uniquely > >indentify all mounted filesystems, and 2^32 is (by definition) enough to > >uniquely indentify each of the files on a filesystem. Why can't a file system have more than 2^32 files? > Hmm, I'm not so sure. In AFS land we have 162 different cells > "in AFS". Yeah, actually four 32-bit numbers identify all files in AFS-space uniquely. That would mean making `ino_t' be a 128-bit number. Can you say `long long long' ? (I don't think it's practical to use more than one device, and you would still need 112 bits). /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 17: 7:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id D5F8C15872 for ; Sat, 20 Nov 1999 17:07:08 -0800 (PST) (envelope-from nemesys@home.com) Received: from cr717730b ([24.112.177.211]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with SMTP id <19991121010511.VFQK7575.mail.rdc3.on.home.com@cr717730b>; Sat, 20 Nov 1999 17:05:11 -0800 Message-ID: <006801bf33bc$92248b80$d3b17018@wlfdle1.on.wave.home.com> From: "Jason Craig" To: "Matthew N. Dodd" Cc: "FreeBSD Hackers" References: Subject: Re: Compile new kernel with MCA support Date: Sat, 20 Nov 1999 20:05:58 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It worked like a charm. I've commented out the SMP portion of the kernel config, and inserted the controller mca0 like you said. I was actually going to try this when I created the kernel config file to begin with. But didn't bother. Guess I should have went with my instinct. Thanks, Jason ----- Original Message ----- From: Matthew N. Dodd To: Jason Craig Cc: FreeBSD Hackers Sent: Saturday, November 20, 1999 4:12 PM Subject: Re: Compile new kernel with MCA support > On Sat, 20 Nov 1999, Jason Craig wrote: > > Here's what I see when I boot with the kernel I compiled a few days ago: > > Humm... > > I see where the problem is. > > I'd like you to compile a kernel without SMP support but with MCA support. > > Add: > > controller mca0 > > I'm working on the SMP angle. > > > Copyright (c) 1982, 1986, 1989, 1991, 1993 > > The Regents of the University of California. All rights reserved. > > FreeBSD 4.0-19991113-CURRENT #0: Fri Nov 19 08:00:49 GMT 1999 > > > > root@cr717730-d.wlfdle1.on.wave.home.com:/usr/src/sys/compile/KERNEL.1119199 > > 9 > > Timecounter "i8254" frequency 1193182 Hz > > CPU: Pentium/P54C (89.96-MHz 586-class CPU) > > Origin = "GenuineIntel" Id = 0x525 Stepping = 5 > > Features=0x3bf > > real memory = 67108864 (65536K bytes) > > avail memory = 62033920 (60580K bytes) > > panic: unknown bus type: 'MCA' > > mp_lock = 00000004; cpuid = 0; lapic.id = 00000000 > > > > Boom... Locked up. > > > > When I created the custom kernel config for this machine I did removed > > devices that were not present in my system (as usual), and enabled SMP. > > > > # To make an SMP kernel, the next two are needed > > options SMP # Symmetric MultiProcessor Kernel > > options APIC_IO # Symmetric (APIC) I/O > > # Optionally these may need tweaked, (defaults shown): > > options NCPU=2 # number of CPUs > > #options NBUS=4 # number of busses > > #options NAPIC=1 # number of IO APICs > > #options NINTR=24 # number of INTs > > > > A little lower I noticed that there were no entries for MCA, should there be > > one? > > > > controller isa0 > > controller pnp0 # PnP support for ISA > > controller eisa0 > > controller pci0 > > > > Thans in advance, > > > > Jason > > > > > > > > > > ----- Original Message ----- > > From: Matthew N. Dodd > > To: Jason Craig > > Cc: > > Sent: Friday, November 19, 1999 8:56 PM > > Subject: Re: Compile new kernel with MCA support > > > > > > > On Fri, 19 Nov 1999, Jason Craig wrote: > > > > I have a few FreeBSD machines that I am playing around with now, and > > > > have come across a nice old IBM PC Server 320 with dual P90 processors > > > > and 64MB of RAM i would also like to utilize. > > > > > > > > I am currently using 4.0-19991113-CURRENT generic kernel, and things are > > > > working great. > > > > > > > > However, I tried to compile a custom kernel to weed out any unwanted > > > > devices, and to enable SMP and have have run into a problem. After > > > > compiling the kernel using the standard procedure, I rebooted it, and > > > > it panic'd after doing the kernel config. > > > > > > > > I tried removing most of the entries from /boot/kernel.conf, only to > > > > find it still panics saying something about the MCA bus. > > > > > > Using the serial console, capture the boot messages and attach them to the > > > reply to this message. > > > > > > -- > > > | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | > > > | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | > > > | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > > -- > | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | > | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | > | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 18:49:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id AFAD515169; Sat, 20 Nov 1999 18:49:08 -0800 (PST) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 2.12 #2) id 11pN3p-0000E8-00; Sat, 20 Nov 1999 19:49:06 -0700 Message-ID: <38375D9F.80C1DFA4@softweyr.com> Date: Sat, 20 Nov 1999 19:49:03 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Ben Smithurst Cc: Kris Kennaway , andrew@ugh.net.au, Daniel O'Connor , hackers@FreeBSD.ORG Subject: Re: Making a port kit References: <3836F676.CB4D2D9F@softweyr.com> <19991120195945.B621@strontium.scientia.demon.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Smithurst wrote: > > Wes Peters wrote: > > > > Which part of MANDIR did I misspell, the "m", "a", or "n"? > > I think it should be ${PREFIX}/man/man, I don't know why, but it > should be from what I can tell. Yes, that's it! The man page gets installed in ${MANDIR}${SECTION} is why this work; it knows the SECTION is 8. Duh. BTW, should this program go in ${PREFIX}/bin or ${PREFIX}/sbin? I guess since it's supposed to be a "secure rm" bin is the correct place. > MAN8 should be in both Makefiles, with > MANCOMPRESSED=yes set in the port Makefile as someone else suggested so > the installation procedure doesn't try to compress them when they are > already compressed. That didn't appear to do anything the first time, but now that I've done it CORRECTLY it seems to work like a charm. Stick it with a fork, it's DONE. I can make; make install; make deinstall; make reinstall; make clean and have nothing puke. Now maybe I can get off my butt and make port kits for a couple of other things I have lying about. Thanks, guys, as usual you've burned through the fog quickly. I'd have been done even quicker, but I spent last night and today doing REAL construction work on my new office, so I can dedicate more time to hacking FreeBSD once winter gets here. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 19:21:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id 5A52F14C19 for ; Sat, 20 Nov 1999 19:21:43 -0800 (PST) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 2.12 #2) id 11pNZO-0004jp-00; Sat, 20 Nov 1999 20:21:42 -0700 Message-ID: <38376544.96B017E9@softweyr.com> Date: Sat, 20 Nov 1999 20:21:40 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Daniel C. Sobral" Cc: John Polstra , Garance A Drosihn , hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? References: <3836DF98.9A84EC44@newsguy.com> <3836F873.D3B989FE@softweyr.com> <3836FF7C.2D8236AE@newsguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" wrote: > > Wes Peters wrote: > > > > It's not broken in this case. 2^16 (st_dev) is certainly enough to uniquely > > indentify all mounted filesystems, and 2^32 is (by definition) enough to > > uniquely indentify each of the files on a filesystem. Discussions (with > > strong, valid reasons) about expanding the size of ino_t should be carried > > out on -arch. > > Just to expand a little bit more, some distributed filesystems *do > not* have a unique identifier like the inode. So then the FreeBSD client software should create one? Do they just assign a random number as the st_ino when stat'ing the file? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 19:37:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id F1C4C15195 for ; Sat, 20 Nov 1999 19:37:43 -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.9.3/8.9.3) with SMTP id WAA03228; Sat, 20 Nov 1999 22:36:48 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Sat, 20 Nov 1999 22:36:48 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Wes Peters Cc: "Daniel C. Sobral" , John Polstra , Garance A Drosihn , hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? In-Reply-To: <38376544.96B017E9@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 20 Nov 1999, Wes Peters wrote: > "Daniel C. Sobral" wrote: > > > > Wes Peters wrote: > > > > > > It's not broken in this case. 2^16 (st_dev) is certainly enough to uniquely > > > indentify all mounted filesystems, and 2^32 is (by definition) enough to > > > uniquely indentify each of the files on a filesystem. Discussions (with > > > strong, valid reasons) about expanding the size of ino_t should be carried > > > out on -arch. > > > > Just to expand a little bit more, some distributed filesystems *do > > not* have a unique identifier like the inode. > > So then the FreeBSD client software should create one? Do they just assign > a random number as the st_ino when stat'ing the file? The problem isn't creating a unique number for a file, it's maintaining the consistency of that unique number over time -- the POSIX quote in question wanted the number to continue to identify the file over more than the single stat reference. Otherwise, we could assign random numbers, incrementing numbers, zero, etc, each reference. Using a unique 32-bit number to identify a file uniquely doesn't work for a large class of file systems, and therefore would appear to be an fs-specific piece of functionality -- something that should not be exposed in an fs-general way--i.e., in the VFS, which is supposed to describe features common across file systems. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 19:38:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id 9D9AA15195 for ; Sat, 20 Nov 1999 19:38:39 -0800 (PST) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 2.12 #2) id 11pNpm-0006Vq-00; Sat, 20 Nov 1999 20:38:39 -0700 Message-ID: <3837692E.3EDEFBF1@softweyr.com> Date: Sat, 20 Nov 1999 20:38:22 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Assar Westerlund Cc: Garance A Drosihn , hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? References: <3836DF98.9A84EC44@newsguy.com> <3836F873.D3B989FE@softweyr.com> <5l1z9kn25i.fsf@foo.sics.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Assar Westerlund wrote: > > Garance A Drosihn writes: > > At 12:37 PM -0700 11/20/99, Wes Peters wrote: > > >It's not broken in this case. 2^16 (st_dev) is certainly enough to uniquely > > >indentify all mounted filesystems, and 2^32 is (by definition) enough to > > >uniquely indentify each of the files on a filesystem. > > Why can't a file system have more than 2^32 files? Because if it does you can't stat it! There's a great case of circular reasoning for you. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 20:28: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from foo.sics.se (foo.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 5182515749 for ; Sat, 20 Nov 1999 20:27:58 -0800 (PST) (envelope-from assar@foo.sics.se) Received: (from assar@localhost) by foo.sics.se (8.9.3/8.9.3) id FAA03595; Sun, 21 Nov 1999 05:27:58 +0100 (CET) (envelope-from assar) To: Wes Peters , "Daniel C. Sobral" Cc: hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? References: <3836DF98.9A84EC44@newsguy.com> <3836F873.D3B989FE@softweyr.com> <3836FF7C.2D8236AE@newsguy.com> <38376544.96B017E9@softweyr.com> From: Assar Westerlund Date: 21 Nov 1999 05:27:57 +0100 In-Reply-To: Wes Peters's message of "Sat, 20 Nov 1999 20:21:40 -0700" Message-ID: <5ln1s88o4y.fsf@foo.sics.se> Lines: 23 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters writes: > "Daniel C. Sobral" wrote: > > > > Just to expand a little bit more, some distributed filesystems *do > > not* have a unique identifier like the inode. > > So then the FreeBSD client software should create one? Do they just assign > a random number as the st_ino when stat'ing the file? If there's none, you of course have to create one. As long as you keep giving the same `va_fileid' to the same file (by remembering what files you have seen), I guess that's ok. But then I don't know of any distributed filesystem that acts this way (what's `same' in the text above?). What filesystems are like that? Looking at some existing file systems: NFS - the server returns a 32-bit file-ID AFS/Arla - files are identified by (cell, volume, vnode, uniquifier) which is hashed down to a 32 bit fileno Coda - same as AFS/Arla /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 20:53:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id B3B3F14EA3 for ; Sat, 20 Nov 1999 20:53:20 -0800 (PST) (envelope-from nemesys@home.com) Received: from cr717730b ([24.112.177.211]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with SMTP id <19991121045123.YKGE7575.mail.rdc3.on.home.com@cr717730b>; Sat, 20 Nov 1999 20:51:23 -0800 Message-ID: <008d01bf33dc$2a9fca40$d3b17018@wlfdle1.on.wave.home.com> From: "Jason Craig" To: "Matthew N. Dodd" Cc: "FreeBSD Hackers" References: Subject: Re: Compile new kernel with MCA support Date: Sat, 20 Nov 1999 23:52:08 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I applied the patch, and it patched successfully. I did the usual /usr/sbin/config KERNEL, then make depend, and then make. During the make it bombed out and gave this message: cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmis sing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -a nsi -nostdinc -I- -I. -I../.. -I/usr/include -DKERNEL -include opt_global.h -elf ../../i386/i386/mp_machdep.c In file included from ../../i386/i386/mp_machdep.c:68: machine/mpapic.h:57: syntax error before `4' ../../i386/i386/mp_machdep.c:690: `MCA' undeclared here (not in a function) ../../i386/i386/mp_machdep.c:690: initializer element for `bus_type_table[3].type' is not constant ../../i386/i386/mp_machdep.c:693: `MCA' undeclared here (not in a function) ../../i386/i386/mp_machdep.c:693: initializer element for `bus_type_table[6].type' is not constant ../../i386/i386/mp_machdep.c:714: `MCA' undeclared here (not in a function) ../../i386/i386/mp_machdep.c:714: initializer element for `default_data[3][2]' is not constant ../../i386/i386/mp_machdep.c:717: `MCA' undeclared here (not in a function) ../../i386/i386/mp_machdep.c:717: initializer element for `default_data[6][2]' is not constant *** Error code 1 Stop in /usr/src/sys/compile/SMP.KERNEL.11201999. I think I found the problem though. In the mca_mp.patch file the line + MCA 4, I think it should read + MCA = 4,. ... Index: include/mpapic.h =================================================================== RCS file: /cvs/src/sys/i386/include/mpapic.h,v retrieving revision 1.12 diff -u -8 -r1.12 mpapic.h --- mpapic.h 1999/08/28 00:44:19 1.12 +++ mpapic.h 1999/11/20 21:26:18 @@ -49,16 +49,17 @@ */ #define NAPICID 16 /* these don't really belong in here... */ enum busTypes { CBUS = 1, CBUSII = 2, EISA = 3, + MCA 4, ISA = 6, PCI = 13, XPRESS = 18, MAX_BUSTYPE = 18, UNKNOWN_BUSTYPE = 0xff }; ... I changed the mpapic.h manually, and it compiled the rest of the kernel. However I have one more problem, probably not related to MCA now, but rather SMP in general. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-19991113-CURRENT #0: Sat Nov 20 18:25:10 EST 1999 root@cr717730-d.wlfdle1.on.wave.home.com:/usr/src/sys/compile/SMP.KERNEL.112 01999 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P54C (89.96-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping = 5 Features=0x3bf real memory = 67108864 (65536K bytes) avail memory = 62029824 (60576K bytes) Programming 16 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x000f0010, at 0xfec00000 MicroChannel Architecture System detected. Preloaded elf kernel "kernel" at 0xc02f3000. Intel Pentium detected, installing workaround for F00F bug ... ... ... ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 panic: APIC RTC != 8 mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 syncing disks... done Automatic reboot in 15 seconds - press a key on the console to abort Any ideas on this problem? Thanks, Jason ----- Original Message ----- From: Matthew N. Dodd To: Jason Craig Cc: FreeBSD Hackers Sent: Saturday, November 20, 1999 4:29 PM Subject: Re: Compile new kernel with MCA support > On Sat, 20 Nov 1999, Jason Craig wrote: > > panic: unknown bus type: 'MCA' > > mp_lock = 00000004; cpuid = 0; lapic.id = 00000000 > > Apply this patch: > > ftp://ftp.jurai.net/users/winter/patches/mca_mp.patch > > And let me know what happens. > > Thanks. > > -- > | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | > | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | > | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 20:56:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 4CF8815038 for ; Sat, 20 Nov 1999 20:56:34 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 2935F1CA0; Sun, 21 Nov 1999 12:56:33 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: "Jason Craig" Cc: "Matthew N. Dodd" , "FreeBSD Hackers" Subject: Re: Compile new kernel with MCA support In-reply-to: Your message of "Sat, 20 Nov 1999 23:52:08 EST." <008d01bf33dc$2a9fca40$d3b17018@wlfdle1.on.wave.home.com> Date: Sun, 21 Nov 1999 12:56:33 +0800 From: Peter Wemm Message-Id: <19991121045633.2935F1CA0@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jason Craig" wrote: > EISA = 3, > + MCA 4, > ISA = 6, Should be: MCA = 4, Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 20:59:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 4233C14D62 for ; Sat, 20 Nov 1999 20:59:31 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id XAA12662; Sat, 20 Nov 1999 23:59:30 -0500 (EST) Date: Sat, 20 Nov 1999 23:59:29 -0500 (EST) From: "Matthew N. Dodd" To: Jason Craig Cc: FreeBSD Hackers Subject: Re: Compile new kernel with MCA support In-Reply-To: <008d01bf33dc$2a9fca40$d3b17018@wlfdle1.on.wave.home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 20 Nov 1999, Jason Craig wrote: > I applied the patch, and it patched successfully. > I did the usual /usr/sbin/config KERNEL, then make depend, and then make. > During the make it bombed out and gave this message: Right, I missed that. :/ > I think I found the problem though. In the mca_mp.patch file the line + MCA > 4, I think it should read + MCA = 4,. Indeed. > I changed the mpapic.h manually, and it compiled the rest of the > kernel. However I have one more problem, probably not related to MCA > now, but rather SMP in general. If the system operates normally with a non SMP kernel then you may be correct though I'm not sure if any additional changes are needed to support SMP operation on an MCA system. Maybe a dump of your mptable would be useful? We may want to move this to the SMP mailing list. > panic: APIC RTC != 8 > mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 > > syncing disks... > done > Automatic reboot in 15 seconds - press a key on the console to abort -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 21:25: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles556.castles.com [208.214.165.120]) by hub.freebsd.org (Postfix) with ESMTP id 2D17F15788 for ; Sat, 20 Nov 1999 21:25: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.3/8.8.8) with ESMTP id VAA02741; Sat, 20 Nov 1999 21:15:41 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911210515.VAA02741@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Dennis Cc: hackers@freebsd.org Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) In-reply-to: Your message of "Sat, 20 Nov 1999 14:41:27 EST." <199911201944.OAA19595@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 20 Nov 1999 21:15:40 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'll test this in 3.3 shortly...has anything been done in this area? It > seems to happen on passive backplace systems (although its more likely the > chipsets used on SBCs)...my acer MB doesnt lock up with the same test. This > problem has been duplicated on more than 1 system with completely different > hardware. > > Any ideas? Nope. You haven't given anything like enough information to even guess at the nature of the problem. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 20 22: 1:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id 13FC514C1B for ; Sat, 20 Nov 1999 22:01:54 -0800 (PST) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 2.12 #2) id 11pQ4O-0007mt-00; Sat, 20 Nov 1999 23:01:53 -0700 Message-ID: <38378ACF.277A81DC@softweyr.com> Date: Sat, 20 Nov 1999 23:01:51 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Assar Westerlund Cc: "Daniel C. Sobral" , hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? References: <3836DF98.9A84EC44@newsguy.com> <3836F873.D3B989FE@softweyr.com> <3836FF7C.2D8236AE@newsguy.com> <38376544.96B017E9@softweyr.com> <5ln1s88o4y.fsf@foo.sics.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Assar Westerlund wrote: > > Wes Peters writes: > > "Daniel C. Sobral" wrote: > > > > > > Just to expand a little bit more, some distributed filesystems *do > > > not* have a unique identifier like the inode. > > > > So then the FreeBSD client software should create one? Do they just assign > > a random number as the st_ino when stat'ing the file? > > If there's none, you of course have to create one. As long as you > keep giving the same `va_fileid' to the same file (by remembering what > files you have seen), I guess that's ok. But then I don't know of any > distributed filesystem that acts this way (what's `same' in the text > above?). What filesystems are like that? > > Looking at some existing file systems: > > NFS - the server returns a 32-bit file-ID The only one I had available, which didn't look like a problem. > AFS/Arla - files are identified by (cell, volume, vnode, > uniquifier) which is hashed down to a 32 bit fileno > Coda - same as AFS/Arla Are hash collisions handled reasonably? I.e. does the test for st_dev/ st_ino uniquely identifying the file during an entire single mount session hold true? If so, no problem. If not, I can name at least one popular security manager program that is going to have a conniption fit. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message