From owner-freebsd-hackers Sun Nov 12 3: 1:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from henny.webweaving.org (unknown [212.113.16.243]) by hub.freebsd.org (Postfix) with ESMTP id 29D8537B479; Sun, 12 Nov 2000 03:01:40 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id KAA49186; Sun, 12 Nov 2000 10:44:42 GMT (envelope-from n_hibma@qubesoft.com) Date: Sun, 12 Nov 2000 10:44:42 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@henny.webweaving.org Reply-To: Nick Hibma To: Chris Dillon Cc: James FitzGibbon , hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: USB-to-SCSI converter 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 don't know. The only thing I know is that the protocol on the USB wire does not let you select the SCSI id, just the LUN. Nick On Fri, 10 Nov 2000, Chris Dillon wrote: > On Fri, 10 Nov 2000, Nick Hibma wrote: > > > This makes sense as the adapter is not a ful controller, just a > > cheapo interface. > > > > You cannot select the SCSI id from the USB driver. > > Hmm.. Since I was looking for a "true" USB-SCSI controller, obviously > this thing won't work. If it only works with devices set to ID 0, it > will never work with a SCSI ZIP drive which only has settings for ID 5 > or 6 (which is one thing I would use it with). Do the Shuttle-based > USB-SCSI adapters have the same limitation? > > > -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net > FreeBSD: The fastest and most stable server OS on the planet. > For IA32 and Alpha architectures. IA64 and PowerPC under development. > http://www.freebsd.org > > -- Qube Software, Ltd. Private: n_hibma@qubesoft.com n_hibma@webweaving.org n_hibma@freebsd.org http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 12 4:37: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay2.wertep.com (relay2.wertep.com [194.44.90.130]) by hub.freebsd.org (Postfix) with ESMTP id B4EBC37B65F for ; Sun, 12 Nov 2000 04:37:00 -0800 (PST) Received: from She.wertep.com (she-tun-proxy [192.168.252.2]) by relay2.wertep.com (8.9.3/8.9.3) with ESMTP id OAA30623 for ; Sun, 12 Nov 2000 14:36:57 +0200 (EET) (envelope-from petro@She.wertep.com) Received: from localhost (petro@localhost) by She.wertep.com (8.9.3/8.9.3) with ESMTP id OAA04176 for ; Sun, 12 Nov 2000 14:37:02 +0200 (EET) (envelope-from petro@She.wertep.com) Date: Sun, 12 Nov 2000 14:37:02 +0200 (EET) From: petro To: freebsd-hackers@FreeBSD.ORG Subject: ISA on EISA. 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! I have the following question I had Compaq Proliant with 5 EISA slots and I would like to insert into it ISA cards. Is it possible or it is unpossible, if possible where I can read about this. Thank you very much..... Petro. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 12 4:50:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 3E5F737B479 for ; Sun, 12 Nov 2000 04:50:09 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13uwaF-0003qK-00; Sun, 12 Nov 2000 12:50:07 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.0) id eAC0rcS00368; Sun, 12 Nov 2000 01:53:38 +0100 (CET) (envelope-from wkb) Date: Sun, 12 Nov 2000 01:53:38 +0100 From: Wilko Bulte To: petro Cc: freebsd-hackers@freebsd.org Subject: Re: ISA on EISA. Message-ID: <20001112015337.A322@freebie.demon.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from petro@She.wertep.com on Sun, Nov 12, 2000 at 02:37:02PM +0200 X-OS: FreeBSD 4.2-BETA X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 12, 2000 at 02:37:02PM +0200, petro wrote: > Hello! > I have the following question I had Compaq Proliant with 5 EISA slots and > I would like to insert into it ISA cards. Is it possible or it is > unpossible, if possible where I can read about this. EISA slots can accomodate ISA cards. Please run the SCU/ECU utility to tell your EISA system BIOS what resources (irq, ioranges etc) your ISA card uses. -- Wilko Bulte Arnhem, the Netherlands wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 12 9:54:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.tor3.targetnet.com (smtp.tor3.targetnet.com [207.176.132.71]) by hub.freebsd.org (Postfix) with ESMTP id 41E4037B479; Sun, 12 Nov 2000 09:54:43 -0800 (PST) Received: from james by smtp.tor3.targetnet.com with local (Exim 3.16 #1) id 13v1KN-000AQG-00; Sun, 12 Nov 2000 12:54:03 -0500 Date: Sun, 12 Nov 2000 12:54:03 -0500 From: James FitzGibbon To: Nick Hibma Cc: Chris Dillon , hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: USB-to-SCSI converter Message-ID: <20001112125403.A3835@targetnet.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from n_hibma@qubesoft.com on Sun, Nov 12, 2000 at 10:44:42AM +0000 Organization: Targetnet.com Inc. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Nick Hibma (n_hibma@qubesoft.com) [001112 06:01]: > I don't know. The only thing I know is that the protocol on the USB > wire does not let you select the SCSI id, just the LUN. I've confirmed that under Windows this cable works with any SCSI ID, but only if you install the Microtech driver. Otherwise, it doesn't show up (i.e. identical to FBSD). Presuming that their driver is actually just a ID mapping layer, would the same thing be feasible under BSD? I'll fire off a note to their support people and see if they can at least confirm my line of thinking here. -- j. James FitzGibbon james@targetnet.com Targetnet.com Inc. Voice/Fax +1 416 306-0466/0452 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 12 10:26:23 2000 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 9F3D437B479 for ; Sun, 12 Nov 2000 10:26:19 -0800 (PST) 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 KAA12884; Sun, 12 Nov 2000 10:26:15 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.0/8.11.0) id eACIQBn40198; Sun, 12 Nov 2000 10:26:11 -0800 (PST) (envelope-from jdp) Date: Sun, 12 Nov 2000 10:26:11 -0800 (PST) Message-Id: <200011121826.eACIQBn40198@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Reply-To: hackers@freebsd.org Cc: ken@cleveland.lug.net Subject: Re: [OT] serial protocol analyzer In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , kf wrote: > I don't remember the url anymore, but I do remember that there was > a Japanese guy who wrote drivers for digital cameras, cameras which > connected to the serial port of a PC to download the pictures. On > his site he mentioned a (free?) package which he used to analyze the > "conversation" between the camera and the PC. Right. That's the "comms/snooper" port that I recommended. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 12 13:39:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.unixbox.com (shell.unixbox.com [207.211.45.65]) by hub.freebsd.org (Postfix) with ESMTP id CD4DB37B479 for ; Sun, 12 Nov 2000 13:39:53 -0800 (PST) Received: from localhost (fengyue@localhost) by shell.unixbox.com (8.11.0/8.11.0) with ESMTP id eACLeXF23519 for ; Sun, 12 Nov 2000 13:40:33 -0800 (PST) Date: Sun, 12 Nov 2000 13:40:33 -0800 (PST) From: FengYue X-Sender: fengyue@shell.unixbox.com To: hackers@freebsd.org Subject: PPPoE w/ nat auto fragmentation hack? 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, Any of you happened to hack the PPPoE support on Fbsd 4.x to automatically fragment the IP datagram if whatever device behind the NAT refuses to adjust its MTU? Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 12 14: 2:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 7C1C837B479 for ; Sun, 12 Nov 2000 14:02:37 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.1/8.11.1) with ESMTP id eACM0LF02520; Sun, 12 Nov 2000 22:00:21 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.1/8.11.1) with ESMTP id eACM0sB04688; Sun, 12 Nov 2000 22:00:54 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200011122200.eACM0sB04688@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: FengYue Cc: hackers@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: PPPoE w/ nat auto fragmentation hack? In-Reply-To: Message from FengYue of "Sun, 12 Nov 2000 13:40:33 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 12 Nov 2000 22:00:54 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hi, Any of you happened to hack the PPPoE support on Fbsd 4.x to > automatically fragment the IP datagram if whatever device behind the > NAT refuses to adjust its MTU? There's a ``tcpmssd'' port. > Thanks -- 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 Sun Nov 12 16:32:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from heorot.1nova.com (sub24-23.member.dsl-only.net [63.105.24.23]) by hub.freebsd.org (Postfix) with ESMTP id BF0B837B479 for ; Sun, 12 Nov 2000 16:32:51 -0800 (PST) Received: by heorot.1nova.com (Postfix, from userid 1000) id 052273271; Sat, 11 Nov 2000 16:56:25 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by heorot.1nova.com (Postfix) with ESMTP id E65373270; Sat, 11 Nov 2000 16:56:25 +0000 (GMT) Date: Sat, 11 Nov 2000 16:56:25 +0000 (GMT) From: Rick Hamell To: petro Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: ISA on EISA. 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 > Hello! > I have the following question I had Compaq Proliant with 5 EISA slots and > I would like to insert into it ISA cards. Is it possible or it is > unpossible, if possible where I can read about this. For the most part, yes. I've ran across one or two places where ISA cards won't run in EISA slots but that was mostly with Packard Bell and Acer. Rick ******************************************************************* Rick's FreeBSD Web page http://heorot.1nova.com/freebsd Ace Logan's Hardware Guide http://www.shatteredcrystal.net/hardware ***FreeBSD - The Power to Serve! 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 Sun Nov 12 20:16:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from uranium.dashmail.net (uranium.dashmail.net [216.36.26.29]) by hub.freebsd.org (Postfix) with ESMTP id E858737B479 for ; Sun, 12 Nov 2000 20:16:56 -0800 (PST) Received: from no1spec (rc1s7p8.dashmail.net [216.36.33.80]) by uranium.dashmail.net (8.10.1/8.10.1) with SMTP id eAD4TBW43618 for ; Mon, 13 Nov 2000 04:29:11 GMT From: "Chris Ptacek" To: Subject: KLDs and PCI? Date: Sun, 12 Nov 2000 20:16:21 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am working on a KLD for a PCI device. My problem is I can't find how to call the probe and attach calls during the load for a PCI device. I have looked in the /usr/src/sys/pci directory and haven't found any KLDs to use as an example. What are the steps I need to take to handle a PCI device in a KLD? Are there any examples I can look out? Oh yeah, I am doing this for a FreeBSD 3.x system (I know, but is needed for this project, it will be ported to 4.x later) - Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 12 22:42:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rjlhome.sco.com (unknown [207.65.180.181]) by hub.freebsd.org (Postfix) with ESMTP id 47F1137B479 for ; Sun, 12 Nov 2000 22:42:53 -0800 (PST) Received: by rjlhome.sco.com (8.9.3/SCO5) id AAA16520 for freebsd-hackers@freebsd.org; Mon, 13 Nov 2000 00:44:10 -0600 (CST) Date: Mon, 13 Nov 2000 00:44:10 -0600 From: Robert Lipe To: freebsd-hackers@freebsd.org Subject: pci bus enumeration & cdevsw indexing Message-ID: <20001113004410.W20018@rjlhome.sco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm new to FreeBSD, but an experienced kernel guy. I'm workgin with 4.1.1 on IA32 and need help understanding the ways of your world. :-) I'd like my project to look like a "normal" driver and use supported interfaces, but I'll patch the core code if I need to. I have a need to walk the PCI bus, gleaning PCI IDs and other data. (Yes, I know a dozen reasons why to NOT do that.) What I *almost* need is the loop in pci_ioctl that walks pci_dev[]. The catch here is that this is a private data structure (static, lots of dependencies on private headers not in , etc) and therefore unavailable. I considered calling the ioctl code myself from withing my driver, but that seems too weird. I thought about shipping the data to myself by way of user-space (daemon does an ioctl ('pciconf -l'ish) to PCI driver, turns around and hands data to me on an ioctl) but that sounds like an application to be punished. Is there a "normal" way for a conforming driver to walk the busses, pluck out bus number, slot number, device id, subsystem id, and all that traditional stuff, or do I just need to carve up pci.c and build my own interface to do it? Also, I have a question on loadable character devices. Is there a way to avoid the hard-coded major numbers in the cdevsw[] entry that's passed? It seems like make_dev() should be able to roam cdevsw, find an empty slot, and create the dev nodes for me. I'm envisioning a very dynamic system with lots of modules (enough that we really don't want to allocate them with a human involved) being popped in and out and would like to not handle the major number management and inevitable conflicts on my own. How is this handled for, say, third-party drivers? Thanx for any help offered. RJL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 12 22:59:38 2000 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 D68AC37B479 for ; Sun, 12 Nov 2000 22:59:35 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA63724; Sun, 12 Nov 2000 23:59:32 -0700 (MST) (envelope-from ken) Date: Sun, 12 Nov 2000 23:59:32 -0700 From: "Kenneth D. Merry" To: Robert Lipe Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: pci bus enumeration & cdevsw indexing Message-ID: <20001112235932.A63657@panzer.kdm.org> References: <20001113004410.W20018@rjlhome.sco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20001113004410.W20018@rjlhome.sco.com>; from robertlipe@usa.net on Mon, Nov 13, 2000 at 12:44:10AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 13, 2000 at 00:44:10 -0600, Robert Lipe wrote: > I'm new to FreeBSD, but an experienced kernel guy. I'm workgin with > 4.1.1 on IA32 and need help understanding the ways of your world. :-) > I'd like my project to look like a "normal" driver and use supported > interfaces, but I'll patch the core code if I need to. > > I have a need to walk the PCI bus, gleaning PCI IDs and other data. > (Yes, I know a dozen reasons why to NOT do that.) What I *almost* > need is the loop in pci_ioctl that walks pci_dev[]. The catch here is > that this is a private data structure (static, lots of dependencies on > private headers not in , etc) and therefore unavailable. I > considered calling the ioctl code myself from withing my driver, but > that seems too weird. I thought about shipping the data to myself by > way of user-space (daemon does an ioctl ('pciconf -l'ish) to PCI driver, > turns around and hands data to me on an ioctl) but that sounds like an > application to be punished. > > Is there a "normal" way for a conforming driver to walk the busses, > pluck out bus number, slot number, device id, subsystem id, and all that > traditional stuff, or do I just need to carve up pci.c and build my own > interface to do it? Well, it might help if we understood a little more about why you want to look at all the devices on the PCI bus. There are certainly plenty of reasons to do it, but there may be other/better ways to get the functionality you need. (I've done it from userland, FWIW. I also wrote the current PCIOCGETCONF code.) What does your driver do? If you do need to get at the data, the easiest thing to do would be to un-staticize pci_devq (in pci.c), and include pci/pcivar.h in your program, to get the definition for struct pci_devinfo. If this is an embedded-type project that's going to involve shipping already-compiled code, I wouldn't worry too much about modifying the PCI code. If this is a driver you're going to want to ship in source or module form, we'll likely need to work out how you're going to do it (i.e. what changes will go into the tree), so the module or driver will work when it is loaded or compiled. [ ...major numbers for loadable devices... ] Someone who knows more about modules can answer that one... 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 13 0:34: 6 2000 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 BD0FC37B479 for ; Mon, 13 Nov 2000 00:34:03 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAD8Y3m18694 for hackers@freebsd.org; Mon, 13 Nov 2000 00:34:03 -0800 (PST) Date: Mon, 13 Nov 2000 00:34:03 -0800 From: Alfred Perlstein To: hackers@freebsd.org Subject: pointer for thread safe resolver stuff? Message-ID: <20001113003402.F11449@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey, I'm not having much fun trying to find threadsafe code to do gethostbyname_r, someone pointed me at Bind9 which has what looks like some threadsafe stuff, however I can't seem to find any docco for it. (such as how to init the hostent that I pass to it and which functions are trully threadsafe) I'm going to keep reading the library source (and cursing the ISC) but I was wondering if anyone knew of any docs for the bind9 stuff or any other thread safe (non-GPL'd) resolver library. thanks, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 0:37: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (unknown [167.216.157.206]) by hub.freebsd.org (Postfix) with ESMTP id 5F64937B479 for ; Mon, 13 Nov 2000 00:37:04 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAD8hAF01093; Mon, 13 Nov 2000 00:43:10 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011130843.eAD8hAF01093@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Robert Lipe Cc: freebsd-hackers@freebsd.org Subject: Re: pci bus enumeration & cdevsw indexing In-reply-to: Your message of "Mon, 13 Nov 2000 00:44:10 CST." <20001113004410.W20018@rjlhome.sco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Nov 2000 00:43:10 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm new to FreeBSD, but an experienced kernel guy. I'm workgin with > 4.1.1 on IA32 and need help understanding the ways of your world. :-) > I'd like my project to look like a "normal" driver and use supported > interfaces, but I'll patch the core code if I need to. This willingness is good. 8) > I have a need to walk the PCI bus, gleaning PCI IDs and other data. > (Yes, I know a dozen reasons why to NOT do that.) What I *almost* > need is the loop in pci_ioctl that walks pci_dev[]. The catch here is > that this is a private data structure (static, lots of dependencies on > private headers not in , etc) and therefore unavailable. I > considered calling the ioctl code myself from withing my driver, but > that seems too weird. I thought about shipping the data to myself by > way of user-space (daemon does an ioctl ('pciconf -l'ish) to PCI driver, > turns around and hands data to me on an ioctl) but that sounds like an > application to be punished. It's definitely not the "right" way to do things. As Ken asked - why are you doing things this way? Are the devices you're interested in likely to be attached to by drivers of their own? Is your driver always going to be in the kernel, or is it liable to be loaded as a module? > Is there a "normal" way for a conforming driver to walk the busses, > pluck out bus number, slot number, device id, subsystem id, and all that > traditional stuff, or do I just need to carve up pci.c and build my own > interface to do it? There isn't a "normal" way for this, because in our view of the world that's the wrong way to do it. (Whether that's absolutely right is entirely open to debate, of course.) In most cases, you can achieve the same thing using other techniques. > Also, I have a question on loadable character devices. Is there a way > to avoid the hard-coded major numbers in the cdevsw[] entry that's > passed? It seems like make_dev() should be able to roam cdevsw, find > an empty slot, and create the dev nodes for me. I'm envisioning a very > dynamic system with lots of modules (enough that we really don't want to > allocate them with a human involved) being popped in and out and would > like to not handle the major number management and inevitable conflicts > on my own. This is what devfs is meant to achieve. Unfortunately at the moment the major numbers need to be fixed because there's no dynamism in /dev. If you don't need the /dev nodes, then of course you don't need major numbers at all... > How is this handled for, say, third-party drivers? Typically in the past we've just handed out major numbers to vendors wanting to ship public drivers, or for in-house stuff just advocated using the "local" ranges. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 0:38:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (unknown [167.216.157.206]) by hub.freebsd.org (Postfix) with ESMTP id 7B15F37B4C5 for ; Mon, 13 Nov 2000 00:38:24 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAD8iVF01116; Mon, 13 Nov 2000 00:44:31 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011130844.eAD8iVF01116@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Chris Ptacek" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: KLDs and PCI? In-reply-to: Your message of "Sun, 12 Nov 2000 20:16:21 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Nov 2000 00:44:31 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am working on a KLD for a PCI device. My problem is I can't find how to > call the probe and attach calls during the load for a PCI device. I have > looked in the /usr/src/sys/pci directory and haven't found any KLDs to use > as an example. What are the steps I need to take to handle a PCI device in > a KLD? Are there any examples I can look out? > > Oh yeah, I am doing this for a FreeBSD 3.x system (I know, but is needed for > this project, it will be ported to 4.x later) You can't (properly) do this with 3.x. You might want to track down Kevin Van Maren, however, who cooked up a technique for doing it. I don't have a current email address for him easily to hand; I'd recommend checking the FreeBSD list archives though. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 1: 1:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from henny.webweaving.org (unknown [212.113.16.243]) by hub.freebsd.org (Postfix) with ESMTP id 2CDFB37B4CF; Mon, 13 Nov 2000 01:01:21 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id IAA51179; Mon, 13 Nov 2000 08:58:00 GMT (envelope-from n_hibma@qubesoft.com) Date: Mon, 13 Nov 2000 08:58:00 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@henny.webweaving.org Reply-To: Nick Hibma To: James FitzGibbon Cc: Chris Dillon , hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: USB-to-SCSI converter In-Reply-To: <20001112125403.A3835@targetnet.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 In that case it might be that they are using some kind of private command to set the SCSI subsequently to different IDs. I'll check whether I have the device here and if so, I will try and snoop that command off the wire. Thanks for the pointer! Nick On Sun, 12 Nov 2000, James FitzGibbon wrote: > * Nick Hibma (n_hibma@qubesoft.com) [001112 06:01]: > > > I don't know. The only thing I know is that the protocol on the USB > > wire does not let you select the SCSI id, just the LUN. > > I've confirmed that under Windows this cable works with any SCSI ID, but > only if you install the Microtech driver. Otherwise, it doesn't show up > (i.e. identical to FBSD). Presuming that their driver is actually just a > ID mapping layer, would the same thing be feasible under BSD? > > I'll fire off a note to their support people and see if they can at least > confirm my line of thinking here. > > -- > j. > > James FitzGibbon james@targetnet.com > Targetnet.com Inc. Voice/Fax +1 416 306-0466/0452 > -- Qube Software, Ltd. Private: n_hibma@qubesoft.com n_hibma@webweaving.org n_hibma@freebsd.org http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 5:22:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id EE73937B479; Mon, 13 Nov 2000 05:22:09 -0800 (PST) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id HAA44176; Mon, 13 Nov 2000 07:22:04 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Mon, 13 Nov 2000 07:22:04 -0600 (CST) From: Chris Dillon To: Nick Hibma Cc: James FitzGibbon , hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: USB-to-SCSI converter 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 Sun, 12 Nov 2000, Nick Hibma wrote: > I don't know. The only thing I know is that the protocol on the > USB wire does not let you select the SCSI id, just the LUN. Since you can select the LUN and not the ID, maybe they've mapped SCSI ID0:LUN0 to ID0:LUN0 (duh), ID1:LUN0 to ID0:LUN1, ID2:LUN0 to ID0:LUN2, and so on, which would explain why we only see a device at ID0:LUN0 if we aren't looking at the remaining LUNs (are we?). This would mean that you can't use multi-LUN devices with the USB-SCSI converter, but that is much more acceptable than only being able to use ID0 with it. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64 and PowerPC under development. 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 Mon Nov 13 5:58:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.rila.bg (earth.rila.bg [212.39.75.31]) by hub.freebsd.org (Postfix) with ESMTP id BBF7A37B479 for ; Mon, 13 Nov 2000 05:58:39 -0800 (PST) Received: from earth.rila.bg (localhost [127.0.0.1]) by earth.rila.bg (8.11.1/8.11.1) with ESMTP id eADDwOj00390 for ; Mon, 13 Nov 2000 15:58:26 +0200 (EET) (envelope-from mitko@earth.rila.bg) Message-Id: <200011131358.eADDwOj00390@earth.rila.bg> X-Mailer: exmh version 2.1.1 10/15/1999 To: hackers@freebsd.org Reply-To: mitko@rila.bg From: "Dimitar V. Peikov" Subject: STABLE ATAPI CD-ROM Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Nov 2000 15:58:23 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yesterday, I've CVSuped -STABLE and UPGRADE using information in /usr/src/UPDATING from 4.1.1-STABLE. make buildworld make buildkernel KERNEL=YOUR_KERNEL_HERE make installkernel KERNEL=YOUR_KERNEL_HERE reboot (in single user) [1] make installworld mergemaster reboot The problem is that my CD-ROM device suddenly disappeared. It worked before I made this upgrade. I use DELL OptiPlex GX300 with atapci0: port 0xffa0-0xffaf at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ad0: 9765MB [19841/16/63] at ata0-master UDMA66 In my kernel config file for ATA devices I have : device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives #options ATA_STATIC_ID #Static device numbering #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices It's strange that ata1 is not recognized during boot procedure. I've tried to remove both lines from config file that described ata0 and ata1 but the result was the same. Any ideas? -- Dimitar Peikov Programmer Analyst "We Build e-Business" RILA Solutions 27 Building, Acad.G.Bonchev Str. 1113 Sofia, Bulgaria home: (+359 2) 595495 phone: (+359 2) 9797320 phone: (+359 2) 9797300 fax: (+359 2) 9733355 http://www.rila.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 6: 4:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id C3E1037B479 for ; Mon, 13 Nov 2000 06:04:25 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id PAA77287; Mon, 13 Nov 2000 15:02:27 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200011131402.PAA77287@freebsd.dk> Subject: Re: STABLE ATAPI CD-ROM In-Reply-To: <200011131358.eADDwOj00390@earth.rila.bg> from "Dimitar V. Peikov" at "Nov 13, 2000 03:58:23 pm" To: mitko@rila.bg Date: Mon, 13 Nov 2000 15:02:27 +0100 (CET) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Dimitar V. Peikov wrote: > > Yesterday, I've CVSuped -STABLE and UPGRADE using information in > /usr/src/UPDATING from 4.1.1-STABLE. Re-cvsup, this has been fixed... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 6:50:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rjlhome.sco.com (unknown [207.65.180.181]) by hub.freebsd.org (Postfix) with ESMTP id 4394237B4E5 for ; Mon, 13 Nov 2000 06:50:24 -0800 (PST) Received: by rjlhome.sco.com (8.9.3/SCO5) id IAA23535; Mon, 13 Nov 2000 08:51:37 -0600 (CST) Date: Mon, 13 Nov 2000 08:51:37 -0600 From: Robert Lipe To: "Kenneth D. Merry" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: pci bus enumeration & cdevsw indexing Message-ID: <20001113085137.X20018@rjlhome.sco.com> References: <20001113004410.W20018@rjlhome.sco.com> <20001112235932.A63657@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20001112235932.A63657@panzer.kdm.org>; from ken@kdm.org on Sun, Nov 12, 2000 at 11:59:32PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth D. Merry wrote: > On Mon, Nov 13, 2000 at 00:44:10 -0600, Robert Lipe wrote: > > I have a need to walk the PCI bus, gleaning PCI IDs and other data. > > (Yes, I know a dozen reasons why to NOT do that.) What I *almost* > > need is the loop in pci_ioctl that walks pci_dev[]. The catch here is > > Well, it might help if we understood a little more about why you want to > look at all the devices on the PCI bus. There are certainly plenty of > reasons to do it, but there may be other/better ways to get the That's fair. I should have expected to "defend" against those dozen reasons. :-) > What does your driver do? It's not a driver as much as driver infrastructure. To measure the difficulty of porting the UDI Reference Implementation (available source soon!) I decided to try porting it to an OS that I knew little about. UDI has a concept somewhat like that expressed in the core BSD bus enumeration code where you have a bus/bridge driver that enumerates children (additional busses or cards) which may each enumerate additional children. It looks like the normal BSD interfaces to the PCI bus assumes that I am one of those children. This is understandable and has parallels in UDI-land. What I really want is to be able to walk the installed/supported busses for a chance to bind them to UDI drivers. So I don't really want to replace the existing tree-builder, I'd like to make something somewhat parallel to it. Alternately, if there's a standard interface to a system configuration database that stores this tree, I could walk that table and hand that information to my bridge driver. UnixWare (resmgr), HP/UX (cdio) , and AIX (can't recall the name of it) have such interfaces. > If you do need to get at the data, the easiest thing to do would be to > un-staticize pci_devq (in pci.c), and include pci/pcivar.h in your program, > to get the definition for struct pci_devinfo. I went down that path, but then got sucked into a morass of chained includes that didn't have an obvious end. It looks like pci_devq has most of the interesting information that I'm looking for. (Not suprising since I'm wanting to do with that data pretty much what pci.c is doing with it...) > code. If this is a driver you're going to want to ship in source or module > form, It is. I'd like the reference implementation to ship in source form. It currently make extensive use of modules. > we'll likely need to work out how you're going to do it (i.e. what > changes will go into the tree), so the module or driver will work when > it is loaded or compiled. I'll come up with a set of changes to pci.c that won't nauseate everyone. Thanx, RJL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 7: 0:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rjlhome.sco.com (unknown [207.65.180.181]) by hub.freebsd.org (Postfix) with ESMTP id AC24C37B4CF; Mon, 13 Nov 2000 07:00:53 -0800 (PST) Received: by rjlhome.sco.com (8.9.3/SCO5) id JAA23903; Mon, 13 Nov 2000 09:02:17 -0600 (CST) Date: Mon, 13 Nov 2000 09:02:17 -0600 From: Robert Lipe To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: pci bus enumeration & cdevsw indexing Message-ID: <20001113090217.Y20018@rjlhome.sco.com> References: <20001113004410.W20018@rjlhome.sco.com> <200011130843.eAD8hAF01093@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200011130843.eAD8hAF01093@mass.osd.bsdi.com>; from msmith@freebsd.org on Mon, Nov 13, 2000 at 12:43:10AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have a need to walk the PCI bus, gleaning PCI IDs and other data. > > (Yes, I know a dozen reasons why to NOT do that.) What I *almost* > > need is the loop in pci_ioctl that walks pci_dev[]. The catch here is > > you doing things this way? [ Answered in separate message. ] > Are the devices you're interested in likely to be attached to by > drivers of their own? Yes. I'm writing the bridge driver. It will then enumerate/bind/attach child devices which are drivers of their own. > Is your driver always going to be in the kernel, or is it liable to be > loaded as a module? I like modules. I think this whole thing would be a numer of modules. > > to avoid the hard-coded major numbers in the cdevsw[] entry that's > > passed? It seems like make_dev() should be able to roam cdevsw, find > > This is what devfs is meant to achieve. Unfortunately at the moment the > major numbers need to be fixed because there's no dynamism in /dev. If If you have devfs (and it means the same to you that it does to other OSes) that would solve the problem nicely. So is devfs something in 4.1.1 or is it future work? If it's here now, can you point me to an example? If it's future work, is that where I should be focusing? > > How is this handled for, say, third-party drivers? > > Typically in the past we've just handed out major numbers to vendors > wanting to ship public drivers, or for in-house stuff just advocated using > the "local" ranges. For a UDI driver, that would be a problem. A UDI driver-writer has no clue where his target device will be running and, indeed, could be running on an OS without a /dev. So we could carve out a pool of b and c major numbers for UDI to then dynamically manage on behalf of the drivers, but that seems tedious. The environment has enough bread crumbs to know of a given driver is an HBA, a NIC, or something else and can set things up appropriately behind the scenes. RJL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 7: 1:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from c014.sfo.cp.net (c014-h023.c014.sfo.cp.net [209.228.12.87]) by hub.freebsd.org (Postfix) with SMTP id 5595C37B4C5 for ; Mon, 13 Nov 2000 07:01:35 -0800 (PST) Received: (cpmta 28229 invoked from network); 13 Nov 2000 07:01:34 -0800 Received: from m12hRs4n205.midsouth.rr.com (HELO mike) (24.95.125.205) by smtp.valuedata.net (209.228.12.87) with SMTP; 13 Nov 2000 07:01:34 -0800 X-Sent: 13 Nov 2000 15:01:34 GMT Message-ID: <007d01c04d82$a1157880$0200000a@mike> From: "Daryl Chance" To: "FreeBSD Hackers" Subject: Smart And Friendly Burner? Date: Mon, 13 Nov 2000 09:01:40 -0600 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.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Anyone else have a smart and friendly cd burner? When I boot I get this: /kernel: acd0: CDROM at ata1-master using UDMA33 /kernel: ata1-slave: timeout waiting for command=ef s=00 e=00 /kernel: ata1-slave: timeout waiting for command=ef s=00 e=00 /kernel: ata1-slave: CDROM device -NO DRIVER! I'm running 4.2 RC1 (the iso out on the ftp site). I've since recompiled the kernel (commenting out a lot of things) and I get this now: /kernel: acd1: CD-RW at ata1-slave using WDMA2 So it looks fine now. I haven't added to the kernel, just removed stuff. If needed, I could send the conf file. Daryl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 7:39:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.tor3.targetnet.com (smtp.tor3.targetnet.com [207.176.132.71]) by hub.freebsd.org (Postfix) with ESMTP id DB2BB37B479; Mon, 13 Nov 2000 07:39:26 -0800 (PST) Received: from james by smtp.tor3.targetnet.com with local (Exim 3.16 #1) id 13vLgy-000OHH-00; Mon, 13 Nov 2000 10:38:44 -0500 Date: Mon, 13 Nov 2000 10:38:44 -0500 From: James FitzGibbon To: Chris Dillon Cc: Nick Hibma , hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: USB-to-SCSI converter Message-ID: <20001113103844.A91950@targetnet.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from cdillon@wolves.k12.mo.us on Mon, Nov 13, 2000 at 07:22:04AM -0600 Organization: Targetnet.com Inc. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Chris Dillon (cdillon@wolves.k12.mo.us) [001113 08:22]: > On Sun, 12 Nov 2000, Nick Hibma wrote: > > > I don't know. The only thing I know is that the protocol on the > > USB wire does not let you select the SCSI id, just the LUN. > > Since you can select the LUN and not the ID, maybe they've mapped SCSI > ID0:LUN0 to ID0:LUN0 (duh), ID1:LUN0 to ID0:LUN1, ID2:LUN0 to > ID0:LUN2, and so on, which would explain why we only see a device at > ID0:LUN0 if we aren't looking at the remaining LUNs (are we?). This > would mean that you can't use multi-LUN devices with the USB-SCSI > converter, but that is much more acceptable than only being able to > use ID0 with it. I've got a Nakamichi mj-4.8s (4 disc scsi jukebox) at home that I can put in an external case to test this premise. It comes up as the chosen ID and LUNS 0-3. -- j. James FitzGibbon james@targetnet.com Targetnet.com Inc. Voice/Fax +1 416 306-0466/0452 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 8:49:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id D8AE737B65E for ; Mon, 13 Nov 2000 08:49:43 -0800 (PST) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eADGndR07117; Mon, 13 Nov 2000 09:49:39 -0700 (MST) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.1/8.8.3) with ESMTP id eADGp9G40549; Mon, 13 Nov 2000 09:51:13 -0700 (MST) Message-Id: <200011131651.eADGp9G40549@billy-club.village.org> To: "Chris Ptacek" Subject: Re: KLDs and PCI? Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 12 Nov 2000 20:16:21 PST." References: Date: Mon, 13 Nov 2000 09:51:09 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Chris Ptacek" writes: : I am working on a KLD for a PCI device. My problem is I can't find how to : call the probe and attach calls during the load for a PCI device. I have : looked in the /usr/src/sys/pci directory and haven't found any KLDs to use : as an example. What are the steps I need to take to handle a PCI device in : a KLD? Are there any examples I can look out? It just works for PCI in 4.0 and newer. : Oh yeah, I am doing this for a FreeBSD 3.x system (I know, but is needed for : this project, it will be ported to 4.x later) Ah. Well, that's different. You should be able to look at the if_* directory because it has klds in 3.x and they seem to get their probe routines called when loaded after boot. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 8:51:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 56FBD37B4C5 for ; Mon, 13 Nov 2000 08:51:16 -0800 (PST) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eADGpDR07132; Mon, 13 Nov 2000 09:51:13 -0700 (MST) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.1/8.8.3) with ESMTP id eADGqkG40565; Mon, 13 Nov 2000 09:52:47 -0700 (MST) Message-Id: <200011131652.eADGqkG40565@billy-club.village.org> To: Robert Lipe Subject: Re: pci bus enumeration & cdevsw indexing Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 13 Nov 2000 00:44:10 CST." <20001113004410.W20018@rjlhome.sco.com> References: <20001113004410.W20018@rjlhome.sco.com> Date: Mon, 13 Nov 2000 09:52:46 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001113004410.W20018@rjlhome.sco.com> Robert Lipe writes: : Is there a "normal" way for a conforming driver to walk the busses, : pluck out bus number, slot number, device id, subsystem id, and all that : traditional stuff, or do I just need to carve up pci.c and build my own : interface to do it? You may need to carve up pci.c, but there will likely be resistance to such a change. You rarely, if ever, need to do this from a driver. : Also, I have a question on loadable character devices. Is there a way : to avoid the hard-coded major numbers in the cdevsw[] entry that's : passed? It seems like make_dev() should be able to roam cdevsw, find : an empty slot, and create the dev nodes for me. I'm envisioning a very : dynamic system with lots of modules (enough that we really don't want to : allocate them with a human involved) being popped in and out and would : like to not handle the major number management and inevitable conflicts : on my own. No. Get a major number from us and avoid confusion. Or wait for 5.0 and devfs. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 9:26:49 2000 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 BFB6F37B479 for ; Mon, 13 Nov 2000 09:26:44 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA67038; Mon, 13 Nov 2000 10:26:42 -0700 (MST) (envelope-from ken) Date: Mon, 13 Nov 2000 10:26:42 -0700 From: "Kenneth D. Merry" To: Robert Lipe Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: pci bus enumeration & cdevsw indexing Message-ID: <20001113102641.B66956@panzer.kdm.org> References: <20001113004410.W20018@rjlhome.sco.com> <20001112235932.A63657@panzer.kdm.org> <20001113085137.X20018@rjlhome.sco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20001113085137.X20018@rjlhome.sco.com>; from robertlipe@usa.net on Mon, Nov 13, 2000 at 08:51:37AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 13, 2000 at 08:51:37 -0600, Robert Lipe wrote: > Kenneth D. Merry wrote: > > What does your driver do? > > It's not a driver as much as driver infrastructure. To measure the > difficulty of porting the UDI Reference Implementation (available source > soon!) I decided to try porting it to an OS that I knew little about. Ahh. > UDI has a concept somewhat like that expressed in the core BSD bus > enumeration code where you have a bus/bridge driver that enumerates > children (additional busses or cards) which may each enumerate > additional children. It looks like the normal BSD interfaces to the PCI > bus assumes that I am one of those children. This is understandable and > has parallels in UDI-land. > > What I really want is to be able to walk the installed/supported busses > for a chance to bind them to UDI drivers. So I don't really want to > replace the existing tree-builder, I'd like to make something somewhat > parallel to it. > > Alternately, if there's a standard interface to a system configuration > database that stores this tree, I could walk that table and hand that > information to my bridge driver. UnixWare (resmgr), HP/UX (cdio) , and > AIX (can't recall the name of it) have such interfaces. That is probably the direction you want to go in. We've got a device infrastructure already (new-bus), which is probably what you want to use. If you probed and attached UDI devices apart from new-bus, you'll probably run into all sorts of resource conflicts. (cards with two drivers attached and stepping on each other...) Unfortunately I don't know much about new-bus, so I can't tell you how easy it would be to do what you want to do with it. (There are other folks on this list who do know, though.) I do know that we have the concept of probe priorities, so you could probably set up UDI to probe at a higher priority than the default system drivers, and therefore attach instead of the default FreeBSD driver for a given piece of harware. > > If you do need to get at the data, the easiest thing to do would be to > > un-staticize pci_devq (in pci.c), and include pci/pcivar.h in your program, > > to get the definition for struct pci_devinfo. > > I went down that path, but then got sucked into a morass of chained > includes that didn't have an obvious end. It looks like pci_devq > has most of the interesting information that I'm looking for. (Not > suprising since I'm wanting to do with that data pretty much what pci.c > is doing with it...) Yep. That's probably not the way to go for what you're doing, though. > > code. If this is a driver you're going to want to ship in source or module > > form, > > It is. I'd like the reference implementation to ship in source form. > It currently make extensive use of modules. Cool, it'll be interesting to see the source. 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 13 9:46:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rjlhome.sco.com (unknown [207.65.180.181]) by hub.freebsd.org (Postfix) with ESMTP id AD8A737B4D7 for ; Mon, 13 Nov 2000 09:46:54 -0800 (PST) Received: by rjlhome.sco.com (8.9.3/SCO5) id LAA29875; Mon, 13 Nov 2000 11:48:15 -0600 (CST) Date: Mon, 13 Nov 2000 11:48:15 -0600 From: Robert Lipe To: "Kenneth D. Merry" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: pci bus enumeration & cdevsw indexing Message-ID: <20001113114815.D29431@rjlhome.sco.com> References: <20001113004410.W20018@rjlhome.sco.com> <20001112235932.A63657@panzer.kdm.org> <20001113085137.X20018@rjlhome.sco.com> <20001113102641.B66956@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20001113102641.B66956@panzer.kdm.org>; from ken@kdm.org on Mon, Nov 13, 2000 at 10:26:42AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth D. Merry wrote: > On Mon, Nov 13, 2000 at 08:51:37 -0600, Robert Lipe wrote: > > Kenneth D. Merry wrote: > > That is probably the direction you want to go in. We've got a device > infrastructure already (new-bus), which is probably what you want to use. This is the second mention I've heard of this. I'm about to travel, but will investigate newbus upon my return. > If you probed and attached UDI devices apart from new-bus, you'll probably > run into all sorts of resource conflicts. (cards with two drivers attached > and stepping on each other...) We have variations of this problems in other OSes. If you have two different drivers for the exact same piece of hardware, which one do you use? (One of the OSes answers "both" which works really well when you pop the second one in and it resets the hardware that's controlling your root filesystem. :-) > I do know that we have the concept of probe priorities, so you could > probably set up UDI to probe at a higher priority than the default system > drivers, and therefore attach instead of the default FreeBSD driver for a > given piece of harware. That's clever. > > It is. I'd like the reference implementation to ship in source form. > > It currently make extensive use of modules. > > Cool, it'll be interesting to see the source. It's a brief time (low nubmer of weeks) until the NDAs on the reference implementation go away. I have the core stuff up on FreeBSD/IA32, but I probably won't be able to get it over the finish line by myself. Many of the concepts have mapped very well so far. Thanx, RJL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 10:23:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 8565337B479 for ; Mon, 13 Nov 2000 10:23:07 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id TAA35683; Mon, 13 Nov 2000 19:21:23 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200011131821.TAA35683@freebsd.dk> Subject: Re: Smart And Friendly Burner? In-Reply-To: <007d01c04d82$a1157880$0200000a@mike> from Daryl Chance at "Nov 13, 2000 09:01:40 am" To: dchance@valuedata.net (Daryl Chance) Date: Mon, 13 Nov 2000 19:21:23 +0100 (CET) Cc: hackers@FreeBSD.ORG (FreeBSD Hackers) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Daryl Chance wrote: > Hi, > > Anyone else have a smart and friendly cd burner? When I boot I get this: > > /kernel: acd0: CDROM at ata1-master using > UDMA33 > /kernel: ata1-slave: timeout waiting for command=ef s=00 e=00 > /kernel: ata1-slave: timeout waiting for command=ef s=00 e=00 > /kernel: ata1-slave: CDROM device -NO DRIVER! > > I'm running 4.2 RC1 (the iso out on the ftp site). I've since recompiled > the kernel (commenting out a lot of things) and I get this now: > > /kernel: acd1: CD-RW at ata1-slave using WDMA2 > > So it looks fine now. I haven't added to the kernel, just removed stuff. > If needed, I could send the conf file. You dont mention what version on FreeBSD we are talking about here, in any case you should upgrade to the latest version on the branch you are on... What exactly have you removed ? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 10:42:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from c014.sfo.cp.net (c014-h023.c014.sfo.cp.net [209.228.12.87]) by hub.freebsd.org (Postfix) with SMTP id B48F937B479 for ; Mon, 13 Nov 2000 10:42:31 -0800 (PST) Received: (cpmta 24750 invoked from network); 13 Nov 2000 10:42:30 -0800 Received: from m12hRs4n205.midsouth.rr.com (HELO mike) (24.95.125.205) by smtp.valuedata.net (209.228.12.87) with SMTP; 13 Nov 2000 10:42:30 -0800 X-Sent: 13 Nov 2000 18:42:30 GMT Message-ID: <009d01c01a85$52838f20$0200000a@mike> From: "Daryl Chance" To: "Soren Schmidt" Cc: "FreeBSD Hackers" References: <200011131821.TAA35683@freebsd.dk> Subject: Re: Smart And Friendly Burner? Date: Sat, 9 Sep 2000 12:42:27 -0500 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_009A_01C01A5B.6905AE60" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_009A_01C01A5B.6905AE60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit I burned the copy from the 4.2RC1 iso found on the ftp site. doing a list on / shows the kernel was compiled on Nov 7th. When I recompiled the kernel (not adding, just commenting stuff out) It showed the message that looked fine. (/kernel: acd1: CD-RW at ata1-slave using WDMA2) The first message I got with the default kernel. I went ahead and attached my config file. HTH, ----------------------------------------------------------------------- | Daryl Chance | We start seeing these new accounts being created, | | -------------- | but that could be an anomaly of the system. After | | Valuedata, LLC | a day or two, we realized it was someone hacking | | Memphis, TN | into the system. - Microsoft on thier hacker | ----------------------------------------------------------------------- ----- Original Message ----- From: "Soren Schmidt" To: "Daryl Chance" Cc: "FreeBSD Hackers" Sent: Monday, November 13, 2000 1:21 PM Subject: Re: Smart And Friendly Burner? > It seems Daryl Chance wrote: > > Hi, > > > > Anyone else have a smart and friendly cd burner? When I boot I get this: > > > > /kernel: acd0: CDROM at ata1-master using > > UDMA33 > > /kernel: ata1-slave: timeout waiting for command=ef s=00 e=00 > > /kernel: ata1-slave: timeout waiting for command=ef s=00 e=00 > > /kernel: ata1-slave: CDROM device -NO DRIVER! > > > > I'm running 4.2 RC1 (the iso out on the ftp site). I've since recompiled > > the kernel (commenting out a lot of things) and I get this now: > > > > /kernel: acd1: CD-RW at ata1-slave using WDMA2 > > > > So it looks fine now. I haven't added to the kernel, just removed stuff. > > If needed, I could send the conf file. > > You dont mention what version on FreeBSD we are talking about here, in > any case you should upgrade to the latest version on the branch you > are on... > > What exactly have you removed ? > > -Søren > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > ------=_NextPart_000_009A_01C01A5B.6905AE60 Content-Type: application/octet-stream; name="chancedj" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="chancedj" #=0A= # GENERIC -- Generic kernel configuration file for FreeBSD/i386=0A= #=0A= # For more information on this file, please read the handbook section on=0A= # Kernel Configuration Files:=0A= #=0A= # http://www.FreeBSD.org/handbook/kernelconfig-config.html=0A= #=0A= # The handbook is also available locally in /usr/share/doc/handbook=0A= # if you've installed the doc distribution, otherwise always see the=0A= # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the=0A= # latest information.=0A= #=0A= # An exhaustive list of options and more detailed explanations of the=0A= # device lines is also present in the ./LINT configuration file. If you = are=0A= # in doubt as to the purpose or necessity of a line, check first in LINT.=0A= #=0A= # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.20 2000/10/31 23:16:07 = n_hibma Exp $=0A= =0A= machine i386=0A= #cpu I386_CPU=0A= #cpu I486_CPU=0A= #cpu I586_CPU=0A= cpu I686_CPU=0A= ident GENERIC=0A= maxusers 32=0A= =0A= #makeoptions DEBUG=3D-g #Build kernel with gdb(1) debug symbols=0A= =0A= options MATH_EMULATE #Support for x87 emulation=0A= options INET #InterNETworking=0A= #options INET6 #IPv6 communications protocols=0A= options FFS #Berkeley Fast Filesystem=0A= options FFS_ROOT #FFS usable as root device [keep this!]=0A= options SOFTUPDATES #Enable FFS soft updates support=0A= #options MFS #Memory Filesystem=0A= #options MD_ROOT #MD is a potential root device=0A= #options NFS #Network Filesystem=0A= #options NFS_ROOT #NFS usable as root device, NFS required=0A= #options MSDOSFS #MSDOS Filesystem=0A= options CD9660 #ISO 9660 Filesystem=0A= options CD9660_ROOT #CD-ROM usable as root, CD9660 required=0A= options PROCFS #Process filesystem=0A= options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!]=0A= #options SCSI_DELAY=3D15000 #Delay (in ms) before probing SCSI=0A= #options UCONSOLE #Allow users to grab the console=0A= #options USERCONFIG #boot -c editor=0A= #options VISUAL_USERCONFIG #visual boot -c editor=0A= #options KTRACE #ktrace(1) support=0A= options SYSVSHM #SYSV-style shared memory=0A= options SYSVMSG #SYSV-style message queues=0A= options SYSVSEM #SYSV-style semaphores=0A= options P1003_1B #Posix P1003_1B real-time extensions=0A= options _KPOSIX_PRIORITY_SCHEDULING=0A= options ICMP_BANDLIM #Rate limit bad replies=0A= options KBD_INSTALL_CDEV # install a CDEV entry in /dev=0A= =0A= # To make an SMP kernel, the next two are needed=0A= #options SMP # Symmetric MultiProcessor Kernel=0A= #options APIC_IO # Symmetric (APIC) I/O=0A= =0A= device isa=0A= device eisa=0A= device pci=0A= =0A= # Floppy drives=0A= device fdc0 at isa? port IO_FD1 irq 6 drq 2=0A= device fd0 at fdc0 drive 0=0A= device fd1 at fdc0 drive 1=0A= =0A= # ATA and ATAPI devices=0A= #device ata0 at isa? port IO_WD1 irq 14=0A= #device ata1 at isa? port IO_WD2 irq 15=0A= device ata=0A= device atadisk # ATA disk drives=0A= device atapicd # ATAPI CDROM drives=0A= #device atapifd # ATAPI floppy drives=0A= #device atapist # ATAPI tape drives=0A= options ATA_STATIC_ID #Static device numbering=0A= options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices=0A= =0A= # SCSI Controllers=0A= #device ahb # EISA AHA1742 family=0A= #device ahc # AHA2940 and onboard AIC7xxx devices=0A= #device amd # AMD 53C974 (Teckram DC-390(T))=0A= #device isp # Qlogic family=0A= #device ncr # NCR/Symbios Logic=0A= #device sym # NCR/Symbios Logic (newer chipsets)=0A= #options SYM_SETUP_LP_PROBE_MAP=3D0x40=0A= # Allow ncr to attach legacy NCR devices when=0A= # both sym and ncr are configured=0A= =0A= #device adv0 at isa?=0A= #device adw=0A= #device bt0 at isa?=0A= #device aha0 at isa?=0A= #device aic0 at isa?=0A= =0A= #device ncv # NCR 53C500=0A= #device nsp # Workbit Ninja SCSI-3=0A= #device stg # TMC 18C30/18C50=0A= =0A= # SCSI peripherals=0A= #device scbus # SCSI bus (required)=0A= #device da # Direct Access (disks)=0A= #device sa # Sequential Access (tape etc)=0A= #device cd # CD=0A= #device pass # Passthrough device (direct SCSI access)=0A= =0A= # RAID controllers interfaced to the SCSI subsystem=0A= #device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID=0A= #device dpt # DPT Smartcache - See LINT for options!=0A= #device mly # Mylex AcceleRAID/eXtremeRAID=0A= =0A= # RAID controllers=0A= #device ida # Compaq Smart RAID=0A= #device amr # AMI MegaRAID=0A= #device mlx # Mylex DAC960 family=0A= #device twe # 3ware Escalade=0A= =0A= # atkbdc0 controls both the keyboard and the PS/2 mouse=0A= device atkbdc0 at isa? port IO_KBD=0A= device atkbd0 at atkbdc? irq 1 flags 0x1=0A= device psm0 at atkbdc? irq 12=0A= =0A= device vga0 at isa?=0A= =0A= # splash screen/screen saver=0A= pseudo-device splash=0A= =0A= # syscons is the default console driver, resembling an SCO console=0A= device sc0 at isa? flags 0x100=0A= =0A= # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver=0A= #device vt0 at isa?=0A= #options XSERVER # support for X server on a vt console=0A= #options FAT_CURSOR # start with block cursor=0A= # If you have a ThinkPAD, uncomment this along with the rest of the PCVT = lines=0A= #options PCVT_SCANSET=3D2 # IBM keyboards are non-std=0A= =0A= # Floating point support - do not disable.=0A= device npx0 at nexus? port IO_NPX irq 13=0A= =0A= # Power management support (see LINT for more options)=0A= device apm0 at nexus? disable flags 0x20 # Advanced Power Management=0A= =0A= # PCCARD (PCMCIA) support=0A= #device card=0A= #device pcic0 at isa? irq 0 port 0x3e0 iomem 0xd0000=0A= #device pcic1 at isa? irq 0 port 0x3e2 iomem 0xd4000 disable=0A= =0A= # Serial (COM) ports=0A= #device sio0 at isa? port IO_COM1 flags 0x10 irq 4=0A= #device sio1 at isa? port IO_COM2 irq 3=0A= #device sio2 at isa? disable port IO_COM3 irq 5=0A= #device sio3 at isa? disable port IO_COM4 irq 9=0A= =0A= # Parallel port=0A= #device ppc0 at isa? irq 7=0A= #device ppbus # Parallel port bus (required)=0A= #device lpt # Printer=0A= #device plip # TCP/IP over parallel=0A= #device ppi # Parallel port interface device=0A= #device vpo # Requires scbus and da=0A= =0A= =0A= # PCI Ethernet NICs.=0A= #device de # DEC/Intel DC21x4x (``Tulip'')=0A= #device fxp # Intel EtherExpress PRO/100B (82557, 82558)=0A= #device tx # SMC 9432TX (83c170 ``EPIC'')=0A= #device vx # 3Com 3c590, 3c595 (``Vortex'')=0A= #device wx # Intel Gigabit Ethernet Card (``Wiseman'')=0A= =0A= # PCI Ethernet NICs that use the common MII bus controller code.=0A= # NOTE: Be sure to keep the 'device miibus' line in order to use these = NICs!=0A= device miibus # MII bus support=0A= device dc # DEC/Intel 21143 and various workalikes=0A= #device pcn # AMD Am79C79x PCI 10/100 NICs=0A= #device rl # RealTek 8129/8139=0A= #device sf # Adaptec AIC-6915 (``Starfire'')=0A= #device sis # Silicon Integrated Systems SiS 900/SiS 7016=0A= #device ste # Sundance ST201 (D-Link DFE-550TX)=0A= #device tl # Texas Instruments ThunderLAN=0A= #device vr # VIA Rhine, Rhine II=0A= #device wb # Winbond W89C840F=0A= #device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'')=0A= =0A= # ISA Ethernet NICs.=0A= #device ed0 at isa? port 0x280 irq 10 iomem 0xd8000=0A= #device ex=0A= #device ep=0A= #device fe0 at isa? port 0x300=0A= # WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really=0A= # exists only as a PCMCIA device, so there is no ISA attatement needed=0A= # and resources will always be dynamically assigned by the pccard code.=0A= #device wi=0A= # Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below = will=0A= # work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP=0A= # mode (the factory default). If you set the switches on your ISA=0A= # card for a manually chosen I/O address and IRQ, you must specify=0A= # those paremeters here.=0A= #device an=0A= # Xircom Ethernet=0A= #device xe=0A= # The probe order of these is presently determined by = i386/isa/isa_compat.c.=0A= #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000=0A= #device le0 at isa? port 0x300 irq 5 iomem 0xd0000=0A= #device lnc0 at isa? port 0x280 irq 10 drq 0=0A= #device cs0 at isa? port 0x300=0A= #device sn0 at isa? port 0x300 irq 10=0A= =0A= # Pseudo devices - the number indicates how many units to allocated.=0A= pseudo-device loop # Network loopback=0A= pseudo-device ether # Ethernet support=0A= #pseudo-device sl 1 # Kernel SLIP=0A= #pseudo-device ppp 1 # Kernel PPP=0A= #pseudo-device tun # Packet tunnel.=0A= pseudo-device pty # Pseudo-ttys (telnet etc)=0A= #pseudo-device md # Memory "disks"=0A= #pseudo-device gif 4 # IPv6 and IPv4 tunneling=0A= #pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation)=0A= =0A= # The `bpf' pseudo-device enables the Berkeley Packet Filter.=0A= # Be aware of the administrative consequences of enabling this!=0A= pseudo-device bpf #Berkeley packet filter=0A= =0A= # USB support=0A= device uhci # UHCI PCI->USB interface=0A= device ohci # OHCI PCI->USB interface=0A= device usb # USB Bus (required)=0A= device ugen # Generic=0A= device uhid # "Human Interface Devices"=0A= #device ukbd # Keyboard=0A= #device ulpt # Printer=0A= #device umass # Disks/Mass storage - Requires scbus and da=0A= device ums # Mouse=0A= #device uscanner # Scanners=0A= # USB Ethernet, requires mii=0A= #device aue # ADMtek USB ethernet=0A= #device cue # CATC USB ethernet=0A= #device kue # Kawasaki LSI USB ethernet=0A= ------=_NextPart_000_009A_01C01A5B.6905AE60-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 10:43:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 630F737B69E; Mon, 13 Nov 2000 10:43:02 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp245.osd.bsdi.com [204.216.28.245]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id eADIgjB57242; Mon, 13 Nov 2000 10:42:45 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 13 Nov 2000 10:43:11 -0800 (PST) From: John Baldwin To: Zhiui Zhang Subject: RE: simple lock and the lost wakeup problem Cc: freebsd-smp@FreeBSD.org, freebsd-hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12-Nov-00 Zhiui Zhang wrote: > > I am new to SMP subject and have some questions to ask: > > Is the simplelock() really needed since FreeBSD is using the big giant > lock and the kernel is non preemptive? Or has FreeBSD changed the big > giant lock and made kernel thread preemptive? Uresha Vahalia talks about > Lost Wakeup Problem (page 196), the test of the resource and sleep() has > to be done atomically. Which correct mechanism should I use on FreeBSD to > achieve this (avoid the lost-wakeup problem)? simplelocks are used in interrupt handlers and a few other places that do not run while holding the big giant lock. In -current all of this has changed, however, as we now have mutexes. Most of the kernel is still under the Giant mutex at this point in time, but in the future Giant will be replaced by many other locks that protect data structures within the kernel. To avoid the lost wakeup problem I think you are referring to (I don't have Unix Internals here with me @ home) in -current, we have a replacment for tsleep() called msleep(). msleep() takes an additional parameter which is a mutex to release when going to sleep. From the kernel's perspective, the mutex is released and the process is put to sleep as an atomic operation. Hope this helps. > Any help is appreciated. > > -Zhihui > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Mon Nov 13 10:48: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 8306737B479; Mon, 13 Nov 2000 10:47:55 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13vOe1-0006ah-00; Mon, 13 Nov 2000 18:47:54 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.0) id eAD6pSv01865; Mon, 13 Nov 2000 07:51:28 +0100 (CET) (envelope-from wkb) Date: Mon, 13 Nov 2000 07:51:28 +0100 From: Wilko Bulte To: James FitzGibbon Cc: Chris Dillon , Nick Hibma , hackers@freebsd.org, scsi@freebsd.org Subject: Re: USB-to-SCSI converter Message-ID: <20001113075128.F1643@freebie.demon.nl> References: <20001113103844.A91950@targetnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20001113103844.A91950@targetnet.com>; from james@targetnet.com on Mon, Nov 13, 2000 at 10:38:44AM -0500 X-OS: FreeBSD 4.2-BETA X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 13, 2000 at 10:38:44AM -0500, James FitzGibbon wrote: > * Chris Dillon (cdillon@wolves.k12.mo.us) [001113 08:22]: > > On Sun, 12 Nov 2000, Nick Hibma wrote: > > > > > I don't know. The only thing I know is that the protocol on the > > > USB wire does not let you select the SCSI id, just the LUN. > > > > Since you can select the LUN and not the ID, maybe they've mapped SCSI > > ID0:LUN0 to ID0:LUN0 (duh), ID1:LUN0 to ID0:LUN1, ID2:LUN0 to > > ID0:LUN2, and so on, which would explain why we only see a device at > > ID0:LUN0 if we aren't looking at the remaining LUNs (are we?). This > > would mean that you can't use multi-LUN devices with the USB-SCSI > > converter, but that is much more acceptable than only being able to > > use ID0 with it. > > I've got a Nakamichi mj-4.8s (4 disc scsi jukebox) at home that I can put in > an external case to test this premise. It comes up as the chosen ID and > LUNS 0-3. And the nice thing is that it is known-good on FreeBSD on plain SCSI. I have one here on 4.2-beta which works like a charm. -- Wilko Bulte Arnhem, the Netherlands wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 10:58:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from beast.daemontech.com (beast.daemontech.com [208.138.46.45]) by hub.freebsd.org (Postfix) with SMTP id E66FD37B479 for ; Mon, 13 Nov 2000 10:58:39 -0800 (PST) Received: (qmail 23709 invoked for bounce); 13 Nov 2000 18:58:39 -0000 Received: from xwin.nmhtech.com (208.138.46.10) by beast.daemontech.com with SMTP; 13 Nov 2000 18:58:39 -0000 Content-Length: 2470 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 13 Nov 2000 10:58:39 -0800 (PST) Organization: Daemon Technologies From: Nicole Harrington To: freebsd-hackers@freebsd.org Subject: Log analysis program running under apache reboots server! Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings all.. I have been trying to test an apache log analizing program called Nettracker (wwww.sane.com) the program seems nice except for the fact that it keeps rebooting/crashing the server. This would just be labeled crappy software except for the fact that I am running the software as user apache and have setup process limits in login.conf and it is still able to reboot the server. This seems like a real problem and security issue as I have setup limits in /etc/login.conf (see below) and the program is being run via CGI as user apache, yet it is still capable of rebooting the system. Seems like a nice hack to me. If anyone could check over my login.conf settings below and make sure they are correct/ truly usefull, I would really appreciate it! Also any information on how this program could so easily reboot the server would be nice too. Thanks!! Nicole System is 4.1-STABLE and has 256 Megs of memory and 4X that of swap. apacheuser:\ :manpath=/usr/share/man /usr/X11R6/man /usr/local/man:\ :cputime=4h:\ :datasize=64M:\ :stacksize=4M:\ :filesize=infinity:\ :memoryuse=64M:\ :priority=0:\ :datasize-cur=32M:\ :stacksize-cur=32M:\ :coredumpsize-cur=0:\ :maxmemorysize-cur=64M:\ :memorylocked=32M:\ :maxproc=128:\ :openfiles=256:\ :tc=standard: ## standard - standard user defaults ## standard:\ :copyright=/etc/COPYRIGHT:\ :welcome=/etc/motd:\ :setenv=MAIL=/var/mail/$,BLOCKSIZE=K:\ :path=~/bin /bin /usr/bin /usr/local/bin:\ :manpath=/usr/share/man /usr/local/man:\ :nologin=/var/run/nologin:\ :cputime=1h30m:\ :datasize=8M:\ :stacksize=2M:\ :memorylocked=4M:\ :memoryuse=8M:\ :filesize=8M:\ :coredumpsize=8M:\ :openfiles=24:\ :maxproc=32:\ :priority=0:\ :requirehome:\ :passwordtime=90d:\ :umask=002:\ :ignoretime@:\ :tc=default: default:\ :cputime=infinity:\ :datasize-cur=22M:\ :stacksize-cur=8M:\ :memorylocked-cur=10M:\ :memoryuse-cur=30M:\ :filesize=infinity:\ :coredumpsize=infinity:\ :maxproc-cur=64:\ :openfiles-cur=64:\ :priority=0:\ :requirehome@:\ :umask=022:\ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 11:15:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from femail1.sdc1.sfba.home.com (femail1.sdc1.sfba.home.com [24.0.95.81]) by hub.freebsd.org (Postfix) with ESMTP id 3628C37B4C5 for ; Mon, 13 Nov 2000 11:15:32 -0800 (PST) Received: from beastie.localdomain ([24.19.158.41]) by femail1.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20001113191515.MESZ14040.femail1.sdc1.sfba.home.com@beastie.localdomain>; Mon, 13 Nov 2000 11:15:15 -0800 Received: (from brian@localhost) by beastie.localdomain (8.9.3/8.8.7) id LAA13441; Mon, 13 Nov 2000 11:18:37 -0800 (PST) (envelope-from brian) Date: Mon, 13 Nov 2000 11:18:37 -0800 From: "Brian O'Shea" To: Nicole Harrington Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Log analysis program running under apache reboots server! Message-ID: <20001113111837.J622@beastie.localdomain> Reply-To: boshea@ricochet.net Mail-Followup-To: Nicole Harrington , freebsd-hackers@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Nicole Harrington on Mon, Nov 13, 2000 at 10:58:39AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nicole, Is it a panic, or does it just silently reboot? If it's a panic, what is the panic message, or any other message on the console when the system crashes? Also, can you get a crash dump? (see the dumpon(8) man page) -brian On Mon, Nov 13, 2000 at 10:58:39AM -0800, Nicole Harrington wrote: > Greetings all.. > > I have been trying to test an apache log analizing program called Nettracker > (wwww.sane.com) the program seems nice except for the fact that it keeps > rebooting/crashing the server. This would just be labeled crappy software > except for the fact that I am running the software as user apache and have > setup process limits in login.conf and it is still able to reboot the server. > > This seems like a real problem and security issue as I have setup limits in > /etc/login.conf (see below) and the program is being run via CGI as user > apache, yet it is still capable of rebooting the system. Seems like a nice > hack > to me. > > If anyone could check over my login.conf settings below and make sure they > are > correct/ truly usefull, I would really appreciate it! Also any information on > how this program could so easily reboot the server would be nice too. > > Thanks!! > > > Nicole > > System is 4.1-STABLE and has 256 Megs of memory and 4X that of swap. > > apacheuser:\ > :manpath=/usr/share/man /usr/X11R6/man /usr/local/man:\ > :cputime=4h:\ > :datasize=64M:\ > :stacksize=4M:\ > :filesize=infinity:\ > :memoryuse=64M:\ > :priority=0:\ > :datasize-cur=32M:\ > :stacksize-cur=32M:\ > :coredumpsize-cur=0:\ > :maxmemorysize-cur=64M:\ > :memorylocked=32M:\ > :maxproc=128:\ > :openfiles=256:\ > :tc=standard: > > ## standard - standard user defaults > ## > standard:\ > :copyright=/etc/COPYRIGHT:\ > :welcome=/etc/motd:\ > :setenv=MAIL=/var/mail/$,BLOCKSIZE=K:\ > :path=~/bin /bin /usr/bin /usr/local/bin:\ > :manpath=/usr/share/man /usr/local/man:\ > :nologin=/var/run/nologin:\ > :cputime=1h30m:\ > :datasize=8M:\ > :stacksize=2M:\ > :memorylocked=4M:\ > :memoryuse=8M:\ > :filesize=8M:\ > :coredumpsize=8M:\ > :openfiles=24:\ > :maxproc=32:\ > :priority=0:\ > :requirehome:\ > :passwordtime=90d:\ > :umask=002:\ > :ignoretime@:\ > :tc=default: > > default:\ > :cputime=infinity:\ > :datasize-cur=22M:\ > :stacksize-cur=8M:\ > :memorylocked-cur=10M:\ > :memoryuse-cur=30M:\ > :filesize=infinity:\ > :coredumpsize=infinity:\ > :maxproc-cur=64:\ > :openfiles-cur=64:\ > :priority=0:\ > :requirehome@:\ > :umask=022:\ > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Brian O'Shea boshea@ricochet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 11:29:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id 5876737B4C5 for ; Mon, 13 Nov 2000 11:29:44 -0800 (PST) Received: (qmail 62464 invoked by uid 1003); 13 Nov 2000 19:29:40 -0000 Date: Mon, 13 Nov 2000 21:29:40 +0200 From: Neil Blakey-Milner To: Roger Hardiman Cc: Mike Smith , joe@FreeBSD.org, hackers@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/pciconf vendors.h pciconf.8 pciconf.c Message-ID: <20001113212940.A54725@mithrandr.moria.org> References: <200011131217.eADCHvF03753@mass.osd.bsdi.com> <3A0FDD63.18869D9F@cs.strath.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A0FDD63.18869D9F@cs.strath.ac.uk>; from roger@cs.strath.ac.uk on Mon, Nov 13, 2000 at 12:24:03PM +0000 X-Operating-System: FreeBSD 4.1-STABLE i386 X-URL: http://mithrandr.moria.org/nbm/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon 2000-11-13 (12:24), Roger Hardiman wrote: > Mike Smith wrote: > > > > The downside of this is that it bloats pciconf from about 5k to about > > 130k. If someone feels passionately about this, they're welcome to add a > > compile-time option to leave the strings out. > > We will have to add this for PicoBSD where we want the kernel nice and > small. > > > Joe - you listening? pciconf isn't on any picobsd images I've seem. However, we can save a lot of space by reorganizing pci/pcisupport.c in such a way to make it easy to drop text identifiers for the pci devices. I seem to remember posting one way to do it to -arch a while back. It was a sizable win on the images I was playing with. Anyone interested can look at the (now heavily outdated) patch and recreate it. phk suggested there be one massive table, but I used a table per device type. I'm uncertain as to what others think on that. Cheers, Neil -- Neil Blakey-Milner nbm@mithrandr.moria.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 13 11:56:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from krell.webweaver.net (krell.webweaver.net [206.24.105.170]) by hub.freebsd.org (Postfix) with ESMTP id 2994E37B479 for ; Mon, 13 Nov 2000 11:56:38 -0800 (PST) Received: from xwin.nmhtech.com (xwin.nmhtech.com [208.138.46.10]) by krell.webweaver.net (Postfix) with ESMTP id 2A6AA20F12; Mon, 13 Nov 2000 11:42:01 -0800 (PST) Content-Length: 4054 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20001113111837.J622@beastie.localdomain> Date: Mon, 13 Nov 2000 11:56:37 -0700 (PST) From: Nicole H To: "Brian O'Shea" Subject: Re: Log analysis program running under apache reboots server! Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Nov-00 Brian O'Shea wrote: > Nicole, > > Is it a panic, or does it just silently reboot? If it's a panic, > what is the panic message, or any other message on the console when > the system crashes? Also, can you get a crash dump? (see the > dumpon(8) man page) > > -brian > Silent reboot :( Nicole > > On Mon, Nov 13, 2000 at 10:58:39AM -0800, Nicole Harrington wrote: >> Greetings all.. >> >> I have been trying to test an apache log analizing program called >> Nettracker >> (wwww.sane.com) the program seems nice except for the fact that it keeps >> rebooting/crashing the server. This would just be labeled crappy software >> except for the fact that I am running the software as user apache and have >> setup process limits in login.conf and it is still able to reboot the >> server. >> >> This seems like a real problem and security issue as I have setup limits >> in >> /etc/login.conf (see below) and the program is being run via CGI as user >> apache, yet it is still capable of rebooting the system. Seems like a nice >> hack >> to me. >> >> If anyone could check over my login.conf settings below and make sure >> they >> are >> correct/ truly usefull, I would really appreciate it! Also any information >> on >> how this program could so easily reboot the server would be nice too. >> >> Thanks!! >> >> >> Nicole >> >> System is 4.1-STABLE and has 256 Megs of memory and 4X that of swap. >> >> apacheuser:\ >> :manpath=/usr/share/man /usr/X11R6/man /usr/local/man:\ >> :cputime=4h:\ >> :datasize=64M:\ >> :stacksize=4M:\ >> :filesize=infinity:\ >> :memoryuse=64M:\ >> :priority=0:\ >> :datasize-cur=32M:\ >> :stacksize-cur=32M:\ >> :coredumpsize-cur=0:\ >> :maxmemorysize-cur=64M:\ >> :memorylocked=32M:\ >> :maxproc=128:\ >> :openfiles=256:\ >> :tc=standard: >> >> ## standard - standard user defaults >> ## >> standard:\ >> :copyright=/etc/COPYRIGHT:\ >> :welcome=/etc/motd:\ >> :setenv=MAIL=/var/mail/$,BLOCKSIZE=K:\ >> :path=~/bin /bin /usr/bin /usr/local/bin:\ >> :manpath=/usr/share/man /usr/local/man:\ >> :nologin=/var/run/nologin:\ >> :cputime=1h30m:\ >> :datasize=8M:\ >> :stacksize=2M:\ >> :memorylocked=4M:\ >> :memoryuse=8M:\ >> :filesize=8M:\ >> :coredumpsize=8M:\ >> :openfiles=24:\ >> :maxproc=32:\ >> :priority=0:\ >> :requirehome:\ >> :passwordtime=90d:\ >> :umask=002:\ >> :ignoretime@:\ >> :tc=default: >> >> default:\ >> :cputime=infinity:\ >> :datasize-cur=22M:\ >> :stacksize-cur=8M:\ >> :memorylocked-cur=10M:\ >> :memoryuse-cur=30M:\ >> :filesize=infinity:\ >> :coredumpsize=infinity:\ >> :maxproc-cur=64:\ >> :openfiles-cur=64:\ >> :priority=0:\ >> :requirehome@:\ >> :umask=022:\ >> >> >> >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-hackers" in the body of the message > > -- > Brian O'Shea > boshea@ricochet.net > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message nicole@unixgirl.com |\ __ /| (`\ http://www.unixgirl.com/ webmistress@dangermouse.org | o_o |__ ) ) http://www.dangermouse.org/ nicole@deviantimages.com // \\ http://www.deviantimages.com/ ---------------------------(((---(((----------------------------------------- -- Powered by Coka-Cola and FreeBSD -- -- Strong as any man - made for a Woman -- -- "I drank WHAT ?!" - Socrates -- Hmm You seem better - "been giving myself shock treatments" Up the Voltage! ----------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 12: 3:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from krell.webweaver.net (krell.webweaver.net [206.24.105.170]) by hub.freebsd.org (Postfix) with ESMTP id 016ED37B479 for ; Mon, 13 Nov 2000 12:03:50 -0800 (PST) Received: from xwin.nmhtech.com (xwin.nmhtech.com [208.138.46.10]) by krell.webweaver.net (Postfix) with ESMTP id C811920F10; Mon, 13 Nov 2000 11:49:13 -0800 (PST) Content-Length: 5162 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 13 Nov 2000 12:03:49 -0700 (PST) From: Nicole To: Nicole H Subject: Re: Log analysis program running under apache reboots server! Cc: freebsd-hackers@FreeBSD.ORG, "Brian O'Shea" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Nov-00 Nicole H wrote: > > On 13-Nov-00 Brian O'Shea wrote: >> Nicole, >> >> Is it a panic, or does it just silently reboot? If it's a panic, >> what is the panic message, or any other message on the console when >> the system crashes? Also, can you get a crash dump? (see the >> dumpon(8) man page) >> >> -brian >> > > Silent reboot :( I hate to respond to my own message.. But the server is remote.. But there is nothing in the logs afterwards.. and nothing appears on the screen when it occurs. Nicole > > > Nicole > > >> >> On Mon, Nov 13, 2000 at 10:58:39AM -0800, Nicole Harrington wrote: >>> Greetings all.. >>> >>> I have been trying to test an apache log analizing program called >>> Nettracker >>> (wwww.sane.com) the program seems nice except for the fact that it keeps >>> rebooting/crashing the server. This would just be labeled crappy software >>> except for the fact that I am running the software as user apache and have >>> setup process limits in login.conf and it is still able to reboot the >>> server. >>> >>> This seems like a real problem and security issue as I have setup limits >>> in >>> /etc/login.conf (see below) and the program is being run via CGI as user >>> apache, yet it is still capable of rebooting the system. Seems like a nice >>> hack >>> to me. >>> >>> If anyone could check over my login.conf settings below and make sure >>> they >>> are >>> correct/ truly usefull, I would really appreciate it! Also any information >>> on >>> how this program could so easily reboot the server would be nice too. >>> >>> Thanks!! >>> >>> >>> Nicole >>> >>> System is 4.1-STABLE and has 256 Megs of memory and 4X that of swap. >>> >>> apacheuser:\ >>> :manpath=/usr/share/man /usr/X11R6/man /usr/local/man:\ >>> :cputime=4h:\ >>> :datasize=64M:\ >>> :stacksize=4M:\ >>> :filesize=infinity:\ >>> :memoryuse=64M:\ >>> :priority=0:\ >>> :datasize-cur=32M:\ >>> :stacksize-cur=32M:\ >>> :coredumpsize-cur=0:\ >>> :maxmemorysize-cur=64M:\ >>> :memorylocked=32M:\ >>> :maxproc=128:\ >>> :openfiles=256:\ >>> :tc=standard: >>> >>> ## standard - standard user defaults >>> ## >>> standard:\ >>> :copyright=/etc/COPYRIGHT:\ >>> :welcome=/etc/motd:\ >>> :setenv=MAIL=/var/mail/$,BLOCKSIZE=K:\ >>> :path=~/bin /bin /usr/bin /usr/local/bin:\ >>> :manpath=/usr/share/man /usr/local/man:\ >>> :nologin=/var/run/nologin:\ >>> :cputime=1h30m:\ >>> :datasize=8M:\ >>> :stacksize=2M:\ >>> :memorylocked=4M:\ >>> :memoryuse=8M:\ >>> :filesize=8M:\ >>> :coredumpsize=8M:\ >>> :openfiles=24:\ >>> :maxproc=32:\ >>> :priority=0:\ >>> :requirehome:\ >>> :passwordtime=90d:\ >>> :umask=002:\ >>> :ignoretime@:\ >>> :tc=default: >>> >>> default:\ >>> :cputime=infinity:\ >>> :datasize-cur=22M:\ >>> :stacksize-cur=8M:\ >>> :memorylocked-cur=10M:\ >>> :memoryuse-cur=30M:\ >>> :filesize=infinity:\ >>> :coredumpsize=infinity:\ >>> :maxproc-cur=64:\ >>> :openfiles-cur=64:\ >>> :priority=0:\ >>> :requirehome@:\ >>> :umask=022:\ >>> >>> >>> >>> >>> >>> To Unsubscribe: send mail to majordomo@FreeBSD.org >>> with "unsubscribe freebsd-hackers" in the body of the message >> >> -- >> Brian O'Shea >> boshea@ricochet.net >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-hackers" in the body of the message > > nicole@unixgirl.com |\ __ /| (`\ http://www.unixgirl.com/ > webmistress@dangermouse.org | o_o |__ ) ) http://www.dangermouse.org/ > nicole@deviantimages.com // \\ http://www.deviantimages.com/ > > ---------------------------(((---(((----------------------------------------- > > -- Powered by Coka-Cola and FreeBSD -- > -- Strong as any man - made for a Woman -- > -- "I drank WHAT ?!" - Socrates -- > Hmm You seem better - "been giving myself shock treatments" Up the Voltage! > ----------------------------------------------------------------------------- > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message nicole@unixgirl.com |\ __ /| (`\ http://www.unixgirl.com/ webmistress@dangermouse.org | o_o |__ ) ) http://www.dangermouse.org/ nicole@deviantimages.com // \\ http://www.deviantimages.com/ ---------------------------(((---(((----------------------------------------- -- Powered by Coka-Cola and FreeBSD -- -- Strong as any man - made for a Woman -- -- "I drank WHAT ?!" - Socrates -- Hmm You seem better - "been giving myself shock treatments" Up the Voltage! ----------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 14:21: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from field.videotron.net (field.videotron.net [205.151.222.108]) by hub.freebsd.org (Postfix) with ESMTP id E26F837B4C5 for ; Mon, 13 Nov 2000 14:21:02 -0800 (PST) Received: from modemcable213.3-201-24.mtl.mc.videotron.ca ([24.201.3.213]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G3Z00AR1I2W3N@field.videotron.net> for freebsd-hackers@FreeBSD.ORG; Mon, 13 Nov 2000 17:20:56 -0500 (EST) Date: Mon, 13 Nov 2000 17:26:02 -0500 (EST) From: Bosko Milekic Subject: Re: Log analysis program running under apache reboots server! In-reply-to: X-Sender: bmilekic@jehovah.technokratis.com To: Nicole Cc: freebsd-hackers@FreeBSD.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 Likely, you're getting a panic() and since you likely don't have debugging options, the machine eventually reboots itself. Notice that this is all "likely" and that since we don't have a crash dump, stack trace, or similar debugging information, that there's not much that can be done except guessing. I would suggest that you try to reproduce the problem on a local machine and get some debugging info. On Mon, 13 Nov 2000, Nicole wrote: > > Silent reboot :( > > I hate to respond to my own message.. But the server is remote.. But there is > nothing in the logs afterwards.. and nothing appears on the screen when it > occurs. > > Nicole [...] > >>> apacheuser:\ > >>> :manpath=/usr/share/man /usr/X11R6/man /usr/local/man:\ > >>> :cputime=4h:\ > >>> :datasize=64M:\ > >>> :stacksize=4M:\ > >>> :filesize=infinity:\ > >>> :memoryuse=64M:\ > >>> :priority=0:\ > >>> :datasize-cur=32M:\ > >>> :stacksize-cur=32M:\ > >>> :coredumpsize-cur=0:\ > >>> :maxmemorysize-cur=64M:\ > >>> :memorylocked=32M:\ > >>> :maxproc=128:\ > >>> :openfiles=256:\ > >>> :tc=standard: > >>> > >>> ## standard - standard user defaults > >>> ## > >>> standard:\ > >>> :copyright=/etc/COPYRIGHT:\ > >>> :welcome=/etc/motd:\ > >>> :setenv=MAIL=/var/mail/$,BLOCKSIZE=K:\ > >>> :path=~/bin /bin /usr/bin /usr/local/bin:\ > >>> :manpath=/usr/share/man /usr/local/man:\ > >>> :nologin=/var/run/nologin:\ > >>> :cputime=1h30m:\ > >>> :datasize=8M:\ > >>> :stacksize=2M:\ > >>> :memorylocked=4M:\ > >>> :memoryuse=8M:\ > >>> :filesize=8M:\ > >>> :coredumpsize=8M:\ > >>> :openfiles=24:\ > >>> :maxproc=32:\ > >>> :priority=0:\ > >>> :requirehome:\ > >>> :passwordtime=90d:\ > >>> :umask=002:\ > >>> :ignoretime@:\ > >>> :tc=default: > >>> > >>> default:\ > >>> :cputime=infinity:\ > >>> :datasize-cur=22M:\ > >>> :stacksize-cur=8M:\ > >>> :memorylocked-cur=10M:\ > >>> :memoryuse-cur=30M:\ > >>> :filesize=infinity:\ > >>> :coredumpsize=infinity:\ > >>> :maxproc-cur=64:\ > >>> :openfiles-cur=64:\ > >>> :priority=0:\ > >>> :requirehome@:\ > >>> :umask=022:\ For starters, I don't see "sbsize" in there, although it doesn't sound like something that should be causing a panic() anymore anyway. Please provide more debugging infos. Thanks, Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 14:35:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tabby.kudra.com (gw.kudra.com [199.6.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 89CC537B4C5 for ; Mon, 13 Nov 2000 14:35:44 -0800 (PST) Received: (from robert@localhost) by tabby.kudra.com (8.9.3/8.9.3) id RAA95342; Mon, 13 Nov 2000 17:35:36 -0500 (EST) (envelope-from robert) Date: Mon, 13 Nov 2000 17:35:36 -0500 From: Robert Sexton To: Nicole H Cc: freebsd-hackers@freebsd.org Subject: Re: Log analysis program running under apache reboots server! Message-ID: <20001113173536.A93680@tabby.kudra.com> References: <20001113111837.J622@beastie.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Nicole H on Mon, Nov 13, 2000 at 11:56:37AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 13, 2000 at 11:56:37AM -0700, Nicole H wrote: > > On 13-Nov-00 Brian O'Shea wrote: > > Nicole, > > > > Is it a panic, or does it just silently reboot? If it's a panic, > > what is the panic message, or any other message on the console when > > the system crashes? Also, can you get a crash dump? (see the > > dumpon(8) man page) > > > > -brian > > > > Silent reboot :( Be sure the machine is setup to capture a crashdump on panic. I had a machine that was doing this, and wehn I got it to do proper crashdumps, I got a good lead on the problem. in my case, I set aside a raw partition, and setup this in rc.conf: dumpdev="/dev/rda2s1h" # Device name to crashdump to (if enabled). Then I symlinked /var/crash to someplace else, because my /var wasn't too big. Good Luck. -- Robert Sexton - robert@kudra.com, Cincinnati OH, USA The individual choice of garnishment of a burger can be an important point to the consumer in this day when individualism is an increasingly important thing to people. -- Donald N. Smith, president of Burger King To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 16: 6:18 2000 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 ABB8337B479; Mon, 13 Nov 2000 16:06:14 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAE06E415062; Mon, 13 Nov 2000 16:06:14 -0800 (PST) Date: Mon, 13 Nov 2000 16:06:14 -0800 From: Alfred Perlstein To: markm@freebsd.org Cc: hackers@freebsd.org Subject: patches for 4.x devrandom so that bind "works" Message-ID: <20001113160614.R11449@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was playing with bind9 and got the typical: On FreeBSD systems, the server logs error messages like "fcntl(8, F_SETFL, 4): Inappropriate ioctl for device". This is due to a bug in the FreeSBD /dev/random device. The bug has been reported to the FreeBSD maintainers. Versions of OpenBSD prior to 2.8 have a similar problem. I took a look at what OpenBSD did and it looks like they just no-op'd out the ioctl: http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/rnd.c?r1=1.40&r2=1.41 I have a patch that seems to shut bind up, but I'm not 100% sure this is the right fix, as it looks like it just fakes the nonblocking access to the random devices. Here's my patch (I can probably generate this for alpha): Index: mem.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/mem.c,v retrieving revision 1.79.2.4 diff -u -u -r1.79.2.4 mem.c --- mem.c 2000/08/04 22:31:07 1.79.2.4 +++ mem.c 2000/11/13 23:53:43 @@ -57,6 +57,7 @@ #include #include #include +#include #include #include @@ -465,8 +466,20 @@ * selecting and inspecting which interrupts are used in the muck * gathering business. */ - if (cmd != MEM_SETIRQ && cmd != MEM_CLEARIRQ && cmd != MEM_RETURNIRQ) + switch (cmd) { + case FIOASYNC: + /* rnd has no async flag in softc so this is really a no-op. */ + /* FALLTHROUGH */ + case FIONBIO: + /* Handled in the upper FS layer. */ + return (0); + case MEM_SETIRQ: + case MEM_CLEARIRQ: + case MEM_RETURNIRQ: + break; + default: return (ENOTTY); + } /* * Even inspecting the state is privileged, since it gives a hint Did I miss part of the OpenBSD delta? This looks too easy. :( -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 16:26:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 6E11A37B479 for ; Mon, 13 Nov 2000 16:26:09 -0800 (PST) Received: from bellatlantic.net (client-151-198-117-35.nnj.dialup.bellatlantic.net [151.198.117.35]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id TAA06924; Mon, 13 Nov 2000 19:26:00 -0500 (EST) Message-ID: <3A108697.1BF0AF92@bellatlantic.net> Date: Mon, 13 Nov 2000 19:25:59 -0500 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: en, ru MIME-Version: 1.0 To: Robert Lipe Cc: "Kenneth D. Merry" , freebsd-hackers@FreeBSD.ORG Subject: Re: pci bus enumeration & cdevsw indexing References: <20001113004410.W20018@rjlhome.sco.com> <20001112235932.A63657@panzer.kdm.org> <20001113085137.X20018@rjlhome.sco.com> <20001113102641.B66956@panzer.kdm.org> <20001113114815.D29431@rjlhome.sco.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Lipe wrote: > > Kenneth D. Merry wrote: > > I do know that we have the concept of probe priorities, so you could > > probably set up UDI to probe at a higher priority than the default system > > drivers, and therefore attach instead of the default FreeBSD driver for a > > given piece of harware. > > That's clever. As far as I understand, that's not too easy: most drivers' probes return the highest priority, so you won't be able to override them. But doing the other way is easy: just return a lower priority and the UDI driver will be used only if there is no native driver. Actually, if there are multiple drivers returning the same priority then one will be selected at random (the one appearing earlier in the table) and there still will be no conflict. May be my article http://www.daemonnews.org/200008/isa.html would be of some help, it considers the ISA bus but by the way touches the general issues of the new bus architecture too. -SB (also sergey@sco.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 17:39:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hand.dotat.at (sfo-gw.covalent.net [207.44.198.62]) by hub.freebsd.org (Postfix) with ESMTP id CB6F037B4C5 for ; Mon, 13 Nov 2000 17:39:51 -0800 (PST) Received: from fanf by hand.dotat.at with local (Exim 3.15 #3) id 13vV49-0004hX-00; Tue, 14 Nov 2000 01:39:17 +0000 Date: Tue, 14 Nov 2000 01:39:17 +0000 From: Tony Finch To: Alfred Perlstein Cc: hackers@freebsd.org Subject: Re: pointer for thread safe resolver stuff? Message-ID: <20001114013917.F25050@hand.dotat.at> References: <20001113003402.F11449@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20001113003402.F11449@fw.wintelcom.net> Organization: Covalent Technologies, Inc Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > >I'm going to keep reading the library source (and cursing the ISC) >but I was wondering if anyone knew of any docs for the bind9 stuff >or any other thread safe (non-GPL'd) resolver library. AFAIK the bind-9 resolver is a full resolver not a stub resolver, which probably isn't what you want. I haven't checked this hearsay for myself though. Tony. -- en oeccget g mtcaa f.a.n.finch v spdlkishrhtewe y dot@dotat.at eatp o v eiti i d. fanf@covalent.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 17:49:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from portnoy.lbl.gov (portnoy.lbl.gov [131.243.2.11]) by hub.freebsd.org (Postfix) with ESMTP id 67B1137B479 for ; Mon, 13 Nov 2000 17:49:27 -0800 (PST) Received: (from jin@localhost) by portnoy.lbl.gov (8.11.1/8.11.1) id eAE1nRI14099 for hackers@freebsd.org; Mon, 13 Nov 2000 17:49:27 -0800 (PST) Date: Mon, 13 Nov 2000 17:49:27 -0800 (PST) From: Jin Guojun (DSD staff) Message-Id: <200011140149.eAE1nRI14099@portnoy.lbl.gov> To: hackers@freebsd.org Subject: zero copy TCP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I heard that zero copy TCP is already in FreeBSD, isn't it? I could not find any information in searching the entire website. Before I am going to spend some silly time working on it, I would like to know what is the status for "ZERO COPY TCP" in FreeBSD right now. If it already exists, how can I enable it (for 1500 MTU, not Jumbo Frame)? or someone is still working on it. -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 17:59:20 2000 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 0E5B737B4C5 for ; Mon, 13 Nov 2000 17:59:19 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAE1xIv18932; Mon, 13 Nov 2000 17:59:18 -0800 (PST) Date: Mon, 13 Nov 2000 17:59:17 -0800 From: Alfred Perlstein To: Jin Guojun Cc: hackers@FreeBSD.ORG Subject: Re: zero copy TCP Message-ID: <20001113175917.W11449@fw.wintelcom.net> References: <200011140149.eAE1nRI14099@portnoy.lbl.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200011140149.eAE1nRI14099@portnoy.lbl.gov>; from jin@george.lbl.gov on Mon, Nov 13, 2000 at 05:49:27PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jin Guojun [001113 17:49] wrote: > I heard that zero copy TCP is already in FreeBSD, isn't it? > I could not find any information in searching the entire website. > Before I am going to spend some silly time working on it, > I would like to know what is the status for "ZERO COPY TCP" in > FreeBSD right now. > If it already exists, how can I enable it (for 1500 MTU, not Jumbo Frame)? > or someone is still working on it. It's not integrated into the source tree yet. What sort of zero copy do you hope to accomplish? Sending files? Sending preloaded data? -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 18: 6:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from femail4.sdc1.sfba.home.com (femail4.sdc1.sfba.home.com [24.0.95.84]) by hub.freebsd.org (Postfix) with ESMTP id E49BE37B479 for ; Mon, 13 Nov 2000 18:06:39 -0800 (PST) Received: from beastie.localdomain ([24.19.158.41]) by femail4.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20001114020512.SAWP26316.femail4.sdc1.sfba.home.com@beastie.localdomain>; Mon, 13 Nov 2000 18:05:12 -0800 Received: (from brian@localhost) by beastie.localdomain (8.9.3/8.8.7) id SAA14381; Mon, 13 Nov 2000 18:09:42 -0800 (PST) (envelope-from brian) Date: Mon, 13 Nov 2000 18:09:42 -0800 From: "Brian O'Shea" To: Nicole H Cc: "Brian O'Shea" , freebsd-hackers@FreeBSD.ORG Subject: Re: Log analysis program running under apache reboots server! Message-ID: <20001113180942.L622@beastie.localdomain> Reply-To: boshea@ricochet.net Mail-Followup-To: Nicole H , Brian O'Shea , freebsd-hackers@FreeBSD.ORG References: <20001113111837.J622@beastie.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Nicole H on Mon, Nov 13, 2000 at 11:56:37AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 13, 2000 at 11:56:37AM -0700, Nicole H wrote: > > On 13-Nov-00 Brian O'Shea wrote: > > Nicole, > > > > Is it a panic, or does it just silently reboot? If it's a panic, > > what is the panic message, or any other message on the console when > > the system crashes? Also, can you get a crash dump? (see the > > dumpon(8) man page) > > > > -brian > > > > Silent reboot :( > Are you logged in on a network terminal via ssh or telnet or the like, or on a serial console via a terminal server? The panic message will only appear on the console, so unless it's the latter, it will be hard to determine the cause of the problem. There are good instructions on how to get debugging information for kernel crashes here: http://www.freebsd.org/handbook/kerneldebug.html -brian -- Brian O'Shea boshea@ricochet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 18:26:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from portnoy.lbl.gov (portnoy.lbl.gov [131.243.2.11]) by hub.freebsd.org (Postfix) with ESMTP id 26FA337B4C5 for ; Mon, 13 Nov 2000 18:26:45 -0800 (PST) Received: (from jin@localhost) by portnoy.lbl.gov (8.11.1/8.11.1) id eAE2QiK14602; Mon, 13 Nov 2000 18:26:44 -0800 (PST) Date: Mon, 13 Nov 2000 18:26:44 -0800 (PST) From: Jin Guojun (DSD staff) Message-Id: <200011140226.eAE2QiK14602@portnoy.lbl.gov> To: bright@wintelcom.net Subject: Re: zero copy TCP Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred wrote: > > I heard that zero copy TCP is already in FreeBSD, isn't it? > > I could not find any information in searching the entire website. > > Before I am going to spend some silly time working on it, > > I would like to know what is the status for "ZERO COPY TCP" in > > FreeBSD right now. > > If it already exists, how can I enable it (for 1500 MTU, not Jumbo Frame)? > > or someone is still working on it. > > It's not integrated into the source tree yet. What sort of zero > copy do you hope to accomplish? Sending files? Sending preloaded > data? Both, but I may do either way, depending on which way is easier. If we can directly DMA from a disk drive to a NIC, that will be great. If the current implementation requires preloaded buffer, that works. So, where can I look for the patch? Thanks, -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 19:25:38 2000 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 E3E0737B479 for ; Mon, 13 Nov 2000 19:25:36 -0800 (PST) Received: from modemcable213.3-201-24.mtl.mc.videotron.ca ([24.201.3.213]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G3Z00DKXW6L8H@falla.videotron.net> for hackers@FreeBSD.ORG; Mon, 13 Nov 2000 22:25:34 -0500 (EST) Date: Mon, 13 Nov 2000 21:30:22 -0500 (EST) From: Bosko Milekic Subject: Re: zero copy TCP In-reply-to: <200011140226.eAE2QiK14602@portnoy.lbl.gov> X-Sender: bmilekic@jehovah.technokratis.com To: Jin Guojun Cc: hackers@FreeBSD.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 Mon, 13 Nov 2000, Jin Guojun wrote: > Both, but I may do either way, depending on which way is easier. > If we can directly DMA from a disk drive to a NIC, that will be great. > If the current implementation requires preloaded buffer, that works. > So, where can I look for the patch? > > Thanks, > > -Jin Please see sendfile(2). Regards, Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 22:17:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 388BE37B479 for ; Mon, 13 Nov 2000 22:17:17 -0800 (PST) Received: from grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.1/8.11.1) with ESMTP id eAE6Gvw04883; Tue, 14 Nov 2000 08:16:58 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200011140616.eAE6Gvw04883@grimreaper.grondar.za> To: Alfred Perlstein Cc: hackers@freebsd.org Subject: Re: patches for 4.x devrandom so that bind "works" References: <20001113160614.R11449@fw.wintelcom.net> In-Reply-To: <20001113160614.R11449@fw.wintelcom.net> ; from Alfred Perlstein "Mon, 13 Nov 2000 16:06:14 PST." Date: Tue, 14 Nov 2000 08:16:57 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I have something similar to this, and it goes slightly further. Yes, it is this simple :-). M > I was playing with bind9 and got the typical: > > On FreeBSD systems, the server logs error messages like "fcntl(8, > F_SETFL, 4): Inappropriate ioctl for device". This is due to > a bug in the FreeSBD /dev/random device. The bug has been > reported to the FreeBSD maintainers. Versions of OpenBSD prior > to 2.8 have a similar problem. > > I took a look at what OpenBSD did and it looks like they just > no-op'd out the ioctl: > > http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/rnd.c?r1=1.40&r2=1.41 > > I have a patch that seems to shut bind up, but I'm not 100% sure > this is the right fix, as it looks like it just fakes the nonblocking > access to the random devices. > > Here's my patch (I can probably generate this for alpha): > > Index: mem.c > =================================================================== > RCS file: /home/ncvs/src/sys/i386/i386/mem.c,v > retrieving revision 1.79.2.4 > diff -u -u -r1.79.2.4 mem.c > --- mem.c 2000/08/04 22:31:07 1.79.2.4 > +++ mem.c 2000/11/13 23:53:43 > @@ -57,6 +57,7 @@ > #include > #include > #include > +#include > #include > > #include > @@ -465,8 +466,20 @@ > * selecting and inspecting which interrupts are used in the muck > * gathering business. > */ > - if (cmd != MEM_SETIRQ && cmd != MEM_CLEARIRQ && cmd != MEM_RETURNIRQ) > + switch (cmd) { > + case FIOASYNC: > + /* rnd has no async flag in softc so this is really a no-op. */ > + /* FALLTHROUGH */ > + case FIONBIO: > + /* Handled in the upper FS layer. */ > + return (0); > + case MEM_SETIRQ: > + case MEM_CLEARIRQ: > + case MEM_RETURNIRQ: > + break; > + default: > return (ENOTTY); > + } > > /* > * Even inspecting the state is privileged, since it gives a hint > > Did I miss part of the OpenBSD delta? This looks too easy. :( > > -- > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > "I have the heart of a child; I keep it in a jar on my desk." > -- Mark Murray Join the anti-SPAM movement: http://www.cauce.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 13 22:36: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ebola.biohz.net (ebola.biohz.net [206.80.1.35]) by hub.freebsd.org (Postfix) with ESMTP id 2440637B4C5 for ; Mon, 13 Nov 2000 22:36:00 -0800 (PST) Received: from flu (localhost [127.0.0.1]) by ebola.biohz.net (Postfix) with SMTP id 6D1C43A3CB; Mon, 13 Nov 2000 22:35:59 -0800 (PST) Message-ID: <000001c04e05$269b7860$0402010a@biohz.net> From: "Renaud Waldura" To: "FengYue" , References: Subject: Re: PPPoE w/ nat auto fragmentation hack? Date: Mon, 13 Nov 2000 19:35:57 -0800 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.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote an article about this setup. Should be published soon enough. http://renaud.waldura.com/doc/freebsd-pppoe/ I'd like to get your feedback on the section making use of tcpmssd: it doesn't seem to work when the link is brought up automatically by ppp. --Renaud ----- Original Message ----- From: FengYue To: Sent: Sunday, November 12, 2000 1:40 PM Subject: PPPoE w/ nat auto fragmentation hack? > > Hi, Any of you happened to hack the PPPoE support on Fbsd 4.x to > automatically fragment the IP datagram if whatever device behind the > NAT refuses to adjust its MTU? > > Thanks > > > > 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 13 22:36:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (c228380-a.sfmissn1.sfba.home.com [24.20.90.44]) by hub.freebsd.org (Postfix) with ESMTP id D3E9437B479 for ; Mon, 13 Nov 2000 22:36:52 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAE6h8F00774; Mon, 13 Nov 2000 22:43:08 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011140643.eAE6h8F00774@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Robert Lipe Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: pci bus enumeration & cdevsw indexing In-reply-to: Your message of "Mon, 13 Nov 2000 08:51:37 CST." <20001113085137.X20018@rjlhome.sco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Nov 2000 22:43:08 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What does your driver do? > > It's not a driver as much as driver infrastructure. To measure the > difficulty of porting the UDI Reference Implementation (available source > soon!) I decided to try porting it to an OS that I knew little about. Aha! I've been waiting for this since February or so, which was the last time anyone mentioned that the UDI reference implementation was going to go public. 8) > UDI has a concept somewhat like that expressed in the core BSD bus > enumeration code where you have a bus/bridge driver that enumerates > children (additional busses or cards) which may each enumerate > additional children. It looks like the normal BSD interfaces to the PCI > bus assumes that I am one of those children. This is understandable and > has parallels in UDI-land. Unfortunately for UDI implementation, the only real way to do this "right" is going to be by merging the two infrastructures, ie. making it possible for UDI drivers to attach to newbus busses (and vice-versa, although that is probably asking a bit much). > What I really want is to be able to walk the installed/supported busses > for a chance to bind them to UDI drivers. So I don't really want to > replace the existing tree-builder, I'd like to make something somewhat > parallel to it. Don't. Shim the UDI drivers so that they look like "normal" newbus devices. Trying to have two sets of infrastructure "owning" the same bus/ resource domain is just going to be ugly. Alternatively, if you really want to use the UDI bus infrastructure, you'll have to merge the two fairly intimately. A third approach would be to discard the newbus code and work out how to shim existing FreeBSD drivers to live under the UDI infrastructure. Given the way that newbus works, this might not be all that easy (eg. there are cases where drivers make valid assumptions about the tree above them which would be invalidated by this). > Alternately, if there's a standard interface to a system configuration > database that stores this tree, I could walk that table and hand that > information to my bridge driver. UnixWare (resmgr), HP/UX (cdio) , and > AIX (can't recall the name of it) have such interfaces. One thing you could do, if you only care (for now) about unattached PCI devices, is to look at the way that PCI nomatch is handled, and pass these devices off to the UDI probe/attach handler. Resources for these devices can be managed using the normal bus_*_resource interface. > > If you do need to get at the data, the easiest thing to do would be to > > code. If this is a driver you're going to want to ship in source or module > > form, > > It is. I'd like the reference implementation to ship in source form. > It currently make extensive use of modules. That's not an unreasonable thing to do. Note that every time you load a device module the system performs a complete bus rescan, so the nomatch handler is called for every device that hasn't already been claimed. If you want to discuss this in more detail, please do. Note also that depending on your NDA circumstances I may already be in a situation where it would be easy for you to discuss some of this material offline. I'm pretty familiar with the way that newbus and the BSD PCI code works, just not with the innards of the UDI reference implementation. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 22:40: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (c228380-a.sfmissn1.sfba.home.com [24.20.90.44]) by hub.freebsd.org (Postfix) with ESMTP id 81DFA37B479 for ; Mon, 13 Nov 2000 22:40:03 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAE6kJF00794; Mon, 13 Nov 2000 22:46:20 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011140646.eAE6kJF00794@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Robert Lipe Cc: freebsd-hackers@freebsd.org Subject: Re: pci bus enumeration & cdevsw indexing In-reply-to: Your message of "Mon, 13 Nov 2000 09:02:17 CST." <20001113090217.Y20018@rjlhome.sco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Nov 2000 22:46:19 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > to avoid the hard-coded major numbers in the cdevsw[] entry that's > > > passed? It seems like make_dev() should be able to roam cdevsw, find > > > > This is what devfs is meant to achieve. Unfortunately at the moment the > > major numbers need to be fixed because there's no dynamism in /dev. If > > If you have devfs (and it means the same to you that it does to other > OSes) that would solve the problem nicely. So is devfs something in > 4.1.1 or is it future work? If it's here now, can you point me to an > example? If it's future work, is that where I should be focusing? It's a work-in-progress for 5.0 (on the -current branch), and yes, you should most definitely be focussing there. > For a UDI driver, that would be a problem. A UDI driver-writer has > no clue where his target device will be running and, indeed, could be > running on an OS without a /dev. So we could carve out a pool of b > and c major numbers for UDI to then dynamically manage on behalf of > the drivers, but that seems tedious. The environment has enough bread > crumbs to know of a given driver is an HBA, a NIC, or something else and > can set things up appropriately behind the scenes. Realistically, the only things that still care about device major/minor numbers are tty devices, control interfaces and non-SCSI non-ATA block devices. Having said that, DEVFS is really the only sane answer here, and it would probably be a prerequisite for anything like UDI. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 22:49: 3 2000 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 4992137B479 for ; Mon, 13 Nov 2000 22:49:00 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAE6mns26634; Mon, 13 Nov 2000 22:48:49 -0800 (PST) Date: Mon, 13 Nov 2000 22:48:49 -0800 From: Alfred Perlstein To: Mark Murray Cc: hackers@freebsd.org Subject: Re: patches for 4.x devrandom so that bind "works" Message-ID: <20001113224849.Z11449@fw.wintelcom.net> References: <20001113160614.R11449@fw.wintelcom.net> <200011140616.eAE6Gvw04883@grimreaper.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200011140616.eAE6Gvw04883@grimreaper.grondar.za>; from mark@grondar.za on Tue, Nov 14, 2000 at 08:16:57AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Mark Murray [001113 22:17] wrote: > > I was playing with bind9 and got the typical: > > > > On FreeBSD systems, the server logs error messages like "fcntl(8, > > F_SETFL, 4): Inappropriate ioctl for device". This is due to > > a bug in the FreeSBD /dev/random device. The bug has been > > reported to the FreeBSD maintainers. Versions of OpenBSD prior > > to 2.8 have a similar problem. > > > > I took a look at what OpenBSD did and it looks like they just > > no-op'd out the ioctl: > > > > http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/rnd.c?r1=1.40&r2=1.41 > > > > I have a patch that seems to shut bind up, but I'm not 100% sure > > this is the right fix, as it looks like it just fakes the nonblocking > > access to the random devices. > > > > Here's my patch (I can probably generate this for alpha): > > > > Index: mem.c [snip] > > > > Did I miss part of the OpenBSD delta? This looks too easy. :( > > Hi > > I have something similar to this, and it goes slightly further. > > Yes, it is this simple :-). Can you get it ready for 4.2? I'd like to see us be able to run bind9 in the next release. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 13 23:50: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.unixbox.com (shell.unixbox.com [207.211.45.65]) by hub.freebsd.org (Postfix) with ESMTP id 7316E37B4C5 for ; Mon, 13 Nov 2000 23:50:00 -0800 (PST) Received: from localhost (fengyue@localhost) by shell.unixbox.com (8.11.0/8.11.0) with ESMTP id eAE7oTY55816; Mon, 13 Nov 2000 23:50:29 -0800 (PST) Date: Mon, 13 Nov 2000 23:50:29 -0800 (PST) From: FengYue X-Sender: fengyue@shell.unixbox.com To: Renaud Waldura Cc: hackers@FreeBSD.ORG Subject: Re: PPPoE w/ nat auto fragmentation hack? In-Reply-To: <000001c04e05$269b7860$0402010a@biohz.net> 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, 13 Nov 2000, Renaud Waldura wrote: ->I wrote an article about this setup. Should be published soon enough. ->http://renaud.waldura.com/doc/freebsd-pppoe/ -> ->I'd like to get your feedback on the section making use of tcpmssd: it ->doesn't seem to work when the link is brought up automatically by ppp. -> ->--Renaud -> Thanks Renaud, great article and very helpful. I've not got a chance to test out the PPPoE with tcpmssd yet as the machine is not local to me. (I could ssh to it but have no access to the machines behind the nat to generate some testing packets) The only thing is that tcpmssd from FreeBSD port does not have -l option. The -l option, however, is being used in your tcpmssd.rc script. My port tree is quiet new so I guess there is some difference between the tcpmssd you offered on your site and the freebsd port. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 0:41:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id B2FB537B479 for ; Tue, 14 Nov 2000 00:41:30 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.0/8.11.0) id eAE8ec584504; Tue, 14 Nov 2000 10:40:38 +0200 (EET) (envelope-from ru) Date: Tue, 14 Nov 2000 10:40:38 +0200 From: Ruslan Ermilov To: Renaud Waldura Cc: FengYue , hackers@FreeBSD.ORG Subject: Re: PPPoE w/ nat auto fragmentation hack? Message-ID: <20001114104038.C81845@sunbay.com> Mail-Followup-To: Renaud Waldura , FengYue , hackers@FreeBSD.ORG References: <000001c04e05$269b7860$0402010a@biohz.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <000001c04e05$269b7860$0402010a@biohz.net>; from renaud@waldura.com on Mon, Nov 13, 2000 at 07:35:57PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 13, 2000 at 07:35:57PM -0800, Renaud Waldura wrote: > I wrote an article about this setup. Should be published soon enough. > http://renaud.waldura.com/doc/freebsd-pppoe/ > > I'd like to get your feedback on the section making use of tcpmssd: it > doesn't seem to work when the link is brought up automatically by ppp. > What exactly does not work? What does the option -l do? The tcpmssd is now part of the Ports Collection: http://www.freebsd.org/cgi/url.cgi?ports/net/tcpmssd/pkg-descr -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 5: 8: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 5146337B479 for ; Tue, 14 Nov 2000 05:08:01 -0800 (PST) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JWJ767YRRI000XRT@research.kpn.com> for hackers@FreeBSD.ORG; Tue, 14 Nov 2000 14:07:58 +0100 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Tue, 14 Nov 2000 14:07:58 +0100 Content-return: allowed Date: Tue, 14 Nov 2000 14:07:52 +0100 From: "Koster, K.J." Subject: RE: Legacy ethernet cards in FreeBSD To: hackers@FreeBSD.ORG Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D79E9@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Ok, "seem to have lost support" is about the vaguest thing you could > have said. I've killed people for less. > I'm too young to die. Sorry for the lack of detail. I should have known better. > > Please explain in detail how > you arrived at the conclusion that the card was no longer supported. > Show us the dmesg output from your machine. Explain what you tried to > do and what results you observed. Don't just say "it doesn't work." > You've not going to help anyone that way. > 4.0 detects my card, prints the ethernet address during the probe, and actually transmits data when asked to do so. DHCP configures the card, etc. 4.2 detects the card, but does *not* find its ethernet address and the DHCP probe simply never returns, although the machine responds to keypresses to break the installation. > > Did you check to see if a pcn0 device was detected? Did you attempt > to use it? > No. > > If not, why not? > I did not know it was there. > > > SMC EtherEZ ISA > > Should also work with the ed driver, though you may have to turn off > plug and play mode using the SMC EZSetup utility. > I will try this. > > > RealTek "TP-Link" PCI > > If this is a 10mbps card, it should be an NE2000 clone, and will work > with the ed driver. If it's a 100Mbps card, it should work with the > rl driver. > Like I said: it probes, works for a bit, then drops the line and needs a power-cycle. I have two, one of them is available for an individual who wants to hack at it, the other one will serve as a cupholder after I've stomped on it for a bit, otherwise the cups keep falling over. > > > I'll be happy to try out patches for the lnc driver to fix > the problem of > > the Deskpro, or to give remote access to it if you want to > work on it. > > I'd be happier if you told me whether the pcn driver works or not. > Will try. Please hold ... Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 5:37:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 601A537B479 for ; Tue, 14 Nov 2000 05:37:42 -0800 (PST) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id A13CB49; Tue, 14 Nov 2000 09:37:35 -0400 (AST) Message-ID: <3A11401F.85B7F51E@vangelderen.org> Date: Tue, 14 Nov 2000 09:37:35 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Jin Guojun (DSD staff)" Cc: hackers@FreeBSD.ORG Subject: Re: zero copy TCP References: <200011140149.eAE1nRI14099@portnoy.lbl.gov> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jin Guojun (DSD staff)" wrote: > > I heard that zero copy TCP is already in FreeBSD, isn't it? > I could not find any information in searching the entire website. > Before I am going to spend some silly time working on it, > I would like to know what is the status for "ZERO COPY TCP" in > FreeBSD right now. > If it already exists, how can I enable it (for 1500 MTU, not Jumbo Frame)? > or someone is still working on it. http://people.freebsd.org/~ken/ http://people.freebsd.org/~ken/zero_copy/ -Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 7:39:40 2000 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 E592137B479 for ; Tue, 14 Nov 2000 07:39:37 -0800 (PST) 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 HAA12104 for ; Tue, 14 Nov 2000 07:39:37 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 14 Nov 2000 07:39:36 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: hackers@freebsd.org Subject: New US CVSup mirror Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been getting some reports lately that our US CVSup mirror sites are increasingly hard to get into. I've just added a new one, cvsup10.FreeBSD.org, which should help matters. There are a couple of additional mirrors in the pipeline, too. This has become possible because we replaced the master server with a more powerful machine that can handle more mirror sites. (Thanks, Yahoo!) If you ever get shut out of a mirror site, check the current listing in the FreeBSD Handbook, at http://www.freebsd.org/handbook/cvsup.html#CVSUP-MIRRORS You might well find that there are new mirror sites you weren't aware of before. John Polstra FreeBSD CVSup Mirror Coordinator To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 8:11:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.tor3.targetnet.com (smtp.tor3.targetnet.com [207.176.132.71]) by hub.freebsd.org (Postfix) with ESMTP id 3D0BB37B4CF; Tue, 14 Nov 2000 08:11:18 -0800 (PST) Received: from james by smtp.tor3.targetnet.com with local (Exim 3.16 #1) id 13vifC-000Div-00; Tue, 14 Nov 2000 11:10:26 -0500 Date: Tue, 14 Nov 2000 11:10:26 -0500 From: James FitzGibbon To: Chris Dillon Cc: Nick Hibma , hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: USB-to-SCSI converter Message-ID: <20001114111026.B51582@targetnet.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from cdillon@wolves.k12.mo.us on Mon, Nov 13, 2000 at 07:22:04AM -0600 Organization: Targetnet.com Inc. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Chris Dillon (cdillon@wolves.k12.mo.us) [001113 08:22]: > Since you can select the LUN and not the ID, maybe they've mapped SCSI > ID0:LUN0 to ID0:LUN0 (duh), ID1:LUN0 to ID0:LUN1, ID2:LUN0 to > ID0:LUN2, and so on, which would explain why we only see a device at > ID0:LUN0 if we aren't looking at the remaining LUNs (are we?). This > would mean that you can't use multi-LUN devices with the USB-SCSI > converter, but that is much more acceptable than only being able to > use ID0 with it. I think this is what they do, as my test with a multi-LUN CD changer which works find as a SCSI device only shows up as one CD-ROM under both Windows and BSD. Time to hit up Microtech support to see if they'll at least admit that this is what their driver does. The question then is if we are to implement this kind of ID-to-LUN mapping in the umass driver, what do we predicate that behaviour on ? -- j. James FitzGibbon james@targetnet.com Targetnet.com Inc. Voice/Fax +1 416 306-0466/0452 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 8:31:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from portnoy.lbl.gov (portnoy.lbl.gov [131.243.2.11]) by hub.freebsd.org (Postfix) with ESMTP id 31D5E37B4C5 for ; Tue, 14 Nov 2000 08:31:46 -0800 (PST) Received: (from jin@localhost) by portnoy.lbl.gov (8.11.1/8.11.1) id eAEGVhx28040; Tue, 14 Nov 2000 08:31:43 -0800 (PST) Date: Tue, 14 Nov 2000 08:31:43 -0800 (PST) From: Jin Guojun (DSD staff) Message-Id: <200011141631.eAEGVhx28040@portnoy.lbl.gov> To: bmilekic@dsuper.net Subject: Re: zero copy TCP (Thanks) Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for all people who have responded to this thread. -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 9: 8:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ebola.biohz.net (ebola.biohz.net [206.80.1.35]) by hub.freebsd.org (Postfix) with ESMTP id BD6E537B479; Tue, 14 Nov 2000 09:08:21 -0800 (PST) Received: from flu (localhost [127.0.0.1]) by ebola.biohz.net (Postfix) with SMTP id EFF7C3A3CB; Tue, 14 Nov 2000 09:08:20 -0800 (PST) Message-ID: <003701c04e5d$7d902e60$0402010a@biohz.net> From: "Renaud Waldura" To: "Ruslan Ermilov" Cc: "FengYue" , References: <000001c04e05$269b7860$0402010a@biohz.net> <20001114104038.C81845@sunbay.com> Subject: Re: PPPoE w/ nat auto fragmentation hack? (use tcpmssd port) Date: Tue, 14 Nov 2000 09:08:20 -0800 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.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear hackers, > What exactly does not work? > What does the option -l do? When launched automatically by ppp, tcpmssd doesn't get any of the packets and is useless. When I start it manually from the command line, it works fine. I realize this isn't much in the way of helpful debugging information, and was hoping to further define this: I implemented that "-l" option to log all the packets processed by tcpmssd. I'm not even sure this bug applies to anybody else, which is why I did not seek help or publicize it until now. Anyway, I haven't been able to figure out what the problem is (and am lacking time now). The best I have is this: when launched by ppp, tcpmssd never seems to return from the main select() call. Ruslan, if you feel like an account on the machine where I'm using this could help, just let me know and I will gladly give you one. ----- Original Message ----- From: Ruslan Ermilov To: Renaud Waldura Cc: FengYue ; Sent: Tuesday, November 14, 2000 12:40 AM Subject: Re: PPPoE w/ nat auto fragmentation hack? > On Mon, Nov 13, 2000 at 07:35:57PM -0800, Renaud Waldura wrote: > > I wrote an article about this setup. Should be published soon enough. > > http://renaud.waldura.com/doc/freebsd-pppoe/ > > > > I'd like to get your feedback on the section making use of tcpmssd: it > > doesn't seem to work when the link is brought up automatically by ppp. > > > What exactly does not work? > What does the option -l do? > > The tcpmssd is now part of the Ports Collection: > http://www.freebsd.org/cgi/url.cgi?ports/net/tcpmssd/pkg-descr > > > -- > Ruslan Ermilov Oracle Developer/DBA, > ru@sunbay.com Sunbay Software AG, > ru@FreeBSD.org FreeBSD committer, > +380.652.512.251 Simferopol, Ukraine > > http://www.FreeBSD.org The Power To Serve > http://www.oracle.com Enabling The Information Age > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 9:21:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lh04.opsion.fr (lh04.opsion.fr [212.73.208.230]) by hub.freebsd.org (Postfix) with SMTP id 8197E37B4CF for ; Tue, 14 Nov 2000 09:21:37 -0800 (PST) Received: from 198.168.78.67 [198.168.78.67] by lh04.opsion.fr; Tue, 14 Nov 2000 17:23:16 GMT From: Thierry Reply-To: tjmsdn@ifrance.com To: freebsd-hackers@freebsd.org Subject: C and C++ on FreeBSD Date: Tue, 14 Nov 2000 12:21:31 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00111412240100.00321@tjonas_dev.eicon.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, We are implementing our OS modem on FreeBSD, but lot of our sources have writen in C++. Is it possible to compile the FreeBSD kernel in C++ to include our driver ? Thanks in Advance. Thierry ( tjmsdn@ifrance.com ) ______________________________________________________________________________ Vous avez un site perso ? 2 millions de francs à gagner sur i(france) ! Webmasters : ZE CONCOURS ! http://www.ifrance.com/_reloc/concours.emailif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 9:41:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 44BE237B4E5 for ; Tue, 14 Nov 2000 09:41:15 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAEHfDR12501; Tue, 14 Nov 2000 10:41:14 -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 KAA48265; Tue, 14 Nov 2000 10:41:13 -0700 (MST) Message-Id: <200011141741.KAA48265@harmony.village.org> To: tjmsdn@ifrance.com Subject: Re: C and C++ on FreeBSD Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 14 Nov 2000 12:21:31 EST." <00111412240100.00321@tjonas_dev.eicon.com> References: <00111412240100.00321@tjonas_dev.eicon.com> Date: Tue, 14 Nov 2000 10:41:13 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <00111412240100.00321@tjonas_dev.eicon.com> Thierry writes: : We are implementing our OS modem on FreeBSD, but lot of our sources : have writen in C++. Is it possible to compile the FreeBSD kernel in : C++ to include our driver ? Yes and No. If you use only the bare minimal subset of features for the C++ and avoid the problem areas of the language, you might be able to. But you'd have to add new and delete support to the kernel's library. That should be almost trivial. The problem areas definitely include exceptions, some automatic memory allocation (where temporary variables are malloced), large objects appearing on the stack (because the kernel stack is so small). I don't know if ctors for static objects would be called in the kernel. Templates might also be a problem, but they might not. Years ago I was able to do some very simple C++ in the kernel, but never integrated the support. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 9:57:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hda.hda.com (host65.hda.com [63.104.68.65]) by hub.freebsd.org (Postfix) with ESMTP id 8ED0137B4FE for ; Tue, 14 Nov 2000 09:57:51 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.9.3/8.9.3) id NAA99016; Tue, 14 Nov 2000 13:02:57 -0500 (EST) (envelope-from dufault) From: Peter Dufault Message-Id: <200011141802.NAA99016@hda.hda.com> Subject: Re: C and C++ on FreeBSD In-Reply-To: <200011141741.KAA48265@harmony.village.org> from Warner Losh at "Nov 14, 2000 10:41:13 am" To: freebsd-hackers@FreeBSD.ORG Date: Tue, 14 Nov 2000 13:02:57 -0500 (EST) Cc: tjmsdn@ifrance.com X-Mailer: ELM [version 2.4ME+ PL61 (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 > In message <00111412240100.00321@tjonas_dev.eicon.com> Thierry writes: > : We are implementing our OS modem on FreeBSD, but lot of our sources > : have writen in C++. Is it possible to compile the FreeBSD kernel in > : C++ to include our driver ? > > Yes and No. > > If you use only the bare minimal subset of features for the C++ and > avoid the problem areas of the language, you might be able to. But > you'd have to add new and delete support to the kernel's library. > That should be almost trivial. > > The problem areas definitely include exceptions, some automatic memory > allocation (where temporary variables are malloced), large objects > appearing on the stack (because the kernel stack is so small). I > don't know if ctors for static objects would be called in the kernel. > Templates might also be a problem, but they might not. I'll second the "doability" of this. I've been going through some C++ work in an embedded system. Exceptions had already been given up on. The ctors/dtors are handled with "munch" style tools (from vxWorks land) that generate construct/destruct vectors that you'll probably then hook in with kernel modules. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 10: 8: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.unixbox.com (shell.unixbox.com [207.211.45.65]) by hub.freebsd.org (Postfix) with ESMTP id 942CF37B4C5; Tue, 14 Nov 2000 10:08:00 -0800 (PST) Received: from localhost (fengyue@localhost) by shell.unixbox.com (8.11.0/8.11.0) with ESMTP id eAEI8Ys64033; Tue, 14 Nov 2000 10:08:34 -0800 (PST) Date: Tue, 14 Nov 2000 10:08:34 -0800 (PST) From: FengYue X-Sender: fengyue@shell.unixbox.com To: Renaud Waldura Cc: Ruslan Ermilov , hackers@FreeBSD.ORG Subject: Re: PPPoE w/ nat auto fragmentation hack? (use tcpmssd port) In-Reply-To: <003701c04e5d$7d902e60$0402010a@biohz.net> 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, 14 Nov 2000, Renaud Waldura wrote: ->Dear hackers, -> ->> What exactly does not work? ->> What does the option -l do? -> ->When launched automatically by ppp, tcpmssd doesn't get any of the packets ->and is useless. When I start it manually from the command line, it works ->fine. -> ->I realize this isn't much in the way of helpful debugging information, and ->was hoping to further define this: I implemented that "-l" option to log all ->the packets processed by tcpmssd. I'm not even sure this bug applies to ->anybody else, which is why I did not seek help or publicize it until now. -> ->Anyway, I haven't been able to figure out what the problem is (and am ->lacking time now). The best I have is this: when launched by ppp, tcpmssd ->never seems to return from the main select() call. Ruslan, if you feel like ->an account on the machine where I'm using this could help, just let me know ->and I will gladly give you one. It does not work for me either. Start the script in rc.local rather than ppp.linkup works fine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 10:14:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38]) by hub.freebsd.org (Postfix) with ESMTP id 50F5A37B4E5 for ; Tue, 14 Nov 2000 10:14:17 -0800 (PST) Received: from imr3.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP (peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47]) id QQjpho13357 for ; Tue, 14 Nov 2000 18:14:16 GMT Received: from sysenglt112 by imr3.ash.ops.us.uu.net with SMTP (peer crosschecked as: ippool144-215.corp.us.uu.net [153.39.144.215]) id QQjpho15746 for ; Tue, 14 Nov 2000 18:12:01 GMT Reply-To: From: "Raymond Hicks" To: Subject: I wanna help Date: Tue, 14 Nov 2000 13:13:40 -0500 Message-ID: <000301c04e66$9ecfe7b0$d7902799@sysenglt112> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am Raymond Hicks and consider myself to be fairly knowledgable when it comes to BSD UNIX and your lovely OS FreeBSD.. I would like to help out by offering my time and technical knowhow to your development team.. If you would like specific information about my skills I can email you a detailed resume of past and current projects.. I would love to help out with the hackers mailing list as well.. Please let me know what I can do or who I need to contact... lates raymond hicks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 10:34:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id A528237B4FE for ; Tue, 14 Nov 2000 10:34:25 -0800 (PST) Received: from grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.1/8.11.1) with ESMTP id eAE8Xa105573; Tue, 14 Nov 2000 10:33:39 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200011140833.eAE8Xa105573@grimreaper.grondar.za> To: Alfred Perlstein Cc: hackers@freebsd.org Subject: Re: patches for 4.x devrandom so that bind "works" References: <20001113224849.Z11449@fw.wintelcom.net> In-Reply-To: <20001113224849.Z11449@fw.wintelcom.net> ; from Alfred Perlstein "Mon, 13 Nov 2000 22:48:49 PST." Date: Tue, 14 Nov 2000 10:33:36 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Yes, it is this simple :-). > > Can you get it ready for 4.2? I'd like to see us be able to > run bind9 in the next release. Sure. I'll see if I can do it in the next couple of hours. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.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 14 10:58:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.matriplex.com (ns1.matriplex.com [208.131.42.8]) by hub.freebsd.org (Postfix) with ESMTP id 73F2937B4D7 for ; Tue, 14 Nov 2000 10:58:36 -0800 (PST) Received: from mail.matriplex.com (mail.matriplex.com [208.131.42.9]) by mail.matriplex.com (8.9.2/8.9.2) with ESMTP id KAA40138 for ; Tue, 14 Nov 2000 10:58:30 -0800 (PST) (envelope-from rh@matriplex.com) Date: Tue, 14 Nov 2000 10:58:30 -0800 (PST) From: Richard Hodges To: freebsd-hackers@FreeBSD.ORG Subject: page fault question 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 been having a great time :-) debugging a device driver, and have run into a really fun way to panic. With one type of traffic, [something] happens and the kernel drops into DDB, just the way I want. Well, actually DDB seems to get trapped in some kind of loop that spews messages faster than a human can read them. When I finally got a piece of a clue, I booted with serial console and captured the following (also an endless loop): Fatal trap 12: page fault while in kernel mode fault virtual address = 0x8 fault code = supervisor read, page not present instruction pointer = 0x8:0xc014ed6b stack pointer = 0x10:0xc02b1360 frame pointer = 0x10:0xc02b1388 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = net tty bio cam kernel: type 12 trap, code=0 Stopped at The PC seems to have died in the DDB, that's odd (or maybe not?) ts7# nm /kernel | grep c014ed c014ed38 T linker_ddb_search_symbol c014edbc T linker_ddb_symbol_values Now looking back at the panic message, it looks like the stack has pushed into the "frame pointer". Is this an actual problem, or just some side effect of the page fault? Should I start spending my time looking for kernel stack hogs in the device driver? I can very easily add code to log ESP & EBP; would that be productive? Is there a maximum size for a softc? Maybe I'm accidentally ignoring some "code of the west" and am getting punished for it? (It wouldn't be the first time). Helpful flames gratefully accepted :-) Thanks, -Richard ------------------------------------------- Richard Hodges | Matriplex, inc. | 769 Basque Way rh@matriplex.com | Carson City, NV 89706 775-886-6477 | www.matriplex.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 14 11: 4:49 2000 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 0A26937B4FE for <freebsd-hackers@FreeBSD.ORG>; Tue, 14 Nov 2000 11:04:45 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAEJ4cu16447; Tue, 14 Nov 2000 11:04:38 -0800 (PST) Date: Tue, 14 Nov 2000 11:04:38 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: Raymond Hicks <rayhicks@UU.NET> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: I wanna help Message-ID: <20001114110437.H11449@fw.wintelcom.net> References: <000301c04e66$9ecfe7b0$d7902799@sysenglt112> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <000301c04e66$9ecfe7b0$d7902799@sysenglt112>; from rayhicks@UU.NET on Tue, Nov 14, 2000 at 01:13:40PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Raymond Hicks <rayhicks@UU.NET> [001114 10:14] wrote: > I am Raymond Hicks and consider myself to be fairly knowledgable when it > comes to BSD UNIX and your lovely OS FreeBSD.. I would like to help out by > offering my time and technical knowhow to your development team.. If you > would like specific information about my skills I can email you a detailed > resume of past and current projects.. I would love to help out with the > hackers mailing list as well.. Please let me know what I can do or who I > need to contact... The best ways to get on the devel team (committers) is: $foo = "then pester a committer about it"; 1) find solutions for PRs that have no patches $foo 2) submit PRs that contain patches for bugs and/or features $foo 3) implement a new facility, (driver, filesystem, network system, etc) $foo 4) submit ports via the PR system $foo best of luck, and hope to have you onboard soon. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 11: 6:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 8EECD37B4C5 for <freebsd-hackers@FreeBSD.ORG>; Tue, 14 Nov 2000 11:06:05 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAEJ5iR12883; Tue, 14 Nov 2000 12:05: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 MAA49023; Tue, 14 Nov 2000 12:05:44 -0700 (MST) Message-Id: <200011141905.MAA49023@harmony.village.org> To: Peter Dufault <dufault@hda.com> Subject: Re: C and C++ on FreeBSD Cc: freebsd-hackers@FreeBSD.ORG, tjmsdn@ifrance.com In-reply-to: Your message of "Tue, 14 Nov 2000 13:02:57 EST." <200011141802.NAA99016@hda.hda.com> References: <200011141802.NAA99016@hda.hda.com> Date: Tue, 14 Nov 2000 12:05:44 -0700 From: Warner Losh <imp@village.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200011141802.NAA99016@hda.hda.com> Peter Dufault writes: : C++ work in an embedded system. Exceptions had already been given : up on. The ctors/dtors are handled with "munch" style tools : (from vxWorks land) that generate construct/destruct : vectors that you'll probably then hook in with kernel modules. Yes. You could easily hook them into the sysinit facility with relative ease. You'd need to do a trick similar to the setdefs trick we do now (which was based on what munch from cfront land used to do). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 11:23: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from brutus.conectiva.com.br (brutus.conectiva.com.br [200.250.58.146]) by hub.freebsd.org (Postfix) with ESMTP id 67B9737B479 for <hackers@FreeBSD.ORG>; Tue, 14 Nov 2000 11:22:50 -0800 (PST) Received: from localhost (riel@localhost) by brutus.conectiva.com.br (8.11.1/8.11.1) with ESMTP id eAEJL9c28613; Tue, 14 Nov 2000 17:21:10 -0200 X-Authentication-Warning: duckman.distro.conectiva: riel owned process doing -bs Date: Tue, 14 Nov 2000 17:21:09 -0200 (BRDT) From: Rik van Riel <riel@conectiva.com.br> X-Sender: riel@duckman.distro.conectiva To: Terry Lambert <tlambert@primenet.com> Cc: void <float@firedrake.org>, hackers@FreeBSD.ORG Subject: Re: "iowait" CPU state In-Reply-To: <200011101833.LAA23780@usr08.primenet.com> Message-ID: <Pine.LNX.4.21.0011141720170.25493-100000@duckman.distro.conectiva> 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, 10 Nov 2000, Terry Lambert wrote: > > Thank you! This gets the me disk %busy, which is one of the things I > > was looking for. Now, can anyone tell me how to tell what percentage of > > processor time is being spent waiting for disk I/O to complete? > > Uh, none? > > If there is disk I/O pending, the processor just runs a > different process... am I missing your question? I guess it might be useful to see the difference between "true" idle time and time the system couldn't do anything useful because it was blocked on the disk (but /should/ have done something useful...). regards, Rik -- "What you're running that piece of shit Gnome?!?!" -- Miguel de Icaza, UKUUG 2000 http://www.conectiva.com/ http://www.surriel.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 14 13:18:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 3325437B4C5; Tue, 14 Nov 2000 13:18:16 -0800 (PST) Received: from bonsai.knology.net (user-24-214-88-8.knology.net [24.214.88.8]) by mail.hiwaay.net (8.11.0/8.11.0) with ESMTP id eAELID701563; Tue, 14 Nov 2000 15:18:14 -0600 (CST) Received: (from steve@localhost) by bonsai.knology.net (8.11.0/8.9.3) id eAELID665537; Tue, 14 Nov 2000 15:18:13 -0600 (CST) (envelope-from steve) Date: Tue, 14 Nov 2000 15:18:12 -0600 From: Steve Price <sprice@hiwaay.net> To: alpha@freebsd.org Cc: hackers@freebsd.org Subject: kernel boot question Message-ID: <20001114151812.F62344@bonsai.knology.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This may seem like a strange request but ... I'm trying to rebuild my Alpha box with the latest 4.2RC bits so I can start and new package build with the new libc (with version no. bump). The box is two hours North of here and everyone that is at the office right now is pretty clueless about computers. I updated everything but the box is not coming back up. I either have to figure out how to get it back on its feet remotely or drive 2 hours up there to fix it myself. I talked one of the people through booting it back up with kernel.old so I can get back into the box now. My question is is there a way to seed the boot process try a new (test) kernel once and if it panics then go back to using the regular kernel? So it would go something like this. boot kernel.test panic boot kernel tweak and rebuild new kernel rinse and repeat Thanks. BTW, the last part of the dmesg output looks like this and the only thing I changed in the GENERIC kernel config was 'maxusers 64': Mounting root from ufs:/dev/da0a da0 at sym0 bus 0 target 0 lun 0 da0: <IBM DDRS-39130D DC1B> Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) da1 at sym0 bus 0 target 9 lun 0 da1: <IBM DDRS-39130D DC1B> Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) WARNING: / was not properly dismounted panic: kmem_malloc(536887296): kmem_map too small: 5685248 total allocated syncing disks... 8 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 giving up on 3 buffers Uptime: 2m4s Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 13:28:58 2000 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 2C71737B479 for <hackers@FreeBSD.ORG>; Tue, 14 Nov 2000 13:28:55 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA79032; Tue, 14 Nov 2000 14:28:20 -0700 (MST) (envelope-from ken) Date: Tue, 14 Nov 2000 14:28:20 -0700 From: "Kenneth D. Merry" <ken@kdm.org> To: "Jeroen C. van Gelderen" <jeroen@vangelderen.org> Cc: "Jin Guojun (DSD staff)" <jin@george.lbl.gov>, hackers@FreeBSD.ORG Subject: Re: zero copy TCP Message-ID: <20001114142820.A79002@panzer.kdm.org> References: <200011140149.eAE1nRI14099@portnoy.lbl.gov> <3A11401F.85B7F51E@vangelderen.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3A11401F.85B7F51E@vangelderen.org>; from jeroen@vangelderen.org on Tue, Nov 14, 2000 at 09:37:35AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 14, 2000 at 09:37:35 -0400, Jeroen C. van Gelderen wrote: > "Jin Guojun (DSD staff)" wrote: > > > > I heard that zero copy TCP is already in FreeBSD, isn't it? > > I could not find any information in searching the entire website. > > Before I am going to spend some silly time working on it, > > I would like to know what is the status for "ZERO COPY TCP" in > > FreeBSD right now. > > If it already exists, how can I enable it (for 1500 MTU, not Jumbo Frame)? > > or someone is still working on it. > > http://people.freebsd.org/~ken/ > http://people.freebsd.org/~ken/zero_copy/ FWIW, I just put up a new snapshot. All known bugs are now fixed. :) 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 Tue Nov 14 13:32:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from home.welcomehome.org (home.welcomehome.org [209.6.45.100]) by hub.freebsd.org (Postfix) with ESMTP id 7F81337B479 for <freebsd-hackers@freebsd.org>; Tue, 14 Nov 2000 13:32:50 -0800 (PST) Received: (from paonia@localhost) by home.welcomehome.org (8.9.3+3.2W/8.9.3/Debian 8.9.3-21) id QAA17474 for freebsd-hackers@freebsd.org; Tue, 14 Nov 2000 16:32:49 -0500 From: Paonia Ezrine <paonia@home.welcomehome.org> Message-Id: <200011142132.QAA17474@home.welcomehome.org> Subject: looking for kernel hacking info To: freebsd-hackers@freebsd.org Date: Tue, 14 Nov 2000 16:32:49 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL66 (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 I am looking for info on programing in kernel land. System calls, howto's etc. I have not found anything that realy covers this stuff any and all help would be welcomed! thanks Paonia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 13:59:44 2000 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 C8BA537B4C5; Tue, 14 Nov 2000 13:59:31 -0800 (PST) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with ESMTP id QAA29107; Tue, 14 Nov 2000 16:57:51 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20001114165655.03b2beb0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Tue, 14 Nov 2000 16:58:16 -0500 To: hackers@freebsd.org From: Dennis <dennis@etinc.com> Subject: RE: Best Gigabit ethernet for 4.x Cc: isp@freebsd.org In-Reply-To: <5FE9B713CCCDD311A03400508B8B301301C7892A@bdr-xcln.is.match logic.com> 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 What is the adapter of choice for gigabit ethernet for 4.x FreeBSD? thanks. DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 14:11:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from errata.net (unknown [63.216.201.162]) by hub.freebsd.org (Postfix) with ESMTP id 20E9F37B479 for <freebsd-hackers@freebsd.org>; Tue, 14 Nov 2000 14:11:19 -0800 (PST) Received: from anthrax (ppp020-bsace7009.telebrasilia.net.br [200.181.88.20]) by errata.net (8.9.3/8.9.3) with ESMTP id PAA87997 for <freebsd-hackers@freebsd.org>; Tue, 14 Nov 2000 15:09:57 -0500 (EST) (envelope-from visi0n@aux-tech.org) Date: Wed, 15 Nov 2000 06:19:34 +0000 (GMT) From: visi0n <visi0n@aux-tech.org> X-Sender: visi0n@anthrax.chinatown.org To: freebsd-hackers@freebsd.org Subject: libexec directory error ? Message-ID: <Pine.BSF.4.21.0011140801190.163-100000@anthrax.chinatown.org> 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 a box with FreeBSD 4.1 installed and when I ls -l /usr I saw something weird... anthrax# ls -la total 35 drwxr-xr-x 18 root wheel 512 Oct 17 02:55 . drwxr-xr-x 15 root wheel 512 Oct 8 02:23 .. drwxr-xr-x 3 root wheel 512 Oct 10 19:06 X11R6 drwxr-xr-x 3 root wheel 512 Oct 8 02:37 aux drwxr-xr-x 2 root wheel 6656 Oct 8 02:21 bin drwxr-xr-x 2 root wheel 512 Oct 8 02:22 compat drwxr-xr-x 2 root wheel 512 Oct 24 08:22 downloads drwxr-xr-x 3 root wheel 512 Oct 8 02:23 home drwxr-xr-x 35 root wheel 3072 Oct 8 02:21 include drwxr-xr-x 4 root wheel 5632 Jul 28 14:44 lib drwxr-xr-x 9 root wheel 512 Oct 8 02:19 libdata drwxr-xr-x 8 root wheel 2199023257088 Oct 8 02:22 libexec drwxr-xr-x 11 root wheel 512 Oct 8 02:25 local drwxr-xr-x 2 root wheel 512 Oct 8 02:22 obj drwxr-xr-x 2 root wheel 4096 Oct 8 02:21 sbin drwxr-xr-x 25 root wheel 512 Oct 8 02:22 share drwxr-xr-x 5 root wheel 512 Oct 8 02:21 src drwxrwxrwt 2 root wheel 512 Oct 28 22:35 tmp anthrax# this is a default installation and I didnt change anything in the configuration even the kernel. My dmesg follows. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.1-RELEASE #0: Fri Jul 28 14:30:31 GMT 2000 jkh@ref4.freebsd.org:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (451.03-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX> AMD Features=0x80000800<SYSCALL,3DNow!> real memory = 134152192 (131008K bytes) config> di lnc0 config> di le0 config> di ie0 config> di fe0 config> di cs0 config> di bt0 config> di aic0 config> di aha0 config> di adv0 config> en sn0 config> po sn0 0x220 config> ir sn0 11 config> f sn0 0 config> en ed0 config> po ed0 0x260 config> ir ed0 9 config> iom ed0 0xd8000 config> f ed0 0 config> q avail memory = 126341120 (123380K bytes) Preloaded elf kernel "kernel" at 0xc040d000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc040d09c. K6-family MTRR support enabled (2 registers) md0: Malloc disk npx0: <math processor> on motherboard npx0: INT 16 interface pcib0: <Host to PCI bridge> on motherboard pci0: <PCI bus> on pcib0 pcib2: <VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge> at device 1.0 on pci0 pci1: <PCI bus> on pcib2 isab0: <VIA 82C586 PCI-ISA bridge> at device 7.0 on pci0 isa0: <ISA bus> on isab0 atapci0: <VIA 82C586 ATA33 controller> port 0xe000-0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 uhci0: <VIA 83C572 USB controller> port 0xe400-0xe41f irq 11 at device 7.2 on p$usb0: <VIA 83C572 USB controller> on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub0: port 1 power on failed, IOERROR uhub0: port 2 power on failed, IOERROR wb0: <Winbond W89C840F 10/100BaseTX> port 0xe800-0xe87f mem 0xd1400000-0xd14000$wb0: Ethernet address: 00:40:c7:a6:11:ee miibus0: <MII bus> on wb0 ukphy0: <Generic IEEE 802.3u media interface> on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcib1: <Host to PCI bridge> on motherboard pci2: <PCI bus> on pcib1 fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0 vga0: <Generic ISA VGA> at port 0x3d0-0x3db iomem 0xb8000-0xbffff on isa0 sc0: <System console> at flags 0x100 on isa0 sc0: CGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppi0: <Parallel I/O> on ppbus0 lpt0: <Printer> on ppbus0 lpt0: Interrupt-driven port plip0: <PLIP network interface> on ppbus0 ad0: 516MB <QUANTUM MAVERICK 540A> [1049/16/63] at ata0-master using PIO3 =============================================================================== visi0n AUX Technologies [www.aux-tech.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 14 14:26:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 6ED5837B4D7; Tue, 14 Nov 2000 14:26:27 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp245.osd.bsdi.com [204.216.28.245]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id eAEMQJB01936; Tue, 14 Nov 2000 14:26:19 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: <XFMail.001114142649.jhb@FreeBSD.org> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20001114151812.F62344@bonsai.knology.net> Date: Tue, 14 Nov 2000 14:26:49 -0800 (PST) From: John Baldwin <jhb@FreeBSD.org> To: Steve Price <sprice@hiwaay.net> Subject: RE: kernel boot question Cc: hackers@FreeBSD.org, alpha@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Nov-00 Steve Price wrote: > This may seem like a strange request but ... I'm trying to rebuild > my Alpha box with the latest 4.2RC bits so I can start and new > package build with the new libc (with version no. bump). The box > is two hours North of here and everyone that is at the office right > now is pretty clueless about computers. I updated everything but > the box is not coming back up. I either have to figure out how to > get it back on its feet remotely or drive 2 hours up there to fix > it myself. I talked one of the people through booting it back up > with kernel.old so I can get back into the box now. > > My question is is there a way to seed the boot process try a new > (test) kernel once and if it panics then go back to using the regular > kernel? So it would go something like this. > > boot kernel.test > panic > boot kernel > tweak and rebuild new kernel > rinse and repeat > > Thanks. Don't compile ddb into your test kernel. :) > BTW, the last part of the dmesg output looks like this and the only > thing I changed in the GENERIC kernel config was 'maxusers 64': > > Mounting root from ufs:/dev/da0a > da0 at sym0 bus 0 target 0 lun 0 > da0: <IBM DDRS-39130D DC1B> Fixed Direct Access SCSI-2 device > da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing > Enabled > da0: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) > da1 at sym0 bus 0 target 9 lun 0 > da1: <IBM DDRS-39130D DC1B> Fixed Direct Access SCSI-2 device > da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing > Enabled > da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) > WARNING: / was not properly dismounted > panic: kmem_malloc(536887296): kmem_map too small: 5685248 total allocated > > syncing disks... 8 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 > giving up on 3 buffers > Uptime: 2m4s > Automatic reboot in 15 seconds - press a key on the console to abort > Rebooting... Looks like your mountd is out of sync with your kernel. > -steve -- John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Tue Nov 14 14:34:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from krell.webweaver.net (krell.webweaver.net [206.24.105.170]) by hub.freebsd.org (Postfix) with ESMTP id 810C137B4D7 for <freebsd-hackers@freebsd.org>; Tue, 14 Nov 2000 14:34:54 -0800 (PST) Received: from xwin.nmhtech.com (xwin.nmhtech.com [208.138.46.10]) by krell.webweaver.net (Postfix) with ESMTP id 85A1720F0C for <freebsd-hackers@freebsd.org>; Tue, 14 Nov 2000 14:20:10 -0800 (PST) Content-Length: 1067 Message-ID: <XFMail.001114143454.nicole@unixgirl.com> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 14 Nov 2000 14:34:54 -0700 (PST) From: Nicole <nicole@unixgirl.com> To: freebsd-hackers@freebsd.org Subject: What is the cost of a simlink? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings I have a disk load problem I was hoping to solve by using an added disk and simlinking a number of directories over to the new disk. These are directories to be accessed by apache and there may be as many as 40-60 simlinks to the new drive for the data directories. My question is how much of a hit do I take by using this large a number of simlinks? How much processing/memory usage does it eat to traverse a link from one disk top another? Thanks!! Nicole nicole@unixgirl.com |\ __ /| (`\ http://www.unixgirl.com/ webmistress@dangermouse.org | o_o |__ ) ) http://www.dangermouse.org/ nicole@deviantimages.com // \\ http://www.deviantimages.com/ ---------------------------(((---(((----------------------------------------- -- Powered by Coka-Cola and FreeBSD -- -- "I drank WHAT ?!" - Socrates -- Hmm You seem better - "been giving myself shock treatments" Up the Voltage! ----------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 14:37:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id DBB8B37B4FE; Tue, 14 Nov 2000 14:37:50 -0800 (PST) Received: from bonsai.knology.net (user-24-214-88-8.knology.net [24.214.88.8]) by mail.hiwaay.net (8.11.0/8.11.0) with ESMTP id eAEMbi731239; Tue, 14 Nov 2000 16:37:45 -0600 (CST) Received: (from steve@localhost) by bonsai.knology.net (8.11.0/8.9.3) id eAEMbc278051; Tue, 14 Nov 2000 16:37:38 -0600 (CST) (envelope-from steve) Date: Tue, 14 Nov 2000 16:37:38 -0600 From: Steve Price <sprice@hiwaay.net> To: John Baldwin <jhb@FreeBSD.org> Cc: Steve Price <sprice@hiwaay.net>, hackers@FreeBSD.org, alpha@FreeBSD.org Subject: Re: kernel boot question Message-ID: <20001114163738.K62344@bonsai.knology.net> References: <20001114151812.F62344@bonsai.knology.net> <XFMail.001114142649.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <XFMail.001114142649.jhb@FreeBSD.org>; from jhb@FreeBSD.org on Tue, Nov 14, 2000 at 02:26:49PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 14, 2000 at 02:26:49PM -0800, John Baldwin wrote: # # > WARNING: / was not properly dismounted # > panic: kmem_malloc(536887296): kmem_map too small: 5685248 total allocated # > # > syncing disks... 8 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 # > giving up on 3 buffers # > Uptime: 2m4s # > Automatic reboot in 15 seconds - press a key on the console to abort # > Rebooting... # # Looks like your mountd is out of sync with your kernel. Yep, that was it. Thanks. -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 14:59:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 64B4337B4D7 for <freebsd-hackers@freebsd.org>; Tue, 14 Nov 2000 14:59:23 -0800 (PST) Received: from gaborone-34.budapest.interware.hu ([195.70.52.162] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 13vp2t-0002jR-00; Tue, 14 Nov 2000 23:59:19 +0100 Message-ID: <3A113077.FD5979BF@elischer.org> Date: Tue, 14 Nov 2000 04:30:47 -0800 From: Julian Elischer <julian@elischer.org> X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Chris Ptacek <ptacek@technologist.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: KLDs and PCI? References: <NEBBKLFHMJGHPAEKCHJJGELNCEAA.ptacek@technologist.com> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try use the newest version of /usr/share/examples/drivers/make_device_driver.sh I just added PCI support (but I have't tested it much yet) Hopefully I'll get feedback it it's too radically wrong. > I am working on a KLD for a PCI device. My problem is I can't find how to > call the probe and attach calls during the load for a PCI device. I have > looked in the /usr/src/sys/pci directory and haven't found any KLDs to use > as an example. What are the steps I need to take to handle a PCI device in > a KLD? Are there any examples I can look out? > > Oh yeah, I am doing this for a FreeBSD 3.x system (I know, but is needed for > this project, it will be ported to 4.x later) > > - Chris > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 15:13: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 539F637B479 for <freebsd-hackers@FreeBSD.ORG>; Tue, 14 Nov 2000 15:12:57 -0800 (PST) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id eAENBdj41133; Wed, 15 Nov 2000 09:41:39 +1030 (CST) (envelope-from grog) Date: Wed, 15 Nov 2000 09:41:39 +1030 From: Greg Lehey <grog@lemis.com> To: Paonia Ezrine <paonia@home.welcomehome.org> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: looking for kernel hacking info Message-ID: <20001115094139.C39755@wantadilla.lemis.com> References: <200011142132.QAA17474@home.welcomehome.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200011142132.QAA17474@home.welcomehome.org>; from paonia@home.welcomehome.org on Tue, Nov 14, 2000 at 04:32:49PM -0500 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 14 November 2000 at 16:32:49 -0500, Paonia Ezrine wrote: > I am looking for info on programing in kernel land. System calls, howto's > etc. I have not found anything that realy covers this stuff any and all > help would be welcomed! The system calls are described in section 2 of the manual. 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 14 15:28:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dayspring.firedrake.org (dayspring.firedrake.org [195.82.105.251]) by hub.freebsd.org (Postfix) with ESMTP id 6FD3637B4C5 for <freebsd-hackers@freebsd.org>; Tue, 14 Nov 2000 15:28:27 -0800 (PST) Received: from float by dayspring.firedrake.org with local (Exim 3.12 #1 (Debian)) id 13vpUn-0003oM-00; Tue, 14 Nov 2000 23:28:09 +0000 Date: Tue, 14 Nov 2000 23:28:09 +0000 To: Nicole <nicole@unixgirl.com> Cc: freebsd-hackers@freebsd.org Subject: Re: What is the cost of a simlink? Message-ID: <20001114232809.A14478@firedrake.org> References: <XFMail.001114143454.nicole@unixgirl.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <XFMail.001114143454.nicole@unixgirl.com>; from nicole@unixgirl.com on Tue, Nov 14, 2000 at 02:34:54PM -0700 From: void <float@firedrake.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 14, 2000 at 02:34:54PM -0700, Nicole wrote: > > Greetings > I have a disk load problem I was hoping to solve by using an added disk and > simlinking a number of directories over to the new disk. > > These are directories to be accessed by apache and there may be as many as > 40-60 simlinks to the new drive for the data directories. > > My question is how much of a hit do I take by using this large a number of > simlinks? How much processing/memory usage does it eat to traverse a link from > one disk top another? It's about the same cost as another layer of directory structure. The biggest cost will be disk seeks, but if you have enough memory, that shouldn't happen too often. -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 17:46:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 574FC37B479; Tue, 14 Nov 2000 17:46:39 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.1/8.11.1) with ESMTP id eAF1goF16913; Wed, 15 Nov 2000 01:42:50 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.1/8.11.1) with ESMTP id eAF1hQF04103; Wed, 15 Nov 2000 01:43:26 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200011150143.eAF1hQF04103@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: FengYue <fengyue@bluerose.windmoon.nu> Cc: Renaud Waldura <renaud@waldura.com>, Ruslan Ermilov <ru@FreeBSD.ORG>, hackers@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: PPPoE w/ nat auto fragmentation hack? (use tcpmssd port) In-Reply-To: Message from FengYue <fengyue@bluerose.windmoon.nu> of "Tue, 14 Nov 2000 10:08:34 PST." <Pine.BSF.4.21.0011141007130.63974-100000@shell.unixbox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Nov 2000 01:43:25 +0000 From: Brian Somers <brian@Awfulhak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Tue, 14 Nov 2000, Renaud Waldura wrote: > > ->Dear hackers, > -> > ->> What exactly does not work? > ->> What does the option -l do? > -> > ->When launched automatically by ppp, tcpmssd doesn't get any of the packets > ->and is useless. When I start it manually from the command line, it works > ->fine. > -> > ->I realize this isn't much in the way of helpful debugging information, and > ->was hoping to further define this: I implemented that "-l" option to log all > ->the packets processed by tcpmssd. I'm not even sure this bug applies to > ->anybody else, which is why I did not seek help or publicize it until now. > -> > ->Anyway, I haven't been able to figure out what the problem is (and am > ->lacking time now). The best I have is this: when launched by ppp, tcpmssd > ->never seems to return from the main select() call. Ruslan, if you feel like > ->an account on the machine where I'm using this could help, just let me know > ->and I will gladly give you one. > > It does not work for me either. Start the script in rc.local rather than > ppp.linkup works fine. What are you doing in ppp.linkup ? When I add this: ! sudo ipfw add 40000 divert 12345 all from any to any via INTERFACE ! sudo /usr/local/bin/tcpmssd -p 12345 -i INTERFACE everything seems to work ok.... -- Brian <brian@Awfulhak.org> <brian@[uk.]FreeBSD.org> <http://www.Awfulhak.org> <brian@[uk.]OpenBSD.org> 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 14 18: 1:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from errata.net (permission.denied.org [63.216.201.162]) by hub.freebsd.org (Postfix) with ESMTP id 4C71937B479 for <freebsd-hackers@FreeBSD.ORG>; Tue, 14 Nov 2000 18:01:12 -0800 (PST) Received: from anthrax (ppp020-bsace7009.telebrasilia.net.br [200.181.88.20]) by errata.net (8.9.3/8.9.3) with ESMTP id SAA88619; Tue, 14 Nov 2000 18:59:08 -0500 (EST) (envelope-from visi0n@aux-tech.org) Date: Wed, 15 Nov 2000 10:08:45 +0000 (GMT) From: visi0n <visi0n@aux-tech.org> X-Sender: visi0n@anthrax.chinatown.org To: Greg Lehey <grog@lemis.com> Cc: Paonia Ezrine <paonia@home.welcomehome.org>, freebsd-hackers@FreeBSD.ORG Subject: Re: looking for kernel hacking info In-Reply-To: <20001115094139.C39755@wantadilla.lemis.com> Message-ID: <Pine.BSF.4.21.0011151003330.1362-100000@anthrax.chinatown.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The THC have a documentation about freebsd kernel space. packetstorm.securify.com/groups/thc/bsdkern.htm =============================================================================== visi0n AUX Technologies [www.aux-tech.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 14 18:14: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from KIWI-Computer.com (kiwi-computer.com [63.224.10.3]) by hub.freebsd.org (Postfix) with ESMTP id DB26837B4C5 for <freebsd-hackers@freebsd.org>; Tue, 14 Nov 2000 18:14:03 -0800 (PST) Received: from localhost (shadow@localhost) by KIWI-Computer.com (8.9.3/8.9.3) with ESMTP id UAA44123 for <freebsd-hackers@freebsd.org>; Tue, 14 Nov 2000 20:12:03 -0600 (CST) (envelope-from shadow@megan.kiwi-computer.com) Date: Tue, 14 Nov 2000 20:12:03 -0600 (CST) From: Dave Howland <shadow@KIWI-Computer.com> To: freebsd-hackers@freebsd.org Subject: Moused doesn't reinitialize mouse after removal and reinsertion... Message-ID: <Pine.BSF.4.21.0011142010480.44097-100000@megan.kiwi-computer.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's a puzzle for someone who has a little free time... I've got a manual switchbox to switch my mouse, keyboard, and monitor between to computers. It's a manual switchbox, so it doesn't send a constant signal to both systems (like those fancy - and expensive - automatic ones). Here's the problem: When my mouse (actully a trackball, a PS/2 Logitech TrackMan Marble) is unplugged from the system, it ceases to remember how to send a signal to the system (I assume some initialization is being done by moused when it starts up). So, when I switch over to my second system and back over to the FreeBSD one, the cursor doesn't respond to any mouse movement. To fix it I have to kill moused and start it back up. Sort of a pain, albeit not completely unbearable. Anyone have any theories on how we could get moused to a) detect the mouse being unplugged and reinserted and b) reinitialize the mouse after this happens? Here's some fun info type stuff (in case it'll help)... I'm running FreeBSD 4.2-BETA #10 (although I believe the problem existed under FreeBSD 4.1-RELEASE too. From dmesg (after a verbose boot): psm0: current command byte:0065 psm: status 00 02 64 psm: status 09 03 c8 psm: status 09 03 c8 psm: status 09 03 c8 psm: data 08 00 00 psm: status 10 00 64 psm: status 00 02 64 psm: data 08 00 00 psm: status 00 02 64 psm0: <PS/2 Mouse> irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0-00, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 From rc.conf: moused_flags="" moused_port="/dev/psm0" moused_type="auto" moused_enable="YES" I'd greatly appreciate any help anyone can give me! If you need any more info about my system setup, just give me a yell... Thanks a million.... Dave Howland shadow@kiwi-computer.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 14 18:14:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from home.welcomehome.org (home.welcomehome.org [209.6.45.100]) by hub.freebsd.org (Postfix) with ESMTP id 7249837B4C5 for <freebsd-hackers@FreeBSD.ORG>; Tue, 14 Nov 2000 18:14:41 -0800 (PST) Received: (from paonia@localhost) by home.welcomehome.org (8.9.3+3.2W/8.9.3/Debian 8.9.3-21) id VAA27289; Tue, 14 Nov 2000 21:14:25 -0500 From: Paonia Ezrine <paonia@home.welcomehome.org> Message-Id: <200011150214.VAA27289@home.welcomehome.org> Subject: Re: looking for kernel hacking info In-Reply-To: <20001115094139.C39755@wantadilla.lemis.com> from Greg Lehey at "Nov 15, 2000 09:41:39 am" To: Greg Lehey <grog@lemis.com> Date: Tue, 14 Nov 2000 21:14:25 -0500 (EST) Cc: Paonia Ezrine <paonia@home.welcomehome.org>, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL66 (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 > On Tuesday, 14 November 2000 at 16:32:49 -0500, Paonia Ezrine wrote: > > I am looking for info on programing in kernel land. System calls, howto's > > etc. I have not found anything that realy covers this stuff any and all > > help would be welcomed! > > The system calls are described in section 2 of the manual. > > Greg thanks. do you mean handbook? thanks Paonia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 18:39:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.prod.itd.earthlink.net [207.217.121.49]) by hub.freebsd.org (Postfix) with ESMTP id 9CE3D37B4D7 for <hackers@FreeBSD.ORG>; Tue, 14 Nov 2000 18:39:39 -0800 (PST) Received: from eln005748 (lanadmin1.mis.earthlink.net [207.217.65.4]) by scaup.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with SMTP id SAA15748 for <hackers@FreeBSD.ORG>; Tue, 14 Nov 2000 18:39:38 -0800 (PST) Message-ID: <003401c04ead$4a6537b0$0441d9cf@earthlink.net> From: "Steveb 99" <steveb98@earthlink.net> To: <hackers@FreeBSD.ORG> References: <200011140149.eAE1nRI14099@portnoy.lbl.gov> <3A11401F.85B7F51E@vangelderen.org> Subject: Porting Linux to FreeBSD Date: Tue, 14 Nov 2000 18:39:34 -0800 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.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How different is Linux from FreeBSD when it comes to porting code. Nothing specific just in general, are there major differences or small differences. Assuming same hardware just OS is different. Device driver vs applications. What areas are the gottcha's? Steve 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 14 18:47:10 2000 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 DFB6137B479 for <hackers@FreeBSD.ORG>; Tue, 14 Nov 2000 18:47:07 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAF2l6Z01609; Tue, 14 Nov 2000 18:47:06 -0800 (PST) Date: Tue, 14 Nov 2000 18:47:06 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: Steveb 99 <steveb98@earthlink.net> Cc: hackers@FreeBSD.ORG Subject: Re: Porting Linux to FreeBSD Message-ID: <20001114184706.C29448@fw.wintelcom.net> References: <200011140149.eAE1nRI14099@portnoy.lbl.gov> <3A11401F.85B7F51E@vangelderen.org> <003401c04ead$4a6537b0$0441d9cf@earthlink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <003401c04ead$4a6537b0$0441d9cf@earthlink.net>; from steveb98@earthlink.net on Tue, Nov 14, 2000 at 06:39:34PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Steveb 99 <steveb98@earthlink.net> [001114 18:39] wrote: > How different is Linux from FreeBSD when it comes to porting code. Nothing > specific just in general, are there major differences or small differences. > Assuming same hardware just OS is different. Device driver vs applications. > What areas are the gottcha's? (I wish you had been more specific...) There can be a lot of gotchas if you're not careful and you use low level interfaces into the system, let me explain: If you use Linux's SOCK_PACKET to do packet filtering you're in for a minor headache when porting to FreeBSD because FreeBSD doesn't have this. However, if you use the freely available 'libpcap' your application would work on Linux and FreeBSD (and Solaris, and others) without problems because libpcap offers an abstraction over several 'native' packet filters. It's really a matter of how your code is done and how Linux specific it is, if you've already ported to Solaris as well as Linux you'll probably find most of the kinks worked out by the time you get around to FreeBSD. But if you make it a habit of #include <linux/foo.h> you're not going to have much fun. As far as device drivers there's some similarities but also a lot of differences with locking structure and internals such as network buffers and IO buffers, porting drivers is most likely going to be a lot more difficult that porting application code. best of luck, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 18:47:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.gbch.net (gw.gbch.net [203.24.22.66]) by hub.freebsd.org (Postfix) with SMTP id 0B2FA37B4C5 for <freebsd-hackers@FreeBSD.ORG>; Tue, 14 Nov 2000 18:47:30 -0800 (PST) Received: (qmail 94532 invoked by uid 1001); 15 Nov 2000 12:47:22 +1000 X-Posted-By: GBA-Post 2.06 15-Sep-2000 X-PGP-Fingerprint: 5A91 6942 8CEA 9DAB B95B C249 1CE1 493B 2B5A CE30 X-PGP-Public-Key: <http://www.gbch.net/gjb/gjb-pgpkey.asc> Message-Id: <nospam-3a11f950251711a@maxim.gbch.net> Date: Wed, 15 Nov 2000 12:47:22 +1000 From: Greg Black <gjb@gbch.net> To: Paonia Ezrine <paonia@home.welcomehome.org> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: looking for kernel hacking info References: <200011150214.VAA27289@home.welcomehome.org> In-reply-to: <200011150214.VAA27289@home.welcomehome.org> of Tue, 14 Nov 2000 21:14:25 EST Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Paonia Ezrine wrote: > > The system calls are described in section 2 of the manual. > thanks. do you mean handbook? No, he meant what he said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 14 18:51:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 5F7A437B479 for <freebsd-hackers@FreeBSD.ORG>; Tue, 14 Nov 2000 18:51:16 -0800 (PST) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id eAF2p5Q46071; Wed, 15 Nov 2000 13:21:05 +1030 (CST) (envelope-from grog) Date: Wed, 15 Nov 2000 13:21:05 +1030 From: Greg Lehey <grog@lemis.com> To: Paonia Ezrine <paonia@home.welcomehome.org> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: looking for kernel hacking info Message-ID: <20001115132105.H39755@wantadilla.lemis.com> References: <20001115094139.C39755@wantadilla.lemis.com> <200011150214.VAA27289@home.welcomehome.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200011150214.VAA27289@home.welcomehome.org>; from paonia@home.welcomehome.org on Tue, Nov 14, 2000 at 09:14:25PM -0500 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 14 November 2000 at 21:14:25 -0500, Paonia Ezrine wrote: > > >> On Tuesday, 14 November 2000 at 16:32:49 -0500, Paonia Ezrine wrote: >>> I am looking for info on programing in kernel land. System calls, howto's >>> etc. I have not found anything that realy covers this stuff any and all >>> help would be welcomed! >> >> The system calls are described in section 2 of the manual. > > thanks. do you mean handbook? No, the manual. That's the real name for the man pages. Read it with man(1). 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 14 19: 2:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id C37E537B479 for <freebsd-hackers@FreeBSD.ORG>; Tue, 14 Nov 2000 19:02:36 -0800 (PST) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id eAF32Ad46113; Wed, 15 Nov 2000 13:32:10 +1030 (CST) (envelope-from grog) Date: Wed, 15 Nov 2000 13:32:10 +1030 From: Greg Lehey <grog@lemis.com> To: visi0n <visi0n@aux-tech.org> Cc: Paonia Ezrine <paonia@home.welcomehome.org>, freebsd-hackers@FreeBSD.ORG Subject: Re: looking for kernel hacking info Message-ID: <20001115133210.I39755@wantadilla.lemis.com> References: <20001115094139.C39755@wantadilla.lemis.com> <Pine.BSF.4.21.0011151003330.1362-100000@anthrax.chinatown.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <Pine.BSF.4.21.0011151003330.1362-100000@anthrax.chinatown.org>; from visi0n@aux-tech.org on Wed, Nov 15, 2000 at 10:08:45AM +0000 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 15 November 2000 at 10:08:45 +0000, visi0n wrote: > > The THC have a documentation about freebsd kernel space. > > packetstorm.securify.com/groups/thc/bsdkern.htm Repeating the full URL for the benefit of mutt users, this is http://packetstorm.securify.com/groups/thc/bsdkern.htm This is an interesting document. It describes how to insert a Trojan into the FreeBSD kernel When it came out, we discussed it and decided that it would be of no danger to a properly secured system. On the other hand, the documentation is relatively well done. We should really import it. 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 14 23:13:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 6B61337B4CF for <freebsd-hackers@FreeBSD.ORG>; Tue, 14 Nov 2000 23:13:51 -0800 (PST) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAF7DTR15542; Wed, 15 Nov 2000 00:13:29 -0700 (MST) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.1/8.8.3) with ESMTP id eAF7FLG47669; Wed, 15 Nov 2000 00:15:21 -0700 (MST) Message-Id: <200011150715.eAF7FLG47669@billy-club.village.org> To: Dave Howland <shadow@KIWI-Computer.com> Subject: Re: Moused doesn't reinitialize mouse after removal and reinsertion... Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 14 Nov 2000 20:12:03 CST." <Pine.BSF.4.21.0011142010480.44097-100000@megan.kiwi-computer.com> References: <Pine.BSF.4.21.0011142010480.44097-100000@megan.kiwi-computer.com> Date: Wed, 15 Nov 2000 00:15:20 -0700 From: Warner Losh <imp@village.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <Pine.BSF.4.21.0011142010480.44097-100000@megan.kiwi-computer.com> Dave Howland writes: : pain, albeit not completely unbearable. Anyone have any theories on how we : could get moused to a) detect the mouse being unplugged and reinserted and : b) reinitialize the mouse after this happens? Here's some fun info type : stuff (in case it'll help)... With all due respect, pay the extra money for the electric switch. You will burn out your keyboard and mouse ports if you aren't careful. They aren't designed for this sort of hot plugging. I used to think it was OK to do this, but I've had too many keyboard and/or mouse controllers die of the years connected to a mechanical switch to really trust them. 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 15 2:25: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hawk.gnome.co.uk (gnome.gw.cerbernet.net [193.243.224.22]) by hub.freebsd.org (Postfix) with ESMTP id 0AE2137B479; Wed, 15 Nov 2000 02:24:47 -0800 (PST) Received: from hawk.gnome.co.uk (localhost [127.0.0.1]) by hawk.gnome.co.uk (8.11.1/8.11.1) with ESMTP id eAFANIN01084; Wed, 15 Nov 2000 10:23:18 GMT (envelope-from jacs@hawk.gnome.co.uk) Message-Id: <200011151023.eAFANIN01084@hawk.gnome.co.uk> X-Mailer: exmh version 2.2 06/23/2000 with version: MH 6.8.4 #1[UCI] To: questions@freebsd.org Cc: hackers@freebsd.org Subject: Forwarding broadcast packets Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Nov 2000 10:23:16 +0000 From: Chris Stenton <jacs@gnome.co.uk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wish to forward broadcast packets from one subnet to another via a FreeBSD box. Both subnets are on the same Ethernet interface. Is this possible? Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 15 3:23:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-206-90-77.dsl.snfc21.pacbell.net [63.206.90.77]) by hub.freebsd.org (Postfix) with ESMTP id E849737B4CF for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Nov 2000 03:23:26 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAFBToF02993; Wed, 15 Nov 2000 03:29:50 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011151129.eAFBToF02993@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Richard Hodges <rh@matriplex.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: page fault question In-reply-to: Your message of "Tue, 14 Nov 2000 10:58:30 PST." <Pine.BSF.4.10.10011141036500.38382-100000@mail.matriplex.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Nov 2000 03:29:50 -0800 From: Mike Smith <msmith@freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have been having a great time :-) debugging a device driver, > and have run into a really fun way to panic. With one type > of traffic, [something] happens and the kernel drops into > DDB, just the way I want. 8) > Well, actually DDB seems to get trapped in some kind of loop > that spews messages faster than a human can read them. When > I finally got a piece of a clue, I booted with serial console > and captured the following (also an endless loop): > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x8 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc014ed6b > stack pointer = 0x10:0xc02b1360 > frame pointer = 0x10:0xc02b1388 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = Idle > interrupt mask = net tty bio cam > kernel: type 12 trap, code=0 > Stopped at > > The PC seems to have died in the DDB, that's odd (or maybe not?) > ts7# nm /kernel | grep c014ed > c014ed38 T linker_ddb_search_symbol > c014edbc T linker_ddb_symbol_values This is pretty normal; ddb is a little fragile sometimes. You want to go back and look at the very first trap; it will probably be different and will be the *real* trap. All the rest are just ddb exploding. > Now looking back at the panic message, it looks like the stack has > pushed into the "frame pointer". Is this an actual problem, or > just some side effect of the page fault? The frame pointer is a pointer into the stack, so no, it's not a problem. > Should I start spending my time looking for kernel stack hogs in > the device driver? I can very easily add code to log ESP & EBP; > would that be productive? Typically stack overruns lead to double faults (because there's no stack on which to handle the fault) and a spontaneous reboot. This just sounds like there's something about your first trap that kills DDB (eg. an invalid instruction pointer, etc.) > Is there a maximum size for a softc? Maybe I'm accidentally ignoring > some "code of the west" and am getting punished for it? (It wouldn't > be the first time). Softc structures should never be allocated on the stack, they're malloc'ed by the newbus infrastructure so you should be OK there. Hope this helps; let us know if the first trap isn't any more illuminating. You might also try using remote gdb instead of ddb. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 15 4:58: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dialup.ptt.ru (dialup.ptt.ru [195.34.0.100]) by hub.freebsd.org (Postfix) with SMTP id F125837B4C5 for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Nov 2000 04:58:05 -0800 (PST) Received: (qmail 6007 invoked from network); 15 Nov 2000 13:02:08 -0000 Received: from unknown (HELO 195.34.10.160) (@195.34.10.160) by dialup.ptt.ru with SMTP; 15 Nov 2000 13:02:08 -0000 Date: Wed, 15 Nov 2000 16:02:28 +0300 From: hellman <sec@artofit.com> X-Mailer: The Bat! (v1.47 Halloween Edition) Personal Reply-To: hellman <sec@artofit.com> X-Priority: 3 (Normal) Message-ID: <14711511562.20001115160228@artofit.com> To: freebsd-hackers@FreeBSD.ORG Subject: porting from old to new one 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 Hello, How can i port all content of my server to new one ? On a new server i have new hdd... I want to port kernel,all packages installed and so so so... What is a correct answer for this? Unix-administrator mailto: hellman@freebsd.sh < /etc/master.passwd -----BEGIN PGP PUBLIC KEY BLOCK----- mQGiBDk2mmwRBADZ35CdgG9sFpIAWW/0z4D+uJc9I6k3CVa6P5XNwk3SQ1UyVkxV sZiraUNpuUoXRDxxLCo5k9/ZsY0YJ7Cv/Yd/zkxz2rbacHZGX7Mq907Rcls7egQx sHTyCCKlOAFlBFzg6wyOlkg9jGf88nhojfqkljN65m5u7o6SG5hi5qR8JQCg/5Qz c+gSu9Mr9Rg9X54V0/ho8BkD/R7t6g+q5DNhTyxl0QyUJXL2OJAYhaujFPJpjgNC VkALk8fK2O0Li5vD7nY/yAitEIlous5L75YKPQxxRvDd8rBBecCigkgEcQjpiHB7 PEjNRCWfM1Jsv05jWjTeAwoYtsJTulZv1zxvt5Z+D3qPMAFKbVth0jy+KbhrNzvQ ULAAA/9N/rWTi+5C3t3dv0PxxxPpixy8wAfQLweog9DLkrBVODTAzi7z/+cEP4je kmEqr4lmL6eWqW5sc2Y67loHp/K4VsoX2kKgVK1UkOAX0Nm0STwWO8hrSIue1Dbe MnYV+hQkyxc/7Ll1f7+ei/FZCdz9cjQRcLIG2VU16My7deRWDrQeSGVsbF9tYW4g PGhlbGxtYW5AYXN0cmF0ZWwucnU+iQBOBBARAgAOBQI5NppsBAsDAgECGQEACgkQ V1wXLAwYCJ3oQwCdHpA5THKyWifi0XODfOYkaoqMZq8AoMo+nPGRndrvgR+k1ar2 UYJDZ6pPuQINBDk2mm0QCAD2Qle3CH8IF3KiutapQvMF6PlTETlPtvFuuUs4INoB p1ajFOmPQFXz0AfGy0OplK33TGSGSfgMg71l6RfUodNQ+PVZX9x2Uk89PY3bzpnh V5JZzf24rnRPxfx2vIPFRzBhznzJZv8V+bv9kV7HAarTW56NoKVyOtQa8L9GAFgr 5fSI/VhOSdvNILSd5JEHNmszbDgNRR0PfIizHHxbLY7288kjwEPwpVsYjY67VYy4 XTjTNP18F1dDox0YbN4zISy1Kv884bEpQBgRjXyEpwpy1obEAxnIByl6ypUM2Zaf q9AKUJsCRtMIPWakXUGfnHy9iUsiGSa6q6Jew1XpMgs7AAICCACZsqA5WqknThTy iW1yQyzsMOvPp72HW4Mup+qfuGUcCQQ+WqDGLMcj42Me1Zk3atVEcjWxMCgbRWPc DMeoXt/B+/lsaZL207a58qKTP7TChGaDb5yzF2M/3vGI29PtTiyRqwljVdLtFx11 SJkyyIneSGHSbeM9m57Yt6AFxm+nhYLcto8bhAAPPNJmrj45Iyj7DA6X4GEp6BxC Vs1d7tdl8Dfg3VxtcjbN7QfE1wuxl6C5zzMpl0Z6VNAU5Zg8oQy1w1zFzaq/WrQp dweLAcgRg/Ej3DviDfz/2YamvXElcee+8vT7r8cCVwZLSAJ+EkrM3JZ6fNvGJH6I 3sjKoYagiQBGBBgRAgAGBQI5NpptAAoJEFdcFywMGAidwScAnj6XEfh7MkLCN8CM 7k7mm8UHd5WeAJ4+XVxbn35j6iZcEct4wQTaylNftw== =TaEU -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 15 6:17:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (pool14-tch-1.Sofia.0rbitel.net [212.95.170.14]) by hub.freebsd.org (Postfix) with SMTP id 407C037B4CF for <freebsd-hackers@freebsd.org>; Wed, 15 Nov 2000 06:17:40 -0800 (PST) Received: (qmail 12765 invoked by uid 1000); 15 Nov 2000 14:13:16 -0000 Date: Wed, 15 Nov 2000 16:13:16 +0200 From: Peter Pentchev <roam@orbitel.bg> To: freebsd-hackers@freebsd.org Subject: changing a running process's credentials Message-ID: <20001115161316.C309@ringworld.oblivion.bg> Mail-Followup-To: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All right, feel free to flame me a LOT for what follows :) There are situations (at least I could think of some :) where it is necessary to change a running process's credentials. I'm thinking specifically of the effective UID and GID, but I might have to tinker with the real and saved UID's, too. As far as I can see, FreeBSD (nor any other Unix system I'm aware of) does not provide a way to do this (short of writing to /dev/kmem ;). If a new syscall should be implemented to this end, would it be enough to change a struct proc's p_cred member, its pc_ucred and such, or would that raise hell all over the process table? I see the comments mentioning 'possibly shared' credentials - does this mean that I can inadvertently change the credentials of a whole process children/siblings tree? That does not sound too good - how do I go about taking a single process's credentials out - just allocate a new pcred/ucred structure? And yes, I'm quite aware of the security implications of something like that.. let's just say I like playing with fire in a controlled environment :) (famous last words..) G'luck, Peter -- If the meanings of 'true' and 'false' were switched, then this sentence wouldn't be false. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 15 6:28:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web.cs.ndsu.nodak.edu (web.cs.ndsu.NoDak.edu [134.129.125.7]) by hub.freebsd.org (Postfix) with ESMTP id 14B8137B4CF; Wed, 15 Nov 2000 06:28:46 -0800 (PST) Received: (from tinguely@localhost) by web.cs.ndsu.nodak.edu (8.9.3/8.9.3) id IAA28388; Wed, 15 Nov 2000 08:28:41 -0600 (CST) (envelope-from tinguely) Date: Wed, 15 Nov 2000 08:28:41 -0600 (CST) From: mark tinguely <tinguely@web.cs.ndsu.nodak.edu> Message-Id: <200011151428.IAA28388@web.cs.ndsu.nodak.edu> To: jacs@gnome.co.uk, questions@FreeBSD.ORG Subject: Re: Forwarding broadcast packets Cc: hackers@FreeBSD.ORG In-Reply-To: <200011151023.eAFANIN01084@hawk.gnome.co.uk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I wish to forward broadcast packets from one subnet to another via a FreeBSD > box. > Both subnets are on the same Ethernet interface. Is this possible? You should not do this in a routed environment, but is required in a bidged enviroment. the kernel bridge(4) support should allow you to do this, see the man page and the network Handbook web pages on how to set up bridging. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 15 7: 6:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from csunb0.leeds.ac.uk (csunb0.leeds.ac.uk [129.11.144.2]) by hub.freebsd.org (Postfix) with SMTP id 9B78837B65F for <freebsd-hackers@FreeBSD.org>; Wed, 15 Nov 2000 07:06:46 -0800 (PST) Received: from cslin.leeds.ac.uk (csunc0.leeds.ac.uk [129.11.144.3]) by csunb0.leeds.ac.uk (8.6.12/8.6.12) with ESMTP id OAA27624; Wed, 15 Nov 2000 14:55:05 GMT Received: from cslin027.leeds.ac.uk (cslin027 [129.11.146.27]) by cslin.leeds.ac.uk (8.9.3+Sun/) with ESMTP id OAA09579; Wed, 15 Nov 2000 14:55:14 GMT Date: Wed, 15 Nov 2000 14:55:04 +0000 From: Ben Smithurst <csxbcs@comp.leeds.ac.uk> To: Paonia Ezrine <paonia@home.welcomehome.org> Cc: Greg Lehey <grog@lemis.com>, freebsd-hackers@FreeBSD.org Subject: Re: looking for kernel hacking info Message-ID: <20001115145503.A2390@comp.leeds.ac.uk> References: <20001115094139.C39755@wantadilla.lemis.com> <200011150214.VAA27289@home.welcomehome.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200011150214.VAA27289@home.welcomehome.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Paonia Ezrine wrote: >> The system calls are described in section 2 of the manual. > > thanks. do you mean handbook? No, he means the manual. "man 2 intro" to get an introduction, "man 2 read" for a particular system call, etc. -- Ben Smithurst / csxbcs@comp.leeds.ac.uk / ben@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 15 8:47:29 2000 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 6E1B537B4C5 for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Nov 2000 08:47:26 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAFGlMN20617; Wed, 15 Nov 2000 08:47:22 -0800 (PST) Date: Wed, 15 Nov 2000 08:47:22 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: Peter Pentchev <roam@orbitel.bg> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: changing a running process's credentials Message-ID: <20001115084722.I29448@fw.wintelcom.net> References: <20001115161316.C309@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20001115161316.C309@ringworld.oblivion.bg>; from roam@orbitel.bg on Wed, Nov 15, 2000 at 04:13:16PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Peter Pentchev <roam@orbitel.bg> [001115 06:19] wrote: > All right, feel free to flame me a LOT for what follows :) No need for that. (yet) :-) > There are situations (at least I could think of some :) where it is necessary > to change a running process's credentials. I'm thinking specifically of the > effective UID and GID, but I might have to tinker with the real and saved > UID's, too. Well there's setuid for you. > As far as I can see, FreeBSD (nor any other Unix system I'm aware of) does not > provide a way to do this (short of writing to /dev/kmem ;). If a new syscall > should be implemented to this end, would it be enough to change a struct > proc's p_cred member, its pc_ucred and such, or would that raise hell all over > the process table? I see the comments mentioning 'possibly shared' > credentials - does this mean that I can inadvertently change the credentials > of a whole process children/siblings tree? That does not sound too good - > how do I go about taking a single process's credentials out - just allocate > a new pcred/ucred structure? Struct ucred is read-only, that would mean that strange things may happen, fortunatly at the moment most access control checks are only done at file open/socket bind time, so that if your cred changes you should still have access to it. > And yes, I'm quite aware of the security implications of something like > that.. let's just say I like playing with fire in a controlled environment :) > (famous last words..) Well there wouldn't be any security implications if done right... What comes to mind is using the cmsg stuff that's normally used to pass file descriptors and authentication information to pass the ability to setuid over to another application over a unix domain pipe. The recieving process would read using recvmsg determine if the passed uid is 'ok' (the kernel would hold it in the proc struct in a temporary), if it 'wanted' this uid it could then call some variation of setuid to switch to this recieved uid. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 15 9: 2: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (pool237-tch-1.Sofia.0rbitel.net [212.95.170.237]) by hub.freebsd.org (Postfix) with SMTP id C037937B4C5 for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Nov 2000 09:02:00 -0800 (PST) Received: (qmail 14273 invoked by uid 1000); 15 Nov 2000 17:01:36 -0000 Date: Wed, 15 Nov 2000 19:01:35 +0200 From: Peter Pentchev <roam@orbitel.bg> To: Alfred Perlstein <bright@wintelcom.net> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: changing a running process's credentials Message-ID: <20001115190135.E309@ringworld.oblivion.bg> Mail-Followup-To: Alfred Perlstein <bright@wintelcom.net>, freebsd-hackers@FreeBSD.ORG References: <20001115161316.C309@ringworld.oblivion.bg> <20001115084722.I29448@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001115084722.I29448@fw.wintelcom.net>; from bright@wintelcom.net on Wed, Nov 15, 2000 at 08:47:22AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 15, 2000 at 08:47:22AM -0800, Alfred Perlstein wrote: > * Peter Pentchev <roam@orbitel.bg> [001115 06:19] wrote: > > All right, feel free to flame me a LOT for what follows :) > > No need for that. (yet) :-) ..possibly because I did not make my intentions clear enough :) > > There are situations (at least I could think of some :) where it is necessary > > to change a running process's credentials. I'm thinking specifically of the > > effective UID and GID, but I might have to tinker with the real and saved > > UID's, too. > > Well there's setuid for you. Hmm.. I've also received two private mails so far, pointing me to setuid(). The problem is, I want to force a new UID on *another* process without its knowledge. setuid() only works on the process invoking it, so both the 'force' and the 'without its knowledge' part fall by the wayside :( > > > As far as I can see, FreeBSD (nor any other Unix system I'm aware of) does not > > provide a way to do this (short of writing to /dev/kmem ;). If a new syscall > > should be implemented to this end, would it be enough to change a struct > > proc's p_cred member, its pc_ucred and such, or would that raise hell all over > > the process table? I see the comments mentioning 'possibly shared' > > credentials - does this mean that I can inadvertently change the credentials > > of a whole process children/siblings tree? That does not sound too good - > > how do I go about taking a single process's credentials out - just allocate > > a new pcred/ucred structure? > > Struct ucred is read-only, that would mean that strange things may > happen, fortunatly at the moment most access control checks are > only done at file open/socket bind time, so that if your cred > changes you should still have access to it. > > > And yes, I'm quite aware of the security implications of something like > > that.. let's just say I like playing with fire in a controlled environment :) > > (famous last words..) > > Well there wouldn't be any security implications if done right... The security implications I meant have to do with the ability to provide either a tool or a sysctl to change the uid of any running process on the system - that would have to include stringent controls on exactly who and why uses this tool/sysctl. I have some ideas about this, but they need some more grinding before they're ready to be tossed at the world for discussion (and dissing ;) > What comes to mind is using the cmsg stuff that's normally used to > pass file descriptors and authentication information to pass the > ability to setuid over to another application over a unix domain > pipe. The recieving process would read using recvmsg determine if > the passed uid is 'ok' (the kernel would hold it in the proc struct > in a temporary), if it 'wanted' this uid it could then call some > variation of setuid to switch to this recieved uid. Yeah; problem is, as I said above, I do not want the receiving process to do anything special - just to wake up with a shiny new uid (this would probably surprise the hell out of most programs, but oh well :) G'luck, Peter -- If I had finished this sentence, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 15 9: 9:38 2000 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 96C0037B4E5 for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Nov 2000 09:09:35 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAFH9Ye00983 for freebsd-hackers@FreeBSD.ORG; Wed, 15 Nov 2000 09:09:34 -0800 (PST) Date: Wed, 15 Nov 2000 09:09:34 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: freebsd-hackers@FreeBSD.ORG Subject: Re: changing a running process's credentials Message-ID: <20001115090934.A830@fw.wintelcom.net> References: <20001115161316.C309@ringworld.oblivion.bg> <20001115084722.I29448@fw.wintelcom.net> <20001115190135.E309@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001115190135.E309@ringworld.oblivion.bg>; from roam@orbitel.bg on Wed, Nov 15, 2000 at 07:01:35PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Peter Pentchev <roam@orbitel.bg> [001115 09:02] wrote: > > > > Well there's setuid for you. > > Hmm.. I've also received two private mails so far, pointing me to setuid(). > The problem is, I want to force a new UID on *another* process without > its knowledge. setuid() only works on the process invoking it, so > both the 'force' and the 'without its knowledge' part fall by the wayside :( > > > What comes to mind is using the cmsg stuff that's normally used to > > pass file descriptors and authentication information to pass the > > ability to setuid over to another application over a unix domain > > pipe. The recieving process would read using recvmsg determine if > > the passed uid is 'ok' (the kernel would hold it in the proc struct > > in a temporary), if it 'wanted' this uid it could then call some > > variation of setuid to switch to this recieved uid. > > Yeah; problem is, as I said above, I do not want the receiving process > to do anything special - just to wake up with a shiny new uid (this > would probably surprise the hell out of most programs, but oh well :) Unless this syscall was restricted to root, or a small subset of uid's it would cause some severe security issues from my point of view. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 15 9:12:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id C72B637B4CF for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Nov 2000 09:12:10 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAFHC9R17671; Wed, 15 Nov 2000 10:12: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 KAA56732; Wed, 15 Nov 2000 10:12:09 -0700 (MST) Message-Id: <200011151712.KAA56732@harmony.village.org> To: Peter Pentchev <roam@orbitel.bg> Subject: Re: changing a running process's credentials Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 15 Nov 2000 16:13:16 +0200." <20001115161316.C309@ringworld.oblivion.bg> References: <20001115161316.C309@ringworld.oblivion.bg> Date: Wed, 15 Nov 2000 10:12:09 -0700 From: Warner Losh <imp@village.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001115161316.C309@ringworld.oblivion.bg> Peter Pentchev writes: : There are situations (at least I could think of some :) where it is necessary : to change a running process's credentials. I'm thinking specifically of the : effective UID and GID, but I might have to tinker with the real and saved : UID's, too. setuid doesn't work for you? 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 15 9:15:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 742C537B4E5 for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Nov 2000 09:15:54 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAFHFpR17686; Wed, 15 Nov 2000 10:15:51 -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 KAA56762; Wed, 15 Nov 2000 10:15:51 -0700 (MST) Message-Id: <200011151715.KAA56762@harmony.village.org> To: Peter Pentchev <roam@orbitel.bg> Subject: Re: changing a running process's credentials Cc: Alfred Perlstein <bright@wintelcom.net>, freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 15 Nov 2000 19:01:35 +0200." <20001115190135.E309@ringworld.oblivion.bg> References: <20001115190135.E309@ringworld.oblivion.bg> <20001115161316.C309@ringworld.oblivion.bg> <20001115084722.I29448@fw.wintelcom.net> Date: Wed, 15 Nov 2000 10:15:51 -0700 From: Warner Losh <imp@village.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001115190135.E309@ringworld.oblivion.bg> Peter Pentchev writes: : Hmm.. I've also received two private mails so far, pointing me to setuid(). : The problem is, I want to force a new UID on *another* process without : its knowledge. setuid() only works on the process invoking it, so : both the 'force' and the 'without its knowledge' part fall by the wayside :( I think the reaction to this by the security officer team would be a) extreme and b) negative. The security implications are huge. : The security implications I meant have to do with the ability to provide : either a tool or a sysctl to change the uid of any running process : on the system - that would have to include stringent controls on exactly : who and why uses this tool/sysctl. I have some ideas about this, : but they need some more grinding before they're ready to be tossed : at the world for discussion (and dissing ;) I'd make it a full syscall, not just a sysctl. I'd also make sure that only root and no body else could use it. Maybe I should back up a step and ask what it is you are trying to accomplish here. 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 15 9:16:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id B0BB837B479 for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Nov 2000 09:16:30 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAFHGTR17695; Wed, 15 Nov 2000 10:16:29 -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 KAA56789; Wed, 15 Nov 2000 10:16:29 -0700 (MST) Message-Id: <200011151716.KAA56789@harmony.village.org> To: Alfred Perlstein <bright@wintelcom.net> Subject: Re: changing a running process's credentials Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 15 Nov 2000 09:09:34 PST." <20001115090934.A830@fw.wintelcom.net> References: <20001115090934.A830@fw.wintelcom.net> <20001115161316.C309@ringworld.oblivion.bg> <20001115084722.I29448@fw.wintelcom.net> <20001115190135.E309@ringworld.oblivion.bg> Date: Wed, 15 Nov 2000 10:16:29 -0700 From: Warner Losh <imp@village.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001115090934.A830@fw.wintelcom.net> Alfred Perlstein writes: : Unless this syscall was restricted to root, or a small subset of : uid's it would cause some severe security issues from my point : of view. Even the small subset of uids would be highly suspect. 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 15 9:19:26 2000 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 19D1037B4D7 for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Nov 2000 09:19:23 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAFHJLk01385; Wed, 15 Nov 2000 09:19:21 -0800 (PST) Date: Wed, 15 Nov 2000 09:19:21 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: Warner Losh <imp@village.org> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: changing a running process's credentials Message-ID: <20001115091920.D830@fw.wintelcom.net> References: <20001115090934.A830@fw.wintelcom.net> <20001115161316.C309@ringworld.oblivion.bg> <20001115084722.I29448@fw.wintelcom.net> <20001115190135.E309@ringworld.oblivion.bg> <20001115090934.A830@fw.wintelcom.net> <200011151716.KAA56789@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200011151716.KAA56789@harmony.village.org>; from imp@village.org on Wed, Nov 15, 2000 at 10:16:29AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Warner Losh <imp@village.org> [001115 09:16] wrote: > In message <20001115090934.A830@fw.wintelcom.net> Alfred Perlstein writes: > : Unless this syscall was restricted to root, or a small subset of > : uid's it would cause some severe security issues from my point > : of view. > > Even the small subset of uids would be highly suspect. Setable via a syscall/sysctl only by root. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 15 9:31:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (Postfix) with ESMTP id 93D7237B4E5 for <hackers@FreeBSD.ORG>; Wed, 15 Nov 2000 09:31:19 -0800 (PST) Received: (from daemon@localhost) by smtp01.primenet.com (8.9.3/8.9.3) id KAA13533; Wed, 15 Nov 2000 10:30:17 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp01.primenet.com, id smtpdAAAl9ayrA; Wed Nov 15 10:30:08 2000 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id KAA12666; Wed, 15 Nov 2000 10:30:54 -0700 (MST) From: Terry Lambert <tlambert@primenet.com> Message-Id: <200011151730.KAA12666@usr01.primenet.com> Subject: Re: "iowait" CPU state To: riel@conectiva.com.br (Rik van Riel) Date: Wed, 15 Nov 2000 17:30:54 +0000 (GMT) Cc: tlambert@primenet.com (Terry Lambert), float@firedrake.org (void), hackers@FreeBSD.ORG In-Reply-To: <Pine.LNX.4.21.0011141720170.25493-100000@duckman.distro.conectiva> from "Rik van Riel" at Nov 14, 2000 05:21:09 PM X-Mailer: ELM [version 2.5 PL2] 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 > > > Thank you! This gets the me disk %busy, which is one of the things I > > > was looking for. Now, can anyone tell me how to tell what percentage of > > > processor time is being spent waiting for disk I/O to complete? > > > > Uh, none? > > > > If there is disk I/O pending, the processor just runs a > > different process... am I missing your question? > > I guess it might be useful to see the difference between > "true" idle time and time the system couldn't do anything > useful because it was blocked on the disk (but /should/ > have done something useful...). You mean because the programmer didn't interleave their I/O, and wrote to a threads interface, or some other interface that's prone to subsystem stalling, instead? I think you get what you pay for, when it comes to engineering skill. It's easy to write code that stalls, and then expect to be able to throw clock-doubled hardware at it to "fix it". I'm always tempted to set up a company where the main engineers have a centralized batch compile server, so as to not slow down developement, but requiring that they run no better than a 386SX/16 on their desktop. If they are good, I'd give them a full 8M of real RAM, instead of 4M. Modern bloat-ware really pisses me off; I built the bind library the other day: the frigging thing was 4M, unstripped. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 15 11: 7:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from brutus.conectiva.com.br (brutus.conectiva.com.br [200.250.58.146]) by hub.freebsd.org (Postfix) with ESMTP id 7FBF237B479 for <hackers@FreeBSD.ORG>; Wed, 15 Nov 2000 11:07:39 -0800 (PST) Received: from localhost (riel@localhost) by brutus.conectiva.com.br (8.11.1/8.11.1) with ESMTP id eAFJ72c08856; Wed, 15 Nov 2000 17:07:02 -0200 X-Authentication-Warning: duckman.distro.conectiva: riel owned process doing -bs Date: Wed, 15 Nov 2000 17:07:02 -0200 (BRDT) From: Rik van Riel <riel@conectiva.com.br> X-Sender: riel@duckman.distro.conectiva To: Terry Lambert <tlambert@primenet.com> Cc: void <float@firedrake.org>, hackers@FreeBSD.ORG Subject: Re: "iowait" CPU state In-Reply-To: <200011151730.KAA12666@usr01.primenet.com> Message-ID: <Pine.LNX.4.21.0011151704110.5584-100000@duckman.distro.conectiva> 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, 15 Nov 2000, Terry Lambert wrote: > > > > Thank you! This gets the me disk %busy, which is one of the things I > > > > was looking for. Now, can anyone tell me how to tell what percentage of > > > > processor time is being spent waiting for disk I/O to complete? > > > > > > Uh, none? > > > > > > If there is disk I/O pending, the processor just runs a > > > different process... am I missing your question? > > > > I guess it might be useful to see the difference between > > "true" idle time and time the system couldn't do anything > > useful because it was blocked on the disk (but /should/ > > have done something useful...). > > You mean because the programmer didn't interleave their I/O, > and wrote to a threads interface, or some other interface > that's prone to subsystem stalling, instead? Interleaving IO only makes sense when you have tons of parallelisable jobs. If you have one big serial job this doesn't buy you anything... Yes, you can use a separate thread to queue IO in advance, but in this case it might just be useful to have the %iowait statistic so you know how much work to queue in advance. Then again, this may be a bad example. I can't quite put my finger on it, but somehow I have the idea that the %iowait may be a useful statistic to keep... > Modern bloat-ware really pisses me off; I built the bind > library the other day: the frigging thing was 4M, unstripped. How does this affect the (non?-)usefullness of the %iowait statistic? regards, Rik -- "What you're running that piece of shit Gnome?!?!" -- Miguel de Icaza, UKUUG 2000 http://www.conectiva.com/ http://www.surriel.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 15 12:41:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from west.lustig.com (west.lustig.com [209.157.26.130]) by hub.freebsd.org (Postfix) with SMTP id 1534C37B4C5 for <hackers@FreeBSD.ORG>; Wed, 15 Nov 2000 12:41:31 -0800 (PST) Received: (qmail 16669 invoked from network); 15 Nov 2000 20:41:30 -0000 Received: from lustig.ne.mediaone.net (HELO devious.lustig.com) (@24.91.125.166) by west.lustig.com with SMTP; 15 Nov 2000 20:41:30 -0000 Received: (qmail 12981 invoked by uid 1001); 15 Nov 2000 20:41:28 -0000 Message-ID: <20001115204128.12980.qmail@devious.lustig.com> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach_patches v148.2) In-Reply-To: <200011151730.KAA12666@usr01.primenet.com> X-Nextstep-Mailer: Mail 4.2mach_patches [i386] (Enhance 2.2p2) Received: by NeXT.Mailer (1.148.2.RR) From: Barry Lustig <barry@lustig.com> Date: Wed, 15 Nov 2000 15:41:27 -0500 To: Terry Lambert <tlambert@primenet.com> Subject: Re: "iowait" CPU state Cc: hackers@FreeBSD.ORG Reply-To: barry@Lustig.COM References: <200011151730.KAA12666@usr01.primenet.com> X-Organizations: Barry Lustig & Associates, Inc. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 15 Nov 2000, Terry Lambert wrote: > > I'm always tempted to set up a company where the main > engineers have a centralized batch compile server, so as to > not slow down developement, but requiring that they run no > better than a 386SX/16 on their desktop. If they are good, > I'd give them a full 8M of real RAM, instead of 4M. > That's what they did at NeXT. The engineers got machines with slower processors and small amounts of RAM. It was designed to encourage them to produce fast efficient code. barry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 15 13:48:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ebola.biohz.net (ebola.biohz.net [206.80.1.35]) by hub.freebsd.org (Postfix) with ESMTP id D3F7C37B4C5 for <hackers@FreeBSD.ORG>; Wed, 15 Nov 2000 13:48:50 -0800 (PST) Received: from flu (localhost [127.0.0.1]) by ebola.biohz.net (Postfix) with SMTP id 224FC3A3CB; Wed, 15 Nov 2000 13:48:50 -0800 (PST) Message-ID: <000701c04f4d$d6e9da60$0402010a@biohz.net> From: "Renaud Waldura" <renaud@waldura.com> To: "Brian Somers" <brian@Awfulhak.org> Cc: <hackers@FreeBSD.ORG> References: <200011150143.eAF1hQF04103@hak.lan.Awfulhak.org> Subject: Re: PPPoE w/ nat auto fragmentation hack? (use tcpmssd port) Date: Wed, 15 Nov 2000 13:48:49 -0800 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.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maybe I'm just being boneheaded, but... > ! sudo ipfw add 40000 divert 12345 all from any to any via INTERFACE > ! sudo /usr/local/bin/tcpmssd -p 12345 -i INTERFACE I was under the (tested & confirmed) impression that programs executed by ppp are run under uid 0. Eg. I don't use "sudo" but the ipfw rule is added anyway, and tcpmssd is run as root. But maybe a sudo environment brings something else? That could explain a lot right there. --Renaud ----- Original Message ----- From: Brian Somers <brian@Awfulhak.org> To: FengYue <fengyue@bluerose.windmoon.nu> Cc: Renaud Waldura <renaud@waldura.com>; Ruslan Ermilov <ru@FreeBSD.ORG>; <hackers@FreeBSD.ORG>; <brian@Awfulhak.org> Sent: Tuesday, November 14, 2000 5:43 PM Subject: Re: PPPoE w/ nat auto fragmentation hack? (use tcpmssd port) > > > > On Tue, 14 Nov 2000, Renaud Waldura wrote: > > > > ->Dear hackers, > > -> > > ->> What exactly does not work? > > ->> What does the option -l do? > > -> > > ->When launched automatically by ppp, tcpmssd doesn't get any of the packets > > ->and is useless. When I start it manually from the command line, it works > > ->fine. > > -> > > ->I realize this isn't much in the way of helpful debugging information, and > > ->was hoping to further define this: I implemented that "-l" option to log all > > ->the packets processed by tcpmssd. I'm not even sure this bug applies to > > ->anybody else, which is why I did not seek help or publicize it until now. > > -> > > ->Anyway, I haven't been able to figure out what the problem is (and am > > ->lacking time now). The best I have is this: when launched by ppp, tcpmssd > > ->never seems to return from the main select() call. Ruslan, if you feel like > > ->an account on the machine where I'm using this could help, just let me know > > ->and I will gladly give you one. > > > > It does not work for me either. Start the script in rc.local rather than > > ppp.linkup works fine. > > What are you doing in ppp.linkup ? > > When I add this: > > ! sudo ipfw add 40000 divert 12345 all from any to any via INTERFACE > ! sudo /usr/local/bin/tcpmssd -p 12345 -i INTERFACE > > everything seems to work ok.... > > -- > Brian <brian@Awfulhak.org> <brian@[uk.]FreeBSD.org> > <http://www.Awfulhak.org> <brian@[uk.]OpenBSD.org> > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 15 14:56: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id E286337B479 for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Nov 2000 14:56:05 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id eAFMvH123857; Wed, 15 Nov 2000 14:57:17 -0800 (PST) (envelope-from kris) Date: Wed, 15 Nov 2000 14:57:17 -0800 From: Kris Kennaway <kris@FreeBSD.ORG> To: hellman <sec@artofit.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: porting from old to new one Message-ID: <20001115145717.A23764@citusc17.usc.edu> References: <14711511562.20001115160228@artofit.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="T4sUOijqQbZv57TR" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14711511562.20001115160228@artofit.com>; from sec@artofit.com on Wed, Nov 15, 2000 at 04:02:28PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 15, 2000 at 04:02:28PM +0300, hellman wrote: > Hello, >=20 > How can i port all content of my server to new one ? >=20 > On a new server i have new hdd... >=20 > I want to port kernel,all packages installed and so so so... >=20 > What is a correct answer for this? tar and netcat or a NFS mount. Kris --T4sUOijqQbZv57TR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjoTFM0ACgkQWry0BWjoQKVEgwCfZg1JgGld5ovpuBxWmv3Vux4a 0WgAoNBZXCIZ9jzR6Bac4cNF3MxXHs7d =HAZ6 -----END PGP SIGNATURE----- --T4sUOijqQbZv57TR-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 15 15:22:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from luxren2.boostworks.com (luxren2.boostworks.com [194.167.81.214]) by hub.freebsd.org (Postfix) with ESMTP id 4648937B4D7 for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Nov 2000 15:22:26 -0800 (PST) Received: from boostworks.com (root@oldrn.luxdev.boostworks.com [192.168.1.99]) by luxren2.boostworks.com (8.9.1/8.9.1) with ESMTP id AAA18010 for <freebsd-hackers@FreeBSD.ORG>; Thu, 16 Nov 2000 00:22:16 +0100 (CET) Message-Id: <200011152322.AAA18010@luxren2.boostworks.com> Date: Thu, 16 Nov 2000 00:23:27 +0100 (CET) From: Remy Nonnenmacher <remy@boostworks.com> Reply-To: remy@boostworks.com Subject: Any known issue about icmp replies ? To: freebsd-hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, It seems that some Linux distribs are on trouble with icmp replies that get replied (see below). My question is: is there any known issue on FreeBSD getting an icmp reply and responding by another icmp reply ? (Guess not but better be sure). Exemple: 00:10:37.305915 33.85.11.rrcentralflorida.cfl.rr.com > luxufr12.boostworks.com: icmp: echo reply (ttl 43, id 22520) 0000: 45 00 04 14 57 F8 00 00 2B 01 D0 FC 41 21 55 0B E...W...+...A!U. 0010: D4 9B F8 2C 00 00 9C A3 1A 0A 00 00 00 00 00 00 ...,............ 0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0030: 73 6B 69 6C 6C 7A 00 00 00 00 00 00 00 00 00 00 skillz.......... 0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ .. 0400: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0410: 00 00 00 00 ED .... 00:10:37.338329 luxufr12.boostworks.com > 33.85.11.rrcentralflorida.cfl.rr.com: icmp: echo reply (ttl 63, id 1063) 0000: 45 00 04 14 04 27 00 00 3F 01 10 CE D4 9B F8 2C E....'..?......, 0010: 41 21 55 0B 00 00 B6 B1 1A 0B 00 00 00 00 00 00 A!U............. 0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0030: 66 69 63 6B 65 6E 00 00 00 00 00 00 00 00 00 00 ficken.......... 0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ .. 0400: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0410: 00 00 00 00 ED .... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 15 16:34: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 1214E37B4C5 for <hackers@FreeBSD.ORG>; Wed, 15 Nov 2000 16:34:02 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.1/8.11.1) with ESMTP id eAG0WVF23430; Thu, 16 Nov 2000 00:32:31 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.1/8.11.1) with ESMTP id eAG0Ws526758; Thu, 16 Nov 2000 00:32:54 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200011160032.eAG0Ws526758@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Renaud Waldura" <renaud@waldura.com> Cc: "Brian Somers" <brian@Awfulhak.org>, hackers@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: PPPoE w/ nat auto fragmentation hack? (use tcpmssd port) In-Reply-To: Message from "Renaud Waldura" <renaud@waldura.com> of "Wed, 15 Nov 2000 13:48:49 PST." <000701c04f4d$d6e9da60$0402010a@biohz.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 Nov 2000 00:32:54 +0000 From: Brian Somers <brian@Awfulhak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Maybe I'm just being boneheaded, but... > > > ! sudo ipfw add 40000 divert 12345 all from any to any via INTERFACE > > ! sudo /usr/local/bin/tcpmssd -p 12345 -i INTERFACE > > I was under the (tested & confirmed) impression that programs executed by > ppp are run under uid 0. Eg. I don't use "sudo" but the ipfw rule is added > anyway, and tcpmssd is run as root. > > But maybe a sudo environment brings something else? That could explain a lot > right there. > > --Renaud ppp will run programs as the user id that invoked ppp rather than using the effective user id (ie, it runs things as *you*, not *root*). AFAIK, sudo will not muck about with your environment.... A good ``first step'' is to run ! sh -c "/usr/local/bin/tcpmssd -p 12345 -i INTERFACE >/tmp/log 2>&1" so that you can get to see any error messages - ppp redirects I/O to /dev/null by default. -- Brian <brian@Awfulhak.org> <brian@[uk.]FreeBSD.org> <http://www.Awfulhak.org> <brian@[uk.]OpenBSD.org> 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 Wed Nov 15 19:26:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ebola.biohz.net (ebola.biohz.net [206.80.1.35]) by hub.freebsd.org (Postfix) with ESMTP id B9D5437B4C5 for <hackers@FreeBSD.ORG>; Wed, 15 Nov 2000 19:26:26 -0800 (PST) Received: from flu (localhost [127.0.0.1]) by ebola.biohz.net (Postfix) with SMTP id 2805A3A3CB; Wed, 15 Nov 2000 19:26:26 -0800 (PST) Message-ID: <002a01c04f7d$00699680$0402010a@biohz.net> From: "Renaud Waldura" <renaud@waldura.com> To: "Brian Somers" <brian@Awfulhak.org> Cc: <hackers@FreeBSD.ORG> References: <200011160032.eAG0Ws526758@hak.lan.Awfulhak.org> Subject: Re: PPPoE w/ nat auto fragmentation hack? (use tcpmssd port) Date: Wed, 15 Nov 2000 19:26:25 -0800 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.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ppp will run programs as the user id that invoked ppp rather than > using the effective user id (ie, it runs things as *you*, not *root*). Mmm-mmh. In my case, since ppp is started at boot time, the only user that ever invokes it is root, hence the tcpmssd thingy is run as root. As confirmed by the multiple "ps" I ran: euid == ruid == svguid == 0. > A good ``first step'' is to run > ! sh -c "/usr/local/bin/tcpmssd -p 12345 -i INTERFACE >/tmp/log 2>&1" > so that you can get to see any error messages - ppp redirects I/O to Yup, tried that, here's what I get: ******************** start *************** Wed Nov 15 13:30:12 PST 2000 id says: uid=0(root) gid=0(wheel) groups=0(wheel) HOME=/ PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin 01001 divert 1234 tcp from any to any out xmit tun0 setup The rule gets inserted, tcpmssd runs as root, and I feel like a dummy. Any other ideas? Thanks for the help Brian, --Renaud ----- Original Message ----- From: Brian Somers <brian@Awfulhak.org> To: Renaud Waldura <renaud@waldura.com> Cc: Brian Somers <brian@Awfulhak.org>; <hackers@FreeBSD.ORG>; <brian@Awfulhak.org> Sent: Wednesday, November 15, 2000 4:32 PM Subject: Re: PPPoE w/ nat auto fragmentation hack? (use tcpmssd port) > > Maybe I'm just being boneheaded, but... > > > > > ! sudo ipfw add 40000 divert 12345 all from any to any via INTERFACE > > > ! sudo /usr/local/bin/tcpmssd -p 12345 -i INTERFACE > > > > I was under the (tested & confirmed) impression that programs executed by > > ppp are run under uid 0. Eg. I don't use "sudo" but the ipfw rule is added > > anyway, and tcpmssd is run as root. > > > > But maybe a sudo environment brings something else? That could explain a lot > > right there. > > > > --Renaud > > ppp will run programs as the user id that invoked ppp rather than > using the effective user id (ie, it runs things as *you*, not *root*). > > AFAIK, sudo will not muck about with your environment.... > > A good ``first step'' is to run > > ! sh -c "/usr/local/bin/tcpmssd -p 12345 -i INTERFACE >/tmp/log 2>&1" > > so that you can get to see any error messages - ppp redirects I/O to > /dev/null by default. > > -- > Brian <brian@Awfulhak.org> <brian@[uk.]FreeBSD.org> > <http://www.Awfulhak.org> <brian@[uk.]OpenBSD.org> > 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 Wed Nov 15 23:14: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f41.pav1.hotmail.com [64.4.31.41]) by hub.freebsd.org (Postfix) with ESMTP id F11BF37B4E5 for <freebsd-hackers@freebsd.org>; Wed, 15 Nov 2000 23:14:03 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 15 Nov 2000 23:14:03 -0800 Received: from 202.101.165.61 by pv1fd.pav1.hotmail.msn.com with HTTP; Thu, 16 Nov 2000 07:14:03 GMT X-Originating-IP: [202.101.165.61] From: "frank xu" <bsdman@hotmail.com> To: freebsd-hackers@freebsd.org Subject: scheduler activations in FBSD5.0? Date: Thu, 16 Nov 2000 15:14:03 CST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: <F41mcarcR4ZDgC81Tbd00000651@hotmail.com> X-OriginalArrivalTime: 16 Nov 2000 07:14:03.0757 (UTC) FILETIME=[CCE731D0:01C04F9C] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I heard rumor that Thomas E. Anderson's Scheduler Activations theory will be implemented in FreeBSD 5.0 kernel, is it true? Regards, XuYifeng _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 15 23:30: 7 2000 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 0CFDB37B4C5 for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Nov 2000 23:30:06 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAG7U4Q24484; Wed, 15 Nov 2000 23:30:04 -0800 (PST) Date: Wed, 15 Nov 2000 23:30:04 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: frank xu <bsdman@hotmail.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: scheduler activations in FBSD5.0? Message-ID: <20001115233003.Y830@fw.wintelcom.net> References: <F41mcarcR4ZDgC81Tbd00000651@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <F41mcarcR4ZDgC81Tbd00000651@hotmail.com>; from bsdman@hotmail.com on Thu, Nov 16, 2000 at 03:14:03PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * frank xu <bsdman@hotmail.com> [001115 23:15] wrote: > I heard rumor that Thomas E. Anderson's Scheduler Activations theory will > be implemented in FreeBSD 5.0 kernel, is it true? Several people have begun the initial development on it. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 15 23:51:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay1.bcs.zp.ua (bcs-zyx-eth.marka.net.ua [195.248.171.202]) by hub.freebsd.org (Postfix) with ESMTP id 4530537B479 for <hackers@freebsd.org>; Wed, 15 Nov 2000 23:51:23 -0800 (PST) Received: (from eugen@localhost) by relay1.bcs.zp.ua (8.11.0/8.11.0) id eAG7oSO13677; Thu, 16 Nov 2000 09:50:28 +0200 (EET) Date: Thu, 16 Nov 2000 09:50:28 +0200 (EET) Message-Id: <200011160750.eAG7oSO13677@relay1.bcs.zp.ua> From: Eugene Polovnikov <eugen@bcs.zp.ua> To: remy@boostworks.com Cc: hackers@freebsd.org Subject: Re: Any known issue about icmp replies ? X-Newsgroups: bcs.Gated.FreeBSD-Hackers In-Reply-To: <200011152322.AAA18010@luxren2.boostworks.com> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-RELEASE (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are you sure that your system isn't hacked/cracked ? Content of packets look strange for me. In article <200011152322.AAA18010@luxren2.boostworks.com> you wrote: > Hello, > It seems that some Linux distribs are on trouble with icmp replies that > get replied (see below). My question is: is there any known issue on > FreeBSD getting an icmp reply and responding by another icmp reply ? > (Guess not but better be sure). > Exemple: > 00:10:37.305915 33.85.11.rrcentralflorida.cfl.rr.com > luxufr12.boostworks.com: > icmp: echo reply (ttl 43, id 22520) > 0000: 45 00 04 14 57 F8 00 00 2B 01 D0 FC 41 21 55 0B E...W...+...A!U. > 0010: D4 9B F8 2C 00 00 9C A3 1A 0A 00 00 00 00 00 00 ...,............ > 0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 0030: 73 6B 69 6C 6C 7A 00 00 00 00 00 00 00 00 00 00 skillz.......... > 0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > .. > 0400: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 0410: 00 00 00 00 ED .... > 00:10:37.338329 luxufr12.boostworks.com > 33.85.11.rrcentralflorida.cfl.rr.com: > icmp: echo reply (ttl 63, id 1063) > 0000: 45 00 04 14 04 27 00 00 3F 01 10 CE D4 9B F8 2C E....'..?......, > 0010: 41 21 55 0B 00 00 B6 B1 1A 0B 00 00 00 00 00 00 A!U............. > 0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 0030: 66 69 63 6B 65 6E 00 00 00 00 00 00 00 00 00 00 ficken.......... > 0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > .. > 0400: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 0410: 00 00 00 00 ED .... > 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 15 23:57:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-c.mdsn1.wi.home.com [24.183.3.139]) by hub.freebsd.org (Postfix) with ESMTP id 17D4237B4CF for <hackers@freebsd.org>; Wed, 15 Nov 2000 23:57:08 -0800 (PST) Received: (qmail 61758 invoked by uid 1000); 16 Nov 2000 07:57:06 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 16 Nov 2000 07:57:06 -0000 Date: Thu, 16 Nov 2000 01:57:06 -0600 (CST) From: Mike Silbersack <silby@silby.com> To: Eugene Polovnikov <eugen@bcs.zp.ua> Cc: remy@boostworks.com, hackers@freebsd.org Subject: Re: Any known issue about icmp replies ? In-Reply-To: <200011160750.eAG7oSO13677@relay1.bcs.zp.ua> Message-ID: <Pine.BSF.4.21.0011160155550.61756-100000@achilles.silby.com> 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, 16 Nov 2000, Eugene Polovnikov wrote: > Are you sure that your system isn't hacked/cracked ? > Content of packets look strange for me. Yeah, now that you suggested that, I checked - that's Stacheldraht's handiwork. Unplug the box soon, Remy! Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 0:28:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id E1B4437B4CF for <hackers@FreeBSD.ORG>; Thu, 16 Nov 2000 00:28:27 -0800 (PST) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id BAA24022; Thu, 16 Nov 2000 01:26:25 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpdAAAs0aaZU; Thu Nov 16 01:26:16 2000 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id BAA00995; Thu, 16 Nov 2000 01:28:08 -0700 (MST) From: Terry Lambert <tlambert@primenet.com> Message-Id: <200011160828.BAA00995@usr02.primenet.com> Subject: Re: "iowait" CPU state To: riel@conectiva.com.br (Rik van Riel) Date: Thu, 16 Nov 2000 08:28:07 +0000 (GMT) Cc: tlambert@primenet.com (Terry Lambert), float@firedrake.org (void), hackers@FreeBSD.ORG In-Reply-To: <Pine.LNX.4.21.0011151704110.5584-100000@duckman.distro.conectiva> from "Rik van Riel" at Nov 15, 2000 05:07:02 PM X-Mailer: ELM [version 2.5 PL2] 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 > > > I guess it might be useful to see the difference between > > > "true" idle time and time the system couldn't do anything > > > useful because it was blocked on the disk (but /should/ > > > have done something useful...). > > > > You mean because the programmer didn't interleave their I/O, > > and wrote to a threads interface, or some other interface > > that's prone to subsystem stalling, instead? > > Interleaving IO only makes sense when you have tons of > parallelisable jobs. If you have one big serial job this > doesn't buy you anything... Then neither does looking at how it's not running. 8-). > Yes, you can use a separate thread to queue IO in > advance, but in this case it might just be useful to > have the %iowait statistic so you know how much work > to queue in advance. These statistics are only available to priviledged programs and/or programs willing to popen() priviledged programs. > Then again, this may be a bad example. I can't quite > put my finger on it, but somehow I have the idea that > the %iowait may be a useful statistic to keep... It's not there now. > > Modern bloat-ware really pisses me off; I built the bind > > library the other day: the frigging thing was 4M, unstripped. > > How does this affect the (non?-)usefullness of the > %iowait statistic? When you are waiting for I/O in a well written program, it is because there's nothing left to do but wait, which would make the statistic useless. If there's something else you could do, and you're waiting, by definition the program is not well written (well written programs don't waste time for no good reason). In a badly written program, I guess you could argue that a manager could use it to decide who didn't think before they wrote their code, for things like proportioning merit raises or pink slips, based on whether or not someone thought before they wrote their code... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 1:12:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from matrix.42.org (matrix.42.org [194.246.250.200]) by hub.freebsd.org (Postfix) with ESMTP id 883C537B4C5 for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 01:12:55 -0800 (PST) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.5) id KAA14766 (sender <sec>); Thu, 16 Nov 2000 10:12:51 +0100 (CET) Date: Thu, 16 Nov 2000 10:12:50 +0100 From: Stefan `Sec` Zehl <sec@42.org> To: Peter Pentchev <roam@orbitel.bg> Cc: freebsd-hackers@freebsd.org Subject: Re: changing a running process's credentials Message-ID: <20001116101250.A14200@matrix.42.org> References: <20001115161316.C309@ringworld.oblivion.bg> <20001115190135.E309@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20001115190135.E309@ringworld.oblivion.bg>; from roam@orbitel.bg on Wed, Nov 15, 2000 at 06:02:22PM +0100 I-love-doing-this: really X-Modeline: vim:set ts=8 sw=4 smarttab tw=72 si noic notitle: Accept-Languages: de, en X-URL: http://sec.42.org/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 15, 2000 at 06:02:22PM +0100, Peter Pentchev wrote: > On Wed, Nov 15, 2000 at 08:47:22AM -0800, Alfred Perlstein wrote: > > * Peter Pentchev <roam@orbitel.bg> [001115 06:19] wrote: > > > As far as I can see, FreeBSD (nor any other Unix system I'm aware > > > of) does not provide a way to do this (short of writing to > > > /dev/kmem ;). If a new syscall should be implemented to this end, > > > would it be enough to change a struct proc's p_cred member, its > > > pc_ucred and such, or would that raise hell all over the process > > > table? I see the comments mentioning 'possibly shared' > > > credentials - does this mean that I can inadvertently change the > > > credentials of a whole process children/siblings tree? That does > > > not sound too good - how do I go about taking a single process's > > > credentials out - just allocate a new pcred/ucred structure? > > > > Struct ucred is read-only, that would mean that strange things may > > happen, fortunatly at the moment most access control checks are > > only done at file open/socket bind time, so that if your cred > > changes you should still have access to it. > > > > > And yes, I'm quite aware of the security implications of something like > > > that.. let's just say I like playing with fire in a controlled > > > environment :) (famous last words..) > > > > Well there wouldn't be any security implications if done right... > > The security implications I meant have to do with the ability to provide > either a tool or a sysctl to change the uid of any running process > on the system - that would have to include stringent controls on exactly > who and why uses this tool/sysctl. I have some ideas about this, > but they need some more grinding before they're ready to be tossed > at the world for discussion (and dissing ;) A few years ago (Feb-1997 on FreeBSD-2.1.0) i wrote a little proof-of-concept program to show that write access means instant root. It uses stolen parts from the kvm lib and /bin/ps to do it. I ported it to FreeBSD-3.2 a year ago, and it compiles and runs on 4.1 also. I found it really handy when I start to edit a file to which i have no write access. I can promote vi to root, and write the file instead of fiddling around with temp-files ;-) I've put the source at <ftp://ftp.42.org/pub/B/presto/presto-1.1.tar.gz> in case anyone wants it. Of course it will only work as root, as write access to /dev/kmem is needed. Do not make /dev/kmem group or even world writable ;-) If this code is usefull for anyone else, i'd be happy to hear about it ;-) CU, Sec -- My biggest problem was when I screwed up the device driver for my eyelids I couldn't open my eyes to debug them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 2:37:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from distortion.dk (distortion.dk [195.249.147.156]) by hub.freebsd.org (Postfix) with ESMTP id A0CDA37B4C5 for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 02:37:10 -0800 (PST) Received: from petri2000 ([194.192.131.97]) by distortion.dk (8.9.3/8.9.1) with SMTP id LAA86711 for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 11:43:06 +0100 (CET) (envelope-from nicolai@petri.cc) Message-ID: <021501c04fb9$574f9030$6732a8c0@atomic.dk> From: "Nicolai Petri" <nicolai@petri.cc> To: <freebsd-hackers@freebsd.org> Subject: Multithreaded tcp-server or non-blocking ? Date: Thu, 16 Nov 2000 11:38:14 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What's the best approach for a simple web-server(never more the 10 clients) ? Is it using pthread and a thread per connection . Or to make a non-blocking single thread server. Can people show me some simple examples of the 2 techniques ? And what's the pro's and con's for the 2 methods ??? --- Cheers, Nicolai Petri // *If you can't follow the standard, break it (MickeySoft)* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 2:51: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from luxren2.boostworks.com (luxren2.boostworks.com [194.167.81.214]) by hub.freebsd.org (Postfix) with ESMTP id 04DF137B4CF for <hackers@freebsd.org>; Thu, 16 Nov 2000 02:50:48 -0800 (PST) Received: from boostworks.com (root@oldrn.luxdev.boostworks.com [192.168.1.99]) by luxren2.boostworks.com (8.9.1/8.9.1) with ESMTP id LAA20403; Thu, 16 Nov 2000 11:49:33 +0100 (CET) Message-Id: <200011161049.LAA20403@luxren2.boostworks.com> Date: Thu, 16 Nov 2000 11:50:44 +0100 (CET) From: Remy Nonnenmacher <remy@boostworks.com> Reply-To: remy@boostworks.com Subject: Re: Any known issue about icmp replies ? To: silby@silby.com Cc: eugen@bcs.zp.ua, hackers@freebsd.org In-Reply-To: <Pine.BSF.4.21.0011160155550.61756-100000@achilles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16 Nov, Mike Silbersack wrote: > > On Thu, 16 Nov 2000, Eugene Polovnikov wrote: > >> Are you sure that your system isn't hacked/cracked ? >> Content of packets look strange for me. > > Yeah, now that you suggested that, I checked - that's Stacheldraht's > handiwork. > > Unplug the box soon, Remy! > > Mike "Silby" Silbersack > OK. got the reference. I simply dropped any icmp packets to this machine of no importance. It's amazing to find such a breach known for a year and not fixed. Well. I'm getting more and more convinced that L will be the next W$... Thanks. 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 16 3:12: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 51E4E37B479; Thu, 16 Nov 2000 03:11:59 -0800 (PST) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JWLVP2O67Q000Z8V@research.kpn.com>; Thu, 16 Nov 2000 12:11:57 +0100 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id <SKHLHM4V>; Thu, 16 Nov 2000 12:11:56 +0100 Content-return: allowed Date: Thu, 16 Nov 2000 12:11:56 +0100 From: "Koster, K.J." <K.J.Koster@kpn.com> Subject: More detail on Deskpro XL6200 NIC (was: Legacy ethernet cards in FreeBSD) To: "'wpaul@FreeBSD.ORG'" <wpaul@FreeBSD.ORG> Cc: 'FreeBSD Hackers mailing list' <freebsd-hackers@freebsd.org> Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D7A07@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Bill, others, I've been working on getting my Deskpros to use their NIC under 4.2, but no luck. The problem is as follows: I installed 4.0, and the NIC came up under the lnc driver, reports its MAC address and works fine. -- FreeBSD 4.0-RELEASE #0: Mon Mar 20 22:50:22 GMT 2000 root@monster.cdrom.com:/usr/src/sys/compile/GENERIC ... lnc0: <PCNet/PCI Ethernet adapter> port 0x7000-0x701f irq 5 at device 11.0 on pci0 lnc0: supplying EUI64: 00:80:5f:ff:fe:fa:a0:82 lnc0: PCnet-32 VL-Bus address 00:80:5f:fa:a0:82 lnc0: driver is using old-style compatability shims -- In 4.2, the lnc driver still probes and finds the NIC, but does not report finding a MAC address, and the NIC remains dead. -- FreeBSD 4.2-BETA #0: Thu Nov 16 11:03:15 CET 2000 kjkoster@dl6101.research.kpn.com:/usr/obj/usr/src/sys/QUAM ... lnc0: <PCNet/PCI Ethernet adapter> port 0x7000-0x701f irq 5 at device 11.0 on pci0 lnc0: driver is using old-style compatability shims --- Compiling a kernel with the pcn driver does not help. Booting a lnc+pcn kernel causes the behaviour described above, booting a pcn-only kernel makes the NIC show up as an unknown device, vendor 0x1022, device 0x2000. -- pci0: <unknown card> (vendor=0x1022, dev=0x2000) at 11.0 irq 5 -- Looking in the source shows that the pcn driver knows about this vendor/device combination. Booting -v does not show any attempts on pcn's part to take the card into its arms. -- avail memory = 62328832 (60868K bytes) bios32: Bad BIOS32 Service Directory Other BIOS signatures found: ACPI: 00000000 Preloaded elf kernel "kernel" at 0xc0308000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc03080a8. Pentium Pro MTRR support enabled pci_open(1): mode 1 addr port (0x0cf8) is 0x0000a06c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 1 2 3 4 5 6 7 8 9 10 11 [class=020000] [hdr=00] is there (id=20001022) npx0: <math processor> on motherboard npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 1 2 3 4 5 6 7 8 9 10 11 [class=020000] [hdr=00] is there (id=20001022) pcib0: <Intel 82454KX/GX (Orion) host to PCI bridge> on motherboard found-> vendor=0x1022, dev=0x2000, revid=0x02 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=b, irq=5 map[10]: type 1, range 32, base 00007000, size 5 found-> vendor=0x1022, dev=0x2020, revid=0x02 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base 00007100, size 7 found-> vendor=0x102b, dev=0x0519, revid=0x01 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=255 map[10]: type 1, range 32, base 04200000, size 14 map[14]: type 1, range 32, base 04800000, size 23 found-> vendor=0x10ec, dev=0x8139, revid=0x10 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=5 map[10]: type 1, range 32, base 00006000, size 8 map[14]: type 1, range 32, base 40000000, size 8 found-> vendor=0x0e11, dev=0x0001, revid=0x07 class=06-02-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x84c5, revid=0x04 class=05-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x84c4, revid=0x04 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 pci0: <PCI bus> on pcib0 lnc0: <PCNet/PCI Ethernet adapter> port 0x7000-0x701f irq 5 at device 11.0 on pci0 lnc0: driver is using old-style compatability shims -- What am I missing? Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 3:15:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.alcove.fr (smtp.alcove.fr [212.155.209.139]) by hub.freebsd.org (Postfix) with ESMTP id 4BD8937B4C5 for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 03:15:46 -0800 (PST) Received: from wiliam.alcove-int ([10.16.110.19]) by smtp.alcove.fr with esmtp (Exim 3.12 #1 (Debian)) id 13wN16-0007r4-00 for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 12:15:44 +0100 Received: from nsouch by wiliam.alcove-int with local (Exim 3.12 #1 (Debian)) id 13wN15-0002gR-00 for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 12:15:43 +0100 Date: Thu, 16 Nov 2000 12:15:43 +0100 From: Nicolas Souchu <nsouch@alcove.fr> To: freebsd-hackers@freebsd.org Subject: running lastest ggi demos on R4.1.1 Message-ID: <20001116121543.A10291@wiliam.alcove-int> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.4i Organization: =?iso-8859-1?Q?Alc=F4ve=2C_http:=2F=2Fwww=2Ealcove=2Efr?= Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi hackers, Has anyone been able to run the latest GGI stuff on a stable box? The port graphics/libggi is outdated. The problem seems to be when the execution enters the X library... There package is really easy-to-compile. Any X advanced user to give it a try? (gdb) core-file lt-demo.core Core was generated by `lt-demo'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/local/contrib/degas/lib/libggi/ggi/.libs/libggi.so.2...done. Reading symbols from /usr/local/lib/libgii.so.0...done. Reading symbols from /usr/local/lib/libgg.so.0...done. Reading symbols from /usr/lib/libc.so.4...done. Reading symbols from /usr/local/lib/ggi/display/X.so...done. Reading symbols from /usr/local/lib/libggi.so.2...done. Reading symbols from /usr/X11R6/lib/libX11.so.6...done. Reading symbols from /usr/X11R6/lib/libXext.so.6...done. Reading symbols from /usr/X11R6/lib/libXThrStub.so.6...done. Reading symbols from /usr/local/lib/ggi/input/xwin.so...done. Reading symbols from /usr/local/lib/ggi/display/mansync.so...done. Reading symbols from /usr/libexec/ld-elf.so.1...done. #0 0x28153907 in XCreateWindow () from /usr/X11R6/lib/libX11.so.6 (gdb) where #0 0x28153907 in XCreateWindow () from /usr/X11R6/lib/libX11.so.6 #1 0x2811521c in GGIdl_X () at mode.inc:393 #2 0x2806b3fd in ggiSetMode () at mode.c:68 #3 0x804941b in main (argc=0, argv=0xbfbffb94) at demo.c:379 #4 0x8048ec1 in _start () Thanks, Nicholas -- Nicolas Souchu Alcôve - Open Source Software Engineer - http://www.alcove.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 3:18:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from distortion.dk (distortion.dk [195.249.147.156]) by hub.freebsd.org (Postfix) with ESMTP id 2C20837B4CF for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 03:18:47 -0800 (PST) Received: from petri2000 ([194.192.131.97]) by distortion.dk (8.9.3/8.9.1) with SMTP id MAA87904; Thu, 16 Nov 2000 12:24:29 +0100 (CET) (envelope-from nicolai@petri.cc) Message-ID: <023301c04fbf$1f9c2ad0$6732a8c0@atomic.dk> From: "Nicolai Petri" <nicolai@petri.cc> To: <andrew@ugh.net.au> Cc: <freebsd-hackers@freebsd.org> References: <Pine.BSF.4.21.0011162051330.10324-100000@starbug.ugh.net.au> Subject: Re: Multithreaded tcp-server or non-blocking ? Date: Thu, 16 Nov 2000 12:19:41 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: <andrew@ugh.net.au> > On Thu, 16 Nov 2000, Nicolai Petri wrote: > > What's the best approach for a simple web-server(never more the 10 clients) > > Is it using pthread and a thread per connection . > That is probably simplest from a programming point of view. That's sounds fine to me.. :o) > > Or to make a > > non-blocking single thread server. > That will probably give you the best performance. It willl probably use > slightly less RAM as well but not enough to be of an issue unless you are > trying to fit in 4MB or something. I've got plenty of RAM. It's more a question of stability / simplicity. > > Can people show me some simple examples > > of the 2 techniques ? > As in web servers that use one or the other method or are you just after > software that uses pthreads and/or non blocking I/O? > For non blocking I/O you are probably after select, poll or kqueue. I'm quite lost here.. Is there a good reason for using kqueue instead of select/poll ? > I have a basic program that uses pthreads if that will help...it uses > kqueue as well although not for non blocking I/O. Its not finished but the > threading part works... I would love to see the code.. I'm having some stability problems with my own code. Maybe I can figure out where I went wrong. > > And what's the pro's and con's for the 2 methods ??? > > It really does depend on what you're trying to acheive...I'd tend to go > for the threads solution with the argument that the programmers time is > worth far more than the extra hardware it would take to make up any minor > performance penalty. I personally prefer the most simple and failsafe solution. Too much performance hunting will often give less understandable/debugable code. --- Thanks for your good answers. - Nicolai Petri To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 3:40:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from brutus.conectiva.com.br (brutus.conectiva.com.br [200.250.58.146]) by hub.freebsd.org (Postfix) with ESMTP id 4336B37B4C5 for <hackers@FreeBSD.ORG>; Thu, 16 Nov 2000 03:40:45 -0800 (PST) Received: from localhost (riel@localhost) by brutus.conectiva.com.br (8.11.1/8.11.1) with ESMTP id eAGBeHK13134; Thu, 16 Nov 2000 09:40:22 -0200 X-Authentication-Warning: duckman.distro.conectiva: riel owned process doing -bs Date: Thu, 16 Nov 2000 09:40:17 -0200 (BRDT) From: Rik van Riel <riel@conectiva.com.br> X-Sender: riel@duckman.distro.conectiva To: Terry Lambert <tlambert@primenet.com> Cc: void <float@firedrake.org>, hackers@FreeBSD.ORG Subject: Re: "iowait" CPU state In-Reply-To: <200011160828.BAA00995@usr02.primenet.com> Message-ID: <Pine.LNX.4.21.0011160938080.13085-100000@duckman.distro.conectiva> 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, 16 Nov 2000, Terry Lambert wrote: > > > Modern bloat-ware really pisses me off; I built the bind > > > library the other day: the frigging thing was 4M, unstripped. > > > > How does this affect the (non?-)usefullness of the > > %iowait statistic? > > When you are waiting for I/O in a well written program, it > is because there's nothing left to do but wait, which would > make the statistic useless. If there's something else you > could do, and you're waiting, by definition the program is > not well written (well written programs don't waste time for > no good reason). Ummm, how about a situation where you have a steadily increasing work load (more customers?) and want to have decent statistics of your servers to determine exactly what parts to upgrade and/or if you need to put extra machines into service? I agree that *any* statistics become useless after some time in a completely static situation, but thruth is that the number of internet users is still increasing and the workload on servers is doing the same ;) regards, Rik -- "What you're running that piece of shit Gnome?!?!" -- Miguel de Icaza, UKUUG 2000 http://www.conectiva.com/ http://www.surriel.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 16 4:16:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gate.trident-uk.co.uk (mail.trident-uk.co.uk [195.166.16.10]) by hub.freebsd.org (Postfix) with ESMTP id A7C6437B4C5 for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 04:16:18 -0800 (PST) Received: from [194.207.93.139] by gate.trident-uk.co.uk for freebsd-hackers@freebsd.org id MAA29506; Thu Nov 16 12:15:11 2000 Organization: Psi-Domain Ltd. Subject: make install world Date: Thu, 16 Nov 2000 12:18:40 +0000 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00111612204500.83372@freefire.psi-domain.co.uk> Content-Transfer-Encoding: 8bit To: freebsd-hackers@freebsd.org From: Jamie Heckford <heckfordj@psi-domain.co.uk> Reply-To: heckfordj@psi-domain.co.uk Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, During make install world, I keep having it stop complaining "xxx Directory: Not Found" If i manually create this directorys with mkdir, and re-run make install world, it works fine, but then stops when it cant find a different directory. Is their any way I can have make install world or is their something I can run before that to create the missing directorys manually? Thanks, -- Jamie Heckford Chief Network Engineer Psi-Domain - Innovative Linux Solutions. Ask Us How. =================================== email: heckfordj@psi-domain.co.uk web: http://www.psi-domain.co.uk/ tel: +44 (0)1737 789 246 fax: +44 (0)1737 789 245 mobile: +44 (0)7779 646 529 =================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 4:20:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from phobos.illtel.denver.co.us (dsl-206.169.4.82.wenet.com [206.169.4.82]) by hub.freebsd.org (Postfix) with ESMTP id 746A037B479 for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 04:20:42 -0800 (PST) Received: from localhost (abelits@localhost) by phobos.illtel.denver.co.us (8.9.3/8.9.3) with ESMTP id EAA16924; Thu, 16 Nov 2000 04:21:32 -0800 Date: Thu, 16 Nov 2000 04:21:32 -0800 (PST) From: Alex Belits <abelits@phobos.illtel.denver.co.us> To: Nicolai Petri <nicolai@petri.cc> Cc: freebsd-hackers@freebsd.org Subject: Re: Multithreaded tcp-server or non-blocking ? In-Reply-To: <021501c04fb9$574f9030$6732a8c0@atomic.dk> Message-ID: <Pine.LNX.4.20.0011160414480.16899-100000@phobos.illtel.denver.co.us> 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, 16 Nov 2000, Nicolai Petri wrote: > What's the best approach for a simple web-server(never more the 10 clients) > ? Is it using pthread and a thread per connection . Or to make a > non-blocking single thread server. Can people show me some simple examples > of the 2 techniques ? > > And what's the pro's and con's for the 2 methods ??? I would prefer one process without nonblocking i/o, as multithreaded program easily becomes hard to manage if you have any more or less complex data model. However even apache-style multiple processes will work, and will be even simplier than either -- the disadvantage is only that it will have to keep all processes independent, so some kinds of processing will be hard to implement. I wrote my own HTTP server (fhttpd) that combines nonblocking main process and multiple backend modules processes that can be blocking or nonblocking -- it's possible that what you are trying to accomplish can be done in fhttpd module without writing a full-blown server. -- Alex ---------------------------------------------------------------------- Excellent.. now give users the option to cut your hair you hippie! -- Anonymous Coward To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 4:26:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from numeri.campus.luth.se (numeri.campus.luth.se [130.240.197.103]) by hub.freebsd.org (Postfix) with ESMTP id 3C9F037B4C5 for <freebsd-hackers@FreeBSD.ORG>; Thu, 16 Nov 2000 04:26:28 -0800 (PST) Received: from numeri.campus.luth.se (localhost [127.0.0.1]) by numeri.campus.luth.se (8.9.3/8.9.3) with ESMTP id NAA08461; Thu, 16 Nov 2000 13:29:08 +0100 (CET) (envelope-from k@numeri.campus.luth.se) Message-Id: <200011161229.NAA08461@numeri.campus.luth.se> X-Mailer: exmh version 2.1.1 10/15/1999 To: heckfordj@psi-domain.co.uk Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: make install world In-Reply-To: Your message of "Thu, 16 Nov 2000 12:18:40 GMT." <00111612204500.83372@freefire.psi-domain.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 Nov 2000 13:29:08 +0100 From: Johan Karlsson <k@numeri.campus.luth.se> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Are you actually using #make install world ??? I think you want #make installworld after you succesfully build the world using #make buildworld /Johan K At Thu, 16 Nov 2000 12:18:40 GMT, Jamie Heckford wrote: > Hi, > > During make install world, I keep having it stop complaining "xxx Directory: > Not Found" > > If i manually create this directorys with mkdir, and re-run make install worl >d, > it works fine, but then stops when it cant find a different directory. > > Is their any way I can have make install world or is their something I can ru >n > before that to create the missing directorys manually? > > Thanks, > > -- > Jamie Heckford > Chief Network Engineer > Psi-Domain - Innovative Linux Solutions. Ask Us How. > > =================================== > email: heckfordj@psi-domain.co.uk > web: http://www.psi-domain.co.uk/ > > tel: +44 (0)1737 789 246 > fax: +44 (0)1737 789 245 > mobile: +44 (0)7779 646 529 > =================================== > > > 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 16 4:27: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.159.1.85]) by hub.freebsd.org (Postfix) with ESMTP id 4B67D37B479 for <freebsd-hackers@FreeBSD.ORG>; Thu, 16 Nov 2000 04:26:54 -0800 (PST) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id MAA92776; Thu, 16 Nov 2000 12:32:48 GMT (envelope-from geoffb) Date: Thu, 16 Nov 2000 12:32:48 +0000 From: Geoff Buckingham <geoffb@chuggalug.clues.com> To: Nicolai Petri <nicolai@petri.cc> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Multithreaded tcp-server or non-blocking ? Message-ID: <20001116123248.B92673@chuggalug.clues.com> References: <021501c04fb9$574f9030$6732a8c0@atomic.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <021501c04fb9$574f9030$6732a8c0@atomic.dk>; from Nicolai Petri on Thu, Nov 16, 2000 at 11:38:14AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 16, 2000 at 11:38:14AM +0100, Nicolai Petri wrote: > What's the best approach for a simple web-server(never more the 10 clients) > ? Is it using pthread and a thread per connection . Or to make a > non-blocking single thread server. Can people show me some simple examples > of the 2 techniques ? > Depending on exactly what you are trying to achieve you may want to take a look at thttpd, if you have not allready seen it. It is select based though: http://www.acme.com/software/thttpd/notes.html#select -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 6:50:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from c014.sfo.cp.net (c014-h003.c014.sfo.cp.net [209.228.12.67]) by hub.freebsd.org (Postfix) with SMTP id EF87C37B4C5 for <hackers@freebsd.org>; Thu, 16 Nov 2000 06:50:53 -0800 (PST) Received: (cpmta 8379 invoked from network); 16 Nov 2000 06:50:53 -0800 Received: from m12hRs4n205.midsouth.rr.com (HELO mike) (24.95.125.205) by smtp.valuedata.net (209.228.12.67) with SMTP; 16 Nov 2000 06:50:53 -0800 X-Sent: 16 Nov 2000 14:50:53 GMT Message-ID: <001d01c04fdc$9e2e2e80$0200000a@mike> From: "Daryl Chance" <dchance@valuedata.net> To: "FreeBSD Hackers" <hackers@freebsd.org> References: <F41mcarcR4ZDgC81Tbd00000651@hotmail.com> <20001115233003.Y830@fw.wintelcom.net> Subject: Re: scheduler activations in FBSD5.0? Date: Thu, 16 Nov 2000 08:50:52 -0600 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.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a FreeBSD 5.0 Stable or is there only a current and stable reserved for the current release version (4.X). Thanks, - Daryl Chance | And which parallel universe did ValueData, LLC | YOU crawl out of? Memphis, TN | - http://www.thinkgeek.com ----- Original Message ----- From: "Alfred Perlstein" <bright@wintelcom.net> To: "frank xu" <bsdman@hotmail.com> Cc: <freebsd-hackers@FreeBSD.ORG> Sent: Thursday, November 16, 2000 1:30 AM Subject: Re: scheduler activations in FBSD5.0? > * frank xu <bsdman@hotmail.com> [001115 23:15] wrote: > > I heard rumor that Thomas E. Anderson's Scheduler Activations theory will > > be implemented in FreeBSD 5.0 kernel, is it true? > > Several people have begun the initial development on it. > > -- > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > "I have the heart of a child; I keep it in a jar on my desk." > > > 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 16 6:51: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mb1i0.ns.pitt.edu (mb1i0.ns.pitt.edu [136.142.186.35]) by hub.freebsd.org (Postfix) with ESMTP id 722E937B4C5 for <freebsd-hackers@FreeBSD.ORG>; Thu, 16 Nov 2000 06:51:00 -0800 (PST) Received: from unixs1.cis.pitt.edu ("port 34327"@[136.142.185.31]) by pitt.edu (PMDF V5.2-32 #41462) with SMTP id <01JWLQSA550S00774Q@mb1i0.ns.pitt.edu> for freebsd-hackers@FreeBSD.ORG; Thu, 16 Nov 2000 09:50:59 EST Date: Thu, 16 Nov 2000 09:51:00 -0500 (EST) From: Pedro F Giffuni <pfg1+@pitt.edu> Subject: Re: scheduler activations in FBSD5.0? In-reply-to: <F41mcarcR4ZDgC81Tbd00000651@hotmail.com> X-Sender: pfg1@unixs1.cis.pitt.edu To: frank xu <bsdman@hotmail.com> Cc: freebsd-hackers@FreeBSD.ORG Message-id: <Pine.GSO.3.96L.1001116095042.28872A-100000@unixs1.cis.pitt.edu> MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://people.FreeBSD.org/~jasone/kse/ On Thu, 16 Nov 2000, frank xu wrote: > I heard rumor that Thomas E. Anderson's Scheduler Activations theory will > be implemented in FreeBSD 5.0 kernel, is it true? > > Regards, > XuYifeng > > _________________________________________________________________________ > Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. > > Share information about yourself, create your own public profile at > http://profiles.msn.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 Thu Nov 16 6:58:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gate.trident-uk.co.uk (mail.trident-uk.co.uk [195.166.16.10]) by hub.freebsd.org (Postfix) with ESMTP id D73EE37B4CF for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 06:58:49 -0800 (PST) Received: from [194.207.93.139] by gate.trident-uk.co.uk for freebsd-hackers@freebsd.org id OAA11663; Thu Nov 16 14:58:47 2000 Organization: Psi-Domain Ltd. Subject: Sound card support Date: Thu, 16 Nov 2000 15:02:50 +0000 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00111615042100.00255@freefire.psi-domain.co.uk> Content-Transfer-Encoding: 8bit To: freebsd-hackers@freebsd.org From: Jamie Heckford <heckfordj@psi-domain.co.uk> Reply-To: heckfordj@psi-domain.co.uk Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have an onboard sound card, and am trying to get it to work with FreeBSD. At boot, I have the following message: chip1: <Intel 82801AA (ICH) AC'97 Audio Controller> port 0xdc00-0xdc3f,0xd800-0x d8ff irq 5 at device 31.5 on pci0 And in my Kernel: # Sound device pcm This does not work though. Does anyone have any suggestions? I am using FreeBSD 4.2-BETA Thanks, -- Jamie Heckford Chief Network Engineer Psi-Domain - Innovative Linux Solutions. Ask Us How. =================================== email: heckfordj@psi-domain.co.uk web: http://www.psi-domain.co.uk/ tel: +44 (0)1737 789 246 fax: +44 (0)1737 789 245 mobile: +44 (0)7779 646 529 =================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 7: 5:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.rila.bg (earth.rila.bg [212.39.75.31]) by hub.freebsd.org (Postfix) with ESMTP id A89A837B479 for <hackers@freebsd.org>; Thu, 16 Nov 2000 07:05:35 -0800 (PST) Received: from earth.rila.bg (localhost [127.0.0.1]) by earth.rila.bg (8.11.1/8.11.1) with ESMTP id eAGF57m10268; Thu, 16 Nov 2000 17:05:09 +0200 (EET) (envelope-from mitko@earth.rila.bg) Message-Id: <200011161505.eAGF57m10268@earth.rila.bg> X-Mailer: exmh version 2.1.1 10/15/1999 To: heckfordj@psi-domain.co.uk Cc: hackers@freebsd.org Subject: Re: Sound card support In-Reply-To: Your message of "Thu, 16 Nov 2000 15:02:50 GMT." <00111615042100.00255@freefire.psi-domain.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 Nov 2000 17:05:07 +0200 From: Dimitar Peikov <mitko@earth.rila.bg> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://www.katsurajima.seya.yokohama.jp/ich/ Have fun. It works fine for me! -- Dimitar Peikov Programmer Analyst "We Build e-Business" RILA Solutions 27 Building, Acad.G.Bonchev Str. 1113 Sofia, Bulgaria home: (+359 2) 595495 phone: (+359 2) 9797320 phone: (+359 2) 9797300 fax: (+359 2) 9733355 http://www.rila.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 16 7:20:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 9374537B4C5 for <hackers@FreeBSD.ORG>; Thu, 16 Nov 2000 07:20:20 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAGFKGQ00429; Thu, 16 Nov 2000 08:20:16 -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 IAA65450; Thu, 16 Nov 2000 08:20:16 -0700 (MST) Message-Id: <200011161520.IAA65450@harmony.village.org> To: "Daryl Chance" <dchance@valuedata.net> Subject: Re: scheduler activations in FBSD5.0? Cc: "FreeBSD Hackers" <hackers@FreeBSD.ORG> In-reply-to: Your message of "Thu, 16 Nov 2000 08:50:52 CST." <001d01c04fdc$9e2e2e80$0200000a@mike> References: <001d01c04fdc$9e2e2e80$0200000a@mike> <F41mcarcR4ZDgC81Tbd00000651@hotmail.com> <20001115233003.Y830@fw.wintelcom.net> Date: Thu, 16 Nov 2000 08:20:15 -0700 From: Warner Losh <imp@village.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <001d01c04fdc$9e2e2e80$0200000a@mike> "Daryl Chance" writes: : Is there a FreeBSD 5.0 Stable or is there only a current : and stable reserved for the current release version (4.X). STABLE is reserved for those branches that have had a release on them. Since there's been no 5.0 release yet, it doesn't have a STABLE version. That's why it is called -current. 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 16 7:35:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 3EEE737B479 for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 07:35:56 -0800 (PST) Received: from pretoria-26.budapest.interware.hu ([195.70.53.90] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 13wR4r-0002JT-00; Thu, 16 Nov 2000 16:35:54 +0100 Message-ID: <3A13FEBB.D3CE66F1@elischer.org> Date: Thu, 16 Nov 2000 07:35:23 -0800 From: Julian Elischer <julian@elischer.org> X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: frank xu <bsdman@hotmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: scheduler activations in FBSD5.0? References: <F41mcarcR4ZDgC81Tbd00000651@hotmail.com> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG frank xu wrote: > > I heard rumor that Thomas E. Anderson's Scheduler Activations theory will > be implemented in FreeBSD 5.0 kernel, is it true? Basically the coming FreeBSD threading system will be based on the work by Anderson. It may have some different aspects too. I see someone already sent you the reference on how the plans are progressing at this time > > Regards, > XuYifeng -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 7:47:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.161.193]) by hub.freebsd.org (Postfix) with ESMTP id EDA5737B4C5 for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 07:47:28 -0800 (PST) Received: from mail.vt.edu (gkar.cc.vt.edu [198.82.161.190]) by lennier.cc.vt.edu (8.11.0/8.11.0) with ESMTP id eAGFlRd189874 for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 10:47:27 -0500 (EST) Received: from flaw.vt.edu ([198.82.82.148]) by gkar.cc.vt.edu (Sun Internet Mail Server sims.3.5.2000.03.23.18.03.p10) with ESMTP id <0G4400AMYJV068@gkar.cc.vt.edu> for freebsd-hackers@freebsd.org; Thu, 16 Nov 2000 10:47:24 -0500 (EST) Date: Thu, 16 Nov 2000 10:56:59 -0500 From: Raymond Law <flaw@vt.edu> Subject: FreeBSD VM X-Sender: flaw@mail.vt.edu To: freebsd-hackers@freebsd.org Message-id: <4.3.0.20001116105139.00b63cd0@mail.vt.edu> MIME-version: 1.0 X-Mailer: QUALCOMM Windows Eudora Version 4.3 Content-type: text/plain; format=flowed; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG majflt doesn't increase when a process is generating page faults. Instead, the swapper process (pid 0) gets all the page faults and it is the same as the page faults given by cnt in vmmeter.c. Why is this happening? Is there a way to get the number of page faults generated by a SINGLE process? proc *p; num_pageflts = p->p_stats->p_ru.majflt The above doesn't get increased. Thanks. Ray, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 8: 8:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from trauco.colomsat.net.co (trauco.colomsat.net.co [200.13.195.2]) by hub.freebsd.org (Postfix) with ESMTP id 8E19237B479; Thu, 16 Nov 2000 08:08:21 -0800 (PST) Received: from yahoo.com (200.13.214.129) by trauco.colomsat.net.co (NPlex 4.0.068) id 3A13EAE100001452; Thu, 16 Nov 2000 11:01:38 -0500 Message-ID: <394A5225.AF165842@yahoo.com> Date: Fri, 16 Jun 2000 11:13:25 -0500 From: "Yonny Cardenas B." <ycardena@yahoo.com> X-Mailer: Mozilla 4.61 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: hackersBSD <hackers@FreeBSD.ORG> Cc: questions <questions@FreeBSD.ORG>, German Vega <gvega@uniandes.edu.co> Subject: RTP as system calls. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello I want you to ask a favor. I'm incorporating the Real Time Transport Protocol(RTP) to FreeBSD Kernel. I want use the RTP Library API developed by Lucent http://www.cs.columbia.edu/~hgs/rtplib/rtplib-1.0a1/rtp_api.html First, I want try if this API can be add to Kernel as system calls. I know this a little crazy but I think that is possible, with corrections of course. I compiled with the Kernel this APIs without problems. But I have problems linking kernel. The following message is show it: cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 vers.c linking kernel init_sysent.o(.data+0xb8c): undefined reference to `RTPSend' init_sysent.o(.data+0xc0c): undefined reference to `RTPSchedule' rtp_unix.o: In function `_sys_bind': rtp_unix.o(.text+0x141): undefined reference to `__error' rtp_unix.o: In function `_sys_send': rtp_unix.o(.text+0x1c8): undefined reference to `send' rtp_unix.o: In function `random32': rtp_unix.o(.text+0x23d): undefined reference to `clock' rtp_unix.o(.text+0x253): undefined reference to `gethostid' I don't understand the message "undefined reference to", for example the function "send" is a socket API. In the file rtp_unix.c you can see: #include <sys/types.h> #include <sys/socket.h> ... int _sys_send(socktype skt, char *buf, int buflen, int flags) { int res; res = send(skt, buf, buflen, flags); return(res); } In the Kernel Makefile: rtp_unix.o: $S/kern/rtp/rtp_unix.c ${NORMAL_C} In the RTPLibrary Makefile: rtp_unix.o: rtp_unix.c rtp_unix.h rtp_api.h sysdep.h config.h I have some questions: 1) Can I call functions level's user into kernel, as socket() or calloc() ? 2) How must I use the global variable "errno" for value returned for system calls ? Is sufficient with #include <sys/errno.h> ? 3) How can I solve above linking errors. Thanks for your help. +------------------------------------------------------------------+ | YONNY CARDENAS B. Apartado Aereo 22828 | | Systems Engineer Santafe de Bogota D.C. | | Colombia - South America | | Student M.Sc. Tels: +571 6095477 | | UNIVERSIDAD DE LOS ANDES mailto: y-carden@uniandes.edu.co | | ycardena@yahoo.com | +------------------------------------------------------------------+ UNIX is BSD, and FreeBSD is an advanced 4.4BSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 8:52: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gate.trident-uk.co.uk (mail.trident-uk.co.uk [195.166.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 0BB6737B4C5 for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 08:51:49 -0800 (PST) Received: from [194.207.93.139] by gate.trident-uk.co.uk for freebsd-hackers@freebsd.org id QAA17536; Thu Nov 16 16:51:44 2000 Organization: Psi-Domain Ltd. Subject: New sound driver Date: Thu, 16 Nov 2000 16:53:57 +0000 X-Mailer: KMail [version 1.0.28] Content-Type: Multipart/Mixed; boundary="Boundary-=_WfAZyzAZOHsNGHcxSfUBSnsNWfUJ" MIME-Version: 1.0 Message-Id: <00111616571802.00211@freefire.psi-domain.co.uk> To: freebsd-hackers@freebsd.org From: Jamie Heckford <heckfordj@psi-domain.co.uk> Reply-To: heckfordj@psi-domain.co.uk Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Boundary-=_WfAZyzAZOHsNGHcxSfUBSnsNWfUJ Content-Type: text/plain Content-Transfer-Encoding: 8bit Hi, I tried to get my onboard intel AC'97 card to work, and used a third party driver to get success (written by Katsurajima Naoto) The following card is: pcm0: <Intel 82801AA AC'97 audio port 0xdc00-0xdc3f,0xd800-0xd8ff irq 5 at device 31.5 on pci0 This wasn't supported by FreeBSD first off, but after inclusion of the attached driver to the kernel, all i did was recompile with device pcm and it worked. Any chance someone with commit privs. could take a look at the source and *maybe* include it in FreeBSD? Thanks, -- Jamie Heckford Chief Network Engineer Psi-Domain - Innovative Linux Solutions. Ask Us How. =================================== email: heckfordj@psi-domain.co.uk web: http://www.psi-domain.co.uk/ tel: +44 (0)1737 789 246 fax: +44 (0)1737 789 245 mobile: +44 (0)7779 646 529 =================================== --Boundary-=_WfAZyzAZOHsNGHcxSfUBSnsNWfUJ Content-Type: text/english; name="ich.c" Content-Transfer-Encoding: base64 Content-Description: ICH.C Driver Source Content-Disposition: attachment; filename="ich.c" LyoKICogQ29weXJpZ2h0IChjKSAyMDAwIEthdHN1cmFqaW1hIE5hb3RvIDxyYXZlbkBrYXRzdXJh amltYS5zZXlhLnlva29oYW1hLmpwPgogKiBBbGwgcmlnaHRzIHJlc2VydmVkLgogKgogKiBSZWRp c3RyaWJ1dGlvbiBhbmQgdXNlIGluIHNvdXJjZSBhbmQgYmluYXJ5IGZvcm1zLCB3aXRoIG9yIHdp dGhvdXQKICogbW9kaWZpY2F0aW9uLCBhcmUgcGVybWl0dGVkIHByb3ZpZGVkIHRoYXQgdGhlIGZv bGxvd2luZyBjb25kaXRpb25zCiAqIGFyZSBtZXQ6CiAqIDEuIFJlZGlzdHJpYnV0aW9ucyBvZiBz b3VyY2UgY29kZSBtdXN0IHJldGFpbiB0aGUgYWJvdmUgY29weXJpZ2h0CiAqICAgIG5vdGljZSwg dGhpcyBsaXN0IG9mIGNvbmRpdGlvbnMgYW5kIHRoZSBmb2xsb3dpbmcgZGlzY2xhaW1lci4KICog Mi4gUmVkaXN0cmlidXRpb25zIGluIGJpbmFyeSBmb3JtIG11c3QgcmVwcm9kdWNlIHRoZSBhYm92 ZSBjb3B5cmlnaHQKICogICAgbm90aWNlLCB0aGlzIGxpc3Qgb2YgY29uZGl0aW9ucyBhbmQgdGhl IGZvbGxvd2luZyBkaXNjbGFpbWVyIGluIHRoZQogKiAgICBkb2N1bWVudGF0aW9uIGFuZC9vciBv dGhlciBtYXRlcmlhbHMgcHJvdmlkZWQgd2l0aCB0aGUgZGlzdHJpYnV0aW9uLgogKgogKiBUSElT IFNPRlRXQVJFIElTIFBST1ZJREVEIEJZIFRIRSBBVVRIT1IgQU5EIENPTlRSSUJVVE9SUyBgYEFT IElTJycgQU5ECiAqIEFOWSBFWFBSRVNTIE9SIElNUExJRUQgV0FSUkFOVElFUywgSU5DTFVESU5H LCBCVVQgTk9UIExJTUlURUQgVE8sIFRIRQogKiBJTVBMSUVEIFdBUlJBTlRJRVMgT0YgTUVSQ0hB TlRBQklMSVRZIEFORCBGSVRORVNTIEZPUiBBIFBBUlRJQ1VMQVIgUFVSUE9TRQogKiBBUkUgRElT Q0xBSU1FRC4gIElOIE5PIEVWRU5UIFNIQUxMIFRIRSBBVVRIT1IgT1IgQ09OVFJJQlVUT1JTIEJF IExJQUJMRQogKiBGT1IgQU5ZIERJUkVDVCwgSU5ESVJFQ1QsIElOQ0lERU5UQUwsIFNQRUNJQUws IEVYRU1QTEFSWSwgT1IgQ09OU0VRVUVOVElBTAogKiBEQU1BR0VTIChJTkNMVURJTkcsIEJVVCBO T1QgTElNSVRFRCBUTywgUFJPQ1VSRU1FTlQgT0YgU1VCU1RJVFVURSBHT09EUwogKiBPUiBTRVJW SUNFUzsgTE9TUyBPRiBVU0UsIERBVEEsIE9SIFBST0ZJVFM7IE9SIEJVU0lORVNTIElOVEVSUlVQ VElPTikKICogSE9XRVZFUiBDQVVTRUQgQU5EIE9OIEFOWSBUSEVPUlkgT0YgTElBQklMSVRZLCBX SEVUSEVSSU4gQ09OVFJBQ1QsIFNUUklDVAogKiBMSUFCSUxJVFksIE9SIFRPUlQgKElOQ0xVRElO RyBORUdMSUdFTkNFIE9SIE9USEVSV0lTRSkgQVJJU0lORyBJTiBBTlkgV0FZCiAqIE9VVCBPRiBU SEUgVVNFIE9GIFRISVMgU09GVFdBUkUsIEVWRU4gSUYgQURWSVNFRCBPRiBUSEVQT1NTSUJJTElU WSBPRgogKiBTVUNIIERBTUFHRS4KICoKICogJEZyZWVCU0QkCiAqLwoKI2luY2x1ZGUgPGRldi9z b3VuZC9wY20vc291bmQuaD4KI2luY2x1ZGUgPGRldi9zb3VuZC9wY20vYWM5Ny5oPgoKI2luY2x1 ZGUgPHBjaS9wY2lyZWcuaD4KI2luY2x1ZGUgPHBjaS9wY2l2YXIuaD4KCgovKiAtLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LSAqLwoKI2RlZmluZSBJQ0hfUkVDUFJJTUFSWSAwCgojZGVmaW5lIElDSF9USU1FT1VUIDEwMDAg Lyogc2VtYXBob3JlIHRpbWVvdXQgcG9sbGluZyBjb3VudCAqLwoKI2RlZmluZSBQQ0lSX05BTUJB UiAweDEwCiNkZWZpbmUgUENJUl9OQUJNQkFSIDB4MTQKCi8qIE5hdGl2ZSBBdWRpbyBCdXMgTWFz dGVyIENvbnRyb2wgUmVnaXN0ZXJzICovCiNkZWZpbmUgSUNIX1JFR19QSV9CREJBUiAweDAwCiNk ZWZpbmUgSUNIX1JFR19QSV9DSVYgICAweDA0CiNkZWZpbmUgSUNIX1JFR19QSV9MVkkgICAweDA1 CiNkZWZpbmUgSUNIX1JFR19QSV9TUiAgICAweDA2CiNkZWZpbmUgSUNIX1JFR19QSV9QSUNCICAw eDA4CiNkZWZpbmUgSUNIX1JFR19QSV9QSVYgICAweDBhCiNkZWZpbmUgSUNIX1JFR19QSV9DUiAg ICAweDBiCiNkZWZpbmUgSUNIX1JFR19QT19CREJBUiAweDEwCiNkZWZpbmUgSUNIX1JFR19QT19D SVYgICAweDE0CiNkZWZpbmUgSUNIX1JFR19QT19MVkkgICAweDE1CiNkZWZpbmUgSUNIX1JFR19Q T19TUiAgICAweDE2CiNkZWZpbmUgSUNIX1JFR19QT19QSUNCICAweDE4CiNkZWZpbmUgSUNIX1JF R19QT19QSVYgICAweDFhCiNkZWZpbmUgSUNIX1JFR19QT19DUiAgICAweDFiCiNkZWZpbmUgSUNI X1JFR19NQ19CREJBUiAweDIwCiNkZWZpbmUgSUNIX1JFR19NQ19DSVYgICAweDI0CiNkZWZpbmUg SUNIX1JFR19NQ19MVkkgICAweDI1CiNkZWZpbmUgSUNIX1JFR19NQ19TUiAgICAweDI2CiNkZWZp bmUgSUNIX1JFR19NQ19QSUNCICAweDI4CiNkZWZpbmUgSUNIX1JFR19NQ19QSVYgICAweDJhCiNk ZWZpbmUgSUNIX1JFR19NQ19DUiAgICAweDJiCiNkZWZpbmUgSUNIX1JFR19HTE9CX0NOVCAweDJj CiNkZWZpbmUgSUNIX1JFR19HTE9CX1NUQSAweDMwCiNkZWZpbmUgSUNIX1JFR19BQ0NfU0VNQSAw eDM0Ci8qIFN0YXR1cyBSZWdpc3RlciBWYWx1ZXMgKi8KI2RlZmluZSBJQ0hfWF9TUl9EQ0ggICAw eDAwMDEKI2RlZmluZSBJQ0hfWF9TUl9DRUxWICAweDAwMDIKI2RlZmluZSBJQ0hfWF9TUl9MVkJD SSAweDAwMDQKI2RlZmluZSBJQ0hfWF9TUl9CQ0lTICAweDAwMDgKI2RlZmluZSBJQ0hfWF9TUl9G SUZPRSAweDAwMTAKLyogQ29udHJvbCBSZWdpc3RlciBWYWx1ZXMgKi8KI2RlZmluZSBJQ0hfWF9D Ul9SUEJNICAweDAxCiNkZWZpbmUgSUNIX1hfQ1JfUlIgICAgMHgwMgojZGVmaW5lIElDSF9YX0NS X0xWQklFIDB4MDQKI2RlZmluZSBJQ0hfWF9DUl9GRUlFICAweDA4CiNkZWZpbmUgSUNIX1hfQ1Jf SU9DRSAgMHgxMAovKiBHbG9iYWwgQ29udHJvbCBSZWdpc3RlciBWYWx1ZXMgKi8KI2RlZmluZSBJ Q0hfR0xPQl9DVExfR0lFICAweDAwMDAwMDAxCiNkZWZpbmUgSUNIX0dMT0JfQ1RMX0NPTEQgMHgw MDAwMDAwMiAvKiBuZWdhdGUgKi8KI2RlZmluZSBJQ0hfR0xPQl9DVExfV0FSTSAweDAwMDAwMDA0 CiNkZWZpbmUgSUNIX0dMT0JfQ1RMX1NIVVQgMHgwMDAwMDAwOAojZGVmaW5lIElDSF9HTE9CX0NU TF9QUkVTIDB4MDAwMDAwMTAKI2RlZmluZSBJQ0hfR0xPQl9DVExfU1JFUyAweDAwMDAwMDIwCi8q IEdsb2JhbCBTdGF0dXMgUmVnaXN0ZXIgVmFsdWVzICovCiNkZWZpbmUgSUNIX0dMT0JfU1RBX0dT Q0kgICAweDAwMDAwMDAxCiNkZWZpbmUgSUNIX0dMT0JfU1RBX01JSU5UICAweDAwMDAwMDAyCiNk ZWZpbmUgSUNIX0dMT0JfU1RBX01PSU5UICAweDAwMDAwMDA0CiNkZWZpbmUgSUNIX0dMT0JfU1RB X1BJSU5UICAweDAwMDAwMDIwCiNkZWZpbmUgSUNIX0dMT0JfU1RBX1BPSU5UICAweDAwMDAwMDQw CiNkZWZpbmUgSUNIX0dMT0JfU1RBX01JTlQgICAweDAwMDAwMDgwCiNkZWZpbmUgSUNIX0dMT0Jf U1RBX1BDUiAgICAweDAwMDAwMTAwCiNkZWZpbmUgSUNIX0dMT0JfU1RBX1NDUiAgICAweDAwMDAw MjAwCiNkZWZpbmUgSUNIX0dMT0JfU1RBX1BSRVMgICAweDAwMDAwNDAwCiNkZWZpbmUgSUNIX0dM T0JfU1RBX1NSRVMgICAweDAwMDAwODAwCiNkZWZpbmUgSUNIX0dMT0JfU1RBX1NMT1QxMiAweDAw MDA3MDAwCiNkZWZpbmUgSUNIX0dMT0JfU1RBX1JDT0RFQyAweDAwMDA4MDAwCiNkZWZpbmUgSUNI X0dMT0JfU1RBX0FEMyAgICAweDAwMDEwMDAwCiNkZWZpbmUgSUNIX0dMT0JfU1RBX01EMyAgICAw eDAwMDIwMDAwCiNkZWZpbmUgSUNIX0dMT0JfU1RBX0lNQVNLICAoSUNIX0dMT0JfU1RBX01JSU5U IHwgSUNIX0dMT0JfU1RBX01PSU5UIHwgSUNIX0dMT0JfU1RBX1BJSU5UIHwgSUNIX0dMT0JfU1RB X1BPSU5UIHwgSUNIX0dMT0JfU1RBX01JTlQgfCBJQ0hfR0xPQl9TVEFfUFJFUyB8IElDSF9HTE9C X1NUQV9TUkVTKQoKLyogQUMnOTcgcG93ZXIvcmVhZHkgZnVuY3Rpb25zICovCiNkZWZpbmUgQUM5 N19QT1dFUl9QSU5QT1dFUiAgMHgwMTAwCiNkZWZpbmUgQUM5N19QT1dFUl9QSU5SRUFEWSAgMHgw MDAxCiNkZWZpbmUgQUM5N19QT1dFUl9QT1VUUE9XRVIgMHgwMjAwCiNkZWZpbmUgQUM5N19QT1dF Ul9QT1VUUkVBRFkgMHgwMDAyCgovKiBwbGF5L3JlY29yZCBidWZmZXIgKi8KI2RlZmluZSBJQ0hf RklGT0lOREVYIDMyCiNkZWZpbmUgSUNIX0JEQ19JT0MgMHg4MDAwMDAwMAojZGVmaW5lIElDSF9C RENfQlVQIDB4NDAwMDAwMDAKI2RlZmluZSBJQ0hfREVGQVVMVF9CTE9DS1NaIDIwNDgKLyogYnVm ZmVyIGRlc2NyaXB0b3IgKi8Kc3RydWN0IGljaF9kZXNjIHsKCXZvbGF0aWxlIHVfaW50MzJfdCBi dWZmZXI7Cgl2b2xhdGlsZSB1X2ludDMyX3QgbGVuZ3RoOwp9OwoKc3RydWN0IHNjX2luZm87Cgov KiBjaGFubmVsIHJlZ2lzdGVycyAqLwpzdHJ1Y3Qgc2NfY2hpbmZvIHsKCWludCBydW4sIHNwZCwg ZGlyLCBmbXQ7CglzbmRfZGJ1ZiAqYnVmZmVyOwoJcGNtX2NoYW5uZWwgKmNoYW5uZWw7CglzdHJ1 Y3Qgc2NfaW5mbyAqcGFyZW50OwoJc3RydWN0IGljaF9kZXNjICppbmRleDsKCXVfaW50MzJfdCBs dmk7Cn07CgovKiBkZXZpY2UgcHJpdmF0ZSBkYXRhICovCnN0cnVjdCBzY19pbmZvIHsKCWRldmlj ZV90CWRldjsKCXVfaW50MzJfdCAJdHlwZSwgcmV2OwoJdV9pbnQzMl90CWNkMmlkLCBjdHJsYmFz ZTsKCglzdHJ1Y3QgcmVzb3VyY2UgKm5hbWJhciwgKm5hYm1iYXI7CglpbnQJCW5hbWJhcmlkLCBu YWJtYmFyaWQ7CglidXNfc3BhY2VfdGFnX3QgbmFtYmFydCwgbmFibWJhcnQ7CglidXNfc3BhY2Vf aGFuZGxlX3QgbmFtYmFyaCwgbmFibWJhcmg7CglidXNfZG1hX3RhZ190IHBhcmVudF9kbWF0OwoJ c3RydWN0IHJlc291cmNlICppcnE7CglpbnQJCWlycWlkOwoJdm9pZAkJKmloOwoKCXN0cnVjdCBh Yzk3X2luZm8gKmNvZGVjOwoJc3RydWN0IHNjX2NoaW5mbyAqcGksICpwbzsKfTsKCnN0cnVjdCB7 Cgl1X2ludDMyX3QgZGV2LCBzdWJkZXY7CgljaGFyICpuYW1lOwoJdV9pbnQzMl90ICptY29kZTsK fSBpY2hfZGV2c1tdID0gewovKiBCZXdhcmUsIHRoaW5ncyBrbm93IHRoZSBpbmRleGVzIGhlcmUg Ki8KCXsweDcxOTU4MDg2LCAwLCAiSW50ZWwgNDQzTVggQUMnOTcgYXVkaW8iLCBOVUxMfSwKCXsw eDI0MTU4MDg2LCAwLCAiSW50ZWwgODI4MDFBQSBBQyc5NyBhdWRpbyIsIE5VTEx9LAoJezB4MjQy NTgwODYsIDAsICJJbnRlbCA4MjkwMUFCIEFDJzk3IGF1ZGlvIiwgTlVMTH0sCgl7MHgyNDQ1ODA4 NiwgMCwgIkludGVsIDgyODAxQkEgQUMnOTcgYXVkaW8iLCBOVUxMfSwKCXswLCAwLCBOVUxMLCBO VUxMfQp9OwoKLyogdmFyaWFibGUgcmF0ZSBhdWRpbyAqLwpzdGF0aWMgdV9pbnQxNl90IGljaF9y YXRlW10gPSB7CiAgICA4MDAwLCAxMTAyNSwgMTYwMDAsIDIyMDUwLCA0NDEwMCwgNDgwMDAsIDAK fTsKCi8qIC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tICovCgovKgogKiBwcm90b3R5cGVzCiAqLwoKLyogY2hhbm5lbCBp bnRlcmZhY2UgKi8Kc3RhdGljIHZvaWQgKmljaHBjaGFuX2luaXQodm9pZCAqZGV2aW5mbywgc25k X2RidWYgKmIsIHBjbV9jaGFubmVsICpjLCBpbnQgZGlyKTsKc3RhdGljIGludCBpY2hwY2hhbl9z ZXRkaXIodm9pZCAqZGF0YSwgaW50IGRpcik7CnN0YXRpYyBpbnQgaWNocGNoYW5fc2V0Zm9ybWF0 KHZvaWQgKmRhdGEsIHVfaW50MzJfdCBmb3JtYXQpOwpzdGF0aWMgaW50IGljaHBjaGFuX3NldHNw ZWVkKHZvaWQgKmRhdGEsIHVfaW50MzJfdCBzcGVlZCk7CnN0YXRpYyBpbnQgaWNocGNoYW5fc2V0 YmxvY2tzaXplKHZvaWQgKmRhdGEsIHVfaW50MzJfdCBibG9ja3NpemUpOwpzdGF0aWMgaW50IGlj aHBjaGFuX3RyaWdnZXIodm9pZCAqZGF0YSwgaW50IGdvKTsKc3RhdGljIGludCBpY2hwY2hhbl9n ZXRwdHIodm9pZCAqZGF0YSk7CnN0YXRpYyBwY21jaGFuX2NhcHMgKmljaHBjaGFuX2dldGNhcHMo dm9pZCAqZGF0YSk7CgpzdGF0aWMgdm9pZCAqaWNocmNoYW5faW5pdCh2b2lkICpkZXZpbmZvLCBz bmRfZGJ1ZiAqYiwgcGNtX2NoYW5uZWwgKmMsIGludCBkaXIpOwpzdGF0aWMgaW50IGljaHJjaGFu X3NldGRpcih2b2lkICpkYXRhLCBpbnQgZGlyKTsKc3RhdGljIGludCBpY2hyY2hhbl9zZXRmb3Jt YXQodm9pZCAqZGF0YSwgdV9pbnQzMl90IGZvcm1hdCk7CnN0YXRpYyBpbnQgaWNocmNoYW5fc2V0 c3BlZWQodm9pZCAqZGF0YSwgdV9pbnQzMl90IHNwZWVkKTsKc3RhdGljIGludCBpY2hyY2hhbl9z ZXRibG9ja3NpemUodm9pZCAqZGF0YSwgdV9pbnQzMl90IGJsb2Nrc2l6ZSk7CnN0YXRpYyBpbnQg aWNocmNoYW5fdHJpZ2dlcih2b2lkICpkYXRhLCBpbnQgZ28pOwpzdGF0aWMgaW50IGljaHJjaGFu X2dldHB0cih2b2lkICpkYXRhKTsKc3RhdGljIHBjbWNoYW5fY2FwcyAqaWNocmNoYW5fZ2V0Y2Fw cyh2b2lkICpkYXRhKTsKCi8qIHRhbGsgdG8gdGhlIGNvZGVjIC0gY2FsbGVkIGZyb20gYWM5Ny5j ICovCnN0YXRpYyB1X2ludDMyX3QgaWNoX3JkY2Qodm9pZCAqLCBpbnQpOwpzdGF0aWMgdm9pZCAg CSBpY2hfd3JjZCh2b2lkICosIGludCwgdV9pbnQzMl90KTsKCi8qIHN0dWZmICovCnN0YXRpYyBp bnQgICAgICAgaWNoX2luaXQoc3RydWN0IHNjX2luZm8gKik7CnN0YXRpYyB2b2lkICAgICAgaWNo X2ludHIodm9pZCAqKTsKCi8qIHRhbGsgdG8gdGhlIGNhcmQgKi8Kc3RhdGljIHVfaW50MzJfdCBp Y2hfcmQoc3RydWN0IHNjX2luZm8gKiwgaW50LCBpbnQpOwpzdGF0aWMgdm9pZCAJIGljaF93cihz dHJ1Y3Qgc2NfaW5mbyAqLCBpbnQsIHVfaW50MzJfdCwgaW50KTsKCi8qIC0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tICov CgpzdGF0aWMgdV9pbnQzMl90IGljaF9yZWNmbXRbXSA9IHsKCUFGTVRfU1RFUkVPIHwgQUZNVF9T MTZfTEUsCgkwCn07CnN0YXRpYyBwY21jaGFuX2NhcHMgaWNoX3JlY2NhcHMgPSB7ODAwMCwgNDgw MDAsIGljaF9yZWNmbXQsIDB9OwoKc3RhdGljIHVfaW50MzJfdCBpY2hfcGxheWZtdFtdID0gewoJ QUZNVF9TVEVSRU8gfCBBRk1UX1MxNl9MRSwKCTAKfTsKc3RhdGljIHBjbWNoYW5fY2FwcyBpY2hf cGxheWNhcHMgPSB7ODAwMCwgNDgwMDAsIGljaF9wbGF5Zm10LCAwfTsKCnN0YXRpYyBwY21fY2hh bm5lbCBpY2hfcGNoYW50ZW1wbGF0ZSA9IHsKCWljaHBjaGFuX2luaXQsCglpY2hwY2hhbl9zZXRk aXIsCglpY2hwY2hhbl9zZXRmb3JtYXQsCglpY2hwY2hhbl9zZXRzcGVlZCwKCWljaHBjaGFuX3Nl dGJsb2Nrc2l6ZSwKCWljaHBjaGFuX3RyaWdnZXIsCglpY2hwY2hhbl9nZXRwdHIsCglpY2hwY2hh bl9nZXRjYXBzLAp9OwoKc3RhdGljIHBjbV9jaGFubmVsIGljaF9yY2hhbnRlbXBsYXRlID0gewoJ aWNocmNoYW5faW5pdCwKCWljaHJjaGFuX3NldGRpciwKCWljaHJjaGFuX3NldGZvcm1hdCwKCWlj aHJjaGFuX3NldHNwZWVkLAoJaWNocmNoYW5fc2V0YmxvY2tzaXplLAoJaWNocmNoYW5fdHJpZ2dl ciwKCWljaHJjaGFuX2dldHB0ciwKCWljaHJjaGFuX2dldGNhcHMsCn07CgovKiAtLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LSAqLwovKiBIYXJkd2FyZSAqLwpzdGF0aWMgdV9pbnQzMl90CmljaF9yZChzdHJ1Y3Qgc2NfaW5m byAqc2MsIGludCByZWdubywgaW50IHNpemUpCnsKCXN3aXRjaCAoc2l6ZSkgewoJY2FzZSAxOgoJ CXJldHVybiBidXNfc3BhY2VfcmVhZF8xKHNjLT5uYW1iYXJ0LCBzYy0+bmFtYmFyaCwgcmVnbm8p OwoJY2FzZSAyOgoJCXJldHVybiBidXNfc3BhY2VfcmVhZF8yKHNjLT5uYW1iYXJ0LCBzYy0+bmFt YmFyaCwgcmVnbm8pOwoJY2FzZSA0OgoJCXJldHVybiBidXNfc3BhY2VfcmVhZF80KHNjLT5uYW1i YXJ0LCBzYy0+bmFtYmFyaCwgcmVnbm8pOwoJZGVmYXVsdDoKCQlyZXR1cm4gMHhmZmZmZmZmZjsK CX0KfQoKc3RhdGljIHZvaWQKaWNoX3dyKHN0cnVjdCBzY19pbmZvICpzYywgaW50IHJlZ25vLCB1 X2ludDMyX3QgZGF0YSwgaW50IHNpemUpCnsKCXN3aXRjaCAoc2l6ZSkgewoJY2FzZSAxOgoJCWJ1 c19zcGFjZV93cml0ZV8xKHNjLT5uYW1iYXJ0LCBzYy0+bmFtYmFyaCwgcmVnbm8sIGRhdGEpOwoJ CWJyZWFrOwoJY2FzZSAyOgoJCWJ1c19zcGFjZV93cml0ZV8yKHNjLT5uYW1iYXJ0LCBzYy0+bmFt YmFyaCwgcmVnbm8sIGRhdGEpOwoJCWJyZWFrOwoJY2FzZSA0OgoJCWJ1c19zcGFjZV93cml0ZV80 KHNjLT5uYW1iYXJ0LCBzYy0+bmFtYmFyaCwgcmVnbm8sIGRhdGEpOwoJCWJyZWFrOwoJfQp9Cgov KiBhYzk3IGNvZGVjICovCnN0YXRpYyBpbnQKaWNoX3dhaXRjZCh2b2lkICpkZXZpbmZvKQp7Cglp bnQgaTsKCXVfaW50MzJfdCBkYXRhOwoJc3RydWN0IHNjX2luZm8gKnNjID0gKHN0cnVjdCBzY19p bmZvICopZGV2aW5mbzsKCWZvciAoaSA9IDA7aSA8IElDSF9USU1FT1VUO2krKykgewoJCWRhdGEg PSBidXNfc3BhY2VfcmVhZF8xKHNjLT5uYWJtYmFydCwgc2MtPm5hYm1iYXJoLAoJCSAgICBJQ0hf UkVHX0FDQ19TRU1BKTsKCQlpZiAoKGRhdGEgJiAweDAxKSA9PSAwKQoJCQlyZXR1cm4gMDsKCX0K CWRldmljZV9wcmludGYoc2MtPmRldiwgIkNPREVDIHNlbWFwaG9yZSB0aW1lb3V0XG4iKTsKCXJl dHVybiBFVElNRURPVVQ7Cn0KCnN0YXRpYyB1X2ludDMyX3QKaWNoX3JkY2Qodm9pZCAqZGV2aW5m bywgaW50IHJlZ25vKQp7CglzdHJ1Y3Qgc2NfaW5mbyAqc2MgPSAoc3RydWN0IHNjX2luZm8gKilk ZXZpbmZvOwoJcmVnbm8gJj0gMHhmZjsKI2lmKDApCglkZXZpY2VfcHJpbnRmKHNjLT5kZXYsICJp Y2hfcmRjZChzYywgMHglMDJ4KVxuIiwgcmVnbm8pOwojZW5kaWYKCWljaF93YWl0Y2Qoc2MpOwoJ cmV0dXJuIGljaF9yZChzYywgcmVnbm8sIDIpOwp9CgpzdGF0aWMgdm9pZAppY2hfd3JjZCh2b2lk ICpkZXZpbmZvLCBpbnQgcmVnbm8sIHVfaW50MzJfdCBkYXRhKQp7CglzdHJ1Y3Qgc2NfaW5mbyAq c2MgPSAoc3RydWN0IHNjX2luZm8gKilkZXZpbmZvOwoJcmVnbm8gJj0gMHhmZjsKI2lmKDApCglk ZXZpY2VfcHJpbnRmKHNjLT5kZXYsICJpY2hfd3JjZChzYywgMHglMDJ4LCAweCUwNHgpXG4iLCBy ZWdubywgZGF0YSk7CiNlbmRpZgoJaWNoX3dhaXRjZChzYyk7CglpY2hfd3Ioc2MsIHJlZ25vLCBk YXRhLCAyKTsKfQoKLyogY2hhbm5lbCBjb21tb24gcm91dGluZXMgKi8Kc3RhdGljIHZvaWQKaWNo Y2hhbl9zZXRtYXAodm9pZCAqYXJnLCBidXNfZG1hX3NlZ21lbnRfdCAqc2VncywgaW50IG5zZWcs IGludCBlcnJvcikKewoJc3RydWN0IHNjX2NoaW5mbyAqY2ggPSBhcmc7CgoJaWYgKGJvb3R2ZXJi b3NlKSB7CgkJZGV2aWNlX3ByaW50ZihjaC0+cGFyZW50LT5kZXYsICJzZXRtYXAoMHglbHgsIDB4 JWx4KVxuIiwgKHVuc2lnbmVkIGxvbmcpc2Vncy0+ZHNfYWRkciwgKHVuc2lnbmVkIGxvbmcpc2Vn cy0+ZHNfbGVuKTsKCX0KfQoKc3RhdGljIGludAppY2hjaGFuX2luaXRidWYoc3RydWN0IHNjX2No aW5mbyAqY2gpCnsKCXN0cnVjdCBzY19pbmZvICpzYyA9IGNoLT5wYXJlbnQ7CglidXNfZG1hbWFw X3QgbWFwOwoJaW50IGk7CgoJY2gtPmJ1ZmZlci0+YnVmID0gTlVMTDsKCWNoLT5idWZmZXItPmJ1 ZnNpemUgPSBJQ0hfREVGQVVMVF9CTE9DS1NaICogSUNIX0ZJRk9JTkRFWDsKCWlmIChjaG5fYWxs b2NidWYoY2gtPmJ1ZmZlciwgc2MtPnBhcmVudF9kbWF0KSkgewoJCWZyZWUoY2gsIE1fREVWQlVG KTsKCQlyZXR1cm4gLTE7Cgl9CglpZiAoYnVzX2RtYW1lbV9hbGxvYyhzYy0+cGFyZW50X2RtYXQs KHZvaWQgKiopJmNoLT5pbmRleCwgQlVTX0RNQV9OT1dBSVQsICZtYXApKSB7CgkJZnJlZShjaCwg TV9ERVZCVUYpOwoJCXJldHVybiAtMTsKCX0KCWlmIChidXNfZG1hbWFwX2xvYWQoc2MtPnBhcmVu dF9kbWF0LCBtYXAsIGNoLT5pbmRleCwKCSAgICBzaXplb2Yoc3RydWN0IGljaF9kZXNjKSAqIElD SF9GSUZPSU5ERVgsIGljaGNoYW5fc2V0bWFwLCBjaCwgMCkpIHsKCQlmcmVlKGNoLCBNX0RFVkJV Rik7CgkJcmV0dXJuIC0xOwoJfQoJZm9yIChpID0gMDtpIDwgSUNIX0ZJRk9JTkRFWDtpKyspIHsK CQljaC0+aW5kZXhbaV0uYnVmZmVyID0gdnRvcGh5cyhjaC0+YnVmZmVyLT5idWYpICsKCQkgICAg SUNIX0RFRkFVTFRfQkxPQ0tTWiAqIGk7CgkJaWYgKGNoLT5kaXIgPT0gUENNRElSX1BMQVkpCgkJ CWNoLT5pbmRleFtpXS5sZW5ndGggPSAwOwoJCWVsc2UKCQkJY2gtPmluZGV4W2ldLmxlbmd0aCA9 IElDSF9CRENfSU9DICsKCQkJICAgIElDSF9ERUZBVUxUX0JMT0NLU1ogLyAyOwoJfQoJcmV0dXJu IDA7Cn0KCi8qIHBsYXkgY2hhbm5lbCBpbnRlcmZhY2UgKi8Kc3RhdGljIGludAppY2hwY2hhbl9w b3dlcihzdHJ1Y3Qgc2NfaW5mbyAqc2MsIGludCBzdykKewoJdV9pbnQzMl90IGNyOwoJaW50IGk7 CgoJY3IgPSBpY2hfcmRjZChzYywgQUM5N19SRUdfUE9XRVIpOwoJaWYgKHN3KSB7IC8qIHBvd2Vy IG9uICovCgkJY3IgJj0gfkFDOTdfUE9XRVJfUE9VVFBPV0VSOwoJCWljaF93cmNkKHNjLCBBQzk3 X1JFR19QT1dFUiwgY3IpOwoJCWZvciAoaSA9IDA7aSA8IElDSF9USU1FT1VUO2krKykgewoJCQlj ciA9IGljaF9yZGNkKHNjLCBBQzk3X1JFR19QT1dFUik7CgkJCWlmICgoY3IgJiBBQzk3X1BPV0VS X1BPVVRSRUFEWSkgIT0gMCkKCQkJCWJyZWFrOwoJCX0KCX0KCWVsc2UgeyAvKiBwb3dlciBvZmYg Ki8KCQljciB8PSBBQzk3X1BPV0VSX1BPVVRQT1dFUjsKCQlpY2hfd3JjZChzYywgQUM5N19SRUdf UE9XRVIsIGNyKTsKCQlmb3IgKGkgPSAwO2kgPCBJQ0hfVElNRU9VVDtpKyspIHsKCQkJY3IgPSBp Y2hfcmRjZChzYywgQUM5N19SRUdfUE9XRVIpOwoJCQlpZiAoKGNyICYgQUM5N19QT1dFUl9QT1VU UkVBRFkpID09IDApCgkJCQlicmVhazsKCQl9Cgl9CglpZiAoaSA9PSBJQ0hfVElNRU9VVCkKCQly ZXR1cm4gLTE7CglyZXR1cm4gMDsKfQoKc3RhdGljIHZvaWQgKgppY2hwY2hhbl9pbml0KHZvaWQg KmRldmluZm8sIHNuZF9kYnVmICpiLCBwY21fY2hhbm5lbCAqYywgaW50IGRpcikKewoJc3RydWN0 IHNjX2luZm8gKnNjID0gZGV2aW5mbzsKCXN0cnVjdCBzY19jaGluZm8gKmNoOwoJdV9pbnQzMl90 IGNyOwoJaW50IGk7CgojaWYoMCkKCWRldmljZV9wcmludGYoc2MtPmRldiwgImljaHBjaGFuX2lu aXQoMHglMDh4LCAweCUwOHgsIDB4JTA4eCwgJWQpXG4iLCBkZXZpbmZvLCBiLCBjLCBkaXIpOwoj ZW5kaWYKCWJ1c19zcGFjZV93cml0ZV8xKHNjLT5uYWJtYmFydCwgc2MtPm5hYm1iYXJoLCBJQ0hf UkVHX1BPX0NSLCAwKTsKCWJ1c19zcGFjZV93cml0ZV8xKHNjLT5uYWJtYmFydCwgc2MtPm5hYm1i YXJoLCBJQ0hfUkVHX1BPX0NSLAoJICAgIElDSF9YX0NSX1JSKTsKCWZvciAoaSA9IDA7aSA8IElD SF9USU1FT1VUO2krKykgewoJCWNyID0gYnVzX3NwYWNlX3JlYWRfMShzYy0+bmFibWJhcnQsIHNj LT5uYWJtYmFyaCwKCQkgICAgSUNIX1JFR19QT19DUik7CgkJaWYgKGNyID09IDApCgkJCWJyZWFr OwoJfQoJaWYgKGkgPT0gSUNIX1RJTUVPVVQpIHsKCQlkZXZpY2VfcHJpbnRmKHNjLT5kZXYsICJj YW5ub3QgcmVzZXQgcGxheSBjb2RlY1xuIik7CgkJcmV0dXJuIE5VTEw7Cgl9CglpZiAoaWNocGNo YW5fcG93ZXIoc2MsIDEpID09IC0xKSB7CgkJZGV2aWNlX3ByaW50ZihzYy0+ZGV2LCAicGxheSBE QUMgbm90IHJlYWR5XG4iKTsKCQlyZXR1cm4gTlVMTDsKCX0KCWljaHBjaGFuX3Bvd2VyKHNjLCAw KTsKCWlmICgoY2ggPSBtYWxsb2Moc2l6ZW9mKCpjaCksIE1fREVWQlVGLCBNX05PV0FJVCkpID09 IE5VTEwpIHsKCQlkZXZpY2VfcHJpbnRmKHNjLT5kZXYsICJjYW5ub3QgYWxsb2NhdGUgY2hhbm5l bCBpbmZvIGFyZWFcbiIpOwoJCXJldHVybiBOVUxMOwoJfQoJY2gtPmJ1ZmZlciA9IGI7CgljaC0+ Y2hhbm5lbCA9IGM7CgljaC0+cGFyZW50ID0gc2M7CgljaC0+ZGlyID0gUENNRElSX1BMQVk7Cglj aC0+cnVuID0gMDsKCWNoLT5sdmkgPSAwOwoJaWYgKGljaGNoYW5faW5pdGJ1ZihjaCkpIHsKCQlk ZXZpY2VfcHJpbnRmKHNjLT5kZXYsICJjYW5ub3QgYWxsb2NhdGUgY2hhbm5lbCBidWZmZXJcbiIp OwoJCXJldHVybiBOVUxMOwoJfQoJYnVzX3NwYWNlX3dyaXRlXzQoc2MtPm5hYm1iYXJ0LCBzYy0+ bmFibWJhcmgsIElDSF9SRUdfUE9fQkRCQVIsCgkgICAgKHVfaW50MzJfdCl2dG9waHlzKGNoLT5p bmRleCkpOwoJc2MtPnBvID0gY2g7CglpZiAoYm9vdHZlcmJvc2UpIHsKCQlkZXZpY2VfcHJpbnRm KHNjLT5kZXYsIlBsYXkgY29kZWMgc3VwcG9ydCByYXRlKEh6KTogIik7CgkJZm9yIChpID0gMDtp Y2hfcmF0ZVtpXSAhPSAwO2krKykgewoJCQlpZiAoaWNocGNoYW5fc2V0c3BlZWQoY2gsIGljaF9y YXRlW2ldKSA9PSBpY2hfcmF0ZVtpXSkgewoJCQkJcHJpbnRmKCIlZCAiLCBpY2hfcmF0ZVtpXSk7 CgkJCX0KCQl9CgkJcHJpbnRmKCJcbiIpOwoJfQoJcmV0dXJuIGNoOwp9CgpzdGF0aWMgaW50Cmlj aHBjaGFuX3NldGRpcih2b2lkICpkYXRhLCBpbnQgZGlyKQp7CiNpZigwKQoJc3RydWN0IHNjX2No aW5mbyAqY2ggPSBkYXRhOwoJZGV2aWNlX3ByaW50ZihjaC0+cGFyZW50LT5kZXYsICJpY2hwY2hh bl9zZXRkaXIoMHglMDh4LCAlZClcbiIsIGRhdGEsIGRpcik7CiNlbmRpZgoJcmV0dXJuIDA7Cn0K CnN0YXRpYyBpbnQKaWNocGNoYW5fc2V0Zm9ybWF0KHZvaWQgKmRhdGEsIHVfaW50MzJfdCBmb3Jt YXQpCnsKCXN0cnVjdCBzY19jaGluZm8gKmNoID0gZGF0YTsKCiNpZigwKQoJZGV2aWNlX3ByaW50 ZihjaC0+cGFyZW50LT5kZXYsICJpY2hwY2hhbl9zZXRmb3JtYXQoMHglMDh4LCAweCUwOHgpXG4i LCBkYXRhLCBmb3JtYXQpOwojZW5kaWYKCWNoLT5mbXQgPSBmb3JtYXQ7CglyZXR1cm4gMDsKfQoK c3RhdGljIGludAppY2hwY2hhbl9zZXRzcGVlZCh2b2lkICpkYXRhLCB1X2ludDMyX3Qgc3BlZWQp CnsKCXN0cnVjdCBzY19jaGluZm8gKmNoID0gZGF0YTsKCXVfaW50MzJfdCBleHRjYXA7CgojaWYo MCkKCWRldmljZV9wcmludGYoY2gtPnBhcmVudC0+ZGV2LCAiaWNocGNoYW5fc2V0c3BlZWQoMHgl MDh4LCAlZClcbiIsIGRhdGEsIHNwZWVkKTsKI2VuZGlmCglleHRjYXAgPSBpY2hfcmRjZChjaC0+ cGFyZW50LCBBQzk3X1JFR0VYVF9JRCk7CglpZiAoZXh0Y2FwICYgQUM5N19FWFRDQVBfVlJBKSB7 CgkJaWNoX3dyY2QoY2gtPnBhcmVudCwgQUM5N19SRUdFWFRfRkRBQ1JBVEUsIHNwZWVkKTsKCQlj aC0+c3BkID0gaWNoX3JkY2QoY2gtPnBhcmVudCwgQUM5N19SRUdFWFRfRkRBQ1JBVEUpOwoJfQoJ ZWxzZSB7CgkJY2gtPnNwZCA9IDQ4MDAwOyAvKiBiZWZvcmUgQUMnOTcgUjIuMCAqLwoJfQojaWYo MCkKCWRldmljZV9wcmludGYoY2gtPnBhcmVudC0+ZGV2LCAiaWNocGNoYW5fc2V0c3BlZWQoKTpj aC0+c3BkID0gJWRcbiIsIGNoLT5zcGQpOwojZW5kaWYKCXJldHVybiBjaC0+c3BkOwp9CgpzdGF0 aWMgaW50CmljaHBjaGFuX3NldGJsb2Nrc2l6ZSh2b2lkICpkYXRhLCB1X2ludDMyX3QgYmxvY2tz aXplKQp7CglyZXR1cm4gYmxvY2tzaXplOwp9CgovKiB1cGRhdGUgaW5kZXggKi8Kc3RhdGljIHZv aWQKaWNocGNoYW5fdXBkYXRlKHN0cnVjdCBzY19jaGluZm8gKmNoKQp7CglzdHJ1Y3Qgc2NfaW5m byAqc2MgPSBjaC0+cGFyZW50OwoJdV9pbnQzMl90IGx2aTsKCWludCBmcDsKCWludCBsYXN0OwoJ aW50IGk7CgojaWYoMCkKCWRldmljZV9wcmludGYoY2gtPnBhcmVudC0+ZGV2LCAiaWNocGNoYW5f dXBkYXRlKClcbiIpOwojZW5kaWYKCWZwID0gY2gtPmJ1ZmZlci0+ZnA7CglsYXN0ID0gZnAgLSAx OwoJaWYgKGxhc3QgPCAwKQoJCWxhc3QgPSBJQ0hfREVGQVVMVF9CTE9DS1NaICogSUNIX0ZJRk9J TkRFWCAtIDE7CglsdmkgPSBsYXN0IC8gSUNIX0RFRkFVTFRfQkxPQ0tTWjsKCWlmIChsdmkgPj0g Y2gtPmx2aSkgewoJCWZvciAoaSA9IGNoLT5sdmk7aSA8IGx2aTtpKyspCgkJCWNoLT5pbmRleFtp XS5sZW5ndGggPQoJCQkgICAgSUNIX0JEQ19JT0MgKyBJQ0hfREVGQVVMVF9CTE9DS1NaIC8gMjsK CQljaC0+aW5kZXhbaV0ubGVuZ3RoID0gSUNIX0JEQ19JT0MgKyBJQ0hfQkRDX0JVUAoJCSAgICAr IChsYXN0ICUgSUNIX0RFRkFVTFRfQkxPQ0tTWiArIDEpIC8gMjsKCX0KCWVsc2UgewoJCWZvciAo aSA9IGNoLT5sdmk7aSA8IElDSF9GSUZPSU5ERVg7aSsrKQoJCQljaC0+aW5kZXhbaV0ubGVuZ3Ro ID0KCQkJICAgIElDSF9CRENfSU9DICsgSUNIX0RFRkFVTFRfQkxPQ0tTWiAvIDI7CgkJZm9yIChp ID0gMDtpIDwgbHZpO2krKykKCQkJY2gtPmluZGV4W2ldLmxlbmd0aCA9CgkJCSAgICBJQ0hfQkRD X0lPQyArIElDSF9ERUZBVUxUX0JMT0NLU1ogLyAyOwoJCWNoLT5pbmRleFtpXS5sZW5ndGggPSBJ Q0hfQkRDX0lPQyArIElDSF9CRENfQlVQCgkJICAgICsgKGxhc3QgJSBJQ0hfREVGQVVMVF9CTE9D S1NaICsgMSkgLyAyOwoJfQoJYnVzX3NwYWNlX3dyaXRlXzEoc2MtPm5hYm1iYXJ0LCBzYy0+bmFi bWJhcmgsIElDSF9SRUdfUE9fTFZJLCBsdmkpOwoJY2gtPmx2aSA9IGx2aTsKI2lmKDApCglkZXZp Y2VfcHJpbnRmKGNoLT5wYXJlbnQtPmRldiwgImljaHBjaGFuX3VwZGF0ZSgpOmZwID0gJWQsIGx2 aSA9ICVkXG4iLCBmcCwgbHZpKTsKI2VuZGlmCglyZXR1cm47Cn0Kc3RhdGljIHZvaWQKaWNocGNo YW5fZmlsbGJsYW5rKHN0cnVjdCBzY19jaGluZm8gKmNoKQp7CglzdHJ1Y3Qgc2NfaW5mbyAqc2Mg PSBjaC0+cGFyZW50OwoKCWNoLT5sdmkrKzsKCWlmIChjaC0+bHZpID09IElDSF9GSUZPSU5ERVgp CgkJY2gtPmx2aSA9IDA7CgliemVybyhjaC0+YnVmZmVyLT5idWYgKyBJQ0hfREVGQVVMVF9CTE9D S1NaICogY2gtPmx2aSwKCSAgICBJQ0hfREVGQVVMVF9CTE9DS1NaKTsKCWNoLT5pbmRleFtjaC0+ bHZpXS5sZW5ndGggPSBJQ0hfQkRDX0JVUCArIElDSF9ERUZBVUxUX0JMT0NLU1ogLyAyOwoJYnVz X3NwYWNlX3dyaXRlXzEoc2MtPm5hYm1iYXJ0LCBzYy0+bmFibWJhcmgsIElDSF9SRUdfUE9fTFZJ LCBjaC0+bHZpKTsKCXJldHVybjsKfQovKiBzZW1hbnRpYyBub3RlOiBtdXN0IHN0YXJ0IGF0IGJl Z2lubmluZyBvZiBidWZmZXIgKi8Kc3RhdGljIGludAppY2hwY2hhbl90cmlnZ2VyKHZvaWQgKmRh dGEsIGludCBnbykKewoJc3RydWN0IHNjX2NoaW5mbyAqY2ggPSBkYXRhOwoJc3RydWN0IHNjX2lu Zm8gKnNjID0gY2gtPnBhcmVudDsKCXVfaW50MzJfdCBjcjsKCWludCBpOwoKI2lmKDApCglkZXZp Y2VfcHJpbnRmKGNoLT5wYXJlbnQtPmRldiwgImljaHBjaGFuX3RyaWdnZXIoMHglMDh4LCAlZClc biIsIGRhdGEsIGdvKTsKI2VuZGlmCglzd2l0Y2ggKGdvKSB7CgljYXNlIFBDTVRSSUdfU1RBUlQ6 CiNpZigwKQoJCWRldmljZV9wcmludGYoY2gtPnBhcmVudC0+ZGV2LCAiaWNocGNoYW5fdHJpZ2dl cigpOlBDTVRSSUdfU1RBUlRcbiIpOwojZW5kaWYKCQljaC0+cnVuID0gMTsKCQlpY2hwY2hhbl9w b3dlcihzYywgMSk7CgkJYnVzX3NwYWNlX3dyaXRlXzQoc2MtPm5hYm1iYXJ0LCBzYy0+bmFibWJh cmgsIElDSF9SRUdfUE9fQkRCQVIsCgkJICAgICh1X2ludDMyX3QpdnRvcGh5cyhjaC0+aW5kZXgp KTsKCQljaC0+bHZpID0gSUNIX0ZJRk9JTkRFWCAtIDE7CgkJaWNocGNoYW5fdXBkYXRlKGNoKTsK CQlidXNfc3BhY2Vfd3JpdGVfMShzYy0+bmFibWJhcnQsIHNjLT5uYWJtYmFyaCwgSUNIX1JFR19Q T19DUiwKCQkgICAgSUNIX1hfQ1JfUlBCTSB8IElDSF9YX0NSX0xWQklFIHwgSUNIX1hfQ1JfSU9D RSB8CgkJICAgIElDSF9YX0NSX0ZFSUUpOwoJCWJyZWFrOwoJY2FzZSBQQ01UUklHX1NUT1A6CiNp ZigwKQoJCWRldmljZV9wcmludGYoY2gtPnBhcmVudC0+ZGV2LCAiaWNocGNoYW5fdHJpZ2dlcigp OlBDTVRSSUdfU1RPUFxuIik7CiNlbmRpZgoJCWNyID0gYnVzX3NwYWNlX3JlYWRfMShzYy0+bmFi bWJhcnQsIHNjLT5uYWJtYmFyaCwKCQkgICAgSUNIX1JFR19QT19DUik7CgkJYnVzX3NwYWNlX3dy aXRlXzEoc2MtPm5hYm1iYXJ0LCBzYy0+bmFibWJhcmgsIElDSF9SRUdfUE9fQ1IsCgkJICAgIGNy ICYgfklDSF9YX0NSX1JQQk0pOwoJCWljaHBjaGFuX3Bvd2VyKHNjLCAwKTsKCQljaC0+cnVuID0g MDsKCQlicmVhazsKCWNhc2UgUENNVFJJR19BQk9SVDoKI2lmKDApCgkJZGV2aWNlX3ByaW50Zihj aC0+cGFyZW50LT5kZXYsICJpY2hwY2hhbl90cmlnZ2VyKCk6UENNVFJJR19BQk9SVFxuIik7CiNl bmRpZgoJCWJ1c19zcGFjZV93cml0ZV8xKHNjLT5uYWJtYmFydCwgc2MtPm5hYm1iYXJoLCBJQ0hf UkVHX1BPX0NSLAoJCSAgICAwKTsKCQlidXNfc3BhY2Vfd3JpdGVfMShzYy0+bmFibWJhcnQsIHNj LT5uYWJtYmFyaCwgSUNIX1JFR19QT19DUiwKCQkgICAgSUNIX1hfQ1JfUlIpOwoJCWZvciAoaSA9 IDA7aSA8IElDSF9USU1FT1VUO2krKykgewoJCQljciA9IGJ1c19zcGFjZV9yZWFkXzEoc2MtPm5h Ym1iYXJ0LCBzYy0+bmFibWJhcmgsCgkJCSAgICBJQ0hfUkVHX1BPX0NSKTsKCQkJaWYgKGNyID09 IDApCgkJCQlicmVhazsKCQl9CgkJaWNocGNoYW5fcG93ZXIoc2MsIDApOwoJCWNoLT5ydW4gPSAw OwoJCWNoLT5sdmkgPSAwOwoJCWNoLT5jaGFubmVsLT5mbGFncyAmPSB+Q0hOX0ZfREVBRDsKCQli cmVhazsKCWRlZmF1bHQ6CgkJYnJlYWs7Cgl9CglyZXR1cm4gMDsKfQoKc3RhdGljIGludAppY2hw Y2hhbl9nZXRwdHIodm9pZCAqZGF0YSkKewoJc3RydWN0IHNjX2NoaW5mbyAqY2ggPSBkYXRhOwoJ c3RydWN0IHNjX2luZm8gKnNjID0gY2gtPnBhcmVudDsKCXVfaW50MzJfdCBjaTsKCiNpZigwKQoJ ZGV2aWNlX3ByaW50ZihjaC0+cGFyZW50LT5kZXYsICJpY2hwY2hhbl9nZXRwdHIoMHglMDh4KVxu IiwgZGF0YSk7CiNlbmRpZgoJY2kgPSBidXNfc3BhY2VfcmVhZF8xKHNjLT5uYWJtYmFydCwgc2Mt Pm5hYm1iYXJoLCBJQ0hfUkVHX1BPX0NJVik7CiNpZigwKQoJZGV2aWNlX3ByaW50ZihjaC0+cGFy ZW50LT5kZXYsICJpY2hwY2hhbl9nZXRwdHIoKTpJQ0hfUkVHX1BPX0NJViA9ICVkXG4iLCBjaSk7 CiNlbmRpZgoJLyoKCWlmIChjaSA9PSAwKQoJCXJldHVybiBJQ0hfREVGQVVMVF9CTE9DS1NaICog SUNIX0ZJRk9JTkRFWCAtIDE7CgllbHNlCgkJcmV0dXJuIElDSF9ERUZBVUxUX0JMT0NLU1ogKiBj aSAtIDE7CgkqLwoJcmV0dXJuIElDSF9ERUZBVUxUX0JMT0NLU1ogKiBjaTsKfQoKc3RhdGljIHBj bWNoYW5fY2FwcyAqCmljaHBjaGFuX2dldGNhcHModm9pZCAqZGF0YSkKewojaWYoMCkKCXN0cnVj dCBzY19jaGluZm8gKmNoID0gZGF0YTsKCWRldmljZV9wcmludGYoY2gtPnBhcmVudC0+ZGV2LCAi aWNocGNoYW5fZ2V0Y2FwcygweCUwOHgpXG4iLCBkYXRhKTsKI2VuZGlmCglyZXR1cm4gJmljaF9w bGF5Y2FwczsKfQoKLyogcmVjb3JkIGNoYW5uZWwgaW50ZXJmYWNlICovCnN0YXRpYyBpbnQKaWNo cmNoYW5fcG93ZXIoc3RydWN0IHNjX2luZm8gKnNjLCBpbnQgc3cpCnsKCXVfaW50MzJfdCBjcjsK CWludCBpOwoKCWNyID0gaWNoX3JkY2Qoc2MsIEFDOTdfUkVHX1BPV0VSKTsKCWlmIChzdykgeyAv KiBwb3dlciBvbiAqLwoJCWNyICY9IH5BQzk3X1BPV0VSX1BJTlBPV0VSOwoJCWljaF93cmNkKHNj LCBBQzk3X1JFR19QT1dFUiwgY3IpOwoJCWZvciAoaSA9IDA7aSA8IElDSF9USU1FT1VUO2krKykg ewoJCQljciA9IGljaF9yZGNkKHNjLCBBQzk3X1JFR19QT1dFUik7CgkJCWlmICgoY3IgJiBBQzk3 X1BPV0VSX1BJTlJFQURZKSAhPSAwKQoJCQkJYnJlYWs7CgkJfQoJfQoJZWxzZSB7IC8qIHBvd2Vy IG9mZiAqLwoJCWNyIHw9IEFDOTdfUE9XRVJfUElOUE9XRVI7CgkJaWNoX3dyY2Qoc2MsIEFDOTdf UkVHX1BPV0VSLCBjcik7CgkJZm9yIChpID0gMDtpIDwgSUNIX1RJTUVPVVQ7aSsrKSB7CgkJCWNy ID0gaWNoX3JkY2Qoc2MsIEFDOTdfUkVHX1BPV0VSKTsKCQkJaWYgKChjciAmIEFDOTdfUE9XRVJf UElOUkVBRFkpID09IDApCgkJCQlicmVhazsKCQl9Cgl9CglpZiAoaSA9PSBJQ0hfVElNRU9VVCkK CQlyZXR1cm4gLTE7CglyZXR1cm4gMDsKfQoKc3RhdGljIHZvaWQgKgppY2hyY2hhbl9pbml0KHZv aWQgKmRldmluZm8sIHNuZF9kYnVmICpiLCBwY21fY2hhbm5lbCAqYywgaW50IGRpcikKewoJc3Ry dWN0IHNjX2luZm8gKnNjID0gZGV2aW5mbzsKCXN0cnVjdCBzY19jaGluZm8gKmNoOwoJdV9pbnQz Ml90IGNyOwoJaW50IGk7CgoJLyogcmVzZXQgY29kZWMgKi8KCWJ1c19zcGFjZV93cml0ZV8xKHNj LT5uYWJtYmFydCwgc2MtPm5hYm1iYXJoLCBJQ0hfUkVHX1BJX0NSLCAwKTsKCWJ1c19zcGFjZV93 cml0ZV8xKHNjLT5uYWJtYmFydCwgc2MtPm5hYm1iYXJoLCBJQ0hfUkVHX1BJX0NSLAoJICAgIElD SF9YX0NSX1JSKTsKCWZvciAoaSA9IDA7aSA8IElDSF9USU1FT1VUO2krKykgewoJCWNyID0gYnVz X3NwYWNlX3JlYWRfMShzYy0+bmFibWJhcnQsIHNjLT5uYWJtYmFyaCwKCQkgICAgSUNIX1JFR19Q SV9DUik7CgkJaWYgKGNyID09IDApCgkJCWJyZWFrOwoJfQoJaWYgKGkgPT0gSUNIX1RJTUVPVVQp IHsKCQlkZXZpY2VfcHJpbnRmKHNjLT5kZXYsICJjYW5ub3QgcmVzZXQgcmVjb3JkIGNvZGVjXG4i KTsKCQlyZXR1cm4gTlVMTDsKCX0KCWlmIChpY2hyY2hhbl9wb3dlcihzYywgMSkgPT0gLTEpIHsK CQlkZXZpY2VfcHJpbnRmKHNjLT5kZXYsICJyZWNvcmQgQURDIG5vdCByZWFkeVxuIik7CgkJcmV0 dXJuIE5VTEw7Cgl9CglpY2hyY2hhbl9wb3dlcihzYywgMCk7CglpZiAoKGNoID0gbWFsbG9jKHNp emVvZigqY2gpLCBNX0RFVkJVRiwgTV9OT1dBSVQpKSA9PSBOVUxMKSB7CgkJZGV2aWNlX3ByaW50 ZihzYy0+ZGV2LCAiY2Fubm90IGFsbG9jYXRlIGNoYW5uZWwgaW5mbyBhcmVhXG4iKTsKCQlyZXR1 cm4gTlVMTDsKCX0KCWNoLT5idWZmZXIgPSBiOwoJY2gtPmNoYW5uZWwgPSBjOwoJY2gtPnBhcmVu dCA9IHNjOwoJY2gtPmRpciA9IFBDTURJUl9SRUM7CgljaC0+cnVuID0gMDsKCWNoLT5sdmkgPSAw OwoJaWYgKGljaGNoYW5faW5pdGJ1ZihjaCkpIHsKCQlkZXZpY2VfcHJpbnRmKHNjLT5kZXYsICJj YW5ub3QgYWxsb2NhdGUgY2hhbm5lbCBidWZmZXJcbiIpOwoJCXJldHVybiBOVUxMOwoJfQoJYnVz X3NwYWNlX3dyaXRlXzQoc2MtPm5hYm1iYXJ0LCBzYy0+bmFibWJhcmgsIElDSF9SRUdfUElfQkRC QVIsCgkgICAgKHVfaW50MzJfdCl2dG9waHlzKGNoLT5pbmRleCkpOwoJc2MtPnBpID0gY2g7Cglp ZiAoYm9vdHZlcmJvc2UpIHsKCQlkZXZpY2VfcHJpbnRmKHNjLT5kZXYsIlJlY29yZCBjb2RlYyBz dXBwb3J0IHJhdGUoSHopOiAiKTsKCQlmb3IgKGkgPSAwO2ljaF9yYXRlW2ldICE9IDA7aSsrKSB7 CgkJCWlmIChpY2hwY2hhbl9zZXRzcGVlZChjaCwgaWNoX3JhdGVbaV0pID09IGljaF9yYXRlW2ld KSB7CgkJCQlwcmludGYoIiVkICIsIGljaF9yYXRlW2ldKTsKCQkJfQoJCX0KCQlwcmludGYoIlxu Iik7Cgl9CglyZXR1cm4gY2g7Cn0KCnN0YXRpYyBpbnQKaWNocmNoYW5fc2V0ZGlyKHZvaWQgKmRh dGEsIGludCBkaXIpCnsKCXJldHVybiAwOwp9CgpzdGF0aWMgaW50CmljaHJjaGFuX3NldGZvcm1h dCh2b2lkICpkYXRhLCB1X2ludDMyX3QgZm9ybWF0KQp7CglzdHJ1Y3Qgc2NfY2hpbmZvICpjaCA9 IGRhdGE7CgoJY2gtPmZtdCA9IGZvcm1hdDsKCglyZXR1cm4gMDsKfQoKc3RhdGljIGludAppY2hy Y2hhbl9zZXRzcGVlZCh2b2lkICpkYXRhLCB1X2ludDMyX3Qgc3BlZWQpCnsKCXN0cnVjdCBzY19j aGluZm8gKmNoID0gZGF0YTsKCXVfaW50MzJfdCBleHRjYXA7CgoJZXh0Y2FwID0gaWNoX3JkY2Qo Y2gtPnBhcmVudCwgQUM5N19SRUdFWFRfSUQpOwoJaWYgKGV4dGNhcCAmIEFDOTdfRVhUQ0FQX1ZS TSkgewoJCWljaF93cmNkKGNoLT5wYXJlbnQsIEFDOTdfUkVHRVhUX0xBRENSQVRFLCBzcGVlZCk7 CgkJY2gtPnNwZCA9IGljaF9yZGNkKGNoLT5wYXJlbnQsIEFDOTdfUkVHRVhUX0xBRENSQVRFKTsK CX0KCWVsc2UgewoJCWNoLT5zcGQgPSA0ODAwMDsgLyogYmVmb3JlIEFDJzk3IFIyLjAgKi8KCX0K CglyZXR1cm4gY2gtPnNwZDsKfQoKc3RhdGljIGludAppY2hyY2hhbl9zZXRibG9ja3NpemUodm9p ZCAqZGF0YSwgdV9pbnQzMl90IGJsb2Nrc2l6ZSkKewoJcmV0dXJuIGJsb2Nrc2l6ZTsKfQoKLyog c2VtYW50aWMgbm90ZTogbXVzdCBzdGFydCBhdCBiZWdpbm5pbmcgb2YgYnVmZmVyICovCnN0YXRp YyBpbnQKaWNocmNoYW5fdHJpZ2dlcih2b2lkICpkYXRhLCBpbnQgZ28pCnsKCXN0cnVjdCBzY19j aGluZm8gKmNoID0gZGF0YTsKCXN0cnVjdCBzY19pbmZvICpzYyA9IGNoLT5wYXJlbnQ7Cgl1X2lu dDMyX3QgY3I7CglpbnQgaTsKCglzd2l0Y2ggKGdvKSB7CgljYXNlIFBDTVRSSUdfU1RBUlQ6CgkJ Y2gtPnJ1biA9IDE7CgkJaWNocmNoYW5fcG93ZXIoc2MsIDEpOwoJCWJ1c19zcGFjZV93cml0ZV80 KHNjLT5uYWJtYmFydCwgc2MtPm5hYm1iYXJoLCBJQ0hfUkVHX1BJX0JEQkFSLAoJCSAgICAodV9p bnQzMl90KXZ0b3BoeXMoY2gtPmluZGV4KSk7CgkJY2gtPmx2aSA9IElDSF9GSUZPSU5ERVggLSAx OwoJCWJ1c19zcGFjZV93cml0ZV8xKHNjLT5uYWJtYmFydCwgc2MtPm5hYm1iYXJoLCBJQ0hfUkVH X1BJX0xWSSwKCQkgICAgY2gtPmx2aSk7CgkJYnVzX3NwYWNlX3dyaXRlXzEoc2MtPm5hYm1iYXJ0 LCBzYy0+bmFibWJhcmgsIElDSF9SRUdfUElfQ1IsCgkJICAgIElDSF9YX0NSX1JQQk0gfCBJQ0hf WF9DUl9MVkJJRSB8IElDSF9YX0NSX0lPQ0UgfAoJCSAgICBJQ0hfWF9DUl9GRUlFKTsKCQlicmVh azsKCWNhc2UgUENNVFJJR19TVE9QOgoJCWNyID0gYnVzX3NwYWNlX3JlYWRfMShzYy0+bmFibWJh cnQsIHNjLT5uYWJtYmFyaCwKCQkgICAgSUNIX1JFR19QSV9DUik7CgkJYnVzX3NwYWNlX3dyaXRl XzEoc2MtPm5hYm1iYXJ0LCBzYy0+bmFibWJhcmgsIElDSF9SRUdfUElfQ1IsCgkJICAgIGNyICYg fklDSF9YX0NSX1JQQk0pOwoJCWljaHJjaGFuX3Bvd2VyKHNjLCAwKTsKCQljaC0+cnVuID0gMDsK CQlicmVhazsKCWNhc2UgUENNVFJJR19BQk9SVDoKCQlidXNfc3BhY2Vfd3JpdGVfMShzYy0+bmFi bWJhcnQsIHNjLT5uYWJtYmFyaCwgSUNIX1JFR19QSV9DUiwKCQkgICAgMCk7CgkJYnVzX3NwYWNl X3dyaXRlXzEoc2MtPm5hYm1iYXJ0LCBzYy0+bmFibWJhcmgsIElDSF9SRUdfUElfQ1IsCgkJICAg IElDSF9YX0NSX1JSKTsKCQlmb3IgKGkgPSAwO2kgPCBJQ0hfVElNRU9VVDtpKyspIHsKCQkJY3Ig PSBidXNfc3BhY2VfcmVhZF8xKHNjLT5uYWJtYmFydCwgc2MtPm5hYm1iYXJoLAoJCQkgICAgSUNI X1JFR19QSV9DUik7CgkJCWlmIChjciA9PSAwKQoJCQkJYnJlYWs7CgkJfQoJCWljaHJjaGFuX3Bv d2VyKHNjLCAwKTsKCQljaC0+cnVuID0gMDsKCQljaC0+bHZpID0gMDsKCQljaC0+Y2hhbm5lbC0+ ZmxhZ3MgJj0gfkNITl9GX0RFQUQ7CgkJYnJlYWs7CglkZWZhdWx0OgoJCWJyZWFrOwoJfQoJcmV0 dXJuIDA7Cn0KCnN0YXRpYyBpbnQKaWNocmNoYW5fZ2V0cHRyKHZvaWQgKmRhdGEpCnsKCXN0cnVj dCBzY19jaGluZm8gKmNoID0gZGF0YTsKCXN0cnVjdCBzY19pbmZvICpzYyA9IGNoLT5wYXJlbnQ7 Cgl1X2ludDMyX3QgY2k7CgoJY2kgPSBidXNfc3BhY2VfcmVhZF8xKHNjLT5uYWJtYmFydCwgc2Mt Pm5hYm1iYXJoLCBJQ0hfUkVHX1BJX0NJVik7CglyZXR1cm4gY2kgKiBJQ0hfREVGQVVMVF9CTE9D S1NaOwp9CgpzdGF0aWMgcGNtY2hhbl9jYXBzICoKaWNocmNoYW5fZ2V0Y2Fwcyh2b2lkICpkYXRh KQp7CglyZXR1cm4gJmljaF9yZWNjYXBzOwp9CgovKiBUaGUgaW50ZXJydXB0IGhhbmRsZXIgKi8K c3RhdGljIHZvaWQKaWNoX2ludHIodm9pZCAqcCkKewoJc3RydWN0IHNjX2luZm8gKnNjID0gKHN0 cnVjdCBzY19pbmZvICopcDsKCXN0cnVjdCBzY19jaGluZm8gKmNoOwoJdV9pbnQzMl90IGNwOwoJ dV9pbnQzMl90IHNnOwoJdV9pbnQzMl90IHN0OwoJdV9pbnQzMl90IGx2aTsKCiNpZigwKQoJZGV2 aWNlX3ByaW50ZihzYy0+ZGV2LCAiaWNoX2ludHIoMHglMDh4KVxuIiwgcCk7CiNlbmRpZgoJLyog Y2hlY2sgaW50ZXJmYWNlIHN0YXR1cyAqLwoJc2cgPSBidXNfc3BhY2VfcmVhZF80KHNjLT5uYWJt YmFydCwgc2MtPm5hYm1iYXJoLCBJQ0hfUkVHX0dMT0JfU1RBKTsKI2lmKDApCglkZXZpY2VfcHJp bnRmKHNjLT5kZXYsICJpY2hfaW50cigpOlJFR19HTE9CX1NUQSA9IDB4JTA4eFxuIiwgc2cpOwoj ZW5kaWYKCWlmIChzZyAmIElDSF9HTE9CX1NUQV9QT0lOVCkgewoJCS8qIFBDTSBPdXQgSU5UZXJy dXB0ICovCgkJLyogbWFzayBpbnRlcnJ1cHQgKi8KCQljcCA9IGJ1c19zcGFjZV9yZWFkXzEoc2Mt Pm5hYm1iYXJ0LCBzYy0+bmFibWJhcmgsCgkJICAgIElDSF9SRUdfUE9fQ1IpOwoJCWNwICY9IH4o SUNIX1hfQ1JfTFZCSUUgfCBJQ0hfWF9DUl9JT0NFIHwgSUNIX1hfQ1JfRkVJRSk7CgkJYnVzX3Nw YWNlX3dyaXRlXzEoc2MtPm5hYm1iYXJ0LCBzYy0+bmFibWJhcmgsIElDSF9SRUdfUE9fQ1IsCgkJ ICAgIGNwKTsKCQkvKiBjaGVjayBjaGFubmVsIHN0YXR1cyAqLwoJCWNoID0gc2MtPnBvOwoJCXN0 ID0gYnVzX3NwYWNlX3JlYWRfMihzYy0+bmFibWJhcnQsIHNjLT5uYWJtYmFyaCwKCQkgICAgSUNI X1JFR19QT19TUik7CiNpZigwKQoJCWRldmljZV9wcmludGYoc2MtPmRldiwgImljaF9pbnRyKCk6 UkVHX1BPX1NSID0gMHglMDJ4XG4iLCBzdCk7CiNlbmRpZgoJCWlmIChzdCAmIChJQ0hfWF9TUl9C Q0lTIHwgSUNIX1hfU1JfTFZCQ0kpKSB7CgkJCS8qIHBsYXkgYnVmZmVyIGJsb2NrIGNvbXBsZXRl ICovCgkJCWlmIChzdCAmIElDSF9YX1NSX0xWQkNJKQoJCQkJbHZpID0gY2gtPmx2aTsKCQkJLyog dXBkYXRlIGJ1ZmZlciAqLwoJCQljaG5faW50cihjaC0+Y2hhbm5lbCk7CgkJCWljaHBjaGFuX3Vw ZGF0ZShjaCk7CgkJCWlmIChzdCAmIElDSF9YX1NSX0xWQkNJKSB7CgkJCQkvKiByZS1jaGVjayB1 bmRlcmZsb3cgc3RhdHVzICovCgkJCQlpZiAobHZpID09IGNoLT5sdmkpIHsKCQkJCQljaC0+YnVm ZmVyLT51bmRlcmZsb3cgPSAxOwoJCQkJCWljaHBjaGFuX2ZpbGxibGFuayhjaCk7CgkJCQl9CgkJ CX0KCQl9CgkJLyogY2xlYXIgc3RhdHVzIGJpdCAqLwoJCWJ1c19zcGFjZV93cml0ZV8yKHNjLT5u YWJtYmFydCwgc2MtPm5hYm1iYXJoLCBJQ0hfUkVHX1BPX1NSLAoJCSAgICBzdCAmIChJQ0hfWF9T Ul9GSUZPRSB8IElDSF9YX1NSX0JDSVMgfCBJQ0hfWF9TUl9MVkJDSSkpOwoJCS8qIHNldCBpbnRl cnJ1cHQgKi8KCQljcCB8PSAoSUNIX1hfQ1JfTFZCSUUgfCBJQ0hfWF9DUl9JT0NFIHwgSUNIX1hf Q1JfRkVJRSk7CgkJYnVzX3NwYWNlX3dyaXRlXzEoc2MtPm5hYm1iYXJ0LCBzYy0+bmFibWJhcmgs IElDSF9SRUdfUE9fQ1IsCgkJICAgIGNwKTsKCX0KCWlmIChzZyAmIElDSF9HTE9CX1NUQV9QSUlO VCkgewoJCS8qIFBDTSBJbiBJTlRlcnJ1cHQgKi8KCQkvKiBtYXNrIGludGVycnVwdCAqLwoJCWNw ID0gYnVzX3NwYWNlX3JlYWRfMShzYy0+bmFibWJhcnQsIHNjLT5uYWJtYmFyaCwKCQkgICAgSUNI X1JFR19QSV9DUik7CgkJY3AgJj0gfihJQ0hfWF9DUl9MVkJJRSB8IElDSF9YX0NSX0lPQ0UgfCBJ Q0hfWF9DUl9GRUlFKTsKCQlidXNfc3BhY2Vfd3JpdGVfMShzYy0+bmFibWJhcnQsIHNjLT5uYWJt YmFyaCwgSUNIX1JFR19QSV9DUiwKCQkgICAgY3ApOwoJCS8qIGNoZWNrIGNoYW5uZWwgc3RhdHVz ICovCgkJY2ggPSBzYy0+cGk7CgkJc3QgPSBidXNfc3BhY2VfcmVhZF8yKHNjLT5uYWJtYmFydCwg c2MtPm5hYm1iYXJoLAoJCSAgICBJQ0hfUkVHX1BJX1NSKTsKI2lmKDApCgkJZGV2aWNlX3ByaW50 ZihzYy0+ZGV2LCAiaWNoX2ludHIoKTpSRUdfUElfU1IgPSAweCUwMnhcbiIsIHN0KTsKI2VuZGlm CgkJaWYgKHN0ICYgKElDSF9YX1NSX0JDSVMgfCBJQ0hfWF9TUl9MVkJDSSkpIHsKCQkJLyogcmVj b3JkIGJ1ZmZlciBibG9jayBmaWxsZWQgKi8KCQkJaWYgKHN0ICYgSUNIX1hfU1JfTFZCQ0kpCgkJ CQlsdmkgPSBjaC0+bHZpOwoJCQkvKiB1cGRhdGUgc3BhY2UgKi8KCQkJY2huX2ludHIoY2gtPmNo YW5uZWwpOwoJCQljaC0+bHZpID0gY2gtPmJ1ZmZlci0+cnAgLyBJQ0hfREVGQVVMVF9CTE9DS1Na IC0gMTsKCQkJaWYgKGNoLT5sdmkgPCAwKQoJCQkJY2gtPmx2aSA9IElDSF9GSUZPSU5ERVggLSAx OwoJCQlidXNfc3BhY2Vfd3JpdGVfMShzYy0+bmFibWJhcnQsIHNjLT5uYWJtYmFyaCwKCQkJICAg IElDSF9SRUdfUElfTFZJLCBjaC0+bHZpKTsKCQkJaWYgKHN0ICYgSUNIX1hfU1JfTFZCQ0kpIHsK CQkJCS8qIHJlLWNoZWNrIHVuZGVyZmxvdyBzdGF0dXMgKi8KCQkJCWlmIChsdmkgPT0gY2gtPmx2 aSkgewoJCQkJCWNoLT5sdmkrKzsKCQkJCQlpZiAoY2gtPmx2aSA9PSBJQ0hfRklGT0lOREVYKQoJ CQkJCQljaC0+bHZpID0gMDsKCQkJCQlidXNfc3BhY2Vfd3JpdGVfMShzYy0+bmFibWJhcnQsCgkJ CQkJICAgIHNjLT5uYWJtYmFyaCwgSUNIX1JFR19QSV9MVkksCgkJCQkJICAgIGNoLT5sdmkpOwoJ CQkJfQoJCQl9CgkJfQoJCS8qIGNsZWFyIHN0YXR1cyBiaXQgKi8KCQlidXNfc3BhY2Vfd3JpdGVf MihzYy0+bmFibWJhcnQsIHNjLT5uYWJtYmFyaCwgSUNIX1JFR19QSV9TUiwKCQkgICAgc3QgJiAo SUNIX1hfU1JfRklGT0UgfCBJQ0hfWF9TUl9CQ0lTIHwgSUNIX1hfU1JfTFZCQ0kpKTsKCQkvKiBz ZXQgaW50ZXJydXB0ICovCgkJY3AgfD0gKElDSF9YX0NSX0xWQklFIHwgSUNIX1hfQ1JfSU9DRSB8 IElDSF9YX0NSX0ZFSUUpOwoJCWJ1c19zcGFjZV93cml0ZV8xKHNjLT5uYWJtYmFydCwgc2MtPm5h Ym1iYXJoLCBJQ0hfUkVHX1BJX0NSLAoJCSAgICBjcCk7Cgl9Cn0KCi8qIC0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tICov CgovKgogKiBQcm9iZSBhbmQgYXR0YWNoIHRoZSBjYXJkCiAqLwoKc3RhdGljIGludAppY2hfaW5p dChzdHJ1Y3Qgc2NfaW5mbyAqc2MpCnsKCXVfaW50MzJfdCBzdGF0OwoJdV9pbnQzMl90IHNhdmU7 CgoJYnVzX3NwYWNlX3dyaXRlXzQoc2MtPm5hYm1iYXJ0LCBzYy0+bmFibWJhcmgsCgkgICAgSUNI X1JFR19HTE9CX0NOVCwgSUNIX0dMT0JfQ1RMX0NPTEQpOwoJREVMQVkoNjAwMDAwKTsKCXN0YXQg PSBidXNfc3BhY2VfcmVhZF80KHNjLT5uYWJtYmFydCwgc2MtPm5hYm1iYXJoLCBJQ0hfUkVHX0dM T0JfU1RBKTsKCWlmICgoc3RhdCAmIElDSF9HTE9CX1NUQV9QQ1IpID09IDApCgkJcmV0dXJuIC0x OwoJYnVzX3NwYWNlX3dyaXRlXzQoc2MtPm5hYm1iYXJ0LCBzYy0+bmFibWJhcmgsCgkgICAgSUNI X1JFR19HTE9CX0NOVCwgSUNIX0dMT0JfQ1RMX0NPTEQgfCBJQ0hfR0xPQl9DVExfUFJFUyk7Cglz YXZlID0gYnVzX3NwYWNlX3JlYWRfMihzYy0+bmFtYmFydCwgc2MtPm5hbWJhcmgsIEFDOTdfTUlY X01BU1RFUik7CglidXNfc3BhY2Vfd3JpdGVfMihzYy0+bmFtYmFydCwgc2MtPm5hbWJhcmgsIEFD OTdfTUlYX01BU1RFUiwKCQkJICBBQzk3X01VVEUpOwoJaWYgKGljaF93YWl0Y2Qoc2MpID09IEVU SU1FRE9VVCkKCQlyZXR1cm4gLTE7CglERUxBWSg2MDApOyAvKiBpdCBpcyBuZWVkIGZvciBzb21l IHN5c3RlbSAqLwoJc3RhdCA9IGJ1c19zcGFjZV9yZWFkXzIoc2MtPm5hbWJhcnQsIHNjLT5uYW1i YXJoLCBBQzk3X01JWF9NQVNURVIpOwoJaWYgKHN0YXQgIT0gQUM5N19NVVRFKQoJCXJldHVybiAt MTsKCWJ1c19zcGFjZV93cml0ZV8yKHNjLT5uYW1iYXJ0LCBzYy0+bmFtYmFyaCwgQUM5N19NSVhf TUFTVEVSLCBzYXZlKTsKCXJldHVybiAwOwp9CgpzdGF0aWMgaW50CmljaF9maW5kZGV2KHVfaW50 MzJfdCBkZXYsIHVfaW50MzJfdCBzdWJkZXYpCnsKCWludCBpOwoKCWZvciAoaSA9IDA7IGljaF9k ZXZzW2ldLmRldjsgaSsrKSB7CgkJaWYgKGljaF9kZXZzW2ldLmRldiA9PSBkZXYgJiYKCQkgICAg KGljaF9kZXZzW2ldLnN1YmRldiA9PSBzdWJkZXYgfHwgaWNoX2RldnNbaV0uc3ViZGV2ID09IDAp KQoJCQlyZXR1cm4gaTsKCX0KCXJldHVybiAtMTsKfQoKc3RhdGljIGludAppY2hfcGNpX3Byb2Jl KGRldmljZV90IGRldikKewoJaW50IGk7Cgl1X2ludDMyX3Qgc3ViZGV2OwoKCXN1YmRldiA9IChw Y2lfZ2V0X3N1YmRldmljZShkZXYpIDw8IDE2KSB8IHBjaV9nZXRfc3VidmVuZG9yKGRldik7Cglp ID0gaWNoX2ZpbmRkZXYocGNpX2dldF9kZXZpZChkZXYpLCBzdWJkZXYpOwoJaWYgKGkgPj0gMCkg ewoJCWRldmljZV9zZXRfZGVzYyhkZXYsIGljaF9kZXZzW2ldLm5hbWUpOwoJCXJldHVybiAwOwoJ fSBlbHNlCgkJcmV0dXJuIEVOWElPOwp9CgpzdGF0aWMgaW50CmljaF9wY2lfYXR0YWNoKGRldmlj ZV90IGRldikKewoJdV9pbnQzMl90CWRhdGE7Cgl1X2ludDMyX3QJc3ViZGV2OwoJdV9pbnQzMl90 CWV4dGNhcDsKCXN0cnVjdCBzY19pbmZvICpzYzsKCWNoYXIgCQlzdGF0dXNbU05EX1NUQVRVU0xF Tl07CgoJaWYgKChzYyA9IG1hbGxvYyhzaXplb2YoKnNjKSwgTV9ERVZCVUYsIE1fTk9XQUlUKSkg PT0gTlVMTCkgewoJCWRldmljZV9wcmludGYoZGV2LCAiY2Fubm90IGFsbG9jYXRlIHNvZnRjXG4i KTsKCQlyZXR1cm4gRU5YSU87Cgl9CgoJYnplcm8oc2MsIHNpemVvZigqc2MpKTsKCXNjLT5kZXYg PSBkZXY7CglzdWJkZXYgPSAocGNpX2dldF9zdWJkZXZpY2UoZGV2KSA8PCAxNikgfCBwY2lfZ2V0 X3N1YnZlbmRvcihkZXYpOwoJc2MtPnR5cGUgPSBpY2hfZmluZGRldihwY2lfZ2V0X2RldmlkKGRl diksIHN1YmRldik7CglzYy0+cmV2ID0gcGNpX2dldF9yZXZpZChkZXYpOwoKCWRhdGEgPSBwY2lf cmVhZF9jb25maWcoZGV2LCBQQ0lSX0NPTU1BTkQsIDIpOwoJZGF0YSB8PSAoUENJTV9DTURfUE9S VEVOIHwgUENJTV9DTURfTUVNRU4gfCBQQ0lNX0NNRF9CVVNNQVNURVJFTik7CglwY2lfd3JpdGVf Y29uZmlnKGRldiwgUENJUl9DT01NQU5ELCBkYXRhLCAyKTsKCWRhdGEgPSBwY2lfcmVhZF9jb25m aWcoZGV2LCBQQ0lSX0NPTU1BTkQsIDIpOwoKCXNjLT5uYW1iYXJpZCA9IFBDSVJfTkFNQkFSOwoJ c2MtPm5hYm1iYXJpZCA9IFBDSVJfTkFCTUJBUjsKCXNjLT5uYW1iYXIgPSBidXNfYWxsb2NfcmVz b3VyY2UoZGV2LCBTWVNfUkVTX0lPUE9SVCwKCSAgICAmc2MtPm5hbWJhcmlkLCAwLCB+MCwgMjU2 LCBSRl9BQ1RJVkUpOwoJc2MtPm5hYm1iYXIgPSBidXNfYWxsb2NfcmVzb3VyY2UoZGV2LCBTWVNf UkVTX0lPUE9SVCwKCSAgICAmc2MtPm5hYm1iYXJpZCwgMCwgfjAsIDY0LCBSRl9BQ1RJVkUpOwoJ aWYgKCFzYy0+bmFtYmFyIHx8ICFzYy0+bmFibWJhcikgewoJCWRldmljZV9wcmludGYoZGV2LCAi dW5hYmxlIHRvIG1hcCBJTyBwb3J0IHNwYWNlXG4iKTsKCQlnb3RvIGJhZDsKCX0KCXNjLT5uYW1i YXJ0ID0gcm1hbl9nZXRfYnVzdGFnKHNjLT5uYW1iYXIpOwoJc2MtPm5hbWJhcmggPSBybWFuX2dl dF9idXNoYW5kbGUoc2MtPm5hbWJhcik7CglzYy0+bmFibWJhcnQgPSBybWFuX2dldF9idXN0YWco c2MtPm5hYm1iYXIpOwoJc2MtPm5hYm1iYXJoID0gcm1hbl9nZXRfYnVzaGFuZGxlKHNjLT5uYWJt YmFyKTsKCglpZiAoYnVzX2RtYV90YWdfY3JlYXRlKC8qcGFyZW50Ki9OVUxMLCAvKmFsaWdubWVu dCovNCwgLypib3VuZGFyeSovMCwKCSAgICAvKmxvd2FkZHIqL0JVU19TUEFDRV9NQVhBRERSXzMy QklULAoJICAgIC8qaGlnaGFkZHIqL0JVU19TUEFDRV9NQVhBRERSLAoJICAgIC8qZmlsdGVyKi9O VUxMLCAvKmZpbHRlcmFyZyovTlVMTCwKCSAgICAvKm1heHNpemUqLzY1NTM2LCAvKm5zZWdtZW50 cyovMSwgLyptYXhzZWdzeiovMHgzZmZmZiwKCSAgICAvKmZsYWdzKi8wLCAmc2MtPnBhcmVudF9k bWF0KSAhPSAwKSB7CgkJZGV2aWNlX3ByaW50ZihkZXYsICJ1bmFibGUgdG8gY3JlYXRlIGRtYSB0 YWdcbiIpOwoJCWdvdG8gYmFkOwoJfQoKCWlmIChpY2hfaW5pdChzYykgPT0gLTEpIHsKCQlkZXZp Y2VfcHJpbnRmKGRldiwgInVuYWJsZSB0byBpbml0aWFsaXplIHRoZSBjYXJkXG4iKTsKCQlnb3Rv IGJhZDsKCX0KCglzYy0+Y29kZWMgPSBhYzk3X2NyZWF0ZShkZXYsIHNjLCBOVUxMLCBpY2hfcmRj ZCwgaWNoX3dyY2QpOwoJaWYgKHNjLT5jb2RlYyA9PSBOVUxMKQoJCWdvdG8gYmFkOwoJbWl4ZXJf aW5pdChkZXYsICZhYzk3X21peGVyLCBzYy0+Y29kZWMpOwoJLyogY2hlY2sgYW5kIHNldCBWUkEg ZnVuY3Rpb24gKi8KCWRhdGEgPSBpY2hfcmRjZChzYywgQUM5N19SRUdFWFRfSUQpOwoJZXh0Y2Fw ID0gMDsKCWlmIChkYXRhICYgQUM5N19FWFRDQVBfVlJBKQoJCWV4dGNhcCA9IEFDOTdfRVhUQ0FQ X1ZSQTsKCWlmIChkYXRhICYgQUM5N19FWFRDQVBfVlJNKQoJCWV4dGNhcCB8PSBBQzk3X0VYVENB UF9WUk07CglpY2hfd3JjZChzYywgQUM5N19SRUdFWFRfU1RBVCwgZXh0Y2FwKTsKCglzYy0+aXJx aWQgPSAwOwoJc2MtPmlycSA9IGJ1c19hbGxvY19yZXNvdXJjZShkZXYsIFNZU19SRVNfSVJRLCAm c2MtPmlycWlkLAoJCQkJIDAsIH4wLCAxLCBSRl9BQ1RJVkUgfCBSRl9TSEFSRUFCTEUpOwoJaWYg KCFzYy0+aXJxIHx8CgkgICAgYnVzX3NldHVwX2ludHIoZGV2LCBzYy0+aXJxLCBJTlRSX1RZUEVf VFRZLCBpY2hfaW50ciwgc2MsICZzYy0+aWgpKSB7CgkJZGV2aWNlX3ByaW50ZihkZXYsICJ1bmFi bGUgdG8gbWFwIGludGVycnVwdFxuIik7CgkJZ290byBiYWQ7Cgl9CgoJc25wcmludGYoc3RhdHVz LCBTTkRfU1RBVFVTTEVOLAoJICAgICJhdCBpbyAweCVseC0weCVseCwgMHglbHgtMHglbHggaXJx ICVsZCIsCgkgICAgcm1hbl9nZXRfc3RhcnQoc2MtPm5hbWJhciksIHJtYW5fZ2V0X2VuZChzYy0+ bmFtYmFyKSwKCSAgICBybWFuX2dldF9zdGFydChzYy0+bmFibWJhciksIHJtYW5fZ2V0X2VuZChz Yy0+bmFibWJhciksCgkgICAgcm1hbl9nZXRfc3RhcnQoc2MtPmlycSkpOwoKCWlmIChwY21fcmVn aXN0ZXIoZGV2LCBzYywgMSwgMSkpCgkJZ290byBiYWQ7CglwY21fYWRkY2hhbihkZXYsIFBDTURJ Ul9QTEFZLCAmaWNoX3BjaGFudGVtcGxhdGUsIHNjKTsKCXBjbV9hZGRjaGFuKGRldiwgUENNRElS X1JFQywgJmljaF9yY2hhbnRlbXBsYXRlLCBzYyk7CglwY21fc2V0c3RhdHVzKGRldiwgc3RhdHVz KTsKCglyZXR1cm4gMDsKCmJhZDoKCWlmIChzYy0+bmFtYmFyKQoJCWJ1c19yZWxlYXNlX3Jlc291 cmNlKGRldiwgU1lTX1JFU19JT1BPUlQsCgkJICAgIHNjLT5uYW1iYXJpZCwgc2MtPm5hbWJhcik7 CglpZiAoc2MtPm5hYm1iYXIpCgkJYnVzX3JlbGVhc2VfcmVzb3VyY2UoZGV2LCBTWVNfUkVTX0lP UE9SVCwKCQkgICAgc2MtPm5hYm1iYXJpZCwgc2MtPm5hYm1iYXIpOwoJaWYgKHNjLT5paCkKCQli dXNfdGVhcmRvd25faW50cihkZXYsIHNjLT5pcnEsIHNjLT5paCk7CglpZiAoc2MtPmlycSkKCQli dXNfcmVsZWFzZV9yZXNvdXJjZShkZXYsIFNZU19SRVNfSVJRLCBzYy0+aXJxaWQsIHNjLT5pcnEp OwoJZnJlZShzYywgTV9ERVZCVUYpOwoJcmV0dXJuIEVOWElPOwp9CgpzdGF0aWMgaW50CmljaF9w Y2lfcmVzdW1lKGRldmljZV90IGRldikKewoJc25kZGV2X2luZm8gKmQ7CglzdHJ1Y3Qgc2NfaW5m byAqc2M7Cgl1X2ludDMyX3QJZGF0YTsKCXVfaW50MzJfdAlleHRjYXA7CgoJc2MgPSBwY21fZ2V0 ZGV2aW5mbyhkZXYpOwoKCS8qIFJlaW5pdCBhdWRpbyBkZXZpY2UgKi8KICAgIAlpZiAoaWNoX2lu aXQoc2MpID09IC0xKSB7CgkJZGV2aWNlX3ByaW50ZihkZXYsICJ1bmFibGUgdG8gcmVpbml0aWFs aXplIHRoZSBjYXJkXG4iKTsKCQlyZXR1cm4gRU5YSU87Cgl9CgkvKiBSZWluaXQgbWl4ZXIgKi8K ICAgIAlpZiAobWl4ZXJfcmVpbml0KGRldikgPT0gLTEpIHsKCQlkZXZpY2VfcHJpbnRmKGRldiwg InVuYWJsZSB0byByZWluaXRpYWxpemUgdGhlIG1peGVyXG4iKTsKCQlyZXR1cm4gRU5YSU87Cgl9 CgkvKiBjaGVjayBhbmQgc2V0IFZSQSBmdW5jdGlvbiAqLwoJZGF0YSA9IGljaF9yZGNkKHNjLCBB Qzk3X1JFR0VYVF9JRCk7CglleHRjYXAgPSAwOwoJaWYgKGRhdGEgJiBBQzk3X0VYVENBUF9WUkEp CgkJZXh0Y2FwID0gQUM5N19FWFRDQVBfVlJBOwoJaWYgKGRhdGEgJiBBQzk3X0VYVENBUF9WUk0p CgkJZXh0Y2FwIHw9IEFDOTdfRVhUQ0FQX1ZSTTsKCWljaF93cmNkKHNjLCBBQzk3X1JFR0VYVF9T VEFULCBleHRjYXApOwoJcmV0dXJuIDA7Cn0KCnN0YXRpYyBkZXZpY2VfbWV0aG9kX3QgaWNoX21l dGhvZHNbXSA9IHsKCS8qIERldmljZSBpbnRlcmZhY2UgKi8KCURFVk1FVEhPRChkZXZpY2VfcHJv YmUsCQlpY2hfcGNpX3Byb2JlKSwKCURFVk1FVEhPRChkZXZpY2VfYXR0YWNoLAlpY2hfcGNpX2F0 dGFjaCksCglERVZNRVRIT0QoZGV2aWNlX3Jlc3VtZSwJaWNoX3BjaV9yZXN1bWUpLAoJeyAwLCAw IH0KfTsKCnN0YXRpYyBkcml2ZXJfdCBpY2hfZHJpdmVyID0gewoJInBjbSIsCglpY2hfbWV0aG9k cywKCXNpemVvZihzbmRkZXZfaW5mbyksCn07CgpzdGF0aWMgZGV2Y2xhc3NfdCBwY21fZGV2Y2xh c3M7CgpEUklWRVJfTU9EVUxFKHNuZF9pY2gsIHBjaSwgaWNoX2RyaXZlciwgcGNtX2RldmNsYXNz LCAwLCAwKTsKTU9EVUxFX0RFUEVORChzbmRfaWNoLCBzbmRfcGNtLCBQQ01fTUlOVkVSLCBQQ01f UFJFRlZFUixQQ01fTUFYVkVSKTsKTU9EVUxFX1ZFUlNJT04oc25kX2ljaCwgMSk7Cg== --Boundary-=_WfAZyzAZOHsNGHcxSfUBSnsNWfUJ-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 9:31:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dayspring.firedrake.org (dayspring.firedrake.org [195.82.105.251]) by hub.freebsd.org (Postfix) with ESMTP id 7774B37B4CF for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 09:30:31 -0800 (PST) Received: from float by dayspring.firedrake.org with local (Exim 3.12 #1 (Debian)) id 13wSrY-0005zm-00; Thu, 16 Nov 2000 17:30:16 +0000 Date: Thu, 16 Nov 2000 17:30:16 +0000 To: Stefan `Sec` Zehl <sec@42.org> Cc: Peter Pentchev <roam@orbitel.bg>, freebsd-hackers@freebsd.org Subject: Re: changing a running process's credentials Message-ID: <20001116173016.B22216@firedrake.org> References: <20001115161316.C309@ringworld.oblivion.bg> <20001115190135.E309@ringworld.oblivion.bg> <20001116101250.A14200@matrix.42.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001116101250.A14200@matrix.42.org>; from sec@42.org on Thu, Nov 16, 2000 at 10:12:50AM +0100 From: void <float@firedrake.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone remember the article in Phrack, issue 53 I think, about speaking Forth to a Sun's boot-prom in order to write a '0' into the UID member of one's shell's struct proc? -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 10:14:42 2000 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 41B2537B479 for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 10:14:40 -0800 (PST) Received: from shell-2.enteract.com (dscheidt@shell-2.enteract.com [207.229.143.41]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id MAA33932; Thu, 16 Nov 2000 12:14:32 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Thu, 16 Nov 2000 12:14:31 -0600 (CST) From: David Scheidt <dscheidt@enteract.com> To: void <float@firedrake.org> Cc: Stefan `Sec` Zehl <sec@42.org>, Peter Pentchev <roam@orbitel.bg>, freebsd-hackers@freebsd.org Subject: Re: changing a running process's credentials In-Reply-To: <20001116173016.B22216@firedrake.org> Message-ID: <Pine.NEB.3.96.1001116121153.22730B-100000@shell-2.enteract.com> 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, 16 Nov 2000, void wrote: :Does anyone remember the article in Phrack, issue 53 I think, about :speaking Forth to a Sun's boot-prom in order to write a '0' into the UID :member of one's shell's struct proc? Yes. It works a treat. Similar steps let you do the same thing with DDB or (presumably, haven't tried) remote gdb. 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 16 10:38: 1 2000 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 B9B3437B479 for <freebsd-hackers@FreeBSD.ORG>; Thu, 16 Nov 2000 10:37:59 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAGIbr509987; Thu, 16 Nov 2000 10:37:53 -0800 (PST) Date: Thu, 16 Nov 2000 10:37:53 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: Nicolai Petri <nicolai@petri.cc> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Multithreaded tcp-server or non-blocking ? Message-ID: <20001116103753.C830@fw.wintelcom.net> References: <021501c04fb9$574f9030$6732a8c0@atomic.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <021501c04fb9$574f9030$6732a8c0@atomic.dk>; from nicolai@petri.cc on Thu, Nov 16, 2000 at 11:38:14AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Nicolai Petri <nicolai@petri.cc> [001116 02:37] wrote: > What's the best approach for a simple web-server(never more the 10 clients) > ? Is it using pthread and a thread per connection . Or to make a > non-blocking single thread server. Can people show me some simple examples > of the 2 techniques ? > > And what's the pro's and con's for the 2 methods ??? Because you want something simple, I would use a thread per connection. For a more complex/high-perfomance server you'd want to use several threads using event queues and perhaps external processes for disk IO. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 11: 0:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id E25C037B479; Thu, 16 Nov 2000 11:00:49 -0800 (PST) Subject: Re: More detail on Deskpro XL6200 NIC (was: Legacy ethernet cards in FreeBSD) In-Reply-To: <59063B5B4D98D311BC0D0001FA7E4522026D7A07@l04.research.kpn.com> from "Koster, K.J." at "Nov 16, 2000 12:11:56 pm" To: K.J.Koster@kpn.com (Koster, K.J.) Date: Thu, 16 Nov 2000 11:00:49 -0800 (PST) Cc: freebsd-hackers@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 Message-Id: <20001116190049.E25C037B479@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Charset iso-8859-1 unsupported, filtering to ASCII...] > Dear Bill, others, > > I've been working on getting my Deskpros to use their NIC under 4.2, but no > luck. The problem is as follows: I installed 4.0, and the NIC came up under > the lnc driver, reports its MAC address and works fine. > [...] > In 4.2, the lnc driver still probes and finds the NIC, but does not report > finding a MAC address, and the NIC remains dead. [...] > Compiling a kernel with the pcn driver does not help. Booting a lnc+pcn > kernel causes the behaviour described above, booting a pcn-only kernel makes > the NIC show up as an unknown device, vendor 0x1022, device 0x2000. *ahem* How about compiling a kernel *without* the pcn driver? I want to know why you didn't consider this combination. (Well, I know why: because giving me the answer straight away rather than making me drag it out of you would have been too easy. I would never be that lucky.) The pcn driver does *not* want this card. It specifically checks for the device code in the probe routine and rejects cards it doesn't like. Note that this is *not* the PCI vendor/device ID: the way AMD did it, the PCI ID is the same for all the PCnet devices. You need to read a register in I/O space to determine exactly what device this is. That said, I think I know what the problem is. The pcn driver is probing the card first and setting it to 32-bit mode. The lnc driver wants the device to be in 16-bit mode: if it isn't, it won't be able to properly access any of its registers. This is why reading the card type and MAC address fails. Next time, *remove* the pcn device from the kernel config and leave the lnc driver. That should work. In the meantime, I need to get out the PCnet manual and check how to put the device back into 16-bit mode at the end of pcn_probe() so that the lnc driver will play nice with it. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 11: 6:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gate.trident-uk.co.uk (mail.trident-uk.co.uk [195.166.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 7DF4E37B4FE for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 11:06:53 -0800 (PST) Received: from [194.207.93.139] by gate.trident-uk.co.uk for freebsd-hackers@freebsd.org id TAA22873; Thu Nov 16 19:06:51 2000 Organization: Psi-Domain Ltd. Subject: Resolution Date: Thu, 16 Nov 2000 19:11:36 +0000 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00111619122603.05634@freefire.psi-domain.co.uk> Content-Transfer-Encoding: 8bit To: freebsd-hackers@freebsd.org From: Jamie Heckford <heckfordj@psi-domain.co.uk> Reply-To: heckfordj@psi-domain.co.uk Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How would i go about changing the resolution of my vt?? Im fed up with the 320 x X mode it uses, and want to maybe get it up to 1024x768. Any ideas anyone? Thanks, -- Jamie Heckford Chief Network Engineer Psi-Domain - Innovative Linux Solutions. Ask Us How. =================================== email: heckfordj@psi-domain.co.uk web: http://www.psi-domain.co.uk/ tel: +44 (0)1737 789 246 fax: +44 (0)1737 789 245 mobile: +44 (0)7779 646 529 =================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 11:39:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 76ECD37B479 for <freebsd-hackers@FreeBSD.ORG>; Thu, 16 Nov 2000 11:39:45 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.11.1/8.11.1) id eAGJdX026116; Thu, 16 Nov 2000 13:39:33 -0600 (CST) (envelope-from dan) Date: Thu, 16 Nov 2000 13:39:33 -0600 From: Dan Nelson <dnelson@emsphone.com> To: Jamie Heckford <heckfordj@psi-domain.co.uk> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Resolution Message-ID: <20001116133933.A5328@dan.emsphone.com> References: <00111619122603.05634@freefire.psi-domain.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <00111619122603.05634@freefire.psi-domain.co.uk>; from "Jamie Heckford" on Thu Nov 16 19:11:36 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Nov 16), Jamie Heckford said: > How would i go about changing the resolution of my vt?? > > Im fed up with the 320 x X mode it uses, and want to maybe get it up to > 1024x768. Console screens aren't pixel-based; they're character-cell based. The default console is 80x25, which is really 720x400 pixels if you want to keep track. If you want more lines/columns on the console, see the vidcontrol manpage. -- Dan Nelson dnelson@emsphone.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 16 12: 0:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 49A7237B479; Thu, 16 Nov 2000 12:00:07 -0800 (PST) Subject: Re: More detail on Deskpro XL6200 NIC (was: Legacy ethernet cards in FreeBSD) In-Reply-To: <59063B5B4D98D311BC0D0001FA7E4522026D7A07@l04.research.kpn.com> from "Koster, K.J." at "Nov 16, 2000 12:11:56 pm" To: K.J.Koster@kpn.com (Koster K.J.) Date: Thu, 16 Nov 2000 12:00:07 -0800 (PST) Cc: freebsd-hackers@freebsd.org, jkh@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 Message-Id: <20001116200007.49A7237B479@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well this sucks. According to the manual, once you select 32-bit mode, the only way to get the chip back to 16-bit mode is a hardware reset. I suppose the quick fix for now is to not let if_pcn switch the chip into 32-bit mode during the probe routine. Please try the patch for if_pcn.c included with this message. It should fix things so if you have both the pcn and lnc drivers in your kernel, the lnc driver will attach properly. I'm cc'ing this to jkh for his approval to have this patch added to the -stable tree in time for 4.2-RELEASE. -Bill *** if_pcn.c.orig Thu Nov 2 16:37:45 2000 --- if_pcn.c Thu Nov 16 11:48:43 2000 *************** *** 110,115 **** --- 110,116 ---- }; static u_int32_t pcn_csr_read __P((struct pcn_softc *, int)); + static u_int16_t pcn_csr_read16 __P((struct pcn_softc *, int)); static void pcn_csr_write __P((struct pcn_softc *, int, int)); static u_int32_t pcn_bcr_read __P((struct pcn_softc *, int)); static void pcn_bcr_write __P((struct pcn_softc *, int, int)); *************** *** 203,208 **** --- 204,217 ---- return(CSR_READ_4(sc, PCN_IO32_RDP)); } + static u_int16_t pcn_csr_read16(sc, reg) + struct pcn_softc *sc; + int reg; + { + CSR_WRITE_2(sc, PCN_IO16_RAP, reg); + return(CSR_READ_2(sc, PCN_IO16_RDP)); + } + static void pcn_csr_write(sc, reg, val) struct pcn_softc *sc; int reg; *************** *** 401,410 **** mtx_init(&sc->pcn_mtx, device_get_nameunit(dev), MTX_DEF); PCN_LOCK(sc); ! pcn_reset(sc); ! chip_id = pcn_csr_read(sc, PCN_CSR_CHIPID1); chip_id <<= 16; ! chip_id |= pcn_csr_read(sc, PCN_CSR_CHIPID0); bus_release_resource(dev, PCN_RES, PCN_RID, sc->pcn_res); PCN_UNLOCK(sc); --- 410,429 ---- mtx_init(&sc->pcn_mtx, device_get_nameunit(dev), MTX_DEF); PCN_LOCK(sc); ! /* ! * Note: we can *NOT* put the chip into ! * 32-bit mode yet. The lnc driver will only ! * work in 16-bit mode, and once the chip ! * goes into 32-bit mode, the only way to ! * get it out again is with a hardware reset. ! * So if pcn_probe() is called before the ! * lnc driver's probe routine, the chip will ! * be locked into 32-bit operation and the lnc ! * driver will be unable to attach to it. ! */ ! chip_id = pcn_csr_read16(sc, PCN_CSR_CHIPID1); chip_id <<= 16; ! chip_id |= pcn_csr_read16(sc, PCN_CSR_CHIPID0); bus_release_resource(dev, PCN_RES, PCN_RID, sc->pcn_res); PCN_UNLOCK(sc); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 13:18:51 2000 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 0A2D637B4C5; Thu, 16 Nov 2000 13:18:42 -0800 (PST) Received: from newsguy.com (p18-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.83]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id GAA05703; Fri, 17 Nov 2000 06:16:10 +0900 (JST) Message-ID: <3A144E33.F8B57C38@newsguy.com> Date: Fri, 17 Nov 2000 06:14:27 +0900 From: "Daniel C. Sobral" <dcs@newsguy.com> X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: "Yonny Cardenas B." <ycardena@yahoo.com> Cc: hackersBSD <hackers@FreeBSD.ORG>, questions <questions@FreeBSD.ORG>, German Vega <gvega@uniandes.edu.co> Subject: Re: RTP as system calls. References: <394A5225.AF165842@yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Yonny Cardenas B." wrote: > > I have some questions: > > 1) Can I call functions level's user into kernel, as socket() or > calloc() ? No. > 2) How must I use the global variable "errno" for value > returned for system calls ? Is sufficient with #include <sys/errno.h> ? You are not calling system calls from inside the kernel, and you are also not using errno like you would from userland. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@world.wide.bsdconspiracy.net He has been convicted of criminal possession of a clue with intent to distribute. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 13:41:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 402A537B479 for <hackers@FreeBSD.ORG>; Thu, 16 Nov 2000 13:41:28 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.1/8.11.1) with ESMTP id eAGLbMF31998; Thu, 16 Nov 2000 21:37:22 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.1/8.11.1) with ESMTP id eAGLbYb42529; Thu, 16 Nov 2000 21:37:34 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200011162137.eAGLbYb42529@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Renaud Waldura" <renaud@waldura.com> Cc: "Brian Somers" <brian@Awfulhak.org>, hackers@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: PPPoE w/ nat auto fragmentation hack? (use tcpmssd port) In-Reply-To: Message from "Renaud Waldura" <renaud@waldura.com> of "Wed, 15 Nov 2000 19:26:25 PST." <002a01c04f7d$00699680$0402010a@biohz.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 Nov 2000 21:37:33 +0000 From: Brian Somers <brian@Awfulhak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > ppp will run programs as the user id that invoked ppp rather than > > using the effective user id (ie, it runs things as *you*, not *root*). > > Mmm-mmh. In my case, since ppp is started at boot time, the only user that > ever invokes it is root, hence the tcpmssd thingy is run as root. As > confirmed by the multiple "ps" I ran: euid == ruid == svguid == 0. > > > > A good ``first step'' is to run > > ! sh -c "/usr/local/bin/tcpmssd -p 12345 -i INTERFACE >/tmp/log 2>&1" > > so that you can get to see any error messages - ppp redirects I/O to > > Yup, tried that, here's what I get: > > ******************** start *************** > Wed Nov 15 13:30:12 PST 2000 > id says: uid=0(root) gid=0(wheel) groups=0(wheel) > HOME=/ > PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin > 01001 divert 1234 tcp from any to any out xmit tun0 setup > > The rule gets inserted, tcpmssd runs as root, and I feel like a dummy. Any > other ideas? > > Thanks for the help Brian, I'm not sure what the problem could be - can you confirm that everything's seen if you divert everything ? > --Renaud > > > > ----- Original Message ----- > From: Brian Somers <brian@Awfulhak.org> > To: Renaud Waldura <renaud@waldura.com> > Cc: Brian Somers <brian@Awfulhak.org>; <hackers@FreeBSD.ORG>; > <brian@Awfulhak.org> > Sent: Wednesday, November 15, 2000 4:32 PM > Subject: Re: PPPoE w/ nat auto fragmentation hack? (use tcpmssd port) > > > > > Maybe I'm just being boneheaded, but... > > > > > > > ! sudo ipfw add 40000 divert 12345 all from any to any via INTERFACE > > > > ! sudo /usr/local/bin/tcpmssd -p 12345 -i INTERFACE > > > > > > I was under the (tested & confirmed) impression that programs executed > by > > > ppp are run under uid 0. Eg. I don't use "sudo" but the ipfw rule is > added > > > anyway, and tcpmssd is run as root. > > > > > > But maybe a sudo environment brings something else? That could explain a > lot > > > right there. > > > > > > --Renaud > > > > ppp will run programs as the user id that invoked ppp rather than > > using the effective user id (ie, it runs things as *you*, not *root*). > > > > AFAIK, sudo will not muck about with your environment.... > > > > A good ``first step'' is to run > > > > ! sh -c "/usr/local/bin/tcpmssd -p 12345 -i INTERFACE >/tmp/log 2>&1" > > > > so that you can get to see any error messages - ppp redirects I/O to > > /dev/null by default. -- Brian <brian@Awfulhak.org> <brian@[uk.]FreeBSD.org> <http://www.Awfulhak.org> <brian@[uk.]OpenBSD.org> 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 16 13:44: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gate.trident-uk.co.uk (mail.trident-uk.co.uk [195.166.16.10]) by hub.freebsd.org (Postfix) with ESMTP id B5DD837B4C5 for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 13:43:59 -0800 (PST) Received: from [194.207.93.139] by gate.trident-uk.co.uk for freebsd-hackers@freebsd.org id VAA25819; Thu Nov 16 21:43:57 2000 Organization: Psi-Domain Ltd. Subject: compiling X apps Date: Thu, 16 Nov 2000 21:47:51 +0000 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00111621493200.00178@freefire.psi-domain.co.uk> Content-Transfer-Encoding: 8bit To: freebsd-hackers@freebsd.org From: Jamie Heckford <heckfordj@psi-domain.co.uk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Very sorry for posting such a dumb question, but since I cvs'upd something weird seems to have happened. I am using this to compile my X app (which just uses Xlib.h at the mo) gcc -L/usr/X11R6/include -o test test.cc but it cannot locate Xlib.h?!! Any suggestions? Thanks. -- Jamie Heckford Chief Network Engineer Psi-Domain - Innovative Linux Solutions. Ask Us How. =================================== email: heckfordj@psi-domain.co.uk web: http://www.psi-domain.co.uk/ tel: +44 (0)1737 789 246 fax: +44 (0)1737 789 245 mobile: +44 (0)7779 646 529 =================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 13:51:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (Postfix) with SMTP id 6668B37B4E5 for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 13:51:21 -0800 (PST) Received: (qmail 5123 invoked by uid 3001); 16 Nov 2000 21:51:14 -0000 Received: from natto.numachi.com (198.175.254.216) by numachi.numachi.com with SMTP; 16 Nov 2000 21:51:14 -0000 Received: (qmail 23202 invoked by uid 1001); 16 Nov 2000 21:51:14 -0000 Date: Thu, 16 Nov 2000 16:51:14 -0500 From: Brian Reichert <reichert@numachi.com> To: Jamie Heckford <heckfordj@psi-domain.co.uk> Cc: freebsd-hackers@freebsd.org Subject: Re: compiling X apps Message-ID: <20001116165114.A23001@numachi.com> References: <00111621493200.00178@freefire.psi-domain.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <00111621493200.00178@freefire.psi-domain.co.uk>; from heckfordj@psi-domain.co.uk on Thu, Nov 16, 2000 at 09:47:51PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 16, 2000 at 09:47:51PM +0000, Jamie Heckford wrote: > Very sorry for posting such a dumb question, but since I cvs'upd something > weird seems to have happened. > > I am using this to compile my X app (which just uses Xlib.h at the mo) > > gcc -L/usr/X11R6/include -o test test.cc -I/usr/X11R6/include '-L' is for directories of libriaries. > but it cannot locate Xlib.h?!! > > Any suggestions? > > Thanks. > > -- > Jamie Heckford > Chief Network Engineer > Psi-Domain - Innovative Linux Solutions. Ask Us How. 'Innovative Linux'? :) > =================================== > email: heckfordj@psi-domain.co.uk > web: http://www.psi-domain.co.uk/ > > tel: +44 (0)1737 789 246 > fax: +44 (0)1737 789 245 > mobile: +44 (0)7779 646 529 > =================================== -- Brian 'you Bastard' Reichert <reichert@numachi.com> 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 14:14:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from phobos.illtel.denver.co.us (unknown [206.169.4.82]) by hub.freebsd.org (Postfix) with ESMTP id 55B0A37B4C5 for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 14:14:13 -0800 (PST) Received: from localhost (abelits@localhost) by phobos.illtel.denver.co.us (8.9.3/8.9.3) with ESMTP id OAA21640; Thu, 16 Nov 2000 14:13:48 -0800 Date: Thu, 16 Nov 2000 14:13:48 -0800 (PST) From: Alex Belits <abelits@phobos.illtel.denver.co.us> To: Jamie Heckford <heckfordj@psi-domain.co.uk> Cc: freebsd-hackers@freebsd.org Subject: Re: compiling X apps In-Reply-To: <00111621493200.00178@freefire.psi-domain.co.uk> Message-ID: <Pine.LNX.4.20.0011161412350.21504-100000@phobos.illtel.denver.co.us> 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, 16 Nov 2000, Jamie Heckford wrote: > Very sorry for posting such a dumb question, but since I cvs'upd something > weird seems to have happened. > > I am using this to compile my X app (which just uses Xlib.h at the mo) > > gcc -L/usr/X11R6/include -o test test.cc > > but it cannot locate Xlib.h?!! > > Any suggestions? 1. man xmkmf 2. -I /usr/X11R6/include -- Alex ---------------------------------------------------------------------- Excellent.. now give users the option to cut your hair you hippie! -- Anonymous Coward To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 14:36: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from thunderer.cnchost.com (thunderer.concentric.net [207.155.252.72]) by hub.freebsd.org (Postfix) with ESMTP id 8284137B4C5 for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 14:36:03 -0800 (PST) Received: from bitblocks.com (ts002d47.oak-ca.concentric.net [206.173.201.107]) by thunderer.cnchost.com id RAA27714; Thu, 16 Nov 2000 17:35:47 -0500 (EST) [ConcentricHost SMTP Relay 1.10] Message-ID: <200011162235.RAA27714@thunderer.cnchost.com> To: "Nicolai Petri" <nicolai@petri.cc> Cc: freebsd-hackers@freebsd.org Subject: Re: Multithreaded tcp-server or non-blocking ? In-Reply-To: Your message of "Thu, 16 Nov 2000 11:38:14 +0100." <021501c04fb9$574f9030$6732a8c0@atomic.dk> Date: Thu, 16 Nov 2000 14:35:46 -0800 From: Bakul Shah <bakul@bitblocks.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What's the best approach for a simple web-server(never more the 10 clients) > ? Is it using pthread and a thread per connection . Or to make a > non-blocking single thread server. Can people show me some simple examples > of the 2 techniques ? > > And what's the pro's and con's for the 2 methods ??? The simplest solution is to just fork a new process on accepting a new connection. A sample implementation is included at the end. This solution doesn't scale too well as a process is quite heavy weight and uses much more resources than the other two solutions. One variation avoids the cost of fork/exit per connection. The connection accepting process passes the new file descriptor in a message to a free server process. The acceptor creates server threads as needed and the server threads can be made to exit when they are idle for a while. The thread per connection solution is also quite simple and significantly more efficient that process per connection since a thread context switch is a lot cheaper than a process context switch. But you need to deal with concurrency issues if you have to share a bunch of state and your threads can be preempted. With this and the next solution you can also run into file descriptor limits. I don't have an example I can show you. A non-blocking single thread server is likely to be more portable than the pthread solution. See http://www.bitblocks.com/src/select-test.c for an example. The basic problem here is what to do if deep down in some function you need to wait for some response from a client. As an example, consider the case where function A is called when a new connection comes in. A calls B and B calls C and C wants to block. You have no choice but to implement this as a state machine and break functions B, C in B1, B2, C1 and C2 and carry around appropriate state. So you have to take something like A(int fd) { // called on a new connection ... B(fd); ... } B(int fd) { ... C(fd); ... } C(int fd) { ... read(fd, buf, len); ... } and change it to A(int fd, Context* c) { // called on a new connection switch (c->state) { case init: ... B1(fd, c); break; case more: B2(fd, c); ... } } B1(int fd, Context* c) { ... C1(fd, c); } B2(int fd, Context* c) { C2(fd, c); ... } C1(int fd, Context* c) { ... c->state = more; } C2(int fd, Context* c) { len = read(fd, bufptr, len); if (read enough) c->state = init; else update bufptr ... } If you have a complex interaction with the client, the number of states can explode. Worse, such interactions may get added as the application evolves so you are forced to do a conversion like the one shown above. In effect here you are implementing threading in a application specific way and the c->state variable has a role analogous to a program counter of a thread. At the same time concurrency issues are easier to deal with than the pthreads case since this is cooperative multithreading. In my (somewhat dated) experience this solution was a bit more efficient than the pthreads version but significantly more complex -- this situation may have changed in pthreads' favor. Also, typically here you require much less memory to store a connection's state than what you spend with a pthread -- an issue if you have thousands of connections. If only a few are active at a time this single thread select loop solution is a perfectly usable solution and uses the least resources. You didn't ask for this but note that for handling a very large number of clients (thousands to millions) you have to use a combination of techniques to deal with various resource limits. For example, you can push timeconsuming diskio requests to separate threads or ever separate machines. You can use multiple processes to deal with file descriptor limits and so on. -- bakul /* A simple fork-a-server-on-accepting-a-connection solution */ #include <stdio.h> #include <stdlib.h> #include <unistd.h> #include <sys/types.h> #include <sys/socket.h> #include <netinet/in.h> #include <sys/wait.h> #include <signal.h> void reaper(int ignore) { int status; wait(&status); } void process_request(int fd) { char buffer[11]; int len = sprintf(buffer, "%d\n", getpid()); write(fd, buffer, len); } int main(int argc, char** argv) { u_short port = argc > 1? strtoul(argv[1], 0, 0) : 1234; int s = socket(PF_INET, SOCK_STREAM, 0); int one = 1; struct sockaddr_in addr; if (s < 0) { perror("socket"); exit(1); } bzero(&addr, sizeof addr); addr.sin_len = sizeof addr; addr.sin_family = AF_INET; addr.sin_port = htons(port); if (bind(s, (struct sockaddr*)&addr, sizeof addr) < 0) { perror("bind"); exit(1); } if (setsockopt(s, SOL_SOCKET, SO_REUSEPORT, &one, sizeof one) < 0) { perror("setsockopt"); exit(1); } if (listen(s, 5) < 0) { perror("listen"); exit(1); } if (signal(SIGCHLD, reaper) < 0) { perror("signal"); exit(1); } for (;;) { int len = sizeof addr; int fd = accept(s, (struct sockaddr*)&addr, &len); int pid; if (fd < 0) continue; pid = fork(); if (pid) { /*child */ process_request(fd); exit(0); } /* parent */ close(fd); if (pid < 0) { perror("fork"); continue; } } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 15: 9: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id C3C8337B4D7 for <hackers@FreeBSD.ORG>; Thu, 16 Nov 2000 15:09:02 -0800 (PST) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id QAA10589; Thu, 16 Nov 2000 16:07:03 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpdAAA6UaWgp; Thu Nov 16 16:02:28 2000 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id QAA03952; Thu, 16 Nov 2000 16:04:16 -0700 (MST) From: Terry Lambert <tlambert@primenet.com> Message-Id: <200011162304.QAA03952@usr08.primenet.com> Subject: Re: "iowait" CPU state To: riel@conectiva.com.br (Rik van Riel) Date: Thu, 16 Nov 2000 23:04:16 +0000 (GMT) Cc: tlambert@primenet.com (Terry Lambert), float@firedrake.org (void), hackers@FreeBSD.ORG In-Reply-To: <Pine.LNX.4.21.0011160938080.13085-100000@duckman.distro.conectiva> from "Rik van Riel" at Nov 16, 2000 09:40:17 AM X-Mailer: ELM [version 2.5 PL2] 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 > Ummm, how about a situation where you have a steadily > increasing work load (more customers?) and want to have > decent statistics of your servers to determine exactly > what parts to upgrade and/or if you need to put extra > machines into service? Two words: capacity planning. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 15:12:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from brutus.conectiva.com.br (brutus.conectiva.com.br [200.250.58.146]) by hub.freebsd.org (Postfix) with ESMTP id 483D737B479 for <hackers@FreeBSD.ORG>; Thu, 16 Nov 2000 15:12:24 -0800 (PST) Received: from localhost (riel@localhost) by brutus.conectiva.com.br (8.11.1/8.11.1) with ESMTP id eAGNC0226107; Thu, 16 Nov 2000 21:12:00 -0200 X-Authentication-Warning: duckman.distro.conectiva: riel owned process doing -bs Date: Thu, 16 Nov 2000 21:12:00 -0200 (BRDT) From: Rik van Riel <riel@conectiva.com.br> X-Sender: riel@duckman.distro.conectiva To: Terry Lambert <tlambert@primenet.com> Cc: void <float@firedrake.org>, hackers@FreeBSD.ORG Subject: Re: "iowait" CPU state In-Reply-To: <200011162304.QAA03952@usr08.primenet.com> Message-ID: <Pine.LNX.4.21.0011162111240.13085-100000@duckman.distro.conectiva> 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, 16 Nov 2000, Terry Lambert wrote: > > Ummm, how about a situation where you have a steadily > > increasing work load (more customers?) and want to have > > decent statistics of your servers to determine exactly > > what parts to upgrade and/or if you need to put extra > > machines into service? > > Two words: capacity planning. For which you really want all the useful statistics the OS could give you. (including maybe the %iowait one) cheers, Rik -- "What you're running that piece of shit Gnome?!?!" -- Miguel de Icaza, UKUUG 2000 http://www.conectiva.com/ http://www.surriel.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 16 15:20: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.unixbox.com (shell.unixbox.com [207.211.45.65]) by hub.freebsd.org (Postfix) with ESMTP id 45D3937B479 for <freebsd-hackers@FreeBSD.ORG>; Thu, 16 Nov 2000 15:20:00 -0800 (PST) Received: from localhost (fengyue@localhost) by shell.unixbox.com (8.11.0/8.11.0) with ESMTP id eAGNKTA18801 for <freebsd-hackers@FreeBSD.ORG>; Thu, 16 Nov 2000 15:20:29 -0800 (PST) Date: Thu, 16 Nov 2000 15:20:29 -0800 (PST) From: FengYue <fengyue@bluerose.windmoon.nu> X-Sender: fengyue@shell.unixbox.com To: freebsd-hackers@FreeBSD.ORG Subject: Re: Multithreaded tcp-server or non-blocking ? In-Reply-To: <200011162235.RAA27714@thunderer.cnchost.com> Message-ID: <Pine.BSF.4.21.0011161515560.18678-100000@shell.unixbox.com> 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, 16 Nov 2000, Bakul Shah wrote: ->The simplest solution is to just fork a new process on ->accepting a new connection. A sample implementation is why not just bind to the port and then spawn off some processes (like 20 in his case) to do the accept(), once the accept() returns successfully just take care of the request, close the connection and then goes back to accept(). Simple, easy, and even scales pretty well. Since it's freebsd, you even don't need to worry about putting a lock around the accept() call. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 15:55: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from repulse.cnchost.com (repulse.concentric.net [207.155.248.4]) by hub.freebsd.org (Postfix) with ESMTP id B067437B4CF for <freebsd-hackers@FreeBSD.ORG>; Thu, 16 Nov 2000 15:55:03 -0800 (PST) Received: from bitblocks.com (ts002d47.oak-ca.concentric.net [206.173.201.107]) by repulse.cnchost.com id SAA07155; Thu, 16 Nov 2000 18:54:53 -0500 (EST) [ConcentricHost SMTP Relay 1.10] Message-ID: <200011162354.SAA07155@repulse.cnchost.com> To: FengYue <fengyue@bluerose.windmoon.nu> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Multithreaded tcp-server or non-blocking ? In-Reply-To: Your message of "Thu, 16 Nov 2000 15:20:29 PST." <Pine.BSF.4.21.0011161515560.18678-100000@shell.unixbox.com> Date: Thu, 16 Nov 2000 15:54:47 -0800 From: Bakul Shah <bakul@bitblocks.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > why not just bind to the port and then spawn off some processes (like 20 > in his case) to do the accept(), once the accept() returns successfully just > take care of the request, close the connection and then goes back > to accept(). Simple, easy, and even scales pretty well. Since > it's freebsd, you even don't need to worry about putting a lock > around the accept() call. Yes, this is definitely simpler and preferable when servicing a small number of concurrent requests. But you have to spawn off as many processes as the worst case number of concurrent requests you want to service since while all the processes are busy servicing, additional connections are not being accepted (after the listen backlog is exhausted). By using one process to accept connections, hand out requests and create processes as needed and by allowing idle processes to exit, you can dynamically adjust the number of server processes (e.g. depending on some user input or system load or resource use or day of time or whatever). You can also reject additional requests more intelligently (or redirecting them elsewhere) as opposed to not just accepting new connections. So this is more flexible at a small increase in complexity. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 16:15: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.unixbox.com (shell.unixbox.com [207.211.45.65]) by hub.freebsd.org (Postfix) with ESMTP id 563E637B4C5 for <freebsd-hackers@FreeBSD.ORG>; Thu, 16 Nov 2000 16:15:04 -0800 (PST) Received: from localhost (fengyue@localhost) by shell.unixbox.com (8.11.0/8.11.0) with ESMTP id eAH0FSe19906; Thu, 16 Nov 2000 16:15:28 -0800 (PST) Date: Thu, 16 Nov 2000 16:15:28 -0800 (PST) From: FengYue <fengyue@bluerose.windmoon.nu> X-Sender: fengyue@shell.unixbox.com To: Bakul Shah <bakul@bitblocks.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Multithreaded tcp-server or non-blocking ? In-Reply-To: <200011162354.SAA07155@repulse.cnchost.com> Message-ID: <Pine.BSF.4.21.0011161601150.19569-100000@shell.unixbox.com> 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, 16 Nov 2000, Bakul Shah wrote: ->Yes, this is definitely simpler and preferable when servicing ->a small number of concurrent requests. But you have to spawn ->off as many processes as the worst case number of concurrent ->requests you want to service since while all the processes ->are busy servicing, additional connections are not being ->accepted (after the listen backlog is exhausted). By using Well, with some additional coding, the parent process could easily monitor how many child processes are being used at a given time (like using mmap() to create a shared memory region and have the child process increases the busy_count...etc) and then to decide if it needs to spawn off some more processes into the pool based on the percentpage of number_of_busy_processes/total_processes_in_the_pool. Just like the way apache does it I guess. And, ofcoz, I agree that there are some performance impact if too many processes blocking on the accept() call. But then again, we're just talking about an easy solution for a webserver that only wants to handle no more than 15 clients at any given time:) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 16:31:59 2000 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 6CE6337B4C5 for <freebsd-hackers@FreeBSD.ORG>; Thu, 16 Nov 2000 16:31:57 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAH0VqF20904; Thu, 16 Nov 2000 16:31:52 -0800 (PST) Date: Thu, 16 Nov 2000 16:31:52 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: FengYue <fengyue@bluerose.windmoon.nu> Cc: Bakul Shah <bakul@bitblocks.com>, freebsd-hackers@FreeBSD.ORG Subject: Re: Multithreaded tcp-server or non-blocking ? Message-ID: <20001116163152.E18037@fw.wintelcom.net> References: <200011162354.SAA07155@repulse.cnchost.com> <Pine.BSF.4.21.0011161601150.19569-100000@shell.unixbox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <Pine.BSF.4.21.0011161601150.19569-100000@shell.unixbox.com>; from fengyue@bluerose.windmoon.nu on Thu, Nov 16, 2000 at 04:15:28PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * FengYue <fengyue@bluerose.windmoon.nu> [001116 16:15] wrote: > > On Thu, 16 Nov 2000, Bakul Shah wrote: > > ->Yes, this is definitely simpler and preferable when servicing > ->a small number of concurrent requests. But you have to spawn > ->off as many processes as the worst case number of concurrent > ->requests you want to service since while all the processes > ->are busy servicing, additional connections are not being > ->accepted (after the listen backlog is exhausted). By using > > Well, with some additional coding, the parent process could easily > monitor how many child processes are being used at a given time (like > using mmap() to create a shared memory region and have the > child process increases the busy_count...etc) > and then to decide if it needs to spawn off some more processes into > the pool based on the percentpage of > number_of_busy_processes/total_processes_in_the_pool. Just > like the way apache does it I guess. And, ofcoz, I agree that > there are some performance impact if too many processes blocking on the > accept() call. Actually FreeBSD uses wakeup_one() for accept(), the only problem is when your server must wait on more than one port/IP, then you need to use select(), however when many processes are selecting on the same descriptor it kills performance, that's why things like apache use semaphores or file locks instead of select. > But then again, we're just talking about an easy solution for a webserver > that only wants to handle no more than 15 clients at any given time:) Yes, it may be overkill. :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 16:34:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by hub.freebsd.org (Postfix) with ESMTP id 3E3D137B479 for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 16:34:13 -0800 (PST) Received: from office.ripe.net (office.ripe.net [193.0.1.97]) by birch.ripe.net (8.8.8/8.8.8) with ESMTP id BAA20093 for <freebsd-hackers@freebsd.org>; Fri, 17 Nov 2000 01:34:12 +0100 (CET) Received: (from marks@localhost) by office.ripe.net (8.8.8/8.8.5) id BAA11626 for freebsd-hackers@freebsd.org; Fri, 17 Nov 2000 01:34:12 +0100 (CET) Date: Fri, 17 Nov 2000 01:34:12 +0100 From: Mark Santcroos <marks@ripe.net> To: freebsd-hackers@freebsd.org Subject: new kld style Message-ID: <20001117013412.D3410@ripe.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i X-Handles: MS6-6BONE, MS32260-NIC, MS18417-RIPE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, While implementing a module based on /usr/share/examples/cdev??? I noticed that after loading it I get a warning that originates from kern/kern_linker.c telling me that I'm using the old kld style. [This all on -CURRENT] Can you please point me to the right direction for the "new" style. Or explain me if I'm missing something :-) [or even tell me that I should not worry about this] Regards, Mark -- Mark Santcroos RIPE Network Coordination Centre PGP KeyID: 1024/0x3DCBEB8D PGP Fingerprint: BB1E D037 F29D 4B40 0B26 F152 795F FCAB 3DCB EB8D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 16 17:28:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (mail.dobox.com [208.187.122.44]) by hub.freebsd.org (Postfix) with ESMTP id 58DD637B479 for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 17:28:34 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13waLl-0000B2-00; Thu, 16 Nov 2000 18:29:57 -0700 Message-ID: <3A148A14.FA1A573D@softweyr.com> Date: Thu, 16 Nov 2000 18:29:57 -0700 From: Wes Peters <wes@softweyr.com> Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Paonia Ezrine <paonia@home.welcomehome.org> Cc: Greg Lehey <grog@lemis.com>, freebsd-hackers@FreeBSD.ORG Subject: Re: looking for kernel hacking info References: <200011150214.VAA27289@home.welcomehome.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Paonia Ezrine wrote: > > > On Tuesday, 14 November 2000 at 16:32:49 -0500, Paonia Ezrine wrote: > > > I am looking for info on programing in kernel land. System calls, howto's > > > etc. I have not found anything that realy covers this stuff any and all > > > help would be welcomed! > > > > The system calls are described in section 2 of the manual. > > > > Greg > thanks. do you mean handbook? No. On a FreeBSD system, look in /usr/share/man/man2. See all those files? Those are the man pages. You can access them with the "man" command. -- "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 16 17:31:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (mail.dobox.com [208.187.122.44]) by hub.freebsd.org (Postfix) with ESMTP id 52EA937B479 for <freebsd-hackers@freebsd.org>; Thu, 16 Nov 2000 17:31:34 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13waNo-0000BC-00; Thu, 16 Nov 2000 18:32:04 -0700 Message-ID: <3A148A94.59C61A51@softweyr.com> Date: Thu, 16 Nov 2000 18:32:04 -0700 From: Wes Peters <wes@softweyr.com> Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey <grog@lemis.com> Cc: visi0n <visi0n@aux-tech.org>, Paonia Ezrine <paonia@home.welcomehome.org>, freebsd-hackers@FreeBSD.ORG Subject: Re: looking for kernel hacking info References: <20001115094139.C39755@wantadilla.lemis.com> <Pine.BSF.4.21.0011151003330.1362-100000@anthrax.chinatown.org> <20001115133210.I39755@wantadilla.lemis.com> 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 Wednesday, 15 November 2000 at 10:08:45 +0000, visi0n wrote: > > > > The THC have a documentation about freebsd kernel space. > > > > packetstorm.securify.com/groups/thc/bsdkern.htm > > Repeating the full URL for the benefit of mutt users, this is > http://packetstorm.securify.com/groups/thc/bsdkern.htm > > This is an interesting document. It describes how to insert a Trojan > into the FreeBSD kernel When it came out, we discussed it and decided > that it would be of no danger to a properly secured system. On the > other hand, the documentation is relatively well done. We should > really import it. Ah, yes, handbook section 23: "FreeBSD for the Ethically Challenged" ;^) -- "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 16 18:22:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pericles.IPAustralia.gov.au (unknown [202.14.186.30]) by hub.freebsd.org (Postfix) with ESMTP id A08ED37B479 for <FreeBSD-Hackers@FreeBSD.ORG>; Thu, 16 Nov 2000 18:22:19 -0800 (PST) Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.9.3/8.9.3) id NAA07224 for <FreeBSD-Hackers@FreeBSD.ORG>; Fri, 17 Nov 2000 13:21:02 +1100 (EST) (envelope-from anwsmh@IPAustralia.Gov.AU) Received: from disc-4-161.aipo.gov.au(10.0.4.161) by pericles.IPAustralia.gov.au via smap (V2.0) id xma007200; Fri, 17 Nov 00 13:20:40 +1100 Received: from localhost (anwsmh@localhost) by stan.aipo.gov.au (8.9.3/8.9.3) with ESMTP id NAA01445 for <FreeBSD-Hackers@FreeBSD.ORG>; Fri, 17 Nov 2000 13:20:40 +1100 (EST) (envelope-from anwsmh@IPAustralia.Gov.AU) X-Authentication-Warning: stan.aipo.gov.au: anwsmh owned process doing -bs Date: Fri, 17 Nov 2000 13:20:40 +1100 (EST) From: Stanley Hopcroft <Stanley.Hopcroft@IPAustralia.Gov.AU> X-Sender: anwsmh@stan.aipo.gov.au To: FreeBSD-Hackers@FreeBSD.ORG Subject: Re: ntop, worlds greatest network monitor, no go on FreeBSD (fwd) Message-ID: <Pine.BSF.4.21.0011171319520.1202-100000@stan.aipo.gov.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ---------- Forwarded message ---------- Date: Thu, 16 Nov 2000 17:20:11 -0800 (PST) From: FengYue <fengyue@bluerose.windmoon.nu> To: Stanley Hopcroft <Stanley.Hopcroft@IPAustralia.Gov.AU> Subject: Re: ntop, worlds greatest network monitor, no go on FreeBSD you may consider copying this message to hackers@freebsd.org On Thu, 16 Nov 2000, Stanley Hopcroft wrote: ->Dear Ladies and Gentlemen, -> ->I am writing to ask for someone to provide advice to the ntop project ->(http://www.ntop.org) on porting to FreeBSD. -> ->There are a number of problems with ntop (1.3.2 26th October) on ->FreeBSD (eg Mr Petri's letter of a few weeks ago) among them that when ->it's built with pthread support (-pthread), it uses all of the CPU ->(built without pthread support, it behaves). -> ->The problems are manifested on FreeBSD 4.x. -> ->ntop is able to use threads on many other platforms. -> ->ntop is a wonderful monitor. If you have ever wanted RMON2 like ability ->in software with a browser interface, ntop is for you. -> ->There is a port of ntop (for 1.1) but it displays the same CPU hogging ->behaviour as the later version. -> ->There has been no response from the ntop FreeBSD port mailing list. -> ->Thank you. -> ->Yours sincerely, -> -> ->S Hopcroft -> ->Network Specialist ->IP Australia -> ->+61 2 6283 3189 ->+61 2 6281 1353 FAX -> -> -> ->To Unsubscribe: send mail to majordomo@FreeBSD.org ->with "unsubscribe freebsd-isp" 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 16 19:51:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id 14B9837B479 for <freebsd-hackers@FreeBSD.ORG>; Thu, 16 Nov 2000 19:51:34 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id eAH3qga60979; Thu, 16 Nov 2000 19:52:43 -0800 (PST) (envelope-from kris) Date: Thu, 16 Nov 2000 19:52:42 -0800 From: Kris Kennaway <kris@FreeBSD.ORG> To: Jamie Heckford <heckfordj@psi-domain.co.uk> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: compiling X apps Message-ID: <20001116195242.A60945@citusc17.usc.edu> References: <00111621493200.00178@freefire.psi-domain.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="jI8keyz6grp/JLjh" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <00111621493200.00178@freefire.psi-domain.co.uk>; from heckfordj@psi-domain.co.uk on Thu, Nov 16, 2000 at 09:47:51PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --jI8keyz6grp/JLjh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 16, 2000 at 09:47:51PM +0000, Jamie Heckford wrote: > Very sorry for posting such a dumb question, but since I cvs'upd something > weird seems to have happened. >=20 > I am using this to compile my X app (which just uses Xlib.h at the mo) >=20 > gcc -L/usr/X11R6/include -o test test.cc >=20 > but it cannot locate Xlib.h?!! >=20 > Any suggestions? Please restrict your questions of this level to the freebsd-questions@freebsd.org mailing list in future - they are off-topic for -hackers. Thanks. Kris --jI8keyz6grp/JLjh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjoUq4oACgkQWry0BWjoQKWOiACeKbFJy7Y+0aAG+Gwp6w/RZIT7 SQ4AoONllZfawoLqWhTTUZg3K7SvABCh =pIhP -----END PGP SIGNATURE----- --jI8keyz6grp/JLjh-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 17 1:54:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fling.sanbi.ac.za (fling.sanbi.ac.za [196.38.142.119]) by hub.freebsd.org (Postfix) with ESMTP id 0A97C37B479 for <freebsd-hackers@freebsd.org>; Fri, 17 Nov 2000 01:54:08 -0800 (PST) Received: from johann by fling.sanbi.ac.za with local (Exim 3.13 #4) id 13wiDQ-000HGo-00; Fri, 17 Nov 2000 11:53:52 +0200 Date: Fri, 17 Nov 2000 11:53:52 +0200 From: Johann Visagie <johann@egenetics.com> To: frank xu <bsdman@hotmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: scheduler activations in FBSD5.0? Message-ID: <20001117115352.K49568@fling.sanbi.ac.za> References: <F41mcarcR4ZDgC81Tbd00000651@hotmail.com> <3A13FEBB.D3CE66F1@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A13FEBB.D3CE66F1@elischer.org>; from julian@elischer.org on Thu, Nov 16, 2000 at 07:35:23AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer on 2000-11-16 (Thu) at 07:35:23 -0800: > > frank xu wrote: > > > > I heard rumor that Thomas E. Anderson's Scheduler Activations theory will > > be implemented in FreeBSD 5.0 kernel, is it true? > > Basically the coming FreeBSD threading system will be based on the work > by > Anderson. It may have some different aspects too. FYI, a paper I recently came across detailing some of the work surrounding the original implementation of scheduler activation in BSD/OS: http://citeseer.nj.nec.com/43570.html -- V To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 17 2: 6:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.klondike.ru (unknown [195.170.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 30F7437B479 for <freebsd-hackers@freebsd.org>; Fri, 17 Nov 2000 02:06:46 -0800 (PST) Received: from freebsd.klondike.ru (freebsd [195.170.237.64]) by ns.klondike.ru (8.9.3/8.9.3) with SMTP id NAA15426 for <freebsd-hackers@freebsd.org>; Fri, 17 Nov 2000 13:06:39 +0300 (MSK) Message-Id: <200011171006.NAA15426@ns.klondike.ru> Date: Fri, 17 Nov 2000 13:06:10 +0000 From: Kaltashkin Eugene <zhecka@klondike.ru> To: freebsd-hackers@freebsd.org Subject: 2 interfaces on one machine X-Mailer: stuphead version 0.4.5 (GTK+ 1.2.8; FreeBSD 4.2-BETA; i386) Organization: Klondike 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 Hello. i have 2 interface netcard on one computer. This card have ip numbers from one net , eq 192.168.0.1 and 192.168.0.2 i see in log files message arp 192.168.0.2 is on lo0 but got reply from xx:xx:xx:xx on fxp0 ? what is it ? Best Regards. Zhecka. -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 17 3: 5:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from memogw1.sbb.ch (memogw1.sbb.ch [147.78.29.212]) by hub.freebsd.org (Postfix) with ESMTP id 7B8A137B479 for <freebsd-hackers@freebsd.org>; Fri, 17 Nov 2000 03:05:07 -0800 (PST) Received: from aeschbacher.com (I28405.sbb.ch [147.78.31.196]) by memogw1.sbb.ch (2.5 Build 2640 (Berkeley 8.8.6)/8.8.4) with ESMTP id MAA09729 for <freebsd-hackers@freebsd.org>; Fri, 17 Nov 2000 12:04:53 +0100 Message-ID: <3A151190.BDA43C48@aeschbacher.com> Date: Fri, 17 Nov 2000 12:08:00 +0100 From: Stefan Aeschbacher <stefan@aeschbacher.com> X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: 2 interfaces on one machine References: <200011171006.NAA15426@ns.klondike.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi the problem is, that you have the same subnet (indicated by the netmask) on two interfaces. The best solution to the problem is taking two different subnets, e.g. 192.168.0.0 netmask 255.255.255.0 on lo0 and 192.168.1.0 netmask 255.255.255.0 on fxp0. It is also possible to use the 192.168.0 net for both interfaces but the you have to set up something like this: 192.168.0.0 netmask 255.255.255.128 on lo0 and 192.168.0.128 netmask 255.255.255.128 on fxp0 (so you have ip 192.168.0.0-127 on lo0 and 192.168.128-255 on fxp0) Stefan Kaltashkin Eugene wrote: > > Hello. > > i have 2 interface netcard on one computer. > This card have ip numbers from one net , eq 192.168.0.1 and 192.168.0.2 > i see in log files message > arp 192.168.0.2 is on lo0 but got reply from xx:xx:xx:xx on fxp0 ? > > what is it ? > > Best Regards. > Zhecka. > -- > > 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 17 3:14:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.klondike.ru (unknown [195.170.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 5D3D937B479 for <freebsd-hackers@FreeBSD.ORG>; Fri, 17 Nov 2000 03:14:30 -0800 (PST) Received: from freebsd.klondike.ru (freebsd [195.170.237.64]) by ns.klondike.ru (8.9.3/8.9.3) with SMTP id OAA17251; Fri, 17 Nov 2000 14:14:08 +0300 (MSK) Message-Id: <200011171114.OAA17251@ns.klondike.ru> Date: Fri, 17 Nov 2000 14:13:39 +0000 From: Kaltashkin Eugene <zhecka@klondike.ru> To: Stefan Aeschbacher <stefan@aeschbacher.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 2 interfaces on one machine In-Reply-To: <3A151190.BDA43C48@aeschbacher.com> References: <200011171006.NAA15426@ns.klondike.ru> <3A151190.BDA43C48@aeschbacher.com> X-Mailer: stuphead version 0.4.5 (GTK+ 1.2.8; FreeBSD 4.2-BETA; i386) Organization: Klondike 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 On Fri, 17 Nov 2000 12:08:00 +0100 Stefan Aeschbacher <stefan@aeschbacher.com> wrote: SA> Hi SA> the problem is, that you have the same subnet (indicated by the netmask) SA> on two interfaces. The best solution to the problem is taking two SA> different subnets, e.g. 192.168.0.0 netmask 255.255.255.0 on lo0 SA> and 192.168.1.0 netmask 255.255.255.0 on fxp0. It is also possible SA> to use the 192.168.0 net for both interfaces but the you have to SA> set up something like this: 192.168.0.0 netmask 255.255.255.128 SA> on lo0 and 192.168.0.128 netmask 255.255.255.128 on fxp0 (so you have SA> ip 192.168.0.0-127 on lo0 and 192.168.128-255 on fxp0) hm I want to divide(share) transfer of the information into 2 interfaces. some adresses i can place as alias for lo0 but i want use 2 real adresses on one network in 2 interfaces. I have only one net and cannot use Ip address from other nets :( Best Regards. Zhecka. -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 17 3:38:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 28C0237B479; Fri, 17 Nov 2000 03:38:21 -0800 (PST) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JWNAX3CFWI00119G@research.kpn.com>; Fri, 17 Nov 2000 12:38:19 +0100 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id <SKHLH4HY>; Fri, 17 Nov 2000 12:38:18 +0100 Content-return: allowed Date: Fri, 17 Nov 2000 12:38:11 +0100 From: "Koster, K.J." <K.J.Koster@kpn.com> Subject: RE: More detail on Deskpro XL6200 NIC (was: Legacy ethernet cards in FreeBSD) To: "'wpaul@FreeBSD.ORG'" <wpaul@FreeBSD.ORG> Cc: 'FreeBSD Hackers mailing list' <freebsd-hackers@freebsd.org> Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D7A15@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: multipart/mixed; boundary="----_=_NextPart_000_01C0508A.E12A5732" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C0508A.E12A5732 Content-Type: text/plain; charset="iso-8859-1" > > *ahem* How about compiling a kernel *without* the pcn driver? > I want to know why you didn't consider this combination. (Well, I > know why: because giving me the answer straight away rather than > making me drag it out of you would have been too easy. I would never > be that lucky.) > I did not consider a kernel without pcn compiled in is because you asked me to use the pcn driver. If you want straight answers, ask straight questions. :) For your information, I did hack the kernel for the lnc driver to *not* probe for the card, because I (wrongly) guessed that perhaps the lnc probe was screwing things up for the pnc probe. I figured that disabling the lnc driver in the visual config would do the trick, but as I type this it occurs to me that that might only disable the ISA card probe. I've tried a kernel without the pnc driver compiled in. Clean build directory and cvsupped to RELENG_4 as of 30 minutes ago. (typed from the screen, names may be misspelled, number are corrent, dmesg output attached) Fatal trap 12: page fault in kernel mode fault virtaul address: 0x616776 fault code: supervisor read, page not present instruction ptr: 0x8:0x616776 stackprt: 0x10:0xc5d1bc4c frameptr: 0x10:0xc5d1bd0c code segment: base 0x0, limit 0xfffff, type 0x1b DPL 0, pres 1, def32 1 gran 1 processor eflags interrupt enabled, resume, IOPL 0 current proc. 1 (init) interrupt mask none trap nr 12 It just keeps getting better and better. *sigh* This is the first out of three machines that are to move up to 4.2. I planned a day for the first and an hour for each next one. I'm pretty sure the hardware is good. It survived a couple of buildworlds. It works in 4.0. I will see if I have time later today to rebuild the beast with kernel debugging stuff enabled to give more details. Right now I have other work to do. Are there any specific things that I should try? I'm a little lost. Kees Jan ================================================ You are only young once, but you can stay immature all your life. ------_=_NextPart_000_01C0508A.E12A5732 Content-Type: text/plain; name="dmesg.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="dmesg.txt" This is my own custom kernel (4.2) Nov 17 12:38:52 dl6101 /kernel: Copyright (c) 1992-2000 The FreeBSD = Project.=0A= Nov 17 12:38:52 dl6101 /kernel: Copyright (c) 1979, 1980, 1983, 1986, = 1988, 1989, 1991, 1992, 1993, 1994=0A= Nov 17 12:38:52 dl6101 /kernel: The Regents of the University of = California. All rights reserved.=0A= Nov 17 12:38:52 dl6101 /kernel: FreeBSD 4.2-BETA #0: Fri Nov 17 = 12:24:14 CET 2000=0A= Nov 17 12:38:52 dl6101 /kernel: = root@dl6101.research.kpn.com:/usr/src/sys/compile/QUAM=0A= Nov 17 12:38:52 dl6101 /kernel: Timecounter "i8254" frequency 1193182 = Hz=0A= Nov 17 12:38:52 dl6101 /kernel: Timecounter "TSC" frequency 200005039 = Hz=0A= Nov 17 12:38:52 dl6101 /kernel: CPU: Pentium Pro (200.01-MHz 686-class = CPU)=0A= Nov 17 12:38:52 dl6101 /kernel: Origin =3D "GenuineIntel" Id =3D 0x616 = Stepping =3D 6=0A= Nov 17 12:38:52 dl6101 /kernel: = Features=3D0xf9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CM= OV>=0A= Nov 17 12:38:52 dl6101 /kernel: real memory =3D 67108864 (65536K = bytes)=0A= Nov 17 12:38:52 dl6101 /kernel: avail memory =3D 62468096 (61004K = bytes)=0A= Nov 17 12:38:52 dl6101 /kernel: bios32: Bad BIOS32 Service Directory=0A= Nov 17 12:38:52 dl6101 /kernel: Preloaded elf kernel "kernel" at = 0xc02e6000.=0A= Nov 17 12:38:52 dl6101 /kernel: Pentium Pro MTRR support enabled=0A= Nov 17 12:38:52 dl6101 /kernel: npx0: <math processor> on = motherboard=0A= Nov 17 12:38:52 dl6101 /kernel: npx0: INT 16 interface=0A= Nov 17 12:38:52 dl6101 /kernel: pcib0: <Intel 82454KX/GX (Orion) host = to PCI bridge> on motherboard=0A= Nov 17 12:38:52 dl6101 /kernel: pci0: <PCI bus> on pcib0=0A= Nov 17 12:38:53 dl6101 /kernel: lnc0: <PCNet/PCI Ethernet adapter> port = 0x7000-0x701f irq 5 at device 11.0 on pci0=0A= Nov 17 12:38:53 dl6101 /kernel: lnc0: PCnet-32 VL-Bus address = 00:80:5f:fa:a0:82=0A= Nov 17 12:38:53 dl6101 /kernel: lnc0: driver is using old-style = compatability shims=0A= Nov 17 12:38:53 dl6101 /kernel: amd0: <Tekram DC390(T)/AMD53c974 SCSI = Host Adapter> port 0x7100-0x717f irq 10 at device 12.0 on pci0=0A= Nov 17 12:38:53 dl6101 /kernel: pci0: <Matrox MGA Millennium 2064W = graphics accelerator> at 13.0=0A= Nov 17 12:38:53 dl6101 /kernel: rl0: <RealTek 8139 10/100BaseTX> port = 0x7200-0x72ff mem 0x4300000-0x43000ff irq 9 at device 14.0 on pci0=0A= Nov 17 12:38:53 dl6101 /kernel: rl0: Ethernet address: = 00:e0:4c:68:5c:0c=0A= Nov 17 12:38:53 dl6101 /kernel: miibus0: <MII bus> on rl0=0A= Nov 17 12:38:53 dl6101 /kernel: rlphy0: <RealTek internal media = interface> on miibus0=0A= Nov 17 12:38:53 dl6101 /kernel: rlphy0: 10baseT, 10baseT-FDX, = 100baseTX, 100baseTX-FDX, auto=0A= Nov 17 12:38:53 dl6101 /kernel: isab0: <PCI to EISA bridge = (vendor=3D0e11 device=3D0001)> at device 15.0 on pci0=0A= Nov 17 12:38:53 dl6101 /kernel: eisa0: <EISA bus> on isab0=0A= Nov 17 12:38:53 dl6101 /kernel: mainboard0: <CPQ0521 (System Board)> on = eisa0 slot 0=0A= Nov 17 12:38:53 dl6101 /kernel: isa0: <ISA bus> on isab0=0A= Nov 17 12:38:53 dl6101 /kernel: chip0: <Intel 82453KX/GX (Orion) PCI = memory controller> at device 20.0 on pci0=0A= Nov 17 12:38:53 dl6101 /kernel: fdc0: <NEC 72065B or clone> at port = 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0=0A= Nov 17 12:38:53 dl6101 /kernel: fdc0: FIFO enabled, 8 bytes = threshold=0A= Nov 17 12:38:53 dl6101 /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive = 0=0A= Nov 17 12:38:53 dl6101 /kernel: atkbdc0: <Keyboard controller (i8042)> = at port 0x60,0x64 on isa0=0A= Nov 17 12:38:53 dl6101 /kernel: atkbd0: <AT Keyboard> flags 0x1 irq 1 = on atkbdc0=0A= Nov 17 12:38:53 dl6101 /kernel: kbd0 at atkbd0=0A= Nov 17 12:38:53 dl6101 /kernel: vga0: <Generic ISA VGA> at port = 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0=0A= Nov 17 12:38:53 dl6101 /kernel: sc0: <System console> at flags 0x100 on = isa0=0A= Nov 17 12:38:53 dl6101 /kernel: sc0: VGA <16 virtual consoles, = flags=3D0x300>=0A= Nov 17 12:38:53 dl6101 /kernel: Mounting root from ufs:/dev/da0s1a=0A= Nov 17 12:38:53 dl6101 /kernel: da0 at amd0 bus 0 target 0 lun 0=0A= Nov 17 12:38:53 dl6101 /kernel: da0: <COMPAQPC ST32430N 0554> Fixed = Direct Access SCSI-2 device =0A= Nov 17 12:38:53 dl6101 /kernel: da0: 10.000MB/s transfers (10.000MHz, = offset 15)=0A= Nov 17 12:38:53 dl6101 /kernel: da0: 2006MB (4110000 512 byte sectors: = 255H 63S/T 255C)=0A= Nov 17 12:38:53 dl6101 /kernel: cd0 at amd0 bus 0 target 5 lun 0=0A= Nov 17 12:38:53 dl6101 /kernel: cd0: <COMPAQ PD-1 LF-1094C B110> = Removable CD-ROM SCSI-2 device =0A= Nov 17 12:38:53 dl6101 /kernel: cd0: 5.000MB/s transfers (5.000MHz, = offset 8)=0A= Nov 17 12:38:53 dl6101 /kernel: cd0: Attempt to query device size = failed: NOT READY, Medium not present=0A= Nov 17 12:38:53 dl6101 /kernel: da1 at amd0 bus 0 target 5 lun 1=0A= Nov 17 12:38:53 dl6101 /kernel: da1: <COMPAQ PD-1 LF-1094C B110> = Removable Optical SCSI-2 device =0A= Nov 17 12:38:53 dl6101 /kernel: da1: 5.000MB/s transfers (5.000MHz, = offset 8)=0A= Nov 17 12:38:53 dl6101 /kernel: da1: Attempt to query device size = failed: NOT READY, Medium not present=0A= This is the GENERIC kernel (4.0) Nov 17 12:47:40 dl6101 /kernel.GENERIC: Copyright (c) 1992-2000 The = FreeBSD Project.=0A= Nov 17 12:47:40 dl6101 /kernel.GENERIC: Copyright (c) 1982, 1986, 1989, = 1991, 1993=0A= Nov 17 12:47:40 dl6101 /kernel.GENERIC: The Regents of the University = of California. All rights reserved.=0A= Nov 17 12:47:40 dl6101 /kernel.GENERIC: FreeBSD 4.0-RELEASE #0: Mon Mar = 20 22:50:22 GMT 2000=0A= Nov 17 12:47:40 dl6101 /kernel.GENERIC: = root@monster.cdrom.com:/usr/src/sys/compile/GENERIC=0A= Nov 17 12:47:40 dl6101 /kernel.GENERIC: Timecounter "i8254" frequency = 1193182 Hz=0A= Nov 17 12:47:40 dl6101 /kernel.GENERIC: CPU: Pentium Pro (200.00-MHz = 686-class CPU)=0A= Nov 17 12:47:40 dl6101 /kernel.GENERIC: Origin =3D "GenuineIntel" Id = =3D 0x616 Stepping =3D 6=0A= Nov 17 12:47:40 dl6101 /kernel.GENERIC: = Features=3D0xf9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CM= OV>=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: real memory =3D 67108864 = (65536K bytes)=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: avail memory =3D 61161472 = (59728K bytes)=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: bios32: Bad BIOS32 Service = Directory=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: Preloaded elf kernel = "kernel.GENERIC" at 0xc03c0000.=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: Pentium Pro MTRR support = enabled=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: md0: Malloc disk=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: npx0: <math processor> on = motherboard=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: npx0: INT 16 interface=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: pcib0: <Intel 82454KX/GX = (Orion) host to PCI bridge> on motherboard=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: pci0: <PCI bus> on pcib0=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: lnc0: <PCNet/PCI Ethernet = adapter> port 0x7000-0x701f irq 5 at device 11.0 on pci0=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: lnc0: supplying EUI64: = 00:80:5f:ff:fe:fa:a0:82=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: lnc0: PCnet-32 VL-Bus address = 00:80:5f:fa:a0:82=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: lnc0: driver is using old-style = compatability shims=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: amd0: <Tekram = DC390(T)/AMD53c974 SCSI Host Adapter> port 0x7100-0x717f irq 10 at = device 12.0 on pci0=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: amd0: driver is using old-style = compatability shims=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: pci0: <Matrox MGA Millennium = 2064W graphics accelerator> at 13.0=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: rl0: <RealTek 8139 = 10/100BaseTX> port 0x7200-0x72ff mem 0x4300000-0x43000ff irq 9 at = device 14.0 on pci0=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: rl0: Ethernet address: = 00:e0:4c:68:5c:0c=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: miibus0: <MII bus> on rl0=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: rlphy0: <RealTek internal media = interface> on miibus0=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: rlphy0: 10baseT, 10baseT-FDX, = 100baseTX, 100baseTX-FDX, auto=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: isab0: <PCI to EISA bridge = (vendor=3D0e11 device=3D0001)> at device 15.0 on pci0=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: eisa0: <EISA bus> on isab0=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: mainboard0: <CPQ0521 (System = Board)> on eisa0 slot 0=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: isa0: <ISA bus> on isab0=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: chip0: <Intel 82453KX/GX = (Orion) PCI memory controller> at device 20.0 on pci0=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: fdc0: <NEC 72065B or clone> at = port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: fdc0: FIFO enabled, 8 bytes = threshold=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: fd0: <1440-KB 3.5" drive> on = fdc0 drive 0=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: atkbdc0: <keyboard controller = (i8042)> at port 0x60-0x6f on isa0=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: atkbd0: <AT Keyboard> irq 1 on = atkbdc0=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: vga0: <Generic ISA VGA> at port = 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: sc0: <System console> on = isa0=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: sc0: VGA <16 virtual consoles, = flags=3D0x200>=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: sio0 at port 0x3f8-0x3ff irq 4 = flags 0x10 on isa0=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: sio0: type 16550A=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: sio1 at port 0x2f8-0x2ff irq 3 = on isa0=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: sio1: type 16550A=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: ppc0: <Parallel port> at port = 0x378-0x37f irq 7 on isa0=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: ppc0: Generic chipset = (NIBBLE-only) in COMPATIBLE mode=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: ppi0: <Parallel I/O> on = ppbus0=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: lpt0: <Printer> on ppbus0=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: lpt0: Interrupt-driven port=0A= Nov 17 12:47:41 dl6101 /kernel.GENERIC: plip0: <PLIP network interface> = on ppbus0=0A= Nov 17 12:47:42 dl6101 /kernel.GENERIC: Waiting 15 seconds for SCSI = devices to settle=0A= Nov 17 12:47:42 dl6101 /kernel.GENERIC: Mounting root from = ufs:/dev/da0s1a=0A= Nov 17 12:47:42 dl6101 /kernel.GENERIC: da0 at amd0 bus 0 target 0 lun = 0=0A= Nov 17 12:47:42 dl6101 /kernel.GENERIC: da0: <COMPAQPC ST32430N 0554> = Fixed Direct Access SCSI-2 device =0A= Nov 17 12:47:42 dl6101 /kernel.GENERIC: da0: 10.000MB/s transfers = (10.000MHz, offset 15)=0A= Nov 17 12:47:42 dl6101 /kernel.GENERIC: da0: 2006MB (4110000 512 byte = sectors: 255H 63S/T 255C)=0A= Nov 17 12:47:42 dl6101 /kernel.GENERIC: cd0 at amd0 bus 0 target 5 lun = 0=0A= Nov 17 12:47:42 dl6101 /kernel.GENERIC: cd0: <COMPAQ PD-1 LF-1094C = B110> Removable CD-ROM SCSI-2 device =0A= Nov 17 12:47:42 dl6101 /kernel.GENERIC: cd0: 5.000MB/s transfers = (5.000MHz, offset 8)=0A= Nov 17 12:47:42 dl6101 /kernel.GENERIC: cd0: Attempt to query device = size failed: NOT READY, Medium not present=0A= Nov 17 12:47:42 dl6101 /kernel.GENERIC: da1 at amd0 bus 0 target 5 lun = 1=0A= Nov 17 12:47:42 dl6101 /kernel.GENERIC: da1: <COMPAQ PD-1 LF-1094C = B110> Removable Optical SCSI-2 device =0A= Nov 17 12:47:42 dl6101 /kernel.GENERIC: da1: 5.000MB/s transfers = (5.000MHz, offset 8)=0A= Nov 17 12:47:42 dl6101 /kernel.GENERIC: da1: Attempt to query device = size failed: NOT READY, Medium not present=0A= Nov 17 12:47:42 dl6101 /kernel.GENERIC: WARNING: / was not properly = dismounted=0A= Nov 17 12:47:42 dl6101 /kernel.GENERIC: lnc0: starting DAD for = fe80:0001::0280:5fff:fefa:a082=0A= Nov 17 12:47:42 dl6101 /kernel.GENERIC: lnc0: DAD complete for = fe80:0001::0280:5fff:fefa:a082 - no duplicates found=0A= Nov 17 12:47:44 dl6101 /kernel.GENERIC: pid 157 (sendmail), uid 0: = exited on signal 12=0A= Nov 17 12:48:05 dl6101 login: ROOT LOGIN (root) ON ttyv0=0A= ------_=_NextPart_000_01C0508A.E12A5732-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 17 4: 0: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from euromail1.genrad.com (x207.genrad.co.uk [195.99.3.207]) by hub.freebsd.org (Postfix) with ESMTP id CAE8F37B479; Fri, 17 Nov 2000 04:00:04 -0800 (PST) Received: from CDP437 (cdp437.uk.genrad.com [132.223.135.120]) by euromail1.genrad.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id W7W2XV8W; Fri, 17 Nov 2000 11:59:59 -0000 From: Robert Swindells <swindellsr@genrad.co.uk> To: K.J.Koster@kpn.com Cc: wpaul@FreeBSD.ORG, freebsd-hackers@freebsd.org In-reply-to: <59063B5B4D98D311BC0D0001FA7E4522026D7A15@l04.research.kpn.com> (K.J.Koster@kpn.com) Subject: Re: More detail on Deskpro XL6200 NIC (was: Legacy ethernet cards in FreeBSD) Reply-To: rjs@fdy2.demon.co.uk Message-Id: <20001117120004.CAE8F37B479@hub.freebsd.org> Date: Fri, 17 Nov 2000 04:00:04 -0800 (PST) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There used to be some very strange code in the lnc driver that relied on the ISA probe for the original PCnet-PCI device failing, then probed it in the if_lnc_pci stub. Your card shouldn't really be identified as a VL-Bus one when it is a PCI device, so maybe the lnc probe has been broken by the removal of it's PCI stub that used to be in pci/if_lnc_pci.c The datasheet for the 79C970 doesn't seem to be available on AMD's website anymore, so I couldn't check on the device ID, but I think that the one specified in the header was deliberately incorrect. Robert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 17 5: 3:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from memogw1.sbb.ch (memogw1.sbb.ch [147.78.29.212]) by hub.freebsd.org (Postfix) with ESMTP id 9BF8337B4CF for <freebsd-hackers@FreeBSD.ORG>; Fri, 17 Nov 2000 05:03:46 -0800 (PST) Received: from aeschbacher.com (I28405.sbb.ch [147.78.31.196]) by memogw1.sbb.ch (2.5 Build 2640 (Berkeley 8.8.6)/8.8.4) with ESMTP id OAA12892; Fri, 17 Nov 2000 14:02:57 +0100 Message-ID: <3A152D3D.625E37D2@aeschbacher.com> Date: Fri, 17 Nov 2000 14:06:05 +0100 From: Stefan Aeschbacher <stefan@aeschbacher.com> X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Kaltashkin Eugene <zhecka@klondike.ru> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 2 interfaces on one machine References: <200011171006.NAA15426@ns.klondike.ru> <3A151190.BDA43C48@aeschbacher.com> <200011171114.OAA17251@ns.klondike.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i don't know if i understand exactly what you want but the following setup could work: lo0 has ip-address 192.168.0.1 and netmask 255.255.255.128 the computers connected to this interface can have the ip-addresses: 192.168.0.2-192.168.0.126 (broadcast ip for this subnet is 192.168.0.127) fxp0 has ip-address 192.168.0.129 and netmask 255.255.255.128 the computers connected to this interface can have the ip-addresses: 192.168.0.130-192.168.0.255 (broadcast ip for this subnet is 192.168.0.256) Kaltashkin Eugene wrote: > [snip] > hm > I want to divide(share) transfer of the information into 2 interfaces. > some adresses i can place as alias for lo0 but i want use 2 real adresses on > one network in 2 interfaces. > I have only one net and cannot use Ip address from other nets :( > > Best Regards. > Zhecka. > > -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 17 10:44:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id C48A137B479; Fri, 17 Nov 2000 10:44:42 -0800 (PST) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JWNPSQ5C100011FZ@research.kpn.com>; Fri, 17 Nov 2000 19:44:41 +0100 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id <SKHLHXFW>; Fri, 17 Nov 2000 19:44:40 +0100 Content-return: allowed Date: Fri, 17 Nov 2000 19:44:34 +0100 From: "Koster, K.J." <K.J.Koster@kpn.com> Subject: RE: More detail on Deskpro XL6200 NIC (was: Legacy ethernet cards in FreeBSD) To: "'wpaul@FreeBSD.ORG'" <wpaul@FreeBSD.ORG> Cc: freebsd-hackers@FreeBSD.ORG Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D7A2F@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Bill, I've cvsupped, which gave me the patched version of the pcn driver. Thanks for the prompt response. I've build various kernels. Kernel with pcn and lnc compiled in: trap 12 Kernel with lnc only: trap 12 Kernel with pcn only: works, but no network Kernel with neihter: works, but no network A backtrace reveals that the box dies with trap 12 in the function: __set_videodriver_set_sym_vga_driver() alloc_scp() scopen() cnopen() spec_open() spec_vnoperate() ufs_vnoperatespec() vn_open() open() syscall2() Xint0x80_syscall() The last thing that the box prints is "Addtional TCP options: ." and then the date. *beng* trap 12 etc.... Yes, it does print the "." in the end, so it completes the additional TCP options successfully. I'm lost here. If anyone has any suggestions I will happily try them on Monday. Otherwise I'm moving down a version or two. Right now I'm going home for the weekend (to a system that actually *works*). Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 17 12:10:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 039CD37B479 for <hackers@FreeBSD.org>; Fri, 17 Nov 2000 12:10:15 -0800 (PST) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 5AF4E3E4F; Fri, 17 Nov 2000 21:10:13 +0100 (CET) Date: Fri, 17 Nov 2000 21:10:13 +0100 From: Jesper Skriver <jesper@skriver.dk> To: hackers@FreeBSD.org Subject: React to ICMP administratively prohibited ? Message-ID: <20001117211013.C9227@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm currently looking at how various operating systems react to a 'ICMP administratively prohibited'. My motivation is setup's where access to the primary mailserver is blocked by filters (usually to block open relay's), and all mail has to go via the backup MX, a example from a customer of ours. jesper@freesbee$ host -t mx nemo.dyndns.dk nemo.dyndns.dk mail is handled (pri=10) by nemo.dyndns.dk nemo.dyndns.dk mail is handled (pri=20) by backup-mx.post.tele.dk Here we block access to tcp/25 on nemo.dyndns.dk (a ADSL users), but provide a backup MX for him to use, but when a mailserver wants to send mail to him, they will experience a timeout before sending the mail to backup-mx.post.tele.dk, which can send the mail onwards to nemo.dyndns.dk. This timeout could be avoided if the sending mail server reacted to the 'ICMP administratively prohibited' they got from our router. 20:57:03.799129 193.162.74.6.1071 > 193.89.247.125.25: S 831128672:831128672(0) win 16384 <mss 1460> (DF) [tos 0x10] 20:57:03.818322 195.249.14.202 > 193.162.74.6: icmp: host 193.89.247.125 unreachable - admin prohibited filter 20:57:06.797061 193.162.74.6.1071 > 193.89.247.125.25: S 831128672:831128672(0) win 16384 <mss 1460> (DF) [tos 0x10] 20:57:06.812424 195.249.14.202 > 193.162.74.6: icmp: host 193.89.247.125 unreachable - admin prohibited filter FreeBSD (as of last saturdays -current atleast) doesn't react to this $ telnet nemo.dyndns.dk 25 Trying 193.89.247.125... Of the other operating systems we've looked at (win2k, linux and solaris), only linux react to this. $ telnet nemo.dyndns.dk 25 Trying 193.89.247.125... telnet: Unable to connect to remote host: No route to host $ uname -a Linux xyz.dk 2.0.32 #1 Wed Nov 19 00:46:45 EST 1997 i586 unknown Wouldn't it be a idea to implement a similar behaviour in FreeBSD ? /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 17 12:49:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.alacritech.com (smtp.alacritech.com [209.10.208.82]) by hub.freebsd.org (Postfix) with ESMTP id 61E3337B479 for <freebsd-hackers@FreeBSD.ORG>; Fri, 17 Nov 2000 12:49:21 -0800 (PST) Received: from [10.1.10.22] by smtp.alacritech.com (NTMail 4.30.0012/NY3553.00.2884f51f) with ESMTP id mzxkaaaa for <freebsd-hackers@FreeBSD.ORG>; Fri, 17 Nov 2000 12:46:21 -0800 From: "Christopher Harrer" <charrer@alacritech.com> To: "Freebsd-Hackers" <freebsd-hackers@FreeBSD.ORG> Subject: Remote GDB Date: Fri, 17 Nov 2000 15:46:41 -0500 Message-ID: <POELKPJGDHAPIPMEMHGAIEPJCNAA.charrer@alacritech.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_00AC_01C050AD.948089B0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-MS-TNEF-Correlator: <POELKPJGDHAPIPMEMHGAIEPJCNAA.charrer@alacritech.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_00AC_01C050AD.948089B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hello All, Is there a way to "break" into a gdb (using remote GDB) while a FreeBSD system under test is running? I've tried ^C with no success (meaning I never stop execution). Also, I've tried "interrupt" from the button menu in DDD. Thanks! Chris Chris Harrer Alacritech, Inc. 403 West Lincoln Hwy. Suite 108 Exton, PA 19341 w-(484)875-9520 c-(484)433-5767 ------=_NextPart_000_00AC_01C050AD.948089B0 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="winmail.dat" eJ8+IikUAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEGgAMADgAAANAHCwARAA8ALgAAAAUANQEB A5AGAEwGAAAlAAAACwACAAEAAAALACMAAAAAAAMAJgAAAAAACwApAAAAAAADADYAAAAAAB4AcAAB AAAACwAAAFJlbW90ZSBHREIAAAIBcQABAAAAFgAAAAHAUNd8yVrHKGHNu00esNntEczhPHgAAAIB HQwBAAAAHAAAAFNNVFA6Q0hBUlJFUkBBTEFDUklURUNILkNPTQALAAEOAAAAAEAABg4AtHVk11DA AQIBCg4BAAAAGAAAAAAAAAB9dTnDQNb+S6+WSnq2B4e2woAAAAsAHw4BAAAAAgEJEAEAAADsAQAA 6AEAAIMCAABMWkZ1euxtHgMACgByY3BnMTI1FjIA+Atgbg4QMDMzTwH3AqQD4wIAY2gKwHPwZXQw IAcTAoMAUARVfxDJCFUHsgKDDlAD1RF1fSUKgXYIkHdrC4BkNB0MYGMAUAsDC7UgSGXubAkAEWAX YCwKogqECoASSQQgdGgEkGUgYTAgd2F5GMAXgCJi4QlwYWsiIAuAGZEZMMBnZGIgKHUAkA8gFiAJ cARgdBkQR0RCWikZQGgDEBkSRgnRQkBTRCBzeXMboG38IHUV8BOhG6AdQBowBCAOch2QAwAPID8g IEkUJ3YZEHQIgWQgXkpDGUBpGNAgbheAc+0WMGMHkAQgKAeAAHAbIjpJIDBlHzAFwB1Ab3CIIGV4 BZB1dGkCIIwpLh7wF6BzbywfCv4iGkEEkB5wBTAaIANSGMI8IGIikBmQA6AHgG51qRoxIEQmcC4X 6lQQ8JBua3MhF+pDaAUQ9xCwF/kWZTETQCiyFzAKwP0JcHIX5BegANAFEBugEOApI2FuYyalNA9Q IFcdHgJMC4AI4QOgSHd5qSalU3UrsSAPQDgX5ExFeCWxI2BQQS7AOQwzNBZTGCZ3LSg0ADg0KTg3 NS05Vw5AAUAX82MxJDQPYC3wNTc2NxQxHvApWzH1BRVRADUgCwABgAggBgAAAAAAwAAAAAAAAEYA AAAAA4UAAAAAAAADAAOACCAGAAAAAADAAAAAAAAARgAAAAAQhQAAAAAAAAMAB4AIIAYAAAAAAMAA AAAAAABGAAAAAFKFAAAnagEAHgAJgAggBgAAAAAAwAAAAAAAAEYAAAAAVIUAAAEAAAAEAAAAOS4w AB4ACoAIIAYAAAAAAMAAAAAAAABGAAAAADaFAAABAAAAAQAAAAAAAAAeAAuACCAGAAAAAADAAAAA AAAARgAAAAA3hQAAAQAAAAEAAAAAAAAAHgAMgAggBgAAAAAAwAAAAAAAAEYAAAAAOIUAAAEAAAAB AAAAAAAAAAsADYAIIAYAAAAAAMAAAAAAAABGAAAAAIKFAAABAAAACwA6gAggBgAAAAAAwAAAAAAA AEYAAAAADoUAAAAAAAADADyACCAGAAAAAADAAAAAAAAARgAAAAARhQAAAAAAAAMAPYAIIAYAAAAA AMAAAAAAAABGAAAAABiFAAAAAAAACwBSgAggBgAAAAAAwAAAAAAAAEYAAAAABoUAAAAAAAADAFOA CCAGAAAAAADAAAAAAAAARgAAAAABhQAAAAAAAAIB+A8BAAAAEAAAAH11OcNA1v5Lr5ZKerYHh7YC AfoPAQAAABAAAAB9dTnDQNb+S6+WSnq2B4e2AgH7DwEAAACXAAAAAAAAADihuxAF5RAaobsIACsq VsIAAFBTVFBSWC5ETEwAAAAAAAAAAE5JVEH5v7gBAKoAN9luAAAAQzpcRG9jdW1lbnRzIGFuZCBT ZXR0aW5nc1xjaHJpc1xMb2NhbCBTZXR0aW5nc1xBcHBsaWNhdGlvbiBEYXRhXE1pY3Jvc29mdFxP dXRsb29rXG91dGxvb2sucHN0AAADAP4PBQAAAAMADTT9NwAAAgF/AAEAAAA2AAAAPFBPRUxLUEpH REhBUElQTUVNSEdBSUVQSkNOQUEuY2hhcnJlckBhbGFjcml0ZWNoLmNvbT4AAAADAAYQVPG4dgMA BxAjAQAAAwAQEAAAAAADABEQAAAAAB4ACBABAAAAZQAAAEhFTExPQUxMLElTVEhFUkVBV0FZVE8i QlJFQUsiSU5UT0FHREIoVVNJTkdSRU1PVEVHREIpV0hJTEVBRlJFRUJTRFNZU1RFTVVOREVSVEVT VElTUlVOTklORz9JVkVUUklFREMAAAAAX1Q= ------=_NextPart_000_00AC_01C050AD.948089B0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 17 12:53:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.alacritech.com (smtp.alacritech.com [209.10.208.82]) by hub.freebsd.org (Postfix) with ESMTP id 8D9A237B479 for <freebsd-hackers@FreeBSD.ORG>; Fri, 17 Nov 2000 12:53:16 -0800 (PST) Received: from [10.1.10.22] by smtp.alacritech.com (NTMail 4.30.0012/NY3553.00.2884f51f) with ESMTP id szxkaaaa for <freebsd-hackers@FreeBSD.ORG>; Fri, 17 Nov 2000 12:50:14 -0800 From: "Christopher Harrer" <charrer@alacritech.com> To: "Freebsd-Hackers" <freebsd-hackers@FreeBSD.ORG> Subject: Remote GDB Date: Fri, 17 Nov 2000 15:50:33 -0500 Message-ID: <POELKPJGDHAPIPMEMHGAMEPKCNAA.charrer@alacritech.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello All, Is there a way to "break" into a gdb (using remote GDB) while a FreeBSD system under test is running? I've tried ^C with no success (meaning I never stop execution). Also, I've tried "interrupt" from the button menu in DDD. Thanks! Chris Chris Harrer Alacritech, Inc. 403 West Lincoln Hwy. Suite 108 Exton, PA 19341 w-(484)875-9520 c-(484)433-5767 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 17 13:48:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 3D7B137B479 for <freebsd-hackers@freebsd.org>; Fri, 17 Nov 2000 13:48:18 -0800 (PST) Received: from harare-60.budapest.interware.hu ([195.70.50.60] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 13wtMm-0007vT-00; Fri, 17 Nov 2000 22:48:17 +0100 Message-ID: <3A15A780.18CA7F66@elischer.org> Date: Fri, 17 Nov 2000 13:47:44 -0800 From: Julian Elischer <julian@elischer.org> X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Christopher Harrer <charrer@alacritech.com> Cc: Freebsd-Hackers <freebsd-hackers@FreeBSD.ORG> Subject: Re: Remote GDB References: <POELKPJGDHAPIPMEMHGAIEPJCNAA.charrer@alacritech.com> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christopher Harrer wrote: > > Hello All, > > Is there a way to "break" into a gdb (using remote GDB) while a FreeBSD > system under test is running? I've tried ^C with no success (meaning I > never stop execution). Also, I've tried "interrupt" from the button menu in do you mean kernel debugging? --on the console type the following keystrokes-- <ALT><CTL><ESC> g s then start the remote gdb.. > DDD. > > Thanks! > > Chris > > Chris Harrer > Alacritech, Inc. > 403 West Lincoln Hwy. > Suite 108 > Exton, PA 19341 > > w-(484)875-9520 > c-(484)433-5767 > > ------------------------------------------------------------------------ > Name: winmail.dat > winmail.dat Type: application/ms-tnef > Encoding: base64 -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 17 13:51: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.alacritech.com (smtp.alacritech.com [209.10.208.82]) by hub.freebsd.org (Postfix) with ESMTP id 9F10F37B479 for <freebsd-hackers@FreeBSD.ORG>; Fri, 17 Nov 2000 13:50:58 -0800 (PST) Received: from [10.1.10.22] by smtp.alacritech.com (NTMail 4.30.0012/NY3553.00.2884f51f) with ESMTP id pbykaaaa for <freebsd-hackers@FreeBSD.ORG>; Fri, 17 Nov 2000 13:48:01 -0800 From: "Christopher Harrer" <charrer@alacritech.com> To: "Julian Elischer" <julian@elischer.org> Cc: "Freebsd-Hackers" <freebsd-hackers@FreeBSD.ORG> Subject: RE: Remote GDB Date: Fri, 17 Nov 2000 16:48:20 -0500 Message-ID: <POELKPJGDHAPIPMEMHGAIEPNCNAA.charrer@alacritech.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <3A15A780.18CA7F66@elischer.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, that's what I mean. I've already gotten the remote kernel debugging started. What I want to do is at some point after running for a while, from the remote gdb terminal "break" into the running kernel. In other systems, I was able to do this by entering a ^c from the gdb terminal. It doesn't work in this environment. Any ideas? Thanks. Chris -----Original Message----- From: owner-freebsd-hackers@FreeBSD.ORG [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Julian Elischer Sent: Friday, November 17, 2000 4:48 PM To: Christopher Harrer Cc: Freebsd-Hackers Subject: Re: Remote GDB Christopher Harrer wrote: > > Hello All, > > Is there a way to "break" into a gdb (using remote GDB) while a FreeBSD > system under test is running? I've tried ^C with no success (meaning I > never stop execution). Also, I've tried "interrupt" from the button menu in do you mean kernel debugging? --on the console type the following keystrokes-- <ALT><CTL><ESC> g s then start the remote gdb.. > DDD. > > Thanks! > > Chris > > Chris Harrer > Alacritech, Inc. > 403 West Lincoln Hwy. > Suite 108 > Exton, PA 19341 > > w-(484)875-9520 > c-(484)433-5767 > > ------------------------------------------------------------------------ > Name: winmail.dat > winmail.dat Type: application/ms-tnef > Encoding: base64 -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v 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 17 14: 5:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.alacritech.com (smtp.alacritech.com [209.10.208.82]) by hub.freebsd.org (Postfix) with ESMTP id A749D37B479 for <freebsd-hackers@FreeBSD.ORG>; Fri, 17 Nov 2000 14:05:09 -0800 (PST) Received: from [10.1.10.22] by smtp.alacritech.com (NTMail 4.30.0012/NY3553.00.2884f51f) with ESMTP id bcykaaaa for <freebsd-hackers@FreeBSD.ORG>; Fri, 17 Nov 2000 14:02:11 -0800 From: "Christopher Harrer" <charrer@alacritech.com> To: "Christopher Harrer" <charrer@alacritech.com>, "Julian Elischer" <julian@elischer.org> Cc: "Freebsd-Hackers" <freebsd-hackers@FreeBSD.ORG> Subject: RE: Remote GDB Date: Fri, 17 Nov 2000 17:02:29 -0500 Message-ID: <POELKPJGDHAPIPMEMHGAAEPOCNAA.charrer@alacritech.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <POELKPJGDHAPIPMEMHGAIEPNCNAA.charrer@alacritech.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Duh, nevermind, thanks Julian. -----Original Message----- From: owner-freebsd-hackers@FreeBSD.ORG [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Christopher Harrer Sent: Friday, November 17, 2000 4:48 PM To: Julian Elischer Cc: Freebsd-Hackers Subject: RE: Remote GDB Yes, that's what I mean. I've already gotten the remote kernel debugging started. What I want to do is at some point after running for a while, from the remote gdb terminal "break" into the running kernel. In other systems, I was able to do this by entering a ^c from the gdb terminal. It doesn't work in this environment. Any ideas? Thanks. Chris -----Original Message----- From: owner-freebsd-hackers@FreeBSD.ORG [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Julian Elischer Sent: Friday, November 17, 2000 4:48 PM To: Christopher Harrer Cc: Freebsd-Hackers Subject: Re: Remote GDB Christopher Harrer wrote: > > Hello All, > > Is there a way to "break" into a gdb (using remote GDB) while a FreeBSD > system under test is running? I've tried ^C with no success (meaning I > never stop execution). Also, I've tried "interrupt" from the button menu in do you mean kernel debugging? --on the console type the following keystrokes-- <ALT><CTL><ESC> g s then start the remote gdb.. > DDD. > > Thanks! > > Chris > > Chris Harrer > Alacritech, Inc. > 403 West Lincoln Hwy. > Suite 108 > Exton, PA 19341 > > w-(484)875-9520 > c-(484)433-5767 > > ------------------------------------------------------------------------ > Name: winmail.dat > winmail.dat Type: application/ms-tnef > Encoding: base64 -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 17 14:29:14 2000 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 6D46237B4C5 for <hackers@FreeBSD.ORG>; Fri, 17 Nov 2000 14:29:12 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAHMT5222711; Fri, 17 Nov 2000 14:29:05 -0800 (PST) Date: Fri, 17 Nov 2000 14:29:04 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: Jesper Skriver <jesper@skriver.dk> Cc: hackers@FreeBSD.ORG Subject: Re: React to ICMP administratively prohibited ? Message-ID: <20001117142904.T18037@fw.wintelcom.net> References: <20001117211013.C9227@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001117211013.C9227@skriver.dk>; from jesper@skriver.dk on Fri, Nov 17, 2000 at 09:10:13PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jesper Skriver <jesper@skriver.dk> [001117 12:11] wrote: [snip] > > This timeout could be avoided if the sending mail server reacted to the > 'ICMP administratively prohibited' they got from our router. [snip] > > $ telnet nemo.dyndns.dk 25 > Trying 193.89.247.125... > telnet: Unable to connect to remote host: No route to host > $ uname -a > Linux xyz.dk 2.0.32 #1 Wed Nov 19 00:46:45 EST 1997 i586 unknown > > Wouldn't it be a idea to implement a similar behaviour in FreeBSD ? Probably not, what if one started a stream of spoofed ICMP lying about the state of the route between the two machines? I have the impression that the Linux box wouldn't be able to connect because of this behavior. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 17 14:57: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 58FDB37B479 for <freebsd-hackers@freebsd.org>; Fri, 17 Nov 2000 14:57:05 -0800 (PST) Received: (from gallatin@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id OAA47717 for freebsd-hackers@freebsd.org; Fri, 17 Nov 2000 14:57:05 -0800 (PST) (envelope-from gallatin@FreeBSD.org) Date: Fri, 17 Nov 2000 14:57:05 -0800 (PST) From: <gallatin@FreeBSD.org> Message-Id: <200011172257.OAA47717@freefall.freebsd.org> To: freebsd-hackers@freebsd.org Subject: FreeBSD papers at Freenix Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm on USENIX's Freenix program committee this year and have been asked to recruit submissions from FreeBSD developers for refereed track papers. I've already sent targeted solicitations to a handful of people, however I'm certainly overlooking people who are doing exciting, researchy stuff with FreeBSD. If you're doing something cool and would like to let others outside the FreeBSD community know about your project, this is an excellent opportunity. The Freenix track is very well attended. And remember that Freenix papers are very good PR for FreeBSD. The submission deadline is Monday, Nov. 27. You only need to submit a 1-3 page extended abstract by that date. More detailed information about Freenix is available at http://www.usenix.org/events/usenix01/cfp/freenix.html Finally, if you know of somebody who is not a committer, but is doing good work with FreeBSD or open source software in general, please pass this note along. Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 17 14:58: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from po3.glue.umd.edu (po3.glue.umd.edu [128.8.10.123]) by hub.freebsd.org (Postfix) with ESMTP id 6EBAD37B479 for <freebsd-hackers@FreeBSD.ORG>; Fri, 17 Nov 2000 14:58:04 -0800 (PST) Received: from glue.umd.edu (poseidon.student.umd.edu [129.2.144.21]) by po3.glue.umd.edu (8.10.1/8.10.1) with ESMTP id eAHMvra28413; Fri, 17 Nov 2000 17:57:54 -0500 (EST) Message-ID: <3A15B7F1.325854FB@glue.umd.edu> Date: Fri, 17 Nov 2000 17:57:53 -0500 From: Brandon Fosdick <bfoz@glue.umd.edu> X-Mailer: Mozilla 4.74 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kaltashkin Eugene <zhecka@klondike.ru> Cc: Stefan Aeschbacher <stefan@aeschbacher.com>, freebsd-hackers@FreeBSD.ORG Subject: Re: 2 interfaces on one machine References: <200011171006.NAA15426@ns.klondike.ru> <3A151190.BDA43C48@aeschbacher.com> <200011171114.OAA17251@ns.klondike.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kaltashkin Eugene wrote: > > On Fri, 17 Nov 2000 12:08:00 +0100 > Stefan Aeschbacher <stefan@aeschbacher.com> wrote: > > SA> Hi > SA> the problem is, that you have the same subnet (indicated by the netmask) > SA> on two interfaces. The best solution to the problem is taking two > SA> different subnets, e.g. 192.168.0.0 netmask 255.255.255.0 on lo0 > SA> and 192.168.1.0 netmask 255.255.255.0 on fxp0. It is also possible > SA> to use the 192.168.0 net for both interfaces but the you have to > SA> set up something like this: 192.168.0.0 netmask 255.255.255.128 > SA> on lo0 and 192.168.0.128 netmask 255.255.255.128 on fxp0 (so you have > SA> ip 192.168.0.0-127 on lo0 and 192.168.128-255 on fxp0) > > hm > I want to divide(share) transfer of the information into 2 interfaces. > some adresses i can place as alias for lo0 but i want use 2 real adresses on > one network in 2 interfaces. > I have only one net and cannot use Ip address from other nets :( Are you talking about channel bonding? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 17 15: 4:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from downserv.kjkoster.org (213-84-15-12.adsl.xs4all.nl [213.84.15.12]) by hub.freebsd.org (Postfix) with ESMTP id DAB5437B479 for <freebsd-hackers@freebsd.org>; Fri, 17 Nov 2000 15:04:48 -0800 (PST) Received: from tccn.cs.kun.nl (likeever.kjkoster.org [192.168.0.1]) by downserv.kjkoster.org (8.11.1/8.11.0) with ESMTP id eAHN4Xi10515 for <freebsd-hackers@freebsd.org>; Sat, 18 Nov 2000 00:04:33 +0100 (CET) (envelope-from dutchman@tccn.cs.kun.nl) Message-ID: <3A15B980.B65FFBB4@tccn.cs.kun.nl> Date: Sat, 18 Nov 2000 00:04:32 +0100 From: Kees Jan Koster <dutchman@tccn.cs.kun.nl> X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-BETA i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Audio and PS/2 mouse success stories Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear All, When I said that I was going home to a system that actually works I really meant it: Upgrading my home box to FreeBSD 4.2-beta has given me working audio on my Asus k7v motherboard (using the pcm driver and option PNPBIOS). The dreaded out of sync errors from the (logitech cordless) PS/2 mouse are also gone, even without the disable/enable hack patch that I used before. For this machine, 4.2 is a big step forward. Great work everyone. Thank you, thank you! Enjoy, Kees Jan PS. Now if only I could get my Deskpro XL 6200's to work with 4.2. :-) ---------------------------------------------------------------------- Kees Jan Koster e-mail: dutchman "at" tccn.cs.kun.nl ---------------------------------------------------------------------- Calvin: "Sometimes the world seems like a pretty mean place." Hobbes: "That's why animals are so soft and huggy." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 17 16:12:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 9922C37B479 for <freebsd-hackers@freebsd.org>; Fri, 17 Nov 2000 16:12:50 -0800 (PST) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id SAA11240 for freebsd-hackers@freebsd.org; Fri, 17 Nov 2000 18:12:49 -0600 (CST) Date: Fri, 17 Nov 2000 18:12:49 -0600 (CST) From: Mohit Aron <aron@cs.rice.edu> Message-Id: <200011180012.SAA11240@cs.rice.edu> To: freebsd-hackers@freebsd.org Subject: slab allocator for FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, does anyone know of a slab allocator implementation for BSD ? Linux now supports a slab allocator in the kernel for efficient allocation and deallocation of memory objects. - Mohit P.S. more info on slab allocator can be obtained from the USENIX 1994 paper: http://www.usenix.org/publications/library/proceedings/bos94/bonwick.htm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 17 21:31:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id CD51C37B4C5 for <hackers@freebsd.org>; Fri, 17 Nov 2000 21:31:40 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13x0co-0000DM-00; Fri, 17 Nov 2000 22:33:18 -0700 Message-ID: <3A16149E.B2B42267@softweyr.com> Date: Fri, 17 Nov 2000 22:33:18 -0700 From: Wes Peters <wes@softweyr.com> Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: barry@Lustig.COM Cc: Terry Lambert <tlambert@primenet.com>, hackers@FreeBSD.ORG Subject: Re: "iowait" CPU state References: <200011151730.KAA12666@usr01.primenet.com> <20001115204128.12980.qmail@devious.lustig.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Barry Lustig wrote: > > On Wed, 15 Nov 2000, Terry Lambert wrote: > > > > I'm always tempted to set up a company where the main > > engineers have a centralized batch compile server, so as to > > not slow down developement, but requiring that they run no > > better than a 386SX/16 on their desktop. If they are good, > > I'd give them a full 8M of real RAM, instead of 4M. > > > > That's what they did at NeXT. The engineers got machines with slower > processors and small amounts of RAM. It was designed to encourage them to > produce fast efficient code. So all you guys running dual PIIIs send them to me, I'll replace them with some lovely dual PPro's with 32MB RAM. -- "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 18 0:19:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 17F2337B479 for <hackers@FreeBSD.ORG>; Sat, 18 Nov 2000 00:19:33 -0800 (PST) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.0/8.11.0) id eAI8J1V20277; Sat, 18 Nov 2000 10:19:01 +0200 (SAT) (envelope-from jhay) From: John Hay <jhay@icomtek.csir.co.za> Message-Id: <200011180819.eAI8J1V20277@zibbi.icomtek.csir.co.za> Subject: Re: React to ICMP administratively prohibited ? In-Reply-To: <20001117211013.C9227@skriver.dk> from Jesper Skriver at "Nov 17, 2000 09:10:13 pm" To: jesper@skriver.dk (Jesper Skriver) Date: Sat, 18 Nov 2000 10:19:01 +0200 (SAT) Cc: hackers@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 > > I'm currently looking at how various operating systems react to a 'ICMP > administratively prohibited'. > > My motivation is setup's where access to the primary mailserver is > blocked by filters (usually to block open relay's), and all mail has to > go via the backup MX, a example from a customer of ours. > > jesper@freesbee$ host -t mx nemo.dyndns.dk > nemo.dyndns.dk mail is handled (pri=10) by nemo.dyndns.dk > nemo.dyndns.dk mail is handled (pri=20) by backup-mx.post.tele.dk > > Here we block access to tcp/25 on nemo.dyndns.dk (a ADSL users), but > provide a backup MX for him to use, but when a mailserver wants to send > mail to him, they will experience a timeout before sending the mail to > backup-mx.post.tele.dk, which can send the mail onwards to > nemo.dyndns.dk. You can also solve the problem another way. You can remove the MX for the customer machine, so that your backup-mx is the prefered MX for his mail. Then on backup-mx you can add a mailertable entry to direct the mail to his machine. Something like: nemo.dyndns.dk smtp:[nemo.dyndns.dk] The square brackets are needed to tell sendmail not to do MX lookups again. Or if you don't want to use mailertables, you can set the confTRY_NULL_MX_LIST variable to true. This way you don't have to worry how someone else's machine is going to handle those icmp packets. John -- John Hay -- John.Hay@icomtek.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 18 4: 9: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from barkley.garen.net (barkley.garen.net [209.181.43.155]) by hub.freebsd.org (Postfix) with SMTP id 9992D37B479 for <freebsd-hackers@freebsd.org>; Sat, 18 Nov 2000 04:09:02 -0800 (PST) Received: (qmail 60381 invoked by uid 1000); 18 Nov 2000 12:08:26 -0000 Date: Sat, 18 Nov 2000 04:08:25 -0800 From: Andreas Persson <pap@garen.net> To: Mohit Aron <aron@cs.rice.edu> Cc: freebsd-hackers@freebsd.org Subject: Re: slab allocator for FreeBSD Message-ID: <20001118040825.A60334@barkley.garen.net> References: <200011180012.SAA11240@cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200011180012.SAA11240@cs.rice.edu>; from aron@cs.rice.edu on Fri, Nov 17, 2000 at 06:12:49PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 17, 2000 at 06:12:49PM -0600, Mohit Aron wrote: >Hi, > does anyone know of a slab allocator implementation for BSD ? Linux >now supports a slab allocator in the kernel for efficient allocation and >deallocation of memory objects. FreeBSD supports this as well with the zone allocator. See /usr/src/sys/vm/vm_zone.[ch] for for information. It does not have page coloring though. NetBSD has a pool allocator which does something along these lines as well. >- Mohit -- Andreas Persson pap@garen.net "I could be bounded in a nutshell and count myself a king of infinite space." --Shakespeare To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 18 4:28:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.hitbase.com (ns.hitbase.com [64.65.2.58]) by hub.freebsd.org (Postfix) with ESMTP id A3C8437B479 for <freebsd-hackers@freebsd.org>; Sat, 18 Nov 2000 04:28:46 -0800 (PST) Received: from dima (ppp-237.pool-113.spbnit.ru [212.48.192.237]) by ns.hitbase.com (8.9.3/8.9.3) with SMTP id IAA11152 for <freebsd-hackers@freebsd.org>; Sat, 18 Nov 2000 08:25:16 -0500 Message-ID: <002301c05153$0e84e620$edc030d4@dima> From: "Dmitry Sychov" <accelware@accelware.com> To: <freebsd-hackers@freebsd.org> Subject: close(), shutdown() behaviour when SO_LINGER is set. Date: Sat, 18 Nov 2000 14:27:44 +0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0012_01C0516B.B70543E0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0012_01C0516B.B70543E0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Greetings! I'am developing the single thread http server which uses kqueue/kevent for both sockets and async file reads. It works just fine and I thought I 'd be able to do all the stuff with one thread until it comes to proper socket closing. As far as I understand the only way for server, working with HTTP/1.0 client, to mark the data end is to close the connection when the response was done. According to the interface this does't mean that all the packets will arrive to the client so one should set the socket option to SO_LINGER and then call close() to be sure that all the packets are acknowledged before closing the connection and make the OS handle the connection = close. The problem is, according to some posts, many systems block the process on close() or shutdown() _when_ SO_LINGER is used. My question is: Does it safe to SO_LINGER with close() or shutdown() in = FreeBSD 4.1+? Will they block or not? Thanks for all replies, Dmitry ------=_NextPart_000_0012_01C0516B.B70543E0 Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"> <HTML> <HEAD> <META content=3Dtext/html;charset=3Dkoi8-r http-equiv=3DContent-Type> <META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3D"Arial Cyr" size=3D2>Greetings!</FONT></DIV> <DIV><FONT face=3D"Arial Cyr" size=3D2></FONT> </DIV> <DIV><FONT face=3D"Arial Cyr" size=3D2>I'am developing the single thread = http=20 server</FONT></DIV> <DIV><FONT face=3D"Arial Cyr" size=3D2>which uses kqueue/kevent for both = sockets</FONT></DIV> <DIV><FONT face=3D"Arial Cyr" size=3D2>and async file reads. It works = just fine and=20 I thought</FONT></DIV> <DIV><FONT face=3D"Arial Cyr" size=3D2>I 'd be able to do all the stuff = with one=20 thread until it</FONT></DIV> <DIV><FONT face=3D"Arial Cyr" size=3D2>comes to proper socket = closing.</FONT></DIV> <DIV><FONT face=3D"Arial Cyr" size=3D2></FONT> </DIV> <DIV><FONT face=3D"Arial Cyr" size=3D2>As far as I understand the only = way for=20 server, working</FONT></DIV> <DIV><FONT face=3D"Arial Cyr" size=3D2>with HTTP/1.0 client, to mark the = data end is=20 to close the</FONT></DIV> <DIV><FONT face=3D"Arial Cyr" size=3D2>connection when the response was = done.=20 According to the</FONT></DIV> <DIV><FONT face=3D"Arial Cyr" size=3D2>interface this does't mean that = all the=20 packets will arrive to the</FONT></DIV> <DIV><FONT face=3D"Arial Cyr" size=3D2>client so one should set the = socket option to=20 SO_LINGER</FONT></DIV> <DIV><FONT face=3D"Arial Cyr" size=3D2>and then call close() to = </FONT><FONT=20 face=3D"Arial Cyr" size=3D2>be sure that all the packets are = acknowledged<BR>before=20 closing the connection and </FONT><FONT face=3D"Arial Cyr" size=3D2>make = the OS=20 handle the connection close.</FONT></DIV> <DIV><FONT face=3D"Arial Cyr" size=3D2></FONT> </DIV> <DIV><FONT face=3D"Arial Cyr" size=3D2>The problem is, according to some = posts, many=20 systems</FONT></DIV> <DIV><FONT face=3D"Arial Cyr" size=3D2>block the process on close() or = shutdown()=20 _when_ SO_LINGER is used.</FONT></DIV> <DIV><FONT face=3D"Arial Cyr" size=3D2></FONT> </DIV> <DIV><FONT face=3D"Arial Cyr" size=3D2>My question is:  Does it = safe to=20 SO_LINGER with close() or shutdown() in FreeBSD 4.1+?</FONT></DIV> <DIV><FONT face=3D"Arial Cyr" size=3D2>Will they block or = not?</FONT></DIV> <DIV><FONT face=3D"Arial Cyr" size=3D2></FONT> </DIV> <DIV><FONT face=3D"Arial Cyr" size=3D2>Thanks for all = replies,</FONT></DIV> <DIV><FONT face=3D"Arial Cyr" size=3D2></FONT><FONT face=3D"Arial Cyr"=20 size=3D2>Dmitry</FONT></DIV></BODY></HTML> ------=_NextPart_000_0012_01C0516B.B70543E0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 18 6: 3:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from nebula.cybercable.fr (d217.dhcp212-126.cybercable.fr [212.198.126.217]) by hub.freebsd.org (Postfix) with ESMTP id B026D37B479 for <freebsd-hackers@freebsd.org>; Sat, 18 Nov 2000 06:03:37 -0800 (PST) Received: (from mux@localhost) by nebula.cybercable.fr (8.11.1/8.11.1) id eAIE4kQ00290 for freebsd-hackers@freebsd.org; Sat, 18 Nov 2000 15:04:46 +0100 (CET) (envelope-from mux) Date: Sat, 18 Nov 2000 15:04:45 +0100 From: Maxime Henrion <mux@qualys.com> To: freebsd-hackers@freebsd.org Subject: kqueue()/kevent(), select() and poll() Message-ID: <20001118150445.A260@nebula.cybercable.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I was wondering if it was reasonnable to implement the select() and poll() system calls as kqueue()/kevent() wrappers. This would make any application using these system calls benefit from the performance improvements of the new kernel thread. Do you think it's possible and that it won't cause some portability problems ? Best regards, Maxime Henrion -- Don't be fooled by cheap finnish imitations ; BSD is the One True Code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 18 6:54:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 1D84B37B479 for <hackers@FreeBSD.ORG>; Sat, 18 Nov 2000 06:54:48 -0800 (PST) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id BCE1B3E5B; Sat, 18 Nov 2000 15:54:46 +0100 (CET) Date: Sat, 18 Nov 2000 15:54:46 +0100 From: Jesper Skriver <jesper@skriver.dk> To: Alfred Perlstein <bright@wintelcom.net> Cc: hackers@FreeBSD.ORG Subject: Re: React to ICMP administratively prohibited ? Message-ID: <20001118155446.A81075@skriver.dk> References: <20001117211013.C9227@skriver.dk> <20001117142904.T18037@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001117142904.T18037@fw.wintelcom.net>; from bright@wintelcom.net on Fri, Nov 17, 2000 at 02:29:04PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 17, 2000 at 02:29:04PM -0800, Alfred Perlstein wrote: > * Jesper Skriver <jesper@skriver.dk> [001117 12:11] wrote: > [snip] > > > > This timeout could be avoided if the sending mail server reacted to the > > 'ICMP administratively prohibited' they got from our router. > [snip] > > > > $ telnet nemo.dyndns.dk 25 > > Trying 193.89.247.125... > > telnet: Unable to connect to remote host: No route to host > > $ uname -a > > Linux xyz.dk 2.0.32 #1 Wed Nov 19 00:46:45 EST 1997 i586 unknown > > > > Wouldn't it be a idea to implement a similar behaviour in FreeBSD ? > > Probably not, what if one started a stream of spoofed ICMP lying > about the state of the route between the two machines? I have > the impression that the Linux box wouldn't be able to connect > because of this behavior. Correct, a attacker could in theory make sure we couldn't connect to a given remote box, but as I see it, it's mostly in teory. We could only react to this if we had a TCP session where we was waiting for a SYN/ACK from this specific host, this only leaves a very narrow window for a attacker to abuse, as he had to know both destination and time. Do you agree ? /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 18 7:21:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 8EDCA37B479 for <hackers@FreeBSD.ORG>; Sat, 18 Nov 2000 07:21:52 -0800 (PST) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 5F22A3E5C; Sat, 18 Nov 2000 16:21:51 +0100 (CET) Date: Sat, 18 Nov 2000 16:21:51 +0100 From: Jesper Skriver <jesper@skriver.dk> To: John Hay <jhay@icomtek.csir.co.za> Cc: hackers@FreeBSD.ORG Subject: Re: React to ICMP administratively prohibited ? Message-ID: <20001118162151.B81075@skriver.dk> References: <20001117211013.C9227@skriver.dk> <200011180819.eAI8J1V20277@zibbi.icomtek.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200011180819.eAI8J1V20277@zibbi.icomtek.csir.co.za>; from jhay@icomtek.csir.co.za on Sat, Nov 18, 2000 at 10:19:01AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 18, 2000 at 10:19:01AM +0200, John Hay wrote: > > > > I'm currently looking at how various operating systems react to a 'ICMP > > administratively prohibited'. > > > > My motivation is setup's where access to the primary mailserver is > > blocked by filters (usually to block open relay's), and all mail has to > > go via the backup MX, a example from a customer of ours. > > > > jesper@freesbee$ host -t mx nemo.dyndns.dk > > nemo.dyndns.dk mail is handled (pri=10) by nemo.dyndns.dk > > nemo.dyndns.dk mail is handled (pri=20) by backup-mx.post.tele.dk > > > > Here we block access to tcp/25 on nemo.dyndns.dk (a ADSL users), but > > provide a backup MX for him to use, but when a mailserver wants to send > > mail to him, they will experience a timeout before sending the mail to > > backup-mx.post.tele.dk, which can send the mail onwards to > > nemo.dyndns.dk. > > You can also solve the problem another way. You can remove the MX for > the customer machine, so that your backup-mx is the prefered MX for his > mail. Then on backup-mx you can add a mailertable entry to direct the > mail to his machine. Something like: > > nemo.dyndns.dk smtp:[nemo.dyndns.dk] I know, but this require per-domain/user configuration on backup-mx, something we want to avoid at any cost, now you're going to ask how we make sure backup-mx is not a open relay. This is ensured by a patch(*) I wrote for postfix, from sample-smtpd.cf # permit_auth_mx_backup: accept mail if all ip address(es) of the primary MX is # within $auth_mx_backup_networks, See auth_mx_backup_networks # # The auth_mx_backup_networks parameter specifies a list of networks # where Postfix will act as a backup MX host if the primary MX is # within these networks, and permit_auth_mx_backup is configured. # # The list is used by the anti-UCE software. See permit_auth_mx_backup # in the sample-smtpd.cf file. > This way you don't have to worry how someone else's machine is going > to handle those icmp packets. Your solution is a good one, if the product has a margin that allow for user specific configuration on the backup-mx, but in this case it's a ADSL product for home users, with a very little margin ... *) <http://freesbee.wheel.dk/~jesper/permit_auth_mx_backup.20001030.diff> See the postfix.users archive for history (the above patch is the same, only relative to 20001030 instead of 20000531. <http://x71.deja.com/[ST_rn=ps]/getdoc.xp?AN=648703086&CONTEXT=974559861.626524165&hitnum=26> /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 18 8: 0:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.fsbdial.co.uk (unknown [195.89.137.31]) by hub.freebsd.org (Postfix) with ESMTP id A849A37B4C5 for <hackers@freefall.cdrom.com>; Sat, 18 Nov 2000 08:00:39 -0800 (PST) Received: from [212.1.145.69] by mail.FSBDial.co.uk (NTMail 6.02.0004/NT0619.00.fa900c19) with ESMTP id czyqndaa for hackers@freefall.cdrom.com; Sat, 18 Nov 2000 15:53:59 +0000 X-Sender: jkstrading@FreeNet.co.uk From: Finances Dept <jkstrading@FreeNet.co.uk> To: "UK" <jkstrading@FreeNet.co.uk> Date: Sat, 18 Nov 2000 15:54:57 +0000 Subject: Cut your mortgage costs & get a FREE consultation Reply-To: optout@jkstrading.bizexplore.co.uk MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-Id: <15535945370822@mail.FSBDial.co.uk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Your Mortgage Options www.captainmortgage.co.uk ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Make an appointment for any of the following mortgage services and we will give you a £10 flight to New York *Terms and Conditions apply check website for details ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Want that Dream Holiday, New Car, Make those Home Improvements? Now you can! Saving up for those luxuries? The truth is you can probably afford them! By making an appointment with one of our mortgage advisers www.captainmortgage.co.uk We could re-arrange your existing mortgage payments to unlock cash when you want it! ~~~~~~~~~~~~~~~~~~~~~~~~~ Already have a Mortgage? ~~~~~~~~~~~~~~~~~~~~~~~~~ The chances are, you are paying too much for your home! Our mortgage advisors can assess your current situation and advise you on ways to Save You £1,000's on your existing home. Click here to arrange a free, no obligation appointment with an independent mortgage adviser www.captainmortgage.co.uk ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1stTime Buyer looking for Independent Mortgage advice? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Click here to make an appointment at your home, office or place of work. www.captainmortgage.co.uk With over 2,000 Mortgage advisers throughout the country we will provide you with FREE, NO COMMITMENT, INDEPENDENT Mortgage advice. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ YOUR HOME IS AT RISK IF YOU DO NOT KEEP UP REPAYMENTS ON A MORTGAGE OR OTHER LOAN SECURED ON IT. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ THIS IS NOT SPAM - To remove yourself from any further informative mail from us please right to mailto:optout@jkstrading.bizexplore.co.uk or contact the customer service dept on 0700 530 0459. In providing this information we comply with all laws and statutes governing the sending of mail to third parties. Your address was supplied as someone seeking fiancial information if you have recieved it in error or at more than one email address please accept our apologies ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 18 8: 0:54 2000 Delivered-To: freebsd-hackers@freefall.cdrom.com Received: from mail.fsbdial.co.uk (unknown [195.89.137.31]) by hub.freebsd.org (Postfix) with ESMTP id 5AF2937B4E5 for <freebsd-hackers@freefall.cdrom.com>; Sat, 18 Nov 2000 08:00:42 -0800 (PST) Received: from [212.1.145.69] by mail.FSBDial.co.uk (NTMail 6.02.0004/NT0619.00.fa900c19) with ESMTP id czyqndaa for freebsd-hackers@freefall.cdrom.com; Sat, 18 Nov 2000 15:53:59 +0000 X-Sender: jkstrading@FreeNet.co.uk From: Finances Dept <jkstrading@FreeNet.co.uk> To: "UK" <jkstrading@FreeNet.co.uk> Date: Sat, 18 Nov 2000 15:54:57 +0000 Subject: Cut your mortgage costs & get a FREE consultation Reply-To: optout@jkstrading.bizexplore.co.uk MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-Id: <15535945370822@mail.FSBDial.co.uk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Your Mortgage Options www.captainmortgage.co.uk ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Make an appointment for any of the following mortgage services and we will give you a £10 flight to New York *Terms and Conditions apply check website for details ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Want that Dream Holiday, New Car, Make those Home Improvements? Now you can! Saving up for those luxuries? The truth is you can probably afford them! By making an appointment with one of our mortgage advisers www.captainmortgage.co.uk We could re-arrange your existing mortgage payments to unlock cash when you want it! ~~~~~~~~~~~~~~~~~~~~~~~~~ Already have a Mortgage? ~~~~~~~~~~~~~~~~~~~~~~~~~ The chances are, you are paying too much for your home! Our mortgage advisors can assess your current situation and advise you on ways to Save You £1,000's on your existing home. Click here to arrange a free, no obligation appointment with an independent mortgage adviser www.captainmortgage.co.uk ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1stTime Buyer looking for Independent Mortgage advice? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Click here to make an appointment at your home, office or place of work. www.captainmortgage.co.uk With over 2,000 Mortgage advisers throughout the country we will provide you with FREE, NO COMMITMENT, INDEPENDENT Mortgage advice. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ YOUR HOME IS AT RISK IF YOU DO NOT KEEP UP REPAYMENTS ON A MORTGAGE OR OTHER LOAN SECURED ON IT. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ THIS IS NOT SPAM - To remove yourself from any further informative mail from us please right to mailto:optout@jkstrading.bizexplore.co.uk or contact the customer service dept on 0700 530 0459. In providing this information we comply with all laws and statutes governing the sending of mail to third parties. Your address was supplied as someone seeking fiancial information if you have recieved it in error or at more than one email address please accept our apologies ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 18 8:34: 7 2000 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 1096537B479; Sat, 18 Nov 2000 08:34:02 -0800 (PST) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with ESMTP id LAA45147; Sat, 18 Nov 2000 11:33:09 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20001118113245.032d3130@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sat, 18 Nov 2000 11:33:29 -0500 To: "Schmalzbauer, Harald" <H.Schmalzbauer@belenus.com>, hackers@FreeBSD.ORG, isp@FreeBSD.ORG From: Dennis <dennis@etinc.com> Subject: Re: AW: Best Gigabit ethernet for 4.x In-Reply-To: <B14AF62CDA08D4118B8C00508B44A0B5154E4E@server02.belenus.co m> 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 04:28 PM 11/17/2000, Schmalzbauer, Harald wrote: >I just heard that Intel doesn't supply documentation on ther chipset and the >FreeBSD and Linux support is quiet bad. The Netgear GA620 is said to be >twice as fast. The same Chipset (Alteon Tigon/AceNIC) is on the 3com985. Are all of the cards supported that use this chipset? I read somewhere that the netgear card has a smallish buffer, and that the alteon was a better choice. How does the 3com card compare in that respect? 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 18 9: 5: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-c.mdsn1.wi.home.com [24.183.3.139]) by hub.freebsd.org (Postfix) with ESMTP id A8F3B37B479 for <hackers@FreeBSD.ORG>; Sat, 18 Nov 2000 09:05:00 -0800 (PST) Received: (qmail 52998 invoked by uid 1000); 18 Nov 2000 17:04:55 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 18 Nov 2000 17:04:55 -0000 Date: Sat, 18 Nov 2000 11:04:55 -0600 (CST) From: Mike Silbersack <silby@silby.com> To: Jesper Skriver <jesper@skriver.dk> Cc: Alfred Perlstein <bright@wintelcom.net>, hackers@FreeBSD.ORG Subject: Re: React to ICMP administratively prohibited ? In-Reply-To: <20001118155446.A81075@skriver.dk> Message-ID: <Pine.BSF.4.21.0011181102540.52996-100000@achilles.silby.com> 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, 18 Nov 2000, Jesper Skriver wrote: > On Fri, Nov 17, 2000 at 02:29:04PM -0800, Alfred Perlstein wrote: > > > > Probably not, what if one started a stream of spoofed ICMP lying > > about the state of the route between the two machines? I have > > the impression that the Linux box wouldn't be able to connect > > because of this behavior. > > Correct, a attacker could in theory make sure we couldn't connect to > a given remote box, but as I see it, it's mostly in teory. > > We could only react to this if we had a TCP session where we was > waiting for a SYN/ACK from this specific host, this only leaves a very > narrow window for a attacker to abuse, as he had to know both > destination and time. > > Do you agree ? > > /Jesper Well, if you honor such messages, don't you have to honor them in the middle of a connection too? Then you could cause a connection drop at any time. It would seem simpler to have the ISP in question use proper RST responses, or just stop filtering totally. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 18 9:22:46 2000 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 4802B37B479 for <freebsd-hackers@FreeBSD.ORG>; Sat, 18 Nov 2000 09:22:45 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAIHMdL20692; Sat, 18 Nov 2000 09:22:39 -0800 (PST) Date: Sat, 18 Nov 2000 09:22:39 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: Maxime Henrion <mux@qualys.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: kqueue()/kevent(), select() and poll() Message-ID: <20001118092238.B18037@fw.wintelcom.net> References: <20001118150445.A260@nebula.cybercable.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001118150445.A260@nebula.cybercable.fr>; from mux@qualys.com on Sat, Nov 18, 2000 at 03:04:45PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Maxime Henrion <mux@qualys.com> [001118 06:03] wrote: > Hi, > > I was wondering if it was reasonnable to implement the select() and poll() > system calls as kqueue()/kevent() wrappers. This would make any application > using these system calls benefit from the performance improvements of the new > kernel thread. > > Do you think it's possible and that it won't cause some portability problems ? It would just cause more overhead. To implement select()/poll() using kevent would necessitate building up an eventlist that was comprised of EVFILT_ONESHOT events, then after return or timeout clearing the events that hadn't fired. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 18 9:23:37 2000 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 9183B37B4C5 for <hackers@FreeBSD.ORG>; Sat, 18 Nov 2000 09:23:35 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAIHNWN20716; Sat, 18 Nov 2000 09:23:32 -0800 (PST) Date: Sat, 18 Nov 2000 09:23:32 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: Jesper Skriver <jesper@skriver.dk> Cc: hackers@FreeBSD.ORG Subject: Re: React to ICMP administratively prohibited ? Message-ID: <20001118092332.C18037@fw.wintelcom.net> References: <20001117211013.C9227@skriver.dk> <20001117142904.T18037@fw.wintelcom.net> <20001118155446.A81075@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001118155446.A81075@skriver.dk>; from jesper@skriver.dk on Sat, Nov 18, 2000 at 03:54:46PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jesper Skriver <jesper@skriver.dk> [001118 06:54] wrote: > On Fri, Nov 17, 2000 at 02:29:04PM -0800, Alfred Perlstein wrote: > > * Jesper Skriver <jesper@skriver.dk> [001117 12:11] wrote: > > [snip] > > > > > > This timeout could be avoided if the sending mail server reacted to the > > > 'ICMP administratively prohibited' they got from our router. > > [snip] > > > > > > $ telnet nemo.dyndns.dk 25 > > > Trying 193.89.247.125... > > > telnet: Unable to connect to remote host: No route to host > > > $ uname -a > > > Linux xyz.dk 2.0.32 #1 Wed Nov 19 00:46:45 EST 1997 i586 unknown > > > > > > Wouldn't it be a idea to implement a similar behaviour in FreeBSD ? > > > > Probably not, what if one started a stream of spoofed ICMP lying > > about the state of the route between the two machines? I have > > the impression that the Linux box wouldn't be able to connect > > because of this behavior. > > Correct, a attacker could in theory make sure we couldn't connect to > a given remote box, but as I see it, it's mostly in teory. > > We could only react to this if we had a TCP session where we was > waiting for a SYN/ACK from this specific host, this only leaves a very > narrow window for a attacker to abuse, as he had to know both > destination and time. > > Do you agree ? If I agreed I wouldn't have objected in the first place. :( -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 18 9:36:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 8B65037B479 for <hackers@FreeBSD.ORG>; Sat, 18 Nov 2000 09:36:34 -0800 (PST) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id A183D3E5B; Sat, 18 Nov 2000 18:36:32 +0100 (CET) Date: Sat, 18 Nov 2000 18:36:32 +0100 From: Jesper Skriver <jesper@skriver.dk> To: Mike Silbersack <silby@silby.com> Cc: Alfred Perlstein <bright@wintelcom.net>, hackers@FreeBSD.ORG Subject: Re: React to ICMP administratively prohibited ? Message-ID: <20001118183632.A99512@skriver.dk> References: <20001118155446.A81075@skriver.dk> <Pine.BSF.4.21.0011181102540.52996-100000@achilles.silby.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <Pine.BSF.4.21.0011181102540.52996-100000@achilles.silby.com>; from silby@silby.com on Sat, Nov 18, 2000 at 11:04:55AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 18, 2000 at 11:04:55AM -0600, Mike Silbersack wrote: > > On Sat, 18 Nov 2000, Jesper Skriver wrote: > > > On Fri, Nov 17, 2000 at 02:29:04PM -0800, Alfred Perlstein wrote: > > > > > > Probably not, what if one started a stream of spoofed ICMP lying > > > about the state of the route between the two machines? I have > > > the impression that the Linux box wouldn't be able to connect > > > because of this behavior. > > > > Correct, a attacker could in theory make sure we couldn't connect to > > a given remote box, but as I see it, it's mostly in teory. > > > > We could only react to this if we had a TCP session where we was > > waiting for a SYN/ACK from this specific host, this only leaves a very > > narrow window for a attacker to abuse, as he had to know both > > destination and time. > > > > Do you agree ? > > > > /Jesper > > Well, if you honor such messages, don't you have to honor them in the > middle of a connection too? Then you could cause a connection drop at any > time. I cannot see why we should honor them "in the middle of a connection", the real problem exist when setting up TCP sessions, if someone configure a filter when there are existing connections, they will die due to lack of response, but this would be a one time event. > It would seem simpler to have the ISP in question use proper RST > responses The problem is that the largest router vendor (Cisco) cannot do this. > or just stop filtering totally. Which is not a option in this case, and in the real world it's that uncommon. I'll see if I can get code together which will do this. If we leave this off by default, would people object to putting in this functionality ? /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 18 10:35:53 2000 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 8718E37B4CF for <hackers@FreeBSD.ORG>; Sat, 18 Nov 2000 10:35:50 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAIIZjI22481; Sat, 18 Nov 2000 10:35:45 -0800 (PST) Date: Sat, 18 Nov 2000 10:35:45 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: Jesper Skriver <jesper@skriver.dk> Cc: Mike Silbersack <silby@silby.com>, hackers@FreeBSD.ORG Subject: Re: React to ICMP administratively prohibited ? Message-ID: <20001118103545.F18037@fw.wintelcom.net> References: <20001118155446.A81075@skriver.dk> <Pine.BSF.4.21.0011181102540.52996-100000@achilles.silby.com> <20001118183632.A99512@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001118183632.A99512@skriver.dk>; from jesper@skriver.dk on Sat, Nov 18, 2000 at 06:36:32PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jesper Skriver <jesper@skriver.dk> [001118 09:36] wrote: > > Which is not a option in this case, and in the real world it's that > uncommon. > > I'll see if I can get code together which will do this. > > If we leave this off by default, would people object to putting in > this functionality ? I wouldn't object as long as it was not the default. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 18 13:18:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-c.mdsn1.wi.home.com [24.183.3.139]) by hub.freebsd.org (Postfix) with ESMTP id 0BB3137B479 for <hackers@FreeBSD.ORG>; Sat, 18 Nov 2000 13:18:37 -0800 (PST) Received: (qmail 53216 invoked by uid 1000); 18 Nov 2000 21:18:36 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 18 Nov 2000 21:18:36 -0000 Date: Sat, 18 Nov 2000 15:18:36 -0600 (CST) From: Mike Silbersack <silby@silby.com> To: Jesper Skriver <jesper@skriver.dk> Cc: Alfred Perlstein <bright@wintelcom.net>, hackers@FreeBSD.ORG Subject: Re: React to ICMP administratively prohibited ? In-Reply-To: <20001118183632.A99512@skriver.dk> Message-ID: <Pine.BSF.4.21.0011181510400.53208-100000@achilles.silby.com> 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, 18 Nov 2000, Jesper Skriver wrote: > > or just stop filtering totally. > > Which is not a option in this case, and in the real world it's that > uncommon. > > I'll see if I can get code together which will do this. > > If we leave this off by default, would people object to putting in > this functionality ? > > /Jesper What's the point? If people complain about a badly setup MX behind a firewall, are you going to respond and tell them to flip a sysctl? This isn't a case of interoperability with a common TCP stack which needs to be lived with. It's a case of something that is broken even with the suggested "fix". The correct thing to do in this situation is to configure sendmail properly so that the MX silliness isn't needed. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 18 13:32:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dayspring.firedrake.org (dayspring.firedrake.org [195.82.105.251]) by hub.freebsd.org (Postfix) with ESMTP id F1A0037B479 for <hackers@freebsd.org>; Sat, 18 Nov 2000 13:32:30 -0800 (PST) Received: from float by dayspring.firedrake.org with local (Exim 3.12 #1 (Debian)) id 13xFay-0005mj-00; Sat, 18 Nov 2000 21:32:24 +0000 Date: Sat, 18 Nov 2000 21:32:24 +0000 To: hackers@freebsd.org Subject: "device not configured" from sa driver Message-ID: <20001118213224.A22036@firedrake.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i From: void <float@firedrake.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have set up a tape drive, correctly I believe, yet I keep getting "device not configured" errors from it. See: http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=2849646+2851949+/usr/local/www/db/text/2000/freebsd-questions/20001029.freebsd-questions Some have said that this error indicates no tapes in the drive, but the drive does have tapes in it. What else could it indicate? I tried reading the source, but I found it beyond me. -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 18 13:37:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id A522D37B479 for <hackers@FreeBSD.ORG>; Sat, 18 Nov 2000 13:37:28 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA19391; Sat, 18 Nov 2000 13:37:17 -0800 Date: Sat, 18 Nov 2000 13:37:14 -0800 (PST) From: Matthew Jacob <mjacob@feral.com> Reply-To: mjacob@feral.com To: void <float@firedrake.org> Cc: hackers@FreeBSD.ORG Subject: Re: "device not configured" from sa driver In-Reply-To: <20001118213224.A22036@firedrake.org> Message-ID: <Pine.LNX.4.21.0011181334530.13406-100000@zeppo.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try an mt -f /dev/nrsa0 status and mt -f /dev/nrsa1 status The ctl node specifically makes no access to the device. If there is indeed a tape inserted, build a CAMDEBUG kernel, boot it, and do camcontrol debug -Ic b:t:l (b = bus, t = target, l = lun) and then do the 'mt status' dance as above and send to scsi@freebsd.org (the appropriate list- not hackers). I'm the tape driver maintainer, but I'll be out of town this next week. > I have set up a tape drive, correctly I believe, yet I keep getting > "device not configured" errors from it. See: > > http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=2849646+2851949+/usr/local/www/db/text/2000/freebsd-questions/20001029.freebsd-questions > > Some have said that this error indicates no tapes in the drive, but the > drive does have tapes in it. What else could it indicate? I tried > reading the source, but I found it beyond me. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 18 13:51:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 0E89937B4C5 for <hackers@FreeBSD.ORG>; Sat, 18 Nov 2000 13:51:21 -0800 (PST) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 93BE33E5B; Sat, 18 Nov 2000 22:51:19 +0100 (CET) Date: Sat, 18 Nov 2000 22:51:19 +0100 From: Jesper Skriver <jesper@skriver.dk> To: Mike Silbersack <silby@silby.com> Cc: Alfred Perlstein <bright@wintelcom.net>, hackers@FreeBSD.ORG Subject: Re: React to ICMP administratively prohibited ? Message-ID: <20001118225119.B73853@skriver.dk> References: <20001118183632.A99512@skriver.dk> <Pine.BSF.4.21.0011181510400.53208-100000@achilles.silby.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <Pine.BSF.4.21.0011181510400.53208-100000@achilles.silby.com>; from silby@silby.com on Sat, Nov 18, 2000 at 03:18:36PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 18, 2000 at 03:18:36PM -0600, Mike Silbersack wrote: > > On Sat, 18 Nov 2000, Jesper Skriver wrote: > > > > or just stop filtering totally. > > > > Which is not a option in this case, and in the real world it's that > > uncommon. > > > > I'll see if I can get code together which will do this. > > > > If we leave this off by default, would people object to putting in > > this functionality ? > > > > /Jesper > > What's the point? If people complain about a badly setup MX behind a > firewall, are you going to respond and tell them to flip a sysctl? My motivation is primarily to get the code working, and perhaps in the future get it enabled by default. But until then tell people that a sysctl can get this behaviour. > This isn't a case of interoperability with a common TCP stack which needs > to be lived with. It's a case of something that is broken even with the > suggested "fix". I wouldn't call it broken, why should the routers bother to send a ICMP access prohibited (or any of the other unreachables) if nobody cares anyway. My approach is a bit more pragmatic, and as I can see it, the chance that a attacker can abuse this seems very slim. > The correct thing to do in this situation is to configure sendmail > properly so that the MX silliness isn't needed. Using a static mail routing from a public known MX to the real mailserver is certainly a better solution if the same people control both, but in this case it's not like that. Let me explain in a bit more detail. We have lots of ADSL users (potentially hundreds of thousands), lots of these have open relays(*) that relay via our mailservers, making our mailservers open for spammers to use. The best solution we have been able to find, was the filters that block access to tcp/25 except from the backup-mx host, this eliminated the open relays once and for all, with very little work. We have no knowledge of which domains the users have (and this also changes all the time), and the price structure doesn't leave room for the hazzle of maintaining (and supporting) such static mail routing table, it's also significantly easier for the users to understand why they should configure xyz.dk. IN MX 10 xyz.dk. xyz.dk. IN MX 20 backup-mx.post.tele.dk. than xyz.dk. IN MX 10 backup-mx.post.tele.dk. And then do what ever to get the static mail routing configured. *) Often a simple "gateway" like WinGate or similar with by default seems to give this "functionality" :-( /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 18 14: 4:58 2000 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 2E05737B479; Sat, 18 Nov 2000 14:04:54 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA16058; Sat, 18 Nov 2000 15:04:37 -0700 (MST) (envelope-from ken) Date: Sat, 18 Nov 2000 15:04:37 -0700 From: "Kenneth D. Merry" <ken@kdm.org> To: Dennis <dennis@etinc.com> Cc: "Schmalzbauer, Harald" <H.Schmalzbauer@belenus.com>, hackers@FreeBSD.ORG, isp@FreeBSD.ORG Subject: Re: AW: Best Gigabit ethernet for 4.x Message-ID: <20001118150437.A15956@panzer.kdm.org> References: <B14AF62CDA08D4118B8C00508B44A0B5154E4E@server02.belenus.co m> <5.0.0.25.0.20001118113245.032d3130@mail.etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <5.0.0.25.0.20001118113245.032d3130@mail.etinc.com>; from dennis@etinc.com on Sat, Nov 18, 2000 at 11:33:29AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 18, 2000 at 11:33:29 -0500, Dennis wrote: > At 04:28 PM 11/17/2000, Schmalzbauer, Harald wrote: > >I just heard that Intel doesn't supply documentation on ther chipset and the > >FreeBSD and Linux support is quiet bad. The Netgear GA620 is said to be > >twice as fast. The same Chipset (Alteon Tigon/AceNIC) is on the 3com985. > > > Are all of the cards supported that use this chipset? I read somewhere that > the netgear card has a smallish buffer, and that the alteon was a better > choice. How does the 3com card compare in that respect? The Netgear boards have 512K SRAM, the 3Com boards have 1MB SRAM. You can get Alteon-branded boards (with either 512K or 1MB SRAM), but generally only directly from Alteon, and you're going to pay more than you would for either the 3Com or Netgear boards. The 3Com and Netgear boards are identical to the Alteon boards. The only difference is they've got "Netgear" or "3Com" silk-screened on them, and the Alteon boards don't have any logos on them. FWIW, 3Com is buying Alteon's NIC group. Apparantly (according to an Alteon engineer who posted on the linux-acenic list) they're just buying the technology, not hiring the engineers: http://dailynews.yahoo.com/h/nm/20001115/tc/nortel_com_dc_4.html 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 Sat Nov 18 14:24: 4 2000 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 7365A37B479 for <hackers@FreeBSD.ORG>; Sat, 18 Nov 2000 14:24:01 -0800 (PST) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.1/8.11.0) with ESMTP id eAIMNs747524; Sat, 18 Nov 2000 17:23:54 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200011182223.eAIMNs747524@whizzo.transsys.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Mike Silbersack <silby@silby.com> Cc: Jesper Skriver <jesper@skriver.dk>, Alfred Perlstein <bright@wintelcom.net>, hackers@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" <louie@TransSys.COM> Subject: Re: React to ICMP administratively prohibited ? References: <Pine.BSF.4.21.0011181102540.52996-100000@achilles.silby.com> In-reply-to: Your message of "Sat, 18 Nov 2000 11:04:55 CST." <Pine.BSF.4.21.0011181102540.52996-100000@achilles.silby.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Nov 2000 17:23:54 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Sat, 18 Nov 2000, Jesper Skriver wrote: > > > On Fri, Nov 17, 2000 at 02:29:04PM -0800, Alfred Perlstein wrote: > > > > > > Probably not, what if one started a stream of spoofed ICMP lying > > > about the state of the route between the two machines? I have > > > the impression that the Linux box wouldn't be able to connect > > > because of this behavior. > > > > Correct, a attacker could in theory make sure we couldn't connect to > > a given remote box, but as I see it, it's mostly in teory. > > > > We could only react to this if we had a TCP session where we was > > waiting for a SYN/ACK from this specific host, this only leaves a very > > narrow window for a attacker to abuse, as he had to know both > > destination and time. > > > > Do you agree ? > > > > /Jesper > > Well, if you honor such messages, don't you have to honor them in the > middle of a connection too? Then you could cause a connection drop at any > time. No, you don't. This is a replay of discussions that happened literally 20 years ago as the first TCP implementations were being done. I believe the acceptable practice at the time was to honor an ICMP advisory (e.g., pass it to TCP to have it abort the pending connection) while in SYN-SENT state. That is, when initially trying to open the connection, give up sooner based on the ICMP message, rather than waiting for an ACK timeout. If an ICMP message associated with a connection was received after the connection passed to ESTABLISHED state, then you could choose to pass an advisory to the application, but not abort the connection. The Berkeley network stack did this, and a variety of applications would give up and die should they get an error return from a read() or write() system call on the connection, even though it was still alive. I think that behavior may have changed, but I haven't check anytime recently. At the time, the anticipated source of ICMP messages were Destination Unreachable advisories, provoked by either permanant or transient routing failures to the destination. > It would seem simpler to have the ISP in question use proper RST > responses, or just stop filtering totally. This behavior, while widely implemented, is a hack and a kludge. An intermediate network element isn't supposed to spoof source address and return responses on behalf of some other system. This only works for TCP, and only if you can see the headers (e.g., not encrypted with IPSEC). louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 18 14:28:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.welearn.com.au (phoenix.welearn.com.au [139.130.44.81]) by hub.freebsd.org (Postfix) with ESMTP id 07EDC37B479; Sat, 18 Nov 2000 14:28:19 -0800 (PST) Received: (from sue@localhost) by phoenix.welearn.com.au (8.9.3/8.9.3) id JAA91099; Sun, 19 Nov 2000 09:33:40 +1100 (EST) (envelope-from sue) Date: Sun, 19 Nov 2000 09:33:33 +1100 From: Sue Blake <sue@welearn.com.au> To: "Koster, K.J." <K.J.Koster@kpn.com> Cc: "'FreeBSD Hackers mailing list'" <freebsd-hackers@FreeBSD.ORG>, Paul Richards <paul@FreeBSD.ORG> Subject: Re: Legacy ethernet cards in FreeBSD Message-ID: <20001119093322.B90638@welearn.com.au> Mail-Followup-To: "Koster, K.J." <K.J.Koster@kpn.com>, 'FreeBSD Hackers mailing list' <freebsd-hackers@FreeBSD.ORG>, Paul Richards <paul@freebsd.org> References: <59063B5B4D98D311BC0D0001FA7E4522026D79E3@l04.research.kpn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <59063B5B4D98D311BC0D0001FA7E4522026D79E3@l04.research.kpn.com>; from Koster, K.J. on Fri, Nov 10, 2000 at 02:27:31PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 10, 2000 at 02:27:31PM +0100, Koster, K.J. wrote: > If there are people who are cleaning up the support for older network cards > in FreeBSD I'd like to help out by sending you my old NICs. It's not like > they're any good to me without OS support. > > Please contact me off-list for any of the following cards: > > 3Com 3c503 ISA > DEC Etherworks ISA > DEC DE205 ISA > SMC EtherEZ ISA > RealTek "TP-Link" PCI That's great, thank you! :-) When I had similar problems, I searched the web site for relevant PRs and found that although the problem wasn't widely known, I was not alone. As far as the DEC cards go, see PR misc/18641, we have been trying to get some old DEC cards to Paul Richards so that he can work on a fix for the le(4) driver, but fate keeps getting in the way. (BTW, I'm using these fine with FreeBSD 3.3 but 3.5 and above don't work) Please contact Paul if you can arrange to send the DEC cards to the UK. -- Regards, -*Sue*- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 18 16:31:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from portnoy.lbl.gov (portnoy.lbl.gov [131.243.2.11]) by hub.freebsd.org (Postfix) with ESMTP id 3B0CD37B479 for <hackers@FreeBSD.ORG>; Sat, 18 Nov 2000 16:31:19 -0800 (PST) Received: (from jin@localhost) by portnoy.lbl.gov (8.11.1/8.11.1) id eAJ0VBo29408; Sat, 18 Nov 2000 16:31:11 -0800 (PST) Date: Sat, 18 Nov 2000 16:31:11 -0800 (PST) From: Jin Guojun (DSD staff) <jin@george.lbl.gov> Message-Id: <200011190031.eAJ0VBo29408@portnoy.lbl.gov> To: bmilekic@dsuper.net Subject: sendfile for raw disk (was: zero copy TCP) Cc: hackers@FreeBSD.ORG, jin@george.lbl.gov Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Both, but I may do either way, depending on which way is easier. > > If we can directly DMA from a disk drive to a NIC, that will be great. > > If the current implementation requires preloaded buffer, that works. > > So, where can I look for the patch? > > > > Please see sendfile(2). It seems that sendfile(2) can read only a regular file. I wiould like to modify it to send a raw disk block. Before going for it, I would like to know what was the reason for not doing this, and what may be the issus for doing this? -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 18 17:24:39 2000 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 E42AC37B479 for <hackers@FreeBSD.ORG>; Sat, 18 Nov 2000 17:24:36 -0800 (PST) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id RAA06983; Sat, 18 Nov 2000 17:23:32 -0800 (PST) Message-Id: <200011190123.RAA06983@implode.root.com> To: Jin Guojun (DSD staff) <jin@george.lbl.gov> Cc: bmilekic@dsuper.net, hackers@FreeBSD.ORG Subject: Re: sendfile for raw disk (was: zero copy TCP) In-reply-to: Your message of "Sat, 18 Nov 2000 16:31:11 PST." <200011190031.eAJ0VBo29408@portnoy.lbl.gov> From: David Greenman <dg@root.com> Reply-To: dg@root.com Date: Sat, 18 Nov 2000 17:23:31 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > Both, but I may do either way, depending on which way is easier. >> > If we can directly DMA from a disk drive to a NIC, that will be great. >> > If the current implementation requires preloaded buffer, that works. >> > So, where can I look for the patch? >> > >> >> Please see sendfile(2). > >It seems that sendfile(2) can read only a regular file. I wiould like to >modify it to send a raw disk block. >Before going for it, I would like to know what was the reason for not doing >this, and what may be the issus for doing this? The main issue is that sendfile() is very much VM-system centric in the way that it implements zero-copy sends. In order for raw devices to work, you would need to have a raw device vm_object to hold the pages. The problem with this is that it creates cache coherency problems with any cached file data. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - 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